linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: linux-pci@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: AMCC PPC460EX Canyonlands does not see PCIe end point with only non-prefetchable memory (both 2.6.27.7 and -next)
Date: Wed, 26 Nov 2008 19:26:47 +0100	[thread overview]
Message-ID: <c384c5ea0811261026y73679a16tfa29a33f3e780954@mail.gmail.com> (raw)
In-Reply-To: <c384c5ea0811260725x3476fa43o9950123948e99acb@mail.gmail.com>

On Wed, Nov 26, 2008 at 4:25 PM, Leon Woestenberg
<leon.woestenberg@gmail.com> wrote:
> The non-detected end point boot:
>
> pci 0001:80:00.0: scanning behind bridge, config bf8180, pass 0
> PCI: Scanning bus 0001:81
> PCI: Fixups for bus 0001:81
>
Further debugging.

drivers/pci/probe.c:
static struct pci_dev *pci_scan_device(struct pci_bus *bus, int devfn)
{
...
	if (pci_bus_read_config_dword(bus, devfn, PCI_VENDOR_ID, &l))
		return NULL;
...
	/* some broken boards return 0 or ~0 if a slot is empty: */
	if (l == 0xffffffff || l == 0x00000000 ||
	    l == 0x0000ffff || l == 0xffff0000) {
  	printk(KERN_WARNING "--- slot empty?! l == 0x%lx\n", (u32)l);
		return NULL;
	}

It ends up here with l == 0xffffffff.

Note that u-boot finds the end point vendor ID, and Linux on x86 and
Linux on  mpc8316e powerpc also.

Regards,
-- 
Leon

  reply	other threads:[~2008-11-26 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 14:32 AMCC PPC460EX Canyonlands does not see PCIe end point with only non-prefetchable memory (both 2.6.27.7 and -next) Leon Woestenberg
2008-11-26 15:25 ` Leon Woestenberg
2008-11-26 18:26   ` Leon Woestenberg [this message]
2008-11-28 10:54     ` Leon Woestenberg
2008-12-01  8:11       ` Benjamin Herrenschmidt

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=c384c5ea0811261026y73679a16tfa29a33f3e780954@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).