Op 05-05-10 20:09, Dmitry Torokhov schreef: > On Wednesday 05 May 2010 11:00:48 am Florian Ragwitz wrote: : >> Some firmwares always set the upper bits to 0. Others don't. >> >> As far as I can see, we only know about firmware version 2.1 and 4.1 >> using those high bits for width reports. >> >> However, there's firmware versions inbetween, like 2.48, which don't >> report width information. And there's even other firmware versions >> inbetween, like 2.36, which actually implment what the driver calls >> hardware version 1. Those have a quite different packet format, and also >> no width information. > > What we need to figure out if 2.48 and 2.36 are in fact something like > 2.0.48 and 2.0.36.. And 2.1 is actually 2.x.1. Then it would all make > better sense. Could it be that the ability of detecting width is indicated in the capability bytes? Here I have 0x08 0x13 0x0d . Eric -- 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
