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 "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
244 Support for NatSemi SONIC based Ethernet devices. This includes
245 the onboard Ethernet in many Quadras as well as some LC-PDS,
246 a few Nubus and all known Comm Slot Ethernet cards. If you have
247 one of these say Y and read the Ethernet-HOWTO, available from
248 <http://www.tldp.org/docs.html#howto>.
250 To compile this driver as a module, choose M here. This module will
254 tristate "Korina (IDT RC32434) Ethernet support"
255 depends on NET_ETHERNET && MIKROTIK_RB532
257 If you have a Mikrotik RouterBoard 500 or IDT RC32434
258 based system say Y. Otherwise say N.
260 config MIPS_JAZZ_SONIC
261 tristate "MIPS JAZZ onboard SONIC Ethernet support"
264 This is the driver for the onboard card of MIPS Magnum 4000,
265 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
267 config XTENSA_XT2000_SONIC
268 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
269 depends on XTENSA_PLATFORM_XT2000
271 This is the driver for the onboard card of the Xtensa XT2000 board.
274 bool "SGI IOC3 Ethernet"
275 depends on PCI && SGI_IP27
279 If you have a network (Ethernet) card of this type, say Y and read
280 the Ethernet-HOWTO, available from
281 <http://www.tldp.org/docs.html#howto>.
284 tristate "MIPS simulator Network device"
287 The MIPSNET device is a simple Ethernet network device which is
288 emulated by the MIPS Simulator.
289 If you are not using a MIPSsim or are unsure, say N.
291 config SGI_O2MACE_ETH
292 tristate "SGI O2 MACE Fast Ethernet support"
293 depends on SGI_IP32=y
296 tristate "Renesas SuperH Ethernet support"
297 depends on SUPERH && \
298 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
299 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
300 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
306 Renesas SuperH Ethernet device driver.
307 This driver supporting CPUs are:
308 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
311 tristate "Blackfin on-chip MAC support"
312 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
316 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
318 This is the driver for Blackfin on-chip mac device. Say Y if you want it
319 compiled into the kernel. This driver is also available as a module
320 ( = code which can be inserted in and removed from the running kernel
321 whenever you want). The module will be called bfin_mac.
323 config BFIN_MAC_USE_L1
324 bool "Use L1 memory for rx/tx packets"
325 depends on BFIN_MAC && (BF527 || BF537)
328 To get maximum network performance, you should use L1 memory as rx/tx buffers.
329 Say N here if you want to reserve L1 memory for other uses.
331 config BFIN_TX_DESC_NUM
332 int "Number of transmit buffer packets"
334 range 6 10 if BFIN_MAC_USE_L1
338 Set the number of buffer packets used in driver.
340 config BFIN_RX_DESC_NUM
341 int "Number of receive buffer packets"
343 range 20 100 if BFIN_MAC_USE_L1
347 Set the number of buffer packets used in driver.
349 config BFIN_MAC_USE_HWSTAMP
350 bool "Use IEEE 1588 hwstamp"
351 depends on BFIN_MAC && BF518
354 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
357 tristate "Marvell pxa168 ethernet support"
358 depends on CPU_PXA168
361 This driver supports the pxa168 Ethernet ports.
363 To compile this driver as a module, choose M here. The module
364 will be called pxa168_eth.
367 tristate "NetX Ethernet support"
371 This is support for the Hilscher netX builtin Ethernet ports
373 To compile this driver as a module, choose M here. The module
374 will be called netx-eth.
376 config TI_DAVINCI_EMAC
377 tristate "TI DaVinci EMAC Support"
378 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
379 select TI_DAVINCI_MDIO
380 select TI_DAVINCI_CPDMA
383 This driver supports TI's DaVinci Ethernet .
385 To compile this driver as a module, choose M here: the module
386 will be called davinci_emac_driver. This is recommended.
388 config TI_DAVINCI_MDIO
389 tristate "TI DaVinci MDIO Support"
390 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
393 This driver supports TI's DaVinci MDIO module.
395 To compile this driver as a module, choose M here: the module
396 will be called davinci_mdio. This is recommended.
398 config TI_DAVINCI_CPDMA
399 tristate "TI DaVinci CPDMA Support"
400 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
402 This driver supports TI's DaVinci CPDMA dma engine.
404 To compile this driver as a module, choose M here: the module
405 will be called davinci_cpdma. This is recommended.
408 tristate "DM9000 support"
409 depends on ARM || BLACKFIN || MIPS
413 Support for DM9000 chipset.
415 To compile this driver as a module, choose M here. The module
416 will be called dm9000.
418 config DM9000_DEBUGLEVEL
419 int "DM9000 maximum debug level"
423 The maximum level of debugging code compiled into the DM9000
426 config DM9000_FORCE_SIMPLE_PHY_POLL
427 bool "Force simple NSR based PHY polling"
430 This configuration forces the DM9000 to use the NSR's LinkStatus
431 bit to determine if the link is up or down instead of the more
432 costly MII PHY reads. Note, this will not work if the chip is
433 operating with an external PHY.
436 tristate "ENC28J60 support"
437 depends on EXPERIMENTAL && SPI && NET_ETHERNET
440 Support for the Microchip EN28J60 ethernet chip.
442 To compile this driver as a module, choose M here. The module will be
445 config ENC28J60_WRITEVERIFY
446 bool "Enable write verify"
449 Enable the verify after the buffer write useful for debugging purpose.
453 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
454 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
460 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
463 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
468 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
471 tristate "Dave ethernet support (DNET)"
472 depends on NET_ETHERNET && HAS_IOMEM
475 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
476 Say Y to include support for the DNET chip.
478 To compile this driver as a module, choose M here: the module
481 source "drivers/net/tulip/Kconfig"
484 tristate "AT1700/1720 support (EXPERIMENTAL)"
485 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
488 If you have a network (Ethernet) card of this type, say Y and read
489 the Ethernet-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>.
492 To compile this driver as a module, choose M here. The module
493 will be called at1700.
496 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
497 depends on ISA || EISA || PCI
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 hp100.
507 bool "Other ISA cards"
510 If your network (Ethernet) card hasn't been mentioned yet and its
511 bus system (that's the way the cards talks to the other components
512 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
513 Make sure you know the name of your card. Read the Ethernet-HOWTO,
514 available from <http://www.tldp.org/docs.html#howto>.
518 Note that the answer to this question doesn't directly affect the
519 kernel: saying N will just cause the configurator to skip all
520 the remaining ISA network card questions. If you say Y, you will be
521 asked for your specific card in the following questions.
524 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
528 This driver supports the DE203, DE204 and DE205 network (Ethernet)
529 cards. If this is for you, say Y and read
530 <file:Documentation/networking/ewrk3.txt> in the kernel source as
531 well as the Ethernet-HOWTO, available from
532 <http://www.tldp.org/docs.html#howto>.
534 To compile this driver as a module, choose M here. The module
535 will be called ewrk3.
538 tristate "ICL EtherTeam 16i/32 support"
541 If you have a network (Ethernet) card of this type, say Y and read
542 the Ethernet-HOWTO, available from
543 <http://www.tldp.org/docs.html#howto>.
545 To compile this driver as a module, choose M here. The module
546 will be called eth16i.
549 tristate "SEEQ8005 support (EXPERIMENTAL)"
550 depends on NET_ISA && EXPERIMENTAL
552 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
553 is for you, read the Ethernet-HOWTO, available from
554 <http://www.tldp.org/docs.html#howto>.
556 To compile this driver as a module, choose M here. The module
557 will be called seeq8005.
560 tristate "IBM LAN Adapter/A support"
563 This is a Micro Channel Ethernet adapter. You need to set
564 CONFIG_MCA to use this driver. It is both available as an in-kernel
565 driver and as a module.
567 To compile this driver as a module, choose M here. The only
568 currently supported card is the IBM LAN Adapter/A for Ethernet. It
569 will both support 16K and 32K memory windows, however a 32K window
570 gives a better security against packet losses. Usage of multiple
571 boards with this driver should be possible, but has not been tested
572 up to now due to lack of hardware.
575 bool "EISA, VLB, PCI and on board controllers"
576 depends on ISA || EISA || PCI
578 This is another class of network cards which attach directly to the
579 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
580 available from <http://www.tldp.org/docs.html#howto>.
582 Note that the answer to this question doesn't directly affect the
583 kernel: saying N will just cause the configurator to skip all
584 the questions about this class of network cards. If you say Y, you
585 will be asked for your specific card in the following questions. If
586 you are unsure, say Y.
588 config ADAPTEC_STARFIRE
589 tristate "Adaptec Starfire/DuraLAN support"
590 depends on NET_PCI && PCI
594 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
595 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
596 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
599 To compile this driver as a module, choose M here: the module
600 will be called starfire. This is recommended.
603 tristate "Micrel KSZ8841/2 PCI"
604 depends on NET_PCI && PCI
608 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
610 To compile this driver as a module, choose M here. The module
611 will be called ksz884x.
614 tristate "nForce Ethernet support"
615 depends on NET_PCI && PCI
617 If you have a network (Ethernet) controller of this type, say Y and
618 read the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 To compile this driver as a module, choose M here. The module
622 will be called forcedeth.
625 tristate "TOSHIBA TC35815 Ethernet support"
626 depends on NET_PCI && PCI && MIPS
630 tristate "Myson MTD-8xx PCI Ethernet support"
631 depends on NET_PCI && PCI
635 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
636 cards. <http://www.myson.com.tw/>
639 tristate "National Semiconductor DP8381x series PCI Ethernet support"
640 depends on NET_PCI && PCI
643 This driver is for the National Semiconductor DP83810 series,
644 which is used in cards from PureData, NetGear, Linksys
645 and others, including the 83815 chip.
646 More specific information and updates are available from
647 <http://www.scyld.com/network/natsemi.html>.
650 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
651 depends on NET_PCI && PCI && EXPERIMENTAL
655 This is a driver for the Fast Ethernet PCI network cards based on
656 the RTL8139C+ chips. If you have one of those, say Y and read
657 the Ethernet-HOWTO, available from
658 <http://www.tldp.org/docs.html#howto>.
660 To compile this driver as a module, choose M here: the module
661 will be called 8139cp. This is recommended.
664 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
665 depends on NET_PCI && PCI
669 This is a driver for the Fast Ethernet PCI network cards based on
670 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
671 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
673 To compile this driver as a module, choose M here: the module
674 will be called 8139too. This is recommended.
677 bool "Use PIO instead of MMIO"
681 This instructs the driver to use programmed I/O ports (PIO) instead
682 of PCI shared memory (MMIO). This can possibly solve some problems
683 in case your mainboard has memory consistency issues. If unsure,
686 config 8139TOO_TUNE_TWISTER
687 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
690 This implements a function which might come in handy in case you
691 are using low quality on long cabling. It is required for RealTek
692 RTL-8139 revision K boards, and totally unused otherwise. It tries
693 to match the transceiver to the cable characteristics. This is
694 experimental since hardly documented by the manufacturer.
698 bool "Support for older RTL-8129/8130 boards"
701 This enables support for the older and uncommon RTL-8129 and
702 RTL-8130 chips, which support MII via an external transceiver,
703 instead of an internal one. Disabling this option will save some
704 memory by making the code size smaller. If unsure, say Y.
706 config 8139_OLD_RX_RESET
707 bool "Use older RX-reset method"
710 The 8139too driver was recently updated to contain a more rapid
711 reset sequence, in the face of severe receive errors. This "new"
712 RX-reset method should be adequate for all boards. But if you
713 experience problems, you can enable this option to restore the
714 old RX-reset behavior. If unsure, say N.
717 tristate "RDC R6040 Fast Ethernet Adapter support"
718 depends on NET_PCI && PCI
723 This is a driver for the R6040 Fast Ethernet MACs found in the
724 the RDC R-321x System-on-chips.
726 To compile this driver as a module, choose M here: the module
727 will be called r6040. This is recommended.
730 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
731 depends on NET_PCI && PCI
735 This is a driver for the Fast Ethernet PCI network cards based on
736 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
737 SiS 630 and SiS 540 chipsets.
739 This driver also supports AMD 79C901 HomePNA so that you can use
740 your phone line as a network cable.
742 To compile this driver as a module, choose M here: the module
743 will be called sis900. This is recommended.
746 tristate "Sundance Alta support"
747 depends on NET_PCI && PCI
751 This driver is for the Sundance "Alta" chip.
752 More specific information and updates are available from
753 <http://www.scyld.com/network/sundance.html>.
756 bool "Use MMIO instead of PIO"
759 Enable memory-mapped I/O for interaction with Sundance NIC registers.
760 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
761 is known to solve bugs on certain chips.
766 tristate "TI ThunderLAN support"
767 depends on NET_PCI && (PCI || EISA)
769 If you have a PCI Ethernet network card based on the ThunderLAN chip
770 which is supported by this driver, say Y and read the
771 Ethernet-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>.
774 Devices currently supported by this driver are Compaq Netelligent,
775 Compaq NetFlex and Olicom cards. Please read the file
776 <file:Documentation/networking/tlan.txt> for more details.
778 To compile this driver as a module, choose M here. The module
781 Please email feedback to <torben.mathiasen@compaq.com>.
784 tristate "Micrel KSZ8841/42 with generic bus interface"
785 depends on HAS_IOMEM && DMA_ENGINE
787 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
788 ethernet switch chip (managed, VLAN, QoS) from Micrel or
792 tristate "Micrel KS8851 SPI"
797 SPI driver for Micrel KS8851 SPI attached network chip.
800 tristate "Micrel KS8851 MLL"
804 This platform driver is for Micrel KS8851 Address/data bus
805 multiplexed network chip.
808 tristate "VIA Rhine support"
809 depends on NET_PCI && PCI
813 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
814 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
815 Ethernet functions can also be found integrated on South Bridges
818 To compile this driver as a module, choose M here. The module
819 will be called via-rhine.
821 config VIA_RHINE_MMIO
822 bool "Use MMIO instead of PIO"
825 This instructs the driver to use PCI shared memory (MMIO) instead of
826 programmed I/O ports (PIO). Enabling this gives an improvement in
827 processing time in parts of the driver.
832 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
833 depends on NET_PCI && PCI && EXPERIMENTAL
836 This is a driver for the Fast Ethernet PCI network cards based on
837 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
838 have one of these, say Y here.
840 To compile this driver as a module, choose M here: the module
841 will be called sc92031. This is recommended.
844 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
845 depends on NET_ETHERNET && EXPERIMENTAL && AR7
848 TI AR7 CPMAC Ethernet support
851 bool "Pocket and portable adapters"
854 Cute little network (Ethernet) devices which attach to the parallel
855 port ("pocket adapters"), commonly used with laptops. If you have
856 one of those, say Y and read the Ethernet-HOWTO, available from
857 <http://www.tldp.org/docs.html#howto>.
859 If you want to plug a network (or some other) card into the PCMCIA
860 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
861 credit card size extension cards used by all modern laptops), you
862 need the pcmcia-cs package (location contained in the file
863 <file:Documentation/Changes>) and you can say N here.
865 Laptop users should read the Linux Laptop home page at
866 <http://www.linux-on-laptops.com/> or
867 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
869 Note that the answer to this question doesn't directly affect the
870 kernel: saying N will just cause the configurator to skip all
871 the questions about this class of network devices. If you say Y, you
872 will be asked for your specific device in the following questions.
875 tristate "AT-LAN-TEC/RealTek pocket adapter support"
876 depends on NET_POCKET && PARPORT && X86
879 This is a network (Ethernet) device which attaches to your parallel
880 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
881 available from <http://www.tldp.org/docs.html#howto>, if you
882 want to use this. If you intend to use this driver, you should have
883 said N to the "Parallel printer support", because the two drivers
884 don't like each other.
886 To compile this driver as a module, choose M here: the module
890 tristate "D-Link DE600 pocket adapter support"
891 depends on NET_POCKET && PARPORT
893 This is a network (Ethernet) device which attaches to your parallel
894 port. Read <file:Documentation/networking/DLINK.txt> as well as the
895 Ethernet-HOWTO, available from
896 <http://www.tldp.org/docs.html#howto>, if you want to use
897 this. It is possible to have several devices share a single parallel
898 port and it is safe to compile the corresponding drivers into the
901 To compile this driver as a module, choose M here: the module
902 will be called de600.
905 tristate "D-Link DE620 pocket adapter support"
906 depends on NET_POCKET && PARPORT
908 This is a network (Ethernet) device which attaches to your parallel
909 port. Read <file:Documentation/networking/DLINK.txt> as well as the
910 Ethernet-HOWTO, available from
911 <http://www.tldp.org/docs.html#howto>, if you want to use
912 this. It is possible to have several devices share a single parallel
913 port and it is safe to compile the corresponding drivers into the
916 To compile this driver as a module, choose M here: the module
917 will be called de620.
920 tristate "SGI Seeq ethernet controller support"
921 depends on SGI_HAS_SEEQ
923 Say Y here if you have an Seeq based Ethernet network card. This is
924 used in many Silicon Graphics machines.
927 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
928 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
929 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
930 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
933 Say Y here if you want to use the built-in 10/100 Fast ethernet
934 controller on some Motorola ColdFire and Freescale i.MX processors.
937 tristate "MPC52xx FEC driver"
938 depends on PPC_MPC52xx && PPC_BESTCOMM
941 select PPC_BESTCOMM_FEC
943 This option enables support for the MPC5200's on-chip
944 Fast Ethernet Controller
945 If compiled as module, it will be called fec_mpc52xx.
947 config FEC_MPC52xx_MDIO
948 bool "MPC52xx FEC MDIO bus driver"
949 depends on FEC_MPC52xx
952 The MPC5200's FEC can connect to the Ethernet either with
953 an external MII PHY chip or 10 Mbps 7-wire interface
954 (Motorola? industry standard).
955 If your board uses an external PHY connected to FEC, enable this.
957 If compiled as module, it will be called fec_mpc52xx_phy.
960 tristate "Atheros L2 Fast Ethernet support"
965 This driver supports the Atheros L2 fast ethernet adapter.
967 To compile this driver as a module, choose M here. The module
970 config XILINX_EMACLITE
971 tristate "Xilinx 10/100 Ethernet Lite support"
972 depends on PPC32 || MICROBLAZE
975 This driver supports the 10/100 Ethernet Lite from Xilinx.
978 tristate "Faraday FTMAC100 10/100 Ethernet support"
982 This driver supports the FTMAC100 10/100 Ethernet controller
983 from Faraday. It is used on Faraday A320, Andes AG101 and some
984 other ARM/NDS32 SoC's.
987 tristate "Lantiq SoC ETOP driver"
988 depends on SOC_TYPE_XWAY
990 Support for the MII0 inside the Lantiq SoC
993 source "drivers/net/fs_enet/Kconfig"
995 source "drivers/net/octeon/Kconfig"
1003 menuconfig NETDEV_1000
1004 bool "Ethernet (1000 Mbit)"
1008 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1009 type of Local Area Network (LAN) in universities and companies.
1011 Say Y here to get to see options for Gigabit Ethernet drivers.
1012 This option alone does not add any kernel code.
1013 Note that drivers supporting both 100 and 1000 MBit may be listed
1014 under "Ethernet (10 or 100MBit)" instead.
1016 If you say N, all options in this submenu will be skipped and disabled.
1021 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1025 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1027 D-Link DGE-550T Gigabit Ethernet Adapter.
1028 D-Link DL2000-based Gigabit Ethernet Adapter.
1029 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1031 To compile this driver as a module, choose M here: the
1032 module will be called dl2k.
1035 tristate "IP1000 Gigabit Ethernet support"
1036 depends on PCI && EXPERIMENTAL
1039 This driver supports IP1000 gigabit Ethernet cards.
1041 To compile this driver as a module, choose M here: the module
1042 will be called ipg. This is recommended.
1044 source "drivers/net/ixp2000/Kconfig"
1047 tristate "National Semiconductor DP83820 support"
1050 This is a driver for the National Semiconductor DP83820 series
1051 of gigabit ethernet MACs. Cards using this chipset include
1052 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1053 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1057 tristate "Packet Engines Hamachi GNIC-II support"
1061 If you have a Gigabit Ethernet card of this type, say Y and read
1062 the Ethernet-HOWTO, available from
1063 <http://www.tldp.org/docs.html#howto>.
1065 To compile this driver as a module, choose M here. The module will be
1069 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1070 depends on PCI && EXPERIMENTAL
1073 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1074 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1075 used by the Beowulf Linux cluster project. See
1076 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1077 information about this driver in particular and Beowulf in general.
1079 To compile this driver as a module, choose M here: the module
1080 will be called yellowfin. This is recommended.
1083 tristate "Realtek 8169 gigabit ethernet support"
1089 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1091 To compile this driver as a module, choose M here: the module
1092 will be called r8169. This is recommended.
1095 tristate "SiS190/SiS191 gigabit ethernet support"
1100 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1101 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1102 appear in lan on motherboard designs which are based on SiS 965
1103 and SiS 966 south bridge.
1105 To compile this driver as a module, choose M here: the module
1106 will be called sis190. This is recommended.
1109 tristate "Marvell Yukon Gigabit Ethernet support"
1113 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1114 and related Gigabit Ethernet adapters. It is a new smaller driver
1115 with better performance and more complete ethtool support.
1117 It does not support the link failover and network management
1118 features that "portable" vendor supplied sk98lin driver does.
1120 This driver supports adapters based on the original Yukon chipset:
1121 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
1122 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
1124 It does not support the newer Yukon2 chipset: a separate driver,
1125 sky2, is provided for these adapters.
1127 To compile this driver as a module, choose M here: the module
1128 will be called skge. This is recommended.
1131 bool "Debugging interface"
1132 depends on SKGE && DEBUG_FS
1134 This option adds the ability to dump driver state for debugging.
1135 The file /sys/kernel/debug/skge/ethX displays the state of the internal
1136 transmit and receive rings.
1141 bool "Support for older SysKonnect Genesis boards"
1144 This enables support for the older and uncommon SysKonnect Genesis
1145 chips, which support MII via an external transceiver, instead of
1146 an internal one. Disabling this option will save some memory
1147 by making code smaller. If unsure say Y.
1150 tristate "Marvell Yukon 2 support"
1154 This driver supports Gigabit Ethernet adapters based on the
1155 Marvell Yukon 2 chipset:
1156 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
1157 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
1159 There is companion driver for the older Marvell Yukon and
1160 SysKonnect Genesis based adapters: skge.
1162 To compile this driver as a module, choose M here: the module
1163 will be called sky2. This is recommended.
1166 bool "Debugging interface"
1167 depends on SKY2 && DEBUG_FS
1169 This option adds the ability to dump driver state for debugging.
1170 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
1171 transmit and receive rings.
1176 tristate "VIA Velocity support"
1182 If you have a VIA "Velocity" based network card say Y here.
1184 To compile this driver as a module, choose M here. The module
1185 will be called via-velocity.
1188 tristate "Spider Gigabit Ethernet driver"
1189 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
1192 This driver supports the Gigabit Ethernet chips present on the
1193 Cell Processor-Based Blades from IBM.
1196 tristate "Tundra TSI108 gigabit Ethernet support"
1197 depends on TSI108_BRIDGE
1199 This driver supports Tundra TSI108 gigabit Ethernet ports.
1200 To compile this driver as a module, choose M here: the module
1201 will be called tsi108_eth.
1204 tristate "PS3 Gigabit Ethernet driver"
1206 select PS3_SYS_MANAGER
1208 This driver supports the network device on the PS3 game
1209 console. This driver has built-in support for Ethernet.
1211 To compile this driver as a module, choose M here: the
1212 module will be called ps3_gelic.
1214 config GELIC_WIRELESS
1215 bool "PS3 Wireless support"
1217 depends on GELIC_NET
1220 This option adds the support for the wireless feature of PS3.
1221 If you have the wireless-less model of PS3 or have no plan to
1222 use wireless feature, disabling this option saves memory. As
1223 the driver automatically distinguishes the models, you can
1224 safely enable this option even if you have a wireless-less model.
1227 tristate "Freescale PQ MDIO"
1231 This driver supports the MDIO bus used by the gianfar and UCC drivers.
1234 tristate "Gianfar Ethernet"
1240 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
1241 and MPC86xx family of chips, and the FEC on the 8540.
1244 tristate "Freescale QE Gigabit Ethernet"
1245 depends on QUICC_ENGINE
1249 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
1250 which is available on some Freescale SOCs.
1252 config UGETH_TX_ON_DEMAND
1253 bool "Transmit on Demand support"
1257 tristate "Marvell Discovery (643XX) and Orion ethernet support"
1258 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
1262 This driver supports the gigabit ethernet MACs in the
1263 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
1264 in the Marvell Orion ARM SoC family.
1266 Some boards that use the Discovery chipset are the Momenco
1267 Ocelot C and Jaguar ATX and Pegasos II.
1269 config XILINX_LL_TEMAC
1270 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1271 depends on PPC || MICROBLAZE
1274 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1275 core used in Xilinx Spartan and Virtex FPGAs
1278 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
1283 This driver supports the Atheros/Attansic L1 gigabit ethernet
1286 To compile this driver as a module, choose M here. The module
1287 will be called atl1.
1290 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
1291 depends on PCI && EXPERIMENTAL
1295 This driver supports the Atheros L1E gigabit ethernet adapter.
1297 To compile this driver as a module, choose M here. The module
1298 will be called atl1e.
1301 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
1302 depends on PCI && EXPERIMENTAL
1306 This driver supports the Atheros L1C gigabit ethernet adapter.
1308 To compile this driver as a module, choose M here. The module
1309 will be called atl1c.
1312 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1317 This driver supports the PCI-Express gigabit ethernet adapters
1318 based on JMicron JMC250 chipset.
1320 To compile this driver as a module, choose M here. The module
1324 tristate "S6105 GMAC ethernet support"
1325 depends on XTENSA_VARIANT_S6000
1328 This driver supports the on chip ethernet device on the
1329 S6105 xtensa processor.
1331 To compile this driver as a module, choose M here. The module
1332 will be called s6gmac.
1335 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1339 This is a gigabit ethernet driver for EG20T PCH.
1340 EG20T PCH is the platform controller hub that is used in Intel's
1341 general embedded platform.
1342 EG20T PCH has Gigabit Ethernet interface.
1343 Using this interface, it is able to access system devices connected
1344 to Gigabit Ethernet.
1345 This driver enables Gigabit Ethernet function.
1347 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1348 Output Hub), ML7223.
1349 ML7223 IOH is for MP(Media Phone) use.
1350 ML7223 is companion chip for Intel Atom E6xx series.
1351 ML7223 is completely compatible for Intel EG20T PCH.
1354 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
1358 This driver supports the FTGMAC100 Gigabit Ethernet controller
1359 from Faraday. It is used on Faraday A369, Andes AG102 and some
1360 other ARM/NDS32 SoC's.
1365 # 10 Gigabit Ethernet
1368 menuconfig NETDEV_10000
1369 bool "Ethernet (10000 Mbit)"
1373 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1374 This option alone does not add any kernel code.
1376 If you say N, all options in this submenu will be skipped and disabled.
1383 endif # NETDEV_10000
1385 source "drivers/net/tokenring/Kconfig"
1387 source "drivers/net/wireless/Kconfig"
1389 source "drivers/net/wimax/Kconfig"
1391 source "drivers/net/usb/Kconfig"
1393 source "drivers/net/pcmcia/Kconfig"
1395 source "drivers/net/wan/Kconfig"
1397 source "drivers/atm/Kconfig"
1399 source "drivers/ieee802154/Kconfig"
1401 source "drivers/s390/net/Kconfig"
1403 source "drivers/net/caif/Kconfig"
1406 tristate "Tilera GBE/XGBE network driver support"
1411 This is a standard Linux network device driver for the
1412 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1414 To compile this driver as a module, choose M here: the module
1415 will be called tile_net.
1417 config XEN_NETDEV_FRONTEND
1418 tristate "Xen network device frontend driver"
1420 select XEN_XENBUS_FRONTEND
1423 This driver provides support for Xen paravirtual network
1424 devices exported by a Xen network driver domain (often
1427 The corresponding Linux backend driver is enabled by the
1428 CONFIG_XEN_NETDEV_BACKEND option.
1430 If you are compiling a kernel for use as Xen guest, you
1431 should say Y here. To compile this driver as a module, chose
1432 M here: the module will be called xen-netfront.
1434 config XEN_NETDEV_BACKEND
1435 tristate "Xen backend network device"
1436 depends on XEN_BACKEND
1438 This driver allows the kernel to act as a Xen network driver
1439 domain which exports paravirtual network devices to other
1440 Xen domains. These devices can be accessed by any operating
1441 system that implements a compatible front end.
1443 The corresponding Linux frontend driver is enabled by the
1444 CONFIG_XEN_NETDEV_FRONTEND configuration option.
1446 The backend driver presents a standard network device
1447 endpoint for each paravirtual network device to the driver
1448 domain network stack. These can then be bridged or routed
1449 etc in order to provide full network connectivity.
1451 If you are compiling a kernel to run in a Xen network driver
1452 domain (often this is domain 0) you should say Y here. To
1453 compile this driver as a module, chose M here: the module
1454 will be called xen-netback.
1457 tristate "RapidIO Ethernet over messaging driver support"
1460 config RIONET_TX_SIZE
1461 int "Number of outbound queue entries"
1465 config RIONET_RX_SIZE
1466 int "Number of inbound queue entries"
1471 tristate "FDDI driver support"
1472 depends on (PCI || EISA || TC)
1474 Fiber Distributed Data Interface is a high speed local area network
1475 design; essentially a replacement for high speed Ethernet. FDDI can
1476 run over copper or fiber. If you are connected to such a network and
1477 want a driver for the FDDI card in your computer, say Y here (and
1478 then also Y to the driver for your FDDI card, below). Most people
1482 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1483 depends on FDDI && (PCI || EISA || TC)
1485 This is support for the DIGITAL series of TURBOchannel (DEFTA),
1486 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1487 to a local FDDI network.
1489 To compile this driver as a module, choose M here: the module
1490 will be called defxx. If unsure, say N.
1494 prompt "Use MMIO instead of PIO" if PCI || EISA
1496 default n if PCI || EISA
1499 This instructs the driver to use EISA or PCI memory-mapped I/O
1500 (MMIO) as appropriate instead of programmed I/O ports (PIO).
1501 Enabling this gives an improvement in processing time in parts
1502 of the driver, but it may cause problems with EISA (DEFEA)
1503 adapters. TURBOchannel does not have the concept of I/O ports,
1504 so MMIO is always used for these (DEFTA) adapters.
1509 tristate "SysKonnect FDDI PCI support"
1510 depends on FDDI && PCI
1513 Say Y here if you have a SysKonnect FDDI PCI adapter.
1514 The following adapters are supported by this driver:
1515 - SK-5521 (SK-NET FDDI-UP)
1516 - SK-5522 (SK-NET FDDI-UP DAS)
1517 - SK-5541 (SK-NET FDDI-FP)
1518 - SK-5543 (SK-NET FDDI-LP)
1519 - SK-5544 (SK-NET FDDI-LP DAS)
1520 - SK-5821 (SK-NET FDDI-UP64)
1521 - SK-5822 (SK-NET FDDI-UP64 DAS)
1522 - SK-5841 (SK-NET FDDI-FP64)
1523 - SK-5843 (SK-NET FDDI-LP64)
1524 - SK-5844 (SK-NET FDDI-LP64 DAS)
1525 - Netelligent 100 FDDI DAS Fibre SC
1526 - Netelligent 100 FDDI SAS Fibre SC
1527 - Netelligent 100 FDDI DAS UTP
1528 - Netelligent 100 FDDI SAS UTP
1529 - Netelligent 100 FDDI SAS Fibre MIC
1531 Read <file:Documentation/networking/skfp.txt> for information about
1534 Questions concerning this driver can be addressed to:
1535 <linux@syskonnect.de>
1537 To compile this driver as a module, choose M here: the module
1538 will be called skfp. This is recommended.
1541 bool "HIPPI driver support (EXPERIMENTAL)"
1542 depends on EXPERIMENTAL && INET && PCI
1544 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1545 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1546 can run over copper (25m) or fiber (300m on multi-mode or 10km on
1547 single-mode). HIPPI networks are commonly used for clusters and to
1548 connect to super computers. If you are connected to a HIPPI network
1549 and have a HIPPI network card in your computer that you want to use
1550 under Linux, say Y here (you must also remember to enable the driver
1551 for your HIPPI card below). Most people will say N here.
1554 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1555 depends on HIPPI && PCI
1557 Say Y here if this is your PCI HIPPI network card.
1559 To compile this driver as a module, choose M here: the module
1560 will be called rrunner. If unsure, say N.
1562 config ROADRUNNER_LARGE_RINGS
1563 bool "Use large TX/RX rings (EXPERIMENTAL)"
1564 depends on ROADRUNNER
1566 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1567 of additional memory to allow for fastest operation, both for
1568 transmitting and receiving. This memory cannot be used by any other
1569 kernel code or by user space programs. Say Y here only if you have
1573 tristate "PLIP (parallel port) support"
1576 PLIP (Parallel Line Internet Protocol) is used to create a
1577 reasonably fast mini network consisting of two (or, rarely, more)
1578 local machines. A PLIP link from a Linux box is a popular means to
1579 install a Linux distribution on a machine which doesn't have a
1580 CD-ROM drive (a minimal system has to be transferred with floppies
1581 first). The kernels on both machines need to have this PLIP option
1582 enabled for this to work.
1584 The PLIP driver has two modes, mode 0 and mode 1. The parallel
1585 ports (the connectors at the computers with 25 holes) are connected
1586 with "null printer" or "Turbo Laplink" cables which can transmit 4
1587 bits at a time (mode 0) or with special PLIP cables, to be used on
1588 bidirectional parallel ports only, which can transmit 8 bits at a
1589 time (mode 1); you can find the wiring of these cables in
1590 <file:Documentation/networking/PLIP.txt>. The cables can be up to
1591 15m long. Mode 0 works also if one of the machines runs DOS/Windows
1592 and has some PLIP software installed, e.g. the Crynwr PLIP packet
1593 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1594 and winsock or NCSA's telnet.
1596 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1597 as the NET-3-HOWTO, both available from
1598 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
1599 protocol has been changed and this PLIP driver won't work together
1600 with the PLIP support in Linux versions 1.0.x. This option enlarges
1601 your kernel by about 8 KB.
1603 To compile this driver as a module, choose M here. The module
1604 will be called plip. If unsure, say Y or M, in case you buy
1608 tristate "PPP (point-to-point protocol) support"
1611 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
1612 the same purpose: sending Internet traffic over telephone (and other
1613 serial) lines. Ask your access provider if they support it, because
1614 otherwise you can't use it; most Internet access providers these
1615 days support PPP rather than SLIP.
1617 To use PPP, you need an additional program called pppd as described
1618 in the PPP-HOWTO, available at
1619 <http://www.tldp.org/docs.html#howto>. Make sure that you have
1620 the version of pppd recommended in <file:Documentation/Changes>.
1621 The PPP option enlarges your kernel by about 16 KB.
1623 There are actually two versions of PPP: the traditional PPP for
1624 asynchronous lines, such as regular analog phone lines, and
1625 synchronous PPP which can be used over digital ISDN lines for
1626 example. If you want to use PPP over phone lines or other
1627 asynchronous serial lines, you need to say Y (or M) here and also to
1628 the next option, "PPP support for async serial ports". For PPP over
1629 synchronous lines, you should say Y (or M) here and to "Support
1630 synchronous PPP", below.
1632 If you said Y to "Version information on all symbols" above, then
1633 you cannot compile the PPP driver into the kernel; you can then only
1634 compile it as a module. To compile this driver as a module, choose M
1635 here. The module will be called ppp_generic.
1637 config PPP_MULTILINK
1638 bool "PPP multilink support (EXPERIMENTAL)"
1639 depends on PPP && EXPERIMENTAL
1641 PPP multilink is a protocol (defined in RFC 1990) which allows you
1642 to combine several (logical or physical) lines into one logical PPP
1643 connection, so that you can utilize your full bandwidth.
1645 This has to be supported at the other end as well and you need a
1646 version of the pppd daemon which understands the multilink protocol.
1651 bool "PPP filtering"
1654 Say Y here if you want to be able to filter the packets passing over
1655 PPP interfaces. This allows you to control which packets count as
1656 activity (i.e. which packets will reset the idle timer or bring up
1657 a demand-dialed link) and which packets are to be dropped entirely.
1658 You need to say Y here if you wish to use the pass-filter and
1659 active-filter options to pppd.
1664 tristate "PPP support for async serial ports"
1668 Say Y (or M) here if you want to be able to use PPP over standard
1669 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
1670 a modem (not a synchronous or ISDN modem) to contact your ISP, you
1673 To compile this driver as a module, choose M here.
1678 tristate "PPP support for sync tty ports"
1681 Say Y (or M) here if you want to be able to use PPP over synchronous
1682 (HDLC) tty devices, such as the SyncLink adapter. These devices
1683 are often used for high-speed leased lines like T1/E1.
1685 To compile this driver as a module, choose M here.
1688 tristate "PPP Deflate compression"
1693 Support for the Deflate compression method for PPP, which uses the
1694 Deflate algorithm (the same algorithm that gzip uses) to compress
1695 each PPP packet before it is sent over the wire. The machine at the
1696 other end of the PPP link (usually your ISP) has to support the
1697 Deflate compression method as well for this to be useful. Even if
1698 they don't support it, it is safe to say Y here.
1700 To compile this driver as a module, choose M here.
1703 tristate "PPP BSD-Compress compression"
1706 Support for the BSD-Compress compression method for PPP, which uses
1707 the LZW compression method to compress each PPP packet before it is
1708 sent over the wire. The machine at the other end of the PPP link
1709 (usually your ISP) has to support the BSD-Compress compression
1710 method as well for this to be useful. Even if they don't support it,
1711 it is safe to say Y here.
1713 The PPP Deflate compression method ("PPP Deflate compression",
1714 above) is preferable to BSD-Compress, because it compresses better
1717 Note that the BSD compression code will always be compiled as a
1718 module; it is called bsd_comp and will show up in the directory
1719 modules once you have said "make modules". If unsure, say N.
1722 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1723 depends on PPP && EXPERIMENTAL
1729 Support for the MPPE Encryption protocol, as employed by the
1730 Microsoft Point-to-Point Tunneling Protocol.
1732 See http://pptpclient.sourceforge.net/ for information on
1733 configuring PPTP clients and servers to utilize this method.
1736 tristate "PPP over Ethernet (EXPERIMENTAL)"
1737 depends on EXPERIMENTAL && PPP
1739 Support for PPP over Ethernet.
1741 This driver requires the latest version of pppd from the CVS
1742 repository at cvs.samba.org. Alternatively, see the
1743 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1744 which contains instruction on how to use this driver (under
1745 the heading "Kernel mode PPPoE").
1748 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1749 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1751 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1753 This driver requires pppd plugin to work in client mode or
1754 modified pptpd (poptop) to work in server mode.
1755 See http://accel-pptp.sourceforge.net/ for information how to
1756 utilize this module.
1759 tristate "PPP over ATM"
1760 depends on ATM && PPP
1762 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1763 This implementation does not yet comply with section 8 of RFC2364,
1764 which can lead to bad results if the ATM peer loses state and
1765 changes its encapsulation unilaterally.
1768 tristate "PPP over L2TP (EXPERIMENTAL)"
1769 depends on EXPERIMENTAL && L2TP && PPP
1771 Support for PPP-over-L2TP socket family. L2TP is a protocol
1772 used by ISPs and enterprises to tunnel PPP traffic over UDP
1773 tunnels. L2TP is replacing PPTP for VPN uses.
1776 tristate "SLIP (serial line) support"
1778 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1779 connect to your Internet service provider or to connect to some
1780 other local Unix box or if you want to configure your Linux box as a
1781 Slip/CSlip server for other people to dial in. SLIP (Serial Line
1782 Internet Protocol) is a protocol used to send Internet traffic over
1783 serial connections such as telephone lines or null modem cables;
1784 nowadays, the protocol PPP is more commonly used for this same
1787 Normally, your access provider has to support SLIP in order for you
1788 to be able to use it, but there is now a SLIP emulator called SLiRP
1789 around (available from
1790 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1791 allows you to use SLIP over a regular dial up shell connection. If
1792 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1793 NET-3-HOWTO, available from
1794 <http://www.tldp.org/docs.html#howto>, explains how to
1795 configure SLIP. Note that you don't need this option if you just
1796 want to run term (term is a program which gives you almost full
1797 Internet connectivity if you have a regular dial up shell account on
1798 some Internet connected Unix computer. Read
1799 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1800 support will enlarge your kernel by about 4 KB. If unsure, say N.
1802 To compile this driver as a module, choose M here. The module
1803 will be called slip.
1805 config SLIP_COMPRESSED
1806 bool "CSLIP compressed headers"
1810 This protocol is faster than SLIP because it uses compression on the
1811 TCP/IP headers (not on the data itself), but it has to be supported
1812 on both ends. Ask your access provider if you are not sure and
1813 answer Y, just in case. You will still be able to use plain SLIP. If
1814 you plan to use SLiRP, the SLIP emulator (available from
1815 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1816 allows you to use SLIP over a regular dial up shell connection, you
1817 definitely want to say Y here. The NET-3-HOWTO, available from
1818 <http://www.tldp.org/docs.html#howto>, explains how to configure
1819 CSLIP. This won't enlarge your kernel.
1824 This option enables Van Jacobsen serial line header compression
1828 bool "Keepalive and linefill"
1831 Adds additional capabilities to the SLIP driver to support the
1832 RELCOM line fill and keepalive monitoring. Ideal on poor quality
1835 config SLIP_MODE_SLIP6
1836 bool "Six bit SLIP encapsulation"
1839 Just occasionally you may need to run IP over hostile serial
1840 networks that don't pass all control characters or are only seven
1841 bit. Saying Y here adds an extra mode you can use with SLIP:
1842 "slip6". In this mode, SLIP will only send normal ASCII symbols over
1843 the serial device. Naturally, this has to be supported at the other
1844 end of the link as well. It's good enough, for example, to run IP
1845 over the async ports of a Camtec JNT Pad. If unsure, say N.
1848 bool "Fibre Channel driver support"
1849 depends on SCSI && PCI
1851 Fibre Channel is a high speed serial protocol mainly used to connect
1852 large storage devices to the computer; it is compatible with and
1853 intended to replace SCSI.
1855 If you intend to use Fibre Channel, you need to have a Fibre channel
1856 adaptor card in your computer; say Y here and to the driver for your
1857 adaptor below. You also should have said Y to "SCSI support" and
1858 "SCSI generic support".
1861 tristate "Network console logging support"
1863 If you want to log kernel messages over the network, enable this.
1864 See <file:Documentation/networking/netconsole.txt> for details.
1866 config NETCONSOLE_DYNAMIC
1867 bool "Dynamic reconfiguration of logging targets"
1868 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1869 !(NETCONSOLE=y && CONFIGFS_FS=m)
1871 This option enables the ability to dynamically reconfigure target
1872 parameters (interface, IP addresses, port numbers, MAC addresses)
1873 at runtime through a userspace interface exported using configfs.
1874 See <file:Documentation/networking/netconsole.txt> for details.
1880 bool "Netpoll traffic trapping"
1884 config NET_POLL_CONTROLLER
1888 tristate "Virtio network driver (EXPERIMENTAL)"
1889 depends on EXPERIMENTAL && VIRTIO
1891 This is the virtual network driver for virtio. It can be used with
1892 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
1895 tristate "VMware VMXNET3 ethernet driver"
1896 depends on PCI && INET
1898 This driver supports VMware's vmxnet3 virtual ethernet NIC.
1899 To compile this driver as a module, choose M here: the
1900 module will be called vmxnet3.