linux/meta-intel.git/common/recipes-bsp/systemd-boot, branch master

meta-intel: Reorganize the layout to remove common

2017-11-20T23:33:02+00:00

Remove the concept of the common directory and move all the recipes-* dirs to the top level as a normal layer would be. layer.conf is updated appropriately Signed-off-by: Saul Wold

systemd-boot: fix Yocto Project compatibility issue

2017-09-12T15:37:53+00:00

do_compile and do_deploy were being appended to unconditionally. Fix the issue by using the intel-x86-common MACHINEOVERRIDE. Signed-off-by: California Sullivan Signed-off-by: Saul Wold

systemd-boot_%.bbappend: compile and deploy EFI stub

2017-07-10T19:08:20+00:00

The EFI stub can be used to directly boot a kernel + initramfs. This addition was taken from meta-refkit. Signed-off-by: California Sullivan Signed-off-by: Saul Wold

rmc: split rmc.bb and rmc-efi.bb into separate recipes

2017-07-06T23:03:29+00:00

X32 builds require that the bootloader is built as x86_64 binary. This patch splits the build definitions of the RMC userspace application and the RMC EFI library into separate recipes and builds an x86_64 EFI library when DEFAULTTUNE is x32. Signed-off-by: Todor Minchev Signed-off-by: Saul Wold

systemd-boot: disable RMC for systemd-boot EFI_PROVIDER

2017-06-23T23:07:40+00:00

Previously the RMC library was always linked into systemd-boot. Non rmc-boot EFI_PROVIDERs will not build the rmc.db and userspace tool and therefore linking the library into these bootloaders is redundant. This change disables RMC completely when the EFI_PROVIDER is not rmc-boot. The default EFI_PROVIDER in meta-intel is rmc-boot. To use systemd-boot without RMC, set EFI_PROVIDER to systemd-boot in your conf/local.conf. Example: EFI_PROVIDER = "systemd-boot" Signed-off-by: Todor Minchev Signed-off-by: Saul Wold

systemd-boot: stub: check LoadOptions contains data

2017-03-13T16:17:14+00:00

With some UEFI shells LoadOptionsSize is reported being > 0 but the corresponding LoadOptions does not contain any data (the first element has value 0). When that happens, the stub feature that allows .cmdline to be replaced by what's in LoadOptions ends up copying nothing/random data to the kernel cmdline resulting in different kinds of boot problems. To fix this, add a check to see if LoadOptions contains data before replacing the .cmdline. Upstream-Status: Accepted [https://github.com/systemd/systemd/pull/5467] Fixes [YOCTO #11078]. Signed-off-by: Mikko Ylinen Signed-off-by: Saul Wold

systemd-boot: use RMC database in EFI stub

2017-02-02T20:58:46+00:00

systemd-boot's EFI stub can be built in an EFI executable with the kernel, cmdline, and initrd. This commit enables the EFI stub code to use the RMC database and appends the board specific cmdline (KBOOTPARAM) to the built-in cmdline. Signed-off-by: Mikko Ylinen Signed-off-by: California Sullivan

systemd-boot: update 230 -> 232

2017-01-24T22:31:01+00:00

This change updates the locked systemd-boot revision to v232 release which is the current in OE. Signed-off-by: Jianxun Zhang Signed-off-by: California Sullivan

systemd-boot%.bbappend: rename to match the versioned recipe

2016-12-23T18:42:45+00:00

OE-Core recently renamed the recipe to have PV in the name and the bbappend wildcard was added to make the transition smooth. The renaming is now complete so rename the bbappend again to match the new versioned recipe only. The aggresive systemd-boot% wildcard matches systemd-bootchart too giving unexpected results. Depends on OE-Core 8fe1e5197f6f94a49693de09f4eb9394df531cc8. Signed-off-by: Mikko Ylinen Signed-off-by: Saul Wold

systemd-boot.bbappend: Rename to use wildcard

2016-12-07T22:05:36+00:00

OE-Core is in process of renaming the recipe to have PV in recipe name. Cover that case for bbappend Signed-off-by: Khem Raj Signed-off-by: California Sullivan