From: "Steven A. Falco" <sfalco@harris.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Wolfgang Denk <wd@denx.de>
Subject: Re: [QUESTION] 440EPx with PCI to PCIe bridge error
Date: Tue, 06 Jan 2009 17:22:01 -0500 [thread overview]
Message-ID: <4963D989.6090909@harris.com> (raw)
In-Reply-To: <1231279340.14860.31.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Tue, 2009-01-06 at 16:38 -0500, Steven A. Falco wrote:
>> 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
>
> So your problem is fixed ? I didn't have a chance yet to look at your
> logs, but it could just have been that you didn't have enough space
> allocated to PCI for your card...
>
> Cheers,
> Ben.
That appears to be the problem. Apparently the PCI/PCIe bridge requests
in excess of 256 MB of space, but the default in the sequoia .dts file is
"only" for 256 MB, so the request fails.
I'm not sure if this should be changed in the mainline. This card works
out of the box when used with a generic x86 PC, but not when used with
a sequoia. But, maybe it's just me climbing the PPC learning curve.
Steve
next prev parent reply other threads:[~2009-01-06 22:22 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
2009-01-06 22:02 ` Benjamin Herrenschmidt
2009-01-06 22:22 ` Steven A. Falco [this message]
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=4963D989.6090909@harris.com \
--to=sfalco@harris.com \
--cc=benh@kernel.crashing.org \
--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).