Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

Add support for more bootloaders #131

Open
ricardon opened this issue Feb 23, 2018 · 3 comments
Open

Add support for more bootloaders #131

ricardon opened this issue Feb 23, 2018 · 3 comments
Assignees

Comments

@ricardon
Copy link
Contributor

ricardon commented Feb 23, 2018

Today we only use grub as bootloader. It might be good to test more bootloaders. For instance:

Linux as bootloader (aka EFI stub)
systemd boot

This could help to uncover issues as by the time Linux boots the bootloader has already interatected with the firmware (e.g., grub called by this point the UEFI Boot time service ExitBootServices()).

@sakar-arora
Copy link

At Arm, we are using EFI stub as the default mechanism to boot luvOS for running the enterprise architecture compliance suite. And it works smoothly.

@meghadey meghadey changed the title Test more bootloaders Add support for more bootloaders Jun 13, 2018
@meghadey
Copy link
Contributor

Add a distro like option to select which bootloader to run LUV on.
-eLiLo
-efi STUB
-systemd boot
-syslinux

For now, we can eliminate BITS for the above bootloaders.

@ricardon ricardon assigned ricardon and gkammela and unassigned ricardon Aug 2, 2018
@ricardon
Copy link
Contributor Author

ricardon commented Aug 2, 2018

@meghadey suggested that a good quick test is to change the EFI_PROVIDER from "luv-efi" to "systemd-boot" here [1] and see how the boot partition is populated; or at least see what things break when building.

At a later stage we would need to wire things up to run BITS from systemd-boot, implement configurations for netconsole, tests suites to run, etc.

[1]. https://github.com/intel/luv-yocto/blob/master/meta-luv/conf/distro/luv.conf#L13

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants