My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more then enough with 4 core + HT, but now

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.7.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BS

Signed-off-by: Khem Raj <raj.khem@...> --- ...rincs-Check-for-__builtin_ia32_rdtsc.patch | 33 +++++++++++++++++++ .../nativesdk-mingw-w64-runtime_7.0.0.bb | 2 ++ 2 files changed, 35 insertions(+) crea

For more info see: https://github.com/openwall/lkrg Add to local.conf: IMAGE_INSTALL_append = " kernel-module-lkrg" Need these kconfig options enabled: CONFIG_KALLSYMS_ALL=y CONFIG_JUMP_LABEL=y CONFIG

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-scanners/clamav/clamav_0.104.0.bb | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/recipes-scanners/clamav/clamav_0.104.

A build flagged for QA (yocto-3.1.7.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.7.rc1 Build hash information: bitbake: 017a39ed05d065

Add a column "Host Data" to publish the host data collected. Signed-off-by: Sakib Sajal <sakib.sajal@...> Signed-off-by: Randy MacLeod <Randy.MacLeod@...> --- scripts/generate-testresult-index.py | 18

collect-data template generates host_stats files which are collected. All files are published, file names are determined by the contents: - Files that contain "top" output are named host_stats_<number

add the variables required to collect data to "defaults" so that data is collected on all builds. Signed-off-by: Sakib Sajal <sakib.sajal@...> Signed-off-by: Randy MacLeod <Randy.MacLeod@...> --- conf

collect-data template can run arbitrary commands/scripts on a regular basis and logs the output in a file. See oe-core for more details: edb7098e9e buildstats.bbclass: add functionality to collect bui

Greetings, Wouldn't it make sense to reverse the order of migration guides in the reference manual (https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#migration)? I guess it would be eas

Drop backported patches: 0001-Mark-declaration-with-extern.patch 0006-Fix-tools-Fix-definition-of-curses_indented_printf.patch Rebase patches: 0001-Fix-python3-usage.patch 0001-pacemaker-fix-compile-e

I have created rootfs with Rocko yocto version. I need sysyvinit as system manager instead of Systemd. I have tried with following in local.conf DISTRO_FEATURES_append = " sysvinit" VIRTUAL-RUNTIME_in

From: Yann Dirson <yann@...> FIXME: - this is not specific to the board, and would indeed apply to any SoC supported by OP-TEE. - should rather be selected by "optee" in DISTRO_FEATURES, maybe using a

From: Yann Dirson <yann@...> FIXME: - provide an .scc with proper information - maybe bundle with dts overlay - select a more suitable path in config namespace --- recipes-kernel/linux/files/bsp/tee.c

From: Yann Dirson <yann@...> This is the current state of working patches being discussed in https://github.com/OP-TEE/optee_os/issues/4542 --- conf/machine/include/rk3399.inc | 2 + ...399-enable-seri

From: Yann Dirson <yann@...> This effectively sets up a single switch to activate OP-TEE support. Disabling optee-* recipes when the feature is not set is not the primary goal, though it can occasiona

From: Yann Dirson <yann@...> This tries to provide a generic framework for easier OP-TEE support in BSP layers. It would probably make sense to have the generic parts in meta-arm when they are finaliz

From: Yann Dirson <yann@...> This instructs TF-A to: - load OP-TEE OS as BL32, but still relies on the actual image to be provided through other means, eg. in u-boot.itb - run opteed as Secure Payload

From: Yann Dirson <yann@...> This causes OP-TEE to get included into the u-boot.itb fitImage so u-boot can load it for the trusted-firmware-a BL31 to run it. This is configured automatically when DIST