On Wed, Oct 23, 2019 at 06:55:56PM +0200, Ahmad Fatoum wrote: > 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.rem...@pengutronix.de> > Signed-off-by: Ahmad Fatoum <a.fat...@pengutronix.de> > --- > 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 > >
Reviewed-by: <o.rem...@pengutronix.de> -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
