From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@kernel.org>,
KVM list <kvm@vger.kernel.org>,
Cyrill Gorcunov <gorcunov@gmail.com>,
John Floren <john@jfloren.net>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH] kvm tools, ui: Optimize SDL updates
Date: Mon, 06 Jun 2011 09:02:47 +0200 [thread overview]
Message-ID: <4DEC7B97.8090607@redhat.com> (raw)
In-Reply-To: <EF895B2F-0138-4386-AF44-AA5531D8EB1D@suse.de>
Hi,
> Also, I'm fairly sure vesafb implements scrolling almost
> unconditionally. Check for "ypan" in drivers/video/vesafb.c.
ypan uses the protected mode interface provided by the vesa bios.
It is not used by default works on 32bit only.
>> If you think qxl-fb can be done gradually in that context then
>> that's probably the right solution. Is there *any* QXL code in the
>> kernel that would allow us to get started? I really know nothing
>> about QXL.
>
> I don't think there is. CC'ing Gerd for that discussion. He's taking
> care of all the upstreaming work and community efforts around QXL.
No kernel code right now.
cheers,
Gerd
prev parent reply other threads:[~2011-06-06 7:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 21:20 [PATCH] kvm tools, ui: Optimize SDL updates Pekka Enberg
2011-06-04 9:54 ` Ingo Molnar
2011-06-04 10:27 ` Alexander Graf
2011-06-04 10:42 ` Ingo Molnar
2011-06-04 10:46 ` Alexander Graf
2011-06-04 10:54 ` Ingo Molnar
2011-06-04 11:07 ` Alexander Graf
2011-06-04 11:53 ` Ingo Molnar
2011-06-04 11:59 ` Alexander Graf
2011-06-04 12:04 ` Sasha Levin
2011-06-04 13:48 ` Alexander Graf
2011-06-04 14:19 ` Sasha Levin
2011-06-04 15:21 ` Alexander Graf
2011-06-04 15:34 ` Sasha Levin
2011-06-04 15:40 ` Alexander Graf
2011-06-04 16:49 ` Sasha Levin
2011-06-05 8:41 ` Alexander Graf
2011-06-05 9:32 ` Alon Levy
2011-06-06 7:02 ` Gerd Hoffmann [this message]
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=4DEC7B97.8090607@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=gorcunov@gmail.com \
--cc=john@jfloren.net \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.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