| 285f7c6527244c749aafdc1edec39787e12bd871 |
|
26-Nov-2014 |
Zhenye Zhu <zhenye@broadcom.com> |
PAN TAP fd is not monitored in all cases
Bug: 18271987
Change-Id: I348f3851a955b5277e7cdf0102583eaaef2ef0f3
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 95ca3c43eae763465bbd7bddc927279f17b16106 |
|
26-Aug-2014 |
Zhenye Zhu <zhenye@broadcom.com> |
Limit the time PAN can occupy the BTU stack thread
Also make sure tap read/write are non-blocking and PAN does not use the
complete shared buffer pool to avoid GKI buffer overruns.
Bug: 16374840
Change-Id: I6f96d1c8d2804d253d33fe37ff87275e03e55ddd
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| e85eb5a7c3ea7eaca09cbb33920435d809b4dd3d |
|
03-Oct-2013 |
Nitin Shivpure <nshivpur@codeaurora.org> |
Bluetooth: Cleaning up pan_conn DB, if connection is not successful. - do not merge
A case where DUT is paired with remoteDeviceA & remoteDeviceB.
remoteDeviceA is not pagable(turned off or some other reason).
DUT(PANU) try to connect remoteDeviceA(NAP). But connection is
unsuccessful, Because remoteDeviceA is not pagable, In this scenario
btpan_conn Database is not cleaning up at btif layer. Later
remoteDeviceB(PANU) connect to DUT(NAP) & connection is succesful,
When remoteDeviceB disconnect existing connection. As database
still has remoteDeviceA BD address at Btif layer. remoteDeviceA
BD address is passed instead of remoteDeviceB BD address from Btif
to UI. So remoteDeviceB still shows connected on UI. Cleaning up
pan_conn database for particular pan connection at BTIF layer,
whichever connection is not successful will solve this issue.
Change-Id: I31dfe3ef46295e74bbfb57563e4fd4fc7155f006
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master
Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
| e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL.
Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 533cc76a012444993eb5e566238f71fc9f24ba0d |
|
19-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 27232899: am 283aa16d: Merge "Bluedroid: Avoid multicast address for tun-tap interface"
* commit '2723289960c3eca333aa25369bde59cf8d36dcf4':
Bluedroid: Avoid multicast address for tun-tap interface
|
| 2723289960c3eca333aa25369bde59cf8d36dcf4 |
|
19-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 283aa16d: Merge "Bluedroid: Avoid multicast address for tun-tap interface"
* commit '283aa16d5f16bc10b5491661b5729c5f25635731':
Bluedroid: Avoid multicast address for tun-tap interface
|
| 01364c729dd8f94be9959300188c94324960e0df |
|
08-Apr-2014 |
Loic Poulain <loic.poulain@intel.com> |
Bluedroid: Avoid multicast address for tun-tap interface
Linux Kernel disallows to set an ethernet multicast
address as ethernet device address.
The IEEE has specified that the most significant bit
of the most significant byte of a mac address is used
for multicast. If its a 1, that means multicast, 0
means unicast.
Bluedroid uses the BD address to set the tun-tap intf
mac address. This BD address can be randomly auto
generated, possibly with the multicast bit.
To avoid any address issue, this patch masks this bit
before setting the ethernet mac address.
Change-Id: Ifff4ec7237ae6cbef3b8d4c23096c5df65e1431c
Signed-off-by: Loic Poulain <loic.poulain@intel.com>
Reviewed-on: https://android.intel.com/184768
Reviewed-by: Zhang, Jianxun <jianxun.zhang@intel.com>
Tested-by: Zhang, Jianxun <jianxun.zhang@intel.com>
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| da271ee4a0afcf5516208dc8df18a4da41a47124 |
|
31-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Whitelist IPv6 packets so they can be sent over PAN.
Change-Id: I68e96bc34af1dfded2761c9bc780c089076d15e0
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| f1d9b90f44336264a7dfee8708f208cd7b7fd541 |
|
31-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Whitelist IPv6 packets so they can be sent over PAN.
Change-Id: I68e96bc34af1dfded2761c9bc780c089076d15e0
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 4186b0ec7e0b7efe17c3b7cb8546ff359e099408 |
|
07-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add flow control for PAN.
This change reads from the TAP fd only when btpan_cb.flow == 1.
The value of this flag changes based on L2CAP congestion events.
http://b/13246629
Change-Id: Ic28bf65737dbd74c41b68198fceee58e3bff08d4
Conflicts:
btif/src/btif_pan.c
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 72f5ce63c2dbf31c7cfbb903c687ea71ad29b3ea |
|
21-Apr-2014 |
Matthew Xie <mattx@google.com> |
am 4b416130: Merge "Bluetooth: Adding Sniff feature for PAN Profile"
* commit '4b41613019829b40e8ca75a87219a415c51ae3a1':
Bluetooth: Adding Sniff feature for PAN Profile
|
| f4b8f8aa313d3b7d88b683bfe0e5f9eb0a29b3b3 |
|
07-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add flow control for PAN.
This change reads from the TAP fd only when btpan_cb.flow == 1.
The value of this flag changes based on L2CAP congestion events.
http://b/13246629
Change-Id: Ic28bf65737dbd74c41b68198fceee58e3bff08d4
Conflicts:
btif/src/btif_pan.c
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 36f43cc4b0ce38007c29d573f251ec594d95b180 |
|
29-Aug-2013 |
Nitin Shivpure <nshivpur@codeaurora.org> |
Bluetooth: Adding Sniff feature for PAN Profile
Sniff feature for PAN profile was not implemented in power
manager module of the stack, which was causing higher power
consumption after connecting PAN profile, Even though PAN
ACL link is idle & there is no data communication between
DUT & remote device. Adding sniff feature for PANU role &
NAP role to reduce power consumption.
Change-Id: Idf568f53a317abd536edf34fbdf1733fdf53b7d0
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 3576c564b33c20b5e2e90fdd3bca7ce24392ca50 |
|
01-Apr-2014 |
Mike J. Chen <mjchen@google.com> |
Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE
Change-Id: I14acefd66291adc2119daf97bd364b2eecf18d51
Signed-off-by: Mike J. Chen <mjchen@google.com>
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 5cd8bff2dd0337cb52bf48f312e3d2d55a8882fb |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Major warnings cleanup
Mostly fixing unused parameter warnings.
A few other warnings also fixed like possible use of
unitialized variables (no real issue found, just compiler couldn't
follow the path), signed vs unsigned warning.
Also fixed some typos, indent issues, removal of dead code, etc.
Change-Id: I95eb887aefc4d559d7921f71a0af5f3bfb01ac01
Signed-off-by: Mike J. Chen <mjchen@google.com>
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 689d66b6559dcb3a0ad7f6cc33b6129e50910253 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2
Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/btif/src/btif_pan.c
|