summaryrefslogtreecommitdiff
path: root/evtest-capture.txt
blob: 6c4e41011692039532f7902886579316d71c3427 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
EVTEST-CAPTURE(1)
=================

NAME
----

     evtest-capture - Input device event capture program

SYNOPSIS
--------
     evtest-capture "/dev/input/eventX" [evtest-capture.xml]

DESCRIPTION
-----------
evtest-capture captures the information and events from the input device
specified on the command line and writes it to the xml file given. If no
filename is given for the output file, evtest-capture.xml is chosen as
default.

evtest-capture needs to be able to read from the device; in most cases this means it
must be run as root.

Together with with evtest-create-device.xsl, a simple uinput-based software
input device can be created that replays the events as if the same input was
performed on the physical device. This can be useful to replicate bugs with
input devices in upper layers of the stack.

To convert evtest-capture.xml into such a uinput device, run:

     xsltproc evtest-create-device.xls evtest-capture.xml > mydevice.c
     gcc -o mydevice mydevice.c
     ./mydevice


DIAGNOSTICS
-----------
If evtest-capture does not see any events even though the device is being
used, the device may be grabbed by a process (EVIOCGRAB).  This is usually the
case when debugging a synaptics device from within X. VT switching to a TTY or
shutting down the X server terminates this grab and synaptics devices can be
debugged.

SEE ALSO
--------
evtest(1)

AUTHOR
------
evtest-capture was written by Peter Hutterer <peter.hutterer@redhat.com>.