From: "Sy, Dely L" <dely.l.sy@intel.com>
To: "Shah, Rajesh" <rajesh.shah@intel.com>, "Greg KH" <gregkh@suse.de>
Cc: <linux-pci@atrey.karlin.mff.cuni.cz>,
<linux-kernel@vger.kernel.org>,
<pcihpd-discuss@lists.sourceforge.net>, <akpm@osdl.org>,
"Brown, Len" <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>
Subject: RE: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: Mon, 21 Mar 2005 17:06:47 -0800 [thread overview]
Message-ID: <468F3FDA28AA87429AD807992E22D07E04A3DDC9@orsmsx408> (raw)
On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
> On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
> > - Does this break the i386 acpiphp functionality?
> Dely Sy had tested hotplug with an earlier version of my patches
> (with minor differences from the current series) on i386 and it
> worked fine. She probably hasn't tested the latest one. Dely,
> could you check that please?
I tested an earlier version of this patch on my i386 system with
PCI Express hot-plug slots. The i386 acpiphp functionality worked
fine - i.e. I was able to do hot-plug of single- & multi-function
cards.
I'll check this new patch on my system.
> > - Have you tested other pci hotplug systems with this patch
> > series? Like pci express hotplug, standard pci hotplug,
> > cardbus, etc?
> No, because I the one system I have access to isn't doing any
> hot-plug. I'm working on fixing that but was also hoping to hear
> from others who surely have access to more machines than I do.
PCI Express hot-plug has been tried (see above). The original
acpiphp driver won't detect hot-pluggable slots that locate on the
p2p bridge (PCI Express to PCI/PCI-X bridge) behind another p2p
bridge (root port). Therefore, the acpiphp can't be used for
standard PCI hot-plug in my system.
Thanks,
Dely
next reply other threads:[~2005-03-22 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 1:06 Sy, Dely L [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 3:13 Dely Sy
2005-03-18 21:38 Rajesh Shah
2005-03-19 5:13 ` Greg KH
2005-03-21 18:04 ` Rajesh Shah
2005-03-21 18:27 ` Greg KH
2005-03-31 19:06 ` Len Brown
2005-03-19 13:50 ` Paul Ionescu
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=468F3FDA28AA87429AD807992E22D07E04A3DDC9@orsmsx408 \
--to=dely.l.sy@intel.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.com \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®