From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Tue, 06 Feb 2001 03:00:07 +0000 Subject: Re: We need reference implementations for each driver/bus type. 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 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" To: Sent: Saturday, February 03, 2001 3:48 PM Subject: 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 > Linux-hotplug-devel@lists.sourceforge.net > http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel