From: Max Krasnyansky <maxk@qualcomm.com>
To: Steven Singer <steven.singer@csr.com>
Cc: Christian Eiselt <c.eiselt@gmx.de>,
bluez Dev <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hciconfig
Date: Thu, 09 Oct 2003 10:25:33 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20031009102229.05a801a0@unixmail.qualcomm.com> (raw)
In-Reply-To: <3F854DE3.9090001@csr.com>
At 05:00 AM 10/9/2003, Steven Singer wrote:
>Max Krasnyansky wrote:
>>In older HCI implementation HCI_Reset used to reset USB transport even
>>though spec clearly states that it shouldn't. This may cases all sorts of problems. Looks like you got one of those dongle with buggy HCI implementation.
>
>I'd like to pick you up on the words "clearly" and "buggy". This is an
>example of how the Bluetooth spec has been tightened to avoid ambiguity.
:)
Thanks for clarification Steven. I didn't know that 1.0b allowed complete
reset and I was referring to 1.1.
Max
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-10-09 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002401c3632a$5b9714b0$1ab91e8d@chris1>
2003-10-09 0:58 ` [Bluez-devel] hciconfig Max Krasnyansky
2003-10-09 12:00 ` Steven Singer
2003-10-09 17:25 ` Max Krasnyansky [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=5.1.0.14.2.20031009102229.05a801a0@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=c.eiselt@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.