From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Some questions about audio on embedded systems
Date: Wed, 15 Oct 2008 18:13:01 -0600 [thread overview]
Message-ID: <d89ddf300810151713red04b2dx1f58d00bc1ba3ed1@mail.gmail.com> (raw)
In-Reply-To: <48F63E95.4010605@slackdot.org>
Deker
The best option is to use the most recent bluez version you can and
use the built-in audio service it provides. btsco and plugz are both
dead ends. There is a little bit of hackery you'll have to do with eg
hciattach which has patches that can't go upstream. See the gumstix
openembedded package for details. Make sure you ask the gumstix folks
because I believe they have a newer bluez than the default one you get
in their openembedded environment.
As far as hardware, if you're not using a prototype of the next
gumstix board then you should add a bluetooth USB adapter that has a
CSR chip in it to a verdex board. The integrated bluetooth module has
not been used successfully for SCO.
Brad
On Wed, Oct 15, 2008 at 1:03 PM, deker <deker@slackdot.org> wrote:
> Hi,
>
> I'm doing some research for an upcoming project where I'll need to use
> a bluetooth headset for audio (send & recv) with a gumstix. I found the
> following two pages:
>
> http://bluetooth-alsa.sourceforge.net/embed.html
> http://bluetooth-alsa.sourceforge.net/embedv1.html
>
> which have great information, but I'm curious as to which is the most
> current/correct. Specifically, I'm wondering what the current status of
> SCO audio with the gumstix (and just on regular PCs frankly) is. I
> understand that the blues-alsa project is moving away from btsco toward
> plugz, but didn't know how this would affect me on a gumstix.
>
> Any info would be greatly appreciated.
>
> Thanks,
>
> -d
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
--
Brad Midgley
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-10-16 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 19:03 [Bluez-devel] Some questions about audio on embedded systems deker
2008-10-16 0:13 ` Brad Midgley [this message]
2008-10-16 2:23 ` deker
2008-10-16 2:52 ` 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=d89ddf300810151713red04b2dx1f58d00bc1ba3ed1@mail.gmail.com \
--to=bmidgley@gmail.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