[deliverable/linux.git] / drivers / net / ethernet / intel / Kconfig

#
# Intel network device configuration
#

config NET_VENDOR_INTEL
	bool "Intel devices"
	default y
	---help---
	  If you have a network (Ethernet) card belonging to this class, say Y.

	  Note that the answer to this question doesn't directly affect the
	  kernel: saying N will just cause the configurator to skip all
	  the questions about Intel cards. If you say Y, you will be asked for
	  your specific card in the following questions.

if NET_VENDOR_INTEL

config E100
	tristate "Intel(R) PRO/100+ support"
	depends on PCI
	select MII
	---help---
	  This driver supports Intel(R) PRO/100 family of adapters.
	  To verify that your adapter is supported, find the board ID number
	  on the adapter. Look for a label that has a barcode and a number
	  in the format 123456-001 (six digits hyphen three digits).

	  Use the above information and the Adapter & Driver ID Guide that
	  can be located at:

	  <http://support.intel.com>

	  to identify the adapter.

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/e100.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called e100.

config E1000
	tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
	depends on PCI
	---help---
	  This driver supports Intel(R) PRO/1000 gigabit ethernet family of
	  adapters.  For more information on how to identify your adapter, go
	  to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/e1000.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called e1000.

config E1000E
	tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
	depends on PCI && (!SPARC32 || BROKEN)
	select CRC32
	select PTP_1588_CLOCK
	---help---
	  This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
	  ethernet family of adapters. For PCI or PCI-X e1000 adapters,
	  use the regular e1000 driver For more information on how to
	  identify your adapter, go to the Adapter & Driver ID Guide that
	  can be located at:

	  <http://support.intel.com>

	  To compile this driver as a module, choose M here. The module
	  will be called e1000e.

config E1000E_HWTS
	bool "Support HW cross-timestamp on PCH devices"
	default y
	depends on E1000E && X86
	---help---
	 Say Y to enable hardware supported cross-timestamping on PCH
	 devices. The cross-timestamp is available through the PTP clock
	 driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).

config IGB
	tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
	depends on PCI
	select PTP_1588_CLOCK
	select I2C
	select I2C_ALGOBIT
	---help---
	  This driver supports Intel(R) 82575/82576 gigabit ethernet family of
	  adapters.  For more information on how to identify your adapter, go
	  to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/e1000.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called igb.

config IGB_HWMON
	bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
	default y
	depends on IGB && HWMON && !(IGB=y && HWMON=m)
	---help---
	  Say Y if you want to expose thermal sensor data on Intel devices.

	  Some of our devices contain thermal sensors, both external and internal.
	  This data is available via the hwmon sysfs interface and exposes
	  the onboard sensors.

config IGB_DCA
	bool "Direct Cache Access (DCA) Support"
	default y
	depends on IGB && DCA && !(IGB=y && DCA=m)
	---help---
	  Say Y here if you want to use Direct Cache Access (DCA) in the
	  driver.  DCA is a method for warming the CPU cache before data
	  is used, with the intent of lessening the impact of cache misses.

config IGBVF
	tristate "Intel(R) 82576 Virtual Function Ethernet support"
	depends on PCI
	---help---
	  This driver supports Intel(R) 82576 virtual functions.  For more
	  information on how to identify your adapter, go to the Adapter &
	  Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/e1000.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called igbvf.

config IXGB
	tristate "Intel(R) PRO/10GbE support"
	depends on PCI
	---help---
	  This driver supports Intel(R) PRO/10GbE family of adapters for
	  PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
	  instead. For more information on how to identify your adapter, go
	  to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/ixgb.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called ixgb.

config IXGBE
	tristate "Intel(R) 10GbE PCI Express adapters support"
	depends on PCI
	select MDIO
	select PTP_1588_CLOCK
	---help---
	  This driver supports Intel(R) 10GbE PCI Express family of
	  adapters.  For more information on how to identify your adapter, go
	  to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  To compile this driver as a module, choose M here. The module
	  will be called ixgbe.

config IXGBE_VXLAN
	bool "Virtual eXtensible Local Area Network Support"
	default n
	depends on IXGBE && VXLAN && !(IXGBE=y && VXLAN=m)
	---help---
	  This allows one to create VXLAN virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  Say Y here if you want to use Virtual eXtensible Local Area Network
	  (VXLAN) in the driver.

