Re: [Bluez-devel] snd-bt-sco development teamup...

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

Marcel Holtmann wrote:
> 
> the point is in writing an ALSA driver and not changing the ALSA
> subsystem. The SCO driver is part of the Bluetooth subsystem and so it
> will go in by me. The ALSA subsystem provides an in-kernel API and that
> can be used without any acknowledge of the ALSA maintainer.

ALSA is very modularised. This separates the hardware specific driver 
stuff from the more general alsa kernel code. So, if you write your own 
ALSA driver hardware module, it will have to depend on other ALSA 
modules. The only ALSA API that is going to be stable is the user land 
alsa-lib, which talks to applications. Although the ALSA kernel API and 
ALSA low level hardware driver API has not changed in some time, the 
ALSA maintainer reserves the right to change it at any time without 
having to warn people, as alsa-lib hides all the changes from users.
It is therefore a good idea to place any ALSA specific code in the ALSA 
tree, so that the ALSA maintainers keep it's kernel API up to date.
This would then leave the BlueZ team to only have to worry about the 
ALSA to BlueZ API.

> 
> 
>>I was just offering to help with the submission.
> 
> 
> Thanks, but going through the ALSA CVS won't give me any advantage. I
> hope that I can talk with Jaroslav about the Bluetooth issue at the
> Linux-Kongress next month.

He does actually answer emails as well. ;-)

> 
> Regards
> 
> Marcel
> 

James