Re: should the module script be invoked every time?

[Pedro Lopez-Cabanillas <plcl@telefonica.net>]

On Monday 25 November 2002 22:57, David Brownell wrote:
> Pedro Lopez-Cabanillas wrote:
> > Is there a reason to name the hotplug scripts like the modules?
>
> Keeping things straight, and making it so you don't need to make any
> kind of error-prone modification to files in tha quirky syntax.
>
> This is a bug that's been hanging around for a while.  The fix should
> finally be in current CVS, along with a few other updates mostly for
> a bit more intelligence about how hotplug changed in 2.5 ...

That's good, but IMHO there are several situations for hotplug to give some 
kind of support.

1. Scripts that need to run once, before or after modprobe. This is usually 
done with modules.conf (pre-install/post-install), but i would like to do 
that with hotplug also...

2. Scripts that need to run every time the device is plugged or unplugged, 
even if the driver is already loaded or not. That is the case of our ezusbmidi 
firmware loader.

BTW, there can be several drivers for the same device, i.e. 'usb-midi' is the 
OSS driver and 'snd-usb-audio' is the ALSA driver. Midiman MidisportNxN 
devices may work with both drivers, but some firmware is needed  first. The 
name 'ezusbmidi' for the script is neutral, and associated to the  EZ-USB 
devices, not the driver name.

I know another firmware for the same devices:
http://www.informatik.uni-halle.de/~ladischc/midisport_linux_firmware.html
That script is named 'midisport_fw', and i like that name.

Regards,
Pedro



-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
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