From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [efitools PATCH 1/1] Make.rules: enable building on riscv64
Date: Tue, 31 Aug 2021 10:33:20 +0200 [thread overview]
Message-ID: <fb11e204-a306-8857-08a0-267d28c12ef1@canonical.com> (raw)
In-Reply-To: <20210401165754.131719-1-xypron.glpk@gmx.de>
On 4/1/21 6:57 PM, Heinrich Schuchardt wrote:
> We can use just the same flags as for aarch64.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> RISC-V patches for gnu-efi are not yet accepted in upstream. Cf.
>
> [Gnu-efi-discuss] [PATCH 1/1] Initial support for RISCV64
> https://sourceforge.net/p/gnu-efi/mailman/gnu-efi-discuss/thread/20210401153553.103286-1-xypron.glpk%40gmx.de/#msg37253360
> [Gnu-efi-discuss] [PATCH 1/1] Undefined Status in LibGetVariableAndSize()
> https://sourceforge.net/p/gnu-efi/mailman/gnu-efi-discuss/thread/20210319162557.334645-1-xypron.glpk%40gmx.de/#msg37243995
>
> You can use
> https://github.com/xypron/gnu-efi/releases/tag/riscv64-2021-04-01 for
> building sbsigntools and efitools.
Hello James,
I did not see any review from you on this patch yet.
https://lore.kernel.org/linux-efi/?q=Make.rules%3A+enable+building+on+riscv64
gnu-efi 3.0.14 has been released with RISC-V support.
Best regards
Heinrich
> ---
> Make.rules | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Make.rules b/Make.rules
> index 903a5a4..69bd3bd 100644
> --- a/Make.rules
> +++ b/Make.rules
> @@ -10,6 +10,8 @@ else ifeq ($(ARCH),aarch64)
> ARCH3264 =
> else ifeq ($(ARCH),arm)
> ARCH3264 =
> +else ifeq ($(ARCH),riscv64)
> +ARCH3264 =
> else
> $(error unknown architecture $(ARCH))
> endif
> @@ -56,6 +58,11 @@ ifeq ($(ARCH),aarch64)
> FORMAT = -O binary
> endif
>
> +ifeq ($(ARCH),riscv64)
> + LDFLAGS += --defsym=EFI_SUBSYSTEM=0x0a
> + FORMAT = -O binary
> +endif
> +
> %.efi: %.so
> $(OBJCOPY) -j .text -j .sdata -j .data -j .dynamic -j .dynsym \
> -j .rel -j .rela -j .rel.* -j .rela.* -j .rel* -j .rela* \
> --
> 2.30.2
>
prev parent reply other threads:[~2021-08-31 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 16:57 [efitools PATCH 1/1] Make.rules: enable building on riscv64 Heinrich Schuchardt
2021-08-31 8:33 ` Heinrich Schuchardt [this message]
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=fb11e204-a306-8857-08a0-267d28c12ef1@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).