From: "Rafał Cygnarowski" <zswi@pers.pl>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu kbd emulation
Date: Wed, 28 Jun 2006 10:27:31 +0200 [thread overview]
Message-ID: <200606281027.31617.zswi@pers.pl> (raw)
Hi!
I wanted to correct qemu emulation of keyboard under DOS as
guest OS, so I started with simple pascal program to check
what happen on guest DOS (and DOS) when I press up/down/left/right
keys.
The program was:
-- BEGIN test.pas --
program time; {$M 2048,0,0}
uses crt, dos;
var OldKeyInt : procedure;
procedure NewKeyInt; interrupt;
begin
write(Port[$60]); write(' ')
inline($9c); OldKeyInt;
end;
begin
getintvec($9, addr(OldKeyInt));
setintvec($9, @NewKeyInt);
keep(0);
end.
-- END test.pas --
and it look that qemu does not generate some codes before
pressing and after releasing arrow keys. For example pressing
up key on qemu looks like:
224 72 224 200
while without emulation it looks:
224 42 224 72 224 200 224 170.
It's true only for single keystrokes, but good for the
beginning.
So I tried to patch qemu for this and created following patch:
-- BEGIN sdl.patch --
--- sdl.c.old 2006-05-03 20:32:58.000000000 +0000
+++ sdl.c 2006-06-28 07:26:14.000000000 +0000
@@ -254,14 +254,34 @@
kbd_put_keycode(keycode);
kbd_put_keycode(keycode | 0x80);
return;
+ case 0xc8: /* up */
+ case 0xd0: /* down */
+ case 0xcd: /* right */
+ case 0xcb: /* left */
+ if (ev->type != SDL_KEYUP) {
+ kbd_put_keycode(e0);
+ kbd_put_keycode(2a);
+ }
+ break;
}
-
+
/* now send the key code */
if (keycode & 0x80)
kbd_put_keycode(0xe0);
- if (ev->type == SDL_KEYUP)
- kbd_put_keycode(keycode | 0x80);
- else
+
+ if (ev->type == SDL_KEYUP) {
+ kbd_put_keycode(keycode | 0x80);
+
+ switch(keycode) {
+ case 0xc8: /* up */
+ case 0xd0: /* down */
+ case 0xcd: /* right */
+ case 0xcb: /* left */
+ kbd_put_keycode(0xe0);
+ kbd_put_keycode(0xaa);
+ break;
+ }
+ } else
kbd_put_keycode(keycode & 0x7f);
}
-- END sdl.patch --
Unfortunatelly results of this patch completely suprised me. After this patch
my test program produces results witch are impossible to produce in normal
situation. Example output for UP key was:
224 224 72 88224 224 170.
What's wrong with this patch? What I'm doing wrong?
Regards,
--
Rafał Cygnarowski
rafi@pers.pl
next reply other threads:[~2006-06-28 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 8:27 Rafał Cygnarowski [this message]
2006-06-28 8:39 ` [Qemu-devel] qemu kbd emulation Oliver Gerlich
2006-06-28 12:16 ` Rafał Cygnarowski
2006-06-28 14:28 ` Jim C. Brown
2006-06-28 17:27 ` Rafał Cygnarowski
2006-06-29 20:56 ` Rafał Cygnarowski
2006-06-28 15:05 ` Stuart Brady
2006-06-28 9:39 ` Stuart Brady
2006-06-28 10:07 ` Stuart Brady
2006-06-28 11:17 ` Rafał Cygnarowski
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=200606281027.31617.zswi@pers.pl \
--to=zswi@pers.pl \
--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).