An error occurred fetching the project authors.
  1. 01 Nov, 2012 2 commits
  2. 24 Oct, 2012 3 commits
  3. 15 Oct, 2012 1 commit
  4. 08 Oct, 2012 1 commit
  5. 07 Oct, 2012 1 commit
  6. 27 Sep, 2012 3 commits
  7. 21 Aug, 2012 1 commit
  8. 06 Aug, 2012 2 commits
  9. 15 Jul, 2012 1 commit
    • Mat Martineau's avatar
      Bluetooth: Use tx window from config response for ack timing · c20f8e35
      Mat Martineau authored
      This change addresses an L2CAP ERTM throughput problem when a remote
      device does not fully utilize the available transmit window.
      
      The L2CAP ERTM transmit window size determines the maximum number of
      unacked frames that may be outstanding at any time. It is configured
      separately for each direction of an ERTM connection. Each side sends a
      configuration request with a tx_win field indicating how many unacked
      frames it is capable of receiving before sending an ack. The
      configuration response's tx_win field shows how many frames the
      transmitter will actually send before waiting for an ack.
      
      It's important to trace both the actual transmit window (to check for
      validity of incoming frames) and the number of frames that the
      transmitter will send before waiting (to send acks at the appropriate
      time). Now there are separate tx_win and ack_win values. ack_win is
      updated based on configuration responses, and is used to determine
      when acks are sent.
      Signed-off-by: default avatarMat Martineau <mathewm@codeaurora.org>
      Signed-off-by: default avatarGustavo Padovan <gustavo.padovan@collabora.co.uk>
      c20f8e35
  10. 11 Jul, 2012 1 commit
  11. 05 Jun, 2012 13 commits
  12. 09 May, 2012 11 commits