Commit | Line | Data |
---|---|---|
0cd9fa61 C |
1 | .TH CSS 4 "27 July 1983" |
2 | .UC 4 | |
3 | .SH NAME | |
4 | css \- DEC IMP-11A LH/DH IMP interface | |
5 | .SH SYNOPSIS | |
6 | .B "pseudo-device imp" | |
7 | .br | |
8 | .B "device css0 at uba0 csr 167600 flags 10 vector cssrint cssxint" | |
9 | .SH DESCRIPTION | |
10 | The | |
11 | .I css | |
12 | device provides a Local Host/Distant Host | |
13 | interface to an IMP. It is normally used when participating | |
14 | in the DARPA Internet. The controller itself is not accessible | |
15 | to users, but instead provides the hardware support to the IMP | |
16 | interface described in | |
17 | .IR imp (4). | |
18 | When configuring, the | |
19 | .I imp | |
20 | pseudo-device is also included. | |
21 | .SH DIAGNOSTICS | |
22 | .BR "css%d: not alive" . | |
23 | The initialization routine was entered even though the device | |
24 | did not autoconfigure. This is indicates a system problem. | |
25 | .PP | |
26 | .BR "css%d: can't initialize" . | |
27 | Insufficient UNIBUS resources existed to initialize the device. | |
28 | This is likely to occur when the device is run on a buffered | |
29 | data path on an 11/750 and other network interfaces are also | |
30 | configured to use buffered data paths, or when it is configured | |
31 | to use buffered data paths on an 11/730 (which has none). | |
32 | .PP | |
33 | .BR "css%d: imp doesn't respond, icsr=%b" . | |
34 | The driver attempted to initialize the device, but the IMP | |
35 | failed to respond after 500 tries. Check the cabling. | |
36 | .PP | |
37 | .BR "css%d: stray output interrupt csr=%b" . | |
38 | An interrupt occurred when no output had previously been started. | |
39 | .PP | |
40 | .BR "css%d: output error, ocsr=%b icsr=%b" . | |
41 | The device indicated a problem sending data on output. | |
42 | .PP | |
43 | .BR "css%d: recv error, csr=%b" . | |
44 | The device indicated a problem receiving data on input. | |
45 | .PP | |
46 | .BR "css%d: bad length=%d" . | |
47 | An input operation resulted in a data transfer of less than | |
48 | 0 or more than 1008 bytes of | |
49 | data into memory (according to the word count register). | |
50 | This should never happen as the maximum size of a host-IMP | |
51 | message is 1008 bytes. |