From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: We need reference implementations for each driver/bus type.
Date: Tue, 06 Feb 2001 03:00:07 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98142870210604@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98124396809907@msgid-missing>
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" <miles@megapathdsl.net>
To: <linux-hotplug-devel@lists.sourceforge.net>
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
prev parent reply other threads:[~2001-02-06 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 23:48 We need reference implementations for each driver/bus type Miles Lane
2001-02-06 3:00 ` David Brownell [this message]
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-98142870210604@msgid-missing \
--to=david-b@pacbell.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).