[Bug 1876620] Re: Enable riscv64 build

[Dimitri John Ledkov]

Given there is no secureboot support with lockdown for the platform as
far as I know, it is premature to sign the grub2 for riscv64.

Also I think we'd want these patches from upstream. By taking 2.06 or
like master for the riscv64 build.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1876620

Title:
  Enable riscv64 build

Status in grub2 package in Ubuntu:
  New

Bug description:
  RISC-V EFI support is not yet in the Linux kernel (ca. 5.8:
  https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader
  support needs to happen with the kernel
  (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html),
  GRUB2 already has RISC-V EFI support.  It can't currently boot
  anything, but it is a valid UEFI application and displays a pretty
  menu.

  Please see the attached debdiff.  Of note:

  * grub2 requires efibootmgr and efivar.  I've filed Debian bugs to
  enable riscv64 for them (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959499 respectively), but if this is actioned
  before those end up happening, it's a simple Architecture: update on
  each.

  * riscv-default-platform.patch: Upstreamed, allows `grub-install` to
  work without --platform.

  * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer"
  failure.

  * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv
  support; not sure if this should be integrated into ubuntu-
  linuxefi.patch.

  * Tested on qemu-system-riscv64 focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876620/+subscriptions