From: Alain Kalker <miki@dds.nl>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org
Subject: Re: Improve DKMS build of v4l-dvb?
Date: Wed, 11 Mar 2009 15:51:24 +0100 [thread overview]
Message-ID: <1236783084.5991.61.camel@miki-desktop> (raw)
In-Reply-To: <412bdbff0903110714o6f92c8cax96009226d033c611@mail.gmail.com>
Op woensdag 11-03-2009 om 10:14 uur [tijdzone -0400], schreef Devin
Heitmueller:
> I hate to be the one to point this out, but isn't the notion of
> automatically rebuilding the modules for *your* hardware broken right
> from the start? What this would mean that if I own a laptop and my
> USB based capture device happens to not be connected when I upgrade my
> kernel, then my drivers are going to be screwed up?
Not at all. Hardware detection needs to be done only once: when you
first plug in a new device. The result of this detection is then used to
generate a dkms.conf file, which specifies exactly which driver needs to
be (re-)built.
During initial install, and whenever you upgrade your kernel (Whether
you have the device plugged in or not), DKMS will (re-)build the driver
to match the (current or new) kernel and install its modules on your
system. Whenever you plug in your device, the modules making up its
driver will get loaded.
Kind regards,
Alain
next prev parent reply other threads:[~2009-03-11 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 15:34 Improve DKMS build of v4l-dvb? Alain Kalker
2009-03-09 23:43 ` Mauro Carvalho Chehab
2009-03-11 11:36 ` Alain Kalker
2009-03-11 11:47 ` Mauro Carvalho Chehab
2009-03-11 12:03 ` Alain Kalker
2009-03-11 14:14 ` Devin Heitmueller
2009-03-11 14:51 ` Alain Kalker [this message]
2009-03-11 11:50 ` Alain Kalker
2009-03-13 9:12 ` Trent Piepho
2009-03-17 15:29 ` Alain Kalker
2009-03-17 19:50 ` Trent Piepho
2009-03-18 1:12 ` Alain Kalker
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=1236783084.5991.61.camel@miki-desktop \
--to=miki@dds.nl \
--cc=devin.heitmueller@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox