diff options
author | Patrick Rudolph <patrick.rudolph@9elements.com> | 2020-03-24 08:40:45 +0100 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2020-04-28 06:14:25 +0000 |
commit | 8c82010c9769ea101e78aac38e17fb09bbf11405 (patch) | |
tree | c52a0a22fde85745176ee0c64e6e7c217a81632a /Documentation/mainboard/lenovo | |
parent | 6093c5099f673a2f274acfbd9e6b17a9bf76843d (diff) | |
download | coreboot-8c82010c9769ea101e78aac38e17fb09bbf11405.tar.xz |
Documentation: Spell vboot all lowercase
Update all occurrences of vboot and spell it lowercase.
Change-Id: I432b0db8a3dda43b71844e557a3d89180f25f1c3
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/39799
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'Documentation/mainboard/lenovo')
-rw-r--r-- | Documentation/mainboard/lenovo/vboot.md | 12 |
1 files changed, 6 insertions, 6 deletions
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 |