From: Scott Wood <scottwood@freescale.com>
To: James Black <jblack547@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: muram in device tree for mpc8250 in arch/powerpc
Date: Thu, 20 Mar 2008 13:20:13 -0500 [thread overview]
Message-ID: <47E2AADD.6090101@freescale.com> (raw)
In-Reply-To: <b77025b40803201102w200dde6fuc4235d9a3cb8b0dd@mail.gmail.com>
James Black wrote:
> Zone PFN ranges:
> DMA 0 -> 16384
> Normal 16384 -> 16384
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0 -> 16384
> Unable to handle kernel paging request for data at address 0xe001a000
> Faulting instruction address: 0xc00e1a6c
What function is 0xc00e1a6c in?
Is it possible that you have an SMC device initialized by your firmware
that is corrupting parameter RAM?
> muram@0 {
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0 0 10000>;
>
> data@0 {
> compatible = "fsl,cpm-muram-data";
> reg = <0 4000 8000 1000 B000 1000>;
You can't use all of 0x8000-0x8fff; there is device parameter RAM in
there. If you can figure out the portions that aren't in use, you can
use those, but I wouldn't bother unless you really need the extra muram.
-Scott
next prev parent reply other threads:[~2008-03-20 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 17:06 muram in device tree for mpc8250 in arch/powerpc James Black
2008-03-19 17:40 ` Scott Wood
[not found] ` <b77025b40803191107x2f9a7884n9b7f062fcf45370@mail.gmail.com>
2008-03-20 18:02 ` James Black
2008-03-20 18:20 ` Scott Wood [this message]
2008-03-20 23:02 ` James Black
2008-03-21 16:18 ` Scott Wood
2008-03-21 20:14 ` James Black
2008-03-21 20:34 ` Scott Wood
2008-03-21 21:35 ` James Black
2008-03-24 16:52 ` Scott Wood
2008-03-24 21:45 ` James Black
2008-03-24 21:53 ` Scott Wood
2008-03-24 21:59 ` James Black
2008-03-24 22:05 ` Scott Wood
2008-03-24 22:09 ` James Black
2008-03-24 22:28 ` James Black
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=47E2AADD.6090101@freescale.com \
--to=scottwood@freescale.com \
--cc=jblack547@gmail.com \
--cc=linuxppc-embedded@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 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).