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 bool "SGI IOC3 Ethernet"
249 depends on PCI && SGI_IP27
253 If you have a network (Ethernet) card of this type, say Y and read
254 the Ethernet-HOWTO, available from
255 <http://www.tldp.org/docs.html#howto>.
258 tristate "MIPS simulator Network device"
261 The MIPSNET device is a simple Ethernet network device which is
262 emulated by the MIPS Simulator.
263 If you are not using a MIPSsim or are unsure, say N.
265 config SGI_O2MACE_ETH
266 tristate "SGI O2 MACE Fast Ethernet support"
267 depends on SGI_IP32=y
270 tristate "Renesas SuperH Ethernet support"
271 depends on SUPERH && \
272 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
273 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
274 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
280 Renesas SuperH Ethernet device driver.
281 This driver supporting CPUs are:
282 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
285 tristate "Blackfin on-chip MAC support"
286 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
290 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
292 This is the driver for Blackfin on-chip mac device. Say Y if you want it
293 compiled into the kernel. This driver is also available as a module
294 ( = code which can be inserted in and removed from the running kernel
295 whenever you want). The module will be called bfin_mac.
297 config BFIN_MAC_USE_L1
298 bool "Use L1 memory for rx/tx packets"
299 depends on BFIN_MAC && (BF527 || BF537)
302 To get maximum network performance, you should use L1 memory as rx/tx buffers.
303 Say N here if you want to reserve L1 memory for other uses.
305 config BFIN_TX_DESC_NUM
306 int "Number of transmit buffer packets"
308 range 6 10 if BFIN_MAC_USE_L1
312 Set the number of buffer packets used in driver.
314 config BFIN_RX_DESC_NUM
315 int "Number of receive buffer packets"
317 range 20 100 if BFIN_MAC_USE_L1
321 Set the number of buffer packets used in driver.
323 config BFIN_MAC_USE_HWSTAMP
324 bool "Use IEEE 1588 hwstamp"
325 depends on BFIN_MAC && BF518
328 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
331 tristate "Marvell pxa168 ethernet support"
332 depends on CPU_PXA168
335 This driver supports the pxa168 Ethernet ports.
337 To compile this driver as a module, choose M here. The module
338 will be called pxa168_eth.
341 tristate "NetX Ethernet support"
345 This is support for the Hilscher netX builtin Ethernet ports
347 To compile this driver as a module, choose M here. The module
348 will be called netx-eth.
350 config TI_DAVINCI_EMAC
351 tristate "TI DaVinci EMAC Support"
352 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
353 select TI_DAVINCI_MDIO
354 select TI_DAVINCI_CPDMA
357 This driver supports TI's DaVinci Ethernet .
359 To compile this driver as a module, choose M here: the module
360 will be called davinci_emac_driver. This is recommended.
362 config TI_DAVINCI_MDIO
363 tristate "TI DaVinci MDIO Support"
364 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
367 This driver supports TI's DaVinci MDIO module.
369 To compile this driver as a module, choose M here: the module
370 will be called davinci_mdio. This is recommended.
372 config TI_DAVINCI_CPDMA
373 tristate "TI DaVinci CPDMA Support"
374 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
376 This driver supports TI's DaVinci CPDMA dma engine.
378 To compile this driver as a module, choose M here: the module
379 will be called davinci_cpdma. This is recommended.
382 tristate "DM9000 support"
383 depends on ARM || BLACKFIN || MIPS
387 Support for DM9000 chipset.
389 To compile this driver as a module, choose M here. The module
390 will be called dm9000.
392 config DM9000_DEBUGLEVEL
393 int "DM9000 maximum debug level"
397 The maximum level of debugging code compiled into the DM9000
400 config DM9000_FORCE_SIMPLE_PHY_POLL
401 bool "Force simple NSR based PHY polling"
404 This configuration forces the DM9000 to use the NSR's LinkStatus
405 bit to determine if the link is up or down instead of the more
406 costly MII PHY reads. Note, this will not work if the chip is
407 operating with an external PHY.
410 tristate "ENC28J60 support"
411 depends on EXPERIMENTAL && SPI && NET_ETHERNET
414 Support for the Microchip EN28J60 ethernet chip.
416 To compile this driver as a module, choose M here. The module will be
419 config ENC28J60_WRITEVERIFY
420 bool "Enable write verify"
423 Enable the verify after the buffer write useful for debugging purpose.
427 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
428 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
434 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
437 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
442 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
445 tristate "Dave ethernet support (DNET)"
446 depends on NET_ETHERNET && HAS_IOMEM
449 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
450 Say Y to include support for the DNET chip.
452 To compile this driver as a module, choose M here: the module
456 tristate "AT1700/1720 support (EXPERIMENTAL)"
457 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
460 If you have a network (Ethernet) card of this type, say Y and read
461 the Ethernet-HOWTO, available from
462 <http://www.tldp.org/docs.html#howto>.
464 To compile this driver as a module, choose M here. The module
465 will be called at1700.
468 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
469 depends on ISA || EISA || PCI
471 If you have a network (Ethernet) card of this type, say Y and read
472 the Ethernet-HOWTO, available from
473 <http://www.tldp.org/docs.html#howto>.
475 To compile this driver as a module, choose M here. The module
476 will be called hp100.
479 bool "Other ISA cards"
482 If your network (Ethernet) card hasn't been mentioned yet and its
483 bus system (that's the way the cards talks to the other components
484 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
485 Make sure you know the name of your card. Read the Ethernet-HOWTO,
486 available from <http://www.tldp.org/docs.html#howto>.
490 Note that the answer to this question doesn't directly affect the
491 kernel: saying N will just cause the configurator to skip all
492 the remaining ISA network card questions. If you say Y, you will be
493 asked for your specific card in the following questions.
496 tristate "ICL EtherTeam 16i/32 support"
499 If you have a network (Ethernet) card of this type, say Y and read
500 the Ethernet-HOWTO, available from
501 <http://www.tldp.org/docs.html#howto>.
503 To compile this driver as a module, choose M here. The module
504 will be called eth16i.
507 tristate "SEEQ8005 support (EXPERIMENTAL)"
508 depends on NET_ISA && EXPERIMENTAL
510 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
511 is for you, read the Ethernet-HOWTO, available from
512 <http://www.tldp.org/docs.html#howto>.
514 To compile this driver as a module, choose M here. The module
515 will be called seeq8005.
518 bool "EISA, VLB, PCI and on board controllers"
519 depends on ISA || EISA || PCI
521 This is another class of network cards which attach directly to the
522 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
523 available from <http://www.tldp.org/docs.html#howto>.
525 Note that the answer to this question doesn't directly affect the
526 kernel: saying N will just cause the configurator to skip all
527 the questions about this class of network cards. If you say Y, you
528 will be asked for your specific card in the following questions. If
529 you are unsure, say Y.
531 config ADAPTEC_STARFIRE
532 tristate "Adaptec Starfire/DuraLAN support"
533 depends on NET_PCI && PCI
537 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
538 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
539 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
542 To compile this driver as a module, choose M here: the module
543 will be called starfire. This is recommended.
546 tristate "Micrel KSZ8841/2 PCI"
547 depends on NET_PCI && PCI
551 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
553 To compile this driver as a module, choose M here. The module
554 will be called ksz884x.
557 tristate "nForce Ethernet support"
558 depends on NET_PCI && PCI
560 If you have a network (Ethernet) controller of this type, say Y and
561 read the Ethernet-HOWTO, available from
562 <http://www.tldp.org/docs.html#howto>.
564 To compile this driver as a module, choose M here. The module
565 will be called forcedeth.
568 tristate "TOSHIBA TC35815 Ethernet support"
569 depends on NET_PCI && PCI && MIPS
573 tristate "Myson MTD-8xx PCI Ethernet support"
574 depends on NET_PCI && PCI
578 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
579 cards. <http://www.myson.com.tw/>
582 tristate "RDC R6040 Fast Ethernet Adapter support"
583 depends on NET_PCI && PCI
588 This is a driver for the R6040 Fast Ethernet MACs found in the
589 the RDC R-321x System-on-chips.
591 To compile this driver as a module, choose M here: the module
592 will be called r6040. This is recommended.
595 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
596 depends on NET_PCI && PCI
600 This is a driver for the Fast Ethernet PCI network cards based on
601 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
602 SiS 630 and SiS 540 chipsets.
604 This driver also supports AMD 79C901 HomePNA so that you can use
605 your phone line as a network cable.
607 To compile this driver as a module, choose M here: the module
608 will be called sis900. This is recommended.
611 tristate "TI ThunderLAN support"
612 depends on NET_PCI && (PCI || EISA)
614 If you have a PCI Ethernet network card based on the ThunderLAN chip
615 which is supported by this driver, say Y and read the
616 Ethernet-HOWTO, available from
617 <http://www.tldp.org/docs.html#howto>.
619 Devices currently supported by this driver are Compaq Netelligent,
620 Compaq NetFlex and Olicom cards. Please read the file
621 <file:Documentation/networking/tlan.txt> for more details.
623 To compile this driver as a module, choose M here. The module
626 Please email feedback to <torben.mathiasen@compaq.com>.
629 tristate "Micrel KSZ8841/42 with generic bus interface"
630 depends on HAS_IOMEM && DMA_ENGINE
632 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
633 ethernet switch chip (managed, VLAN, QoS) from Micrel or
637 tristate "Micrel KS8851 SPI"
642 SPI driver for Micrel KS8851 SPI attached network chip.
645 tristate "Micrel KS8851 MLL"
649 This platform driver is for Micrel KS8851 Address/data bus
650 multiplexed network chip.
653 tristate "VIA Rhine support"
654 depends on NET_PCI && PCI
658 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
659 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
660 Ethernet functions can also be found integrated on South Bridges
663 To compile this driver as a module, choose M here. The module
664 will be called via-rhine.
666 config VIA_RHINE_MMIO
667 bool "Use MMIO instead of PIO"
670 This instructs the driver to use PCI shared memory (MMIO) instead of
671 programmed I/O ports (PIO). Enabling this gives an improvement in
672 processing time in parts of the driver.
677 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
678 depends on NET_ETHERNET && EXPERIMENTAL && AR7
681 TI AR7 CPMAC Ethernet support
684 bool "Pocket and portable adapters"
687 Cute little network (Ethernet) devices which attach to the parallel
688 port ("pocket adapters"), commonly used with laptops. If you have
689 one of those, say Y and read the Ethernet-HOWTO, available from
690 <http://www.tldp.org/docs.html#howto>.
692 If you want to plug a network (or some other) card into the PCMCIA
693 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
694 credit card size extension cards used by all modern laptops), you
695 need the pcmcia-cs package (location contained in the file
696 <file:Documentation/Changes>) and you can say N here.
698 Laptop users should read the Linux Laptop home page at
699 <http://www.linux-on-laptops.com/> or
700 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
702 Note that the answer to this question doesn't directly affect the
703 kernel: saying N will just cause the configurator to skip all
704 the questions about this class of network devices. If you say Y, you
705 will be asked for your specific device in the following questions.
708 tristate "SGI Seeq ethernet controller support"
709 depends on SGI_HAS_SEEQ
711 Say Y here if you have an Seeq based Ethernet network card. This is
712 used in many Silicon Graphics machines.
715 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
716 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
717 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
718 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
721 Say Y here if you want to use the built-in 10/100 Fast ethernet
722 controller on some Motorola ColdFire and Freescale i.MX processors.
725 tristate "MPC52xx FEC driver"
726 depends on PPC_MPC52xx && PPC_BESTCOMM
729 select PPC_BESTCOMM_FEC
731 This option enables support for the MPC5200's on-chip
732 Fast Ethernet Controller
733 If compiled as module, it will be called fec_mpc52xx.
735 config FEC_MPC52xx_MDIO
736 bool "MPC52xx FEC MDIO bus driver"
737 depends on FEC_MPC52xx
740 The MPC5200's FEC can connect to the Ethernet either with
741 an external MII PHY chip or 10 Mbps 7-wire interface
742 (Motorola? industry standard).
743 If your board uses an external PHY connected to FEC, enable this.
745 If compiled as module, it will be called fec_mpc52xx_phy.
747 config XILINX_EMACLITE
748 tristate "Xilinx 10/100 Ethernet Lite support"
749 depends on PPC32 || MICROBLAZE
752 This driver supports the 10/100 Ethernet Lite from Xilinx.
755 tristate "Lantiq SoC ETOP driver"
756 depends on SOC_TYPE_XWAY
758 Support for the MII0 inside the Lantiq SoC
761 source "drivers/net/fs_enet/Kconfig"
763 source "drivers/net/octeon/Kconfig"
771 menuconfig NETDEV_1000
772 bool "Ethernet (1000 Mbit)"
776 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
777 type of Local Area Network (LAN) in universities and companies.
779 Say Y here to get to see options for Gigabit Ethernet drivers.
780 This option alone does not add any kernel code.
781 Note that drivers supporting both 100 and 1000 MBit may be listed
782 under "Ethernet (10 or 100MBit)" instead.
784 If you say N, all options in this submenu will be skipped and disabled.
789 tristate "IP1000 Gigabit Ethernet support"
790 depends on PCI && EXPERIMENTAL
793 This driver supports IP1000 gigabit Ethernet cards.
795 To compile this driver as a module, choose M here: the module
796 will be called ipg. This is recommended.
799 tristate "Packet Engines Hamachi GNIC-II support"
803 If you have a Gigabit Ethernet card of this type, say Y and read
804 the Ethernet-HOWTO, available from
805 <http://www.tldp.org/docs.html#howto>.
807 To compile this driver as a module, choose M here. The module will be
811 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
812 depends on PCI && EXPERIMENTAL
815 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
816 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
817 used by the Beowulf Linux cluster project. See
818 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
819 information about this driver in particular and Beowulf in general.
821 To compile this driver as a module, choose M here: the module
822 will be called yellowfin. This is recommended.
825 tristate "SiS190/SiS191 gigabit ethernet support"
830 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
831 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
832 appear in lan on motherboard designs which are based on SiS 965
833 and SiS 966 south bridge.
835 To compile this driver as a module, choose M here: the module
836 will be called sis190. This is recommended.
839 tristate "Marvell Yukon Gigabit Ethernet support"
843 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
844 and related Gigabit Ethernet adapters. It is a new smaller driver
845 with better performance and more complete ethtool support.
847 It does not support the link failover and network management
848 features that "portable" vendor supplied sk98lin driver does.
850 This driver supports adapters based on the original Yukon chipset:
851 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
852 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
854 It does not support the newer Yukon2 chipset: a separate driver,
855 sky2, is provided for these adapters.
857 To compile this driver as a module, choose M here: the module
858 will be called skge. This is recommended.
861 bool "Debugging interface"
862 depends on SKGE && DEBUG_FS
864 This option adds the ability to dump driver state for debugging.
865 The file /sys/kernel/debug/skge/ethX displays the state of the internal
866 transmit and receive rings.
871 bool "Support for older SysKonnect Genesis boards"
874 This enables support for the older and uncommon SysKonnect Genesis
875 chips, which support MII via an external transceiver, instead of
876 an internal one. Disabling this option will save some memory
877 by making code smaller. If unsure say Y.
880 tristate "Marvell Yukon 2 support"
884 This driver supports Gigabit Ethernet adapters based on the
885 Marvell Yukon 2 chipset:
886 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
887 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
889 There is companion driver for the older Marvell Yukon and
890 SysKonnect Genesis based adapters: skge.
892 To compile this driver as a module, choose M here: the module
893 will be called sky2. This is recommended.
896 bool "Debugging interface"
897 depends on SKY2 && DEBUG_FS
899 This option adds the ability to dump driver state for debugging.
900 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
901 transmit and receive rings.
906 tristate "VIA Velocity support"
912 If you have a VIA "Velocity" based network card say Y here.
914 To compile this driver as a module, choose M here. The module
915 will be called via-velocity.
918 tristate "Spider Gigabit Ethernet driver"
919 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
923 This driver supports the Gigabit Ethernet chips present on the
924 Cell Processor-Based Blades from IBM.
927 tristate "Tundra TSI108 gigabit Ethernet support"
928 depends on TSI108_BRIDGE
930 This driver supports Tundra TSI108 gigabit Ethernet ports.
931 To compile this driver as a module, choose M here: the module
932 will be called tsi108_eth.
935 tristate "PS3 Gigabit Ethernet driver"
937 select PS3_SYS_MANAGER
939 This driver supports the network device on the PS3 game
940 console. This driver has built-in support for Ethernet.
942 To compile this driver as a module, choose M here: the
943 module will be called ps3_gelic.
945 config GELIC_WIRELESS
946 bool "PS3 Wireless support"
951 This option adds the support for the wireless feature of PS3.
952 If you have the wireless-less model of PS3 or have no plan to
953 use wireless feature, disabling this option saves memory. As
954 the driver automatically distinguishes the models, you can
955 safely enable this option even if you have a wireless-less model.
958 tristate "Freescale PQ MDIO"
962 This driver supports the MDIO bus used by the gianfar and UCC drivers.
965 tristate "Gianfar Ethernet"
971 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
972 and MPC86xx family of chips, and the FEC on the 8540.
975 tristate "Freescale QE Gigabit Ethernet"
976 depends on QUICC_ENGINE
980 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
981 which is available on some Freescale SOCs.
983 config UGETH_TX_ON_DEMAND
984 bool "Transmit on Demand support"
988 tristate "Marvell Discovery (643XX) and Orion ethernet support"
989 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
993 This driver supports the gigabit ethernet MACs in the
994 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
995 in the Marvell Orion ARM SoC family.
997 Some boards that use the Discovery chipset are the Momenco
998 Ocelot C and Jaguar ATX and Pegasos II.
1000 config XILINX_LL_TEMAC
1001 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1002 depends on PPC || MICROBLAZE
1005 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1006 core used in Xilinx Spartan and Virtex FPGAs
1009 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1014 This driver supports the PCI-Express gigabit ethernet adapters
1015 based on JMicron JMC250 chipset.
1017 To compile this driver as a module, choose M here. The module
1021 tristate "S6105 GMAC ethernet support"
1022 depends on XTENSA_VARIANT_S6000
1025 This driver supports the on chip ethernet device on the
1026 S6105 xtensa processor.
1028 To compile this driver as a module, choose M here. The module
1029 will be called s6gmac.
1032 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1036 This is a gigabit ethernet driver for EG20T PCH.
1037 EG20T PCH is the platform controller hub that is used in Intel's
1038 general embedded platform.
1039 EG20T PCH has Gigabit Ethernet interface.
1040 Using this interface, it is able to access system devices connected
1041 to Gigabit Ethernet.
1042 This driver enables Gigabit Ethernet function.
1044 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1045 Output Hub), ML7223.
1046 ML7223 IOH is for MP(Media Phone) use.
1047 ML7223 is companion chip for Intel Atom E6xx series.
1048 ML7223 is completely compatible for Intel EG20T PCH.
1053 # 10 Gigabit Ethernet
1056 menuconfig NETDEV_10000
1057 bool "Ethernet (10000 Mbit)"
1061 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1062 This option alone does not add any kernel code.
1064 If you say N, all options in this submenu will be skipped and disabled.
1074 endif # NETDEV_10000
1076 source "drivers/net/tokenring/Kconfig"
1078 source "drivers/net/wireless/Kconfig"
1080 source "drivers/net/wimax/Kconfig"
1082 source "drivers/net/usb/Kconfig"
1084 source "drivers/net/pcmcia/Kconfig"
1086 source "drivers/net/wan/Kconfig"
1088 source "drivers/atm/Kconfig"
1090 source "drivers/ieee802154/Kconfig"
1092 source "drivers/s390/net/Kconfig"
1094 source "drivers/net/caif/Kconfig"
1097 tristate "Tilera GBE/XGBE network driver support"
1102 This is a standard Linux network device driver for the
1103 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1105 To compile this driver as a module, choose M here: the module
1106 will be called tile_net.
1108 config XEN_NETDEV_FRONTEND
1109 tristate "Xen network device frontend driver"
1111 select XEN_XENBUS_FRONTEND
1114 This driver provides support for Xen paravirtual network
1115 devices exported by a Xen network driver domain (often
1118 The corresponding Linux backend driver is enabled by the
1119 CONFIG_XEN_NETDEV_BACKEND option.
1121 If you are compiling a kernel for use as Xen guest, you
1122 should say Y here. To compile this driver as a module, chose
1123 M here: the module will be called xen-netfront.
1125 config XEN_NETDEV_BACKEND
1126 tristate "Xen backend network device"
1127 depends on XEN_BACKEND
1129 This driver allows the kernel to act as a Xen network driver
1130 domain which exports paravirtual network devices to other
1131 Xen domains. These devices can be accessed by any operating
1132 system that implements a compatible front end.
1134 The corresponding Linux frontend driver is enabled by the
1135 CONFIG_XEN_NETDEV_FRONTEND configuration option.
1137 The backend driver presents a standard network device
1138 endpoint for each paravirtual network device to the driver
1139 domain network stack. These can then be bridged or routed
1140 etc in order to provide full network connectivity.
1142 If you are compiling a kernel to run in a Xen network driver
1143 domain (often this is domain 0) you should say Y here. To
1144 compile this driver as a module, chose M here: the module
1145 will be called xen-netback.
1148 tristate "RapidIO Ethernet over messaging driver support"
1151 config RIONET_TX_SIZE
1152 int "Number of outbound queue entries"
1156 config RIONET_RX_SIZE
1157 int "Number of inbound queue entries"
1162 tristate "FDDI driver support"
1163 depends on (PCI || EISA || TC)
1165 Fiber Distributed Data Interface is a high speed local area network
1166 design; essentially a replacement for high speed Ethernet. FDDI can
1167 run over copper or fiber. If you are connected to such a network and
1168 want a driver for the FDDI card in your computer, say Y here (and
1169 then also Y to the driver for your FDDI card, below). Most people
1173 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1174 depends on FDDI && (PCI || EISA || TC)
1176 This is support for the DIGITAL series of TURBOchannel (DEFTA),
1177 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1178 to a local FDDI network.
1180 To compile this driver as a module, choose M here: the module
1181 will be called defxx. If unsure, say N.
1185 prompt "Use MMIO instead of PIO" if PCI || EISA
1187 default n if PCI || EISA
1190 This instructs the driver to use EISA or PCI memory-mapped I/O
1191 (MMIO) as appropriate instead of programmed I/O ports (PIO).
1192 Enabling this gives an improvement in processing time in parts
1193 of the driver, but it may cause problems with EISA (DEFEA)
1194 adapters. TURBOchannel does not have the concept of I/O ports,
1195 so MMIO is always used for these (DEFTA) adapters.
1200 tristate "SysKonnect FDDI PCI support"
1201 depends on FDDI && PCI
1204 Say Y here if you have a SysKonnect FDDI PCI adapter.
1205 The following adapters are supported by this driver:
1206 - SK-5521 (SK-NET FDDI-UP)
1207 - SK-5522 (SK-NET FDDI-UP DAS)
1208 - SK-5541 (SK-NET FDDI-FP)
1209 - SK-5543 (SK-NET FDDI-LP)
1210 - SK-5544 (SK-NET FDDI-LP DAS)
1211 - SK-5821 (SK-NET FDDI-UP64)
1212 - SK-5822 (SK-NET FDDI-UP64 DAS)
1213 - SK-5841 (SK-NET FDDI-FP64)
1214 - SK-5843 (SK-NET FDDI-LP64)
1215 - SK-5844 (SK-NET FDDI-LP64 DAS)
1216 - Netelligent 100 FDDI DAS Fibre SC
1217 - Netelligent 100 FDDI SAS Fibre SC
1218 - Netelligent 100 FDDI DAS UTP
1219 - Netelligent 100 FDDI SAS UTP
1220 - Netelligent 100 FDDI SAS Fibre MIC
1222 Read <file:Documentation/networking/skfp.txt> for information about
1225 Questions concerning this driver can be addressed to:
1226 <linux@syskonnect.de>
1228 To compile this driver as a module, choose M here: the module
1229 will be called skfp. This is recommended.
1232 bool "HIPPI driver support (EXPERIMENTAL)"
1233 depends on EXPERIMENTAL && INET && PCI
1235 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1236 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1237 can run over copper (25m) or fiber (300m on multi-mode or 10km on
1238 single-mode). HIPPI networks are commonly used for clusters and to
1239 connect to super computers. If you are connected to a HIPPI network
1240 and have a HIPPI network card in your computer that you want to use
1241 under Linux, say Y here (you must also remember to enable the driver
1242 for your HIPPI card below). Most people will say N here.
1245 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1246 depends on HIPPI && PCI
1248 Say Y here if this is your PCI HIPPI network card.
1250 To compile this driver as a module, choose M here: the module
1251 will be called rrunner. If unsure, say N.
1253 config ROADRUNNER_LARGE_RINGS
1254 bool "Use large TX/RX rings (EXPERIMENTAL)"
1255 depends on ROADRUNNER
1257 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1258 of additional memory to allow for fastest operation, both for
1259 transmitting and receiving. This memory cannot be used by any other
1260 kernel code or by user space programs. Say Y here only if you have
1264 tristate "PLIP (parallel port) support"
1267 PLIP (Parallel Line Internet Protocol) is used to create a
1268 reasonably fast mini network consisting of two (or, rarely, more)
1269 local machines. A PLIP link from a Linux box is a popular means to
1270 install a Linux distribution on a machine which doesn't have a
1271 CD-ROM drive (a minimal system has to be transferred with floppies
1272 first). The kernels on both machines need to have this PLIP option
1273 enabled for this to work.
1275 The PLIP driver has two modes, mode 0 and mode 1. The parallel
1276 ports (the connectors at the computers with 25 holes) are connected
1277 with "null printer" or "Turbo Laplink" cables which can transmit 4
1278 bits at a time (mode 0) or with special PLIP cables, to be used on
1279 bidirectional parallel ports only, which can transmit 8 bits at a
1280 time (mode 1); you can find the wiring of these cables in
1281 <file:Documentation/networking/PLIP.txt>. The cables can be up to
1282 15m long. Mode 0 works also if one of the machines runs DOS/Windows
1283 and has some PLIP software installed, e.g. the Crynwr PLIP packet
1284 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1285 and winsock or NCSA's telnet.
1287 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1288 as the NET-3-HOWTO, both available from
1289 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
1290 protocol has been changed and this PLIP driver won't work together
1291 with the PLIP support in Linux versions 1.0.x. This option enlarges
1292 your kernel by about 8 KB.
1294 To compile this driver as a module, choose M here. The module
1295 will be called plip. If unsure, say Y or M, in case you buy
1299 tristate "PPP (point-to-point protocol) support"
1302 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
1303 the same purpose: sending Internet traffic over telephone (and other
1304 serial) lines. Ask your access provider if they support it, because
1305 otherwise you can't use it; most Internet access providers these
1306 days support PPP rather than SLIP.
1308 To use PPP, you need an additional program called pppd as described
1309 in the PPP-HOWTO, available at
1310 <http://www.tldp.org/docs.html#howto>. Make sure that you have
1311 the version of pppd recommended in <file:Documentation/Changes>.
1312 The PPP option enlarges your kernel by about 16 KB.
1314 There are actually two versions of PPP: the traditional PPP for
1315 asynchronous lines, such as regular analog phone lines, and
1316 synchronous PPP which can be used over digital ISDN lines for
1317 example. If you want to use PPP over phone lines or other
1318 asynchronous serial lines, you need to say Y (or M) here and also to
1319 the next option, "PPP support for async serial ports". For PPP over
1320 synchronous lines, you should say Y (or M) here and to "Support
1321 synchronous PPP", below.
1323 If you said Y to "Version information on all symbols" above, then
1324 you cannot compile the PPP driver into the kernel; you can then only
1325 compile it as a module. To compile this driver as a module, choose M
1326 here. The module will be called ppp_generic.
1328 config PPP_MULTILINK
1329 bool "PPP multilink support (EXPERIMENTAL)"
1330 depends on PPP && EXPERIMENTAL
1332 PPP multilink is a protocol (defined in RFC 1990) which allows you
1333 to combine several (logical or physical) lines into one logical PPP
1334 connection, so that you can utilize your full bandwidth.
1336 This has to be supported at the other end as well and you need a
1337 version of the pppd daemon which understands the multilink protocol.
1342 bool "PPP filtering"
1345 Say Y here if you want to be able to filter the packets passing over
1346 PPP interfaces. This allows you to control which packets count as
1347 activity (i.e. which packets will reset the idle timer or bring up
1348 a demand-dialed link) and which packets are to be dropped entirely.
1349 You need to say Y here if you wish to use the pass-filter and
1350 active-filter options to pppd.
1355 tristate "PPP support for async serial ports"
1359 Say Y (or M) here if you want to be able to use PPP over standard
1360 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
1361 a modem (not a synchronous or ISDN modem) to contact your ISP, you
1364 To compile this driver as a module, choose M here.
1369 tristate "PPP support for sync tty ports"
1372 Say Y (or M) here if you want to be able to use PPP over synchronous
1373 (HDLC) tty devices, such as the SyncLink adapter. These devices
1374 are often used for high-speed leased lines like T1/E1.
1376 To compile this driver as a module, choose M here.
1379 tristate "PPP Deflate compression"
1384 Support for the Deflate compression method for PPP, which uses the
1385 Deflate algorithm (the same algorithm that gzip uses) to compress
1386 each PPP packet before it is sent over the wire. The machine at the
1387 other end of the PPP link (usually your ISP) has to support the
1388 Deflate compression method as well for this to be useful. Even if
1389 they don't support it, it is safe to say Y here.
1391 To compile this driver as a module, choose M here.
1394 tristate "PPP BSD-Compress compression"
1397 Support for the BSD-Compress compression method for PPP, which uses
1398 the LZW compression method to compress each PPP packet before it is
1399 sent over the wire. The machine at the other end of the PPP link
1400 (usually your ISP) has to support the BSD-Compress compression
1401 method as well for this to be useful. Even if they don't support it,
1402 it is safe to say Y here.
1404 The PPP Deflate compression method ("PPP Deflate compression",
1405 above) is preferable to BSD-Compress, because it compresses better
1408 Note that the BSD compression code will always be compiled as a
1409 module; it is called bsd_comp and will show up in the directory
1410 modules once you have said "make modules". If unsure, say N.
1413 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1414 depends on PPP && EXPERIMENTAL
1420 Support for the MPPE Encryption protocol, as employed by the
1421 Microsoft Point-to-Point Tunneling Protocol.
1423 See http://pptpclient.sourceforge.net/ for information on
1424 configuring PPTP clients and servers to utilize this method.
1427 tristate "PPP over Ethernet (EXPERIMENTAL)"
1428 depends on EXPERIMENTAL && PPP
1430 Support for PPP over Ethernet.
1432 This driver requires the latest version of pppd from the CVS
1433 repository at cvs.samba.org. Alternatively, see the
1434 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1435 which contains instruction on how to use this driver (under
1436 the heading "Kernel mode PPPoE").
1439 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1440 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1442 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1444 This driver requires pppd plugin to work in client mode or
1445 modified pptpd (poptop) to work in server mode.
1446 See http://accel-pptp.sourceforge.net/ for information how to
1447 utilize this module.
1450 tristate "PPP over ATM"
1451 depends on ATM && PPP
1453 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1454 This implementation does not yet comply with section 8 of RFC2364,
1455 which can lead to bad results if the ATM peer loses state and
1456 changes its encapsulation unilaterally.
1459 tristate "PPP over L2TP (EXPERIMENTAL)"
1460 depends on EXPERIMENTAL && L2TP && PPP
1462 Support for PPP-over-L2TP socket family. L2TP is a protocol
1463 used by ISPs and enterprises to tunnel PPP traffic over UDP
1464 tunnels. L2TP is replacing PPTP for VPN uses.
1467 tristate "SLIP (serial line) support"
1469 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1470 connect to your Internet service provider or to connect to some
1471 other local Unix box or if you want to configure your Linux box as a
1472 Slip/CSlip server for other people to dial in. SLIP (Serial Line
1473 Internet Protocol) is a protocol used to send Internet traffic over
1474 serial connections such as telephone lines or null modem cables;
1475 nowadays, the protocol PPP is more commonly used for this same
1478 Normally, your access provider has to support SLIP in order for you
1479 to be able to use it, but there is now a SLIP emulator called SLiRP
1480 around (available from
1481 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1482 allows you to use SLIP over a regular dial up shell connection. If
1483 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1484 NET-3-HOWTO, available from
1485 <http://www.tldp.org/docs.html#howto>, explains how to
1486 configure SLIP. Note that you don't need this option if you just
1487 want to run term (term is a program which gives you almost full
1488 Internet connectivity if you have a regular dial up shell account on
1489 some Internet connected Unix computer. Read
1490 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1491 support will enlarge your kernel by about 4 KB. If unsure, say N.
1493 To compile this driver as a module, choose M here. The module
1494 will be called slip.
1496 config SLIP_COMPRESSED
1497 bool "CSLIP compressed headers"
1501 This protocol is faster than SLIP because it uses compression on the
1502 TCP/IP headers (not on the data itself), but it has to be supported
1503 on both ends. Ask your access provider if you are not sure and
1504 answer Y, just in case. You will still be able to use plain SLIP. If
1505 you plan to use SLiRP, the SLIP emulator (available from
1506 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1507 allows you to use SLIP over a regular dial up shell connection, you
1508 definitely want to say Y here. The NET-3-HOWTO, available from
1509 <http://www.tldp.org/docs.html#howto>, explains how to configure
1510 CSLIP. This won't enlarge your kernel.
1515 This option enables Van Jacobsen serial line header compression
1519 bool "Keepalive and linefill"
1522 Adds additional capabilities to the SLIP driver to support the
1523 RELCOM line fill and keepalive monitoring. Ideal on poor quality
1526 config SLIP_MODE_SLIP6
1527 bool "Six bit SLIP encapsulation"
1530 Just occasionally you may need to run IP over hostile serial
1531 networks that don't pass all control characters or are only seven
1532 bit. Saying Y here adds an extra mode you can use with SLIP:
1533 "slip6". In this mode, SLIP will only send normal ASCII symbols over
1534 the serial device. Naturally, this has to be supported at the other
1535 end of the link as well. It's good enough, for example, to run IP
1536 over the async ports of a Camtec JNT Pad. If unsure, say N.
1539 bool "Fibre Channel driver support"
1540 depends on SCSI && PCI
1542 Fibre Channel is a high speed serial protocol mainly used to connect
1543 large storage devices to the computer; it is compatible with and
1544 intended to replace SCSI.
1546 If you intend to use Fibre Channel, you need to have a Fibre channel
1547 adaptor card in your computer; say Y here and to the driver for your
1548 adaptor below. You also should have said Y to "SCSI support" and
1549 "SCSI generic support".
1552 tristate "Network console logging support"
1554 If you want to log kernel messages over the network, enable this.
1555 See <file:Documentation/networking/netconsole.txt> for details.
1557 config NETCONSOLE_DYNAMIC
1558 bool "Dynamic reconfiguration of logging targets"
1559 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1560 !(NETCONSOLE=y && CONFIGFS_FS=m)
1562 This option enables the ability to dynamically reconfigure target
1563 parameters (interface, IP addresses, port numbers, MAC addresses)
1564 at runtime through a userspace interface exported using configfs.
1565 See <file:Documentation/networking/netconsole.txt> for details.
1571 bool "Netpoll traffic trapping"
1575 config NET_POLL_CONTROLLER
1579 tristate "Virtio network driver (EXPERIMENTAL)"
1580 depends on EXPERIMENTAL && VIRTIO
1582 This is the virtual network driver for virtio. It can be used with
1583 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
1586 tristate "VMware VMXNET3 ethernet driver"
1587 depends on PCI && INET
1589 This driver supports VMware's vmxnet3 virtual ethernet NIC.
1590 To compile this driver as a module, choose M here: the
1591 module will be called vmxnet3.