From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: steve@sparta.com
Subject: Re: [Bluez-devel] Continued SCO audio issues...
Date: Sat, 06 Dec 2008 22:16:47 +0100 [thread overview]
Message-ID: <1228598207.28839.49.camel@violet.holtmann.net> (raw)
In-Reply-To: <4939BB42.1080607@slackdot.org>
Hi Rob,
> I posted a while back about having some issues getting SCO audio to work
> on some Compulab em-x270 boards. Well, we're still not there, but we've
> tried a lot more things. I'm going to describe the problem in some more
> detail now in the hopes that somebody here can help point me in a
> direction to get this working.
>
> Symptoms:
>
> - Everything involved (bt headset, ALSA, aplay/mplayer/pulseaudio,
> etc) seems to think everything is working.
> - No sound comes out of the headset. We hear a hissing from the
> headset during actual audio playback (or when I have pulseaudio talking
> to it via 'module-alsa-sink' and the sink is not suspended).
>
> Config(s) Tested:
>
> - Kernels: 2.6.23, 2.6.26, 2.6.27
> - Bluez: 3.26, 3.36, 4.12, 4.18
> - ALSA drivers: as shipped w/ kernels above
>
> We've been through about every possible combination of the above. We've
> tried hci_usb and btusb. We've tested with 3 models of bt headset and 2
> development boards. For some reason, the ONLY place I can make SCO audio
> work is under a stock Ubuntu 8.10 (which uses Bluez 4.12, kernel 2.6.27,
> and ALSA 1.0.17 for the record).
>
> I'm stumped. Here is some sample output from various pieces as we try to
> play a file. Right now we're using Bluez 3.36 (getting 4.x running on
> this platform was a bit of a PITA and was somewhat unstable so we backed
> out to what currently ships with openembedded)
>
> We've tried with separate USB dongles (using the same chipset, that
> works under Ubuntu 8.10) so it's not the onboard BT chipset...
>
> # hciconfig hci0 version
> hci0: Type: USB
> BD Address: 00:02:5B:00:A5:A5 ACL MTU: 310:10 SCO MTU: 64:8
> HCI Ver: 2.0 (0x3) HCI Rev: 0xc5c LMP Ver: 2.0 (0x3) LMP Subver: 0xc5c
> Manufacturer: Cambridge Silicon Radio (10)
>
> # hciconfig hci0 revision
> hci0: Type: USB
> BD Address: 00:02:5B:00:A5:A5 ACL MTU: 310:10 SCO MTU: 64:8
> Unified 21e
> Chip version: BlueCore4-ROM
> Max key size: 128 bit
> SCO mapping: PCM
you never thought that routing the SCO packets via the chips internal
PCM (instead of HCI) might be a problem if you wanna use ALSA?
Regards
Marcel
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-12-06 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 23:37 [Bluez-devel] Continued SCO audio issues Rob "Deker" Dekelbaum
2008-12-06 21:16 ` Marcel Holtmann [this message]
2008-12-07 1:34 ` Rob "Deker" Dekelbaum
2008-12-07 2:14 ` Marcel Holtmann
2008-12-07 16:08 ` deker
2008-12-08 18:36 ` Rob "Deker" Dekelbaum
2008-12-08 19:56 ` Marcel Holtmann
2008-12-08 20:46 ` Rob "Deker" Dekelbaum
2008-12-12 1:49 ` 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=1228598207.28839.49.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=steve@sparta.com \
/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