summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorYork Sun <yorksun@freescale.com>2015-12-07 11:05:29 -0800
committerYork Sun <yorksun@freescale.com>2015-12-15 08:57:33 +0800
commitaabd7ddb889aec3c6c4139974f66a44e2ce46ba5 (patch)
tree994bb4cf82b7efd6c61866cfd551905859288d2f /README
parentc107c0c05c988ac6cfba6de60c90f105bbea0e1e (diff)
downloadtalos-obmc-uboot-aabd7ddb889aec3c6c4139974f66a44e2ce46ba5.zip
talos-obmc-uboot-aabd7ddb889aec3c6c4139974f66a44e2ce46ba5.tar.gz
common: Rewrite hiding the end of memory
As the name may be confusing, the CONFIG_SYS_MEM_TOP_HIDE reserves some memory from the end of ram, tracked by gd->ram_size. It is not always the top of u-boot visible memory. Rewrite the macro with a weak function to provide flexibility for complex calcuation. Legacy use of this macro is still supported. Signed-off-by: York Sun <yorksun@freescale.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 6ea1af2..4aa2aae 100644
--- a/README
+++ b/README
@@ -3877,7 +3877,7 @@ Configuration Settings:
the RAM base is not zero, or RAM is divided into banks,
this variable needs to be recalcuated to get the address.
-- CONFIG_SYS_MEM_TOP_HIDE (PPC only):
+- CONFIG_SYS_MEM_TOP_HIDE:
If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
this specified memory area will get subtracted from the top
(end) of RAM and won't get "touched" at all by U-Boot. By
OpenPOWER on IntegriCloud