From: Jan Kiszka <jan.kiszka@siemens.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Andrew Davis <afd@ti.com>, Bao Cheng Su <baocheng.su@siemens.com>,
Simon Glass <sjg@chromium.org>
Subject: [PATCH 0/3] iot2050: Re-unify its configs and build processes
Date: Mon, 5 Jun 2023 16:39:50 +0200 [thread overview]
Message-ID: <cover.1685975993.git.jan.kiszka@siemens.com> (raw)
This restores the possibility to build firmware images for both PG1 and
PG2-based IOT2050 devices in one run. We still end up with different
binaries, but the the build is now fed again from a single defconfig.
Should simplify maintenance and will also simplify our generation
tooling around it.
Jan
CC: Simon Glass <sjg@chromium.org>
Jan Kiszka (3):
binman: Allow to define custom arguments
iot2050: Use binman in signing script
boards: siemens: iot2050: Unify PG1 and PG2/M.2 configurations again
Makefile | 1 +
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 299 ++++++++++--------
board/siemens/iot2050/Kconfig | 30 +-
board/siemens/iot2050/board.c | 14 +-
board/siemens/iot2050/config.mk | 6 +-
...ot2050_pg1_defconfig => iot2050_defconfig} | 3 +-
configs/iot2050_pg2_defconfig | 150 ---------
doc/board/siemens/iot2050.rst | 29 +-
tools/iot2050-sign-fw.sh | 13 +-
9 files changed, 203 insertions(+), 342 deletions(-)
rename configs/{iot2050_pg1_defconfig => iot2050_defconfig} (97%)
delete mode 100644 configs/iot2050_pg2_defconfig
--
2.35.3
next reply other threads:[~2023-06-05 14:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:39 Jan Kiszka [this message]
2023-06-05 14:39 ` [PATCH 1/3] binman: Allow to define custom arguments Jan Kiszka
2023-06-12 21:17 ` Simon Glass
2023-06-15 10:26 ` Jan Kiszka
2023-06-15 10:55 ` Simon Glass
2023-06-15 11:08 ` Jan Kiszka
2023-06-15 11:19 ` Simon Glass
2023-06-15 11:20 ` Jan Kiszka
2023-06-15 11:38 ` Simon Glass
2023-06-15 11:46 ` Jan Kiszka
2023-06-16 15:42 ` Jan Kiszka
2023-06-19 12:36 ` Simon Glass
2023-06-19 13:28 ` Jan Kiszka
2023-06-19 14:09 ` Simon Glass
2023-06-19 15:09 ` Jan Kiszka
2023-06-20 10:11 ` Simon Glass
2023-06-20 10:37 ` Jan Kiszka
2023-06-20 14:36 ` Simon Glass
2023-06-20 17:05 ` Jan Kiszka
2023-06-20 17:12 ` Simon Glass
2023-06-05 14:39 ` [PATCH 2/3] iot2050: Use binman in signing script Jan Kiszka
2023-06-12 21:17 ` Simon Glass
2023-06-05 14:39 ` [PATCH 3/3] boards: siemens: iot2050: Unify PG1 and PG2/M.2 configurations again Jan Kiszka
2023-06-12 21:17 ` Simon Glass
2023-06-15 11:22 ` Jan Kiszka
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=cover.1685975993.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=afd@ti.com \
--cc=baocheng.su@siemens.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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