----- Original message ----- > On Fri, 11 Mar 2011, Rafi Rubin wrote: > > > On a related note, I looked into switching to usbhid_submit_report for > > firmware version polling but it looks like the report offset (or > > something like that) is wrong. > > > > I get: > > af082500 > > > > usbmon shows the devices sends: > > 0c002508 afe10000 > > > > If I change the report offset in the field to 8, I get the desired > > bits: e1af0825 > > > > > > I don't really know much about parsing the hid descriptors, so I don't > > know why its off by a byte. Perhaps its worth testing a different > > firmware to see if this is specific to my current firmware. > > I am not really sure I fully understand what you are saying here. Just > for clarification: > > - isn't the byte the 'report id' number here? > - does your message mean that the patch doesn't work? Or is this quite > the contrary -- explanation why it is written the way it is (i.e. using > usb_control_msg() instead of usbhid_submit_report())? usbhid_submit_report does not work for calibration and firmware version polling. Sorry for the confusion. Rafi -- 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
