From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miles Lane Date: Sat, 03 Feb 2001 23:37:06 +0000 Subject: Re: hotplug TTD 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 Can we continue this discussion? It seems there are important questions left unanswered here. Keith Owens wrote: > > > >> And, I remember reading that the latest modutils had some > > > >> mechanism to pass config info, but I haven't looked further.. > > > > > > > >That's module configuration data, not device configuration data. > > > > > > It can be either. > > > > Hmm ... is there some simple example module on the web, doing both? > > I probably wouldn't have seen a notice, and haven't had time to do > > more than glance at the persistence patch in the modutils FTP area. > > No module currently uses persistent data. I tested it with some dummy > module code and released the patch. It is up to coders to decide how > they use persistent data. So, are we going to attempt to use the persistent module data for any Hotplug related development? Might this be helpful for giving some more consistent mapping of a device node to a physical device resource (e.g., /dev/eth0 -> the 3c575 with a particular set of device characteristics -- memory ranges, IRQ, DMA, etc)> > >Was the output format text, or binary? Tools could be easier if > >they could rely on text. > > man insmod, man rmmod, man modules.conf. All text. Persistent data > behaves as if you specified the saved values on the insmod command > line. The order is values from modules.conf, then saved persistent > data, then insmod options. modules.conf is default values, persistent > data is what you set the values to after loading, insmod is override > for this load. > > > It'd be nice if Linux had a better solution than distro-specific > > config files to hold device configuration data, and I could see > > the module persistence stuff evolving into that. It'd sure help > > make hotplug policy software be more portable if it could rely on > > all hotpluggable drivers (network, media, ...) using such a scheme. Has anyone begun using this data, yet? _______________________________________________ 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