From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need new modutils aliases for 2.4.0? (Was)
Date: Fri, 26 Jan 2001 16:44:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98052821621825@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98021018610942@msgid-missing>
> From: David Hinds <dhinds@sonic.net>
> Sent: Thursday, January 25, 2001 8:54 PM
>
> Actually I think all the evidence suggests that at this point the
> unbundled pcmcia drivers still get considerably more attention than
> the kernel drivers, at least at the end user level.
You're likely right about that, but I guess I thought that was
something that folk wanted to change. Maybe not all at once ...
and focussing on Cardbus at first.
> > I would like to explore the "mutual-noninterference pact"
> > between Cardmgr and /sbin/hotplug. It seems important to
> > get right. Obviously, David Hinds will play a big role
> > in this.
>
> I have added code to cardmgr to parse modules.pcimap to figure out
> which cards should be handled by the hotplug stuff. I still have a
> few things to clean up but I don't think it will be hard.
That sounds good. Can that also understand the network hotplugging?
Or is that going to need work yet?
- Dave
_______________________________________________
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-01-26 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 0:33 Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards Miles Lane
2001-01-23 0:52 ` Miles Lane
2001-01-23 1:14 ` Bill Nottingham
2001-01-23 3:39 ` David Hinds
2001-01-26 16:44 ` 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-98052821621825@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.