config IXGBE_HWMON
	bool "Intel(R) 10GbE PCI Express adapters HWMON support"
	default y
	depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
	---help---
	  Say Y if you want to expose the thermal sensor data on some of
	  our cards, via a hwmon sysfs interface.

config IXGBE_DCA
	bool "Direct Cache Access (DCA) Support"
	default y
	depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
	---help---
	  Say Y here if you want to use Direct Cache Access (DCA) in the
	  driver.  DCA is a method for warming the CPU cache before data
	  is used, with the intent of lessening the impact of cache misses.

config IXGBE_DCB
	bool "Data Center Bridging (DCB) Support"
	default n
	depends on IXGBE && DCB
	---help---
	  Say Y here if you want to use Data Center Bridging (DCB) in the
	  driver.

	  If unsure, say N.

config IXGBEVF
	tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
	depends on PCI_MSI
	---help---
	  This driver supports Intel(R) PCI Express virtual functions for the
	  Intel(R) ixgbe driver.  For more information on how to identify your
	  adapter, go to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  More specific information on configuring the driver is in
	  <file:Documentation/networking/ixgbevf.txt>.

	  To compile this driver as a module, choose M here. The module
	  will be called ixgbevf.  MSI-X interrupt support is required
	  for this driver to work correctly.

config I40E
	tristate "Intel(R) Ethernet Controller XL710 Family support"
	select PTP_1588_CLOCK
	depends on PCI
	---help---
	  This driver supports Intel(R) Ethernet Controller XL710 Family of
	  devices.  For more information on how to identify your adapter, go
	  to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  To compile this driver as a module, choose M here. The module
	  will be called i40e.

config I40E_VXLAN
	bool "Virtual eXtensible Local Area Network Support"
	default n
	depends on I40E && VXLAN && !(I40E=y && VXLAN=m)
	---help---
	  This allows one to create VXLAN virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  Say Y here if you want to use Virtual eXtensible Local Area Network
	  (VXLAN) in the driver.

config I40E_GENEVE
	bool "Generic Network Virtualization Encapsulation (GENEVE) Support"
	depends on I40E && GENEVE && !(I40E=y && GENEVE=m)
	default n
	---help---
	  This allows one to create GENEVE virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. GENEVE is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  Say Y here if you want to use GENEVE in the driver.

config I40E_DCB
	bool "Data Center Bridging (DCB) Support"
	default n
	depends on I40E && DCB
	---help---
	  Say Y here if you want to use Data Center Bridging (DCB) in the
	  driver.

	  If unsure, say N.

config I40E_FCOE
	bool "Fibre Channel over Ethernet (FCoE)"
	default n
	depends on I40E && DCB && FCOE
	---help---
	  Say Y here if you want to use Fibre Channel over Ethernet (FCoE)
	  in the driver. This will create new netdev for exclusive FCoE
	  use with XL710 FCoE offloads enabled.

	  If unsure, say N.

config I40EVF
	tristate "Intel(R) XL710 X710 Virtual Function Ethernet support"
	depends on PCI_MSI
	---help---
	  This driver supports Intel(R) XL710 and X710 virtual functions.
	  For more information on how to identify your adapter, go to the
	  Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  To compile this driver as a module, choose M here. The module
	  will be called i40evf.  MSI-X interrupt support is required
	  for this driver to work correctly.

config FM10K
	tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
	default n
	depends on PCI_MSI
	select PTP_1588_CLOCK
	---help---
	  This driver supports Intel(R) FM10000 Ethernet Switch Host
	  Interface.  For more information on how to identify your adapter,
	  go to the Adapter & Driver ID Guide that can be located at:

	  <http://support.intel.com>

	  To compile this driver as a module, choose M here. The module
	  will be called fm10k.  MSI-X interrupt support is required

config FM10K_VXLAN
	bool "Virtual eXtensible Local Area Network Support"
	default n
	depends on FM10K && VXLAN && !(FM10K=y && VXLAN=m)
	---help---
	  This allows one to create VXLAN virtual interfaces that provide
	  Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	  to tunnel virtual network infrastructure in virtualized environments.
	  Say Y here if you want to use Virtual eXtensible Local Area Network
	  (VXLAN) in the driver.

