public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] PPC40x: Rework CFG_INIT_DCACHE_CS Block to Avoid Machine Checks
Date: Sun, 18 May 2008 22:38:02 +0200	[thread overview]
Message-ID: <20080518203802.8A8642476E@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 16 May 2008 14:35:11 PDT." <1210973711-1855-1-git-send-email-gerickson@nuovations.com>

In message <1210973711-1855-1-git-send-email-gerickson@nuovations.com> you wrote:
>
...
> cpu/ppc4xx/start.S:
>   Reworked code to handle the primordial stack and data area initialization when CFG_INIT_DCACHE_CS is asserted.
...
> -	 * Boards like the Kilauea (405EX) don't have OCM and can't use
> -	 * DCache for init-ram. So setup stack here directly after the
> -	 * SDRAM is initialized.
> +	 * For boards that don't have OCM and can't use the data cache
> +	 * for their primordial stack, setup stack here directly after the
> +	 * SDRAM is initialized in ext_bus_cntlr_init.

Was there ever a useful explanation given why these boards should not
be able to use DC as initial RAM?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
[Braddock:] Mr. Churchill, you are drunk.
[Churchill:] And you madam, are ugly.  But I shall be sober tomorrow.

  reply	other threads:[~2008-05-18 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 21:35 [U-Boot-Users] [PATCH] PPC40x: Rework CFG_INIT_DCACHE_CS Block to Avoid Machine Checks Grant Erickson
2008-05-18 20:38 ` Wolfgang Denk [this message]
2008-05-18 20:56   ` Grant Erickson
2008-05-18 21:23     ` Wolfgang Denk
2008-05-18 21:35       ` Grant Erickson

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=20080518203802.8A8642476E@gemini.denx.de \
    --to=wd@denx.de \
    --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