1.\" Copyright (c) 1983, 1991 Regents of the University of California. 2.\" 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.\" from: @(#)dmc.4 6.5 (Berkeley) 3/27/91 33.\" $Id: dmc.4,v 1.2 1993/08/01 07:36:29 mycroft Exp $ 34.\" 35.Dd March 27, 1991 36.Dt DMC 4 vax 37.Os BSD 4.2 38.Sh NAME 39.Nm dmc 40.Nd 41.Tn DEC 42.Tn DMC-11 Ns / Tn DMR-11 43point-to-point communications device 44.Sh SYNOPSIS 45.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint" 46.Sh DESCRIPTION 47The 48.Nm dmc 49interface provides access to a point-to-point communications 50device which runs at either 1 Mb/s or 56 Kb/s. 51.Tn DMC-11 Ns s 52communicate 53using the 54.Tn DEC DDCMP 55link layer protocol. 56.Pp 57The 58.Nm dmc 59interface driver also supports a 60.Tn DEC 61.Tn DMR-11 62providing point-to-point 63communication running at data rates from 2.4 Kb/s to 1 Mb/s. 64.Tn DMR-11 Ns s 65are a more recent design and thus are preferred over 66.Tn DMC-11 Ns s . 67The 68.Dv NXMT 69and 70.Dv NRCV 71constants in the driver may be increased in this case, 72as the 73.Tn DMR 74can accept up to 64 transmit and receive buffers, as opposed 75to 7 for the 76.Tn DMC . 77.Pp 78The configuration flags specify how to set up the device, 79.Bl -column xxx -offset indent 800 full duplex DDCMP (normal mode) 811 DDCMP Maintence mode (generally useless) 822 DDCMP Half Duplex, primary station 833 DDCMP Half Duplex, secondary station 84.El 85.Pp 86Several device error counters are available via 87.Xr adb 1 , 88for 89more information see the 90.Xr adb 91script 92.Pa /usr/lib/adb/dmcstats , 93or the 94.Tn DMC-11 95technical manual. 96.Pp 97The host's address must be specified with an 98.Dv SIOCSIFADDR 99.Xr ioctl 2 , 100and the destination address specified with a 101.Dv SIOCSIFDSTADDR 102.Xr ioctl , 103before the interface will transmit or receive any packets. 104.Sh ROUTING 105The driver places a 106.Tn HOST 107entry in the kernel routing tables for the 108address given in the 109.Dv SIOCSIFDSTADDR 110.Xr ioctl. 111To use the 112.Tn DMC 113as a 114link between local nets, the route to the remote net must be added manually 115with the 116.Xr route 8 117command, or by the use of the routing process 118.Xr routed 8 119on each end of the link. 120.Sh DIAGNOSTICS 121.Bl -diag 122.It dmc%d: bad control %o. 123A bad parameter was passed to the 124.Em dmcload 125routine. 126.Pp 127.It dmc%d: unknown address type %d. 128An input packet was received which contained a type of 129address unknown to the driver. 130.Pp 131.It DMC fatal error 0%o. 132A fatal error in 133.Tn DDMCP 134occurred, causing the device to be restarted. 135.Pp 136.It DMC soft error 0%o. 137A non-fatal error in 138.Tn DDMCP 139has occurred. 140.Pp 141.It dmc%d: af%d not supported. 142The interface was handed a message which has 143addresses formatted in an unsuitable address family. 144.El 145.Sh SEE ALSO 146.Xr intro 4 , 147.Xr inet 4 148.Sh HISTORY 149The 150.Nm 151driver appeared in 152.Bx 4.2 . 153.Sh BUGS 154The current version of the driver uses a link-level encapsulation 155so that multiple protocol types may be used. 156It is thus incompatible with earlier drivers, 157including the 158.Bx 4.2 159version. 160