Comment 6 for bug 1584475

Revision history for this message
Xaratas (nomikon+ubuntu) wrote :

Ok, tested a bit further. upstream kernel 3.15 generates the input events, but the event devices is only accessible for root.
But thats not a problem as there is also a js0 device which is picked up by stempania and works fine.

uname -a
Linux Y4e 3.15.0-031500-generic #201406131105 SMP Fri Jun 13 15:06:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

ls -l /dev/input/event15
crw-rw---- 1 root input 13, 79 Mai 24 20:12 /dev/input/event15
ls -al /dev/input/js0
crw-rw-r-- 1 root input 13, 0 Mai 24 20:46 /dev/input/js0

sudo evtest output:
Event: time 1464115604.587967, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1464115604.587967, type 1 (EV_KEY), code 294 (BTN_BASE), value 0
Event: time 1464115604.587967, -------------- SYN_REPORT ------------
Event: time 1464115611.017624, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1464115611.017624, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1464115611.017624, -------------- SYN_REPORT ------------
Event: time 1464115611.104563, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1464115611.104563, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1464115611.104563, -------------- SYN_REPORT ------------
Event: time 1464115615.113371, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1464115615.113371, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1464115615.113371, -------------- SYN_REPORT ------------
Event: time 1464115615.295383, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1464115615.295383, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0

upstream kernel 3.17.0 generates some events, but these are spoty and unreliable. The dancemat is not working in Stepmania.

uname -a
Linux Y4e 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

evtest output: if one event appears, then there are huge repetitions of these 0 values which, from the name dose not make much sense for a dance pad, which has no orientation or analog positon x and y.
Event: time 1464115318.219259, -------------- SYN_REPORT ------------
Event: time 1464115318.220260, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 49 (ABS_MT_TOUCH_MINOR), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 51 (ABS_MT_WIDTH_MINOR), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 52 (ABS_MT_ORIENTATION), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 55 (ABS_MT_TOOL_TYPE), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 56 (ABS_MT_BLOB_ID), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 59 (ABS_MT_DISTANCE), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 60 (ABS_MT_TOOL_X), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 61 (ABS_MT_TOOL_Y), value 0

3.19.8 has the bug