1GPM-TYPES(7) Miscellaneous Information Manual GPM-TYPES(7)
2
6 This manual page describes what pointer types (mice, tablets, etc) are
7 currently managed by gpm.
8 The information below is extracted from the texinfo file, which is the
9 preferred source of information.
10
12 This manpage describes the various pointer types currently available in
13 gpm. If you look at the source code, you'll find that pointer-specific
14 code is confined to mice.c (while it used to only include mouse
15 decoders, gpm now supports tablets and touchscreens as well).
16 The mouse type is specified on command line with the -t option. The
19 option takes an argument, which represents the name of a mouse type.
20 Each type can be associated to different names. For old mouse types,
21 one name is the old selection-compatible name, and another is the XFree
22 name. After version 1.18.1 of gpm, the number of synonyms was made
23 arbitrary and the actual name being used is made available to the func‐
24 tion responsible for mouse initialization. Therefore it is possible for
25 a mouse decoder to behave slightly differently according to the name
26 being used for the device (if this feature was already present, we
27 wouldn't have for example ms+ and ms+lr as different mouse types).
28 The initialization procedure of each mouse type can also receive extra
31 option, by means of the -o command line option. Since interpretation of
32 the option string is decoder-specific, the allowed options are
33 described in association to each mouse type. When no description of
34 option strings is provided, that means the option string is unused for
35 that mouse type and specifying one generates an error. When the docu‐
36 ment refer to ``standard serial options'' it means that one of -o dtr,
37 -o rts, -o both can be specified to toggle the control lines of the
38 serial port.
39 The following mouse type are corrently recognized:
42 bare Microsoft
44 The Microsoft protocol, without any extension. It only reports
45 two buttons. If your device has three, you should either try
46 running the mman decoder or msc. In the latter case, you need to
47 tell the mouse to talk msc protocol by toggling the DTR and RTS
48 lines (with one of -o drt, -o rts or -o both) or invoking gpm -t
49 msc while keeping the middle button pressed. Very annoying,
50 indeed. This mouse decoder accepts standard serial options,
51 although they should not be needed.
52 ms This is the original Microsoft protocol, with a middle-button
54 extension. Some old two-button devices send some spurious pack‐
55 ets which can be misunderstood as middle-button events. If this
56 is your case, use the bare mouse type. Some new two-button
57 devices are ``plug and play'', and they don't play fair at all;
58 in this case try -t pnp. Many (most) three-button devices that
59 use the microsoft protocol fail to report some middle-button
60 events during mouse motion. Since the protocol does not distin‐
61 guish between the middle button going up and the middle button
62 going down it would be liable to get out of step, so this
63 decoder declares the middle button to be up whenever the mouse
64 moves. This prevents dragging with the middle button, so you
65 should probably use -t ms+lr instead of this decoder, especially
66 if you want to use X. This mouse decoder accepts standard
67 serial options, although they should not be needed.
68 ms+ This is the same as -t ms except that the middle button is not
70 reset during mouse motion. So you can drag with the middle but‐
71 ton. However, if your mouse exhibits the usual buggy behaviour
72 the decoder is likely to get out of step with reality, thinking
73 the middle button is up when it's down and vice versa. You
74 should probably use -t ms+lr instead of this decoder. This
75 mouse decoder accepts standard serial options, although they
76 should not be needed.
77 ms+lr This is the same as -t ms+ except that there is an additional
79 facility to reset the state of the middle button by pressing the
80 other two buttons together. Do this when the decoder gets into a
81 confused state where it thinks the middle button is up when it's
82 down and vice versa. (If you get sick of having to do this,
83 please don't blame gpm; blame your buggy mouse! Note that most
84 three-button mice that do the microsoft protocol can be made to
85 do the MouseSystems protocol instead. The ``3 Button Serial
86 Mouse mini-HOWTO'' has information about this.) This mouse
87 decoder accepts standard serial options, although they should
88 not be needed.
89 msc MouseSystems
92 This is the standard protocol for three-button serial devices.
93 Some of such devices only enter MouseSystem mode if the RTS, DTR
94 or both lines are pushed low. Thus, you may try -t msc associ‐
95 ated with -o rts, -o dtr or -o both.
96 mman Mouseman
99 The protocol used by the new Logitech devices with three but‐
100 tons. It is backward compatible with the Microsoft protocol, so
101 if your mouse has three buttons and works with -t ms or similar
102 decoders you may try -t mman instead to use the middle button.
103 This mouse decoder accepts standard serial options, although
104 they should not be needed.
105 sun The protocol used on Sparc computers and a few others. This
108 mouse decoder accepts standard serial options, although they
109 should not be needed.
110 mm MMSeries
113 Title says it all. This mouse decoder accepts standard serial
114 options, although they should not be needed.
115 logi Logitech
118 This is the protocol used by old serial Logitech mice.
119 bm BusMouse
122 Some bus devices use this protocol, including those produced by
123 Logitech.
124 ps2 PS/2
127 The protocol used by most busmice.
128 ncr This `type' is able to decode the pointing pen found on some
131 laptops (the NCR 3125 pen)
132 wacom The protocol used by the Wacom tablet. Since version 1.18.1 we
135 have a new Wacom decoder, as the old one was not working with
136 new tablets. This decoder was tested with Ultrapad, PenPartner,
137 and Graphire tablets. Options: -o relative (default) for rela‐
138 tive mode, -o absolute for absolute mode.
139 genitizer
142 The This mouse decoder accepts standard serial options, although
143 they should not be needed.
144 logim Used to turn Logitech mice into Mouse-Systems-Compatible. Obvi‐
147 ously, it only works with some of the Logitech mice.
148 pnp This decoder works with the new mice produces by our friend
151 Bill, and maybe with the old ones as well. The Pnp protocol is
152 hardwired at 1200 baud and is upset by normal initialization, so
153 this is a -t bare decoder with no initialization at all. This
154 mouse decoder accepts standard serial options, although they
155 should not be needed.
156 ms3 A decoder for the new serial IntelliMouse devices, the ones with
159 three buttons and a protocol incompatible with older ones. The
160 wheel is currently unused.
161 imps2 ``IntelliMouse'' on the ps/2 port. This type can also be used
164 for a generic 2-button ps/2 mouse too, since it will auto-detect
165 the type.
166 netmouse
169 Decodes the ``Genius NetMouse'' type of devices on the ps/2
170 port. For serial ``Netmouse'' devices, use the ``ms3'' decoder.
171 cal A decoder of the ``Calcomp UltraSlate device.
175 calr Same as above, but in relative mode.
178 twid Support for the twiddler keyboard. As of gpm-1.14 this decoder
181 includes a char generator for the text console, but doesn't yet
182 support X keycodes. If used with -R, gpm will anyway repeat
183 mouse events to the X server. More information about twiddler
184 support can be found in README.twiddler, in the gpm distribu‐
185 tion.
186 syn synaptics
189 A decoder for the Synaptics TouchPad connected to the serial
190 port. This mouse decoder accepts standard serial options,
191 although they should not be needed.
192 synps2 synaptics_ps2
195 Same as above, but for the devices attached to the ps2 port.
196 brw A decoder for the Fellowes Browser, a device with 4 buttons and
199 a wheel. This mouse decoder accepts standard serial options,
200 although they should not be needed.
201 js Joystick
204 This mouse type uses the joystick device to generate mouse
205 events. It is only available if the header linux/joystick.h is
206 found at compile time. The header (and the device as well) has
207 been introduced only during 2.1 development, and is not present
208 in version 2.0 of the kernel.
209 summa This is a decode for the Symmagraphics of Genius tablet, run in
212 absolute mode. A repeater is associated to this decoder, so it
213 can -R summa can be used to generate X events even for other
214 absolute-pointing devices, like touchscreens. To use the
215 repeated data from X, you need a modified xf86Summa.o module.
216 mtouch A decoder for the MicroTouch touch screen. Please refer to the
219 file README.microtouch in the source tree of gpm for further
220 information. In the near future, anyways, I plan to fold back to
221 this documentation the content of that file.
222 gunze A decoder for the gunze touch screen. Please refer to the file
225 README.gunze in the source tree of gpm for further information.
226 In the near future, anyways, I plan to fold back to this docu‐
227 mentation the content of that file. The decoder accepts the fol‐
228 lowing options: smooth=, debounce=. An higher smoothness results
229 in slower motion as well; a smaller smoothness gives faster
230 motion but, obviously, less smooth. The default smoothness is
231 9. The debounce time is express in milliseconds and is the mini‐
232 mum duration of an up-down event to be taken as a tap. Smaller
233 bounces are ignored.
234 acecad The Acecad tablet in absolute mode.
237 wp wizardpad
240 Genius WizardPad tablet
241
246 src/mice.c The source file for pointer decoders
247
250 gpm(8) The General Purpose Mouse server
251 The info file about `gpm', which gives more complete information and
253 explains how to write a gpm client.
2544th Berkeley Distribution July 2000 GPM-TYPES(7)