[coreboot] [PATCH] Move cmos.default handling to bootblock
Patrick.Georgi at secunet.com
Fri Feb 18 12:28:23 CET 2011
Am Freitag, den 18.02.2011, 12:15 +0100 schrieb Peter Stuge:
> > 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?
We don't deliver cmos.default files, so this is a user setting at this
This might change, and then we should reevaluate how we handle CMOS.
But USE_OPTION_TABLE should disable it _all_ anyway.
So you already have:
- no CMOS at all
- CMOS support, but no cmos.default
- CMOS support with cmos.default
> 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;
We already stretch Kconfig beyond its limits. Let's not do it any
further or it will break apart.
> * Strict mode (requires NVRAM to always be correct, or will fail to
> boot. maybe also other extra checks in the code)
"Fail to boot"? I wonder about its use.
SINA-Development - High Security
secunet Security Networks AG - Mergenthalerallee 77 - 65760 Eschborn, Germany
Phone +49 201 54 54-3610 - Fax +49 201 54 54-1325 - www.secunet.com
Sitz: Kronprinzenstraße 30, 45128 Essen / Amtsgericht Essen HRB 13615
Vorstand: Dr. Rainer Baumgart (Vors.), Thomas Koelzer, Thomas Pleines
Aufsichtsratsvorsitzender: Dr. Karsten Ottenberg
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the coreboot