From: Nick Pelly <npelly@google.com>
To: 卞磊 <mykofzone@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: eSCO or SCO link?
Date: Mon, 30 Mar 2009 23:13:27 -0700 [thread overview]
Message-ID: <35c90d960903302313y3900c724m285f984ba5eb9ec0@mail.gmail.com> (raw)
In-Reply-To: <a172fe730903302253j6f137249g10c51d85488bd608@mail.gmail.com>
2009/3/30 卞磊 <mykofzone@gmail.com>:
> Hi All,
> I made a mistake when writing the email, I have not complete my question.
>
> 2009/3/31 卞磊 <mykofzone@gmail.com>:
>> Hi All,
>> I have a stlc2500c which is a Bluetooth 1.2 chip. When debuging
>> function 'hci_connect', i found the hci link type of the arguments was
>> SCO_LINK, because i enabled 'lmp_esco_capable' in my kernel, it call
>> 'hci_setup_sync' to setup eSCO link.
>
> But when i check connection by 'hcitool con', the hcitool show it was
> a SCO link. So, is it a SCO link or eSCO link? Thanks.
hcitool con will report eSCO if it is eSCO, so you have a SCO link.
hci_setup_sync can be used for both SCO and eSCO, and the chipset
and/or the host stack will fall back to SCO if eSCO parameters can not
be negotiated. An LMP log will show why.
Nick
next prev parent reply other threads:[~2009-03-31 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 5:45 eSCO or SCO link? 卞磊
2009-03-31 5:53 ` 卞磊
2009-03-31 6:13 ` Nick Pelly [this message]
2009-03-31 6:43 ` 卞磊
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=35c90d960903302313y3900c724m285f984ba5eb9ec0@mail.gmail.com \
--to=npelly@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mykofzone@gmail.com \
/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