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)
This commit is contained in:
parent
029aaf627c
commit
8449b5e0a9
|
@ -30,8 +30,8 @@
|
||||||
#ifndef _SYSINFO_H
|
#ifndef _SYSINFO_H
|
||||||
#define _SYSINFO_H
|
#define _SYSINFO_H
|
||||||
|
|
||||||
/* Allow a maximum of 16 memory range definitions. */
|
/* Maximum number of memory range definitions. */
|
||||||
#define SYSINFO_MAX_MEM_RANGES 16
|
#define SYSINFO_MAX_MEM_RANGES 32
|
||||||
/* Allow a maximum of 8 GPIOs */
|
/* Allow a maximum of 8 GPIOs */
|
||||||
#define SYSINFO_MAX_GPIOS 8
|
#define SYSINFO_MAX_GPIOS 8
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue