From: Sunil V L <sunilvl@ventanamicro.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, Ard Biesheuvel <ardb@kernel.org>,
Anup Patel <apatel@ventanamicro.com>,
Atish Patra <atishp@rivosinc.com>,
Abner Chang <abner.chang@hpe.com>,
Jessica Clarke <jrtc27@jrtc27.com>,
Sunil V L <sunilvl@ventanamicro.com>
Subject: [RFC PATCH 0/1] RISCV_EFI_BOOT_PROTOCOL support in U-boot
Date: Wed, 26 Jan 2022 16:36:10 +0530 [thread overview]
Message-ID: <20220126110611.33325-1-sunilvl@ventanamicro.com> (raw)
This patch adds the support in u-boot for new RISCV_EFI_BOOT_PROTOCOL for RISC-V
UEFI platforms. This protocol is required to communicate the boot hart ID to the
bootloader/kernel which need to follow the EFI calling conventions.
The latest draft spec of this new protocol is available at
https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc2/RISCV_UEFI_PROTOCOL-spec.pdf
This u-boot patch can be found in:
riscv_boot_protocol_rfc_v1 branch at https://github.com/vlsunil/u-boot.git
This patch is tested in qemu. To fully test the feature, we need
Linux changes which consume this protocol.
The linux patch can be found in:
riscv_boot_protocol_rfc_v1 branch at https://github.com/vlsunil/linux.git
Sunil V L (1):
efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support
include/efi_api.h | 4 +++
include/efi_loader.h | 2 ++
include/efi_riscv.h | 16 +++++++++
lib/efi_loader/Kconfig | 7 ++++
lib/efi_loader/Makefile | 1 +
lib/efi_loader/efi_riscv.c | 69 ++++++++++++++++++++++++++++++++++++++
lib/efi_loader/efi_setup.c | 6 ++++
7 files changed, 105 insertions(+)
create mode 100644 include/efi_riscv.h
create mode 100644 lib/efi_loader/efi_riscv.c
--
2.25.1
next reply other threads:[~2022-01-26 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:06 Sunil V L [this message]
2022-01-26 11:06 ` [RFC PATCH 1/1] efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support Sunil V L
2022-01-26 14:01 ` Jessica Clarke
2022-01-27 6:35 ` Heinrich Schuchardt
2022-01-27 8:44 ` Heinrich Schuchardt
2022-01-28 5:08 ` Sunil V L
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=20220126110611.33325-1-sunilvl@ventanamicro.com \
--to=sunilvl@ventanamicro.com \
--cc=abner.chang@hpe.com \
--cc=apatel@ventanamicro.com \
--cc=ardb@kernel.org \
--cc=atishp@rivosinc.com \
--cc=jrtc27@jrtc27.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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