All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Problems with anycom usb dongle
Date: Wed, 08 Dec 2004 13:00:19 +0100	[thread overview]
Message-ID: <1102507219.9988.55.camel@pegasus> (raw)
In-Reply-To: <41B6E98F.8030603@csr.com>

Hi Steven,

> >                                        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 :)

> > on the HCI. Feel free to correct me, because I never really looked under
> > the HCI layer in that detail.
> 
> Correct. The LMP SCO handle is an 8 bit number in the range 1 to 255.
> The HCI SCO handle is a 12 bit number in the range 0 to 0x0eff.
> 
> LMP SCO handles are unique per piconet and are assigned by the master.
> If a device is a participant in multiple piconets then it may see the
> same LMP handle on different networks. The LM must distinguish SCO
> links using the (piconet, handle) pair.
> 
> HCI SCO handles are unique per host<->controller link. However, the
> same HCI SCO handle may be being used by different devices in a
> piconet to refer to different SCO links.
> 
> The LMP SCO handle is shared between the two devices in a SCO link
> (this allows the devices to distinguish multiple SCO links so that they
> agree on which link is to disconnect, for example).
> 
> The HCI SCO handles are not shared between the two devices. The two
> hosts may see different handles.

And there can't be a SCO and an ACL link with the same handle, right?

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. Actually I tend to simply mark the SCO support of
this dongle broken.

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-12-08 12: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 [this message]
2004-12-08 13:00                         ` Steven Singer
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=1102507219.9988.55.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 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.