I am using the meta-intel layer with a machine configured to intel-core-i7 and core-image-Sato. A very basic build and using bmaptool to generate an image from .wic to a usb stick.The problem is that

Thanks Quentin, that did the trick. -- "A man can fail many times, but he isn't a failure until he begins to blame somebody else." -- John Burroughs

Signed-off-by: Armin Kuster <akuster808@...> --- meta-integrity/recipes-kernel/linux/linux-%.bbappend | 6 +----- meta-integrity/recipes-kernel/linux/linux_ima.inc | 5 +++++ 2 files

Signed-off-by: Armin Kuster <akuster808@...> --- meta-integrity/README.md | 18 +++++++++++++++++- .../classes/sanity-meta-integrity.bbclass | 10 ++++++++++

Signed-off-by: Armin Kuster <akuster808@...> --- .../linux/linux-yocto_5.%.bbappend | 18 +----------------- .../recipes-kernel/linux/linux-yocto_tpm.inc | 17 +++++++++++++++++ 2

Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/README | 19 +++++++++++++++++++ meta-tpm/classes/sanity-meta-tpm.bbclass | 10 ++++++++++

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/linux/linux-yocto-dev.bbappend | 1 - 1 file changed, 1 deletion(-) delete mode 100644

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/linux/linux-yocto-dev.bbappend | 4 +--- recipes-kernel/linux/linux-yocto_5.%.bbappend | 4 +---

Signed-off-by: Armin Kuster <akuster808@...> --- README | 18 ++++++++++++++++++ classes/sanity-meta-security.bbclass | 10 ++++++++++ conf/layer.conf

This series superceeds the privious set to help pass the check-layer scrip. Armin Kuster (7): meta-security: add sanity check meta-security/recipe-kernel: use sanity check linux-yocto-dev: drop

Op 14-04-2021 om 06:59 schreef Richard Purdie: I like the idea. Unfortunately the patch doesn't apply to Gatesgarth, so I couldn't test it. Any chance you would be doing a refresh?

Hi, fsl,use-minimum-ecc is a property not a node, you need to use /delete-property/ instead, c.f.

Hi, I am building following imx6ulz-kobs.dts file to a dtb in zeus: $ cat imx6ulz-kobs.dts #include "imx6ulz.dts" /{ model = "customized imx6ull"; compatible = "fsl,imx6ull"; }; &gpmi {

In your upgrade, did the bootloader/initramfs/kernel version change ? The passing of the device tree to the kernel is (commonly) part of the bootflow, so changes to any of the components in that flow

On Fri, Jun 4, 2021 at 8:37 AM Bruce Ashfield via lists.yoctoproject.org <bruce.ashfield=gmail.com@...> wrote: Apologies on this, I see in the follow up email you did mention

I took a quick look, is this warning coming from the layer index ? That would be important information to convey when sending changes like this. That being said, it is a longer fix to get that

Nope. It is compatible with those releases, so they need to stay. I see no valid reason to be limited to a certain number of characters. That is just as arbitrary, I'll keep it as-is. Bruce -- -

Please ignore it according to Martin's comment in oe-devel list. Regards, Kai -- Kai KangWind River Linux

Hi, I made the following observation in my custom Yocto system: The device tree loaded by the Linux kernel is one that is only available in the barebox directory, but not available in the kernel

From: Kai Kang <kai.kang@...> There is no hardknott branch yet, so keep 'hardknott' rather than replace it. Signed-off-by: Kai Kang <kai.kang@...> --- conf/layer.conf | 2 +- 1