[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1386478] [NEW] PS/2 keyboard returns incorrect scan co
From: |
Kevin Lamonte |
Subject: |
[Qemu-devel] [Bug 1386478] [NEW] PS/2 keyboard returns incorrect scan code for F7 to guest |
Date: |
Tue, 28 Oct 2014 01:39:27 -0000 |
Public bug reported:
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).
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1386478
Title:
PS/2 keyboard returns incorrect scan code for F7 to guest
Status in QEMU:
New
Bug description:
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).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1386478/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |