linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>,
	linux-fbdev-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support
Date: Fri, 6 Nov 2009 02:39:15 +0000	[thread overview]
Message-ID: <20091106023915.GO21630@shareable.org> (raw)
In-Reply-To: <4AEFCBED.50804@redhat.com>

Avi Kivity wrote:
> On 11/03/2009 12:09 AM, Alexander Graf wrote:
> >When we want to create a full VirtIO based machine, we're still missing
> >graphics output. Fortunately, Linux provides us with most of the frameworks
> >to render text and everything, we only need to implement a transport.
> >
> >So this is a frame buffer backend written for VirtIO. Using this and my
> >patch to qemu, you can use paravirtualized graphics.
> 
> What does this do that cirrus and/or vmware-vga don't?

*This* virtio-fb doesn't, but one feature I think a lot of users
(including me) would like is:

   Option to resize the guest desktop when the host desktop / host
   window / VNC client resizes.

   Tell the guest to provide multiple desktops when the host has
   multiple desktops, so things like twin monitors work nicely with
   guests.

   Relay EDID/Xrandr information and updates from host to guest, and
   generally handle hotplugging host monitors nicely.

Are there any real hardware standards worth emulating which do that?

-- Jamie

  parent reply	other threads:[~2009-11-06  2:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 22:09 [PATCH] Add VirtIO Frame Buffer Support Alexander Graf
2009-11-02 22:32 ` Ondrej Zajicek
2009-11-02 22:42   ` Alexander Graf
2009-11-02 23:24     ` [Linux-fbdev-devel] " Alexander Graf
2009-11-02 23:57       ` Ondrej Zajicek
2009-11-02 23:59         ` [Linux-fbdev-devel] " Alexander Graf
2009-11-02 23:51     ` Ondrej Zajicek
2009-11-02 23:53       ` Alexander Graf
2009-11-02 23:58         ` Ondrej Zajicek
2009-11-03  6:21 ` Avi Kivity
2009-11-03  6:22   ` Alexander Graf
2009-11-03  6:24     ` Avi Kivity
2009-11-03  6:27       ` Alexander Graf
2009-11-03  6:34         ` Avi Kivity
2009-11-03  6:39           ` Alexander Graf
2009-11-03  7:43             ` Avi Kivity
2009-11-03  7:50               ` Alexander Graf
2009-11-03  8:20                 ` Avi Kivity
2009-11-03  8:26                   ` Alexander Graf
2009-11-03  8:53                     ` Avi Kivity
2009-11-03 15:14                       ` Anthony Liguori
2009-11-03 15:57                         ` Avi Kivity
2009-11-03 11:25             ` [Qemu-devel] " Vincent Hanquez
2009-11-03  9:38               ` Avi Kivity
2009-11-03 15:29                 ` Ondrej Zajicek
2009-11-03 16:05                   ` [Linux-fbdev-devel] " Avi Kivity
2009-11-03 16:53                     ` Ondrej Zajicek
2009-11-03 17:33                     ` [Linux-fbdev-devel] " Paolo Bonzini
2009-11-04 16:09                 ` [Qemu-devel] " Vincent Hanquez
2009-11-04 16:35                   ` Anthony Liguori
2009-11-05  9:04                     ` Avi Kivity
2009-11-06  2:39   ` Jamie Lokier [this message]
2009-11-06  3:05     ` Anthony Liguori
2009-11-05 11:36 ` Michael S. Tsirkin

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=20091106023915.GO21630@shareable.org \
    --to=jamie@shareable.org \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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).