1. 13 2月, 2012 5 次提交
  2. 23 12月, 2011 1 次提交
  3. 19 12月, 2011 7 次提交
  4. 17 12月, 2011 3 次提交
  5. 03 12月, 2011 1 次提交
  6. 08 11月, 2011 4 次提交
    • A
      Bluetooth: Define HCI reasons instead of magic number · 9f5a0d7b
      Andrei Emeltchenko 提交于
      Use HCI error reasons instead of magic numbers.
      Signed-off-by: NAndrei Emeltchenko <andrei.emeltchenko@intel.com>
      Acked-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      9f5a0d7b
    • L
      Bluetooth: prioritizing data over HCI · 73d80deb
      Luiz Augusto von Dentz 提交于
      This implement priority based scheduler using skbuffer priority set via
      SO_PRIORITY socket option.
      
      It introduces hci_chan_hash (list of HCI Channel/hci_chan) per connection,
      each item in this list refer to a L2CAP connection and it is used to
      queue the data for transmission.
      Signed-off-by: NLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
      Acked-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      73d80deb
    • L
      Bluetooth: replace list_for_each with list_for_each_entry whenever possible · 8035ded4
      Luiz Augusto von Dentz 提交于
      When all items in the list have the same type there is no much of a point
      to use list_for_each except if you want to use the list pointer itself.
      Signed-off-by: NLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      8035ded4
    • A
      Bluetooth: Revert: Fix L2CAP connection establishment · 4dff523a
      Arek Lichwa 提交于
      This reverts commit 33060542.
      The commit introduces regression when two 2.1 devices attempt
      establish rfcomm channel. Such connection is refused since there's
      a security block issue on l2cap. It means the link is unencrypted.
      
      2011-09-16 18:08:46.567616 < ACL data: handle 1 flags 0x00 dlen 24
          0000: 14 00 40 00 06 00 02 00  0f 35 03 19 12 00 ff ff
      ..@......5....˙˙
          0010: 35 05 0a 00 00 ff ff 00                           5....˙˙.
      2011-09-16 18:08:46.572377 > HCI Event: Number of Completed Packets
      (0x13) plen 5
          handle 1 packets 1
      2011-09-16 18:08:46.577931 > ACL data: handle 1 flags 0x02 dlen 88
          L2CAP(d): cid 0x0040 len 84 [psm 0]
            0000: 07 00 02 00 4f 00 4c 35  4a 35 48 09 00 00 0a 00
      ....O.L5J5H.....
            0010: 01 00 00 09 00 01 35 03  19 12 00 09 00 05 35 03
      ......5.......5.
            0020: 19 10 02 09 00 09 35 08  35 06 19 12 00 09 01 02
      ......5.5.......
            0030: 09 02 00 09 01 02 09 02  01 09 00 0a 09 02 02 09
      ................
            0040: 00 00 09 02 03 09 00 00  09 02 04 28 01 09 02 05
      ...........(....
            0050: 09 00 02 00                                       ....
      2011-09-16 18:08:46.626057 < HCI Command: Authentication Requested
      (0x01|0x0011) plen 2
          handle 1
      2011-09-16 18:08:46.627614 > HCI Event: Command Status (0x0f) plen 4
          Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
      2011-09-16 18:08:46.627675 > HCI Event: Link Key Request (0x17) plen 6
          bdaddr 00:00:F2:6A:29:69
      2011-09-16 18:08:46.634999 < HCI Command: Link Key Request Reply
      (0x01|0x000b) plen 22
          bdaddr 00:00:F2:6A:29:69 key 58CD393179FC902E5E8F512A855EE532
      2011-09-16 18:08:46.683278 > HCI Event: Command Complete (0x0e) plen 10
          Link Key Request Reply (0x01|0x000b) ncmd 1
          status 0x00 bdaddr 00:00:F2:6A:29:69
      2011-09-16 18:08:46.764729 > HCI Event: Auth Complete (0x06) plen 3
          status 0x00 handle 1
      2011-09-16 18:08:46.764821 < ACL data: handle 1 flags 0x00 dlen 12
          0000: 08 00 01 00 02 05 04 00  03 00 41 00              ..........A.
      2011-09-16 18:08:46.764851 > HCI Event: Command Status (0x0f) plen 4
          Unknown (0x00|0x0000) status 0x00 ncmd 2
      2011-09-16 18:08:46.768117 > HCI Event: Number of Completed Packets
      (0x13) plen 5
          handle 1 packets 1
      2011-09-16 18:08:46.770894 > ACL data: handle 1 flags 0x02 dlen 16
          L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0
            Connection refused - security block
      2011-09-16 18:08:49.000691 < ACL data: handle 1 flags 0x00 dlen 12
          0000: 08 00 01 00 06 06 04 00  40 00 40 00              ........@.@.
      2011-09-16 18:08:49.015675 > HCI Event: Number of Completed Packets
      (0x13) plen 5
          handle 1 packets 1
      2011-09-16 18:08:49.016927 > ACL data: handle 1 flags 0x02 dlen 12
          L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
      2011-09-16 18:08:51.009480 < HCI Command: Disconnect (0x01|0x0006) plen
      3
          handle 1 reason 0x13
          Reason: Remote User Terminated Connection
      2011-09-16 18:08:51.011525 > HCI Event: Command Status (0x0f) plen 4
          Disconnect (0x01|0x0006) status 0x00 ncmd 1
      2011-09-16 18:08:51.123494 > HCI Event: Disconn Complete (0x05) plen 4
          status 0x00 handle 1 reason 0x16
          Reason: Connection Terminated by Local Host
      Signed-off-by: NArek Lichwa <arkadiusz.lichwa@tieto.com>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      4dff523a
  7. 28 9月, 2011 1 次提交
    • A
      Bluetooth: use recommended LE connection parameters · 0e833915
      Anderson Lizardo 提交于
      The new connection parameters now match the recommended values for
      Proximity and Health Thermometer profiles. The previous values were
      ramdomly chosen, and are either too low or too high for most cases.
      
      New values:
      
      Scan Interval: 60 ms
      Scan Window: 30 ms
      Minimum Connection Interval: 50 ms
      Maximum Connection Interval: 70 ms
      Supervision Timeout: 420 ms
      
      See "Table 5.2: Recommended Scan Interval and Scan Window Values" and
      "Table 5.3: Recommended Connection Interval Values" for both profiles
      for details. Note that the "fast connection" parameters were chosen,
      because we do not support yet dynamically changing these parameters from
      initiator side.
      
      Additionally, the Proximity profile recommends (section "4.4 Alert on
      Link Loss"):
      
      "It is recommended that the Link Supervision Timeout (LSTO) is set to 6x
      the connection interval."
      
      Minimum_CE_Length and Maximum_CE_Length were also changed from 0x0001 to
      0x0000 because they are informational and optional, and old value was
      not reflecting reality.
      Signed-off-by: NAnderson Lizardo <anderson.lizardo@openbossa.org>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      0e833915
  8. 21 9月, 2011 1 次提交
  9. 01 7月, 2011 1 次提交
  10. 16 6月, 2011 1 次提交
  11. 14 6月, 2011 3 次提交
  12. 09 6月, 2011 6 次提交
  13. 12 5月, 2011 1 次提交
  14. 29 4月, 2011 2 次提交
  15. 28 2月, 2011 1 次提交
  16. 22 2月, 2011 2 次提交