From: Dave Littell <littelld@verizon.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC440Epx Sequoia Flash-based size limitation?
Date: Fri, 14 Mar 2008 21:51:10 -0500 [thread overview]
Message-ID: <47DB399E.1080003@verizon.net> (raw)
In-Reply-To: <200803140722.18084.sr@denx.de>
Stefan Roese wrote:
[deletia]
>
> Another idea comes to my mind here. It's on my todo list to implement a
> workaround for the 440EPx errata CHIP 11:
>
>> CHIP_11: End of memory range area restricted access.
[deletia]
>
> One simple idea is to add :
>
> #define CONFIG_PRAM 1
>
> to your U-Boot config file.
>
This seems to have fixed the problem, although I had to juggle the order
to get the PRAM trimmed out before the LOGBUFFER memory. I later went
back and trimmed only the AMCC-recommended 256 bytes and this also seems
to resolved the problem.
Odd timing that CHIP_11 chose to bite, eh? Thanks very much for the help.
Dave
next prev parent reply other threads:[~2008-03-15 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 1:33 [U-Boot-Users] PPC440Epx Sequoia Flash-based size limitation? Dave Littell
2008-03-14 6:22 ` Stefan Roese
2008-03-15 2:38 ` Dave Littell
2008-03-15 2:51 ` Dave Littell [this message]
2008-03-14 7:13 ` Niklaus Giger
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=47DB399E.1080003@verizon.net \
--to=littelld@verizon.net \
--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