BSD 4_3_Net_2 release

[unix-history] / usr / src / share / man / man4 / man4.vax / dhu.4

diff --git a/usr/src/share/man/man4/man4.vax/dhu.4 b/usr/src/share/man/man4/man4.vax/dhu.4
index dc7558d..1fd7f23 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dhu.4
+++ b/usr/src/share/man/man4/man4.vax/dhu.4
@@ -1,58 +1,145 @@
-.\" Copyright (c) 1985 Regents of the University of California.
-.\" All rights reserved.  The Berkeley software License Agreement
-.\" specifies the terms and conditions for redistribution.
+.\" Copyright (c) 1985, 1991 Regents of the University of California.
+.\" All rights reserved.

 .\"
 .\"

-.\"    @(#)dhu.4       6.2 (Berkeley) %G%
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.TH DHU 4 ""
-.UC 6
-.SH NAME
-dhu \- DHU-11 communications multiplexer
-.SH SYNOPSIS
-.B "device dhu0 at uba0 csr 0160440 vector dhurint dhuxint"
-.SH DESCRIPTION
-A DHU-11 provides 16 communication lines.
-.PP
-Each line attached to the DHU-11 communications multiplexer
-behaves as described in
-.IR tty (4).
-Input and output for each line may independently
-be set to run at any of 13 speeds (50, 200 and 38400 baud are not available);
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     @(#)dhu.4      6.3 (Berkeley) 3/27/91
+.\"
+.Dd March 27, 1991
+.Dt DHU 4 vax
+.Os BSD 4.3
+.Sh NAME
+.Nm dhu
+.Nd
+.Tn DHU-11
+communications multiplexer
+.Sh SYNOPSIS
+.Cd "device dhu0 at uba0 csr 0160440 vector dhurint dhuxint"
+.Sh DESCRIPTION
+A
+.Tn DHU-11
+provides 16 communication lines.
+.Pp
+An optional argument
+.Ar flags
+may be supplied with the device specification
+in the config file indicating
+that the line corresponding to
+bit number
+.Ar i
+is not properly
+connected, and should be treated as hard-wired with carrier
+always present.  Thus specifying
+.Ql flags 0x0004
+for
+.Li dhu0
+would cause line
+.Pa ttyS2
+to be treated in this way.
+.Pp
+Normal I/O
+control parameters for individual lines are managed by
+.Xr ioctl 2
+calls.
+Individual
+.Tn DHU-11
+lines may be configured to run at any of 13 speeds
+(50, 200 and 38400 baud are not available);
+the speed may be set via
+.Xr getty 8
+or
+.Xr stty 1
+or may be communicated by other programs which
+utilize
+.Xr ioctl
+such as
+.Xr ifcongif 8 ,

 see
 see

-.IR tty (4)
-for the encoding.
-.PP
-Bit
-.I i
-of flags may be specified for a DHU-11 to say that a line is not properly
-connected, and that the line should be treated as hard-wired with carrier
-always present.  Thus specifying ``flags 0x0004'' in the specification of dhu0
-would cause line ttyS2 to be treated in this way.
-.PP
-The DHU-11 driver normally uses input silos
+.Xr tty 4 .
+.Pp
+The
+.Tn DHU-11
+driver normally uses input silos

 and delays receiver interrupts by 20 milliseconds
 rather than taking an interrupt on each input character.
 and delays receiver interrupts by 20 milliseconds
 rather than taking an interrupt on each input character.

-.SH FILES
-/dev/tty[S-Z][0-9a-f]
-.SH "SEE ALSO"
-tty(4)
-.SH DIAGNOSTICS
-\fBdhu(%d,%d): NXM fault\fR.  No response from UNIBUS on a DMA transfer
-within a timeout period.  This is often followed by a UNIBUS adapter
-error.  This occurs most frequently when the UNIBUS is heavily loaded
-and when devices which hog the bus (such as RK07s) are present.
+.Sh FILES
+.Bl -tag -width /dev/tty[S-Z][0-9a-f]xx -compact
+.It Pa /dev/tty[S-Z][0-9a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dhu(%d,%d): NXM fault.
+No response from
+.Tn UNIBUS
+on a
+.Tn DMA
+transfer
+within a timeout period.  This is often followed by a
+.Tn UNIBUS
+adapter
+error.  This occurs most frequently when the
+.Tn UNIBUS
+is heavily loaded
+and when devices which hog the bus (such as
+.Tn RK07 Ns s )
+are present.

 It is not serious.
 It is not serious.

-.PP
-\fBdhu%d: silo overflow\fR.  The character input silo overflowed
+.Pp
+.It dhu%d: silo overflow.
+The character input silo overflowed

 before it could be serviced.  This can happen if a hard error occurs
 before it could be serviced.  This can happen if a hard error occurs

-when the CPU is running with elevated priority, as the system may
+when the
+.Tn CPU
+is running with elevated priority, as the system may

 then print a message on the console with interrupts disabled.
 then print a message on the console with interrupts disabled.

-.SH NOTES
+.El
+.Sh NOTES

 The driver currently does not make full use of the hardware
 The driver currently does not make full use of the hardware

-capabilities of the DHU-11, for dealing with XON/XOFF flow-control or hard-wired
+capabilities of the
+.Tn DHU-11 ,
+for dealing with
+.Tn XON/XOFF
+flow-control or hard-wired

 lines for example.
 lines for example.

-.PP
-Although the devices are not the same, a DHU-11 can convince the
-DH-11 autoconfiguration code that it is a DH-11.
-.PP
+.Pp
+Although the devices are not the same, a
+.Tn DHU-11
+can convince the
+.Tn DH-11
+autoconfiguration code that it is a
+.Tn DH-11 .
+.Pp

 The 4 40-way cables are a pain.
 The 4 40-way cables are a pain.

+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver appeared in
+.Bx 4.3 .