Hi Jan, Thanks for the work to support secureboot in arm64. I am building the arm64 image to check secureboot support in arm64, got the below error and do you have any idea about this

cip-gitlab/ci/pavel/linux-test baseline: 75 runs, 10 regressions (v5.10.109-cip5-384-g722204542e8a) Regressions Summary ------------------- platform | arch | lab |

cip/linux-5.10.y-cip-rt build: 188 builds: 3 failed, 185 passed, 4 errors, 11 warnings (v5.10.109-cip5-rt4) Full Build Summary:

cip-gitlab/ci/pavel/linux-test build: 185 builds: 3 failed, 182 passed, 4 errors, 10 warnings (v5.10.109-cip5-384-g722204542e8a) Full Build Summary:

Hi! New realtime trees should be available at kernel.org. Trees are available

From: Jan Kiszka <jan.kiszka@...> There is no "qemu-armhf", we called it qemu-arm. Therefore, finding its images failed. Rename DISTRO_ARCH to QEMU_ARCH and set it to "arm" for the related

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc smc: 3 runs, 1 regressions (v5.10.112-cip6-218-g8253434cd56a) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc kselftest-seccomp: 4 runs, 1 regressions (v5.10.112-cip6-218-g8253434cd56a) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline: 106 runs, 8 regressions (v5.10.112-cip6-218-g8253434cd56a) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-nfs: 22 runs, 1 regressions (v5.10.112-cip6-218-g8253434cd56a) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc build: 187 builds: 4 failed, 183 passed, 5 errors, 11 warnings (v5.10.112-cip6-218-g8253434cd56a) Full Build Summary:

Thanks, applied. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Quirin Gylstorff <quirin.gylstorff@...> Update SWUpdate to commit https://salsa.debian.org/debian/swupdate/ 344548c816b555c58ec199f31e45703897d23fb5. This contains the upstream version

Hi Koguchi-san, It will be fixed in 5.10.114. 5.10.114-rc1:

Iwamatsu-san,

From: Jan Kiszka <jan.kiszka@...> We just need to pick up the newly deployed firmware.bin as -bios, analogously to the x86's OVMF, and switch to a disk image. A separate key storage is not

From: Jan Kiszka <jan.kiszka@...> We crash in case of an empty command line with non-unified kernel images right now. Just avoid cmdline==None, will also make upcoming

From: Jan Kiszka <jan.kiszka@...> This will be used for booting via UEFI, both in open and locked-down secure mode. The secure mode variations can be selected by adding "secureboot" to

From: Jan Kiszka <jan.kiszka@...> Switch to the unified kernel image and its generator script that EFI Boot Guard now provides. So far this only simplifies the generation process. But it will

From: Jan Kiszka <jan.kiszka@...> Pick up the DTBs specified via DTB_FILES and embed them into the unified kernel image that the wic plugin can generate. This does not work for normal