Linux drivers for Lilliput Touchscreen?

Visual Echo · 02-28-2004, 09:51 PM

I'm looking for drivers for the USB touchscreen itself, not video.

I've found an old set of drivers for the 'TouchKit' with all the files inside dated November 29, 2002... they support Red Hat v8.0, but crash and burn trying to compile with Fedora Core 1. I think I'm figuring it out, but these still seem... old. That's not usually a problem if the device itself doesn't change.

Anybody seen any updated drivers? I've only spent a few hours (not days) searching the web, nada so far except as above.

I've had some other trouble with the Lilliput video, but I'll save that for another topic.

Nokia6600 · 02-29-2004, 03:42 AM

Quote: Originally Posted by Visual Echo

I'm looking for drivers for the USB touchscreen itself, not video.

I've found an old set of drivers for the 'TouchKit' with all the files inside dated November 29, 2002... they support Red Hat v8.0, but crash and burn trying to compile with Fedora Core 1. I think I'm figuring it out, but these still seem... old. That's not usually a problem if the device itself doesn't change.

Anybody seen any updated drivers? I've only spent a few hours (not days) searching the web, nada so far except as above.

I've had some other trouble with the Lilliput video, but I'll save that for another topic.

I can't help you right now but as soon as I get my touchscreen I will be making universal Linux drivers for Gnome and KDE (Open source)
I probably getting the screen within 2 week and it shouldt take more then a couple of days to program and test the touchscreen drivers for this particular ts

Maeveth · 03-01-2004, 06:41 PM

I would also be very interested in getting linux Lilliput Drivers

001 · 03-05-2004, 05:12 PM

Quote: Originally Posted by Visual Echo

I'm looking for drivers for the USB touchscreen itself, not video.

I've found an old set of drivers for the 'TouchKit' with all the files inside dated November 29, 2002... they support Red Hat v8.0, but crash and burn trying to compile with Fedora Core 1. I think I'm figuring it out, but these still seem... old. That's not usually a problem if the device itself doesn't change.

Anybody seen any updated drivers? I've only spent a few hours (not days) searching the web, nada so far except as above.

The driver is TouchKit, it support Mandrake Linux ( X86 ), Red Hat Linux ( X86 ), and Yellow Dog Linux ( PowerPC ), the latest drivers are available from TouchKit manufacturer:

http://www.egalax.com.tw/Download.htm

Our customer have installed many the Lilliput 619GL-70NP into a self-assembled gaming system using Red Hat Linux.

Paul
Allcam -World of Portables
www.allcam.biz
www.portable-dvd-player.co.uk/catalog/

cowiam · 04-14-2004, 09:48 PM

I just found a patch for the usb driver for the 2.4.20 kernel, and I'm going to try it on RH9. I bet it will work for the 2.4.22 kernel too. If anyone has success with it on Fedora I'd like to hear about it.

http://cvs.pld.org.pl/SOURCES/touchkit-2.4.20.patch

tejohnson · 05-14-2004, 08:50 AM

See:

http://marc.theaimsgroup.com/?l=linu...1374426876&w=2

It should make it into the 2.6.7 kernel. It is currently in the latest -mm patches available at kernel.org (This will get much easier over time). Have fun!

kevlar · 05-28-2004, 03:14 AM

I have successfully made the Lilliput 7" to work under XFree86, with one hitch.

The cursor moves faster than I slide my finger, causing it to jump to the wrong spot when I touch my finger on a specific spot. I've tried setting Option "Resolution" and the Option "MinX" and the "MaxX" etc settings. Nothing changed it. We're guessing it is a hardcoded value in the driver source as specified by TOUCHKIT_MAX_XC, etc.

So, you can either patch your current kernel, or go grab 2.6.7 (it has the current eGalax driver as touchkitusb.c). Be sure to enable eGalax in your kernel, and recompile, reboot.

Oh, in order to get the Lilliput to work under XFree86, this is my clip for configuring it (I had to Invert X and then Flip X with Y).

Section "InputDevice"
Identifier "TouchScreen0"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/input/mouse0"
Option "SendCoreEvents"
Option "FlipXY"
Option "InvX"
EndSection

Adjust accordingly.

Regards,

Kevin Elliott

tejohnson · 05-28-2004, 10:34 PM

The issues you are having are due to using the wrong X driver. Use the following howto (Steps #8 - #11) for the right driver.

http://www.groomlakelabs.com/grandam...reen-HowTo.txt

The X mouse driver relies on relative data (REL). This touch driver, which is a derivitave of the one I wrote (mtouchusb), reports absolute data (ABS). If you use the driver I have in the howto, it should fix your issues. Hope this helps!

If not, and you are using the X driver in the howto, let me know, or send the author a message with the problems. I'm sure he would be happy to help fix the issue!

htd · 05-30-2004, 08:59 AM

I have the same issues - i have got a egalax touchscreen and run kernel 2.6.7rc1 (now has got a egalax driver!).

Using /dev/input/mouse0 and the mouse driver like kevlar does results at least in a weird working touchscreen - but using your tips from http://www.groomlakelabs.com/grandam...reen-HowTo.txt

does result in even more weird behaviour. Sometimes the cursor doesn't move at all - i guess that's related to the MinX, MinY, etc. options, but i don't know how to setup valid values for this (i'm still trying different values).

