diff options
| author | yuchenlin <yuchenlin@synology.com> | 2018-11-07 11:47:13 +0800 |
|---|---|---|
| committer | Laszlo Ersek <lersek@redhat.com> | 2018-11-20 20:49:15 +0100 |
| commit | d021868ccf49e2a39664021909354ef1150b0a6d (patch) | |
| tree | 6fb4594a821f377d7aa80567fc93d78ccdb177d0 /SecurityPkg/Tcg | |
| parent | 330e18555cd246465e0229e1daa1a72287d3274d (diff) | |
| download | edk2-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 'SecurityPkg/Tcg')
0 files changed, 0 insertions, 0 deletions