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: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer as 11.\" the first lines of this file unmodified. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in the 14.\" documentation and/or other materials provided with the distribution. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 17.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 18.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 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: src/share/man/man4/psm.4,v 1.24.2.9 2002/12/29 16:35:38 schweikh Exp $ 28.\" $DragonFly: src/share/man/man4/psm.4,v 1.5 2006/05/26 19:39:39 swildner Exp $ 29.\" 30.Dd April 1, 2000 31.Dt PSM 4 32.Os 33.Sh NAME 34.Nm psm 35.Nd PS/2 mouse style pointing device driver 36.Sh SYNOPSIS 37.Cd "options KBD_RESETDELAY=N" 38.Cd "options KBD_MAXWAIT=N" 39.Cd "options PSM_DEBUG=N" 40.Cd "options KBDIO_DEBUG=N" 41.Cd "device psm0 at atkbdc? irq 12" 42.Sh DESCRIPTION 43The 44.Nm 45driver provides support for the PS/2 mouse style pointing device. 46Currently there can be only one 47.Nm 48device node in the system. 49As the PS/2 mouse port is located 50at the auxiliary port of the keyboard controller, 51the keyboard controller driver, 52.Nm atkbdc , 53must also be configured in the kernel. 54Note that there is currently no provision of changing the 55.Em irq 56number. 57.Pp 58Basic PS/2 style pointing device has two or three buttons. 59Some devices may have a roller or a wheel and/or additional buttons. 60.Ss Device Resolution 61The PS/2 style pointing device usually has several grades of resolution, 62that is, sensitivity of movement. 63They are typically 25, 50, 100 and 200 64pulse per inch. 65Some devices may have finer resolution. 66The current resolution can be changed at runtime. 67The 68.Nm 69driver allows the user to initially set the resolution 70via the driver flag 71(see 72.Sx "DRIVER CONFIGURATION" ) 73or change it later via the 74.Xr ioctl 2 75command 76.Dv MOUSE_SETMODE 77(see 78.Sx IOCTLS ) . 79.Ss Report Rate 80Frequency, or report rate, at which the device sends movement 81and button state reports to the host system is also configurable. 82The PS/2 style pointing device typically supports 10, 20, 40, 60, 80, 100 83and 200 reports per second. 8460 or 100 appears to be the default value for many devices. 85Note that when there is no movement and no button has changed its state, 86the device won't send anything to the host system. 87The report rate can be changed via an ioctl call. 88.Ss Operation Levels 89The 90.Nm 91driver has three levels of operation. 92The current operation level can be set via an ioctl call. 93.Pp 94At the level zero the basic support is provided; the device driver will report 95horizontal and vertical movement of the attached device 96and state of up to three buttons. 97The movement and status are encoded in a series of fixed-length data packets 98(see 99.Sx "Data Packet Format" ) . 100This is the default level of operation and the driver is initially 101at this level when opened by the user program. 102.Pp 103The operation level one, the `extended' level, supports a roller (or wheel), 104if any, and up to 11 buttons. 105The movement of the roller is reported as movement along the Z axis. 1068 byte data packets are sent to the user program at this level. 107.Pp 108At the operation level two, data from the pointing device is passed to the 109user program as is. 110Modern PS/2 type pointing devices often use proprietary data format. 111Therefore, the user program is expected to have 112intimate knowledge about the format from a particular device when operating 113the driver at this level. 114This level is called `native' level. 115.Ss Data Packet Format 116Data packets read from the 117.Nm 118driver are formatted differently at each operation level. 119.Pp 120A data packet from the PS/2 mouse style pointing device 121is three bytes long at the operation level zero: 122.Pp 123.Bl -tag -width Byte_1 -compact 124.It Byte 1 125.Bl -tag -width bit_7 -compact 126.It bit 7 127One indicates overflow in the vertical movement count. 128.It bit 6 129One indicates overflow in the horizontal movement count. 130.It bit 5 131Set if the vertical movement count is negative. 132.It bit 4 133Set if the horizontal movement count is negative. 134.It bit 3 135Always one. 136.\" The ALPS GlidePoint clears this bit when the user `taps' the surface of 137.\" the pad, otherwise the bit is set. 138.\" Most, if not all, other devices always set this bit. 139.It bit 2 140Middle button status; set if pressed. 141For devices without the middle 142button, this bit is always zero. 143.It bit 1 144Right button status; set if pressed. 145.It bit 0 146Left button status; set if pressed. 147.El 148.It Byte 2 149Horizontal movement count in two's complement; 150-256 through 255. 151Note that the sign bit is in the first byte. 152.It Byte 3 153Vertical movement count in two's complement; 154-256 through 255. 155Note that the sign bit is in the first byte. 156.El 157.Pp 158At the level one, a data packet is encoded 159in the standard format 160.Dv MOUSE_PROTO_SYSMOUSE 161as defined in 162.Xr mouse 4 . 163.Pp 164At the level two, native level, there is no standard on the size and format 165of the data packet. 166.Ss Acceleration 167The 168.Nm 169driver can somewhat `accelerate' the movement of the pointing device. 170The faster you move the device, the further the pointer 171travels on the screen. 172The driver has an internal variable which governs the effect of 173the acceleration. 174Its value can be modified via the driver flag 175or via an ioctl call. 176.Ss Device Number 177The minor device number of the 178.Nm 179is made up of: 180.Bd -literal -offset indent 181minor = (`unit' << 1) | `non-blocking' 182.Ed 183.Pp 184where `unit' is the device number (usually 0) and the `non-blocking' bit 185is set to indicate ``don't block waiting for mouse input, 186return immediately''. 187The `non-blocking' bit should be set for \fIXFree86\fP, 188therefore the minor device number usually used for \fIXFree86\fP is 1. 189See 190.Sx FILES 191for device node names. 192.Sh DRIVER CONFIGURATION 193.Ss Kernel Configuration Options 194There are following kernel configuration options to control the 195.Nm 196driver. 197They may be set in the kernel configuration file 198(see 199.Xr config 8 ) . 200.Bl -tag -width MOUSE 201.It Em KBD_RESETDELAY=X , KBD_MAXWAIT=Y 202The 203.Nm 204driver will attempt to reset the pointing device during the boot process. 205It sometimes takes a long while before the device will respond after 206reset. 207These options control how long the driver should wait before 208it eventually gives up waiting. 209The driver will wait 210.Fa X 211* 212.Fa Y 213msecs at most. 214If the driver seems unable to detect your pointing 215device, you may want to increase these values. 216The default values are 217200 msec for 218.Fa X 219and 5 220for 221.Fa Y . 222.It Em PSM_DEBUG=N , KBDIO_DEBUG=N 223Sets the debug level to 224.Fa N . 225The default debug level is zero. 226See 227.Sx DIAGNOSTICS 228for debug logging. 229.El 230.Ss Driver Flags 231The 232.Nm 233driver accepts the following driver flags. 234Set them in the 235kernel configuration file or in the User Configuration Menu at 236the boot time 237(see 238.Xr boot 8 ) . 239.Pp 240.Bl -tag -width MOUSE 241.It bit 0..3 RESOLUTION 242This flag specifies the resolution of the pointing device. 243It must be zero through four. 244The greater the value 245is, the finer resolution the device will select. 246Actual resolution selected by this field varies according to the model 247of the device. 248Typical resolutions are: 249.Pp 250.Bl -tag -width 0_(medium_high)__ -compact 251.It Em 1 (low) 25225 pulse per inch (ppi) 253.It Em 2 (medium low) 25450 ppi 255.It Em 3 (medium high) 256100 ppi 257.It Em 4 (high) 258200 ppi 259.El 260.Pp 261Leaving this flag zero will selects the default resolution for the 262device (whatever it is). 263.It bit 4..7 ACCELERATION 264This flag controls the amount of acceleration effect. 265The smaller the value of this flag is, more sensitive the movement becomes. 266The minimum value allowed, thus the value for the most sensitive setting, 267is one. 268Setting this flag to zero will completely disables the 269acceleration effect. 270.It bit 8 NOCHECKSYNC 271The 272.Nm 273driver tries to detect the first byte of the data packet by checking 274the bit pattern of that byte. 275Although this method should work with most 276PS/2 pointing devices, it may interfere with some devices which are not 277so compatible with known devices. 278If you think your pointing device is not functioning as expected, 279and the kernel frequently prints the following message to the console, 280.Bd -literal -offset indent 281psmintr: out of sync (xxxx != yyyy). 282.Ed 283.Pp 284set this flag to disable synchronization check and see if it helps. 285.It bit 9 NOIDPROBE 286The 287.Nm 288driver will not try to identify the model of the pointing device and 289will not carry out model-specific initialization. 290The device should always act like a standard PS/2 mouse without such 291initialization. 292Extra features, such as wheels and additional buttons, won't be 293recognized by the 294.Nm 295driver. 296.It bit 10 NORESET 297When this flag is set, the 298.Nm 299driver won't reset the pointing device when initializing the device. 300If the 301.Dx 302kernel 303is started after another OS has run, the pointing device will inherit 304settings from the previous OS. 305However, because there is no way for the 306.Nm 307driver to know the settings, the device and the driver may not 308work correctly. 309The flag should never be necessary under normal circumstances. 310.It bit 11 FORCETAP 311Some pad devices report as if the fourth button is pressed 312when the user `taps' the surface of the device (see 313.Sx CAVEATS ) . 314This flag will make the 315.Nm 316driver assume that the device behaves this way. 317Without the flag, the driver will assume this behavior 318for ALPS GlidePoint models only. 319.It bit 12 IGNOREPORTERROR 320This flag makes 321.Nm 322driver ignore certain error conditions when probing the PS/2 mouse port. 323It should never be necessary under normal circumstances. 324.It bit 13 HOOKRESUME 325The built-in PS/2 pointing device of some laptop computers is somehow 326not operable immediately after the system `resumes' from 327the power saving mode, 328though it will eventually become available. 329There are reports that 330stimulating the device by performing I/O will help 331waking up the device quickly. 332This flag will enable a piece of code in the 333.Nm 334driver to hook 335the `resume' event and exercise some harmless I/O operations on the 336device. 337.It bit 14 INITAFTERSUSPEND 338This flag adds more drastic action for the above problem. 339It will cause the 340.Nm 341driver to reset and re-initialize the pointing device 342after the `resume' event. 343It has no effect unless the 344.Em HOOKRESUME 345flag is set as well. 346.El 347.Sh IOCTLS 348There are a few 349.Xr ioctl 2 350commands for mouse drivers. 351These commands and related structures and constants are defined in 352.In machine/mouse.h . 353General description of the commands is given in 354.Xr mouse 4 . 355This section explains the features specific to the 356.Nm 357driver. 358.Pp 359.Bl -tag -width MOUSE -compact 360.It Dv MOUSE_GETLEVEL Ar int *level 361.It Dv MOUSE_SETLEVEL Ar int *level 362These commands manipulate the operation level of the 363.Nm 364driver. 365.Pp 366.It Dv MOUSE_GETHWINFO Ar mousehw_t *hw 367Returns the hardware information of the attached device in the following 368structure. 369.Bd -literal 370typedef struct mousehw { 371 int buttons; /* number of buttons */ 372 int iftype; /* I/F type */ 373 int type; /* mouse/track ball/pad... */ 374 int model; /* I/F dependent model ID */ 375 int hwid; /* I/F dependent hardware ID */ 376} mousehw_t; 377.Ed 378.Pp 379The 380.Dv buttons 381field holds the number of buttons on the device. 382The 383.Nm 384driver currently can detect the 3 button mouse from Logitech and report 385accordingly. 386The 3 button mouse from the other manufacturer may or may not be 387reported correctly. 388However, it will not affect the operation of 389the driver. 390.Pp 391The 392.Dv iftype 393is always 394.Dv MOUSE_IF_PS2 . 395.Pp 396The 397.Dv type 398tells the device type: 399.Dv MOUSE_MOUSE , 400.Dv MOUSE_TRACKBALL , 401.Dv MOUSE_STICK , 402.Dv MOUSE_PAD , 403or 404.Dv MOUSE_UNKNOWN . 405The user should not heavily rely on this field, as the 406driver may not always, in fact it is very rarely able to, identify 407the device type. 408.Pp 409The 410.Dv model 411is always 412.Dv MOUSE_MODEL_GENERIC 413at the operation level 0. 414It may be 415.Dv MOUSE_MODEL_GENERIC 416or one of 417.Dv MOUSE_MODEL_XXX 418constants at higher operation levels. 419Again the 420.Nm 421driver may or may not set an appropriate value in this field. 422.Pp 423The 424.Dv hwid 425is the ID value returned by the device. 426Known IDs include: 427.Pp 428.Bl -tag -width 0__ -compact 429.It Em 0 430Mouse (Microsoft, Logitech and many other manufacturers) 431.It Em 2 432Microsoft Ballpoint mouse 433.It Em 3 434Microsoft IntelliMouse 435.El 436.Pp 437.It Dv MOUSE_GETMODE Ar mousemode_t *mode 438The command gets the current operation parameters of the mouse 439driver. 440.Bd -literal 441typedef struct mousemode { 442 int protocol; /* MOUSE_PROTO_XXX */ 443 int rate; /* report rate (per sec), -1 if unknown */ 444 int resolution; /* MOUSE_RES_XXX, -1 if unknown */ 445 int accelfactor; /* acceleration factor */ 446 int level; /* driver operation level */ 447 int packetsize; /* the length of the data packet */ 448 unsigned char syncmask[2]; /* sync. bits */ 449} mousemode_t; 450.Ed 451.Pp 452The 453.Dv protocol 454is 455.Dv MOUSE_PROTO_PS2 456at the operation level zero and two. 457.Dv MOUSE_PROTO_SYSMOUSE 458at the operation level one. 459.Pp 460The 461.Dv rate 462is the status report rate (reports/sec) at which the device will send 463movement report to the host computer. 464Typical supported values are 10, 20, 40, 60, 80, 100 and 200. 465Some mice may accept other arbitrary values too. 466.Pp 467The 468.Dv resolution 469of the pointing device must be one of 470.Dv MOUSE_RES_XXX 471constants or a positive value. 472The greater the value 473is, the finer resolution the mouse will select. 474Actual resolution selected by the 475.Dv MOUSE_RES_XXX 476constant varies according to the model of mouse. 477Typical resolutions are: 478.Pp 479.Bl -tag -width MOUSE_RES_MEDIUMHIGH__ -compact 480.It Dv MOUSE_RES_LOW 48125 ppi 482.It Dv MOUSE_RES_MEDIUMLOW 48350 ppi 484.It Dv MOUSE_RES_MEDIUMHIGH 485100 ppi 486.It Dv MOUSE_RES_HIGH 487200 ppi 488.El 489.Pp 490The 491.Dv accelfactor 492field holds a value to control acceleration feature 493(see 494.Sx Acceleration ) . 495It must be zero or greater. If it is zero, acceleration is disabled. 496.Pp 497The 498.Dv packetsize 499field specifies the length of the data packet. 500It depends on the 501operation level and the model of the pointing device. 502.Pp 503.Bl -tag -width level_0__ -compact 504.It Em level 0 5053 bytes 506.It Em level 1 5078 bytes 508.It Em level 2 509Depends on the model of the device 510.El 511.Pp 512The array 513.Dv syncmask 514holds a bit mask and pattern to detect the first byte of the 515data packet. 516.Dv syncmask[0] 517is the bit mask to be ANDed with a byte. 518If the result is equal to 519.Dv syncmask[1] , 520the byte is likely to be the first byte of the data packet. 521Note that this detection method is not 100% reliable, 522thus, should be taken only as an advisory measure. 523.Pp 524.It Dv MOUSE_SETMODE Ar mousemode_t *mode 525The command changes the current operation parameters of the mouse driver 526as specified in 527.Ar mode . 528Only 529.Dv rate , 530.Dv resolution , 531.Dv level 532and 533.Dv accelfactor 534may be modifiable. 535Setting values in the other field does not generate 536error and has no effect. 537.Pp 538If you do not want to change the current setting of a field, put -1 539there. 540You may also put zero in 541.Dv resolution 542and 543.Dv rate , 544and the default value for the fields will be selected. 545.\" .Pp 546.\" .It Dv MOUSE_GETVARS Ar mousevar_t *vars 547.\" .It Dv MOUSE_SETVARS Ar mousevar_t *vars 548.\" These commands are not supported by the 549.\" .Nm 550.\" driver. 551.Pp 552.It Dv MOUSE_READDATA Ar mousedata_t *data 553.\" The command reads the raw data from the device. 554.\" .Bd -literal 555.\" typedef struct mousedata { 556.\" int len; /* # of data in the buffer */ 557.\" int buf[16]; /* data buffer */ 558.\" } mousedata_t; 559.\" .Ed 560.\" .Pp 561.\" Upon returning to the user program, the driver will place the number 562.\" of valid data bytes in the buffer in the 563.\" .Dv len 564.\" field. 565.\" .Pp 566.It Dv MOUSE_READSTATE Ar mousedata_t *state 567.\" The command reads the hardware settings from the device. 568.\" Upon returning to the user program, the driver will place the number 569.\" of valid data bytes in the buffer in the 570.\" .Dv len 571.\" field. It is usually 3 bytes. 572.\" The buffer is formatted as follows: 573.\" .Pp 574.\" .Bl -tag -width Byte_1 -compact 575.\" .It Byte 1 576.\" .Bl -tag -width bit_6 -compact 577.\" .It bit 7 578.\" Reserved. 579.\" .It bit 6 580.\" 0 - stream mode, 1 - remote mode. 581.\" In the stream mode, the pointing device sends the device status 582.\" whenever its state changes. In the remote mode, the host computer 583.\" must request the status to be sent. 584.\" The 585.\" .Nm 586.\" driver puts the device in the stream mode. 587.\" .It bit 5 588.\" Set if the pointing device is currently enabled. Otherwise zero. 589.\" .It bit 4 590.\" 0 - 1:1 scaling, 1 - 2:1 scaling. 591.\" 1:1 scaling is the default. 592.\" .It bit 3 593.\" Reserved. 594.\" .It bit 2 595.\" Left button status; set if pressed. 596.\" .It bit 1 597.\" Middle button status; set if pressed. 598.\" .It bit 0 599.\" Right button status; set if pressed. 600.\" .El 601.\" .It Byte 2 602.\" .Bl -tag -width bit_6_0 -compact 603.\" .It bit 7 604.\" Reserved. 605.\" .It bit 6..0 606.\" Resolution code: zero through three. Actual resolution for 607.\" the resolution code varies from one device to another. 608.\" .El 609.\" .It Byte 3 610.\" The status report rate (reports/sec) at which the device will send 611.\" movement report to the host computer. 612.\" .El 613These commands are not currently supported by the 614.Nm 615driver. 616.Pp 617.It Dv MOUSE_GETSTATUS Ar mousestatus_t *status 618The command returns the current state of buttons and 619movement counts as described in 620.Xr mouse 4 . 621.El 622.Sh FILES 623.Bl -tag -width /dev/npsm0 -compact 624.It Pa /dev/psm0 625`non-blocking' device node 626.It Pa /dev/bpsm0 627`blocking' device node 628.El 629.Sh EXAMPLES 630.Dl "device psm0 at atkbdc? irq 12 flags 0x2000" 631.Pp 632Add the 633.Nm 634driver to the kernel with the optional code to stimulate the pointing device 635after the `resume' event. 636.Pp 637.Dl "device psm0 at atkbdc? flags 0x024 irq 12" 638.Pp 639Set the device resolution high (4) and the acceleration factor to 2. 640.Sh DIAGNOSTICS 641At debug level 0, little information is logged except for the following 642line during boot process: 643.Bd -literal -offset indent 644psm0: device ID X 645.Ed 646.Pp 647where 648.Fa X 649the device ID code returned by the found pointing device. 650See 651.Dv MOUSE_GETINFO 652for known IDs. 653.Pp 654At debug level 1 more information will be logged 655while the driver probes the auxiliary port (mouse port). 656Messages are logged with the LOG_KERN facility at the LOG_DEBUG level 657(see 658.Xr syslogd 8 ) . 659.Bd -literal -offset indent 660psm0: current command byte:xxxx 661kbdio: TEST_AUX_PORT status:0000 662kbdio: RESET_AUX return code:00fa 663kbdio: RESET_AUX status:00aa 664kbdio: RESET_AUX ID:0000 665[...] 666psm: status 00 02 64 667psm0 irq 12 on isa 668psm0: model AAAA, device ID X, N buttons 669psm0: config:00000www, flags:0000uuuu, packet size:M 670psm0: syncmask:xx, syncbits:yy 671.Ed 672.Pp 673The first line shows the command byte value of the keyboard 674controller just before the auxiliary port is probed. 675It usually is 4D, 45, 47 or 65, depending on how the motherboard BIOS 676initialized the keyboard controller upon power-up. 677.Pp 678The second line shows the result of the keyboard controller's 679test on the auxiliary port interface, with zero indicating 680no error; note that some controllers report no error even if 681the port does not exist in the system, however. 682.Pp 683The third through fifth lines show the reset status of the pointing device. 684The functioning device should return the sequence of FA AA <ID>. 685The ID code is described above. 686.Pp 687The seventh line shows the current hardware settings. 688.\" See 689.\" .Dv MOUSE_READSTATE 690.\" for definitions. 691These bytes are formatted as follows: 692.Pp 693.Bl -tag -width Byte_1 -compact 694.It Byte 1 695.Bl -tag -width bit_6 -compact 696.It bit 7 697Reserved. 698.It bit 6 6990 - stream mode, 1 - remote mode. 700In the stream mode, the pointing device sends the device status 701whenever its state changes. 702In the remote mode, the host computer 703must request the status to be sent. 704The 705.Nm 706driver puts the device in the stream mode. 707.It bit 5 708Set if the pointing device is currently enabled. 709Otherwise zero. 710.It bit 4 7110 - 1:1 scaling, 1 - 2:1 scaling. 7121:1 scaling is the default. 713.It bit 3 714Reserved. 715.It bit 2 716Left button status; set if pressed. 717.It bit 1 718Middle button status; set if pressed. 719.It bit 0 720Right button status; set if pressed. 721.El 722.It Byte 2 723.Bl -tag -width bit_6_0 -compact 724.It bit 7 725Reserved. 726.It bit 6..0 727Resolution code: zero through three. 728Actual resolution for 729the resolution code varies from one device to another. 730.El 731.It Byte 3 732The status report rate (reports/sec) at which the device will send 733movement report to the host computer. 734.El 735.Pp 736Note that the pointing device will not be enabled until the 737.Nm 738driver is opened by the user program. 739.Pp 740The rest of the lines show the device ID code, the number of detected 741buttons and internal variables. 742.Pp 743At debug level 2, much more detailed information is logged. 744.Sh CAVEATS 745Many pad devices behave as if the first (left) button were pressed if 746the user `taps' the surface of the pad. 747In contrast, some pad products, e.g. some versions of ALPS GlidePoint 748and Interlink VersaPad, treat the tapping action 749as fourth button events. 750.Pp 751It is reported that Interlink VersaPad rquires both 752.Em HOOKRESUME 753and 754.Em INITAFTERSUSPEND 755flags in order to recover from suspended state. 756These flags are automatically set when VersaPad is detected by the 757.Nm 758driver. 759.Pp 760Some PS/2 mouse models from MouseSystems require to be put in the 761high resolution mode to work properly. 762Use the driver flag to 763set resolution. 764.Pp 765There is not a guaranteed way to re-synchronize with the first byte 766of the packet once we are out of synchronization with the data 767stream. 768However, if you are using the \fIXFree86\fP server and experiencing 769the problem, you may be able to make the X server synchronize with the mouse 770by switching away to a virtual terminal and getting back to the X server, 771unless the X server is accessing the mouse via 772.Xr moused 8 . 773Clicking any button without moving the mouse may also work. 774.Sh SEE ALSO 775.Xr ioctl 2 , 776.Xr syslog 3 , 777.Xr atkbdc 4 , 778.Xr mouse 4 , 779.Xr mse 4 , 780.Xr sysmouse 4 , 781.Xr moused 8 , 782.Xr syslogd 8 783.\".Sh HISTORY 784.Sh AUTHORS 785.An -nosplit 786The 787.Nm 788driver is based on the work done by quite a number of people, including 789.An Eric Forsberg , 790.An Sandi Donno , 791.An Rick Macklem , 792.An Andrew Herbert , 793.An Charles Hannum , 794.An Shoji Yuen 795and 796.An Kazutaka Yokota 797to name the few. 798.Pp 799This manual page was written by 800.An Kazutaka Yokota Aq yokota@FreeBSD.org . 801.Sh BUGS 802The ioctl command 803.Dv MOUSEIOCREAD 804has been removed. 805It was never functional anyway. 806