[coreboot] newconfig to Kconfig for Dummies
mylesgw at gmail.com
Fri Feb 5 18:17:48 CET 2010
> -----Original Message-----
> From: coreboot-bounces at coreboot.org [mailto:coreboot-bounces at coreboot.org]
> On Behalf Of Stefan Reinauer
> Sent: Friday, February 05, 2010 9:44 AM
> To: ron minnich
> Cc: coreboot at coreboot.org
> Subject: Re: [coreboot] newconfig to Kconfig for Dummies
> On 2/5/10 5:17 PM, ron minnich wrote:
> > On Fri, Feb 5, 2010 at 1:29 AM, Stefan Reinauer <stepan at coresystems.de>
> >> On 2/5/10 5:28 AM, Myles Watson wrote:
> >>>> -CONFIG_LOGICAL_CPUS = 0x0 - Why would newconfig specify 0 cpus???
> >>> LOGICAL_CPUS is code for multiple cores. In this case I'm assuming
> >>> your CPU is single-core.
> >> Also, despite what the name implies, this is a "boolean" type of value,
> >> 0 meaning no and 1 meaning yes. It's not a number.
> > I wish we could change that name.
> > Doesn't it really mean cores?
> I think it means CONFIG_SMP while CONFIG_SMP means "create an IRQ table"
It's close to SMP, but if you have a dual K8 with single-core processors,
you can set LOGICAL_CPUS=0. For testing, you could do that with dual-core
processors to disable the siblings... right?
I guess it comes down to the fact that we should document it. If we can't
define it succinctly on the mailing list, the chance that we're going to be
able to come up with a descriptive CONFIG_ name is small.
More information about the coreboot