xref: /netbsd-src/share/man/man4/man4.vax/dmc.4 (revision cda4f8f6ee55684e8d311b86c99ea59191e6b74f)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)dmc.4	8.1 (Berkeley) 6/5/93
33.\"
34.Dd June 5, 1993
35.Dt DMC 4 vax
36.Os BSD 4.2
37.Sh NAME
38.Nm dmc
39.Nd
40.Tn DEC
41.Tn DMC-11 Ns / Tn DMR-11
42point-to-point communications device
43.Sh SYNOPSIS
44.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint"
45.Sh DESCRIPTION
46The
47.Nm dmc
48interface provides access to a point-to-point communications
49device which runs at either 1 Mb/s or 56 Kb/s.
50.Tn DMC-11 Ns s
51communicate
52using the
53.Tn DEC DDCMP
54link layer protocol.
55.Pp
56The
57.Nm dmc
58interface driver also supports a
59.Tn DEC
60.Tn DMR-11
61providing point-to-point
62communication running at data rates from 2.4 Kb/s to 1 Mb/s.
63.Tn DMR-11 Ns s
64are a more recent design and thus are preferred over
65.Tn DMC-11 Ns s .
66The
67.Dv NXMT
68and
69.Dv NRCV
70constants in the driver may be increased in this case,
71as the
72.Tn DMR
73can accept up to 64 transmit and receive buffers, as opposed
74to 7 for the
75.Tn DMC .
76.Pp
77The configuration flags specify how to set up the device,
78.Bl -column xxx -offset indent
790	full duplex DDCMP (normal mode)
801	DDCMP Maintence mode (generally useless)
812	DDCMP Half Duplex, primary station
823	DDCMP Half Duplex, secondary station
83.El
84.Pp
85Several device error counters are available via
86.Xr adb 1 ,
87for
88more information see the
89.Xr adb
90script
91.Pa /usr/lib/adb/dmcstats ,
92or the
93.Tn DMC-11
94technical manual.
95.Pp
96The host's address must be specified with an
97.Dv SIOCSIFADDR
98.Xr ioctl 2 ,
99and the destination address specified with a
100.Dv SIOCSIFDSTADDR
101.Xr ioctl ,
102before the interface will transmit or receive any packets.
103.Sh ROUTING
104The driver places a
105.Tn HOST
106entry in the kernel routing tables for the
107address given in the
108.Dv SIOCSIFDSTADDR
109.Xr ioctl.
110To use the
111.Tn DMC
112as a
113link between local nets, the route to the remote net must be added manually
114with the
115.Xr route 8
116command, or by the use of the routing process
117.Xr routed 8
118on each end of the link.
119.Sh DIAGNOSTICS
120.Bl -diag
121.It dmc%d: bad control %o.
122A bad parameter was passed to the
123.Em dmcload
124routine.
125.Pp
126.It dmc%d: unknown address type %d.
127An input packet was received which contained a type of
128address unknown to the driver.
129.Pp
130.It DMC fatal error 0%o.
131A fatal error in
132.Tn DDMCP
133occurred, causing the device to be restarted.
134.Pp
135.It DMC soft error 0%o.
136A non-fatal error in
137.Tn DDMCP
138has occurred.
139.Pp
140.It dmc%d: af%d not supported.
141The interface was handed a message which has
142addresses formatted in an unsuitable address family.
143.El
144.Sh SEE ALSO
145.Xr intro 4 ,
146.Xr inet 4
147.Sh HISTORY
148The
149.Nm
150driver appeared in
151.Bx 4.2 .
152.Sh BUGS
153The current version of the driver uses a link-level encapsulation
154so that multiple protocol types may be used.
155It is thus incompatible with earlier drivers,
156including the
157.Bx 4.2
158version.
159