mtouchusb.txt 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. CHANGES
  2. - 0.3 - Created based off of scanner & INSTALL from the original touchscreen
  3. driver on freecode (http://freecode.com/projects/3mtouchscreendriver)
  4. - Amended for linux-2.4.18, then 2.4.19
  5. - 0.5 - Complete rewrite using Linux Input in 2.6.3
  6. Unfortunately no calibration support at this time
  7. - 1.4 - Multiple changes to support the EXII 5000UC and house cleaning
  8. Changed reset from standard USB dev reset to vendor reset
  9. Changed data sent to host from compensated to raw coordinates
  10. Eliminated vendor/product module params
  11. Performed multiple successful tests with an EXII-5010UC
  12. SUPPORTED HARDWARE:
  13. All controllers have the Vendor: 0x0596 & Product: 0x0001
  14. Controller Description Part Number
  15. ------------------------------------------------------
  16. USB Capacitive - Pearl Case 14-205 (Discontinued)
  17. USB Capacitive - Black Case 14-124 (Discontinued)
  18. USB Capacitive - No Case 14-206 (Discontinued)
  19. USB Capacitive - Pearl Case EXII-5010UC
  20. USB Capacitive - Black Case EXII-5030UC
  21. USB Capacitive - No Case EXII-5050UC
  22. DRIVER NOTES:
  23. Installation is simple, you only need to add Linux Input, Linux USB, and the
  24. driver to the kernel. The driver can also be optionally built as a module.
  25. This driver appears to be one of possible 2 Linux USB Input Touchscreen
  26. drivers. Although 3M produces a binary only driver available for
  27. download, I persist in updating this driver since I would like to use the
  28. touchscreen for embedded apps using QTEmbedded, DirectFB, etc. So I feel the
  29. logical choice is to use Linux Input.
  30. Currently there is no way to calibrate the device via this driver. Even if
  31. the device could be calibrated, the driver pulls to raw coordinate data from
  32. the controller. This means calibration must be performed within the
  33. userspace.
  34. The controller screen resolution is now 0 to 16384 for both X and Y reporting
  35. the raw touch data. This is the same for the old and new capacitive USB
  36. controllers.
  37. Perhaps at some point an abstract function will be placed into evdev so
  38. generic functions like calibrations, resets, and vendor information can be
  39. requested from the userspace (And the drivers would handle the vendor specific
  40. tasks).
  41. TODO:
  42. Implement a control urb again to handle requests to and from the device
  43. such as calibration, etc once/if it becomes available.
  44. DISCLAIMER:
  45. I am not a MicroTouch/3M employee, nor have I ever been. 3M does not support
  46. this driver! If you want touch drivers only supported within X, please go to:
  47. http://www.3m.com/3MTouchSystems/
  48. THANKS:
  49. A huge thank you to 3M Touch Systems for the EXII-5010UC controllers for
  50. testing!