2 # Intel network device configuration
5 config NET_VENDOR_INTEL
9 If you have a network (Ethernet) card belonging to this class, say Y.
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.
19 tristate "Intel(R) PRO/100+ support"
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).
28 Use the above information and the Adapter & Driver ID Guide at:
30 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
32 to identify the adapter.
34 For the latest Intel PRO/100 network driver for Linux, see:
36 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
38 More specific information on configuring the driver is in
39 <file:Documentation/networking/e100.txt>.
41 To compile this driver as a module, choose M here. The module
45 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
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:
52 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
54 For general information and support, go to the Intel support
57 <http://support.intel.com>
59 More specific information on configuring the driver is in
60 <file:Documentation/networking/e1000.txt>.
62 To compile this driver as a module, choose M here. The module
66 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
67 depends on PCI && (!SPARC32 || BROKEN)
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:
76 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
78 For general information and support, go to the Intel support
81 <http://support.intel.com>
83 To compile this driver as a module, choose M here. The module
84 will be called e1000e.
87 bool "Support HW cross-timestamp on PCH devices"
89 depends on E1000E && X86
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).
96 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
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:
106 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
108 For general information and support, go to the Intel support
111 <http://support.intel.com>
113 More specific information on configuring the driver is in
114 <file:Documentation/networking/e1000.txt>.
116 To compile this driver as a module, choose M here. The module
120 bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
122 depends on IGB && HWMON && !(IGB=y && HWMON=m)
124 Say Y if you want to expose thermal sensor data on Intel devices.
126 Some of our devices contain thermal sensors, both external and internal.
127 This data is available via the hwmon sysfs interface and exposes
131 bool "Direct Cache Access (DCA) Support"
133 depends on IGB && DCA && !(IGB=y && DCA=m)
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.
140 tristate "Intel(R) 82576 Virtual Function Ethernet support"
143 This driver supports Intel(R) 82576 virtual functions. For more
144 information on how to identify your adapter, go to the Adapter &
147 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
149 For general information and support, go to the Intel support
152 <http://support.intel.com>
154 More specific information on configuring the driver is in
155 <file:Documentation/networking/e1000.txt>.
157 To compile this driver as a module, choose M here. The module
158 will be called igbvf.
161 tristate "Intel(R) PRO/10GbE support"
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:
169 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
171 For general information and support, go to the Intel support
174 <http://support.intel.com>
176 More specific information on configuring the driver is in
177 <file:Documentation/networking/ixgb.txt>.
179 To compile this driver as a module, choose M here. The module
183 tristate "Intel(R) 10GbE PCI Express adapters support"
186 select PTP_1588_CLOCK
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:
192 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
194 For general information and support, go to the Intel support
197 <http://support.intel.com>
199 To compile this driver as a module, choose M here. The module
200 will be called ixgbe.
203 bool "Virtual eXtensible Local Area Network Support"
205 depends on IXGBE && VXLAN && !(IXGBE=y && VXLAN=m)
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.
214 bool "Intel(R) 10GbE PCI Express adapters HWMON support"
216 depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
218 Say Y if you want to expose the thermal sensor data on some of
219 our cards, via a hwmon sysfs interface.
222 bool "Direct Cache Access (DCA) Support"
224 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
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.
231 bool "Data Center Bridging (DCB) Support"
233 depends on IXGBE && DCB
235 Say Y here if you want to use Data Center Bridging (DCB) in the
241 tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
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:
248 <http://support.intel.com/support/network/sb/CS-008441.htm>
250 For general information and support, go to the Intel support
253 <http://support.intel.com>
255 More specific information on configuring the driver is in
256 <file:Documentation/networking/ixgbevf.txt>.
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.
263 tristate "Intel(R) Ethernet Controller XL710 Family support"
264 select PTP_1588_CLOCK
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:
271 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
273 For general information and support, go to the Intel support
276 <http://support.intel.com>
278 To compile this driver as a module, choose M here. The module
282 bool "Virtual eXtensible Local Area Network Support"
284 depends on I40E && VXLAN && !(I40E=y && VXLAN=m)
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.
293 bool "Generic Network Virtualization Encapsulation (GENEVE) Support"
294 depends on I40E && GENEVE && !(I40E=y && GENEVE=m)
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.
303 bool "Data Center Bridging (DCB) Support"
305 depends on I40E && DCB
307 Say Y here if you want to use Data Center Bridging (DCB) in the
313 bool "Fibre Channel over Ethernet (FCoE)"
315 depends on I40E && DCB && FCOE
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.
324 tristate "Intel(R) XL710 X710 Virtual Function Ethernet support"
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:
331 <http://support.intel.com/support/network/sb/CS-008441.htm>
333 For general information and support, go to the Intel support
336 <http://support.intel.com>
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.
343 tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
346 select PTP_1588_CLOCK
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:
352 <http://support.intel.com/support/network/sb/CS-008441.htm>
354 For general information and support, go to the Intel support
357 <http://support.intel.com>
359 To compile this driver as a module, choose M here. The module
360 will be called fm10k. MSI-X interrupt support is required
363 bool "Virtual eXtensible Local Area Network Support"
365 depends on FM10K && VXLAN && !(FM10K=y && VXLAN=m)
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.
373 endif # NET_VENDOR_INTEL