diff options
| author | Gerd Hoffmann <kraxel@redhat.com> | 2021-12-13 09:16:56 +0100 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2021-12-13 12:16:32 +0000 |
| commit | c802f8935ca34f06f22292c92ed152db89c66f00 (patch) | |
| tree | a3e7a5ee9fbecad23d809f11bb015694d8e9e319 /IntelFsp2Pkg/FspSecCore | |
| parent | 79dcaf7054dbe90a30c7ce288b7f2ed882d96cf2 (diff) | |
| download | edk2-c802f8935ca34f06f22292c92ed152db89c66f00.tar.gz edk2-c802f8935ca34f06f22292c92ed152db89c66f00.tar.bz2 edk2-c802f8935ca34f06f22292c92ed152db89c66f00.zip | |
OvmfPkg/Microvm/fdt: add empty fdt
FdtClient is unhappy without a device tree, so add an empty fdt
which we can use in case etc/fdt is not present in fw_cfg.
On ARM machines a device tree is mandatory for hardware detection,
that's why FdtClient fails hard.
On microvm the device tree is only used to detect virtio-mmio devices
(this patch series) and the pcie host (future series). So edk2 can
continue with limited functionality in case no device tree is present:
no storage, no network, but serial console and direct kernel boot
works.
qemu release 6.2 & newer will provide a device tree for microvm.
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3689
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Diffstat (limited to 'IntelFsp2Pkg/FspSecCore')
0 files changed, 0 insertions, 0 deletions