From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm/omap3: limit chip select iteration based on board config
Date: Tue, 3 Jan 2012 07:31:21 -0700 [thread overview]
Message-ID: <4F031139.9020502@ti.com> (raw)
In-Reply-To: <1324582093-27718-1-git-send-email-marathon96@gmail.com>
On 12/22/2011 12:28 PM, Grant Erickson wrote:
> Only attempt to configure and add DRAM at chip select 1 if the board has configured more than one bank of DRAM.
>
> This prevents boards that have CONFIG_NR_DRAM_BANKS set to 1 from getting an incorrect DRAM size.
>
> Signed-off-by: Grant Erickson <marathon96@gmail.com>
> Cc: Tom Rini <trini@ti.com>
OK, what problem (and on what board) are you seeing? Many boards only
have CS0 populated with DRAM but when we try and configure CS1 the
mem_ok() call fails and we don't try and use it, so we don't get a wrong
amount of memory. Thanks!
--
Tom
next prev parent reply other threads:[~2012-01-03 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 19:28 [U-Boot] [PATCH] arm/omap3: limit chip select iteration based on board config Grant Erickson
2012-01-03 14:31 ` Tom Rini [this message]
[not found] ` <4f0475fc.a24de70a.57f2.540d@mx.google.com>
2012-01-04 16:10 ` Grant Erickson
2012-01-04 16:14 ` Tom Rini
2012-01-04 16:28 ` Grant Erickson
2012-01-05 8:44 ` Wolfgang Denk
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=4F031139.9020502@ti.com \
--to=trini@ti.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