summaryrefslogtreecommitdiff
path: root/static/netbsd/man4/man4.vax/dmc.4 4.html
blob: 4af84275cc22cb62135e857206a3225075e76edf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
<table class="head">
  <tr>
    <td class="head-ltitle">DMC(4)</td>
    <td class="head-vol">Device Drivers Manual (vax)</td>
    <td class="head-rtitle">DMC(4)</td>
  </tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">dmc</code> &#x2014; <span class="Nd">DEC
    DMC-11/DMR-11 point-to-point serial communications device</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">dmc0 at uba0 csr 167600</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">NOTE: This driver has not been ported from
    <span class="Ux">4.4BSD</span> yet.</p>
<p class="Pp">The <code class="Nm">dmc</code> interface provides access to a
    point-to-point communications device which runs at either 1 Mb/s or 56 Kb/s.
    DMC-11s communicate using the DEC DDCMP link layer protocol.</p>
<p class="Pp">The <code class="Nm">dmc</code> 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-11s are a more recent design and thus are preferred
    over DMC-11s. The <code class="Dv">NXMT</code> and
    <code class="Dv">NRCV</code> constants in the driver may be increased in
    this case, as the DMR can accept up to 64 transmit and receive buffers, as
    opposed to 7 for the DMC.</p>
<p class="Pp">The configuration flags specify how to set up the device,</p>
<table class="Bl-column Bd-indent">
  <tr>
    <td>0</td>
    <td>full duplex DDCMP (normal mode)</td>
  </tr>
  <tr>
    <td>1</td>
    <td>DDCMP Maintenance mode (generally useless)</td>
  </tr>
  <tr>
    <td>2</td>
    <td>DDCMP Half Duplex, primary station</td>
  </tr>
  <tr>
    <td>3</td>
    <td>DDCMP Half Duplex, secondary station</td>
  </tr>
</table>
The host's address must be specified with an <code class="Dv">SIOCSIFADDR</code>
  <a class="Xr">ioctl(2)</a>, and the destination address specified with a
  <code class="Dv">SIOCSIFDSTADDR</code> <a class="Xr">ioctl(2)</a>, before the
  interface will transmit or receive any packets.
</section>
<section class="Sh">
<h1 class="Sh" id="ROUTING"><a class="permalink" href="#ROUTING">ROUTING</a></h1>
<p class="Pp">The driver places a HOST entry in the kernel routing tables for
    the address given in the <code class="Dv">SIOCSIFDSTADDR</code>
    <a class="Xr">ioctl(2)</a>. To use the DMC as a link between local nets, the
    route to the remote net must be added manually with the
    <a class="Xr">route(8)</a> command, or by the use of the routing process
    <a class="Xr">routed(8)</a> on each end of the link.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
  <dt id="dmcload">dmc%d: bad control %o.</dt>
  <dd>A bad parameter was passed to the
      <a class="permalink" href="#dmcload"><i class="Em">dmcload</i></a>
      routine.</dd>
  <dt>dmc%d: unknown address type %d.</dt>
  <dd>An input packet was received which contained a type of address unknown to
      the driver.</dd>
  <dt>DMC fatal error 0%o.</dt>
  <dd>A fatal error in DDMCP occurred, causing the device to be restarted.</dd>
  <dt>DMC soft error 0%o.</dt>
  <dd>A non-fatal error in DDMCP has occurred.</dd>
  <dt>dmc%d: af%d not supported.</dt>
  <dd>The interface was handed a message which has addresses formatted in an
      unsuitable address family.</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
  ALSO</a></h1>
<p class="Pp"><a class="Xr">inet(4)</a>, <a class="Xr">vax/intro(4)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">dmc</code> driver appeared in
    <span class="Ux">4.2BSD</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
<p class="Pp">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 <span class="Ux">4.2BSD</span> version.</p>
</section>
</div>
<table class="foot">
  <tr>
    <td class="foot-date">February 17, 2017</td>
    <td class="foot-os">NetBSD 10.1</td>
  </tr>
</table>