[LinuxBIOS] LinuxBIOSv3 Config files
myles at pel.cs.byu.edu
Thu Jan 10 20:28:51 CET 2008
> -----Original Message-----
> From: Jordan Crouse [mailto:jordan.crouse at amd.com]
> Sent: Thursday, January 10, 2008 12:18 PM
> To: ron minnich
> Cc: Myles Watson; Linuxbios
> Subject: Re: LinuxBIOSv3 Config files
> On 10/01/08 11:03 -0800, ron minnich wrote:
> > On Jan 10, 2008 10:29 AM, Jordan Crouse <jordan.crouse at amd.com> wrote:
> > >
> > > On 10/01/08 10:19 -0800, ron minnich wrote:
> > > > On Jan 9, 2008 1:56 PM, Myles Watson <myles at pel.cs.byu.edu> wrote:
> > > >
> > > > > make oldconfig < newlines.txt
> > > >
> > > > yes y | make oldconfig
> > >
> > > Dangerous - not all defaults are 'y'.
> > >
> > sure, but it's at least as safe as newlines.txt
> His goal was to get the defaults - newlines.txt will do that. Your option
> may turn very undesirable options - saying 'y' to "experimental" is not
> always the best way.
> I am on record as forcing the buildrom developer to generate and maintain
> a complete configuration file - I think it supports more reproducible
> and eliminates doubt and confusion. That I said, I understand what Myles
> is trying to do, and it really should be a feature that kconfig offers.
This brings us back to the reason we started this conversation. I think
it's too bad to force the ROM_size argument from a config file. Having a
different config file for each architecture * rom_size * console_option *
boot_Device means that no one will implement/maintain them.
I think it would be nice to allow people (maybe only with "Advanced Options"
selected) to configure v3 (at least specify the ROM size and the
architecture) from buildrom. I think the easier we make it to try out
different things, the more people will try things and help us improve.
We can also do checks to see if payloads will fit from buildrom if we have
some idea about the ROM size.
> Jordan Crouse
> Systems Software Development Engineer
> Advanced Micro Devices, Inc.
More information about the coreboot