All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Memory size detection on P1011
Date: Thu, 05 May 2011 22:14:55 +0300	[thread overview]
Message-ID: <4DC2F72F.2050009@embedded-sol.com> (raw)
In-Reply-To: <20110505182440.867B0D60EB7@gemini.denx.de>

Hi Wolfgang,

On 05/05/2011 09:24 PM, Wolfgang Denk wrote:
> Dear York Sun,
>
> In message<1304602168.21927.16.camel@oslab-l1>  you wrote:
>> I don't think get_ram_size works for your case. If you want to test the
> You are wrong. We have been doing this for a long time on many boards
> with similar properties.
>
>> DDR to find the correct size, you have to initialize the DDR first. But
>> you cannot do this correctly without knowing the number of banks. You
>> may be able to blindly set the bank number and test the DDR to catch the
> Incorrect number of banks will give different results than correct
> number, so try both. The correct configuration is simply the one that
> gives the maximum total memory size.

I'm trying to do that, but get the same wrong memory size
in both cases. On the other hand, if I program the correct
number of banks from the start, get_ram_size() returns the
correct size in both cases.

The closest example of using get_ram_size() I've found is
for MPC8548 TQM boards. But all these boards have 4-bank
memory devices, so I'm sure my case was tested. Don't you
think there can be a problem with reprogramming bank number
in this particular DDR controller ?

Felix.

  reply	other threads:[~2011-05-05 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 13:17 [U-Boot] Memory size detection on P1011 Felix Radensky
2011-05-05 13:29 ` York Sun
2011-05-05 14:05   ` Felix Radensky
2011-05-05 18:24   ` Wolfgang Denk
2011-05-05 19:14     ` Felix Radensky [this message]
2011-05-05 19:43       ` Wolfgang Denk
2011-05-06  6:11         ` Felix Radensky

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=4DC2F72F.2050009@embedded-sol.com \
    --to=felix@embedded-sol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.