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