summaryrefslogtreecommitdiff
path: root/payloads/libpayload
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2013-11-05 17:07:44 -0600
committerAaron Durbin <adurbin@google.com>2014-01-28 23:13:12 +0100
commit8449b5e0a9e5eca3c91c1d9351d5f21eaa0ba582 (patch)
treead16c84f2efb119b39d87909002b1bc46fd0c5e6 /payloads/libpayload
parent029aaf627c381a70b365e8b29797425785eb6788 (diff)
libpayload: adjust max number of memranges
Rambi currently has more than 16 memory ranges. Because of this libpayload is silently dropping them and the full amount of memory is not being properly wiped. Correct this by bumping the number of ranges to 32. BUG=None BRANCH=None TEST=Built and booted rambi. Noted that the full amount of memory was being properly wiped. Change-Id: Ida456decf2498cb1547c0ceef23df446a975606b Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/175792 Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: http://review.coreboot.org/4942 Reviewed-by: Aaron Durbin <adurbin@google.com> Tested-by: build bot (Jenkins)
Diffstat (limited to 'payloads/libpayload')
-rw-r--r--payloads/libpayload/include/sysinfo.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/payloads/libpayload/include/sysinfo.h b/payloads/libpayload/include/sysinfo.h
index fd60dc34d9..a66c1e7c8f 100644
--- a/payloads/libpayload/include/sysinfo.h
+++ b/payloads/libpayload/include/sysinfo.h
@@ -30,8 +30,8 @@
#ifndef _SYSINFO_H
#define _SYSINFO_H
-/* Allow a maximum of 16 memory range definitions. */
-#define SYSINFO_MAX_MEM_RANGES 16
+/* Maximum number of memory range definitions. */
+#define SYSINFO_MAX_MEM_RANGES 32
/* Allow a maximum of 8 GPIOs */
#define SYSINFO_MAX_GPIOS 8