1 .\" Copyright (c) 2006 Broadcom Corporation
2 .\" David Christensen <davidch@broadcom.com>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
13 .\" 3. Neither the name of Broadcom Corporation nor the name of its contributors
14 .\" may be used to endorse or promote products derived from this software
15 .\" without specific prior written consent.
17 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS'
18 .\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
19 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
20 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
21 .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
22 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
23 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
24 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
25 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
26 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
27 .\" THE POSSIBILITY OF SUCH DAMAGE.
36 .Nd "Broadcom NetXtreme II (BCM5706/BCM5708) PCI/PCIe Gigabit Ethernet adapter driver"
38 To compile this driver into the kernel,
39 place the following lines in your
40 kernel configuration file:
41 .Bd -ragged -offset indent
46 Alternatively, to load the driver as a
47 module at boot time, place the following line in
49 .Bd -literal -offset indent
55 driver supports Broadcom's NetXtreme II product family, including the
56 BCM5706 and BCM5708 Ethernet controllers.
58 The NetXtreme II product family is composed of various Converged NIC (or CNIC)
59 Ethernet controllers which support a TCP Offload Engine (TOE), Remote DMA (RDMA),
60 and iSCSI acceleration, in addition to standard L2 Ethernet traffic, all on the
62 The following features are supported in the
67 .Bl -item -offset indent -compact
69 IP/TCP/UDP checksum offload
71 Jumbo frames (up to 9022 bytes)
77 10/100/1000Mbps operation in full-duplex mode
79 10/100Mbps operation in half-duplex mode
84 driver supports the following media types:
85 .Bl -tag -width ".Cm 10baseT/UTP"
87 Enable autoselection of the media type and options.
88 The user can manually override
89 the autoselected mode by adding media options to
96 option can also be used to select either
102 Set 100Mbps (Fast Ethernet) operation.
106 option can also be used to select either
112 Set 1000baseTX operation over twisted pair.
120 driver supports the following media options:
121 .Bl -tag -width ".Cm full-duplex"
123 Force full duplex operation.
125 Force half duplex operation.
128 For more information on configuring this device, see
133 driver provides support for various NICs based on the Broadcom NetXtreme II
134 family of Gigabit Ethernet controllers, including the
139 HP NC370T Multifunction Gigabit Server Adapter
141 HP NC370i Multifunction Gigabit Server Adapter
145 .It "bce%d: PCI memory allocation failed!"
146 The driver has encountered a fatal initialization error.
147 .It "bce%d: PCI map interrupt failed!"
148 The driver has encountered a fatal initialization error.
149 .It "bce%d: Unsupported controller revision (%c%d)"
150 The driver does not support the controller revision in use.
151 .It "bce%d: Controller initialization failed!"
152 The driver has encountered a fatal initialization error.
153 .It "bce%d: NVRAM test failed!"
154 The driver could not access the controller NVRAM correctly.
155 .It "bce%d: DMA resource allocation failed!"
156 The driver could not allocate DMA memory to setup the controllers
157 host memory data structures.
158 .It "bce%d: Interface allocation failed!"
159 The driver could not create a network interface for the controller.
160 .It "bce%d: PHY probe failed!"
161 The driver could not access the PHY used by the controller.
162 .It "bce%d: Failed to setup IRQ!"
163 The driver could not initialize the IRQ handler.
164 .It "bce%d: Error: PHY read timeout!"
165 The driver could not read a PHY register before the timeout period expired.
166 .It "bce%d: PHY write timeout!"
167 The driver could not write to the PHY register because a timeout occurred.
168 .It "bce%d: Timeout error reading NVRAM at offset 0x%08X!"
169 The driver could not write to NVRAM because a timeout occurred.
170 .It "bce%d: Unknown Flash NVRAM found!"
171 The driver does not recognize the NVRAM device being used and therefore
172 cannot access it correctly.
173 .It "bce%d: Invalid NVRAM magic value!"
174 The driver cannot read NVRAM or the NVRAM is corrupt.
175 .It "bce%d: Invalid Manufacturing Information NVRAM CRC!"
176 The driver cannot read NVRAM or the NVRAM is corrupt.
177 .It "bce%d: Invalid Feature Configuration Information NVRAM CRC!"
178 The driver cannot read NVRAM or the NVRAM is corrupt.
179 .It "bce%d: DMA mapping error!"
180 The driver was unable to map memory into DMA addressable space required
182 .It "bce%d: Could not allocate parent DMA tag!"
183 The driver could not allocate a PCI compatible DMA tag.
184 .It "bce%d: Could not allocate status block DMA tag!"
185 The driver could not allocate a DMA tag for the controller's
187 .It "bce%d: Could not allocate status block DMA memory!"
188 The driver could not allocate DMA addressable memory for the controller's
190 .It "bce_d: Could not map status block DMA memory!"
191 The driver could not map the status block memory into the controller's DMA
193 .It "bce%d: Could not allocate statistics block DMA tag!"
194 The driver could not allocate a DMA tag for the controller's
196 .It "bce%d: Could not allocate statistics block DMA memory!"
197 The driver could not allocate DMA addressable memory for the controller's
199 .It "bce%d: Could not map statistics block DMA memory!"
200 The driver could not map the statistics block memory into the controller's DMA
202 .It "bce%d: Could not allocate TX descriptor chain DMA tag!"
203 The driver could not allocate a DMA tag for the controller's
205 .It "bce%d: Could not allocate TX descriptor chain DMA memory!
206 The driver could not allocate DMA addressable memory for the controller's
208 .It "bce%d: Could not map TX descriptor chain DMA memory!"
209 The driver could not map the TX descriptor chain memory into the controller's DMA
211 .It "bce%d: Could not allocate TX mbuf DMA tag!"
212 The driver could not allocate a DMA tag for the controller's
214 .It "bce%d: Unable to create TX mbuf DMA map!"
215 The driver could not map the TX mbuf memory into the controller's DMA
217 .It "bce%d: Could not allocate RX descriptor chain DMA tag!"
218 The driver could not allocate a DMA tag for the controller's
220 .It "bce%d: Could not allocate RX descriptor chain "
221 The driver could not allocate DMA addressable memory for the controller's
223 .It "bce%d: Could not map RX descriptor chain DMA memory!"
224 The driver could not map the RX descriptor chain memory into the controller's DMA
226 .It "bce%d: Could not allocate RX mbuf DMA tag!"
227 The driver could not allocate a DMA tag for the controller's
229 .It "bce%d: Unable to create RX mbuf DMA map!"
230 The driver could not map the RX mbuf memory into the controller's DMA
232 .It "bce%d: Firmware synchronization timeout!"
233 The driver was not able to synchronize with the firmware running on the
235 The firmware may be stopped or hung.
236 .It "bce%d: Invalid Ethernet address!"
237 The driver was not able to read a valid Ethernet MAC address from NVRAM.
238 .It "bce%d: Reset failed!"
239 The driver has encountered a fatal initialization error.
240 .It "bce%d: Byte swap is incorrect!"
241 The driver has encountered a fatal initialization error.
243 with details of the CPU architecture and system chipset in use.
244 .It "bce%d: Firmware did not complete initialization!"
245 The driver has encountered a fatal initialization error.
246 .It "bce%d: Bootcode not running!"
247 The driver has encountered a fatal initialization error.
248 .It "bce%d: Error mapping mbuf into RX chain!"
249 The driver could not map a RX mbuf into DMA addressable memory.
250 .It "bce%d: Error filling RX chain: rx_bd[0x%04X]!"
251 The driver was unable to allocate enough mbufs to fill the RX chain
252 during initialization.
253 Try increasing the number of mbufs available in
254 the system, increase system memory, or if using jumbo frames, make sure
255 enough 9KB mbufs are available.
256 .It "bce%d: Failed to allocate new mbuf, incoming frame dropped!"
257 The driver was unable to allocate a new mbuf for the RX chain and reused
258 the mbuf for the received frame, dropping the incoming frame in the process.
259 Try increasing the number of mbufs available in the system or increase system
261 .It "bce%d: Controller reset failed!"
262 A fatal initialization error has occurred.
263 .It "bce%d: Controller initialization failed!"
264 A fatal initialization error has occurred.
265 .It "bce%d: Block initialization failed!"
266 A fatal initialization error has occurred.
267 .It "bce%d: Error mapping mbuf into TX chain!"
268 The driver could not map a TX mbuf into DMA addressable memory.
269 .It "bce%d: Error registering poll function!"
270 The driver received an error while attempting to register the poll function.
271 .It "bce%d: Changing VLAN_MTU not supported."
272 Changing the VLAN MTU is not currently supported by the driver.
273 .It "bce%d: Cannot change VLAN_HWTAGGING while management firmware (ASF/IPMI/UMP) is running!"
274 Management firmware to support ASF/IPMI/UMP requires that VLAN
275 tag stripping be enabled in the controller.
276 .It "bce%d: Changing VLAN_HWTAGGING not supported!"
277 Disabling VLAN tag stripping is not currently supported by the driver.
278 .It "bce%d: Watchdog timeout occurred, resetting!"
279 The device has stopped responding to the network, there is a problem
280 with the cable connection, or a driver logic problem has occurred..
281 .It "bce%d: Fatal attention detected: 0x%08X!"
282 A controller hardware failure has occurred.
283 If the problem continues replace the controller.
296 device driver first appeared in
301 driver was written by
302 .An David Christensen Aq davidch@broadcom.com .