Re: [Bluez-devel] HCI USB driver and SCO support

[James Courtier-Dutton <James@superbug.demon.co.uk>]

Max Krasnyansky wrote:
> At 02:35 AM 8/4/2003, Marcel Holtmann wrote:
> 
>>Hi James,
>>
>>
>>>If we are going to use the SCO channels for sound output from 
>>>applications, it would be very useful if we could provide some sort of 
>>>ring buffer support, with hardware pointer updates.
>>>Currently, there are no callbacks from sco to the application layer, 
>>>telling it how many sound samples have actually left the PC for the 
>>>Bluetooth device. This is a requirement if we are to support any sound 
>>>card simulation layer above the SCO layer.
>>>Until this is resolved, we will not be able to implement alsa or oss 
>>>support.
>>
>>I don't care about this at the moment, because the current problem is
>>the hci_usb driver. We need to adjust the alternate setting for the ISOC
>>interface on demand. And this setting depends on the voice setting (8 or
>>16 bit) and the number of SCO connections. If the used alternate setting
>>is not correct, you don't get any correct audio data over the SCO link.
> 
> Yep. I agree. Let's fix the driver/core interaction first.
> 
> 

I would like to help with bluez developement, but it seems that bluez 
developement is not done on kernel 2.6, so I cannot help.
All kernel usb development is done on kernel 2.6, so why developement of 
the bluez hci_usb driver is not also done on kernel 2.6 is a mystery to me.