| bnxt.4 (d933e97f9d7c919e68dc6aca4a6819a13ab3fbbf) | bnxt.4 (443788c26716250d8110b6aa6df481634a1a268f) |
|---|---|
| 1.\" Copyright (c) 2016 Broadcom, All Rights Reserved. 2.\" The term Broadcom refers to Broadcom Limited and/or its subsidiaries 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 8.\" 1. Redistributions of source code must retain the above copyright --- 11 unchanged lines hidden (view full) --- 20.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 21.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 22.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 23.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 24.\" THE POSSIBILITY OF SUCH DAMAGE. 25.\" 26.\" $FreeBSD$ 27.\" | 1.\" Copyright (c) 2016 Broadcom, All Rights Reserved. 2.\" The term Broadcom refers to Broadcom Limited and/or its subsidiaries 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 8.\" 1. Redistributions of source code must retain the above copyright --- 11 unchanged lines hidden (view full) --- 20.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 21.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 22.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 23.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 24.\" THE POSSIBILITY OF SUCH DAMAGE. 25.\" 26.\" $FreeBSD$ 27.\" |
| 28.Dd May 12, 2016 | 28.Dd November 16, 2016 |
| 29.Dt BNXT 4 30.Os 31.Sh NAME 32.Nm bnxt 33.Nd "Broadcom NetXtreme-C/NetXtreme-E Family Ethernet driver" 34.Sh SYNOPSIS 35To compile this driver into the kernel, 36place the following lines in your --- 47 unchanged lines hidden (view full) --- 84.It 85Broadcom BCM57407 NetXtreme-E 25Gb Ethernet Controller 86.It 87Broadcom BCM57304 NetXtreme-C Virtual Function 88.It 89Broadcom BCM57404 NetXtreme-E Virtual Function 90.El 91.Sh SYSCTL VARIABLES | 29.Dt BNXT 4 30.Os 31.Sh NAME 32.Nm bnxt 33.Nd "Broadcom NetXtreme-C/NetXtreme-E Family Ethernet driver" 34.Sh SYNOPSIS 35To compile this driver into the kernel, 36place the following lines in your --- 47 unchanged lines hidden (view full) --- 84.It 85Broadcom BCM57407 NetXtreme-E 25Gb Ethernet Controller 86.It 87Broadcom BCM57304 NetXtreme-C Virtual Function 88.It 89Broadcom BCM57404 NetXtreme-E Virtual Function 90.El 91.Sh SYSCTL VARIABLES |
| 92These variables must be set before loading the driver, either via | 92These variables must be set before loading the driver, either via |
| 93.Xr loader.conf 5 94or through the use of 95.Xr kenv 1 . 96These are provided by the 97.Xr iflib 9 98framework, and might be better documented there. 99.Bl -tag -width indent 100.It Va dev.bnxt.X.iflib.override_nrxds --- 59 unchanged lines hidden (view full) --- 160.El 161.Pp 162These 163.Xr sysctl 8 164variables are read-only: 165.Bl -tag -width indent 166.It Va dev.bnxt.X.if_name 167Current interface name of the device. | 93.Xr loader.conf 5 94or through the use of 95.Xr kenv 1 . 96These are provided by the 97.Xr iflib 9 98framework, and might be better documented there. 99.Bl -tag -width indent 100.It Va dev.bnxt.X.iflib.override_nrxds --- 59 unchanged lines hidden (view full) --- 160.El 161.Pp 162These 163.Xr sysctl 8 164variables are read-only: 165.Bl -tag -width indent 166.It Va dev.bnxt.X.if_name 167Current interface name of the device. |
| 168This will normally be | 168This will normally be |
| 169.Va bnxtX , 170but this can be changed using 171.Cm ifconfig name . | 169.Va bnxtX , 170but this can be changed using 171.Cm ifconfig name . |
| 172This sysctl allows correlating an interface with a child of dev.bnxt. | 172This sysctl allows correlating an interface with a child of 173.Va dev.bnxt . |
| 173.It Va dev.bnxt.X.nvram.* 174Information about the NVRAM device which contains the device firmware. 175.It Va dev.bnxt.X.ver.* 176Version-related information about the device and firmware: 177.It Va dev.bnxt.X.ver.hwrm_if 178Supported HWRM API version of the currently running firmware. 179.It Va dev.bnxt.X.ver.driver_hwrm_if 180HWRM API version the driver was built to support. --- 5 unchanged lines hidden (view full) --- 186incorrect destination MAC, unsubscribed multicast address, and other normal 187reasons to ignore Ethernet frames. 188.El 189.Sh DIAGNOSTICS 190.Bl -diag 191.It "bnxt%d: %s command returned %s error." 192Device firmware rejected a command from the driver. 193There might be a driver/firmware HWRM API mismatch. | 174.It Va dev.bnxt.X.nvram.* 175Information about the NVRAM device which contains the device firmware. 176.It Va dev.bnxt.X.ver.* 177Version-related information about the device and firmware: 178.It Va dev.bnxt.X.ver.hwrm_if 179Supported HWRM API version of the currently running firmware. 180.It Va dev.bnxt.X.ver.driver_hwrm_if 181HWRM API version the driver was built to support. --- 5 unchanged lines hidden (view full) --- 187incorrect destination MAC, unsubscribed multicast address, and other normal 188reasons to ignore Ethernet frames. 189.El 190.Sh DIAGNOSTICS 191.Bl -diag 192.It "bnxt%d: %s command returned %s error." 193Device firmware rejected a command from the driver. 194There might be a driver/firmware HWRM API mismatch. |
| 194.It "bnxt%d: Timeout sending %s (timeout: %d) seq %d\n" | 195.It "bnxt%d: Timeout sending %s (timeout: %d) seq %d" |
| 195Device firmware unresponsive. 196A PCI device reset is likely needed. | 196Device firmware unresponsive. 197A PCI device reset is likely needed. |
| 197.It "bnxt%d: Timeout sending %s (timeout: %d) msg {0x%x 0x%x} len:%d v: %d\n" | 198.It "bnxt%d: Timeout sending %s (timeout: %d) msg {0x%x 0x%x} len:%d v: %d" |
| 198Partial firmware response. 199A PCI device reset is likely needed. 200.Pp 201As of this writing, the system must be rebooted to initiate a PCI device reset. 202.El 203.Sh SEE ALSO 204.Xr altq 4 , 205.Xr arp 4 , | 199Partial firmware response. 200A PCI device reset is likely needed. 201.Pp 202As of this writing, the system must be rebooted to initiate a PCI device reset. 203.El 204.Sh SEE ALSO 205.Xr altq 4 , 206.Xr arp 4 , |
| 207.Xr iflib 4 , |
|
| 206.Xr netintro 4 , 207.Xr ng_ether 4 , 208.Xr vlan 4 , | 208.Xr netintro 4 , 209.Xr ng_ether 4 , 210.Xr vlan 4 , |
| 209.Xr ifconfig 8 , 210.Xr iflib 4 | 211.Xr ifconfig 8 |
| 211.Sh HISTORY 212The 213.Nm 214device driver first appeared in 215.Fx 12.0 . 216.Sh AUTHORS | 212.Sh HISTORY 213The 214.Nm 215device driver first appeared in 216.Fx 12.0 . 217.Sh AUTHORS |
| 218.An -nosplit |
|
| 217The 218.Nm 219driver was written by | 219The 220.Nm 221driver was written by |
| 220.An Jack Vogel Aq Mt jfvogel@gmail.com . | 222.An Jack Vogel Aq Mt jfvogel@gmail.com , |
| 221and is currently maintained by 222.An Stephen Hurd Aq Mt stephen.hurd@broadcom.com . | 223and is currently maintained by 224.An Stephen Hurd Aq Mt stephen.hurd@broadcom.com . |