From: Larry Johnson <lrj@acm.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ppc4xx: Don't use last 256 bytes of SDRAM, workaround for 440EPx CHIP 11 errata
Date: Thu, 27 Mar 2008 13:36:36 -0500 [thread overview]
Message-ID: <47EBE934.5010706@acm.org> (raw)
In-Reply-To: <200803270721.20326.sr@denx.de>
Stefan Roese wrote:
> On Thursday 27 March 2008, Larry Johnson wrote:
>> Yes, we normally use ECC modules in our testing. I've been looking at a
>> patch for "initdram()" Denali SPD, but I've been waiting to see how your
>> "CFG_MEM_TOP_HIDE" patch would turn out.
>>
>> As things stand now, can I assume that boards using the Denali SPD will
>> also define "CFG_MEM_TOP_HIDE", and therefore initdram() should continue
>> to return the full size of the memory?
>
> Correct.
>
>> The only place that the last 256 bytes of memory are touched is when
>> "dflush()" is called to zero the SDRAM.
>
> To be more specific, in the dcbz_area() call.
>
>> This does not cause a Machine
>> Check interrupt. I am guessing that all the writes from "dflush()" are
>> aligned, and therefore there are no burst that access beyond the end of
>> of the SDRAM memory space. If so, then my inclination is not to change
>> this part of the code. Does this make sense?
>
> I recommend to change it this way:
>
> /* Zero the memory */
> debug("Zeroing SDRAM...");
> - dcbz_area(CFG_SDRAM_BASE, dram_size);
> + dcbz_area(CFG_SDRAM_BASE, dram_size - CFG_MEM_TOP_HIDE);
> dflush();
>
> And perhaps put something like:
>
> #ifndef CFG_MEM_TOP_HIDE
> #error "Please define CFG_MEM_TOP_HIDE (see README) in your board config
> file!"
> #endif
>
> at the top of the file. What do you think?
>
> Best regards,
> Stefan
That sound fine, I'll try to get a patch out soon.
Best regards,
Larry
prev parent reply other threads:[~2008-03-27 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 9:46 [U-Boot-Users] [PATCH] ppc4xx: Don't use last 256 bytes of SDRAM, workaround for 440EPx CHIP 11 errata Stefan Roese
2008-03-20 10:03 ` Wolfgang Denk
2008-03-20 10:29 ` Stefan Roese
2008-03-20 11:16 ` Wolfgang Denk
2008-03-20 12:55 ` Kumar Gala
2008-03-20 13:57 ` Stefan Roese
2008-03-20 11:50 ` Dave Littell
2008-03-20 14:11 ` Stefan Roese
2008-03-20 16:06 ` Larry Johnson
2008-03-20 21:12 ` Stefan Roese
2008-03-27 2:50 ` Larry Johnson
2008-03-27 6:21 ` Stefan Roese
2008-03-27 18:36 ` Larry Johnson [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=47EBE934.5010706@acm.org \
--to=lrj@acm.org \
--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