linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug TTD
Date: Sat, 03 Feb 2001 23:37:06 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98124332509105@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97901650309422@msgid-missing>

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

  parent reply	other threads:[~2001-02-03 23:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  4:59 hotplug TTD Morton, Andrew [WOLL:4009-M:EXCH]
2001-01-09  5:47 ` Miles Lane
2001-01-09  6:55 ` Miles Lane
2001-01-09  8:49 ` Adam J. Richter
2001-01-09 17:09 ` David Brownell
2001-01-09 17:38 ` David Brownell
2001-01-10  6:20 ` Grover, Andrew
2001-01-10  6:34 ` Grover, Andrew
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:59 ` Andrew Morton
2001-01-11 16:10 ` David Brownell
2001-01-11 16:40 ` David Brownell
2001-01-11 17:18 ` David Hinds
2001-01-11 18:04 ` David Brownell
2001-01-12  0:09 ` Grover, Andrew
2001-01-12  0:33 ` Grover, Andrew
2001-01-12  1:13 ` Grover, Andrew
2001-01-12 12:51 ` Andrew Morton
2001-01-12 16:42 ` David Brownell
2001-01-12 17:37 ` David Brownell
2001-01-12 23:45 ` Keith Owens
2001-01-13 18:54 ` David Brownell
2001-01-13 23:25 ` Keith Owens
2001-02-03 23:37 ` Miles Lane [this message]
2001-02-03 23:48 ` Keith Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-98124332509105@msgid-missing \
    --to=miles@megapathdsl.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).