summaryrefslogtreecommitdiffstats
path: root/SignedCapsulePkg
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2024-06-17 17:07:41 +0200
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2024-06-18 20:52:56 +0000
commitc1d1910be6e04a8b1a73090cf2881fb698947a6e (patch)
treea04a6bf14e83387e36341ff38a975debf57852b7 /SignedCapsulePkg
parentffce430d2b65d508a1604dc986ba16db3583943d (diff)
downloadedk2-c1d1910be6e04a8b1a73090cf2881fb698947a6e.tar.gz
edk2-c1d1910be6e04a8b1a73090cf2881fb698947a6e.tar.bz2
edk2-c1d1910be6e04a8b1a73090cf2881fb698947a6e.zip
OvmfPkg/QemuVideoDxe: add feature PCD to remap framebuffer W/C
Some platforms (such as SBSA-QEMU on recent builds of the emulator) only tolerate misaligned accesses to normal memory, and raise alignment faults on such accesses to device memory, which is the default for PCIe MMIO BARs. When emulating a PCIe graphics controller, the framebuffer is typically exposed via a MMIO BAR, while the disposition of the region is closer to memory (no side effects on reads or writes, except for the changing picture on the screen; direct random access to any pixel in the image). In order to permit the use of such controllers on platforms that only tolerate these types of accesses for normal memory, it is necessary to remap the memory. Use the DXE services to set the desired capabilities and attributes. Hide this behavior under a feature PCD so only platforms that really need it can enable it. (OVMF on x86 has no need for this) Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'SignedCapsulePkg')
0 files changed, 0 insertions, 0 deletions