qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] linux framebuffer display driver
Date: Tue, 11 Sep 2012 04:09:25 -0400 (EDT)	[thread overview]
Message-ID: <303604638.32854461.1347350965011.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1347286860-22918-1-git-send-email-kraxel@redhat.com>

> 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. 

Tested with Seabios. Works as advertised, tested console switching, quit, serial console. 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.

Verified systemtap points using the following script:

$ cat scripts/simple-qemu-trace.py 
#!/usr/bin/env python

import sys

start = sys.argv[1]

for line in sys.stdin:
    if not line.startswith(start):
        continue
    probe = line.split('(')[0]
    print """probe qemu.system.x86_64.%s {
    printf("%s\\n");
}
""" % (probe, probe)

./scripts/simple-qemu-trace.py fbdev < trace-events | sudo stap -v -s1 -I x86_64-softmmu -

> 
> enjoy,
>   Gerd
> 
> Gerd Hoffmann (4):
>   QLIST-ify display change listeners.
>   add unregister_displaychangelistener
>   fbdev: add linux framebuffer display driver.
>   fbdev: add monitor command to enable/disable
> 
>  console.h           |   86 +++--
>  hmp-commands.hx     |   15 +
>  hmp.c               |    9 +
>  hmp.h               |    1 +
>  hw/xenfb.c          |    2 +-
>  qapi-schema.json    |   15 +
>  qemu-options.hx     |    8 +
>  qmp-commands.hx     |    6 +
>  qmp.c               |   17 +
>  sysemu.h            |    1 +
>  trace-events        |   14 +
>  ui/Makefile.objs    |    1 +
>  ui/fbdev.c          |  953
>  +++++++++++++++++++++++++++++++++++++++++++++++++++
>  ui/linux-keynames.h |  388 +++++++++++++++++++++
>  vl.c                |   50 ++-
>  15 files changed, 1518 insertions(+), 48 deletions(-)
>  create mode 100644 ui/fbdev.c
>  create mode 100644 ui/linux-keynames.h
> 
> 
> 

  parent reply	other threads:[~2012-09-11  8:09 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 ` Alon Levy [this message]
2012-09-11  8:54   ` [Qemu-devel] [PATCH 0/4] linux framebuffer display driver Gerd Hoffmann

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=303604638.32854461.1347350965011.JavaMail.root@redhat.com \
    --to=alevy@redhat.com \
    --cc=kraxel@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).