diff options
Diffstat (limited to 'static/netbsd/man4/man4.vax/hy.4 4.html')
| -rw-r--r-- | static/netbsd/man4/man4.vax/hy.4 4.html | 99 |
1 files changed, 0 insertions, 99 deletions
diff --git a/static/netbsd/man4/man4.vax/hy.4 4.html b/static/netbsd/man4/man4.vax/hy.4 4.html deleted file mode 100644 index b3268739..00000000 --- a/static/netbsd/man4/man4.vax/hy.4 4.html +++ /dev/null @@ -1,99 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">HY(4)</td> - <td class="head-vol">Device Drivers Manual (vax)</td> - <td class="head-rtitle">HY(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">hy</code> — <span class="Nd">Network - Systems Hyperchannel interface</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">hy0 at uba0 csr 0172410 vector hyint</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">NOTE: This driver has not been ported from - <span class="Ux">4.4BSD</span> yet.</p> -<p class="Pp">The <code class="Nm">hy</code> interface provides access to a - Network Systems Corporation Hyperchannel Adapter.</p> -<p class="Pp">The network to which the interface is attached is specified at - boot time with an <code class="Dv">SIOCSIFADDR</code> - <a class="Xr">ioctl(2)</a>. The host's address is discovered by reading the - adapter status register. The interface will not transmit or receive packets - until the network number is known.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>hy%d: unit number 0x%x port %d type %x microcode level 0x%x.</dt> - <dd>Identifies the device during autoconfiguration.</dd> - <dt>hy%d: can't handle af%d.</dt> - <dd>The interface was handed a message with addresses formatted in an - unsuitable address family; the packet was dropped.</dd> - <dt>hy%d: can't initialize.</dt> - <dd>The interface was unable to allocate UNIBUS resources. This is usually due - to having too many network devices on an 11/750 where there are only 3 - buffered data paths.</dd> - <dt>hy%d: NEX - Non Existent Memory.</dt> - <dd>Non existent memory error returned from hardware.</dd> - <dt>hy%d: BAR overflow.</dt> - <dd>Bus address register overflow error returned from hardware.</dd> - <dt>hy%d: Power Off bit set, trying to reset.</dt> - <dd>Adapter has lost power, driver will reset the bit and see if power is - still out in the adapter.</dd> - <dt>hy%d: Power Off Error, network shutdown.</dt> - <dd>Power was really off in the adapter, network connections are dropped. - Software does not shut down the network unless power has been off for a - while.</dd> - <dt>hy%d: RECVD MP > MPSIZE (%d).</dt> - <dd>A message proper was received that is too big. Probable a driver bug. - Shouldn't happen.</dd> - <dt>hy%d: xmit error - len > hy_olen [%d > %d].</dt> - <dd>Probable driver error. Shouldn't happen.</dd> - <dt>hy%d: DRIVER BUG - INVALID STATE %d.</dt> - <dd>The driver state machine reached a non-existent state. Definite driver - bug.</dd> - <dt>hy%d: watchdog timer expired.</dt> - <dd>A command in the adapter has taken too long to complete. Driver will abort - and retry the command.</dd> - <dt>hy%d: adapter power restored.</dt> - <dd>Software was able to reset the power off bit, indicating that the power - has been restored.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">inet(4)</a>, <a class="Xr">netintro(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">hy</code> interface appeared in - <span class="Ux">4.2BSD</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">If the adapter does not respond to the status command issued - during autoconfigure, the adapter is assumed down. A reboot is required to - recognize it.</p> -<p class="Pp">The adapter power fail interrupt seems to occur sporadically when - power has, in fact, not failed. The driver will believe that power has - failed only if it can not reset the power fail latch after a - “reasonable” time interval. These seem to appear about 2-4 - times a day on some machines. There seems to be no correlation with adapter - rev level, number of ports used etc. and whether a machine will get these - “bogus powerfails”. They don't seem to cause any real problems - so they have been ignored.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 5, 1993</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |