uImage generation: kernel.bbclass vs linux.inc

["Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>]

With the recent changes to kernel.bbclass it seems that uboot-mkimage is
called twice:

linux.inc: do_compile_append()

1/ uses uboot-mkimage to generate generates arch/${ARCH}/boot/uImage


kernel.bbclass: do_deploy()

1/ copies arch/${ARCH}/boot/uImage to
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin

2/ does package_stagefile_shell
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin

3/ uses uboot-mkimage to generate
${DEPLOY_DIR_IMAGE}/uImage-${PV}-${PR}-${MACHINE}.bin

This seems pretty inconsistent! Also, why the hard-coded uImage-xyz file
name, shouldn't we be using KERNEL_IMAGE_BASE_NAME?

To make things a bit more interesting, KERNEL_IMAGE_BASE_NAME is set
differently in kernel.bbclass and linux.inc:

kernel.bbclass :
KERNEL_IMAGE_BASE_NAME =
${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}-${DATETIME}"

linux.inc:
KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}"

Where do we go from here?

Cheers,
Jeremy