From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sheevaplug: correct SDRAM address control register value
Date: Sun, 18 Oct 2009 15:11:11 -0500 [thread overview]
Message-ID: <4ADB765F.3070608@windriver.com> (raw)
In-Reply-To: <1255712955-27760-1-git-send-email-mark.asselstine@windriver.com>
Mark Asselstine wrote:
> The SheevaPlug DevKit is shipped with 4x8 by 1Gb DDR devices in
> two banks for a total of 512MB of RAM. Based on this configuration
> the existing values for SDRAM address control register are incorrect
> and result in random kernel oops as memory is incorrectly accessed
> (while for example extracting a large tarball such as a rootfs).
> Based on the hardware configuration along with the supporting
> documentation from Marvell these are the correct values, as
> well this change mimics values previously used in Marvell's own
> u-boot git tree for the SheevaPlug.
>
> Other variants of the hardware such as the PogoPlug and TonidoPlug
> may have different memory configurations but to properly support
> those additional board directories should be maintained or a better
> system to support other kwb*.cfg is needed.
>
> Tested on SheevaPlug DevKit.
Mark and Prafulla
If this configuration is different from the what is already in use,
then the kwbimage.cfg can not be overwritten.
Reviewing the kwbimage.cfg file shows a lot of magic.
What would be a good way to generalize this ?
More versions of the file ?
Variable support in the file?
Other ideas ?
Tom
>
> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> ---
> board/Marvell/sheevaplug/kwbimage.cfg | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/board/Marvell/sheevaplug/kwbimage.cfg b/board/Marvell/sheevaplug/kwbimage.cfg
> index 6c47d62..61be8c2 100644
> --- a/board/Marvell/sheevaplug/kwbimage.cfg
> +++ b/board/Marvell/sheevaplug/kwbimage.cfg
> @@ -74,11 +74,11 @@ DATA 0xFFD0140C 0x00000a33 # DDR Timing (High)
> # bit12-11: TW2W
> # bit31-13: zero required
>
> -DATA 0xFFD01410 0x00000099 # DDR Address Control
> -# bit1-0: 01, Cs0width=x16
> -# bit3-2: 10, Cs0size=512Mb
> -# bit5-4: 01, Cs1width=x16
> -# bit7-6: 10, Cs1size=512Mb
> +DATA 0xFFD01410 0x000000cc # DDR Address Control
> +# bit1-0: 00, Cs0width=reserved
> +# bit3-2: 11, Cs0size=1Gb
> +# bit5-4: 00, Cs1width=reserved
> +# bit7-6: 11, Cs1size=1Gb
> # bit9-8: 00, Cs2width=nonexistent
> # bit11-10: 00, Cs2size =nonexistent
> # bit13-12: 00, Cs3width=nonexistent
next prev parent reply other threads:[~2009-10-18 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 17:09 [U-Boot] [PATCH] sheevaplug: correct SDRAM address control register value Mark Asselstine
2009-10-18 20:11 ` Tom [this message]
2009-10-19 0:26 ` Mark Asselstine
2009-10-19 6:32 ` Simon Kagstrom
2009-10-19 13:19 ` [U-Boot] [PATCH V2] " Mark Asselstine
2009-10-27 9:45 ` Prafulla Wadaskar
[not found] <73173D32E9439E4ABB5151606C3E19E202F1D3730E@SC-VEXCH1.marvell.com>
2009-11-01 23:17 ` [U-Boot] [PATCH] " Tom
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=4ADB765F.3070608@windriver.com \
--to=tom.rix@windriver.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