Hi,
I’d like to know why RW_Legacy UEFI payloads don’t get updated releases like their counterpart full UEFI ROMs where UEFI payloads do get updated along with newer Coreboot releases?
How does one go about compiling a recent build of RW_Legacy UEFI payloads?
why do you think it needs to be updated?
RW_LEGACY is just the edk2 payload; it runs after the stock Google firmware (coreboot + vboot + depthcharge).
The UEFI Full ROM is coreboot + edk2. The updates are to coreboot or to edk2 features which require integration with coreboot.
TLDR there is nothing to update
That makes sense. Thanks for the clarification. However, I would still like to know how to build those RW_Legacy binary releases, if you wouldn’t mind. Guides on compiling are only available for Full UEFI ROMs.
I don’t have a guide for building RW_LEGACY payloads. You can’t just use the edk2 payload from the Full ROM as it’s grown too big and it has features enabled that the stock firmware doesn’t support