From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need new modutils aliases for 2.4.0? (Was) Re: Cannothotplugcardbus cards.
Date: Fri, 26 Jan 2001 04:54:25 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98048495224744@msgid-missing> (raw)
On Thu, Jan 25, 2001 at 01:43:18PM -0800, Miles Lane wrote:
> David Brownell wrote:
> >
> > My thoughts exactly. 2.4 should be hotplugging the 2.4 kernel's
> > Cardbus drivers ... unbundled pcmcia_cs drivers shouldn't be used,
> > as a rule, the kernel drivers get more attention (and the expectation
> > is that'll continue).
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.
> 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.
-- 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
next reply other threads:[~2001-01-26 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 4:54 David Hinds [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 18:10 Need new modutils aliases for 2.4.0? (Was) Re:Cannothotplugcardbus cards David Hinds
2001-01-27 3:12 Need new modutils aliases for 2.4.0? (Was)Re:Cannothotplugcardbus cards David Hinds
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-98048495224744@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 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.