BSD 4_3 release

[unix-history] / usr / man / man4 / dmc.4

diff --git a/usr/man/man4/dmc.4 b/usr/man/man4/dmc.4
index d0cdc07..c44e839 100644 (file)
--- a/usr/man/man4/dmc.4
+++ b/usr/man/man4/dmc.4
@@ -1,5 +1,11 @@
-.TH DMC 4 "27 July 1983"
-.UC 4
+.\" Copyright (c) 1983 Regents of the University of California.
+.\" All rights reserved.  The Berkeley software License Agreement
+.\" specifies the terms and conditions for redistribution.
+.\"
+.\"    @(#)dmc.4       6.3 (Berkeley) 5/21/86
+.\"
+.TH DMC 4 "May 21, 1986"
+.UC 5

 .SH NAME
 dmc \- DEC DMC-11/DMR-11 point-to-point communications device
 .SH SYNOPSIS
 .SH NAME
 dmc \- DEC DMC-11/DMR-11 point-to-point communications device
 .SH SYNOPSIS


@@ -16,9 +22,37 @@ The
 interface driver also supports a DEC DMR-11 providing point-to-point
 communication running at data rates from 2.4 Kb/s to 1 Mb/s.
 DMR-11's are a more recent design and thus are preferred over DMC-11's.
 interface driver also supports a DEC DMR-11 providing point-to-point
 communication running at data rates from 2.4 Kb/s to 1 Mb/s.
 DMR-11's are a more recent design and thus are preferred over DMC-11's.

+The NXMT and NRCV constants in the driver should be increased in this case,
+as the DMR can accept up to 64 transmit and receive buffers, as opposed
+to 7 for the DMC.

 .PP
 .PP

-The host's address must be specified with an SIOCSIFADDR ioctl
-before the interface will transmit or recive any packets.
+The configuration flags specify how to set up the device, 
+.br
+0 -- full duplex DDCMP (normal mode)
+.br
+1 -- DDCMP Maintence mode (generally useless)
+.br
+2 -- DDCMP Half Duplex, primary station
+.br
+3 -- DDCMP Half Duplex, secondary station
+.ti
+.PP
+Several device error counters are available via "adb", for
+more information see the adb script /usr/lib/adb/dmcstats, or the
+DMC11 technical manual.
+.PP
+The host's address must be specified with an SIOCSIFADDR ioctl,
+and the destination address specified with a SIOCSIFDSTADDR ioctl,
+before the interface will transmit or receive any packets.
+.SH ROUTING
+The driver places a HOST entry in the kernel routing tables for the
+address given in the SIOCSIFDSTADDR ioctl.  To use the DMC as a
+link between local nets, the route to the remote net must be added manually
+with the
+.IR route (8)
+command, or by the use of the routing process
+.IR routed (8)
+on each end of the link.

 .SH DIAGNOSTICS
 .BR "dmc%d: bad control %o" .
 A bad parameter was passed to the
 .SH DIAGNOSTICS
 .BR "dmc%d: bad control %o" .
 A bad parameter was passed to the


@@ -29,9 +63,11 @@ routine.
 An input packet was received which contained a type of
 address unknown to the driver.
 .PP
 An input packet was received which contained a type of
 address unknown to the driver.
 .PP

-.BR "DMC FATAL ERROR 0%o" .
+.BR "DMC fatal error 0%o" .
+A fatal error in DDMCP occurred, causing the device to be restarted.

 .PP
 .PP

-.BR "DMC SOFT ERROR 0%o" .
+.BR "DMC soft error 0%o" .
+A non-fatal error in DDMCP has occurred. 

 .PP
 .BR "dmc%d: af%d not supported" . 
 The interface was handed a message which has
 .PP
 .BR "dmc%d: af%d not supported" . 
 The interface was handed a message which has


@@ -39,6 +75,7 @@ addresses formatted in an unsuitable address family.
 .SH SEE ALSO
 intro(4N), inet(4F)
 .SH BUGS
 .SH SEE ALSO
 intro(4N), inet(4F)
 .SH BUGS

-Should allow multiple outstanding DMA requests, but due to
-the design of the current UNIBUS support routines this is
-very difficult.
+The current version of the driver uses a link-level encapsulation
+so that multiple protocol types may be used.
+It is thus incompatible with earlier drivers,
+including the 4.2BSD version.