From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-ppc@nongnu.org, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc/spapr: Allow VIRTIO_VGA
Date: Wed, 16 Sep 2015 07:08:10 +1000 [thread overview]
Message-ID: <1442351290.3146.17.camel@kernel.crashing.org> (raw)
In-Reply-To: <1442308746.2895.19.camel@redhat.com>
On Tue, 2015-09-15 at 11:19 +0200, Gerd Hoffmann wrote:
> On Di, 2015-09-15 at 15:51 +1000, Benjamin Herrenschmidt wrote:
> > It works fine with the Linux driver out of the box
>
> Do you actually want the vga compatibility bits on pseries?
Yes, our firmware SLOF uses them (via MMIO BARs) for the early boot
stuff (well, it will use them when the patches I sent are merged).
> There also is virtio-gpu-pci (same thing as virtio-vga but without
> vga compatibility), which should already be enabled on ppc64.
>
> Thel inux kvm driver certainly doesn't need vga compatibility.
>
> For slof support it might be useful though, the vga compatibility
> bits
> in virtio-vga are fully compatible to stdvga, so slof support should
> be
> as simple as adding a PCI ID ...
Right. Well, I first had to update SLOF to use the MMIO BARs rather
than the legacy IO crap, but yes, that's pretty much what I did.
> cheers,
> Gerd
>
next prev parent reply other threads:[~2015-09-15 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 5:51 [Qemu-devel] [PATCH] ppc/spapr: Allow VIRTIO_VGA Benjamin Herrenschmidt
2015-09-15 9:19 ` Gerd Hoffmann
2015-09-15 21:08 ` Benjamin Herrenschmidt [this message]
2015-09-16 6:52 ` Gerd Hoffmann
2015-09-30 5:42 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2015-09-30 6:29 ` Gerd Hoffmann
2015-10-01 6:31 ` David Gibson
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=1442351290.3146.17.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).