treeImage vs cuImage

Hello,

I am upgrading my BSP to 2.6.25 and notice cuImage and treeImage.  The
source files both say Old U-Boot compatibility.

Someone please educate me (or point me to a good URL that explains) as
to what the difference is.

I want to be able to load the kernel image using an older U-Boot and
currently use cuImage for 2.6.23 arch/powerpc (and plain uImage for
older kernels under arch/ppc).

Eventually, I want to generate both an old U-Boot compatible image and a
new U-boot compatible image.

I notice that some boards, the boot support is all in one file, in
others, it is split between cuboot-<board>.c and <board>.c.  In the case
of ebony board, I see support for both cuImage and treeImage.  Is the
strcuture into multiple files to ensure that ebony supports both of
these and new U-boot support as well?

I would like to make my BSP modules lean and clean enough to eventually
send back upstream to kernel.org.

Also, if there are common snags / pitfalls I need to watch out for
switching my BSP and DTS from 2.6.23 to 2.6.25, please warn me.

I am using AMCC PPC405EP processor.


Thanks in advance.


Regards,

Darcy

On Fri, 2008-05-02 at 07:14 -0700, Darcy Watkins wrote:

Hello,

I am upgrading my BSP to 2.6.25 and notice cuImage and treeImage.  The
source files both say Old U-Boot compatibility.

That's wrong.  treeImage isn't for U-Boot.  I should correct that
comment.

Someone please educate me (or point me to a good URL that explains) as
to what the difference is.

treeImage is for the older IBM 4xx eval boards that use the simple
OpenBIOS ROM monitor.  Ebony, Walnut, etc typically came with this
firmware.  cuImage is for boards using older U-Boot.

I want to be able to load the kernel image using an older U-Boot and
currently use cuImage for 2.6.23 arch/powerpc (and plain uImage for
older kernels under arch/ppc).

You want cuImage then.

Eventually, I want to generate both an old U-Boot compatible image and a
new U-boot compatible image.

You'll get this by default when you build for cuImage.  The cuImage will
contain the vmlinux and the dtb wrapped into a single file for use with
older U-Boots.  You can just use the vmlinux itself and provide the dtb
separately for newer. (I think.)

I notice that some boards, the boot support is all in one file, in
others, it is split between cuboot-<board>.c and <board>.c.  In the case
of ebony board, I see support for both cuImage and treeImage.  Is the
strcuture into multiple files to ensure that ebony supports both of
these and new U-boot support as well?

The boards that are split are for support with multiple different
firmwares, or because pieces of those can be shared with different
boards.

I would like to make my BSP modules lean and clean enough to eventually
send back upstream to kernel.org.

Great!

Also, if there are common snags / pitfalls I need to watch out for
switching my BSP and DTS from 2.6.23 to 2.6.25, please warn me.

I am using AMCC PPC405EP processor.

405EP should be supported soon.  I have a Taihu board, I just need to
port it.  After that, you should be able to either reuse or mostly copy
it.  But if you beat me to it, I won't complain at all :)

josh