Commit | Line | Data |
---|---|---|
5ebe7d4b KB |
1 | .\" Copyright (c) 1983, 1991, 1993 |
2 | .\" The Regents of the University of California. All rights reserved. | |
be5b365a | 3 | .\" |
9903e566 | 4 | .\" %sccs.include.redist.man% |
be5b365a | 5 | .\" |
5ebe7d4b | 6 | .\" @(#)dmc.4 8.1 (Berkeley) %G% |
9903e566 CL |
7 | .\" |
8 | .Dd | |
9 | .Dt DMC 4 vax | |
10 | .Os BSD 4.2 | |
11 | .Sh NAME | |
12 | .Nm dmc | |
13 | .Nd | |
14 | .Tn DEC | |
15 | .Tn DMC-11 Ns / Tn DMR-11 | |
16 | point-to-point communications device | |
17 | .Sh SYNOPSIS | |
18 | .Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint" | |
19 | .Sh DESCRIPTION | |
be5b365a | 20 | The |
9903e566 | 21 | .Nm dmc |
be5b365a | 22 | interface provides access to a point-to-point communications |
9903e566 CL |
23 | device which runs at either 1 Mb/s or 56 Kb/s. |
24 | .Tn DMC-11 Ns s | |
25 | communicate | |
26 | using the | |
27 | .Tn DEC DDCMP | |
28 | link layer protocol. | |
29 | .Pp | |
be5b365a | 30 | The |
9903e566 CL |
31 | .Nm dmc |
32 | interface driver also supports a | |
33 | .Tn DEC | |
34 | .Tn DMR-11 | |
35 | providing point-to-point | |
be5b365a | 36 | communication running at data rates from 2.4 Kb/s to 1 Mb/s. |
9903e566 CL |
37 | .Tn DMR-11 Ns s |
38 | are a more recent design and thus are preferred over | |
39 | .Tn DMC-11 Ns s . | |
40 | The | |
41 | .Dv NXMT | |
42 | and | |
43 | .Dv NRCV | |
44 | constants in the driver may be increased in this case, | |
45 | as the | |
46 | .Tn DMR | |
47 | can accept up to 64 transmit and receive buffers, as opposed | |
48 | to 7 for the | |
49 | .Tn DMC . | |
50 | .Pp | |
51 | The configuration flags specify how to set up the device, | |
52 | .Bl -column xxx -offset indent | |
53 | 0 full duplex DDCMP (normal mode) | |
54 | 1 DDCMP Maintence mode (generally useless) | |
55 | 2 DDCMP Half Duplex, primary station | |
56 | 3 DDCMP Half Duplex, secondary station | |
57 | .El | |
58 | .Pp | |
59 | Several device error counters are available via | |
60 | .Xr adb 1 , | |
61 | for | |
62 | more information see the | |
63 | .Xr adb | |
64 | script | |
65 | .Pa /usr/lib/adb/dmcstats , | |
66 | or the | |
67 | .Tn DMC-11 | |
68 | technical manual. | |
69 | .Pp | |
70 | The host's address must be specified with an | |
71 | .Dv SIOCSIFADDR | |
72 | .Xr ioctl 2 , | |
73 | and the destination address specified with a | |
74 | .Dv SIOCSIFDSTADDR | |
75 | .Xr ioctl , | |
86703e53 | 76 | before the interface will transmit or receive any packets. |
9903e566 CL |
77 | .Sh ROUTING |
78 | The driver places a | |
79 | .Tn HOST | |
80 | entry in the kernel routing tables for the | |
81 | address given in the | |
82 | .Dv SIOCSIFDSTADDR | |
83 | .Xr ioctl. | |
84 | To use the | |
85 | .Tn DMC | |
86 | as a | |
86703e53 MK |
87 | link between local nets, the route to the remote net must be added manually |
88 | with the | |
9903e566 | 89 | .Xr route 8 |
86703e53 | 90 | command, or by the use of the routing process |
9903e566 | 91 | .Xr routed 8 |
86703e53 | 92 | on each end of the link. |
9903e566 CL |
93 | .Sh DIAGNOSTICS |
94 | .Bl -diag | |
95 | .It dmc%d: bad control %o. | |
be5b365a | 96 | A bad parameter was passed to the |
9903e566 | 97 | .Em dmcload |
be5b365a | 98 | routine. |
9903e566 CL |
99 | .Pp |
100 | .It dmc%d: unknown address type %d. | |
be5b365a KM |
101 | An input packet was received which contained a type of |
102 | address unknown to the driver. | |
9903e566 CL |
103 | .Pp |
104 | .It DMC fatal error 0%o. | |
105 | A fatal error in | |
106 | .Tn DDMCP | |
107 | occurred, causing the device to be restarted. | |
108 | .Pp | |
109 | .It DMC soft error 0%o. | |
110 | A non-fatal error in | |
111 | .Tn DDMCP | |
112 | has occurred. | |
113 | .Pp | |
114 | .It dmc%d: af%d not supported. | |
be5b365a KM |
115 | The interface was handed a message which has |
116 | addresses formatted in an unsuitable address family. | |
9903e566 CL |
117 | .El |
118 | .Sh SEE ALSO | |
119 | .Xr intro 4 , | |
120 | .Xr inet 4 | |
121 | .Sh HISTORY | |
122 | The | |
123 | .Nm | |
124 | driver appeared in | |
125 | .Bx 4.2 . | |
126 | .Sh BUGS | |
86703e53 MK |
127 | The current version of the driver uses a link-level encapsulation |
128 | so that multiple protocol types may be used. | |
129 | It is thus incompatible with earlier drivers, | |
9903e566 CL |
130 | including the |
131 | .Bx 4.2 | |
132 | version. |