From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eliot Blennerhassett Subject: Re: alsa-compile.sh - easy testing of latest ALSA code Date: Wed, 24 Feb 2010 09:51:47 +1300 Message-ID: <4B843FE3.3030606@audioscience.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by alsa0.perex.cz (Postfix) with ESMTP id A3B6B1038AF for ; Tue, 23 Feb 2010 21:52:36 +0100 (CET) Received: from [192.168.1.6] (121-72-250-62.cable.telstraclear.net [121.72.250.62]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KYB00CCQBBLGU10@smtp3.clear.net.nz> for alsa-devel@alsa-project.org; Wed, 24 Feb 2010 09:52:34 +1300 (NZDT) In-reply-to: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Jaroslav Kysela Cc: Takashi Iwai , ALSA development List-Id: alsa-devel@alsa-project.org Jaroslav Kysela wrote: > On Tue, 23 Feb 2010, Takashi Iwai wrote: >> Just one point I noticed quickly is that the standard directory for >> update modules is either /lib/modules/$VERSION/updates or >> /lib/modules/$VERSION/extras. We should follow that. > > The script just call 'make install-modules' in the alsa-driver package. > Anyway, overwriting kernel modules is just a workaround to bypass the > standard packaging. I don't think that using a special directory helps. I think it helps: Building drivers from source I usually configure --with-moddir=updates/alsa This means * The newly generated modules do not overwrite the distro supplied ones. * I can easily revert to the distro ones by deleting updates/alsa (my updates directory also has a dkms subdirectory) and rerunning depmod -- Eliot