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

#
# Network device configuration
#

menuconfig NETDEVICES
	default y if UML
	depends on NET
	bool "Network device support"
	---help---
	  You can say N here if you don't intend to connect your Linux box to
	  any other computer at all.

	  You'll have to say Y if your computer contains a network card that
	  you want to use under Linux. If you are going to run SLIP or PPP over
	  telephone line or null modem cable you need say Y here. Connecting
	  two machines with parallel ports using PLIP needs this, as well as
	  AX.25/KISS for sending Internet traffic over amateur radio links.

	  See also "The Linux Network Administrator's Guide" by Olaf Kirch and
	  Terry Dawson. Available at <http://www.tldp.org/guides.html>.

	  If unsure, say Y.

# All the following symbols are dependent on NETDEVICES - do not repeat
# that for each of the symbols.
if NETDEVICES

config MII
	tristate

config NET_CORE
	default y
	bool "Network core driver support"
	---help---
	  You can say N here if you do not intend to use any of the
	  networking core drivers (i.e. VLAN, bridging, bonding, etc.)

if NET_CORE

config BONDING
	tristate "Bonding driver support"
	depends on INET
	depends on IPV6 || IPV6=n
	---help---
	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	  Channels together. This is called 'Etherchannel' by Cisco,
	  'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.

	  The driver supports multiple bonding modes to allow for both high
	  performance and high availability operation.

	  Refer to <file:Documentation/networking/bonding.txt> for more
	  information.

	  To compile this driver as a module, choose M here: the module
	  will be called bonding.

config DUMMY
	tristate "Dummy net driver support"
	---help---
	  This is essentially a bit-bucket device (i.e. traffic you send to
	  this device is consigned into oblivion) with a configurable IP
	  address. It is most commonly used in order to make your currently
	  inactive SLIP address seem like a real address for local programs.
	  If you use SLIP or PPP, you might want to say Y here. Since this
	  thing often comes in handy, the default is Y. It won't enlarge your
	  kernel either. What a deal. Read about it in the Network
	  Administrator's Guide, available from
	  <http://www.tldp.org/docs.html#guide>.

	  To compile this driver as a module, choose M here: the module
	  will be called dummy.

config EQUALIZER
	tristate "EQL (serial line load balancing) support"
	---help---
	  If you have two serial connections to some other computer (this
	  usually requires two modems and two telephone lines) and you use
	  SLIP (the protocol for sending Internet traffic over telephone
	  lines) or PPP (a better SLIP) on them, you can make them behave like
	  one double speed connection using this driver.  Naturally, this has
	  to be supported at the other end as well, either with a similar EQL
	  Linux driver or with a Livingston Portmaster 2e.

	  Say Y if you want this and read
	  <file:Documentation/networking/eql.txt>.  You may also want to read
	  section 6.2 of the NET-3-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

	  To compile this driver as a module, choose M here: the module
	  will be called eql.  If unsure, say N.

config NET_FC
	bool "Fibre Channel driver support"
	depends on SCSI && PCI
	help
	  Fibre Channel is a high speed serial protocol mainly used to connect
	  large storage devices to the computer; it is compatible with and
	  intended to replace SCSI.

	  If you intend to use Fibre Channel, you need to have a Fibre channel
	  adaptor card in your computer; say Y here and to the driver for your
	  adaptor below. You also should have said Y to "SCSI support" and
	  "SCSI generic support".

config IFB
	tristate "Intermediate Functional Block support"
	depends on NET_CLS_ACT
	---help---
	  This is an intermediate driver that allows sharing of
	  resources.
	  To compile this driver as a module, choose M here: the module
	  will be called ifb.  If you want to use more than one ifb
	  device at a time, you need to compile this driver as a module.
	  Instead of 'ifb', the devices will then be called 'ifb0',
	  'ifb1' etc.
	  Look at the iproute2 documentation directory for usage etc

source "drivers/net/team/Kconfig"

