summaryrefslogtreecommitdiff
path: root/Documentation/mainboard
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/mainboard')
-rw-r--r--Documentation/mainboard/index.md2
-rw-r--r--Documentation/mainboard/lenovo/vboot.md12
2 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/mainboard/index.md b/Documentation/mainboard/index.md
index 3426395dfb..e80ff0b512 100644
--- a/Documentation/mainboard/index.md
+++ b/Documentation/mainboard/index.md
@@ -74,7 +74,7 @@ The boards in this section are not real mainboards, but emulators.
- [R60](lenovo/r60.md)
- [T4xx common](lenovo/t4xx_series.md)
- [X2xx common](lenovo/x2xx_series.md)
-- [VBOOT](lenovo/vboot.md)
+- [vboot](lenovo/vboot.md)
### Arrandale series
diff --git a/Documentation/mainboard/lenovo/vboot.md b/Documentation/mainboard/lenovo/vboot.md
index 3e4d43bd14..4e1b946d08 100644
--- a/Documentation/mainboard/lenovo/vboot.md
+++ b/Documentation/mainboard/lenovo/vboot.md
@@ -3,18 +3,18 @@
By default a single instance of coreboot is present in the firmware flash,
no verification is done and the flash is not write-protected, so as to allow
firmware updates from the OS.
-The verified boot mechanism also called [VBOOT] allows secure firmware
+The verified boot mechanism also called [vboot] allows secure firmware
updates using an A/B partitioning scheme once enabled.
-## Enabling VBOOT
-You can enable [VBOOT] in Kconfig's *Security* section. Besides a verified
+## Enabling vboot
+You can enable [vboot] in Kconfig's *Security* section. Besides a verified
boot you can also enable a measured boot by setting
`CONFIG_VBOOT_MEASURED_BOOT`. Both options need a working TPM, which is
present on all recent Lenovo devices.
## Updating and recovery
As the A/B partition is writeable you can still update them from the OS.
-By using the [VBOOT] mechanism you store a copy of coreboot in the `RO`
+By using the [vboot] mechanism you store a copy of coreboot in the `RO`
partition that acts as failsafe in case the regular firmware update, that
goes to the `A` or `B` partition fails.
@@ -32,8 +32,8 @@ default FMAP. They are missing the `B` partition, due to size constaints.
You can still provide your own FMAP if you need `RO`+`A`+`B` partitions.
## CMOS
-[VBOOT] on *Lenovo* devices uses the CMOS to store configuration data, like
+[vboot] on *Lenovo* devices uses the CMOS to store configuration data, like
boot failures and the last successfully booted partition.
-[VBOOT]: ../../security/vboot/index.md
[CB:32705]: https://review.coreboot.org/32705
+[vboot]: ../../security/vboot/index.md