From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] 460GT PCIe configuration
Date: Wed, 14 Jan 2009 20:09:13 +0100 [thread overview]
Message-ID: <200901142009.13561.sr@denx.de> (raw)
In-Reply-To: <200901141856.05990.sr@denx.de>
On Wednesday 14 January 2009, Stefan Roese wrote:
> On Wednesday 14 January 2009, vb wrote:
> > thank you for confirming my suspicions and for your suggestion, I will
> > compare notes with the Linux version (should have thought about this
> > earlier). But I also was under impression that Linux does not touch
> > some parts of PCI configuration, as the memory map is set by u-boot
> > and used by Linux. Or does linux use the addresses from the device
> > tree to reprogram the PCIe subsystem?
>
> Correct. Linux (re-)configures the 4xx PCI(e) controller completely.
> Everything should be overwritten by Linux.
BTW: Do you see the same problems (PCIe memory read timeout) under Linux?
If PCIe works on Glacier and fails on your custom board it may be a hardware
related problem on your board (either board routing or endpoint etc). Are you
sure that your FPGA based PCIe endpoint is working correctly? Can you "plug"
a standard PCIe endpoint in your custom hardware?
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 19:09 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
2009-01-14 16:42 ` vb
2009-01-14 17:56 ` Stefan Roese
2009-01-14 19:09 ` Stefan Roese [this message]
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=200901142009.13561.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