Em Mon, 7 Sep 2020 16:58:06 +0200 Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> escreveu: > Em Mon, 7 Sep 2020 15:43:09 +0100 > Sean Young <sean@xxxxxxxx> escreveu: > > > On Mon, Sep 07, 2020 at 11:36:59AM +0200, Mauro Carvalho Chehab wrote: > > > While --device option doesn't work for enumerating and for RC/LIRC > > > specific control, it is still useful for testing purposes > > > for all kinds of input devices. For example, it can be used to > > > test mouse events: > > > > > > $ ./utils/keytable/ir-keytable -d /dev/input/event4 -t > > > Testing events. Please, press CTRL-C to abort. > > > 1222738.567737: event type EV_REL(0x02): REL_X (0x0000) value=1 > > > 1222738.567737: event type EV_SYN(0x00). > > > 1222738.573742: event type EV_REL(0x02): REL_X (0x0000) value=1 > > > 1222738.573742: event type EV_SYN(0x00). > > > 1222738.581738: event type EV_REL(0x02): REL_X (0x0000) value=2 > > > 1222738.581738: event type EV_REL(0x02): REL_Y (0x0001) value=1 > > > > > > So, re-add it, but only on test mode. > > > > Isn't this the same functionality as evtest(1), but not as complete? > > > > https://cgit.freedesktop.org/evtest/ > > > > evtest is packaged for Fedora, Debian, and Ubuntu. > > No idea. At least on the device I'm testing (Hikey 970), evtest doesn't > produce anything when I move my mouse (checking via ssh): > > $ sudo evtest > No device specified, trying to scan all of /dev/input/event* > Available devices: > /dev/input/event0: PixArt Dell MS116 USB Optical Mouse > Select the device event number [0-0]: > > While ir-keytable works fine. Gah! it actually expects a "0" as input, as pressing just <enter> does nothing. crap! Thanks, Mauro
