[coreboot] Can we please remove the FSP TempRamInit option (where applicable)
nico.h at gmx.de
Tue Nov 6 19:11:22 CET 2018
Hi coreboot fellows,
I have always been confused that we have the option to use FSP's
TempRamInit (CAR setup) even when a native coreboot implementation is
available. Now, what I'm really concerned about is the low quality of
the code in coreboot surrounding it. There are often Kconfig prompts
that don't add up, and about every related, merged commit I've been
looking at today seemed somehow flawed.
So if we can't keep the quality we are used to when trying to maintain
two (or even more) CAR options, why not focus on a single one? After
all, coreboot is a firmware framework, not an FSP testing framework.
Here's just one weird example of what I was confronted with today:
default USE_CANNONLAKE_CAR_NEM_ENHANCED if
I don't understand it, but somehow feel offended. Does that mean I have
to work with ChromeOS now to get reasonable defaults?
More information about the coreboot