From: Eliot Blennerhassett <linux@audioscience.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: alsa-compile.sh - easy testing of latest ALSA code
Date: Wed, 24 Feb 2010 09:51:47 +1300 [thread overview]
Message-ID: <4B843FE3.3030606@audioscience.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1002231003530.28127@eeebox2.perex-int.cz>
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
prev parent reply other threads:[~2010-02-23 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 16:37 alsa-compile.sh - easy testing of latest ALSA code Jaroslav Kysela
2010-02-23 8:18 ` Takashi Iwai
2010-02-23 9:26 ` Jaroslav Kysela
2010-02-23 20:47 ` Eliot Blennerhassett
2010-02-23 22:41 ` Takashi Iwai
2010-02-24 12:20 ` Jaroslav Kysela
2010-02-23 20:51 ` Eliot Blennerhassett [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B843FE3.3030606@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.