[coreboot] [v2] r4188 - trunk/coreboot-v2/targets/hp/dl145_g3
mylesgw at gmail.com
Tue Apr 28 00:03:39 CEST 2009
> -----Original Message-----
> From: ron minnich [mailto:rminnich at gmail.com]
> Sent: Monday, April 27, 2009 3:57 PM
> To: Myles Watson
> Cc: coreboot at coreboot.org
> Subject: Re: [coreboot] [v2] r4188 - trunk/coreboot-v2/targets/hp/dl145_g3
> On Mon, Apr 27, 2009 at 2:54 PM, Myles Watson <mylesgw at gmail.com> wrote:
> > Right now Config.lb files are mostly commented out lines referring to
> > someone else's test payloads. I think we should hide most of the
> > options in src/mainboard/*/Config.lb, and only have the ones users
> > should need to care about in target/*/Config.lb.
> well, of course. That's how it is intended to work. The issue is the
> usage, but the basic design is what you say.
Understood. I'd like to get the usage in line.
> But I don't see the point of only having one Config.lb in targets.
Why should there be multiple?
> I want to make sure you are not proposing that they make a habit of
> changing the Config.lb in targets. That way lies madness.
Who do you mean? I think it should be a habit for users to customize one
Config.lb. Having many files makes it hard to keep them updated. An
example of that is the Kontron abuild that only builds fallback. The
Config.lb builds normal and fallback, so now abuild doesn't check the
"default" config file's build.
More information about the coreboot