endif # NET_VENDOR_INTEL
Commit	Line	Data
dee1ad47 JK	1	#
	2	# Intel network device configuration
	3	#
	4
	5	config NET_VENDOR_INTEL
	6	bool "Intel devices"
88f07484	7	default y
dee1ad47	8	---help---
138b15ed	9	If you have a network (Ethernet) card belonging to this class, say Y.
dee1ad47 JK	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
	16	if NET_VENDOR_INTEL
	17
	18	config 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
5bd0c020 JB	28	Use the above information and the Adapter & Driver ID Guide that
5bd0c020 JB	29	can be located at:
dee1ad47	30
5bd0c020	31	<http://support.intel.com>
dee1ad47 JK	32
	33	to identify the adapter.
	34
dee1ad47 JK	35	More specific information on configuring the driver is in
	36	<file:Documentation/networking/e100.txt>.
	37
	38	To compile this driver as a module, choose M here. The module
	39	will be called e100.
	40
	41	config E1000
	42	tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
	43	depends on PCI
	44	---help---
	45	This driver supports Intel(R) PRO/1000 gigabit ethernet family of
	46	adapters. For more information on how to identify your adapter, go
5bd0c020	47	to the Adapter & Driver ID Guide that can be located at:
dee1ad47 JK	48
	49	<http://support.intel.com>
	50
	51	More specific information on configuring the driver is in
	52	<file:Documentation/networking/e1000.txt>.
	53
	54	To compile this driver as a module, choose M here. The module
	55	will be called e1000.
	56
	57	config E1000E
	58	tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
	59	depends on PCI && (!SPARC32 \|\| BROKEN)
	60	select CRC32
d89777bf	61	select PTP_1588_CLOCK
dee1ad47 JK	62	---help---
	63	This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
	64	ethernet family of adapters. For PCI or PCI-X e1000 adapters,
	65	use the regular e1000 driver For more information on how to
5bd0c020 JB	66	identify your adapter, go to the Adapter & Driver ID Guide that
5bd0c020 JB	67	can be located at:
dee1ad47 JK	68
	69	<http://support.intel.com>
	70
	71	To compile this driver as a module, choose M here. The module
	72	will be called e1000e.
	73
01d7ada5 CH	74	config E1000E_HWTS
	75	bool "Support HW cross-timestamp on PCH devices"
	76	default y
	77	depends on E1000E && X86
	78	---help---
	79	Say Y to enable hardware supported cross-timestamping on PCH
	80	devices. The cross-timestamp is available through the PTP clock
	81	driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
	82
dee1ad47 JK	83	config IGB
	84	tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
	85	depends on PCI
a24006ed	86	select PTP_1588_CLOCK
441fc6fd CW	87	select I2C
441fc6fd CW	88	select I2C_ALGOBIT
dee1ad47 JK	89	---help---
	90	This driver supports Intel(R) 82575/82576 gigabit ethernet family of
	91	adapters. For more information on how to identify your adapter, go
5bd0c020	92	to the Adapter & Driver ID Guide that can be located at:
dee1ad47 JK	93
	94	<http://support.intel.com>
	95
	96	More specific information on configuring the driver is in
	97	<file:Documentation/networking/e1000.txt>.
	98
	99	To compile this driver as a module, choose M here. The module
	100	will be called igb.
	101
e428893b CW	102	config IGB_HWMON
	103	bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
	104	default y
	105	depends on IGB && HWMON && !(IGB=y && HWMON=m)
	106	---help---
	107	Say Y if you want to expose thermal sensor data on Intel devices.
	108
	109	Some of our devices contain thermal sensors, both external and internal.
	110	This data is available via the hwmon sysfs interface and exposes
	111	the onboard sensors.
	112
dee1ad47 JK	113	config IGB_DCA
	114	bool "Direct Cache Access (DCA) Support"
	115	default y
	116	depends on IGB && DCA && !(IGB=y && DCA=m)
	117	---help---
	118	Say Y here if you want to use Direct Cache Access (DCA) in the
	119	driver. DCA is a method for warming the CPU cache before data
	120	is used, with the intent of lessening the impact of cache misses.
	121
	122	config IGBVF
	123	tristate "Intel(R) 82576 Virtual Function Ethernet support"
	124	depends on PCI
	125	---help---
	126	This driver supports Intel(R) 82576 virtual functions. For more
	127	information on how to identify your adapter, go to the Adapter &
