BSD 4_3_Tahoe release
[unix-history] / usr / src / man / man4 / vax / pcl.4
CommitLineData
e28f7377
KM
1.\" Copyright (c) 1983 Regents of the University of California.
2.\" All rights reserved. The Berkeley software License Agreement
3.\" specifies the terms and conditions for redistribution.
4.\"
95f51977 5.\" @(#)pcl.4 6.2 (Berkeley) 5/21/86
e28f7377 6.\"
95f51977 7.TH PCL 4 "May 21, 1986"
e28f7377
KM
8.UC 5
9.SH NAME
10pcl \- DEC CSS PCL-11 B Network Interface
11.SH SYNOPSIS
12.B "device pcl0 at uba? csr 164200 vector pclxint pclrint"
13.SH DESCRIPTION
14The
15.I pcl
16device provides an IP-only interface to the DEC CSS PCL-11
17time division multiplexed network bus.
18The controller itself is not accessible to users.
19.PP
20The hosts's address is specified with the SIOCSIFADDR ioctl.
21The interface will not transmit or receive any data before
22its address is defined.
23.PP
24As the PCL-11 hardware is only capable of having 15 interfaces per network,
25a single-byte host-on-network number is used, with range [1..15] to match
26the TDM bus addresses of the interfaces.
27.PP
28The interface currently only supports the Internet protocol family
29and only provides ``natural'' (header) encapsulation.
30.SH DIAGNOSTICS
31.BR "pcl%d: can't init" .
32Insufficient UNIBUS resources existed to initialize the device.
33This is likely to occur when the device is run on a buffered
34data path on an 11/750 and other network interfaces are also
35configured to use buffered data paths, or when it is configured
36to use buffered data paths on an 11/730 (which has none).
37.PP
38.BR "pcl%d: can't handle af%d" .
39The interface was handed a message with addresses formatted in an
40unsuitable address family; the packet was dropped.
41.PP
42.BR "pcl%d: stray xmit interrupt" .
8781d1b7 43An interrupt occurred when no output had previously been started.
e28f7377
KM
44.PP
45.BR "pcl%d: master" .
46The TDM bus had no station providing ``bus master'' timing signals,
47so this interface has assumed the ``master'' role. This message should
48only appear at most once per UNIBUS INIT on a single system.
49Unless there is a hardware failure, only one station may be master at at time.
50.PP
51.BR "pcl%d: send error, tcr=%b, tsr=%b" .
52The device indicated a problem sending data on output.
53If a ``receiver offline'' error is detected, it is not normally logged
54unless the option PCL_TESTING has been selected, as this causes a lot
55of console chatter when sending to a down machine. However, this option
56is quite useful when debugging problems with the PCL interfaces.
57.PP
58.BR "pcl%d: rcv error, rcr=%b rsr=%b" .
59The device indicated a problem receiving data on input.
60.PP
61.BR "pcl%d: bad len=%d" .
62An input operation resulted in a data transfer of less than
630 or more than 1008 bytes of
64data into memory (according to the word count register).
65This should never happen as the maximum size of a PCL message
66has been agreed upon to be 1008 bytes (same as ArpaNet message).
67.SH "SEE ALSO"
68intro(4N), inet(4F)