From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 1/4] ARM: K3: am62l: don't put sysfwdata into 1st stage image
Date: Tue, 02 Dec 2025 16:58:25 +0100 [thread overview]
Message-ID: <20251202-k3-deps-v1-1-68404d3b2c70@pengutronix.de> (raw)
In-Reply-To: <20251202-k3-deps-v1-0-68404d3b2c70@pengutronix.de>
SYSFWDATA is not needed for the tiboot3 stage. Drop it.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
images/Makefile.k3 | 2 --
1 file changed, 2 deletions(-)
diff --git a/images/Makefile.k3 b/images/Makefile.k3
index d2b7be7ca017325dfc8700f556c7d17760c8aa1e..27ddb5d0b68ac6411165847f1fab18c38f48dc04 100644
--- a/images/Makefile.k3
+++ b/images/Makefile.k3
@@ -85,7 +85,6 @@ INNERDATA_start_am62lx_evm.pblb.k3_am62lx_img=$(INNERDATA_am62lx)
KEY_start_am62lx_evm.pblb.k3_am62lx_img=$(KEY_custmpk)
SYSFW_start_am62lx_evm.pblb.k3_am62lx_tiboot3_img=$(SYSFW_am62lx_hs_fs)
-SYSFWDATA_start_am62lx_evm.pblb.k3_am62lx_tiboot3_img=$(SYSFWDATA_am62lx)
INNERDATA_start_am62lx_evm.pblb.k3_am62lx_tiboot3_img=$(INNERDATA_am62lx)
TFA_BL1_start_am62lx_evm.pblb.k3_am62lx_tiboot3_img=$(FIRMWARE_DIR)/am62lx-bl1.bin
KEY_start_am62lx_evm.pblb.k3_am62lx_tiboot3_img=$(KEY_custmpk)
@@ -134,7 +133,6 @@ quiet_cmd_k3_am62lx_tiboot3_image = K3_am62lx_tiboot3_IMG $@
$(srctree)/scripts/k3img \
$(TFA_BL1_$(@F)):1:16:160:70800000 \
$(SYSFW_$(@F)):2:0:0:00040000 \
- $(SYSFWDATA_$(@F)):18:0:0:0006c000 \
$(INNERDATA_$(@F)):3:0:0:00000000 \
--key "$(KEY_$(@F))" \
--out $@
--
2.47.3
next prev parent reply other threads:[~2025-12-02 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 15:58 [PATCH 0/4] ARM: k3: fix k3img dependencies Sascha Hauer
2025-12-02 15:58 ` Sascha Hauer [this message]
2025-12-02 15:58 ` [PATCH 2/4] ARM: k3: make some firmware files SoC specific Sascha Hauer
2025-12-02 15:58 ` [PATCH 3/4] ARM: k3: am62l: Add dedicated config option for OP-TEE Sascha Hauer
2025-12-02 15:58 ` [PATCH 4/4] ARM: k3: am62l: fix dependencies on k3img input files Sascha Hauer
2025-12-03 11:56 ` [PATCH 0/4] ARM: k3: fix k3img dependencies Sascha Hauer
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=20251202-k3-deps-v1-1-68404d3b2c70@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