Kyösti Mälkki has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36418 )
Change subject: [NOT FOR MERGE]: Demo adding near_reset_vector symbol ......................................................................
Patch Set 1:
(1 comment)
A bit off-topic, but I think the development effort should be in providing good methods for equivalent of normal/fallback boot flows with and without VBOOT installed. Should we support configuration where bootblock has only CBMEM console enabled, while SPI/EHCI consoles would be delayed to (fallback) romstage? Assuming one does not completely mess up the build of an experimental romstage, bootblock and VBOOT debug output from CBMEM could be replayed to SPI/EHCI even before raminit? This would often bring bootblock size downto 16 KiB or less, while not having undesirable speed impact for 'stable or normal' boot flow.
https://review.coreboot.org/c/coreboot/+/36418/1/src/cpu/x86/16bit/entry16.i... File src/cpu/x86/16bit/entry16.inc:
https://review.coreboot.org/c/coreboot/+/36418/1/src/cpu/x86/16bit/entry16.i... PS1, Line 44: .type _start16bit, @function
Is it not? The .align 4096 is sitting up there still on line 37.
The section is defined with an absolute start address in reset16.ld.
fffffe00 A _NEAR_RESET_VECTOR fffffe00 T _start16bit
and
2 .near_reset_vector 000000bb fffffe00 fffffe00 00003e54 2**2