There are more USB touchscreen drivers that can store calibration data in EEPROM, e.g. the DMC TSC-10/25. I know, because I contributed the part to handle this USB touchscreen controller into the kernel :-) > > > But in my application I kept the calibration data in the filesystem, and the hardware didn't have an EEPROM soldered anyway.
Still I can see how a generic support would be useful, so I still recommend to look and/or use usbtouchscreen.c. Adding some "write calibration data" that is generic enought so that other controllers can eventually be handled, too, would be very acceptable by the input driver maintainers of the Linux kernel community. Also, even when the driver doesn't get a "write calibration data" feature, it's simply to write to the controller from user-space using libusb. Libusb is really simply to use! So you could use the usbtouchscreen.c to get coordinates out, but a user-space tool to do calibration and calibration programming. For the first part (determining the calibration coeffizients) you'd need a user-space tool anyway :-) -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
