1 comment:
File Documentation/releases/coreboot-4.12-relnotes.md:
Historically the bootblock on x86 platforms has been compiled with
romcc. This means that the generated code only uses CPU registers
and therefore no stack. This 20K+ LOC compiler is limited and hard
to maintain and so is the code that one has to write in that
environment. A different solution is to set up Cache-as-Ram in the
bootblock and run GCC compiled code in the bootblock. The advantages
are increased flexibility and consistency with other architectures as
well as other stages: e.g. printing to console is possible and
VBOOT can run before romstage, making romstage updatable via RW FMAP
regions.
If the normal/fallback mechanism is dropped as a consequence of this change, it would also be a good […]
It's not about dropping it or not, it's that when you change the bootblock, you can't use normal/fallback as-is to test the new bootblock
To view, visit change 37064. To unsubscribe, or for help writing mail filters, visit settings.