From: Steven Singer <steven.singer@csr.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Problems with anycom usb dongle
Date: Wed, 08 Dec 2004 13:00:24 +0000 [thread overview]
Message-ID: <41B6FAE8.7030003@csr.com> (raw)
In-Reply-To: <1102507219.9988.55.camel@pegasus>
Marcel Holtmann wrote:
>> > As far as I know, the connection
>> > handle from the link manager must not be the same connection handle used
>>
>> I think you mean 'need not' not 'must not'.
>
> oh yes, right. Germans (especially I) tend to translate this wrong :)
I can see why this could be a problem. If "must" means "is required to
be" then it has two opposites "is required not to be" and "is not required
to be". That is, does the negation bind to "required" or to "to be".
You can't easily get to "is not required to be" using must. You end up
writing something horribly long like "it is not the case that A must be
B".
You could have said "doesn't need to be", but "need not be" is
idiomatic.
Anyway, back to the matter at hand:
> And there can't be a SCO and an ACL link with the same handle, right?
Correct. I don't know if the HCI spec explicitly states this, but it is
implicit. For example, the Disconnect command takes a connection handle
as an argument. If SCO and ACL links were able to have the same handle
then it would be ambiguous which was to be disconnected.
> However the problems is that we see a SCO data packet with HCI handle 0
> and zero data len, which should not be send up to the HCI. Basically I
> think we must drop this directly in hci_usb driver and not even send it
> up to BlueZ HCI core.
It would be valid for the dongle to create a link with HCI SCO handle 0,
but, if I read the traces correctly, it hasn't done this. So the problem
is that it's sending SCO packets for a non-existent handle.
It may just be a feature of this dongle that if the isochronous endpoint
is started up and there's no SCO data to send (or if it hasn't quite
finished setting up the SCO link internally) then it sends a dummy HCI
SCO header.
If the zero length packets are ignored then does the rest of the data
make sense. If so, silently dropping zero length packets might be
useful.
> Actually I tend to simply mark the SCO support of
> this dongle broken.
I think you mean "intend" not "tend". :-)
- Steven
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-08 13:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 22:56 [Bluez-devel] snd-bt-sco problem Chris Boyle
2004-12-07 7:37 ` [Bluez-devel] " Sebastian Roth
2004-12-07 8:21 ` Marcel Holtmann
2004-12-07 9:06 ` [Bluez-devel] Problems with anycom usb dongle (was: snd-bt-sco problem) Sebastian Roth
2004-12-07 9:17 ` Marcel Holtmann
2004-12-07 13:13 ` [Bluez-devel] Re: Problems with anycom usb dongle Sebastian Roth
2004-12-07 13:22 ` Marcel Holtmann
2004-12-07 14:07 ` Sebastian Roth
2004-12-07 17:05 ` Marcel Holtmann
2004-12-08 8:59 ` Sebastian Roth
2004-12-08 9:06 ` Marcel Holtmann
2004-12-08 9:39 ` [Bluez-devel] CVS doubles suche.org
2004-12-08 9:48 ` Marcel Holtmann
2004-12-08 10:33 ` suche.org
2004-12-08 11:08 ` Marcel Holtmann
2004-12-08 11:46 ` [Bluez-devel] Re: Problems with anycom usb dongle Steven Singer
2004-12-08 12:00 ` Marcel Holtmann
2004-12-08 13:00 ` Steven Singer [this message]
2004-12-08 13:19 ` Marcel Holtmann
2004-12-08 11:53 ` Sebastian Roth
2004-12-08 10:34 ` [Bluez-devel] Re: snd-bt-sco problem Chris Boyle
2004-12-08 10:38 ` [Bluez-devel] Re[2]: " suche.org
2004-12-08 14:35 ` [Bluez-devel] " Lars Grunewaldt
2004-12-07 7:57 ` [Bluez-devel] " Marcel Holtmann
2004-12-08 10:24 ` Chris Boyle
2004-12-08 3:10 ` Brad Midgley
2004-12-08 10:26 ` Chris Boyle
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=41B6FAE8.7030003@csr.com \
--to=steven.singer@csr.com \
--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