Return-Path: Message-ID: <4118E6A1.4030709@superbug.demon.co.uk> Date: Tue, 10 Aug 2004 16:15:45 +0100 From: James Courtier-Dutton MIME-Version: 1.0 To: Marcel Holtmann CC: BlueZ Mailing List Subject: Re: [Bluez-devel] snd-bt-sco development teamup... References: <4117AB9A.9010909@dark-reality.de> <1092071356.4564.12.camel@pegasus> <4117B098.5020805@dark-reality.de> <1092073167.4564.26.camel@pegasus> <4117C0AB.2010609@superbug.demon.co.uk> <1092090364.4564.46.camel@pegasus> <41180E64.1010007@dark-reality.de> <1092140041.4564.96.camel@pegasus> <1092143505.4564.117.camel@pegasus> <4118D049.9060000@superbug.demon.co.uk> <1092145771.4564.148.camel@pegasus> <4118D6B9.3090708@superbug.demon.co.uk> <1092148473.4564.156.camel@pegasus> In-Reply-To: <1092148473.4564.156.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed List-ID: Marcel Holtmann wrote: > 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 > > I thought that if you wished to submit a BlueZ ALSA driver, you would be submitting it to the person mentioned in this record. SOUND P: Jaroslav Kysela M: perex@suse.cz L: alsa-devel@alsa-project.org S: Maintained I did not know that you could bypass that person to get a SOUND related item into the kernel. I was just offering to help with the submission. James