diff options
Diffstat (limited to 'static/freebsd/man4/bce.4 3.html')
| -rw-r--r-- | static/freebsd/man4/bce.4 3.html | 364 |
1 files changed, 0 insertions, 364 deletions
diff --git a/static/freebsd/man4/bce.4 3.html b/static/freebsd/man4/bce.4 3.html deleted file mode 100644 index 697ab5ab..00000000 --- a/static/freebsd/man4/bce.4 3.html +++ /dev/null @@ -1,364 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BCE(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">BCE(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">bce</code> — <span class="Nd">QLogic - NetXtreme II (BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapter - 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 bce</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_bce_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">bce</code> driver supports QLogic's NetXtreme - II product family, including the BCM5706, BCM5708, BCM5709 and BCM5716 - Ethernet controllers.</p> -<p class="Pp">The NetXtreme II product family is composed of various Converged - NIC (or CNIC) Ethernet controllers which support a TCP Offload Engine (TOE), - Remote DMA (RDMA), and iSCSI acceleration, in addition to standard L2 - Ethernet traffic, all on the same controller.</p> -<p class="Pp">The following features are supported in the - <code class="Nm">bce</code> driver under - <span class="Ux">FreeBSD</span>:</p> -<p class="Pp"></p> -<ul class="Bl-item Bd-indent Bl-compact"> - <li>IP/TCP/UDP checksum offload</li> - <li>Jumbo frames (up to 9022 bytes)</li> - <li>VLAN tag stripping</li> - <li>Interrupt coalescing</li> - <li>10/100/1000Mbps operation in full-duplex mode</li> - <li>10/100Mbps operation in half-duplex mode</li> -</ul> -<p class="Pp">The <code class="Nm">bce</code> driver supports the following - media types:</p> -<dl class="Bl-tag"> - <dt id="autoselect"><a class="permalink" href="#autoselect"><code class="Cm">autoselect</code></a></dt> - <dd>Enable autoselection of the media type and options. The user can manually - override the autoselected mode by adding media options to - <a class="Xr">rc.conf(5)</a>.</dd> - <dt id="10baseT/UTP"><a class="permalink" href="#10baseT/UTP"><code class="Cm">10baseT/UTP</code></a></dt> - <dd>Set 10Mbps operation. The <a class="Xr">ifconfig(8)</a> - <code class="Cm">mediaopt</code> option can also be used to select either - <code class="Cm">full-duplex</code> or <code class="Cm">half-duplex</code> - modes.</dd> - <dt id="100baseTX"><a class="permalink" href="#100baseTX"><code class="Cm">100baseTX</code></a></dt> - <dd>Set 100Mbps (Fast Ethernet) operation. The <a class="Xr">ifconfig(8)</a> - <code class="Cm">mediaopt</code> option can also be used to select either - <code class="Cm">full-duplex</code> or <code class="Cm">half-duplex</code> - modes.</dd> - <dt id="1000baseSX"><a class="permalink" href="#1000baseSX"><code class="Cm">1000baseSX</code></a></dt> - <dd>Sets 1000Mbps operation. Only <code class="Cm">full-duplex</code> mode is - supported at this speed.</dd> - <dt id="1000baseT"><a class="permalink" href="#1000baseT"><code class="Cm">1000baseT</code></a></dt> - <dd>Set 1000baseT operation over twisted pair. Only - <code class="Cm">full-duplex</code> mode is supported.</dd> - <dt id="2500BaseSX"><a class="permalink" href="#2500BaseSX"><code class="Cm">2500BaseSX</code></a></dt> - <dd>Set 2500Mbps operation. Only <code class="Cm">full-duplex</code> mode is - supported.</dd> -</dl> -<p class="Pp">The <code class="Nm">bce</code> driver supports the following - media options:</p> -<dl class="Bl-tag"> - <dt id="full-duplex"><a class="permalink" href="#full-duplex"><code class="Cm">full-duplex</code></a></dt> - <dd>Force full duplex operation.</dd> - <dt id="half-duplex"><a class="permalink" href="#half-duplex"><code class="Cm">half-duplex</code></a></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">bce</code> driver provides support for - various NICs based on the QLogic NetXtreme II family of Gigabit Ethernet - controllers, including the following:</p> -<p class="Pp"></p> -<ul class="Bl-bullet Bl-compact"> - <li>QLogic NetXtreme II BCM5706 1000Base-SX</li> - <li>QLogic NetXtreme II BCM5706 1000Base-T</li> - <li>QLogic NetXtreme II BCM5708 1000Base-SX</li> - <li>QLogic NetXtreme II BCM5708 1000Base-T</li> - <li>QLogic NetXtreme II BCM5709 1000Base-SX</li> - <li>QLogic NetXtreme II BCM5709 1000Base-T</li> - <li>QLogic NetXtreme II BCM5716 1000Base-T</li> - <li>Dell PowerEdge 1950 integrated BCM5708 NIC</li> - <li>Dell PowerEdge 2950 integrated BCM5708 NIC</li> - <li>Dell PowerEdge R710 integrated BCM5709 NIC</li> - <li>HP NC370F Multifunction Gigabit Server Adapter</li> - <li>HP NC370T Multifunction Gigabit Server Adapter</li> - <li>HP NC370i Multifunction Gigabit Server Adapter</li> - <li>HP NC371i Multifunction Gigabit Server Adapter</li> - <li>HP NC373F PCIe Multifunc Giga Server Adapter</li> - <li>HP NC373T PCIe Multifunction Gig Server Adapter</li> - <li>HP NC373i Multifunction Gigabit Server Adapter</li> - <li>HP NC373m Multifunction Gigabit Server Adapter</li> - <li>HP NC374m PCIe Multifunction Adapter</li> - <li>HP NC380T PCIe DP Multifunc Gig Server Adapter</li> - <li>HP NC382T PCIe DP Multifunction Gigabit Server Adapter</li> - <li>HP NC382i DP Multifunction Gigabit Server Adapter</li> - <li>HP NC382m DP 1GbE Multifunction BL-c Adapter</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="hw.bce.verbose"><var class="Va">hw.bce.verbose</var></dt> - <dd>Enable/Disable verbose logging and output to the console. Useful for - debugging (default 0).</dd> - <dt id="hw.bce.msi_enable"><var class="Va">hw.bce.msi_enable</var></dt> - <dd>Enable/Disable MSI support (default 1).</dd> - <dt id="hw.bce.tso_enable"><var class="Va">hw.bce.tso_enable</var></dt> - <dd>Enable/Disable TSO support (default 1).</dd> - <dt id="hw.bce.strict_rx_mtu"><var class="Va">hw.bce.strict_rx_mtu</var></dt> - <dd>Enable/Disable strict RX frame size checking (default 0).</dd> - <dt id="hw.bce.hdr_split"><var class="Va">hw.bce.hdr_split</var></dt> - <dd>Enable/Disable frame header/payload splitting (default 1).</dd> - <dt id="hw.bce.rx_pages"><var class="Va">hw.bce.rx_pages</var></dt> - <dd>Set the number of memory pages assigned to receive packets by the driver. - Due to alignment issues, this value can only be of the set 1, 2, 4 or 8 - (default 2).</dd> - <dt id="hw.bce.tx_pages"><var class="Va">hw.bce.tx_pages</var></dt> - <dd>Set the number of memory pages assigned to transmit packets by the driver. - Due to alignment issues, this value can only be of the set 1, 2, 4 or 8 - (default 2).</dd> - <dt id="hw.bce.rx_ticks"><var class="Va">hw.bce.rx_ticks</var></dt> - <dd>Time in microsecond ticks to wait before generating a status block updates - due to RX processing activity. Values from 0-100 are valid. A value of 0 - disables this status block update. Cannot be set to 0 if - hw.bce.rx_quick_cons_trip is also 0 (default 18).</dd> - <dt id="hw.bce.rx_ticks_int"><var class="Va">hw.bce.rx_ticks_int</var></dt> - <dd>Time in microsecond ticks to wait during RX interrupt processing before - generating a status block update. Values from 0-100 are valid. Valid - values are in the range from 0-100. A value of 0 disables this status - block update (default 18).</dd> - <dt id="hw.bce.rx_quick_cons_trip"><var class="Va">hw.bce.rx_quick_cons_trip</var></dt> - <dd>Number of RX Quick BD Chain entries that must be completed before a status - block is generated. Values from 0-256 are valid. A value of 0 disables - this status block update. Cannot be set to 0 if hw.bce.rx_ticks is also 0 - (default 6).</dd> - <dt id="hw.bce.rx_quick_cons_trip_int"><var class="Va">hw.bce.rx_quick_cons_trip_int</var></dt> - <dd>Number of RX quick BD entries that must be completed before a status block - is generated duing interrupt processing. Values from 0-256 are valid. A - value of 0 disables this status block update (default 6).</dd> - <dt id="hw.bce.tx_ticks"><var class="Va">hw.bce.tx_ticks</var></dt> - <dd>Time in microsecond ticks to wait before a status block update is - generated due to TX activity. Values from 0-100 are valid. A value of 0 - disables this status block update. Cannot be set to 0 if - hw.bce.tx_quick_cons_trip is also 0 (default 80).</dd> - <dt id="hw.bce.tx_ticks_int"><var class="Va">hw.bce.tx_ticks_int</var></dt> - <dd>Time in microsecond ticks to wait in interrupt processing before a status - block update is generated due to TX activity Values from 0-100 are valid. - A value of 0 disables this status block update (default 80).</dd> - <dt id="hw.bce.tx_cons_trip"><var class="Va">hw.bce.tx_cons_trip</var></dt> - <dd>How many TX Quick BD Chain entries that must be completed before a status - block is generated. Values from 0-100 are valid. A value of 0 disables - this status block update. Cannot be set to 0 if hw.bce.tx_ticks is also 0 - (default 20).</dd> - <dt id="hw.bce.tx_cons_trip_int"><var class="Va">hw.bce.tx_cons_trip_int</var></dt> - <dd>How many TX Quick BD Chain entries that must be completed before a status - block is generated during an interrupt. Values from 0-100 are valid. A - value of 0 disables this status block update (default 20).</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>bce%d: PCI memory allocation failed!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: PCI map interrupt failed!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: Unsupported controller revision (%c%d)</dt> - <dd>The driver does not support the controller revision in use.</dd> - <dt>bce%d: Controller initialization failed!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: NVRAM test failed!</dt> - <dd>The driver could not access the controller NVRAM correctly.</dd> - <dt>bce%d: DMA resource allocation failed!</dt> - <dd>The driver could not allocate DMA memory to setup the controllers host - memory data structures.</dd> - <dt>bce%d: Interface allocation failed!</dt> - <dd>The driver could not create a network interface for the controller.</dd> - <dt>bce%d: PHY probe failed!</dt> - <dd>The driver could not access the PHY used by the controller.</dd> - <dt>bce%d: Failed to setup IRQ!</dt> - <dd>The driver could not initialize the IRQ handler.</dd> - <dt>bce%d: Error: PHY read timeout!</dt> - <dd>The driver could not read a PHY register before the timeout period - expired.</dd> - <dt>bce%d: PHY write timeout!</dt> - <dd>The driver could not write to the PHY register because a timeout - occurred.</dd> - <dt>bce%d: Timeout error reading NVRAM at offset 0x%08X!</dt> - <dd>The driver could not write to NVRAM because a timeout occurred.</dd> - <dt>bce%d: Unknown Flash NVRAM found!</dt> - <dd>The driver does not recognize the NVRAM device being used and therefore - cannot access it correctly.</dd> - <dt>bce%d: Invalid NVRAM magic value!</dt> - <dd>The driver cannot read NVRAM or the NVRAM is corrupt.</dd> - <dt>bce%d: Invalid Manufacturing Information NVRAM CRC!</dt> - <dd>The driver cannot read NVRAM or the NVRAM is corrupt.</dd> - <dt>bce%d: Invalid Feature Configuration Information NVRAM CRC!</dt> - <dd>The driver cannot read NVRAM or the NVRAM is corrupt.</dd> - <dt>bce%d: DMA mapping error!</dt> - <dd>The driver was unable to map memory into DMA addressable space required by - the controller.</dd> - <dt>bce%d: Could not allocate parent DMA tag!</dt> - <dd>The driver could not allocate a PCI compatible DMA tag.</dd> - <dt>bce%d: Could not allocate status block DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's status - block.</dd> - <dt>bce%d: Could not allocate status block DMA memory!</dt> - <dd>The driver could not allocate DMA addressable memory for the controller's - status block.</dd> - <dt>bce%d: Could not map status block DMA memory!</dt> - <dd>The driver could not map the status block memory into the controller's DMA - address space.</dd> - <dt>bce%d: Could not allocate statistics block DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's statistics - block.</dd> - <dt>bce%d: Could not allocate statistics block DMA memory!</dt> - <dd>The driver could not allocate DMA addressable memory for the controller's - statistics block.</dd> - <dt>bce%d: Could not map statistics block DMA memory!</dt> - <dd>The driver could not map the statistics block memory into the controller's - DMA address space.</dd> - <dt>bce%d: Could not allocate TX descriptor chain DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's TX - chain.</dd> - <dt>bce%d: Could not allocate TX descriptor chain DMA memory!</dt> - <dd>The driver could not allocate DMA addressable memory for the controller's - TX chain.</dd> - <dt>bce%d: Could not map TX descriptor chain DMA memory!</dt> - <dd>The driver could not map the TX descriptor chain memory into the - controller's DMA address space.</dd> - <dt>bce%d: Could not allocate TX mbuf DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's TX mbuf - memory.</dd> - <dt>bce%d: Unable to create TX mbuf DMA map!</dt> - <dd>The driver could not map the TX mbuf memory into the controller's DMA - address space.</dd> - <dt>bce%d: Could not allocate RX descriptor chain DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's RX - chain.</dd> - <dt>bce%d: Could not allocate RX descriptor chain </dt> - <dd>The driver could not allocate DMA addressable memory for the controller's - RX chain.</dd> - <dt>bce%d: Could not map RX descriptor chain DMA memory!</dt> - <dd>The driver could not map the RX descriptor chain memory into the - controller's DMA address space.</dd> - <dt>bce%d: Could not allocate RX mbuf DMA tag!</dt> - <dd>The driver could not allocate a DMA tag for the controller's RX mbuf - memory.</dd> - <dt>bce%d: Unable to create RX mbuf DMA map!</dt> - <dd>The driver could not map the RX mbuf memory into the controller's DMA - address space.</dd> - <dt>bce%d: Firmware synchronization timeout!</dt> - <dd>The driver was not able to synchronize with the firmware running on the - controller. The firmware may be stopped or hung.</dd> - <dt>bce%d: Invalid Ethernet address!</dt> - <dd>The driver was not able to read a valid Ethernet MAC address from - NVRAM.</dd> - <dt>bce%d: Reset failed!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: Byte swap is incorrect!</dt> - <dd>The driver has encountered a fatal initialization error. Contact the - author with details of the CPU architecture and system chipset in - use.</dd> - <dt>bce%d: Firmware did not complete initialization!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: Bootcode not running!</dt> - <dd>The driver has encountered a fatal initialization error.</dd> - <dt>bce%d: Error mapping mbuf into RX chain!</dt> - <dd>The driver could not map a RX mbuf into DMA addressable memory.</dd> - <dt>bce%d: Error filling RX chain: rx_bd[0x%04X]!</dt> - <dd>The driver was unable to allocate enough mbufs to fill the RX chain during - initialization. Try increasing the number of mbufs available in the - system, increase system memory, or if using jumbo frames, make sure enough - 9KB mbufs are available.</dd> - <dt>bce%d: Failed to allocate new mbuf, incoming frame dropped!</dt> - <dd>The driver was unable to allocate a new mbuf for the RX chain and reused - the mbuf for the received frame, dropping the incoming frame in the - process. Try increasing the number of mbufs available in the system or - increase system memory.</dd> - <dt>bce%d: Controller reset failed!</dt> - <dd>A fatal initialization error has occurred.</dd> - <dt>bce%d: Controller initialization failed!</dt> - <dd>A fatal initialization error has occurred.</dd> - <dt>bce%d: Block initialization failed!</dt> - <dd>A fatal initialization error has occurred.</dd> - <dt>bce%d: Error mapping mbuf into TX chain!</dt> - <dd>The driver could not map a TX mbuf into DMA addressable memory.</dd> - <dt>bce%d: Error registering poll function!</dt> - <dd>The driver received an error while attempting to register the poll - function.</dd> - <dt>bce%d: Changing VLAN_MTU not supported.</dt> - <dd>Changing the VLAN MTU is not currently supported by the driver.</dd> - <dt>bce%d: Cannot change VLAN_HWTAGGING while management firmware - (ASF/IPMI/UMP) is running!</dt> - <dd>Management firmware to support ASF/IPMI/UMP requires that VLAN tag - stripping be enabled in the controller.</dd> - <dt>bce%d: Changing VLAN_HWTAGGING not supported!</dt> - <dd>Disabling VLAN tag stripping is not currently supported by the - driver.</dd> - <dt>bce%d: Watchdog timeout occurred, resetting!</dt> - <dd>The device has stopped responding to the network, there is a problem with - the cable connection, or a driver logic problem has occurred..</dd> - <dt>bce%d: Fatal attention detected: 0x%08X!</dt> - <dd>A controller hardware failure has occurred. If the problem continues - replace the controller.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SUPPORT"><a class="permalink" href="#SUPPORT">SUPPORT</a></h1> -<p class="Pp">For support questions please contact your QLogic approved reseller - or QLogic Technical Support at - <span class="Pa">http://support.qlogic.com</span>, or by E-mail at - <<a class="Mt" href="mailto:support@qlogic.com">support@qlogic.com</a>>.</p> -</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">vlan(4)</a>, - <a class="Xr">ifconfig(8)</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">bce</code> device driver first appeared in - <span class="Ux">FreeBSD 6.1</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">bce</code> driver was written by - <span class="An">David Christensen</span> - <<a class="Mt" href="mailto:davidch@broadcom.com">davidch@broadcom.com</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 4, 2012</td> - <td class="foot-os">FreeBSD 15.0</td> - </tr> -</table> |