From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Wed, 12 Dec 2001 20:24:29 +0000 Subject: Re: newbie questions on hotplug with IBM X20 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > > 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