guerrerolor / android-x86

Automatically exported from code.google.com/p/android-x86
2 stars 1 forks source link

Faytech Automotive Touchscreen Monitor #670

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. connect Faytech monitor to VGA and USB 
2. compile Android with usbtouchscreen eGalax
3. load and run

What is the expected output? What do you see instead?
Touchscreen responding correctly

What version of the product are you using? On what operating system?
gingerbread, honeycomb, ics

Please provide any additional information below.
Faytech Automotive monitors us a eGalax 4000 series chipset and reports as a 
0EEF:0001 ver 100 device. However there are 2 version of 0EEF:0001. The first 
version is for the 4000 series chip running as a Resistive Touch screen and is 
referenced with the 1.1 development manual. The second version is for the 
development chipset referenced with the 2.0 development manual. This is used to 
develop and than once done is assigned a new ID (example is the Dell 0EEE:a001)

Attached is a patch file for both the usbtouchscreen.c and the Kconfig to allow 
the choice of the older eGalax controller on a Faytech monitor. There are over 
20,000 of these units in the market place. I have over 500!!

Original issue reported on code.google.com by markesse...@gmail.com on 3 Feb 2012 at 5:44

Attachments:

GoogleCodeExporter commented 9 years ago
Applied to android-3.2 branch.

Original comment by cwhuang@android-x86.org on 22 Feb 2012 at 8:41