|
|
1.1 root 1: .\" @(#)hdh.4 6.1 (Berkeley) 8/8/85
2: .\"
3: .TH HDH 4 "August 8, 1985"
4: .UC 6
5: .SH NAME
6: hdh \- ACC IF-11/HDH IMP interface
7: .SH SYNOPSIS
8: .B "pseudo-device imp"
9: .br
10: .B "device hdh0 at uba0 csr 166740 vector hdhintr"
11: .SH DESCRIPTION
12: The
13: .I hdh
14: device provides an HDLC Host (HDH)
15: interface to an IMP. It is normally used when participating
16: in the DARPA Internet. The controller itself is not accessible
17: to users, but instead provides the hardware support to the IMP
18: interface described in
19: .IR imp (4).
20: When configuring, the
21: .I imp
22: pseudo-device must also be included.
23: .SH DIAGNOSTICS
24: .BR "hdh%d: not alive" .
25: The initialization routine was entered even though the device
26: did not autoconfigure. This indicates a system problem.
27: .PP
28: .BR "hdh%d: cannot get chan %d uba resources" .
29: Insufficient UNIBUS resources existed to initialize the device.
30: This is likely to be a shortage of UNIBUS mapping registers.
31: .PP
32: .BR "hdh%d: LINE UP" .
33: This indicates that both the HDLC and HDH protocols have declared the
34: link to the IMP alive.
35: .PP
36: .BR "hdh%d: LINE DOWN" .
37: This indicates that the link to the IMP has died.
38: .PP
39: .BR "hdh%d: HOST SEQUENCE ERROR"
40: .br
41: .BR "hdh%d: IMP SEQUENCE ERROR"
42: .br
43: .BR "hdh%d: HOST DATA ERROR"
44: .br
45: .BR "hdh%d: TIMEOUT"
46: .br
47: These errors indicate that an HDH protocol error has been detected.
48: .PP
49: .BR "hdh%d: cannot get supervisor cmnd buffer" .
50: This error indicates that an
51: .I mbuf
52: could not be allocated to send a command to the IF-11/HDH.
53: .PP
54: Any other error message from hdh%d: indicates a serious error
55: detected by either the driver or the IF-11/HDH firmware.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.