summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorFabio Estevam <fabio.estevam@nxp.com>2017-01-05 21:33:08 -0200
committerStefano Babic <sbabic@denx.de>2017-01-27 10:34:14 +0100
commit7a037cc91fac1379cd2c2ea3274275c753566e18 (patch)
tree8a04ee10697209e1a1f0b5ee48a4b2d7e21e8620 /doc
parent565cfcf0e177887810cd350869043a3e27309aba (diff)
README: mxc_hab: Adapt the CONFIG_SECURE_BOOT text to Kconfig
Commit 6e1f4d2652e79 ("arm: imx-common: add SECURE_BOOT option to Kconfig") moved the CONFIG_SECURE_BOOT option to Kconfig, so update the mxc_hab README file to reflect that. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.mxc_hab5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/README.mxc_hab b/doc/README.mxc_hab
index b688580f75..c1f8ded5ee 100644
--- a/doc/README.mxc_hab
+++ b/doc/README.mxc_hab
@@ -2,10 +2,9 @@ High Assurance Boot (HAB) for i.MX6 CPUs
To enable the authenticated or encrypted boot mode of U-Boot, it is
required to set the proper configuration for the target board. This
-is done by adding the following configuration in in the proper config
-file (e.g. include/configs/mx6qarm2.h)
+is done by adding the following configuration in the defconfig file:
-#define CONFIG_SECURE_BOOT
+CONFIG_SECURE_BOOT=y
In addition, the U-Boot image to be programmed into the
boot media needs to be properly constructed, i.e. it must contain a