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 "Korina (IDT RC32434) Ethernet support"
311 depends on NET_ETHERNET && MIKROTIK_RB532
313 If you have a Mikrotik RouterBoard 500 or IDT RC32434
314 based system say Y. Otherwise say N.
316 config MIPS_JAZZ_SONIC
317 tristate "MIPS JAZZ onboard SONIC Ethernet support"
320 This is the driver for the onboard card of MIPS Magnum 4000,
321 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
323 config XTENSA_XT2000_SONIC
324 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
325 depends on XTENSA_PLATFORM_XT2000
327 This is the driver for the onboard card of the Xtensa XT2000 board.
330 bool "SGI IOC3 Ethernet"
331 depends on PCI && SGI_IP27
335 If you have a network (Ethernet) card of this type, say Y and read
336 the Ethernet-HOWTO, available from
337 <http://www.tldp.org/docs.html#howto>.
340 tristate "MIPS simulator Network device"
343 The MIPSNET device is a simple Ethernet network device which is
344 emulated by the MIPS Simulator.
345 If you are not using a MIPSsim or are unsure, say N.
347 config SGI_O2MACE_ETH
348 tristate "SGI O2 MACE Fast Ethernet support"
349 depends on SGI_IP32=y
352 tristate "Renesas SuperH Ethernet support"
353 depends on SUPERH && \
354 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
355 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
356 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
362 Renesas SuperH Ethernet device driver.
363 This driver supporting CPUs are:
364 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
367 tristate "Blackfin on-chip MAC support"
368 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
372 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
374 This is the driver for Blackfin on-chip mac device. Say Y if you want it
375 compiled into the kernel. This driver is also available as a module
376 ( = code which can be inserted in and removed from the running kernel
377 whenever you want). The module will be called bfin_mac.
379 config BFIN_MAC_USE_L1
380 bool "Use L1 memory for rx/tx packets"
381 depends on BFIN_MAC && (BF527 || BF537)
384 To get maximum network performance, you should use L1 memory as rx/tx buffers.
385 Say N here if you want to reserve L1 memory for other uses.
387 config BFIN_TX_DESC_NUM
388 int "Number of transmit buffer packets"
390 range 6 10 if BFIN_MAC_USE_L1
394 Set the number of buffer packets used in driver.
396 config BFIN_RX_DESC_NUM
397 int "Number of receive buffer packets"
399 range 20 100 if BFIN_MAC_USE_L1
403 Set the number of buffer packets used in driver.
405 config BFIN_MAC_USE_HWSTAMP
406 bool "Use IEEE 1588 hwstamp"
407 depends on BFIN_MAC && BF518
410 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
413 tristate "Marvell pxa168 ethernet support"
414 depends on CPU_PXA168
417 This driver supports the pxa168 Ethernet ports.
419 To compile this driver as a module, choose M here. The module
420 will be called pxa168_eth.
423 tristate "NetX Ethernet support"
427 This is support for the Hilscher netX builtin Ethernet ports
429 To compile this driver as a module, choose M here. The module
430 will be called netx-eth.
432 config TI_DAVINCI_EMAC
433 tristate "TI DaVinci EMAC Support"
434 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
435 select TI_DAVINCI_MDIO
436 select TI_DAVINCI_CPDMA
439 This driver supports TI's DaVinci Ethernet .
441 To compile this driver as a module, choose M here: the module
442 will be called davinci_emac_driver. This is recommended.
444 config TI_DAVINCI_MDIO
445 tristate "TI DaVinci MDIO Support"
446 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
449 This driver supports TI's DaVinci MDIO module.
451 To compile this driver as a module, choose M here: the module
452 will be called davinci_mdio. This is recommended.
454 config TI_DAVINCI_CPDMA
455 tristate "TI DaVinci CPDMA Support"
456 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
458 This driver supports TI's DaVinci CPDMA dma engine.
460 To compile this driver as a module, choose M here: the module
461 will be called davinci_cpdma. This is recommended.
464 tristate "DM9000 support"
465 depends on ARM || BLACKFIN || MIPS
469 Support for DM9000 chipset.
471 To compile this driver as a module, choose M here. The module
472 will be called dm9000.
474 config DM9000_DEBUGLEVEL
475 int "DM9000 maximum debug level"
479 The maximum level of debugging code compiled into the DM9000
482 config DM9000_FORCE_SIMPLE_PHY_POLL
483 bool "Force simple NSR based PHY polling"
486 This configuration forces the DM9000 to use the NSR's LinkStatus
487 bit to determine if the link is up or down instead of the more
488 costly MII PHY reads. Note, this will not work if the chip is
489 operating with an external PHY.
492 tristate "ENC28J60 support"
493 depends on EXPERIMENTAL && SPI && NET_ETHERNET
496 Support for the Microchip EN28J60 ethernet chip.
498 To compile this driver as a module, choose M here. The module will be
501 config ENC28J60_WRITEVERIFY
502 bool "Enable write verify"
505 Enable the verify after the buffer write useful for debugging purpose.
509 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
510 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
516 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
519 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
524 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
527 tristate "Dave ethernet support (DNET)"
528 depends on NET_ETHERNET && HAS_IOMEM
531 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
532 Say Y to include support for the DNET chip.
534 To compile this driver as a module, choose M here: the module
537 source "drivers/net/tulip/Kconfig"
540 tristate "AT1700/1720 support (EXPERIMENTAL)"
541 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
544 If you have a network (Ethernet) card of this type, say Y and read
545 the Ethernet-HOWTO, available from
546 <http://www.tldp.org/docs.html#howto>.
548 To compile this driver as a module, choose M here. The module
549 will be called at1700.
552 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
553 depends on ISA || EISA || PCI
555 If you have a network (Ethernet) card of this type, say Y and read
556 the Ethernet-HOWTO, available from
557 <http://www.tldp.org/docs.html#howto>.
559 To compile this driver as a module, choose M here. The module
560 will be called hp100.
563 bool "Other ISA cards"
566 If your network (Ethernet) card hasn't been mentioned yet and its
567 bus system (that's the way the cards talks to the other components
568 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
569 Make sure you know the name of your card. Read the Ethernet-HOWTO,
570 available from <http://www.tldp.org/docs.html#howto>.
574 Note that the answer to this question doesn't directly affect the
575 kernel: saying N will just cause the configurator to skip all
576 the remaining ISA network card questions. If you say Y, you will be
577 asked for your specific card in the following questions.
580 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
584 This driver supports the DE203, DE204 and DE205 network (Ethernet)
585 cards. If this is for you, say Y and read
586 <file:Documentation/networking/ewrk3.txt> in the kernel source as
587 well as the Ethernet-HOWTO, available from
588 <http://www.tldp.org/docs.html#howto>.
590 To compile this driver as a module, choose M here. The module
591 will be called ewrk3.
594 tristate "ICL EtherTeam 16i/32 support"
597 If you have a network (Ethernet) card of this type, say Y and read
598 the Ethernet-HOWTO, available from
599 <http://www.tldp.org/docs.html#howto>.
601 To compile this driver as a module, choose M here. The module
602 will be called eth16i.
605 tristate "SEEQ8005 support (EXPERIMENTAL)"
606 depends on NET_ISA && EXPERIMENTAL
608 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
609 is for you, read the Ethernet-HOWTO, available from
610 <http://www.tldp.org/docs.html#howto>.
612 To compile this driver as a module, choose M here. The module
613 will be called seeq8005.
616 tristate "IBM LAN Adapter/A support"
619 This is a Micro Channel Ethernet adapter. You need to set
620 CONFIG_MCA to use this driver. It is both available as an in-kernel
621 driver and as a module.
623 To compile this driver as a module, choose M here. The only
624 currently supported card is the IBM LAN Adapter/A for Ethernet. It
625 will both support 16K and 32K memory windows, however a 32K window
626 gives a better security against packet losses. Usage of multiple
627 boards with this driver should be possible, but has not been tested
628 up to now due to lack of hardware.
631 tristate "IBM LAN Virtual Ethernet support"
632 depends on PPC_PSERIES
634 This driver supports virtual ethernet adapters on newer IBM iSeries
637 To compile this driver as a module, choose M here. The module will
640 source "drivers/net/ibm_newemac/Kconfig"
643 bool "EISA, VLB, PCI and on board controllers"
644 depends on ISA || EISA || PCI
646 This is another class of network cards which attach directly to the
647 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
648 available from <http://www.tldp.org/docs.html#howto>.
650 Note that the answer to this question doesn't directly affect the
651 kernel: saying N will just cause the configurator to skip all
652 the questions about this class of network cards. If you say Y, you
653 will be asked for your specific card in the following questions. If
654 you are unsure, say Y.
656 config ADAPTEC_STARFIRE
657 tristate "Adaptec Starfire/DuraLAN support"
658 depends on NET_PCI && PCI
662 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
663 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
664 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
667 To compile this driver as a module, choose M here: the module
668 will be called starfire. This is recommended.
671 tristate "Micrel KSZ8841/2 PCI"
672 depends on NET_PCI && PCI
676 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
678 To compile this driver as a module, choose M here. The module
679 will be called ksz884x.
682 tristate "nForce Ethernet support"
683 depends on NET_PCI && PCI
685 If you have a network (Ethernet) controller of this type, say Y and
686 read the Ethernet-HOWTO, available from
687 <http://www.tldp.org/docs.html#howto>.
689 To compile this driver as a module, choose M here. The module
690 will be called forcedeth.
693 tristate "CS89x0 support"
694 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
695 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
697 Support for CS89x0 chipset based Ethernet cards. If you have a
698 network (Ethernet) card of this type, say Y and read the
699 Ethernet-HOWTO, available from
700 <http://www.tldp.org/docs.html#howto> as well as
701 <file:Documentation/networking/cs89x0.txt>.
703 To compile this driver as a module, choose M here. The module
704 will be called cs89x0.
706 config CS89x0_NONISA_IRQ
708 depends on CS89x0 != n
709 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
712 tristate "TOSHIBA TC35815 Ethernet support"
713 depends on NET_PCI && PCI && MIPS
717 tristate "Myson MTD-8xx PCI Ethernet support"
718 depends on NET_PCI && PCI
722 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
723 cards. <http://www.myson.com.tw/>
726 tristate "National Semiconductor DP8381x series PCI Ethernet support"
727 depends on NET_PCI && PCI
730 This driver is for the National Semiconductor DP83810 series,
731 which is used in cards from PureData, NetGear, Linksys
732 and others, including the 83815 chip.
733 More specific information and updates are available from
734 <http://www.scyld.com/network/natsemi.html>.
737 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
738 depends on NET_PCI && PCI && EXPERIMENTAL
742 This is a driver for the Fast Ethernet PCI network cards based on
743 the RTL8139C+ chips. If you have one of those, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>.
747 To compile this driver as a module, choose M here: the module
748 will be called 8139cp. This is recommended.
751 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
752 depends on NET_PCI && PCI
756 This is a driver for the Fast Ethernet PCI network cards based on
757 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
758 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
760 To compile this driver as a module, choose M here: the module
761 will be called 8139too. This is recommended.
764 bool "Use PIO instead of MMIO"
768 This instructs the driver to use programmed I/O ports (PIO) instead
769 of PCI shared memory (MMIO). This can possibly solve some problems
770 in case your mainboard has memory consistency issues. If unsure,
773 config 8139TOO_TUNE_TWISTER
774 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
777 This implements a function which might come in handy in case you
778 are using low quality on long cabling. It is required for RealTek
779 RTL-8139 revision K boards, and totally unused otherwise. It tries
780 to match the transceiver to the cable characteristics. This is
781 experimental since hardly documented by the manufacturer.
785 bool "Support for older RTL-8129/8130 boards"
788 This enables support for the older and uncommon RTL-8129 and
789 RTL-8130 chips, which support MII via an external transceiver,
790 instead of an internal one. Disabling this option will save some
791 memory by making the code size smaller. If unsure, say Y.
793 config 8139_OLD_RX_RESET
794 bool "Use older RX-reset method"
797 The 8139too driver was recently updated to contain a more rapid
798 reset sequence, in the face of severe receive errors. This "new"
799 RX-reset method should be adequate for all boards. But if you
800 experience problems, you can enable this option to restore the
801 old RX-reset behavior. If unsure, say N.
804 tristate "RDC R6040 Fast Ethernet Adapter support"
805 depends on NET_PCI && PCI
810 This is a driver for the R6040 Fast Ethernet MACs found in the
811 the RDC R-321x System-on-chips.
813 To compile this driver as a module, choose M here: the module
814 will be called r6040. This is recommended.
817 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
818 depends on NET_PCI && PCI
822 This is a driver for the Fast Ethernet PCI network cards based on
823 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
824 SiS 630 and SiS 540 chipsets.
826 This driver also supports AMD 79C901 HomePNA so that you can use
827 your phone line as a network cable.
829 To compile this driver as a module, choose M here: the module
830 will be called sis900. This is recommended.
833 tristate "Sundance Alta support"
834 depends on NET_PCI && PCI
838 This driver is for the Sundance "Alta" chip.
839 More specific information and updates are available from
840 <http://www.scyld.com/network/sundance.html>.
843 bool "Use MMIO instead of PIO"
846 Enable memory-mapped I/O for interaction with Sundance NIC registers.
847 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
848 is known to solve bugs on certain chips.
853 tristate "TI ThunderLAN support"
854 depends on NET_PCI && (PCI || EISA)
856 If you have a PCI Ethernet network card based on the ThunderLAN chip
857 which is supported by this driver, say Y and read the
858 Ethernet-HOWTO, available from
859 <http://www.tldp.org/docs.html#howto>.
861 Devices currently supported by this driver are Compaq Netelligent,
862 Compaq NetFlex and Olicom cards. Please read the file
863 <file:Documentation/networking/tlan.txt> for more details.
865 To compile this driver as a module, choose M here. The module
868 Please email feedback to <torben.mathiasen@compaq.com>.
871 tristate "Micrel KSZ8841/42 with generic bus interface"
872 depends on HAS_IOMEM && DMA_ENGINE
874 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
875 ethernet switch chip (managed, VLAN, QoS) from Micrel or
879 tristate "Micrel KS8851 SPI"
884 SPI driver for Micrel KS8851 SPI attached network chip.
887 tristate "Micrel KS8851 MLL"
891 This platform driver is for Micrel KS8851 Address/data bus
892 multiplexed network chip.
895 tristate "VIA Rhine support"
896 depends on NET_PCI && PCI
900 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
901 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
902 Ethernet functions can also be found integrated on South Bridges
905 To compile this driver as a module, choose M here. The module
906 will be called via-rhine.
908 config VIA_RHINE_MMIO
909 bool "Use MMIO instead of PIO"
912 This instructs the driver to use PCI shared memory (MMIO) instead of
913 programmed I/O ports (PIO). Enabling this gives an improvement in
914 processing time in parts of the driver.
919 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
920 depends on NET_PCI && PCI && EXPERIMENTAL
923 This is a driver for the Fast Ethernet PCI network cards based on
924 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
925 have one of these, say Y here.
927 To compile this driver as a module, choose M here: the module
928 will be called sc92031. This is recommended.
931 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
932 depends on NET_ETHERNET && EXPERIMENTAL && AR7
935 TI AR7 CPMAC Ethernet support
938 bool "Pocket and portable adapters"
941 Cute little network (Ethernet) devices which attach to the parallel
942 port ("pocket adapters"), commonly used with laptops. If you have
943 one of those, say Y and read the Ethernet-HOWTO, available from
944 <http://www.tldp.org/docs.html#howto>.
946 If you want to plug a network (or some other) card into the PCMCIA
947 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
948 credit card size extension cards used by all modern laptops), you
949 need the pcmcia-cs package (location contained in the file
950 <file:Documentation/Changes>) and you can say N here.
952 Laptop users should read the Linux Laptop home page at
953 <http://www.linux-on-laptops.com/> or
954 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
956 Note that the answer to this question doesn't directly affect the
957 kernel: saying N will just cause the configurator to skip all
958 the questions about this class of network devices. If you say Y, you
959 will be asked for your specific device in the following questions.
962 tristate "AT-LAN-TEC/RealTek pocket adapter support"
963 depends on NET_POCKET && PARPORT && X86
966 This is a network (Ethernet) device which attaches to your parallel
967 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
968 available from <http://www.tldp.org/docs.html#howto>, if you
969 want to use this. If you intend to use this driver, you should have
970 said N to the "Parallel printer support", because the two drivers
971 don't like each other.
973 To compile this driver as a module, choose M here: the module
977 tristate "D-Link DE600 pocket adapter support"
978 depends on NET_POCKET && PARPORT
980 This is a network (Ethernet) device which attaches to your parallel
981 port. Read <file:Documentation/networking/DLINK.txt> as well as the
982 Ethernet-HOWTO, available from
983 <http://www.tldp.org/docs.html#howto>, if you want to use
984 this. It is possible to have several devices share a single parallel
985 port and it is safe to compile the corresponding drivers into the
988 To compile this driver as a module, choose M here: the module
989 will be called de600.
992 tristate "D-Link DE620 pocket adapter support"
993 depends on NET_POCKET && PARPORT
995 This is a network (Ethernet) device which attaches to your parallel
996 port. Read <file:Documentation/networking/DLINK.txt> as well as the
997 Ethernet-HOWTO, available from
998 <http://www.tldp.org/docs.html#howto>, if you want to use
999 this. It is possible to have several devices share a single parallel
1000 port and it is safe to compile the corresponding drivers into the
1003 To compile this driver as a module, choose M here: the module
1004 will be called de620.
1007 tristate "SGI Seeq ethernet controller support"
1008 depends on SGI_HAS_SEEQ
1010 Say Y here if you have an Seeq based Ethernet network card. This is
1011 used in many Silicon Graphics machines.
1014 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1015 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1016 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1017 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1020 Say Y here if you want to use the built-in 10/100 Fast ethernet
1021 controller on some Motorola ColdFire and Freescale i.MX processors.
1024 tristate "MPC52xx FEC driver"
1025 depends on PPC_MPC52xx && PPC_BESTCOMM
1028 select PPC_BESTCOMM_FEC
1030 This option enables support for the MPC5200's on-chip
1031 Fast Ethernet Controller
1032 If compiled as module, it will be called fec_mpc52xx.
1034 config FEC_MPC52xx_MDIO
1035 bool "MPC52xx FEC MDIO bus driver"
1036 depends on FEC_MPC52xx
1039 The MPC5200's FEC can connect to the Ethernet either with
1040 an external MII PHY chip or 10 Mbps 7-wire interface
1041 (Motorola? industry standard).
1042 If your board uses an external PHY connected to FEC, enable this.
1043 If not sure, enable.
1044 If compiled as module, it will be called fec_mpc52xx_phy.
1047 tristate "Atheros L2 Fast Ethernet support"
1052 This driver supports the Atheros L2 fast ethernet adapter.
1054 To compile this driver as a module, choose M here. The module
1055 will be called atl2.
1057 config XILINX_EMACLITE
1058 tristate "Xilinx 10/100 Ethernet Lite support"
1059 depends on PPC32 || MICROBLAZE
1062 This driver supports the 10/100 Ethernet Lite from Xilinx.
1065 tristate "Faraday FTMAC100 10/100 Ethernet support"
1069 This driver supports the FTMAC100 10/100 Ethernet controller
1070 from Faraday. It is used on Faraday A320, Andes AG101 and some
1071 other ARM/NDS32 SoC's.
1074 tristate "Lantiq SoC ETOP driver"
1075 depends on SOC_TYPE_XWAY
1077 Support for the MII0 inside the Lantiq SoC
1080 source "drivers/net/fs_enet/Kconfig"
1082 source "drivers/net/octeon/Kconfig"
1084 endif # NET_ETHERNET
1090 menuconfig NETDEV_1000
1091 bool "Ethernet (1000 Mbit)"
1095 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1096 type of Local Area Network (LAN) in universities and companies.
1098 Say Y here to get to see options for Gigabit Ethernet drivers.
1099 This option alone does not add any kernel code.
1100 Note that drivers supporting both 100 and 1000 MBit may be listed
1101 under "Ethernet (10 or 100MBit)" instead.
1103 If you say N, all options in this submenu will be skipped and disabled.
1108 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1112 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1114 D-Link DGE-550T Gigabit Ethernet Adapter.
1115 D-Link DL2000-based Gigabit Ethernet Adapter.
1116 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1118 To compile this driver as a module, choose M here: the
1119 module will be called dl2k.
1122 tristate "IP1000 Gigabit Ethernet support"
1123 depends on PCI && EXPERIMENTAL
1126 This driver supports IP1000 gigabit Ethernet cards.
1128 To compile this driver as a module, choose M here: the module
1129 will be called ipg. This is recommended.
1131 source "drivers/net/ixp2000/Kconfig"
1134 tristate "National Semiconductor DP83820 support"
1137 This is a driver for the National Semiconductor DP83820 series
1138 of gigabit ethernet MACs. Cards using this chipset include
1139 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1140 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1144 tristate "Packet Engines Hamachi GNIC-II support"
1148 If you have a Gigabit Ethernet card of this type, say Y and read
1149 the Ethernet-HOWTO, available from
1150 <http://www.tldp.org/docs.html#howto>.
1152 To compile this driver as a module, choose M here. The module will be
1156 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1157 depends on PCI && EXPERIMENTAL
1160 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1161 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1162 used by the Beowulf Linux cluster project. See
1163 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1164 information about this driver in particular and Beowulf in general.
1166 To compile this driver as a module, choose M here: the module
1167 will be called yellowfin. This is recommended.
1170 tristate "Realtek 8169 gigabit ethernet support"
1176 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1178 To compile this driver as a module, choose M here: the module
1179 will be called r8169. This is recommended.
1182 tristate "SiS190/SiS191 gigabit ethernet support"
1187 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1188 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1189 appear in lan on motherboard designs which are based on SiS 965
1190 and SiS 966 south bridge.
1192 To compile this driver as a module, choose M here: the module
1193 will be called sis190. This is recommended.
1196 tristate "Marvell Yukon Gigabit Ethernet support"
1200 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1201 and related Gigabit Ethernet adapters. It is a new smaller driver
1202 with better performance and more complete ethtool support.
1204 It does not support the link failover and network management
1205 features that "portable" vendor supplied sk98lin driver does.
1207 This driver supports adapters based on the original Yukon chipset:
1208 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
1209 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
1211 It does not support the newer Yukon2 chipset: a separate driver,
1212 sky2, is provided for these adapters.
1214 To compile this driver as a module, choose M here: the module
1215 will be called skge. This is recommended.
1218 bool "Debugging interface"
1219 depends on SKGE && DEBUG_FS
1221 This option adds the ability to dump driver state for debugging.
1222 The file /sys/kernel/debug/skge/ethX displays the state of the internal
1223 transmit and receive rings.
1228 bool "Support for older SysKonnect Genesis boards"
1231 This enables support for the older and uncommon SysKonnect Genesis
1232 chips, which support MII via an external transceiver, instead of
1233 an internal one. Disabling this option will save some memory
1234 by making code smaller. If unsure say Y.
1237 tristate "Marvell Yukon 2 support"
1241 This driver supports Gigabit Ethernet adapters based on the
1242 Marvell Yukon 2 chipset:
1243 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
1244 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
1246 There is companion driver for the older Marvell Yukon and
1247 SysKonnect Genesis based adapters: skge.
1249 To compile this driver as a module, choose M here: the module
1250 will be called sky2. This is recommended.
1253 bool "Debugging interface"
1254 depends on SKY2 && DEBUG_FS
1256 This option adds the ability to dump driver state for debugging.
1257 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
1258 transmit and receive rings.
1263 tristate "VIA Velocity support"
1269 If you have a VIA "Velocity" based network card say Y here.
1271 To compile this driver as a module, choose M here. The module
1272 will be called via-velocity.
1275 tristate "Spider Gigabit Ethernet driver"
1276 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
1279 This driver supports the Gigabit Ethernet chips present on the
1280 Cell Processor-Based Blades from IBM.
1283 tristate "Tundra TSI108 gigabit Ethernet support"
1284 depends on TSI108_BRIDGE
1286 This driver supports Tundra TSI108 gigabit Ethernet ports.
1287 To compile this driver as a module, choose M here: the module
1288 will be called tsi108_eth.
1291 tristate "PS3 Gigabit Ethernet driver"
1293 select PS3_SYS_MANAGER
1295 This driver supports the network device on the PS3 game
1296 console. This driver has built-in support for Ethernet.
1298 To compile this driver as a module, choose M here: the
1299 module will be called ps3_gelic.
1301 config GELIC_WIRELESS
1302 bool "PS3 Wireless support"
1304 depends on GELIC_NET
1307 This option adds the support for the wireless feature of PS3.
1308 If you have the wireless-less model of PS3 or have no plan to
1309 use wireless feature, disabling this option saves memory. As
1310 the driver automatically distinguishes the models, you can
1311 safely enable this option even if you have a wireless-less model.
1314 tristate "Freescale PQ MDIO"
1318 This driver supports the MDIO bus used by the gianfar and UCC drivers.
1321 tristate "Gianfar Ethernet"
1327 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
1328 and MPC86xx family of chips, and the FEC on the 8540.
1331 tristate "Freescale QE Gigabit Ethernet"
1332 depends on QUICC_ENGINE
1336 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
1337 which is available on some Freescale SOCs.
1339 config UGETH_TX_ON_DEMAND
1340 bool "Transmit on Demand support"
1344 tristate "Marvell Discovery (643XX) and Orion ethernet support"
1345 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
1349 This driver supports the gigabit ethernet MACs in the
1350 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
1351 in the Marvell Orion ARM SoC family.
1353 Some boards that use the Discovery chipset are the Momenco
1354 Ocelot C and Jaguar ATX and Pegasos II.
1356 config XILINX_LL_TEMAC
1357 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1358 depends on PPC || MICROBLAZE
1361 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1362 core used in Xilinx Spartan and Virtex FPGAs
1365 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
1370 This driver supports the Atheros/Attansic L1 gigabit ethernet
1373 To compile this driver as a module, choose M here. The module
1374 will be called atl1.
1377 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
1378 depends on PCI && EXPERIMENTAL
1382 This driver supports the Atheros L1E gigabit ethernet adapter.
1384 To compile this driver as a module, choose M here. The module
1385 will be called atl1e.
1388 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
1389 depends on PCI && EXPERIMENTAL
1393 This driver supports the Atheros L1C gigabit ethernet adapter.
1395 To compile this driver as a module, choose M here. The module
1396 will be called atl1c.
1399 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1404 This driver supports the PCI-Express gigabit ethernet adapters
1405 based on JMicron JMC250 chipset.
1407 To compile this driver as a module, choose M here. The module
1411 tristate "S6105 GMAC ethernet support"
1412 depends on XTENSA_VARIANT_S6000
1415 This driver supports the on chip ethernet device on the
1416 S6105 xtensa processor.
1418 To compile this driver as a module, choose M here. The module
1419 will be called s6gmac.
1421 source "drivers/net/stmmac/Kconfig"
1424 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1428 This is a gigabit ethernet driver for EG20T PCH.
1429 EG20T PCH is the platform controller hub that is used in Intel's
1430 general embedded platform.
1431 EG20T PCH has Gigabit Ethernet interface.
1432 Using this interface, it is able to access system devices connected
1433 to Gigabit Ethernet.
1434 This driver enables Gigabit Ethernet function.
1436 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1437 Output Hub), ML7223.
1438 ML7223 IOH is for MP(Media Phone) use.
1439 ML7223 is companion chip for Intel Atom E6xx series.
1440 ML7223 is completely compatible for Intel EG20T PCH.
1443 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
1447 This driver supports the FTGMAC100 Gigabit Ethernet controller
1448 from Faraday. It is used on Faraday A369, Andes AG102 and some
1449 other ARM/NDS32 SoC's.
1454 # 10 Gigabit Ethernet
1457 menuconfig NETDEV_10000
1458 bool "Ethernet (10000 Mbit)"
1462 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1463 This option alone does not add any kernel code.
1465 If you say N, all options in this submenu will be skipped and disabled.
1473 tristate "eHEA Ethernet support"
1474 depends on IBMEBUS && INET && SPARSEMEM
1477 This driver supports the IBM pSeries eHEA ethernet adapter.
1479 To compile the driver as a module, choose M here. The module
1480 will be called ehea.
1483 tristate "Cisco VIC Ethernet NIC Support"
1484 depends on PCI && INET
1486 This enables the support for the Cisco VIC Ethernet card.
1489 tristate "Exar Xframe 10Gb Ethernet Adapter"
1492 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
1494 More specific information on configuring the driver is in
1495 <file:Documentation/networking/s2io.txt>.
1497 To compile this driver as a module, choose M here. The module
1498 will be called s2io.
1501 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
1502 depends on PCI && INET
1504 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
1505 I/O Virtualized Server Adapter.
1507 More specific information on configuring the driver is in
1508 <file:Documentation/networking/vxge.txt>.
1510 To compile this driver as a module, choose M here. The module
1511 will be called vxge.
1513 config VXGE_DEBUG_TRACE_ALL
1514 bool "Enabling All Debug trace statments in driver"
1518 Say Y here if you want to enabling all the debug trace statements in
1519 the vxge driver. By default only few debug trace statements are
1523 tristate "Myricom Myri-10G Ethernet support"
1524 depends on PCI && INET
1529 This driver supports Myricom Myri-10G Dual Protocol interface in
1530 Ethernet mode. If the eeprom on your board is not recent enough,
1531 you will need a newer firmware image.
1532 You may get this image or more information, at:
1534 <http://www.myri.com/scs/download-Myri10GE.html>
1536 To compile this driver as a module, choose M here. The module
1537 will be called myri10ge.
1540 bool "Direct Cache Access (DCA) Support"
1542 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
1544 Say Y here if you want to use Direct Cache Access (DCA) in the
1545 driver. DCA is a method for warming the CPU cache before data
1546 is used, with the intent of lessening the impact of cache misses.
1549 tristate "PA Semi 1/10Gbit MAC"
1550 depends on PPC_PASEMI && PCI && INET
1554 This driver supports the on-chip 1/10Gbit Ethernet controller on
1555 PA Semi's PWRficient line of chips.
1558 tristate "Mellanox Technologies 10Gbit Ethernet support"
1559 depends on PCI && INET
1563 This driver supports Mellanox Technologies ConnectX Ethernet
1572 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
1573 depends on MLX4_CORE
1576 This option causes debugging code to be compiled into the
1577 mlx4_core driver. The output can be turned on via the
1578 debug_level module parameter (which can also be set after
1579 the driver is loaded through sysfs).
1582 tristate "Tehuti Networks 10G Ethernet"
1585 Tehuti Networks 10G Ethernet NIC
1588 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
1591 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
1593 To compile this driver as a module, choose M here: the module
1596 For general information and support, go to the Brocade support
1599 <http://support.brocade.com>
1601 source "drivers/net/benet/Kconfig"
1603 endif # NETDEV_10000
1605 source "drivers/net/tokenring/Kconfig"
1607 source "drivers/net/wireless/Kconfig"
1609 source "drivers/net/wimax/Kconfig"
1611 source "drivers/net/usb/Kconfig"
1613 source "drivers/net/pcmcia/Kconfig"
1615 source "drivers/net/wan/Kconfig"
1617 source "drivers/atm/Kconfig"
1619 source "drivers/ieee802154/Kconfig"
1621 source "drivers/s390/net/Kconfig"
1623 source "drivers/net/caif/Kconfig"
1626 tristate "Tilera GBE/XGBE network driver support"
1631 This is a standard Linux network device driver for the
1632 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1634 To compile this driver as a module, choose M here: the module
1635 will be called tile_net.
1637 config XEN_NETDEV_FRONTEND
1638 tristate "Xen network device frontend driver"
1640 select XEN_XENBUS_FRONTEND
1643 This driver provides support for Xen paravirtual network
1644 devices exported by a Xen network driver domain (often
1647 The corresponding Linux backend driver is enabled by the
1648 CONFIG_XEN_NETDEV_BACKEND option.
1650 If you are compiling a kernel for use as Xen guest, you
1651 should say Y here. To compile this driver as a module, chose
1652 M here: the module will be called xen-netfront.
1654 config XEN_NETDEV_BACKEND
1655 tristate "Xen backend network device"
1656 depends on XEN_BACKEND
1658 This driver allows the kernel to act as a Xen network driver
1659 domain which exports paravirtual network devices to other
1660 Xen domains. These devices can be accessed by any operating
1661 system that implements a compatible front end.
1663 The corresponding Linux frontend driver is enabled by the
1664 CONFIG_XEN_NETDEV_FRONTEND configuration option.
1666 The backend driver presents a standard network device
1667 endpoint for each paravirtual network device to the driver
1668 domain network stack. These can then be bridged or routed
1669 etc in order to provide full network connectivity.
1671 If you are compiling a kernel to run in a Xen network driver
1672 domain (often this is domain 0) you should say Y here. To
1673 compile this driver as a module, chose M here: the module
1674 will be called xen-netback.
1677 tristate "iSeries Virtual Ethernet driver support"
1678 depends on PPC_ISERIES
1681 tristate "RapidIO Ethernet over messaging driver support"
1684 config RIONET_TX_SIZE
1685 int "Number of outbound queue entries"
1689 config RIONET_RX_SIZE
1690 int "Number of inbound queue entries"
1695 tristate "FDDI driver support"
1696 depends on (PCI || EISA || TC)
1698 Fiber Distributed Data Interface is a high speed local area network
1699 design; essentially a replacement for high speed Ethernet. FDDI can
1700 run over copper or fiber. If you are connected to such a network and
1701 want a driver for the FDDI card in your computer, say Y here (and
1702 then also Y to the driver for your FDDI card, below). Most people
1706 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1707 depends on FDDI && (PCI || EISA || TC)
1709 This is support for the DIGITAL series of TURBOchannel (DEFTA),
1710 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1711 to a local FDDI network.
1713 To compile this driver as a module, choose M here: the module
1714 will be called defxx. If unsure, say N.
1718 prompt "Use MMIO instead of PIO" if PCI || EISA
1720 default n if PCI || EISA
1723 This instructs the driver to use EISA or PCI memory-mapped I/O
1724 (MMIO) as appropriate instead of programmed I/O ports (PIO).
1725 Enabling this gives an improvement in processing time in parts
1726 of the driver, but it may cause problems with EISA (DEFEA)
1727 adapters. TURBOchannel does not have the concept of I/O ports,
1728 so MMIO is always used for these (DEFTA) adapters.
1733 tristate "SysKonnect FDDI PCI support"
1734 depends on FDDI && PCI
1737 Say Y here if you have a SysKonnect FDDI PCI adapter.
1738 The following adapters are supported by this driver:
1739 - SK-5521 (SK-NET FDDI-UP)
1740 - SK-5522 (SK-NET FDDI-UP DAS)
1741 - SK-5541 (SK-NET FDDI-FP)
1742 - SK-5543 (SK-NET FDDI-LP)
1743 - SK-5544 (SK-NET FDDI-LP DAS)
1744 - SK-5821 (SK-NET FDDI-UP64)
1745 - SK-5822 (SK-NET FDDI-UP64 DAS)
1746 - SK-5841 (SK-NET FDDI-FP64)
1747 - SK-5843 (SK-NET FDDI-LP64)
1748 - SK-5844 (SK-NET FDDI-LP64 DAS)
1749 - Netelligent 100 FDDI DAS Fibre SC
1750 - Netelligent 100 FDDI SAS Fibre SC
1751 - Netelligent 100 FDDI DAS UTP
1752 - Netelligent 100 FDDI SAS UTP
1753 - Netelligent 100 FDDI SAS Fibre MIC
1755 Read <file:Documentation/networking/skfp.txt> for information about
1758 Questions concerning this driver can be addressed to:
1759 <linux@syskonnect.de>
1761 To compile this driver as a module, choose M here: the module
1762 will be called skfp. This is recommended.
1765 bool "HIPPI driver support (EXPERIMENTAL)"
1766 depends on EXPERIMENTAL && INET && PCI
1768 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1769 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1770 can run over copper (25m) or fiber (300m on multi-mode or 10km on
1771 single-mode). HIPPI networks are commonly used for clusters and to
1772 connect to super computers. If you are connected to a HIPPI network
1773 and have a HIPPI network card in your computer that you want to use
1774 under Linux, say Y here (you must also remember to enable the driver
1775 for your HIPPI card below). Most people will say N here.
1778 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1779 depends on HIPPI && PCI
1781 Say Y here if this is your PCI HIPPI network card.
1783 To compile this driver as a module, choose M here: the module
1784 will be called rrunner. If unsure, say N.
1786 config ROADRUNNER_LARGE_RINGS
1787 bool "Use large TX/RX rings (EXPERIMENTAL)"
1788 depends on ROADRUNNER
1790 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1791 of additional memory to allow for fastest operation, both for
1792 transmitting and receiving. This memory cannot be used by any other
1793 kernel code or by user space programs. Say Y here only if you have
1797 tristate "PLIP (parallel port) support"
1800 PLIP (Parallel Line Internet Protocol) is used to create a
1801 reasonably fast mini network consisting of two (or, rarely, more)
1802 local machines. A PLIP link from a Linux box is a popular means to
1803 install a Linux distribution on a machine which doesn't have a
1804 CD-ROM drive (a minimal system has to be transferred with floppies
1805 first). The kernels on both machines need to have this PLIP option
1806 enabled for this to work.
1808 The PLIP driver has two modes, mode 0 and mode 1. The parallel
1809 ports (the connectors at the computers with 25 holes) are connected
1810 with "null printer" or "Turbo Laplink" cables which can transmit 4
1811 bits at a time (mode 0) or with special PLIP cables, to be used on
1812 bidirectional parallel ports only, which can transmit 8 bits at a
1813 time (mode 1); you can find the wiring of these cables in
1814 <file:Documentation/networking/PLIP.txt>. The cables can be up to
1815 15m long. Mode 0 works also if one of the machines runs DOS/Windows
1816 and has some PLIP software installed, e.g. the Crynwr PLIP packet
1817 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1818 and winsock or NCSA's telnet.
1820 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1821 as the NET-3-HOWTO, both available from
1822 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
1823 protocol has been changed and this PLIP driver won't work together
1824 with the PLIP support in Linux versions 1.0.x. This option enlarges
1825 your kernel by about 8 KB.
1827 To compile this driver as a module, choose M here. The module
1828 will be called plip. If unsure, say Y or M, in case you buy
1832 tristate "PPP (point-to-point protocol) support"
1835 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
1836 the same purpose: sending Internet traffic over telephone (and other
1837 serial) lines. Ask your access provider if they support it, because
1838 otherwise you can't use it; most Internet access providers these
1839 days support PPP rather than SLIP.
1841 To use PPP, you need an additional program called pppd as described
1842 in the PPP-HOWTO, available at
1843 <http://www.tldp.org/docs.html#howto>. Make sure that you have
1844 the version of pppd recommended in <file:Documentation/Changes>.
1845 The PPP option enlarges your kernel by about 16 KB.
1847 There are actually two versions of PPP: the traditional PPP for
1848 asynchronous lines, such as regular analog phone lines, and
1849 synchronous PPP which can be used over digital ISDN lines for
1850 example. If you want to use PPP over phone lines or other
1851 asynchronous serial lines, you need to say Y (or M) here and also to
1852 the next option, "PPP support for async serial ports". For PPP over
1853 synchronous lines, you should say Y (or M) here and to "Support
1854 synchronous PPP", below.
1856 If you said Y to "Version information on all symbols" above, then
1857 you cannot compile the PPP driver into the kernel; you can then only
1858 compile it as a module. To compile this driver as a module, choose M
1859 here. The module will be called ppp_generic.
1861 config PPP_MULTILINK
1862 bool "PPP multilink support (EXPERIMENTAL)"
1863 depends on PPP && EXPERIMENTAL
1865 PPP multilink is a protocol (defined in RFC 1990) which allows you
1866 to combine several (logical or physical) lines into one logical PPP
1867 connection, so that you can utilize your full bandwidth.
1869 This has to be supported at the other end as well and you need a
1870 version of the pppd daemon which understands the multilink protocol.
1875 bool "PPP filtering"
1878 Say Y here if you want to be able to filter the packets passing over
1879 PPP interfaces. This allows you to control which packets count as
1880 activity (i.e. which packets will reset the idle timer or bring up
1881 a demand-dialed link) and which packets are to be dropped entirely.
1882 You need to say Y here if you wish to use the pass-filter and
1883 active-filter options to pppd.
1888 tristate "PPP support for async serial ports"
1892 Say Y (or M) here if you want to be able to use PPP over standard
1893 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
1894 a modem (not a synchronous or ISDN modem) to contact your ISP, you
1897 To compile this driver as a module, choose M here.
1902 tristate "PPP support for sync tty ports"
1905 Say Y (or M) here if you want to be able to use PPP over synchronous
1906 (HDLC) tty devices, such as the SyncLink adapter. These devices
1907 are often used for high-speed leased lines like T1/E1.
1909 To compile this driver as a module, choose M here.
1912 tristate "PPP Deflate compression"
1917 Support for the Deflate compression method for PPP, which uses the
1918 Deflate algorithm (the same algorithm that gzip uses) to compress
1919 each PPP packet before it is sent over the wire. The machine at the
1920 other end of the PPP link (usually your ISP) has to support the
1921 Deflate compression method as well for this to be useful. Even if
1922 they don't support it, it is safe to say Y here.
1924 To compile this driver as a module, choose M here.
1927 tristate "PPP BSD-Compress compression"
1930 Support for the BSD-Compress compression method for PPP, which uses
1931 the LZW compression method to compress each PPP packet before it is
1932 sent over the wire. The machine at the other end of the PPP link
1933 (usually your ISP) has to support the BSD-Compress compression
1934 method as well for this to be useful. Even if they don't support it,
1935 it is safe to say Y here.
1937 The PPP Deflate compression method ("PPP Deflate compression",
1938 above) is preferable to BSD-Compress, because it compresses better
1941 Note that the BSD compression code will always be compiled as a
1942 module; it is called bsd_comp and will show up in the directory
1943 modules once you have said "make modules". If unsure, say N.
1946 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1947 depends on PPP && EXPERIMENTAL
1953 Support for the MPPE Encryption protocol, as employed by the
1954 Microsoft Point-to-Point Tunneling Protocol.
1956 See http://pptpclient.sourceforge.net/ for information on
1957 configuring PPTP clients and servers to utilize this method.
1960 tristate "PPP over Ethernet (EXPERIMENTAL)"
1961 depends on EXPERIMENTAL && PPP
1963 Support for PPP over Ethernet.
1965 This driver requires the latest version of pppd from the CVS
1966 repository at cvs.samba.org. Alternatively, see the
1967 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1968 which contains instruction on how to use this driver (under
1969 the heading "Kernel mode PPPoE").
1972 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1973 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1975 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1977 This driver requires pppd plugin to work in client mode or
1978 modified pptpd (poptop) to work in server mode.
1979 See http://accel-pptp.sourceforge.net/ for information how to
1980 utilize this module.
1983 tristate "PPP over ATM"
1984 depends on ATM && PPP
1986 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1987 This implementation does not yet comply with section 8 of RFC2364,
1988 which can lead to bad results if the ATM peer loses state and
1989 changes its encapsulation unilaterally.
1992 tristate "PPP over L2TP (EXPERIMENTAL)"
1993 depends on EXPERIMENTAL && L2TP && PPP
1995 Support for PPP-over-L2TP socket family. L2TP is a protocol
1996 used by ISPs and enterprises to tunnel PPP traffic over UDP
1997 tunnels. L2TP is replacing PPTP for VPN uses.
2000 tristate "SLIP (serial line) support"
2002 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2003 connect to your Internet service provider or to connect to some
2004 other local Unix box or if you want to configure your Linux box as a
2005 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2006 Internet Protocol) is a protocol used to send Internet traffic over
2007 serial connections such as telephone lines or null modem cables;
2008 nowadays, the protocol PPP is more commonly used for this same
2011 Normally, your access provider has to support SLIP in order for you
2012 to be able to use it, but there is now a SLIP emulator called SLiRP
2013 around (available from
2014 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2015 allows you to use SLIP over a regular dial up shell connection. If
2016 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2017 NET-3-HOWTO, available from
2018 <http://www.tldp.org/docs.html#howto>, explains how to
2019 configure SLIP. Note that you don't need this option if you just
2020 want to run term (term is a program which gives you almost full
2021 Internet connectivity if you have a regular dial up shell account on
2022 some Internet connected Unix computer. Read
2023 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2024 support will enlarge your kernel by about 4 KB. If unsure, say N.
2026 To compile this driver as a module, choose M here. The module
2027 will be called slip.
2029 config SLIP_COMPRESSED
2030 bool "CSLIP compressed headers"
2034 This protocol is faster than SLIP because it uses compression on the
2035 TCP/IP headers (not on the data itself), but it has to be supported
2036 on both ends. Ask your access provider if you are not sure and
2037 answer Y, just in case. You will still be able to use plain SLIP. If
2038 you plan to use SLiRP, the SLIP emulator (available from
2039 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2040 allows you to use SLIP over a regular dial up shell connection, you
2041 definitely want to say Y here. The NET-3-HOWTO, available from
2042 <http://www.tldp.org/docs.html#howto>, explains how to configure
2043 CSLIP. This won't enlarge your kernel.
2048 This option enables Van Jacobsen serial line header compression
2052 bool "Keepalive and linefill"
2055 Adds additional capabilities to the SLIP driver to support the
2056 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2059 config SLIP_MODE_SLIP6
2060 bool "Six bit SLIP encapsulation"
2063 Just occasionally you may need to run IP over hostile serial
2064 networks that don't pass all control characters or are only seven
2065 bit. Saying Y here adds an extra mode you can use with SLIP:
2066 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2067 the serial device. Naturally, this has to be supported at the other
2068 end of the link as well. It's good enough, for example, to run IP
2069 over the async ports of a Camtec JNT Pad. If unsure, say N.
2072 bool "Fibre Channel driver support"
2073 depends on SCSI && PCI
2075 Fibre Channel is a high speed serial protocol mainly used to connect
2076 large storage devices to the computer; it is compatible with and
2077 intended to replace SCSI.
2079 If you intend to use Fibre Channel, you need to have a Fibre channel
2080 adaptor card in your computer; say Y here and to the driver for your
2081 adaptor below. You also should have said Y to "SCSI support" and
2082 "SCSI generic support".
2085 tristate "Network console logging support"
2087 If you want to log kernel messages over the network, enable this.
2088 See <file:Documentation/networking/netconsole.txt> for details.
2090 config NETCONSOLE_DYNAMIC
2091 bool "Dynamic reconfiguration of logging targets"
2092 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
2093 !(NETCONSOLE=y && CONFIGFS_FS=m)
2095 This option enables the ability to dynamically reconfigure target
2096 parameters (interface, IP addresses, port numbers, MAC addresses)
2097 at runtime through a userspace interface exported using configfs.
2098 See <file:Documentation/networking/netconsole.txt> for details.
2104 bool "Netpoll traffic trapping"
2108 config NET_POLL_CONTROLLER
2112 tristate "Virtio network driver (EXPERIMENTAL)"
2113 depends on EXPERIMENTAL && VIRTIO
2115 This is the virtual network driver for virtio. It can be used with
2116 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
2119 tristate "VMware VMXNET3 ethernet driver"
2120 depends on PCI && INET
2122 This driver supports VMware's vmxnet3 virtual ethernet NIC.
2123 To compile this driver as a module, choose M here: the
2124 module will be called vmxnet3.