Hi Gregor
Am 2016-03-09 12:43, schrieb Gregor Riepl:
I realized that the stick does not conform to the USB HID interface
after looking more closely at the lsusb -v output (pasted below).
The Fightstick seems to use a "Vendor Specific Class" and not the HID
interface.
This may be because Xbox One controllers require a special
initialisation
sequence to make them send input reports at all.
As far as I know, xpad does this for Xbox One pads, but the commands
sent may
not be sufficient for the Mad Catz. This may also be the reason why it
doesn't
show up as a HID device: It's possible that the device descriptor
changes as
soon as initialisation is complete.
So thanks to this suggestion I looked at the xpad.c code again yesterday
to see which initialisation bytes are being sent. When reading through
it I realized that I did not add an entry for the fight stick in the
xpad_table[] array. Adding an entry there using the XPAD_XBOXONE_VENDOR
macro (whose .bInterfaceSubClass and .bInterfaceProtocol values
correspond to what I found in the lsusb -v output) lets the driver find
the stick and also lets me read input from it.
I am travelling till next week but as soon as I get back I will test the
stick's functionality and check if I have to add a quirk. If I find the
stick to be reasonably functional after some tweaking I will send a
patch to the list.
Thanks for your help!
Cheers,
Silvan
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
