Package: xserver-xorg-input-tslib
Version: 0.0.4-5
Given a touchscreen being configured in /etc/hal/fdi/policy as using the
xserver tslib input, it is not correctly added to the X server upon
connecting the touchscreen to a USB port. The kernel level driver
(usbtouchscreen) is correctly loaded, but the X input module is not
getting the device path and is defaulting to the compiled-in path of
"/dev/event0" (rather than the actual path of /dev/input/event[n] where
[n] depends upon what else is plugged in at the time).
Here is a log of the kernel messages and the X server messages upon
plugging in a touchscreen device:
usb 1-1.4.4: new full speed USB device using musb_hdrc and address
44
usb 1-1.4.4: configuration #1 chosen from 1
choice
input: eGalax Inc. USB TouchController
as /class/input/input41
input: USB HID v1.00 Pointer [eGalax Inc. USB TouchController] on
usb-musb_hdrc-1.4.4
(**) eGalax Inc. USB TouchController: always reports core
events
(**) Option "TslibDevice"
"/dev/event0"
ts_open failed
(device=/dev/event0)
(EE) PreInit returned NULL for "eGalax Inc. USB TouchController"
This has been seen on both an x86-32 PC running Lenny and an ARMEL
Beagleboard (also running lenny), so it would seem to be (somewhat)
independent of the platform architecture.
PC version data:
cat /proc/version
Linux version 2.6.26-1-686 (Debian 2.6.26-11) ([email protected]) (gcc
version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Nov 26
19:14:11 UTC 2008
cat /etc/debian_version
5.0
Beagleboard version data:
cat /proc/version
Linux version 2.6.27 (r...@beagleboard) (gcc version 4.3.2 (Debian
4.3.2-1.1) ) #2 Wed Jan 14 10:42:38 EST 2009
cat /etc/debian_version
5.0
For reference, the .fdi file is:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="input.product" contains="Touchscreen">
<merge key="input.x11_driver" type="string">tslib</merge>
<merge key="input.x11_options.MinX" type="string">2274</merge>
<merge key="input.x11_options.MaxX" type="string">13295</merge>
<merge key="input.x11_options.MinY" type="string">3500</merge>
<merge key="input.x11_options.MaxY" type="string">13000</merge>
<merge key="input.x11_options.DeviceName"
type="string">Microtouch</merge>
</match>
</device>
<device>
<match key="input.product" contains="eGalax">
<merge key="input.x11_driver" type="string">tslib</merge>
<merge key="input.x11_options.MinX" type="string">14200</merge>
<merge key="input.x11_options.MaxX" type="string">2160</merge>
<merge key="input.x11_options.MinY" type="string">2580</merge>
<merge key="input.x11_options.MaxY" type="string">13800</merge>
<merge key="input.x11_options.DeviceName"
type="string">eGalix</merge>
<merge key="input.x11_options.TsLibDevice"
type="copy_property">input.device</merge>
</match>
</device>
</deviceinfo>
(please forgive this unavoidable wart added by the corporate mail
servers: the intended distribution of this email is "anybody").
Notice: This e-mail is intended solely for use of the individual or entity to
which it is addressed and may contain information that is proprietary,
privileged, company confidential and/or exempt from disclosure under applicable
law. If the reader is not the intended recipient or agent responsible for
delivering the message to the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is strictly
prohibited. If this communication has been transmitted from a U.S. location it
may also contain data subject to the International Traffic in Arms Regulations
or U.S. Export Administration Regulations and cannot be disseminated,
distributed or copied to foreign nationals, residing in the U.S. or abroad,
without the prior approval of the U.S. Department of State or appropriate
export licensing authority. If you have received this communication in error,
please notify the sender by reply e-mail or collect telephone call and del
ete or destroy all copies of this e-mail message, any physical copies made of
this e-mail message and/or any file attachment(s).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
