Qtopia Core Pointer Handling

Specifying a Driver

Provided that the "pc" mouse driver is enabled, Qtopia Core will try to auto-detect the mouse device if it is one of the supported types on /dev/psaux or one of the /dev/ttyS? serial lines. If multiple mice are detected, all may be used simultaneously.

Note that Qtopia Core does not support auto-detection of touch panels in which case the driver must be specified explicitly to determine which device to use.

To manually specify which driver to use, set the QWS_MOUSE_PROTO environment variable. For example (if the current shell is bash, ksh, zsh or sh):

 export QWS_MOUSE_PROTO=<driver>[:<driver specific options>]

The valid values for the <driver> argument are MouseMan, IntelliMouse, Microsoft, VR41xx, LinuxTP, Yopy, Tslib and keys identifying custom drivers, and the driver specific options are typically a device, e.g., /dev/mouse for mouse devices and /dev/ts for touch panels.

Multiple mouse drivers can be specified in one go:

  export QWS_MOUSE_PROTO="<driver>[:<driver specific options>]
          <driver>[:<driver specific options>]
          <driver>[:<driver specific options>]"

Input will be read from all specified drivers.

Note that the Vr41xx driver also accepts two optional arguments: press=<value> defining a mouse click (the default value is 750) and filter=<value> specifying the length of the filter used to eliminate noise (the default length is 3). For example:

 export QWS_MOUSE_PROTO="Vr41xx:press=500:/dev/misc/ts"

 ./configure  -L <path to tslib library> -I <path to tslib headers>

  module_raw input
  module linear

 QWS_MOUSE_PROTO=IntelliMouse:/dev/input/mouse0}

 cat /dev/input/mouse0 | hexdump

 QWS_MOUSE_PROTO=IntelliMouse:/dev/input/mouse0

     chmod a+rw /dev/input/mouse0