Node:XFree 3.3,
Next:XFree 4.0,
Previous:XFree Configuration,
Up:XFree Configuration
XFree 3.3
In order to use a Gunze device with XFree 3.3 you need to add the
following two sections to your XF86Config
(the example below shows
all the options available for the module, but most of them are
optional, see below for details):
Section "module"
Load "xf86Gunze.so"
EndSection
Section "Xinput"
Subsection "GunzeTS"
DeviceName "touchscreen"
Port "/dev/ttyS0"
DeviceType Serial
Speed 9600
CalibrationFile "/etc/gunzets.calib"
Smoothness 9
TappingDelay 0
DebugLevel 0
#Res12Bit
AlwaysCore
EndSubSection
EndSection
The meaning of the individual options is the following:
DeviceName "touchscreen"
-
The device name is an identifier string chosen by the user.
It is mandatory.
Port "/dev/ttyS0"
-
The hardware channel used to read input data. The line is
mandatory. It can be a serial port, a PS/2 port (
/dev/psaux
)
or the USB entry point (/dev/gunzets
).
DeviceType Serial
-
Optional specification of the device type. It is used to
select the protocol used by the port. Possible values are
(case-insensitive): "serial", "ps2" (or "ps/2") and "usb". If
the information is not present in the configuration file, the
file name is used to guess the device type. Such guess will
work under Linux but may fail under other operating systems.
Speed 9600
-
Speed of the serial connection. Only used for serial devices,
the value defaults to 9600. Only valid values are 9600 and
19200.
CalibrationFile "/etc/gunzets.calib"
-
Optional specification of the calibration file. The default is
/etc/gunzets.calib
as shown. The format of the calibration
file is specified later in this documents.
Smoothness 9
-
The smoothness value is used to smooth out movements. It is
only meaningful for motion and drag events. Allowed values are
in the range 0 to 50. If you want to do handwriting, you'll need
to disable smoothness processing (i.e., set it to 0).
TappingDelay 0
-
Optional selection of tapping mode.
By default (tapping delay set to 0), any touch
event is reported as a button press. In tapping mode the first
touch event is used to move the pointer, and button press is
only reported when the user taps on the device. If the delay,
measured in milliseconds, between pen-up and pen-down is greater
than the selected value, the pen-down even is considered motion.
I personally
prefer tapping mode when testing the device, as it allows me
to use the common point-and-click semantics instead of
click-only; this is especially true if your touchscreen is not
placed over the image but in side of it (as you guess, I do that).
DebugLevel 0
-
Any debug level greater than 0 tells the driver to spit
informative messages. The greater the number, the higher the
message rate. Messages go to the usual X error channel
(stderr, normally connected to the text console used to fire
X).
Res12Bit
-
The boolean option states whether your panel
reports data with 12 bits of resolution (i.e., as numbers
in the 0-4095 range). The default, when no option is
specified, is 10 bits (0-1023).
12-bit support is implemented by discarding the lowest two bits,
and has been contributed by Atsushi Nemoto.
AlwaysCore
-
The input device is a "core" input device (like the main
pointer device - the mouse or equivalent). If the directive
is not specified, the touch screen acts as an auxiliary input
device, and applications may individually request to use it.