On Wed, 2023-02-01 at 06:52 +0100, Jan Kiszka wrote: > On 31.01.23 15:58, Moessbauer, Felix wrote: > > On Tue, 2023-01-31 at 09:44 +0100, Jan Kiszka wrote: > > > On 31.01.23 09:27, Felix Moessbauer wrote: > > > > By adding the machine type name, the generated efi binary for > > > > riscv64 is suffixed with the corresponding efi machine name. > > > > > > > > > > And did you successfully test both the bootloader as well as the > > > UKI > > > stub on that arch? > > > > I successfully tested the stub on an u-boot 2022.04. The image was > > assembled via a patched version of the cip-core EBG wic plugin. > > The used hardware was a StarFive VisionFive2 board. Just the > > watchdog > > had to be disabled as the JH7110 watchdog is not yet supported in > > EBG. > > Watchdog on U-Boot-based platforms is generally a U-Boot topic. > > > > > I did not test the UKI yet, but would assume that this works as > > well. > > Testers welcome. > > We do UKI by default in isar-cip-core. Did you actually deviate from > that (unified-kernel=n)?
I also used the standard (non secure-boot) pattern from isar-cip-core. My understanding was that we only use UKI for secure boot, but this is apparently not the case. By that, both workflows are tested and I can confirm that this works. Felix > > Jan > > -- > Siemens AG, Technology > Competence Center Embedded Linux > -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/922f07c1975e1bc07b90855ae18af8c7d7d8f219.camel%40siemens.com.
