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 "MACE (Power Mac ethernet) support"
242 depends on PPC_PMAC && PPC32
245 Power Macintoshes and clones with Ethernet built-in on the
246 motherboard will usually use a MACE (Medium Access Control for
247 Ethernet) interface. Say Y to include support for the MACE chip.
249 To compile this driver as a module, choose M here: the module
252 config MACE_AAUI_PORT
253 bool "Use AAUI port instead of TP by default"
256 Some Apple machines (notably the Apple Network Server) which use the
257 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
258 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
259 Y here if you have such a machine. If unsure, say N.
260 The driver will default to AAUI on ANS anyway, and if you use it as
261 a module, you can provide the port_aaui=0|1 to force the driver.
264 tristate "BMAC (G3 ethernet) support"
265 depends on PPC_PMAC && PPC32
268 Say Y for support of BMAC Ethernet interfaces. These are used on G3
271 To compile this driver as a module, choose M here: the module
275 tristate "Macintosh CS89x0 based ethernet cards"
278 Support for CS89x0 chipset based Ethernet cards. If you have a
279 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
280 read the Ethernet-HOWTO, available from
281 <http://www.tldp.org/docs.html#howto>.
283 To compile this driver as a module, choose M here. This module will
287 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
290 Support for NatSemi SONIC based Ethernet devices. This includes
291 the onboard Ethernet in many Quadras as well as some LC-PDS,
292 a few Nubus and all known Comm Slot Ethernet cards. If you have
293 one of these say Y and read the Ethernet-HOWTO, available from
294 <http://www.tldp.org/docs.html#howto>.
296 To compile this driver as a module, choose M here. This module will
300 bool "Macintosh (AV) onboard MACE ethernet"
304 Support for the onboard AMD 79C940 MACE Ethernet controller used in
305 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
306 say Y and read the Ethernet-HOWTO, available from
307 <http://www.tldp.org/docs.html#howto>.
310 tristate "MVME16x Ethernet support"
313 This is the driver for the Ethernet interface on the Motorola
314 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
315 driver for this chip in your kernel.
316 To compile this driver as a module, choose M here.
319 tristate "BVME6000 Ethernet support"
322 This is the driver for the Ethernet interface on BVME4000 and
323 BVME6000 VME boards. Say Y here to include the driver for this chip
325 To compile this driver as a module, choose M here.
328 bool "Sun3 on-board Intel 82586 support"
331 This driver enables support for the on-board Intel 82586 based
332 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
333 that this driver does not support 82586-based adapters on additional
337 tristate "Lasi ethernet"
340 Say Y here to support the builtin Intel 82596 ethernet controller
341 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
344 tristate "SNI RM ethernet"
345 depends on NET_ETHERNET && SNI_RM
347 Say Y here to support the on-board Intel 82596 ethernet controller
348 built into SNI RM machines.
351 tristate "Korina (IDT RC32434) Ethernet support"
352 depends on NET_ETHERNET && MIKROTIK_RB532
354 If you have a Mikrotik RouterBoard 500 or IDT RC32434
355 based system say Y. Otherwise say N.
357 config MIPS_JAZZ_SONIC
358 tristate "MIPS JAZZ onboard SONIC Ethernet support"
361 This is the driver for the onboard card of MIPS Magnum 4000,
362 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
364 config XTENSA_XT2000_SONIC
365 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
366 depends on XTENSA_PLATFORM_XT2000
368 This is the driver for the onboard card of the Xtensa XT2000 board.
371 bool "SGI IOC3 Ethernet"
372 depends on PCI && SGI_IP27
376 If you have a network (Ethernet) card of this type, say Y and read
377 the Ethernet-HOWTO, available from
378 <http://www.tldp.org/docs.html#howto>.
381 tristate "MIPS simulator Network device"
384 The MIPSNET device is a simple Ethernet network device which is
385 emulated by the MIPS Simulator.
386 If you are not using a MIPSsim or are unsure, say N.
388 config SGI_O2MACE_ETH
389 tristate "SGI O2 MACE Fast Ethernet support"
390 depends on SGI_IP32=y
393 tristate "Renesas SuperH Ethernet support"
394 depends on SUPERH && \
395 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
396 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
397 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
403 Renesas SuperH Ethernet device driver.
404 This driver supporting CPUs are:
405 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
408 tristate "Sun Happy Meal 10/100baseT support"
409 depends on SBUS || PCI
412 This driver supports the "hme" interface present on most Ultra
413 systems and as an option on older Sbus systems. This driver supports
414 both PCI and Sbus devices. This driver also supports the "qfe" quad
415 100baseT device available in both PCI and Sbus configurations.
417 To compile this driver as a module, choose M here: the module
418 will be called sunhme.
421 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
422 depends on SBUS && EXPERIMENTAL
425 This driver supports the "be" interface available as an Sbus option.
426 This is Sun's older 100baseT Ethernet device.
428 To compile this driver as a module, choose M here: the module
429 will be called sunbmac.
432 tristate "Sun QuadEthernet support"
436 This driver supports the "qe" 10baseT Ethernet device, available as
437 an Sbus option. Note that this is not the same as Quad FastEthernet
438 "qfe" which is supported by the Happy Meal driver instead.
440 To compile this driver as a module, choose M here: the module
441 will be called sunqe.
444 tristate "Sun GEM support"
448 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
449 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
452 tristate "Sun Cassini support"
456 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
457 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
460 tristate "Sun Virtual Network support"
463 Support for virtual network devices under Sun Logical Domains.
466 tristate "3c503 \"EtherLink II\" support"
470 If you have a network (Ethernet) card of this type, say Y and read
471 the Ethernet-HOWTO, available from
472 <http://www.tldp.org/docs.html#howto>.
474 To compile this driver as a module, choose M here. The module
475 will be called 3c503.
478 tristate "3c505 \"EtherLink Plus\" support"
479 depends on ISA && ISA_DMA_API
481 Information about this network (Ethernet) card can be found in
482 <file:Documentation/networking/3c505.txt>. If you have a card of
483 this type, say Y and read the Ethernet-HOWTO, available from
484 <http://www.tldp.org/docs.html#howto>.
486 To compile this driver as a module, choose M here. The module
487 will be called 3c505.
490 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
491 depends on ISA && EXPERIMENTAL
493 If you have a network (Ethernet) card of this type, say Y and read
494 the Ethernet-HOWTO, available from
495 <http://www.tldp.org/docs.html#howto>.
497 To compile this driver as a module, choose M here. The module
498 will be called 3c507.
501 tristate "3c523 \"EtherLink/MC\" support"
502 depends on MCA_LEGACY
504 If you have a network (Ethernet) card of this type, say Y and read
505 the Ethernet-HOWTO, available from
506 <http://www.tldp.org/docs.html#howto>.
508 To compile this driver as a module, choose M here. The module
509 will be called 3c523.
512 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
513 depends on MCA && MCA_LEGACY
515 If you have a network (Ethernet) card of this type, say Y and read
516 the Ethernet-HOWTO, available from
517 <http://www.tldp.org/docs.html#howto>.
519 To compile this driver as a module, choose M here. The module
520 will be called 3c527.
523 tristate "Blackfin on-chip MAC support"
524 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
528 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
530 This is the driver for Blackfin on-chip mac device. Say Y if you want it
531 compiled into the kernel. This driver is also available as a module
532 ( = code which can be inserted in and removed from the running kernel
533 whenever you want). The module will be called bfin_mac.
535 config BFIN_MAC_USE_L1
536 bool "Use L1 memory for rx/tx packets"
537 depends on BFIN_MAC && (BF527 || BF537)
540 To get maximum network performance, you should use L1 memory as rx/tx buffers.
541 Say N here if you want to reserve L1 memory for other uses.
543 config BFIN_TX_DESC_NUM
544 int "Number of transmit buffer packets"
546 range 6 10 if BFIN_MAC_USE_L1
550 Set the number of buffer packets used in driver.
552 config BFIN_RX_DESC_NUM
553 int "Number of receive buffer packets"
555 range 20 100 if BFIN_MAC_USE_L1
559 Set the number of buffer packets used in driver.
561 config BFIN_MAC_USE_HWSTAMP
562 bool "Use IEEE 1588 hwstamp"
563 depends on BFIN_MAC && BF518
566 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
569 tristate "Marvell pxa168 ethernet support"
570 depends on CPU_PXA168
573 This driver supports the pxa168 Ethernet ports.
575 To compile this driver as a module, choose M here. The module
576 will be called pxa168_eth.
579 tristate "NetX Ethernet support"
583 This is support for the Hilscher netX builtin Ethernet ports
585 To compile this driver as a module, choose M here. The module
586 will be called netx-eth.
588 config TI_DAVINCI_EMAC
589 tristate "TI DaVinci EMAC Support"
590 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
591 select TI_DAVINCI_MDIO
592 select TI_DAVINCI_CPDMA
595 This driver supports TI's DaVinci Ethernet .
597 To compile this driver as a module, choose M here: the module
598 will be called davinci_emac_driver. This is recommended.
600 config TI_DAVINCI_MDIO
601 tristate "TI DaVinci MDIO Support"
602 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
605 This driver supports TI's DaVinci MDIO module.
607 To compile this driver as a module, choose M here: the module
608 will be called davinci_mdio. This is recommended.
610 config TI_DAVINCI_CPDMA
611 tristate "TI DaVinci CPDMA Support"
612 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
614 This driver supports TI's DaVinci CPDMA dma engine.
616 To compile this driver as a module, choose M here: the module
617 will be called davinci_cpdma. This is recommended.
620 tristate "DM9000 support"
621 depends on ARM || BLACKFIN || MIPS
625 Support for DM9000 chipset.
627 To compile this driver as a module, choose M here. The module
628 will be called dm9000.
630 config DM9000_DEBUGLEVEL
631 int "DM9000 maximum debug level"
635 The maximum level of debugging code compiled into the DM9000
638 config DM9000_FORCE_SIMPLE_PHY_POLL
639 bool "Force simple NSR based PHY polling"
642 This configuration forces the DM9000 to use the NSR's LinkStatus
643 bit to determine if the link is up or down instead of the more
644 costly MII PHY reads. Note, this will not work if the chip is
645 operating with an external PHY.
648 tristate "ENC28J60 support"
649 depends on EXPERIMENTAL && SPI && NET_ETHERNET
652 Support for the Microchip EN28J60 ethernet chip.
654 To compile this driver as a module, choose M here. The module will be
657 config ENC28J60_WRITEVERIFY
658 bool "Enable write verify"
661 Enable the verify after the buffer write useful for debugging purpose.
665 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
666 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
672 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
675 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
680 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
682 config NET_VENDOR_RACAL
683 bool "Racal-Interlan (Micom) NI cards"
686 If you have a network (Ethernet) card belonging to this class, such
687 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
688 available from <http://www.tldp.org/docs.html#howto>.
690 Note that the answer to this question doesn't directly affect the
691 kernel: saying N will just cause the configurator to skip all
692 the questions about NI cards. If you say Y, you will be asked for
693 your specific card in the following questions.
696 tristate "NI5010 support (EXPERIMENTAL)"
697 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
699 If you have a network (Ethernet) card of this type, say Y and read
700 the Ethernet-HOWTO, available from
701 <http://www.tldp.org/docs.html#howto>. Note that this is still
704 To compile this driver as a module, choose M here. The module
705 will be called ni5010.
708 tristate "NI5210 support"
709 depends on NET_VENDOR_RACAL && ISA
711 If you have a network (Ethernet) card of this type, say Y and read
712 the Ethernet-HOWTO, available from
713 <http://www.tldp.org/docs.html#howto>.
715 To compile this driver as a module, choose M here. The module
719 tristate "Dave ethernet support (DNET)"
720 depends on NET_ETHERNET && HAS_IOMEM
723 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
724 Say Y to include support for the DNET chip.
726 To compile this driver as a module, choose M here: the module
729 source "drivers/net/tulip/Kconfig"
732 tristate "AT1700/1720 support (EXPERIMENTAL)"
733 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
736 If you have a network (Ethernet) card of this type, say Y and read
737 the Ethernet-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>.
740 To compile this driver as a module, choose M here. The module
741 will be called at1700.
744 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
745 depends on ISA || EISA || PCI
747 If you have a network (Ethernet) card of this type, say Y and read
748 the Ethernet-HOWTO, available from
749 <http://www.tldp.org/docs.html#howto>.
751 To compile this driver as a module, choose M here. The module
752 will be called hp100.
755 bool "Other ISA cards"
758 If your network (Ethernet) card hasn't been mentioned yet and its
759 bus system (that's the way the cards talks to the other components
760 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
761 Make sure you know the name of your card. Read the Ethernet-HOWTO,
762 available from <http://www.tldp.org/docs.html#howto>.
766 Note that the answer to this question doesn't directly affect the
767 kernel: saying N will just cause the configurator to skip all
768 the remaining ISA network card questions. If you say Y, you will be
769 asked for your specific card in the following questions.
772 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
776 This driver supports the DE203, DE204 and DE205 network (Ethernet)
777 cards. If this is for you, say Y and read
778 <file:Documentation/networking/ewrk3.txt> in the kernel source as
779 well as the Ethernet-HOWTO, available from
780 <http://www.tldp.org/docs.html#howto>.
782 To compile this driver as a module, choose M here. The module
783 will be called ewrk3.
786 tristate "EtherExpress 16 support"
789 If you have an EtherExpress16 network (Ethernet) card, say Y and
790 read the Ethernet-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>. Note that the Intel
792 EtherExpress16 card used to be regarded as a very poor choice
793 because the driver was very unreliable. We now have a new driver
794 that should do better.
796 To compile this driver as a module, choose M here. The module
797 will be called eexpress.
800 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
803 If you have a network (Ethernet) card of this type, say Y. This
804 driver supports Intel i82595{FX,TX} based boards. Note however
805 that the EtherExpress PRO/100 Ethernet card has its own separate
806 driver. Please read the Ethernet-HOWTO, available from
807 <http://www.tldp.org/docs.html#howto>.
809 To compile this driver as a module, choose M here. The module
810 will be called eepro.
813 tristate "LP486E on board Ethernet"
816 Say Y here to support the 82596-based on-board Ethernet controller
817 for the Panther motherboard, which is one of the two shipped in the
818 Intel Professional Workstation.
821 tristate "ICL EtherTeam 16i/32 support"
824 If you have a network (Ethernet) card of this type, say Y and read
825 the Ethernet-HOWTO, available from
826 <http://www.tldp.org/docs.html#howto>.
828 To compile this driver as a module, choose M here. The module
829 will be called eth16i.
832 tristate "Zenith Z-Note support (EXPERIMENTAL)"
833 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
835 The Zenith Z-Note notebook computer has a built-in network
836 (Ethernet) card, and this is the Linux driver for it. Note that the
837 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
838 by this driver. Read the Ethernet-HOWTO, available from
839 <http://www.tldp.org/docs.html#howto>.
842 tristate "SEEQ8005 support (EXPERIMENTAL)"
843 depends on NET_ISA && EXPERIMENTAL
845 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
846 is for you, read the Ethernet-HOWTO, available from
847 <http://www.tldp.org/docs.html#howto>.
849 To compile this driver as a module, choose M here. The module
850 will be called seeq8005.
853 tristate "IBM LAN Adapter/A support"
856 This is a Micro Channel Ethernet adapter. You need to set
857 CONFIG_MCA to use this driver. It is both available as an in-kernel
858 driver and as a module.
860 To compile this driver as a module, choose M here. The only
861 currently supported card is the IBM LAN Adapter/A for Ethernet. It
862 will both support 16K and 32K memory windows, however a 32K window
863 gives a better security against packet losses. Usage of multiple
864 boards with this driver should be possible, but has not been tested
865 up to now due to lack of hardware.
868 tristate "IBM LAN Virtual Ethernet support"
869 depends on PPC_PSERIES
871 This driver supports virtual ethernet adapters on newer IBM iSeries
874 To compile this driver as a module, choose M here. The module will
877 source "drivers/net/ibm_newemac/Kconfig"
880 bool "EISA, VLB, PCI and on board controllers"
881 depends on ISA || EISA || PCI
883 This is another class of network cards which attach directly to the
884 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
885 available from <http://www.tldp.org/docs.html#howto>.
887 Note that the answer to this question doesn't directly affect the
888 kernel: saying N will just cause the configurator to skip all
889 the questions about this class of network cards. If you say Y, you
890 will be asked for your specific card in the following questions. If
891 you are unsure, say Y.
893 config ADAPTEC_STARFIRE
894 tristate "Adaptec Starfire/DuraLAN support"
895 depends on NET_PCI && PCI
899 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
900 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
901 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
904 To compile this driver as a module, choose M here: the module
905 will be called starfire. This is recommended.
908 tristate "Micrel KSZ8841/2 PCI"
909 depends on NET_PCI && PCI
913 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
915 To compile this driver as a module, choose M here. The module
916 will be called ksz884x.
919 tristate "Apricot Xen-II on board Ethernet"
920 depends on NET_PCI && ISA
922 If you have a network (Ethernet) controller of this type, say Y and
923 read the Ethernet-HOWTO, available from
924 <http://www.tldp.org/docs.html#howto>.
926 To compile this driver as a module, choose M here. The module
927 will be called apricot.
930 tristate "nForce Ethernet support"
931 depends on NET_PCI && PCI
933 If you have a network (Ethernet) controller of this type, say Y and
934 read the Ethernet-HOWTO, available from
935 <http://www.tldp.org/docs.html#howto>.
937 To compile this driver as a module, choose M here. The module
938 will be called forcedeth.
941 tristate "CS89x0 support"
942 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
943 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
945 Support for CS89x0 chipset based Ethernet cards. If you have a
946 network (Ethernet) card of this type, say Y and read the
947 Ethernet-HOWTO, available from
948 <http://www.tldp.org/docs.html#howto> as well as
949 <file:Documentation/networking/cs89x0.txt>.
951 To compile this driver as a module, choose M here. The module
952 will be called cs89x0.
954 config CS89x0_NONISA_IRQ
956 depends on CS89x0 != n
957 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
960 tristate "TOSHIBA TC35815 Ethernet support"
961 depends on NET_PCI && PCI && MIPS
965 tristate "Myson MTD-8xx PCI Ethernet support"
966 depends on NET_PCI && PCI
970 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
971 cards. <http://www.myson.com.tw/>
974 tristate "National Semiconductor DP8381x series PCI Ethernet support"
975 depends on NET_PCI && PCI
978 This driver is for the National Semiconductor DP83810 series,
979 which is used in cards from PureData, NetGear, Linksys
980 and others, including the 83815 chip.
981 More specific information and updates are available from
982 <http://www.scyld.com/network/natsemi.html>.
985 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
986 depends on NET_PCI && PCI && EXPERIMENTAL
990 This is a driver for the Fast Ethernet PCI network cards based on
991 the RTL8139C+ chips. If you have one of those, say Y and read
992 the Ethernet-HOWTO, available from
993 <http://www.tldp.org/docs.html#howto>.
995 To compile this driver as a module, choose M here: the module
996 will be called 8139cp. This is recommended.
999 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1000 depends on NET_PCI && PCI
1004 This is a driver for the Fast Ethernet PCI network cards based on
1005 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1006 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1008 To compile this driver as a module, choose M here: the module
1009 will be called 8139too. This is recommended.
1012 bool "Use PIO instead of MMIO"
1016 This instructs the driver to use programmed I/O ports (PIO) instead
1017 of PCI shared memory (MMIO). This can possibly solve some problems
1018 in case your mainboard has memory consistency issues. If unsure,
1021 config 8139TOO_TUNE_TWISTER
1022 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1025 This implements a function which might come in handy in case you
1026 are using low quality on long cabling. It is required for RealTek
1027 RTL-8139 revision K boards, and totally unused otherwise. It tries
1028 to match the transceiver to the cable characteristics. This is
1029 experimental since hardly documented by the manufacturer.
1033 bool "Support for older RTL-8129/8130 boards"
1036 This enables support for the older and uncommon RTL-8129 and
1037 RTL-8130 chips, which support MII via an external transceiver,
1038 instead of an internal one. Disabling this option will save some
1039 memory by making the code size smaller. If unsure, say Y.
1041 config 8139_OLD_RX_RESET
1042 bool "Use older RX-reset method"
1045 The 8139too driver was recently updated to contain a more rapid
1046 reset sequence, in the face of severe receive errors. This "new"
1047 RX-reset method should be adequate for all boards. But if you
1048 experience problems, you can enable this option to restore the
1049 old RX-reset behavior. If unsure, say N.
1052 tristate "RDC R6040 Fast Ethernet Adapter support"
1053 depends on NET_PCI && PCI
1058 This is a driver for the R6040 Fast Ethernet MACs found in the
1059 the RDC R-321x System-on-chips.
1061 To compile this driver as a module, choose M here: the module
1062 will be called r6040. This is recommended.
1065 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1066 depends on NET_PCI && PCI
1070 This is a driver for the Fast Ethernet PCI network cards based on
1071 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1072 SiS 630 and SiS 540 chipsets.
1074 This driver also supports AMD 79C901 HomePNA so that you can use
1075 your phone line as a network cable.
1077 To compile this driver as a module, choose M here: the module
1078 will be called sis900. This is recommended.
1081 tristate "Sundance Alta support"
1082 depends on NET_PCI && PCI
1086 This driver is for the Sundance "Alta" chip.
1087 More specific information and updates are available from
1088 <http://www.scyld.com/network/sundance.html>.
1090 config SUNDANCE_MMIO
1091 bool "Use MMIO instead of PIO"
1094 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1095 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1096 is known to solve bugs on certain chips.
1101 tristate "TI ThunderLAN support"
1102 depends on NET_PCI && (PCI || EISA)
1104 If you have a PCI Ethernet network card based on the ThunderLAN chip
1105 which is supported by this driver, say Y and read the
1106 Ethernet-HOWTO, available from
1107 <http://www.tldp.org/docs.html#howto>.
1109 Devices currently supported by this driver are Compaq Netelligent,
1110 Compaq NetFlex and Olicom cards. Please read the file
1111 <file:Documentation/networking/tlan.txt> for more details.
1113 To compile this driver as a module, choose M here. The module
1114 will be called tlan.
1116 Please email feedback to <torben.mathiasen@compaq.com>.
1119 tristate "Micrel KSZ8841/42 with generic bus interface"
1120 depends on HAS_IOMEM && DMA_ENGINE
1122 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1123 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1127 tristate "Micrel KS8851 SPI"
1132 SPI driver for Micrel KS8851 SPI attached network chip.
1135 tristate "Micrel KS8851 MLL"
1136 depends on HAS_IOMEM
1139 This platform driver is for Micrel KS8851 Address/data bus
1140 multiplexed network chip.
1143 tristate "VIA Rhine support"
1144 depends on NET_PCI && PCI
1148 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1149 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1150 Ethernet functions can also be found integrated on South Bridges
1153 To compile this driver as a module, choose M here. The module
1154 will be called via-rhine.
1156 config VIA_RHINE_MMIO
1157 bool "Use MMIO instead of PIO"
1158 depends on VIA_RHINE
1160 This instructs the driver to use PCI shared memory (MMIO) instead of
1161 programmed I/O ports (PIO). Enabling this gives an improvement in
1162 processing time in parts of the driver.
1167 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1168 depends on NET_PCI && PCI && EXPERIMENTAL
1171 This is a driver for the Fast Ethernet PCI network cards based on
1172 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1173 have one of these, say Y here.
1175 To compile this driver as a module, choose M here: the module
1176 will be called sc92031. This is recommended.
1179 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1180 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1183 TI AR7 CPMAC Ethernet support
1186 bool "Pocket and portable adapters"
1189 Cute little network (Ethernet) devices which attach to the parallel
1190 port ("pocket adapters"), commonly used with laptops. If you have
1191 one of those, say Y and read the Ethernet-HOWTO, available from
1192 <http://www.tldp.org/docs.html#howto>.
1194 If you want to plug a network (or some other) card into the PCMCIA
1195 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1196 credit card size extension cards used by all modern laptops), you
1197 need the pcmcia-cs package (location contained in the file
1198 <file:Documentation/Changes>) and you can say N here.
1200 Laptop users should read the Linux Laptop home page at
1201 <http://www.linux-on-laptops.com/> or
1202 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1204 Note that the answer to this question doesn't directly affect the
1205 kernel: saying N will just cause the configurator to skip all
1206 the questions about this class of network devices. If you say Y, you
1207 will be asked for your specific device in the following questions.
1210 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1211 depends on NET_POCKET && PARPORT && X86
1214 This is a network (Ethernet) device which attaches to your parallel
1215 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1216 available from <http://www.tldp.org/docs.html#howto>, if you
1217 want to use this. If you intend to use this driver, you should have
1218 said N to the "Parallel printer support", because the two drivers
1219 don't like each other.
1221 To compile this driver as a module, choose M here: the module
1225 tristate "D-Link DE600 pocket adapter support"
1226 depends on NET_POCKET && PARPORT
1228 This is a network (Ethernet) device which attaches to your parallel
1229 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1230 Ethernet-HOWTO, available from
1231 <http://www.tldp.org/docs.html#howto>, if you want to use
1232 this. It is possible to have several devices share a single parallel
1233 port and it is safe to compile the corresponding drivers into the
1236 To compile this driver as a module, choose M here: the module
1237 will be called de600.
1240 tristate "D-Link DE620 pocket adapter support"
1241 depends on NET_POCKET && PARPORT
1243 This is a network (Ethernet) device which attaches to your parallel
1244 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1245 Ethernet-HOWTO, available from
1246 <http://www.tldp.org/docs.html#howto>, if you want to use
1247 this. It is possible to have several devices share a single parallel
1248 port and it is safe to compile the corresponding drivers into the
1251 To compile this driver as a module, choose M here: the module
1252 will be called de620.
1255 tristate "SGI Seeq ethernet controller support"
1256 depends on SGI_HAS_SEEQ
1258 Say Y here if you have an Seeq based Ethernet network card. This is
1259 used in many Silicon Graphics machines.
1262 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1263 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1264 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1265 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1268 Say Y here if you want to use the built-in 10/100 Fast ethernet
1269 controller on some Motorola ColdFire and Freescale i.MX processors.
1272 tristate "MPC52xx FEC driver"
1273 depends on PPC_MPC52xx && PPC_BESTCOMM
1276 select PPC_BESTCOMM_FEC
1278 This option enables support for the MPC5200's on-chip
1279 Fast Ethernet Controller
1280 If compiled as module, it will be called fec_mpc52xx.
1282 config FEC_MPC52xx_MDIO
1283 bool "MPC52xx FEC MDIO bus driver"
1284 depends on FEC_MPC52xx
1287 The MPC5200's FEC can connect to the Ethernet either with
1288 an external MII PHY chip or 10 Mbps 7-wire interface
1289 (Motorola? industry standard).
1290 If your board uses an external PHY connected to FEC, enable this.
1291 If not sure, enable.
1292 If compiled as module, it will be called fec_mpc52xx_phy.
1295 tristate "Atheros L2 Fast Ethernet support"
1300 This driver supports the Atheros L2 fast ethernet adapter.
1302 To compile this driver as a module, choose M here. The module
1303 will be called atl2.
1305 config XILINX_EMACLITE
1306 tristate "Xilinx 10/100 Ethernet Lite support"
1307 depends on PPC32 || MICROBLAZE
1310 This driver supports the 10/100 Ethernet Lite from Xilinx.
1313 tristate "Faraday FTMAC100 10/100 Ethernet support"
1317 This driver supports the FTMAC100 10/100 Ethernet controller
1318 from Faraday. It is used on Faraday A320, Andes AG101 and some
1319 other ARM/NDS32 SoC's.
1322 tristate "Lantiq SoC ETOP driver"
1323 depends on SOC_TYPE_XWAY
1325 Support for the MII0 inside the Lantiq SoC
1328 source "drivers/net/fs_enet/Kconfig"
1330 source "drivers/net/octeon/Kconfig"
1332 endif # NET_ETHERNET
1338 menuconfig NETDEV_1000
1339 bool "Ethernet (1000 Mbit)"
1343 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1344 type of Local Area Network (LAN) in universities and companies.
1346 Say Y here to get to see options for Gigabit Ethernet drivers.
1347 This option alone does not add any kernel code.
1348 Note that drivers supporting both 100 and 1000 MBit may be listed
1349 under "Ethernet (10 or 100MBit)" instead.
1351 If you say N, all options in this submenu will be skipped and disabled.
1356 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1360 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1362 D-Link DGE-550T Gigabit Ethernet Adapter.
1363 D-Link DL2000-based Gigabit Ethernet Adapter.
1364 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1366 To compile this driver as a module, choose M here: the
1367 module will be called dl2k.
1370 tristate "IP1000 Gigabit Ethernet support"
1371 depends on PCI && EXPERIMENTAL
1374 This driver supports IP1000 gigabit Ethernet cards.
1376 To compile this driver as a module, choose M here: the module
1377 will be called ipg. This is recommended.
1379 source "drivers/net/ixp2000/Kconfig"
1382 tristate "National Semiconductor DP83820 support"
1385 This is a driver for the National Semiconductor DP83820 series
1386 of gigabit ethernet MACs. Cards using this chipset include
1387 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1388 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1392 tristate "Packet Engines Hamachi GNIC-II support"
1396 If you have a Gigabit Ethernet card of this type, say Y and read
1397 the Ethernet-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>.
1400 To compile this driver as a module, choose M here. The module will be
1404 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1405 depends on PCI && EXPERIMENTAL
1408 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1409 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1410 used by the Beowulf Linux cluster project. See
1411 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1412 information about this driver in particular and Beowulf in general.
1414 To compile this driver as a module, choose M here: the module
1415 will be called yellowfin. This is recommended.
1418 tristate "Realtek 8169 gigabit ethernet support"
1424 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1426 To compile this driver as a module, choose M here: the module
1427 will be called r8169. This is recommended.
1430 tristate "SiS190/SiS191 gigabit ethernet support"
1435 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1436 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1437 appear in lan on motherboard designs which are based on SiS 965
1438 and SiS 966 south bridge.
1440 To compile this driver as a module, choose M here: the module
1441 will be called sis190. This is recommended.
1444 tristate "Marvell Yukon Gigabit Ethernet support"
1448 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1449 and related Gigabit Ethernet adapters. It is a new smaller driver
1450 with better performance and more complete ethtool support.
1452 It does not support the link failover and network management
1453 features that "portable" vendor supplied sk98lin driver does.
1455 This driver supports adapters based on the original Yukon chipset:
1456 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
1457 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
1459 It does not support the newer Yukon2 chipset: a separate driver,
1460 sky2, is provided for these adapters.
1462 To compile this driver as a module, choose M here: the module
1463 will be called skge. This is recommended.
1466 bool "Debugging interface"
1467 depends on SKGE && DEBUG_FS
1469 This option adds the ability to dump driver state for debugging.
1470 The file /sys/kernel/debug/skge/ethX displays the state of the internal
1471 transmit and receive rings.
1476 bool "Support for older SysKonnect Genesis boards"
1479 This enables support for the older and uncommon SysKonnect Genesis
1480 chips, which support MII via an external transceiver, instead of
1481 an internal one. Disabling this option will save some memory
1482 by making code smaller. If unsure say Y.
1485 tristate "Marvell Yukon 2 support"
1489 This driver supports Gigabit Ethernet adapters based on the
1490 Marvell Yukon 2 chipset:
1491 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
1492 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
1494 There is companion driver for the older Marvell Yukon and
1495 SysKonnect Genesis based adapters: skge.
1497 To compile this driver as a module, choose M here: the module
1498 will be called sky2. This is recommended.
1501 bool "Debugging interface"
1502 depends on SKY2 && DEBUG_FS
1504 This option adds the ability to dump driver state for debugging.
1505 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
1506 transmit and receive rings.
1511 tristate "VIA Velocity support"
1517 If you have a VIA "Velocity" based network card say Y here.
1519 To compile this driver as a module, choose M here. The module
1520 will be called via-velocity.
1523 tristate "Spider Gigabit Ethernet driver"
1524 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
1527 This driver supports the Gigabit Ethernet chips present on the
1528 Cell Processor-Based Blades from IBM.
1531 tristate "Tundra TSI108 gigabit Ethernet support"
1532 depends on TSI108_BRIDGE
1534 This driver supports Tundra TSI108 gigabit Ethernet ports.
1535 To compile this driver as a module, choose M here: the module
1536 will be called tsi108_eth.
1539 tristate "PS3 Gigabit Ethernet driver"
1541 select PS3_SYS_MANAGER
1543 This driver supports the network device on the PS3 game
1544 console. This driver has built-in support for Ethernet.
1546 To compile this driver as a module, choose M here: the
1547 module will be called ps3_gelic.
1549 config GELIC_WIRELESS
1550 bool "PS3 Wireless support"
1552 depends on GELIC_NET
1555 This option adds the support for the wireless feature of PS3.
1556 If you have the wireless-less model of PS3 or have no plan to
1557 use wireless feature, disabling this option saves memory. As
1558 the driver automatically distinguishes the models, you can
1559 safely enable this option even if you have a wireless-less model.
1562 tristate "Freescale PQ MDIO"
1566 This driver supports the MDIO bus used by the gianfar and UCC drivers.
1569 tristate "Gianfar Ethernet"
1575 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
1576 and MPC86xx family of chips, and the FEC on the 8540.
1579 tristate "Freescale QE Gigabit Ethernet"
1580 depends on QUICC_ENGINE
1584 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
1585 which is available on some Freescale SOCs.
1587 config UGETH_TX_ON_DEMAND
1588 bool "Transmit on Demand support"
1592 tristate "Marvell Discovery (643XX) and Orion ethernet support"
1593 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
1597 This driver supports the gigabit ethernet MACs in the
1598 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
1599 in the Marvell Orion ARM SoC family.
1601 Some boards that use the Discovery chipset are the Momenco
1602 Ocelot C and Jaguar ATX and Pegasos II.
1604 config XILINX_LL_TEMAC
1605 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1606 depends on PPC || MICROBLAZE
1609 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1610 core used in Xilinx Spartan and Virtex FPGAs
1613 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
1618 This driver supports the Atheros/Attansic L1 gigabit ethernet
1621 To compile this driver as a module, choose M here. The module
1622 will be called atl1.
1625 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
1626 depends on PCI && EXPERIMENTAL
1630 This driver supports the Atheros L1E gigabit ethernet adapter.
1632 To compile this driver as a module, choose M here. The module
1633 will be called atl1e.
1636 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
1637 depends on PCI && EXPERIMENTAL
1641 This driver supports the Atheros L1C gigabit ethernet adapter.
1643 To compile this driver as a module, choose M here. The module
1644 will be called atl1c.
1647 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1652 This driver supports the PCI-Express gigabit ethernet adapters
1653 based on JMicron JMC250 chipset.
1655 To compile this driver as a module, choose M here. The module
1659 tristate "S6105 GMAC ethernet support"
1660 depends on XTENSA_VARIANT_S6000
1663 This driver supports the on chip ethernet device on the
1664 S6105 xtensa processor.
1666 To compile this driver as a module, choose M here. The module
1667 will be called s6gmac.
1669 source "drivers/net/stmmac/Kconfig"
1672 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1676 This is a gigabit ethernet driver for EG20T PCH.
1677 EG20T PCH is the platform controller hub that is used in Intel's
1678 general embedded platform.
1679 EG20T PCH has Gigabit Ethernet interface.
1680 Using this interface, it is able to access system devices connected
1681 to Gigabit Ethernet.
1682 This driver enables Gigabit Ethernet function.
1684 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1685 Output Hub), ML7223.
1686 ML7223 IOH is for MP(Media Phone) use.
1687 ML7223 is companion chip for Intel Atom E6xx series.
1688 ML7223 is completely compatible for Intel EG20T PCH.
1691 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
1695 This driver supports the FTGMAC100 Gigabit Ethernet controller
1696 from Faraday. It is used on Faraday A369, Andes AG102 and some
1697 other ARM/NDS32 SoC's.
1702 # 10 Gigabit Ethernet
1705 menuconfig NETDEV_10000
1706 bool "Ethernet (10000 Mbit)"
1710 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1711 This option alone does not add any kernel code.
1713 If you say N, all options in this submenu will be skipped and disabled.
1721 tristate "eHEA Ethernet support"
1722 depends on IBMEBUS && INET && SPARSEMEM
1725 This driver supports the IBM pSeries eHEA ethernet adapter.
1727 To compile the driver as a module, choose M here. The module
1728 will be called ehea.
1731 tristate "Cisco VIC Ethernet NIC Support"
1732 depends on PCI && INET
1734 This enables the support for the Cisco VIC Ethernet card.
1737 tristate "Exar Xframe 10Gb Ethernet Adapter"
1740 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
1742 More specific information on configuring the driver is in
1743 <file:Documentation/networking/s2io.txt>.
1745 To compile this driver as a module, choose M here. The module
1746 will be called s2io.
1749 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
1750 depends on PCI && INET
1752 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
1753 I/O Virtualized Server Adapter.
1755 More specific information on configuring the driver is in
1756 <file:Documentation/networking/vxge.txt>.
1758 To compile this driver as a module, choose M here. The module
1759 will be called vxge.
1761 config VXGE_DEBUG_TRACE_ALL
1762 bool "Enabling All Debug trace statments in driver"
1766 Say Y here if you want to enabling all the debug trace statements in
1767 the vxge driver. By default only few debug trace statements are
1771 tristate "Myricom Myri-10G Ethernet support"
1772 depends on PCI && INET
1777 This driver supports Myricom Myri-10G Dual Protocol interface in
1778 Ethernet mode. If the eeprom on your board is not recent enough,
1779 you will need a newer firmware image.
1780 You may get this image or more information, at:
1782 <http://www.myri.com/scs/download-Myri10GE.html>
1784 To compile this driver as a module, choose M here. The module
1785 will be called myri10ge.
1788 bool "Direct Cache Access (DCA) Support"
1790 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
1792 Say Y here if you want to use Direct Cache Access (DCA) in the
1793 driver. DCA is a method for warming the CPU cache before data
1794 is used, with the intent of lessening the impact of cache misses.
1797 tristate "Sun Neptune 10Gbit Ethernet support"
1801 This enables support for cards based upon Sun's
1805 tristate "PA Semi 1/10Gbit MAC"
1806 depends on PPC_PASEMI && PCI && INET
1810 This driver supports the on-chip 1/10Gbit Ethernet controller on
1811 PA Semi's PWRficient line of chips.
1814 tristate "Mellanox Technologies 10Gbit Ethernet support"
1815 depends on PCI && INET
1819 This driver supports Mellanox Technologies ConnectX Ethernet
1828 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
1829 depends on MLX4_CORE
1832 This option causes debugging code to be compiled into the
1833 mlx4_core driver. The output can be turned on via the
1834 debug_level module parameter (which can also be set after
1835 the driver is loaded through sysfs).
1838 tristate "Tehuti Networks 10G Ethernet"
1841 Tehuti Networks 10G Ethernet NIC
1844 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
1847 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
1849 To compile this driver as a module, choose M here: the module
1852 For general information and support, go to the Brocade support
1855 <http://support.brocade.com>
1857 source "drivers/net/sfc/Kconfig"
1859 source "drivers/net/benet/Kconfig"
1861 endif # NETDEV_10000
1863 source "drivers/net/tokenring/Kconfig"
1865 source "drivers/net/wireless/Kconfig"
1867 source "drivers/net/wimax/Kconfig"
1869 source "drivers/net/usb/Kconfig"
1871 source "drivers/net/pcmcia/Kconfig"
1873 source "drivers/net/wan/Kconfig"
1875 source "drivers/atm/Kconfig"
1877 source "drivers/ieee802154/Kconfig"
1879 source "drivers/s390/net/Kconfig"
1881 source "drivers/net/caif/Kconfig"
1884 tristate "Tilera GBE/XGBE network driver support"
1889 This is a standard Linux network device driver for the
1890 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1892 To compile this driver as a module, choose M here: the module
1893 will be called tile_net.
1895 config XEN_NETDEV_FRONTEND
1896 tristate "Xen network device frontend driver"
1898 select XEN_XENBUS_FRONTEND
1901 This driver provides support for Xen paravirtual network
1902 devices exported by a Xen network driver domain (often
1905 The corresponding Linux backend driver is enabled by the
1906 CONFIG_XEN_NETDEV_BACKEND option.
1908 If you are compiling a kernel for use as Xen guest, you
1909 should say Y here. To compile this driver as a module, chose
1910 M here: the module will be called xen-netfront.
1912 config XEN_NETDEV_BACKEND
1913 tristate "Xen backend network device"
1914 depends on XEN_BACKEND
1916 This driver allows the kernel to act as a Xen network driver
1917 domain which exports paravirtual network devices to other
1918 Xen domains. These devices can be accessed by any operating
1919 system that implements a compatible front end.
1921 The corresponding Linux frontend driver is enabled by the
1922 CONFIG_XEN_NETDEV_FRONTEND configuration option.
1924 The backend driver presents a standard network device
1925 endpoint for each paravirtual network device to the driver
1926 domain network stack. These can then be bridged or routed
1927 etc in order to provide full network connectivity.
1929 If you are compiling a kernel to run in a Xen network driver
1930 domain (often this is domain 0) you should say Y here. To
1931 compile this driver as a module, chose M here: the module
1932 will be called xen-netback.
1935 tristate "iSeries Virtual Ethernet driver support"
1936 depends on PPC_ISERIES
1939 tristate "RapidIO Ethernet over messaging driver support"
1942 config RIONET_TX_SIZE
1943 int "Number of outbound queue entries"
1947 config RIONET_RX_SIZE
1948 int "Number of inbound queue entries"
1953 tristate "FDDI driver support"
1954 depends on (PCI || EISA || TC)
1956 Fiber Distributed Data Interface is a high speed local area network
1957 design; essentially a replacement for high speed Ethernet. FDDI can
1958 run over copper or fiber. If you are connected to such a network and
1959 want a driver for the FDDI card in your computer, say Y here (and
1960 then also Y to the driver for your FDDI card, below). Most people
1964 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1965 depends on FDDI && (PCI || EISA || TC)
1967 This is support for the DIGITAL series of TURBOchannel (DEFTA),
1968 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1969 to a local FDDI network.
1971 To compile this driver as a module, choose M here: the module
1972 will be called defxx. If unsure, say N.
1976 prompt "Use MMIO instead of PIO" if PCI || EISA
1978 default n if PCI || EISA
1981 This instructs the driver to use EISA or PCI memory-mapped I/O
1982 (MMIO) as appropriate instead of programmed I/O ports (PIO).
1983 Enabling this gives an improvement in processing time in parts
1984 of the driver, but it may cause problems with EISA (DEFEA)
1985 adapters. TURBOchannel does not have the concept of I/O ports,
1986 so MMIO is always used for these (DEFTA) adapters.
1991 tristate "SysKonnect FDDI PCI support"
1992 depends on FDDI && PCI
1995 Say Y here if you have a SysKonnect FDDI PCI adapter.
1996 The following adapters are supported by this driver:
1997 - SK-5521 (SK-NET FDDI-UP)
1998 - SK-5522 (SK-NET FDDI-UP DAS)
1999 - SK-5541 (SK-NET FDDI-FP)
2000 - SK-5543 (SK-NET FDDI-LP)
2001 - SK-5544 (SK-NET FDDI-LP DAS)
2002 - SK-5821 (SK-NET FDDI-UP64)
2003 - SK-5822 (SK-NET FDDI-UP64 DAS)
2004 - SK-5841 (SK-NET FDDI-FP64)
2005 - SK-5843 (SK-NET FDDI-LP64)
2006 - SK-5844 (SK-NET FDDI-LP64 DAS)
2007 - Netelligent 100 FDDI DAS Fibre SC
2008 - Netelligent 100 FDDI SAS Fibre SC
2009 - Netelligent 100 FDDI DAS UTP
2010 - Netelligent 100 FDDI SAS UTP
2011 - Netelligent 100 FDDI SAS Fibre MIC
2013 Read <file:Documentation/networking/skfp.txt> for information about
2016 Questions concerning this driver can be addressed to:
2017 <linux@syskonnect.de>
2019 To compile this driver as a module, choose M here: the module
2020 will be called skfp. This is recommended.
2023 bool "HIPPI driver support (EXPERIMENTAL)"
2024 depends on EXPERIMENTAL && INET && PCI
2026 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2027 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2028 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2029 single-mode). HIPPI networks are commonly used for clusters and to
2030 connect to super computers. If you are connected to a HIPPI network
2031 and have a HIPPI network card in your computer that you want to use
2032 under Linux, say Y here (you must also remember to enable the driver
2033 for your HIPPI card below). Most people will say N here.
2036 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2037 depends on HIPPI && PCI
2039 Say Y here if this is your PCI HIPPI network card.
2041 To compile this driver as a module, choose M here: the module
2042 will be called rrunner. If unsure, say N.
2044 config ROADRUNNER_LARGE_RINGS
2045 bool "Use large TX/RX rings (EXPERIMENTAL)"
2046 depends on ROADRUNNER
2048 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2049 of additional memory to allow for fastest operation, both for
2050 transmitting and receiving. This memory cannot be used by any other
2051 kernel code or by user space programs. Say Y here only if you have
2055 tristate "PLIP (parallel port) support"
2058 PLIP (Parallel Line Internet Protocol) is used to create a
2059 reasonably fast mini network consisting of two (or, rarely, more)
2060 local machines. A PLIP link from a Linux box is a popular means to
2061 install a Linux distribution on a machine which doesn't have a
2062 CD-ROM drive (a minimal system has to be transferred with floppies
2063 first). The kernels on both machines need to have this PLIP option
2064 enabled for this to work.
2066 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2067 ports (the connectors at the computers with 25 holes) are connected
2068 with "null printer" or "Turbo Laplink" cables which can transmit 4
2069 bits at a time (mode 0) or with special PLIP cables, to be used on
2070 bidirectional parallel ports only, which can transmit 8 bits at a
2071 time (mode 1); you can find the wiring of these cables in
2072 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2073 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2074 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2075 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2076 and winsock or NCSA's telnet.
2078 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2079 as the NET-3-HOWTO, both available from
2080 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2081 protocol has been changed and this PLIP driver won't work together
2082 with the PLIP support in Linux versions 1.0.x. This option enlarges
2083 your kernel by about 8 KB.
2085 To compile this driver as a module, choose M here. The module
2086 will be called plip. If unsure, say Y or M, in case you buy
2090 tristate "PPP (point-to-point protocol) support"
2093 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2094 the same purpose: sending Internet traffic over telephone (and other
2095 serial) lines. Ask your access provider if they support it, because
2096 otherwise you can't use it; most Internet access providers these
2097 days support PPP rather than SLIP.
2099 To use PPP, you need an additional program called pppd as described
2100 in the PPP-HOWTO, available at
2101 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2102 the version of pppd recommended in <file:Documentation/Changes>.
2103 The PPP option enlarges your kernel by about 16 KB.
2105 There are actually two versions of PPP: the traditional PPP for
2106 asynchronous lines, such as regular analog phone lines, and
2107 synchronous PPP which can be used over digital ISDN lines for
2108 example. If you want to use PPP over phone lines or other
2109 asynchronous serial lines, you need to say Y (or M) here and also to
2110 the next option, "PPP support for async serial ports". For PPP over
2111 synchronous lines, you should say Y (or M) here and to "Support
2112 synchronous PPP", below.
2114 If you said Y to "Version information on all symbols" above, then
2115 you cannot compile the PPP driver into the kernel; you can then only
2116 compile it as a module. To compile this driver as a module, choose M
2117 here. The module will be called ppp_generic.
2119 config PPP_MULTILINK
2120 bool "PPP multilink support (EXPERIMENTAL)"
2121 depends on PPP && EXPERIMENTAL
2123 PPP multilink is a protocol (defined in RFC 1990) which allows you
2124 to combine several (logical or physical) lines into one logical PPP
2125 connection, so that you can utilize your full bandwidth.
2127 This has to be supported at the other end as well and you need a
2128 version of the pppd daemon which understands the multilink protocol.
2133 bool "PPP filtering"
2136 Say Y here if you want to be able to filter the packets passing over
2137 PPP interfaces. This allows you to control which packets count as
2138 activity (i.e. which packets will reset the idle timer or bring up
2139 a demand-dialed link) and which packets are to be dropped entirely.
2140 You need to say Y here if you wish to use the pass-filter and
2141 active-filter options to pppd.
2146 tristate "PPP support for async serial ports"
2150 Say Y (or M) here if you want to be able to use PPP over standard
2151 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2152 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2155 To compile this driver as a module, choose M here.
2160 tristate "PPP support for sync tty ports"
2163 Say Y (or M) here if you want to be able to use PPP over synchronous
2164 (HDLC) tty devices, such as the SyncLink adapter. These devices
2165 are often used for high-speed leased lines like T1/E1.
2167 To compile this driver as a module, choose M here.
2170 tristate "PPP Deflate compression"
2175 Support for the Deflate compression method for PPP, which uses the
2176 Deflate algorithm (the same algorithm that gzip uses) to compress
2177 each PPP packet before it is sent over the wire. The machine at the
2178 other end of the PPP link (usually your ISP) has to support the
2179 Deflate compression method as well for this to be useful. Even if
2180 they don't support it, it is safe to say Y here.
2182 To compile this driver as a module, choose M here.
2185 tristate "PPP BSD-Compress compression"
2188 Support for the BSD-Compress compression method for PPP, which uses
2189 the LZW compression method to compress each PPP packet before it is
2190 sent over the wire. The machine at the other end of the PPP link
2191 (usually your ISP) has to support the BSD-Compress compression
2192 method as well for this to be useful. Even if they don't support it,
2193 it is safe to say Y here.
2195 The PPP Deflate compression method ("PPP Deflate compression",
2196 above) is preferable to BSD-Compress, because it compresses better
2199 Note that the BSD compression code will always be compiled as a
2200 module; it is called bsd_comp and will show up in the directory
2201 modules once you have said "make modules". If unsure, say N.
2204 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2205 depends on PPP && EXPERIMENTAL
2211 Support for the MPPE Encryption protocol, as employed by the
2212 Microsoft Point-to-Point Tunneling Protocol.
2214 See http://pptpclient.sourceforge.net/ for information on
2215 configuring PPTP clients and servers to utilize this method.
2218 tristate "PPP over Ethernet (EXPERIMENTAL)"
2219 depends on EXPERIMENTAL && PPP
2221 Support for PPP over Ethernet.
2223 This driver requires the latest version of pppd from the CVS
2224 repository at cvs.samba.org. Alternatively, see the
2225 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2226 which contains instruction on how to use this driver (under
2227 the heading "Kernel mode PPPoE").
2230 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
2231 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
2233 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
2235 This driver requires pppd plugin to work in client mode or
2236 modified pptpd (poptop) to work in server mode.
2237 See http://accel-pptp.sourceforge.net/ for information how to
2238 utilize this module.
2241 tristate "PPP over ATM"
2242 depends on ATM && PPP
2244 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2245 This implementation does not yet comply with section 8 of RFC2364,
2246 which can lead to bad results if the ATM peer loses state and
2247 changes its encapsulation unilaterally.
2250 tristate "PPP over L2TP (EXPERIMENTAL)"
2251 depends on EXPERIMENTAL && L2TP && PPP
2253 Support for PPP-over-L2TP socket family. L2TP is a protocol
2254 used by ISPs and enterprises to tunnel PPP traffic over UDP
2255 tunnels. L2TP is replacing PPTP for VPN uses.
2258 tristate "SLIP (serial line) support"
2260 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2261 connect to your Internet service provider or to connect to some
2262 other local Unix box or if you want to configure your Linux box as a
2263 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2264 Internet Protocol) is a protocol used to send Internet traffic over
2265 serial connections such as telephone lines or null modem cables;
2266 nowadays, the protocol PPP is more commonly used for this same
2269 Normally, your access provider has to support SLIP in order for you
2270 to be able to use it, but there is now a SLIP emulator called SLiRP
2271 around (available from
2272 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2273 allows you to use SLIP over a regular dial up shell connection. If
2274 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2275 NET-3-HOWTO, available from
2276 <http://www.tldp.org/docs.html#howto>, explains how to
2277 configure SLIP. Note that you don't need this option if you just
2278 want to run term (term is a program which gives you almost full
2279 Internet connectivity if you have a regular dial up shell account on
2280 some Internet connected Unix computer. Read
2281 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2282 support will enlarge your kernel by about 4 KB. If unsure, say N.
2284 To compile this driver as a module, choose M here. The module
2285 will be called slip.
2287 config SLIP_COMPRESSED
2288 bool "CSLIP compressed headers"
2292 This protocol is faster than SLIP because it uses compression on the
2293 TCP/IP headers (not on the data itself), but it has to be supported
2294 on both ends. Ask your access provider if you are not sure and
2295 answer Y, just in case. You will still be able to use plain SLIP. If
2296 you plan to use SLiRP, the SLIP emulator (available from
2297 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2298 allows you to use SLIP over a regular dial up shell connection, you
2299 definitely want to say Y here. The NET-3-HOWTO, available from
2300 <http://www.tldp.org/docs.html#howto>, explains how to configure
2301 CSLIP. This won't enlarge your kernel.
2306 This option enables Van Jacobsen serial line header compression
2310 bool "Keepalive and linefill"
2313 Adds additional capabilities to the SLIP driver to support the
2314 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2317 config SLIP_MODE_SLIP6
2318 bool "Six bit SLIP encapsulation"
2321 Just occasionally you may need to run IP over hostile serial
2322 networks that don't pass all control characters or are only seven
2323 bit. Saying Y here adds an extra mode you can use with SLIP:
2324 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2325 the serial device. Naturally, this has to be supported at the other
2326 end of the link as well. It's good enough, for example, to run IP
2327 over the async ports of a Camtec JNT Pad. If unsure, say N.
2330 bool "Fibre Channel driver support"
2331 depends on SCSI && PCI
2333 Fibre Channel is a high speed serial protocol mainly used to connect
2334 large storage devices to the computer; it is compatible with and
2335 intended to replace SCSI.
2337 If you intend to use Fibre Channel, you need to have a Fibre channel
2338 adaptor card in your computer; say Y here and to the driver for your
2339 adaptor below. You also should have said Y to "SCSI support" and
2340 "SCSI generic support".
2343 tristate "Network console logging support"
2345 If you want to log kernel messages over the network, enable this.
2346 See <file:Documentation/networking/netconsole.txt> for details.
2348 config NETCONSOLE_DYNAMIC
2349 bool "Dynamic reconfiguration of logging targets"
2350 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
2351 !(NETCONSOLE=y && CONFIGFS_FS=m)
2353 This option enables the ability to dynamically reconfigure target
2354 parameters (interface, IP addresses, port numbers, MAC addresses)
2355 at runtime through a userspace interface exported using configfs.
2356 See <file:Documentation/networking/netconsole.txt> for details.
2362 bool "Netpoll traffic trapping"
2366 config NET_POLL_CONTROLLER
2370 tristate "Virtio network driver (EXPERIMENTAL)"
2371 depends on EXPERIMENTAL && VIRTIO
2373 This is the virtual network driver for virtio. It can be used with
2374 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
2377 tristate "VMware VMXNET3 ethernet driver"
2378 depends on PCI && INET
2380 This driver supports VMware's vmxnet3 virtual ethernet NIC.
2381 To compile this driver as a module, choose M here: the
2382 module will be called vmxnet3.