linux/poky.git/meta/recipes-core/ovmf, branch hardknott

ovmf: Fix VLA warnings with GCC 11

2021-08-06T08:59:15+00:00

(From OE-Core rev: 811ce3e6fa51ff615b7f81126d0611ba30408c85) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie (cherry picked from commit 5406ce83e07c3f89b9f2bb26f083861467b7bc59) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

ovmf: make output binaries reproducible

2021-03-20T18:54:55+00:00

OVMF is mostly reproducible, but the final .efi binaries have a 'NM10' segment in that references the original input file, and this input file has the build path in. This can be solved by passing --zero to GenFw so that this segment is zero'd out in release builds. [ YOCTO #14264 ] (From OE-Core rev: 8b4e5a3b8c3eabfbb94ab577529240b2e270efa7) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ovmf: upgrade 202011 -> 202102

2021-03-14T16:33:59+00:00

0003-ovmf-enable-long-path-file.patch removed since it is not available in 202102. (From OE-Core rev: c364d64adcb8c7fdfe196186efa868381f8630e7) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

ovmf-shell-image: image is only buildable on x86-64

2021-01-23T17:08:54+00:00

This image is only buildable for x86-64, so add a COMPATIBLE assignment to ensure it isn't attempted on others. (From OE-Core rev: bdd8208675c8a0c0232c678804a8b62cd74f1d48) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ovmf: upgrade 202008 -> 202011

2020-12-31T11:53:26+00:00

(From OE-Core rev: f1382f73f1faa0653aebd2cbb492131972755c20) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

ovmf: update edk2-stable202005 -> edk2-stable202008

2020-10-30T13:22:48+00:00

(From OE-Core rev: 61cc9acb54be09a12aac7c79f4b14e7e525d5596) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

deploy.bbclass: Clean DEPLOYDIR before do_deploy

2020-06-30T22:03:02+00:00

do_deploy should clean up ${DEPLOYDIR} before running, just like do_install cleans up ${D} before running. This reduces the risk of DEPLOYDIR being accidentally contaminated by files from previous runs, possibly even with different config, in case of incremental builds. It is convenient to have this in deploy.bbclass, so it doesn't have to be duplicated in every recipe, considering for example meta-freescale, which has 23 affected recipes. All recipes using deploy.bbclass (grep -r 'inherit .*deploy') in poky, meta-openembedded and meta-freescale look like they either benefit from this or are at least not affected negatively by it. The only exception I've noticed was uboot-sign.bbclass, which was however fixed by the previous patch. (From OE-Core rev: 7083a7d56f4d90c81d2e6652ee291d20fd908bbe) Signed-off-by: Daniel Klauer Signed-off-by: Richard Purdie

ovmf: build natively everywhere

2020-06-28T07:36:00+00:00

The OVMF target binaries are (currently) x86-specific, but the native tools to build them are not. Make the COMPATIBLE_HOST assignment target-specific, so that the native tools can be built on an arm64 build server. (From OE-Core rev: 58ebb47688fc98fdaeb78b4033bd31100218d5d6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ovmf: update to 202005

2020-06-09T12:14:00+00:00

(From OE-Core rev: f8bf6b5f9aedcc4490008000250e69f74529db75) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

ovmf: update to 202002

2020-05-07T11:16:00+00:00

(From OE-Core rev: c4301758f5a1560965ca5fb69eb1492adf351ed0) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie