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: Re: [Qemu-devel] input, virtio-vga & multihead -- current state
Date: Wed, 29 Jan 2014 17:28:49 +0100 [thread overview]
Message-ID: <1391012929.31899.9.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1390904751.30708.20.camel@nilsson.home.kraxel.org>
> * 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
Switched to virtio-vga-3d branch -- that is working better. Handover
from vesafb to virtio-vga drm driver doesn't work though ...
cheers,
Gerd
next prev parent reply other threads:[~2014-01-29 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 10:25 [Qemu-devel] input, virtio-vga & multihead -- current state Gerd Hoffmann
2014-01-29 16:28 ` Gerd Hoffmann [this message]
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=1391012929.31899.9.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).