From 39762c00bf95c9f2a026c290d2aa8ee13b33e172 Mon Sep 17 00:00:00 2001 From: Tyler Baker Date: Tue, 12 May 2026 21:23:04 -0400 Subject: [PATCH] image_types_qcom: include *.img in qcomflash bundle whitelist The boot-firmware deploy loop in create_qcomflash_pkg only picks up a fixed set of file patterns (*.elf, *.mbn*, *.melf*, *.fv, named *.bin families, etc.). Boards whose LUN payloads are deployed as raw *.img files therefore never make it into the qcomflash tarball, even though the firmware recipe deploys them into QCOM_BOOT_FILES_SUBDIR. In particular, the Thundercomm RUBIK Pi 3 has LUN 6 partitions backed by rubikpi_config.img, devcfg_full.img, rubikpi_dtso.img and splash.img. Without this whitelist entry these files are silently dropped from the bundle and the resulting flashable image is incomplete; this was previously being worked around in a downstream bbappend on core-image-base, which is the wrong layer. Add *.img to the find expression at the same precedence as the other plain extension globs. The change is purely additive: existing targets that do not deploy any *.img files into QCOM_BOOT_FILES_SUBDIR see no behavioural change, and the exclusions inside the \( ... \) ELF group are unaffected. Link: https://github.com/qualcomm-linux/meta-qcom-3rdparty/pull/41#discussion_r3230762891 Signed-off-by: Tyler Baker --- classes-recipe/image_types_qcom.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/classes-recipe/image_types_qcom.bbclass b/classes-recipe/image_types_qcom.bbclass index 0a4b57b9d..b936e9bae 100644 --- a/classes-recipe/image_types_qcom.bbclass +++ b/classes-recipe/image_types_qcom.bbclass @@ -101,6 +101,7 @@ create_qcomflash_pkg() { -name '*.mbn*' -o \ -name '*.melf*' -o \ -name '*.fv' -o \ + -name '*.img' -o \ -name 'cdt_*.bin' -o \ -name 'logfs_*.bin' -o \ -name 'qsahara_*.xml' -o \