Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You're right, the RS232 interfaces are kind of dated - it's getting harder to walk into a store and buy a computer with a RS232 port on it at all, although there are some USB-to-RS232 converter cables available.
I just wanted to see if any forum members actually use touchscreens, and if so, for what? But it appears that either no one's doing it, or they don't want to talk about it!
I've got touchscreens on Dell POS systems working - those are 3M (formerly MIcrotouch) USB devices. I have a new project going using PartnerTech POS systems that have something called eGalax touch screens - also USB interface - which I haven't got working yet - but haven't tried real hard, since the primary app on those is keyboard and scanner driven...
3M actually has Linux drivers on their website for some RedHat and SuSE distros, which means they probably work for others, too.
eGalax actually ships Linux drivers on their CD (along with 37 flavors of WinDos), but they want XFree86 to install and the OS we're putting on them is SuSE 9.2, which is Xorg - that's the part I have to find a way around... most of the newer distros are Xorg. Hopefully, the drivers will work, but the rpm's won't install unless they see XFree86, and XFree86 won't install unless you override conflicts, which I haven't done because (a) it might screw up the Xorg and (b) the client isn't planning on using touchscreen anytime soon.
Hi - I have no experience with touchscreens. There are a few on the consumer market here. Standard-looking 15"/17" displays are about double the regular price without any indication of linux support.
There are also smaller units around 8" which I think may be based on the eGalax screens you mention. I am curious about the linux interface. There are separate VGA and USB connections, right? The USB interface is mentioned as being supported by the hiddev driver. My understanding is that if the device is picked up by hiddev then you only need a user-space driver to use it.
I found out about this when I experimentally plugged in a USB IR dongle, which triggered the hiddev driver. Since then the IR remote LIRC project has provided full support for this, which could be a model of how to use hiddev with other devices.
Originally posted by maroonbaboon Hi - I have no experience with touchscreens. There are a few on the consumer market here. Standard-looking 15"/17" displays are about double the regular price without any indication of linux support.
There are also smaller units around 8" which I think may be based on the eGalax screens you mention. I am curious about the linux interface. There are separate VGA and USB connections, right? The USB interface is mentioned as being supported by the hiddev driver. My understanding is that if the device is picked up by hiddev then you only need a user-space driver to use it.
I found out about this when I experimentally plugged in a USB IR dongle, which triggered the hiddev driver. Since then the IR remote LIRC project has provided full support for this, which could be a model of how to use hiddev with other devices.
Touchscreens come in the same sizes the visual screens do, they're add-ons to detect touch, that's all.
While there are a number of touchscreen manufacturers, the only ones I have any familiarity with at all are ELO, 3M (formerly MicroTouch, bought by 3M), and now eGalax.
ELO and 3M are used by a number of different monitor manufacturers to add touchscreen functionality to their monitors. Since I've only seen eGalax built into a POS system I'm working with right now, I don't know much about them.
There are at least two different mechanisms for detecting a touch (capacitive and resistive), and some different ports used for transmitting the information to the computer, including RS232 and USB, and others.
The particular system I'm seeing eGalax on has a 15" LCD screen, and it and the touchscreen are connected internally. This particular motherboard has two VGA ports, one internal and one external, and they can both be used at the same time, or either one can be turned off. I haven't got far enough with it to know if they can have different images.
Touchscreens are essentially mouse-like, in that they report motion, but they also report location. which the mouse does not, and they do not have buttons to click or a wheel to spin, so these latter functions have to be carried out by software (or firmware in special cases).
Basically, though, the purpose of a touchscreen is to provide a pointing method to replace the mouse.
Yes, a USB touchscreen "only needs a user-space driver", but... someone has to write that driver, so that when the thing's plugged in, the system can find the right driver and install it so it can act as another (or the only) mouse. To my simple understanding, what happens when you plug in a USB device for the first time, your computer's USB-detection software is alerted, and begins a dialog with the device, part of which includes the device giving the computer two four-digit numbers, which are its manufacturer ID number, and the device's ID number. The computer then scans its USB drivers for one that matches those two numbers. If there is such a driver, then it's the one; if not, the software tries to match it up according to what class (kind of a device) it is, and then it launches the installation process where you pick the right driver or an acceptable substitute, or tell it where to find the driver (or give up). Once one is installed, that's the one the software loads the next time it sees that device plugged in.
I'm hoping others will jump in with information and/or experiences (good and bad) with touchscreens...
Which one? What computer? Any particular application?
Well, I work for a company that is trying to put together kiosks for their sites, and I was asked to come up with a cheap solution (does management want any other?). Anyway, I have a DELL Optiplex GX270 with an ELO ET1525L touchscreen. As of this moment, the furthest I have gotten is to successfully load the elographics_drv module. It fails, however, because the touchscreen has a USB connection for the mouse input, and I get this after running startx:
Quote:
Originally Posted by longtex
(EE) xf86OpenSerial: Cannot open device /dev/usb/mouse1
BTW, I am running the latest Debian release with the KDE desktop manager.
I know that the system sees the USB input, because it reports a valid connection on device 00:1d.1-2. It also says "assigned address 3", which changes every time I pull the plug. In other words, on boot, it will assign address 1 to the input, then 2 if I pull it and plug it in again, etc. What remains constant is the device identifier.
*My* problem is trying to figure out how I can get the driver to recognize the USB connection. Even if I assumed that it would always be plugged into the same bus/port, I still don't know how to tell XF86Config which device the touchscreen input uses.
ELO is absolutely no help. They have a "public" driver that doesn't even load. My guess is that I would have to recompile the code on my machine. And, even then, I don't know that it would work without modification.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.