Mirror of git.yoctoproject.org/meta-virtualization https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=honister 2021-11-03T13:50:07+00:00 2021-11-03T13:50:07+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2021-10-29T13:51:13+00:00 urn:sha1:b4ba17f1b97674a3d3ca251d9921b82bbe3c39aa As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-08-02T21:17:53+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2021-07-28T18:22:43+00:00 urn:sha1:d876cfc5bfafa516dee55d04b50b319a22165640 OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-05-14T12:28:42+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-05-14T09:51:54+00:00 urn:sha1:343665d40347e89b6257b5391ac5b441cec2095a ipxe/gitrAUTOINC+18dc73d27e-r0/git$ git describe --tags v1.20.1-1-g18dc73d2 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-05-14T12:28:42+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-05-14T09:51:53+00:00 urn:sha1:aea26f7791d221ccd4865f69ca8db237571963ee * with gcc-11 it fails with: drivers/net/ath/ath5k/ath5k_eeprom.c:437:65: error: 'val' may be used uninitialized [-Werror=maybe-uninitialized] 437 | ee->ee_switch_settling_turbo[mode] = (val >> 8) & 0x7f; | ~~~~~~~~~~~^~~~~~ tests/bigint_test.c: In function 'bigint_test_exec': tests/bigint_test.c:232:14: error: 'result_raw' may be used uninitialized [-Werror=maybe-uninitialized] 232 | ok ( memcmp ( result_raw, expected_raw, \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 233 | sizeof ( result_raw ) ) == 0 ); \ | ~~~~~~~~~~~~~~~~~~~~~~~ Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-04-07T00:34:26+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-04-03T19:51:33+00:00 urn:sha1:8f06d920950f969ab0741df3dfbffa67142e8fa3 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-04-07T00:34:26+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-04-03T19:51:32+00:00 urn:sha1:b7dba4e73f8426b662961c3c15419cff8ae55b5a * git.ipxe.org is gone: fatal: unable to access 'https://git.ipxe.org/ipxe.git/': Couldn't connect to server Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-04-07T00:34:26+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-04-03T19:51:30+00:00 urn:sha1:4c073402756248acd32b209b7b8a5e1fe328b13b * this depends on syslinux Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2020-10-15T00:34:04+00:00 Bertrand Marquis bertrand.marquis@arm.com 2020-10-09T12:37:18+00:00 urn:sha1:1d861978463fdc247a7a57464b8349debba51912 Add ipxe patch to pass -fcommon flag to gcc during compilation. This patch is required to have ipxe compiling properly with gcc10. Without it the following error occur (and multiple others of the same kind: bin/blib.a(epic100.o):(.bss+0x0): multiple definition of `_shared_bss'; bin/blib.a(davicom.o):(.bss+0x0): first defined here Change-Id: Id9aed4cfe6bec9c0cbdb0b99271ddff472f1f0c3 Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2020-08-03T00:24:07+00:00 Christopher Clark christopher.w.clark@gmail.com 2020-07-30T17:20:40+00:00 urn:sha1:27759eff63089f539ab9fac366498377ef6dd666 Apply two upstream patches to fix compiler warnings. Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2020-02-27T21:59:22+00:00 Christopher Clark christopher.w.clark@gmail.com 2020-02-26T00:15:46+00:00 urn:sha1:5ce7eb1f13a7ac88bd750ec8f67456704308c708 Newer version allows for a simpler version of the cross-compile patch, which is updated in this change. Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>