Which QEMU-Version? Which OVMF version (buster/bullseye/something else)? I'm not seeing this, but I'm facing other issues with that firmware provided by bullseye (a crash). Jan

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting is sch

From: Jan Kiszka <jan.kiszka@...> The wrong filename was used for deleting a preexisting image, and that caused mksquashfs to refuse creating a new one. We can achieve this also without an exp

Is that thing configuration-free? Or will the customization recipe need some tuning as well? Jan

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting is sch

I think we actually have to limit the SRC_URI to the cases we support, and that is efibootguard for now. There is no such thing as a if-file-exists entry, unfortunately. Jan PS: You likely want to hav

thanks, applied to next. Jan

Thanks, applied. Jan

Thanks, applied to next. Jan

I think we can skip the second test. The non-secure build variant is already sufficiently covered by the x86 build, and the non-secure u-boot build for arm64 is not too special. Jan

From: Jan Kiszka <jan.kiszka@...> Signed-off-by: Jan Kiszka <jan.kiszka@...> --- ...{linux-cip_4.19.245-cip74.bb => linux-cip_4.19.246-cip75.bb} | 2 +- .../{linux-cip_5.10.118-cip8.bb

From: Jan Kiszka <jan.kiszka@...> Signed-off-by: Jan Kiszka <jan.kiszka@...> --- ....233-cip69-rt24.bb => linux-cip-rt_4.19.245-cip74-rt25.bb} | 2 +- ...4.302-cip68-rt38.bb => linux-ci

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting is sch

buster vs. bullseye: the former worked (as tested in CI), the latter was broken. As suspected, patch 3 needed to go before patch 1 - or folded into it. I did the latter while merging. Thanks, Jan

Err, no, we are building that ("extension: test", see e.g. https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/2554473964). Now I'm confused, specifically as I've seen build issues locally as

Hmm, just realized that we are not testing this recipe in CI. We should probably enable kas/opt/test.yml for some representative target(s) to close this gap. Jan

OK, then we can keep the ordering. Jan

Was that already the case with the previous version? If not, this should probably be moved the front of the series, right? Jan

Now that squashfs is converted, that class should be pushed to Isar soon. Will "just" need a test case there. Maybe verity could go upstream as well, though it is more specific and may not make too mu

Will, CI should fail without patch 4, e.g. Probably, it's an all-or-nothing series from that perspective, and it only makes sense to break it up for readability reasons. OK. Looking at more details no