From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] btsco and PCM routing
Date: Mon, 11 Jul 2005 12:18:34 -0600 [thread overview]
Message-ID: <42D2B7FA.4000305@xmission.com> (raw)
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
reply other threads:[~2005-07-11 18:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42D2B7FA.4000305@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@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