extras/keymap/findkeyboards: Filter out non-event devices

[elogind.git] / extras / keymap / README.keymap.txt

diff --git a/extras/keymap/README.keymap.txt b/extras/keymap/README.keymap.txt
index eab8587de8abd5747ebb268ef7977f0518bfe9d8..79d9971b1d64b666d12964ebf466d53218354b4c 100644 (file)
--- a/extras/keymap/README.keymap.txt
+++ b/extras/keymap/README.keymap.txt
@@ -48,13 +48,10 @@ 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:
-
- sudo /lib/udev/keymap input/eventX > /tmp/orig-map.txt
-
- 3. Find broken scan codes:
+ 2. Find broken scan codes:
 
  sudo /lib/udev/keymap -i input/eventX
 
@@ -73,18 +70,22 @@ 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.
 
- 4. Find out your system vendor and product:
+ 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 .
+
+ 3. Find out your system vendor and product:
 
  cat /sys/class/dmi/id/sys_vendor
  cat /sys/class/dmi/id/product_name
 
- 5. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".
-
- 6. Send the system vendor/product names, the key mapping from step 3,
- /tmp/orig-map.txt from step 2, and /tmp/udev-db.txt from step 5
- to the bug tracker, so that they can be included in the next release:
+ 4. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".
 
-   https://bugs.launchpad.net/udev-extras/+bugs
+ 6. Send the system vendor/product names, the key mapping from step 2,
+ and /tmp/udev-db.txt from step 4 to the linux-hotplug@vger.kernel.org mailing
+ list, so that they can be included in the next release.
 
 For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
 name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules: