On Wed, 20 Jun 2007, Anssi Hannula wrote: > > did you make any progress here please? I am going to merge the patch, > > still I'd be understand what caused it (on the other hand from Diogo's > > last comment it doesn't seem 100% certain that we cased it somewhere > > around 2.6.20). > I finally had time to bisect 2.6.20 vs 2.6.21, and for me it seems to > start happening after commit 4237081e573b99a48991aa71364b0682c444651c:
Hi Anssi, thanks a lot. Could you please check any kernel after the commit 46386b587086c8d2698222a031bf749688464032 (for example 2.6.22-rc1)? That should be the definitive fix for all issues with zeroing of unused bits in output reports. Thanks, -- Jiri Kosina
