Andrea Adami wrote:
Random question: It's really easy to make extra uImage files, ...
Do you mean uImage *only* for kexecboot?
No, I meant that linux-kexec boots generates a zImage *and* uImage at
the same time.
Warning: horrible linewrap ahead
It's a matter of doing
DEPENDS += "uboot-mkimage-whatchamacallit""
do_compile_append() {
if test -e arch/${ARCH}/boot/compressed/vmlinux ; then
${OBJCOPY} -O binary -R .note -R .comment -S
arch/${ARCH}/boot/compressed/vmlinux linux.bin
uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C none
-a ${UBOOT_LOADADDRESS} -e ${UBOOT_ENTRYPOINT} -n
"${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin arch/${ARCH}/boot/uImage
rm -f linux.bin
else
${OBJCOPY} -O binary -R .note -R .comment -S vmlinux linux.bin
rm -f linux.bin.gz
gzip -9 linux.bin
uboot-mkimage -A ${UBOOT_ARCH} -O linux -T kernel -C gzip
-a ${UBOOT_LOADADDRESS} -e ${UBOOT_ENTRYPOINT} -n
"${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin.gz arch/${ARCH}/boot/uImage
rm -f linux.bin.gz
fi
}
and fishing it ot of arch/${ARCH}/boot/ in do_deploy
If you refer to http://bugs.openembedded.net/show_bug.cgi?id=4544 ,
yes, it is really easy.
By mistake, I forgot there some bits about kexecboot too...
P.S. during initramfs tests, I got used to gzip the zImage again doing
the mkimage step: this squeezes out a couple of kb more, thus allowing
to fit the 1408k kernel-partition- size given by u-boot. Compressing
the decompressor...unortodox at least...
Squeezing out extra bits can be done later, let's get the
linux-kexecboot recipe sorted out first so other machines (e.g. non
zaurus pdas to start with) can start using it.
regards,
Koen
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
