From alsa-user-owner@alsa.jcu.cz  Wed Mar 10 14:29:46 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 OAA19551
	for <alsa-user@alsa.jcu.cz>; Wed, 10 Mar 1999 14:24:12 +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 IAA17671
	for <alsa-user@alsa.jcu.cz>; Wed, 10 Mar 1999 08:23:36 -0500
Message-ID: <36E672A6.BF006211@usa.net>
Date: Wed, 10 Mar 1999 08:24:54 -0500
From: Glenn <dodgepond@usa.net>
MIME-Version: 1.0
To: alsa-user@alsa.jcu.cz
Subject: [Fwd: ALSA and new kernel/modules]
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

Hi,

I have been having trouble getting new kernels to recognize ALSA modules
compiled under older kernel versions, i.e., 2.2.0, 2.2.1, etc. I have
been configuring my kernel part for modules as:

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

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

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?

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.

Thanks,
Glenn

