From: Quirin Gylstorff <quirin.gylstorff@...> As the usage of a unified kernel image freeze the kernel commmandline during build time the rootfs selection for swupdate can no longer be done

From: Quirin Gylstorff <quirin.gylstorff@...> This patchset adds secureboot with efibootguard to cip-core. The image build signs the efibootguard bootloader (bootx64.efi) and generates a

From: Quirin Gylstorff <quirin.gylstorff@...> Add a fat configuration to access FAT Partitions on the qemu-amd64 target. Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> ---

From: Quirin Gylstorff <quirin.gylstorff@...> Create a swu file for swupdate to update devices in the field. This is done in the same step as the complete image build to avoid diverging

From: Quirin Gylstorff <quirin.gylstorff@...> Add swupdate for A/B software updates. Currently the Round Robin handler in lua supports efibootguard as bootloader. The u-boot implementation is

From: Quirin Gylstorff <quirin.gylstorff@...> Add wks for: - simatic-ipc227e - qemu-amd64 Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- kas/opt/ebg-swu.yml

From: Quirin Gylstorff <quirin.gylstorff@...> Add the bootloader efibootguard for A/B partition update on x86 with EFI. Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> ---

From: Quirin Gylstorff <quirin.gylstorff@...> This patchset adds efibootguard, swupdate to allow A/B updates in cip-core. The update mechanism is currently only implemented for

From: Quirin Gylstorff <quirin.gylstorff@...> swupdate 2020.04 requires libubootenv as build dependency. libubootenv is a library that provides a hardware independent way to access to U-Boot

I will fix that in v2

Sure

it uses the partuuid from root. If someone finds a better way to get the current root without parsing the kernel commandline I would use that. I move the patch to the a/b update patch. -- Quirin

Seems not really specific to secure-boot, rather related to the initramfs-based rootfs selection. But is that one actually using PARTUUID in the end? Or rather device paths? Anyway, I'm not against

Hi,

Hi, CIP kernel team has released Linux kernel v4.19.130-cip29. The linux-4.19.y-cip tree has been updated base version from v4.19.128 to v4.19.130. You can get this release via the git tree at:

Applied to next, also fixing up the remaining README spots. Thanks, Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

From: Quirin Gylstorff <quirin.gylstorff@...> Move kas related files into folder kas for a cleaner repository root. Update isar to remove patches folder for now Changes V2: - move kas-cip

From: Quirin Gylstorff <quirin.gylstorff@...> Create folder structure kas -> general configuration kas/board -> all supported boards kas/opt -> all kas option files Signed-off-by: Quirin

I just released 0.7. Maybe you could update when preparing v2. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

Internal mirror. You need to go back to upstream. And do we actually need gitsm? It is not a mature feature of bitbake, thus generally discouraged. Jan -- Siemens AG, Corporate Technology, CT RDA