Commit 9331e5e7 authored by Grant Likely's avatar Grant Likely Committed by Jonathan Corbet

efi_stub: update documentation on dtb= parameter

The dtb= parameter is no longer the primary mechanism for providing a
devicetree to the kernel. Now either firmware or the boot selector (ex.
Grub) should provide the devicetree and dtb= should only be used for
debug or when using firmware that doesn't understand DT.
Update the EFI stub documentation to reflect the current usage.
Signed-off-by: default avatarGrant Likely <grant.likely@arm.com>
Reviewed-by: default avatarAlexander Graf <agraf@suse.de>
Acked-by: default avatarLeif Lindholm <leif.lindholm@linaro.org>
Acked-by: default avatarOlof Johansson <olof@lixom.net>
Acked-by: default avatarArd Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 2f4830ef
...@@ -83,7 +83,18 @@ is passed to bzImage.efi. ...@@ -83,7 +83,18 @@ is passed to bzImage.efi.
The "dtb=" option The "dtb=" option
----------------- -----------------
For the ARM and arm64 architectures, we also need to be able to provide a For the ARM and arm64 architectures, a device tree must be provided to
device tree to the kernel. This is done with the "dtb=" command line option, the kernel. Normally firmware shall supply the device tree via the
and is processed in the same manner as the "initrd=" option that is EFI CONFIGURATION TABLE. However, the "dtb=" command line option can
be used to override the firmware supplied device tree, or to supply
one when firmware is unable to.
Please note: Firmware adds runtime configuration information to the
device tree before booting the kernel. If dtb= is used to override
the device tree, then any runtime data provided by firmware will be
lost. The dtb= option should only be used either as a debug tool, or
as a last resort when a device tree is not provided in the EFI
CONFIGURATION TABLE.
"dtb=" is processed in the same manner as the "initrd=" option that is
described above. described above.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment