From: Greg KH <greg@kroah.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:51:32 +0000 [thread overview]
Message-ID: <20060304005132.GA27526@kroah.com> (raw)
In-Reply-To: <1141418150.4408a8a625721@cs1.alpha12.l-secure.net>
On Fri, Mar 03, 2006 at 10:35:50PM +0200, juuso.alasuutari@tamperelainen.org wrote:
> Hello. This is my first post on this list, and I hope I'm not asking something
> that's already been dealt with. (I searched the docs and this list before
> posting.)
>
> 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
> and after they are loaded, which makes finding a solution to my problem a bit
> of a paradox.
Look in /sys/module/ That will have the module name if the module is
loaded _or_ if the module is built into the kernel.
If it's not there, then it should be safe to load it.
Or you can always just try to load the thing, as if it's already in the
kernel built in, it will not be present in the tree as a module.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-03-04 0:51 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
2006-03-04 0:51 ` Greg KH [this message]
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=20060304005132.GA27526@kroah.com \
--to=greg@kroah.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).