From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.4.0 Patch for 3c575
Date: Thu, 11 Jan 2001 17:29:21 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97923417317056@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97923399516514@msgid-missing>
On Thu, Jan 11, 2001 at 09:25:30AM -0800, Miles Lane wrote:
>
> I am going to go through pcmcia-cs and work with you to
> get a comprehensive mapping of device support to the
> kernel drivers. Then, we'll identify all the yet-to-be-ported
> drivers and put together some sort of porting strategy.
See the README-2.4 file (plus the SUPPORTED.CARDS file) in the current
PCMCIA package for this mapping.
> Alright. Can you please work with the folks on
> linux-hotplug-devel@lists.sourceforge.net to come up with
> an acceptable method? Let's open a discussion there on
> what some possible "generic" methods might be. It would
> make a lot of sense to design something that would have
> value across all sorts of drivers, beyond the scope of
> PCMCIA/Cardbus. Ideally, this would allow straightforward
> solutions to the kind of problem we have now for all driver
> modules.
I was thinking of just having a new keyword in /etc/pcmcia/config to
say that certain drivers are "hotplug", which would mean to ignore
those config entries under a 2.4 kernel with hotplug support.
-- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-11 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 17:25 2.4.0 Patch for 3c575 Miles Lane
2001-01-11 17:29 ` David Hinds [this message]
2001-01-11 18:15 ` David Brownell
2001-01-11 19:43 ` Miles Lane
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-97923417317056@msgid-missing \
--to=dhinds@sonic.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).