summaryrefslogtreecommitdiff
path: root/BaseTools/Source/Python/Workspace/MetaDataTable.py
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2017-03-17 15:37:47 +0300
committerLaszlo Ersek <lersek@redhat.com>2017-03-28 14:48:39 +0300
commit30cb1485b1df44cf4fbec3b80051ef326da12eb6 (patch)
tree1d4b786e6473549bb040f29e334e9d0e14520834 /BaseTools/Source/Python/Workspace/MetaDataTable.py
parent3efa3f3d05ea3fef964e59aea9b5792cfec348ed (diff)
downloadedk2-30cb1485b1df44cf4fbec3b80051ef326da12eb6.tar.xz
Revert "ArmVirtPkg/FdtClientDxe: make DT table installation !ACPI dependent"
This reverts commit 78c41ff519b187d8979cda7074f007a6323f9acd. We realized that DXE drivers that are independent of AcpiPlatformDxe (that is, independent of QEMU's ACPI generation), such as RamDiskDxe and BootGraphicsResourceTableDxe, may produce and/or manipulate ACPI tables, at driver dispatch or even at Ready To Boot. This makes it unsafe for us to check for ACPI presence in the UEFI system config table in a Ready To Boot callback, in order to decide about exposing the DT. Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Leif Lindholm <leif.lindholm@linaro.org> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/MetaDataTable.py')
0 files changed, 0 insertions, 0 deletions