From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: [patch 02/10] powerpc: Move CONFIG_PPC64 into CPU selection
Date: Tue, 12 Jun 2007 10:08:01 +0200 [thread overview]
Message-ID: <200706121008.01661.arnd@arndb.de> (raw)
In-Reply-To: <18030.15937.699275.958545@cargo.ozlabs.ibm.com>
On Tuesday 12 June 2007, Paul Mackerras wrote:
> > Currently, PPC64 is a top level configuration option in
> > arch/powerpc/Kconfig, which is somewhat unconventional.
>=20
> It makes a lot of sense to me to have 32 vs. 64 bits as a high level
> binary selector that conditions the things that follow. =A0I don't think
> it makes sense to push it down into the CPU selection menu.
Can you eleborate, other than stating the exact opposite of what
my comment said?
I don't mind removing this patch from the series, but I'd like to
understand the reason. I've always thought of the top-level option
as a temporary ugly hack that should eventually go away ;-)
Other than subjective feelings, my reasons for this patch were:
* No other architecture I have seen uses bool options in the top-level
menu, so it would be more consistant to move it to the cpu type
selection menu.
* we have six (depending on how you count) PPC CPU families
supported by Linux (4xx, 6xx, 8xx, e200, e500, ppc64), each
of them incompatible with the others, meaning that you can run
common user space but not a common kernel. Having the list in
as the first Kconfig choice seems logical to me, because
all other options more or less depend on these.
* The only major difference between ppc64 and the others is the
object format of the kernel binary. My impression when playing
with the cpu selection menu was that we have a lot more stuff
depending on 6xx than on ppc64.
* Given the choice between the equivalent
> config PPC64
> bool
>
> choice
> depends on !PPC64
> config 4xx
> config 6xx
> config 8xx
> config E200
> config E500
> endchoice
and
> choice
> config PPC64
> config 4xx
> config 6xx
> config 8xx
> config E200
> config E500
> endchoice
I find the latter easier to understand regarding further options
depending on each of them in the individual platforms, e.g. each
of the platforms/foo/Kconfig files depends on exactly one of these
six options.=20
Arnd <><
next prev parent reply other threads:[~2007-06-12 8:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:28 [patch 00/10] CPU selection Kconfig cleanup, take 2 arnd
2007-06-11 23:28 ` [patch 01/10] powerpc: split out CPU specific options into a new Kconfig file arnd
2007-06-12 4:02 ` Stephen Rothwell
2007-06-12 7:42 ` Arnd Bergmann
2007-06-12 11:12 ` Paul Mackerras
2007-06-12 12:42 ` Arnd Bergmann
2007-06-11 23:28 ` [patch 02/10] powerpc: Move CONFIG_PPC64 into CPU selection arnd
2007-06-12 6:33 ` Paul Mackerras
2007-06-12 8:08 ` Arnd Bergmann [this message]
2007-06-12 11:11 ` Paul Mackerras
2007-06-12 11:35 ` Segher Boessenkool
2007-06-12 21:32 ` Benjamin Herrenschmidt
2007-06-13 4:52 ` Segher Boessenkool
2007-06-13 0:42 ` Paul Mackerras
2007-06-13 4:57 ` Segher Boessenkool
2007-06-12 11:49 ` Arnd Bergmann
2007-06-11 23:28 ` [patch 03/10] powerpc: move 82xx/83xx/86xx Kconfig options to platform selection arnd
2007-06-11 23:28 ` [patch 04/10] powerpc: rename add_bridge to avoid namespace clashes arnd
2007-06-12 4:11 ` Stephen Rothwell
2007-06-11 23:28 ` [patch 05/10] powerpc: Multiplatformize 8{2,3,6}xx configuration arnd
2007-06-11 23:28 ` [patch 06/10] powerpc: multiplatformize embedded6xx Kconfig arnd
2007-06-12 4:15 ` Stephen Rothwell
2007-06-12 4:16 ` Stephen Rothwell
2007-06-12 5:59 ` Kumar Gala
2007-06-12 7:46 ` Arnd Bergmann
2007-06-11 23:28 ` [patch 07/10] powerpc: multiplatformize 52xx configuration arnd
2007-06-11 23:28 ` [patch 08/10] powerpc: multiplatformize 85xx Kconfig arnd
2007-06-11 23:28 ` [patch 09/10] powerpc: autoselect PPC_MULTIPLATFORM arnd
2007-06-11 23:28 ` [patch 10/10] powerpc: autoselect optimal -mcpu= flag by platform arnd
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=200706121008.01661.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.