Add a note about how bootmeth drivers are instantiated.
Signed-off-by: Simon Glass <s...@chromium.org>
Reviewed-by: Mattijs Korpershoek <mkorpersh...@baylibre.com>
Suggested-by: Heinrich Schuchardt <xypron.g...@gmx.de>
---
(no changes since v2)
Changes in v2:
- Add new patch to mention automatic binding of bootmeths
doc/develop/bootstd/overview.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/develop/bootstd/overview.rst b/doc/develop/bootstd/overview.rst
index 761f61a573b..d5051e986bb 100644
--- a/doc/develop/bootstd/overview.rst
+++ b/doc/develop/bootstd/overview.rst
@@ -419,6 +419,9 @@ Bootmeth drivers are provided for:
- VBE
- EFI boot using boot manager
+Each driver is controlled by a Kconfig option. If no bootmeth driver is
+selected by a compatible string in the devicetree, all available bootmeth
+drivers are bound automatically.
Command interface
-----------------
--
2.34.1
