public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Bin <binch@mobilesoft.com.cn>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] SCO route way!!
Date: Tue, 28 Sep 2004 16:34:39 +0800	[thread overview]
Message-ID: <1096360479.2115.9.camel@debian> (raw)
In-Reply-To: <1096359291.4684.26.camel@notepaq>

Hi Holtmann,

Thanks for your kind answer. I have another question. 

If the SCO is over PCM, what should I do before I write data from the
codec to the chip, just establish the connection is enough?

I mean, I use HCI ACL to add a SCO link with the chip, then I write the
voice data from the codec to the chip. I wonder if there are several SCO
connections over the chip, how can the chip determine which connection
will be used to send the voice? Should I do more steps to specify which
connection to use?

Thanks in advance.

Chen
在2004年09月28日的16:14,Marcel Holtmann写道:
> Hi Chen,
> 
> > I am developing Bluetooth on Smart Phone, I have a question about
> > bluetooth voice, I don't know whether it is suitable to ask this
> > question here. 
> 
> yes, this is the wrong mailing list until you start using Linux and
> BlueZ on your smart phone ;)
> 
> > My chip is TI BRF6100, I can change data between my board and the BT usb
> > dongle, and it can connect to the bluetooth headset, but it can't play
> > any music to it. 
> > 
> > The rfcomm connection has been connected and I can receive the AT
> > command from the headset.Using hcidump, I found that the SCO link is
> > added, but then there is no SCO traffic in the channel. 
> > 
> > The chip can support SCO data route from hci or direct to the baseband
> > from codec. I think the default choice of the chip is baseband. 
> > 
> > How can I choose the SCO route method? Is it a standard HCI command or
> > vendor-specific command? 
> 
> There are two ways, SCO over HCI and SCO over PCM. There is no standard
> HCI command to switch between them. They are all vendor specific or
> preset by the chip manufacturer and not changeable.
> 
> Regards
> 
> Marcel
> 
> 

  reply	other threads:[~2004-09-28  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27  1:46 [Bluez-users] SCO route way!! Chen Bin
2004-09-28  8:14 ` Marcel Holtmann
2004-09-28  8:34   ` Chen Bin [this message]
2004-09-28  8:38     ` Marcel Holtmann

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=1096360479.2115.9.camel@debian \
    --to=binch@mobilesoft.com.cn \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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