[ added some CCs In short -- Sergey has problem with his joystick not being properly handled starting with 2.6.30 kernel (it used to work with 2.6.29 and older). The problem is that joydev is not created. ] On Mon, 7 Sep 2009, Sergey Kolesnikov 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 > 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? > This could be compared to device successfully identified as joystick: > > I: Bus=0003 Vendor=06a3 Product=5f0d Version=0110 > N: Name="Saitek PLC Saitek P2600 Rumble Force Pad" > P: Phys=usb-0000:00:1d.7-6.4/input0 > S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb7/7-6/7-6.4/7-6.4:1.0/input/input11 > U: Uniq= > H: Handlers=js0 event7 > B: EV=1b > B: KEY=fff00000000 0 0 0 0 > B: ABS=300c3 > B: MSC=10 Yup, this device doesn't have BTN_DIGI in its keymask, so it's not blacklisted by joydev_blacklist[] entry. It will be also interesting to obtain HID debugging output (*) from the time the device gets plugged in, so that we can check why is mapping of BTN_DIGI established and to check whether it makes any sense. What kind of joystick is that? (*) configure the kernel with CONFIG_HID_DEBUG set, modprobe the 'hid' device with 'debug=2' parameter, plug the device in, and send the dmesg output. -- 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
