From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Need for Bluetooth A2DP sink
Date: Fri, 25 Mar 2005 00:05:40 +0100 [thread overview]
Message-ID: <1111705540.9195.15.camel@pegasus> (raw)
In-Reply-To: <42430E8D.9030609@xmission.com>
Hi Brad,
> As Marcel pointed out, Henryk's SBC implementation includes decoding.
>
> Implementing the AVDTP part of the sink would be very much like what
> we're doing in a2play.c, but it would require some coding. If you're
> familiar with the spec it could be done in a few days.
for checking out the Toshiba Windows stack, I wrote something that could
be extended to A2DP sink. However I can't find it anymore.
The Toshiba Windows stack also supports the A2DP profile, but only with
their own SR-1 headphone. The details for that can be found at
http://www.holtmann.org/linux/bluetooth/audio.html
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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-03-24 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 18:47 [Bluez-devel] Need for Bluetooth A2DP sink Shawn Rutledge
2005-03-24 19:01 ` Brad Midgley
2005-03-24 23:05 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 15:18 Wu, Qi (K-EFE/I)
2004-12-15 16:24 ` 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=1111705540.9195.15.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.