blob: fc7c9b8ca7672a9c0ef592e7133be5def4efb650 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
device: 0.869
ppc: 0.860
graphic: 0.722
performance: 0.704
mistranslation: 0.624
socket: 0.606
vnc: 0.589
semantic: 0.556
debug: 0.518
network: 0.501
register: 0.473
architecture: 0.470
PID: 0.445
risc-v: 0.422
i386: 0.375
boot: 0.354
files: 0.354
arm: 0.350
user-level: 0.350
x86: 0.314
permissions: 0.304
VMM: 0.253
peripherals: 0.248
kernel: 0.209
hypervisor: 0.209
TCG: 0.205
virtual: 0.135
assembly: 0.058
KVM: 0.037
PS/2 keyboard returns incorrect scan code for F7 to guest
Using qemu 2.1 as supplied in Debian jessie, the F7 scan code (scan set 2) is being returned by qemu to the guest as 0x02, and not the correct value of 0x83. (I assume 0x83 is correct, given that I cannot locate any scan set 2 charts that use any other value for F7. Including those published by Microsoft.)
I see the map in hw/input/ps2.c ps2_raw_keycode[] using the correct values, starting at F1: 5, 6, 4, 12 (0x0C). 3. 11 (0x0B), 2, 10 (0x0A), 1, 9, ... but nowhere in that map do I see 131 (0x83).
I think this has been fixed by:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=8c10e0baf0260b5
... so closing this ticket now. If you still have trouble, please re-open it.
|