Return-Path: Subject: Re: [Bluez-devel] Hardware Error event patch From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: <42498E15.9000409@csr.com> References: <42498E15.9000409@csr.com> Content-Type: text/plain Message-Id: <1112117413.9016.98.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: Tue, 29 Mar 2005 19:30:13 +0200 Hi Steven, > > I've finished the patch for handling the Hardware Error event and you have > > it attached below. > > > > To briefly remind the context: when H4 (HCI over UART) is used > > as the transport layer between the host and the Bluetooth controller > > and the controller detects a loss of synchronization, it sends a > > "Hardware Error" event to the host, which should then send a "Reset" > > command for resynchronization. The procedure is described under "Error > > Recovery" in the H:4 appendix of Bluetooth v1.1 specification. > > Are you resetting for all hardware error events, or just when you think > that H4 synchronisation has been lost? > > It is true that the spec says that a device will issue a hardware error > when synchronisation is lost but it doesn't say that that's the only > reason for a device to issue a hardware error. > > CSR devices, for example, use hardware error code 0xFE to mean that H4 > synchronisation has been lost. Other hardware error events mean other > things and HCI_Reset is not the appropriate action in all cases. In some > cases no action is required. In other cases user intervention will be > needed to clear the error and we'll emit a hardware error on every boot > until the problem is resolved. A few cases will require a harder reset > than an HCI_Reset. > > You probably don't want to reset if you receive a hardware error and > you were not using the H4 host transport. thanks for the information. You are making a good point here. However the error code is another weird vendor specific thing in the Bluetooth specification. Proposals on how to deal with it are very welcome. 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