public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] set up stack before board_init_f() on ppc440 core?
Date: Fri, 25 Feb 2005 14:56:17 -0800	[thread overview]
Message-ID: <c3d0340b05022514561d473407@mail.gmail.com> (raw)
In-Reply-To: <20050225214603.27978C1430@atlas.denx.de>

Dear Wolfgang,

> Which part of section "Initial Stack,  Global  Data"  in  the  README
> don't you understand?

Thanks for pointing out the section. I didn't read it through before. :(

> > stack in DCACHE (Walnut 405 is an example). But the CFG_INIT_RAM_ADDR
> > is 0x40000000, which is inside SDRAM. Why was it commented that the
> 
> No, this is not inside SDRAM. There is no board (yet) with  1  GB  of
> RAM.

Well, "inside SDRAM" is what is commented on WALNUT.h. Now I
understand the value of CFG_INIT_RAM_ADDR is better not to interfere
with the system design.

> In short: cache is like normal memory, just very fast (which does not
> play a role here). We just have to make sure that no cache  fills  or
> cache  flushes  will  be done (at least not for that part of the data
> cache which is being used for the initial stack).

I don't see any caches are in a system memory mapping. Then I thought
it could be only accessed by those cache specific instructions, like
dcread. That's my misunderstanding.

Thanks,
-Shawn.

  reply	other threads:[~2005-02-25 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 18:42 [U-Boot-Users] set up stack before board_init_f() on ppc440 core? Shawn Jin
2005-02-25 21:45 ` Wolfgang Denk
2005-02-25 22:56   ` Shawn Jin [this message]
2005-02-26 16:23     ` Grant Likely
2005-03-04  3:29       ` Shawn Jin

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=c3d0340b05022514561d473407@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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