summaryrefslogtreecommitdiff
path: root/3rdparty
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2015-09-17 17:02:53 -0500
committerAaron Durbin <adurbin@chromium.org>2015-09-22 21:22:44 +0000
commitd972f78e759ffccf9187ab3f3b00b567c7f30f53 (patch)
tree435ba6384408f63a21c633141a9d1bece8079421 /3rdparty
parentf66a026d70961832164ca4edd701d762384786b3 (diff)
linking: link bootblock.elf with .data and .bss sections again
Currently coreboot expects the loader to clear the bss section for all stages. i.e. stages don't clear their own bss. On ARM SoCs the BootROM would be responsible for this. To do that one needs to include the bss section data (all zeros) in the bootblock.bin file. This was previously being attempted by keeping the .bss info in the .data section because objcopy happened zero out non-file allocated data section data. Instead go back to linking bootblock with the bss section but mark the bss section as loadable allocatable data. That way it will be included in the binary properly when objcopy -O binary is emplyed. Also do the same for the data section in the case of no non-zero object values are in the data section. Without this change the trick of including .bss in .data was not working when there wasn't a non-zero value object in the data section. BUG=None BRANCH=None TEST=Built emulation/qemu-armv7 and noted bootblock.bin contains the cleared bss. Change-Id: I94bd404c2c4a8b9332393e6224e98940a9cad4a2 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11680 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to '3rdparty')
0 files changed, 0 insertions, 0 deletions