What i also didn't find was where to get the evtest utility... it isn't installed on my gentoo system and i don't know whicht package it is related to.

I hope i can get to work with the new kernel driver, then i don't have to use these closed source drivers from egalax, although it's probably the easiest way to get it working

HTD

htd · 05-30-2004, 10:12 AM

With these settings my touchscreen works quite ok (last issue is that the vertical movement is inverted... when i touch the bottom of the screen the cursor moves to the top and vice-versa)
horizontal movement works normally.

Code:

Section "InputDevice"
        Identifier "touchscreen"
        Driver "evtouch"
        Option "Device" "/dev/input/event1"
        Option "DeviceName" "touchscreen"
        Option "MinX" "200"
        Option "MinY" "200"
        Option "MaxX" "2048"
        Option "MaxY" "2048"
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons"
        Option "Emulate3Timeout" "50"
        Option "SendCoreEvents"
EndSection

hope that helps someone
HTD

tejohnson · 05-30-2004, 02:41 PM

Quote: Originally Posted by htd

I have the same issues - i have got a egalax touchscreen and run kernel 2.6.7rc1 (now has got a egalax driver!).

Using /dev/input/mouse0 and the mouse driver like kevlar does results at least in a weird working touchscreen - but using your tips from http://www.groomlakelabs.com/grandam...reen-HowTo.txt

does result in even more weird behaviour. Sometimes the cursor doesn't move at all - i guess that's related to the MinX, MinY, etc. options, but i don't know how to setup valid values for this (i'm still trying different values).

What i also didn't find was where to get the evtest utility... it isn't installed on my gentoo system and i don't know whicht package it is related to.

I hope i can get to work with the new kernel driver, then i don't have to use these closed source drivers from egalax, although it's probably the easiest way to get it working

HTD

Don't use /dev/input/mouse0, use the event interface. The mouse handle attempts to give coordinates in relative data, and this simply seems broken (Which can not be fixed in this driver, but in the linux input subsystem instead). If you look back at the howto, you will see the the event interface is used. (ex: /dev/input/event1). The howto should help you find the appropriate event handle. Sorry, I should have clarified this in my last post. In short, use the entire howto to help you get the device working. Although it is for mtouchusb (3m touch controllers), you should get the same results, only using a different device. Make sure you build the kernel for touchkitusb and not mtouchusb with this device though

.

For evtest, you can d/l it from:

http://groomlakelabs.com/grandamp/co.../applications/

To build, just do:
gcc -o evtest evtest.c
chmod 755 evtest
./evtest /dev/input/event1 (Or what ever event interface is assigned to the device)

Hope this helps!

tejohnson · 05-30-2004, 02:45 PM

Quote: Originally Posted by htd

With these settings my touchscreen works quite ok (last issue is that the vertical movement is inverted... when i touch the bottom of the screen the cursor moves to the top and vice-versa)
horizontal movement works normally.

So you are saying that the verticle movement is still inverted?

ismell · 06-01-2004, 01:29 AM

ok i got it working all nice and prefect

Do what tejohnson said to do #8-11 on
http://www.groomlakelabs.com/granda...creen-HowTo.txt
then

1) vi /usr/src/linux/drivers/usb/input/touchkitusb.c
go to line 55
55:#define TOUCHKIT_GET_X(dat) (((dat)[3] << 7) | (dat)[4])
56:#define TOUCHKIT_GET_Y(dat) (((dat)[1] << 7) | (dat)[2])

and swap the X and the Y so it looks like this
#define TOUCHKIT_GET_Y(dat) (((dat)[3] << 7) | (dat)[4])
#define TOUCHKIT_GET_X(dat) (((dat)[1] << 7) | (dat)[2])

recompile the module or kernel which ever and load.
2) Put this in your X config

Section "InputDevice"
Identifier "touchscreen0"
Driver "evtouch"
Option "Device" "/dev/input/event2"
Option "DeviceName" "touchscreen"
Option "MinX" "49"
Option "MaxX" "1980"
Option "MinY" "100"
Option "MaxY" "1960"
Option "ScreenNumber" "1"
Option "DragTimer" "200"
Option "MoveLimit" "600"
Option "ReportingMode" "Raw"
EndSection
3) start X and it should work.
i have the screen Number on there because im running dual monitors, you might not need this

hope this helps

millec · 06-01-2004, 02:06 AM

FYI... these drivers also work with the xenarc monitors. I just got my serial xenarc monitor working under Gentoo tonight.

--Craig

htd · 06-06-2004, 05:38 AM

ismell: thanks for your patch info of the linux source.

I tried to fix it in evtouch X11-driver code (adding an option like InvY for mouse), i never thought of hacking the kernel driver directly, seems like i didn't see the forest because of all the trees