linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: Rajat Jain <rajat.noida.india@gmail.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: Fri, 30 Sep 2005 20:24:41 +0000	[thread overview]
Message-ID: <20050930132440.C28328@unix-os.sc.intel.com> (raw)
In-Reply-To: <b115cb5f0509292257j395d60f8j53d1afa967caa263@mail.gmail.com>; from rajat.noida.india@gmail.com on Fri, Sep 30, 2005 at 02:57:07PM +0900

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. 

> 
> I am not sure where the problem lies. But the fact that the entries
> are appearing correctly when I disable ACPI, combined with above error
> messages, I suspect that there is a problem with ACPI namespace
> (probably the resources cannot be found using ACPI).
> 
At init time, the pciehp driver scans the ACPI namespace and tries
to collect resources for all bridges - host as well as PCI. It's
pretty rare for BIOS to describe PCI bridge resources in ACPI
namespace, so that's not unusual. What's unexpected is that these
pciehp bridges weren't even listed in the namespace.

With the pciehp version that has acpi disabled, it's not going to
try to get bridge resources and other information from acpi. In
that case, it simply reads the bridge config space to determine
resource ranges it is decoding. This is what the acpi version of
pciehp also defaults to for PCI bridges that are listed without
resource descriptions in the acpi namespace. So, the error you
are running into is somewhat bogus. The proper long term fix
is to change pciehp to not depend so much on acpi and just use
the pci core for resource management. In the meantime, you should
just use the non-acpi version of pciehp. 

Rajesh



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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

  reply	other threads:[~2005-09-30 20:24 UTC|newest]

Thread overview: 13+ 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] Re: ACPI problem with PCI Express Native Kristen Accardi
2005-09-05  1:58     ` [Pcihpd-discuss] Re: ACPI problem with PCI Express Native Hot-plug driver Rajat Jain
2005-09-30  5:57       ` Rajat Jain
2005-09-30 20:24         ` Rajesh Shah [this message]
2005-10-03  5:07           ` Rajat Jain
2005-10-05  4:10             ` Rajat Jain
2005-09-02  8:12 ` Greg KH
2005-09-03 10:40 ` kylin
2005-09-30  8:20 ` Re: ACPI problem with PCI Express Native Hot-plug driver (Rajat Jain) kylin
2005-10-03  5:20   ` Rajat Jain
2005-10-03 12:16     ` kylin

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=20050930132440.C28328@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.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=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;
as well as URLs for NNTP newsgroup(s).