From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HSP and audio -- "right thing" to look at?
Date: Wed, 15 Dec 2004 11:52:01 +0100 [thread overview]
Message-ID: <1103107921.2143.197.camel@pegasus> (raw)
In-Reply-To: <4aaa2e1c04121406315ecf8659@mail.gmail.com>
Hi Wartan,
> As far as I see, most development on audio transmission is happening
> at bluetooth-alsa, which is a separate project from bluez (right?).
> Having read the mailing list, I didn't quite understand the
> development direction that bluez would like to follow "mainstream"
> implementing audio and headset profiles, and if things now being
> implemented by bluetooth-alsa are "Right Way".
the Bluetooth-ALSA project is somekind of spin-off to play with headset,
handsfree and advanced audio support that is actually to experimental to
merge it back into BlueZ mainline. However it will be merged back when
it is more stable and the best solution is found. Besides the different
website and their CVS, the bluez-devel mailing list is used for the
discussion.
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-12-15 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 14:31 [Bluez-devel] HSP and audio -- "right thing" to look at? Wartan Hachaturow
2004-12-15 10:52 ` Marcel Holtmann [this message]
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=1103107921.2143.197.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox