diff options
Diffstat (limited to 'static/netbsd/man4/fxp.4 4.html')
| -rw-r--r-- | static/netbsd/man4/fxp.4 4.html | 120 |
1 files changed, 0 insertions, 120 deletions
diff --git a/static/netbsd/man4/fxp.4 4.html b/static/netbsd/man4/fxp.4 4.html deleted file mode 100644 index e9d25a87..00000000 --- a/static/netbsd/man4/fxp.4 4.html +++ /dev/null @@ -1,120 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">FXP(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">FXP(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">fxp</code> — <span class="Nd">Intel i8255x - 10/100 Ethernet device driver</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">fxp* at cardbus? function ?</code> - <br/> - <code class="Cd">fxp* at pci? dev ? function ?</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">fxp</code> device driver supports Ethernet - interfaces based on the Intel i82557, i82558, i82559, and i82550 10/100 PCI - Ethernet chips.</p> -<p class="Pp">Certain versions of the i8255x support loading microcode which - implements a receive interrupt mitigation function, known as - “CPUSaver”. Use of this option can improve performance in some - situations by reducing interrupt load on the host. This option is available - on the following chip versions:</p> -<p class="Pp"></p> -<ul class="Bl-bullet Bl-compact"> - <li>i82558 step A4 (rev 4)</li> - <li>i82558 step B0 (rev 5)</li> - <li>i82559 step A0 (rev 8)</li> - <li>i82559S step A (rev 9)</li> - <li>i82550 (rev 12)</li> - <li>i82550 step C (rev 13)</li> -</ul> -<p class="Pp">This option is enabled by setting the “link0” option - with <a class="Xr">ifconfig(8)</a>.</p> -<p class="Pp">Some chipset revisions can suffer from a receiver-side lockup bug - which can be mitigated by resetting the chip every sixteen seconds without - traffic. Since the probe for affected chipsets generates false positives and - the workaround can cause momentary loss of responsiveness, particularly - noticeable when playing audio, the workaround is not enabled by default. The - boot messages will indicate if any interface may have this issue. The - workaround is enabled by setting the “link1” option with - <a class="Xr">ifconfig(8)</a>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1> -<p class="Pp">Cards supported by the <code class="Nm">fxp</code> driver - include:</p> -<p class="Pp"></p> -<ul class="Bl-bullet Bl-compact"> - <li>Intel EtherExpress Pro 10+</li> - <li>Intel EtherExpress Pro 100B</li> - <li>Intel EtherExpress Pro 100+</li> - <li>Intel InBusiness 10/100</li> - <li>Intel PRO/100 S</li> -</ul> -</section> -<section class="Sh"> -<h1 class="Sh" id="MEDIA_SELECTION"><a class="permalink" href="#MEDIA_SELECTION">MEDIA - SELECTION</a></h1> -<p class="Pp">Media selection is supported via MII. See - <a class="Xr">ifmedia(4)</a> and <a class="Xr">mii(4)</a> for more - information.</p> -<p class="Pp">EtherExpress Pro 10+ boards may use a Seeq 80c24 AutoDUPLEX(tm) - media interface. Boards with these chips do not support media selection, as - the 80c24 has no programming interface, and no way to read link status. - These boards claim a media of "manual" since they self-configure - based on the configuration of the link partner (hub or switch).</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>fxp0: WARNING: SCB timed out!</dt> - <dd>The driver timed out waiting for the chip's command interface to become - ready.</dd> - <dt>fxp0: too many segments, aborting</dt> - <dd>The driver encountered a packet that included too many DMA segments, and - was not able to allocate a new buffer to transmit the packet from. The - packet has been dropped.</dd> - <dt>fxp0: too many segments, retrying</dt> - <dd>The driver encountered a packet that included too many DMA segments, and - allocated a new buffer to transmit the packet from.</dd> - <dt>fxp0: can't load mbuf chain, error = %d</dt> - <dd>The driver was unable to load a transmit DMA map, and has reported the - errno value.</dd> - <dt>fxp0: device timeout</dt> - <dd>The device failed to generate a transmit complete interrupt for the last - packet transmitted. The device has been reset.</dd> - <dt>fxp0: can't load rx buffer, error = %d</dt> - <dd>The driver was unable to load the DMA map for a receive buffer, and has - reported the errno value. This error is currently fatal, and will panic - the system.</dd> - <dt>fxp0: fxp_mdi_read: timed out</dt> - <dd>The MDIO failed to become ready during an MII read operation.</dd> - <dt>fxp0: fxp_mdi_write: timed out</dt> - <dd>The MDIO failed to become ready during an MII write operation.</dd> - <dt>fxp0: May need receiver lock-up workaround</dt> - <dd>The interface may need to be periodically reset to workaround a receiver - lock-up bug.</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">cardbus(4)</a>, <a class="Xr">ifmedia(4)</a>, - <a class="Xr">intro(4)</a>, <a class="Xr">mii(4)</a>, - <a class="Xr">pci(4)</a>, <a class="Xr">ifconfig(8)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">October 15, 2005</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |