does flush_to in l2cap setsockopt currently do anything?

Bluez-devel Albert Huang 2 participants 2 messages Mar 29, 2005 Bluetooth drivers

Share & tools

Albert Huang

author

2005-03-29 23:07 UTC #0 lore raw

Hi all,

I was poking through the sources while trying to find an easy way to set the ACL automatic flush timeout with an l2cap socket.

Does setsockopt(s, SOL_L2CAP, L2CAP_OPTIONS, ...) cause the underlying ACL automatic flush timeout to change? It doesn't look like flush_to is being used in net/bluetooth/l2cap.c:setsockopt

Is there an easier way of doing it short of extracting the underlying ACL connection handle and then sending an HCI Write_Automatic_Flush_Timeout command packet to a separate HCI socket?

Regards,
Albert

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Marcel Holtmann

maintainer

2005-03-29 23:11 UTC #1 lore raw

Hi Albert,

Quoted 6 lines

I was poking through the sources while trying to find an easy way to set the ACL automatic flush timeout with an l2cap socket.
Does setsockopt(s, SOL_L2CAP, L2CAP_OPTIONS, ...) cause the underlying ACL automatic flush timeout to change? It doesn't look like flush_to is being used in net/bluetooth/l2cap.c:setsockopt

it is doing nothing at the moment.

Quoted 3 lines

Is there an easier way of doing it short of extracting the underlying ACL connection handle and then sending an HCI Write_Automatic_Flush_Timeout command packet to a separate HCI socket?

May you wanna look at the cmd_info() part of hcitool.c.

Regards

Marcel