diff options
Diffstat (limited to 'static/freebsd/man4/ste.4 3.html')
| -rw-r--r-- | static/freebsd/man4/ste.4 3.html | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/static/freebsd/man4/ste.4 3.html b/static/freebsd/man4/ste.4 3.html new file mode 100644 index 00000000..615e008f --- /dev/null +++ b/static/freebsd/man4/ste.4 3.html @@ -0,0 +1,154 @@ +<table class="head"> + <tr> + <td class="head-ltitle">STE(4)</td> + <td class="head-vol">Device Drivers Manual</td> + <td class="head-rtitle">STE(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">ste</code> — <span class="Nd">Sundance + Technologies ST201 Fast 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">To compile this driver into the kernel, place the following lines + in your kernel configuration file:</p> +<div class="Bd Pp Bd-indent"><code class="Cd">device miibus</code> +<br/> +<code class="Cd">device ste</code></div> +<p class="Pp">Alternatively, to load the driver as a module at boot time, place + the following line in <a class="Xr">loader.conf(5)</a>:</p> +<div class="Bd Pp Bd-indent Li"> +<pre>if_ste_load="YES"</pre> +</div> +</section> +<section class="Sh"> +<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> +<p class="Pp">The <code class="Nm">ste</code> driver provides support for PCI + Ethernet adapters and embedded controllers based on the Sundance + Technologies ST201 PCI Fast Ethernet controller chip.</p> +<p class="Pp">The Sundance ST201 uses bus master DMA and is designed to be a + 3Com Etherlink XL workalike. It uses the same DMA descriptor structure and + is very similar in operation, however its register layout is different. The + ST201 has a 64-bit multicast hash filter and a single perfect filter entry + for the station address. It supports both 10 and 100Mbps speeds in either + full or half duplex using an MII transceiver.</p> +<p class="Pp">The <code class="Nm">ste</code> driver supports the following + media types:</p> +<dl class="Bl-tag"> + <dt>autoselect</dt> + <dd>Enable autoselection of the media type and options. The user can manually + override the autoselected mode by adding media options to the + <span class="Pa">/etc/rc.conf</span> file.</dd> + <dt>10baseT/UTP</dt> + <dd>Set 10Mbps operation. The <var class="Ar">mediaopt</var> option can also + be used to select either <var class="Ar">full-duplex</var> or + <var class="Ar">half-duplex</var> modes.</dd> + <dt>100baseTX</dt> + <dd>Set 100Mbps (Fast Ethernet) operation. The <var class="Ar">mediaopt</var> + option can also be used to select either <var class="Ar">full-duplex</var> + or <var class="Ar">half-duplex</var> modes.</dd> +</dl> +<p class="Pp">The <code class="Nm">ste</code> driver supports the following + media options:</p> +<dl class="Bl-tag"> + <dt>full-duplex</dt> + <dd>Force full duplex operation.</dd> + <dt>half-duplex</dt> + <dd>Force half duplex operation.</dd> +</dl> +<p class="Pp">For more information on configuring this device, see + <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">The <code class="Nm">ste</code> driver supports Sundance + Technologies ST201 based Fast Ethernet adapters and embedded controllers + including:</p> +<p class="Pp"></p> +<ul class="Bl-bullet Bl-compact"> + <li>D-Link DFE-530TXS</li> + <li>D-Link DFE-550TX</li> + <li>D-Link DFE-580TX</li> +</ul> +</section> +<section class="Sh"> +<h1 class="Sh" id="SYSCTL_VARIABLES"><a class="permalink" href="#SYSCTL_VARIABLES">SYSCTL + VARIABLES</a></h1> +<p class="Pp">The following variables are available as both + <a class="Xr">sysctl(8)</a> variables and <a class="Xr">loader(8)</a> + tunables:</p> +<dl class="Bl-tag"> + <dt id="dev.ste._d.int_rx_mod"><var class="Va">dev.ste.%d.int_rx_mod</var></dt> + <dd>Maximum number of time to delay RX interrupts. The valid range is 0 to + 209712 in units of 1us, the default is 150 (150us). The value 0 + effectively disables the RX interrupt moderation. The resolution of timer + is about 3.2us so finer tuning than 3.2us wouldn't be available. The + interface does not need to be brought down and up again before a change + takes effect.</dd> +</dl> +</section> +<section class="Sh"> +<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> +<dl class="Bl-diag"> + <dt>ste%d: couldn't map ports/memory</dt> + <dd>A fatal initialization error has occurred.</dd> + <dt>ste%d: couldn't map interrupt</dt> + <dd>A fatal initialization error has occurred.</dd> + <dt>ste%d: watchdog timeout</dt> + <dd>The device has stopped responding to the network, or there is a problem + with the network connection (cable).</dd> + <dt>ste%d: no memory for rx list</dt> + <dd>The driver failed to allocate an mbuf for the receiver ring.</dd> + <dt>ste%d: no memory for tx list</dt> + <dd>The driver failed to allocate an mbuf for the transmitter ring when + allocating a pad buffer or collapsing an mbuf chain into a cluster.</dd> + <dt>ste%d: chip is in D3 power state -- setting to D0</dt> + <dd>This message applies only to adapters which support power management. Some + operating systems place the controller in low power mode when shutting + down, and some PCI BIOSes fail to bring the chip out of this state before + configuring it. The controller loses all of its PCI configuration in the + D3 state, so if the BIOS does not set it back to full power mode in time, + it will not be able to configure it correctly. The driver tries to detect + this condition and bring the adapter back to the D0 (full power) state, + but this may not be enough to return the driver to a fully operational + condition. If you see this message at boot time and the driver fails to + attach the device as a network interface, you will have to perform a + second warm boot to have the device properly configured. + <p class="Pp">Note that this condition only occurs when warm booting from + another operating system. If you power down your system prior to booting + <span class="Ux">FreeBSD</span>, the card should be configured + correctly.</p> + </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">altq(4)</a>, <a class="Xr">arp(4)</a>, + <a class="Xr">miibus(4)</a>, <a class="Xr">netintro(4)</a>, + <a class="Xr">ng_ether(4)</a>, <a class="Xr">polling(4)</a>, + <a class="Xr">vlan(4)</a>, <a class="Xr">ifconfig(8)</a></p> +<p class="Pp"><cite class="Rs"><span class="RsT">Sundance ST201 data + sheet</span>.</cite></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">ste</code> device driver first appeared in + <span class="Ux">FreeBSD 3.0</span>.</p> +</section> +<section class="Sh"> +<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> +<p class="Pp">The <code class="Nm">ste</code> driver was written by + <span class="An">Bill Paul</span> + <<a class="Mt" href="mailto:wpaul@ee.columbia.edu">wpaul@ee.columbia.edu</a>>.</p> +</section> +</div> +<table class="foot"> + <tr> + <td class="foot-date">December 24, 2009</td> + <td class="foot-os">FreeBSD 15.0</td> + </tr> +</table> |