diff options
author | Gabe Black <gabeblack@chromium.org> | 2013-07-01 04:34:29 -0700 |
---|---|---|
committer | Patrick Georgi <patrick@georgi-clan.de> | 2013-08-15 20:13:39 +0200 |
commit | ec3a462d03527b2f4e620f43a5fa8fe518c5dee7 (patch) | |
tree | d9124a450754a2785ac7afb0fae5e6beedd9be71 /src/superio/acpi/pnp_kbc.asl | |
parent | 0c605a5a6cf0b5a7bdaa6068168581dc8fb24d22 (diff) |
CBFS: Change how the bss is zeroed when loading a stage.
For reasons explained in a previous CL, it might be necessary to "load" a file
from CBFS in place. The loading code in CBFS was, however, zeroing the area of
memory the stage was about to be loaded into. When the CBFS data is located
elsewhere this works fine, but when it isn't you end up clobbering the data
you're trying to load. Also, there's no reason to zero memory we're about to
load something into or have just loaded something into. This change makes it
so that we only zero out the portion of the memory between what was
loaded/decompressed and the final size of the stage in memory.
Change-Id: If34df16bd74b2969583e11ef6a26eb4065842f57
Signed-off-by: Gabe Black <gabeblack@chromium.org>
Reviewed-on: http://review.coreboot.org/3579
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <patrick@georgi-clan.de>
Diffstat (limited to 'src/superio/acpi/pnp_kbc.asl')
0 files changed, 0 insertions, 0 deletions