config MACVLAN
	tristate "MAC-VLAN support"
	---help---
	  This allows one to create virtual interfaces that map packets to
	  or from specific MAC addresses to a particular interface.

	  Macvlan devices can be added using the "ip" command from the
	  iproute2 package starting with the iproute2-2.6.23 release:

	  "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"

	  To compile this driver as a module, choose M here: the module
	  will be called macvlan.

config MACVTAP
	tristate "MAC-VLAN based tap driver"
	depends on MACVLAN
	help
	  This adds a specialized tap character device driver that is based
	  on the MAC-VLAN network interface, called macvtap. A macvtap device
	  can be added in the same way as a macvlan device, using 'type
	  macvtap', and then be accessed through the tap user space interface.

	  To compile this driver as a module, choose M here: the module
	  will be called macvtap.

config VXLAN
       tristate "Virtual eXtensible Local Area Network (VXLAN)"
       depends on INET
       select NET_IP_TUNNEL
       ---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.
	  For more information see:
	    http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02

	  To compile this driver as a module, choose M here: the module
	  will be called vxlan.

config NETCONSOLE
	tristate "Network console logging support"
	---help---
	If you want to log kernel messages over the network, enable this.
	See <file:Documentation/networking/netconsole.txt> for details.

config NETCONSOLE_DYNAMIC
	bool "Dynamic reconfiguration of logging targets"
	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
			!(NETCONSOLE=y && CONFIGFS_FS=m)
	help
	  This option enables the ability to dynamically reconfigure target
	  parameters (interface, IP addresses, port numbers, MAC addresses)
	  at runtime through a userspace interface exported using configfs.
	  See <file:Documentation/networking/netconsole.txt> for details.

config NETPOLL
	def_bool NETCONSOLE

config NET_POLL_CONTROLLER
	def_bool NETPOLL

config NTB_NETDEV
	tristate "Virtual Ethernet over NTB"
	depends on NTB

config RIONET
	tristate "RapidIO Ethernet over messaging driver support"
	depends on RAPIDIO

config RIONET_TX_SIZE
	int "Number of outbound queue entries"
	depends on RIONET
	default "128"

config RIONET_RX_SIZE
	int "Number of inbound queue entries"
	depends on RIONET
	default "128"

config TUN
	tristate "Universal TUN/TAP device driver support"
	select CRC32
	---help---
	  TUN/TAP provides packet reception and transmission for user space
	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
	  device, which instead of receiving packets from a physical media,
	  receives them from user space program and instead of sending packets
	  via physical media writes them to the user space program.

	  When a program opens /dev/net/tun, driver creates and registers
	  corresponding net device tunX or tapX.  After a program closed above
	  devices, driver will automatically delete tunXX or tapXX device and
	  all routes corresponding to it.

	  Please read <file:Documentation/networking/tuntap.txt> for more
	  information.

	  To compile this driver as a module, choose M here: the module
	  will be called tun.

	  If you don't know what to use this for, you don't need it.

config VETH
	tristate "Virtual ethernet pair device"
	---help---
	  This device is a local ethernet tunnel. Devices are created in pairs.
	  When one end receives the packet it appears on its pair and vice
	  versa.

config VIRTIO_NET
	tristate "Virtio network driver"
	depends on VIRTIO
	select AVERAGE
	---help---
	  This is the virtual network driver for virtio.  It can be used with
	  lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.

config NLMON
	tristate "Virtual netlink monitoring device"
	---help---
	  This option enables a monitoring net device for netlink skbs. The
	  purpose of this is to analyze netlink messages with packet sockets.
	  Thus applications like tcpdump will be able to see local netlink
	  messages if they tap into the netlink device, record pcaps for further
	  diagnostics, etc. This is mostly intended for developers or support
	  to debug netlink issues. If unsure, say N.

endif # NET_CORE

config SUNGEM_PHY
	tristate

source "drivers/net/arcnet/Kconfig"

source "drivers/atm/Kconfig"

source "drivers/net/caif/Kconfig"

source "drivers/net/dsa/Kconfig"

source "drivers/net/ethernet/Kconfig"

source "drivers/net/fddi/Kconfig"

source "drivers/net/hippi/Kconfig"

