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

[Marcel Holtmann <marcel@holtmann.org>]

Hi James,

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

why should this be? ALSA is part of the Linux 2.6 kernel and so I would
submit a BlueZ ALSA driver for kernel inclusion only. I don't care about
the ALSA CVS, because the ALSA CVS must track the kernel and not vice
versa.

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

Maybe I have to repeat it, but I don't care about the ALSA CVS and any
older kernel versions. The current mainline kernel is the only base.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel