xref: /netbsd/share/man/man4/man4.vax/css.4 (revision bf9ec67e)
1.\"	$NetBSD: css.4,v 1.9 2001/08/18 12:05:25 wiz Exp $
2.\"
3.\" Copyright (c) 1983, 1991, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by the University of
17.\"	California, Berkeley and its contributors.
18.\" 4. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     from: @(#)css.4	8.1 (Berkeley) 6/5/93
35.\"
36.Dd June 5, 1993
37.Dt CSS 4 vax
38.Os
39.Sh NAME
40.Nm css
41.Nd
42.Tn DEC IMP-11A LH/DH IMP
43network interface
44.Sh SYNOPSIS
45.Cd "pseudo-device imp device css0 \&at uba0 csr 167600 flags 10 vector cssrint cssxint"
46.Sh DESCRIPTION
47NOTE: At the moment,
48.Nx
49does not support
50.Tn IMP ,
51so this manual page is not relevant.
52.Pp
53The
54.Nm css
55device provides a Local Host/Distant Host
56interface to an
57.Tn IMP .
58It is normally used when participating
59in the
60.Tn DARPA
61Internet.  The controller itself is not accessible
62to users, but instead provides the hardware support to the
63.Tn IMP
64interface described in
65.Xr imp 4 .
66The configuration entry for the
67.Xr imp 4
68must also include the
69.Em pseudo-device
70as shown above.
71.Sh DIAGNOSTICS
72.Bl -diag
73.It css%d: not alive.
74The initialization routine was entered even though the device
75did not autoconfigure.  This is indicates a system problem.
76.Pp
77.It css%d: can't initialize.
78Insufficient
79.Tn UNIBUS
80resources existed to initialize the device.
81This is likely to occur when the device is run on a buffered
82data path on an 11/750 and other network interfaces are also
83configured to use buffered data paths, or when it is configured
84to use buffered data paths on an 11/730 (which has none).
85.Pp
86.It css%d: imp doesn't respond, icsr=%b.
87The driver attempted to initialize the device, but the
88.Tn IMP
89failed to respond after 500 tries.  Check the cabling.
90.Pp
91.It css%d: stray output interrupt csr=%b.
92An interrupt occurred when no output had previously been started.
93.Pp
94.It css%d: output error, ocsr=%b icsr=%b.
95The device indicated a problem sending data on output.
96.Pp
97.It css%d: recv error, csr=%b.
98The device indicated a problem receiving data on input.
99.Pp
100.It css%d: bad length=%d.
101An input operation resulted in a data transfer of less than
1020 or more than 1008 bytes of
103data into memory (according to the word count register).
104This should never happen as the maximum size of a
105.Pf host- Tn IMP
106message is 1008 bytes.
107.El
108.Sh HISTORY
109The
110.Nm
111interface appeared in
112.Bx 4.2 .
113