From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: We need reference implementations for each driver/bus type.
Date: Sat, 03 Feb 2001 23:48:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98124396809907@msgid-missing> (raw)
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
next reply other threads:[~2001-02-03 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 23:48 Miles Lane [this message]
2001-02-06 3:00 ` We need reference implementations for each driver/bus type David Brownell
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-98124396809907@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).