1WDAEMON(1) [FIXME: manual] WDAEMON(1)
2
6 wdaemon - Wacom tablet hotplugging emulator
7
9 wdaemon [options]
10
12 wdaemon is an application to abstract Wacom tablet hotplugging. wdaemon
13 creates virtual input devices using the uinput kernel module and makes
14 them available while at run time keeps looking for specified devices to
15 be plugged in.
16 Instead of looking for the actual device, the X server is configured to
18 look for the emulated device. wdaemon will provide the an identical
19 device description, allowing the server to initialize properly. Once
20 the physical device is plugged in, wdaemon will forward all events
21 through the emulated device and thus to the X server.
22 For easier recognition, the device name is prefixed with the string
24 "wdaemon". This can be disabled at configure time.
25
27 -h
28 Print a help message
29 -p
31 Path to the device file to monitor, load to or extract
32 -t
34 Device type, use -w to get a list
35 -c file
37 Use <file> as configuration file.
38 -d N
40 Enable debug messages up to level N
41 -o file
43 Redirect debug messages to file
44 -f
46 Fork on start and enter in daemon mode
47 -w
49 Get a list of supported devices and their numbers
50 -a
52 Autoconfigure, generate a configuration file based on currently
53 plugged in tablets
54 -l file
56 Load a device description from file
57 -x file
59 Extract a device description into file
60 -s
62 Use syslog for debug messages (conflicts with -o)
63 -v
65 Print version number
66
68 wdaemon requires configuration in the udev(7) system setup, the
69 xorg.conf(5) configuration files and finally wdaemon itself.
70 UDEV CONFIGURATION
72 wdaemon requires a tablet to have a predictable unique device file.
73 This is usually accomplished through udev rules. For example, on modern
74 systems, a tablet may appear as
75 /dev/input/by-id/usb-Tablet_PTZ-630-event-mouse
77 which will point to the event device of a Intuos3 6x8. The wdaemon
79 package provides udev rules to create symlinks to known tablet models
80 in the form of
81 /dev/input/wacomX,
83 /dev/input/wacom-tablets/wacom-<model>-tabletX and
84 /dev/input/wacom-tablets/wacom-<model>-tablet-<phys path>
85 The last link provides unique type per USB port. Once a tablet reliably
87 appears at a given device path, wdaemon may be configured to use it.
88 The second step consists in creating a persistent name for uinput
90 devices created by wdaemon, so you can configure your xorg.conf right.
91 An example udev rule to do this:
92 KERNEL="event*", PROGRAM="/lib/udev/wdaemon_is_uinput.sh", \
94 RESULT="056a-0000", \
95 SYMLINK="input/uinput-devices/uinput-wacom-penpartner-tablet%e"
96 This will create a symbolic link for penpartner tablets. Notice it
98 needs wdaemon_is_uinput.sh script (included in this package). Also
99 included in this package, 11-uinput-wacom.rules has these rules done
100 for most tablets. With the rule in place, a wdaemon-created device will
101 have predictable device files. This makes xorg.conf configuration
102 simpler.
103 XORG.CONF CONFIGURATION
105 The X server should be configured to use the devices by wdaemon instead
106 of the actual physical devices. An xorg.conf(5) section may look like
107 this:
108 Section "InputDevice"
110 Identifier "cursor"
111 Driver "wacom"
112 Option "Type" "cursor"
113 Option "Device" "/dev/input/uinput-devices/uinput-wacom-intuos3-6x8-tablet"
114 Option "Mode" "relative"
115 Option "Tilt" "on"
116 Option "Threshold" "20"
117 Option "Suppress" "6"
118 Option "USB" "On"
119 EndSection
120 Note that if the X server is configured to hotplug devices, it must
122 ignore physical devices in use by wdaemon. Example xorg.conf.d(5) and
123 fdi files are provided with this package.
124 WDAEMON CONFIGURATION
126 Now wdaemon must be configured to monitor the physical tablet and
127 create matching uinput device. A /etc/wdaemon.conf for two devices may
128 look like this:
129 device = 36,/dev/input/wacom-tablets/intuos3-6x8-tablet
131 device = 6,/dev/input/wacom-tablets/graphire4-4x5-tablet
132 Notice the spaces. The wdaemon parser is very rudimentary at this point
134 and can get easily confused. The device types 36 and 6 can be
135 determined by running
136 wdaemon -w
138 When wdaemon is started, it will create devices of the types specified
140 in the wdaemon.conf configuration file and monitor the device path.
141 Whenever the physical tablet appears, wdaemon will forward events from
142 the device to the uinput device.
143 If the device type is unknown to wdaemon, see SAVING AND LOADING
145 DEVICES below.
146 AUTO-CONFIGURATION
148 The -a option was added in 0.14 to generate a wdaemon.conf based on the
149 currently plugged-in tablets. First, plug in all tablets that should be
150 emulated by wdaemon in the future. Then run
151 wdaemon -a
153 This command prints a configuration file that can then be used for
155 wdaemon.
156 Auto-configuration only works with device types known to wdaemon.
158 SAVING AND LOADING DEVICES
160 wdaemon has the device descriptions for a number of devices built-in.
161 For devices that are unknown to wdaemon the device description must be
162 gathered from the physical device and loaded on startup.
163 A device description may be extracted with the -x option:
165 wdaemon -p /dev/input/by-id/usb-Tablet_PTZ-630-event-mouse -x Intuos3_6x8.desc
167 The resulting device file is a description of the device currently
169 available as /dev/input/event12. The description may be loaded again
170 with the -l option:
171 wdaemon -p /dev/input/by-id/usb-Tablet_PTZ-630-event-mouse -l Intuos3_6x8.desc
173 wdaemon will initialize a device based on the description file and
175 forward events from the specified device path.
176
178 The configuration format supports the following keywords:
179 debug = <debuglevel>
181 Where debuglevel is an integer equal or larger than 0.
183 device = <type>,<path>
185 Where type is an integer representing the device type and path the path
187 to the device to monitor.
188 description = <desc>,<path>
190 Where desc is the path to a device file description and path the path
192 to the device to monitor.
193 wdaemon’s parser is simple and the spaces in the configuration file
195 must be exactly as above. That is, no space at the beginning of the
196 line, a space before and after the = sign and no spaces elsewhere.
197
199 UINPUT_DEVICE
200 Specifies the path to the uinput kernel device.
201
203 0.17
204
206 This man page was written by Peter Hutterer
207 <peter.hutterer@redhat.com[1]> based on the README provided by wdaemon.
208
210 xorg.conf(5), wacom(4)
211
213 1. peter.hutterer@redhat.com
214 mailto:peter.hutterer@redhat.com
215[FIXME: source] 02/21/2013 WDAEMON(1)