README revision 302b15bd 
1Synaptics touchpad driver for X.Org
2-----------------------------------
3
4FAQ
5---
6
7* Is this free software?
8
9    Yes, the source code is released under the MIT license.
10
11* When will the driver be included in the XOrg distribution?
12
13    It is already.
14
15* How do I use this driver with Linux kernel 2.6.x?
16
17    You need to have the "evdev" driver loaded or compiled into the
18    kernel (CONFIG_INPUT_EVDEV). Set the "Protocol" parameter in the X
19    configuration file to "auto-dev". Also, if you set the "Device"
20    parameter to "/dev/psaux", the same X configuration file should
21    work for a 2.4.x kernel.
22
23    When configuring the kernel, enable PS/2 mouse support
24    (CONFIG_MOUSE_PS2).
25
26* It still doesn't work with a 2.6 kernel.
27
28    Some distributions come with an incomplete /dev directory. The
29    driver needs the /dev/input/eventX device nodes. Try to create
30    them manually if they don't exist already. (Look at
31    /proc/bus/input/devices to figure out how many nodes you need.)
32
33	     # mknod /dev/input/event0 c 13 64
34	     # mknod /dev/input/event1 c 13 65
35	     # mknod /dev/input/event2 c 13 66
36	     ...
37
38* How can I configure tap-to-click behavior?
39
40    If you set MaxTapTime=0 in the X config file then the touchpad
41    will not use tapping at all, i.e. touching/tapping will not be
42    taken as a mouse click.
43
44    If, instead, you set MaxTapMove=0 in the X config file, then the
45    touchpad will not use tapping for a single finger tap (left mouse
46    button click) but will for the two and three finger tap (middle
47    and right button click).
48
49* Why did tap-to-click stop working after I upgraded from an old version?
50
51    Time is now measured in milliseconds instead of "number of
52    packets". In practice, this means that if you are upgrading from
53    an old version, you need to change MaxTapTime and
54    EmulateMidButtonTime to make "tap to click" work. Good values are
55    180 and 75 respectively.
56
57* Gnome scrollbars scroll too much when using tap-to-click. Why?
58
59    The ClickTime parameter is probably too big. Try setting it to
60    100. Gnome scrollbars use auto repeat, ie if you press the left
61    mouse button and keep it pressed, the scroll bar will move until
62    you release the button. This will lead to problems if the tap time
63    is longer than the delay before auto repeat starts.
64
65* Vertical and horizontal scrolling events are mixed up. How come?
66
67    Probably because some X startup/login script uses xmodmap to remap
68    the mouse buttons. Correct settings for the touchpad are:
69
70	xmodmap -e 'pointer = 1 2 3 4 5 6 7'
71
72    You can check the current settings by running:
73
74	xmodmap -pp
75
76* Horizontal scrolling doesn't work in some programs. Is it a driver
77  bug?
78
79    No, probably not. Support for horizontal scroll events must be
80    handled by the application programs. Not all programs do that
81    yet. Ask the authors of the application in question to implement
82    support for horizontal scroll events.
83
84    You can use the "xev" program to check if the synaptics driver
85    generates the horizontal scroll events.
86
87    If you are having problems with Mozilla, try this link:
88
89	http://lists.debian.org/debian-laptop/2004/08/msg00167.html
90
91* Can the driver be used together with gpm?
92
93    No, not reliably, if you are using a 2.4.x kernel. The gpm driver
94    and the X driver both try to read data from the touchpad, and if
95    they try to read at the same time, both drivers see incomplete
96    data and don't know how to interpret it.
97
98    If you are running a 2.6.x kernel though, there should be no
99    conflict, because the kernel driver will make sure both user space
100    drivers receive all events from the touchpad.
101
102* Can I use this driver with an ALPS Glidepoint device?
103
104    Yes, see the README.alps file for more information.
105
106* The driver says "reset failed" and the touchpad doesn't work. What
107  can I do?
108
109    This problem has been reported for some Compaq models. It's
110    currently not known why it happens, but removing the reset command
111    from the driver appears to make it work. If you use a 2.4 linux
112    kernel, replace the contents of the ps2_synaptics_reset() function
113    in ps2comm.c with a "return TRUE;" statement. If you use a 2.6
114    linux kernel, remove the while loop in synaptics_query_hardware()
115    in the file drivers/input/mouse/synaptics.c in the linux kernel
116    source code.
117
118
119Authors
120-------
121
122Many people have contributed to this driver. Look at the top of
123synaptics.c and ps2comm.c for details.
124
125The current maintainer is X.org development team <xorg-devel@lists.x.org>.
126
127
128Contacts
129--------
130All questions regarding this software should be directed at the
131Xorg mailing list:
132
133        http://lists.freedesktop.org/mailman/listinfo/xorg
134
135Please submit bug reports to the Xorg bugzilla:
136
137        https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
138
139The master development code repository can be found at:
140
141        git://anongit.freedesktop.org/git/xorg/driver/xf86-input-synaptics
142
143        http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics
144
145For patch submission instructions, see:
146
147	http://www.x.org/wiki/Development/Documentation/SubmittingPatches
148
149For more information on the git code manager, see:
150
151        http://wiki.x.org/wiki/GitPage
152
153