X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=extras%2Fkeymap%2FREADME.keymap.txt;h=9c2d5dc16a151d57720b1dfe39e784f1b1d47367;hb=23c455b887e039183a1b2d78305df7b9f1cdad73;hp=274dc6ac83152653f9702626bf6a7f71b5ae94fa;hpb=f0f7a43f4e60bc2233d86e6f24e2aca2410bc85e;p=elogind.git

diff --git a/extras/keymap/README.keymap.txt b/extras/keymap/README.keymap.txt
index 274dc6ac8..9c2d5dc16 100644
--- a/extras/keymap/README.keymap.txt
+++ b/extras/keymap/README.keymap.txt
@@ -48,7 +48,8 @@ for inclusion you need to do the following steps:
  keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
  Acers) have multimedia/function keys on a separate input device instead of the
  primary keyboard. The keyboard device should have a name like "input/event3".
- In the following commands, the name will be written as "input/eventX".
+ In the following commands, the name will be written as "input/eventX" (replace
+ X with the appropriate number).
 
  2. Dump current mapping:
 
@@ -73,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