linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Steven A. Falco" <sfalco@harris.com>
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: Wed, 07 Jan 2009 10:13:43 +1100	[thread overview]
Message-ID: <1231283623.14860.32.camel@pasglop> (raw)
In-Reply-To: <4963D989.6090909@harris.com>


> 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.

Nah, I think 256M is ridiculously small :-) I think the .dts for that
board should be changed, there is plenty of physical address space
available on those chips since it's using a 36-bit bus.

Cheers,
Ben.
 

  reply	other threads:[~2009-01-06 23:14 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
2009-01-06 23:13               ` Benjamin Herrenschmidt [this message]
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=1231283623.14860.32.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfalco@harris.com \
    --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).