On Sun, Apr 25, 2010 at 02:42:50PM -0000, ALLurGroceries wrote:
> I could be wrong about 0x0c to reg_10 with regard to your patches.
> Instead of disregarding the high bits I copied the code from the two
> finger condition (but using normal resolution) which is a bit different,
> and probably isn't the right way to do it. However, it worked and I ran
> out of time. I'll bug my friend to get your patches tested and see if it
> works without that register being set. Thanks!
Oh, too bad. I guess I've seen this comment only after I already made
the changes. In case the patch set doesn't work for you as is: please
apply 0001-Input-elantech-allow-forcing-of-different-register-m.patch
and 0002-Input-elantech-whitelist-firmware-version-4.17.patch on top.
If the original set works for you as is (that is, with force_elantech=1),
0001-Input-elantech-whitelist-firmware-version-4.17.patch will do the
whitelisting only, without changing the magic.
I'll hold off sending those patches to linux-input until you've got a
chance to test them. They aren't really relevant to the original patch
series anyway, as that just doesn't change any behaviour on firmware
4.17 yet.
On Sun, Apr 25, 2010 at 02:42:50PM -0000, ALLurGroceries wrote:
> I could be wrong about 0x0c to reg_10 with regard to your patches.
> Instead of disregarding the high bits I copied the code from the two
> finger condition (but using normal resolution) which is a bit different,
> and probably isn't the right way to do it. However, it worked and I ran
> out of time. I'll bug my friend to get your patches tested and see if it
> works without that register being set. Thanks!
Oh, too bad. I guess I've seen this comment only after I already made elantech- allow-forcing- of-different- register- m.patch elantech- whitelist- firmware- version- 4.17.patch on top.
the changes. In case the patch set doesn't work for you as is: please
apply 0001-Input-
and 0002-Input-
If the original set works for you as is (that is, with force_elantech=1), elantech- whitelist- firmware- version- 4.17.patch will do the
0001-Input-
whitelisting only, without changing the magic.
I'll hold off sending those patches to linux-input until you've got a
chance to test them. They aren't really relevant to the original patch
series anyway, as that just doesn't change any behaviour on firmware
4.17 yet.
Thanks again.
--
BOFH excuse #418:
Sysadmins busy fighting SPAM.