From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?
Date: Mon, 26 Feb 2001 22:48:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98322846614326@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>
> > Systems with a dozen USB devices are not uncommon;
> > I'd rather rely on hub LEDs for feedback than get lots of
> > noise on reboot, or when I plug in a hub that has a bunch
> > of devices already connected.
>
> I'm not talking about USB at all. I'm talking about the transition
> of users from 2.2 based systems to 2.4, and their expectations
> thereof.
Yet full support for 2.4 includes hotplugging of USB, and one of
your issues was the lack of audible hotplug feedback ...
> > > 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.
>
> One can use cardmgr's previous cardbus support with minor kernel
> patches.
This is the first time I've heard that; the topic has come up
several times, and the story I've gotten from the answers is that
pcmcia_cs integration with kernel cardbus support is still weak.
(I don't have a Cardbus setup, so I have to trust those answers.)
It could be that folk have been going at that question with
different assumptions.
- 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 prev parent reply other threads:[~2001-02-26 22:48 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 [this message]
2001-02-27 6:23 ` Miles Lane
2001-02-27 6:46 ` Miles Lane
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-98322846614326@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 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).