diff options
| author | Daniel P. Berrange <berrange@redhat.com> | 2017-07-27 12:32:43 +0100 |
|---|---|---|
| committer | Gerd Hoffmann <kraxel@redhat.com> | 2017-07-27 14:24:05 +0200 |
| commit | 7c388dbd0b2c54b3d836c23ea43e2cee38de66a4 (patch) | |
| tree | c14c3ca8d6156143a6a464d8006b3d65585b39d0 /hw/vfio/platform.c | |
| parent | 912092b8e47f31c3db25e088af8460d9e752da29 (diff) | |
| download | focaccia-qemu-7c388dbd0b2c54b3d836c23ea43e2cee38de66a4.tar.gz focaccia-qemu-7c388dbd0b2c54b3d836c23ea43e2cee38de66a4.zip | |
ps2: fix sending of PAUSE/BREAK scancodes
The processing of the scancodes for PAUSE/BREAK has been broken since
the conversion to qcodes in:
commit 8c10e0baf0260b59a4e984744462a18016662e3e
Author: Hervé Poussineau <hpoussin@reactos.org>
Date: Thu Sep 15 22:06:26 2016 +0200
ps2: use QEMU qcodes instead of scancodes
When using a VNC client, with the raw scancode extension, the client
will send a scancode of 0xc6 for both PAUSE and BREAK. There is mistakenly
no entry in the qcode_to_number table for this scancode, so
ps2_keyboard_event() just generates a log message and discards the
scancode
When using a SPICE client, it will also send 0xc6 for BREAK, but
will send 0xe1 0x1d 0x45 0xe1 0x9d 0xc5 for PAUSE. There is no
entry in the qcode_to_number table for the scancode 0xe1 because
it is a special XT keyboard prefix not mapping to any QKeyCode.
Again ps2_keyboard_event() just generates a log message and discards
the scancode. The following 0x1d, 0x45, 0x9d, 0xc5 scancodes get
handled correctly. Rather than trying to handle 3 byte sequences
of scancodes in the PS/2 driver, special case the SPICE input
code so that it captures the 3 byte pause sequence and turns it
into a Pause QKeyCode.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170727113243.23991-1-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/vfio/platform.c')
0 files changed, 0 insertions, 0 deletions