From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dan Kegel <dank@kegel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix allnoconfig on arm with small tweak to kconfig?
Date: Mon, 13 Sep 2004 09:15:34 +0100 [thread overview]
Message-ID: <20040913091534.B27423@flint.arm.linux.org.uk> (raw)
In-Reply-To: <414551FD.4020701@kegel.com>; from dank@kegel.com on Mon, Sep 13, 2004 at 12:53:33AM -0700
On Mon, Sep 13, 2004 at 12:53:33AM -0700, Dan Kegel wrote:
> 'make allnoconfig' generates a broken .config on arm because
> none of the boolean CPU types get selected.
> ARCH_RPC *does* get selected ok, and I can make CPU_SA110 the
> default if ARCH_RPC, but that doesn't help, since allnoconfig
> sets all booleans that are exposed to the user to false, so
> CPU_SA110 remains false.
allnoconfig is broken. It doesn't generate a legal configuration on
this platform.
There are cases where you have the choice of selecting several options
and you may select one or more. Zero options selected is not valid.
Unfortunately, Kconfig does not provide a way to express this.
> I tried it (see patch below), but couldn't get it to work in first
> few tries. Can someone who understands kconfig have a look?
I don't think hacking around allnoconfig works - it means that we
have to decide on a default for every configuration. ARCH_RPC is
only one such small case. There's loads more.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-09-13 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 7:53 Dan Kegel
2004-09-13 8:15 ` Russell King [this message]
2004-09-13 15:22 ` Dan Kegel
2004-09-13 18:51 ` Russell King
2004-09-13 19:29 ` Herbert Poetzl
2004-09-13 21:06 ` Nicolas Pitre
2004-09-13 21:34 ` Russell King
2004-09-14 1:42 ` Dan Kegel
2004-09-14 8:29 ` Russell King
2004-09-17 8:39 ` Dan Kegel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040913091534.B27423@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome