From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [RFC] memsize.c: adapt get_ram_size() for address spaces >32 bit
Date: Thu, 27 May 2010 16:05:20 -0500 [thread overview]
Message-ID: <4BFEDE90.6070802@freescale.com> (raw)
In-Reply-To: <20100527205755.446C4EAC238@gemini.denx.de>
Wolfgang Denk wrote:
> The systems I know are the opposite - initially they map more memory
> than they support, then they determine the real size, then they
> adjust the mapping to the real size.
But we don't ever do that, at least not on systems that use SPD. We query
the DIMMs directly via SPD and calculate how much memory is in the system.
Most of our boards support both SPD and "fixed" DDR programming. In fixed
mode, the actual values to be programmed in the controller are hard-coded in
the board header file, like this:
#define CONFIG_SYS_DDR_CS0_BNDS 0x0000003F
#define CONFIG_SYS_DDR_CS1_BNDS 0x00000000
#define CONFIG_SYS_DDR_CS0_CONFIG 0x80014202
#define CONFIG_SYS_DDR_CS1_CONFIG 0x00000000
...
So in this case, as long as there's <= 2GB of DDR expected, then
get_ram_size() can work.
But on the P1022DS, I don't support fixed DDR mode. Only SPD is supported,
so I have no idea at compile-time how much memory is in the system. That's
why I don't think calling get_ram_size() is appropriate for the P1022DS board.
--
Timur Tabi
Linux kernel developer@Freescale
next prev parent reply other threads:[~2010-05-27 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 18:11 [U-Boot] [PATCH] [RFC] memsize.c: adapt get_ram_size() for address spaces >32 bit Wolfgang Denk
2010-05-27 18:16 ` [U-Boot] [PATCH v2] " Wolfgang Denk
2010-05-27 19:46 ` Scott Wood
2010-05-27 19:57 ` Wolfgang Denk
2010-05-27 20:00 ` Scott Wood
2010-05-27 20:53 ` Wolfgang Denk
2010-05-27 18:23 ` [U-Boot] [PATCH] " Timur Tabi
2010-05-27 19:44 ` Wolfgang Denk
2010-05-27 20:01 ` Timur Tabi
2010-05-27 20:57 ` Wolfgang Denk
2010-05-27 21:05 ` Timur Tabi [this message]
2010-05-27 21:13 ` Wolfgang Denk
2010-05-27 21:10 ` Kumar Gala
2010-05-27 21:16 ` Wolfgang Denk
2010-05-27 20:06 ` Scott Wood
2010-05-27 21:06 ` Wolfgang Denk
2010-05-27 18:59 ` Wolfgang Wegner
2010-05-27 19:49 ` 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=4BFEDE90.6070802@freescale.com \
--to=timur@freescale.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