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