Update to reflect sysctl changes in Synaptics Touchpad driver.

share/man/man4/pms.4

@@ -1,4 +1,4 @@
-.\" $NetBSD: pms.4,v 1.17 2004/12/28 21:08:17 wiz Exp $
+.\" $NetBSD: pms.4,v 1.18 2005/01/02 22:39:08 scw Exp $
 .\"
 .\" Copyright (c) 1993 Christopher G. Demetriou
 .\" All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd Exp>>
 .\"
-.Dd December 28, 2004
+.Dd January 2, 2005
 .Dt PMS 4
 .Os
 .Sh NAME
@@ -81,24 +81,63 @@ In addition, the
 .Nm
 driver supports the
 .Dq Synaptics
-pad.
+touchpad.
 The following
 .Xr sysctl 8
-variables control the pad's behavior:
+variables control the touchpad's behavior:
 .Bl -tag
-.It Dv hw.synaptics.emulate_mid
-Emulate the middle button by pressing both buttons (default 0).
-.It Dv hw.synaptics.slow_limit
-Distance in pixels that is considered to be a slow (high-res) move.
-(default 900)
-.It Dv hw.synaptics.tap_enable
-Enable tapping on the pad to behave like a mouse click (default 1).
-.It Dv hw.synaptics.tap_length
-Time in microseconds that the pad needs to be pressed to be considered a tap
-(default 200000).
-.It Dv hw.synaptics.tap_tolerance
-Tolerance in pixels we can move on the pad and still considered a tap
-(default 500).
+.It Dv hw.synaptics.up_down_emulation
+If the touchpad reports the existence of Up/Down buttons, this value
+determines if they should be reported as button 4 and 5 events or if
+they should be used to emulate some other event.
+When set to 0, report Up/Down events as buttons 4 and 5.
+When set to 1, the Up and Down buttons are both mapped to the middle button.
+When set to 2 (default), the Up and Down buttons are used for Z-axis
+emulation, which more closely resembles how mouse wheels operate.
+.It Dv hw.synaptics.up_down_motion_delta
+When the Up/Down buttons are used for Z-axis emulation, this value specifies
+the emulated delta-Z value per click.
+.It Dv hw.synaptics.gesture_move
+Gestures will not be recognised if the finger moves by more than this
+amount between taps.
+.It Dv hw.synaptics.gesture_length
+Gestures will not be recognised if the number of packets (at 80 packets
+per second) between taps exceeds this value.
+.It Dv hw.synaptics.edge_left
+.It Dv hw.synaptics.edge_right
+.It Dv hw.synaptics.edge_top
+.It Dv hw.synaptics.edge_bottom
+These values define a border around the touchpad which will be used for
+edge motion emulation during a drag gesture.
+If a drag gesture is in progress and the finger moves into this border,
+the driver will behave as if the finger continues to move in the same
+direction beyond the edge of the touchpad.
+.It Dv hw.synaptics.edge_motion_delta
+This specifies the pointer speed when edge motion is in effect.
+.It Dv hw.synaptics.finger_high
+The driver will ignore new finger events until the reported pressure exceeds 
+this value.
+.It Dv hw.synaptics.finger_low
+The driver will assume a finger remains on the touchpad until the
+reported pressure drops below this value.
+.It Dv hw.synaptics.two_fingers_emulation
+More recent touchpads can report the presence of more than one finger
+on the pad.
+This value determines how such events are used.
+If set to 0 (default), two-finger events are ignored.
+If set to 1, two-finger events generate a right button click.
+If set to 2, two-finger events generate a middle button click.
+.It Dv hw.synaptics.scale_x
+.It Dv hw.synaptics.scale_y
+Scale factor used to divide movement deltas derived from Synaptics
+coordinates (0-6143) to yield more reasonable values (default 16).
+.It Dv hw.synaptics.max_speed_x
+.It Dv hw.synaptics.max_speed_y
+Limits pointer rate of change (after scaling) per reported movement
+event (default 32).
+.It Dv hw.synaptics.movement_threshold
+Movements of less than this value (in Synaptics coordinates) are
+ignored (default 4).
 .El
 .Sh SEE ALSO
 .Xr pckbc 4 ,
@@ -116,7 +155,7 @@ Special thanks to Ray Trent, at Synaptics, who contributed valuable
 insight into how to identify bogus mouse data.
 The changes to add
 .Dq Synaptics
-pad support were by Ales Krenek and Kentaro A. Kurahone.
+pad support were by Ales Krenek, Kentaro A. Kurahone, and Steve C. Woodford.
 .Sh BUGS
 It is possible for the driver to mistakenly negotiate the non-scroll-wheel
 protocol, after which it is unlikely to recover until the device is closed