On Wed, 19 Mar 2008, Pete Zaitcev wrote: > To tell you the truth, I just now noticed that the button does not > work. Kernel prints this: > hiddev96hidraw0: USB HID v1.10 Device [DMI WD5000AAKB-00UKA] on usb-0000:00:13.5-3 > But then the events do not get delivered. This is what happens > with DEBUG enabled in hid-core.c: > usb 2-3.2: new high speed USB device using address 3 > INPUT[INPUT] > Field(0) > Usage(2) > ffa0.00a6 > ffa0.00a7 > Logical Minimum(-128) > Logical Maximum(127) > Report Size(8) > Report Count(2) > Report Offset(0) > Flags( Variable Absolute ) Hi Pete, yes, so the device doesn't provide any application we handle in HID <-> input mapping, it contains only vendor-speicific usages from 0xffa0 page. hiddev/hidraw device surely is created for this device (as it is not handled by hid-input), so a userspace driver can be written easily to handle this button. So your patch makes sense, I will apply it to my tree, 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
