Am 11.05.2011 00:04, schrieb Stefan Reinauer:
Yes, given how complex most cmos.layouts look, I was surprised. Is there an easy way to clean those cmos.layout files up?
Obsolete build_opt_tbl by moving its functionality to nvramtool (that's WIP here), define a new format (eg. the one on Infrastructure_Projects) and implement that in nvramtool with both reader and writer. Then read all cmos.layout files and write in their new form.
Not exactly "easy", but automated.
Which nvram variables are used in romstage (and by whom). e.g. that multi_core does only make sense on AMD CPUs. Does it matter?
Infrastructure_Projects :-) I'd like to move nvram variables to where they are used (eg. multi_core to AMD CPUs).
Patrick