1*61595Sbostic.\" Copyright (c) 1983, 1991, 1993 2*61595Sbostic.\" The Regents of the University of California. All rights reserved. 320710Smckusick.\" 447674Scael.\" %sccs.include.redist.man% 520710Smckusick.\" 6*61595Sbostic.\" @(#)dmc.4 8.1 (Berkeley) 06/05/93 747674Scael.\" 847674Scael.Dd 947674Scael.Dt DMC 4 vax 1047674Scael.Os BSD 4.2 1147674Scael.Sh NAME 1247674Scael.Nm dmc 1347674Scael.Nd 1447674Scael.Tn DEC 1547674Scael.Tn DMC-11 Ns / Tn DMR-11 1647674Scaelpoint-to-point communications device 1747674Scael.Sh SYNOPSIS 1847674Scael.Cd "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint" 1947674Scael.Sh DESCRIPTION 2020710SmckusickThe 2147674Scael.Nm dmc 2220710Smckusickinterface provides access to a point-to-point communications 2347674Scaeldevice which runs at either 1 Mb/s or 56 Kb/s. 2447674Scael.Tn DMC-11 Ns s 2547674Scaelcommunicate 2647674Scaelusing the 2747674Scael.Tn DEC DDCMP 2847674Scaellink layer protocol. 2947674Scael.Pp 3020710SmckusickThe 3147674Scael.Nm dmc 3247674Scaelinterface driver also supports a 3347674Scael.Tn DEC 3447674Scael.Tn DMR-11 3547674Scaelproviding point-to-point 3620710Smckusickcommunication running at data rates from 2.4 Kb/s to 1 Mb/s. 3747674Scael.Tn DMR-11 Ns s 3847674Scaelare a more recent design and thus are preferred over 3947674Scael.Tn DMC-11 Ns s . 4047674ScaelThe 4147674Scael.Dv NXMT 4247674Scaeland 4347674Scael.Dv NRCV 4447674Scaelconstants in the driver may be increased in this case, 4547674Scaelas the 4647674Scael.Tn DMR 4747674Scaelcan accept up to 64 transmit and receive buffers, as opposed 4847674Scaelto 7 for the 4947674Scael.Tn DMC . 5047674Scael.Pp 5147674ScaelThe configuration flags specify how to set up the device, 5247674Scael.Bl -column xxx -offset indent 5347674Scael0 full duplex DDCMP (normal mode) 5447674Scael1 DDCMP Maintence mode (generally useless) 5547674Scael2 DDCMP Half Duplex, primary station 5647674Scael3 DDCMP Half Duplex, secondary station 5747674Scael.El 5847674Scael.Pp 5947674ScaelSeveral device error counters are available via 6047674Scael.Xr adb 1 , 6147674Scaelfor 6247674Scaelmore information see the 6347674Scael.Xr adb 6447674Scaelscript 6547674Scael.Pa /usr/lib/adb/dmcstats , 6647674Scaelor the 6747674Scael.Tn DMC-11 6847674Scaeltechnical manual. 6947674Scael.Pp 7047674ScaelThe host's address must be specified with an 7147674Scael.Dv SIOCSIFADDR 7247674Scael.Xr ioctl 2 , 7347674Scaeland the destination address specified with a 7447674Scael.Dv SIOCSIFDSTADDR 7547674Scael.Xr ioctl , 7628260Skarelsbefore the interface will transmit or receive any packets. 7747674Scael.Sh ROUTING 7847674ScaelThe driver places a 7947674Scael.Tn HOST 8047674Scaelentry in the kernel routing tables for the 8147674Scaeladdress given in the 8247674Scael.Dv SIOCSIFDSTADDR 8347674Scael.Xr ioctl. 8447674ScaelTo use the 8547674Scael.Tn DMC 8647674Scaelas a 8728260Skarelslink between local nets, the route to the remote net must be added manually 8828260Skarelswith the 8947674Scael.Xr route 8 9028260Skarelscommand, or by the use of the routing process 9147674Scael.Xr routed 8 9228260Skarelson each end of the link. 9347674Scael.Sh DIAGNOSTICS 9447674Scael.Bl -diag 9547674Scael.It dmc%d: bad control %o. 9620710SmckusickA bad parameter was passed to the 9747674Scael.Em dmcload 9820710Smckusickroutine. 9947674Scael.Pp 10047674Scael.It dmc%d: unknown address type %d. 10120710SmckusickAn input packet was received which contained a type of 10220710Smckusickaddress unknown to the driver. 10347674Scael.Pp 10447674Scael.It DMC fatal error 0%o. 10547674ScaelA fatal error in 10647674Scael.Tn DDMCP 10747674Scaeloccurred, causing the device to be restarted. 10847674Scael.Pp 10947674Scael.It DMC soft error 0%o. 11047674ScaelA non-fatal error in 11147674Scael.Tn DDMCP 11247674Scaelhas occurred. 11347674Scael.Pp 11447674Scael.It dmc%d: af%d not supported. 11520710SmckusickThe interface was handed a message which has 11620710Smckusickaddresses formatted in an unsuitable address family. 11747674Scael.El 11847674Scael.Sh SEE ALSO 11947674Scael.Xr intro 4 , 12047674Scael.Xr inet 4 12147674Scael.Sh HISTORY 12247674ScaelThe 12347674Scael.Nm 12447674Scaeldriver appeared in 12547674Scael.Bx 4.2 . 12647674Scael.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, 13047674Scaelincluding the 13147674Scael.Bx 4.2 13247674Scaelversion. 133