On Tue, 8 Sep 2009, Dmitry Torokhov wrote: > > > Here goes /proc/bus/input/devices dump (VID/PID included): > > > > > > I: Bus=0003 Vendor=06a3 Product=0762 Version=0111 > > > N: Name="Saitek Saitek X52 Pro Flight Control System" > > > P: Phys=usb-0000:00:1d.7-6.3/input0 > > > S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb7/7-6/7-6.3/7-6.3:1.0/input/input10 > > > U: Uniq= > > > H: Handlers=event6 > > > B: EV=1b > > > B: KEY=7f ffffffff00000000 0 0 0 0 > > I find it doubtful that the device actually has 39 buttons... Yup, a little bit strange :) That's why I asked Sergey to provide more details about the device. > > > B: ABS=3000003007f > > > B: MSC=10 > > > > If I got my math right, this means that the KEY bitmask includes digitizer > > BTN_DIGI/BTN_TOOL_PEN, right? > > > > Sergey, I believe that reverting commit d07a9cba6b (you can do so using > > git revert d07a9cba6b) will fix your joystick, is that correct? > > While this will get Sergey's joystick back I think that HID should be > more careful in assigning the BTN_* events. Right now it starts at a > certain type and goes forward without checking if range (joystick, > gamepad, etc) is exhausted or not. Let's see the Min/Max values from the HID report descriptor Sergey will hopefully provide. This was mainly heads-up, that there is hardware out there which is affected by this patch. Thanks, -- Jiri Kosina SUSE Labs -- 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
