From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Meaning of hcitool -i dev con
Date: Fri, 27 Jun 2008 04:51:38 +0200 [thread overview]
Message-ID: <1214535098.19001.3.camel@violet> (raw)
In-Reply-To: <loom.20080626T223113-455@post.gmane.org>
Hi,
> > > > SCO 00:19:2C:D5:90:DF handle 2 state 1 lm SLAVE
> > > < ACL 00:19:2C:D5:90:DF handle 1 state 1 lm MASTER ENCRYPT
> > >
> > > Does this mean that the USB adapter is playing TWO roles (master and
> > > slave) at the same moment??
> >
> > that is for the SCO connection. The ACL connection is the one that
> > counts. The SCO depends on the ACL connection.
> >
> > Actually the the SCO/eSCO connections don't have a link mode. It is an
> > issue how these information are presented.
> >
> Thank you for the explanation.
> This explains the output from hci command and hcidump.
> Your words also reminds me that standard has said "before creating SCO, a ACL
> link must exist".
> But I am still confused about the handle.
> If ACL first use handle 0, does that mean the upcoming SCO will use handle 0?
> Or another one?
the handle 0 is invalid first of all. The ACL link gets a handle and the
SCO link gets its own handle. Like you see it in the example above.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-06-27 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 18:27 [Bluez-devel] Meaning of hcitool -i dev con Jui-Hao Chiang
2008-06-26 20:56 ` Jui-Hao Chiang
2008-06-26 21:07 ` Marcel Holtmann
2008-06-26 22:42 ` Jui-Hao Chiang
2008-06-27 2:51 ` 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=1214535098.19001.3.camel@violet \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox