diff options
author | Gabe Black <gabeblack@chromium.org> | 2012-01-15 06:54:59 -0800 |
---|---|---|
committer | Gabe Black (Do Not Use) <gabeblack@google.com> | 2012-01-18 20:55:47 -0800 |
commit | 29538919a8c0206c320162c061ce2511ea86e1e6 (patch) | |
tree | 12e0e7975c0a23d798bf1dd289479d477b998996 /include | |
parent | edc55109a42662c7e661070433b478f74ebb4165 (diff) |
X86: Don't assume U-Boot extends to the end of memory when wiping
On ARM, U-Boot is put at the end of memory, and the code that records the
unused areas of memory to be wiped uses the end of RAM as the upper bound
for the region occupied by U-Boot. On x86, U-Boot may have been relocated to
somewhere lower than the end of RAM because it can normally only address a 32
bit address space. This change makes the wiping code calculate where U-Boot
actually ends on x86 so the areas with large addresses will be wiped properly.
BUG=chrome-os-partner:7579
TEST=Built and booted on Lumpy, Stumpy, and Kaen. On Lumpy, verified that the
area with physical addresses above 4GB was now in the list to be wiped.
Change-Id: Ib7e0818e85daf512b76f85f4e68f88230d301cea
Signed-off-by: Gabe Black <gabeblack@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/14223
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions