From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?
Date: Tue, 27 Feb 2001 06:46:41 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98325629904606@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>
David Brownell wrote:
>>> I think the plan of record for 2.4 is to make hotplug handle cardbus
>>> and pcmcia_cs/cardmgr handle pcmcia. If anyone thinks it's
>>> something else, please speak up!
No. Unless I am greatly mistaken, all PC Cards can be handled
by /sbin/hotplug by 2.4.x drivers and cardmgr should ignore
devices supported by those drivers. I guess all that's really
needed from pcmcia_cs at this point is cardctl and the config
files.
>> That's rather ugly (cardmgr will still print messages for everything
>> that's inserted),
It shouldn't, since it should be ignoring those devices.
> Noise in /var/log/messages that will normally be ignored.
> (If it's a problem, wouldn't it be a cardmgr problem?)
>
>> inconsistent in UI (cardmgr beeps, etc., hotplug
>> doesn't),
Shouldn't happen, unless you are trying to mix 2.4.x
drivers with pcmcia_cs drivers (can this even work?).
I punted on testing pcmcia_cs stuff a long time ago
and just use the 2.4.x drivers for everything. Works
for me.
<snip>
> Though if you really think that CardBus hotplugging should
> beep, that should be an easy patch ... cPCI evidently uses
> blue lights in its feedback (doesn't Compaq's Hotplug PCI
> use LEDs too?), so that shouldn't be a PCI-wide policy.
I don't think the beeps are needed, but I suppose we could
make it a configuration setting. Some people, understandably,
like the reassurance of system feedback telling them that
everything is working as it should be.
>> and just generally odd from an end-user's perspective
>> (You see, if you plug *that* card into the slot, you need cardmgr
>> running; if you plug that other card in, you need hotplug.)
>
>
> "Have both these installed and any supported card will work"
> doesn't seem odd! Quite the opposite.
If you are using the 2.4.x kernel drivers and pcmcia_cs cardctl
and config files, none of this should be a problem.
>> It's actually not too hard to make cardmgr work fine with 2.4.
>
>
> Never said it was. The question is how to handle cardbus
> support, given that pcmcia_cs (with cardmgr) is oriented
> towards pcmcia while the overall Linux direction seems to
> be to towards a more general framework for pci hotplug.
The sooner we can supercede pcmcia_cs functionality with
drivers in the kernel tree and a hotplug support package,
the happier I'll be.
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
next prev parent reply other threads:[~2001-02-27 6:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 8:47 OT(?) -- Should the net.agent script cause "ifup lo" to be run? Miles Lane
2001-02-25 10:03 ` Adam J. Richter
2001-02-25 21:37 ` Bill Nottingham
2001-02-25 23:45 ` David Brownell
2001-02-26 0:38 ` Bill Nottingham
2001-02-26 3:40 ` David Brownell
2001-02-26 4:12 ` Bill Nottingham
2001-02-26 4:14 ` Bill Nottingham
2001-02-26 6:59 ` Miles Lane
2001-02-26 7:17 ` Miles Lane
2001-02-26 16:50 ` David Brownell
2001-02-26 17:31 ` David Brownell
2001-02-26 19:52 ` Bill Nottingham
2001-02-26 22:08 ` David Brownell
2001-02-26 22:14 ` David Brownell
2001-02-26 22:17 ` David Brownell
2001-02-26 22:24 ` Bill Nottingham
2001-02-26 22:30 ` Bill Nottingham
2001-02-26 22:48 ` David Brownell
2001-02-27 6:23 ` Miles Lane
2001-02-27 6:46 ` Miles Lane [this message]
2001-02-27 7:17 ` Miles Lane
2001-02-27 7:23 ` Miles Lane
2001-02-27 7:54 ` David Hinds
2001-02-28 5:14 ` Miles Lane
2001-02-28 16:50 ` David Brownell
2001-02-28 17:24 ` David Hinds
2001-03-01 4:37 ` David Brownell
2001-03-01 5:27 ` Bill Nottingham
2001-03-01 5:34 ` Bill Nottingham
2001-03-01 5:45 ` David Hinds
2001-03-01 17:27 ` David Brownell
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-98325629904606@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).