Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] boot/grub2: add RISC-V 64bit EFI support
Date: Fri, 29 Dec 2023 16:47:38 +0100	[thread overview]
Message-ID: <783a8cc0ec3eef55827fa3a0bffbb43d@free.fr> (raw)
In-Reply-To: <ZYhjQtmfpGir8zsQ@landeda>

Hi Yann, All,

On 24/12/2023 17:58, Yann E. MORIN wrote:
> Julien, All,
> 
> On 2023-12-23 22:29 +0100, Julien Olivain spake thusly:
>> Grub can be built as a RISC-V UEFI application since commit [1]. This
>> commit was first included in grub version 2.04.
>> 
>> This commit enables this support.
>> 
>> [1] 
>> https://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=f1957dc8a3347278a095bc8f44197662559a8ba3
>> 
>> Signed-off-by: Julien Olivain <ju.o@free.fr>
> 
> Oh, I forgot to add: it would be awesome if you coulde extend the
> existing runtiem test to include a risc-v test:
>     support/testing/tests/boot/test_grub.py

In fact, I already had a test ready. I didn't send it because
the current Buildroot docker image does not include qemu with
RISC-V system emulation. See [1]. I sent a patch, accepted in
commit [2] to enable this support, but the image was not regenerated
since then.

Moreover, this RISCV 64bit EFI boot requires qemu >= 8.0.0.
Buildroot docker image is still on Debian 11 bullseye, which
includes qemu 5.2.0. Debian 12.4 bookworm only includes qemu 7.2.0,
see [3].

Do you think in that specific case I could include add
BR2_PACKAGE_HOST_QEMU=y in this specific runtime test config?

> Also, it would be nice to extend the readme for grub:
>     boot/grub2/readme.txt

I added that to my task list!

> Regards,
> Yann E. MORIN.
> 

Best regards,

Julien.

[1] 
https://gitlab.com/buildroot.org/buildroot/-/blob/master/.gitlab-ci.yml?ref_type=heads#L4
[2] 
https://gitlab.com/buildroot.org/buildroot/-/commit/93c7b55c778e3dd4d84945918e5d97d5f56256c5
[3] https://packages.debian.org/bookworm/qemu-system-misc
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-12-29 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 19:41 [Buildroot] [PATCH 1/2] boot/grub2: add RISC-V 64bit EFI support Julien Olivain
2023-12-23 19:41 ` [Buildroot] [PATCH 2/2] configs/qemu_riscv64_virt_efi: new defconfig Julien Olivain
2023-12-23 21:29 ` [Buildroot] [PATCH v2 1/2] boot/grub2: add RISC-V 64bit EFI support Julien Olivain
2023-12-23 21:29   ` [Buildroot] [PATCH v2 2/2] configs/qemu_riscv64_virt_efi: new defconfig Julien Olivain
2023-12-24 16:57     ` Yann E. MORIN
2023-12-24 16:56   ` [Buildroot] [PATCH v2 1/2] boot/grub2: add RISC-V 64bit EFI support Yann E. MORIN
2023-12-24 16:58   ` Yann E. MORIN
2023-12-29 15:47     ` Julien Olivain [this message]
2023-12-29 20:47       ` Yann E. MORIN

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=783a8cc0ec3eef55827fa3a0bffbb43d@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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