From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: John Baboval <john.baboval@citrix.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] input, virtio-vga & multihead -- current state
Date: Tue, 28 Jan 2014 11:25:51 +0100 [thread overview]
Message-ID: <1390904751.30708.20.camel@nilsson.home.kraxel.org> (raw)
Hi,
Input layer + sdl2 pull request just sent. So the first bits will
hopefully be merged soon.
On top of that I've been working on some multihead and virtio gpu/vga
bits. Current state is here:
http://www.kraxel.org/cgit/qemu/log/?h=rebase/input-wip
Commits are baby steps, build fixes not squashed in yet, commit log
needs more info, ...
On multihead:
* QemuConsole got a new 'head' field for devices with multiple heads,
with some infrastructure (func to query head etc.).
* Created QemuUIInfo struct. Each QemuConsole gets one of these
assigned. It is supposed to carry hints from the UI code for the
graphics emulation. For now it carries the window geometry.
I think edid information should live there too. Maybe even
replace width+height.
* gfx hardware -> ui notification on head geometry is still to be
done.
* Dave used dpy_gfx_replace_surface(con, NULL) to disable heads.
Nice idea. /me fixed spice to handle that correctly.
On virtio-vga:
* Both virtio-gpu-pci and virtio-vga are children of virtio-pci-proxy
now.
* Didn't came very far in testing. Guest kernel just says:
[ 50.712897] [drm] got -2147483647 outputs
I've used
http://cgit.freedesktop.org/~airlied/linux/log/?h=virtio-vga
Ideas?
cheers,
Gerd
next reply other threads:[~2014-01-28 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 10:25 Gerd Hoffmann [this message]
2014-01-29 16:28 ` [Qemu-devel] input, virtio-vga & multihead -- current state Gerd Hoffmann
2014-01-30 1:05 ` Dave Airlie
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=1390904751.30708.20.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@gmail.com \
--cc=john.baboval@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).