From: robert <rbscott@cadvium.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] SCO Question
Date: Wed, 22 Aug 2007 11:23:16 -0700 [thread overview]
Message-ID: <076BF2A0-A0AF-44B5-9A4D-2BC3EBBE2940@cadvium.net> (raw)
Hello Bluez,
How would I go about redirecting incoming SCO data to an alsa device,
and transmit incoming audio data out as SCO?
I have read the following pages,
http://wiki.bluez.org/wiki/Audio
http://wiki.bluez.org/wiki/HOWTO/AudioDevices
but everything described seems to do too much. I would prefer to
handle the RFCOMM channel, and SDP registration elsewhere.
Presently, I just want to determine how to redirect the SCO traffic.
Thanks,
--robert
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-08-22 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:23 robert [this message]
2007-08-24 11:35 ` [Bluez-devel] SCO Question Mikael Bengtsson
2007-08-24 12:06 ` Marcel Holtmann
2007-09-06 11:03 ` Mikael Bengtsson
[not found] <A1F0D47583A2D711919F00600819B3A45BDC65@goofy.vitronics.com >
2004-07-09 7:48 ` [Bluez-devel] SCO question Arnaud Mouiche
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 20:11 Williams, Richard
[not found] <A1F0D47583A2D711919F00600819B3A4028BAE@goofy.vitronics.com >
2004-07-08 14:08 ` Arnaud Mouiche
2004-07-08 13:12 Williams, Richard
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=076BF2A0-A0AF-44B5-9A4D-2BC3EBBE2940@cadvium.net \
--to=rbscott@cadvium.net \
--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