1.\" $NetBSD: dz.4,v 1.9 2017/08/01 11:04:21 wiz 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. 60Thus specifying 61.Ql flags 0x04 62for 63.Li dz0 64would cause line 65.Pa tty02 66to be treated in this way. 67.Pp 68Normal I/O 69control parameters for individual lines are managed by 70.Xr ioctl 2 71calls. 72Line speeds may be initiated via 73the 74.Xr ttys 5 75file, 76.Xr stty 1 77or 78.Xr ifconfig 8 79to name a few, 80see 81.Xr tty 4 . 82.Pp 83The 84.Nm dz 85driver monitors the rate of input on each board, 86and switches between the use of character-at-a-time interrupts 87and input silos. 88While the silo is enabled during periods of high-speed input, 89the driver polls for input 30 times per second. 90.Sh FILES 91.Bl -tag -width /dev/tty[0-9][0-9]xx -compact 92.It Pa /dev/tty[0-9][0-9] 93.It Pa /dev/ttyd[0-9a-f] 94dialups 95.El 96.Sh DIAGNOSTICS 97.Bl -diag 98.It dz%d: silo overflow . 99The 64 character input silo overflowed 100before it could be serviced. 101This can happen if a hard error occurs 102when the 103.Tn CPU 104is running with elevated priority, as the system will 105then print a message on the console with interrupts disabled. 106It is not serious. 107.El 108.Sh SEE ALSO 109.Xr stty 1 , 110.Xr tty 4 , 111.Xr ttys 5 , 112.Xr getty 8 113.Sh HISTORY 114A 115.Nm 116driver appeared in 117.At 32v . 118