From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/7] ramfb: simple boot framebuffer, no legacy vga
Date: Fri, 23 Mar 2018 16:12:21 +0100 [thread overview]
Message-ID: <646a54e2-dc81-978d-de7a-293f2ce1766a@redhat.com> (raw)
In-Reply-To: <20180323145131.whyitmksl2s3d6c6@sirius.home.kraxel.org>
On 03/23/18 15:51, Gerd Hoffmann wrote:
> Hi,
>
>> I believe the only point of this device model (and the associated guest
>> fw driver) is Windows-on-KVM/aarch64.
>
> The other one is vgpu boot display.
Interesting. I know nearly nothing about vgpu, but I hoped it'd come
with its own UEFI GOP driver in the ROM BAR; similarly to assigned
physical GPUs. I thought the oprom would originate from the physical GPU
(with the help of the host kernel), out of which the vgpu was carved out.
Is that far-fetched?
Thanks
Laszlo
next prev parent reply other threads:[~2018-03-23 15:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 12:25 [Qemu-devel] [PATCH v2 0/7] ramfb: simple boot framebuffer, no legacy vga Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 1/7] [testing] update bios, add vgabios-ramfb Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 2/7] [testing] add ovmf build with ramfb support Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 3/7] hw/display: add ramfb, a simple boot framebuffer living in guest ram Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 4/7] hw/display: add ramfb-testdev Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 5/7] hw/display: add virtio-ramfb Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 6/7] hw/vfio/display: add ramfb support Gerd Hoffmann
2018-03-23 12:25 ` [Qemu-devel] [PATCH v2 7/7] [wip] hw/display: add qxl-ramfb Gerd Hoffmann
2018-03-23 13:27 ` [Qemu-devel] [PATCH v2 0/7] ramfb: simple boot framebuffer, no legacy vga Laszlo Ersek
2018-03-23 14:51 ` Gerd Hoffmann
2018-03-23 15:12 ` Laszlo Ersek [this message]
2018-03-23 17:07 ` Gerd Hoffmann
2018-03-23 18:29 ` Laszlo Ersek
2018-03-24 3:51 ` Ard Biesheuvel
2018-04-25 14:07 ` Gerd Hoffmann
2018-04-25 20:43 ` Laszlo Ersek
2018-05-31 8:43 ` Gerd Hoffmann
2018-05-31 9:11 ` Laszlo Ersek
2018-06-05 11:06 ` Gerd Hoffmann
2018-06-05 12:07 ` Laszlo Ersek
2018-06-05 13:16 ` Gerd Hoffmann
2018-06-05 13:23 ` Laszlo Ersek
2018-06-06 8:49 ` Gerd Hoffmann
2018-06-06 12:43 ` Laszlo Ersek
2018-06-06 13:21 ` Gerd Hoffmann
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-all 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=646a54e2-dc81-978d-de7a-293f2ce1766a@redhat.com \
--to=lersek@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=kraxel@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).