From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: I knew how to do this once...
Date: Fri, 17 Feb 2006 22:09:42 +0000 [thread overview]
Message-ID: <20060217220942.GA14432@kroah.com> (raw)
In-Reply-To: <200602160530.k1G5UTNG020004@deneb.dwf.com>
On Fri, Feb 17, 2006 at 12:47:38PM -0700, Reg Clemens wrote:
> OK, sorry to bother you again, but perhaps you can fill me in on this.
> >
> > Is one module dependant on the other one? If so, modprobe will handle
> > it automatically. Otherwise, just put it in the file that your distro
> > uses to load modules at boot time, in the order you want it to be
> > loaded.
> >
> OK, excuse me if this seems like a dumb question, but I am not familiar
> with whats included in a kernel module. If I have the source is there
> some line to look for that tells the kernel that this guy is dependant on
> another module? Or vice versa?
modprobe -n -v module_name
will show you what modules will be loaded in what order so that any
dependancies in "module_name" are handled properly.
> Ditto, is there something there that tells the kernel that this
> should be loaded when /dev/ttyS0 is touched? From what you say
> Ill assume so, but what is it so I can check to see if its there
> or not.
Yes, look for the MODULE_ALIAS_CHARDEV_MAJOR() macro.
But please realize, that's the "old style" way of loading modules, and
is not recommended. It's because the major:minor does not describe a
driver properly anymore, with the different types of serial, usb, and
other drivers.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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
prev parent reply other threads:[~2006-02-17 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 5:30 I knew how to do this once clemens
2006-02-17 3:42 ` Greg KH
2006-02-17 19:47 ` Reg Clemens
2006-02-17 22:09 ` Greg KH [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=20060217220942.GA14432@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).