All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH] doc: update efidebug command
Date: Wed, 10 Feb 2021 13:22:02 +0200	[thread overview]
Message-ID: <20210210112202.362706-1-ilias.apalodimas@linaro.org> (raw)

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(-)

diff --git a/doc/api/efi.rst b/doc/api/efi.rst
index cb2a1c897e69..2ecb3ffe324f 100644
--- a/doc/api/efi.rst
+++ b/doc/api/efi.rst
@@ -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:
diff --git a/doc/uefi/uefi.rst b/doc/uefi/uefi.rst
index 02a377b834f0..bc20e2813fa2 100644
--- a/doc/uefi/uefi.rst
+++ b/doc/uefi/uefi.rst
@@ -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
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/doc/usage/bootefi.rst b/doc/usage/bootefi.rst
index 282f22aac966..89117806a8d8 100644
--- a/doc/usage/bootefi.rst
+++ b/doc/usage/bootefi.rst
@@ -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
-- 
2.30.0

                 reply	other threads:[~2021-02-10 11:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210210112202.362706-1-ilias.apalodimas@linaro.org \
    --to=ilias.apalodimas@linaro.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.