From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v4 2/3] tools: mkimage: Add Allwinner eGON support
Date: Thu, 7 Jan 2021 05:36:24 -0700 [thread overview]
Message-ID: <CAPnjgZ2Wtrndjike5heWZ8UsM_OOkJ_naeR3CnBzokiUhUGq6Q@mail.gmail.com> (raw)
In-Reply-To: <20210106092438.3438-3-andre.przywara@arm.com>
On Wed, 6 Jan 2021 at 02:25, Andre Przywara <andre.przywara@arm.com> wrote:
>
> So far we used the separate mksunxiboot tool for generating a bootable
> image for Allwinner SPLs, probably just for historical reasons.
>
> Use the mkimage framework to generate a so called eGON image the
> Allwinner BROM expects.
> The new image type is called "sunxi_egon", to differentiate it
> from the (still to be implemented) secure boot TOC0 image.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> common/image.c | 1 +
> include/image.h | 1 +
> include/sunxi_image.h | 1 +
> tools/Makefile | 1 +
> tools/sunxi_egon.c | 136 ++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 140 insertions(+)
> create mode 100644 tools/sunxi_egon.c
>
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2021-01-07 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 9:24 [PATCH v4 0/3] tools/sunxi: Use mkimage for SPL generation Andre Przywara
2021-01-06 9:24 ` [PATCH v4 1/3] sunxi: Factor out eGON BROM header description Andre Przywara
2021-01-06 9:24 ` [PATCH v4 2/3] tools: mkimage: Add Allwinner eGON support Andre Przywara
2021-01-07 12:36 ` Simon Glass [this message]
2021-01-06 9:24 ` [PATCH v4 3/3] sunxi: Use mkimage for SPL boot image generation Andre Przywara
2021-01-07 12:36 ` Simon Glass
2021-01-07 13:27 ` André Przywara
2021-01-06 21:26 ` [linux-sunxi] [PATCH v4 0/3] tools/sunxi: Use mkimage for SPL generation Jernej Škrabec
2021-01-07 10:43 ` Samuel Holland
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=CAPnjgZ2Wtrndjike5heWZ8UsM_OOkJ_naeR3CnBzokiUhUGq6Q@mail.gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.