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