linux/poky.git/scripts, branch master-next

runqemu: resize rootfs image to power of 2 for SD or pflash

2025-11-07T13:15:35+00:00

QEMU requires that SD and pflash images are sized to be a power of 2 (e.g., 32M, 64M, etc). So, if the image being used is not a power of 2 and it's being used for SD or pflash, increase it to the next power of 2 size via the truncate command. This might not be an actual spec requirement, and is being investigated in https://gitlab.com/qemu-project/qemu/-/issues/1754 (From OE-Core rev: 4e2f75f89843d629d9e0b9d3f7a68414091f2b70) Signed-off-by: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

runqemu: remove setting of mem on kernel command line for certain systems

2025-11-07T13:15:35+00:00

Some emulated hardware will not boot if mem is set on the kernel command line (all of the Raspberry Pi machines seemed to fail with this set, possibly many others). Also, it is not necessary if the device tree file is present, as that _should_ have the memory size specified in it. Add a check for QB_DTB and don't set mem in the kernel command line if present. (From OE-Core rev: cf3524dbd536c206a49e06da8bb1067900fdc777) Signed-off-by: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

wic/engine: fix copying directories into wic image with ext* partition

2025-11-07T13:15:35+00:00

wic uses debugfs to write on ext* partitions, but debugfs can only write to the current working directory and it cannot copy complete directory trees. Running 'wic ls' on a copied directory show this: -l: Ext2 inode is not a directory Fix this by creating a command list for debugfs (-f parameter) when recursive parsing the host directory in order to create a similar directory structure (mkdir) and copy files (write) on each level into the destination directory from the wic's ext* partition. (From OE-Core rev: 7f6205e9e98f2e885b29e80ee7ca08b66b909429) Signed-off-by: Daniel Dragomir Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

package_manager/oe-pkgdata-util: fix complementary package installation

2025-11-07T13:15:35+00:00

We currently have a problem regarding complementary package installation, that is, if 'oe-pkgdata-util glob' maps out packages that are not in the oe-rootfs-repo, we will get error like below: No match for argument: lib32-glibc-locale-en-gb Error: Unable to find a match: lib32-glibc-locale-en-gb Here are the steps to reproduce the issue: 1. Add the following lines to local.conf: require conf/multilib.conf MULTILIBS ?= "multilib:lib32" DEFAULTTUNE:virtclass-multilib-lib32 ?= "core2-32" IMAGE_INSTALL:append = " lib32-sysstat" 2. bitbake lib32-glibc-locale && bitbake core-image-full-cmdline This problem appears because: 1) At do_rootfs time, we first contruct a repo with a filtering mechanism to ensure we don't pull in unneeded packages.[1] 2) oe-pkgdata-util uses the pkgdata without filtering. In order to avoid any hardcoding that might grow in the future[2], we need to give 'oe-pkgdata-util glob' some filtering ability. So this patch does the following things: 1) Add a new option, '-a/--allpkgs', to 'oe-pkgdata-util glob'. This gives it a filtering mechanism. As it's an option, people who use 'oe-pkgdata-util glob' command could use it as before. 2) Add to package_manager 'list_all' function implementations which list all available functions in our filtered repo. [1] https://git.openembedded.org/openembedded-core/commit/?id=85e72e129362db896b0d368077033e4a2e373cf9 [2] https://lists.openembedded.org/g/openembedded-core/message/221449 (From OE-Core rev: 72824e1b763838252b8533ec679535f5b77e1cc8) Signed-off-by: Chen Qi Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

oe-build-perf-report: filter used measurements for each commit

2025-11-07T13:15:35+00:00

As the poky repository is no longer used, measurements are indexed using the oe-core commit. But as bitbake, oe-core and meta-yocto are now retrieved from separate gits, while measuring performances for a given branch at some time interval, we can get the same commit for oe-core but different ones for bitbake or meta-yocto. As a consequence, metadata associated with the same index (oe-core commit) might differ. Today this is not supported, as we do expect all metadata for a given version remain the same. For each oe-core commit, filter the measurements, in order to only keep the ones with the metadata matching the last measurement found for the said commit. Fixes [YOCTO #16014] (From OE-Core rev: 90aeba0abdac086495fc39486ab37d41f84477ee) Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

oe-setup-layers: make "path" optional

2025-11-03T17:40:41+00:00

Layer names and path are often redundant. Allow users to omit the path key when it is equal to the layer name by using the layer name as a default value for its path. For example, from layers.example.json: "sources": { "meta-alex": { "path": "meta-alex" }, "meta-intel": { "path": "meta-intel" }, "poky": { "path": "poky" } }, Update the schema to stop requiring "path" and remove it in example for "meta-intel". (From OE-Core rev: 7f36f0526fae5a81f9bc02e16cc849a2b1ea5797) Signed-off-by: Yoann Congal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

wic: add wic tests and support setting GPT diskid

2025-10-30T11:06:28+00:00

Also extend implementation to allow defining the diskid for GPT partitions. Add unit tests for wic.py to cover new setting. (From OE-Core rev: 0d5da9477703212d3cfb63828c5c38afdb162e43) Signed-off-by: Steffen Greber Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

devtool/ide_sdk: Fix help message syntax

2025-10-27T17:20:42+00:00

(From OE-Core rev: 161cc3742e5a787beabfa6748547d93037185725) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

improve_kernel_cve_report: add option to read debugsources.zstd

2025-10-27T17:20:42+00:00

Adding option to be able to import debugsources.zstd directly. The linux-yocto-debugsources.zstd is generated in every build and does not require any additional configuration. In contrast, SPDX_INCLUDE_COMPILED_SOURCES needs to be explicitly added and increases build time. (From OE-Core rev: c84a8958f30bbb982656ddcbe7476f6f81e1a6fb) Signed-off-by: Daniel Turull Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

devtool: un-/deploy-target: put deploylist into destdir

2025-10-27T17:20:42+00:00

When deploying on devices with a RO root-filesystem, devtool would fail on writing to the hard-coded "deploylist_path = '/.devtool'" Since devtool already supports deploying to a different root-prefix with: hostname[:destdir], we can make use of this guaranteed RW location to place the deployment-list there. Add the destdir parameter to the _prepare_remote_script function, to construct the deploylist_path from it. For the 'undeploy' the same host:destdir splitting logic is used as in 'deploy'. Now it is possible to modify and build a recipe 'foo-bar' with devtool, and have its ./image content deployed through: $build> devtool deploy foo-bar target:/opt/development-overlay Or removed again with: $build> devtool undeploy foo-bar target:/opt/development-overlay (From OE-Core rev: 216a4c4a4ee58222127c830ac56126bdbb95308d) Signed-off-by: Johannes Schneider Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie