[patch 1/9] move 82xx/83xx/86xx Kconfig options to platform selection
Mark A. Greer
mgreer at mvista.com
Thu Jul 12 09:47:09 EST 2007
On Wed, Jul 11, 2007 at 10:33:51PM +0200, Arnd Bergmann wrote:
> On Wednesday 11 July 2007, Mark A. Greer wrote:
>
> > > +config CLASSIC32
> > > + def_bool y
> > > + depends on 6xx && PPC_MULTIPLATFORM
> > ^^^^^^^^^^^^^^^^^^^^
> > Arnd, is this really what you wanted? With it, none of the embedded
> > classics have CLASSIC32 defined which means they don't get TAU or
> > ALTIVEC defined which isn't good.
>
> Sorry, this was the result of a wrong patch reordering. In my initial
> patch set I ended up with 6xx == CLASSIC32 and PPC_MULTIPLATFORM=y,
> but then I backed out a few patches in the middle.
Ah, okay.
> I guess the best is to do another patch that moves PPC_EMBEDDED6xx into
> PPC_MULTIPLATFORM again and leaves this one as it is.
> Alternatively, we could kill CONFIG_CLASSIC32 entirely as it is used
> only in a few places. Especially after I resubmit my CPU type selection
> patch again, which allows you do it in a more fine grained way.
Yes, it seems like getting rid of CLASSIC32 would be okay since it is
hardly used.
> Which systems in particular should allow CONFIG_TAU? Is there a more
> specific dependency than (6xx && !(82xx || 83xx || 86xx || 52xx))?
I think Segher pretty much answered this. We definitely need to get
ALTIVEC back soon for 74xx--currently SIGILL's my init when booting.
Since it sounds like you're still tweaking things in Kconfig files,
I'll leave it to you to take care of it. If not, just let me know.
Mark
More information about the Linuxppc-dev
mailing list