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

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

Hi, I am trying to include qca9377 module in my image (yocto-gatesgarth). I am using command bitbake imx-image-full, and i added two lines in my local.conf file: MACHINE_FEATURES += " qca9377" IMAGE_I

Hi, Myself had to ask web search engine for usage of Task Dependency Explorer taskexp as I didn't succeed on search in Yocto materials. Hence, the way I try to use taskexp might be not right. In the f

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

Hi I am new to Yocto project and have little experience in Linux. In my computer, Root folder is having free space of 65 GB and Home is having 45 GB free space. Shall I get the poky in root folder and

for a current project (and subsequent projects), i want to define a hardware bringup image; that is, a really basic image chock-full of low-level utilities for debugging initial board bringup. this me

The current implementation was overwriting the sshd_config and sshd assuming PAM is needed by default. openssh should use the default sshd_config packaged with the component if no distro specific need

From: Meng Li <Meng.Li@...> Signed-off-by: Meng Li <Meng.Li@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 756e7f4..

Hi, we are developing an application in go and use the "go-mod" bb-class from poky. This works fine. However, the problem is, that the dependencies in go.mod are now fetched in the compile phase and n

Hi everyone, I've installed nodejs and node-red by using meta-oe and meta-iot-cloud, with IMAGE_INSTALL_append = " nodejs node-red bash" it was initially working but then I've got some pseudo aborts t

Working with zeus 3.0.4, extended SDK… Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ? Thanks… When I add in native-python3 support # # Additi

Yocto Technical Team Minutes, Engineering Sync, for April 13, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

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@...> 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@...> 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 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

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 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 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