From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Julian Pidancet <julian.pidancet@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] Add QEMU DirectFB display driver
Date: Tue, 18 May 2010 11:23:04 +0200 [thread overview]
Message-ID: <4BF25C78.5070404@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005181005160.11380@kaball-desktop>
On 05/18/10 11:12, Stefano Stabellini wrote:
> I think it would be better to implement an accelerated frontend for
> rendering the framebuffer, like opengl or xv.
Well. xv is pretty pointless IMHO. gl makes sense. But to have some
effect this needs some major restructions in qemu, the current
DisplayState infrastructure can't handle anything but a simple, stupid
framebuffer. There isn't much to accelerate, except maybe scaling the
guest display to fullscreen on the host.
qxl + spice will change that though. qxl is a paravirtualized gfx
adapter. Guest sends rendering commands. The spice protocol sends the
rendering commands over the wire to the spice client, which in turn will
render them (and can use gl to accelerate that).
cheers,
Gerd
next prev parent reply other threads:[~2010-05-18 9:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 15:53 [Qemu-devel] [PATCH] Add QEMU DirectFB display driver Julian Pidancet
2010-05-16 1:10 ` Paul Brook
2010-05-16 1:14 ` Alexander Graf
2010-05-17 13:30 ` Anthony Liguori
2010-05-17 15:09 ` Julian Pidancet
2010-05-17 16:28 ` Anthony Liguori
2010-05-17 20:20 ` Gerd Hoffmann
2010-05-17 20:32 ` Anthony Liguori
2010-05-17 21:35 ` malc
2010-05-17 21:43 ` Anthony Liguori
2010-05-17 21:45 ` malc
2010-05-17 22:26 ` Alexander Graf
2010-05-17 22:42 ` malc
2010-05-17 22:47 ` Anthony Liguori
2010-05-17 22:55 ` Alexander Graf
2010-05-17 23:17 ` Anthony Liguori
2010-05-17 22:46 ` Anthony Liguori
2010-05-17 22:49 ` Alexander Graf
2010-05-17 22:54 ` Anthony Liguori
2010-05-17 22:59 ` Alexander Graf
2010-05-18 0:26 ` [Qemu-devel] qemu usage K D
2010-05-18 8:09 ` [Qemu-devel] [PATCH] Add QEMU DirectFB display driver Kevin Wolf
2010-05-18 9:12 ` Stefano Stabellini
2010-05-18 9:23 ` Gerd Hoffmann [this message]
2010-05-18 9:29 ` Stefano Stabellini
2010-05-18 9:39 ` Gerd Hoffmann
2010-05-18 10:34 ` Stefano Stabellini
2010-05-18 11:20 ` Gerd Hoffmann
2010-05-18 13:02 ` Anthony Liguori
2010-05-18 22:00 ` Gerd Hoffmann
2010-05-19 12:06 ` Stefano Stabellini
2010-05-19 13:38 ` Gerd Hoffmann
2010-05-19 13:52 ` Stefano Stabellini
2010-05-19 15:22 ` Gerd Hoffmann
2010-05-19 15:30 ` Stefano Stabellini
2010-05-19 16:06 ` Julian Pidancet
2010-05-19 16:30 ` Jamie Lokier
2010-05-20 7:32 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2010-05-14 16:20 Julian Pidancet
2010-05-14 16:58 Julian Pidancet
2010-05-14 17:07 ` Anthony Liguori
2010-05-17 10:58 ` Gerd Hoffmann
2010-05-17 10:53 ` Gerd Hoffmann
2010-05-17 12:04 ` Julian Pidancet
2010-05-17 19:25 ` Gerd Hoffmann
2010-05-17 11:44 ` Christoph Hellwig
2010-05-17 12:14 ` Julian Pidancet
2010-05-17 12:35 ` Christoph Hellwig
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=4BF25C78.5070404@redhat.com \
--to=kraxel@redhat.com \
--cc=julian.pidancet@citrix.com \
--cc=kwolf@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).