diff options
author | Stephen Warren <swarren@nvidia.com> | 2014-12-23 10:34:51 -0700 |
---|---|---|
committer | Tom Warren <twarren@nvidia.com> | 2015-03-04 10:08:56 -0700 |
commit | 56519c4f0498acdfb4dccd27bbb4b69a60cbb823 (patch) | |
tree | 69367e919018f8ce32ec52746447d7b0d935d28b /doc/README.VLAN | |
parent | 3a2cab512c0c4d96d8210e4f729dd080bbf8c90d (diff) | |
download | u-boot-imx-56519c4f0498acdfb4dccd27bbb4b69a60cbb823.zip u-boot-imx-56519c4f0498acdfb4dccd27bbb4b69a60cbb823.tar.gz u-boot-imx-56519c4f0498acdfb4dccd27bbb4b69a60cbb823.tar.bz2 |
ARM: tegra: support large RAM sizes
Some systems have so much RAM that the end of RAM is beyond 4GB. An
example would be a Tegra124 system (where RAM starts at 2GB physical)
that has more than 2GB of RAM.
In this case, we want gd->ram_size to represent the actual RAM size, so
that the actual RAM size is passed to the OS. This is useful if the OS
implements LPAE, and can actually use the "extra" RAM.
However, we can't use get_ram_size() to verify the actual amount of RAM
present on such systems, since some of the RAM can't be accesses, which
confuses that function. Avoid calling get_ram_size() when the RAM size
is too large for it to work correctly. It's never actually needed anyway,
since there's no reason for the BCT to report the wrong RAM size.
In systems with >=4GB RAM, we still need to clip the reported RAM size
since U-Boot uses a 32-bit variable to represent the RAM size in bytes.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'doc/README.VLAN')
0 files changed, 0 insertions, 0 deletions