mtouchusb.rst 2.8 KB

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