xref: /netbsd-src/share/man/man4/man4.vax/pcl.4 (revision d9158b13b5dfe46201430699a3f7a235ecf28df3)
1.\" Copyright (c) 1983, 1991 Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     from: @(#)pcl.4	6.3 (Berkeley) 3/27/91
33.\"	$Id: pcl.4,v 1.2 1993/08/01 07:36:05 mycroft Exp $
34.\"
35.Dd March 27, 1991
36.Dt PCL 4 vax
37.Os BSD 4.2
38.Sh NAME
39.Nm pcl
40.Nd
41.Tn DEC CSS
42.Tn PCL-11 B
43Network Interface
44.Sh SYNOPSIS
45.Cd "device pcl0 at uba? csr 164200 vector pclxint pclrint"
46.Sh DESCRIPTION
47The
48.Nm pcl
49device provides an
50.Tn IP Ns -only
51interface to the
52.Tn DEC CSS
53.Tn PCL-11
54time division multiplexed network bus.
55The controller itself is not accessible to users.
56.Pp
57The hosts's address is specified with the
58.Dv SIOCSIFADDR
59.Xr ioctl 2 .
60The interface will not transmit or receive any data before
61its address is defined.
62.Pp
63As the
64.Tn PCL-11
65hardware is only capable of having 15 interfaces per network,
66a single-byte host-on-network number is used, with range [1..15] to match
67the
68.Tn TDM
69bus addresses of the interfaces.
70.Pp
71The interface currently only supports the Internet protocol family
72and only provides
73.Dq natural
74(header) encapsulation.
75.Sh DIAGNOSTICS
76.Bl -diag
77.It pcl%d: can't init.
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 pcl%d: can't handle af%d.
87The interface was handed a message with addresses formatted in an
88unsuitable address family;  the packet was dropped.
89.Pp
90.It pcl%d: stray xmit interrupt.
91An interrupt occurred when no output had previously been started.
92.Pp
93.It pcl%d: master.
94The
95.Tn TDM
96bus had no station providing ``bus master'' timing signals,
97so this interface has assumed the ``master'' role.  This message should
98only appear at most once per
99.Tn UNIBUS INIT
100on a single system.
101Unless there is a hardware failure, only one station may be master at at time.
102.Pp
103.It pcl%d: send error, tcr=%b, tsr=%b.
104The device indicated a problem sending data on output.
105If a ``receiver offline'' error is detected, it is not normally logged
106unless the option
107.Dv PCL_TESTING
108has been selected, as this causes a lot
109of console chatter when sending to a down machine.  However, this option
110is quite useful when debugging problems with the
111.Tn PCL
112interfaces.
113.Pp
114.It pcl%d: rcv error, rcr=%b rsr=%b.
115The device indicated a problem receiving data on input.
116.Pp
117.It pcl%d: bad len=%d.
118An input operation resulted in a data transfer of less than
1190 or more than 1008 bytes of
120data into memory (according to the word count register).
121This should never happen as the maximum size of a
122.Tn PCL
123message
124has been agreed upon to be 1008 bytes (same as ArpaNet message).
125.El
126.Sh SEE ALSO
127.Xr intro 4 ,
128.Xr inet 4
129.Sh HISTORY
130The
131.Nm
132interface appeared in
133.Bx 4.2 .
134