Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Simon Glass <sjg@chromium.org>
Cc: neil.armstrong@linaro.org, sjg@chromium.org,
	u-boot-amlogic@groups.io, u-boot@lists.denx.de,
	alpernebiyasak@gmail.com, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 0/1] meson: Demonstration of using binman to produce the image
Date: Sat, 01 Apr 2023 23:27:58 +0200	[thread overview]
Message-ID: <87zg7rb8dd.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <20230401185458.2280200-1-sjg@chromium.org> (message from Simon Glass on Sun, 2 Apr 2023 06:54:57 +1200)

> From: Simon Glass <sjg@chromium.org>
> Date: Sun,  2 Apr 2023 06:54:57 +1200
> 
> The Odroid-C2 is quite a complicated image with many steps. It is an ideal
> example for how Binman can be used.

You say Odroid-C2, but the patches seem to address the Odroid-C4...

> 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
> 
> 

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  parent reply	other threads:[~2023-04-01 21:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 18:54 [PATCH v2 0/1] meson: Demonstration of using binman to produce the image Simon Glass
2023-04-01 18:54 ` [PATCH v2 1/1] RFC: Move Odroid-C2 to use " Simon Glass
2023-04-01 20:53   ` Steev Klimaszewski
2023-04-03  7:31   ` Neil Armstrong
2023-04-05 18:38     ` Simon Glass
2023-04-05 22:06       ` Mark Kettenis
2023-04-06  7:44       ` neil.armstrong
2023-04-01 21:27 ` Mark Kettenis [this message]
     [not found]   ` <CAPnjgZ0Js43JOi3xaeY8tYuELSPXWL-PCBq1-iANLs1074MzbQ@mail.gmail.com>
2023-04-03  8:10     ` [PATCH v2 0/1] meson: Demonstration of using " Christian Hewitt
2023-04-05 18:38       ` Simon Glass
2023-04-08  3:34         ` Da Xue
2023-04-19  1:49           ` Simon Glass
  -- strict thread matches above, loose matches on Subject: below --
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
2023-04-01  6:25 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=87zg7rb8dd.fsf@bloch.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=alpernebiyasak@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sjg@chromium.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