>> > Anyone having such a keyboard and willing to run some tests?
[...]
> (c) Then use 'input-events <device-number>' to get a input event log
> printed to the terminal. Type each missing key once.
>
> (d) Send me the log (with annotation which key is which).
There are two missing keys: / (which is also ? with shift) in the normal
keyboard and . in the numpad.
Here are the logs for two ABNT2 keyboards:
First keyboard:
/dev/input/event0
bustype : BUS_USB
vendor : 0x45e
product : 0x750
version : 273
name : "Microsoft Wired Keyboard 600"
phys : "usb-0000:00:1d.1-1/input0"
uniq : ""
bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
waiting for events
12:44:00.341645: EV_MSC MSC_SCAN 458792 <== RETURN released when
input-events was run
12:44:00.341645: EV_KEY KEY_ENTER (0x1c) released
12:44:00.341645: EV_SYN code=0 value=0
12:44:02.389552: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
12:44:02.389552: EV_KEY KEY_RO (0x59) pressed
12:44:02.389552: EV_SYN code=0 value=0
/12:44:02.517537: EV_MSC MSC_SCAN 458887 <== Here, / was released
12:44:02.517537: EV_KEY KEY_RO (0x59) released
12:44:02.517537: EV_SYN code=0 value=0
12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was pressed
12:44:04.253486: EV_KEY KEY_KPCOMMA (0x79) pressed
12:44:04.253486: EV_SYN code=0 value=0
.12:44:04.381484: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was
released
12:44:04.381484: EV_KEY KEY_KPCOMMA (0x79) released
12:44:04.381484: EV_SYN code=0 value=0
Second keyboard:
/dev/input/event15
bustype : BUS_USB
vendor : 0x4f3
product : 0x103
version : 272
name : "HID 04f3:0103"
phys : "usb-0000:00:1d.3-2/input0"
uniq : ""
bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
waiting for events
13:00:00.686312: EV_MSC MSC_SCAN 458792 <== RETURN released when
input-events was run
13:00:00.686312: EV_KEY KEY_ENTER (0x1c) released
13:00:00.686312: EV_SYN code=0 value=0
13:00:03.182228: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
13:00:03.182228: EV_KEY KEY_RO (0x59) pressed
13:00:03.182228: EV_SYN code=0 value=0
/13:00:03.254226: EV_MSC MSC_SCAN 458887 <== Here, / was released
13:00:03.254226: EV_KEY KEY_RO (0x59) released
13:00:03.254226: EV_SYN code=0 value=0
13:00:04.942163: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was pressed
13:00:04.942163: EV_KEY KEY_KPCOMMA (0x79) pressed
13:00:04.942163: EV_SYN code=0 value=0
.13:00:05.030163: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was
released
13:00:05.030163: EV_KEY KEY_KPCOMMA (0x79) released
13:00:05.030163: EV_SYN code=0 value=0
Both keys are fixed with the following patch that I sent previously:
--- ui/x_keymap.c~
+++ ui/x_keymap.c
@@ -94,7 +94,7 @@
*/
static const uint8_t evdev_keycode_to_pc_keycode[61] = {
- 0, /* 97 EVDEV - RO ("Internet" Keyboards) */
+ 0x73, /* 97 EVDEV - /?<C2><B0> (ABNT2 Keyboards) */
0, /* 98 EVDEV - KATA (Katakana) */
0, /* 99 EVDEV - HIRA (Hiragana) */
0x79, /* 100 EVDEV - HENK (Henkan) */
@@ -126,7 +126,7 @@
0, /* 126 EVDEV - I126 ("Internet" Keyboards) */
0, /* 127 EVDEV - PAUS */
0, /* 128 EVDEV - ???? */
- 0, /* 129 EVDEV - I129 ("Internet" Keyboards) */
+ 0x34, /* 129 abnt2 KP-period */
0xf1, /* 130 EVDEV - HNGL (Korean Hangul Latin toggle) */
0xf2, /* 131 EVDEV - HJCV (Korean Hangul Hanja toggle) */
0x7d, /* 132 AE13 (Yen)*/
Thank you,
Joao Luis.
