From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] 460GT PCIe configuration
Date: Wed, 14 Jan 2009 16:03:18 +0100 [thread overview]
Message-ID: <200901141603.18246.sr@denx.de> (raw)
In-Reply-To: <f608b67d0901121822o1dd8316ei1773e8b9d49fe6c2@mail.gmail.com>
On Tuesday 13 January 2009, vb wrote:
> I am trying to troubleshoot a weird PCIe problem on a PPC460GT based
> target, and it is getting curiouser and curiouser.
>
> There is a tlb overlap I mentioned in an earlier email; on top of that
> there are some things happening in cpu/ppc4xx/4xx_pcie.c which I also
> find hard to understand:
>
> there is a static function pcie_get_base(), which returns a value as in
>
> address = pcie_get_base(hose, devfn)
>
> there are two instances of this, in both cases `address' is never used.
Good catch. pcie_get_base() can be removed. This is probably a remnant from an
older driver version.
> The CONFIG_SYS_PCIE0_XCFGBASE constant (and its counterparts for other
> PCIe ports) is defined and used in the code, and gets a TLB entry
> assigned, but I can't find a place where it is programmed into the CPU
> - how does it know where this section is?!
Again you seem to be correct here. I can't find a place where this area is
programmed. I don't have the time to dig into this right now, so it would be
great if you could work on this a little deeper. I suggest to look at the
Linux 4xx PCI driver (arch/powerpc/sysdev/ppc4xx_pci.c) as reference.
> I have several different targets with different PCIe components, but
> all using the same base CPU subsystem design, and on some of them PCIe
> components misbehave, namely, PCIe memory read transactions fail with
> a machine check after a timeout, even though the PCIe side of things
> is fine (when looking with a protocol analyzer).
Is this all 460EX? Or some other 4xx? What are the PCIe endpoints you are
using? Do you see the same problems on Canyonlands as well?
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-01-14 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 2:22 [U-Boot] 460GT PCIe configuration vb
2009-01-14 15:03 ` Stefan Roese [this message]
2009-01-14 16:42 ` vb
2009-01-14 17:56 ` Stefan Roese
2009-01-14 19:09 ` Stefan Roese
2009-03-10 21:23 ` Leon Woestenberg
2009-03-10 22:13 ` vb
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=200901141603.18246.sr@denx.de \
--to=sr@denx.de \
--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