From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Janne Grunau <j@jannau.net>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Atish Patra <atishp@atishpatra.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH v1 3/3] booti/bootm: riscv: Verify image arch type
Date: Tue, 11 Mar 2025 14:59:06 +0100 [thread overview]
Message-ID: <94b900c3-56bd-41fa-a2de-a47b21e02ee9@gmx.de> (raw)
In-Reply-To: <20250311133506.124914-4-mchitale@ventanamicro.com>
On 11.03.25 14:35, Mayuresh Chitale wrote:
> Unlike ARM and X86, booting 32-bit images on 64-bit CPUs is currently
> not supported for Risc-V. Hence, for bootm, disallow booting a FIT
> or a legacy image that was built for an arch type which is different
> than the current arch and for booti, set the arch type to be the
> same as the current arch.
>
> Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
> ---
> arch/riscv/lib/bootm.c | 4 ++++
> cmd/booti.c | 5 ++++-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/arch/riscv/lib/bootm.c b/arch/riscv/lib/bootm.c
> index 76c610bcee0..90f71bee6a5 100644
> --- a/arch/riscv/lib/bootm.c
> +++ b/arch/riscv/lib/bootm.c
> @@ -94,6 +94,10 @@ static void boot_jump_linux(struct bootm_headers *images, int flag)
> announce_and_cleanup(fake);
>
> if (!fake) {
> + if (images->os.arch != IH_ARCH_DEFAULT) {
> + printf("Image arch not compatible with host arch.\n");
> + hang();
> + }
> if (CONFIG_IS_ENABLED(OF_LIBFDT) && images->ft_len) {
> #ifdef CONFIG_SMP
> ret = smp_call_function(images->ep,
> diff --git a/cmd/booti.c b/cmd/booti.c
> index 1a57fe91397..00921ec4a9d 100644
> --- a/cmd/booti.c
> +++ b/cmd/booti.c
> @@ -131,7 +131,10 @@ int do_booti(struct cmd_tbl *cmdtp, int flag, int argc, char *const argv[])
>
> images.os.os = IH_OS_LINUX;
> if (IS_ENABLED(CONFIG_RISCV_SMODE))
Why do we check for S-mode here? Wouldn't checking CONFIG_RISCV be more
adequate? Think of a micro-controller with only M and U mode.
sipeed_maix_bitm_defconfig has CONFIG_RISCV_MMODE=y, CONFIG_CMD_BOOTI=y.
Cf. 3cedc97479ff ("RISCV: image: Add booti support")
Otherwise looks good.
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> - images.os.arch = IH_ARCH_RISCV;
> + if (IS_ENABLED(CONFIG_64BIT))
> + images.os.arch = IH_ARCH_RISCV64;
> + else
> + images.os.arch = IH_ARCH_RISCV;
> else if (IS_ENABLED(CONFIG_ARM64))
> images.os.arch = IH_ARCH_ARM64;
>
next prev parent reply other threads:[~2025-03-11 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:35 [PATCH v1 0/3] Risc-V 32 bit/64 bit images Mayuresh Chitale
2025-03-11 13:35 ` [PATCH v1 1/3] riscv: image: Add new image type for RV64 Mayuresh Chitale
2025-03-12 11:51 ` Максим Москалец
2025-04-03 10:56 ` Mayuresh Chitale
2025-03-11 13:35 ` [PATCH v1 2/3] riscv: Select appropriate image type Mayuresh Chitale
2025-03-11 13:35 ` [PATCH v1 3/3] booti/bootm: riscv: Verify image arch type Mayuresh Chitale
2025-03-11 13:59 ` Heinrich Schuchardt [this message]
2025-04-03 10:58 ` Mayuresh Chitale
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=94b900c3-56bd-41fa-a2de-a47b21e02ee9@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=atishp@atishpatra.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=ilias.apalodimas@linaro.org \
--cc=j@jannau.net \
--cc=mchitale@ventanamicro.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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