From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Julien Olivain <ju.o@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 21:47:45 +0100 [thread overview]
Message-ID: <ZY8wcbOiR8eYA0qK@landeda> (raw)
In-Reply-To: <783a8cc0ec3eef55827fa3a0bffbb43d@free.fr>
Julien, All,
On 2023-12-29 16:47 +0100, Julien Olivain spake thusly:
> On 24/12/2023 17:58, Yann E. MORIN wrote:
> > 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.
> > 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.
Hm... I also have a pending series about reorganising the docker images:
https://patchwork.ozlabs.org/project/buildroot/list/?series=386976
I did not include a bump of the image yet, to not make it too complex a
series, but the goal was to indeed update to a more recent base image,
like bookworm.
> 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].
Bullseye backports only has 7.2, but Bookworm backports has 8.1.2:
https://packages.debian.org/bookworm-backports/qemu-system-misc
So, if we bump to bookworm, we could get a more recent qemu.
An alternative would be to switch to another distro that is more up to
date, like Fedora (39 has qemu 8.1.3) or Ubuntu (23.10 has qemu 8.0.4).
> Do you think in that specific case I could include add
> BR2_PACKAGE_HOST_QEMU=y in this specific runtime test config?
I would not care, but I think the runtime test infra can not use the
qemu from the build; it only uses the qemu from the system AFAICS; see
support/testing/infra/emulator.py@39.
So, for now, it means we can't have a runtime test for EIF grub2 on
riscv64.
> > Also, it would be nice to extend the readme for grub:
> > boot/grub2/readme.txt
> I added that to my task list!
Wee! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-29 20: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
2023-12-29 20:47 ` Yann E. MORIN [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=ZY8wcbOiR8eYA0qK@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.