From: yuchenlin <yuchenlin@synology.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: edk2-devel@lists.01.org, phil@philjordan.eu,
jordan.l.justen@intel.com, anthony.perard@citrix.com,
lersek@redhat.com
Subject: Re: [PATCH 0/4] OvmfPkg: simply use the Bochs interface for vmsvga
Date: Fri, 02 Nov 2018 10:12:57 +0800 [thread overview]
Message-ID: <4442dbe4144402f98e619c2f9931987e@synology.com> (raw)
In-Reply-To: <e4e04289-01d1-17bc-702b-1fc265a1a3cf@redhat.com>
On 2018-11-02 03:02, Philippe Mathieu-Daudé wrote:
> Hi Yu-chen Lin,
>
> On 24/10/18 8:40, yuchenlin@synology.com wrote:
>> From: yuchenlin <yuchenlin@synology.com>
>>
>> In this series, replace the original vmsvga driver to Bochs
>> interface.
>
> This is the 'v2' of your previous patch 'OvmfPkg: initialize bochs
> when initializing vmsvga':
> https://lists.01.org/pipermail/edk2-devel/2018-October/031235.html
>
> Keeping different versions and referencing previous series helps when
> reviewing.
>
Sorry for that.
I will add v2 (or v3?) next time.
Thanks,
yuchenlin
>>
>> Simply revert vmsvga driver implementation. After it, use Bochs
>> interface for initializing vmsvga.
>>
>> Because of the PCI BARs difference between std vga and vmsvga.
>> We can not simply recognize the "QEMU VMWare SVGA" as the
>> QEMU_VIDEO_BOCHS_MMIO variant.
>>
>> BAR | std vga | vmsvga
>> ---------------------------------
>> 0 | Framebuffer | I/O space
>> 1 | Reserved | Framebuffer
>> 2 | MMIO | FIFO
>>
>> To overcome this problem, we remain variant QEMU_VIDEO_VMWARE_SVGA,
>> and use it for:
>>
>> (1) Get framebuffer from correct PCI BAR
>> (2) Prevent using BAR2 for MMIO
>>
>> We have tested on qemu before and after commit 104bd1dc70 and all
>> worked.
>
> Did you also test against QEMU v2.9.1?
>
No, but I tested it in QEMU v2.9.0.
Thanks,
yuchenlin
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: yuchenlin <yuchenlin@synology.com>
>>
>> yuchenlin (4):
>> Revert "OvmfPkg/QemuVideoDxe: VMWare SVGA device support"
>> Revert "OvmfPkg/QemuVideoDxe: Helper functions for unaligned port
>> I/O."
>> Revert "OvmfPkg/QemuVideoDxe: list "UnalignedIoInternal.h" in the
>> INF
>> file"
>> OvmfPkg: simply use the Bochs interface for vmsvga
>>
>> OvmfPkg/QemuVideoDxe/Driver.c | 137 ++-------------
>> OvmfPkg/QemuVideoDxe/Gop.c | 68 +-------
>> OvmfPkg/QemuVideoDxe/Initialize.c | 157
>> ------------------
>> OvmfPkg/QemuVideoDxe/Qemu.h | 27 ---
>> OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf | 7 -
>> OvmfPkg/QemuVideoDxe/UnalignedIoGcc.c | 70 --------
>> OvmfPkg/QemuVideoDxe/UnalignedIoIcc.c | 80 ---------
>> OvmfPkg/QemuVideoDxe/UnalignedIoInternal.h | 59 -------
>> OvmfPkg/QemuVideoDxe/UnalignedIoMsc.c | 78 ---------
>> OvmfPkg/QemuVideoDxe/UnalignedIoUnsupported.c | 66 --------
>> 10 files changed, 17 insertions(+), 732 deletions(-)
>> delete mode 100644 OvmfPkg/QemuVideoDxe/UnalignedIoGcc.c
>> delete mode 100644 OvmfPkg/QemuVideoDxe/UnalignedIoIcc.c
>> delete mode 100644 OvmfPkg/QemuVideoDxe/UnalignedIoInternal.h
>> delete mode 100644 OvmfPkg/QemuVideoDxe/UnalignedIoMsc.c
>> delete mode 100644 OvmfPkg/QemuVideoDxe/UnalignedIoUnsupported.c
>>
prev parent reply other threads:[~2018-11-02 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 6:40 [PATCH 0/4] OvmfPkg: simply use the Bochs interface for vmsvga yuchenlin
2018-10-24 6:40 ` [PATCH 1/4] Revert "OvmfPkg/QemuVideoDxe: VMWare SVGA device support" yuchenlin
2018-11-01 18:58 ` Philippe Mathieu-Daudé
2018-11-02 2:09 ` yuchenlin
2018-10-24 6:40 ` [PATCH 2/4] Revert "OvmfPkg/QemuVideoDxe: Helper functions for unaligned port I/O." yuchenlin
2018-10-24 6:40 ` [PATCH 3/4] Revert "OvmfPkg/QemuVideoDxe: list "UnalignedIoInternal.h" in the INF file" yuchenlin
2018-10-24 6:40 ` [PATCH 4/4] OvmfPkg: simply use the Bochs interface for vmsvga yuchenlin
2018-10-24 9:16 ` Gerd Hoffmann
2018-11-01 18:54 ` Philippe Mathieu-Daudé
2018-11-02 2:05 ` yuchenlin
2018-11-01 19:02 ` [PATCH 0/4] " Philippe Mathieu-Daudé
2018-11-02 2:12 ` yuchenlin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4442dbe4144402f98e619c2f9931987e@synology.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox