| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | # |
|---|
| 2 | 3 | # Solarflare device configuration |
|---|
| 3 | 4 | # |
|---|
| .. | .. |
|---|
| 5 | 6 | config NET_VENDOR_SOLARFLARE |
|---|
| 6 | 7 | bool "Solarflare devices" |
|---|
| 7 | 8 | default y |
|---|
| 8 | | - ---help--- |
|---|
| 9 | + help |
|---|
| 9 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
|---|
| 10 | 11 | |
|---|
| 11 | 12 | Note that the answer to this question doesn't directly affect the |
|---|
| .. | .. |
|---|
| 16 | 17 | if NET_VENDOR_SOLARFLARE |
|---|
| 17 | 18 | |
|---|
| 18 | 19 | config SFC |
|---|
| 19 | | - tristate "Solarflare SFC9000/SFC9100-family support" |
|---|
| 20 | + tristate "Solarflare SFC9000/SFC9100/EF100-family support" |
|---|
| 20 | 21 | depends on PCI |
|---|
| 21 | 22 | select MDIO |
|---|
| 22 | 23 | select CRC32 |
|---|
| 23 | | - select I2C |
|---|
| 24 | | - select I2C_ALGOBIT |
|---|
| 25 | 24 | imply PTP_1588_CLOCK |
|---|
| 26 | | - ---help--- |
|---|
| 25 | + help |
|---|
| 27 | 26 | This driver supports 10/40-gigabit Ethernet cards based on |
|---|
| 28 | 27 | the Solarflare SFC9000-family and SFC9100-family controllers. |
|---|
| 28 | + |
|---|
| 29 | + It also supports 10/25/40/100-gigabit Ethernet cards based |
|---|
| 30 | + on the Solarflare EF100 networking IP in Xilinx FPGAs. |
|---|
| 29 | 31 | |
|---|
| 30 | 32 | To compile this driver as a module, choose M here. The module |
|---|
| 31 | 33 | will be called sfc. |
|---|
| .. | .. |
|---|
| 33 | 35 | bool "Solarflare SFC9000/SFC9100-family MTD support" |
|---|
| 34 | 36 | depends on SFC && MTD && !(SFC=y && MTD=m) |
|---|
| 35 | 37 | default y |
|---|
| 36 | | - ---help--- |
|---|
| 38 | + help |
|---|
| 37 | 39 | This exposes the on-board flash and/or EEPROM as MTD devices |
|---|
| 38 | 40 | (e.g. /dev/mtd1). This is required to update the firmware or |
|---|
| 39 | 41 | the boot configuration under Linux. |
|---|
| .. | .. |
|---|
| 41 | 43 | bool "Solarflare SFC9000/SFC9100-family hwmon support" |
|---|
| 42 | 44 | depends on SFC && HWMON && !(SFC=y && HWMON=m) |
|---|
| 43 | 45 | default y |
|---|
| 44 | | - ---help--- |
|---|
| 46 | + help |
|---|
| 45 | 47 | This exposes the on-board firmware-managed sensors as a |
|---|
| 46 | 48 | hardware monitor device. |
|---|
| 47 | 49 | config SFC_SRIOV |
|---|
| 48 | 50 | bool "Solarflare SFC9000-family SR-IOV support" |
|---|
| 49 | 51 | depends on SFC && PCI_IOV |
|---|
| 50 | 52 | default y |
|---|
| 51 | | - ---help--- |
|---|
| 53 | + help |
|---|
| 52 | 54 | This enables support for the SFC9000 I/O Virtualization |
|---|
| 53 | 55 | features, allowing accelerated network performance in |
|---|
| 54 | 56 | virtualized environments. |
|---|
| .. | .. |
|---|
| 56 | 58 | bool "Solarflare SFC9000/SFC9100-family MCDI logging support" |
|---|
| 57 | 59 | depends on SFC |
|---|
| 58 | 60 | default y |
|---|
| 59 | | - ---help--- |
|---|
| 61 | + help |
|---|
| 60 | 62 | This enables support for tracing of MCDI (Management-Controller-to- |
|---|
| 61 | 63 | Driver-Interface) commands and responses, allowing debugging of |
|---|
| 62 | 64 | driver/firmware interaction. The tracing is actually enabled by |
|---|