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

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

Marcel Holtmann wrote:
> Hi James,
> 
> 
>>>I prefer the ALSA integration would be written from scratch, because the
>>>original driver was written for a 2.4 kernel and we must concentrate on
>>>the 2.6 series. The ALSA subsytem will be cleaned up in the next kernel
>>>releases and the magic casting stuff they do is still wrong.
>>
>>The latest alsa cvs fixes the magic casting stuff.
> 
> 
> as I said, I don't care about what is in the ALSA CVS or their external
> drivers. The main focus is the ALSA subsystem in the mainline kernel.
> 
> So everone who will work on this have this in mind and start with the
> latest 2.6 kernel. If the ALSA stuff in their CVS is newer, then ping
> them to merge it mainline.
> 
> Regards
> 
> Marcel
> 

I can get modules added to the alsa cvs. I would think that newly 
developed modules should go into cvs first, and then backported to older 
kernel versions. After all, the only way to get snd-bt-sco into the 
linux kernel proper, is via the alsa cvs.
There are various staging steps in the alsa cvs, before a module in the 
alsa cvs gets into the linux kernel proper.

Of course the snd-bt-sco module will just be a bit of shim code between 
alsa and blues. With the major work done in a user space bluetooth profile.

One advantage of alsa, is that once a module is in the alsa cvs, it will 
will always function correctly on all kernel versions, so back porting 
is not an issue with alsa.

James