ps2kbd: default to scancode_set 2, as with KBD_CMD_RESET
commit089adafdc6be4ea2a25593ce92cb5d66b3c90559
authorHervé Poussineau <hpoussin@reactos.org>
Wed, 23 Mar 2016 06:21:40 +0000 (23 07:21 +0100)
committerPaolo Bonzini <pbonzini@redhat.com>
Thu, 7 Apr 2016 22:07:36 +0000 (8 00:07 +0200)
tree79c3268bb1b401b8f878fe3fafdf45c1ee464395
parent7acbff99c6c285b3070bf0e768d56f511e2bf346
ps2kbd: default to scancode_set 2, as with KBD_CMD_RESET

This line has been added in commit ef74679a810fe6858f625b9d52b68cc3fc61eb3d with
other initializations. However, scancode set 0 doesn't exist (only 1, 2, 3).
This works well as long as operating system is resetting keyboard, or overwriting
the current scancode set with the one it wants.

This fixes IBM 40p firmware, which doesn't bother sending KBD_CMD_RESET or KBD_CMD_SCANCODE.

Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
Message-Id: <1458714100-28885-1-git-send-email-hpoussin@reactos.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
hw/input/ps2.c