From: Wolfgang Denk <wd@denx.de>
To: "Russell McGuire" <rmcguire@uwbt.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8360E Startup - CFG_INIT_RAM
Date: Tue, 12 Dec 2006 02:17:59 +0100 [thread overview]
Message-ID: <20061212011759.D6839353BC7@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 11 Dec 2006 15:05:42 PST." <000801c71d78$e28cae60$6405a8c0@absolut>
Dear Russel,
in message <000801c71d78$e28cae60$6405a8c0@absolut> you wrote:
>
> I am porting U-boot to a new custom MPC8360E based board.
You're off topic here. You should post such things on the
U-Bootmailing list instead.
> I have downloaded the GIT U-boot tree, and see that DENX has made an example
> for the MPC8360E-MDS board, and it is an excellent start. <If anyone is
No, the MPC8360EMDS was not done by us, but by Dave Liu; see the
MAINTAINERS file for details.
> My question lies with what value to place in the CFG_INIT_RAM address.
See the "Note:" in the README...
> Due to the massive amount of flash on our board <128M>, I cannot leave the
> .text space at 0xFE00000. So I would prefer the IMMR be located at
> 0xF0000000 and flash be at 0xE0000000, this would leave room for future
> expansion <maybe up to 256M>, if this is even related to early startup.
Even if you boot high you can easily adjust for different flash
sizes. This hase been done with other boards before. Just look around
a bit. Of course everything is much easier if you boot low.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A conservative is a man with two perfectly good legs who has never
learned to walk. - Franklin D. Roosevelt
prev parent reply other threads:[~2006-12-12 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1727.1165862180.2346.linuxppc-embedded@ozlabs.org>
2006-12-11 23:05 ` MPC8360E Startup - CFG_INIT_RAM Russell McGuire
2006-12-12 1:17 ` Wolfgang Denk [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=20061212011759.D6839353BC7@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rmcguire@uwbt.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 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).