From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver.
Date: Tue, 11 Jun 2013 08:12:37 +0200 [thread overview]
Message-ID: <51B6BFD5.10005@redhat.com> (raw)
In-Reply-To: <87mwr3ghk0.fsf@codemonkey.ws>
Hi,
>> +static QEMUCursor *ptr_cursor;
>> +static pixman_image_t *ptr_image;
>> +static int ptr_refresh;
>> +static int px, py, pw, ph;
>> +static int mx, my, mon;
>> +
>> +/* options */
>> +static int use_scale;
>> +static pixman_filter_t pfilter = PIXMAN_FILTER_GOOD;
>
> Should stick all of this within a structure and pass it around where
> possible.
Don't see what this buys us as there can be only a single framebuffer
display anyway. Can do that though.
>> + if (qemu_console_is_graphic(NULL)) {
>> + send_scancode(keycode, up);
>> + } else if (!up) {
>> + send_keysym(keycode, shift);
>
> I'm confused here... Why can't use use the normal keymap code with the
> keycode value?
keycode != keycode. qemu uses ps/2 keycodes. fbdev gets linux input
layer keycodes as input.
cheers,
Gerd
next prev parent reply other threads:[~2013-06-11 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 15:37 [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver Gerd Hoffmann
2013-06-06 15:37 ` [Qemu-devel] [PATCH 2/2] fbdev: add monitor command to enable/disable Gerd Hoffmann
2013-06-15 15:19 ` Eric Blake
2013-06-06 19:33 ` [Qemu-devel] [PATCH 1/2] fbdev: add linux framebuffer display driver Anthony Liguori
2013-06-11 6:12 ` Gerd Hoffmann [this message]
2013-06-12 8:34 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2013-06-26 11:38 Gerd Hoffmann
2013-06-26 15:48 ` Luiz Capitulino
2013-06-27 9:58 ` Gerd Hoffmann
2013-06-27 13:23 ` Luiz Capitulino
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=51B6BFD5.10005@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.