Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 1 | # |
| 2 | # Intel network device configuration |
| 3 | # |
| 4 | |
| 5 | config NET_VENDOR_INTEL |
| 6 | bool "Intel devices" |
Jeff Kirsher | 88f0748 | 2011-08-23 01:29:52 -0700 | [diff] [blame] | 7 | default y |
Jeff Kirsher | 433aee0 | 2011-11-02 00:30:52 +0000 | [diff] [blame] | 8 | depends on PCI || PCI_MSI || ISA || ISA_DMA_API || ARM || \ |
| 9 | ARCH_ACORN || MCA || MCA_LEGACY || SNI_RM || SUN3 || \ |
Rob Herring | 695e007 | 2012-04-03 15:34:00 +0000 | [diff] [blame] | 10 | GSC || BVME6000 || MVME16x || \ |
Jeff Kirsher | 433aee0 | 2011-11-02 00:30:52 +0000 | [diff] [blame] | 11 | (ARM && ARCH_IXP4XX && IXP4XX_NPE && IXP4XX_QMGR) || \ |
| 12 | EXPERIMENTAL |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 13 | ---help--- |
| 14 | If you have a network (Ethernet) card belonging to this class, say Y |
| 15 | and read the Ethernet-HOWTO, available from |
| 16 | <http://www.tldp.org/docs.html#howto>. |
| 17 | |
| 18 | Note that the answer to this question doesn't directly affect the |
| 19 | kernel: saying N will just cause the configurator to skip all |
| 20 | the questions about Intel cards. If you say Y, you will be asked for |
| 21 | your specific card in the following questions. |
| 22 | |
| 23 | if NET_VENDOR_INTEL |
| 24 | |
| 25 | config E100 |
| 26 | tristate "Intel(R) PRO/100+ support" |
| 27 | depends on PCI |
Jeff Kirsher | aaba215 | 2011-09-14 21:23:14 +0000 | [diff] [blame] | 28 | select NET_CORE |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 29 | select MII |
| 30 | ---help--- |
| 31 | This driver supports Intel(R) PRO/100 family of adapters. |
| 32 | To verify that your adapter is supported, find the board ID number |
| 33 | on the adapter. Look for a label that has a barcode and a number |
| 34 | in the format 123456-001 (six digits hyphen three digits). |
| 35 | |
| 36 | Use the above information and the Adapter & Driver ID Guide at: |
| 37 | |
| 38 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 39 | |
| 40 | to identify the adapter. |
| 41 | |
| 42 | For the latest Intel PRO/100 network driver for Linux, see: |
| 43 | |
| 44 | <http://www.intel.com/p/en_US/support/highlights/network/pro100plus> |
| 45 | |
| 46 | More specific information on configuring the driver is in |
| 47 | <file:Documentation/networking/e100.txt>. |
| 48 | |
| 49 | To compile this driver as a module, choose M here. The module |
| 50 | will be called e100. |
| 51 | |
| 52 | config E1000 |
| 53 | tristate "Intel(R) PRO/1000 Gigabit Ethernet support" |
| 54 | depends on PCI |
| 55 | ---help--- |
| 56 | This driver supports Intel(R) PRO/1000 gigabit ethernet family of |
| 57 | adapters. For more information on how to identify your adapter, go |
| 58 | to the Adapter & Driver ID Guide at: |
| 59 | |
| 60 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 61 | |
| 62 | For general information and support, go to the Intel support |
| 63 | website at: |
| 64 | |
| 65 | <http://support.intel.com> |
| 66 | |
| 67 | More specific information on configuring the driver is in |
| 68 | <file:Documentation/networking/e1000.txt>. |
| 69 | |
| 70 | To compile this driver as a module, choose M here. The module |
| 71 | will be called e1000. |
| 72 | |
| 73 | config E1000E |
| 74 | tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" |
| 75 | depends on PCI && (!SPARC32 || BROKEN) |
| 76 | select CRC32 |
| 77 | ---help--- |
| 78 | This driver supports the PCI-Express Intel(R) PRO/1000 gigabit |
| 79 | ethernet family of adapters. For PCI or PCI-X e1000 adapters, |
| 80 | use the regular e1000 driver For more information on how to |
| 81 | identify your adapter, go to the Adapter & Driver ID Guide at: |
| 82 | |
| 83 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 84 | |
| 85 | For general information and support, go to the Intel support |
| 86 | website at: |
| 87 | |
| 88 | <http://support.intel.com> |
| 89 | |
| 90 | To compile this driver as a module, choose M here. The module |
| 91 | will be called e1000e. |
| 92 | |
| 93 | config IGB |
| 94 | tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" |
| 95 | depends on PCI |
Ben Hutchings | a24006e | 2012-10-31 15:33:52 +0000 | [diff] [blame^] | 96 | select PTP_1588_CLOCK |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 97 | ---help--- |
| 98 | This driver supports Intel(R) 82575/82576 gigabit ethernet family of |
| 99 | adapters. For more information on how to identify your adapter, go |
| 100 | to the Adapter & Driver ID Guide at: |
| 101 | |
| 102 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 103 | |
| 104 | For general information and support, go to the Intel support |
| 105 | website at: |
| 106 | |
| 107 | <http://support.intel.com> |
| 108 | |
| 109 | More specific information on configuring the driver is in |
| 110 | <file:Documentation/networking/e1000.txt>. |
| 111 | |
| 112 | To compile this driver as a module, choose M here. The module |
| 113 | will be called igb. |
| 114 | |
| 115 | config IGB_DCA |
| 116 | bool "Direct Cache Access (DCA) Support" |
| 117 | default y |
| 118 | depends on IGB && DCA && !(IGB=y && DCA=m) |
| 119 | ---help--- |
| 120 | Say Y here if you want to use Direct Cache Access (DCA) in the |
| 121 | driver. DCA is a method for warming the CPU cache before data |
| 122 | is used, with the intent of lessening the impact of cache misses. |
| 123 | |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 124 | config IGBVF |
| 125 | tristate "Intel(R) 82576 Virtual Function Ethernet support" |
| 126 | depends on PCI |
| 127 | ---help--- |
| 128 | This driver supports Intel(R) 82576 virtual functions. For more |
| 129 | information on how to identify your adapter, go to the Adapter & |
| 130 | Driver ID Guide at: |
| 131 | |
| 132 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 133 | |
| 134 | For general information and support, go to the Intel support |
| 135 | website at: |
| 136 | |
| 137 | <http://support.intel.com> |
| 138 | |
| 139 | More specific information on configuring the driver is in |
| 140 | <file:Documentation/networking/e1000.txt>. |
| 141 | |
| 142 | To compile this driver as a module, choose M here. The module |
| 143 | will be called igbvf. |
| 144 | |
| 145 | config IXGB |
| 146 | tristate "Intel(R) PRO/10GbE support" |
| 147 | depends on PCI |
| 148 | ---help--- |
| 149 | This driver supports Intel(R) PRO/10GbE family of adapters for |
| 150 | PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver |
| 151 | instead. For more information on how to identify your adapter, go |
| 152 | to the Adapter & Driver ID Guide at: |
| 153 | |
| 154 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 155 | |
| 156 | For general information and support, go to the Intel support |
| 157 | website at: |
| 158 | |
| 159 | <http://support.intel.com> |
| 160 | |
| 161 | More specific information on configuring the driver is in |
| 162 | <file:Documentation/networking/ixgb.txt>. |
| 163 | |
| 164 | To compile this driver as a module, choose M here. The module |
| 165 | will be called ixgb. |
| 166 | |
| 167 | config IXGBE |
| 168 | tristate "Intel(R) 10GbE PCI Express adapters support" |
| 169 | depends on PCI && INET |
| 170 | select MDIO |
Ben Hutchings | a24006e | 2012-10-31 15:33:52 +0000 | [diff] [blame^] | 171 | select PTP_1588_CLOCK |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 172 | ---help--- |
| 173 | This driver supports Intel(R) 10GbE PCI Express family of |
| 174 | adapters. For more information on how to identify your adapter, go |
| 175 | to the Adapter & Driver ID Guide at: |
| 176 | |
| 177 | <http://support.intel.com/support/network/adapter/pro100/21397.htm> |
| 178 | |
| 179 | For general information and support, go to the Intel support |
| 180 | website at: |
| 181 | |
| 182 | <http://support.intel.com> |
| 183 | |
| 184 | To compile this driver as a module, choose M here. The module |
| 185 | will be called ixgbe. |
| 186 | |
Don Skidmore | 3ca8bc6 | 2012-04-12 00:33:31 +0000 | [diff] [blame] | 187 | config IXGBE_HWMON |
| 188 | bool "Intel(R) 10GbE PCI Express adapters HWMON support" |
| 189 | default y |
| 190 | depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m) |
| 191 | ---help--- |
| 192 | Say Y if you want to expose the thermal sensor data on some of |
| 193 | our cards, via a hwmon sysfs interface. |
| 194 | |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 195 | config IXGBE_DCA |
| 196 | bool "Direct Cache Access (DCA) Support" |
| 197 | default y |
| 198 | depends on IXGBE && DCA && !(IXGBE=y && DCA=m) |
| 199 | ---help--- |
| 200 | Say Y here if you want to use Direct Cache Access (DCA) in the |
| 201 | driver. DCA is a method for warming the CPU cache before data |
| 202 | is used, with the intent of lessening the impact of cache misses. |
| 203 | |
| 204 | config IXGBE_DCB |
| 205 | bool "Data Center Bridging (DCB) Support" |
| 206 | default n |
| 207 | depends on IXGBE && DCB |
| 208 | ---help--- |
| 209 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 210 | driver. |
| 211 | |
| 212 | If unsure, say N. |
| 213 | |
Jeff Kirsher | dee1ad4 | 2011-04-07 07:42:33 -0700 | [diff] [blame] | 214 | config IXGBEVF |
| 215 | tristate "Intel(R) 82599 Virtual Function Ethernet support" |
| 216 | depends on PCI_MSI |
| 217 | ---help--- |
| 218 | This driver supports Intel(R) 82599 virtual functions. For more |
| 219 | information on how to identify your adapter, go to the Adapter & |
| 220 | Driver ID Guide at: |
| 221 | |
| 222 | <http://support.intel.com/support/network/sb/CS-008441.htm> |
| 223 | |
| 224 | For general information and support, go to the Intel support |
| 225 | website at: |
| 226 | |
| 227 | <http://support.intel.com> |
| 228 | |
| 229 | More specific information on configuring the driver is in |
| 230 | <file:Documentation/networking/ixgbevf.txt>. |
| 231 | |
| 232 | To compile this driver as a module, choose M here. The module |
| 233 | will be called ixgbevf. MSI-X interrupt support is required |
| 234 | for this driver to work correctly. |
| 235 | |
| 236 | endif # NET_VENDOR_INTEL |