From: Martin Pitt Date: Tue, 5 Jan 2010 08:52:30 +0000 (+0100) Subject: keymap: Document force-release X-Git-Tag: 174~649 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=1e69248fec27deb701713d2dc7bc449976ef0cce keymap: Document force-release Make a note in README.keymap.txt about stuck keys which need a force-release quirk. --- diff --git a/extras/keymap/README.keymap.txt b/extras/keymap/README.keymap.txt index ae8916bb6..9c2d5dc16 100644 --- a/extras/keymap/README.keymap.txt +++ b/extras/keymap/README.keymap.txt @@ -74,6 +74,12 @@ for inclusion you need to do the following steps: /lib/udev/keymaps/ for existing key map files and make sure that you use the same structure. + If the key only ever works once and then your keyboard (or the entire desktop) + gets stuck for a long time, then it is likely that the BIOS fails to send a + corresponding "key release" event after the key press event. Please note down + this case as well, as it can be worked around in + /lib/udev/keymaps/95-keyboard-force-release.rules . + 4. Find out your system vendor and product: cat /sys/class/dmi/id/sys_vendor