From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Why does -device qxl-vga not suppress default vga?
Date: Mon, 16 May 2011 09:28:07 +0200 [thread overview]
Message-ID: <4DD0D207.9040600@redhat.com> (raw)
In-Reply-To: <m3liyahef2.fsf@blackfin.pond.sub.org>
On 05/13/11 16:18, Markus Armbruster wrote:
> VGA, cirrus-vga and vmware-svga do. Gerd, you added it (commit
> a19cbfb3), care to explain?
Just forgot to add it to the list when merging.
I'll go stuff a patch into the spice patch queue.
Does "-device VGA" work these days btw?
Last time I tries it didn't due to some init order issues.
cheers,
Gerd
next prev parent reply other threads:[~2011-05-16 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 14:18 [Qemu-devel] Why does -device qxl-vga not suppress default vga? Markus Armbruster
2011-05-16 7:28 ` Gerd Hoffmann [this message]
2011-05-16 7:43 ` Jan Kiszka
2011-05-17 7:52 ` Markus Armbruster
2011-05-18 7:19 ` Jan Kiszka
2011-05-18 7:47 ` Gleb Natapov
2011-05-18 8:02 ` Jan Kiszka
2011-05-18 8:18 ` Gleb Natapov
2011-05-16 8:05 ` Markus Armbruster
2011-05-18 12:32 ` Markus Armbruster
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=4DD0D207.9040600@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@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).