From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to check if driver is in-built or module?
Date: Sat, 04 Mar 2006 00:12:11 +0000 [thread overview]
Message-ID: <1141431131.8309.5.camel@syndicate.netsplit.com> (raw)
In-Reply-To: <1141418150.4408a8a625721@cs1.alpha12.l-secure.net>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Fri, 2006-03-03 at 22:01 +0100, Marco d'Itri wrote:
> On Mar 03, juuso.alasuutari@tamperelainen.org wrote:
>
> > How can I tell udev to modprobe <module> only if <module> exists and hasn't been
> > compiled in the kernel? In my experience modules are visible to udev only when
>
> # check if the device has already been claimed by a driver
> ENV{PHYSDEVDRIVER}=="?*", GOTO="hotplug_driver_loaded"
>
> ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe $env{MODALIAS}"
>
> LABEL="hotplug_driver_loaded"
>
This breaks drivers like joydev which augment an existing loaded driver.
PHYSDEVDRIVER contains usbhid, so you never load joydev (which is
expanded by the MODALIAS).
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-04 0:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 20:35 How to check if driver is in-built or module? juuso.alasuutari
2006-03-03 21:01 ` Marco d'Itri
2006-03-04 0:12 ` Scott James Remnant [this message]
2006-03-04 0:51 ` Greg KH
2006-03-04 2:49 ` juuso.alasuutari
2006-03-04 5:42 ` Greg KH
2006-03-04 12:07 ` juuso.alasuutari
2006-03-04 12:10 ` Marco d'Itri
2006-03-06 23:45 ` juuso.alasuutari
2006-03-08 9:38 ` Andrey Borzenkov
2006-03-31 20:52 ` juuso.alasuutari
2006-04-01 1:05 ` Greg KH
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=1141431131.8309.5.camel@syndicate.netsplit.com \
--to=scott@ubuntu.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).