-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| the kernel should just send out the unfiltered evens and let userspace | decide what to do with it. And if userspace decides to do Nonsense, even a floppy driver does retries on bad data before giving up to userspace. | So let's look forward and find a better solution to the "compose a | custom filterchain" problem! I don't think we need it. What's going on here is a workaround for broken hardware, all GTA02 touchscreen have the same broken erratic behaviour. Therefore it's fine if mach-gta02.c is issuing a specific prescription to hide that from userspace for all GTA02. Today we had Marco telling us specifically that 2.6.28 touchscreen filtering arrangements made things slow for him. But, when we looked closer, it seems the keyboard code itself can be broken and slow (I gave a link to the thread on Community list) and we did not nail down that there was any problem with our existing arrangements, he didn't reply yet about tests with the python script so we can isolate the slowness to the keyboard or the touchscreen filter action. It also turned out he's running a unique old build of stable-tracking (not recommended anyway) with a bunch of patches ripped out. So if I were you before embarking on a project to compose a custom filterchain I would try to quantify what it is you think needs fixing, I suspect we find there isn't much and what there is can be done by tweaking parameters in mach-gta02.c. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmA0MUACgkQOjLpvpq7dMq1rgCeLf0mg4WZ6ve1v+oA148sSqIV E1YAoIwpMGoM9mg1/+HZzVsW1ORaJfz0 =iiTE -----END PGP SIGNATURE-----
