Kconfig options discussion

[Myles Watson]

I divided the options from config/Options.lb up the way it made most sense
to me.  I'd like to see other people's divisions.

It seems like many options can just go away with Kconfig.

Having agreement on what options should be set where will hopefully speed
porting/reviewing efforts.

Thanks,
Myles

[ron minnich]

On Thu, Aug 13, 2009 at 11:42 AM, Myles Watson wrote:
> I divided the options from config/Options.lb up the way it made most sense
> to me.  I'd like to see other people's divisions.

This is a great breakdown.

What I wonder about doing to start: starting with ALL the options
listed in, e.g., cpu.txt,
move them from the mainboard Kconfig to the src/socket/Kconfig file,
and see if we can make it work correctly.

Stupid question: I know that we can, e.g.
select SOCKET_AMD_F
in the mainboard Kconfig.
How do we set a value to a config variable (non-interactively)?

ron
For a config variable with a value,