[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 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.  If you want to use more than one dummy
	  device at a time, you need to compile this driver as a module.
	  Instead of 'dummy', the devices will then be called 'dummy0',
	  'dummy1' etc.

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 MII
	tristate "Generic Media Independent Interface device support"
	help
	  Most ethernet controllers have MII transceiver either as an external
	  or internal device.  It is safe to say Y or M here even if your
	  ethernet card lacks MII.

source "drivers/ieee802154/Kconfig"

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

config MACVLAN
	tristate "MAC-VLAN support (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	---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 (EXPERIMENTAL)"
	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
	  macvlan', 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 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 NETPOLL_TRAP
	bool "Netpoll traffic trapping"
	default n
	depends on NETPOLL

config NET_POLL_CONTROLLER
	def_bool NETPOLL

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 (EXPERIMENTAL)"
	depends on EXPERIMENTAL && VIRTIO
	---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.

endif # NET_CORE

config SUNGEM_PHY
	tristate

source "drivers/net/arcnet/Kconfig"

source "drivers/atm/Kconfig"

source "drivers/net/caif/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/tokenring/Kconfig"

source "drivers/net/usb/Kconfig"

source "drivers/net/wireless/Kconfig"

source "drivers/net/wimax/Kconfig"

source "drivers/net/wan/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.

endif # NETDEVICES
Commit	Line	Data
1da177e4 LT	1	#
	2	# Network device configuration
	3	#
	4
d1c0a65f	5	menuconfig NETDEVICES
ce2d2aed	6	default y if UML
e0009820	7	depends on NET
1da177e4 LT	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
1618cb0c RD	24	# All the following symbols are dependent on NETDEVICES - do not repeat
	25	# that for each of the symbols.
	26	if NETDEVICES
cbcd2a4c	27
88491d81 JK	28	config NET_CORE
	29	default y
	30	bool "Network core driver support"
253af423	31	---help---
88491d81 JK	32	You can say N here if you do not intend to use any of the
	33	networking core drivers (i.e. VLAN, bridging, bonding, etc.)
	34
	35	if NET_CORE
	36
	37	config BONDING
	38	tristate "Bonding driver support"
	39	depends on INET
	40	depends on IPV6 \|\| IPV6=n
	41	---help---
	42	Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	43	Channels together. This is called 'Etherchannel' by Cisco,
	44	'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
	45
	46	The driver supports multiple bonding modes to allow for both high
	47	performance and high availability operation.
	48
	49	Refer to <file:Documentation/networking/bonding.txt> for more
	50	information.
	51
253af423	52	To compile this driver as a module, choose M here: the module
88491d81	53	will be called bonding.
253af423	54
1da177e4 LT	55	config DUMMY
1da177e4 LT	56	tristate "Dummy net driver support"
1da177e4 LT	57	---help---
	58	This is essentially a bit-bucket device (i.e. traffic you send to
	59	this device is consigned into oblivion) with a configurable IP
	60	address. It is most commonly used in order to make your currently
	61	inactive SLIP address seem like a real address for local programs.
	62	If you use SLIP or PPP, you might want to say Y here. Since this
	63	thing often comes in handy, the default is Y. It won't enlarge your
	64	kernel either. What a deal. Read about it in the Network
	65	Administrator's Guide, available from
	66	<http://www.tldp.org/docs.html#guide>.
	67
	68	To compile this driver as a module, choose M here: the module
	69	will be called dummy. If you want to use more than one dummy
	70	device at a time, you need to compile this driver as a module.
	71	Instead of 'dummy', the devices will then be called 'dummy0',
	72	'dummy1' etc.
	73
88491d81 JK	74	config EQUALIZER
88491d81 JK	75	tristate "EQL (serial line load balancing) support"
1da177e4	76	---help---
88491d81 JK	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.
1da177e4	84
88491d81 JK	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>.
1da177e4	89
88491d81 JK	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".
1da177e4	105
88491d81 JK	106	config MII
	107	tristate "Generic Media Independent Interface device support"
	108	help
	109	Most ethernet controllers have MII transceiver either as an external
	110	or internal device. It is safe to say Y or M here even if your
	111	ethernet card lacks MII.
	112
	113	source "drivers/ieee802154/Kconfig"
	114
	115	config IFB
	116	tristate "Intermediate Functional Block support"
	117	depends on NET_CLS_ACT
	118	---help---
	119	This is an intermediate driver that allows sharing of
	120	resources.
1da177e4	121	To compile this driver as a module, choose M here: the module
88491d81 JK	122	will be called ifb. If you want to use more than one ifb
	123	device at a time, you need to compile this driver as a module.
	124	Instead of 'ifb', the devices will then be called 'ifb0',
	125	'ifb1' etc.
	126	Look at the iproute2 documentation directory for usage etc
1da177e4	127
b863ceb7 PM	128	config MACVLAN
	129	tristate "MAC-VLAN support (EXPERIMENTAL)"
	130	depends on EXPERIMENTAL
	131	---help---
	132	This allows one to create virtual interfaces that map packets to
	133	or from specific MAC addresses to a particular interface.
	134
3dbf8d56 PM	135	Macvlan devices can be added using the "ip" command from the
	136	iproute2 package starting with the iproute2-2.6.23 release:
	137
	138	"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
	139
b863ceb7 PM	140	To compile this driver as a module, choose M here: the module
	141	will be called macvlan.
	142
20d29d7a AB	143	config MACVTAP
	144	tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
	145	depends on MACVLAN
	146	help
	147	This adds a specialized tap character device driver that is based
	148	on the MAC-VLAN network interface, called macvtap. A macvtap device
	149	can be added in the same way as a macvlan device, using 'type
	150	macvlan', and then be accessed through the tap user space interface.
	151
	152	To compile this driver as a module, choose M here: the module
	153	will be called macvtap.
	154
88491d81 JK	155	config NETCONSOLE
88491d81 JK	156	tristate "Network console logging support"
1da177e4	157	---help---
88491d81 JK	158	If you want to log kernel messages over the network, enable this.
88491d81 JK	159	See <file:Documentation/networking/netconsole.txt> for details.
1da177e4	160
88491d81 JK	161	config NETCONSOLE_DYNAMIC
	162	bool "Dynamic reconfiguration of logging targets"
	163	depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
	164	!(NETCONSOLE=y && CONFIGFS_FS=m)
	165	help
	166	This option enables the ability to dynamically reconfigure target
	167	parameters (interface, IP addresses, port numbers, MAC addresses)
	168	at runtime through a userspace interface exported using configfs.
	169	See <file:Documentation/networking/netconsole.txt> for details.
1da177e4	170
88491d81 JK	171	config NETPOLL
	172	def_bool NETCONSOLE
	173
	174	config NETPOLL_TRAP
	175	bool "Netpoll traffic trapping"
	176	default n
	177	depends on NETPOLL
	178
	179	config NET_POLL_CONTROLLER
	180	def_bool NETPOLL
	181
	182	config RIONET
	183	tristate "RapidIO Ethernet over messaging driver support"
	184	depends on RAPIDIO
	185
	186	config RIONET_TX_SIZE
	187	int "Number of outbound queue entries"
	188	depends on RIONET
	189	default "128"
	190
	191	config RIONET_RX_SIZE
	192	int "Number of inbound queue entries"
	193	depends on RIONET
	194	default "128"
1da177e4 LT	195
	196	config TUN
	197	tristate "Universal TUN/TAP device driver support"
1da177e4 LT	198	select CRC32
	199	---help---
	200	TUN/TAP provides packet reception and transmission for user space
	201	programs. It can be viewed as a simple Point-to-Point or Ethernet
	202	device, which instead of receiving packets from a physical media,
	203	receives them from user space program and instead of sending packets
	204	via physical media writes them to the user space program.
	205
	206	When a program opens /dev/net/tun, driver creates and registers
	207	corresponding net device tunX or tapX. After a program closed above
	208	devices, driver will automatically delete tunXX or tapXX device and
	209	all routes corresponding to it.
	210
	211	Please read <file:Documentation/networking/tuntap.txt> for more
	212	information.
	213
	214	To compile this driver as a module, choose M here: the module
	215	will be called tun.
	216
	217	If you don't know what to use this for, you don't need it.
	218
e314dbdc	219	config VETH
6a9a0250	220	tristate "Virtual ethernet pair device"
e314dbdc	221	---help---
6a9a0250 RR	222	This device is a local ethernet tunnel. Devices are created in pairs.
	223	When one end receives the packet it appears on its pair and vice
	224	versa.
e314dbdc	225
88491d81 JK	226	config VIRTIO_NET
	227	tristate "Virtio network driver (EXPERIMENTAL)"
	228	depends on EXPERIMENTAL && VIRTIO
	229	---help---
	230	This is the virtual network driver for virtio. It can be used with
	231	lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
	232
	233	endif # NET_CORE
	234
	235	config SUNGEM_PHY
	236	tristate
	237
	238	source "drivers/net/arcnet/Kconfig"
	239
	240	source "drivers/atm/Kconfig"
	241
	242	source "drivers/net/caif/Kconfig"
	243
	244	source "drivers/net/ethernet/Kconfig"
	245
	246	source "drivers/net/fddi/Kconfig"
	247
fecc7351 PB	248	source "drivers/net/hippi/Kconfig"
fecc7351 PB	249
1da177e4 LT	250	config NET_SB1000
1da177e4 LT	251	tristate "General Instruments Surfboard 1000"
cbcd2a4c	252	depends on PNP
1da177e4 LT	253	---help---
	254	This is a driver for the General Instrument (also known as
	255	NextLevel) SURFboard 1000 internal
	256	cable modem. This is an ISA card which is used by a number of cable
	257	TV companies to provide cable modem access. It's a one-way
	258	downstream-only cable modem, meaning that your upstream net link is
	259	provided by your regular phone modem.
	260
	261	At present this driver only compiles as a module, so say M here if
	262	you have this card. The module will be called sb1000. Then read
	263	<file:Documentation/networking/README.sb1000> for information on how
	264	to use this module, as it needs special ppp scripts for establishing
	265	a connection. Further documentation and the necessary scripts can be
	266	found at:
	267
	268	<http://www.jacksonville.net/~fventuri/>
	269	<http://home.adelphia.net/~siglercm/sb1000.html>
	270	<http://linuxpower.cx/~cable/>
	271
	272	If you don't have this card, of course say N.
	273
00db8189 AF	274	source "drivers/net/phy/Kconfig"
00db8189 AF	275
18e635f4 JK	276	source "drivers/net/plip/Kconfig"
18e635f4 JK	277
88491d81 JK	278	source "drivers/net/ppp/Kconfig"
88491d81 JK	279
b5451d78 JK	280	source "drivers/net/slip/Kconfig"
b5451d78 JK	281
88491d81 JK	282	source "drivers/s390/net/Kconfig"
88491d81 JK	283
1da177e4 LT	284	source "drivers/net/tokenring/Kconfig"
1da177e4 LT	285
88491d81 JK	286	source "drivers/net/usb/Kconfig"
88491d81 JK	287
1da177e4 LT	288	source "drivers/net/wireless/Kconfig"
1da177e4 LT	289
143ee2d5 IPG	290	source "drivers/net/wimax/Kconfig"
143ee2d5 IPG	291
1da177e4 LT	292	source "drivers/net/wan/Kconfig"
1da177e4 LT	293
0d160211 JF	294	config XEN_NETDEV_FRONTEND
	295	tristate "Xen network device frontend driver"
	296	depends on XEN
7003087c	297	select XEN_XENBUS_FRONTEND
0d160211 JF	298	default y
0d160211 JF	299	help
f942dc25 IC	300	This driver provides support for Xen paravirtual network
	301	devices exported by a Xen network driver domain (often
	302	domain 0).
	303
	304	The corresponding Linux backend driver is enabled by the
	305	CONFIG_XEN_NETDEV_BACKEND option.
	306
	307	If you are compiling a kernel for use as Xen guest, you
	308	should say Y here. To compile this driver as a module, chose
	309	M here: the module will be called xen-netfront.
	310
	311	config XEN_NETDEV_BACKEND
	312	tristate "Xen backend network device"
	313	depends on XEN_BACKEND
	314	help
	315	This driver allows the kernel to act as a Xen network driver
	316	domain which exports paravirtual network devices to other
	317	Xen domains. These devices can be accessed by any operating
	318	system that implements a compatible front end.
	319
	320	The corresponding Linux frontend driver is enabled by the
	321	CONFIG_XEN_NETDEV_FRONTEND configuration option.
	322
	323	The backend driver presents a standard network device
	324	endpoint for each paravirtual network device to the driver
	325	domain network stack. These can then be bridged or routed
	326	etc in order to provide full network connectivity.
	327
	328	If you are compiling a kernel to run in a Xen network driver
	329	domain (often this is domain 0) you should say Y here. To
	330	compile this driver as a module, chose M here: the module
	331	will be called xen-netback.
0d160211	332
d1a890fa	333	config VMXNET3
e85eb117 PDM	334	tristate "VMware VMXNET3 ethernet driver"
	335	depends on PCI && INET
	336	help
	337	This driver supports VMware's vmxnet3 virtual ethernet NIC.
	338	To compile this driver as a module, choose M here: the
	339	module will be called vmxnet3.
d1a890fa	340
d1c0a65f	341	endif # NETDEVICES