linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 2/6] powerpc: Move CONFIG_PPC64 into CPU selection
Date: Wed, 2 May 2007 08:35:43 -0500	[thread overview]
Message-ID: <6F25998F-1F2B-448B-A2CD-AF6EC97EF150@kernel.crashing.org> (raw)
In-Reply-To: <20070502115644.764580297@arndb.de>


On May 2, 2007, at 6:47 AM, Arnd Bergmann wrote:

> Currently, PPC64 is a top level configuration option in
> arch/powerpc/Kconfig, which is somewhat unconventional.
>
> Moving it into the CPU selection menu is a natural choice,
> and is transparent to the rest of the configuration logic.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

I know Paul made a very conscious decisions to make the 64-bit choice  
a top level config option when we moved to arch/powerpc.  This is  
patch effective reverts back to how we did things in arch/ppc.

I'll let it up to him to remind us why he wanted that since I dont  
remember.

- k

> Index: linux-2.6/arch/powerpc/platforms/Kconfig.cputype
> ===================================================================
> --- linux-2.6.orig/arch/powerpc/platforms/Kconfig.cputype
> +++ linux-2.6/arch/powerpc/platforms/Kconfig.cputype
> @@ -1,37 +1,24 @@
> -config PPC64
> -	bool "64-bit kernel"
> -	default n
> -	help
> -	  This option selects whether a 32-bit or a 64-bit kernel
> -	  will be built.
> -
>  menu "Processor support"
>  choice
>  	prompt "Processor Type"
> -	depends on PPC32
>  	default 6xx
> -
> -config CLASSIC32
> -	bool "52xx/6xx/7xx/74xx"
> -	select PPC_FPU
> -	select 6xx
>  	help
>  	  There are four families of PowerPC chips supported.  The more  
> common
>  	  types (601, 603, 604, 740, 750, 7400), the Motorola embedded
> -	  versions (821, 823, 850, 855, 860, 52xx, 82xx, 83xx), the AMCC
> -	  embedded versions (403 and 405) and the high end 64 bit Power
> -	  processors (POWER 3, POWER4, and IBM PPC970 also known as G5).
> -
> -	  This option is the catch-all for 6xx types, including some of the
> -	  embedded versions.  Unless there is see an option for the specific
> -	  chip family you are using, you want this option.
> +	  versions (8xx, 55xx, 85xx), the AMCC embedded version (403, 405,
> +	  440, 460) and the 64 bit processors (POWER 3, POWER4, POWER5,
> +	  POWER6, PowerPC 970, Cell/B.E., PA6T).
>
> -	  You do not want this if you are building a kernel for a 64 bit
> -	  IBM RS/6000 or an Apple G5, choose 6xx.
> +	  If unsure, select 52xx/6xx/7xx/74xx.
>
> -	  If unsure, select this option
> +config PPC64
> +	bool "any 64 bit PowerPC"
> +	select PPC_FPU
>
> -	  Note that the kernel runs in 32-bit mode even on 64-bit chips.
> +config CLASSIC32
> +	bool "52xx/6xx/7xx/74xx"
> +	select PPC_FPU
> +	select 6xx
>
>  config PPC_82xx
>  	bool "Freescale 82xx"
> @@ -119,7 +106,6 @@ config E500
>
>  config PPC_FPU
>  	bool
> -	default y if PPC64
>
>  config BOOKE
>  	bool
>
> --

  reply	other threads:[~2007-05-02 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 11:47 [PATCH 0/6] CPU selection Kconfig cleanup Arnd Bergmann
2007-05-02 11:47 ` [PATCH 1/6] powerpc: split out CPU specific options into a new Kconfig file Arnd Bergmann
2007-05-02 15:54   ` Timur Tabi
2007-05-02 16:40     ` Arnd Bergmann
2007-05-02 17:51     ` Jon Loeliger
2007-05-02 11:47 ` [PATCH 2/6] powerpc: Move CONFIG_PPC64 into CPU selection Arnd Bergmann
2007-05-02 13:35   ` Kumar Gala [this message]
2007-05-02 11:47 ` [PATCH 3/6] powerpc: move 82xx/83xx/86xx Kconfig options to platform selection Arnd Bergmann
2007-05-02 11:47 ` [PATCH 4/6] powerpc: rename add_bridge to avoid namespace clashes Arnd Bergmann
2007-05-02 11:47 ` [PATCH 5/6] powerpc: Multiplatformize 8{2,3,6}xx configuration Arnd Bergmann
2007-05-02 12:13 ` [PATCH 6/6] powerpc: autoselect optimal -mcpu= flag by platform Arnd Bergmann

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=6F25998F-1F2B-448B-A2CD-AF6EC97EF150@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).