On Thu, Oct 27, 2011 at 10:01 AM, Cedric Sodhi <man...@gmx.net> wrote: > Thanks Chris for replying, I knew I could rely on you guys :) > > On Thu, Oct 27, 2011 at 09:07:37AM -0500, Chris Bagwell wrote: >> On Thu, Oct 27, 2011 at 7:25 AM, Cedric Sodhi <man...@gmx.net> wrote: >> > I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a >> > WACOM Digitizer (Stylus & Erasor). I did not know that. I thought it was >> > all WACOM, now I'm faced with the prolem that I have no driver for the >> > eGalax touchpad, I hope you can help, since I don't know any other >> > people on the internet who deal with these kind of things. >> >> When you say "eGalax touchpad", you really mean touchscreen, right? >> If your hardware is being detected as a touchpad then thats your >> problem right there. Touchpad == relative mouse-like device handled >> by xf86-input-synaptics. Touchscreen == absolute mode touchscreen >> like device handled by xf86-input-evdev. > > Urgh, I of course meant TOUCHSCREEN, *not* touchpad. > >> > I get an event node in /dev/input, do you have any suggestions how to >> > make the touchscreen work? In the worst case that there really is no >> > driver and I (god beware, I will rather return the tablet) would have to >> > write my own, is there anything in Wacom that can be reused? >> >> Based on your description of hardware, you should see two /dev/inputs. >> One for the wacom and one for the eGalax. Are you seeing one >> specifically for eGalax in your dmesg output? We need to make sure >> your really getting a kernel driver loaded for the eGalax part. >> >> I find the "evtest" program extremely useful in verifying the kernel >> side is working and which /dev/input goes to which hardware. You can >> google it for more info. >> >> What kernel driver is being used by this hardware? I hope its not a >> binary blob because then your pretty much on your own getting it >> working. > > Ok, I guess I should have been a bit more verbose. I'm fighting with > sysfs here, and given that I'm not very familar with it, forgive me my > ignorance. > > Kernel Config I: > > HID_MULTITOUCH=M > USB_HIDDEV=Y > TOUCHSCREEN_USB_COMPOSITE=N > > I do have three mice input devices from udev: > > mouse0: The Wacom 056a:0090 > mouse1: The eGalax 0eef:a001 > mouse2: Some attached USB mouse > > As for mouse1, udevadm points me to input7 in sysfs, and I do get > response (with xxd), but no hid_multitouch.ko is loaded (so apparently > it is not the reason for existance). Maybe you can extract information > from the modalias > > input: b0003v056Ap0090e0206-e0,1,3,k140,141,14A,14B,14C,ra0,1,18,mlsfw > > Kernel Config II > > HID_MULTITOUCH=N > USB_HIDDEV=Y > TOUCHSCREEN_USB_COMPOSITE=M > TOUCHSCREEN_USB_EGALAX=Y > > Dito. Module not loaded either, but I got the 3 input devices.
Still can't tell from all that what driver is being used. Please show output from "dmesg" where eGalax line is mentioned (and a few lines before and after it). It will prove what driver is being used. Any special reason you have HID_MULTITOUCH=N? In newer kernels, for hardware that supports it, its a better driver then the hid-egalax/hid-mosart/hid-etc drivers. Also, what kernel version are you using? > >> > I'm generally wondering why there is not ONE UNIFIED X >> > tablet/touchscreen driver for all touchscreens there are. They all have >> > mostly the same capabilities. Why is there no unified common interface >> > on the kernel level that exposes tablets through a unified interface to >> > the X server?! >> >> There is a unified X driver for generic touchscreen/mice/etc. Its >> called xf86-input-evdev. It all depends on the kernel driver used to >> which X driver gets loaded. We'd need that info to go any further. > > I tried evdev and it does not work (properly), see my mail to xorg-devel > for that. And it never will, I think, not for touchscreens (but I'd > welcome to be proven wrong). No, evdev is designed to work with touchscreens. Its usually the best choice for non-wacom touchscreens. You are hitting some other problem. sounds like in kernel driver. > > If you need any more infos, shoot, I'll readily trying everything you > suggest. > > PS: There is an opensource KO called "tkusb" provided by the producer of > the eGalax for kernels 2.6, but their readme leaves me unclear on > whether it is still current, what it requires, and so forth. I also > tried their Xorg module (which is said to be for 1.10 and is closed > source) and it loads without errors, but shows no response. (Just as a > sidenote) > > http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm Used to, this driver contained binary blobs and also required an xf86-input-egalax to work with it. I've not used it in maybe 3 years though with a now dead egalax touchscreen. Most egalax hardware is supported by standard linux kernel + standard xf86-input-evdev. Not sure of this exact hardware issue. I quickly found this bug report that says it is reporting itself as a touchpad which would explain why its not working correctly with xf86-input-evdev. It doesn't go into very much detail on the why its reporting that way or what kernel driver its using. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/854445 That is purely kernel side issue so thats were you want to concentrate. Chris > > Thank you > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
