From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.4.0 Patch for 3c575
Date: Thu, 11 Jan 2001 19:43:45 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97924229211199@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97923399516514@msgid-missing>
David Brownell wrote:
>> 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.
>
>
> That's probably a workable solution. Though I suspect the pcmcia_cs
> package will want a way to detect that hotplug PCI is running, so it
> will do the right thing with such cardbus drivers in atypical setups.
>
> Have you looked at the (PCI-less) /etc/hotplug stuff I sent around?
> We could arrange that the next iteration of that use some sort of
> config file in /etc/hotplug to expose such information; I can toss
> in the PCI/Cardbus support, but it'll be short of testing. The same
> stuff could let the /sbin/hotplug command itself show status info.
Hi Dave,
I'd like to get the Cardbus hotplug stuff working for configuring
my BusPort Mobile, again. As soon as you have thise PCI/Cardbus
support part patched up again, please send it to me and I'll test it.
I fear that there is more brokenness in the call_usermodehelper
stuff, but I hope I'm wrong.
I really am looking forward to seeing what you and David Hinds
come up with. I'll test it like crazy as soon as it's available.
Miles
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-11 19:43 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
2001-01-11 18:15 ` David Brownell
2001-01-11 19:43 ` Miles Lane [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-97924229211199@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).