| moused.8 (32277) | moused.8 (32767) |
|---|---|
| 1.\" Copyright (c) 1996 2.\" Mike Pritchard <mpp@FreeBSD.org>. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 14 unchanged lines hidden (view full) --- 23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 29.\" SUCH DAMAGE. 30.\" | 1.\" Copyright (c) 1996 2.\" Mike Pritchard <mpp@FreeBSD.org>. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 14 unchanged lines hidden (view full) --- 23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 29.\" SUCH DAMAGE. 30.\" |
| 31.\" $Id: moused.8,v 1.9 1997/12/23 08:04:37 yokota Exp $ | 31.\" $Id: moused.8,v 1.10 1998/01/05 12:38:13 yokota Exp $ |
| 32.\" 33.Dd December 3, 1997 34.Dt MOUSED 8 35.Os FreeBSD 36.Sh NAME 37.Nm moused 38.Nd pass mouse data to the console driver 39.Sh SYNOPSIS --- 68 unchanged lines hidden (view full) --- 108Set the report rate (reports/sec) of the device if supported. 109.It Fl P 110Do not start the Plug and Play COM device enumeration procedure 111when identifying the serial mouse. 112If this option is given together with the 113.Fl i 114option, the 115.Nm | 32.\" 33.Dd December 3, 1997 34.Dt MOUSED 8 35.Os FreeBSD 36.Sh NAME 37.Nm moused 38.Nd pass mouse data to the console driver 39.Sh SYNOPSIS --- 68 unchanged lines hidden (view full) --- 108Set the report rate (reports/sec) of the device if supported. 109.It Fl P 110Do not start the Plug and Play COM device enumeration procedure 111when identifying the serial mouse. 112If this option is given together with the 113.Fl i 114option, the 115.Nm |
| 116command won't be able to print userful information for the serial mouse. | 116command won't be able to print useful information for the serial mouse. |
| 117.It Fl R 118Lower RTS on the serial port. 119This option is valid only if 120.Ar mousesystems 121is selected as the protocol type by the 122.Fl t 123option below. It is often used with the 124.Fl D --- 17 unchanged lines hidden (view full) --- 142information are: 143.Pp 144.Bl -tag -compact -width modelxxx 145.It Ar port 146Port (device file) name, i.e. 147.Pa /dev/cuaa0 , 148.Pa /dev/mse0 149and | 117.It Fl R 118Lower RTS on the serial port. 119This option is valid only if 120.Ar mousesystems 121is selected as the protocol type by the 122.Fl t 123option below. It is often used with the 124.Fl D --- 17 unchanged lines hidden (view full) --- 142information are: 143.Pp 144.Bl -tag -compact -width modelxxx 145.It Ar port 146Port (device file) name, i.e. 147.Pa /dev/cuaa0 , 148.Pa /dev/mse0 149and |
| 150.Pa /dev/psm0. | 150.Pa /dev/psm0 . |
| 151.It Ar if 152Interface type: serial, bus, inport or ps/2. 153.It Ar type 154Protocol type. It is one of the types listed under the 155.Fl t 156option below or 157.Ar sysmouse 158if the driver supports the --- 141 unchanged lines hidden (view full) --- 300Some mice come with adapters with which the connector can 301be converted to another. If you are to use such an adapter, 302remember the connector at the very end of the mouse/adapter pair is 303what matters. 304.Pp 305The next thing to decide is a port to use for the given interface. 306For the bus, InPort and PS/2 mice, there is little choice: 307the bus and InPort mice always use | 151.It Ar if 152Interface type: serial, bus, inport or ps/2. 153.It Ar type 154Protocol type. It is one of the types listed under the 155.Fl t 156option below or 157.Ar sysmouse 158if the driver supports the --- 141 unchanged lines hidden (view full) --- 300Some mice come with adapters with which the connector can 301be converted to another. If you are to use such an adapter, 302remember the connector at the very end of the mouse/adapter pair is 303what matters. 304.Pp 305The next thing to decide is a port to use for the given interface. 306For the bus, InPort and PS/2 mice, there is little choice: 307the bus and InPort mice always use |
| 308.Pa /dev/mse0, | 308.Pa /dev/mse0 , |
| 309and the PS/2 mouse is always at | 309and the PS/2 mouse is always at |
| 310.Pa /dev/psm0. | 310.Pa /dev/psm0 . |
| 311There may be more than one serial port to which the serial 312mouse can be attached. Many people often assign the first, built-in 313serial port 314.Pa /dev/cuaa0 315to the mouse. 316You may want to create a symbolic link 317.Pa /dev/mouse 318pointing to the real port to which the mouse is connected, so that you --- 79 unchanged lines hidden (view full) --- 398.Pp 399.Dl vidcontrol -m on 400.Pp 401start the mouse daemon in the foreground mode, 402.Pp 403.Dl moused -f -p Ar _selected_port_ -t Ar _selected_protocol_ 404.Pp 405and see if the mouse pointer travels correctly | 311There may be more than one serial port to which the serial 312mouse can be attached. Many people often assign the first, built-in 313serial port 314.Pa /dev/cuaa0 315to the mouse. 316You may want to create a symbolic link 317.Pa /dev/mouse 318pointing to the real port to which the mouse is connected, so that you --- 79 unchanged lines hidden (view full) --- 398.Pp 399.Dl vidcontrol -m on 400.Pp 401start the mouse daemon in the foreground mode, 402.Pp 403.Dl moused -f -p Ar _selected_port_ -t Ar _selected_protocol_ 404.Pp 405and see if the mouse pointer travels correctly |
| 406according to the mouse movement. Then try cur & paste features by | 406according to the mouse movement. Then try cut & paste features by |
| 407clicking the left, right and middle buttons. Type ^C to stop 408the command. 409.Ss Multiple Mice 410As many instances of the mouse daemon as the number of mice attached to 411the system may be run simultaneously; one 412instance for each mouse. 413This is useful if the user wants to use the built-in PS/2 pointing device 414of a laptop computer while on the road, but wants to use a serial --- 25 unchanged lines hidden (view full) --- 440.El 441.Sh EXAMPLE 442.Pp 443.Dl moused -p /dev/cuaa0 -i type 444.Pp 445Let the 446.Nm 447command determine the protocol type of the mouse at the serial port | 407clicking the left, right and middle buttons. Type ^C to stop 408the command. 409.Ss Multiple Mice 410As many instances of the mouse daemon as the number of mice attached to 411the system may be run simultaneously; one 412instance for each mouse. 413This is useful if the user wants to use the built-in PS/2 pointing device 414of a laptop computer while on the road, but wants to use a serial --- 25 unchanged lines hidden (view full) --- 440.El 441.Sh EXAMPLE 442.Pp 443.Dl moused -p /dev/cuaa0 -i type 444.Pp 445Let the 446.Nm 447command determine the protocol type of the mouse at the serial port |
| 448.Pa /dev/cuaa0. | 448.Pa /dev/cuaa0 . |
| 449If successful, the command will print the type, otherwise it will say 450``unknown''. 451.Pp 452.Dl moused -p /dev/cuaa0 453.Dl vidcontrol -m on 454.Pp 455If the 456.Nm 457command is able to identify the protocol type of the mouse at the specified 458port automatically, you can start the daemon without the 459.Fl t 460option and enable the mouse pointer in the text console as above. 461.Pp 462.Dl moused -p /dev/mouse -t microsoft 463.Dl vidcontrol -m on 464.Pp 465Start the mouse daemon on the serial port | 449If successful, the command will print the type, otherwise it will say 450``unknown''. 451.Pp 452.Dl moused -p /dev/cuaa0 453.Dl vidcontrol -m on 454.Pp 455If the 456.Nm 457command is able to identify the protocol type of the mouse at the specified 458port automatically, you can start the daemon without the 459.Fl t 460option and enable the mouse pointer in the text console as above. 461.Pp 462.Dl moused -p /dev/mouse -t microsoft 463.Dl vidcontrol -m on 464.Pp 465Start the mouse daemon on the serial port |
| 466.Pa /dev/mouse. | 466.Pa /dev/mouse . |
| 467The protocol type 468.Ar microsoft 469is explicitly specified by the 470.Fl t 471option. 472.Pp 473.Dl moused -p /dev/mouse -m 1=3 -m 3=1 474.Pp --- 70 unchanged lines hidden --- | 467The protocol type 468.Ar microsoft 469is explicitly specified by the 470.Fl t 471option. 472.Pp 473.Dl moused -p /dev/mouse -m 1=3 -m 3=1 474.Pp --- 70 unchanged lines hidden --- |