2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 menuconfig NET_ETHERNET
199 bool "Ethernet (10 or 100Mbit)"
202 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
203 type of Local Area Network (LAN) in universities and companies.
205 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
206 coaxial cable, linking computers in a chain), 10BASE-T or twisted
207 pair (10 Mbps over twisted pair cable, linking computers to central
208 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
209 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
210 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
211 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
212 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
213 Ethernet (1 Gbps over optical fiber or short copper links).
215 If your Linux machine will be connected to an Ethernet and you have
216 an Ethernet network interface card (NIC) installed in your computer,
217 say Y here and read the Ethernet-HOWTO, available from
218 <http://www.tldp.org/docs.html#howto>. You will then also have
219 to say Y to the driver for your particular NIC.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about Ethernet network cards. If unsure, say N.
228 tristate "Atmel MACB support"
229 depends on HAVE_NET_MACB
232 The Atmel MACB ethernet interface is found on many AT32 and AT91
233 parts. Say Y to include support for the MACB chip.
235 To compile this driver as a module, choose M here: the module
238 source "drivers/net/arm/Kconfig"
241 tristate "MACE (Power Mac ethernet) support"
242 depends on PPC_PMAC && PPC32
245 Power Macintoshes and clones with Ethernet built-in on the
246 motherboard will usually use a MACE (Medium Access Control for
247 Ethernet) interface. Say Y to include support for the MACE chip.
249 To compile this driver as a module, choose M here: the module
252 config MACE_AAUI_PORT
253 bool "Use AAUI port instead of TP by default"
256 Some Apple machines (notably the Apple Network Server) which use the
257 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
258 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
259 Y here if you have such a machine. If unsure, say N.
260 The driver will default to AAUI on ANS anyway, and if you use it as
261 a module, you can provide the port_aaui=0|1 to force the driver.
264 tristate "BMAC (G3 ethernet) support"
265 depends on PPC_PMAC && PPC32
268 Say Y for support of BMAC Ethernet interfaces. These are used on G3
271 To compile this driver as a module, choose M here: the module
275 tristate "Macintosh CS89x0 based ethernet cards"
278 Support for CS89x0 chipset based Ethernet cards. If you have a
279 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
280 read the Ethernet-HOWTO, available from
281 <http://www.tldp.org/docs.html#howto>.
283 To compile this driver as a module, choose M here. This module will
287 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
290 Support for NatSemi SONIC based Ethernet devices. This includes
291 the onboard Ethernet in many Quadras as well as some LC-PDS,
292 a few Nubus and all known Comm Slot Ethernet cards. If you have
293 one of these say Y and read the Ethernet-HOWTO, available from
294 <http://www.tldp.org/docs.html#howto>.
296 To compile this driver as a module, choose M here. This module will
300 bool "Macintosh (AV) onboard MACE ethernet"
304 Support for the onboard AMD 79C940 MACE Ethernet controller used in
305 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
306 say Y and read the Ethernet-HOWTO, available from
307 <http://www.tldp.org/docs.html#howto>.
310 tristate "MVME16x Ethernet support"
313 This is the driver for the Ethernet interface on the Motorola
314 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
315 driver for this chip in your kernel.
316 To compile this driver as a module, choose M here.
319 tristate "BVME6000 Ethernet support"
322 This is the driver for the Ethernet interface on BVME4000 and
323 BVME6000 VME boards. Say Y here to include the driver for this chip
325 To compile this driver as a module, choose M here.
328 bool "Sun3 on-board Intel 82586 support"
331 This driver enables support for the on-board Intel 82586 based
332 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
333 that this driver does not support 82586-based adapters on additional
337 tristate "Lasi ethernet"
340 Say Y here to support the builtin Intel 82596 ethernet controller
341 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
344 tristate "SNI RM ethernet"
345 depends on NET_ETHERNET && SNI_RM
347 Say Y here to support the on-board Intel 82596 ethernet controller
348 built into SNI RM machines.
351 tristate "Korina (IDT RC32434) Ethernet support"
352 depends on NET_ETHERNET && MIKROTIK_RB532
354 If you have a Mikrotik RouterBoard 500 or IDT RC32434
355 based system say Y. Otherwise say N.
357 config MIPS_JAZZ_SONIC
358 tristate "MIPS JAZZ onboard SONIC Ethernet support"
361 This is the driver for the onboard card of MIPS Magnum 4000,
362 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
364 config XTENSA_XT2000_SONIC
365 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
366 depends on XTENSA_PLATFORM_XT2000
368 This is the driver for the onboard card of the Xtensa XT2000 board.
371 bool "SGI IOC3 Ethernet"
372 depends on PCI && SGI_IP27
376 If you have a network (Ethernet) card of this type, say Y and read
377 the Ethernet-HOWTO, available from
378 <http://www.tldp.org/docs.html#howto>.
381 tristate "MIPS simulator Network device"
384 The MIPSNET device is a simple Ethernet network device which is
385 emulated by the MIPS Simulator.
386 If you are not using a MIPSsim or are unsure, say N.
388 config SGI_O2MACE_ETH
389 tristate "SGI O2 MACE Fast Ethernet support"
390 depends on SGI_IP32=y
393 tristate "Renesas SuperH Ethernet support"
394 depends on SUPERH && \
395 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
396 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
397 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
403 Renesas SuperH Ethernet device driver.
404 This driver supporting CPUs are:
405 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
408 tristate "Sun Happy Meal 10/100baseT support"
409 depends on SBUS || PCI
412 This driver supports the "hme" interface present on most Ultra
413 systems and as an option on older Sbus systems. This driver supports
414 both PCI and Sbus devices. This driver also supports the "qfe" quad
415 100baseT device available in both PCI and Sbus configurations.
417 To compile this driver as a module, choose M here: the module
418 will be called sunhme.
421 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
422 depends on SBUS && EXPERIMENTAL
425 This driver supports the "be" interface available as an Sbus option.
426 This is Sun's older 100baseT Ethernet device.
428 To compile this driver as a module, choose M here: the module
429 will be called sunbmac.
432 tristate "Sun QuadEthernet support"
436 This driver supports the "qe" 10baseT Ethernet device, available as
437 an Sbus option. Note that this is not the same as Quad FastEthernet
438 "qfe" which is supported by the Happy Meal driver instead.
440 To compile this driver as a module, choose M here: the module
441 will be called sunqe.
444 tristate "Sun GEM support"
448 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
449 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
452 tristate "Sun Cassini support"
456 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
457 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
460 tristate "Sun Virtual Network support"
463 Support for virtual network devices under Sun Logical Domains.
466 tristate "3c503 \"EtherLink II\" support"
470 If you have a network (Ethernet) card of this type, say Y and read
471 the Ethernet-HOWTO, available from
472 <http://www.tldp.org/docs.html#howto>.
474 To compile this driver as a module, choose M here. The module
475 will be called 3c503.
478 tristate "3c505 \"EtherLink Plus\" support"
479 depends on ISA && ISA_DMA_API
481 Information about this network (Ethernet) card can be found in
482 <file:Documentation/networking/3c505.txt>. If you have a card of
483 this type, say Y and read the Ethernet-HOWTO, available from
484 <http://www.tldp.org/docs.html#howto>.
486 To compile this driver as a module, choose M here. The module
487 will be called 3c505.
490 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
491 depends on ISA && EXPERIMENTAL
493 If you have a network (Ethernet) card of this type, say Y and read
494 the Ethernet-HOWTO, available from
495 <http://www.tldp.org/docs.html#howto>.
497 To compile this driver as a module, choose M here. The module
498 will be called 3c507.
501 tristate "3c523 \"EtherLink/MC\" support"
502 depends on MCA_LEGACY
504 If you have a network (Ethernet) card of this type, say Y and read
505 the Ethernet-HOWTO, available from
506 <http://www.tldp.org/docs.html#howto>.
508 To compile this driver as a module, choose M here. The module
509 will be called 3c523.
512 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
513 depends on MCA && MCA_LEGACY
515 If you have a network (Ethernet) card of this type, say Y and read
516 the Ethernet-HOWTO, available from
517 <http://www.tldp.org/docs.html#howto>.
519 To compile this driver as a module, choose M here. The module
520 will be called 3c527.
523 tristate "Blackfin on-chip MAC support"
524 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
528 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
530 This is the driver for Blackfin on-chip mac device. Say Y if you want it
531 compiled into the kernel. This driver is also available as a module
532 ( = code which can be inserted in and removed from the running kernel
533 whenever you want). The module will be called bfin_mac.
535 config BFIN_MAC_USE_L1
536 bool "Use L1 memory for rx/tx packets"
537 depends on BFIN_MAC && (BF527 || BF537)
540 To get maximum network performance, you should use L1 memory as rx/tx buffers.
541 Say N here if you want to reserve L1 memory for other uses.
543 config BFIN_TX_DESC_NUM
544 int "Number of transmit buffer packets"
546 range 6 10 if BFIN_MAC_USE_L1
550 Set the number of buffer packets used in driver.
552 config BFIN_RX_DESC_NUM
553 int "Number of receive buffer packets"
555 range 20 100 if BFIN_MAC_USE_L1
559 Set the number of buffer packets used in driver.
561 config BFIN_MAC_USE_HWSTAMP
562 bool "Use IEEE 1588 hwstamp"
563 depends on BFIN_MAC && BF518
566 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
569 tristate "SMC 9194 support"
570 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
573 This is support for the SMC9xxx based Ethernet cards. Choose this
574 option if you have a DELL laptop with the docking station, or
575 another SMC9192/9194 based chipset. Say Y if you want it compiled
576 into the kernel, and read the file
577 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
578 available from <http://www.tldp.org/docs.html#howto>.
580 To compile this driver as a module, choose M here. The module
581 will be called smc9194.
584 tristate "SMC 91C9x/91C1xxx support"
587 depends on ARM || M32R || SUPERH || \
588 MIPS || BLACKFIN || MN10300 || COLDFIRE
590 This is a driver for SMC's 91x series of Ethernet chipsets,
591 including the SMC91C94 and the SMC91C111. Say Y if you want it
592 compiled into the kernel, and read the file
593 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
594 available from <http://www.tldp.org/docs.html#howto>.
596 This driver is also available as a module ( = code which can be
597 inserted in and removed from the running kernel whenever you want).
598 The module will be called smc91x. If you want to compile it as a
599 module, say M here and read <file:Documentation/kbuild/modules.txt>.
602 tristate "Marvell pxa168 ethernet support"
603 depends on CPU_PXA168
606 This driver supports the pxa168 Ethernet ports.
608 To compile this driver as a module, choose M here. The module
609 will be called pxa168_eth.
612 tristate "NetX Ethernet support"
616 This is support for the Hilscher netX builtin Ethernet ports
618 To compile this driver as a module, choose M here. The module
619 will be called netx-eth.
621 config TI_DAVINCI_EMAC
622 tristate "TI DaVinci EMAC Support"
623 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
624 select TI_DAVINCI_MDIO
625 select TI_DAVINCI_CPDMA
628 This driver supports TI's DaVinci Ethernet .
630 To compile this driver as a module, choose M here: the module
631 will be called davinci_emac_driver. This is recommended.
633 config TI_DAVINCI_MDIO
634 tristate "TI DaVinci MDIO Support"
635 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
638 This driver supports TI's DaVinci MDIO module.
640 To compile this driver as a module, choose M here: the module
641 will be called davinci_mdio. This is recommended.
643 config TI_DAVINCI_CPDMA
644 tristate "TI DaVinci CPDMA Support"
645 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
647 This driver supports TI's DaVinci CPDMA dma engine.
649 To compile this driver as a module, choose M here: the module
650 will be called davinci_cpdma. This is recommended.
653 tristate "DM9000 support"
654 depends on ARM || BLACKFIN || MIPS
658 Support for DM9000 chipset.
660 To compile this driver as a module, choose M here. The module
661 will be called dm9000.
663 config DM9000_DEBUGLEVEL
664 int "DM9000 maximum debug level"
668 The maximum level of debugging code compiled into the DM9000
671 config DM9000_FORCE_SIMPLE_PHY_POLL
672 bool "Force simple NSR based PHY polling"
675 This configuration forces the DM9000 to use the NSR's LinkStatus
676 bit to determine if the link is up or down instead of the more
677 costly MII PHY reads. Note, this will not work if the chip is
678 operating with an external PHY.
681 tristate "ENC28J60 support"
682 depends on EXPERIMENTAL && SPI && NET_ETHERNET
685 Support for the Microchip EN28J60 ethernet chip.
687 To compile this driver as a module, choose M here. The module will be
690 config ENC28J60_WRITEVERIFY
691 bool "Enable write verify"
694 Enable the verify after the buffer write useful for debugging purpose.
698 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
699 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
705 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
708 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
713 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
716 tristate "SMSC LAN911[5678] support"
719 depends on ARM || SUPERH || MN10300
721 This is a driver for SMSC's LAN911x series of Ethernet chipsets
722 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
723 Say Y if you want it compiled into the kernel,
724 and read the Ethernet-HOWTO, available from
725 <http://www.tldp.org/docs.html#howto>.
727 This driver is also available as a module. The module will be
728 called smc911x. If you want to compile it as a module, say M
729 here and read <file:Documentation/kbuild/modules.txt>
732 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
733 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
738 Say Y here if you want support for SMSC LAN911x and LAN921x families
739 of ethernet controllers.
741 To compile this driver as a module, choose M here and read
742 <file:Documentation/networking/net-modules.txt>. The module
743 will be called smsc911x.
745 config SMSC911X_ARCH_HOOKS
749 If the arch enables this, it allows the arch to implement various
750 hooks for more comprehensive interrupt control and also to override
751 the source of the MAC address.
753 config NET_VENDOR_RACAL
754 bool "Racal-Interlan (Micom) NI cards"
757 If you have a network (Ethernet) card belonging to this class, such
758 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
759 available from <http://www.tldp.org/docs.html#howto>.
761 Note that the answer to this question doesn't directly affect the
762 kernel: saying N will just cause the configurator to skip all
763 the questions about NI cards. If you say Y, you will be asked for
764 your specific card in the following questions.
767 tristate "NI5010 support (EXPERIMENTAL)"
768 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
770 If you have a network (Ethernet) card of this type, say Y and read
771 the Ethernet-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>. Note that this is still
775 To compile this driver as a module, choose M here. The module
776 will be called ni5010.
779 tristate "NI5210 support"
780 depends on NET_VENDOR_RACAL && ISA
782 If you have a network (Ethernet) card of this type, say Y and read
783 the Ethernet-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>.
786 To compile this driver as a module, choose M here. The module
790 tristate "Dave ethernet support (DNET)"
791 depends on NET_ETHERNET && HAS_IOMEM
794 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
795 Say Y to include support for the DNET chip.
797 To compile this driver as a module, choose M here: the module
800 source "drivers/net/tulip/Kconfig"
803 tristate "AT1700/1720 support (EXPERIMENTAL)"
804 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
807 If you have a network (Ethernet) card of this type, say Y and read
808 the Ethernet-HOWTO, available from
809 <http://www.tldp.org/docs.html#howto>.
811 To compile this driver as a module, choose M here. The module
812 will be called at1700.
815 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
816 depends on ISA || EISA || PCI
818 If you have a network (Ethernet) card of this type, say Y and read
819 the Ethernet-HOWTO, available from
820 <http://www.tldp.org/docs.html#howto>.
822 To compile this driver as a module, choose M here. The module
823 will be called hp100.
826 bool "Other ISA cards"
829 If your network (Ethernet) card hasn't been mentioned yet and its
830 bus system (that's the way the cards talks to the other components
831 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
832 Make sure you know the name of your card. Read the Ethernet-HOWTO,
833 available from <http://www.tldp.org/docs.html#howto>.
837 Note that the answer to this question doesn't directly affect the
838 kernel: saying N will just cause the configurator to skip all
839 the remaining ISA network card questions. If you say Y, you will be
840 asked for your specific card in the following questions.
843 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
847 This driver supports the DE203, DE204 and DE205 network (Ethernet)
848 cards. If this is for you, say Y and read
849 <file:Documentation/networking/ewrk3.txt> in the kernel source as
850 well as the Ethernet-HOWTO, available from
851 <http://www.tldp.org/docs.html#howto>.
853 To compile this driver as a module, choose M here. The module
854 will be called ewrk3.
857 tristate "EtherExpress 16 support"
860 If you have an EtherExpress16 network (Ethernet) card, say Y and
861 read the Ethernet-HOWTO, available from
862 <http://www.tldp.org/docs.html#howto>. Note that the Intel
863 EtherExpress16 card used to be regarded as a very poor choice
864 because the driver was very unreliable. We now have a new driver
865 that should do better.
867 To compile this driver as a module, choose M here. The module
868 will be called eexpress.
871 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
874 If you have a network (Ethernet) card of this type, say Y. This
875 driver supports Intel i82595{FX,TX} based boards. Note however
876 that the EtherExpress PRO/100 Ethernet card has its own separate
877 driver. Please read the Ethernet-HOWTO, available from
878 <http://www.tldp.org/docs.html#howto>.
880 To compile this driver as a module, choose M here. The module
881 will be called eepro.
884 tristate "LP486E on board Ethernet"
887 Say Y here to support the 82596-based on-board Ethernet controller
888 for the Panther motherboard, which is one of the two shipped in the
889 Intel Professional Workstation.
892 tristate "ICL EtherTeam 16i/32 support"
895 If you have a network (Ethernet) card of this type, say Y and read
896 the Ethernet-HOWTO, available from
897 <http://www.tldp.org/docs.html#howto>.
899 To compile this driver as a module, choose M here. The module
900 will be called eth16i.
903 tristate "Zenith Z-Note support (EXPERIMENTAL)"
904 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
906 The Zenith Z-Note notebook computer has a built-in network
907 (Ethernet) card, and this is the Linux driver for it. Note that the
908 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
909 by this driver. Read the Ethernet-HOWTO, available from
910 <http://www.tldp.org/docs.html#howto>.
913 tristate "SEEQ8005 support (EXPERIMENTAL)"
914 depends on NET_ISA && EXPERIMENTAL
916 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
917 is for you, read the Ethernet-HOWTO, available from
918 <http://www.tldp.org/docs.html#howto>.
920 To compile this driver as a module, choose M here. The module
921 will be called seeq8005.
924 tristate "IBM LAN Adapter/A support"
927 This is a Micro Channel Ethernet adapter. You need to set
928 CONFIG_MCA to use this driver. It is both available as an in-kernel
929 driver and as a module.
931 To compile this driver as a module, choose M here. The only
932 currently supported card is the IBM LAN Adapter/A for Ethernet. It
933 will both support 16K and 32K memory windows, however a 32K window
934 gives a better security against packet losses. Usage of multiple
935 boards with this driver should be possible, but has not been tested
936 up to now due to lack of hardware.
939 tristate "IBM LAN Virtual Ethernet support"
940 depends on PPC_PSERIES
942 This driver supports virtual ethernet adapters on newer IBM iSeries
945 To compile this driver as a module, choose M here. The module will
948 source "drivers/net/ibm_newemac/Kconfig"
951 bool "EISA, VLB, PCI and on board controllers"
952 depends on ISA || EISA || PCI
954 This is another class of network cards which attach directly to the
955 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
956 available from <http://www.tldp.org/docs.html#howto>.
958 Note that the answer to this question doesn't directly affect the
959 kernel: saying N will just cause the configurator to skip all
960 the questions about this class of network cards. If you say Y, you
961 will be asked for your specific card in the following questions. If
962 you are unsure, say Y.
964 config ADAPTEC_STARFIRE
965 tristate "Adaptec Starfire/DuraLAN support"
966 depends on NET_PCI && PCI
970 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
971 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
972 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
975 To compile this driver as a module, choose M here: the module
976 will be called starfire. This is recommended.
979 tristate "Micrel KSZ8841/2 PCI"
980 depends on NET_PCI && PCI
984 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
986 To compile this driver as a module, choose M here. The module
987 will be called ksz884x.
990 tristate "Apricot Xen-II on board Ethernet"
991 depends on NET_PCI && ISA
993 If you have a network (Ethernet) controller of this type, say Y and
994 read the Ethernet-HOWTO, available from
995 <http://www.tldp.org/docs.html#howto>.
997 To compile this driver as a module, choose M here. The module
998 will be called apricot.
1001 tristate "nForce Ethernet support"
1002 depends on NET_PCI && PCI
1004 If you have a network (Ethernet) controller of this type, say Y and
1005 read the Ethernet-HOWTO, available from
1006 <http://www.tldp.org/docs.html#howto>.
1008 To compile this driver as a module, choose M here. The module
1009 will be called forcedeth.
1012 tristate "CS89x0 support"
1013 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1014 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1016 Support for CS89x0 chipset based Ethernet cards. If you have a
1017 network (Ethernet) card of this type, say Y and read the
1018 Ethernet-HOWTO, available from
1019 <http://www.tldp.org/docs.html#howto> as well as
1020 <file:Documentation/networking/cs89x0.txt>.
1022 To compile this driver as a module, choose M here. The module
1023 will be called cs89x0.
1025 config CS89x0_NONISA_IRQ
1027 depends on CS89x0 != n
1028 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1031 tristate "TOSHIBA TC35815 Ethernet support"
1032 depends on NET_PCI && PCI && MIPS
1036 tristate "Intel(R) PRO/100+ support"
1037 depends on NET_PCI && PCI
1040 This driver supports Intel(R) PRO/100 family of adapters.
1041 To verify that your adapter is supported, find the board ID number
1042 on the adapter. Look for a label that has a barcode and a number
1043 in the format 123456-001 (six digits hyphen three digits).
1045 Use the above information and the Adapter & Driver ID Guide at:
1047 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1049 to identify the adapter.
1051 For the latest Intel PRO/100 network driver for Linux, see:
1053 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1055 More specific information on configuring the driver is in
1056 <file:Documentation/networking/e100.txt>.
1058 To compile this driver as a module, choose M here. The module
1059 will be called e100.
1062 tristate "Myson MTD-8xx PCI Ethernet support"
1063 depends on NET_PCI && PCI
1067 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1068 cards. <http://www.myson.com.tw/>
1071 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1072 depends on NET_PCI && PCI
1075 This driver is for the National Semiconductor DP83810 series,
1076 which is used in cards from PureData, NetGear, Linksys
1077 and others, including the 83815 chip.
1078 More specific information and updates are available from
1079 <http://www.scyld.com/network/natsemi.html>.
1082 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1083 depends on NET_PCI && PCI && EXPERIMENTAL
1087 This is a driver for the Fast Ethernet PCI network cards based on
1088 the RTL8139C+ chips. If you have one of those, say Y and read
1089 the Ethernet-HOWTO, available from
1090 <http://www.tldp.org/docs.html#howto>.
1092 To compile this driver as a module, choose M here: the module
1093 will be called 8139cp. This is recommended.
1096 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1097 depends on NET_PCI && PCI
1101 This is a driver for the Fast Ethernet PCI network cards based on
1102 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1103 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1105 To compile this driver as a module, choose M here: the module
1106 will be called 8139too. This is recommended.
1109 bool "Use PIO instead of MMIO"
1113 This instructs the driver to use programmed I/O ports (PIO) instead
1114 of PCI shared memory (MMIO). This can possibly solve some problems
1115 in case your mainboard has memory consistency issues. If unsure,
1118 config 8139TOO_TUNE_TWISTER
1119 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1122 This implements a function which might come in handy in case you
1123 are using low quality on long cabling. It is required for RealTek
1124 RTL-8139 revision K boards, and totally unused otherwise. It tries
1125 to match the transceiver to the cable characteristics. This is
1126 experimental since hardly documented by the manufacturer.
1130 bool "Support for older RTL-8129/8130 boards"
1133 This enables support for the older and uncommon RTL-8129 and
1134 RTL-8130 chips, which support MII via an external transceiver,
1135 instead of an internal one. Disabling this option will save some
1136 memory by making the code size smaller. If unsure, say Y.
1138 config 8139_OLD_RX_RESET
1139 bool "Use older RX-reset method"
1142 The 8139too driver was recently updated to contain a more rapid
1143 reset sequence, in the face of severe receive errors. This "new"
1144 RX-reset method should be adequate for all boards. But if you
1145 experience problems, you can enable this option to restore the
1146 old RX-reset behavior. If unsure, say N.
1149 tristate "RDC R6040 Fast Ethernet Adapter support"
1150 depends on NET_PCI && PCI
1155 This is a driver for the R6040 Fast Ethernet MACs found in the
1156 the RDC R-321x System-on-chips.
1158 To compile this driver as a module, choose M here: the module
1159 will be called r6040. This is recommended.
1162 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1163 depends on NET_PCI && PCI
1167 This is a driver for the Fast Ethernet PCI network cards based on
1168 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1169 SiS 630 and SiS 540 chipsets.
1171 This driver also supports AMD 79C901 HomePNA so that you can use
1172 your phone line as a network cable.
1174 To compile this driver as a module, choose M here: the module
1175 will be called sis900. This is recommended.
1178 tristate "SMC EtherPower II"
1179 depends on NET_PCI && PCI
1183 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1184 which is based on the SMC83c17x (EPIC/100).
1185 More specific information and updates are available from
1186 <http://www.scyld.com/network/epic100.html>.
1189 tristate "SMSC LAN9420 PCI ethernet adapter support"
1190 depends on NET_PCI && PCI
1195 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1196 Say Y if you want it compiled into the kernel,
1197 and read the Ethernet-HOWTO, available from
1198 <http://www.tldp.org/docs.html#howto>.
1200 This driver is also available as a module. The module will be
1201 called smsc9420. If you want to compile it as a module, say M
1202 here and read <file:Documentation/kbuild/modules.txt>
1205 tristate "Sundance Alta support"
1206 depends on NET_PCI && PCI
1210 This driver is for the Sundance "Alta" chip.
1211 More specific information and updates are available from
1212 <http://www.scyld.com/network/sundance.html>.
1214 config SUNDANCE_MMIO
1215 bool "Use MMIO instead of PIO"
1218 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1219 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1220 is known to solve bugs on certain chips.
1225 tristate "TI ThunderLAN support"
1226 depends on NET_PCI && (PCI || EISA)
1228 If you have a PCI Ethernet network card based on the ThunderLAN chip
1229 which is supported by this driver, say Y and read the
1230 Ethernet-HOWTO, available from
1231 <http://www.tldp.org/docs.html#howto>.
1233 Devices currently supported by this driver are Compaq Netelligent,
1234 Compaq NetFlex and Olicom cards. Please read the file
1235 <file:Documentation/networking/tlan.txt> for more details.
1237 To compile this driver as a module, choose M here. The module
1238 will be called tlan.
1240 Please email feedback to <torben.mathiasen@compaq.com>.
1243 tristate "Micrel KSZ8841/42 with generic bus interface"
1244 depends on HAS_IOMEM && DMA_ENGINE
1246 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1247 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1251 tristate "Micrel KS8851 SPI"
1256 SPI driver for Micrel KS8851 SPI attached network chip.
1259 tristate "Micrel KS8851 MLL"
1260 depends on HAS_IOMEM
1263 This platform driver is for Micrel KS8851 Address/data bus
1264 multiplexed network chip.
1267 tristate "VIA Rhine support"
1268 depends on NET_PCI && PCI
1272 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1273 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1274 Ethernet functions can also be found integrated on South Bridges
1277 To compile this driver as a module, choose M here. The module
1278 will be called via-rhine.
1280 config VIA_RHINE_MMIO
1281 bool "Use MMIO instead of PIO"
1282 depends on VIA_RHINE
1284 This instructs the driver to use PCI shared memory (MMIO) instead of
1285 programmed I/O ports (PIO). Enabling this gives an improvement in
1286 processing time in parts of the driver.
1291 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1292 depends on NET_PCI && PCI && EXPERIMENTAL
1295 This is a driver for the Fast Ethernet PCI network cards based on
1296 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1297 have one of these, say Y here.
1299 To compile this driver as a module, choose M here: the module
1300 will be called sc92031. This is recommended.
1303 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1304 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1307 TI AR7 CPMAC Ethernet support
1310 bool "Pocket and portable adapters"
1313 Cute little network (Ethernet) devices which attach to the parallel
1314 port ("pocket adapters"), commonly used with laptops. If you have
1315 one of those, say Y and read the Ethernet-HOWTO, available from
1316 <http://www.tldp.org/docs.html#howto>.
1318 If you want to plug a network (or some other) card into the PCMCIA
1319 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1320 credit card size extension cards used by all modern laptops), you
1321 need the pcmcia-cs package (location contained in the file
1322 <file:Documentation/Changes>) and you can say N here.
1324 Laptop users should read the Linux Laptop home page at
1325 <http://www.linux-on-laptops.com/> or
1326 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1328 Note that the answer to this question doesn't directly affect the
1329 kernel: saying N will just cause the configurator to skip all
1330 the questions about this class of network devices. If you say Y, you
1331 will be asked for your specific device in the following questions.
1334 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1335 depends on NET_POCKET && PARPORT && X86
1338 This is a network (Ethernet) device which attaches to your parallel
1339 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1340 available from <http://www.tldp.org/docs.html#howto>, if you
1341 want to use this. If you intend to use this driver, you should have
1342 said N to the "Parallel printer support", because the two drivers
1343 don't like each other.
1345 To compile this driver as a module, choose M here: the module
1349 tristate "D-Link DE600 pocket adapter support"
1350 depends on NET_POCKET && PARPORT
1352 This is a network (Ethernet) device which attaches to your parallel
1353 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1354 Ethernet-HOWTO, available from
1355 <http://www.tldp.org/docs.html#howto>, if you want to use
1356 this. It is possible to have several devices share a single parallel
1357 port and it is safe to compile the corresponding drivers into the
1360 To compile this driver as a module, choose M here: the module
1361 will be called de600.
1364 tristate "D-Link DE620 pocket adapter support"
1365 depends on NET_POCKET && PARPORT
1367 This is a network (Ethernet) device which attaches to your parallel
1368 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1369 Ethernet-HOWTO, available from
1370 <http://www.tldp.org/docs.html#howto>, if you want to use
1371 this. It is possible to have several devices share a single parallel
1372 port and it is safe to compile the corresponding drivers into the
1375 To compile this driver as a module, choose M here: the module
1376 will be called de620.
1379 tristate "SGI Seeq ethernet controller support"
1380 depends on SGI_HAS_SEEQ
1382 Say Y here if you have an Seeq based Ethernet network card. This is
1383 used in many Silicon Graphics machines.
1386 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1387 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1388 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1389 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1392 Say Y here if you want to use the built-in 10/100 Fast ethernet
1393 controller on some Motorola ColdFire and Freescale i.MX processors.
1396 tristate "MPC52xx FEC driver"
1397 depends on PPC_MPC52xx && PPC_BESTCOMM
1400 select PPC_BESTCOMM_FEC
1402 This option enables support for the MPC5200's on-chip
1403 Fast Ethernet Controller
1404 If compiled as module, it will be called fec_mpc52xx.
1406 config FEC_MPC52xx_MDIO
1407 bool "MPC52xx FEC MDIO bus driver"
1408 depends on FEC_MPC52xx
1411 The MPC5200's FEC can connect to the Ethernet either with
1412 an external MII PHY chip or 10 Mbps 7-wire interface
1413 (Motorola? industry standard).
1414 If your board uses an external PHY connected to FEC, enable this.
1415 If not sure, enable.
1416 If compiled as module, it will be called fec_mpc52xx_phy.
1419 tristate "Atheros L2 Fast Ethernet support"
1424 This driver supports the Atheros L2 fast ethernet adapter.
1426 To compile this driver as a module, choose M here. The module
1427 will be called atl2.
1429 config XILINX_EMACLITE
1430 tristate "Xilinx 10/100 Ethernet Lite support"
1431 depends on PPC32 || MICROBLAZE
1434 This driver supports the 10/100 Ethernet Lite from Xilinx.
1437 tristate "Faraday FTMAC100 10/100 Ethernet support"
1441 This driver supports the FTMAC100 10/100 Ethernet controller
1442 from Faraday. It is used on Faraday A320, Andes AG101 and some
1443 other ARM/NDS32 SoC's.
1446 tristate "Lantiq SoC ETOP driver"
1447 depends on SOC_TYPE_XWAY
1449 Support for the MII0 inside the Lantiq SoC
1452 source "drivers/net/fs_enet/Kconfig"
1454 source "drivers/net/octeon/Kconfig"
1456 endif # NET_ETHERNET
1462 menuconfig NETDEV_1000
1463 bool "Ethernet (1000 Mbit)"
1467 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1468 type of Local Area Network (LAN) in universities and companies.
1470 Say Y here to get to see options for Gigabit Ethernet drivers.
1471 This option alone does not add any kernel code.
1472 Note that drivers supporting both 100 and 1000 MBit may be listed
1473 under "Ethernet (10 or 100MBit)" instead.
1475 If you say N, all options in this submenu will be skipped and disabled.
1480 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1484 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1486 D-Link DGE-550T Gigabit Ethernet Adapter.
1487 D-Link DL2000-based Gigabit Ethernet Adapter.
1488 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1490 To compile this driver as a module, choose M here: the
1491 module will be called dl2k.
1494 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1497 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1498 adapters. For more information on how to identify your adapter, go
1499 to the Adapter & Driver ID Guide at:
1501 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1503 For general information and support, go to the Intel support
1506 <http://support.intel.com>
1508 More specific information on configuring the driver is in
1509 <file:Documentation/networking/e1000.txt>.
1511 To compile this driver as a module, choose M here. The module
1512 will be called e1000.
1515 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1516 depends on PCI && (!SPARC32 || BROKEN)
1519 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1520 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1521 use the regular e1000 driver For more information on how to
1522 identify your adapter, go to the Adapter & Driver ID Guide at:
1524 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1526 For general information and support, go to the Intel support
1529 <http://support.intel.com>
1531 To compile this driver as a module, choose M here. The module
1532 will be called e1000e.
1535 tristate "IP1000 Gigabit Ethernet support"
1536 depends on PCI && EXPERIMENTAL
1539 This driver supports IP1000 gigabit Ethernet cards.
1541 To compile this driver as a module, choose M here: the module
1542 will be called ipg. This is recommended.
1545 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
1548 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
1549 adapters. For more information on how to identify your adapter, go
1550 to the Adapter & Driver ID Guide at:
1552 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1554 For general information and support, go to the Intel support
1557 <http://support.intel.com>
1559 More specific information on configuring the driver is in
1560 <file:Documentation/networking/e1000.txt>.
1562 To compile this driver as a module, choose M here. The module
1566 bool "Direct Cache Access (DCA) Support"
1568 depends on IGB && DCA && !(IGB=y && DCA=m)
1570 Say Y here if you want to use Direct Cache Access (DCA) in the
1571 driver. DCA is a method for warming the CPU cache before data
1572 is used, with the intent of lessening the impact of cache misses.
1575 tristate "Intel(R) 82576 Virtual Function Ethernet support"
1578 This driver supports Intel(R) 82576 virtual functions. For more
1579 information on how to identify your adapter, go to the Adapter &
1582 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1584 For general information and support, go to the Intel support
1587 <http://support.intel.com>
1589 More specific information on configuring the driver is in
1590 <file:Documentation/networking/e1000.txt>.
1592 To compile this driver as a module, choose M here. The module
1593 will be called igbvf.
1595 source "drivers/net/ixp2000/Kconfig"
1598 tristate "National Semiconductor DP83820 support"
1601 This is a driver for the National Semiconductor DP83820 series
1602 of gigabit ethernet MACs. Cards using this chipset include
1603 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1604 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1608 tristate "Packet Engines Hamachi GNIC-II support"
1612 If you have a Gigabit Ethernet card of this type, say Y and read
1613 the Ethernet-HOWTO, available from
1614 <http://www.tldp.org/docs.html#howto>.
1616 To compile this driver as a module, choose M here. The module will be
1620 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1621 depends on PCI && EXPERIMENTAL
1624 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1625 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1626 used by the Beowulf Linux cluster project. See
1627 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1628 information about this driver in particular and Beowulf in general.
1630 To compile this driver as a module, choose M here: the module
1631 will be called yellowfin. This is recommended.
1634 tristate "Realtek 8169 gigabit ethernet support"
1640 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1642 To compile this driver as a module, choose M here: the module
1643 will be called r8169. This is recommended.
1646 tristate "SiS190/SiS191 gigabit ethernet support"
1651 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1652 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1653 appear in lan on motherboard designs which are based on SiS 965
1654 and SiS 966 south bridge.
1656 To compile this driver as a module, choose M here: the module
1657 will be called sis190. This is recommended.
1660 tristate "Marvell Yukon Gigabit Ethernet support"
1664 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1665 and related Gigabit Ethernet adapters. It is a new smaller driver
1666 with better performance and more complete ethtool support.
1668 It does not support the link failover and network management
1669 features that "portable" vendor supplied sk98lin driver does.
1671 This driver supports adapters based on the original Yukon chipset:
1672 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
1673 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
1675 It does not support the newer Yukon2 chipset: a separate driver,
1676 sky2, is provided for these adapters.
1678 To compile this driver as a module, choose M here: the module
1679 will be called skge. This is recommended.
1682 bool "Debugging interface"
1683 depends on SKGE && DEBUG_FS
1685 This option adds the ability to dump driver state for debugging.
1686 The file /sys/kernel/debug/skge/ethX displays the state of the internal
1687 transmit and receive rings.
1692 bool "Support for older SysKonnect Genesis boards"
1695 This enables support for the older and uncommon SysKonnect Genesis
1696 chips, which support MII via an external transceiver, instead of
1697 an internal one. Disabling this option will save some memory
1698 by making code smaller. If unsure say Y.
1701 tristate "Marvell Yukon 2 support"
1705 This driver supports Gigabit Ethernet adapters based on the
1706 Marvell Yukon 2 chipset:
1707 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
1708 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
1710 There is companion driver for the older Marvell Yukon and
1711 SysKonnect Genesis based adapters: skge.
1713 To compile this driver as a module, choose M here: the module
1714 will be called sky2. This is recommended.
1717 bool "Debugging interface"
1718 depends on SKY2 && DEBUG_FS
1720 This option adds the ability to dump driver state for debugging.
1721 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
1722 transmit and receive rings.
1727 tristate "VIA Velocity support"
1733 If you have a VIA "Velocity" based network card say Y here.
1735 To compile this driver as a module, choose M here. The module
1736 will be called via-velocity.
1739 tristate "Spider Gigabit Ethernet driver"
1740 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
1743 This driver supports the Gigabit Ethernet chips present on the
1744 Cell Processor-Based Blades from IBM.
1747 tristate "Tundra TSI108 gigabit Ethernet support"
1748 depends on TSI108_BRIDGE
1750 This driver supports Tundra TSI108 gigabit Ethernet ports.
1751 To compile this driver as a module, choose M here: the module
1752 will be called tsi108_eth.
1755 tristate "PS3 Gigabit Ethernet driver"
1757 select PS3_SYS_MANAGER
1759 This driver supports the network device on the PS3 game
1760 console. This driver has built-in support for Ethernet.
1762 To compile this driver as a module, choose M here: the
1763 module will be called ps3_gelic.
1765 config GELIC_WIRELESS
1766 bool "PS3 Wireless support"
1768 depends on GELIC_NET
1771 This option adds the support for the wireless feature of PS3.
1772 If you have the wireless-less model of PS3 or have no plan to
1773 use wireless feature, disabling this option saves memory. As
1774 the driver automatically distinguishes the models, you can
1775 safely enable this option even if you have a wireless-less model.
1778 tristate "Freescale PQ MDIO"
1782 This driver supports the MDIO bus used by the gianfar and UCC drivers.
1785 tristate "Gianfar Ethernet"
1791 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
1792 and MPC86xx family of chips, and the FEC on the 8540.
1795 tristate "Freescale QE Gigabit Ethernet"
1796 depends on QUICC_ENGINE
1800 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
1801 which is available on some Freescale SOCs.
1803 config UGETH_TX_ON_DEMAND
1804 bool "Transmit on Demand support"
1808 tristate "Marvell Discovery (643XX) and Orion ethernet support"
1809 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
1813 This driver supports the gigabit ethernet MACs in the
1814 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
1815 in the Marvell Orion ARM SoC family.
1817 Some boards that use the Discovery chipset are the Momenco
1818 Ocelot C and Jaguar ATX and Pegasos II.
1820 config XILINX_LL_TEMAC
1821 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1822 depends on PPC || MICROBLAZE
1825 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1826 core used in Xilinx Spartan and Virtex FPGAs
1829 tristate "QLogic QLA3XXX Network Driver Support"
1832 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
1834 To compile this driver as a module, choose M here: the module
1835 will be called qla3xxx.
1838 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
1843 This driver supports the Atheros/Attansic L1 gigabit ethernet
1846 To compile this driver as a module, choose M here. The module
1847 will be called atl1.
1850 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
1851 depends on PCI && EXPERIMENTAL
1855 This driver supports the Atheros L1E gigabit ethernet adapter.
1857 To compile this driver as a module, choose M here. The module
1858 will be called atl1e.
1861 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
1862 depends on PCI && EXPERIMENTAL
1866 This driver supports the Atheros L1C gigabit ethernet adapter.
1868 To compile this driver as a module, choose M here. The module
1869 will be called atl1c.
1872 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1877 This driver supports the PCI-Express gigabit ethernet adapters
1878 based on JMicron JMC250 chipset.
1880 To compile this driver as a module, choose M here. The module
1884 tristate "S6105 GMAC ethernet support"
1885 depends on XTENSA_VARIANT_S6000
1888 This driver supports the on chip ethernet device on the
1889 S6105 xtensa processor.
1891 To compile this driver as a module, choose M here. The module
1892 will be called s6gmac.
1894 source "drivers/net/stmmac/Kconfig"
1897 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1901 This is a gigabit ethernet driver for EG20T PCH.
1902 EG20T PCH is the platform controller hub that is used in Intel's
1903 general embedded platform.
1904 EG20T PCH has Gigabit Ethernet interface.
1905 Using this interface, it is able to access system devices connected
1906 to Gigabit Ethernet.
1907 This driver enables Gigabit Ethernet function.
1909 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1910 Output Hub), ML7223.
1911 ML7223 IOH is for MP(Media Phone) use.
1912 ML7223 is companion chip for Intel Atom E6xx series.
1913 ML7223 is completely compatible for Intel EG20T PCH.
1916 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
1920 This driver supports the FTGMAC100 Gigabit Ethernet controller
1921 from Faraday. It is used on Faraday A369, Andes AG102 and some
1922 other ARM/NDS32 SoC's.
1927 # 10 Gigabit Ethernet
1930 menuconfig NETDEV_10000
1931 bool "Ethernet (10000 Mbit)"
1935 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1936 This option alone does not add any kernel code.
1938 If you say N, all options in this submenu will be skipped and disabled.
1946 tristate "eHEA Ethernet support"
1947 depends on IBMEBUS && INET && SPARSEMEM
1950 This driver supports the IBM pSeries eHEA ethernet adapter.
1952 To compile the driver as a module, choose M here. The module
1953 will be called ehea.
1956 tristate "Cisco VIC Ethernet NIC Support"
1957 depends on PCI && INET
1959 This enables the support for the Cisco VIC Ethernet card.
1962 tristate "Intel(R) 10GbE PCI Express adapters support"
1963 depends on PCI && INET
1966 This driver supports Intel(R) 10GbE PCI Express family of
1967 adapters. For more information on how to identify your adapter, go
1968 to the Adapter & Driver ID Guide at:
1970 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1972 For general information and support, go to the Intel support
1975 <http://support.intel.com>
1977 To compile this driver as a module, choose M here. The module
1978 will be called ixgbe.
1981 bool "Direct Cache Access (DCA) Support"
1983 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
1985 Say Y here if you want to use Direct Cache Access (DCA) in the
1986 driver. DCA is a method for warming the CPU cache before data
1987 is used, with the intent of lessening the impact of cache misses.
1990 bool "Data Center Bridging (DCB) Support"
1992 depends on IXGBE && DCB
1994 Say Y here if you want to use Data Center Bridging (DCB) in the
2000 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2003 This driver supports Intel(R) 82599 virtual functions. For more
2004 information on how to identify your adapter, go to the Adapter &
2007 <http://support.intel.com/support/network/sb/CS-008441.htm>
2009 For general information and support, go to the Intel support
2012 <http://support.intel.com>
2014 More specific information on configuring the driver is in
2015 <file:Documentation/networking/ixgbevf.txt>.
2017 To compile this driver as a module, choose M here. The module
2018 will be called ixgbevf. MSI-X interrupt support is required
2019 for this driver to work correctly.
2022 tristate "Intel(R) PRO/10GbE support"
2025 This driver supports Intel(R) PRO/10GbE family of adapters for
2026 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2027 instead. For more information on how to identify your adapter, go
2028 to the Adapter & Driver ID Guide at:
2030 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2032 For general information and support, go to the Intel support
2035 <http://support.intel.com>
2037 More specific information on configuring the driver is in
2038 <file:Documentation/networking/ixgb.txt>.
2040 To compile this driver as a module, choose M here. The module
2041 will be called ixgb.
2044 tristate "Exar Xframe 10Gb Ethernet Adapter"
2047 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2049 More specific information on configuring the driver is in
2050 <file:Documentation/networking/s2io.txt>.
2052 To compile this driver as a module, choose M here. The module
2053 will be called s2io.
2056 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2057 depends on PCI && INET
2059 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2060 I/O Virtualized Server Adapter.
2062 More specific information on configuring the driver is in
2063 <file:Documentation/networking/vxge.txt>.
2065 To compile this driver as a module, choose M here. The module
2066 will be called vxge.
2068 config VXGE_DEBUG_TRACE_ALL
2069 bool "Enabling All Debug trace statments in driver"
2073 Say Y here if you want to enabling all the debug trace statements in
2074 the vxge driver. By default only few debug trace statements are
2078 tristate "Myricom Myri-10G Ethernet support"
2079 depends on PCI && INET
2084 This driver supports Myricom Myri-10G Dual Protocol interface in
2085 Ethernet mode. If the eeprom on your board is not recent enough,
2086 you will need a newer firmware image.
2087 You may get this image or more information, at:
2089 <http://www.myri.com/scs/download-Myri10GE.html>
2091 To compile this driver as a module, choose M here. The module
2092 will be called myri10ge.
2095 bool "Direct Cache Access (DCA) Support"
2097 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2099 Say Y here if you want to use Direct Cache Access (DCA) in the
2100 driver. DCA is a method for warming the CPU cache before data
2101 is used, with the intent of lessening the impact of cache misses.
2104 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2108 This enables the support for NetXen's Gigabit Ethernet card.
2111 tristate "Sun Neptune 10Gbit Ethernet support"
2115 This enables support for cards based upon Sun's
2119 tristate "PA Semi 1/10Gbit MAC"
2120 depends on PPC_PASEMI && PCI && INET
2124 This driver supports the on-chip 1/10Gbit Ethernet controller on
2125 PA Semi's PWRficient line of chips.
2128 tristate "Mellanox Technologies 10Gbit Ethernet support"
2129 depends on PCI && INET
2133 This driver supports Mellanox Technologies ConnectX Ethernet
2142 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2143 depends on MLX4_CORE
2146 This option causes debugging code to be compiled into the
2147 mlx4_core driver. The output can be turned on via the
2148 debug_level module parameter (which can also be set after
2149 the driver is loaded through sysfs).
2152 tristate "Tehuti Networks 10G Ethernet"
2155 Tehuti Networks 10G Ethernet NIC
2158 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2162 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2166 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2169 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2171 To compile this driver as a module, choose M here: the module
2172 will be called qlge.
2175 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2178 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2180 To compile this driver as a module, choose M here: the module
2183 For general information and support, go to the Brocade support
2186 <http://support.brocade.com>
2188 source "drivers/net/sfc/Kconfig"
2190 source "drivers/net/benet/Kconfig"
2192 endif # NETDEV_10000
2194 source "drivers/net/tokenring/Kconfig"
2196 source "drivers/net/wireless/Kconfig"
2198 source "drivers/net/wimax/Kconfig"
2200 source "drivers/net/usb/Kconfig"
2202 source "drivers/net/pcmcia/Kconfig"
2204 source "drivers/net/wan/Kconfig"
2206 source "drivers/atm/Kconfig"
2208 source "drivers/ieee802154/Kconfig"
2210 source "drivers/s390/net/Kconfig"
2212 source "drivers/net/caif/Kconfig"
2215 tristate "Tilera GBE/XGBE network driver support"
2220 This is a standard Linux network device driver for the
2221 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2223 To compile this driver as a module, choose M here: the module
2224 will be called tile_net.
2226 config XEN_NETDEV_FRONTEND
2227 tristate "Xen network device frontend driver"
2229 select XEN_XENBUS_FRONTEND
2232 This driver provides support for Xen paravirtual network
2233 devices exported by a Xen network driver domain (often
2236 The corresponding Linux backend driver is enabled by the
2237 CONFIG_XEN_NETDEV_BACKEND option.
2239 If you are compiling a kernel for use as Xen guest, you
2240 should say Y here. To compile this driver as a module, chose
2241 M here: the module will be called xen-netfront.
2243 config XEN_NETDEV_BACKEND
2244 tristate "Xen backend network device"
2245 depends on XEN_BACKEND
2247 This driver allows the kernel to act as a Xen network driver
2248 domain which exports paravirtual network devices to other
2249 Xen domains. These devices can be accessed by any operating
2250 system that implements a compatible front end.
2252 The corresponding Linux frontend driver is enabled by the
2253 CONFIG_XEN_NETDEV_FRONTEND configuration option.
2255 The backend driver presents a standard network device
2256 endpoint for each paravirtual network device to the driver
2257 domain network stack. These can then be bridged or routed
2258 etc in order to provide full network connectivity.
2260 If you are compiling a kernel to run in a Xen network driver
2261 domain (often this is domain 0) you should say Y here. To
2262 compile this driver as a module, chose M here: the module
2263 will be called xen-netback.
2266 tristate "iSeries Virtual Ethernet driver support"
2267 depends on PPC_ISERIES
2270 tristate "RapidIO Ethernet over messaging driver support"
2273 config RIONET_TX_SIZE
2274 int "Number of outbound queue entries"
2278 config RIONET_RX_SIZE
2279 int "Number of inbound queue entries"
2284 tristate "FDDI driver support"
2285 depends on (PCI || EISA || TC)
2287 Fiber Distributed Data Interface is a high speed local area network
2288 design; essentially a replacement for high speed Ethernet. FDDI can
2289 run over copper or fiber. If you are connected to such a network and
2290 want a driver for the FDDI card in your computer, say Y here (and
2291 then also Y to the driver for your FDDI card, below). Most people
2295 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2296 depends on FDDI && (PCI || EISA || TC)
2298 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2299 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2300 to a local FDDI network.
2302 To compile this driver as a module, choose M here: the module
2303 will be called defxx. If unsure, say N.
2307 prompt "Use MMIO instead of PIO" if PCI || EISA
2309 default n if PCI || EISA
2312 This instructs the driver to use EISA or PCI memory-mapped I/O
2313 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2314 Enabling this gives an improvement in processing time in parts
2315 of the driver, but it may cause problems with EISA (DEFEA)
2316 adapters. TURBOchannel does not have the concept of I/O ports,
2317 so MMIO is always used for these (DEFTA) adapters.
2322 tristate "SysKonnect FDDI PCI support"
2323 depends on FDDI && PCI
2326 Say Y here if you have a SysKonnect FDDI PCI adapter.
2327 The following adapters are supported by this driver:
2328 - SK-5521 (SK-NET FDDI-UP)
2329 - SK-5522 (SK-NET FDDI-UP DAS)
2330 - SK-5541 (SK-NET FDDI-FP)
2331 - SK-5543 (SK-NET FDDI-LP)
2332 - SK-5544 (SK-NET FDDI-LP DAS)
2333 - SK-5821 (SK-NET FDDI-UP64)
2334 - SK-5822 (SK-NET FDDI-UP64 DAS)
2335 - SK-5841 (SK-NET FDDI-FP64)
2336 - SK-5843 (SK-NET FDDI-LP64)
2337 - SK-5844 (SK-NET FDDI-LP64 DAS)
2338 - Netelligent 100 FDDI DAS Fibre SC
2339 - Netelligent 100 FDDI SAS Fibre SC
2340 - Netelligent 100 FDDI DAS UTP
2341 - Netelligent 100 FDDI SAS UTP
2342 - Netelligent 100 FDDI SAS Fibre MIC
2344 Read <file:Documentation/networking/skfp.txt> for information about
2347 Questions concerning this driver can be addressed to:
2348 <linux@syskonnect.de>
2350 To compile this driver as a module, choose M here: the module
2351 will be called skfp. This is recommended.
2354 bool "HIPPI driver support (EXPERIMENTAL)"
2355 depends on EXPERIMENTAL && INET && PCI
2357 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2358 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2359 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2360 single-mode). HIPPI networks are commonly used for clusters and to
2361 connect to super computers. If you are connected to a HIPPI network
2362 and have a HIPPI network card in your computer that you want to use
2363 under Linux, say Y here (you must also remember to enable the driver
2364 for your HIPPI card below). Most people will say N here.
2367 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2368 depends on HIPPI && PCI
2370 Say Y here if this is your PCI HIPPI network card.
2372 To compile this driver as a module, choose M here: the module
2373 will be called rrunner. If unsure, say N.
2375 config ROADRUNNER_LARGE_RINGS
2376 bool "Use large TX/RX rings (EXPERIMENTAL)"
2377 depends on ROADRUNNER
2379 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2380 of additional memory to allow for fastest operation, both for
2381 transmitting and receiving. This memory cannot be used by any other
2382 kernel code or by user space programs. Say Y here only if you have
2386 tristate "PLIP (parallel port) support"
2389 PLIP (Parallel Line Internet Protocol) is used to create a
2390 reasonably fast mini network consisting of two (or, rarely, more)
2391 local machines. A PLIP link from a Linux box is a popular means to
2392 install a Linux distribution on a machine which doesn't have a
2393 CD-ROM drive (a minimal system has to be transferred with floppies
2394 first). The kernels on both machines need to have this PLIP option
2395 enabled for this to work.
2397 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2398 ports (the connectors at the computers with 25 holes) are connected
2399 with "null printer" or "Turbo Laplink" cables which can transmit 4
2400 bits at a time (mode 0) or with special PLIP cables, to be used on
2401 bidirectional parallel ports only, which can transmit 8 bits at a
2402 time (mode 1); you can find the wiring of these cables in
2403 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2404 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2405 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2406 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2407 and winsock or NCSA's telnet.
2409 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2410 as the NET-3-HOWTO, both available from
2411 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2412 protocol has been changed and this PLIP driver won't work together
2413 with the PLIP support in Linux versions 1.0.x. This option enlarges
2414 your kernel by about 8 KB.
2416 To compile this driver as a module, choose M here. The module
2417 will be called plip. If unsure, say Y or M, in case you buy
2421 tristate "PPP (point-to-point protocol) support"
2424 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2425 the same purpose: sending Internet traffic over telephone (and other
2426 serial) lines. Ask your access provider if they support it, because
2427 otherwise you can't use it; most Internet access providers these
2428 days support PPP rather than SLIP.
2430 To use PPP, you need an additional program called pppd as described
2431 in the PPP-HOWTO, available at
2432 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2433 the version of pppd recommended in <file:Documentation/Changes>.
2434 The PPP option enlarges your kernel by about 16 KB.
2436 There are actually two versions of PPP: the traditional PPP for
2437 asynchronous lines, such as regular analog phone lines, and
2438 synchronous PPP which can be used over digital ISDN lines for
2439 example. If you want to use PPP over phone lines or other
2440 asynchronous serial lines, you need to say Y (or M) here and also to
2441 the next option, "PPP support for async serial ports". For PPP over
2442 synchronous lines, you should say Y (or M) here and to "Support
2443 synchronous PPP", below.
2445 If you said Y to "Version information on all symbols" above, then
2446 you cannot compile the PPP driver into the kernel; you can then only
2447 compile it as a module. To compile this driver as a module, choose M
2448 here. The module will be called ppp_generic.
2450 config PPP_MULTILINK
2451 bool "PPP multilink support (EXPERIMENTAL)"
2452 depends on PPP && EXPERIMENTAL
2454 PPP multilink is a protocol (defined in RFC 1990) which allows you
2455 to combine several (logical or physical) lines into one logical PPP
2456 connection, so that you can utilize your full bandwidth.
2458 This has to be supported at the other end as well and you need a
2459 version of the pppd daemon which understands the multilink protocol.
2464 bool "PPP filtering"
2467 Say Y here if you want to be able to filter the packets passing over
2468 PPP interfaces. This allows you to control which packets count as
2469 activity (i.e. which packets will reset the idle timer or bring up
2470 a demand-dialed link) and which packets are to be dropped entirely.
2471 You need to say Y here if you wish to use the pass-filter and
2472 active-filter options to pppd.
2477 tristate "PPP support for async serial ports"
2481 Say Y (or M) here if you want to be able to use PPP over standard
2482 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2483 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2486 To compile this driver as a module, choose M here.
2491 tristate "PPP support for sync tty ports"
2494 Say Y (or M) here if you want to be able to use PPP over synchronous
2495 (HDLC) tty devices, such as the SyncLink adapter. These devices
2496 are often used for high-speed leased lines like T1/E1.
2498 To compile this driver as a module, choose M here.
2501 tristate "PPP Deflate compression"
2506 Support for the Deflate compression method for PPP, which uses the
2507 Deflate algorithm (the same algorithm that gzip uses) to compress
2508 each PPP packet before it is sent over the wire. The machine at the
2509 other end of the PPP link (usually your ISP) has to support the
2510 Deflate compression method as well for this to be useful. Even if
2511 they don't support it, it is safe to say Y here.
2513 To compile this driver as a module, choose M here.
2516 tristate "PPP BSD-Compress compression"
2519 Support for the BSD-Compress compression method for PPP, which uses
2520 the LZW compression method to compress each PPP packet before it is
2521 sent over the wire. The machine at the other end of the PPP link
2522 (usually your ISP) has to support the BSD-Compress compression
2523 method as well for this to be useful. Even if they don't support it,
2524 it is safe to say Y here.
2526 The PPP Deflate compression method ("PPP Deflate compression",
2527 above) is preferable to BSD-Compress, because it compresses better
2530 Note that the BSD compression code will always be compiled as a
2531 module; it is called bsd_comp and will show up in the directory
2532 modules once you have said "make modules". If unsure, say N.
2535 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2536 depends on PPP && EXPERIMENTAL
2542 Support for the MPPE Encryption protocol, as employed by the
2543 Microsoft Point-to-Point Tunneling Protocol.
2545 See http://pptpclient.sourceforge.net/ for information on
2546 configuring PPTP clients and servers to utilize this method.
2549 tristate "PPP over Ethernet (EXPERIMENTAL)"
2550 depends on EXPERIMENTAL && PPP
2552 Support for PPP over Ethernet.
2554 This driver requires the latest version of pppd from the CVS
2555 repository at cvs.samba.org. Alternatively, see the
2556 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2557 which contains instruction on how to use this driver (under
2558 the heading "Kernel mode PPPoE").
2561 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
2562 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
2564 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
2566 This driver requires pppd plugin to work in client mode or
2567 modified pptpd (poptop) to work in server mode.
2568 See http://accel-pptp.sourceforge.net/ for information how to
2569 utilize this module.
2572 tristate "PPP over ATM"
2573 depends on ATM && PPP
2575 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2576 This implementation does not yet comply with section 8 of RFC2364,
2577 which can lead to bad results if the ATM peer loses state and
2578 changes its encapsulation unilaterally.
2581 tristate "PPP over L2TP (EXPERIMENTAL)"
2582 depends on EXPERIMENTAL && L2TP && PPP
2584 Support for PPP-over-L2TP socket family. L2TP is a protocol
2585 used by ISPs and enterprises to tunnel PPP traffic over UDP
2586 tunnels. L2TP is replacing PPTP for VPN uses.
2589 tristate "SLIP (serial line) support"
2591 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2592 connect to your Internet service provider or to connect to some
2593 other local Unix box or if you want to configure your Linux box as a
2594 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2595 Internet Protocol) is a protocol used to send Internet traffic over
2596 serial connections such as telephone lines or null modem cables;
2597 nowadays, the protocol PPP is more commonly used for this same
2600 Normally, your access provider has to support SLIP in order for you
2601 to be able to use it, but there is now a SLIP emulator called SLiRP
2602 around (available from
2603 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2604 allows you to use SLIP over a regular dial up shell connection. If
2605 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2606 NET-3-HOWTO, available from
2607 <http://www.tldp.org/docs.html#howto>, explains how to
2608 configure SLIP. Note that you don't need this option if you just
2609 want to run term (term is a program which gives you almost full
2610 Internet connectivity if you have a regular dial up shell account on
2611 some Internet connected Unix computer. Read
2612 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2613 support will enlarge your kernel by about 4 KB. If unsure, say N.
2615 To compile this driver as a module, choose M here. The module
2616 will be called slip.
2618 config SLIP_COMPRESSED
2619 bool "CSLIP compressed headers"
2623 This protocol is faster than SLIP because it uses compression on the
2624 TCP/IP headers (not on the data itself), but it has to be supported
2625 on both ends. Ask your access provider if you are not sure and
2626 answer Y, just in case. You will still be able to use plain SLIP. If
2627 you plan to use SLiRP, the SLIP emulator (available from
2628 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2629 allows you to use SLIP over a regular dial up shell connection, you
2630 definitely want to say Y here. The NET-3-HOWTO, available from
2631 <http://www.tldp.org/docs.html#howto>, explains how to configure
2632 CSLIP. This won't enlarge your kernel.
2637 This option enables Van Jacobsen serial line header compression
2641 bool "Keepalive and linefill"
2644 Adds additional capabilities to the SLIP driver to support the
2645 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2648 config SLIP_MODE_SLIP6
2649 bool "Six bit SLIP encapsulation"
2652 Just occasionally you may need to run IP over hostile serial
2653 networks that don't pass all control characters or are only seven
2654 bit. Saying Y here adds an extra mode you can use with SLIP:
2655 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2656 the serial device. Naturally, this has to be supported at the other
2657 end of the link as well. It's good enough, for example, to run IP
2658 over the async ports of a Camtec JNT Pad. If unsure, say N.
2661 bool "Fibre Channel driver support"
2662 depends on SCSI && PCI
2664 Fibre Channel is a high speed serial protocol mainly used to connect
2665 large storage devices to the computer; it is compatible with and
2666 intended to replace SCSI.
2668 If you intend to use Fibre Channel, you need to have a Fibre channel
2669 adaptor card in your computer; say Y here and to the driver for your
2670 adaptor below. You also should have said Y to "SCSI support" and
2671 "SCSI generic support".
2674 tristate "Network console logging support"
2676 If you want to log kernel messages over the network, enable this.
2677 See <file:Documentation/networking/netconsole.txt> for details.
2679 config NETCONSOLE_DYNAMIC
2680 bool "Dynamic reconfiguration of logging targets"
2681 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
2682 !(NETCONSOLE=y && CONFIGFS_FS=m)
2684 This option enables the ability to dynamically reconfigure target
2685 parameters (interface, IP addresses, port numbers, MAC addresses)
2686 at runtime through a userspace interface exported using configfs.
2687 See <file:Documentation/networking/netconsole.txt> for details.
2693 bool "Netpoll traffic trapping"
2697 config NET_POLL_CONTROLLER
2701 tristate "Virtio network driver (EXPERIMENTAL)"
2702 depends on EXPERIMENTAL && VIRTIO
2704 This is the virtual network driver for virtio. It can be used with
2705 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
2708 tristate "VMware VMXNET3 ethernet driver"
2709 depends on PCI && INET
2711 This driver supports VMware's vmxnet3 virtual ethernet NIC.
2712 To compile this driver as a module, choose M here: the
2713 module will be called vmxnet3.