No one asked for it, but here it is, Gitlab CI for meta-zephyr. Stolen and repurposed from meta-arm. This building and testing should help discover regressions more quickly. And if you include this

Hi everyone, I'm making an image that includes the node-red recipe from meta-iot-cloud. The whole process takes about 30+ minutes for that recipe alone (most of the time spent in do_configure). Now I

After upgrading from Dunfell (YP 3.1) to Hardknott (YP 3.3), our firmware was unable to boot.  Our target hardware is x86-64 booting in legacy BIOS mode using grub on a variety of motherboards and

I have not forgotten about these. My build system is backlogged. I hope to process these by this weekend. -armin

I wonder what are all possible criteria for Bitbake to decide to skip recipe (please compare to reports delivered by bitbake-layers). Recipe overlay, recipe version, others? Which knowledge source to

From: Yann Dirson <yann@...> This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can

From: Yann Dirson <yann@...> Signed-off-by: Yann Dirson <yann@...> --- conf/machine/include/nanopi-m4.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git

From: Yann Dirson <yann@...> This will allow us to define a single set of kernel BSP for all variants of the board (which only need to differ in u-boot dts). Signed-off-by: Yann Dirson

From: Yann Dirson <yann@...> Changes in v4: - install our bsp files in bsp/rockchip/ rather than directly in bsp/ - also add "serial" to MACHINE_FEATURES Changes in v3: - relocate the

Hi Martin, Look how swupdate recipes are done in meta-swupdate: https://github.com/sbabic/meta-swupdate/tree/master/recipes-support/swupdate Basically all variants include the .inc file where

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-security/libseccomp/files/run-ptest | 4 -- .../libseccomp/libseccomp_2.5.1.bb | 47 ------------------- 2 files changed,

Hi Konstantin, Busybox implementation of xargs does not support specifying a delimiter. I suggest you to install the full-featured xargs which is provided by the findutils recipe. You probably need

I'm using the OpenBMC system (https://github.com/openbmc/openbmc) and I've tried to enable AppArmor functionality from the 'meta-security' layer. To achieve this I've added these strings to my

I'm using the OpenBMC system (https://github.com/openbmc/openbmc) and I've tried to enable AppArmor functionality from the 'meta-security' layer. To achieve this I've added these strings to my

The template is not used anywhere, yet, the initial patchset enables the data collection by default. I have left the template in case the data collection is removed from defaults and need to be used

I added a custom layer and under recipes-kernel I try to apply kernel config fragments: └[~]> cat poky/meta-insidem2m/recipes-kernel/linux/linux-yocto_5.10.bbappend FILESEXTRAPATHS_prepend :=

Hello community, I am looking for a best practice / a simple solution for switching the SRCREV in a bitbake recipe between git master HEAD (default, used in nightly builds) and a tagged release

Ah, I forgot to put all of this in a bsp/rockchip/ dir, will reroll.

Generally speaking, I'd say yes, and it would be great if we are able to do that. But from what I've seen of op-tee integration, it looks like vendor platforms usually have different ways of

OE-Core rev: fd1c26ab426c3699ffd8082b83d65a84c8eb8bff added an additional parameter, tmpfsdir, to the API. This caused testimage to no longer work in meta-zephyr. Add that parameter and everything