From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] scooped by pocketpc (a2dp)
Date: Mon, 24 Jan 2005 00:35:57 -0700 [thread overview]
Message-ID: <41F4A55D.9070701@xmission.com> (raw)
In-Reply-To: <41EA1B6E.3070303@xmission.com>
Lars
> hmm. i see a menu for alsa devices but our userspace a2dp device
> (currently stubbed out, but not implemented) doesn't show up. i set it
> up as documented in btsco/bt/BUILD
>
>> That leads to - at least - gnomemeeting and openphone supporting alsa
>> directly :)
I noticed that linphone from debian-testing has oss and alsa devices in
its audio device selection menu.
I still haven't been able to get the stubbed out alsa-lib driver to show
up! I also tried a .asoundrc with
pcm.a2dpplug {
type plug
slave { pcm "a2dp" }
}
pcm.a2dp {
type a2dp
bdaddr "00:08:F4:30:05:BB"
}
since that was more like what the jack plugin is supposed to have... no
luck...
Brad
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-24 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 15:28 [Bluez-devel] scooped by pocketpc (a2dp) Brad Midgley
2005-01-15 15:48 ` Lars Grunewaldt
2005-01-16 7:44 ` Brad Midgley
2005-01-24 7:35 ` Brad Midgley [this message]
2005-01-24 12:28 ` Marcel Holtmann
2005-01-24 12:32 ` Marcel Holtmann
2005-01-15 16:35 ` [Bluez-devel] " Paul Ionescu
2005-01-15 17:26 ` Lars Grunewaldt
2005-01-15 17:27 ` [Bluez-devel] " Paul Ionescu
2005-01-16 0:29 ` [Bluez-devel] " Peter Robinson
2005-01-16 0:41 ` Lars Grunewaldt
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=41F4A55D.9070701@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