All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrey Volkov <avolkov@varma-el.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [POWERPC] MPC52xx is a 6xx variant, remove PPC_52xx config option
Date: Fri, 27 Oct 2006 20:24:53 +1000	[thread overview]
Message-ID: <1161944693.25682.70.camel@localhost.localdomain> (raw)
In-Reply-To: <4541D7D5.7090001@varma-el.com>

On Fri, 2006-10-27 at 13:56 +0400, Andrey Volkov wrote:
> Grant Likely wrote:
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > ---
> >  arch/powerpc/Kconfig |    5 -----
> >  1 files changed, 0 insertions(+), 5 deletions(-)
> > 
> > diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> > index f9b11c1..6bff8b7 100644
> > --- a/arch/powerpc/Kconfig
> > +++ b/arch/powerpc/Kconfig
> > @@ -126,11 +126,6 @@ config CLASSIC32
> >  	  systems, 64 bit IBM RS/6000 or an Apple G5, choose 6xx.
> >  	  Note that the kernel runs in 32-bit mode even on 64-bit chips.
> >  
> > -config PPC_52xx
> > -	bool "Freescale 52xx"
> > -	select 6xx
> > -	select PPC_FPU
> > -	
> >  config PPC_82xx
> >  	bool "Freescale 82xx"
> >  	select 6xx

> Please _don't_ do it, since mpc5200 platform drivers depend from this
> option.

And that should be fixed. We are yet discussing the proper way of
integrating 52xx in arch/powerpc, but that definitely doesn't involve
making it an exclusive processor type. Besides, there will probably be
enough changes in the drivers to adapt them to of_platform_device type
probing that we might just well fork them all anyway.

Ben.

  reply	other threads:[~2006-10-27 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26  3:52 [POWERPC] MPC52xx is a 6xx variant, remove PPC_52xx config option Grant Likely
2006-10-27  9:56 ` Andrey Volkov
2006-10-27 10:24   ` Benjamin Herrenschmidt [this message]
2006-10-27 13:21     ` Grant Likely

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=1161944693.25682.70.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=avolkov@varma-el.com \
    --cc=linuxppc-embedded@ozlabs.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.