From: Gerd Hoffmann <kraxel@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
g@shareable.org, Julian Pidancet <julian.pidancet@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] Add QEMU DirectFB display driver
Date: Thu, 20 May 2010 09:32:04 +0200 [thread overview]
Message-ID: <4BF4E574.4010807@redhat.com> (raw)
In-Reply-To: <20100519163039.GD1693@shareable.org>
On 05/19/10 18:30, Jamie Lokier wrote:
> Julian Pidancet wrote:
>> So after all, why not implementing our own VT switching and using
>> directly the fbdev interface.
>
> It's a good idea. VT switching isn't hard to track reliably.
Indeed, only problem is that the fbdev libs usually want to do that too.
> Being able to tell qemu, through the monitor, to attach/detach from a
> particular VT might be a nice easy bonus too.
Yes, should be doable without too much effort.
>> I just checked the linux fbdev code to
>> find out if it provides with a blitting method that could perform
>> the pixel color conversion automatically for Qemu.
>>
>> Unfortunately, from what I have read from the
>> drivers/video/cfbimgblt.c file in the linux tree, there's no such
>> thing, and it also means that we cannot take advantage of any kind
>> of hardware pixel format conversion.
>
> I'm not sure if DirectFB provides that particular operation, but I
> have the impression it's the sort of thing DirectFB is intended for: A
> framebuffer, plus a variety of 2d acceleration methods (and other
> things like multi-buffering, video and alpha channel overlay).
As far I know acceleration depends on the directfb kernel drivers
though, i.e. in 99% of the cases (standard distro installs) those are
not available and software fallbacks are active anyway. So from a
performance point of view directfb doesn't buy us much. And for the
pixel conversion I'd prefer see some reorganization of the existing qemu
code which is spread all over the place now ...
cheers,
Gerd
next prev parent reply other threads:[~2010-05-20 7:32 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
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 [this message]
-- 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=4BF4E574.4010807@redhat.com \
--to=kraxel@redhat.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=g@shareable.org \
--cc=jamie@shareable.org \
--cc=julian.pidancet@citrix.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).