From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 2/2] ARM: k3r5: Honour CONFIG_EXTRA_FIRMWARE_DIR
Date: Fri, 14 Mar 2025 10:45:59 +0100 [thread overview]
Message-ID: <20250314094559.3631184-2-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20250314094559.3631184-1-s.hauer@pengutronix.de>
barebox expects the firmware blobs in CONFIG_EXTRA_FIRMWARE_DIR, but the
ti-fs-firmware is searched for in $(srctree)/firmware/ instead. Use
$(FIRMWARE_DIR) instead to use the correct directory when changed from
the default.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
images/Makefile.k3 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/images/Makefile.k3 b/images/Makefile.k3
index 466a84af99..fd42877837 100644
--- a/images/Makefile.k3
+++ b/images/Makefile.k3
@@ -25,9 +25,9 @@ ifdef CONFIG_MACH_K3_CORTEX_R5
SYSFWDATA_am625=$(objtree)/arch/arm/mach-k3/combined-sysfw-cfg-am625.k3cfg
DMDATA_am625=$(objtree)/arch/arm/mach-k3/combined-dm-cfg-am625.k3cfg
-SYSFW_am625_hs_fs=$(srctree)/firmware/ti-fs-firmware-am62x-hs-fs-enc.bin
-SYSFW_am625_gp=$(srctree)/firmware/ti-fs-firmware-am62x-gp.bin
-INNERDATA_am625=$(srctree)/firmware/ti-fs-firmware-am62x-hs-fs-cert.bin
+SYSFW_am625_hs_fs=$(FIRMWARE_DIR)/ti-fs-firmware-am62x-hs-fs-enc.bin
+SYSFW_am625_gp=$(FIRMWARE_DIR)/ti-fs-firmware-am62x-gp.bin
+INNERDATA_am625=$(FIRMWARE_DIR)/ti-fs-firmware-am62x-hs-fs-cert.bin
KEY_custmpk=$(srctree)/arch/arm/mach-k3/custMpk.pem
KEY_degenerate=$(srctree)/arch/arm/mach-k3/ti-degenerate-key.pem
--
2.39.5
prev parent reply other threads:[~2025-03-14 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 9:45 [PATCH 1/2] firmware: export firmware directory Sascha Hauer
2025-03-14 9:45 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250314094559.3631184-2-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox