From: Gary Thomas <gary@mlbassoc.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: PCI on 834x
Date: Wed, 24 Feb 2010 12:14:48 -0700 [thread overview]
Message-ID: <4B857AA8.9000208@mlbassoc.com> (raw)
In-Reply-To: <4B85746F.3020200@freescale.com>
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)
In this configuration, my device doesn't seem to be able to
access RAM. If PIWAR1 is too small, the device just hangs.
=============================== 128MB setup =========================
PIWAR1 = 0xA0055000 | (27-1)
POCMR0 = 0x800F0000
PCIAR0 = 0x80000000 | (28-1)
00:00.0 Power PC: Unknown device 1957:0082 (rev 30)
Flags: bus master, 66MHz, fast devsel, latency 0
Memory at cc000000 (32-bit, non-prefetchable) [size=1M]
Memory at c0000000 (64-bit, prefetchable) [size=128M]
Memory at <unassigned> (64-bit, non-prefetchable)
Capabilities: [48] #06 [0000]
00:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
Subsystem: Silicon Image, Inc. SiI 3512 SATALink Controller
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 22
I/O ports at 1000 [size=8]
I/O ports at 1008 [size=4]
I/O ports at 1010 [size=8]
I/O ports at 1018 [size=4]
I/O ports at 1020 [size=16]
Memory at cc180000 (32-bit, non-prefetchable) [size=512]
[virtual] Expansion ROM at cc100000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
00:0c.0 Display controller: Fujitsu Limited. Unknown device 2019 (rev 01)
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at c8000000 (32-bit, non-prefetchable) [size=64M]
=====================================================================
=============================== 256MB setup =========================
PIWAR1 = 0xA0055000 | (28-1)
POCMR0 = 0x800E0000
PCIAR0 = 0x80000000 | (29-1)
00:00.0 Power PC: Unknown device 1957:0082 (rev 30)
Flags: bus master, 66MHz, fast devsel, latency 0
Memory at d4000000 (32-bit, non-prefetchable) [size=1M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at <unassigned> (64-bit, non-prefetchable)
Capabilities: [48] #06 [0000]
00:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
Subsystem: Silicon Image, Inc. SiI 3512 SATALink Controller
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 22
I/O ports at 1000 [size=8]
I/O ports at 1008 [size=4]
I/O ports at 1010 [size=8]
I/O ports at 1018 [size=4]
I/O ports at 1020 [size=16]
Memory at d4180000 (32-bit, non-prefetchable) [size=512]
[virtual] Expansion ROM at d4100000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
00:0c.0 Display controller: Fujitsu Limited. Unknown device 2019 (rev 01)
Flags: bus master, medium devsel, latency 0, IRQ 19
[virtual] Memory at d0000000 (32-bit, non-prefetchable) [size=64M]
=====================================================================
Any ideas what I might be missing?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-02-24 19:14 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 [this message]
2010-02-24 19:31 ` Scott Wood
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=4B857AA8.9000208@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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.