* [Bluez-devel] btsco and PCM routing
@ 2005-07-11 18:18 Brad Midgley
0 siblings, 0 replies; only message in thread
From: Brad Midgley @ 2005-07-11 18:18 UTC (permalink / raw)
To: bluez-devel
Hey
We have depended on audio routing through HCI but if anyone is going to
embed btsco, they will likely want to use PCM routing.
Right now your app will have to open an audio device that you know won't
produce any audio and while it's open, the daemon would keep the SCO
audio flowing through the PCM interface. It seems pretty gross. If the
daemon could get open/close messages through some other means, it could
do the right thing without the fake audio device or any kernel
entanglements. Is that good enough? How should it get those messages?
Just to make sure HCI routing actually works ok on arm, I am trying to
get my embedded setup to have an HCI-routed audio adapter. I'm a little
stuck on the wiring stuff :(
See http://bluetooth-alsa.sourceforge.net/embed.html
Brad
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-07-11 18:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-11 18:18 [Bluez-devel] btsco and PCM routing Brad Midgley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox