From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Cc: Heiko Thiery <heiko.thiery@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Simon Glass <sjg@chromium.org>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: [PATCH v2 0/5] binman: Improvements to FIT entry type
Date: Tue, 8 Feb 2022 01:08:03 +0300 [thread overview]
Message-ID: <20220207220809.4497-1-alpernebiyasak@gmail.com> (raw)
I've managed to build images like in doc/chromium/chainload.rst wtih
binman, but ran into an issue with entry expansion in FIT and worked on
it a bit. I also added SetImagePos() because that documentation asks for
precise placement of u-boot.bin inside the FIT and I felt like doing it
as an easier way to know the positions.
I would try to refactor and experiment with FIT things more, but I know
Simon's currently working on converting SPL_FIT_GENERATOR to binman.
Instead I'm just sending things I have already done with some tests
added, hopefully without too many conflicts.
Changes in v2:
- Split reused testSimpleFit code into a helper function
- Check missing_bintools list instead of catching Fdt exceptions
- Add tag: "Reviewed-by: Simon Glass <sjg@chromium.org>"
v1: https://patchwork.ozlabs.org/project/uboot/list/?series=284714
Alper Nebi Yasak (5):
binman: Fix subentry expansion for FIT entry type
binman: Register and check bintools from FIT subentries
binman: Check missing bintools of Section subclasses
binman: Convert FIT entry type to a subclass of Section entry type
binman: Update image positions of FIT subentries
tools/binman/etype/fit.py | 90 ++++++---
tools/binman/etype/section.py | 1 +
tools/binman/ftest.py | 171 +++++++++++++++++-
.../binman/test/220_fit_subentry_bintool.dts | 39 ++++
4 files changed, 266 insertions(+), 35 deletions(-)
create mode 100644 tools/binman/test/220_fit_subentry_bintool.dts
--
2.34.1
next reply other threads:[~2022-02-07 22:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 22:08 Alper Nebi Yasak [this message]
2022-02-07 22:08 ` [PATCH v2 1/5] binman: Fix subentry expansion for FIT entry type Alper Nebi Yasak
2022-02-08 15:05 ` Simon Glass
2022-02-08 20:39 ` Simon Glass
2022-02-07 22:08 ` [PATCH v2 2/5] binman: Register and check bintools from FIT subentries Alper Nebi Yasak
2022-02-08 20:39 ` Simon Glass
2022-02-07 22:08 ` [PATCH v2 3/5] binman: Check missing bintools of Section subclasses Alper Nebi Yasak
2022-02-08 20:39 ` Simon Glass
2022-02-07 22:08 ` [PATCH v2 4/5] binman: Convert FIT entry type to a subclass of Section entry type Alper Nebi Yasak
2022-02-08 20:39 ` Simon Glass
2022-02-14 9:09 ` Jan Kiszka
2022-02-15 12:27 ` Alper Nebi Yasak
2022-02-15 16:50 ` Jan Kiszka
2022-02-15 17:06 ` Jan Kiszka
2022-02-18 16:50 ` Jan Kiszka
2022-02-18 17:34 ` Alper Nebi Yasak
2022-02-19 15:53 ` Simon Glass
2022-02-21 4:40 ` Simon Glass
2022-02-22 18:58 ` Alper Nebi Yasak
2022-02-23 22:59 ` Simon Glass
2022-02-28 11:48 ` Jan Kiszka
2022-02-28 13:51 ` Alper Nebi Yasak
2022-02-28 13:56 ` Simon Glass
2022-02-28 14:14 ` Jan Kiszka
2022-02-07 22:08 ` [PATCH v2 5/5] binman: Update image positions of FIT subentries Alper Nebi Yasak
2022-02-08 20:43 ` Simon Glass
2022-02-23 2:35 ` Simon Glass
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=20220207220809.4497-1-alpernebiyasak@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=jan.kiszka@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