doc: Add a link to VBE from the bootstd docs

Link to this page to make it easier to find the VBE docs.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

diff --git a/doc/develop/bootstd/overview.rst b/doc/develop/bootstd/overview.rst
index bc7e4b39704a08a28612269205345afd7e82bac5..afc5e0e3710a28f7793699af1d21bc249f6ce3d6 100644 (file)
--- a/doc/develop/bootstd/overview.rst
+++ b/doc/develop/bootstd/overview.rst
@@ -416,16 +416,16 @@ Available bootmeth drivers
 
 Bootmeth drivers are provided for booting from various media:
 
+   - Android bootflow (boot image v4)
+   - :doc:`ChromiumOS <cros>` ChromiumOS boot from a disk
+   - EFI boot using bootefi from disk
+   - EFI boot using boot manager
    - :doc:`extlinux / syslinux <extlinux>` boot from a storage device
    - :doc:`extlinux / syslinux <extlinux>` boot from a network (PXE)
+   - :doc:`sandbox <sandbox>` used only for testing
    - :doc:`U-Boot scripts <script>` from disk, network or SPI flash
-   - EFI boot using bootefi from disk
-   - VBE
-   - :doc:`ChromiumOS <cros>` ChromiumOS boot from a disk
-   - EFI boot using boot manager
-   - Android bootflow (boot image v4)
    - :doc:`QFW <qfw>`: QEMU firmware interface
-   - :doc:`sandbox <sandbox>` used only for testing
+   - :doc:`VBE </develop/vbe>`: Verified Boot for Embedded
 
 Each driver is controlled by a Kconfig option. If no bootmeth driver is
 selected by a compatible string in the devicetree, all available bootmeth