1.\" $NetBSD: dz.4,v 1.8 2003/08/07 10:31:11 agc Exp $ 2.\" 3.\" Copyright (c) 1980, 1991, 1993 4.\" The Regents of the University of California. 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. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" from: @(#)dz.4 8.1 (Berkeley) 6/5/93 31.\" 32.Dd June 5, 1993 33.Dt DZ 4 vax 34.Os 35.Sh NAME 36.Nm dz 37.Nd 38.Tn DZ-11 39serial multiplexer device interface 40.Sh SYNOPSIS 41.Cd "dz0 at uba0 csr 0160100 vector dzrint dzxint" 42.Sh DESCRIPTION 43A 44.Tn DZ-11 45provides 8 communication lines with partial modem control, 46adequate for 47.Ux 48dialup use. 49.Pp 50An optional argument 51.Ar flags 52may be supplied with the device specification 53in the config file indicating 54that the line corresponding to 55bit number 56.Ar i 57is not properly 58connected, and should be treated as hard-wired with carrier 59always present. Thus specifying 60.Ql flags 0x04 61for 62.Li dz0 63would cause line 64.Pa tty02 65to be treated in this way. 66.Pp 67Normal I/O 68control parameters for individual lines are managed by 69.Xr ioctl 2 70calls. 71Line speeds may be initiated via 72the 73.Xr ttys 5 74file, 75.Xr stty 1 76or 77.Xr ifconfig 8 78to name a few, 79see 80.Xr tty 4 . 81.Pp 82The 83.Nm dz 84driver monitors the rate of input on each board, 85and switches between the use of character-at-a-time interrupts 86and input silos. 87While the silo is enabled during periods of high-speed input, 88the driver polls for input 30 times per second. 89.Sh FILES 90.Bl -tag -width /dev/tty[0-9][0-9]xx -compact 91.It Pa /dev/tty[0-9][0-9] 92.It Pa /dev/ttyd[0-9a-f] 93dialups 94.El 95.Sh DIAGNOSTICS 96.Bl -diag 97.It dz%d: silo overflow . 98The 64 character input silo overflowed 99before it could be serviced. This can happen if a hard error occurs 100when the 101.Tn CPU 102is running with elevated priority, as the system will 103then print a message on the console with interrupts disabled. 104It is not serious. 105.El 106.Sh SEE ALSO 107.Xr stty 1 , 108.Xr tty 4 , 109.Xr ttys 5 , 110.Xr getty 8 111.Sh HISTORY 112A 113.Nm 114driver appeared in 115.At 32v . 116