1.\" $NetBSD: com.4,v 1.3 2001/04/20 16:08:16 jdolecek Exp $ 2.\" 3.\" Copyright (c) 1990, 1991 The Regents of the University of California. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to Berkeley by 7.\" the Systems Programming Group of the University of Utah Computer 8.\" Science Department. 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the University of 20.\" California, Berkeley and its contributors. 21.\" 4. Neither the name of the University nor the names of its contributors 22.\" may be used to endorse or promote products derived from this software 23.\" without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 26.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 27.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 28.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 29.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 30.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 31.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 32.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 33.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 34.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 35.\" SUCH DAMAGE. 36.\" 37.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91 38.\" 39.Dd April 20, 2001 40.Dt COM 4 41.Os 42.Sh NAME 43.Nm com 44.Nd 45serial communications interface 46.Sh SYNOPSIS 47.Cd "com0 at isa? port" \&"IO_COM1\&" irq 4 48.Cd "com1 at isa? port" \&"IO_COM2\&" irq 3 49.Cd "com* at cardbus?" 50.Cd "com* at isapnp?" 51.Cd "com* at mca? slot ?" 52.Cd "com* at mhzc?" 53.Cd "com* at ofisa?" 54.Cd "com* at pcmcia?" 55.Cd "com* at pcmcom?" 56.Cd "com* at pnpbios? index ?" 57.Cd "com* at puc? port ?" 58.Ss Arm32 59.Cd "com0 at mainbus? base 0x00210fe0" 60.Cd "com1 at mainbus? base 0x00210be0" 61.Sh DESCRIPTION 62The 63.Nm 64driver provides support for NS8250-, NS16450-, and NS16550-based 65.Tn EIA 66.Tn RS-232C 67.Pf ( Tn CCITT 68.Tn V.28 ) 69communications interfaces. The NS8250 and NS16450 have single character 70buffers, and the NS16550 has a 16 character buffer. 71.Pp 72Input and output for each line may set to one of following baud rates; 7350, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600, 7419200, 38400, 57600, or 115200, or any other baud rate which is a factor 75of 115200. 76.Pp 77The ttyXX devices are traditional dialin devices; the dtyXX devices are 78used for dialout. (See 79.Xr tty 4 . ) 80.Ss Arm32 specific 81If 82.Dq flags 1 83is specified, the 84.Nm 85driver will not set the MCR_IENABLE bit on the UART. This is mainly for 86use on AST multiport boards, where the MCR_IENABLE bit is used to control 87whether or not the devices use a shared interrupt. 88.Sh FILES 89.Bl -tag -width Pa -compact 90.It Pa /dev/dty00 91.It Pa /dev/dty01 92.It Pa /dev/dty02 93.It Pa /dev/tty00 94.It Pa /dev/tty01 95.It Pa /dev/tty02 96.El 97.Sh DIAGNOSTICS 98.Bl -diag 99.It com%d: %d silo overflows 100The input 101.Dq silo 102has overflowed and incoming data has been lost. 103.It com%d: weird interrupt: iir=%x 104The device has generated an unexpected interrupt 105with the code listed. 106.El 107.Sh SEE ALSO 108.Xr ast 4 , 109.Xr cardbus 4 , 110.Xr isa 4 , 111.Xr isapnp 4 , 112.Xr mca 4 , 113.Xr mhzc 4 , 114.Xr ofisa 4 , 115.Xr pcmcia 4 , 116.Xr pcmcom 4 , 117.Xr pnpbios 4 , 118.Xr puc 4 , 119.Xr rtfps 4 , 120.Xr tty 4 121.Sh HISTORY 122The 123.Nm 124driver was originally derived from the HP9000/300 125.Ic dca 126driver. 127.Sh BUGS 128Data loss is possible on busy systems with unbuffered UARTs at high speed. 129.Pp 130The name of this driver and the constants which define the locations 131of the various serial ports are holdovers from 132.Tn DOS . 133