5bd0c020	128	Driver ID Guide that can be located at:
dee1ad47 JK	129
	130	<http://support.intel.com>
	131
	132	More specific information on configuring the driver is in
	133	<file:Documentation/networking/e1000.txt>.
	134
	135	To compile this driver as a module, choose M here. The module
	136	will be called igbvf.
	137
	138	config IXGB
	139	tristate "Intel(R) PRO/10GbE support"
	140	depends on PCI
	141	---help---
	142	This driver supports Intel(R) PRO/10GbE family of adapters for
	143	PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
	144	instead. For more information on how to identify your adapter, go
5bd0c020	145	to the Adapter & Driver ID Guide that can be located at:
dee1ad47 JK	146
	147	<http://support.intel.com>
	148
	149	More specific information on configuring the driver is in
	150	<file:Documentation/networking/ixgb.txt>.
	151
	152	To compile this driver as a module, choose M here. The module
	153	will be called ixgb.
	154
	155	config IXGBE
	156	tristate "Intel(R) 10GbE PCI Express adapters support"
ff33c0e1	157	depends on PCI
dee1ad47	158	select MDIO
a24006ed	159	select PTP_1588_CLOCK
dee1ad47 JK	160	---help---
	161	This driver supports Intel(R) 10GbE PCI Express family of
	162	adapters. For more information on how to identify your adapter, go
5bd0c020	163	to the Adapter & Driver ID Guide that can be located at:
dee1ad47 JK	164
	165	<http://support.intel.com>
	166
	167	To compile this driver as a module, choose M here. The module
	168	will be called ixgbe.
	169
3f207800 DS	170	config IXGBE_VXLAN
	171	bool "Virtual eXtensible Local Area Network Support"
	172	default n
	173	depends on IXGBE && VXLAN && !(IXGBE=y && VXLAN=m)
	174	---help---
	175	This allows one to create VXLAN virtual interfaces that provide
	176	Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	177	to tunnel virtual network infrastructure in virtualized environments.
	178	Say Y here if you want to use Virtual eXtensible Local Area Network
	179	(VXLAN) in the driver.
	180
3ca8bc6d DS	181	config IXGBE_HWMON
	182	bool "Intel(R) 10GbE PCI Express adapters HWMON support"
	183	default y
	184	depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
	185	---help---
	186	Say Y if you want to expose the thermal sensor data on some of
	187	our cards, via a hwmon sysfs interface.
	188
dee1ad47 JK	189	config IXGBE_DCA
	190	bool "Direct Cache Access (DCA) Support"
	191	default y
	192	depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
	193	---help---
	194	Say Y here if you want to use Direct Cache Access (DCA) in the
	195	driver. DCA is a method for warming the CPU cache before data
	196	is used, with the intent of lessening the impact of cache misses.
	197
	198	config IXGBE_DCB
	199	bool "Data Center Bridging (DCB) Support"
	200	default n
	201	depends on IXGBE && DCB
	202	---help---
	203	Say Y here if you want to use Data Center Bridging (DCB) in the
	204	driver.
	205
	206	If unsure, say N.
	207
	208	config IXGBEVF
c0832b2c	209	tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
dee1ad47 JK	210	depends on PCI_MSI
dee1ad47 JK	211	---help---
c0832b2c JK	212	This driver supports Intel(R) PCI Express virtual functions for the
c0832b2c JK	213	Intel(R) ixgbe driver. For more information on how to identify your
5bd0c020	214	adapter, go to the Adapter & Driver ID Guide that can be located at:
dee1ad47 JK	215
	216	<http://support.intel.com>
	217
	218	More specific information on configuring the driver is in
	219	<file:Documentation/networking/ixgbevf.txt>.
	220
	221	To compile this driver as a module, choose M here. The module
	222	will be called ixgbevf. MSI-X interrupt support is required
	223	for this driver to work correctly.
	224
