Re: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-13 Thread Josh Boyer
On Mon, Sep 06, 2010 at 10:45:26AM -0500, Olof Johansson wrote: >On Sun, Sep 05, 2010 at 10:19:53PM -0700, Tirumala Marri wrote: >> > >> > Then the device tree identifier, and the cpu setup functions, etc, >> > should indicate >> > 464, not APM821xx. >> This is new SoC based on 464 cpu core. All th

RE: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-08 Thread Tirumala Marri
> > CPU portion uses SoC name. > > Hm, you're right. Confusing. > > Still, the cpu setup functions would make more sense to have the core > name in, not the SoC name. Especially since multiple SoC families might > use the same core, etc. [Marri] I agree. Probably we need another node which identifi

Re: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-06 Thread Olof Johansson
On Sun, Sep 05, 2010 at 10:19:53PM -0700, Tirumala Marri wrote: > > > > Then the device tree identifier, and the cpu setup functions, etc, > > should indicate > > 464, not APM821xx. > This is new SoC based on 464 cpu core. All the previous SoC device tree > CPU portion uses SoC name. Hm, you're ri

RE: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-06 Thread Tirumala Marri
> >Every new board needs new defconfig. And it is not same as others. It > has > >Different features from other. > > You make it sound as if that is a hard and fixed rule. It's not. Not > all > boards need a defconfig. Also, there was recent work to trim the > defconfigs > that exist today down

Re: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-06 Thread Josh Boyer
On Sun, Sep 05, 2010 at 10:19:53PM -0700, Tirumala Marri wrote: >> >> Then the device tree identifier, and the cpu setup functions, etc, >> should indicate >> 464, not APM821xx. >This is new SoC based on 464 cpu core. All the previous SoC device tree >CPU portion uses SoC name. > >> >> Also, why ad

RE: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-05 Thread Tirumala Marri
> > Then the device tree identifier, and the cpu setup functions, etc, > should indicate > 464, not APM821xx. This is new SoC based on 464 cpu core. All the previous SoC device tree CPU portion uses SoC name. > > Also, why add yet another defconfig? Isn't the eval board similar to > many others an

Re: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-05 Thread Olof Johansson
On Fri, Sep 03, 2010 at 01:38:46PM -0700, Tirumala Marri wrote: > > >APM821xx is Applied Micro Circuits Corporations naming convention for > > >new line of SoCs. > > > > So is it a 440x6 core then? Or what core is inside the SoC? > [Marri] It is 464 core. Then the device tree identifier, and the

RE: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-03 Thread Tirumala Marri
> >APM821xx is Applied Micro Circuits Corporations naming convention for > >new line of SoCs. > > So is it a 440x6 core then? Or what core is inside the SoC? [Marri] It is 464 core. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://list

Re: [PATCH] APM821xx: Add support for new SoC APM821xx

2010-09-02 Thread Josh Boyer
On Thu, Sep 02, 2010 at 02:57:33PM -0700, tma...@apm.com wrote: >From: Tirumala Marri > >This patch adds CPU, device tree, defconfig and bluestone board >support for APM821xx SoC. > >Signed-off-by: Tirumala R Marri >--- >APM821xx is Applied Micro Circuits Corporations naming convention for >new l