summaryrefslogtreecommitdiffstats
path: root/OvmfPkg/QemuVideoDxe/Gop.c
diff options
context:
space:
mode:
authoryuchenlin <yuchenlin@synology.com>2018-11-07 11:47:13 +0800
committerLaszlo Ersek <lersek@redhat.com>2018-11-20 20:49:15 +0100
commitd021868ccf49e2a39664021909354ef1150b0a6d (patch)
tree6fb4594a821f377d7aa80567fc93d78ccdb177d0 /OvmfPkg/QemuVideoDxe/Gop.c
parent330e18555cd246465e0229e1daa1a72287d3274d (diff)
downloadedk2-d021868ccf49e2a39664021909354ef1150b0a6d.tar.gz
edk2-d021868ccf49e2a39664021909354ef1150b0a6d.tar.bz2
edk2-d021868ccf49e2a39664021909354ef1150b0a6d.zip
OvmfPkg: simply use the Bochs interface for vmsvga
BAR | std vga | vmsvga --------------------------------- 0 | Framebuffer | I/O space 1 | Reserved | Framebuffer 2 | MMIO | FIFO - We cannot recognize VMW SVGA as BOCHS because that would confuse the IsQxl setting in QemuVideoControllerDriverStart(), - We cannot recognize VMW SVGA as BOCHS_MMIO because BAR2 on VMW SVGA is not the BOCHS MMIO BAR (we can only use port IO). Therefore the list of reasons for which we should introduce QEMU_VIDEO_VMWARE_SVGA should name three reasons: (1) Get framebuffer from correct PCI BAR (2) Prevent using BAR2 for MMIO (3) Prevent mis-recognizing VMW SVGA as QXL Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: yuchenlin <yuchenlin@synology.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com> Regression-tested-by: Laszlo Ersek <lersek@redhat.com> Tested-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'OvmfPkg/QemuVideoDxe/Gop.c')
-rw-r--r--OvmfPkg/QemuVideoDxe/Gop.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/OvmfPkg/QemuVideoDxe/Gop.c b/OvmfPkg/QemuVideoDxe/Gop.c
index d490fa7a2e..6f542d9eac 100644
--- a/OvmfPkg/QemuVideoDxe/Gop.c
+++ b/OvmfPkg/QemuVideoDxe/Gop.c
@@ -60,7 +60,7 @@ QemuVideoCompleteModeData (
Private->PciIo->GetBarAttributes (
Private->PciIo,
- 0,
+ Private->FrameBufferVramBarIndex,
NULL,
(VOID**) &FrameBufDesc
);