From: Ralf Baechle <ralf@linux-mips.org>
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: linux-mips@linux-mips.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MIPS: Kconfig: Set default value for the "Kernel code model"
Date: Tue, 11 Jun 2013 17:41:29 +0200 [thread overview]
Message-ID: <20130611154129.GD13126@linux-mips.org> (raw)
In-Reply-To: <1370944336-13703-1-git-send-email-markos.chandras@imgtec.com>
On Tue, Jun 11, 2013 at 10:52:16AM +0100, Markos Chandras wrote:
(Adding the kconfig maintainer and mailing list to cc.)
> Certain randconfigs may not select neither CONFIG_32BIT nor
> CONFIG_64BIT which can lead to build problems and to the following
> Kbuild warning:
>
> .config:154:warning: symbol value '' invalid for PHYSICAL_START
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> Acked-by: Steven J. Hill <Steven.Hill@imgtec.com>
Systems are supposed to set if they support 32 bit kernels and/or 64 bit
kernels in arch/mips/Kconfig. The behaviour you're reporting happens
if the default system (which happens to be SGI_IP22) supports both
kernel models, that is SYS_SUPPORTS_32BIT_KERNEL and
SYS_SUPPORTS_64BIT_KERNEL are set. Then "make randconfig" will generate
a .config with neiher CONFIG_32BIT nor CONFIG_64BIT set.
Just defaulting to CONFIG_32BIT as in your patch
http://patchwork.linux-mips.org/patch/5377/ isn't really a good solution
because for some platforms 32 bit kernels, for others 64 bit kernels are
preferred so I tried to implement something like
choice
prompt "Kernel code model"
default 32BIT if SYS_32BIT_KERNEL_PREFERRED
default 64BIT if SYS_64BIT_KERNEL_PREFERRED
and have individual platforms set their preferred kernel variant. And
I got more odd Kconfig behaviour, getting both choice values 32BIT and
64BIT set for some platforms.
Another variant that only uses a single auxilliary symbol,
SYS_64BIT_KERNEL_PREFERRED like this:
choice
prompt "Kernel code model"
default 32BIT if !SYS_64BIT_KERNEL_PREFERRED
default 64BIT if SYS_64BIT_KERNEL_PREFERRED
still results in
CONFIG_32BIT=y
CONFIG_64BIT=y
So I'm not quite certain how to obtain the desired behaviour - but I appears
highly unobvious to buggy on kconfig's side.
Michal, can you shed some light?
Ralf
next parent reply other threads:[~2013-06-11 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370944336-13703-1-git-send-email-markos.chandras@imgtec.com>
2013-06-11 15:41 ` Ralf Baechle [this message]
2013-06-12 11:20 ` [PATCH] MIPS: Kconfig: Set default value for the "Kernel code model" Ralf Baechle
2013-06-12 11:50 ` Markos Chandras
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=20130611154129.GD13126@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=mmarek@suse.cz \
/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