From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: To: bluez-devel@lists.sourceforge.net From: Sebastian Roth Message-ID: References: <20041206225609.GA1177@zeus.galaxy.org.uk> <1102407664.8447.20.camel@pegasus> <1102411047.8447.28.camel@pegasus> <1102425729.8447.41.camel@pegasus> <1102439143.8447.47.camel@pegasus> <1102496771.9988.35.camel@pegasus> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed In-Reply-To: <1102496771.9988.35.camel@pegasus> Subject: [Bluez-devel] Re: Problems with anycom usb dongle 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, 08 Dec 2004 12:53:08 +0100 Hi Marcel, > the link manager runs on the chip and L2CAP is part of the host protocol > stack. And in between we have the HCI. As far as I know, the connection > handle from the link manager must not be the same connection handle used > on the HCI. Feel free to correct me, because I never really looked under > the HCI layer in that detail. I've had a closer look at this but can't find out anything more detailed about the differences of the handles. > Or should I simply drop SCO packets with no data on handle 0 in the > HCI core? Is handle 0 a valid handle? So I can't give you an answer to this. Sorry. Best regards, Sebastian ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel