Lines Matching +full:usb +full:- +full:to +full:- +full:serial

1 .\"-
2 .\" SPDX-License-Identifier: BSD-4-Clause
19 .\"    may be used to endorse or promote products derived from this software
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
60 driver work together to support legacy devices like COM,
65 and some other devices are supported too but not recomended to use with
71 listens to the specified port for mouse data, decodes and then passes
72 it via input event device a.k.a evdev to consumer aplications like
102 .Bl -tag -width indent
104 Lower DTR on the serial port.
108 The DTR line may need to be dropped for a 3-button mouse
122 when identifying the serial mouse.
127 utility will not be able to print useful information for the serial mouse.
129 Lower RTS on the serial port.
138 Both RTS and DTR lines may need to be dropped for
139 a 3-button mouse to operate in the
143 Select the baudrate for the serial port (1200 to 9600).
144 Not all serial mice support this option.
159 .Bl -tag -compact -width modelxxx
167 Interface type: serial or ps/2.
181 utility may not always be able to identify the model.
198 Refer to
210 .Ar medium-low ,
211 .Ar medium-high
216 Select a baudrate of 9600 for the serial line.
217 Not all serial mice support this option.
219 Specify the protocol type of the mouse attached to the port.
230 you need to use this option only if the
232 utility is not able to detect the protocol automatically
241 Also note that if your mouse is attached to the PS/2 mouse port, you should
248 For the USB mouse, the protocol must be
250 No other protocol will work with the USB mouse.
255 For the serial mouse:
256 .Bl -tag -compact -width mousesystemsxxx
258 Microsoft serial mouse protocol.
259 Most 2-button serial mice use this protocol.
268 MouseSystems 5-byte protocol.
269 3-button mice may use this protocol.
281 Some 3-button mice may be compatible
303 .Bl -tag -compact -width mousesystemsxxx
309 For the USB mouse,
311 is the only protocol type available for the USB mouse
312 and should be specified for any USB mice, regardless of the brand.
316 The first thing you need to know is the interface type
317 of the mouse you are going to use.
319 The serial mouse has a D-Sub female 9- or 25-pin connector.
320 The bus and InPort mice have either a D-Sub male 9-pin connector
321 or a round DIN 9-pin connector.
322 The PS/2 mouse is equipped with a small, round DIN 6-pin connector.
324 be converted to another.
325 If you are to use such an adapter,
328 The USB mouse has a flat rectangular connector.
330 The next thing to decide is a port to use for the given interface.
333 There may be more than one serial port to which the serial
335 Many people often assign the first, built-in
336 serial port
339 You can attach multiple USB mice to your system or to your USB hub.
344 You may want to create a symbolic link
346 pointing to the real port to which the mouse is connected, so that you
351 The next step is to guess the appropriate protocol type for the mouse.
354 utility may be able to automatically determine the protocol type.
382 option yields nothing, you need to specify a protocol type to the
387 You have to make a guess and try.
390 .Bl -enum -compact -width 1.X
399 protocol for the USB mouse.
401 Most 2-button serial mice support the
405 3-button serial mice may work with the
412 3-button serial mice may also work with the
416 3-button serial mice may have a small switch to choose between
447 .Dl "moused -p auto"
453 .Dl "msconvd -f -p <selected_port> -t <selected_protocol>"
456 according to the mouse movement.
459 Type ^C to stop
464 as the number of mice attached to the system may be run simultaneously;
466 This is useful if the user wants to use the built-in PS/2 pointing device
467 of a laptop computer while on the road, but wants to use a serial
468 mouse when s/he attaches the system to the docking station in the office.
474 When the serial mouse is not attached, the corresponding
484 .Bl -tag -width /dev/input/event%d -compact
490 serial port
500 UNIX-domain stream socket for X10 MouseRemote events
503 .Dl "msconvd -p /dev/cuau0 -i type"
507 utility determine the protocol type of the mouse at the serial port
511 .Bd -literal -offset indent
512 msconvd -p /dev/cuau0
517 utility is able to identify the protocol type of the mouse at the specified
521 .Bd -literal -offset indent
522 msconvd -p /dev/mouse -t microsoft
525 Start the mouse daemon on the serial port
535 .Dl "ALL ALL = NOPASSWD: /usr/bin/killall -USR1 msconvd"
541 .Dl "killall -USR1 msconvd"
558 in order to support PnP serial mice.
559 However, due to various degrees of conformance to the specification by
560 existing serial mice, it does not strictly follow the version 1.0 of the
564 for the given serial mouse.
570 It is a cropped-down version of
576 .An -nosplit