We need reference implementations for each driver/bus type.

There has been a lot of general discussion of things like using persistent module information verses Distro config scripts verses built-in driver intelligence when it comes to configuring drivers. /sbin/hotplug + /etc/hotplug/usb/MODULENAME and persistent module data are two new and largely unused mechanisms for handling configuration. Wouldn't it be helpful to get a few reference drivers implemented along with attendent configuration files so that driver developers can look at what the benefits and implementation approaches for these new solutions?

Is anyone working on this?

Miles

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

There was a "Visor" HOWTO I saw a while back that showed how to do it, but I'm not sure of its current state. It may still be using the pre-2.4.0 "/etc/usb/drivers/visor" scheme. Basically, you could make sure that when you plugged in your Visor, you could sync right away. Likewise some "gphoto2" users were arranging to tweak camera permissions that way.

- Dave

----- Original Message -----
From: "Miles Lane" <[email protected]>
To: <[email protected]>
Sent: Saturday, February 03, 2001 3:48 PM
Subject: We need reference implementations for each driver/bus type.

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel