Mirror of git.yoctoproject.org/meta-virtualization https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=styhead 2023-08-24T01:38:21+00:00 2023-08-24T01:38:21+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2023-08-12T03:24:38+00:00 urn:sha1:08435d20b1259d2ef0c98638116fb881045ff512 bitbake has been enhanced such that SRCPV is no longer needed in PV to handle updating git hashes and task signatures. We can simplify our PV by dropping SRCPV Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2023-06-22T18:41:44+00:00 Martin Jansa Martin.Jansa@gmail.com 2023-06-21T12:39:12+00:00 urn:sha1:eaa50e95bd6f663958a536375610f25e118eb637 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2023-01-27T15:32:06+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2023-01-27T15:05:04+00:00 urn:sha1:211918936180a0b2a5af770bd5c52025d34221db While the insane.bbclass upstream-status check hasn't been made default, users of meta-virtualization may have it enabled in their distros .. so the effect is the same. We must have this tracking tag in out patches. This is a bulk update to add the tag and silence the QA message. As packages get updated, the normal/routine process of checking the patches will continue, and the status fields may (or may not) get more useful. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2022-05-12T04:01:51+00:00 Khem Raj raj.khem@gmail.com 2022-05-09T17:24:17+00:00 urn:sha1:aa86460a9308626a8093c20cf9a87a91d3584b25 Use single quote instead of double quotes to help bitabake syntax highlighter do right job Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2022-02-18T18:07:10+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2022-02-18T18:05:37+00:00 urn:sha1:108e089f7e844fafd12cfddd7eb6f96bef86c0a3 These changes are the result of running the convert-spdx-licenses.py oe-core script. There's no impact to the build, but we will avoid issues when interacting with core QA by the alignment. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> 2021-11-02T13:57:03+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2021-10-29T13:51:13+00:00 urn:sha1:ac399ad09105dce73bccde9574216377613a98de 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>