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 16:25:23 +0100 [thread overview]
Message-ID: <c384c5ea0811260725x3476fa43o9950123948e99acb@mail.gmail.com> (raw)
In-Reply-To: <c384c5ea0811260632n24e8b536v9a4a16833644976c@mail.gmail.com>
Hello,
I enabled more DEBUG output, the online files have been updated. Snippets:
The detected end point boot:
pci 0001:80:00.0: scanning behind bridge, config bf8180, pass 0
PCI: Scanning bus 0001:81
pci 0001:81:00.0: found [1a0b:5331] class 00ff00 header type 00
pci 0001:81:00.0: reg 10 64bit mmio: [0xb8000000-0xb8ffffff]
pci 0001:81:00.0: reg 18 32bit mmio: [0xb9000000-0xb903ffff]
pci 0001:81:00.0: calling pcibios_fixup_resources+0x0/0xec
pci 0001:81:00.0: calling fixup_ppc4xx_pci_bridge+0x0/0x154
pci 0001:81:00.0: disabling ASPM on pre-1.1 PCIe device. You can
enable it with 'pcie_aspm=force'
PCI: Fixups for bus 0001:81
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
Regards,
--
Leon
next prev parent reply other threads:[~2008-11-26 15:25 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 [this message]
2008-11-26 18:26 ` Leon Woestenberg
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=c384c5ea0811260725x3476fa43o9950123948e99acb@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).