Various fixes to address errors and warnings when running update.py The following changes since commit 796d2455bb862ed4c71eadfa9fcf4c002752c2f3: templates/*: staticfiles -> static (2022-01-13

The build patches are now included in the upstream, the local binary checkes can be disabled with --disable-ptool-checks, the boostrap doesn't need to be called if the release .tar.gz is

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Since Yocto now uses OpenSSL 3.0, the file packaging need to be

The version number is correctly assigned only when the release .tar.gz is used. Signed-off-by: Petr Gotthard <petr.gotthard@...> --- .../tpm2-abrmd/{tpm2-abrmd_2.4.0.bb =>

This deletes the patches that were unused for a long time, updates the tpm2-tss package and introduces a fix to the version number problem that got introduced with the 3.2.0 version. Signed-off-by:

Also, the recipe is fixed to correctly package the openssl provider. This new tpm2-openssl: - Fixed segmentation fault when a signature algorithm is beging initialized without a private key. -

Calling autoreconf outside git repo causes the version number to be null. This patch makes the version number fixed. Signed-off-by: Petr Gotthard <petr.gotthard@...> ---

Hello. I'd suggest some "house cleaning" of the tpm2-software. (I am a member of the tpm2-software community and an upstream developer of the tpm2-openssl provider.) In general: Some tpm2-software

Hi Casey, I've recently had to activate secureboot on some uefi target. I was trying to use meta-secure-core/meta-efi-secure-boot aft first, but after digging a bit more into meta-intel, I've

Hello, We have an Intel Elkhart Lake device that we are trying to get Secure Boot (via meta-secure-core/meta-efi-secure-boot SELoader) working on using the Dunfell release. This device uses Mender for

Hello All, This may not be the issue with Yocto itself but rather related to properly booting up Linux on Avenger96(STM32MP1) board. I am currently working on Avenger96 with Yocto(Dunfell). Aim is to

Thud has been EOL for a long time. You can see when the support been added here (end of 2019 it

I am currently on Thud so I am missing the support from what I can tell to set INCOMPATIBLE_LICENSE per image. I have tried to find the commit that adds that support but am having some problems

Hi, My comments are inline. I am not a lawyer, but I guess you could mention in your manual that you can dish out a non reversible image which was built with a "dummy" key. This would allow the end

Yes I did something similar initially using BBMASK to minimize the build and in the end requesting them to supply a more minimal build setup. The end result was not a pure BSP layer because we needed

Hi! To elaborate more on the GPLv3 topic: If you were to use secure boot, signed update images, and all that jazz, how can you make your Firmware GPLv3 compliant? Has *anyone* done it or knows a

At Daimler, I put my foot down, and forced them to cleanly rewrite the BSP into an actual BSP layer before we would set up official builds with it. It took several months, but eventually we got

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

Hi, util-linux is a meta package. Install the needed util-linux utilities separately, e.g. util-linux-mount, util-linux-umount. Also ptest you can build as distro feature if you don't install ptest

Qualcomm is notorious for the poor quality of their layers. Just tell the management that they created this situation, and they should be held responsible for delaying whatever product you have to