From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Mon, 21 Jan 2002 03:17:44 +0000 Subject: Re: Device has module AND init script 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 > I have a joystick which has the usual module stack, but which also needs to > have jscal executed upon hotplugging (via my script > /etc/hotplug/usb/setupstick). There are three issues here: > > 1. The logical place to name the setup script is usb.usermap, but if any > modules are found, usb.agent bypasses usb.usermap. Workaround: put the > lines in usb.handmap. Simplest is to just name your setup script after the name of the relevant module ... perhaps "joydev", and use "case $PRODUCT" in that script to trigger "jscal" (or "setupstick" etc) for this device. > 2. Both modules and setup scripts have an order dependence which modprobe > may not be able to 100% straighten out. Workaround: Use the source, Luke! > The right effect is achieved if the script is listed first, then the most > specific driver, to the most general. I'm not sure how order dependence > could be enforced neatly, specifically to get the script executed last, so > I didn't try to hack anything for this. The sequence is always: modprobe, then run setup script of that same name (if it exists). The setup scripts can run modprobe itself, if that helps. If that doesn't resolve your problem, then I'm not sure I understand the issue you're trying to describe. > 3. In the obsolete version in my distro (2001_04_24-1_6), > ... I'll look at that a bit later. - 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