History log of /external/bluetooth/bluez/btio/btio.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e4d0096f7bf357124d08b66e80f47986b8af3728 10-Nov-2010 Jaikumar Ganesh <jaikumar@google.com> Add BT_POWER socket option.

BT_POWER socket option is used to control the power
characteristics of the underlying ACL link. Currently, this is
used to set the ACL link to active mode when the remote end has put
the ACL link in sniff mode and we are sending data. By default,
the ACL link will always be moved to active mode. However, this
causes problems with HID devices. And hence, for HID devices the
ACL link will not be moved to active mode when we are sending data.

This socket option is implemented for both rfcomm and l2cap sockets.

Change-Id: I0261a8daa2241d691670cc690cd27c39c67c1591
/external/bluetooth/bluez/btio/btio.c
9c7a6a48f25577f8621dd3cbe4103d481eb14214 15-May-2011 Johan Hedberg <johan.hedberg@intel.com> btio: Fix unused variable warning
/external/bluetooth/bluez/btio/btio.c
b8064300372044679d9b51e735a856c8820097fa 05-May-2011 Anderson Briglia <anderson.briglia@openbossa.org> Fix btio.c compilation warning

This patch fixes a compilation warning regarding btio/btio.c. Actually
this warning seems a false positive by Ubuntu Natty GCC version. A new
bug on Ubuntu bug system was opened but if you do not want to wait until
it is analyzed, just apply this minor fix.

btio/btio.c: In function 'bt_io_get':
btio/btio.c:803:11: warning: 'flushable' may be used uninitialized in
this function
/external/bluetooth/bluez/btio/btio.c
071f7742be87a6532885ddf4116e5dde9398e836 21-Apr-2011 Johan Hedberg <johan.hedberg@nokia.com> Add BT_FLUSHABLE support to BtIO

This patch adds support for the BT_FLUSHABLE L2CAP socket option through
BtIO. This can be used to mark data from specific L2CAP sockets to have
the flushable flag set in their corresponding ACL packets.
/external/bluetooth/bluez/btio/btio.c
aef577312e56ca25408e2627574a8949421dde9b 24-Mar-2011 Luiz Augusto von Dentz <luiz.dentz-von@nokia.com> Fix error message when getting SCO connection handle

Error message should indicate the transport correctly which is SCO
not RFCOMM.
/external/bluetooth/bluez/btio/btio.c
85bf920f1f67d77ea2827e3f9ad78443cba1d9a1 18-Oct-2010 Santiago Carot-Nemesio <sancane@gmail.com> Get mode option for L2CAP sockets
/external/bluetooth/bluez/btio/btio.c
afba441542f19d687111424c0a15d42139869239 20-Jul-2010 Claudio Takahasi <claudio.takahasi@openbossa.org> Add L2CAP fixed channels support for BTIO

Add new option BT_IO_OPT_CID to allow listen and connect using a fixed
L2CAP channel for BTIO.
/external/bluetooth/bluez/btio/btio.c
f57cb78379bf698472d2077daca5b80ca71261f7 13-Sep-2010 Zhenhua Zhang <zhenhua.zhang@intel.com> btio: Seperate btio.[ch] into btio directory

Seperate btio.[ch] from src directory to btio sub-folder.
/external/bluetooth/bluez/btio/btio.c