path: root/recipes-bsp/systemd-boot/systemd-boot/
diff options
authorCalifornia Sullivan <>2018-01-17 22:18:31 (GMT)
committerCalifornia Sullivan <>2018-01-23 00:24:23 (GMT)
commitde43a8f89f3e68930666847adf96e1824e28b5e1 (patch)
treea94a96295c9d04d0c0b86eb1bc74a410e93805c3 /recipes-bsp/systemd-boot/systemd-boot/
parent651c915309774cf8631c9fb8b6f212fc500dd3c1 (diff)
systemd-boot: move commit pinning to
systemd-boot shouldn't be stuck on a certain commit just because RMC is. This effectively upgrades our systemd-boot version from v232 to v234. We also get to drop a patch that was accepted upstream. Signed-off-by: California Sullivan <>
Diffstat (limited to 'recipes-bsp/systemd-boot/systemd-boot/')
1 files changed, 10 insertions, 0 deletions
diff --git a/recipes-bsp/systemd-boot/systemd-boot/ b/recipes-bsp/systemd-boot/systemd-boot/
index 1172d53..aea2249 100644
--- a/recipes-bsp/systemd-boot/systemd-boot/
+++ b/recipes-bsp/systemd-boot/systemd-boot/
@@ -1,3 +1,13 @@
1# Pin systemd revision down for systemd-boot recipe.
2# Patches could not be applied cleanly when systemd in OE is updated,
3# though we don't expect a lot of changes could happen in bootloader.
4# RMC is designed to support a large number of types of boards, so we
5# should do explicit update with validation to prevent regression even
6# resolving conflicts for a new tip could be done in a short time.
8# Revision: systemd v232 in OE
9SRCREV_intel-x86-common = "a1e2ef7ec912902d8142e7cb5830cbfb47dba86c"
1DEPENDS_append_intel-x86-common = " rmc rmc-efi" 11DEPENDS_append_intel-x86-common = " rmc rmc-efi"
2 12
3EXTRA_OEMAKE_append_intel-x86-common = ' EFI_LDFLAGS="-L${STAGING_DIR_HOST}/usr/lib" EFI_CFLAGS="-I${STAGING_INCDIR}/rmc -DRMC_EFI"' 13EXTRA_OEMAKE_append_intel-x86-common = ' EFI_LDFLAGS="-L${STAGING_DIR_HOST}/usr/lib" EFI_CFLAGS="-I${STAGING_INCDIR}/rmc -DRMC_EFI"'