summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: cooker: adjust the error message about missing websockets module to ↵Alexander Kanavin2025-10-141-1/+4
| | | | | | | | | mention bitbake-setup (Bitbake rev: 2d15e6fc93f6a73c9c84e399613f931f1c783922) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add 'install-buildtools' commandAlexander Kanavin2025-10-142-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This basically calls install-buildtools from oe-core/poky, but it ensures via command line parameters that the installation location is stable and the downloads are preserved for reproducibility: $ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf ====== Buildtools archive is downloaded into /home/alex/bitbake-builds/yocto-master-testing/buildtools-downloads/20250319141333 and its content installed into /home/alex/bitbake-builds/yocto-master-testing/buildtools ... (output from install-buildtools script) ====== It also detects when buildtools are already installed, and will direct users what to do: ====== alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-setup install-buildtools Loading settings from /home/alex/bitbake-builds/bitbake-setup.conf Buildtools are already installed in /home/alex/bitbake-builds/yocto-master-testing/buildtools. If you wish to use them, you need to source the the environment setup script e.g. $ . /home/alex/bitbake-builds/yocto-master-testing/buildtools/environment-setup-x86_64-pokysdk-linux You can also re-run bitbake-setup install-buildtools with --force option to force a reinstallation ====== This commits includes fixes by Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 (Bitbake rev: 3fe3096847046110c72b23fce37fb4a459b1d748) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add tests to bitbake-selftestAlexander Kanavin2025-10-142-0/+267
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Run like this: alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-selftest -v bb.tests.setup test_setup (bb.tests.setup.BitbakeSetupTest.test_setup) ... ok ---------------------------------------------------------------------- Ran 1 test in 9.223s OK The test does a basic run-through of init, then status/update on an unchanged configuration, then status/update on a configuration changed via new commits to the test layer, then status/update on configuration changed via the top level json config file. Note that nothing whatsoever is fetched from the network; the test relies entirely on synthetic data contained inside itself, including minimal stubs for oe-setup-build and bitbake-config-build. This data is used to create temporary git repositories then clone them via local filesystem URIs. Later on this can be supplemented by an oe-selftest that tests bitbake-setup against real config files in the official configuration repository and real layers, templates and fragments. (Bitbake rev: e3aa3eb46bd3196fa5415fa36e3737636fd6a1c0) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-setup: add the initial implementationAlexander Kanavin2025-10-141-0/+809
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Preamble ======== The latest iteration of this patchset is available at https://github.com/kanavin/bitbake I recommend taking the patches from there to ensure that you are not trying out outdated code. For the rationale and design guidelines please see this message: https://lists.openembedded.org/g/openembedded-architecture/message/1913 Left out for now but will be done later: - official configuration repository - documentation Amble *scratch* HOWTO ===================== 1. If you don't know where to start, run 'bitbake-setup init'. Bitbake-setup will ask a few questions about available configuration choices and set up a build. Note: 'init' sub-command can also take a path or a URL with a configuration file directly. You can see how those files look like here: https://github.com/kanavin/bitbake-setup-configurations 2. You can then source the bitbake environment and run bitbake to perform builds as usual: $ . /home/alex/bitbake-builds/yocto-master-options-poky-distro_poky-machine_qemux86-64/build/init-build-env Also, subsequent status/update commands will not require a separate --build-dir argument telling bitbake-setup where the build is. 3. To check if the build configuration needs to be updated, run: === $ bin/bitbake-setup status ... Configuration in /home/alex/bitbake-builds/poky-alex/ has not changed. === If the configuration has changed, you will see the difference as a diff. ... - "rev": "akanavin/sstate-for-all" + "rev": "akanavin/bitbake-setup-testing" ... If the configuration has not changed, but layer revisions referred to it have (for example if the configuration specifies a tip of a branch), you will see that too: === ... Layer repository git://git.yoctoproject.org/poky-contrib checked out into /home/alex/builds/poky-alex/layers/poky updated revision akanavin/sstate-for-all from 6b842ba55f996b27c900e3de78ceac8cb3b1c492 to aeb73e29379fe6007a8adc8d94c1ac18a93e68de === 4. If the configuration has changed, you can bring it in sync with: $ bin/bitbake-setup update Note that it will also rename/preserve the existing build/conf directory, and print changes in bitbake configuration (diff of content of build/conf/) if that has changed. I can't at the moment think of anything more clever that is also not much more brittle or complex to implement, but open to suggestions. Terminology =========== - 'top directory' means the place under which bitbake-setup reads and writes everything. bitbake-setup makes a promise to not touch anything outside of that, unless otherwise directed to by entries in settings (currently there is one such setting for fetcher downloads for layers and config registries). Top directory can be selected by an environment variable, a command line option, or otherwise assumed to be ~/bitbake-builds/. If BBPATH is in environment (e.g. we are in a bitbake environment), then the top directory is deduced from that and doesn't need to be specified by hand. - 'settings' means bitbake-setup operational parameters that are global to all builds under a top directory. E.g. the location of configuration registry, or where the bitbake fetcher should place the downloads (DL_DIR setting). Settings are stored in a .conf file in ini format just under the top directory. - 'build' means a tree structure set up by 'bitbake-setup init', consisting of, at least, a layers checkout, and a bitbake build. It maps 1:1 to the json data it was constructed from, which is called 'build configuration'. Build configurations are constructed from generic configurations that may involve making one or more choices about available options in them. Generic configurations are files, URLs or are obtained from git repositories called 'config registries', in which case they can be listed with 'bitbake-setup list'. There can be multiple 'builds' under a top directory. Here are two example generic configurations that showcase this: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-options.conf.json https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-nested-configs.conf.json - 'bitbake-setup status' will tell if a build is in sync with the generic configuration it was made from. 'bitbake-setup update' will bring a build in sync with a configuration if needed. - 'bitbake build' means a particular sub-tree inside a build that bitbake itself operates on, e.g. what is set in BBPATH/BUILDDIR by oe-init-build-env. conf/* in that tree is 'bitbake configuration'. Bitbake configurations are constructed from templates and fragments, with existing mechanisms provided by oe-core. The configuration file format is specified such that other mechanisms to set up a bitbake build can be added; there was a mention of ability to specify local.conf content and a set of layers directly in a configuration. I think that scales poorly compared to templates and fragments, but I made sure alternative ways to configure a bitbake build are possible to add in the future :) - 'source override' is a json file that can be used to modify revisions and origins of layers that need to be checkout into a build (e.g. when master branches need to be changed to master-next for purposes of testing). Such a file is specified with a command-line option to 'init' and an example can be seen here: https://github.com/kanavin/bitbake-setup-configurations/blob/main/yocto-master-next.override.json This commit includes fixes by Ryan Eatmon <reatmon@ti.com> https://github.com/kanavin/bitbake/pull/1 Gyorgy Sarvari <skandigraun@gmail.com> https://github.com/kanavin/bitbake/pull/2 Johannes Schneider <johannes.schneider@leica-geosystems.com> https://github.com/kanavin/bitbake/pull/3 https://github.com/kanavin/bitbake/pull/5 (Bitbake rev: b96154aeb1fc89184ac245e0d68e6e726fe80c04) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty, uihelper: Remove running_pids and lastpidsPeter Kjellerstedt2025-10-132-7/+1
| | | | | | | | | | | | | * lastpids has not been used for almost 10 years. * There is no longer any need to use running_pids to keep track of the order the pids in running_tasks were added as dicts are guaranteed to remember the insertion order since Python 3.7. (Bitbake rev: 562b5bf0be2883144391e7030a9dce6a233802ac) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ast: Warn on multiple builtin config fragments for the same variableYoann Congal2025-10-131-0/+21
| | | | | | | | | | | | | | | | Having multiple builtin config fragments for the same variable (eg OE_FRAGMENTS = "... machine/A ... machine/B") is not supported. Warn the user to make them fix this but continue with the normal variable evaluation : the last affectation "wins". Added warning looks like: WARNING: Multiple builtin fragments are enabled for machine via variable OE_FRAGMENTS: machine/qemux86-64 machine/test machine/qemux86-64. This likely points to a mis-configuration in the metadata, as only one of them should be set. The build will use the last value. (Bitbake rev: 1c12aa23f6678dc289fc0e0d8b4dad311bd39c35) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add Qualcomm rb3gen2 workaroundsMikko Rapeli2025-10-131-0/+12
| | | | | | | | | | | | | u-boot 2025.10rc2 based firmware from meta-ts https://gitlab.com/Linaro/trustedsubstrate/meta-ts triggers some non-fatal errors from various drivers. Ignore them for now since all other oeqa runtime tests pass since in genericarm64 we don't build this firmware. (From meta-yocto rev: fe65e142d0d9ba0e51ff9175ffa82e902f982a20) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericarm64.conf: increase initramfs sizeMikko Rapeli2025-10-131-1/+1
| | | | | | | | | | With firmware files and more kernel modules the size limit is hit again. Increase by 60Mb. (From meta-yocto rev: 4348f496cf4950cf665d7c56643718b5238e96bf) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericarm64.conf: install Qualcomm rb3gen2 firmwareMikko Rapeli2025-10-131-0/+6
| | | | | | | | | | | | Copied from meta-qcom recipes-bsp/packagegroups/packagegroup-rb3gen2.bb Sadly does not fully resolve kernel error messages from WiFi firmware files. (From meta-yocto rev: 6fd803cd96746cbf3ae625d0fadbb176ce1b2919) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add Rpi4 wifi firmware workaroundMikko Rapeli2025-10-131-0/+4
| | | | | | | | | | | The firmware file is not available from linux-firmware package so it may be that another file name is used instead. Thus this non-fatal error can be ignored for now. (From meta-yocto rev: 2d442f338cbd4a681388c093899a5709b7881d96) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericarm64.conf: install linux-firmware-bcm43455 to imagesMikko Rapeli2025-10-131-1/+6
| | | | | | | | | | | | | | | by default. Fixes parselogs oeqa runtime test failures: https://ledge.validation.linaro.org/scheduler/job/121516 Central error: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2 ... Central error: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin failed with error -2 (From meta-yocto rev: dce46431683b5172327770972166c79e4c60cc2d) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add workarounds for NXP imx8mpMikko Rapeli2025-10-131-0/+12
| | | | | | | | | | | | | u-boot 2025.10rc2 based firmware from meta-ts https://gitlab.com/Linaro/trustedsubstrate/meta-ts triggers some non-fatal errors from various drivers. Ignore them for now since all other oeqa runtime tests pass since in genericarm64 we don't build this firmware. (From meta-yocto rev: 0b15a104ea04acd79b87f7cf3da96f637dafdef4) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add workaround for TI K3 am62p5Mikko Rapeli2025-10-131-0/+4
| | | | | | | | | | | With u-boot 2024.04 based firmware the board firmware seems to have one small issue which kernel complains about. The board works well and passes other tests so ignore this for now. (From meta-yocto rev: 56f33867249f79340f868cb90bc7e4c2a6a641d2) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add workarounds for AMD zcu102Mikko Rapeli2025-10-131-0/+8
| | | | | | | | | | | | | u-boot 2025.10rc2 based firmware from meta-ts https://gitlab.com/Linaro/trustedsubstrate/meta-ts triggers some non-fatal errors from various drivers. Ignore them for now since all other oeqa runtime tests pass since in genericarm64 we don't build this firmware. (From meta-yocto rev: 6fc9c8e2a8b23877c2cd2bac43d37dcaf5b6c8ef) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs-ignores-genericarm64.txt: add error messages from rockpi4bMikko Rapeli2025-10-131-0/+9
| | | | | | | | | | | | | | | Rockchip rk3399 based rockpi4b with u-boot 2025.10rc2 based firmware from meta-ts https://gitlab.com/Linaro/trustedsubstrate/meta-ts triggers some non-fatal errors from various drivers. Ignore them for now since all other oeqa runtime tests pass since in genericarm64 we don't build this firmware. https://ledge.validation.linaro.org/scheduler/job/119422 (From meta-yocto rev: b91b6ca6827d489ecb21cb688403c2b1c76ccd52) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: runtime: logrotate: Fix typos and add commentsMathieu Dubois-Briand2025-10-131-15/+16
| | | | | | | (From OE-Core rev: 7d1d3b4958bc48cf49ddb653c76c8cd536babac6) Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x264: switch to PACKAGECONFIGDmitry Baryshkov2025-10-132-3/+47
| | | | | | | | | | | | Switch to PACKAGECONFIG in order to make x264 options configurable. Enable FFmpeg (by default) and OpenCL (if enabled by the distro). Pick up the patch to fix building with the latest FFmpeg. (From OE-Core rev: 4339bf44faa11bf5933f23ac5b0b6ecaa5a1afab) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vte: upgrade 0.80.3 -> 0.82.1Gyorgy Sarvari2025-10-131-1/+1
| | | | | | | | | | | Commitlog: https://gitlab.gnome.org/GNOME/vte/-/compare/0.80.3...0.82.1 (From OE-Core rev: d2e5df7e3daa4b58d8802b62fbbba5f6959379c3) Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm/clang: Upgrade to 21.1.3 releaseKhem Raj2025-10-133-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | brings following fixes * 450f52eec88f Bump version to 21.1.3. * 05b5090e961f Port 5b4819e to release/21.x * 2cb08dbb39b1 [compiler-rt][sanitizer] fix msghdr for musl (#136195) * 6e687cbe0dd3 [SPARC] Prevent meta instructions from being inserted into delay slots (#161111) * f8151a1d2c86 [clang] [Headers] Don't use unreserved names in avx10_2bf16intrin.h (#161824) * 9ee4ac8a8359 [clang][SPARC] Pass 16-aligned structs with the correct alignment in CC (#155829) * 220bac16a417 [Hexagon] Add opcode V6_vS32Ub_npred_ai for offset validity check (#161618) * a867bd53e861 [clang][PAC] Don't try to diagnose use of pointer auth on dependent types #159505 (#159859) * 41e817a1d1f4 release/21.x: [clang-format] Fix bugs in annotating arrows and square brackets (#160973) * 559d966bcb54 [Mips] Fix atomic min/max generate mips4 instructions when compiling for mips2 (#159717) * d1e2f8916128 [LLD] [COFF] Fix symbol names for import thunks (#160694) * 0060034c6a0b [analyzer] Revert #115918, so empty base class optimization works again (#157480) * 31e4363ba9c2 [NVPTX] Disable relative lookup tables (#159748) * 74cb34a6f51a Bump version to 21.1.3 (From OE-Core rev: 4a590bdd8794c6873f9ff0dc6d988d62f5b2ca5c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan: upgrade 1.4.321.0 -> 1.4.328.1Dmitry Baryshkov2025-10-1311-953/+20
| | | | | | | | | | | Upgrade all Vulkan-related packages together in a single commit. License-Update: glslang dropped SPIR-V remapper (From OE-Core rev: 55c7566c33833a8f36cbf50a70cb1a1cf7aa96d5) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: upgrade 20250530 -> 20250930Yi Zhao2025-10-134-12/+9
| | | | | | | | | | | ChangeLog: https://github.com/linux-test-project/ltp/releases/tag/20250930 (From OE-Core rev: dd53cccdd11358398cf154ee8d0e529ff180adb1) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* json-glib: upgrade 1.10.6 -> 1.10.8Yi Zhao2025-10-131-1/+1
| | | | | | | | | | | | ChangeLog: * Add missing escape * Fix static builds (From OE-Core rev: b73e30c82d16e2a93e402873cad0da6ca6251f2b) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/buildoptions: Fix test_yocto_source_mirror MIRRORS & ↵Yoann Congal2025-10-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PREMIRRORS definitions Currently, the definitions of MIRRORS and PREMIRRORS made by test_yocto_source_mirror() are overwritten when run on the autobuilder: * MIRRORS = "" is extended by mirrors.bbclass to its usual value. * PREMIRRORS = "* dl.yp.org" is overwritten by the autobuilder.conf config fragment to "" Simplified variable history: # $MIRRORS [4 operations] # set .../contribution-yocto/builds/build-qemux86-64-st/conf/selftest.inc:3 # "" # append .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/classes-global/mirrors.bbclass:57 # "${DEBIAN_MIRROR} ..." MIRRORS=" http://deb.debian.org/debian/pool ..." # $PREMIRRORS [4 operations] # set .../contribution-yocto/builds/build-qemux86-64-st/conf/selftest.inc:18 # " bzr://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n ..." # set .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/conf/fragments/yocto-autobuilder/autobuilder.conf:6 # "" # append .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/classes-global/mirrors.bbclass:84 # "git://sourceware.org/git/glibc.git https://downloads.yoctoproject.org/mirror/sources/ ..." PREMIRRORS=" git://sourceware.org/git/glibc.git https://downloads.yoctoproject.org/mirror/sources/ ..." Despite this unexpected configuration, the test passes because after failing to find a PREMIRROR (empty), failing to download the normal SRC_URI (because of BB_ALLOWED_NETWORKS), the fetcher tries the MIRRORS which have by default download.yoctoproject.org. For example, on a failed meta-oe-mirror test[0], we can see a lot of warnings: "stdio: WARNING: ... do_fetch: Failed to fetch URL https://... attempting MIRRORS if available" By using the ":forcevariable" override, test_yocto_source_mirror() makes sure the correct value is set for MIRRORS and PREMIRRORS (whatever is the configuration). Simplified variable history (after the fix): # $MIRRORS [4 operations] # append .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/classes-global/mirrors.bbclass:57 # "${DEBIAN_MIRROR} ..." # append .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/classes-global/mirrors.bbclass:68 # "git://salsa.debian.org/.* ..." # override[forcevariable]:set .../contribution-yocto/builds/build-qemux86-64-st/conf/selftest.inc:3 # "" MIRRORS="" # $PREMIRRORS [4 operations] # set .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/conf/fragments/yocto-autobuilder/autobuilder.conf:6 # "" # append .../contribution-yocto/builds/build-qemux86-64-st/../../layers/poky/meta/classes-global/mirrors.bbclass:84 # "git://sourceware.org/git/glibc.git ..." # override[forcevariable]:set .../contribution-yocto/builds/build-qemux86-64-st/conf/selftest.inc:18 # " bzr://.*/.* http://downloads.yoctoproject.org/mirror/sources/ ..." # pre-expansion value: # " bzr://.*/.* http://downloads.yoctoproject.org/mirror/sources/ ..." PREMIRRORS=" bzr://.*/.* http://downloads.yoctoproject.org/mirror/sources/ ..." [0]: https://autobuilder.yoctoproject.org/valkyrie/#/builders/82/builds/470/steps/17/logs/warnings Fixes [YOCTO #15993] (From OE-Core rev: ab810d1239d4db0bc0f23db31c70cc9c6e59357e) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: sort out driver listsDmitry Baryshkov2025-10-131-66/+69
| | | | | | | | | | | | Sort the lists of VUKAN_DRIVERS, GALLIUMDRIVERS and driver-related PACAKGECONFIG entries, making it easier to add new drivers or to find out the correct dependencies for the driver. (From OE-Core rev: 64108679ada885b74fcc6ac49f9e5e983f34e663) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: be more explicit about gallium-llvm dependencyDmitry Baryshkov2025-10-131-14/+13
| | | | | | | | | | | | | | Historically mesa recipe had separate variables for drivers that depended on gallium-llvm PACKAGECONFIG. Since that time we started listing other dependencies explicitly (e.g. libclc). Drop the intermediate variables and make the dependency on gallium-llvm more explicit. (From OE-Core rev: d3ce0b8a9964d2a0afe98701ee4d51b2dbd8d64e) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: drop asahi -> opencl dependencyDmitry Baryshkov2025-10-131-2/+2
| | | | | | | | | | | The Asahi drivers depend on the clc to be available, but not on the RustiCL. Make it possible to build asahi drivers with opencl disabled. (From OE-Core rev: c869128ba34d1c9c9952206fb6814e6fdbd39bef) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: add opencl -> clang build dependencyDmitry Baryshkov2025-10-131-1/+1
| | | | | | | | | | | | | | | | With the commits 448f4a84cb22 ("llvm: add recipe for just the LLVM libraries") and d76dc362c8e1 ("clang: use llvm recipe") the 'llvm' dependency inside mesa.inc does no longer pull in the clang libraries, failing RustiCL build as it can not find Clang libaries. Add direct dependency on the clang in order to fulfill build-time deps. Fixes: d76dc362c8e1 ("clang: use llvm recipe") (From OE-Core rev: b8fa4a0ac33638b599ee169db11b5e77b2483148) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: patch CVE-2025-11083Peter Marko2025-10-132-0/+78
| | | | | | | | | | Pick patch per link in NVD report. (From OE-Core rev: 363961f74e3a8df3d1b97ce33855b8b40f6da497) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: patch CVE-2025-11082Peter Marko2025-10-132-0/+47
| | | | | | | | | | Pick patch per link in NVD report. (From OE-Core rev: 4c72e3bcf1f7898e69d5b0b0d490e550bb96bc0e) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: fix CVE-2025-11081Yash Shinde2025-10-132-0/+52
| | | | | | | | | | | | | | | | | | | | | CVE: CVE-2025-11081 Trying to dump .sframe in a PE file results in a segfault accessing elf_section_data. * objdump (dump_sframe_section, dump_dwarf_section): Don't access elf_section_type without first checking the file is ELF. PR 33406 SEGV in dump_dwarf_section [https://sourceware.org/bugzilla/show_bug.cgi?id=33406] Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b] (From OE-Core rev: d1eb65d2e9365f6bd2acf450496d3bfeda6aedc1) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-c: fix debug symbols containing TMPDIR referencesYash Shinde2025-10-131-0/+2
| | | | | | | | | | | | | | | | | | | | | When building cargo-c with DEBUG mode, QA checks fail due to absolute paths from the build environment (TMPDIR) being embedded into the debug symbols/binaries. This causes issues such as: ERROR: do_package_qa: File /usr/bin/.debug/cargo-capi contains reference to TMPDIR [buildpaths] ERROR: do_package_qa: File /usr/bin/.debug/cargo-cinstall contains reference to TMPDIR [buildpaths] ERROR: do_package_qa: File /usr/bin/.debug/cargo-cbuild contains reference to TMPDIR [buildpaths] ERROR: do_package_qa: File /usr/bin/.debug/cargo-ctest contains reference to TMPDIR [buildpaths] To fix this, pass an additional -ffile-prefix-map option to DEBUG_PREFIX_MAP to ensure that paths under `${CARGO_HOME}` are remapped to `${TARGET_DBGSRC_DIR}`. This ensures debug info is reproducible and does not leak host-specific paths. (From OE-Core rev: 3239961e35434592c06ec2cae2885ab464d35744) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: Make sure the build dir is unique for each UBOOT_CONFIGRyan Eatmon2025-10-133-17/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each UBOOT_CONFIG entry is run in a different directory under ${B} so that the files can be generated, compiled, and installed differently from each other. Currently that unique directory name was just the defconfig used for each UBOOT_CONFIG. One potential conflict arises when you want build the same defconfig twice, but pass in different make options. Then we get directory collision. Simple fix is to include both the defconfig name and the UBOOT_CONFIG type in the directory name. This change has the potential to be backwards breaking if a layer is using the UBOOT_CONFIG flow and overriding/appending any of the do_* shell functions. Each of those will either need to change to using: ${B}/${config} -> ${B}/${config}-${type} or for append functions they can use the new variable in the parent function: ${B}/${config} -> ${B}/${builddir} (From OE-Core rev: 22e96b32b0be02ec0971c9334d4b1df7c9ef8d84) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gawk: disable persistent memory allocator due to licensingRandy MacLeod2025-10-131-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In gawk-5.2, a feature that allows gawk to preserve memory between runs: https://www.gnu.org/software/gawk/manual/html_node/Persistent-Memory.html was added. The files that implement this, support/pma.[ch], are licensed under the AGPL3 which some entities perfer to avoid. Force people to knowingly opt into using this feature and license using: PACKAGECONFIG:append:pn-gawk = " pma-if-64bit" where pma is an abbreviation for persistent memory allocator and the "-if-64bit" suffix is a indicator to users that the feature only works for 64 bit targets. Also add AGPL to LICENSE and LICENSE:${PN}, when using pma. Correct the license to be AGPL-3.0-or-later. There hasn't been a change in the license terms, at least for main.c, haven't changed significantly in the last 15 years: License-Update: Reflects conditional AGPL use and more as described above. Testing requires a non-root account and following the example in the link above: $ truncate -s <size> data.pma $ chmod 0600 data.pma $ GAWK_PERSIST_FILE=data.pma gawk 'BEGIN { print ++i }' 1 $ GAWK_PERSIST_FILE=data.pma gawk 'BEGIN { print ++i }' 2 $ GAWK_PERSIST_FILE=data.pma gawk 'BEGIN { print ++i }' 3 This works on qemu[x86-|arm|riscv]64 but not on qemu[arm|x86] where the --enable-pma is ignored because there is a requirement and build-time test for 8 byte void pointers in m4/pma.m4: if test "$SKIP_PERSIST_MALLOC" = no && test $ac_cv_sizeof_void_p -eq 8 Finally, remove an old comment about GPLv2, GPLv3 versions of gawk since this is no longer important as the GPLv2 version is not maintained. (From OE-Core rev: d7b6887dfbe2817ceb03d44a59210f65bbb25390) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: upgrade 1.25.1 -> 1.25.2Peter Marko2025-10-137-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upgrade to latest 1.25.x release [1]: $ git --no-pager log --oneline go1.25.1..go1.25.2 bed6c81c2d (tag: go1.25.2) [release-branch.go1.25] go1.25.2 2612dcfd3c [release-branch.go1.25] archive/tar: set a limit on the size of GNU sparse file 1.0 regions 90f72bd500 [release-branch.go1.25] encoding/pem: make Decode complexity linear e0f655bf3f [release-branch.go1.25] encoding/asn1: prevent memory exhaustion when parsing using internal/saferio 100c5a6680 [release-branch.go1.25] net/http: add httpcookiemaxnum GODEBUG option to limit number of cookies parsed f0c69db15a [release-branch.go1.25] crypto/x509: improve domain name verification 9fd3ac8a10 [release-branch.go1.25] net/url: enforce stricter parsing of bracketed IPv6 hostnames 5d7a787aa2 [release-branch.go1.25] net/textproto: avoid quadratic complexity in Reader.ReadResponse 930ce220d0 [release-branch.go1.25] crypto/x509: mitigate DoS vector when intermediate certificate contains DSA public key 6a057327cf [release-branch.go1.25] net/mail: avoid quadratic behavior in mail address parsing 66f6feaa53 [release-branch.go1.25] spec: revert "update spec date to match release date" d6f2741248 [release-branch.go1.25] spec: update spec date to match release date 28ac8d2104 [release-branch.go1.25] net/http: avoid connCount underflow race 06993c7721 [release-branch.go1.25] context: don't return a non-nil from Err before Done is closed 0b53e410f8 [release-branch.go1.25] debug/pe: permit symbols with no name 7735dc90ed [release-branch.go1.25] cmd/compile: don't rely on loop info when there are irreducible loops 205d086595 [release-branch.go1.25] crypto/tls: quote protocols in ALPN error message 16fdaac4b1 [release-branch.go1.25] sync/atomic: correct Uintptr.Or return doc f3dc4aac0b [release-branch.go1.25] runtime: initialise debug settings much earlier in startup process 79c3081b4b [release-branch.go1.25] internal/poll: don't call Seek for overlapped Windows handles b816c79658 [release-branch.go1.25] lib/fips140: re-seal v1.0.0 90de3b3399 [release-branch.go1.25] crypto/internal/fips140: remove key import PCTs, make keygen PCTs fatal bec452a3a2 [release-branch.go1.25] crypto/internal/fips140: update frozen module version to "v1.0.0" 57bd28ab7f [release-branch.go1.25] crypto/internal/fips140/ecdsa: make TestingOnlyNewDRBG generic f75bcffa4a [release-branch.go1.25] os: set full name for Roots created with Root.OpenRoot 7d570090a9 [release-branch.go1.25] os: fix Root.MkdirAll to handle race of directory creation be61132165 [release-branch.go1.25] cmd/compile: export to DWARF types only referenced through interfaces a86792b169 [release-branch.go1.25] net: skip TestIPv4WriteMsgUDPAddrPort on plan9 879e3cb5f7 [release-branch.go1.25] runtime: lock mheap_.speciallock when allocating synctest specials Fixes CVE-2025-61725, CVE-2025-58187, CVE-2025-58189, CVE-2025-61723, CVE-2025-47912, CVE-2025-58185, CVE-2025-58186, CVE-2025-58188, CVE-2025-58183 and CVE-2025-61724 [2]. [1] https://github.com/golang/go/compare/go1.25.1...go1.25.2 [2] https://groups.google.com/g/golang-announce/c/4Emdl2iQ_bI (From OE-Core rev: b46e8fdfc23a575ee8c69c136c7815e366a7e904) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: upgrade 1.25.0 -> 1.25.1Peter Marko2025-10-137-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | Upgrade to latest 1.25.x release [1]: $ git --no-pager log --oneline go1.25.0..go1.25.1 56ebf80e57 (tag: go1.25.1) [release-branch.go1.25] go1.25.1 b1959cf6f7 [release-branch.go1.25] net/http: require exact match for CrossSiteProtection bypass patterns cdd8cf4988 [release-branch.go1.25] net: fix WriteMsgUDPAddrPort addr handling on IPv4 sockets 8995e84ac6 [release-branch.go1.25] internal/poll: set the correct file offset in FD.Seek for Windows overlapped handles 749dff880a [release-branch.go1.25] runtime: make all synctest bubble violations fatal panics 21ac81c1e1 [release-branch.go1.25] os/exec: fix incorrect expansion of ".." in LookPath on plan9 c72fcab6d6 [release-branch.go1.25] cmd/go/internal/gover: fix ModIsPrerelease for toolchain versions Fixes CVE-2025-47910 [2]. [1] https://github.com/golang/go/compare/go1.25.0...go1.25.1 [2] https://groups.google.com/g/golang-announce/c/PtW9VW21NPs (From OE-Core rev: 34d34fdac49e2a3035e6a1aa3d5e8d1090e91c9f) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: Improve build race/reproducibulity fixesRichard Purdie2025-10-131-2/+6
| | | | | | | | | | | | | The include options shouldn't be needed with the make fix but issues still remained. Looking at the logs, it looks like these are from other header directories and we need to run "make install_headers" for all of the sub components before starting the main build. Update the workaround to do that for each component with internal header copies. (From OE-Core rev: 0b5f0a7b1db9f6923c027719181fa60f8fdb73e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Set FILES to ""Ryan Eatmon2025-10-131-1/+7
| | | | | | | | | | | | | Now that all of the current firmware has either been moved into sub-packages or removed due to licensing the base package is now empty. Going forward we would like to keep the base package empty and force the version updates to bin any new firmwares into sub-packages. (From OE-Core rev: 9b883aa6f3cf881bfd60442b9ec193ae191b4cbe) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Remove unlicensed firmwareRyan Eatmon2025-10-131-0/+66
| | | | | | | | | | | | | | | Create a new REMOVE_UNLICENSED variable and do_install() logic to allow for marking certain firmware files as something to remove and not package up. This comes from the fact that the WHENCE file has a number of firmware entries that have no license information or very questionable declarations as to what the license is for the firmware. (From OE-Core rev: 406628a31b7d903e6545d8a1b6d0548f0874ed6d) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Move all firmware into sub-packagesRyan Eatmon2025-10-131-16/+949
| | | | | | | | | | | | | | A lot of the firmware has already been broken out into sub-packages, but a good number were still lingering in the base linux-firmware package. Move all of the remaining firmware into sub-packages based on the driver name in the WHENCE file or into existing sub-packages where a file or two were missed. (From OE-Core rev: c53c6a0a11afb5c6133e1751e0b35e7eb809b60b) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image.bbclass: Document two image features that were missingPeter Kjellerstedt2025-10-131-0/+2
| | | | | | | | | | | This adds documentation of overlayfs-etc and read-only-rootfs-delayed-postinsts. (From OE-Core rev: be4882e38e9bc00c1b927982d4ef6a559f5905f7) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image.bbclass: Tweak the descriptions of the image featuresPeter Kjellerstedt2025-10-131-14/+13
| | | | | | | | | | | | Some minor grammatical changes, and removal of some duplicate information. Also note which features were previously part of the debug-tweaks feature. (From OE-Core rev: 377e6e7bc4be086c217f92db11f5c6101b52d88c) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image.bbclass: Improve the documentation of available image featuresPeter Kjellerstedt2025-10-131-8/+15
| | | | | | | | | | | Group the features based on what they are used for, and also sort the features within each group. (From OE-Core rev: b670cb573a0b8015ebff5e78fe2926c843247b9b) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image.bbclass: Sort the FEATURE_PACKAGES_*Peter Kjellerstedt2025-10-131-21/+20
| | | | | | | | | | This is primarily a preparation for the next commit. (From OE-Core rev: cc70aa42c5548c2759cada8f93ca001b07f25599) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image, populate_sdk_base: Add zsh-completion-pkgs image featureAdam Nilsson2025-10-132-0/+2
| | | | | | | | | | | | | Add a zsh-completion-pkgs image feature to install *-zsh-completion packages into an image. This is similar to the existing bash-completion-pkgs feature. Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> (From OE-Core rev: c2d4228197ed0d0d00bb464237fa151a928eba76) Signed-off-by: Adam Nilsson <Adam.X.Nilsson@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/bblayers: fix up compatibility with integrated poky and separate ↵Alexander Kanavin2025-10-131-2/+2
| | | | | | | | | | | | | | | | | layer checkouts Specifically: - when using integrated poky, autobuilder clones it into 'build', rather than 'poky' - do not use a catch-all default to tweak the commit id openembedded-core, rather make it specific to that repository. (From OE-Core rev: 9a77dea19b0a9b07a21648e6f231d936d7387846) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/systemd_boot: Fix changing MACHINE during the testRichard Purdie2025-10-101-1/+1
| | | | | | | | | | | | With config fragments, changing MACHINE in the test like this no longer works. Use the forcevarable override to allow it to work. This also needs a tweak to bitbake to work correctly, sent seperately. Whilst ugly, this avoids the need to start changing config fragments. (From meta-yocto rev: 3f56d9e3b1b30116d979a98f7cf765c26996016a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: Bump versions to resolve hashequiv/reproducibility issuesRichard Purdie2025-10-101-0/+4
| | | | | | (From OE-Core rev: 3fc1fa77dae8d138c9a0bf47172d978812b593b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ast: Fix fragment behaviour with overridesRichard Purdie2025-10-091-1/+2
| | | | | | | | | | | | | | | | | | | | | Imagine a machine fragment machine/A and a configuration which sets: MACHINE = "B" MACHINE:forcevariable = "C" As I understand it, the fragment behaviour was intended to replace the MACHINE = "B", so the override would still be active. The current code replaces all variable overrides. parsing=True, switches to the other behaviour, which I believe was the design intent and the behaviour users would expect. This is useful to allow test configurations to override a MACHINE setting without change the fragments which would complicate the test code. (Bitbake rev: f65bc6aaf4c11bc7e566c895209c093627a3015b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdk/cases/autotools.py: use gnu mirror instead of main serverSteve Sakoman2025-10-091-1/+1
| | | | | | | | | | | | | | | | ftp.gnu.org is the main server of the GNU project, however download speed can vary greatly based on one's location. Using ftpmirror.gnu.org should redirect the request to the closest up-to-date mirror, which should result sometimes in significantly faster download speed, depending on one's location. This should also distribute the traffic more across the mirrors. This information was sourced from https://www.gnu.org/prep/ftp.html (From OE-Core rev: f3046716c9c565e6f65d5169694cd3da126cfaeb) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/cases/meta_ide.py: use gnu mirror instead of main serverSteve Sakoman2025-10-091-1/+1
| | | | | | | | | | | | | | | | ftp.gnu.org is the main server of the GNU project, however download speed can vary greatly based on one's location. Using ftpmirror.gnu.org should redirect the request to the closest up-to-date mirror, which should result sometimes in significantly faster download speed, depending on one's location. This should also distribute the traffic more across the mirrors. This information was sourced from https://www.gnu.org/prep/ftp.html (From OE-Core rev: b8cd34e56819e13fd374210cf67d6952d1f2586d) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-10-18 18:52:53 +0000