diff options
| author | Daniel P. Berrange <berrange@redhat.com> | 2017-10-19 15:28:44 +0100 |
|---|---|---|
| committer | Gerd Hoffmann <kraxel@redhat.com> | 2017-10-23 10:50:02 +0200 |
| commit | 8f63458ff72e6c160db560dca494df5ffbebb15e (patch) | |
| tree | 702a6a1e22a317cc6f3f08292b3d9d289037fbd3 /hw/i2c | |
| parent | 620775d1d8ec4e7e5d3dc6807a9355d6b15cc01d (diff) | |
| download | qemu-8f63458ff72e6c160db560dca494df5ffbebb15e.zip qemu-8f63458ff72e6c160db560dca494df5ffbebb15e.tar.gz qemu-8f63458ff72e6c160db560dca494df5ffbebb15e.tar.bz2 | |
ps2: fix scancodes sent for Shift/Ctrl+Print key combination
The 'Print' key is special in the AT set 1 / set 2 scancode definitions.
An unmodified 'Print' key is supposed to send
AT Set 1: e0 2a e0 37 (Down) e0 b7 e0 aa (Up)
AT Set 2: e0 12 e0 7c (Down) e0 f0 7c e0 f0 12 (Up)
which QEMU gets right. When combined with Shift/Ctrl (both left and right
variants), the leading two bytes should be dropped, resulting in
AT Set 1: e0 37 (Down) e0 b7 (Up)
AT Set 2: e0 7c (Down) e0 f0 7c (Up)
This difference is pretty benign, since of all the operating systems I have
checked (Linux, FreeBSD and OpenStack), none bother to check the leading two
bytes anyway. This change none the less makes the ps2 device better follow real
hardware behaviour.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20171019142848.572-6-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/i2c')
0 files changed, 0 insertions, 0 deletions