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.\" @(#)hy.4 8.1 (Berkeley) 6/5/93 33.\" 34.Dd June 5, 1993 35.Dt HY 4 vax 36.Os BSD 4.2 37.Sh NAME 38.Nm hy 39.Nd Network Systems Hyperchannel interface 40.Sh SYNOPSIS 41.Cd "device hy0 at uba0 csr 0172410 vector hyint" 42.Sh DESCRIPTION 43The 44.Nm hy 45interface provides access to a Network 46Systems Corporation Hyperchannel Adapter. 47.Pp 48The network to which the interface is attached 49is specified at boot time with an 50.Dv SIOCSIFADDR 51.Xr ioctl 2 . 52The host's address is discovered by reading the adapter status 53register. The interface will not transmit or receive 54packets until the network number is known. 55.Sh DIAGNOSTICS 56.Bl -diag 57.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x." 58Identifies the device during autoconfiguration. 59.Pp 60.It hy%d: can't handle af%d. 61The interface was handed 62a message with addresses formatted in an unsuitable address 63family; the packet was dropped. 64.Pp 65.It hy%d: can't initialize. 66The interface was unable to allocate 67.Tn UNIBUS 68resources. This 69is usually due to having too many network devices on an 11/750 70where there are only 3 buffered data paths. 71.Pp 72.It hy%d: NEX - Non Existent Memory. 73Non existent memory error returned from hardware. 74.Pp 75.It hy%d: BAR overflow. 76Bus address register 77overflow error returned from hardware. 78.Pp 79.It hy%d: Power Off bit set, trying to reset. 80Adapter has lost power, driver will reset the bit 81and see if power is still out in the adapter. 82.Pp 83.It hy%d: Power Off Error, network shutdown. 84Power was really off in the adapter, network 85connections are dropped. 86Software does not shut down the network unless 87power has been off for a while. 88.Pp 89.It hy%d: RECVD MP > MPSIZE (%d). 90A message proper was received that is too big. 91Probable a driver bug. 92Shouldn't happen. 93.Pp 94.It "hy%d: xmit error \- len > hy_olen [%d > %d]." 95Probable driver error. 96Shouldn't happen. 97.Pp 98.It hy%d: DRIVER BUG \- INVALID STATE %d. 99The driver state machine reached a non-existent state. 100Definite driver bug. 101.Pp 102.It hy%d: watchdog timer expired. 103A command in the adapter has taken too long to complete. 104Driver will abort and retry the command. 105.Pp 106.It hy%d: adapter power restored. 107Software was able to reset the power off bit, 108indicating that the power has been restored. 109.El 110.Sh SEE ALSO 111.Xr netintro 4 , 112.Xr inet 4 113.Sh HISTORY 114The 115.Nm 116interface appeared in 117.Bx 4.2 . 118.Sh BUGS 119If the adapter does not respond to the status command 120issued during autoconfigure, the adapter is assumed down. 121A reboot is required to recognize it. 122.Pp 123The adapter power fail interrupt seems to occur 124sporadically when power has, in fact, not failed. 125The driver will believe that power has failed 126only if it can not reset the power fail latch after 127a 128.Dq reasonable 129time interval. 130These seem to appear about 2-4 times a day on some machines. 131There seems to be no correlation with adapter 132rev level, number of ports used etc. and whether a 133machine will get these 134.Dq bogus powerfails . 135They don't seem to cause any real problems so they have 136been ignored. 137