public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajat Jain <rajat.noida.india@gmail.com>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Kristen Accardi <kristen.c.accardi@intel.com>,
	Linux-newbie@vger.kernel.org,
	linux-hotplug-devel@lists.sourceforge.net,
	acpi-devel@lists.sourceforge.net,
	pcihpd-discuss@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org,
	greg@kroah.com, 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 14:07:26 +0900	[thread overview]
Message-ID: <b115cb5f0510022207k41df0380nfb8b4ee73149f7ea@mail.gmail.com> (raw)
In-Reply-To: <20050930132440.C28328@unix-os.sc.intel.com>

On 10/1/05, Rajesh Shah <rajesh.shah@intel.com> wrote:
> On Fri, Sep 30, 2005 at 02:57:07PM +0900, Rajat Jain wrote:
> >
> > pciehp: pfar:cannot locate acpi bridge of PCI 0xb.
> > ......
> > pciehp: pfar:cannot locate acpi bridge of PCI 0xe.
>
> This is saying that the driver's probe function was called for
> these pciehp capable bridges, but it didn't find them in the
> ACPI namespace.
>
> >

Hi Rajesh,

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?

Thanks,

Rajat

  reply	other threads:[~2005-10-03  5:07 UTC|newest]

Thread overview: 9+ 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 [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=b115cb5f0510022207k41df0380nfb8b4ee73149f7ea@mail.gmail.com \
    --to=rajat.noida.india@gmail.com \
    --cc=Linux-newbie@vger.kernel.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=dkumar@noida.hcltech.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=rajesh.shah@intel.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