@@ -47,9 +47,8 @@ The relevant variables are:
Efidebug command
~~~~~~~~~~~~~~~~
-The efidebug command is used to set and display boot options as well as to
-display information about internal data of the UEFI subsystem (devices,
-drivers, handles, loaded images, and the memory map).
+The efidebug command is used display information about internal data of the UEFI
+subsystem (devices, drivers, handles, loaded images, and the memory map).
.. kernel-doc:: cmd/efidebug.c
:internal:
@@ -224,7 +224,7 @@ UEFI variables. Booting according to these variables is possible via::
bootefi bootmgr [fdt address]
As of U-Boot v2020.10 UEFI variables cannot be set at runtime. The U-Boot
-command 'efidebug' can be used to set the variables.
+command 'bootmgr' can be used to set the variables.
Executing the built in hello world application
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -66,7 +66,7 @@ option to execute next. If no binary can be loaded via *BootNext* the variable
*BootOrder* specifies in which sequence boot options shalled be tried.
The values of these variables can be managed using the U-Boot command
-*efidebug*.
+*bootmgr*.
UEFI hello world application
''''''''''''''''''''''''''''
@@ -132,4 +132,4 @@ See also
* *bootm* for launching UEFI binaries packed in FIT images
* *booti*, *bootm*, *bootz* for launching a Linux kernel without using the
UEFI sub-system
-* *efidebug* for setting UEFI boot variables
+* *bootmgr* for setting UEFI boot variables
We moved the variable related functionality from efidebug to bootmgr command. Change the relevant documentation to indicate the new command Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> --- doc/api/efi.rst | 5 ++--- doc/uefi/uefi.rst | 2 +- doc/usage/bootefi.rst | 4 ++-- 3 files changed, 5 insertions(+), 6 deletions(-) -- 2.30.0