From: Alexandros Vellis <avel@noc.uoa.gr>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Getting an adaptor to be supported (for SCO audio)
Date: Mon, 01 Aug 2005 12:34:44 +0300 [thread overview]
Message-ID: <1122888885.6800.13.camel@amy> (raw)
In-Reply-To: <42EDBD25.4050301@xmission.com>
Brad Midgley wrote:
> It seems that hci routing of sco audio is only available on CSR chips.
>
> SCO will be routed through the PCM hardware on your silicon wave chip
> but that PCM interface is not connected to anything in a usb dongle.
Voice audio works perfectly in Windows XP, though.
Is it a case such as the one with winmodems, in that software is doing
the voice routing?
Or would these (cheap, admittedly, I got mine for 15 euros) dongles need
some sort of (difficult) reverse engineering to pass through the audio?
Just wondering. :)
> I have the same problem with the builtin infineon bluetooth on gumstix
> (see http://bluetooth-alsa.sf.net/embed.html for more)
I don't particulary like this TODO item:
- Find out if SCO can be mapped to HCI as it can on CSR (*no*)
:-D
Thanks,
Alexandros
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-01 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 5:45 [Bluez-devel] Getting an adaptor to be supported (for SCO audio) Alexandros Vellis
2005-08-01 6:11 ` Brad Midgley
2005-08-01 9:34 ` Alexandros Vellis [this message]
2005-08-01 15:07 ` Brad Midgley
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=1122888885.6800.13.camel@amy \
--to=avel@noc.uoa.gr \
--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