[coreboot] [PATCH] Move cmos.default handling to bootblock
Peter Stuge
peter at stuge.se
Fri Feb 18 12:15:38 CET 2011
Georgi, Patrick wrote:
> > 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.
>
> HAVE_CMOS_DEFAULT. Without this, cmos.default isn't put into CBFS
> (by default), and without that file, no write happens.
But it's a mainboard knob, not a user knob, right?
> > Maybe we should consider some coreboot "profiles" for Kconfig, that
> > would autoselect options, which could be manually overridden by
> > experts?
>
> "profiles"? We have those: mainboard defaults.
Call them profiles or maybe personalities. Yes there is one set of
options from the developer creating the original port, but I'm
thinking more of bird's view variations;
* Zero impact coreboot (never writes to NVRAM)
* Normal mode (will fix NVRAM with defaults)
* Strict mode (requires NVRAM to always be correct, or will fail to
boot. maybe also other extra checks in the code)
There could be other personalities. The point is that they are very
high level (ie. easy for every user to decide on, because they fit or
do not fit) and might control more than one Kconfig option.
//Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20110218/8817df29/attachment.sig>
More information about the coreboot
mailing list