On Wed, 10 Jun 2009, Bastien Nocera wrote: > > Could you please obtain HID debug dump (CONFIG_HID_DEBUG + modprobe > > hid module with 'debug=2') and look at this usage both in the report > > descriptor itself, and also check whether it is present in the > > received reports? > This is the debug output: > http://pastebin.com/m256a4187 > Doesn't look very useful, and I have no idea what the 00ff.00c0 part > does. It doesn't seem to be sending the battery level in a standard-compliant way, at least according to these reports. Could you also please post the report descriptor data? They should appear in a hid debugging mode once the mouse is connected. Does 00ff.00c0 usage change it's value if you put different batteries into the mouse? If this is not successful, looking at what the driver in other operating system does on the transport level might be an option. -- 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
