summaryrefslogtreecommitdiff
path: root/usr.sbin/vipw
diff options
context:
space:
mode:
authorConstantine Sapuntzakis <csapuntz@cvs.openbsd.org>2000-12-19 06:58:40 +0000
committerConstantine Sapuntzakis <csapuntz@cvs.openbsd.org>2000-12-19 06:58:40 +0000
commit135df068726fceeb3fd0e44f16868d8a2089e3d4 (patch)
tree232b4a305dc06ea94125756f193edee2828530da /usr.sbin/vipw
parentf75a5344ac66f9ab3e9de8c22e308cbd146af9b3 (diff)
This fixes keyboard lock-ups I was getting wiggling the mouse in
console mode while using my omnicube KVM switch. The keyboard lock-ups were caused by the keyboard/mouse interface controller's input buffer filling up. This was caused because the mouse was sending data to the computer and the pms driver wasn't draining it. The driver used to rely on the fact that it could disable the mouse device when the mouse driver was closed. Disabling the mouse device prevents it from sending data to the computer. At the same time pms disabled the mouse device, pms disabled interrupt notification of the arrival of new data. This regime doesn't work so well with KVM switches which re-enable the mouse. In this case, the mouse will send data to the computer but the keyboard/moust interface controller won't raise an interrupt (because pms disabled interrupts). pms will never read from the input buffer.
Diffstat (limited to 'usr.sbin/vipw')
0 files changed, 0 insertions, 0 deletions