From: Scott Wood <scottwood@freescale.com>
To: Alan Bennett <embedded@akb.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: kernel update on mpc8248 muram definition?
Date: Thu, 15 Nov 2007 11:30:49 -0600 [thread overview]
Message-ID: <473C8249.8090206@freescale.com> (raw)
In-Reply-To: <bfa0697f0711150743t440298cfsbce6f10b6fa39d73@mail.gmail.com>
Alan Bennett wrote:
> While working on i2c support, I've decided to update to a new kernel.
> In the process of doing this, I'm not sure I've properly configured the
> MURAM node to my device tree (i.e. serial is broken again).
You haven't -- you copied muram/data/reg from some other tree, rather
than from resource 2 of cpm/reg in your old tree.
> Also, does
> this, in any way, change the way I offset the early debug transmit
> descriptor address?
No.
> muram@0 {
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0 0 10000>;
>
> data@0 {
> compatible = "fsl,cpm-muram-data";
> reg = <0 2000 9800 800>;
> };
> };
muram/data/reg should be <80 1f80 9800 800> for your board.
-Scott
prev parent reply other threads:[~2007-11-15 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 15:43 kernel update on mpc8248 muram definition? Alan Bennett
2007-11-15 17:30 ` Scott Wood [this message]
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=473C8249.8090206@freescale.com \
--to=scottwood@freescale.com \
--cc=embedded@akb.net \
--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 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).