Return-Path: Date: Wed, 2 Aug 2006 13:01:09 +0200 (CEST) From: Peter Wippich To: BlueZ development In-Reply-To: <1154488151.3905.34.camel@aeonflux.holtmann.net> Message-ID: References: <1154488151.3905.34.camel@aeonflux.holtmann.net> MIME-Version: 1.0 Subject: Re: [Bluez-devel] Patch for rfcomm tty server ports Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Marcel, On Wed, 2 Aug 2006, Marcel Holtmann wrote: > the idea of using BDADDR_ANY is kinda nice, but the use of another > kernel thread for the listen RFCOMM socket within the RFCOMM module is > not good. We need to integrate all the processing for the server state > in the DLC itself. I partially agree with you. The solution with the kernel thread is somehow "quick 'n dirty". The problem was that I got only a limited time to get this working and did not want to break anything. Currently, only a socket can wait for an incomming connection. It would be nicer if we can put this into the DLC itself, but this would require some more internal changes with a high risk of messing thinks up. > I am not gonna working on this, but I am supporting it and happy to > review any patches. Thank you. When my understanding of the internals gets better I'll try to work something out. Regards, Peter ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel