summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorPali Rohár <pali@kernel.org>2022-09-09 18:32:38 +0300
committerTom Rini <trini@konsulko.com>2022-09-23 22:11:13 +0300
commit7210e457d5d166b4409bde402fd95a99e87cdfc5 (patch)
tree180ff884a4a08b51b3916c429c5de23162d4027c /common
parent4057d64fae78e1e9bf8a5a87a823f188a1339917 (diff)
downloadu-boot-7210e457d5d166b4409bde402fd95a99e87cdfc5.tar.xz
common/memsize.c: Fix get_effective_memsize() to always check for CONFIG_MAX_MEM_MAPPED
CONFIG_MAX_MEM_MAPPED when defined specifies upper memory mapped limit. So check for it always, and not only when CONFIG_VERY_BIG_RAM is defined. Signed-off-by: Pali Rohár <pali@kernel.org>
Diffstat (limited to 'common')
-rw-r--r--common/memsize.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/memsize.c b/common/memsize.c
index d5d13d51bf..31884acca0 100644
--- a/common/memsize.c
+++ b/common/memsize.c
@@ -94,7 +94,7 @@ long get_ram_size(long *base, long maxsize)
phys_size_t __weak get_effective_memsize(void)
{
-#ifndef CONFIG_VERY_BIG_RAM
+#ifndef CONFIG_MAX_MEM_MAPPED
return gd->ram_size;
#else
/* limit stack to what we can reasonable map */