Comment 3 for bug 933258

Revision history for this message
falkTX (Old) (falk-t-j) wrote :

fair enough for me.

I'm currently busy with other stuff at the moment, but nothing stops you from giving me information about the device.
1- device ID as reported by 'lsusb' (connect it over usb and use 'lsusb', you should have some XXXX:YYYY code)
2- jstest information, run it and report me number of axis and buttons. also which button and axis number maps to what buttons on the hardware
3- event dump, run 'sudo hidraw-dump /dev/hidrawX' with it connected over USB. it should print a consistent hexadecimal data. do some analisys to figure out which the codes, like:

0xA0 0x00 0x01 0x00 ....

and report to me the values in order, which in this example could be:
0xA0 - static value, never changes
0x00 - same
0x01 - button #1
0x00 - button #2

then go for line 2, etc until you find a blank newline in hidraw-dump's output.

some of the dumped events may correspond to voltage, battery status, connection status, or other.

thanks in advance!