linux-firmware: skip ldflags sanity check

Some of the firmware blobs, for example qcom/apq8016/modem.mbn, are
actually ELF files. We don't want to hold these to our exacting standard
for link flags because we're not building them and they don't run on the
target directly.

Note that as this check parses the output of ${OBJDUMP} -p it behaves
differently with binutils vs llvm.  It looks like binutils bails early
as it doesn't know what the target architecture is, whereas LLVM is more
comprehensive in its support.

Signed-off-by: Ross Burton <ross.burton@arm.com>

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb
index e69e51024f11a33f3b5be63b2399c7aa64652391..f8d8decfe5b96c6044511c3e305dabfa1c6942f9 100644 (file)
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20250917.bb
@@ -2353,7 +2353,10 @@ python populate_packages:prepend () {
 
 # Firmware files are generally not ran on the CPU, so they can be
 # allarch despite being architecture specific
-INSANE_SKIP = "arch"
+INSANE_SKIP += "arch"
+
+# They can also be ELF files, but obviously won't have the linkage we expect
+INSANE_SKIP += "ldflags"
 
 # Don't warn about already stripped files
 INSANE_SKIP:${PN} = "already-stripped"