From: Andre Przywara <andre.przywara@arm.com>
To: Samuel Holland <samuel@sholland.org>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
Icenowy Zheng <icenowy@aosc.io>, Tom Rini <trini@konsulko.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v3 1/4] mkimage: add a flag to describe whether -A is specified
Date: Tue, 19 Oct 2021 11:49:45 +0100 [thread overview]
Message-ID: <20211019114945.01ccdaf7@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20211015015308.65265-2-samuel@sholland.org>
On Thu, 14 Oct 2021 20:53:04 -0500
Samuel Holland <samuel@sholland.org> wrote:
Hi,
> From: Icenowy Zheng <icenowy@aosc.io>
>
> The sunxi_egon type used to take no -A argument (because we assume sunxi
> targets are all ARM). However, as Allwinner D1 appears as the first
> RISC-V sunxi target, we need to support -A; in addition, as external
> projects rely on U-Boot mkimage to generate sunxi eGON.BT0 header, we
> need to keep compatibility with command line without -A.
>
> As the default value of arch in mkimage is not proper (IH_ARCH_PPC
> instead of IH_ARCH_INVALID), to keep more compatibility, add an Aflag
> field to image parameters to describe whether an architecture is
> explicitly specified.
So there was some nitpic^Wdiscussion about the uppercase in the variable
name, where Icenowy proposed arch_flag instead. Shall this be changed
still? If that's the only thing, I am happy to do it while merging.
Btw: Shall this (and the TOC0) series go through the sunxi tree?
Cheers,
Andre
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> (no changes since v1)
>
> tools/imagetool.h | 1 +
> tools/mkimage.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/tools/imagetool.h b/tools/imagetool.h
> index e229a34ffc..5dc28312c2 100644
> --- a/tools/imagetool.h
> +++ b/tools/imagetool.h
> @@ -51,6 +51,7 @@ struct image_tool_params {
> int pflag;
> int vflag;
> int xflag;
> + int Aflag;
> int skipcpy;
> int os;
> int arch;
> diff --git a/tools/mkimage.c b/tools/mkimage.c
> index fbe883ce36..cfd97b046c 100644
> --- a/tools/mkimage.c
> +++ b/tools/mkimage.c
> @@ -171,6 +171,7 @@ static void process_args(int argc, char **argv)
> show_valid_options(IH_ARCH);
> usage("Invalid architecture");
> }
> + params.Aflag = 1;
> break;
> case 'b':
> if (add_content(IH_TYPE_FLATDT, optarg)) {
next prev parent reply other threads:[~2021-10-19 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 1:53 [PATCH v3 0/4] mkimage: sunxi_egon: add riscv support Samuel Holland
2021-10-15 1:53 ` [PATCH v3 1/4] mkimage: add a flag to describe whether -A is specified Samuel Holland
2021-10-19 10:49 ` Andre Przywara [this message]
2021-10-19 13:17 ` Samuel Holland
2021-10-19 14:11 ` Simon Glass
2021-10-15 1:53 ` [PATCH v3 2/4] mkimage: sunxi_egon: refactor for multi-architecture support Samuel Holland
2021-10-15 1:53 ` [PATCH v3 3/4] mkimage: sunxi_egon: add support for riscv Samuel Holland
2021-10-15 1:53 ` [PATCH v3 4/4] sunxi: specify architecture when generating SPL boot image 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=20211019114945.01ccdaf7@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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