summaryrefslogtreecommitdiff
path: root/src/lib/Kconfig.cbfs_verification
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2020-10-26 20:21:34 -0700
committerJulius Werner <jwerner@chromium.org>2020-12-03 00:10:34 +0000
commit0ba16637d8f12fe9ba8388222cfa71fc5206c0f3 (patch)
tree97a2ba579c41cb3d023d0e16bfbf30aaaf02e5f8 /src/lib/Kconfig.cbfs_verification
parentc4ee28c61d955f598f475ed70951a83ab55d7e45 (diff)
x86: Put bootblock startup code into .text._start section
The initial bootblock assembly code on x86 is just put into the .text section, which just happens to come before all the individual .text.* function sections in the program.ld script. So it tends to be at the start of the image, but if you inserted another linker script section with contents before .text, it would cause a problem. (I'm not sure if it's an architectural requirement for _start16bit to come at the start of the image, but at least its 4K alignment requirement would waste a lot of space if it didn't.) This patch moves the section to .text._start which is the name other architectures use for the code they want in the very front of the image and which is listed first in program.ld. Signed-off-by: Julius Werner <jwerner@chromium.org> Change-Id: Ia84e6e33ec29584d356e226e8fdcb8c9334d49af Reviewed-on: https://review.coreboot.org/c/coreboot/+/46834 Reviewed-by: Furquan Shaikh <furquan@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/lib/Kconfig.cbfs_verification')
0 files changed, 0 insertions, 0 deletions