EETI eGTouch usb touch panel not detected

[tsukishiro yamazaki]

Hello all,

I have EETI eGTouch usb touch panel for my machine.

According to the "enabling guide" of the driver package for the above touch panel,

I needed to enable the following kernel modules:

1. EVDEV

2. UINPUT

3. HIDRAW

4. HID_MULTITOUCH

I have Android-x86-4.0-RC2 source tree (and kernel source).

I generated my .config file using the command :

        make -C kernel O=$OUT/obj/kernel ARCH=x86 menuconfig

as described in this article

I used that generated .config for TARGET_KERNEL_CONFIG and rebuilt my target

Target is, btw, asus_laptop.

After installing the iso_img to my machine, I checked /dev to see if the kernel modules are working

I see uinput but there is no hidraw

Also, I should be able to see my device from /proc/bus/input/devices but again its not there.

Can someone help me figure out how to enable my touch panel?

Thanks and best regards,

-tsukishiro

[Peter Salzmann]

can you modprobe hidraw?
you can also use lsmod to see the currently loaded modules.

that's about as much expertise as I have, sometimes using M instead of Y in kernel config works better, have you tried any other pre-built isos to see if they work?
try tabletsx86.org

[Dan]

I've had mixed success with the eGalax EETI touchscreen controllers:

This one has worked: ETP_MB_S4000UAGG that I bought from interlogic industries but it's gone End of Life

I just got the replacement from them, the ETP-MB-MER4040UPBG, and it didn't work

This one (also an eGalax) doesn't work: TTW4101016-CT  from a company called top touch

So I've had one out of three eGalax touchscreen controllers work.  They all should use the hid_multitouch driver.  You should see in the dmesg files that the ones that work registrer, and the ones that don't just show up as eGalax touch screen at /dev/input/pci/input0 (or something like that) but the driver never registers.

Something in the driver code looks for a release level of the eGalax touch controller - I think the newer ones don't match the release levels the driver is looking for.  But I didn't know enough to fix the driver. 

I'm still looking for a replacement for the ETP_MB_S4000UAGG controller that I've had some success with.

Dan

[Chih-Wei Huang]

You should follow the instructions to customize kernel config.
http://www.android-x86.org/documents/customizekernel

Do not 'make menuconfig' in kernel dir directly.

2013/5/14 Shawn Thul <sthu...@gmail.com>:
> Hi,
>
> I was wondering if anyone has had any success getting the eGTouchD Driver to
> work correctly?
> I'm using a Neo G4 Android Device and have had no success in getting the
> driver to work.
>
> instructions from TouchKit include modifying 3 modules in the kernel:
> CONFIG_INPUT_EVDEV
> CONFIG_INPUT_UINPUT
> CONFIG_HIDRAW (For USB Interface)
>
> I cannot simply get the 'make 'menuconfig' to work on my android device.
>
> Any thoughts?
>
> Thanks,
> Shawn


--
Chih-Wei
Android-x86 project
http://www.android-x86.org