[PATCHv2 0/8] [POWERPC] 8xx cleanups

Hi,

this is a series against paulus for-2.6.25 tree to clean up various 8xx related stuff.
The series can be pulled from git://git.bocc.de/dbox2.git cleanup.
Patch 6 has been modified to remove the #ifdefs as suggested by Arndt Bergmann.
Patch 8 is a new one.

[POWERPC] Remove unused m8xx_cpm_hostalloc/free/dump()
[POWERPC] Rename m8xx_pic_init to mpc8xx_pics_init
[POWERPC] Remove unneeded and misspelled prototype m8xx_calibrate_decr
[POWERPC] Remove declaration of m8xx_pic_init.
[POWERPC] Remove sysdev/commproc.h
[POWERPC] Get rid of conditional includes of board specific setup
[POWERPC] Rename commproc to cpm1 and cpm2_common.c to cpm2.c
[POWERPC] Move definition of buffer descriptor to cpm.h

Thanks,
Jochen

On Jan 23, 2008, at 9:58 AM, Jochen Friedrich wrote:

Hi,

this is a series against paulus for-2.6.25 tree to clean up various  
8xx related stuff.
The series can be pulled from git://git.bocc.de/dbox2.git cleanup.
Patch 6 has been modified to remove the #ifdefs as suggested by  
Arndt Bergmann.
Patch 8 is a new one.

[POWERPC] Remove unused m8xx_cpm_hostalloc/free/dump()
[POWERPC] Rename m8xx_pic_init to mpc8xx_pics_init
[POWERPC] Remove unneeded and misspelled prototype m8xx_calibrate_decr
[POWERPC] Remove declaration of m8xx_pic_init.
[POWERPC] Remove sysdev/commproc.h
[POWERPC] Get rid of conditional includes of board specific setup
[POWERPC] Rename commproc to cpm1 and cpm2_common.c to cpm2.c
[POWERPC] Move definition of buffer descriptor to cpm.h

These roughly look good, had a few comments.  Don't see any reason why  
they can't go in.

What impact do the have on boards in arch/ppc being able to build?

- k

What impact do the have on boards in arch/ppc being able to build?

Byt the way what are the plans for powerpc?
We have:
arch/ppc
arch/ppc64
arch/powerpc

It was my understanding that arch/powerpc was supposed
to be the future unified powerpc architecture but it
does not even provide a defconfig.

And I do not see too much happening to do so - but that maybe
because I looked at a wrong place.

	Sam

Sam Ravnborg wrote:

quoted

What impact do the have on boards in arch/ppc being able to build?

Byt the way what are the plans for powerpc?
We have:
arch/ppc
arch/ppc64
arch/powerpc

It was my understanding that arch/powerpc was supposed
to be the future unified powerpc architecture but it
does not even provide a defconfig.

And I do not see too much happening to do so - but that maybe
because I looked at a wrong place.

You must have looked in the wrong place. :-)

arch/ppc is scheduled for removal from mainline in June.

arch/powerpc is under significant development, with lots
of defconfigs in arch/powerpc/configs.

arch/ppc64 is long dead.

jdl

On Wed, Jan 23, 2008 at 11:31:46AM -0600, Jon Loeliger wrote:

Sam Ravnborg wrote:

quoted

quoted

What impact do the have on boards in arch/ppc being able to build?

Byt the way what are the plans for powerpc?
We have:
arch/ppc
arch/ppc64
arch/powerpc

It was my understanding that arch/powerpc was supposed
to be the future unified powerpc architecture but it
does not even provide a defconfig.

And I do not see too much happening to do so - but that maybe
because I looked at a wrong place.

You must have looked in the wrong place. :-)

arch/ppc is scheduled for removal from mainline in June.

Good to hear.

arch/powerpc is under significant development, with lots
of defconfigs in arch/powerpc/configs.

Double checked - it was my build script that used ARCH=ppc
Now I just need to build another toolchain as the ppc750 could not build
the defconfig. crosstool is my friend here.

	Sam

On Wed, 23 Jan 2008 19:00:12 +0100
Sam Ravnborg [off-list ref] wrote:

On Wed, Jan 23, 2008 at 11:31:46AM -0600, Jon Loeliger wrote:

quoted

Sam Ravnborg wrote:

quoted

quoted

What impact do the have on boards in arch/ppc being able to build?

Byt the way what are the plans for powerpc?
We have:
arch/ppc
arch/ppc64
arch/powerpc

It was my understanding that arch/powerpc was supposed
to be the future unified powerpc architecture but it
does not even provide a defconfig.

And I do not see too much happening to do so - but that maybe
because I looked at a wrong place.

You must have looked in the wrong place. :-)

arch/ppc is scheduled for removal from mainline in June.

Good to hear.

quoted

arch/powerpc is under significant development, with lots
of defconfigs in arch/powerpc/configs.

Double checked - it was my build script that used ARCH=ppc
Now I just need to build another toolchain as the ppc750 could not build
the defconfig. crosstool is my friend here.

You'll need mkimage if you ever venture into some of the embedded board
configs.  Just an FYI.

josh

On Wed, Jan 23, 2008 at 01:35:41PM -0600, Josh Boyer wrote:

On Wed, 23 Jan 2008 19:00:12 +0100
Sam Ravnborg [off-list ref] wrote:

quoted

On Wed, Jan 23, 2008 at 11:31:46AM -0600, Jon Loeliger wrote:

quoted

Sam Ravnborg wrote:

quoted

quoted

What impact do the have on boards in arch/ppc being able to build?

Byt the way what are the plans for powerpc?
We have:
arch/ppc
arch/ppc64
arch/powerpc

It was my understanding that arch/powerpc was supposed
to be the future unified powerpc architecture but it
does not even provide a defconfig.

And I do not see too much happening to do so - but that maybe
because I looked at a wrong place.

You must have looked in the wrong place. :-)

arch/ppc is scheduled for removal from mainline in June.

Good to hear.

quoted

arch/powerpc is under significant development, with lots
of defconfigs in arch/powerpc/configs.

Double checked - it was my build script that used ARCH=ppc
Now I just need to build another toolchain as the ppc750 could not build
the defconfig. crosstool is my friend here.

You'll need mkimage if you ever venture into some of the embedded board
configs.  Just an FYI.

I known - for now I'm 120% occupied getting modpost in shape and will
return to the mkimage thread when below 100%.

	Sam