bootimg bbclass: don't hardcode 'bzImage' name

In the EFI case there are 2 more architectures besides x86(_64) that may use this class: aarch32, which tends to use 'zImage' and aarch64, which uses 'Image'. Instead of hardcoding those values like the luvOS fork does, use the proper variable.

Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>

diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index ab1d1bdd336592eba6426f492d910f7899abe9d1..dbbf046d3a3168c54d81726ecd50244d3ce0e6de 100644 (file)
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -47,6 +47,8 @@ EFI = "${@bb.utils.contains("MACHINE_FEATURES", "efi", "1", "0", d)}"
 EFI_PROVIDER ?= "grub-efi"
 EFI_CLASS = "${@bb.utils.contains("MACHINE_FEATURES", "efi", "${EFI_PROVIDER}", "", d)}"
 
+KERNEL_IMAGETYPE ??= "bzImage"
+
 # Include legacy boot if MACHINE_FEATURES includes "pcbios" or if it does not
 # contain "efi". This way legacy is supported by default if neither is
 # specified, maintaining the original behavior.
@@ -66,8 +68,8 @@ populate() {
        DEST=$1
        install -d ${DEST}
 
-       # Install bzImage, initrd, and rootfs.img in DEST for all loaders to use.
-       install -m 0644 ${DEPLOY_DIR_IMAGE}/bzImage ${DEST}/vmlinuz
+       # Install kernel, initrd, and rootfs.img in DEST for all loaders to use.
+       install -m 0644 ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE} ${DEST}/vmlinuz
        
        # initrd is made of concatenation of multiple filesystem images
        if [ -n "${INITRD}" ]; then