From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: u-boot@lists.denx.de, Linux PPC <linuxppc-dev@ozlabs.org>
Subject: Re: ppc4xx: u-boot sees PCIe endpoint, linux does not.
Date: Mon, 1 Dec 2008 20:19:38 +0100 [thread overview]
Message-ID: <c384c5ea0812011119o97adf68l1546c96d5a6696a8@mail.gmail.com> (raw)
In-Reply-To: <1228119152.7356.118.camel@pasglop>
Hello all,
On Mon, Dec 1, 2008 at 9:12 AM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Fri, 2008-11-28 at 13:50 +0100, Leon Woestenberg wrote:
>>
>> AMCC PPC460EX canyonlands board with an FPGA PCIe end point:
>>
>> u-boot sees the end point, but Linux does not:
>>
>> U-Boot 1.3.3-00249-ga524e11 (Jun 30 2008 - 16:05:51)
>> CPU: AMCC PowerPC 460EX Rev. A at 800 MHz (PLB=200, OPB=100, EBC=100 MHz)
>> <...>
>> Board: Canyonlands - AMCC PPC460EX Evaluation Board, 2*PCIe, Rev. 16
>> <...>
>> PCIE1: successfully set as root-complex
>> 02 00 2071 2071 00ff 00
>>
>> Now, if I re-program the end-point FPGA during the u-boot boot
>> time-out, Linux will recognize the end-point.
>>
> It's possible that either the reset in between goes bonkers or something
> else causes your FPGA to stop responding. It looks like a programming
> problem with the FPGA to me.
>
I have verified that the end point does not receive any kind of reset.
Also, this problem only happens on the Canyonlands board; on x86 and
powerpc MPC8315E it remains properly working after soft/hard resets,
u-boot init etc.
Could it be u-boot overwrites a too large payload into the config
space or something similar, which makes subsequent accesses fail?
Regards,
--
Leon
next prev parent reply other threads:[~2008-12-01 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 12:50 ppc4xx: u-boot sees PCIe endpoint, linux does not Leon Woestenberg
2008-12-01 8:12 ` Benjamin Herrenschmidt
2008-12-01 19:19 ` Leon Woestenberg [this message]
2008-12-01 19:46 ` [U-Boot] " Stefan Roese
2009-03-09 14:23 ` Leon Woestenberg
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=c384c5ea0812011119o97adf68l1546c96d5a6696a8@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=u-boot@lists.denx.de \
/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).