Improve the Capsule Update flow, so that if the
`CONFIG_EDK2_GRAPHICAL_CAPSULE_PROGRESS` is set but no monitor is
detected, the update doesn't fail but rather falls back to serial
mode.
Signed-off-by: Filip Lewinski <filip.lewinski@3mdeb.com>
Trace various branches of capsule processing to report how handling of
a capsule or its payload went. The report is displayed at the end of
the second round of capsule processing or after the first one if it ends
with a reboot.
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
That is loading and processing on-disk capsules during the same boot
without relocating the capsules to a dedicated non-volatile storage on
ESP or loading them as in-RAM capsules and then rebooting.
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
The typos got in the way of grepping for output lines and reporting
errors as numbers is not very helpful.
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
The text field between the list of files and option to create files or
directories was a selectable empty string with no functionality. When
moving through the menu one had to press the arrow one extra time to
navigate to the files. As it is confusing, change the text field to
subtitle so it is not selectable anymore.
Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
Prevent debugging on serial port (whether physical or cbmem console) at
runtime by not doing anything after boot services are exited. It will
stop calling SerialPortWrite if EFI switches to runtime and avoid access
to cbmem CONSOLE buffer which is neither marked as runtime code nor data.
If serial debugging will be necessary, actually mark coreboot's CONSOLE
buffer as runtime data (it's location and size are known).
Solves the issue with Xen backtrace on EFI reset system runtime service:
https://github.com/Dasharo/dasharo-issues/issues/488#issuecomment-1772758851
Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
