From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] linux framebuffer display driver
Date: Tue, 11 Sep 2012 10:54:24 +0200 [thread overview]
Message-ID: <504EFC40.8090501@redhat.com> (raw)
In-Reply-To: <303604638.32854461.1347350965011.JavaMail.root@redhat.com>
On 09/11/12 10:09, Alon Levy wrote:
>> Hi,
>>
>> Undusting an pretty old patch series, rebasing it, testing it,
>> fixing a bug or two, fixing codestyle issues: Qemu can run on the
>> linux framebuffer console as graphical display now.
>
> Patch 4 doesn't apply (hmp.h), missing SoB on a few patches.
Yea, noticed too this morning while rebasing my stuff.
Rebased version is available here:
git://git.kraxel.org/qemu rebase/fbdev
> Some minor point: To switch to serial:
> Ctrl-Alt-1. To switch back to console output you have to release Ctrl
> & release Alt, then repress them, i.e. can't just release 1 and press
> 0.
fbdev resets modifier state on console switches. This causes this
effect, but without it other ugly effects can sneak in (like the guest
seeing a modifier pressed which isn't pressed any more).
cheers,
Gerd
prev parent reply other threads:[~2012-09-11 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 14:20 [Qemu-devel] [PATCH 0/4] linux framebuffer display driver Gerd Hoffmann
2012-09-10 14:20 ` [Qemu-devel] [PATCH 1/4] QLIST-ify display change listeners Gerd Hoffmann
2012-09-10 14:20 ` [Qemu-devel] [PATCH 2/4] add unregister_displaychangelistener Gerd Hoffmann
2012-09-10 14:20 ` [Qemu-devel] [PATCH 3/4] fbdev: add linux framebuffer display driver Gerd Hoffmann
2012-09-11 11:10 ` Markus Armbruster
2012-09-11 20:37 ` Blue Swirl
2012-09-10 14:21 ` [Qemu-devel] [PATCH 4/4] fbdev: add monitor command to enable/disable Gerd Hoffmann
2012-09-11 9:30 ` Markus Armbruster
2012-09-11 8:09 ` [Qemu-devel] [PATCH 0/4] linux framebuffer display driver Alon Levy
2012-09-11 8:54 ` 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=504EFC40.8090501@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.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).