From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: CVS ALSA failed upgrade in Linux 2.6.3 Date: Tue, 02 Mar 2004 18:33:33 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200403021728.RAA18607@liam2.demon.co.uk> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <200403021728.RAA18607@liam2.demon.co.uk> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: William Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Tue, 2 Mar 2004 17:28:18 GMT, William wrote: > > Takashi Iwai wrote: > >> Thanks for explaining that. Please would you delete the word "simply" in > >> the explanation on alsa-project.org because it's misleading. > > > >maybe better to remove the whole sentense. > > I think it would be useful to keep an explanation of how to install > CVS alsa-kernel into a Linux 2.6.x source tree. > > BTW, why is there still an alsa-driver package? > Is there any difference between (a) installing alsa-kernel into Linux 2.6.x > and (b) installing alsa-driver in the normal way with the configure option > --with-kernel=somewhere/linux yes, alsa-kernel is just for update of 2.6.x tree, and it doesn't include the experimental new drivers included in alsa-driver tree. alsa-driver tree also includes bunch of wrappers for 2.2/2.4 kernels. that's why i wrote above to remove the sentense. if you copy the files of alsa-kernel, you'll have no such new drivers. > >the scripts directory shouldn't be copied. > >also, Documentation directory goes to linux/sound/Documentation/sound/alsa > > Don't you mean "linux/sound/Documentation"? sorry, linux/Documentation/sound/alsa. Takashi ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click