commit d07a9cba6be5c0e947afc1014b5a62182a86f1f1 introduced a regression causing the Saitek X52 and X52 Pro to be blacklisted (vid 0x6a3; pid 0x255, 0x075c and 0x762). As a result /dev/input/js* devices won't get created, driving the device useless for most applications.
Hmm, Saitek has no business using the button codes reserved for digitizers...
First-Bad-Commit : d07a9cba6be5c0e947afc1014b5a62182a86f1f1
Created attachment 23054 [details]
Since noone seems to care, here's the revert of the bad commit.
I'm having the same issue with my Saitek X52 Pro.
(In reply to comment #1)
> Hmm, Saitek has no business using the button codes reserved for digitizers...
Then what buttons should it use when it needs 39 buttons to represent all the buttons, hats, and other features found on this combined joystick+throttle unit?
I'm almost certain that this regression is effecting my system. I've not ever tried my Saitek X52 on a non-Windows system in a long while (it *is* currently functioning properly in XP), but am experiencing the symptoms of the device appearing as event in /dev/input but not as /dev/input/jsX. Is there info I can provide for a fix?
Going to try to manually patch and build now and see if this resolves the issue for me.
Not sure if this info is valuable, but I applied diff, compiled kernel, and now my Saitek X52 is functioning properly (and /dev/input is now reflecting corresponding 'js').
The patch works for me too.
Handled-By : Janos Laube <firstname.lastname@example.org>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=23054
Author: Tim Cole <email@example.com>
Date: Thu May 7 17:08:42 2009 -0700
Input: joydev - blacklist digitizers
BTN_TOUCH is not set by the wacom driver which causes it to be handled by the
joydev driver while the resulting device is broken. This causes problems with
applications that try to use a joystick device.
Ubuntu BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/300143
Signed-off-by: Tim Cole <firstname.lastname@example.org>
Signed-off-by: Stefan Bader <email@example.com>
Acked-by: Tim Gardner <firstname.lastname@example.org>
Acked-by: Amit Kucheria <email@example.com>
Signed-off-by: Dmitry Torokhov <firstname.lastname@example.org>
2.6.34 resolves the issue - no patch is needed anymore.
The commit that fixed it: 0b7024ac4df5821347141c18e680b7166bc1cb20