| psm.4 (202386) | psm.4 (208027) |
|---|---|
| 1.\" 2.\" Copyright (c) 1997 3.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26.\" | 1.\" 2.\" Copyright (c) 1997 3.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26.\" |
| 27.\" $FreeBSD: head/share/man/man4/psm.4 202386 2010-01-15 16:01:22Z ru $ | 27.\" $FreeBSD: head/share/man/man4/psm.4 208027 2010-05-13 12:07:55Z uqs $ |
| 28.\" 29.Dd April 8, 2008 30.Dt PSM 4 31.Os 32.Sh NAME 33.Nm psm 34.Nd PS/2 mouse style pointing device driver 35.Sh SYNOPSIS --- 776 unchanged lines hidden (view full) --- 812Note that the pointing device will not be enabled until the 813.Nm 814driver is opened by the user program. 815.Pp 816The rest of the lines show the device ID code, the number of detected 817buttons and internal variables. 818.Pp 819At debug level 2, much more detailed information is logged. | 28.\" 29.Dd April 8, 2008 30.Dt PSM 4 31.Os 32.Sh NAME 33.Nm psm 34.Nd PS/2 mouse style pointing device driver 35.Sh SYNOPSIS --- 776 unchanged lines hidden (view full) --- 812Note that the pointing device will not be enabled until the 813.Nm 814driver is opened by the user program. 815.Pp 816The rest of the lines show the device ID code, the number of detected 817buttons and internal variables. 818.Pp 819At debug level 2, much more detailed information is logged. |
| 820.Sh CAVEATS 821Many pad devices behave as if the first (left) button were pressed if 822the user `taps' the surface of the pad. 823In contrast, some pad products, e.g.\& some versions of ALPS GlidePoint 824and Interlink VersaPad, treat the tapping action 825as fourth button events. 826.Pp 827It is reported that Interlink VersaPad requires both 828.Em HOOKRESUME 829and 830.Em INITAFTERSUSPEND 831flags in order to recover from suspended state. 832These flags are automatically set when VersaPad is detected by the 833.Nm 834driver. 835.Pp 836Some PS/2 mouse models from MouseSystems require to be put in the 837high resolution mode to work properly. 838Use the driver flag to 839set resolution. 840.Pp 841There is not a guaranteed way to re-synchronize with the first byte 842of the packet once we are out of synchronization with the data 843stream. 844However, if you are using the \fIXFree86\fP server and experiencing 845the problem, you may be able to make the X server synchronize with the mouse 846by switching away to a virtual terminal and getting back to the X server, 847unless the X server is accessing the mouse via 848.Xr moused 8 . 849Clicking any button without moving the mouse may also work. | |
| 850.Sh SEE ALSO 851.Xr ioctl 2 , 852.Xr syslog 3 , 853.Xr atkbdc 4 , 854.Xr mouse 4 , 855.Xr mse 4 , 856.Xr sysmouse 4 , 857.Xr moused 8 , --- 15 unchanged lines hidden (view full) --- 873.An Charles Hannum , 874.An Shoji Yuen 875and 876.An Kazutaka Yokota 877to name the few. 878.Pp 879This manual page was written by 880.An Kazutaka Yokota Aq yokota@FreeBSD.org . | 820.Sh SEE ALSO 821.Xr ioctl 2 , 822.Xr syslog 3 , 823.Xr atkbdc 4 , 824.Xr mouse 4 , 825.Xr mse 4 , 826.Xr sysmouse 4 , 827.Xr moused 8 , --- 15 unchanged lines hidden (view full) --- 843.An Charles Hannum , 844.An Shoji Yuen 845and 846.An Kazutaka Yokota 847to name the few. 848.Pp 849This manual page was written by 850.An Kazutaka Yokota Aq yokota@FreeBSD.org . |
| 851.Sh CAVEATS 852Many pad devices behave as if the first (left) button were pressed if 853the user `taps' the surface of the pad. 854In contrast, some pad products, e.g.\& some versions of ALPS GlidePoint 855and Interlink VersaPad, treat the tapping action 856as fourth button events. 857.Pp 858It is reported that Interlink VersaPad requires both 859.Em HOOKRESUME 860and 861.Em INITAFTERSUSPEND 862flags in order to recover from suspended state. 863These flags are automatically set when VersaPad is detected by the 864.Nm 865driver. 866.Pp 867Some PS/2 mouse models from MouseSystems require to be put in the 868high resolution mode to work properly. 869Use the driver flag to 870set resolution. 871.Pp 872There is not a guaranteed way to re-synchronize with the first byte 873of the packet once we are out of synchronization with the data 874stream. 875However, if you are using the \fIXFree86\fP server and experiencing 876the problem, you may be able to make the X server synchronize with the mouse 877by switching away to a virtual terminal and getting back to the X server, 878unless the X server is accessing the mouse via 879.Xr moused 8 . 880Clicking any button without moving the mouse may also work. |
|
| 881.Sh BUGS 882The ioctl command 883.Dv MOUSEIOCREAD 884has been removed. 885It was never functional anyway. 886.Pp 887Enabling the extended support for Synaptics touchpads has been reported to 888cause problems with responsivity on some (newer) models of Synaptics 889hardware, particularly those with guest devices. | 881.Sh BUGS 882The ioctl command 883.Dv MOUSEIOCREAD 884has been removed. 885It was never functional anyway. 886.Pp 887Enabling the extended support for Synaptics touchpads has been reported to 888cause problems with responsivity on some (newer) models of Synaptics 889hardware, particularly those with guest devices. |