1bff6529 JB	225	config I40E
1bff6529 JB	226	tristate "Intel(R) Ethernet Controller XL710 Family support"
beb0dff1	227	select PTP_1588_CLOCK
1bff6529 JB	228	depends on PCI
	229	---help---
	230	This driver supports Intel(R) Ethernet Controller XL710 Family of
	231	devices. For more information on how to identify your adapter, go
5bd0c020	232	to the Adapter & Driver ID Guide that can be located at:
1bff6529 JB	233
	234	<http://support.intel.com>
	235
	236	To compile this driver as a module, choose M here. The module
	237	will be called i40e.
	238
6633d381 SA	239	config I40E_VXLAN
	240	bool "Virtual eXtensible Local Area Network Support"
	241	default n
	242	depends on I40E && VXLAN && !(I40E=y && VXLAN=m)
	243	---help---
	244	This allows one to create VXLAN virtual interfaces that provide
	245	Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	246	to tunnel virtual network infrastructure in virtualized environments.
	247	Say Y here if you want to use Virtual eXtensible Local Area Network
	248	(VXLAN) in the driver.
	249
c110c311 SA	250	config I40E_GENEVE
	251	bool "Generic Network Virtualization Encapsulation (GENEVE) Support"
	252	depends on I40E && GENEVE && !(I40E=y && GENEVE=m)
	253	default n
	254	---help---
	255	This allows one to create GENEVE virtual interfaces that provide
	256	Layer 2 Networks over Layer 3 Networks. GENEVE is often used
	257	to tunnel virtual network infrastructure in virtualized environments.
	258	Say Y here if you want to use GENEVE in the driver.
	259
9d488727 NP	260	config I40E_DCB
	261	bool "Data Center Bridging (DCB) Support"
	262	default n
	263	depends on I40E && DCB
	264	---help---
	265	Say Y here if you want to use Data Center Bridging (DCB) in the
	266	driver.
	267
a1c9a9d9 JK	268	If unsure, say N.
a1c9a9d9 JK	269
776d4e9f VD	270	config I40E_FCOE
	271	bool "Fibre Channel over Ethernet (FCoE)"
	272	default n
	273	depends on I40E && DCB && FCOE
	274	---help---
	275	Say Y here if you want to use Fibre Channel over Ethernet (FCoE)
	276	in the driver. This will create new netdev for exclusive FCoE
	277	use with XL710 FCoE offloads enabled.
	278
	279	If unsure, say N.
	280
105bf2fe GR	281	config I40EVF
	282	tristate "Intel(R) XL710 X710 Virtual Function Ethernet support"
	283	depends on PCI_MSI
	284	---help---
	285	This driver supports Intel(R) XL710 and X710 virtual functions.
	286	For more information on how to identify your adapter, go to the
5bd0c020	287	Adapter & Driver ID Guide that can be located at:
105bf2fe GR	288
	289	<http://support.intel.com>
	290
	291	To compile this driver as a module, choose M here. The module
	292	will be called i40evf. MSI-X interrupt support is required
	293	for this driver to work correctly.
	294
b3890e30 AD	295	config FM10K
	296	tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
	297	default n
	298	depends on PCI_MSI
b71b12dc	299	select PTP_1588_CLOCK
b3890e30 AD	300	---help---
	301	This driver supports Intel(R) FM10000 Ethernet Switch Host
	302	Interface. For more information on how to identify your adapter,
5bd0c020	303	go to the Adapter & Driver ID Guide that can be located at:
b3890e30 AD	304
	305	<http://support.intel.com>
	306
	307	To compile this driver as a module, choose M here. The module
	308	will be called fm10k. MSI-X interrupt support is required
	309
f6b03c10 AZ	310	config FM10K_VXLAN
	311	bool "Virtual eXtensible Local Area Network Support"
	312	default n
	313	depends on FM10K && VXLAN && !(FM10K=y && VXLAN=m)
	314	---help---
	315	This allows one to create VXLAN virtual interfaces that provide
	316	Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	317	to tunnel virtual network infrastructure in virtualized environments.
	318	Say Y here if you want to use Virtual eXtensible Local Area Network
	319	(VXLAN) in the driver.
	320
dee1ad47	321	endif # NET_VENDOR_INTEL