From: Takashi Iwai <tiwai@suse.de>
To: Brad Midgley <bmidgley@xmission.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: bluetooth headset audio
Date: Thu, 30 Sep 2004 11:08:57 +0200 [thread overview]
Message-ID: <s5hzn38xgwm.wl@alsa2.suse.de> (raw)
In-Reply-To: <415B805B.9040900@xmission.com>
At Wed, 29 Sep 2004 21:41:15 -0600,
Brad Midgley wrote:
>
> Hi
>
> I am working with the group doing bluetooth audio.
> (http://sourceforge.net/projects/bluetooth-alsa/)
>
> Right now we have alsa patches to add a bluetooth alsa device to the
> kernel. It works in conjunction with a userspace bluetooth daemon. It's
> not ideal. For one thing, we should be able to support multiple
> bluetooth headsets at once but that would require more kernel changes.
>
> Is there any way to have an alsa sound driver that lives mostly in
> userspace?
Yes, you can write a dedicated plugin of alsa-lib.
> If there was something like that, we could load up one driver
> for each headset we wanted to support. We have to route things through
> userspace anyway to use the bluetooth device. It might also be easier to
> get patches accepted. :)
Patches to drivers are welcome, too :)
The reason I don't take the current bt-sco driver is the design
problem as you wrote above. We should implement either only on
user-space or on kernel-space.
I recently talked with Marcel Holtmann, and he suggested to write
rather a kernel driver. I'd like to develop it when I have some time
later.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
prev parent reply other threads:[~2004-09-30 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 3:41 bluetooth headset audio Brad Midgley
2004-09-30 9:08 ` Takashi Iwai [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=s5hzn38xgwm.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bmidgley@xmission.com \
/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.