The UEFI specification paragraph quoted above notes: > The watchdog timer is only used during boot services. On successful > completion of ExitBootServices() the watchdog timer is disabled. Thus disabling the watchdog is _the_ only proper behavior. Adjust the wording accordingly. Cc: Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> --- Documentation/boards/efi.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst index 2178c9ab4293..f04b1d32378b 100644 --- a/Documentation/boards/efi.rst +++ b/Documentation/boards/efi.rst @@ -350,7 +350,7 @@ https://uefi.org/sites/default/files/resources/UEFI_Spec_2_1_D.pdf Current linux kernel (v5.0) will execute ExitBootServices() during the early boot stage and thus will automatically disable the (U)EFI watchdog. Since it is -a proper behavior according to the (U)EFI specification, it is impossible to +the proper behavior according to the (U)EFI specification, it is impossible to protect full boot chain by using this watchdog only. It is recommended to use an alternative hardware watchdog, preferably started before the bootloader. If (U)EFI firmware lacks this feature, the bootloader should be able to start an alternative -- 2.23.0 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox