1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. 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.\" @(#)pcl.4 8.1 (Berkeley) 6/5/93 33.\" 34.Dd June 5, 1993 35.Dt PCL 4 vax 36.Os BSD 4.2 37.Sh NAME 38.Nm pcl 39.Nd 40.Tn DEC CSS 41.Tn PCL-11 B 42Network Interface 43.Sh SYNOPSIS 44.Cd "device pcl0 at uba? csr 164200 vector pclxint pclrint" 45.Sh DESCRIPTION 46The 47.Nm pcl 48device provides an 49.Tn IP Ns -only 50interface to the 51.Tn DEC CSS 52.Tn PCL-11 53time division multiplexed network bus. 54The controller itself is not accessible to users. 55.Pp 56The hosts's address is specified with the 57.Dv SIOCSIFADDR 58.Xr ioctl 2 . 59The interface will not transmit or receive any data before 60its address is defined. 61.Pp 62As the 63.Tn PCL-11 64hardware is only capable of having 15 interfaces per network, 65a single-byte host-on-network number is used, with range [1..15] to match 66the 67.Tn TDM 68bus addresses of the interfaces. 69.Pp 70The interface currently only supports the Internet protocol family 71and only provides 72.Dq natural 73(header) encapsulation. 74.Sh DIAGNOSTICS 75.Bl -diag 76.It pcl%d: can't init. 77Insufficient 78.Tn UNIBUS 79resources existed to initialize the device. 80This is likely to occur when the device is run on a buffered 81data path on an 11/750 and other network interfaces are also 82configured to use buffered data paths, or when it is configured 83to use buffered data paths on an 11/730 (which has none). 84.Pp 85.It pcl%d: can't handle af%d. 86The interface was handed a message with addresses formatted in an 87unsuitable address family; the packet was dropped. 88.Pp 89.It pcl%d: stray xmit interrupt. 90An interrupt occurred when no output had previously been started. 91.Pp 92.It pcl%d: master. 93The 94.Tn TDM 95bus had no station providing ``bus master'' timing signals, 96so this interface has assumed the ``master'' role. This message should 97only appear at most once per 98.Tn UNIBUS INIT 99on a single system. 100Unless there is a hardware failure, only one station may be master at at time. 101.Pp 102.It pcl%d: send error, tcr=%b, tsr=%b. 103The device indicated a problem sending data on output. 104If a ``receiver offline'' error is detected, it is not normally logged 105unless the option 106.Dv PCL_TESTING 107has been selected, as this causes a lot 108of console chatter when sending to a down machine. However, this option 109is quite useful when debugging problems with the 110.Tn PCL 111interfaces. 112.Pp 113.It pcl%d: rcv error, rcr=%b rsr=%b. 114The device indicated a problem receiving data on input. 115.Pp 116.It pcl%d: bad len=%d. 117An input operation resulted in a data transfer of less than 1180 or more than 1008 bytes of 119data into memory (according to the word count register). 120This should never happen as the maximum size of a 121.Tn PCL 122message 123has been agreed upon to be 1008 bytes (same as ArpaNet message). 124.El 125.Sh SEE ALSO 126.Xr intro 4 , 127.Xr inet 4 128.Sh HISTORY 129The 130.Nm 131interface appeared in 132.Bx 4.2 . 133