i40e: reset VFs after PF reset
[deliverable/linux.git] / drivers / net / ethernet / intel / Kconfig
1 #
2 # Intel network device configuration
3 #
4
5 config 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 and read the Ethernet-HOWTO, available from
11 <http://www.tldp.org/docs.html#howto>.
12
13 Note that the answer to this question doesn't directly affect the
14 kernel: saying N will just cause the configurator to skip all
15 the questions about Intel cards. If you say Y, you will be asked for
16 your specific card in the following questions.
17
18 if NET_VENDOR_INTEL
19
20 config E100
21 tristate "Intel(R) PRO/100+ support"
22 depends on PCI
23 select MII
24 ---help---
25 This driver supports Intel(R) PRO/100 family of adapters.
26 To verify that your adapter is supported, find the board ID number
27 on the adapter. Look for a label that has a barcode and a number
28 in the format 123456-001 (six digits hyphen three digits).
29
30 Use the above information and the Adapter & Driver ID Guide at:
31
32 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
33
34 to identify the adapter.
35
36 For the latest Intel PRO/100 network driver for Linux, see:
37
38 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
39
40 More specific information on configuring the driver is in
41 <file:Documentation/networking/e100.txt>.
42
43 To compile this driver as a module, choose M here. The module
44 will be called e100.
45
46 config E1000
47 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
48 depends on PCI
49 ---help---
50 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
51 adapters. For more information on how to identify your adapter, go
52 to the Adapter & Driver ID Guide at:
53
54 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
55
56 For general information and support, go to the Intel support
57 website at:
58
59 <http://support.intel.com>
60
61 More specific information on configuring the driver is in
62 <file:Documentation/networking/e1000.txt>.
63
64 To compile this driver as a module, choose M here. The module
65 will be called e1000.
66
67 config E1000E
68 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
69 depends on PCI && (!SPARC32 || BROKEN)
70 select CRC32
71 select PTP_1588_CLOCK
72 ---help---
73 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
74 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
75 use the regular e1000 driver For more information on how to
76 identify your adapter, go to the Adapter & Driver ID Guide at:
77
78 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
79
80 For general information and support, go to the Intel support
81 website at:
82
83 <http://support.intel.com>
84
85 To compile this driver as a module, choose M here. The module
86 will be called e1000e.
87
88 config IGB
89 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
90 depends on PCI
91 select PTP_1588_CLOCK
92 select I2C
93 select I2C_ALGOBIT
94 ---help---
95 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
96 adapters. For more information on how to identify your adapter, go
97 to the Adapter & Driver ID Guide at:
98
99 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
100
101 For general information and support, go to the Intel support
102 website at:
103
104 <http://support.intel.com>
105
106 More specific information on configuring the driver is in
107 <file:Documentation/networking/e1000.txt>.
108
109 To compile this driver as a module, choose M here. The module
110 will be called igb.
111
112 config IGB_HWMON
113 bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
114 default y
115 depends on IGB && HWMON && !(IGB=y && HWMON=m)
116 ---help---
117 Say Y if you want to expose thermal sensor data on Intel devices.
118
119 Some of our devices contain thermal sensors, both external and internal.
120 This data is available via the hwmon sysfs interface and exposes
121 the onboard sensors.
122
123 config IGB_DCA
124 bool "Direct Cache Access (DCA) Support"
125 default y
126 depends on IGB && DCA && !(IGB=y && DCA=m)
127 ---help---
128 Say Y here if you want to use Direct Cache Access (DCA) in the
129 driver. DCA is a method for warming the CPU cache before data
130 is used, with the intent of lessening the impact of cache misses.
131
132 config IGBVF
133 tristate "Intel(R) 82576 Virtual Function Ethernet support"
134 depends on PCI
135 ---help---
136 This driver supports Intel(R) 82576 virtual functions. For more
137 information on how to identify your adapter, go to the Adapter &
138 Driver ID Guide at:
139
140 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
141
142 For general information and support, go to the Intel support
143 website at:
144
145 <http://support.intel.com>
146
147 More specific information on configuring the driver is in
148 <file:Documentation/networking/e1000.txt>.
149
150 To compile this driver as a module, choose M here. The module
151 will be called igbvf.
152
153 config IXGB
154 tristate "Intel(R) PRO/10GbE support"
155 depends on PCI
156 ---help---
157 This driver supports Intel(R) PRO/10GbE family of adapters for
158 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
159 instead. For more information on how to identify your adapter, go
160 to the Adapter & Driver ID Guide at:
161
162 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
163
164 For general information and support, go to the Intel support
165 website at:
166
167 <http://support.intel.com>
168
169 More specific information on configuring the driver is in
170 <file:Documentation/networking/ixgb.txt>.
171
172 To compile this driver as a module, choose M here. The module
173 will be called ixgb.
174
175 config IXGBE
176 tristate "Intel(R) 10GbE PCI Express adapters support"
177 depends on PCI
178 select MDIO
179 select PTP_1588_CLOCK
180 ---help---
181 This driver supports Intel(R) 10GbE PCI Express family of
182 adapters. For more information on how to identify your adapter, go
183 to the Adapter & Driver ID Guide at:
184
185 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
186
187 For general information and support, go to the Intel support
188 website at:
189
190 <http://support.intel.com>
191
192 To compile this driver as a module, choose M here. The module
193 will be called ixgbe.
194
195 config IXGBE_HWMON
196 bool "Intel(R) 10GbE PCI Express adapters HWMON support"
197 default y
198 depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
199 ---help---
200 Say Y if you want to expose the thermal sensor data on some of
201 our cards, via a hwmon sysfs interface.
202
203 config IXGBE_DCA
204 bool "Direct Cache Access (DCA) Support"
205 default y
206 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
207 ---help---
208 Say Y here if you want to use Direct Cache Access (DCA) in the
209 driver. DCA is a method for warming the CPU cache before data
210 is used, with the intent of lessening the impact of cache misses.
211
212 config IXGBE_DCB
213 bool "Data Center Bridging (DCB) Support"
214 default n
215 depends on IXGBE && DCB
216 ---help---
217 Say Y here if you want to use Data Center Bridging (DCB) in the
218 driver.
219
220 If unsure, say N.
221
222 config IXGBEVF
223 tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
224 depends on PCI_MSI
225 ---help---
226 This driver supports Intel(R) PCI Express virtual functions for the
227 Intel(R) ixgbe driver. For more information on how to identify your
228 adapter, go to the Adapter & Driver ID Guide at:
229
230 <http://support.intel.com/support/network/sb/CS-008441.htm>
231
232 For general information and support, go to the Intel support
233 website at:
234
235 <http://support.intel.com>
236
237 More specific information on configuring the driver is in
238 <file:Documentation/networking/ixgbevf.txt>.
239
240 To compile this driver as a module, choose M here. The module
241 will be called ixgbevf. MSI-X interrupt support is required
242 for this driver to work correctly.
243
244 config I40E
245 tristate "Intel(R) Ethernet Controller XL710 Family support"
246 select PTP_1588_CLOCK
247 depends on PCI
248 ---help---
249 This driver supports Intel(R) Ethernet Controller XL710 Family of
250 devices. For more information on how to identify your adapter, go
251 to the Adapter & Driver ID Guide at:
252
253 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
254
255 For general information and support, go to the Intel support
256 website at:
257
258 <http://support.intel.com>
259
260 To compile this driver as a module, choose M here. The module
261 will be called i40e.
262
263 config I40E_VXLAN
264 bool "Virtual eXtensible Local Area Network Support"
265 default n
266 depends on I40E && VXLAN && !(I40E=y && VXLAN=m)
267 ---help---
268 This allows one to create VXLAN virtual interfaces that provide
269 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
270 to tunnel virtual network infrastructure in virtualized environments.
271 Say Y here if you want to use Virtual eXtensible Local Area Network
272 (VXLAN) in the driver.
273
274 config I40E_DCB
275 bool "Data Center Bridging (DCB) Support"
276 default n
277 depends on I40E && DCB
278 ---help---
279 Say Y here if you want to use Data Center Bridging (DCB) in the
280 driver.
281
282 If unsure, say N.
283
284 config I40EVF
285 tristate "Intel(R) XL710 X710 Virtual Function Ethernet support"
286 depends on PCI_MSI
287 ---help---
288 This driver supports Intel(R) XL710 and X710 virtual functions.
289 For more information on how to identify your adapter, go to the
290 Adapter & Driver ID Guide at:
291
292 <http://support.intel.com/support/network/sb/CS-008441.htm>
293
294 For general information and support, go to the Intel support
295 website at:
296
297 <http://support.intel.com>
298
299 To compile this driver as a module, choose M here. The module
300 will be called i40evf. MSI-X interrupt support is required
301 for this driver to work correctly.
302
303 endif # NET_VENDOR_INTEL
This page took 0.036969 seconds and 5 git commands to generate.