1# 2# Intel network device configuration 3# 4 5config NET_VENDOR_INTEL 6 bool "Intel devices" 7 default y 8 ---help--- 9 If you have a network (Ethernet) card belonging to this class, say Y. 10 11 Note that the answer to this question doesn't directly affect the 12 kernel: saying N will just cause the configurator to skip all 13 the questions about Intel cards. If you say Y, you will be asked for 14 your specific card in the following questions. 15 16if NET_VENDOR_INTEL 17 18config E100 19 tristate "Intel(R) PRO/100+ support" 20 depends on PCI 21 select MII 22 ---help--- 23 This driver supports Intel(R) PRO/100 family of adapters. 24 To verify that your adapter is supported, find the board ID number 25 on the adapter. Look for a label that has a barcode and a number 26 in the format 123456-001 (six digits hyphen three digits). 27 28 Use the above information and the Adapter & Driver ID Guide at: 29 30 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 31 32 to identify the adapter. 33 34 For the latest Intel PRO/100 network driver for Linux, see: 35 36 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus> 37 38 More specific information on configuring the driver is in 39 <file:Documentation/networking/e100.txt>. 40 41 To compile this driver as a module, choose M here. The module 42 will be called e100. 43 44config E1000 45 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 46 depends on PCI 47 ---help--- 48 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 49 adapters. For more information on how to identify your adapter, go 50 to the Adapter & Driver ID Guide at: 51 52 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 53 54 For general information and support, go to the Intel support 55 website at: 56 57 <http://support.intel.com> 58 59 More specific information on configuring the driver is in 60 <file:Documentation/networking/e1000.txt>. 61 62 To compile this driver as a module, choose M here. The module 63 will be called e1000. 64 65config E1000E 66 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 67 depends on PCI && (!SPARC32 || BROKEN) 68 select CRC32 69 select PTP_1588_CLOCK 70 ---help--- 71 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 72 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 73 use the regular e1000 driver For more information on how to 74 identify your adapter, go to the Adapter & Driver ID Guide at: 75 76 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 77 78 For general information and support, go to the Intel support 79 website at: 80 81 <http://support.intel.com> 82 83 To compile this driver as a module, choose M here. The module 84 will be called e1000e. 85 86config E1000E_HWTS 87 bool "Support HW cross-timestamp on PCH devices" 88 default y 89 depends on E1000E && X86 90 ---help--- 91 Say Y to enable hardware supported cross-timestamping on PCH 92 devices. The cross-timestamp is available through the PTP clock 93 driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE). 94 95config IGB 96 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" 97 depends on PCI 98 select PTP_1588_CLOCK 99 select I2C 100 select I2C_ALGOBIT 101 ---help--- 102 This driver supports Intel(R) 82575/82576 gigabit ethernet family of 103 adapters. For more information on how to identify your adapter, go 104 to the Adapter & Driver ID Guide at: 105 106 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 107 108 For general information and support, go to the Intel support 109 website at: 110 111 <http://support.intel.com> 112 113 More specific information on configuring the driver is in 114 <file:Documentation/networking/e1000.txt>. 115 116 To compile this driver as a module, choose M here. The module 117 will be called igb. 118 119config IGB_HWMON 120 bool "Intel(R) PCI-Express Gigabit adapters HWMON support" 121 default y 122 depends on IGB && HWMON && !(IGB=y && HWMON=m) 123 ---help--- 124 Say Y if you want to expose thermal sensor data on Intel devices. 125 126 Some of our devices contain thermal sensors, both external and internal. 127 This data is available via the hwmon sysfs interface and exposes 128 the onboard sensors. 129 130config IGB_DCA 131 bool "Direct Cache Access (DCA) Support" 132 default y 133 depends on IGB && DCA && !(IGB=y && DCA=m) 134 ---help--- 135 Say Y here if you want to use Direct Cache Access (DCA) in the 136 driver. DCA is a method for warming the CPU cache before data 137 is used, with the intent of lessening the impact of cache misses. 138 139config IGBVF 140 tristate "Intel(R) 82576 Virtual Function Ethernet support" 141 depends on PCI 142 ---help--- 143 This driver supports Intel(R) 82576 virtual functions. For more 144 information on how to identify your adapter, go to the Adapter & 145 Driver ID Guide at: 146 147 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 148 149 For general information and support, go to the Intel support 150 website at: 151 152 <http://support.intel.com> 153 154 More specific information on configuring the driver is in 155 <file:Documentation/networking/e1000.txt>. 156 157 To compile this driver as a module, choose M here. The module 158 will be called igbvf. 159 160config IXGB 161 tristate "Intel(R) PRO/10GbE support" 162 depends on PCI 163 ---help--- 164 This driver supports Intel(R) PRO/10GbE family of adapters for 165 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 166 instead. For more information on how to identify your adapter, go 167 to the Adapter & Driver ID Guide at: 168 169 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 170 171 For general information and support, go to the Intel support 172 website at: 173 174 <http://support.intel.com> 175 176 More specific information on configuring the driver is in 177 <file:Documentation/networking/ixgb.txt>. 178 179 To compile this driver as a module, choose M here. The module 180 will be called ixgb. 181 182config IXGBE 183 tristate "Intel(R) 10GbE PCI Express adapters support" 184 depends on PCI 185 select MDIO 186 select PTP_1588_CLOCK 187 ---help--- 188 This driver supports Intel(R) 10GbE PCI Express family of 189 adapters. For more information on how to identify your adapter, go 190 to the Adapter & Driver ID Guide at: 191 192 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 193 194 For general information and support, go to the Intel support 195 website at: 196 197 <http://support.intel.com> 198 199 To compile this driver as a module, choose M here. The module 200 will be called ixgbe. 201 202config IXGBE_VXLAN 203 bool "Virtual eXtensible Local Area Network Support" 204 default n 205 depends on IXGBE && VXLAN && !(IXGBE=y && VXLAN=m) 206 ---help--- 207 This allows one to create VXLAN virtual interfaces that provide 208 Layer 2 Networks over Layer 3 Networks. VXLAN is often used 209 to tunnel virtual network infrastructure in virtualized environments. 210 Say Y here if you want to use Virtual eXtensible Local Area Network 211 (VXLAN) in the driver. 212 213config IXGBE_HWMON 214 bool "Intel(R) 10GbE PCI Express adapters HWMON support" 215 default y 216 depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m) 217 ---help--- 218 Say Y if you want to expose the thermal sensor data on some of 219 our cards, via a hwmon sysfs interface. 220 221config IXGBE_DCA 222 bool "Direct Cache Access (DCA) Support" 223 default y 224 depends on IXGBE && DCA && !(IXGBE=y && DCA=m) 225 ---help--- 226 Say Y here if you want to use Direct Cache Access (DCA) in the 227 driver. DCA is a method for warming the CPU cache before data 228 is used, with the intent of lessening the impact of cache misses. 229 230config IXGBE_DCB 231 bool "Data Center Bridging (DCB) Support" 232 default n 233 depends on IXGBE && DCB 234 ---help--- 235 Say Y here if you want to use Data Center Bridging (DCB) in the 236 driver. 237 238 If unsure, say N. 239 240config IXGBEVF 241 tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support" 242 depends on PCI_MSI 243 ---help--- 244 This driver supports Intel(R) PCI Express virtual functions for the 245 Intel(R) ixgbe driver. For more information on how to identify your 246 adapter, go to the Adapter & Driver ID Guide at: 247 248 <http://support.intel.com/support/network/sb/CS-008441.htm> 249 250 For general information and support, go to the Intel support 251 website at: 252 253 <http://support.intel.com> 254 255 More specific information on configuring the driver is in 256 <file:Documentation/networking/ixgbevf.txt>. 257 258 To compile this driver as a module, choose M here. The module 259 will be called ixgbevf. MSI-X interrupt support is required 260 for this driver to work correctly. 261 262config I40E 263 tristate "Intel(R) Ethernet Controller XL710 Family support" 264 select PTP_1588_CLOCK 265 depends on PCI 266 ---help--- 267 This driver supports Intel(R) Ethernet Controller XL710 Family of 268 devices. For more information on how to identify your adapter, go 269 to the Adapter & Driver ID Guide at: 270 271 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 272 273 For general information and support, go to the Intel support 274 website at: 275 276 <http://support.intel.com> 277 278 To compile this driver as a module, choose M here. The module 279 will be called i40e. 280 281config I40E_VXLAN 282 bool "Virtual eXtensible Local Area Network Support" 283 default n 284 depends on I40E && VXLAN && !(I40E=y && VXLAN=m) 285 ---help--- 286 This allows one to create VXLAN virtual interfaces that provide 287 Layer 2 Networks over Layer 3 Networks. VXLAN is often used 288 to tunnel virtual network infrastructure in virtualized environments. 289 Say Y here if you want to use Virtual eXtensible Local Area Network 290 (VXLAN) in the driver. 291 292config I40E_GENEVE 293 bool "Generic Network Virtualization Encapsulation (GENEVE) Support" 294 depends on I40E && GENEVE && !(I40E=y && GENEVE=m) 295 default n 296 ---help--- 297 This allows one to create GENEVE virtual interfaces that provide 298 Layer 2 Networks over Layer 3 Networks. GENEVE is often used 299 to tunnel virtual network infrastructure in virtualized environments. 300 Say Y here if you want to use GENEVE in the driver. 301 302config I40E_DCB 303 bool "Data Center Bridging (DCB) Support" 304 default n 305 depends on I40E && DCB 306 ---help--- 307 Say Y here if you want to use Data Center Bridging (DCB) in the 308 driver. 309 310 If unsure, say N. 311 312config I40E_FCOE 313 bool "Fibre Channel over Ethernet (FCoE)" 314 default n 315 depends on I40E && DCB && FCOE 316 ---help--- 317 Say Y here if you want to use Fibre Channel over Ethernet (FCoE) 318 in the driver. This will create new netdev for exclusive FCoE 319 use with XL710 FCoE offloads enabled. 320 321 If unsure, say N. 322 323config I40EVF 324 tristate "Intel(R) XL710 X710 Virtual Function Ethernet support" 325 depends on PCI_MSI 326 ---help--- 327 This driver supports Intel(R) XL710 and X710 virtual functions. 328 For more information on how to identify your adapter, go to the 329 Adapter & Driver ID Guide at: 330 331 <http://support.intel.com/support/network/sb/CS-008441.htm> 332 333 For general information and support, go to the Intel support 334 website at: 335 336 <http://support.intel.com> 337 338 To compile this driver as a module, choose M here. The module 339 will be called i40evf. MSI-X interrupt support is required 340 for this driver to work correctly. 341 342config FM10K 343 tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support" 344 default n 345 depends on PCI_MSI 346 select PTP_1588_CLOCK 347 ---help--- 348 This driver supports Intel(R) FM10000 Ethernet Switch Host 349 Interface. For more information on how to identify your adapter, 350 go to the Adapter & Driver ID Guide at: 351 352 <http://support.intel.com/support/network/sb/CS-008441.htm> 353 354 For general information and support, go to the Intel support 355 website at: 356 357 <http://support.intel.com> 358 359 To compile this driver as a module, choose M here. The module 360 will be called fm10k. MSI-X interrupt support is required 361 362config FM10K_VXLAN 363 bool "Virtual eXtensible Local Area Network Support" 364 default n 365 depends on FM10K && VXLAN && !(FM10K=y && VXLAN=m) 366 ---help--- 367 This allows one to create VXLAN virtual interfaces that provide 368 Layer 2 Networks over Layer 3 Networks. VXLAN is often used 369 to tunnel virtual network infrastructure in virtualized environments. 370 Say Y here if you want to use Virtual eXtensible Local Area Network 371 (VXLAN) in the driver. 372 373endif # NET_VENDOR_INTEL 374