linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Russell McGuire" <rmcguire@uwbt.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: MPC8360E Startup - CFG_INIT_RAM
Date: Mon, 11 Dec 2006 15:05:42 -0800	[thread overview]
Message-ID: <000801c71d78$e28cae60$6405a8c0@absolut> (raw)
In-Reply-To: <mailman.1727.1165862180.2346.linuxppc-embedded@ozlabs.org>

Anybody,

I am porting U-boot to a new custom MPC8360E based board.
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
interested I have the new 83xx header files to support Rev 2.0 CPU's, only
about 10 extra lines>

My question lies with what value to place in the CFG_INIT_RAM address. 

I see that the example board has this mapped to dcache? I think... If so how
does one calculate what address dcache sits at?

Or would I be able to use the internal IMMR space multi-user QE ram?
My question is without dissecting the assembly at startup, does the IMMR get
remapped before or after the CFG_INIT_RAM is used.

The board has no external memory other than DDR, so I am going to have to
use something in the CPU.

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.

-Russ

       reply	other threads:[~2006-12-11 23:12 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 ` Russell McGuire [this message]
2006-12-12  1:17   ` MPC8360E Startup - CFG_INIT_RAM Wolfgang Denk

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='000801c71d78$e28cae60$6405a8c0@absolut' \
    --to=rmcguire@uwbt.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).