1.\" $NetBSD: hy.4,v 1.11 2003/08/07 10:31:11 agc 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. The interface will not transmit or receive 56packets until the network number is known. 57.Sh DIAGNOSTICS 58.Bl -diag 59.It "hy%d: unit number 0x%x port %d type %x microcode level 0x%x." 60Identifies the device during autoconfiguration. 61.Pp 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.Pp 67.It hy%d: can't initialize. 68The interface was unable to allocate 69.Tn UNIBUS 70resources. This 71is usually due to having too many network devices on an 11/750 72where there are only 3 buffered data paths. 73.Pp 74.It hy%d: NEX - Non Existent Memory. 75Non existent memory error returned from hardware. 76.Pp 77.It hy%d: BAR overflow. 78Bus address register 79overflow error returned from hardware. 80.Pp 81.It hy%d: Power Off bit set, trying to reset. 82Adapter has lost power, driver will reset the bit 83and see if power is still out in the adapter. 84.Pp 85.It hy%d: Power Off Error, network shutdown. 86Power was really off in the adapter, network 87connections are dropped. 88Software does not shut down the network unless 89power has been off for a while. 90.Pp 91.It hy%d: RECVD MP \*[Gt] MPSIZE (%d). 92A message proper was received that is too big. 93Probable a driver bug. 94Shouldn't happen. 95.Pp 96.It "hy%d: xmit error \- len \*[Gt] hy_olen [%d \*[Gt] %d]." 97Probable driver error. 98Shouldn't happen. 99.Pp 100.It hy%d: DRIVER BUG \- INVALID STATE %d. 101The driver state machine reached a non-existent state. 102Definite driver bug. 103.Pp 104.It hy%d: watchdog timer expired. 105A command in the adapter has taken too long to complete. 106Driver will abort and retry the command. 107.Pp 108.It hy%d: adapter power restored. 109Software was able to reset the power off bit, 110indicating that the power has been restored. 111.El 112.Sh SEE ALSO 113.Xr inet 4 , 114.Xr netintro 4 115.Sh HISTORY 116The 117.Nm 118interface appeared in 119.Bx 4.2 . 120.Sh BUGS 121If the adapter does not respond to the status command 122issued during autoconfigure, the adapter is assumed down. 123A reboot is required to recognize it. 124.Pp 125The adapter power fail interrupt seems to occur 126sporadically when power has, in fact, not failed. 127The driver will believe that power has failed 128only if it can not reset the power fail latch after 129a 130.Dq reasonable 131time interval. 132These seem to appear about 2-4 times a day on some machines. 133There seems to be no correlation with adapter 134rev level, number of ports used etc. and whether a 135machine will get these 136.Dq bogus powerfails . 137They don't seem to cause any real problems so they have 138been ignored. 139