1ACC(4) Kernel Interfaces Manual ACC(4)
2
6 acc - ACC LH/DH IMP interface
7
9 /sys/conf/SYSTEM:
10 NACC 0 # ACC LH/DH ARPAnet IMP interface
11 PLI YES # LH/DH is connected to a PLI
12
14 The acc device provides a Local Host/Distant Host interface to an IMP.
15 It is normally used when participating in the DARPA Internet. The con‐
16 troller itself is not accessible to users, but instead provides the
17 hardware support to the IMP interface described in imp(4). When con‐
18 figuring, the imp(NIMP) pseudo-device must also be included.
19
21 acc%d: not alive. The initialization routine was entered even though
22 the device did not autoconfigure. This indicates a system problem.
23 acc%d: can't initialize. Insufficient UNIBUS resources existed to ini‐
25 tialize the device. This is likely to occur when the device is run on
26 a buffered data path on an 11/750 and other network interfaces are also
27 configured to use buffered data paths, or when it is configured to use
28 buffered data paths on an 11/730 (which has none).
29 acc%d: imp doesn't respond, icsr=%b. The driver attempted to initial‐
31 ize the device, but the IMP failed to respond after 500 tries. Check
32 the cabling.
33 acc%d: stray xmit interrupt, csr=%b. An interrupt occurred when no
35 output had previously been started.
36 acc%d: output error, ocsr=%b, icsr=%b. The device indicated a problem
38 sending data on output.
39 acc%d: input error, csr=%b. The device indicated a problem receiving
41 data on input.
42 acc%d: bad length=%d. An input operation resulted in a data transfer
44 of less than 0 or more than 1008 bytes of data into memory (according
45 to the word count register). This should never happen as the maximum
46 size of a host-IMP message is 1008 bytes.
473rd Berkeley Distribution July 26, 1987 ACC(4)