From c6153a9ae947a0ae349ab87d39be07e380847df4 Mon Sep 17 00:00:00 2001 From: fp4code Date: Tue, 16 Feb 2016 10:18:20 +0100 Subject: [PATCH] Updated Linux udev keys binding (markdown) --- Linux-udev-keys-binding.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Linux-udev-keys-binding.md b/Linux-udev-keys-binding.md index 1b5122f..fff4624 100644 --- a/Linux-udev-keys-binding.md +++ b/Linux-udev-keys-binding.md @@ -15,16 +15,18 @@ Or interrupt and restart `evtest` giving the device path sudo evtest /dev/input/event6 +First, read the line `Input device ID:` + + Input device ID: bus 0x3 vendor 0xef5 product 0x3014 version 0x100 + +memorize bus, vendor and product values using 4 capitalized digits without 0x: `0003` `0EF5` `3014`. They will be used later. + Click on device buttons and read scancode after `(MSC_SCAN), value` Event: time 1455575367.579903, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004b The scancode is here `7004b`. -Other interesting values were written at the beginning: - - Input device ID: bus 0x3 vendor 0xef5 product 0x3014 version 0x100 - As root, create a file `/etc/udev/hwdb.d/61-smart-pointer.hwdb` and put in it something similar to ### Smart pointer UP4-SP-800 (aka Satechi SP600) binding example ###