config NET_SB1000
	tristate "General Instruments Surfboard 1000"
	depends on PNP
	---help---
	  This is a driver for the General Instrument (also known as
	  NextLevel) SURFboard 1000 internal
	  cable modem. This is an ISA card which is used by a number of cable
	  TV companies to provide cable modem access. It's a one-way
	  downstream-only cable modem, meaning that your upstream net link is
	  provided by your regular phone modem.

	  At present this driver only compiles as a module, so say M here if
	  you have this card. The module will be called sb1000. Then read
	  <file:Documentation/networking/README.sb1000> for information on how
	  to use this module, as it needs special ppp scripts for establishing
	  a connection. Further documentation and the necessary scripts can be
	  found at:

	  <http://www.jacksonville.net/~fventuri/>
	  <http://home.adelphia.net/~siglercm/sb1000.html>
	  <http://linuxpower.cx/~cable/>

	  If you don't have this card, of course say N.

source "drivers/net/phy/Kconfig"

source "drivers/net/plip/Kconfig"

source "drivers/net/ppp/Kconfig"

source "drivers/net/slip/Kconfig"

source "drivers/s390/net/Kconfig"

source "drivers/net/usb/Kconfig"

source "drivers/net/wireless/Kconfig"

source "drivers/net/wimax/Kconfig"

source "drivers/net/wan/Kconfig"

source "drivers/net/ieee802154/Kconfig"

config XEN_NETDEV_FRONTEND
	tristate "Xen network device frontend driver"
	depends on XEN
	select XEN_XENBUS_FRONTEND
	default y
	help
	  This driver provides support for Xen paravirtual network
	  devices exported by a Xen network driver domain (often
	  domain 0).

	  The corresponding Linux backend driver is enabled by the
	  CONFIG_XEN_NETDEV_BACKEND option.

	  If you are compiling a kernel for use as Xen guest, you
	  should say Y here. To compile this driver as a module, chose
	  M here: the module will be called xen-netfront.

config XEN_NETDEV_BACKEND
	tristate "Xen backend network device"
	depends on XEN_BACKEND
	help
	  This driver allows the kernel to act as a Xen network driver
	  domain which exports paravirtual network devices to other
	  Xen domains. These devices can be accessed by any operating
	  system that implements a compatible front end.

	  The corresponding Linux frontend driver is enabled by the
	  CONFIG_XEN_NETDEV_FRONTEND configuration option.

	  The backend driver presents a standard network device
	  endpoint for each paravirtual network device to the driver
	  domain network stack. These can then be bridged or routed
	  etc in order to provide full network connectivity.

	  If you are compiling a kernel to run in a Xen network driver
	  domain (often this is domain 0) you should say Y here. To
	  compile this driver as a module, chose M here: the module
	  will be called xen-netback.

config VMXNET3
	tristate "VMware VMXNET3 ethernet driver"
	depends on PCI && INET
	help
	  This driver supports VMware's vmxnet3 virtual ethernet NIC.
	  To compile this driver as a module, choose M here: the
	  module will be called vmxnet3.

source "drivers/net/hyperv/Kconfig"

