linux-imx
Public
Source
committed 9331e5e7b8476
76
77
77
Notice how bzImage.efi can be specified with a relative path. That's78
78
because the image we're executing is interpreted by the EFI shell,79
79
which understands relative paths, whereas the rest of the command line80
80
is passed to bzImage.efi.81
81
82
82
83
83
The "dtb=" option84
84
-----------------85
85
86
-
For the ARM and arm64 architectures, we also need to be able to provide a87
-
device tree to the kernel. This is done with the "dtb=" command line option,88
-
and is processed in the same manner as the "initrd=" option that is86
+
For the ARM and arm64 architectures, a device tree must be provided to87
+
the kernel. Normally firmware shall supply the device tree via the88
+
EFI CONFIGURATION TABLE. However, the "dtb=" command line option can89
+
be used to override the firmware supplied device tree, or to supply90
+
one when firmware is unable to.91
+
92
+
Please note: Firmware adds runtime configuration information to the93
+
device tree before booting the kernel. If dtb= is used to override94
+
the device tree, then any runtime data provided by firmware will be95
+
lost. The dtb= option should only be used either as a debug tool, or96
+
as a last resort when a device tree is not provided in the EFI97
+
CONFIGURATION TABLE.98
+
99
+
"dtb=" is processed in the same manner as the "initrd=" option that is89
100
described above.