Re: alsa-compile.sh - easy testing of latest ALSA code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 24 Feb 2010, Eliot Blennerhassett wrote:

> 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

OK. I got the point. It's fixed in the current alsa-compile.sh script. 
Also, the --kmodclean option was added to remove ALSA kernel modules in 
this location.

 						Jaroslav

-----
Jaroslav Kysela <perex@xxxxxxxx>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.

_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux