From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ development In-Reply-To: References: <52cf60ee0806261127r15b88ccod1bdba8d42ed4e59@mail.gmail.com> <1214514474.23682.42.camel@violet> Date: Fri, 27 Jun 2008 04:51:38 +0200 Message-Id: <1214535098.19001.3.camel@violet> Mime-Version: 1.0 Subject: Re: [Bluez-devel] Meaning of hcitool -i dev con Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net 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