From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Hardware Error event patch
Date: Tue, 29 Mar 2005 19:30:13 +0200 [thread overview]
Message-ID: <1112117413.9016.98.camel@pegasus> (raw)
In-Reply-To: <42498E15.9000409@csr.com>
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
next prev parent reply other threads:[~2005-03-29 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 14:09 [Bluez-devel] Hardware Error event patch Catalin Drula
2005-03-26 11:47 ` Marcel Holtmann
2005-03-29 17:19 ` Steven Singer
2005-03-29 17:30 ` Marcel Holtmann [this message]
2005-03-30 19:01 ` [Bluez-devel] " Catalin Drula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1112117413.9016.98.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox