On 15.01.24 00:20, 'Earl Chew' via EFI Boot Guard wrote: > While debugging an issue, it was helpful to have a short delay before > the StartImage() handoff in order to read/capture the efibootguard > messages. >
Are you trying to catch the messages from a screen, or are they overwritten on a UART by the succeeding EFI app? > For now, I used a 3 second BS->Stall() before invoking StartImage(). > > While this seems useful and unobtrusive enough to me, upstream users are > probably used to the existing behaviour. > > What does the team think about another environment key > (watchdog_timeout_sec vs start_delay_sec) to achieve this? > The problem is that BG_ENVDATA is fully packed and has no extension space (yeah...). We ran into that issue before, and the long-term plan is to have a new configuration format, plus a clear migration path. Short-term, not much is possible without breaking existing deployments. Jan -- Siemens AG, Technology Linux Expert Center -- 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/ccd42a74-b702-4f7b-a41b-5fb2394ea4c8%40siemens.com.
