From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Christian Ege <chege@cybertux.info>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Bluetooth headset driver
Date: Mon, 26 Apr 2004 22:01:40 +0100 [thread overview]
Message-ID: <408D78B4.4000700@superbug.demon.co.uk> (raw)
In-Reply-To: <1083001170.4dmq5ufy93r4@cybertux.akr.de>
Christian Ege wrote:
> Hi anyone working on something simalar to this?
> http://www.dcs.gla.ac.uk/~jp/snd-bt-sco/
>
> The author of this driver won't continue his work because he switched to MAC OS
> ;-(
>
> I think the way he tried to integrate this driver into alsa isn't the best way.
>
> I am not that kind of Kernel guru but if there are some other people arround
> here interested in that stuff it shouldn't be too much work to integrate this
> driver in alsa.
>
> Or isn't there any interest in bluetooth communication ;-)
>
>
> cu
> chege
>
I have been working on a bluetooth alsa driver, but it turns out to be a
lot more complicated that one would at first think.
1) The bluetooth headset profile is a "profile" and therefore deemed to
be a user space and not a kernel space program.
2) The current bluez bluetooth stack in the kernel does not provide any
"playback" position feedback, so we would not be able to implement
snd_pcm_delay() and therefore it would be extremely difficult to make a
low latency app using it. The first use of a headset profile is for full
duplex speach, which requires low latency, so that is a problem.
3) audio data path would therefore go from alsa-lib(userspace) ->
alsa-driver(kernel-space) -> headset profile (userspace) -> bluez stack
(kernel space). Extremely messy in my view!
(What http://www.dcs.gla.ac.uk/~jp/snd-bt-sco/ currently does in fact)
Summary: -
Until the bluez stack provides a mechanism for us to do
"snd_pcm_delay()", there is very little point advancing with the alsa
side for bluetooth.
Who will want to use a headset that has large uncontrollable latencies?
Cheers
James
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
prev parent reply other threads:[~2004-04-26 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:39 Bluetooth headset driver Christian Ege
2004-04-26 18:23 ` Robert Rozman
2004-04-26 21:01 ` James Courtier-Dutton [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=408D78B4.4000700@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=chege@cybertux.info \
/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