Re: [Bluez-devel] btsco2

Brad Midgley
2004-12-01T21:32:33Z

Thomas

> Currently there is no support for multiple headset because of missing
> arguments. It was an open question how it should be done.

to actually answer the question, this looks best:

- ./btsco2 <mac1> -1 <mac2> 1 <mac3> 2
Where -1 in the Channel Parameter stand for Autodetec

because I'm not sure the autodetect will always work. Can we use '0'
instead of '-1' for autodetect though? -1 looks like a flag.

> This would make it to what it is an small deamon with no dependecies out
> of the kernel. This is ideal for embeded system.

If we combine the a2dp and sco support, then we need to use
alsa-lib/aserver because it requires userspace audio processing.

If you want a voip application to work seamlessly with the headset, to
make the headset ring on an incoming call for example, we need some kind
of signaling like dbus.

We can continue to maintain a daemon that does not support these
features and works well for embeded systems. What applications will you
use the headset with and how will they start/stop/detect connections?

>>> c) Is there any Plan to allow th BT-SCO Sound driver in kernel Space
>>> to handle mor than one bluetooth as sound device.
>>> Nice would be an option to tell the driver how many sound device he
>>> sould allocate.

> If there is an support i will build it in.

the kernel needs changes in bluez.

Marcel explained it once: "To get more than one SCO channel working the
hci_usb driver must be fixed to dynamicaly change the alternate settting."

again, I don't know SCO well enough to understand this, but it sounds
fundamental.

the btsco in the kernel also needs to be changed to allow for multiple
simultaneous audio streams.

brad