From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] fleshing out audio daemon scenarios
Date: Sun, 03 Jun 2007 10:13:10 +0200 [thread overview]
Message-ID: <1180858390.6872.5.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <d89ddf300706012143s1444d9c9l98f2a06c8a05171b@mail.gmail.com>
Hi Brad,
> I spent some time digging through the alsa api and experimenting with
> the daemons in plugz. I also looked over the traces as some alsa
> clients including kphone and twinkle.
>
> I came across two problems to the design we've discussed
>
> * for combo headsets, we incorrectly assumed we'd get a device open
> that was either write-only or read-write and use that to decide
> whether to use a2dp or sco
> * we didn't have any provisions for two headsets connecting
> independently which we might as well get right (imagine a voip
> appliance)
please stop worrying so much about the combo headsets and the
complicated cases. We can fix them later. The goal should be to get
simple headsets working.
This means for me we have no ALSA plugin configuration option right now.
Let the ALSA plugin connect to the audio service and use whatever
headset or headphone it has available. Currently it is really not
important to get all possible scenarios covered.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-03 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 4:43 [Bluez-devel] fleshing out audio daemon scenarios Brad Midgley
2007-06-03 8:13 ` Marcel Holtmann [this message]
2007-06-03 20:41 ` Brad Midgley
2007-06-04 15:25 ` 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=1180858390.6872.5.camel@aeonflux.holtmann.net \
--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