From: Marcel Holtmann <marcel@holtmann.org>
To: Charles Bueche <charles@bueche.ch>
Cc: steven.singer@csr.com,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] First HCI command sent to a device
Date: Fri, 05 Mar 2004 13:28:12 +0100 [thread overview]
Message-ID: <1078489692.2762.67.camel@pegasus> (raw)
In-Reply-To: <20040305131833.3bf6803f.charles@bueche.ch>
Hi Charles,
> I haven't looked at the code so my idea will probably be unusable, but
> how about maintaining a list of which dongles don't like the reset and
> send it only to the other ones ?
>
> Or reversing the test, only sending a reset to the dongles that need
> it.
>
> Of course, it implies that you can identify the device *before* deciding
> on your action.
>
> AFAIK, there is a similar "black-list" of controllers in the IDE layer
> of Linux to decide on the supported features..
I like to identify the dongles that don't like the HCI_Reset, but this
is impossible for UART based adapters and even on the USB side this is
not very trivial. Actually I chose to introduce a reset quirk for the
i-Tec/Broadcom dongle.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-03-05 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 14:50 [Bluez-devel] First HCI command sent to a device Marcel Holtmann
2004-03-04 15:23 ` Steven Singer
2004-03-04 15:55 ` Marcel Holtmann
2004-03-05 12:18 ` Charles Bueche
2004-03-05 12:28 ` Marcel Holtmann [this message]
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=1078489692.2762.67.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=charles@bueche.ch \
--cc=steven.singer@csr.com \
/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