Hi,
Does anybody know the reason why hid input report "caching" / "duplicate elimination" is really needed? That is, if a HID device sends a report with the same absolute value twice, the second report gets swallowed in hid_input_field(). Similarly, relative values of zero never make it through to the userland client. Is there a compelling reason why we must have this? The problem I have with this, is that there are several devices broken by this behavior. There is Bug 1048 in the Linux Bugzilla (http://bugzilla.kernel.org/show_bug.cgi?id=1048) which was opened in 2003 and is still in the "New" state; there is a proposed fix attached by the original reporter, but so far nobody has commented on it neither negatively nor positively.
We distribute the patch with our USB-attached "hardtoken initializers" which we make, but it would be interesting to completely understand all parties' concerns and agree on an "official" solution.
Boris
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
