Asciidoc manpage instead of nroff, add manpage for evtest-capture.

asciidoc has the huge advantage of being human-readable. The generation of
the actual manpage is somewhat complicated, but one can link straight to the
evtest.txt file in cgit instead of being blamed for bleeding eyes when users
look at nroff source.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

1 files changed, 46 insertions, 0 deletions

diff --git a/evtest.txt b/evtest.txt
new file mode 100644
index 0000000..685a4de
--- /dev/null
+++ b/evtest.txt
@@ -0,0 +1,46 @@
+EVTEST(1)
+=========
+
+NAME
+----
+
+     evtest - Input device event monitor
+
+SYNOPSIS
+--------
+     evtest "/dev/input/eventX"
+
+DESCRIPTION
+-----------
+evtest displays information on the input device specified on the command
+line, including all the events supported by the device. It then monitors the
+device and displays all the events layer events generated.
+
+evtest needs to be able to read from the device; in most cases this means it
+must be run as root.
+
+evtest is commonly used to debug issues with input devices in X.Org. The
+output of evtest shows the information presented by the kernel; based on
+this information it can be determined whether a bug may be a kernel or an
+X.Org issue.
+
+DIAGNOSTICS
+-----------
+If evtest does not show 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
+--------
+inputattach(1)
+
+AUTHOR
+------
+evtest was written by Vojtech Pavlik <vojtech@suse.cz>.
+
+This manual page was written by Stephen Kitt <steve@sk2.org>, based on that
+present in the lineakd package, for the Debian GNU/Linux system (but may be
+used by others).
+