Re: [PATCH 08/10] bootwrapper: Add a firmware-independent "raw" target.

2007-09-09 Thread Milton Miller
On Fri Sep 7 10:58:03 EST 2007, David Gibson wrote: >> On Wed, Sep 05, 2007 at 02:21:16PM -0500, Scott Wood wrote: >> This target produces a flat binary rather than an ELF file, >> fixes the entry point at the beginning of the image, and takes >> a complete device tree with no fixups needed. >> >>

Re: [PATCH 2/5] Add Freescale DMA engine driver maintainer.

2007-09-09 Thread David Gibson
On Fri, Sep 07, 2007 at 06:53:53PM +0800, Zhang Wei wrote: > This patch adds Freescale DMA engine driver maintainer. This is meaningless without the actual driver, so it shouldn't be a separate patch. Fold it into the patch that actually adds the driver support. -- David Gibson

Re: [PATCH 1/5] Add Freescale DMA and DMA channel to Documentation/powerpc/booting-without-of.txt file.

2007-09-09 Thread David Gibson
On Fri, Sep 07, 2007 at 04:43:35PM +0200, Segher Boessenkool wrote: > > + l) Freescale DMA > > > +- compatible : Should be "fsl,dma". > > Please choose some more specific name. "fsl,mpc8540-dma" would > be a reasonable choice perhaps. More precisely, the compatible property should always

Re: Document and implement an improved flash device binding for powerpc (v5)

2007-09-09 Thread David Gibson
On Fri, Sep 07, 2007 at 04:25:10PM +0200, Segher Boessenkool wrote: > > This patch replaces the binding for flash chips in > > booting-without-of.txt with an clarified and improved version. It > > also makes drivers/mtd/maps/physmap_of.c recognize this new binding. > > Finally it revises the Ebony

Re: [PATCH 5/5] Add DMA engine driver for Freescale MPC85xx processors.

2007-09-09 Thread Dan Williams
On 9/9/07, Timur Tabi <[EMAIL PROTECTED]> wrote: > Dan Williams wrote: > > > This routine implies that there is a piece of code somewhere that > > wants to select which channels it can use. A similar effect can be > > achieved by registering a dma_client with the dmaengine interface > > ('dma_asyn

Re: [PATCH 5/5] Add DMA engine driver for Freescale MPC85xx processors.

2007-09-09 Thread Timur Tabi
Dan Williams wrote: > This routine implies that there is a piece of code somewhere that > wants to select which channels it can use. A similar effect can be > achieved by registering a dma_client with the dmaengine interface > ('dma_async_client_register'). Then when the client code makes a call

Re: [RFC/PATCH 1/2] Basic generic time/clocksource code for PowerPC

2007-09-09 Thread Paul Mackerras
Gabriel Paubert writes: > The solution now used by i386/x86-64/sparc64 is > CONFIG_GENERIC_CMOS_UPDATE. Maybe powerpc should be switched > to use something similar, but the generic code has some Yes. I'll turn on CONFIG_GENERIC_CMOS_UPDATE. Do you think it needs to be a config option that can b

Re: [2.6 patch] powerpc: proper defconfig for crosscompiles

2007-09-09 Thread Olof Johansson
On Sun, Sep 09, 2007 at 08:21:17PM +0200, Adrian Bunk wrote: > The trick for finding the right defconfig is neat, but you forgot to > provide an i686_defconfig. ;-) > > More seriously, cross compiling the defconfig is often useful, e.g. for > testing the compilation of patches that touch multip

Re: [2.6 patch] powerpc: proper defconfig for crosscompiles

2007-09-09 Thread Sam Ravnborg
On Sun, Sep 09, 2007 at 08:21:17PM +0200, Adrian Bunk wrote: > The trick for finding the right defconfig is neat, but you forgot to > provide an i686_defconfig. ;-) > > More seriously, cross compiling the defconfig is often useful, e.g. for > testing the compilation of patches that touch multip

[2.6 patch] powerpc: proper defconfig for crosscompiles

2007-09-09 Thread Adrian Bunk
The trick for finding the right defconfig is neat, but you forgot to provide an i686_defconfig. ;-) More seriously, cross compiling the defconfig is often useful, e.g. for testing the compilation of patches that touch multiple architectures, and this patch therefore chooses g5_defconfig if $(C

Re: [PATCH 5/5] Add DMA engine driver for Freescale MPC85xx processors.

2007-09-09 Thread Dan Williams
On 9/7/07, Zhang Wei <[EMAIL PROTECTED]> wrote: > The driver implements DMA engine API for Freescale MPC85xx DMA > controller, which could be used for MEM<-->MEM, IO_ADDR<-->MEM > and IO_ADDR<-->IO_ADDR data transfer. > The driver supports the Basic mode of Freescale MPC85xx DMA controller. > The M