1.\" $NetBSD: hy.4,v 1.14 2017/08/01 11:11: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. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" from: @(#)hy.4 8.1 (Berkeley) 6/5/93 31.\" 32.Dd June 5, 1993 33.Dt HY 4 vax 34.Os 35.Sh NAME 36.Nm hy 37.Nd Network Systems Hyperchannel interface 38.Sh SYNOPSIS 39.Cd "hy0 at uba0 csr 0172410 vector hyint" 40.Sh DESCRIPTION 41NOTE: This driver has not been ported from 42.Bx 4.4 43yet. 44.Pp 45The 46.Nm hy 47interface provides access to a Network 48Systems Corporation Hyperchannel Adapter. 49.Pp 50The network to which the interface is attached 51is specified at boot time with an 52.Dv SIOCSIFADDR 53.Xr ioctl 2 . 54The host's address is discovered by reading the adapter status 55register. 56The interface will not transmit or receive 57packets until the network number is known. 58.Sh DIAGNOSTICS 59.Bl -diag 60.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x." 61Identifies the device during autoconfiguration. 62.It hy%d: can't handle af%d. 63The interface was handed 64a message with addresses formatted in an unsuitable address 65family; the packet was dropped. 66.It hy%d: can't initialize. 67The interface was unable to allocate 68.Tn UNIBUS 69resources. 70This 71is usually due to having too many network devices on an 11/750 72where there are only 3 buffered data paths. 73.It hy%d: NEX - Non Existent Memory. 74Non existent memory error returned from hardware. 75.It hy%d: BAR overflow. 76Bus address register 77overflow error returned from hardware. 78.It hy%d: Power Off bit set, trying to reset. 79Adapter has lost power, driver will reset the bit 80and see if power is still out in the adapter. 81.It hy%d: Power Off Error, network shutdown. 82Power was really off in the adapter, network 83connections are dropped. 84Software does not shut down the network unless 85power has been off for a while. 86.It hy%d: RECVD MP > MPSIZE (%d). 87A message proper was received that is too big. 88Probable a driver bug. 89Shouldn't happen. 90.It "hy%d: xmit error \- len > hy_olen [%d > %d]." 91Probable driver error. 92Shouldn't happen. 93.It hy%d: DRIVER BUG \- INVALID STATE %d. 94The driver state machine reached a non-existent state. 95Definite driver bug. 96.It hy%d: watchdog timer expired. 97A command in the adapter has taken too long to complete. 98Driver will abort and retry the command. 99.It hy%d: adapter power restored. 100Software was able to reset the power off bit, 101indicating that the power has been restored. 102.El 103.Sh SEE ALSO 104.Xr inet 4 , 105.Xr netintro 4 106.Sh HISTORY 107The 108.Nm 109interface appeared in 110.Bx 4.2 . 111.Sh BUGS 112If the adapter does not respond to the status command 113issued during autoconfigure, the adapter is assumed down. 114A reboot is required to recognize it. 115.Pp 116The adapter power fail interrupt seems to occur 117sporadically when power has, in fact, not failed. 118The driver will believe that power has failed 119only if it can not reset the power fail latch after 120a 121.Dq reasonable 122time interval. 123These seem to appear about 2-4 times a day on some machines. 124There seems to be no correlation with adapter 125rev level, number of ports used etc. and whether a 126machine will get these 127.Dq bogus powerfails . 128They don't seem to cause any real problems so they have 129been ignored. 130