From: Rajesh Shah <rajesh.shah@intel.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: acpi-devel@lists.sourceforge.net,
pcihpd-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org, dkumar@noida.hcltech.com,
sanjayku@noida.hcltech.com
Subject: Re: [Pcihpd-discuss] Re: ACPI problem with PCI Express Native Hot-plug driver
Date: Mon, 3 Oct 2005 11:14:41 -0700 [thread overview]
Message-ID: <20051003111441.C14857@unix-os.sc.intel.com> (raw)
In-Reply-To: <b115cb5f0510022207k41df0380nfb8b4ee73149f7ea@mail.gmail.com>; from rajat.noida.india@gmail.com on Mon, Oct 03, 2005 at 02:07:26PM +0900
On Mon, Oct 03, 2005 at 02:07:26PM +0900, Rajat Jain wrote:
> Thanks for the insight. But my doubt is that the PCI Express devices
> down the hot-pluggable slots are working fine. i.e. if we forget about
> the hot-plugging / unplugging, the bridges and devices are working
> fine, even with ACPI enabled.
>
> So is the presence of bridges in ACPI namespace required only for
> hot-plugging / unplugging and not for normal operation?
>
Yes, that's correct. The PCI core will correctly scan PCI bridges
independent of their presence in the acpi namespace.
PS: trimming the cc list a bit, as I'm getting rejects due to
too many recipients. pcihp-discuss is the correct list for pciehp
related questions.
Rajesh
next prev parent reply other threads:[~2005-10-03 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 7:57 ACPI problem with PCI Express Native Hot-plug driver Rajat Jain
2005-09-02 7:58 ` Rajat Jain
2005-09-02 17:46 ` [Pcihpd-discuss] " Kristen Accardi
2005-09-05 1:58 ` Rajat Jain
2005-09-30 5:57 ` Rajat Jain
2005-09-30 20:24 ` Rajesh Shah
2005-10-03 5:07 ` Rajat Jain
2005-10-03 18:14 ` Rajesh Shah [this message]
2005-10-05 4:10 ` Rajat Jain
2005-09-02 8:12 ` Greg KH
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=20051003111441.C14857@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dkumar@noida.hcltech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajat.noida.india@gmail.com \
--cc=sanjayku@noida.hcltech.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