Other 3rd party drivers (and seemingly Microsoft's driver as well) uses HID to describe the [any Xbox] controller's features. We can see uses of this in other drivers:
TattieBogle - http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/OsxDriver XBCD - http://www.redcl0ud.com/xbcd.html Xpad has avoided the use of the hid subsystem for whatever reason, for over a decade now. That said, I don't know of any compelling reason to not avoid it. But I did it anyways... I made a small usb driver, implemented a stub hid_ll_driver, copied the descriptor from TattieBogle... and it works... sort of. The button layout is obviously different from what we have now and I cannot get the D-pad working using a Hat Switch usage or the D-pad usages to save my life. I realize that just because other drivers use HID, doesn't mean I should although perhaps there's a compelling reason that I'm missing. Is there any worth to this work? What I have is bare bones but works for (incorrectly mapped, using TattieBogle's report descriptor) input: https://github.com/computerquip/xpad4 Any feedback would be appreciated. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
