[PATCH v2 1/1] RFC: Move Odroid-C2 to use binman to produce the image

Steev Klimaszewski steev at kali.org
Sat Apr 1 22:53:18 CEST 2023


Hi Simon,

On Sat, Apr 1, 2023 at 1:55 PM Simon Glass <sjg at chromium.org> wrote:
>
> This shows how binman can be used to replace the long and complicated
> instructions with an automated build. It is still complicated to read
> but users don't have to worry about the details.
>
> It needs some tidying up and only supports Odroid-C2 at present.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
>
> Changes in v2:
> - Rebase to -next
>
>  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
>
This says C2 and only supports C2, but you're modifying th C4
documentation?  I'm just a random distro maintainer with interest in
this and want to be clear is all.


More information about the U-Boot mailing list