I have a possible hardware problem with my test balloon3 device - this could mean that my latest tests are not caused by the changes in the driver.
AFAICT the original tests were fine - something happened to the device after I first got the touchscreen working. Although X works fine, the touchscreen results are just too variable right now to make much sense of the tests for the patched driver. I have reverted to the current driver version with no change in the variation in touchscreen X values. The current problem completely masks the original "scaling" issue. I'm fairly sure this is a new problem - current behaviour results in the X axis being 1 pixel wide. Previous tests did show that the X axis behaved correctly, within the limits of the hardcoded axes values. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
signature.asc
Description: This is a digitally signed message part
