From: Scott Wood <scottwood@freescale.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: PCI on 834x
Date: Wed, 24 Feb 2010 13:31:45 -0600 [thread overview]
Message-ID: <4B857EA1.6030605@freescale.com> (raw)
In-Reply-To: <4B857AA8.9000208@mlbassoc.com>
Gary Thomas wrote:
> On 02/24/2010 11:48 AM, Scott Wood wrote:
>> Gary Thomas wrote:
>>> Does anyone have experience setting up the PCI controller on
>>> the MPC8349? I have it running fine when my system has 128MB
>>> or less of main memory, but when I have 256MB or more, it all
>>> falls apart :-(
>>>
>>> Any indication of the pertinent settings would be appreciated.
>>
>> Check the inbound PCI translation registers, especially PIWARn.
>
> Yes, I set it to 256MB (the size of RAM).
> I also set PCI_AR0 to a 512MB window (when it's set to 256, I
> get address [segmentation violation] errors when accessing my
> devices that end up at the high end of the logical address space)
> Finally, I set POCMR0 to a 512MB window (corresponding to PCI_AR0)
I don't see what the outbound window size has to do with RAM size... are
there any other differences between the 128MiB and 256MiB setups? Same
exact software? What happens if you take the 256MiB setup and restrict
the kernel to using the lower 128MiB ("mem=128M" on the kernel
bootargs), with no other changes? What happens if you use a 512MiB
outbound window on the 128MiB setup?
Is this behavior consistent across multiple boards (i.e. could there be
a hardware problem)?
Are there any errors indicated in the device, the PCI controller, the
arbiter, etc?
-Scott
next prev parent reply other threads:[~2010-02-24 19:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:49 PCI on 834x Gary Thomas
2010-02-24 18:48 ` Scott Wood
2010-02-24 19:14 ` Gary Thomas
2010-02-24 19:31 ` Scott Wood [this message]
2010-02-24 19:47 ` Gary Thomas
2010-02-24 20:26 ` Scott Wood
2010-02-24 20:51 ` Anton Vorontsov
2010-02-24 22:14 ` Gary Thomas
2010-02-24 22:25 ` Kumar Gala
2010-02-24 23:08 ` Gary Thomas
2010-02-25 14:25 ` Gary Thomas
2010-02-25 20:49 ` Benjamin Herrenschmidt
2010-02-25 21:03 ` Scott Wood
2010-02-25 21:11 ` Gary Thomas
2010-02-25 21:24 ` Scott Wood
2010-02-25 23:43 ` Gary Thomas
2010-02-25 23:49 ` Scott Wood
2010-02-25 22:36 ` 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=4B857EA1.6030605@freescale.com \
--to=scottwood@freescale.com \
--cc=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.