d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- Correct some typos

Browse Source 
- New sentence, new line
This commit is contained in:
Christian Brueffer 2006-04-10 20:12:17 +00:00
parent d8636a9ab7
commit 6e78bb8c0b
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
share/man/man4/bce.4
View File

@ -57,8 +57,9 @@ BCM5706 and BCM5708 Ethernet controllers.
.Pp .Pp
The NetXtreme II product family is composed of various Converged NIC (or CNIC) 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), Ethernet controllers which support a TCP Offload Engine (TOE), Remote DMA (RDMA),
and iSCSI acceleration, in addtion to standard L2 Ethernet traffic, all on the and iSCSI acceleration, in addition to standard L2 Ethernet traffic, all on the
same controller. The following features are supported in the same controller.
The following features are supported in the
.Nm .Nm
driver under FreeBSD: driver under FreeBSD:
.Bd -literal -offset indent .Bd -literal -offset indent
@ -122,7 +123,7 @@ For more information on configuring this device, see
The The
.Nm .Nm
driver provides support for various NICs based on the Broadcom NetXtreme II driver provides support for various NICs based on the Broadcom NetXtreme II
family of Gigabit Ethernet controller, including the family of Gigabit Ethernet controllers, including the
following: following:
.Pp .Pp
.Bl -bullet -compact .Bl -bullet -compact
@ -225,13 +226,15 @@ The driver could not map the RX mbuf memory into the controller's DMA
address space. address space.
.It "bce%d: Firmware synchronization timeout!" .It "bce%d: Firmware synchronization timeout!"
The driver was not able to synchronize with the firmware running on the The driver was not able to synchronize with the firmware running on the
controller. The firmware may be stopped or hung. controller.
The firmware may be stopped or hung.
.It "bce%d: Invalid Ethernet address!" .It "bce%d: Invalid Ethernet address!"
The driver was not able to read a vaild Ethernet MAC address from NVRAM. The driver was not able to read a vaild Ethernet MAC address from NVRAM.
.It "bce%d: Reset failed!" .It "bce%d: Reset failed!"
The driver has encountered a fatal initialization error. The driver has encountered a fatal initialization error.
.It "bce%d: Byte swap is incorrect!" .It "bce%d: Byte swap is incorrect!"
The driver has encountered a fatal initialization error. Contact the author The driver has encountered a fatal initialization error.
Contact the author
with details of the CPU architecture and system chipset in use. with details of the CPU architecture and system chipset in use.
.It "bce%d: Firmware did not complete initialization!" .It "bce%d: Firmware did not complete initialization!"
The driver has encountered a fatal initialization error. The driver has encountered a fatal initialization error.
@ -241,7 +244,8 @@ The driver has encountered a fatal initialization error.
The driver could not map a RX mbuf into DMA addressable memory. The driver could not map a RX mbuf into DMA addressable memory.
.It "bce%d: Error filling RX chain: rx_bd[0x%04X]!" .It "bce%d: Error filling RX chain: rx_bd[0x%04X]!"
The driver was unable to allocate enough mbufs to fill the RX chain The driver was unable to allocate enough mbufs to fill the RX chain
during initialization. Try increasing the number of mbufs available in during initialization.
Try increasing the number of mbufs available in
the system, increase system memory, or if using jumbo frames, make sure the system, increase system memory, or if using jumbo frames, make sure
enough 9KB mbufs are available. enough 9KB mbufs are available.
.It "bce%d: Failed to allocate new mbuf, incoming frame dropped!" .It "bce%d: Failed to allocate new mbuf, incoming frame dropped!"
@ -270,8 +274,8 @@ Disabling VLAN tag stripping is not currently supported by the driver.
The device has stopped responding to the network, there is a problem The device has stopped responding to the network, there is a problem
with the cable connection, or a driver logic problem has occurred.. with the cable connection, or a driver logic problem has occurred..
.It "bce%d: Fatal attention detected: 0x%08X!" .It "bce%d: Fatal attention detected: 0x%08X!"
A controller hardware failure has occurred. If the problem continues replace A controller hardware failure has occurred.
the controller. If the problem continues replace the controller.
.El .El
.Sh SEE ALSO .Sh SEE ALSO
.Xr arp 4 , .Xr arp 4 ,