From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Q] cPCI hotplugging
Date: Mon, 15 Jan 2001 22:44:26 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97959863501530@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97958292121643@msgid-missing>
I think the rule of thumb is that if you want it to happen,
start to make it happen!
How would CompactPCI hotplugging work differently? Knowing
exactly nothing about it, I'd hope that not much was needed.
But maybe there is a codepath that only Cardbus triggers, so
far, and that'd need to kick in.
It's linux/drivers/pci/pci.c that issues call_usermodehelper(),
which is pretty generic. If cPCI called that, it might "just
work". If you try the latest hotplug script (with a PCI
agent) does anything happen?
- Dave
----- Original Message -----
From: Eric <ebrower@usa.net>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Monday, January 15, 2001 10:21 AM
Subject: [Q] cPCI hotplugging
Hi folks,
I was referred to this group by an article at lwn.net, and
it seems that some pretty exciting stuff is going on here.
My question is whether or not this list is concerning itself
with PCI (non-cardbus) hotplug, or simply focusing (for now)
on USB, FireWire and Cardbus. If so, is there any preliminary
documentation on this subsystem (the webpage is understandably
sparse at this time)?
I have been working with a Sun CP1400/1500 CompactPCI box and
it would be most excellent to look into CompactPCI hotplugging.
Thanks for the update,
E
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-15 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 10:21 [Q] cPCI hotplugging Eric
2001-01-15 21:21 ` Matthew Dharm
2001-01-15 22:44 ` David Brownell [this message]
2001-01-15 22:48 ` Scott Laird
2001-01-16 16:47 ` Zink, Dan
2001-01-16 18:54 ` Miles Lane
2001-01-16 21:19 ` Matthew Dharm
2001-01-16 22:30 ` Zink, Dan
2001-01-16 22:51 ` 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-97959863501530@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).