public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Bin <binch@mobilesoft.com.cn>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] SCO route way!!
Date: Mon, 27 Sep 2004 09:46:05 +0800	[thread overview]
Message-ID: <1096249564.1725.0.camel@debian> (raw)

Hi all, 

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. 

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? 

Any help appreciated! 

Chen



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-09-27  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27  1:46 Chen Bin [this message]
2004-09-28  8:14 ` [Bluez-users] SCO route way!! Marcel Holtmann
2004-09-28  8:34   ` Chen Bin
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=1096249564.1725.0.camel@debian \
    --to=binch@mobilesoft.com.cn \
    --cc=bluez-users@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