aboutsummaryrefslogtreecommitdiff
path: root/doc/develop
diff options
context:
space:
mode:
authorJan Kiszka2022-03-16 12:12:16 +0100
committerHeinrich Schuchardt2022-03-20 11:03:06 +0100
commit2899296e5cbbf7e28f5e43025eda74382f44f4ca (patch)
treede1fc2ad5ea1d143c5d06e4b5ec8b5bd2ddc4bda /doc/develop
parentaac01df4f589f31746265fd2b6399ed0a338d51d (diff)
doc: uefi: Fix reference to CONFIG_EFI_SECURE_BOOT
There is no CONFIG_UEFI_SECURE_BOOT, and there was never any. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Diffstat (limited to 'doc/develop')
-rw-r--r--doc/develop/uefi/uefi.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst
index b7bf1356276..fe337c88bda 100644
--- a/doc/develop/uefi/uefi.rst
+++ b/doc/develop/uefi/uefi.rst
@@ -105,7 +105,7 @@ The UEFI specification[1] defines a secure way of executing UEFI images
by verifying a signature (or message digest) of image with certificates.
This feature on U-Boot is enabled with::
- CONFIG_UEFI_SECURE_BOOT=y
+ CONFIG_EFI_SECURE_BOOT=y
To make the boot sequence safe, you need to establish a chain of trust;
In UEFI secure boot the chain trust is defined by the following UEFI variables