From: "Steven A. Falco" <sfalco@harris.com>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: Wolfgang Denk <wd@denx.de>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [QUESTION] 440EPx with PCI to PCIe bridge error
Date: Tue, 06 Jan 2009 16:38:48 -0500 [thread overview]
Message-ID: <4963CF68.3040808@harris.com> (raw)
In-Reply-To: <4963C1DE.6020007@harris.com>
Steven A. Falco wrote:
> Benjamin Herrenschmidt wrote:
>>> Here is a complete startup log, with debug turned on as you requested.
>>> This is still against 2.6.27.9, as it will take me a little time to
>>> build 2.6.28. Hopefully, this log will be useful in the meantime.
>> Can you add "debug" to your kernel command line option or send the
>> output of the "dmesg" command please ?
>>
Time to answer my own questions. U-boot is missing a setting for
CFG_PCI_MEMSIZE in the sequoia.h file. Four 256MB TLBs are reserved,
but since CFG_PCI_MEMSIZE is not set, the size defaults to 256MB,
rather than the 1GB that is allocated.
So, I added:
#define CFG_PCI_MEMSIZE 0x40000000 /* 1GB */
to sequoia.h. Now U-boot uses all four TLBs, and that error message
goes away.
But this has no effect on Linux. So, I also changed the sequoia.dts
to make the outbound range larger, and now Linux is happy too. I now
have ranges for the device:
# cat 0000:01:00.0/resource
0x0000000190000000 0x000000019007ffff 0x0000000000020200
0x0000000180000000 0x000000018fffffff 0x0000000000020200
Steve
next prev parent reply other threads:[~2009-01-06 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:09 [QUESTION] 440EPx with PCI to PCIe bridge error Steven A. Falco
2009-01-05 21:18 ` Benjamin Herrenschmidt
2009-01-05 21:35 ` Steven A. Falco
2009-01-06 6:33 ` Benjamin Herrenschmidt
2009-01-06 14:44 ` Steven A. Falco
2009-01-06 18:33 ` Steven A. Falco
2009-01-06 20:41 ` Steven A. Falco
2009-01-06 21:38 ` Steven A. Falco [this message]
2009-01-06 22:02 ` Benjamin Herrenschmidt
2009-01-06 22:22 ` Steven A. Falco
2009-01-06 23:13 ` Benjamin Herrenschmidt
2009-01-07 14:45 ` Steven A. Falco
2009-01-07 20:52 ` 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=4963CF68.3040808@harris.com \
--to=sfalco@harris.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@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).