Return-Path: Subject: Re: [Bluez-devel] Handling a Hardware Error event on iPAQ h5550 From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1111057586.11792.58.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: Thu, 17 Mar 2005 12:06:26 +0100 Hi Peter, > I'm not that familiar with the architecture of BlueZ but with the > experiences for our own stack I can tell you this is not trivial. The main > problem here is that the Bluetooth Stack is not stateless. One possible > solution is to feed the reset done event to the higher layers (l2cap). But > than L2cap must be modified to correctly shut down all connections. It > would be easier if the HCI layer tracks the state of all ACL and SCO > connections (Marcel ??). Than a reset done event can be handled like a > unexpected link loss on all active connections and the higher layers do > not need any modifications (hopefully). we can do this and actually calling "hcitool cc" does this already, but it waits indeed for a timeout of the HCI_Disconnect. > It may be much simpler trying to find the cause of the data corruption. This is really the best thing to do, because H:4 is a stupid protocol if you run it over hardware. For stack internal use it is perfect. Hopefully 3-Wire UART will come at some time and make the H:4 obsolete. 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