Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
42d12fa98b |
@@ -1055,7 +1055,7 @@ config ARCH_QEMU
|
||||
imply DM_RNG
|
||||
imply DM_RTC
|
||||
imply RTC_PL031
|
||||
imply OF_HAS_PRIOR_STAGE if !TARGET_QEMU_ARM_SBSA
|
||||
imply OF_HAS_PRIOR_STAGE if !TARGET_QEMU_ARM_SBSA && !QEMU_MANUAL_DTB
|
||||
imply VIDEO
|
||||
imply VIDEO_BOCHS
|
||||
imply SYS_WHITE_ON_BLACK
|
||||
|
||||
@@ -13,3 +13,15 @@ config MTDPARTS_NOR1
|
||||
help
|
||||
This define the partition of nor1 used to build mtparts dynamically
|
||||
for the u-boot env stored on nor1.
|
||||
|
||||
config QEMU_MANUAL_DTB
|
||||
bool "Manually provide a device tree to QEMU"
|
||||
help
|
||||
For some use cases, such as FIT validation where a public key must be
|
||||
placed in U-Boot's device tree, we need to override the device tree
|
||||
that QEMU would normally provide to us.
|
||||
|
||||
Note: this work-around is necessary since Linaro has blocked
|
||||
addition of a feature to support additions to the QEMU devicetree:
|
||||
|
||||
Link: https://patchwork.kernel.org/project/qemu-devel/patch/20210926183410.256484-1-sjg@chromium.org/#24481799
|
||||
|
||||
@@ -46,3 +46,8 @@ You can then run qemu with the merged devicetree, e.g.::
|
||||
|
||||
Note that there seems to be a bug in some versions of qemu where the output of
|
||||
dumpdtb does not quite match what is provided to U-Boot.
|
||||
|
||||
See also the
|
||||
`rejected QEMU patch <https://patchwork.kernel.org/project/qemu-devel/patch/20231117021840.117874-1-sjg@chromium.org>`_
|
||||
and
|
||||
`discussion <https://patchwork.kernel.org/project/qemu-devel/patch/20210926183410.256484-1-sjg@chromium.org>`_.
|
||||
|
||||
@@ -190,7 +190,7 @@ config OF_BOARD
|
||||
earlier stage should enable OF_HAS_PRIOR_STAGE.
|
||||
|
||||
config OF_HAS_PRIOR_STAGE
|
||||
bool "Device tree comes from prior-stage firmware"
|
||||
bool
|
||||
help
|
||||
Indicates that a prior stage of the firmware (before U-Boot proper)
|
||||
makes use of device tree and this board normally boots with that prior
|
||||
@@ -205,8 +205,8 @@ config OF_HAS_PRIOR_STAGE
|
||||
development purposes, but it is not recommended, and likely will not
|
||||
even work, for production systems.
|
||||
|
||||
Note: This option can be updated in the board's defconfig file if
|
||||
needed. E.g. for QEMU to support FIT validation the devicetree must
|
||||
Note: This option can be disabled for QEMU usiing QEMU_MANUAL_DTB thus
|
||||
allowing QEMU to support FIT validation, where the devicetree must
|
||||
include a public key.
|
||||
|
||||
See also this for context:
|
||||
|
||||
Reference in New Issue
Block a user