From: Linas Vepstas <linas@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug SIG
Date: Mon, 23 Aug 2004 22:11:51 +0000 [thread overview]
Message-ID: <20040823221151.GZ14002@austin.ibm.com> (raw)
In-Reply-To: <E8C532D801BE5B479B28B626184E8CDD05E7AE07@tayexc14.americas.cpqcorp.net>
Hi,
> 1. Documentation and more documentation.
Yes, please.
> 2. Constant regression testing. As not a lot of people have hardware
> that supports various hotplug and they are not enabled by default new
> features tend to break them.
Yes.
I am not aware of any single, unified, architecture-independent API
or user-space tools for performing PCI hotplug. If they do exist,
then my ignorance can be blamed on bad documentation.
-- There's a command-line tool I use on powerpc that does things
like blink LED's in order to better identify the PCI slot, so
that you don't actually remove the wrong card. A generic
tool that did this for all arches would be nice.
-- Some people like to "echo 1 > /sys/bus/pci/something" to turn
power on and off for a given PCI slot, but its not obvious that
this is how all the various arches work; nor is it obvious
how to match up a given 'geographical' slot location to a given
/sys/whatever entry. So unifying all this would be nice.
Linas.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-08-23 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 15:35 Hotplug SIG Silbermann, Martine
2004-08-12 16:48 ` Greg KH
2004-08-12 19:51 ` Dave Hansen
2004-08-23 22:11 ` Linas Vepstas [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=20040823221151.GZ14002@austin.ibm.com \
--to=linas@austin.ibm.com \
--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).