From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: newbie questions on hotplug with IBM X20
Date: Wed, 12 Dec 2001 20:24:29 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100818898106595@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100815770223799@msgid-missing>
> > So far as I know, there's no standard way for the hotplug
> > scripts to tell when the reason a module can't be loaded
> > is that it's been statically linked. "lsmod" only shows ...
>
> For the USB case, parse /proc/bus/usb/drivers?
That one wasn't a "usb" driver, it's an "input subsystem" driver.
An early USB-only version of the hotplug scripts did look at the
/proc/bus/usb/drivers file, and knew how to work around the
fact that some driver and module names don't match. (One
that comes to mind is "keyboard" vs "usbkbd".) The current
version doesn't ... maybe because after converting to use
the "modules.usbmap" file, it wasn't usually an issue. (The
"mousedev" module in question uses "usb.handmap" to
work around the "no input hotplug" issue.)
> Maybe we can come up with equivalent for other hotplug
> systems during 2.5?
I'd rather see a generic solution that's not specific to
drivers, myself. It's not the sort of thing every driver
subsystem should need to re-invent, IMO.
- Dave
_______________________________________________
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:[~2001-12-12 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 11:46 newbie questions on hotplug with IBM X20 Michael Greenberg
2001-12-12 15:49 ` Greg KH
2001-12-12 19:34 ` David Brownell
2001-12-12 20:03 ` Brad Hards
2001-12-12 20:24 ` David Brownell [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=marc-linux-hotplug-100818898106595@msgid-missing \
--to=david-b@pacbell.net \
--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).