From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: u-boot-amlogic@groups.io, linux-amlogic@lists.infradead.org,
Christian Hewitt <christianshewitt@gmail.com>,
Simon Glass <sjg@chromium.org>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [PATCH v2 0/1] meson: Demonstration of using binman to produce the image
Date: Sat, 1 Apr 2023 19:25:43 +1300 [thread overview]
Message-ID: <20230401062545.2267422-1-sjg@chromium.org> (raw)
The Odroid-C2 is quite a complicated image with many steps. It is an ideal
example for how Binman can be used.
Add a binman description and update the instructions accordingly.
Changes in v2:
- Rebase to -next
Simon Glass (1):
RFC: Move Odroid-C2 to use binman to produce the image
arch/arm/dts/meson-sm1-odroid-c4-u-boot.dtsi | 107 ++++++++++++++++
arch/arm/mach-meson/Kconfig | 1 +
doc/board/amlogic/odroid-c4.rst | 127 +++++--------------
tools/binman/etype/aml_encrypt.py | 124 ++++++++++++++++++
tools/binman/ftest.py | 3 +
tools/binman/missing-blob-help | 6 +
tools/binman/test/213_aml_encrypt.dts | 38 ++++++
tools/binman/test/214_list_no_dtb.dts | 23 ++++
8 files changed, 337 insertions(+), 92 deletions(-)
create mode 100644 tools/binman/etype/aml_encrypt.py
create mode 100644 tools/binman/test/213_aml_encrypt.dts
create mode 100644 tools/binman/test/214_list_no_dtb.dts
--
2.40.0.348.gf938b09366-goog
next reply other threads:[~2023-04-01 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 6:25 Simon Glass [this message]
2023-04-01 18:54 [PATCH v2 0/1] meson: Demonstration of using binman to produce the image Simon Glass
2023-04-01 21:27 ` Mark Kettenis
2023-04-02 2:41 ` Simon Glass
2023-04-03 8:10 ` Christian Hewitt
2023-04-05 18:38 ` Simon Glass
2023-04-08 3:34 ` Da Xue
2023-04-19 1:49 ` Simon Glass
2023-08-30 17:53 Ferass El Hafidi
2023-08-31 3:37 ` Simon Glass
2023-08-31 7:54 ` neil.armstrong
2023-08-31 10:25 ` Ferass El Hafidi
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=20230401062545.2267422-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=alpernebiyasak@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for NNTP newsgroup(s).