All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/6] powerpc: split out CPU specific options into a new Kconfig file
Date: Wed, 2 May 2007 18:40:07 +0200	[thread overview]
Message-ID: <200705021840.07965.arnd@arndb.de> (raw)
In-Reply-To: <4638B42B.7040208@freescale.com>

On Wednesday 02 May 2007, Timur Tabi wrote:
> Arnd Bergmann wrote:
> 
> > +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).
> 
> Is this help text still accurate?  The bool line says "52xx/6xx/7xx/74xx", but you talk 
> about many more processors in the help text.  You mention the 83xx, but not the 85xx or 
> 86xx, nor do you mention Freescale.  Not only that, but the help text implies that 8xx, 
> 52xx, 82xx, and 83xx are part of the same family, but the bool text implies that 52xx is 
> part of a different family.

This patch just moves stuff around, one of the later patches fixes the
text.

> > +	  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.
> 
> So CLASSIC32 is only for 6xx families, not any of the others?  Then what's the "select 
> 6xx" for?  Isn't that redundant?

Currently, CLASSIC32 refers to all Open Firmware based 6xx machines, including
PowerMac, rs6000, CHRP and PReP. 6xx includes those, and also the embedded
platforms based on 6xx cores, like 86xx.

My last patch changes it so that CLASSIC32 and 6xx are actually synonyms,
and we could kill one of them.

> > +	  You do not want this if you are building a kernel for a 64 bit
> > +	  IBM RS/6000 or an Apple G5, choose 6xx.
> 
> This needs to be reworded, as the English doesn't make sense.

It also gets fixed in a later patch.

	Arnd <><

  reply	other threads:[~2007-05-02 16:40 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 [this message]
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
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=200705021840.07965.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=timur@freescale.com \
    /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.