Return-Path: Subject: Re: [Bluez-devel] does flush_to in l2cap setsockopt currently do anything? From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1112137866.9016.164.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Mar 2005 01:11:06 +0200 Hi Albert, > 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. > 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 ------------------------------------------------------- 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 Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel