[Bluez-devel] fleshing out audio daemon scenarios

["Brad Midgley" <bmidgley@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 740 bytes --]

Hey

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)

So I think a solution is not that complicated, but it gets wordy in
explaining it all out. I did a writeup in the wiki

http://wiki.bluez.org/wiki/Audio#Requirementsoftheaudioservice-alsaplugininterface

Brad

[-- Attachment #1.2: Type: text/html, Size: 900 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel