From: Ming Liu <liu.ming50@...> Or else wic will fail without "--no-fstab-update" option. Signed-off-by: Ming Liu <liu.ming50@...> --- meta-integrity/classes/ima-evm-rootfs.bbclass | 3

From: Ming Liu <liu.ming50@...> Otherwise, ima script would not run as intended. Signed-off-by: Ming Liu <liu.ming50@...> --- .../recipes-core/initrdscripts/initramfs-framework-ima/ima

From: Ming Liu <liu.ming50@...> The current logic in ima-evm-rootfs.bbclass does not guarantee ima_evm_sign_rootfs is the last function in IMAGE_PREPROCESS_COMMAND by appending to it, for

From: Ming Liu <liu.ming50@...> /etc/ima-policy > /etc/ima/ima-policy. Signed-off-by: Ming Liu <liu.ming50@...> --- .../recipes-core/initrdscripts/initramfs-framework-ima/ima | 2

From: Ming Liu <liu.ming50@...> 'ima' does not have to be in native DISTRO_FEATURES, unset it to avoid sanity check, this fixes a following error: Signed-off-by: Ming Liu

From: Ming Liu <liu.ming50@...> Ming Liu (5): ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty initramfs-framework-ima: fix a wrong path meta: refactor IMA/EVM sign rootfs

As others have said, please look at the buildstats class and the data it saves into TMPDIR/buildstats. It should do what you want and we have tools like pybootchart which can show it

So, what is your MACHINE variable set to? Maybe knowing that, somebody can help. Zee

As said, buildstats is *exactly* what you want. There's a forked pybootchart in oe-core that can visualise the data too. Ross

Hello folks, I have an issue integrating av1 in yocto. I get the compile error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i

Hi, Please see my comments in-line. ... This looks like the patch you/mender try/tries to apply does not work with your u-boot version.[0] [0]

Yes in some layers they do work across releases but That does have some restrictions and maintenance costs eg if you are patching a recipe via a bbappend then use more liberal bbappend names using %

Thank you for the answer :-). Yes, that works, and it seems like it is commonly used already. But because there is a way to define which versions are supported in the machine configuration, I thought

perhaps you should create a new branch for this layer which will be compatible with gatesgarth, you can seed it with dunfell branch and then make needed changes <jonas.vautherin@...> wrote:

You're welcome :-) I take notes every week, but had stopped sending emails to the list at the end of each meeting. A couple people mentioned privately that they appreciate the notes being formatted

Good evening, I am using Yocto Gatesgarth, and I was just updating a layer that was written for Dunfell. In the `conf/layer.conf`, I can simply add "gatesgarth" to `LAYERSERIES_COMPAT_pocketbeagle`,

Trevor, Thanks for taking and sending the minutes. -armin

you could also look into using buildstats bbclass https://wiki.yoctoproject.org/wiki/TipsAndTricks/InvestigatingBuildTime > >

"time bitbake recipe" is perfect for manual things. But I wanted to also measure the recipe times when building the entire image. I ended up creating a bbappend with new pre/post tasks for the main

Yocto Technical Team Minutes, Engineering Sync, for Feb 16 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to