2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 menuconfig NET_ETHERNET
199 bool "Ethernet (10 or 100Mbit)"
202 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
203 type of Local Area Network (LAN) in universities and companies.
205 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
206 coaxial cable, linking computers in a chain), 10BASE-T or twisted
207 pair (10 Mbps over twisted pair cable, linking computers to central
208 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
209 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
210 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
211 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
212 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
213 Ethernet (1 Gbps over optical fiber or short copper links).
215 If your Linux machine will be connected to an Ethernet and you have
216 an Ethernet network interface card (NIC) installed in your computer,
217 say Y here and read the Ethernet-HOWTO, available from
218 <http://www.tldp.org/docs.html#howto>. You will then also have
219 to say Y to the driver for your particular NIC.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about Ethernet network cards. If unsure, say N.
228 tristate "Atmel MACB support"
229 depends on HAVE_NET_MACB
232 The Atmel MACB ethernet interface is found on many AT32 and AT91
233 parts. Say Y to include support for the MACB chip.
235 To compile this driver as a module, choose M here: the module
238 source "drivers/net/arm/Kconfig"
241 tristate "Korina (IDT RC32434) Ethernet support"
242 depends on NET_ETHERNET && MIKROTIK_RB532
244 If you have a Mikrotik RouterBoard 500 or IDT RC32434
245 based system say Y. Otherwise say N.
248 tristate "MIPS simulator Network device"
251 The MIPSNET device is a simple Ethernet network device which is
252 emulated by the MIPS Simulator.
253 If you are not using a MIPSsim or are unsure, say N.
256 tristate "Renesas SuperH Ethernet support"
257 depends on SUPERH && \
258 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
259 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
260 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
266 Renesas SuperH Ethernet device driver.
267 This driver supporting CPUs are:
268 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
271 tristate "Blackfin on-chip MAC support"
272 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
276 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
278 This is the driver for Blackfin on-chip mac device. Say Y if you want it
279 compiled into the kernel. This driver is also available as a module
280 ( = code which can be inserted in and removed from the running kernel
281 whenever you want). The module will be called bfin_mac.
283 config BFIN_MAC_USE_L1
284 bool "Use L1 memory for rx/tx packets"
285 depends on BFIN_MAC && (BF527 || BF537)
288 To get maximum network performance, you should use L1 memory as rx/tx buffers.
289 Say N here if you want to reserve L1 memory for other uses.
291 config BFIN_TX_DESC_NUM
292 int "Number of transmit buffer packets"
294 range 6 10 if BFIN_MAC_USE_L1
298 Set the number of buffer packets used in driver.
300 config BFIN_RX_DESC_NUM
301 int "Number of receive buffer packets"
303 range 20 100 if BFIN_MAC_USE_L1
307 Set the number of buffer packets used in driver.
309 config BFIN_MAC_USE_HWSTAMP
310 bool "Use IEEE 1588 hwstamp"
311 depends on BFIN_MAC && BF518
314 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
317 tristate "Marvell pxa168 ethernet support"
318 depends on CPU_PXA168
321 This driver supports the pxa168 Ethernet ports.
323 To compile this driver as a module, choose M here. The module
324 will be called pxa168_eth.
327 tristate "NetX Ethernet support"
331 This is support for the Hilscher netX builtin Ethernet ports
333 To compile this driver as a module, choose M here. The module
334 will be called netx-eth.
336 config TI_DAVINCI_EMAC
337 tristate "TI DaVinci EMAC Support"
338 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
339 select TI_DAVINCI_MDIO
340 select TI_DAVINCI_CPDMA
343 This driver supports TI's DaVinci Ethernet .
345 To compile this driver as a module, choose M here: the module
346 will be called davinci_emac_driver. This is recommended.
348 config TI_DAVINCI_MDIO
349 tristate "TI DaVinci MDIO Support"
350 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
353 This driver supports TI's DaVinci MDIO module.
355 To compile this driver as a module, choose M here: the module
356 will be called davinci_mdio. This is recommended.
358 config TI_DAVINCI_CPDMA
359 tristate "TI DaVinci CPDMA Support"
360 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
362 This driver supports TI's DaVinci CPDMA dma engine.
364 To compile this driver as a module, choose M here: the module
365 will be called davinci_cpdma. This is recommended.
368 tristate "DM9000 support"
369 depends on ARM || BLACKFIN || MIPS
373 Support for DM9000 chipset.
375 To compile this driver as a module, choose M here. The module
376 will be called dm9000.
378 config DM9000_DEBUGLEVEL
379 int "DM9000 maximum debug level"
383 The maximum level of debugging code compiled into the DM9000
386 config DM9000_FORCE_SIMPLE_PHY_POLL
387 bool "Force simple NSR based PHY polling"
390 This configuration forces the DM9000 to use the NSR's LinkStatus
391 bit to determine if the link is up or down instead of the more
392 costly MII PHY reads. Note, this will not work if the chip is
393 operating with an external PHY.
396 tristate "ENC28J60 support"
397 depends on EXPERIMENTAL && SPI && NET_ETHERNET
400 Support for the Microchip EN28J60 ethernet chip.
402 To compile this driver as a module, choose M here. The module will be
405 config ENC28J60_WRITEVERIFY
406 bool "Enable write verify"
409 Enable the verify after the buffer write useful for debugging purpose.
413 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
414 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
420 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
423 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
428 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
431 tristate "Dave ethernet support (DNET)"
432 depends on NET_ETHERNET && HAS_IOMEM
435 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
436 Say Y to include support for the DNET chip.
438 To compile this driver as a module, choose M here: the module
442 tristate "AT1700/1720 support (EXPERIMENTAL)"
443 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
446 If you have a network (Ethernet) card of this type, say Y and read
447 the Ethernet-HOWTO, available from
448 <http://www.tldp.org/docs.html#howto>.
450 To compile this driver as a module, choose M here. The module
451 will be called at1700.
454 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
455 depends on ISA || EISA || PCI
457 If you have a network (Ethernet) card of this type, say Y and read
458 the Ethernet-HOWTO, available from
459 <http://www.tldp.org/docs.html#howto>.
461 To compile this driver as a module, choose M here. The module
462 will be called hp100.
465 bool "Other ISA cards"
468 If your network (Ethernet) card hasn't been mentioned yet and its
469 bus system (that's the way the cards talks to the other components
470 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
471 Make sure you know the name of your card. Read the Ethernet-HOWTO,
472 available from <http://www.tldp.org/docs.html#howto>.
476 Note that the answer to this question doesn't directly affect the
477 kernel: saying N will just cause the configurator to skip all
478 the remaining ISA network card questions. If you say Y, you will be
479 asked for your specific card in the following questions.
482 tristate "ICL EtherTeam 16i/32 support"
485 If you have a network (Ethernet) card of this type, say Y and read
486 the Ethernet-HOWTO, available from
487 <http://www.tldp.org/docs.html#howto>.
489 To compile this driver as a module, choose M here. The module
490 will be called eth16i.
493 tristate "SEEQ8005 support (EXPERIMENTAL)"
494 depends on NET_ISA && EXPERIMENTAL
496 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
497 is for you, read the Ethernet-HOWTO, available from
498 <http://www.tldp.org/docs.html#howto>.
500 To compile this driver as a module, choose M here. The module
501 will be called seeq8005.
504 bool "EISA, VLB, PCI and on board controllers"
505 depends on ISA || EISA || PCI
507 This is another class of network cards which attach directly to the
508 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
509 available from <http://www.tldp.org/docs.html#howto>.
511 Note that the answer to this question doesn't directly affect the
512 kernel: saying N will just cause the configurator to skip all
513 the questions about this class of network cards. If you say Y, you
514 will be asked for your specific card in the following questions. If
515 you are unsure, say Y.
517 config ADAPTEC_STARFIRE
518 tristate "Adaptec Starfire/DuraLAN support"
519 depends on NET_PCI && PCI
523 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
524 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
525 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
528 To compile this driver as a module, choose M here: the module
529 will be called starfire. This is recommended.
532 tristate "Micrel KSZ8841/2 PCI"
533 depends on NET_PCI && PCI
537 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
539 To compile this driver as a module, choose M here. The module
540 will be called ksz884x.
543 tristate "nForce Ethernet support"
544 depends on NET_PCI && PCI
546 If you have a network (Ethernet) controller of this type, say Y and
547 read the Ethernet-HOWTO, available from
548 <http://www.tldp.org/docs.html#howto>.
550 To compile this driver as a module, choose M here. The module
551 will be called forcedeth.
554 tristate "TOSHIBA TC35815 Ethernet support"
555 depends on NET_PCI && PCI && MIPS
559 tristate "Myson MTD-8xx PCI Ethernet support"
560 depends on NET_PCI && PCI
564 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
565 cards. <http://www.myson.com.tw/>
568 tristate "RDC R6040 Fast Ethernet Adapter support"
569 depends on NET_PCI && PCI
574 This is a driver for the R6040 Fast Ethernet MACs found in the
575 the RDC R-321x System-on-chips.
577 To compile this driver as a module, choose M here: the module
578 will be called r6040. This is recommended.
581 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
582 depends on NET_PCI && PCI
586 This is a driver for the Fast Ethernet PCI network cards based on
587 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
588 SiS 630 and SiS 540 chipsets.
590 This driver also supports AMD 79C901 HomePNA so that you can use
591 your phone line as a network cable.
593 To compile this driver as a module, choose M here: the module
594 will be called sis900. This is recommended.
597 tristate "TI ThunderLAN support"
598 depends on NET_PCI && (PCI || EISA)
600 If you have a PCI Ethernet network card based on the ThunderLAN chip
601 which is supported by this driver, say Y and read the
602 Ethernet-HOWTO, available from
603 <http://www.tldp.org/docs.html#howto>.
605 Devices currently supported by this driver are Compaq Netelligent,
606 Compaq NetFlex and Olicom cards. Please read the file
607 <file:Documentation/networking/tlan.txt> for more details.
609 To compile this driver as a module, choose M here. The module
612 Please email feedback to <torben.mathiasen@compaq.com>.
615 tristate "Micrel KSZ8841/42 with generic bus interface"
616 depends on HAS_IOMEM && DMA_ENGINE
618 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
619 ethernet switch chip (managed, VLAN, QoS) from Micrel or
623 tristate "Micrel KS8851 SPI"
628 SPI driver for Micrel KS8851 SPI attached network chip.
631 tristate "Micrel KS8851 MLL"
635 This platform driver is for Micrel KS8851 Address/data bus
636 multiplexed network chip.
639 tristate "VIA Rhine support"
640 depends on NET_PCI && PCI
644 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
645 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
646 Ethernet functions can also be found integrated on South Bridges
649 To compile this driver as a module, choose M here. The module
650 will be called via-rhine.
652 config VIA_RHINE_MMIO
653 bool "Use MMIO instead of PIO"
656 This instructs the driver to use PCI shared memory (MMIO) instead of
657 programmed I/O ports (PIO). Enabling this gives an improvement in
658 processing time in parts of the driver.
663 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
664 depends on NET_ETHERNET && EXPERIMENTAL && AR7
667 TI AR7 CPMAC Ethernet support
670 bool "Pocket and portable adapters"
673 Cute little network (Ethernet) devices which attach to the parallel
674 port ("pocket adapters"), commonly used with laptops. If you have
675 one of those, say Y and read the Ethernet-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>.
678 If you want to plug a network (or some other) card into the PCMCIA
679 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
680 credit card size extension cards used by all modern laptops), you
681 need the pcmcia-cs package (location contained in the file
682 <file:Documentation/Changes>) and you can say N here.
684 Laptop users should read the Linux Laptop home page at
685 <http://www.linux-on-laptops.com/> or
686 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
688 Note that the answer to this question doesn't directly affect the
689 kernel: saying N will just cause the configurator to skip all
690 the questions about this class of network devices. If you say Y, you
691 will be asked for your specific device in the following questions.
694 tristate "SGI Seeq ethernet controller support"
695 depends on SGI_HAS_SEEQ
697 Say Y here if you have an Seeq based Ethernet network card. This is
698 used in many Silicon Graphics machines.
701 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
702 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
703 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
704 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
707 Say Y here if you want to use the built-in 10/100 Fast ethernet
708 controller on some Motorola ColdFire and Freescale i.MX processors.
711 tristate "MPC52xx FEC driver"
712 depends on PPC_MPC52xx && PPC_BESTCOMM
715 select PPC_BESTCOMM_FEC
717 This option enables support for the MPC5200's on-chip
718 Fast Ethernet Controller
719 If compiled as module, it will be called fec_mpc52xx.
721 config FEC_MPC52xx_MDIO
722 bool "MPC52xx FEC MDIO bus driver"
723 depends on FEC_MPC52xx
726 The MPC5200's FEC can connect to the Ethernet either with
727 an external MII PHY chip or 10 Mbps 7-wire interface
728 (Motorola? industry standard).
729 If your board uses an external PHY connected to FEC, enable this.
731 If compiled as module, it will be called fec_mpc52xx_phy.
733 config XILINX_EMACLITE
734 tristate "Xilinx 10/100 Ethernet Lite support"
735 depends on PPC32 || MICROBLAZE
738 This driver supports the 10/100 Ethernet Lite from Xilinx.
741 tristate "Lantiq SoC ETOP driver"
742 depends on SOC_TYPE_XWAY
744 Support for the MII0 inside the Lantiq SoC
747 source "drivers/net/fs_enet/Kconfig"
749 source "drivers/net/octeon/Kconfig"
757 menuconfig NETDEV_1000
758 bool "Ethernet (1000 Mbit)"
762 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
763 type of Local Area Network (LAN) in universities and companies.
765 Say Y here to get to see options for Gigabit Ethernet drivers.
766 This option alone does not add any kernel code.
767 Note that drivers supporting both 100 and 1000 MBit may be listed
768 under "Ethernet (10 or 100MBit)" instead.
770 If you say N, all options in this submenu will be skipped and disabled.
775 tristate "IP1000 Gigabit Ethernet support"
776 depends on PCI && EXPERIMENTAL
779 This driver supports IP1000 gigabit Ethernet cards.
781 To compile this driver as a module, choose M here: the module
782 will be called ipg. This is recommended.
785 tristate "Packet Engines Hamachi GNIC-II support"
789 If you have a Gigabit Ethernet card of this type, say Y and read
790 the Ethernet-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>.
793 To compile this driver as a module, choose M here. The module will be
797 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
798 depends on PCI && EXPERIMENTAL
801 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
802 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
803 used by the Beowulf Linux cluster project. See
804 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
805 information about this driver in particular and Beowulf in general.
807 To compile this driver as a module, choose M here: the module
808 will be called yellowfin. This is recommended.
811 tristate "SiS190/SiS191 gigabit ethernet support"
816 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
817 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
818 appear in lan on motherboard designs which are based on SiS 965
819 and SiS 966 south bridge.
821 To compile this driver as a module, choose M here: the module
822 will be called sis190. This is recommended.
825 tristate "Marvell Yukon Gigabit Ethernet support"
829 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
830 and related Gigabit Ethernet adapters. It is a new smaller driver
831 with better performance and more complete ethtool support.
833 It does not support the link failover and network management
834 features that "portable" vendor supplied sk98lin driver does.
836 This driver supports adapters based on the original Yukon chipset:
837 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
838 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
840 It does not support the newer Yukon2 chipset: a separate driver,
841 sky2, is provided for these adapters.
843 To compile this driver as a module, choose M here: the module
844 will be called skge. This is recommended.
847 bool "Debugging interface"
848 depends on SKGE && DEBUG_FS
850 This option adds the ability to dump driver state for debugging.
851 The file /sys/kernel/debug/skge/ethX displays the state of the internal
852 transmit and receive rings.
857 bool "Support for older SysKonnect Genesis boards"
860 This enables support for the older and uncommon SysKonnect Genesis
861 chips, which support MII via an external transceiver, instead of
862 an internal one. Disabling this option will save some memory
863 by making code smaller. If unsure say Y.
866 tristate "Marvell Yukon 2 support"
870 This driver supports Gigabit Ethernet adapters based on the
871 Marvell Yukon 2 chipset:
872 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
873 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
875 There is companion driver for the older Marvell Yukon and
876 SysKonnect Genesis based adapters: skge.
878 To compile this driver as a module, choose M here: the module
879 will be called sky2. This is recommended.
882 bool "Debugging interface"
883 depends on SKY2 && DEBUG_FS
885 This option adds the ability to dump driver state for debugging.
886 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
887 transmit and receive rings.
892 tristate "VIA Velocity support"
898 If you have a VIA "Velocity" based network card say Y here.
900 To compile this driver as a module, choose M here. The module
901 will be called via-velocity.
904 tristate "Spider Gigabit Ethernet driver"
905 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
909 This driver supports the Gigabit Ethernet chips present on the
910 Cell Processor-Based Blades from IBM.
913 tristate "Tundra TSI108 gigabit Ethernet support"
914 depends on TSI108_BRIDGE
916 This driver supports Tundra TSI108 gigabit Ethernet ports.
917 To compile this driver as a module, choose M here: the module
918 will be called tsi108_eth.
921 tristate "PS3 Gigabit Ethernet driver"
923 select PS3_SYS_MANAGER
925 This driver supports the network device on the PS3 game
926 console. This driver has built-in support for Ethernet.
928 To compile this driver as a module, choose M here: the
929 module will be called ps3_gelic.
931 config GELIC_WIRELESS
932 bool "PS3 Wireless support"
937 This option adds the support for the wireless feature of PS3.
938 If you have the wireless-less model of PS3 or have no plan to
939 use wireless feature, disabling this option saves memory. As
940 the driver automatically distinguishes the models, you can
941 safely enable this option even if you have a wireless-less model.
944 tristate "Freescale PQ MDIO"
948 This driver supports the MDIO bus used by the gianfar and UCC drivers.
951 tristate "Gianfar Ethernet"
957 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
958 and MPC86xx family of chips, and the FEC on the 8540.
961 tristate "Freescale QE Gigabit Ethernet"
962 depends on QUICC_ENGINE
966 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
967 which is available on some Freescale SOCs.
969 config UGETH_TX_ON_DEMAND
970 bool "Transmit on Demand support"
974 tristate "Marvell Discovery (643XX) and Orion ethernet support"
975 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
979 This driver supports the gigabit ethernet MACs in the
980 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
981 in the Marvell Orion ARM SoC family.
983 Some boards that use the Discovery chipset are the Momenco
984 Ocelot C and Jaguar ATX and Pegasos II.
986 config XILINX_LL_TEMAC
987 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
988 depends on PPC || MICROBLAZE
991 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
992 core used in Xilinx Spartan and Virtex FPGAs
995 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1000 This driver supports the PCI-Express gigabit ethernet adapters
1001 based on JMicron JMC250 chipset.
1003 To compile this driver as a module, choose M here. The module
1007 tristate "S6105 GMAC ethernet support"
1008 depends on XTENSA_VARIANT_S6000
1011 This driver supports the on chip ethernet device on the
1012 S6105 xtensa processor.
1014 To compile this driver as a module, choose M here. The module
1015 will be called s6gmac.
1018 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1022 This is a gigabit ethernet driver for EG20T PCH.
1023 EG20T PCH is the platform controller hub that is used in Intel's
1024 general embedded platform.
1025 EG20T PCH has Gigabit Ethernet interface.
1026 Using this interface, it is able to access system devices connected
1027 to Gigabit Ethernet.
1028 This driver enables Gigabit Ethernet function.
1030 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1031 Output Hub), ML7223.
1032 ML7223 IOH is for MP(Media Phone) use.
1033 ML7223 is companion chip for Intel Atom E6xx series.
1034 ML7223 is completely compatible for Intel EG20T PCH.
1039 # 10 Gigabit Ethernet
1042 menuconfig NETDEV_10000
1043 bool "Ethernet (10000 Mbit)"
1047 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1048 This option alone does not add any kernel code.
1050 If you say N, all options in this submenu will be skipped and disabled.
1060 endif # NETDEV_10000
1062 source "drivers/net/tokenring/Kconfig"
1064 source "drivers/net/wireless/Kconfig"
1066 source "drivers/net/wimax/Kconfig"
1068 source "drivers/net/usb/Kconfig"
1070 source "drivers/net/pcmcia/Kconfig"
1072 source "drivers/net/wan/Kconfig"
1074 source "drivers/atm/Kconfig"
1076 source "drivers/ieee802154/Kconfig"
1078 source "drivers/s390/net/Kconfig"
1080 source "drivers/net/caif/Kconfig"
1083 tristate "Tilera GBE/XGBE network driver support"
1088 This is a standard Linux network device driver for the
1089 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1091 To compile this driver as a module, choose M here: the module
1092 will be called tile_net.
1094 config XEN_NETDEV_FRONTEND
1095 tristate "Xen network device frontend driver"
1097 select XEN_XENBUS_FRONTEND
1100 This driver provides support for Xen paravirtual network
1101 devices exported by a Xen network driver domain (often
1104 The corresponding Linux backend driver is enabled by the
1105 CONFIG_XEN_NETDEV_BACKEND option.
1107 If you are compiling a kernel for use as Xen guest, you
1108 should say Y here. To compile this driver as a module, chose
1109 M here: the module will be called xen-netfront.
1111 config XEN_NETDEV_BACKEND
1112 tristate "Xen backend network device"
1113 depends on XEN_BACKEND
1115 This driver allows the kernel to act as a Xen network driver
1116 domain which exports paravirtual network devices to other
1117 Xen domains. These devices can be accessed by any operating
1118 system that implements a compatible front end.
1120 The corresponding Linux frontend driver is enabled by the
1121 CONFIG_XEN_NETDEV_FRONTEND configuration option.
1123 The backend driver presents a standard network device
1124 endpoint for each paravirtual network device to the driver
1125 domain network stack. These can then be bridged or routed
1126 etc in order to provide full network connectivity.
1128 If you are compiling a kernel to run in a Xen network driver
1129 domain (often this is domain 0) you should say Y here. To
1130 compile this driver as a module, chose M here: the module
1131 will be called xen-netback.
1134 tristate "RapidIO Ethernet over messaging driver support"
1137 config RIONET_TX_SIZE
1138 int "Number of outbound queue entries"
1142 config RIONET_RX_SIZE
1143 int "Number of inbound queue entries"
1148 tristate "FDDI driver support"
1149 depends on (PCI || EISA || TC)
1151 Fiber Distributed Data Interface is a high speed local area network
1152 design; essentially a replacement for high speed Ethernet. FDDI can
1153 run over copper or fiber. If you are connected to such a network and
1154 want a driver for the FDDI card in your computer, say Y here (and
1155 then also Y to the driver for your FDDI card, below). Most people
1159 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1160 depends on FDDI && (PCI || EISA || TC)
1162 This is support for the DIGITAL series of TURBOchannel (DEFTA),
1163 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1164 to a local FDDI network.
1166 To compile this driver as a module, choose M here: the module
1167 will be called defxx. If unsure, say N.
1171 prompt "Use MMIO instead of PIO" if PCI || EISA
1173 default n if PCI || EISA
1176 This instructs the driver to use EISA or PCI memory-mapped I/O
1177 (MMIO) as appropriate instead of programmed I/O ports (PIO).
1178 Enabling this gives an improvement in processing time in parts
1179 of the driver, but it may cause problems with EISA (DEFEA)
1180 adapters. TURBOchannel does not have the concept of I/O ports,
1181 so MMIO is always used for these (DEFTA) adapters.
1186 tristate "SysKonnect FDDI PCI support"
1187 depends on FDDI && PCI
1190 Say Y here if you have a SysKonnect FDDI PCI adapter.
1191 The following adapters are supported by this driver:
1192 - SK-5521 (SK-NET FDDI-UP)
1193 - SK-5522 (SK-NET FDDI-UP DAS)
1194 - SK-5541 (SK-NET FDDI-FP)
1195 - SK-5543 (SK-NET FDDI-LP)
1196 - SK-5544 (SK-NET FDDI-LP DAS)
1197 - SK-5821 (SK-NET FDDI-UP64)
1198 - SK-5822 (SK-NET FDDI-UP64 DAS)
1199 - SK-5841 (SK-NET FDDI-FP64)
1200 - SK-5843 (SK-NET FDDI-LP64)
1201 - SK-5844 (SK-NET FDDI-LP64 DAS)
1202 - Netelligent 100 FDDI DAS Fibre SC
1203 - Netelligent 100 FDDI SAS Fibre SC
1204 - Netelligent 100 FDDI DAS UTP
1205 - Netelligent 100 FDDI SAS UTP
1206 - Netelligent 100 FDDI SAS Fibre MIC
1208 Read <file:Documentation/networking/skfp.txt> for information about
1211 Questions concerning this driver can be addressed to:
1212 <linux@syskonnect.de>
1214 To compile this driver as a module, choose M here: the module
1215 will be called skfp. This is recommended.
1218 bool "HIPPI driver support (EXPERIMENTAL)"
1219 depends on EXPERIMENTAL && INET && PCI
1221 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1222 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1223 can run over copper (25m) or fiber (300m on multi-mode or 10km on
1224 single-mode). HIPPI networks are commonly used for clusters and to
1225 connect to super computers. If you are connected to a HIPPI network
1226 and have a HIPPI network card in your computer that you want to use
1227 under Linux, say Y here (you must also remember to enable the driver
1228 for your HIPPI card below). Most people will say N here.
1231 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1232 depends on HIPPI && PCI
1234 Say Y here if this is your PCI HIPPI network card.
1236 To compile this driver as a module, choose M here: the module
1237 will be called rrunner. If unsure, say N.
1239 config ROADRUNNER_LARGE_RINGS
1240 bool "Use large TX/RX rings (EXPERIMENTAL)"
1241 depends on ROADRUNNER
1243 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1244 of additional memory to allow for fastest operation, both for
1245 transmitting and receiving. This memory cannot be used by any other
1246 kernel code or by user space programs. Say Y here only if you have
1250 tristate "PLIP (parallel port) support"
1253 PLIP (Parallel Line Internet Protocol) is used to create a
1254 reasonably fast mini network consisting of two (or, rarely, more)
1255 local machines. A PLIP link from a Linux box is a popular means to
1256 install a Linux distribution on a machine which doesn't have a
1257 CD-ROM drive (a minimal system has to be transferred with floppies
1258 first). The kernels on both machines need to have this PLIP option
1259 enabled for this to work.
1261 The PLIP driver has two modes, mode 0 and mode 1. The parallel
1262 ports (the connectors at the computers with 25 holes) are connected
1263 with "null printer" or "Turbo Laplink" cables which can transmit 4
1264 bits at a time (mode 0) or with special PLIP cables, to be used on
1265 bidirectional parallel ports only, which can transmit 8 bits at a
1266 time (mode 1); you can find the wiring of these cables in
1267 <file:Documentation/networking/PLIP.txt>. The cables can be up to
1268 15m long. Mode 0 works also if one of the machines runs DOS/Windows
1269 and has some PLIP software installed, e.g. the Crynwr PLIP packet
1270 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1271 and winsock or NCSA's telnet.
1273 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1274 as the NET-3-HOWTO, both available from
1275 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
1276 protocol has been changed and this PLIP driver won't work together
1277 with the PLIP support in Linux versions 1.0.x. This option enlarges
1278 your kernel by about 8 KB.
1280 To compile this driver as a module, choose M here. The module
1281 will be called plip. If unsure, say Y or M, in case you buy
1285 tristate "PPP (point-to-point protocol) support"
1288 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
1289 the same purpose: sending Internet traffic over telephone (and other
1290 serial) lines. Ask your access provider if they support it, because
1291 otherwise you can't use it; most Internet access providers these
1292 days support PPP rather than SLIP.
1294 To use PPP, you need an additional program called pppd as described
1295 in the PPP-HOWTO, available at
1296 <http://www.tldp.org/docs.html#howto>. Make sure that you have
1297 the version of pppd recommended in <file:Documentation/Changes>.
1298 The PPP option enlarges your kernel by about 16 KB.
1300 There are actually two versions of PPP: the traditional PPP for
1301 asynchronous lines, such as regular analog phone lines, and
1302 synchronous PPP which can be used over digital ISDN lines for
1303 example. If you want to use PPP over phone lines or other
1304 asynchronous serial lines, you need to say Y (or M) here and also to
1305 the next option, "PPP support for async serial ports". For PPP over
1306 synchronous lines, you should say Y (or M) here and to "Support
1307 synchronous PPP", below.
1309 If you said Y to "Version information on all symbols" above, then
1310 you cannot compile the PPP driver into the kernel; you can then only
1311 compile it as a module. To compile this driver as a module, choose M
1312 here. The module will be called ppp_generic.
1314 config PPP_MULTILINK
1315 bool "PPP multilink support (EXPERIMENTAL)"
1316 depends on PPP && EXPERIMENTAL
1318 PPP multilink is a protocol (defined in RFC 1990) which allows you
1319 to combine several (logical or physical) lines into one logical PPP
1320 connection, so that you can utilize your full bandwidth.
1322 This has to be supported at the other end as well and you need a
1323 version of the pppd daemon which understands the multilink protocol.
1328 bool "PPP filtering"
1331 Say Y here if you want to be able to filter the packets passing over
1332 PPP interfaces. This allows you to control which packets count as
1333 activity (i.e. which packets will reset the idle timer or bring up
1334 a demand-dialed link) and which packets are to be dropped entirely.
1335 You need to say Y here if you wish to use the pass-filter and
1336 active-filter options to pppd.
1341 tristate "PPP support for async serial ports"
1345 Say Y (or M) here if you want to be able to use PPP over standard
1346 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
1347 a modem (not a synchronous or ISDN modem) to contact your ISP, you
1350 To compile this driver as a module, choose M here.
1355 tristate "PPP support for sync tty ports"
1358 Say Y (or M) here if you want to be able to use PPP over synchronous
1359 (HDLC) tty devices, such as the SyncLink adapter. These devices
1360 are often used for high-speed leased lines like T1/E1.
1362 To compile this driver as a module, choose M here.
1365 tristate "PPP Deflate compression"
1370 Support for the Deflate compression method for PPP, which uses the
1371 Deflate algorithm (the same algorithm that gzip uses) to compress
1372 each PPP packet before it is sent over the wire. The machine at the
1373 other end of the PPP link (usually your ISP) has to support the
1374 Deflate compression method as well for this to be useful. Even if
1375 they don't support it, it is safe to say Y here.
1377 To compile this driver as a module, choose M here.
1380 tristate "PPP BSD-Compress compression"
1383 Support for the BSD-Compress compression method for PPP, which uses
1384 the LZW compression method to compress each PPP packet before it is
1385 sent over the wire. The machine at the other end of the PPP link
1386 (usually your ISP) has to support the BSD-Compress compression
1387 method as well for this to be useful. Even if they don't support it,
1388 it is safe to say Y here.
1390 The PPP Deflate compression method ("PPP Deflate compression",
1391 above) is preferable to BSD-Compress, because it compresses better
1394 Note that the BSD compression code will always be compiled as a
1395 module; it is called bsd_comp and will show up in the directory
1396 modules once you have said "make modules". If unsure, say N.
1399 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1400 depends on PPP && EXPERIMENTAL
1406 Support for the MPPE Encryption protocol, as employed by the
1407 Microsoft Point-to-Point Tunneling Protocol.
1409 See http://pptpclient.sourceforge.net/ for information on
1410 configuring PPTP clients and servers to utilize this method.
1413 tristate "PPP over Ethernet (EXPERIMENTAL)"
1414 depends on EXPERIMENTAL && PPP
1416 Support for PPP over Ethernet.
1418 This driver requires the latest version of pppd from the CVS
1419 repository at cvs.samba.org. Alternatively, see the
1420 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1421 which contains instruction on how to use this driver (under
1422 the heading "Kernel mode PPPoE").
1425 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1426 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1428 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1430 This driver requires pppd plugin to work in client mode or
1431 modified pptpd (poptop) to work in server mode.
1432 See http://accel-pptp.sourceforge.net/ for information how to
1433 utilize this module.
1436 tristate "PPP over ATM"
1437 depends on ATM && PPP
1439 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1440 This implementation does not yet comply with section 8 of RFC2364,
1441 which can lead to bad results if the ATM peer loses state and
1442 changes its encapsulation unilaterally.
1445 tristate "PPP over L2TP (EXPERIMENTAL)"
1446 depends on EXPERIMENTAL && L2TP && PPP
1448 Support for PPP-over-L2TP socket family. L2TP is a protocol
1449 used by ISPs and enterprises to tunnel PPP traffic over UDP
1450 tunnels. L2TP is replacing PPTP for VPN uses.
1453 tristate "SLIP (serial line) support"
1455 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1456 connect to your Internet service provider or to connect to some
1457 other local Unix box or if you want to configure your Linux box as a
1458 Slip/CSlip server for other people to dial in. SLIP (Serial Line
1459 Internet Protocol) is a protocol used to send Internet traffic over
1460 serial connections such as telephone lines or null modem cables;
1461 nowadays, the protocol PPP is more commonly used for this same
1464 Normally, your access provider has to support SLIP in order for you
1465 to be able to use it, but there is now a SLIP emulator called SLiRP
1466 around (available from
1467 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1468 allows you to use SLIP over a regular dial up shell connection. If
1469 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1470 NET-3-HOWTO, available from
1471 <http://www.tldp.org/docs.html#howto>, explains how to
1472 configure SLIP. Note that you don't need this option if you just
1473 want to run term (term is a program which gives you almost full
1474 Internet connectivity if you have a regular dial up shell account on
1475 some Internet connected Unix computer. Read
1476 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1477 support will enlarge your kernel by about 4 KB. If unsure, say N.
1479 To compile this driver as a module, choose M here. The module
1480 will be called slip.
1482 config SLIP_COMPRESSED
1483 bool "CSLIP compressed headers"
1487 This protocol is faster than SLIP because it uses compression on the
1488 TCP/IP headers (not on the data itself), but it has to be supported
1489 on both ends. Ask your access provider if you are not sure and
1490 answer Y, just in case. You will still be able to use plain SLIP. If
1491 you plan to use SLiRP, the SLIP emulator (available from
1492 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1493 allows you to use SLIP over a regular dial up shell connection, you
1494 definitely want to say Y here. The NET-3-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>, explains how to configure
1496 CSLIP. This won't enlarge your kernel.
1501 This option enables Van Jacobsen serial line header compression
1505 bool "Keepalive and linefill"
1508 Adds additional capabilities to the SLIP driver to support the
1509 RELCOM line fill and keepalive monitoring. Ideal on poor quality
1512 config SLIP_MODE_SLIP6
1513 bool "Six bit SLIP encapsulation"
1516 Just occasionally you may need to run IP over hostile serial
1517 networks that don't pass all control characters or are only seven
1518 bit. Saying Y here adds an extra mode you can use with SLIP:
1519 "slip6". In this mode, SLIP will only send normal ASCII symbols over
1520 the serial device. Naturally, this has to be supported at the other
1521 end of the link as well. It's good enough, for example, to run IP
1522 over the async ports of a Camtec JNT Pad. If unsure, say N.
1525 bool "Fibre Channel driver support"
1526 depends on SCSI && PCI
1528 Fibre Channel is a high speed serial protocol mainly used to connect
1529 large storage devices to the computer; it is compatible with and
1530 intended to replace SCSI.
1532 If you intend to use Fibre Channel, you need to have a Fibre channel
1533 adaptor card in your computer; say Y here and to the driver for your
1534 adaptor below. You also should have said Y to "SCSI support" and
1535 "SCSI generic support".
1538 tristate "Network console logging support"
1540 If you want to log kernel messages over the network, enable this.
1541 See <file:Documentation/networking/netconsole.txt> for details.
1543 config NETCONSOLE_DYNAMIC
1544 bool "Dynamic reconfiguration of logging targets"
1545 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1546 !(NETCONSOLE=y && CONFIGFS_FS=m)
1548 This option enables the ability to dynamically reconfigure target
1549 parameters (interface, IP addresses, port numbers, MAC addresses)
1550 at runtime through a userspace interface exported using configfs.
1551 See <file:Documentation/networking/netconsole.txt> for details.
1557 bool "Netpoll traffic trapping"
1561 config NET_POLL_CONTROLLER
1565 tristate "Virtio network driver (EXPERIMENTAL)"
1566 depends on EXPERIMENTAL && VIRTIO
1568 This is the virtual network driver for virtio. It can be used with
1569 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
1572 tristate "VMware VMXNET3 ethernet driver"
1573 depends on PCI && INET
1575 This driver supports VMware's vmxnet3 virtual ethernet NIC.
1576 To compile this driver as a module, choose M here: the
1577 module will be called vmxnet3.