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 11:46:23 +0000 [thread overview]
Message-ID: <41B6E98F.8030603@csr.com> (raw)
In-Reply-To: <1102496771.9988.35.camel@pegasus>
Marcel Holtmann wrote:
> Sebastian wrote:
>> "This command will cause the link manager to
>> create a SCO connection ...". Does this mean LMP?
The Link Manager or LM is the entity - the code that performs the tasks.
Two link managers communicate with each other over the air using the
Link Manager Protocol or LMP.
Strictly speaking the P in L2CAP means protocol so really you should
talk about the L2CA layer but no one ever does.
> the link manager runs on the chip and L2CAP is part of the host protocol
> stack. And in between we have the HCI.
Or, if you prefer, L2CAP issues the commands, the LM processes the
commands.
The host talks to the link manager on the local device using HCI.
The local link manager talks to the remote link manager using LMP.
> 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'.
> 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.
- 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 11:46 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 ` Steven Singer [this message]
2004-12-08 12:00 ` [Bluez-devel] Re: Problems with anycom usb dongle Marcel Holtmann
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=41B6E98F.8030603@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