From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/4] ARM: k3: fix k3img dependencies
Date: Tue, 02 Dec 2025 16:58:24 +0100 [thread overview]
Message-ID: <20251202-k3-deps-v1-0-68404d3b2c70@pengutronix.de> (raw)
This series fixes a dependency problem in the K3 image generation. The
k3img tool takes several files as input, but only the barebox image is
actually a dependency, so when (only) one of the other files change the
final image is not re-generated.
While at it we can make some input files SoC specific which means we no
longer have to specify them per board, saving one line per board and
file in Makefile.k3
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (4):
ARM: K3: am62l: don't put sysfwdata into 1st stage image
ARM: k3: make some firmware files SoC specific
ARM: k3: am62l: Add dedicated config option for OP-TEE
ARM: k3: am62l: fix dependencies on k3img input files
firmware/Kconfig | 4 ++++
images/Makefile.k3 | 62 ++++++++++++++++++++++++------------------------------
2 files changed, 31 insertions(+), 35 deletions(-)
---
base-commit: 8661354d7ef744e01b6f07b1b0114482c5e8f561
change-id: 20251202-k3-deps-eeff63389f70
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next 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 Sascha Hauer [this message]
2025-12-02 15:58 ` [PATCH 1/4] ARM: K3: am62l: don't put sysfwdata into 1st stage image Sascha Hauer
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-0-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