[coreboot] [PATCH] Move cmos.default handling to bootblock

Peter Stuge peter at stuge.se
Fri Feb 18 03:55:15 CET 2011


Patrick Georgi wrote:
> 
> The cmos.default code wasn't actually used so far, due to an oversight
> when forward-porting this feature from an old branch.
> 
> - Extend walkcbfs' use by factoring out the stage handling into C code.
> - New sanitize_cmos() function that looks if CMOS data is invalid and
>   cmos.default exists and if so overwrites CMOS with cmos.default data.
> - Use sanitize_cmos() in both bootblock implementations.
> - Drop the need to reboot after writing CMOS: CMOS wasn't used so far,
>   so we can go on without a reboot.
> - Remove the restriction that cmos.default only works on CAR boards.
> - Always build in cmos.default support on boards that USE_OPTION_TABLE.

Is there a Kconfig option for enabling the NVRAM write? I would like
that very much. I'd also like it to be off by default.

Maybe we should consider some coreboot "profiles" for Kconfig, that
would autoselect options, which could be manually overridden by
experts?


//Peter




More information about the coreboot mailing list