[PATCH] x86_64: add systemd-boot images

[Elliott Mitchell]

On Tue, Dec 30, 2025 at 03:05:16PM +0100, Jonas Lochmann wrote:
> Am Tue, Dec 30, 2025 at 02:01:21PM +0100, schrieb Paul Spooren:
> > 
> > From my understanding it’s much simpler/smaller than GRUB, so maybe something inline with the efforts of OpenWrt?
> 
> Yes, that's the main motivation. Unlike grub, it only supports UEFI
> boot but this is the only boot method supported by recent x86 hardware.

The motherboard on this system is 3 years old yet will still boot using
the traditional bootsector.  Some things are disabled in that mode, but
it can still boot without UEFI.  This though isn't a bottom tier
motherboard bought with price as the only criterion, nor is this a laptop
which comes with fewer options.

> The legacy boot procedure is relevant only in virtual machines but
> because this implementation uses (like the OpenWrt grub integration)
> the fallback path, no specific values in nvram variables are required
> so that UEFI booting works without effort - like the legacy boot.

Depends on the hypervisor and its configuration.  Both GRUB and
Tianocore/EDK2 have been ported to be directly loadable by at least one
hypervisor and serve as the first stage loader.  If GRUB is the first
stage, then grub.cfg is the first OpenWRT built piece to be loaded.
If Tianocore/EDK2 is the first stage, then it will be UEFI-only.

On the surface the patch didn't look too problematic, but beware of
making needless changes with booting.  Of note SuSE chose to use
"grub2.cfg" and has invested significant energy in keeping that.
Resulting in pull #3791 which I'm unsure of working around a SuSE bug in
OpenWRT.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445