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: Fri, 28 Nov 2008 11:54:18 +0100	[thread overview]
Message-ID: <c384c5ea0811280254y428299a4yd92c1c244bd2482@mail.gmail.com> (raw)
In-Reply-To: <c384c5ea0811261026y73679a16tfa29a33f3e780954@mail.gmail.com>

Hello all,

On Wed, Nov 26, 2008 at 7:26 PM, Leon Woestenberg
<leon.woestenberg@gmail.com> wrote:
> 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
>>

Progress on this issue:

I found out that re-programming the end point FPGA again *just* after
*uboot* read it, and before Linux kernel has started, makes the end
point appear properly.

Either u-boot leaves the end point in bad state, or the root complex
reset also requires an end point reset. (or a third option I could not
think of yet).

I'll pick this up on ppc and u-boot mailing list with new info,
especially with the ppc4xx maintainers.

Consider this thread closed.

Thanks for ignoring my ranting :-)

Regards,
-- 
Leon

  reply	other threads:[~2008-11-28 10:54 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
2008-11-28 10:54     ` Leon Woestenberg [this message]
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=c384c5ea0811280254y428299a4yd92c1c244bd2482@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).