5f740e1fdd
The address range to scan for the coreboot tables varies from machine to machine based on the range memory occupies on the SOC being booted and on the amount of memory installed on the machine. To make libpayload work on different ARM systems with different needs, this change makes the region to scan configurable. In the future, we might want to come up with a more automatic mechanism like on x86, although there's less consistency on ARM as far as what ranges are even memory in the first place. BUG=chrome-os-partner:19420 TEST=Built and booted into depthcharge on snow and pit and saw serial output which implies that the coreboot tables were found and parsed. BRANCH=None Change-Id: Ib50efe25a6152171b0fbd0e324dbc5e89c527d6e Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://gerrit.chromium.org/gerrit/59242 Reviewed-by: Gabe Black <gabeblack@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org> |
||
|---|---|---|
| .. | ||
| config.daisy | ||
| config.falco | ||
| config.fox_baskingridge | ||
| config.fox_wtm2 | ||
| config.link | ||
| config.lumpy | ||
| config.peach_pit | ||
| config.peppy | ||
| config.slippy | ||
| defconfig | ||