Return-Path: Subject: Re: [Bluez-devel] Re: [Patch] Some btsco modifications From: Fredrik Tolf To: bluez-devel@lists.sourceforge.net In-Reply-To: <42368D18.2000405@xmission.com> References: <1110683934.5056.43.camel@pc7.dolda2000.com> <4233C663.80109@xmission.com> <1110762698.5056.73.camel@pc7.dolda2000.com> <423589B1.6000403@xmission.com> <1110809103.5056.102.camel@pc7.dolda2000.com> <42368D18.2000405@xmission.com> Content-Type: text/plain Message-Id: <1110930125.19889.13.camel@pc7.dolda2000.com> 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, 16 Mar 2005 00:42:05 +0100 On Tue, 2005-03-15 at 00:22 -0700, Brad Midgley wrote: > Fredrik > > > Another thing, that I'm not sure is a good idea, is to implement a > > "fail-safe" mode in the daemon. Running the daemon in fail-safe mode > > would mean that it doesn't die from not being able to connect to the > > headset. Instead, it would try to reconnect periodically. Same thing if > > the connection is lost at some point. The reason I'm not sure if this is > > a good idea is that one would have to wait for the reconnection attempt > > to get the headset working after making it accessible. Therefore, it may > > well be a good idea to just have to run the daemon manually when one > > knows that the headset is accessible. However, in this case, the daemon > > should at least terminate if it looses the RFCOMM connection to the > > headset. I don't know if it's possible to detect if the RFCOMM > > connection is lost, though. Comments are appreciated. > > I don't know about detecting broken rfcomm. I haven't experimented with it. I just saw that sometimes the kernel apparently notices a broken RFCOMM channel and closes the socket. I don't know yet what might trigger it apart from an explicit disconnect. Either way, it made the btsco daemon chew up 100% CPU, so I added a case to detect it and exit for now. If it should be handled otherwise, that can be fixed when it is figured out what it should do instead. Fredrik Tolf ------------------------------------------------------- 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