From: Carl Orsborn <cjo@csr.com>
To: Jonathan Paisley <jp-www@dcs.gla.ac.uk>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] snd-bt-sco development teamup...
Date: Tue, 10 Aug 2004 20:22:14 +0100 [thread overview]
Message-ID: <41192066.1060202@csr.com> (raw)
In-Reply-To: <3A71B5F8-EAFD-11D8-A26F-000D932E1CC8@dcs.gla.ac.uk>
Jonathan Paisley wrote:
> On 10 Aug 2004, at 16:51, James Courtier-Dutton wrote:
>> So, I suggest we might do better if we provide a number of different
>> ways to get sound to bluetooth devices, in order of preference.
>> 1) PCM as Carl suggests
>> 2) Bypass HCI stack and send SCO direct to USB devices. I don't think
>> one can do that for UART based devices. I don't know what is best for
>> PCI devices, as I have not looked at the PCI source code. I
>> concentrated on the USB source code when I tried before.
>> 3) Current HCI stack method. <- Last resort.
> \x10Perhaps somebody with more bluetooth know-how can comment here, but:
>
> 1) I thought PCM was for connection from the bluetooth chip to some
> other hardware (e.g., a physical earpiece). That's not an option for
> getting audio to the computer unless the device in question has some
> funky other connection to the computer.
Correct. Our BT chips all have a PCM port which routes one
or more audio streams directly to external chips (usually audio codecs),
so the audio packets don't flow over HCI. (A SCO connection is
created, managed and destroyed over HCI, but the audio packets
run through the PCM port.) The PCM port connection is usually
used in dedicated audio devices: cell phones, headsets, etc.
Some of our chips include an audio codec, so they can directly drive
a microphone and earpiece. (The chips were designed to form the core
of a headset.) In this case, the SCO packets never leave the chip.
As far as I've seen, all BT chip manufacturers provide a PCM port.
The manufacturers' PCM ports are, inevitably, manufacturer-specific,
though they should all have a common core of functionality.
> 2) Isn't the SCO-over-USB standard defined in terms of the HCI
> protocol? How do you go about bypassing it?
I don't understand suggestion (2) above (HCI stack bypass). The
"standard" BT stack loses interest in SCO at HCI - it doesn't travel
through L2CAP, etc. One could conceive of routing an audio
sample stream to another device at, or just above, the host's USB
driver level. But this feels awfully like the "last resort"
option (3).
Carl
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-10 19:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 16:51 [Bluez-devel] snd-bt-sco development teamup Lars Grunewaldt
2004-08-09 17:09 ` Marcel Holtmann
2004-08-09 17:12 ` Lars Grunewaldt
2004-08-09 17:39 ` Marcel Holtmann
2004-08-09 18:21 ` James Courtier-Dutton
2004-08-09 22:26 ` Marcel Holtmann
2004-08-09 23:53 ` Lars Grunewaldt
2004-08-10 12:14 ` Marcel Holtmann
2004-08-10 12:53 ` James Courtier-Dutton
2004-08-10 13:39 ` Jonathan Paisley
2004-08-10 14:26 ` Carl Orsborn
2004-08-10 14:48 ` Marcel Holtmann
2004-08-10 15:31 ` Jonathan Paisley
2004-08-11 8:58 ` Roderick Taylor
2004-08-11 6:40 ` Marcel Holtmann
2004-08-10 15:51 ` James Courtier-Dutton
2004-08-10 18:43 ` Jonathan Paisley
2004-08-10 19:22 ` Carl Orsborn [this message]
2004-08-10 12:56 ` [Bluez-devel] snd-bt-sco development teamup | ALSA connection Lars Grunewaldt
2004-08-10 13:45 ` Marcel Holtmann
2004-08-10 13:53 ` [snd-bt-sco] " Jonathan Paisley
2004-08-10 14:36 ` Marcel Holtmann
2004-08-10 14:39 ` Jonathan Paisley
2004-08-10 14:21 ` Lars Grunewaldt
2004-08-10 15:01 ` Marcel Holtmann
2004-08-10 16:02 ` Lars Grunewaldt
2004-08-10 14:53 ` James Courtier-Dutton
2004-08-10 13:03 ` [Bluez-devel] snd-bt-sco development teamup Jonathan Paisley
2004-08-10 13:11 ` Marcel Holtmann
2004-08-10 13:18 ` Lars Grunewaldt
2004-08-10 13:20 ` Jonathan Paisley
2004-08-10 13:22 ` Lars Grunewaldt
2004-08-10 13:54 ` James Courtier-Dutton
2004-08-10 13:28 ` Marcel Holtmann
2004-08-10 13:40 ` James Courtier-Dutton
2004-08-10 13:49 ` Marcel Holtmann
2004-08-10 14:07 ` James Courtier-Dutton
2004-08-10 14:34 ` Marcel Holtmann
2004-08-10 15:15 ` James Courtier-Dutton
2004-08-10 15:25 ` Marcel Holtmann
2004-08-10 16:46 ` James Courtier-Dutton
2004-08-10 22:58 ` Marcel Holtmann
2004-08-10 11:48 ` Lars Grunewaldt
2004-08-10 12:08 ` Marcel Holtmann
2004-08-10 12:40 ` Lars Grunewaldt
2004-08-10 13:03 ` Marcel Holtmann
2004-08-10 13:10 ` Lars Grunewaldt
2004-08-10 13:30 ` 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=41192066.1060202@csr.com \
--to=cjo@csr.com \
--cc=James@superbug.demon.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jp-www@dcs.gla.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.