endif # NETDEVICES
Commit	Line	Data
	1	#
	2	# Network device configuration
	3	#
	4
	5	menuconfig NETDEVICES
	6	default y if UML
	7	depends on NET
	8	bool "Network device support"
	9	---help---
	10	You can say N here if you don't intend to connect your Linux box to
	11	any other computer at all.
	12
	13	You'll have to say Y if your computer contains a network card that
	14	you want to use under Linux. If you are going to run SLIP or PPP over
	15	telephone line or null modem cable you need say Y here. Connecting
	16	two machines with parallel ports using PLIP needs this, as well as
	17	AX.25/KISS for sending Internet traffic over amateur radio links.
	18
	19	See also "The Linux Network Administrator's Guide" by Olaf Kirch and
	20	Terry Dawson. Available at <http://www.tldp.org/guides.html>.
	21
	22	If unsure, say Y.
	23
	24	# All the following symbols are dependent on NETDEVICES - do not repeat
	25	# that for each of the symbols.
	26	if NETDEVICES
	27
	28	config MII
	29	tristate
	30
	31	config NET_CORE
	32	default y
	33	bool "Network core driver support"
	34	---help---
	35	You can say N here if you do not intend to use any of the
	36	networking core drivers (i.e. VLAN, bridging, bonding, etc.)
	37
	38	if NET_CORE
	39
	40	config BONDING
	41	tristate "Bonding driver support"
	42	depends on INET
	43	depends on IPV6 \|\| IPV6=n
	44	---help---
	45	Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	46	Channels together. This is called 'Etherchannel' by Cisco,
	47	'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
	48
	49	The driver supports multiple bonding modes to allow for both high
	50	performance and high availability operation.
	51
	52	Refer to <file:Documentation/networking/bonding.txt> for more
	53	information.
	54
	55	To compile this driver as a module, choose M here: the module
	56	will be called bonding.
	57
	58	config DUMMY
	59	tristate "Dummy net driver support"
	60	---help---
	61	This is essentially a bit-bucket device (i.e. traffic you send to
	62	this device is consigned into oblivion) with a configurable IP
	63	address. It is most commonly used in order to make your currently
	64	inactive SLIP address seem like a real address for local programs.
	65	If you use SLIP or PPP, you might want to say Y here. Since this
	66	thing often comes in handy, the default is Y. It won't enlarge your
	67	kernel either. What a deal. Read about it in the Network
	68	Administrator's Guide, available from
	69	<http://www.tldp.org/docs.html#guide>.
	70
	71	To compile this driver as a module, choose M here: the module
	72	will be called dummy.
	73
	74	config EQUALIZER
	75	tristate "EQL (serial line load balancing) support"
	76	---help---
	77	If you have two serial connections to some other computer (this
	78	usually requires two modems and two telephone lines) and you use
	79	SLIP (the protocol for sending Internet traffic over telephone
	80	lines) or PPP (a better SLIP) on them, you can make them behave like
	81	one double speed connection using this driver. Naturally, this has
	82	to be supported at the other end as well, either with a similar EQL
	83	Linux driver or with a Livingston Portmaster 2e.
	84
	85	Say Y if you want this and read
	86	<file:Documentation/networking/eql.txt>. You may also want to read
	87	section 6.2 of the NET-3-HOWTO, available from
	88	<http://www.tldp.org/docs.html#howto>.
	89
	90	To compile this driver as a module, choose M here: the module
	91	will be called eql. If unsure, say N.
	92
	93	config NET_FC
	94	bool "Fibre Channel driver support"
	95	depends on SCSI && PCI
	96	help
	97	Fibre Channel is a high speed serial protocol mainly used to connect
	98	large storage devices to the computer; it is compatible with and
	99	intended to replace SCSI.
	100
	101	If you intend to use Fibre Channel, you need to have a Fibre channel
	102	adaptor card in your computer; say Y here and to the driver for your
	103	adaptor below. You also should have said Y to "SCSI support" and
	104	"SCSI generic support".
	105
	106	config IFB
	107	tristate "Intermediate Functional Block support"
	108	depends on NET_CLS_ACT
	109	---help---
	110	This is an intermediate driver that allows sharing of
	111	resources.
	112	To compile this driver as a module, choose M here: the module
	113	will be called ifb. If you want to use more than one ifb
	114	device at a time, you need to compile this driver as a module.
	115	Instead of 'ifb', the devices will then be called 'ifb0',
	116	'ifb1' etc.
	117	Look at the iproute2 documentation directory for usage etc
	118
	119	source "drivers/net/team/Kconfig"
	120
	121	config MACVLAN
	122	tristate "MAC-VLAN support"
	123	---help---
	124	This allows one to create virtual interfaces that map packets to
	125	or from specific MAC addresses to a particular interface.
	126
	127	Macvlan devices can be added using the "ip" command from the
	128	iproute2 package starting with the iproute2-2.6.23 release:
	129
	130	"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
	131
	132	To compile this driver as a module, choose M here: the module
	133	will be called macvlan.
	134
	135	config MACVTAP
	136	tristate "MAC-VLAN based tap driver"
	137	depends on MACVLAN
	138	help
	139	This adds a specialized tap character device driver that is based
	140	on the MAC-VLAN network interface, called macvtap. A macvtap device
	141	can be added in the same way as a macvlan device, using 'type
	142	macvtap', and then be accessed through the tap user space interface.
	143
	144	To compile this driver as a module, choose M here: the module
	145	will be called macvtap.
	146
	147	config VXLAN
	148	tristate "Virtual eXtensible Local Area Network (VXLAN)"
	149	depends on INET
	150	select NET_IP_TUNNEL
	151	---help---
	152	This allows one to create vxlan virtual interfaces that provide
	153	Layer 2 Networks over Layer 3 Networks. VXLAN is often used
	154	to tunnel virtual network infrastructure in virtualized environments.
	155	For more information see:
	156	http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
	157
	158	To compile this driver as a module, choose M here: the module
	159	will be called vxlan.
	160
	161	config NETCONSOLE
	162	tristate "Network console logging support"
	163	---help---
	164	If you want to log kernel messages over the network, enable this.
	165	See <file:Documentation/networking/netconsole.txt> for details.
	166
	167	config NETCONSOLE_DYNAMIC
	168	bool "Dynamic reconfiguration of logging targets"
	169	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
	170	!(NETCONSOLE=y && CONFIGFS_FS=m)
	171	help
	172	This option enables the ability to dynamically reconfigure target
	173	parameters (interface, IP addresses, port numbers, MAC addresses)
	174	at runtime through a userspace interface exported using configfs.
	175	See <file:Documentation/networking/netconsole.txt> for details.
	176
	177	config NETPOLL
	178	def_bool NETCONSOLE
	179
	180	config NET_POLL_CONTROLLER
	181	def_bool NETPOLL
	182
	183	config NTB_NETDEV
	184	tristate "Virtual Ethernet over NTB"
	185	depends on NTB
	186
	187	config RIONET
	188	tristate "RapidIO Ethernet over messaging driver support"
	189	depends on RAPIDIO
	190
	191	config RIONET_TX_SIZE
	192	int "Number of outbound queue entries"
	193	depends on RIONET
	194	default "128"
	195
	196	config RIONET_RX_SIZE
	197	int "Number of inbound queue entries"
	198	depends on RIONET
	199	default "128"
	200
	201	config TUN
	202	tristate "Universal TUN/TAP device driver support"
	203	select CRC32
	204	---help---
	205	TUN/TAP provides packet reception and transmission for user space
	206	programs. It can be viewed as a simple Point-to-Point or Ethernet
	207	device, which instead of receiving packets from a physical media,
	208	receives them from user space program and instead of sending packets
	209	via physical media writes them to the user space program.
	210
	211	When a program opens /dev/net/tun, driver creates and registers
	212	corresponding net device tunX or tapX. After a program closed above
	213	devices, driver will automatically delete tunXX or tapXX device and
	214	all routes corresponding to it.
	215
	216	Please read <file:Documentation/networking/tuntap.txt> for more
	217	information.
	218
	219	To compile this driver as a module, choose M here: the module
	220	will be called tun.
	221
	222	If you don't know what to use this for, you don't need it.
	223
	224	config VETH
	225	tristate "Virtual ethernet pair device"
	226	---help---
	227	This device is a local ethernet tunnel. Devices are created in pairs.
	228	When one end receives the packet it appears on its pair and vice
	229	versa.
	230
	231	config VIRTIO_NET
	232	tristate "Virtio network driver"
	233	depends on VIRTIO
	234	select AVERAGE
	235	---help---
	236	This is the virtual network driver for virtio. It can be used with
	237	lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
	238
	239	config NLMON
	240	tristate "Virtual netlink monitoring device"
	241	---help---
	242	This option enables a monitoring net device for netlink skbs. The
	243	purpose of this is to analyze netlink messages with packet sockets.
	244	Thus applications like tcpdump will be able to see local netlink
	245	messages if they tap into the netlink device, record pcaps for further
	246	diagnostics, etc. This is mostly intended for developers or support
	247	to debug netlink issues. If unsure, say N.
	248
	249	endif # NET_CORE
	250
	251	config SUNGEM_PHY
	252	tristate
	253
	254	source "drivers/net/arcnet/Kconfig"
	255
	256	source "drivers/atm/Kconfig"
	257
	258	source "drivers/net/caif/Kconfig"
	259
	260	source "drivers/net/dsa/Kconfig"
	261
	262	source "drivers/net/ethernet/Kconfig"
	263
	264	source "drivers/net/fddi/Kconfig"
	265
	266	source "drivers/net/hippi/Kconfig"
	267
	268	config NET_SB1000
	269	tristate "General Instruments Surfboard 1000"
	270	depends on PNP
	271	---help---
	272	This is a driver for the General Instrument (also known as
	273	NextLevel) SURFboard 1000 internal
	274	cable modem. This is an ISA card which is used by a number of cable
	275	TV companies to provide cable modem access. It's a one-way
	276	downstream-only cable modem, meaning that your upstream net link is
	277	provided by your regular phone modem.
	278
	279	At present this driver only compiles as a module, so say M here if
	280	you have this card. The module will be called sb1000. Then read
	281	<file:Documentation/networking/README.sb1000> for information on how
	282	to use this module, as it needs special ppp scripts for establishing
	283	a connection. Further documentation and the necessary scripts can be
	284	found at:
	285
	286	<http://www.jacksonville.net/~fventuri/>
	287	<http://home.adelphia.net/~siglercm/sb1000.html>
	288	<http://linuxpower.cx/~cable/>
	289
	290	If you don't have this card, of course say N.
	291
	292	source "drivers/net/phy/Kconfig"
	293
	294	source "drivers/net/plip/Kconfig"
	295
	296	source "drivers/net/ppp/Kconfig"
	297
	298	source "drivers/net/slip/Kconfig"
	299
	300	source "drivers/s390/net/Kconfig"
	301
	302	source "drivers/net/usb/Kconfig"
	303
	304	source "drivers/net/wireless/Kconfig"
	305
	306	source "drivers/net/wimax/Kconfig"
	307
	308	source "drivers/net/wan/Kconfig"
	309
	310	source "drivers/net/ieee802154/Kconfig"
	311
	312	config XEN_NETDEV_FRONTEND
	313	tristate "Xen network device frontend driver"
	314	depends on XEN
	315	select XEN_XENBUS_FRONTEND
	316	default y
	317	help
	318	This driver provides support for Xen paravirtual network
	319	devices exported by a Xen network driver domain (often
	320	domain 0).
	321
	322	The corresponding Linux backend driver is enabled by the
	323	CONFIG_XEN_NETDEV_BACKEND option.
	324
	325	If you are compiling a kernel for use as Xen guest, you
	326	should say Y here. To compile this driver as a module, chose
	327	M here: the module will be called xen-netfront.
	328
	329	config XEN_NETDEV_BACKEND
	330	tristate "Xen backend network device"
	331	depends on XEN_BACKEND
	332	help
	333	This driver allows the kernel to act as a Xen network driver
	334	domain which exports paravirtual network devices to other
	335	Xen domains. These devices can be accessed by any operating
	336	system that implements a compatible front end.
	337
	338	The corresponding Linux frontend driver is enabled by the
	339	CONFIG_XEN_NETDEV_FRONTEND configuration option.
	340
	341	The backend driver presents a standard network device
	342	endpoint for each paravirtual network device to the driver
	343	domain network stack. These can then be bridged or routed
	344	etc in order to provide full network connectivity.
	345
	346	If you are compiling a kernel to run in a Xen network driver
	347	domain (often this is domain 0) you should say Y here. To
	348	compile this driver as a module, chose M here: the module
	349	will be called xen-netback.
	350
	351	config VMXNET3
	352	tristate "VMware VMXNET3 ethernet driver"
	353	depends on PCI && INET
	354	help
	355	This driver supports VMware's vmxnet3 virtual ethernet NIC.
	356	To compile this driver as a module, choose M here: the
	357	module will be called vmxnet3.
	358
	359	source "drivers/net/hyperv/Kconfig"
	360
	361	endif # NETDEVICES