1*47674Scael.\" Copyright (c) 1983, 1991 The Regents of the University of California. 236756Sbostic.\" All rights reserved. 320704Smckusick.\" 443582Strent.\" %sccs.include.redist.man% 520704Smckusick.\" 6*47674Scael.\" @(#)acc.4 6.4 (Berkeley) 03/27/91 736756Sbostic.\" 8*47674Scael.Dd 9*47674Scael.Dt ACC 4 vax 10*47674Scael.Os BSD 4.2 11*47674Scael.Sh NAME 12*47674Scael.Nm acc 13*47674Scael.Nd 14*47674Scael.Tn ACC LH/DH IMP 15*47674Scaelinterface 16*47674Scael.Sh SYNOPSIS 17*47674Scael.Cd pseudo-device imp "device acc0 at uba0 csr 167600 vector accrint accxint" 18*47674Scael.Sh DESCRIPTION 1920704SmckusickThe 20*47674Scael.Nm acc 2120704Smckusickdevice provides a Local Host/Distant Host 22*47674Scaelinterface to an 23*47674Scael.Tn IMP . 24*47674ScaelIt is normally used when participating 25*47674Scaelin the 26*47674Scael.Tn DARPA 27*47674ScaelInternet. The controller itself is not accessible 28*47674Scaelto users, but instead provides the hardware support to the 29*47674Scael.Tn IMP 3020704Smckusickinterface described in 31*47674Scael.Xr imp 4 . 32*47674ScaelThe configuration entry for the 33*47674Scael.Xr imp 34*47674Scaelmust also include the 35*47674Scael.Em pseudo-device 36*47674Scaelas shown above. 37*47674Scael.Sh DIAGNOSTICS 38*47674Scael.Bl -diag 39*47674Scael.It acc%d: not alive. 4020704SmckusickThe initialization routine was entered even though the device 4120704Smckusickdid not autoconfigure. This indicates a system problem. 42*47674Scael.Pp 43*47674Scael.It acc%d: can't initialize. 4420704SmckusickInsufficient UNIBUS resources existed to initialize the device. 4520704SmckusickThis is likely to occur when the device is run on a buffered 4620704Smckusickdata path on an 11/750 and other network interfaces are also 4720704Smckusickconfigured to use buffered data paths, or when it is configured 4820704Smckusickto use buffered data paths on an 11/730 (which has none). 49*47674Scael.Pp 50*47674Scael.It acc%d: imp doesn't respond, icsr=%b. 51*47674ScaelThe driver attempted to initialize the device, but the 52*47674Scael.Tn IMP 5320704Smckusickfailed to respond after 500 tries. Check the cabling. 54*47674Scael.Pp 55*47674Scael.It acc%d: stray xmit interrupt, csr=%b. 5620704SmckusickAn interrupt occurred when no output had previously been started. 57*47674Scael.Pp 58*47674Scael.It acc%d: output error, ocsr=%b, icsr=%b. 5920704SmckusickThe device indicated a problem sending data on output. 60*47674Scael.Pp 61*47674Scael.It acc%d: input error, csr=%b. 6220704SmckusickThe device indicated a problem receiving data on input. 63*47674Scael.Pp 64*47674Scael.It acc%d: bad length=%d. 6520704SmckusickAn input operation resulted in a data transfer of less than 6620704Smckusick0 or more than 1008 bytes of 6720704Smckusickdata into memory (according to the word count register). 68*47674ScaelThis should never happen as the maximum size of a 69*47674Scael.Pf host- Tn IMP 7020704Smckusickmessage is 1008 bytes. 71*47674Scael.El 72*47674Scael.Sh SEE ALSO 73*47674Scael.Xr netintro 4 74*47674Scael.Sh HISTORY 75*47674ScaelThe 76*47674Scael.Nm 77*47674Scaelinterface appeared in 78*47674Scael.Bx 4.2 . 79