From: Mayuresh Chitale <mchitale@ventanamicro.com>
To: u-boot@lists.denx.de
Cc: Mayuresh Chitale <mchitale@ventanamicro.com>,
Tom Rini <trini@konsulko.com>,
Maxim Moskalets <maximmosk4@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Raymond Mao <raymond.mao@linaro.org>,
Simon Glass <sjg@chromium.org>,
Julien Masson <jmasson@baylibre.com>,
Paul HENRYS <paul.henrys_ext@softathome.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Yu-Chien Peter Lin <peter.lin@sifive.com>,
Janne Grunau <j@jannau.net>,
Sam Protsenko <semen.protsenko@linaro.org>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [RFC PATCH 0/3] Risc-V 32 bit/64 bit images
Date: Fri, 21 Feb 2025 12:58:50 +0000 [thread overview]
Message-ID: <20250221125855.300717-1-mchitale@ventanamicro.com> (raw)
This series adds support for building different images for 32-bit vs
64-bit Risc-V CPUs and also for verifying the target arch of an image
before booting it.
Mayuresh Chitale (3):
riscv: image: Add new image type for RV64
riscv: Select appropriate image type
riscv: booti/bootm: Verify image arch type
arch/riscv/dts/binman.dtsi | 14 ++++++++++----
arch/riscv/include/asm/u-boot.h | 4 ++++
arch/riscv/lib/bootm.c | 4 ++++
boot/image.c | 3 ++-
cmd/booti.c | 5 ++++-
include/image.h | 1 +
6 files changed, 25 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2025-02-21 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 12:58 Mayuresh Chitale [this message]
2025-02-21 12:58 ` [RFC PATCH 1/3] riscv: image: Add new image type for RV64 Mayuresh Chitale
2025-02-21 12:58 ` [RFC PATCH 2/3] riscv: Select appropriate image type Mayuresh Chitale
2025-02-21 12:58 ` [RFC PATCH 3/3] riscv: booti/bootm: Verify image arch type Mayuresh Chitale
2025-02-22 5:25 ` Heinrich Schuchardt
2025-02-24 6:21 ` 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=20250221125855.300717-1-mchitale@ventanamicro.com \
--to=mchitale@ventanamicro.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=ilias.apalodimas@linaro.org \
--cc=j@jannau.net \
--cc=jmasson@baylibre.com \
--cc=maximmosk4@gmail.com \
--cc=mkorpershoek@baylibre.com \
--cc=paul.henrys_ext@softathome.com \
--cc=peter.lin@sifive.com \
--cc=raymond.mao@linaro.org \
--cc=rick@andestech.com \
--cc=semen.protsenko@linaro.org \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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