1*47674Scael.\" Copyright (c) 1983, 1991 Regents of the University of California. 2*47674Scael.\" All rights reserved. 320710Smckusick.\" 4*47674Scael.\" %sccs.include.redist.man% 520710Smckusick.\" 6*47674Scael.\" @(#)dmc.4 6.5 (Berkeley) 03/27/91 7*47674Scael.\" 8*47674Scael.Dd 9*47674Scael.Dt DMC 4 vax 10*47674Scael.Os BSD 4.2 11*47674Scael.Sh NAME 12*47674Scael.Nm dmc 13*47674Scael.Nd 14*47674Scael.Tn DEC 15*47674Scael.Tn DMC-11 Ns / Tn DMR-11 16*47674Scaelpoint-to-point communications device 17*47674Scael.Sh SYNOPSIS 18*47674Scael.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint" 19*47674Scael.Sh DESCRIPTION 2020710SmckusickThe 21*47674Scael.Nm dmc 2220710Smckusickinterface provides access to a point-to-point communications 23*47674Scaeldevice which runs at either 1 Mb/s or 56 Kb/s. 24*47674Scael.Tn DMC-11 Ns s 25*47674Scaelcommunicate 26*47674Scaelusing the 27*47674Scael.Tn DEC DDCMP 28*47674Scaellink layer protocol. 29*47674Scael.Pp 3020710SmckusickThe 31*47674Scael.Nm dmc 32*47674Scaelinterface driver also supports a 33*47674Scael.Tn DEC 34*47674Scael.Tn DMR-11 35*47674Scaelproviding point-to-point 3620710Smckusickcommunication running at data rates from 2.4 Kb/s to 1 Mb/s. 37*47674Scael.Tn DMR-11 Ns s 38*47674Scaelare a more recent design and thus are preferred over 39*47674Scael.Tn DMC-11 Ns s . 40*47674ScaelThe 41*47674Scael.Dv NXMT 42*47674Scaeland 43*47674Scael.Dv NRCV 44*47674Scaelconstants in the driver may be increased in this case, 45*47674Scaelas the 46*47674Scael.Tn DMR 47*47674Scaelcan accept up to 64 transmit and receive buffers, as opposed 48*47674Scaelto 7 for the 49*47674Scael.Tn DMC . 50*47674Scael.Pp 51*47674ScaelThe configuration flags specify how to set up the device, 52*47674Scael.Bl -column xxx -offset indent 53*47674Scael0 full duplex DDCMP (normal mode) 54*47674Scael1 DDCMP Maintence mode (generally useless) 55*47674Scael2 DDCMP Half Duplex, primary station 56*47674Scael3 DDCMP Half Duplex, secondary station 57*47674Scael.El 58*47674Scael.Pp 59*47674ScaelSeveral device error counters are available via 60*47674Scael.Xr adb 1 , 61*47674Scaelfor 62*47674Scaelmore information see the 63*47674Scael.Xr adb 64*47674Scaelscript 65*47674Scael.Pa /usr/lib/adb/dmcstats , 66*47674Scaelor the 67*47674Scael.Tn DMC-11 68*47674Scaeltechnical manual. 69*47674Scael.Pp 70*47674ScaelThe host's address must be specified with an 71*47674Scael.Dv SIOCSIFADDR 72*47674Scael.Xr ioctl 2 , 73*47674Scaeland the destination address specified with a 74*47674Scael.Dv SIOCSIFDSTADDR 75*47674Scael.Xr ioctl , 7628260Skarelsbefore the interface will transmit or receive any packets. 77*47674Scael.Sh ROUTING 78*47674ScaelThe driver places a 79*47674Scael.Tn HOST 80*47674Scaelentry in the kernel routing tables for the 81*47674Scaeladdress given in the 82*47674Scael.Dv SIOCSIFDSTADDR 83*47674Scael.Xr ioctl. 84*47674ScaelTo use the 85*47674Scael.Tn DMC 86*47674Scaelas a 8728260Skarelslink between local nets, the route to the remote net must be added manually 8828260Skarelswith the 89*47674Scael.Xr route 8 9028260Skarelscommand, or by the use of the routing process 91*47674Scael.Xr routed 8 9228260Skarelson each end of the link. 93*47674Scael.Sh DIAGNOSTICS 94*47674Scael.Bl -diag 95*47674Scael.It dmc%d: bad control %o. 9620710SmckusickA bad parameter was passed to the 97*47674Scael.Em dmcload 9820710Smckusickroutine. 99*47674Scael.Pp 100*47674Scael.It dmc%d: unknown address type %d. 10120710SmckusickAn input packet was received which contained a type of 10220710Smckusickaddress unknown to the driver. 103*47674Scael.Pp 104*47674Scael.It DMC fatal error 0%o. 105*47674ScaelA fatal error in 106*47674Scael.Tn DDMCP 107*47674Scaeloccurred, causing the device to be restarted. 108*47674Scael.Pp 109*47674Scael.It DMC soft error 0%o. 110*47674ScaelA non-fatal error in 111*47674Scael.Tn DDMCP 112*47674Scaelhas occurred. 113*47674Scael.Pp 114*47674Scael.It dmc%d: af%d not supported. 11520710SmckusickThe interface was handed a message which has 11620710Smckusickaddresses formatted in an unsuitable address family. 117*47674Scael.El 118*47674Scael.Sh SEE ALSO 119*47674Scael.Xr intro 4 , 120*47674Scael.Xr inet 4 121*47674Scael.Sh HISTORY 122*47674ScaelThe 123*47674Scael.Nm 124*47674Scaeldriver appeared in 125*47674Scael.Bx 4.2 . 126*47674Scael.Sh BUGS 12728260SkarelsThe current version of the driver uses a link-level encapsulation 12828260Skarelsso that multiple protocol types may be used. 12928260SkarelsIt is thus incompatible with earlier drivers, 130*47674Scaelincluding the 131*47674Scael.Bx 4.2 132*47674Scaelversion. 133