.\" Copyright (c) 1983, 1991 Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 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.
.\" 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
.\" @(#)dmc.4 6.5 (Berkeley) 3/27/91
.Tn DMC-11 Ns / Tn DMR-11
point-to-point communications device
.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint"
interface provides access to a point-to-point communications
device which runs at either 1 Mb/s or 56 Kb/s.
interface driver also supports a
communication running at data rates from 2.4 Kb/s to 1 Mb/s.
are a more recent design and thus are preferred over
constants in the driver may be increased in this case,
can accept up to 64 transmit and receive buffers, as opposed
The configuration flags specify how to set up the device,
.Bl -column xxx -offset indent
0 full duplex DDCMP (normal mode)
1 DDCMP Maintence mode (generally useless)
2 DDCMP Half Duplex, primary station
3 DDCMP Half Duplex, secondary station
Several device error counters are available via
.Pa /usr/lib/adb/dmcstats ,
The host's address must be specified with an
and the destination address specified with a
before the interface will transmit or receive any packets.
entry in the kernel routing tables for the
link between local nets, the route to the remote net must be added manually
command, or by the use of the routing process
.It dmc%d: bad control %o.
A bad parameter was passed to the
.It dmc%d: unknown address type %d.
An input packet was received which contained a type of
address unknown to the driver.
occurred, causing the device to be restarted.
.It dmc%d: af%d not supported.
The interface was handed a message which has
addresses formatted in an unsuitable address family.
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,