From: Wartan Hachaturow <wartan.hachaturow@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] HSP and audio -- "right thing" to look at?
Date: Tue, 14 Dec 2004 17:31:20 +0300 [thread overview]
Message-ID: <4aaa2e1c04121406315ecf8659@mail.gmail.com> (raw)
Hello.
First of all, thanks for a great job.
Second, a question.
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".
I would be really thankful if someone would summarize the TODOs for
bluez on that matter (like what should be a kernel module, what should
be a userland application, what is good about current snd_bt_sco, and
what is bad), so that I could prepare myself for development on those
subjects in a more "clever" way -- since now I'm pretty lost in the
code and ideas..
--
Thanks in advance, Wartan.
-------------------------------------------------------
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
next reply other threads:[~2004-12-14 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 14:31 Wartan Hachaturow [this message]
2004-12-15 10:52 ` [Bluez-devel] HSP and audio -- "right thing" to look at? 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=4aaa2e1c04121406315ecf8659@mail.gmail.com \
--to=wartan.hachaturow@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