[yocto] [meta-security][PATCH 4/4] dm-verity-img.bbclass: add DM_VERITY_DEPLOY_DIR

If image recipe A wants to embed another image B which used dm-verity-img.bbclass and generated the .wks file, then recipe B must deploy everything to IMGDEPLOYDIR but recipe A finds the output from DM_VERITY_DEPLOY_DIR = "${DEPLOY_DIR_IMAGE}". Now both A and B images can use dm-verity-img.bbclass

[yocto] [meta-security][PATCH 1/4] tpm2-tss: support native builds

systemd tool ukify https://www.freedesktop.org/software/systemd/man/latest/ukify.html depends on systemd-measure https://www.freedesktop.org/software/systemd/man/latest/systemd-measure.html which depends on tpm2-tss. So to support creating UKI images containing both kernel and initramfs with system

[yocto] [meta-security][PATCH 2/4] dm-verity-img.bbclass: use bc-native

From: Erik Schilling Build host may not have bc. Signed-off-by: Mikko Rapeli --- classes/dm-verity-img.bbclass | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass index 045c860..3dd2b94 100644 --- a/classes/dm-

[yocto] [meta-security][PATCH 3/4] dm-verity-img.bbclass: remove IMAGE_NAME_SUFFIX

From: Erik Schilling It is embedded into IMAGE_NAME since poky master branch commit 6f6c79029bc2020907295858449c725952d560a1 Signed-off-by: Mikko Rapeli --- classes/dm-verity-img.bbclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/classes/dm-verity-img.bbclass b/cla

Re: [yocto] [meta-rockchip] [PATCH v2 1/1] orangepi-5-plus: Support Orange Pi 5 Plus single-board computer

A new patch v3 has been created/sent, this patch is outdated, so please use this one instead => [yocto] [meta-rockchip] [PATCH v3 1/1] orangepi-5-plus: Support Orange Pi 5 Plus single-board computer ( https://lists.yoctoproject.org/g/yocto/topic/103295196?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Arecentpos

[yocto] [meta-rockchip] [PATCH v3 1/1] orangepi-5-plus: Support Orange Pi 5 Plus single-board computer

From: Abhisit Sangjan Being merged when the u-boot version is 2024.01-rc5 or newer and the Linux Kernel version is 6.7 or newer Orange Pi 5 Plus is RK3588 based SBC featuring: - 2x 2.5G ethernet ports – onboard NIC hooked to PCIe 2.0 interface - 2x USB 2.0 host ports - 2x USB 3.0 host ports (ex

Re: [yocto] do_populate_sdk_ext failed

Hi Alex:   Nice to meet you and thanks for the comments. Fully understand! We're not trying to push you for the fix(definitely not). Instead, we always appreciate your efforts on bringing Yocto to us. Really so many R&Ds love it. It is even much more than our expectation when we tried to welcome

[yocto] [meta-rockchip] [PATCH] rock 4c+: add

ROCK 4C+ is a Rockchip RK3399-T based SBC from Radxa. Main differences of ROCK 4C+ compared to other ROCK 4 SBC. - Rockchip RK3399-T SoC - DP from ROCK Pi 4C replaced with micro HDMI 2K@60fps - 4-lane MIPI DSI - RK817 Audio codec Signed-off-by: Stephen Chen --- conf/machine/rock-4c-plus.conf | 1

[yocto][meta-lts-mixins] kirkstone/rust branch tracking oe-core master

Currently, there's the rust-1.68 mixins layer. That branch is set to stay on 1.68 (https://lists.yoctoproject.org/g/yocto/message/60259). There are some use cases for a newer version. For example, we use kirkstone in combination with meta-virtualization master and go/rust mixins. The latest ne

Re: [yocto] do_populate_sdk_ext failed

On Wed, 20 Dec 2023 at 01:51, Ming Wen wrote: > Song-Jun and myself are in the same team. We spent some efforts to make it > happen for " do_populate_sdk_ext" finally by fixing some issue in Poky(we're > using latest Kirkstone 4.0). But as you mentioned, when we tried the > generated eSDK, we f

[yocto] INITRAMFS_IMAGE variable changing during kernel module build

The configuration was specified in the build using "-R": bitbake -R layers/meta-manufacturing/conf/iotr_rammfg.conf mlinux-iotr-rammfg-image It is not obvious to me how an external kernel module will use INITRAMFS_IMAGE, but I am seeing this message when running diagnostics after an external ker