QtMoko v18 - based on 2.6.32

Thomas Otterbein th.otterbein at gmx.net
Mon Mar 8 18:04:21 CET 2010

Hi Radek,

> Hi Thomas,
> sure, i can modify xorg.conf. My configuration can be found in this
> document:
> http://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt
> But i dont understand where to put the "void".
In you case it would go into line 333:
 Driver          "mouse"
would be replaced with
 Driver          "void"

> Maybe i dont understand it correctly, but i thought that touchscreen is
> different from mouse and should not appear in /dev/input/mice because it
> generates absolute screen coordinates while mouse generates relative
> coordinates. But that is just my impression, i havent read any docs about
> it yet :)
I'm also not a real expert on Touchscreen but until now I was responsible to 
make 4 different Touchscreens from 3 different vendors work on our embeded 
Debian system. It all comes to a point where the device is supported by the 
kernel, either by default (maybe 2.6.32 is such a case for the ts in the 
neo?), by external (kernel-)modules or by some service started during boot. 
All this leads to X detecting the Touchscreen as a HID (Human Interface Device 
(== keyboard, mouse, touchpad, tablet, etc.). 

Nowadays the less you specify the more X detects itself and usually makes 
perfect use of it. Typical you enter either /dev/input/mice or you leave the 
option out and the later will become the default.
Bus this causes trouble, at least with any touchscreen I had to configure until 
now. You have to be more precise about what device is referenced on what 
input. To do this you have to set Option "Device" for the mouse and/or for the 

Here are two typical configuration we use at our machines:

1. No mouse, Touchscreen replaces the mouse 
Section "InputDevice"
        Identifier "Configured Mouse"
        Driver "void"

Section "InputDevice"
  Identifier "elo"
  Driver "elo"
  Option "Device" "/dev/input/elo"
  Option "SendCoreEvents" "true"

2. Mouse and Touchscreen in paralel
Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option      "Device" "/dev/input/mouse1"
Section "InputDevice"
        Identifier "Touchscreen0"
        Driver "gentouch"
        Option "Device" "/dev/input/mouse2"

Anyway, the NEO will usually not have a mouse attached. I'm therefore not 
exactly sure what to do on the neo. My first guess would be to check out the 
/dev/input directory, see if there there are multiple mice listed 
(mouse0...mouseN) or if another device is present indicating the Touchscreen. 
If you find such a device you could simply try to add "Option "Device" 
"/dev/input/mouseX" to the InputDevice-Section. If that is not enough, play

Hope my lengthy explanation is not complete bullshit... ;-)


> Regards
> Radek
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community

More information about the community mailing list