dependency - gitsm (see patch 1/7) - please factor out revisions into separate variables Or can we also address the revisions via release tags? The recipe carries a release version number in the

Nope, self-built one -> wrong patch ordering, 2/7 must come first. Jan -- Siemens AG, Technology Competence Center Embedded Linux

Do we really need the second-class supported gitsm fetcher here? Also, destsuffix and rev are both redundant (they are defaults). Oh, indention by 4 spaces would be sufficient. Redundant. Do we

From: Sven Schultschik <sven.schultschik@...> This patch is not ment for merge but shows how to generally test the implementation of the optee and rpmb driven secure boot qemu

From: Sven Schultschik <sven.schultschik@...> The start-qemu shell script need some adjustments to switch on secure in the machine statement and adds the virtual random number generator if

From: Sven Schultschik <sven.schultschik@...> The u-boot-efi-ebg-op-tee-qemu kas file combines the different recipes to create an image which can be booted with qemu and provides secure boot

From: Sven Schultschik <sven.schultschik@...> Qemu itself is missing a implemented emulation of an RPBM (replay protected memory) which is part of an emmc. Therefore currently a u-boot patch,

From: Sven Schultschik <sven.schultschik@...> provide a recipe to generate the needed binary to start a secure boot qemu with integrated optee and active RPMB replay protected memory

From: Sven Schultschik <sven.schultschik@...> provide a recipe to create the BL32_AP_MM.fd binary by edk2 which is needed for the qemu optee generation as dependencie. Signed-off-by: Sven

From: Sven Schultschik <sven.schultschik@...> The recipe provides the possibility to create optee-os binaries for use inside of an qemu secureboot setup with edk2, rpmb, u-boot and

From: Jan Kiszka <jan.kiszka@...> The usage of class is not bound to wic, thus we should not declare any dependency of wic on it. This makes the verity pattern analogous to the squashfs one

Hi Chris, ​ I can see in Linaro/test-definitions (https://github.com/Linaro/test-definitions/tree/master/automated/linux) there are 123 test-suites are present but only 4 test-suites are running on

Hello Sarath, Some of those test jobs you linked to are very old. Looking at more recent jobs the smc issue you reported is no longer there. However the RT tests are having issues

Hello Sarath, The tests we currently run in our GitLab CI setup are listed

Thanks, applied. And then I applied Uladzimir's patch on top again. Result now in next. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Quirin Gylstorff <quirin.gylstorff@...> This fixes issues https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/44. Signed-off-by: Quirin Gylstorff

Need to drop it again for now as the current value of TMP_FS_OPTIONS in the recipe is not ready for use. See also https://gitlab.com/cip-project/cip-core/isar-cip-core/-/issues/44. We need a working

Hi Team , I can see in Linaro/test-definitions (https://github.com/Linaro/test-definitions/tree/master/automated/linux) there are 123 test-suites are present but only 4 test-suites are running on cip

Hi Team, I could able to see there are few tests are running in the CIP LAVA platform. I am showing the list below what all LAVA tests are running in the CIP LAVA platform. Test-case CIP

Hi, CIP kernel team has released Linux kernel v4.19.261-cip83 and v5.10.147-cip18. The linux-4.19.y-cip tree has been updated base version from v4.19.259 to v4.19.261, and the linux-5.10.y-cip tree