From alsa-user-owner@alsa.jcu.cz  Wed Mar 10 17:17:55 1999
Received: from brunel.swec.com (brunel.swec.com [199.103.216.36])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id RAA00137
	for <alsa-user@alsa.jcu.cz>; Wed, 10 Mar 1999 17:14:16 +0100
Received: from usa.net (bsnt3035.swec.com [111.1.20.4])
	by brunel.swec.com (8.9.1/8.9.1) with ESMTP id LAA02492;
	Wed, 10 Mar 1999 11:13:29 -0500
Message-ID: <36E69A77.E185E33D@usa.net>
Date: Wed, 10 Mar 1999 11:14:47 -0500
From: Glenn <dodgepond@usa.net>
MIME-Version: 1.0
To: sharkey@ale.physics.sunysb.edu
CC: alsa-user@alsa.jcu.cz
Subject: Re: [Fwd: ALSA and new kernel/modules]
References: <m10KjlO-000sLNC@lbscissors.kek.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Thanks Eric for the sanity check and the alias. You know I have been writing the
two strings each time. One for the kernel and then another for ALSA, but the
alias is the way I'm going now.

Thanks,
Glenn
-----

sharkey@superk.physics.sunysb.edu wrote:

> > >From what I have read the " #CONFIG_MODVERSIONS=y" is supposed to allow
> > the use of older kernel modules with newer versions. Has anyone else run
> > into this?
>
> I'm not an expert kernel hacker, but it's my understanding that it's supposed
> to allow this to work under the assumption that the only thing that will be
> changed is the version numbers.  In other words, if the new kernel
> version has no changes that would in any way affect ALSA, then the old
> modules will work, and the kernel won't complain about the version number
> mismatch.  If the kernel has changed in any way that affects your module,
> then you'll need to recompile it.
>
> In general, it's safest to recompile.  This goes for all independent kernel
> modules, not just ALSA.
>
> > AS an alternative is it possilbe to copy in the ALSA drivers into the
> > sound directory of the kernel being compiled and have ALSA and/or OSS
> > compiled and made directly instead of finishing the kernel (make
> > modules_install) and then re-making the ALSA modules?
>
> In theory, yes, that's possible, but you'll need to do more than just copy
> it.  You'll need to patch the kernel Makefiles to compile ALSA.  That's much
> more work than it's worth.
>
> > With the frequent versions and improvements in the kernel, I would like
> > to be able to cut down on the time spent and avoid remaking ALSA for
> > each kernel version.
>
> Why don't you just create an alias in your .profile, then?
>
> alias ugrkernel = "cd /usr/src/linux ; make dep ; make clean ; make bzImage ;
> make modules ; make modules_install ; cd /usr/local/src/alsa ; make clean ;
> ./configure ; make install"
>
> Or something like that.
>
> Eric


