From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Canyonlands-NAND-boot: Support 2 Crucial 512MByte SODIMM's
Date: Thu, 30 Jul 2009 14:12:40 +0200 [thread overview]
Message-ID: <200907301412.40818.sr@denx.de> (raw)
In-Reply-To: <1248877554-25698-1-git-send-email-sr@denx.de>
On Wednesday 29 July 2009 16:25:54 Stefan Roese wrote:
> Some Canyonlands boards are equipped with different SODIMM's. This is no
> problem with the "normal" NOR booting Canyonlands U-Boot, since it
> automatically detects the SODIMM's via SPD data and correctly configures
> them. But the NAND booting version is different. Here we only have 4k
> of image size to completely setup the hardware, including DDR2 setup.
> So we need to use a fixed DDR2 setup here. This doesn't work for different
> SODIMM's right now.
>
> Currently only this Crucial SODIMM is support:
> CT6464AC667.8FB (dual ranked)
>
> Now some boards are shipped with this SODIMM:
> CT6464AC667.4FE (single ranked)
>
> This patch now supports both SODIMM's by configuring first for the dual
> ranked DIMM. A quick shows, if this module is really installed. If this
> test fails, the DDR2 controller is re-configured for the single
> ranked SODIMM.
>
> Tested with those SODIMM's:
>
> CT6464AC667.8FB (dual ranked)
> CT6464AC667.4FE (single ranked)
>
> Signed-off-by: Stefan Roese <sr@denx.de>
Applied to u-boot-ppc4xx/master. Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2009-07-30 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 14:25 [U-Boot] [PATCH] ppc4xx: Canyonlands-NAND-boot: Support 2 Crucial 512MByte SODIMM's Stefan Roese
2009-07-30 12:12 ` Stefan Roese [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=200907301412.40818.sr@denx.de \
--to=sr@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