[U-Boot] understanding mkimage a bit more

[Charles Krinke]

I can create a uImage with mkimage with "-C gzip" and it boots fine.
If I use "-C none", it hangs on boot with bootm in u-boot. The
arguments below come directly from the linux-2.6.35.12 kernel which
creates uImage from vmlinux.bin.gz (which is already compressed, I
know, but that is a different issue).

In trying to work through how mkimage, uboot, objdump and objcopy
interact, my The question becomes "Why does a uImage created with -C
gzip boot with bootm and a uImage created with -C none hang?"

In both
$ scripts/mkuboot.sh -A ppc -O linux -T kernel -C gzip -a 0x00000000
-e 0x00000000 -n Linux-2.6.35.12-svn438 -d ./vmlinux.bin.gz
/tftpboot/uImage
Image Name:   Linux-2.6.35.12-svn438
Created:      Fri May  6 09:05:42 2011
Image Type:   PowerPC Linux Kernel Image (gzip compressed)
Data Size:    1714808 Bytes = 1674.62 kB = 1.64 MB
Load Address: 0x00000000
Entry Point:  0x00000000

$ scripts/mkuboot.sh -A ppc -O linux -T kernel -C none -a 0x00000000
-e 0x00000000 -n Linux-2.6.35.12-svn438 -d ./vmlinux.bin.gz
/tftpboot/uImage
Image Name:   Linux-2.6.35.12-svn438
Created:      Fri May  6 09:10:31 2011
Image Type:   PowerPC Linux Kernel Image (uncompressed)
Data Size:    1714808 Bytes = 1674.62 kB = 1.64 MB
Load Address: 0x00000000
Entry Point:  0x00000000
ckrinke at hwa:~/svn/trunk/linux-2.6.35.12$
ckrinke at hwa:~/svn/trunk/linux-2.6.35.12$

-- 
Charles Krinke