From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: starting btsco-in-libalsa
Date: Thu, 09 Dec 2004 10:31:41 -0700 [thread overview]
Message-ID: <41B88BFD.8000907@xmission.com> (raw)
In-Reply-To: <41B83BA8.5010001@suche.org>
Thomas,
> i think this goes to the wrong direction.
> 1. Even if there exist alsa library for many programms it is sufficent
> to use /dev/dsp and /dev/audio.
> This mean that the soundcard driver should work independent of the alsa
> library.
...
> So what are the grounds for moving btsco to the lib inseat of moving it
> to the module ?
I think Marcel explained sufficiently that this is how we can get
handsfree and a2dp profiles working properly in the audio driver.
When we get the libalsa stuff going, there will be overlap in function
with the current kernel module and daemon, but we can keep the kernel
module in our project. As with everything open source, it'll be
maintained by people who care about it.
Brad
-------------------------------------------------------
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-09 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 9:28 [Bluez-devel] starting btsco-in-libalsa Brad Midgley
2004-12-09 10:57 ` Marcel Holtmann
2004-12-09 11:48 ` [Bluez-devel] " suche.org
2004-12-09 12:07 ` Marcel Holtmann
2004-12-09 12:49 ` [Bluez-devel] Re2: " suche.org
2004-12-09 13:10 ` [Bluez-devel] " Marcel Holtmann
2004-12-09 17:31 ` Brad Midgley [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=41B88BFD.8000907@xmission.com \
--to=bmidgley@xmission.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