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 "ASIX AX88796 NE2000 clone support"
242 depends on ARM || MIPS || SUPERH
246 AX88796 driver, using platform bus to provide
247 chip detection and resources
250 bool "ASIX AX88796 external 93CX6 eeprom support"
254 Select this if your platform comes with an external 93CX6 eeprom.
257 tristate "MACE (Power Mac ethernet) support"
258 depends on PPC_PMAC && PPC32
261 Power Macintoshes and clones with Ethernet built-in on the
262 motherboard will usually use a MACE (Medium Access Control for
263 Ethernet) interface. Say Y to include support for the MACE chip.
265 To compile this driver as a module, choose M here: the module
268 config MACE_AAUI_PORT
269 bool "Use AAUI port instead of TP by default"
272 Some Apple machines (notably the Apple Network Server) which use the
273 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
274 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
275 Y here if you have such a machine. If unsure, say N.
276 The driver will default to AAUI on ANS anyway, and if you use it as
277 a module, you can provide the port_aaui=0|1 to force the driver.
280 tristate "BMAC (G3 ethernet) support"
281 depends on PPC_PMAC && PPC32
284 Say Y for support of BMAC Ethernet interfaces. These are used on G3
287 To compile this driver as a module, choose M here: the module
291 tristate "Hydra support"
295 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
297 To compile this driver as a module, choose M here: the module
298 will be called hydra.
301 tristate "Zorro NS8390-based Ethernet support"
305 This driver is for Zorro Ethernet cards using an NS8390-compatible
306 chipset, like the Village Tronic Ariadne II and the Individual
307 Computers X-Surf Ethernet cards. If you have such a card, say Y.
310 To compile this driver as a module, choose M here: the module
311 will be called zorro8390.
314 tristate "PCMCIA NE2000 support"
315 depends on AMIGA_PCMCIA
318 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
321 To compile this driver as a module, choose M here: the module
325 bool "Macintosh NS 8390 based ethernet cards"
329 If you want to include a driver to support Nubus or LC-PDS
330 Ethernet cards using an NS8390 chipset or its equivalent, say Y
331 and read the Ethernet-HOWTO, available from
332 <http://www.tldp.org/docs.html#howto>.
335 tristate "Macintosh CS89x0 based ethernet cards"
338 Support for CS89x0 chipset based Ethernet cards. If you have a
339 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
340 read the Ethernet-HOWTO, available from
341 <http://www.tldp.org/docs.html#howto>.
343 To compile this driver as a module, choose M here. This module will
347 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
350 Support for NatSemi SONIC based Ethernet devices. This includes
351 the onboard Ethernet in many Quadras as well as some LC-PDS,
352 a few Nubus and all known Comm Slot Ethernet cards. If you have
353 one of these say Y and read the Ethernet-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>.
356 To compile this driver as a module, choose M here. This module will
360 bool "Macintosh (AV) onboard MACE ethernet"
364 Support for the onboard AMD 79C940 MACE Ethernet controller used in
365 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
366 say Y and read the Ethernet-HOWTO, available from
367 <http://www.tldp.org/docs.html#howto>.
370 tristate "MVME16x Ethernet support"
373 This is the driver for the Ethernet interface on the Motorola
374 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
375 driver for this chip in your kernel.
376 To compile this driver as a module, choose M here.
379 tristate "BVME6000 Ethernet support"
382 This is the driver for the Ethernet interface on BVME4000 and
383 BVME6000 VME boards. Say Y here to include the driver for this chip
385 To compile this driver as a module, choose M here.
388 bool "Sun3 on-board Intel 82586 support"
391 This driver enables support for the on-board Intel 82586 based
392 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
393 that this driver does not support 82586-based adapters on additional
397 tristate "Lasi ethernet"
400 Say Y here to support the builtin Intel 82596 ethernet controller
401 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
404 tristate "SNI RM ethernet"
405 depends on NET_ETHERNET && SNI_RM
407 Say Y here to support the on-board Intel 82596 ethernet controller
408 built into SNI RM machines.
411 tristate "Korina (IDT RC32434) Ethernet support"
412 depends on NET_ETHERNET && MIKROTIK_RB532
414 If you have a Mikrotik RouterBoard 500 or IDT RC32434
415 based system say Y. Otherwise say N.
417 config MIPS_JAZZ_SONIC
418 tristate "MIPS JAZZ onboard SONIC Ethernet support"
421 This is the driver for the onboard card of MIPS Magnum 4000,
422 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
424 config XTENSA_XT2000_SONIC
425 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
426 depends on XTENSA_PLATFORM_XT2000
428 This is the driver for the onboard card of the Xtensa XT2000 board.
431 bool "SGI IOC3 Ethernet"
432 depends on PCI && SGI_IP27
436 If you have a network (Ethernet) card of this type, say Y and read
437 the Ethernet-HOWTO, available from
438 <http://www.tldp.org/docs.html#howto>.
441 tristate "MIPS simulator Network device"
444 The MIPSNET device is a simple Ethernet network device which is
445 emulated by the MIPS Simulator.
446 If you are not using a MIPSsim or are unsure, say N.
448 config SGI_O2MACE_ETH
449 tristate "SGI O2 MACE Fast Ethernet support"
450 depends on SGI_IP32=y
453 tristate "National DP83902AV support"
457 Support for cards based on the National Semiconductor DP83902AV
458 ST-NIC Serial Network Interface Controller for Twisted Pair. This
459 is a 10Mbit/sec Ethernet controller. Product overview and specs at
460 <http://www.national.com/pf/DP/DP83902A.html>.
465 tristate "Renesas SuperH Ethernet support"
466 depends on SUPERH && \
467 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
468 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
469 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
475 Renesas SuperH Ethernet device driver.
476 This driver supporting CPUs are:
477 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
480 tristate "Sun Happy Meal 10/100baseT support"
481 depends on SBUS || PCI
484 This driver supports the "hme" interface present on most Ultra
485 systems and as an option on older Sbus systems. This driver supports
486 both PCI and Sbus devices. This driver also supports the "qfe" quad
487 100baseT device available in both PCI and Sbus configurations.
489 To compile this driver as a module, choose M here: the module
490 will be called sunhme.
493 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
494 depends on SBUS && EXPERIMENTAL
497 This driver supports the "be" interface available as an Sbus option.
498 This is Sun's older 100baseT Ethernet device.
500 To compile this driver as a module, choose M here: the module
501 will be called sunbmac.
504 tristate "Sun QuadEthernet support"
508 This driver supports the "qe" 10baseT Ethernet device, available as
509 an Sbus option. Note that this is not the same as Quad FastEthernet
510 "qfe" which is supported by the Happy Meal driver instead.
512 To compile this driver as a module, choose M here: the module
513 will be called sunqe.
516 tristate "Sun GEM support"
520 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
521 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
524 tristate "Sun Cassini support"
528 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
529 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
532 tristate "Sun Virtual Network support"
535 Support for virtual network devices under Sun Logical Domains.
538 tristate "3c503 \"EtherLink II\" support"
542 If you have a network (Ethernet) card of this type, say Y and read
543 the Ethernet-HOWTO, available from
544 <http://www.tldp.org/docs.html#howto>.
546 To compile this driver as a module, choose M here. The module
547 will be called 3c503.
550 tristate "3c505 \"EtherLink Plus\" support"
551 depends on ISA && ISA_DMA_API
553 Information about this network (Ethernet) card can be found in
554 <file:Documentation/networking/3c505.txt>. If you have a card of
555 this type, say Y and read the Ethernet-HOWTO, available from
556 <http://www.tldp.org/docs.html#howto>.
558 To compile this driver as a module, choose M here. The module
559 will be called 3c505.
562 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
563 depends on ISA && EXPERIMENTAL
565 If you have a network (Ethernet) card of this type, say Y and read
566 the Ethernet-HOWTO, available from
567 <http://www.tldp.org/docs.html#howto>.
569 To compile this driver as a module, choose M here. The module
570 will be called 3c507.
573 tristate "3c523 \"EtherLink/MC\" support"
574 depends on MCA_LEGACY
576 If you have a network (Ethernet) card of this type, say Y and read
577 the Ethernet-HOWTO, available from
578 <http://www.tldp.org/docs.html#howto>.
580 To compile this driver as a module, choose M here. The module
581 will be called 3c523.
584 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
585 depends on MCA && MCA_LEGACY
587 If you have a network (Ethernet) card of this type, say Y and read
588 the Ethernet-HOWTO, available from
589 <http://www.tldp.org/docs.html#howto>.
591 To compile this driver as a module, choose M here. The module
592 will be called 3c527.
594 config NET_VENDOR_SMC
595 bool "Western Digital/SMC cards"
596 depends on ISA || MCA || EISA || MAC
598 If you have a network (Ethernet) card belonging to this class, say Y
599 and read the Ethernet-HOWTO, available from
600 <http://www.tldp.org/docs.html#howto>.
602 Note that the answer to this question doesn't directly affect the
603 kernel: saying N will just cause the configurator to skip all
604 the questions about Western Digital cards. If you say Y, you will be
605 asked for your specific card in the following questions.
608 tristate "WD80*3 support"
609 depends on NET_VENDOR_SMC && ISA
612 If you have a network (Ethernet) card of this type, say Y and read
613 the Ethernet-HOWTO, available from
614 <http://www.tldp.org/docs.html#howto>.
616 To compile this driver as a module, choose M here. The module
620 tristate "SMC Ultra MCA support"
621 depends on NET_VENDOR_SMC && MCA
624 If you have a network (Ethernet) card of this type and are running
625 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
626 available from <http://www.tldp.org/docs.html#howto>.
628 To compile this driver as a module, choose M here. The module
629 will be called smc-mca.
632 tristate "SMC Ultra support"
633 depends on NET_VENDOR_SMC && ISA
636 If you have a network (Ethernet) card of this type, say Y and read
637 the Ethernet-HOWTO, available from
638 <http://www.tldp.org/docs.html#howto>.
640 Important: There have been many reports that, with some motherboards
641 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
642 such as some BusLogic models) causes corruption problems with many
643 operating systems. The Linux smc-ultra driver has a work-around for
644 this but keep it in mind if you have such a SCSI card and have
647 To compile this driver as a module, choose M here. The module
648 will be called smc-ultra.
651 tristate "SMC Ultra32 EISA support"
652 depends on NET_VENDOR_SMC && EISA
655 If you have a network (Ethernet) card of this type, say Y and read
656 the Ethernet-HOWTO, available from
657 <http://www.tldp.org/docs.html#howto>.
659 To compile this driver as a module, choose M here. The module
660 will be called smc-ultra32.
663 tristate "Blackfin on-chip MAC support"
664 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
668 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
670 This is the driver for Blackfin on-chip mac device. Say Y if you want it
671 compiled into the kernel. This driver is also available as a module
672 ( = code which can be inserted in and removed from the running kernel
673 whenever you want). The module will be called bfin_mac.
675 config BFIN_MAC_USE_L1
676 bool "Use L1 memory for rx/tx packets"
677 depends on BFIN_MAC && (BF527 || BF537)
680 To get maximum network performance, you should use L1 memory as rx/tx buffers.
681 Say N here if you want to reserve L1 memory for other uses.
683 config BFIN_TX_DESC_NUM
684 int "Number of transmit buffer packets"
686 range 6 10 if BFIN_MAC_USE_L1
690 Set the number of buffer packets used in driver.
692 config BFIN_RX_DESC_NUM
693 int "Number of receive buffer packets"
695 range 20 100 if BFIN_MAC_USE_L1
699 Set the number of buffer packets used in driver.
701 config BFIN_MAC_USE_HWSTAMP
702 bool "Use IEEE 1588 hwstamp"
703 depends on BFIN_MAC && BF518
706 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
709 tristate "SMC 9194 support"
710 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
713 This is support for the SMC9xxx based Ethernet cards. Choose this
714 option if you have a DELL laptop with the docking station, or
715 another SMC9192/9194 based chipset. Say Y if you want it compiled
716 into the kernel, and read the file
717 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
718 available from <http://www.tldp.org/docs.html#howto>.
720 To compile this driver as a module, choose M here. The module
721 will be called smc9194.
724 tristate "SMC 91C9x/91C1xxx support"
727 depends on ARM || M32R || SUPERH || \
728 MIPS || BLACKFIN || MN10300 || COLDFIRE
730 This is a driver for SMC's 91x series of Ethernet chipsets,
731 including the SMC91C94 and the SMC91C111. Say Y if you want it
732 compiled into the kernel, and read the file
733 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
734 available from <http://www.tldp.org/docs.html#howto>.
736 This driver is also available as a module ( = code which can be
737 inserted in and removed from the running kernel whenever you want).
738 The module will be called smc91x. If you want to compile it as a
739 module, say M here and read <file:Documentation/kbuild/modules.txt>.
742 tristate "Marvell pxa168 ethernet support"
743 depends on CPU_PXA168
746 This driver supports the pxa168 Ethernet ports.
748 To compile this driver as a module, choose M here. The module
749 will be called pxa168_eth.
752 tristate "NetX Ethernet support"
756 This is support for the Hilscher netX builtin Ethernet ports
758 To compile this driver as a module, choose M here. The module
759 will be called netx-eth.
761 config TI_DAVINCI_EMAC
762 tristate "TI DaVinci EMAC Support"
763 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
764 select TI_DAVINCI_MDIO
765 select TI_DAVINCI_CPDMA
768 This driver supports TI's DaVinci Ethernet .
770 To compile this driver as a module, choose M here: the module
771 will be called davinci_emac_driver. This is recommended.
773 config TI_DAVINCI_MDIO
774 tristate "TI DaVinci MDIO Support"
775 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
778 This driver supports TI's DaVinci MDIO module.
780 To compile this driver as a module, choose M here: the module
781 will be called davinci_mdio. This is recommended.
783 config TI_DAVINCI_CPDMA
784 tristate "TI DaVinci CPDMA Support"
785 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
787 This driver supports TI's DaVinci CPDMA dma engine.
789 To compile this driver as a module, choose M here: the module
790 will be called davinci_cpdma. This is recommended.
793 tristate "DM9000 support"
794 depends on ARM || BLACKFIN || MIPS
798 Support for DM9000 chipset.
800 To compile this driver as a module, choose M here. The module
801 will be called dm9000.
803 config DM9000_DEBUGLEVEL
804 int "DM9000 maximum debug level"
808 The maximum level of debugging code compiled into the DM9000
811 config DM9000_FORCE_SIMPLE_PHY_POLL
812 bool "Force simple NSR based PHY polling"
815 This configuration forces the DM9000 to use the NSR's LinkStatus
816 bit to determine if the link is up or down instead of the more
817 costly MII PHY reads. Note, this will not work if the chip is
818 operating with an external PHY.
821 tristate "ENC28J60 support"
822 depends on EXPERIMENTAL && SPI && NET_ETHERNET
825 Support for the Microchip EN28J60 ethernet chip.
827 To compile this driver as a module, choose M here. The module will be
830 config ENC28J60_WRITEVERIFY
831 bool "Enable write verify"
834 Enable the verify after the buffer write useful for debugging purpose.
838 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
839 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
845 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
848 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
853 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
856 tristate "SMSC LAN911[5678] support"
859 depends on ARM || SUPERH || MN10300
861 This is a driver for SMSC's LAN911x series of Ethernet chipsets
862 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
863 Say Y if you want it compiled into the kernel,
864 and read the Ethernet-HOWTO, available from
865 <http://www.tldp.org/docs.html#howto>.
867 This driver is also available as a module. The module will be
868 called smc911x. If you want to compile it as a module, say M
869 here and read <file:Documentation/kbuild/modules.txt>
872 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
873 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
878 Say Y here if you want support for SMSC LAN911x and LAN921x families
879 of ethernet controllers.
881 To compile this driver as a module, choose M here and read
882 <file:Documentation/networking/net-modules.txt>. The module
883 will be called smsc911x.
885 config SMSC911X_ARCH_HOOKS
889 If the arch enables this, it allows the arch to implement various
890 hooks for more comprehensive interrupt control and also to override
891 the source of the MAC address.
893 config NET_VENDOR_RACAL
894 bool "Racal-Interlan (Micom) NI cards"
897 If you have a network (Ethernet) card belonging to this class, such
898 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
899 available from <http://www.tldp.org/docs.html#howto>.
901 Note that the answer to this question doesn't directly affect the
902 kernel: saying N will just cause the configurator to skip all
903 the questions about NI cards. If you say Y, you will be asked for
904 your specific card in the following questions.
907 tristate "NI5010 support (EXPERIMENTAL)"
908 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
910 If you have a network (Ethernet) card of this type, say Y and read
911 the Ethernet-HOWTO, available from
912 <http://www.tldp.org/docs.html#howto>. Note that this is still
915 To compile this driver as a module, choose M here. The module
916 will be called ni5010.
919 tristate "NI5210 support"
920 depends on NET_VENDOR_RACAL && ISA
922 If you have a network (Ethernet) card of this type, say Y and read
923 the Ethernet-HOWTO, available from
924 <http://www.tldp.org/docs.html#howto>.
926 To compile this driver as a module, choose M here. The module
930 tristate "Dave ethernet support (DNET)"
931 depends on NET_ETHERNET && HAS_IOMEM
934 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
935 Say Y to include support for the DNET chip.
937 To compile this driver as a module, choose M here: the module
940 source "drivers/net/tulip/Kconfig"
943 tristate "AT1700/1720 support (EXPERIMENTAL)"
944 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
947 If you have a network (Ethernet) card of this type, say Y and read
948 the Ethernet-HOWTO, available from
949 <http://www.tldp.org/docs.html#howto>.
951 To compile this driver as a module, choose M here. The module
952 will be called at1700.
955 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
956 depends on ISA || EISA || PCI
958 If you have a network (Ethernet) card of this type, say Y and read
959 the Ethernet-HOWTO, available from
960 <http://www.tldp.org/docs.html#howto>.
962 To compile this driver as a module, choose M here. The module
963 will be called hp100.
966 bool "Other ISA cards"
969 If your network (Ethernet) card hasn't been mentioned yet and its
970 bus system (that's the way the cards talks to the other components
971 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
972 Make sure you know the name of your card. Read the Ethernet-HOWTO,
973 available from <http://www.tldp.org/docs.html#howto>.
977 Note that the answer to this question doesn't directly affect the
978 kernel: saying N will just cause the configurator to skip all
979 the remaining ISA network card questions. If you say Y, you will be
980 asked for your specific card in the following questions.
983 tristate "Cabletron E21xx support"
987 If you have a network (Ethernet) card of this type, say Y and read
988 the Ethernet-HOWTO, available from
989 <http://www.tldp.org/docs.html#howto>.
991 To compile this driver as a module, choose M here. The module
992 will be called e2100.
995 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
999 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1000 cards. If this is for you, say Y and read
1001 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1002 well as the Ethernet-HOWTO, available from
1003 <http://www.tldp.org/docs.html#howto>.
1005 To compile this driver as a module, choose M here. The module
1006 will be called ewrk3.
1009 tristate "EtherExpress 16 support"
1012 If you have an EtherExpress16 network (Ethernet) card, say Y and
1013 read the Ethernet-HOWTO, available from
1014 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1015 EtherExpress16 card used to be regarded as a very poor choice
1016 because the driver was very unreliable. We now have a new driver
1017 that should do better.
1019 To compile this driver as a module, choose M here. The module
1020 will be called eexpress.
1023 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1026 If you have a network (Ethernet) card of this type, say Y. This
1027 driver supports Intel i82595{FX,TX} based boards. Note however
1028 that the EtherExpress PRO/100 Ethernet card has its own separate
1029 driver. Please read the Ethernet-HOWTO, available from
1030 <http://www.tldp.org/docs.html#howto>.
1032 To compile this driver as a module, choose M here. The module
1033 will be called eepro.
1036 tristate "HP PCLAN+ (27247B and 27252A) support"
1040 If you have a network (Ethernet) card of this type, say Y and read
1041 the Ethernet-HOWTO, available from
1042 <http://www.tldp.org/docs.html#howto>.
1044 To compile this driver as a module, choose M here. The module
1045 will be called hp-plus.
1048 tristate "HP PCLAN (27245 and other 27xxx series) support"
1052 If you have a network (Ethernet) card of this type, say Y and read
1053 the Ethernet-HOWTO, available from
1054 <http://www.tldp.org/docs.html#howto>.
1056 To compile this driver as a module, choose M here. The module
1060 tristate "LP486E on board Ethernet"
1063 Say Y here to support the 82596-based on-board Ethernet controller
1064 for the Panther motherboard, which is one of the two shipped in the
1065 Intel Professional Workstation.
1068 tristate "ICL EtherTeam 16i/32 support"
1071 If you have a network (Ethernet) card of this type, say Y and read
1072 the Ethernet-HOWTO, available from
1073 <http://www.tldp.org/docs.html#howto>.
1075 To compile this driver as a module, choose M here. The module
1076 will be called eth16i.
1079 tristate "NE2000/NE1000 support"
1080 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1083 If you have a network (Ethernet) card of this type, say Y and read
1084 the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1086 without a specific driver are compatible with NE2000.
1088 If you have a PCI NE2000 card however, say N here and Y to "PCI
1089 NE2000 and clone support" under "EISA, VLB, PCI and on board
1090 controllers" below. If you have a NE2000 card and are running on
1091 an MCA system (a bus system used on some IBM PS/2 computers and
1092 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1095 To compile this driver as a module, choose M here. The module
1099 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1100 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1102 The Zenith Z-Note notebook computer has a built-in network
1103 (Ethernet) card, and this is the Linux driver for it. Note that the
1104 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1105 by this driver. Read the Ethernet-HOWTO, available from
1106 <http://www.tldp.org/docs.html#howto>.
1109 tristate "SEEQ8005 support (EXPERIMENTAL)"
1110 depends on NET_ISA && EXPERIMENTAL
1112 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1113 is for you, read the Ethernet-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>.
1116 To compile this driver as a module, choose M here. The module
1117 will be called seeq8005.
1120 tristate "NE/2 (ne2000 MCA version) support"
1121 depends on MCA_LEGACY
1124 If you have a network (Ethernet) card of this type, say Y and read
1125 the Ethernet-HOWTO, available from
1126 <http://www.tldp.org/docs.html#howto>.
1128 To compile this driver as a module, choose M here. The module
1132 tristate "IBM LAN Adapter/A support"
1135 This is a Micro Channel Ethernet adapter. You need to set
1136 CONFIG_MCA to use this driver. It is both available as an in-kernel
1137 driver and as a module.
1139 To compile this driver as a module, choose M here. The only
1140 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1141 will both support 16K and 32K memory windows, however a 32K window
1142 gives a better security against packet losses. Usage of multiple
1143 boards with this driver should be possible, but has not been tested
1144 up to now due to lack of hardware.
1147 tristate "IBM LAN Virtual Ethernet support"
1148 depends on PPC_PSERIES
1150 This driver supports virtual ethernet adapters on newer IBM iSeries
1151 and pSeries systems.
1153 To compile this driver as a module, choose M here. The module will
1156 source "drivers/net/ibm_newemac/Kconfig"
1159 bool "EISA, VLB, PCI and on board controllers"
1160 depends on ISA || EISA || PCI
1162 This is another class of network cards which attach directly to the
1163 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1164 available from <http://www.tldp.org/docs.html#howto>.
1166 Note that the answer to this question doesn't directly affect the
1167 kernel: saying N will just cause the configurator to skip all
1168 the questions about this class of network cards. If you say Y, you
1169 will be asked for your specific card in the following questions. If
1170 you are unsure, say Y.
1172 config ADAPTEC_STARFIRE
1173 tristate "Adaptec Starfire/DuraLAN support"
1174 depends on NET_PCI && PCI
1178 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1179 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1180 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1183 To compile this driver as a module, choose M here: the module
1184 will be called starfire. This is recommended.
1187 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1188 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1191 If you have a network (Ethernet) card of this type, say Y and read
1192 the Ethernet-HOWTO, available from
1193 <http://www.tldp.org/docs.html#howto>.
1195 To compile this driver as a module, choose M here. The module
1196 will be called ac3200.
1199 tristate "Micrel KSZ8841/2 PCI"
1200 depends on NET_PCI && PCI
1204 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1206 To compile this driver as a module, choose M here. The module
1207 will be called ksz884x.
1210 tristate "Apricot Xen-II on board Ethernet"
1211 depends on NET_PCI && ISA
1213 If you have a network (Ethernet) controller of this type, say Y and
1214 read the Ethernet-HOWTO, available from
1215 <http://www.tldp.org/docs.html#howto>.
1217 To compile this driver as a module, choose M here. The module
1218 will be called apricot.
1221 tristate "Broadcom 440x/47xx ethernet support"
1222 depends on SSB_POSSIBLE && HAS_DMA
1226 If you have a network (Ethernet) controller of this type, say Y
1227 or M and read the Ethernet-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here. The module
1233 # Auto-select SSB PCI-HOST support, if possible
1234 config B44_PCI_AUTOSELECT
1236 depends on B44 && SSB_PCIHOST_POSSIBLE
1240 # Auto-select SSB PCICORE driver, if possible
1241 config B44_PCICORE_AUTOSELECT
1243 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1244 select SSB_DRIVER_PCICORE
1249 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1253 tristate "nForce Ethernet support"
1254 depends on NET_PCI && PCI
1256 If you have a network (Ethernet) controller of this type, say Y and
1257 read the Ethernet-HOWTO, available from
1258 <http://www.tldp.org/docs.html#howto>.
1260 To compile this driver as a module, choose M here. The module
1261 will be called forcedeth.
1264 tristate "CS89x0 support"
1265 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1266 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1268 Support for CS89x0 chipset based Ethernet cards. If you have a
1269 network (Ethernet) card of this type, say Y and read the
1270 Ethernet-HOWTO, available from
1271 <http://www.tldp.org/docs.html#howto> as well as
1272 <file:Documentation/networking/cs89x0.txt>.
1274 To compile this driver as a module, choose M here. The module
1275 will be called cs89x0.
1277 config CS89x0_NONISA_IRQ
1279 depends on CS89x0 != n
1280 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1283 tristate "TOSHIBA TC35815 Ethernet support"
1284 depends on NET_PCI && PCI && MIPS
1288 tristate "Intel(R) PRO/100+ support"
1289 depends on NET_PCI && PCI
1292 This driver supports Intel(R) PRO/100 family of adapters.
1293 To verify that your adapter is supported, find the board ID number
1294 on the adapter. Look for a label that has a barcode and a number
1295 in the format 123456-001 (six digits hyphen three digits).
1297 Use the above information and the Adapter & Driver ID Guide at:
1299 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1301 to identify the adapter.
1303 For the latest Intel PRO/100 network driver for Linux, see:
1305 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1307 More specific information on configuring the driver is in
1308 <file:Documentation/networking/e100.txt>.
1310 To compile this driver as a module, choose M here. The module
1311 will be called e100.
1314 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1315 depends on NET_PCI && EISA && EXPERIMENTAL
1318 If you have a network (Ethernet) card of this type, say Y and read
1319 the Ethernet-HOWTO, available from
1320 <http://www.tldp.org/docs.html#howto>.
1322 To compile this driver as a module, choose M here. The module
1323 will be called lne390.
1326 tristate "Myson MTD-8xx PCI Ethernet support"
1327 depends on NET_PCI && PCI
1331 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1332 cards. <http://www.myson.com.tw/>
1335 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1336 depends on NET_PCI && PCI
1339 This driver is for the National Semiconductor DP83810 series,
1340 which is used in cards from PureData, NetGear, Linksys
1341 and others, including the 83815 chip.
1342 More specific information and updates are available from
1343 <http://www.scyld.com/network/natsemi.html>.
1346 tristate "PCI NE2000 and clones support (see help)"
1347 depends on NET_PCI && PCI
1350 This driver is for NE2000 compatible PCI cards. It will not work
1351 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1352 support" below). If you have a PCI NE2000 network (Ethernet) card,
1353 say Y and read the Ethernet-HOWTO, available from
1354 <http://www.tldp.org/docs.html#howto>.
1356 This driver also works for the following NE2000 clone cards:
1357 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1358 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1359 Holtek HT80232 Holtek HT80229
1361 To compile this driver as a module, choose M here. The module
1362 will be called ne2k-pci.
1365 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1366 depends on NET_PCI && EISA && EXPERIMENTAL
1369 If you have a network (Ethernet) card of this type, say Y and read
1370 the Ethernet-HOWTO, available from
1371 <http://www.tldp.org/docs.html#howto>. Note that this driver
1372 will NOT WORK for NE3200 cards as they are completely different.
1374 To compile this driver as a module, choose M here. The module
1375 will be called ne3210.
1378 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1379 depends on NET_PCI && EISA && EXPERIMENTAL
1382 If you have a network (Ethernet) card of this type, say Y and read
1383 the Ethernet-HOWTO, available from
1384 <http://www.tldp.org/docs.html#howto>.
1386 To compile this driver as a module, choose M here. The module
1387 will be called es3210.
1390 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1391 depends on NET_PCI && PCI && EXPERIMENTAL
1395 This is a driver for the Fast Ethernet PCI network cards based on
1396 the RTL8139C+ chips. If you have one of those, say Y and read
1397 the Ethernet-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>.
1400 To compile this driver as a module, choose M here: the module
1401 will be called 8139cp. This is recommended.
1404 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1405 depends on NET_PCI && PCI
1409 This is a driver for the Fast Ethernet PCI network cards based on
1410 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1411 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1413 To compile this driver as a module, choose M here: the module
1414 will be called 8139too. This is recommended.
1417 bool "Use PIO instead of MMIO"
1421 This instructs the driver to use programmed I/O ports (PIO) instead
1422 of PCI shared memory (MMIO). This can possibly solve some problems
1423 in case your mainboard has memory consistency issues. If unsure,
1426 config 8139TOO_TUNE_TWISTER
1427 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1430 This implements a function which might come in handy in case you
1431 are using low quality on long cabling. It is required for RealTek
1432 RTL-8139 revision K boards, and totally unused otherwise. It tries
1433 to match the transceiver to the cable characteristics. This is
1434 experimental since hardly documented by the manufacturer.
1438 bool "Support for older RTL-8129/8130 boards"
1441 This enables support for the older and uncommon RTL-8129 and
1442 RTL-8130 chips, which support MII via an external transceiver,
1443 instead of an internal one. Disabling this option will save some
1444 memory by making the code size smaller. If unsure, say Y.
1446 config 8139_OLD_RX_RESET
1447 bool "Use older RX-reset method"
1450 The 8139too driver was recently updated to contain a more rapid
1451 reset sequence, in the face of severe receive errors. This "new"
1452 RX-reset method should be adequate for all boards. But if you
1453 experience problems, you can enable this option to restore the
1454 old RX-reset behavior. If unsure, say N.
1457 tristate "RDC R6040 Fast Ethernet Adapter support"
1458 depends on NET_PCI && PCI
1463 This is a driver for the R6040 Fast Ethernet MACs found in the
1464 the RDC R-321x System-on-chips.
1466 To compile this driver as a module, choose M here: the module
1467 will be called r6040. This is recommended.
1470 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1471 depends on NET_PCI && PCI
1475 This is a driver for the Fast Ethernet PCI network cards based on
1476 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1477 SiS 630 and SiS 540 chipsets.
1479 This driver also supports AMD 79C901 HomePNA so that you can use
1480 your phone line as a network cable.
1482 To compile this driver as a module, choose M here: the module
1483 will be called sis900. This is recommended.
1486 tristate "SMC EtherPower II"
1487 depends on NET_PCI && PCI
1491 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1492 which is based on the SMC83c17x (EPIC/100).
1493 More specific information and updates are available from
1494 <http://www.scyld.com/network/epic100.html>.
1497 tristate "SMSC LAN9420 PCI ethernet adapter support"
1498 depends on NET_PCI && PCI
1503 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1504 Say Y if you want it compiled into the kernel,
1505 and read the Ethernet-HOWTO, available from
1506 <http://www.tldp.org/docs.html#howto>.
1508 This driver is also available as a module. The module will be
1509 called smsc9420. If you want to compile it as a module, say M
1510 here and read <file:Documentation/kbuild/modules.txt>
1513 tristate "Sundance Alta support"
1514 depends on NET_PCI && PCI
1518 This driver is for the Sundance "Alta" chip.
1519 More specific information and updates are available from
1520 <http://www.scyld.com/network/sundance.html>.
1522 config SUNDANCE_MMIO
1523 bool "Use MMIO instead of PIO"
1526 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1527 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1528 is known to solve bugs on certain chips.
1533 tristate "TI ThunderLAN support"
1534 depends on NET_PCI && (PCI || EISA)
1536 If you have a PCI Ethernet network card based on the ThunderLAN chip
1537 which is supported by this driver, say Y and read the
1538 Ethernet-HOWTO, available from
1539 <http://www.tldp.org/docs.html#howto>.
1541 Devices currently supported by this driver are Compaq Netelligent,
1542 Compaq NetFlex and Olicom cards. Please read the file
1543 <file:Documentation/networking/tlan.txt> for more details.
1545 To compile this driver as a module, choose M here. The module
1546 will be called tlan.
1548 Please email feedback to <torben.mathiasen@compaq.com>.
1551 tristate "Micrel KSZ8841/42 with generic bus interface"
1552 depends on HAS_IOMEM && DMA_ENGINE
1554 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1555 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1559 tristate "Micrel KS8851 SPI"
1564 SPI driver for Micrel KS8851 SPI attached network chip.
1567 tristate "Micrel KS8851 MLL"
1568 depends on HAS_IOMEM
1571 This platform driver is for Micrel KS8851 Address/data bus
1572 multiplexed network chip.
1575 tristate "VIA Rhine support"
1576 depends on NET_PCI && PCI
1580 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1581 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1582 Ethernet functions can also be found integrated on South Bridges
1585 To compile this driver as a module, choose M here. The module
1586 will be called via-rhine.
1588 config VIA_RHINE_MMIO
1589 bool "Use MMIO instead of PIO"
1590 depends on VIA_RHINE
1592 This instructs the driver to use PCI shared memory (MMIO) instead of
1593 programmed I/O ports (PIO). Enabling this gives an improvement in
1594 processing time in parts of the driver.
1599 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1600 depends on NET_PCI && PCI && EXPERIMENTAL
1603 This is a driver for the Fast Ethernet PCI network cards based on
1604 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1605 have one of these, say Y here.
1607 To compile this driver as a module, choose M here: the module
1608 will be called sc92031. This is recommended.
1611 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1612 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1615 TI AR7 CPMAC Ethernet support
1618 bool "Pocket and portable adapters"
1621 Cute little network (Ethernet) devices which attach to the parallel
1622 port ("pocket adapters"), commonly used with laptops. If you have
1623 one of those, say Y and read the Ethernet-HOWTO, available from
1624 <http://www.tldp.org/docs.html#howto>.
1626 If you want to plug a network (or some other) card into the PCMCIA
1627 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1628 credit card size extension cards used by all modern laptops), you
1629 need the pcmcia-cs package (location contained in the file
1630 <file:Documentation/Changes>) and you can say N here.
1632 Laptop users should read the Linux Laptop home page at
1633 <http://www.linux-on-laptops.com/> or
1634 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1636 Note that the answer to this question doesn't directly affect the
1637 kernel: saying N will just cause the configurator to skip all
1638 the questions about this class of network devices. If you say Y, you
1639 will be asked for your specific device in the following questions.
1642 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1643 depends on NET_POCKET && PARPORT && X86
1646 This is a network (Ethernet) device which attaches to your parallel
1647 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1648 available from <http://www.tldp.org/docs.html#howto>, if you
1649 want to use this. If you intend to use this driver, you should have
1650 said N to the "Parallel printer support", because the two drivers
1651 don't like each other.
1653 To compile this driver as a module, choose M here: the module
1657 tristate "D-Link DE600 pocket adapter support"
1658 depends on NET_POCKET && PARPORT
1660 This is a network (Ethernet) device which attaches to your parallel
1661 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1662 Ethernet-HOWTO, available from
1663 <http://www.tldp.org/docs.html#howto>, if you want to use
1664 this. It is possible to have several devices share a single parallel
1665 port and it is safe to compile the corresponding drivers into the
1668 To compile this driver as a module, choose M here: the module
1669 will be called de600.
1672 tristate "D-Link DE620 pocket adapter support"
1673 depends on NET_POCKET && PARPORT
1675 This is a network (Ethernet) device which attaches to your parallel
1676 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1677 Ethernet-HOWTO, available from
1678 <http://www.tldp.org/docs.html#howto>, if you want to use
1679 this. It is possible to have several devices share a single parallel
1680 port and it is safe to compile the corresponding drivers into the
1683 To compile this driver as a module, choose M here: the module
1684 will be called de620.
1687 tristate "SGI Seeq ethernet controller support"
1688 depends on SGI_HAS_SEEQ
1690 Say Y here if you have an Seeq based Ethernet network card. This is
1691 used in many Silicon Graphics machines.
1694 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1695 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1696 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1697 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1700 Say Y here if you want to use the built-in 10/100 Fast ethernet
1701 controller on some Motorola ColdFire and Freescale i.MX processors.
1704 tristate "MPC52xx FEC driver"
1705 depends on PPC_MPC52xx && PPC_BESTCOMM
1708 select PPC_BESTCOMM_FEC
1710 This option enables support for the MPC5200's on-chip
1711 Fast Ethernet Controller
1712 If compiled as module, it will be called fec_mpc52xx.
1714 config FEC_MPC52xx_MDIO
1715 bool "MPC52xx FEC MDIO bus driver"
1716 depends on FEC_MPC52xx
1719 The MPC5200's FEC can connect to the Ethernet either with
1720 an external MII PHY chip or 10 Mbps 7-wire interface
1721 (Motorola? industry standard).
1722 If your board uses an external PHY connected to FEC, enable this.
1723 If not sure, enable.
1724 If compiled as module, it will be called fec_mpc52xx_phy.
1727 tristate "NE2000 compatible support for H8/300"
1730 Say Y here if you want to use the NE2000 compatible
1731 controller on the Renesas H8/300 processor.
1734 tristate "Atheros L2 Fast Ethernet support"
1739 This driver supports the Atheros L2 fast ethernet adapter.
1741 To compile this driver as a module, choose M here. The module
1742 will be called atl2.
1744 config XILINX_EMACLITE
1745 tristate "Xilinx 10/100 Ethernet Lite support"
1746 depends on PPC32 || MICROBLAZE
1749 This driver supports the 10/100 Ethernet Lite from Xilinx.
1752 tristate "Broadcom 63xx internal mac support"
1757 This driver supports the ethernet MACs in the Broadcom 63xx
1758 MIPS chipset family (BCM63XX).
1761 tristate "Faraday FTMAC100 10/100 Ethernet support"
1765 This driver supports the FTMAC100 10/100 Ethernet controller
1766 from Faraday. It is used on Faraday A320, Andes AG101 and some
1767 other ARM/NDS32 SoC's.
1770 tristate "Lantiq SoC ETOP driver"
1771 depends on SOC_TYPE_XWAY
1773 Support for the MII0 inside the Lantiq SoC
1776 source "drivers/net/fs_enet/Kconfig"
1778 source "drivers/net/octeon/Kconfig"
1780 endif # NET_ETHERNET
1786 menuconfig NETDEV_1000
1787 bool "Ethernet (1000 Mbit)"
1791 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1792 type of Local Area Network (LAN) in universities and companies.
1794 Say Y here to get to see options for Gigabit Ethernet drivers.
1795 This option alone does not add any kernel code.
1796 Note that drivers supporting both 100 and 1000 MBit may be listed
1797 under "Ethernet (10 or 100MBit)" instead.
1799 If you say N, all options in this submenu will be skipped and disabled.
1804 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1808 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1810 D-Link DGE-550T Gigabit Ethernet Adapter.
1811 D-Link DL2000-based Gigabit Ethernet Adapter.
1812 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1814 To compile this driver as a module, choose M here: the
1815 module will be called dl2k.
1818 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1821 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1822 adapters. For more information on how to identify your adapter, go
1823 to the Adapter & Driver ID Guide at:
1825 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1827 For general information and support, go to the Intel support
1830 <http://support.intel.com>
1832 More specific information on configuring the driver is in
1833 <file:Documentation/networking/e1000.txt>.
1835 To compile this driver as a module, choose M here. The module
1836 will be called e1000.
1839 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1840 depends on PCI && (!SPARC32 || BROKEN)
1843 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1844 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1845 use the regular e1000 driver For more information on how to
1846 identify your adapter, go to the Adapter & Driver ID Guide at:
1848 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1850 For general information and support, go to the Intel support
1853 <http://support.intel.com>
1855 To compile this driver as a module, choose M here. The module
1856 will be called e1000e.
1859 tristate "IP1000 Gigabit Ethernet support"
1860 depends on PCI && EXPERIMENTAL
1863 This driver supports IP1000 gigabit Ethernet cards.
1865 To compile this driver as a module, choose M here: the module
1866 will be called ipg. This is recommended.
1869 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
1872 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
1873 adapters. For more information on how to identify your adapter, go
1874 to the Adapter & Driver ID Guide at:
1876 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1878 For general information and support, go to the Intel support
1881 <http://support.intel.com>
1883 More specific information on configuring the driver is in
1884 <file:Documentation/networking/e1000.txt>.
1886 To compile this driver as a module, choose M here. The module
1890 bool "Direct Cache Access (DCA) Support"
1892 depends on IGB && DCA && !(IGB=y && DCA=m)
1894 Say Y here if you want to use Direct Cache Access (DCA) in the
1895 driver. DCA is a method for warming the CPU cache before data
1896 is used, with the intent of lessening the impact of cache misses.
1899 tristate "Intel(R) 82576 Virtual Function Ethernet support"
1902 This driver supports Intel(R) 82576 virtual functions. For more
1903 information on how to identify your adapter, go to the Adapter &
1906 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1908 For general information and support, go to the Intel support
1911 <http://support.intel.com>
1913 More specific information on configuring the driver is in
1914 <file:Documentation/networking/e1000.txt>.
1916 To compile this driver as a module, choose M here. The module
1917 will be called igbvf.
1919 source "drivers/net/ixp2000/Kconfig"
1922 tristate "National Semiconductor DP83820 support"
1925 This is a driver for the National Semiconductor DP83820 series
1926 of gigabit ethernet MACs. Cards using this chipset include
1927 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1928 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1932 tristate "Packet Engines Hamachi GNIC-II support"
1936 If you have a Gigabit Ethernet card of this type, say Y and read
1937 the Ethernet-HOWTO, available from
1938 <http://www.tldp.org/docs.html#howto>.
1940 To compile this driver as a module, choose M here. The module will be
1944 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1945 depends on PCI && EXPERIMENTAL
1948 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1949 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1950 used by the Beowulf Linux cluster project. See
1951 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1952 information about this driver in particular and Beowulf in general.
1954 To compile this driver as a module, choose M here: the module
1955 will be called yellowfin. This is recommended.
1958 tristate "Realtek 8169 gigabit ethernet support"
1964 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1966 To compile this driver as a module, choose M here: the module
1967 will be called r8169. This is recommended.
1970 tristate "SB1250 Gigabit Ethernet support"
1971 depends on SIBYTE_SB1xxx_SOC
1974 This driver supports Gigabit Ethernet interfaces based on the
1975 Broadcom SiByte family of System-On-a-Chip parts. They include
1976 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
1979 To compile this driver as a module, choose M here: the module
1980 will be called sb1250-mac.
1983 tristate "SiS190/SiS191 gigabit ethernet support"
1988 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1989 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1990 appear in lan on motherboard designs which are based on SiS 965
1991 and SiS 966 south bridge.
1993 To compile this driver as a module, choose M here: the module
1994 will be called sis190. This is recommended.
1997 tristate "Marvell Yukon Gigabit Ethernet support"
2001 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2002 and related Gigabit Ethernet adapters. It is a new smaller driver
2003 with better performance and more complete ethtool support.
2005 It does not support the link failover and network management
2006 features that "portable" vendor supplied sk98lin driver does.
2008 This driver supports adapters based on the original Yukon chipset:
2009 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2010 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2012 It does not support the newer Yukon2 chipset: a separate driver,
2013 sky2, is provided for these adapters.
2015 To compile this driver as a module, choose M here: the module
2016 will be called skge. This is recommended.
2019 bool "Debugging interface"
2020 depends on SKGE && DEBUG_FS
2022 This option adds the ability to dump driver state for debugging.
2023 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2024 transmit and receive rings.
2029 bool "Support for older SysKonnect Genesis boards"
2032 This enables support for the older and uncommon SysKonnect Genesis
2033 chips, which support MII via an external transceiver, instead of
2034 an internal one. Disabling this option will save some memory
2035 by making code smaller. If unsure say Y.
2038 tristate "Marvell Yukon 2 support"
2042 This driver supports Gigabit Ethernet adapters based on the
2043 Marvell Yukon 2 chipset:
2044 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2045 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2047 There is companion driver for the older Marvell Yukon and
2048 SysKonnect Genesis based adapters: skge.
2050 To compile this driver as a module, choose M here: the module
2051 will be called sky2. This is recommended.
2054 bool "Debugging interface"
2055 depends on SKY2 && DEBUG_FS
2057 This option adds the ability to dump driver state for debugging.
2058 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2059 transmit and receive rings.
2064 tristate "VIA Velocity support"
2070 If you have a VIA "Velocity" based network card say Y here.
2072 To compile this driver as a module, choose M here. The module
2073 will be called via-velocity.
2076 tristate "Broadcom Tigon3 support"
2080 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2082 To compile this driver as a module, choose M here: the module
2083 will be called tg3. This is recommended.
2086 tristate "Broadcom NetXtremeII support"
2091 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2093 To compile this driver as a module, choose M here: the module
2094 will be called bnx2. This is recommended.
2097 tristate "Broadcom CNIC support"
2102 This driver supports offload features of Broadcom NetXtremeII
2103 gigabit Ethernet cards.
2105 To compile this driver as a module, choose M here: the module
2106 will be called cnic. This is recommended.
2109 tristate "Spider Gigabit Ethernet driver"
2110 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2113 This driver supports the Gigabit Ethernet chips present on the
2114 Cell Processor-Based Blades from IBM.
2117 tristate "Tundra TSI108 gigabit Ethernet support"
2118 depends on TSI108_BRIDGE
2120 This driver supports Tundra TSI108 gigabit Ethernet ports.
2121 To compile this driver as a module, choose M here: the module
2122 will be called tsi108_eth.
2125 tristate "PS3 Gigabit Ethernet driver"
2127 select PS3_SYS_MANAGER
2129 This driver supports the network device on the PS3 game
2130 console. This driver has built-in support for Ethernet.
2132 To compile this driver as a module, choose M here: the
2133 module will be called ps3_gelic.
2135 config GELIC_WIRELESS
2136 bool "PS3 Wireless support"
2138 depends on GELIC_NET
2141 This option adds the support for the wireless feature of PS3.
2142 If you have the wireless-less model of PS3 or have no plan to
2143 use wireless feature, disabling this option saves memory. As
2144 the driver automatically distinguishes the models, you can
2145 safely enable this option even if you have a wireless-less model.
2148 tristate "Freescale PQ MDIO"
2152 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2155 tristate "Gianfar Ethernet"
2161 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2162 and MPC86xx family of chips, and the FEC on the 8540.
2165 tristate "Freescale QE Gigabit Ethernet"
2166 depends on QUICC_ENGINE
2170 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2171 which is available on some Freescale SOCs.
2173 config UGETH_TX_ON_DEMAND
2174 bool "Transmit on Demand support"
2178 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2179 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2183 This driver supports the gigabit ethernet MACs in the
2184 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2185 in the Marvell Orion ARM SoC family.
2187 Some boards that use the Discovery chipset are the Momenco
2188 Ocelot C and Jaguar ATX and Pegasos II.
2190 config XILINX_LL_TEMAC
2191 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2192 depends on PPC || MICROBLAZE
2195 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2196 core used in Xilinx Spartan and Virtex FPGAs
2199 tristate "QLogic QLA3XXX Network Driver Support"
2202 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2204 To compile this driver as a module, choose M here: the module
2205 will be called qla3xxx.
2208 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2213 This driver supports the Atheros/Attansic L1 gigabit ethernet
2216 To compile this driver as a module, choose M here. The module
2217 will be called atl1.
2220 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2221 depends on PCI && EXPERIMENTAL
2225 This driver supports the Atheros L1E gigabit ethernet adapter.
2227 To compile this driver as a module, choose M here. The module
2228 will be called atl1e.
2231 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2232 depends on PCI && EXPERIMENTAL
2236 This driver supports the Atheros L1C gigabit ethernet adapter.
2238 To compile this driver as a module, choose M here. The module
2239 will be called atl1c.
2242 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2247 This driver supports the PCI-Express gigabit ethernet adapters
2248 based on JMicron JMC250 chipset.
2250 To compile this driver as a module, choose M here. The module
2254 tristate "S6105 GMAC ethernet support"
2255 depends on XTENSA_VARIANT_S6000
2258 This driver supports the on chip ethernet device on the
2259 S6105 xtensa processor.
2261 To compile this driver as a module, choose M here. The module
2262 will be called s6gmac.
2264 source "drivers/net/stmmac/Kconfig"
2267 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
2271 This is a gigabit ethernet driver for EG20T PCH.
2272 EG20T PCH is the platform controller hub that is used in Intel's
2273 general embedded platform.
2274 EG20T PCH has Gigabit Ethernet interface.
2275 Using this interface, it is able to access system devices connected
2276 to Gigabit Ethernet.
2277 This driver enables Gigabit Ethernet function.
2279 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
2280 Output Hub), ML7223.
2281 ML7223 IOH is for MP(Media Phone) use.
2282 ML7223 is companion chip for Intel Atom E6xx series.
2283 ML7223 is completely compatible for Intel EG20T PCH.
2286 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
2290 This driver supports the FTGMAC100 Gigabit Ethernet controller
2291 from Faraday. It is used on Faraday A369, Andes AG102 and some
2292 other ARM/NDS32 SoC's.
2297 # 10 Gigabit Ethernet
2300 menuconfig NETDEV_10000
2301 bool "Ethernet (10000 Mbit)"
2305 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2306 This option alone does not add any kernel code.
2308 If you say N, all options in this submenu will be skipped and disabled.
2316 tristate "Chelsio 10Gb Ethernet support"
2321 This driver supports Chelsio gigabit and 10-gigabit
2322 Ethernet cards. More information about adapter features and
2323 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2325 For general information about Chelsio and our products, visit
2326 our website at <http://www.chelsio.com>.
2328 For customer support, please visit our customer support page at
2329 <http://www.chelsio.com/support.html>.
2331 Please send feedback to <linux-bugs@chelsio.com>.
2333 To compile this driver as a module, choose M here: the module
2334 will be called cxgb.
2336 config CHELSIO_T1_1G
2337 bool "Chelsio gigabit Ethernet support"
2338 depends on CHELSIO_T1
2340 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2341 are using only 10G cards say 'N' here.
2344 tristate "Chelsio Communications T3 10Gb Ethernet support"
2345 depends on PCI && INET
2349 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2352 For general information about Chelsio and our products, visit
2353 our website at <http://www.chelsio.com>.
2355 For customer support, please visit our customer support page at
2356 <http://www.chelsio.com/support.html>.
2358 Please send feedback to <linux-bugs@chelsio.com>.
2360 To compile this driver as a module, choose M here: the module
2361 will be called cxgb3.
2364 tristate "Chelsio Communications T4 Ethernet support"
2369 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2372 For general information about Chelsio and our products, visit
2373 our website at <http://www.chelsio.com>.
2375 For customer support, please visit our customer support page at
2376 <http://www.chelsio.com/support.html>.
2378 Please send feedback to <linux-bugs@chelsio.com>.
2380 To compile this driver as a module choose M here; the module
2381 will be called cxgb4.
2384 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2387 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2388 adapters with PCI-E SR-IOV Virtual Functions.
2390 For general information about Chelsio and our products, visit
2391 our website at <http://www.chelsio.com>.
2393 For customer support, please visit our customer support page at
2394 <http://www.chelsio.com/support.html>.
2396 Please send feedback to <linux-bugs@chelsio.com>.
2398 To compile this driver as a module choose M here; the module
2399 will be called cxgb4vf.
2402 tristate "eHEA Ethernet support"
2403 depends on IBMEBUS && INET && SPARSEMEM
2406 This driver supports the IBM pSeries eHEA ethernet adapter.
2408 To compile the driver as a module, choose M here. The module
2409 will be called ehea.
2412 tristate "Cisco VIC Ethernet NIC Support"
2413 depends on PCI && INET
2415 This enables the support for the Cisco VIC Ethernet card.
2418 tristate "Intel(R) 10GbE PCI Express adapters support"
2419 depends on PCI && INET
2422 This driver supports Intel(R) 10GbE PCI Express family of
2423 adapters. For more information on how to identify your adapter, go
2424 to the Adapter & Driver ID Guide at:
2426 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2428 For general information and support, go to the Intel support
2431 <http://support.intel.com>
2433 To compile this driver as a module, choose M here. The module
2434 will be called ixgbe.
2437 bool "Direct Cache Access (DCA) Support"
2439 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2441 Say Y here if you want to use Direct Cache Access (DCA) in the
2442 driver. DCA is a method for warming the CPU cache before data
2443 is used, with the intent of lessening the impact of cache misses.
2446 bool "Data Center Bridging (DCB) Support"
2448 depends on IXGBE && DCB
2450 Say Y here if you want to use Data Center Bridging (DCB) in the
2456 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2459 This driver supports Intel(R) 82599 virtual functions. For more
2460 information on how to identify your adapter, go to the Adapter &
2463 <http://support.intel.com/support/network/sb/CS-008441.htm>
2465 For general information and support, go to the Intel support
2468 <http://support.intel.com>
2470 More specific information on configuring the driver is in
2471 <file:Documentation/networking/ixgbevf.txt>.
2473 To compile this driver as a module, choose M here. The module
2474 will be called ixgbevf. MSI-X interrupt support is required
2475 for this driver to work correctly.
2478 tristate "Intel(R) PRO/10GbE support"
2481 This driver supports Intel(R) PRO/10GbE family of adapters for
2482 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2483 instead. For more information on how to identify your adapter, go
2484 to the Adapter & Driver ID Guide at:
2486 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2488 For general information and support, go to the Intel support
2491 <http://support.intel.com>
2493 More specific information on configuring the driver is in
2494 <file:Documentation/networking/ixgb.txt>.
2496 To compile this driver as a module, choose M here. The module
2497 will be called ixgb.
2500 tristate "Exar Xframe 10Gb Ethernet Adapter"
2503 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2505 More specific information on configuring the driver is in
2506 <file:Documentation/networking/s2io.txt>.
2508 To compile this driver as a module, choose M here. The module
2509 will be called s2io.
2512 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2513 depends on PCI && INET
2515 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2516 I/O Virtualized Server Adapter.
2518 More specific information on configuring the driver is in
2519 <file:Documentation/networking/vxge.txt>.
2521 To compile this driver as a module, choose M here. The module
2522 will be called vxge.
2524 config VXGE_DEBUG_TRACE_ALL
2525 bool "Enabling All Debug trace statments in driver"
2529 Say Y here if you want to enabling all the debug trace statements in
2530 the vxge driver. By default only few debug trace statements are
2534 tristate "Myricom Myri-10G Ethernet support"
2535 depends on PCI && INET
2540 This driver supports Myricom Myri-10G Dual Protocol interface in
2541 Ethernet mode. If the eeprom on your board is not recent enough,
2542 you will need a newer firmware image.
2543 You may get this image or more information, at:
2545 <http://www.myri.com/scs/download-Myri10GE.html>
2547 To compile this driver as a module, choose M here. The module
2548 will be called myri10ge.
2551 bool "Direct Cache Access (DCA) Support"
2553 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2555 Say Y here if you want to use Direct Cache Access (DCA) in the
2556 driver. DCA is a method for warming the CPU cache before data
2557 is used, with the intent of lessening the impact of cache misses.
2560 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2564 This enables the support for NetXen's Gigabit Ethernet card.
2567 tristate "Sun Neptune 10Gbit Ethernet support"
2571 This enables support for cards based upon Sun's
2575 tristate "PA Semi 1/10Gbit MAC"
2576 depends on PPC_PASEMI && PCI && INET
2580 This driver supports the on-chip 1/10Gbit Ethernet controller on
2581 PA Semi's PWRficient line of chips.
2584 tristate "Mellanox Technologies 10Gbit Ethernet support"
2585 depends on PCI && INET
2589 This driver supports Mellanox Technologies ConnectX Ethernet
2598 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2599 depends on MLX4_CORE
2602 This option causes debugging code to be compiled into the
2603 mlx4_core driver. The output can be turned on via the
2604 debug_level module parameter (which can also be set after
2605 the driver is loaded through sysfs).
2608 tristate "Tehuti Networks 10G Ethernet"
2611 Tehuti Networks 10G Ethernet NIC
2614 tristate "Broadcom NetXtremeII 10Gb support"
2621 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2622 To compile this driver as a module, choose M here: the module
2623 will be called bnx2x. This is recommended.
2626 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2630 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2634 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2637 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2639 To compile this driver as a module, choose M here: the module
2640 will be called qlge.
2643 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2646 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2648 To compile this driver as a module, choose M here: the module
2651 For general information and support, go to the Brocade support
2654 <http://support.brocade.com>
2656 source "drivers/net/sfc/Kconfig"
2658 source "drivers/net/benet/Kconfig"
2660 endif # NETDEV_10000
2662 source "drivers/net/tokenring/Kconfig"
2664 source "drivers/net/wireless/Kconfig"
2666 source "drivers/net/wimax/Kconfig"
2668 source "drivers/net/usb/Kconfig"
2670 source "drivers/net/pcmcia/Kconfig"
2672 source "drivers/net/wan/Kconfig"
2674 source "drivers/atm/Kconfig"
2676 source "drivers/ieee802154/Kconfig"
2678 source "drivers/s390/net/Kconfig"
2680 source "drivers/net/caif/Kconfig"
2683 tristate "Tilera GBE/XGBE network driver support"
2688 This is a standard Linux network device driver for the
2689 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2691 To compile this driver as a module, choose M here: the module
2692 will be called tile_net.
2694 config XEN_NETDEV_FRONTEND
2695 tristate "Xen network device frontend driver"
2697 select XEN_XENBUS_FRONTEND
2700 This driver provides support for Xen paravirtual network
2701 devices exported by a Xen network driver domain (often
2704 The corresponding Linux backend driver is enabled by the
2705 CONFIG_XEN_NETDEV_BACKEND option.
2707 If you are compiling a kernel for use as Xen guest, you
2708 should say Y here. To compile this driver as a module, chose
2709 M here: the module will be called xen-netfront.
2711 config XEN_NETDEV_BACKEND
2712 tristate "Xen backend network device"
2713 depends on XEN_BACKEND
2715 This driver allows the kernel to act as a Xen network driver
2716 domain which exports paravirtual network devices to other
2717 Xen domains. These devices can be accessed by any operating
2718 system that implements a compatible front end.
2720 The corresponding Linux frontend driver is enabled by the
2721 CONFIG_XEN_NETDEV_FRONTEND configuration option.
2723 The backend driver presents a standard network device
2724 endpoint for each paravirtual network device to the driver
2725 domain network stack. These can then be bridged or routed
2726 etc in order to provide full network connectivity.
2728 If you are compiling a kernel to run in a Xen network driver
2729 domain (often this is domain 0) you should say Y here. To
2730 compile this driver as a module, chose M here: the module
2731 will be called xen-netback.
2734 tristate "iSeries Virtual Ethernet driver support"
2735 depends on PPC_ISERIES
2738 tristate "RapidIO Ethernet over messaging driver support"
2741 config RIONET_TX_SIZE
2742 int "Number of outbound queue entries"
2746 config RIONET_RX_SIZE
2747 int "Number of inbound queue entries"
2752 tristate "FDDI driver support"
2753 depends on (PCI || EISA || TC)
2755 Fiber Distributed Data Interface is a high speed local area network
2756 design; essentially a replacement for high speed Ethernet. FDDI can
2757 run over copper or fiber. If you are connected to such a network and
2758 want a driver for the FDDI card in your computer, say Y here (and
2759 then also Y to the driver for your FDDI card, below). Most people
2763 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2764 depends on FDDI && (PCI || EISA || TC)
2766 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2767 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2768 to a local FDDI network.
2770 To compile this driver as a module, choose M here: the module
2771 will be called defxx. If unsure, say N.
2775 prompt "Use MMIO instead of PIO" if PCI || EISA
2777 default n if PCI || EISA
2780 This instructs the driver to use EISA or PCI memory-mapped I/O
2781 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2782 Enabling this gives an improvement in processing time in parts
2783 of the driver, but it may cause problems with EISA (DEFEA)
2784 adapters. TURBOchannel does not have the concept of I/O ports,
2785 so MMIO is always used for these (DEFTA) adapters.
2790 tristate "SysKonnect FDDI PCI support"
2791 depends on FDDI && PCI
2794 Say Y here if you have a SysKonnect FDDI PCI adapter.
2795 The following adapters are supported by this driver:
2796 - SK-5521 (SK-NET FDDI-UP)
2797 - SK-5522 (SK-NET FDDI-UP DAS)
2798 - SK-5541 (SK-NET FDDI-FP)
2799 - SK-5543 (SK-NET FDDI-LP)
2800 - SK-5544 (SK-NET FDDI-LP DAS)
2801 - SK-5821 (SK-NET FDDI-UP64)
2802 - SK-5822 (SK-NET FDDI-UP64 DAS)
2803 - SK-5841 (SK-NET FDDI-FP64)
2804 - SK-5843 (SK-NET FDDI-LP64)
2805 - SK-5844 (SK-NET FDDI-LP64 DAS)
2806 - Netelligent 100 FDDI DAS Fibre SC
2807 - Netelligent 100 FDDI SAS Fibre SC
2808 - Netelligent 100 FDDI DAS UTP
2809 - Netelligent 100 FDDI SAS UTP
2810 - Netelligent 100 FDDI SAS Fibre MIC
2812 Read <file:Documentation/networking/skfp.txt> for information about
2815 Questions concerning this driver can be addressed to:
2816 <linux@syskonnect.de>
2818 To compile this driver as a module, choose M here: the module
2819 will be called skfp. This is recommended.
2822 bool "HIPPI driver support (EXPERIMENTAL)"
2823 depends on EXPERIMENTAL && INET && PCI
2825 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2826 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2827 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2828 single-mode). HIPPI networks are commonly used for clusters and to
2829 connect to super computers. If you are connected to a HIPPI network
2830 and have a HIPPI network card in your computer that you want to use
2831 under Linux, say Y here (you must also remember to enable the driver
2832 for your HIPPI card below). Most people will say N here.
2835 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2836 depends on HIPPI && PCI
2838 Say Y here if this is your PCI HIPPI network card.
2840 To compile this driver as a module, choose M here: the module
2841 will be called rrunner. If unsure, say N.
2843 config ROADRUNNER_LARGE_RINGS
2844 bool "Use large TX/RX rings (EXPERIMENTAL)"
2845 depends on ROADRUNNER
2847 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2848 of additional memory to allow for fastest operation, both for
2849 transmitting and receiving. This memory cannot be used by any other
2850 kernel code or by user space programs. Say Y here only if you have
2854 tristate "PLIP (parallel port) support"
2857 PLIP (Parallel Line Internet Protocol) is used to create a
2858 reasonably fast mini network consisting of two (or, rarely, more)
2859 local machines. A PLIP link from a Linux box is a popular means to
2860 install a Linux distribution on a machine which doesn't have a
2861 CD-ROM drive (a minimal system has to be transferred with floppies
2862 first). The kernels on both machines need to have this PLIP option
2863 enabled for this to work.
2865 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2866 ports (the connectors at the computers with 25 holes) are connected
2867 with "null printer" or "Turbo Laplink" cables which can transmit 4
2868 bits at a time (mode 0) or with special PLIP cables, to be used on
2869 bidirectional parallel ports only, which can transmit 8 bits at a
2870 time (mode 1); you can find the wiring of these cables in
2871 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2872 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2873 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2874 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2875 and winsock or NCSA's telnet.
2877 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2878 as the NET-3-HOWTO, both available from
2879 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2880 protocol has been changed and this PLIP driver won't work together
2881 with the PLIP support in Linux versions 1.0.x. This option enlarges
2882 your kernel by about 8 KB.
2884 To compile this driver as a module, choose M here. The module
2885 will be called plip. If unsure, say Y or M, in case you buy
2889 tristate "PPP (point-to-point protocol) support"
2892 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2893 the same purpose: sending Internet traffic over telephone (and other
2894 serial) lines. Ask your access provider if they support it, because
2895 otherwise you can't use it; most Internet access providers these
2896 days support PPP rather than SLIP.
2898 To use PPP, you need an additional program called pppd as described
2899 in the PPP-HOWTO, available at
2900 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2901 the version of pppd recommended in <file:Documentation/Changes>.
2902 The PPP option enlarges your kernel by about 16 KB.
2904 There are actually two versions of PPP: the traditional PPP for
2905 asynchronous lines, such as regular analog phone lines, and
2906 synchronous PPP which can be used over digital ISDN lines for
2907 example. If you want to use PPP over phone lines or other
2908 asynchronous serial lines, you need to say Y (or M) here and also to
2909 the next option, "PPP support for async serial ports". For PPP over
2910 synchronous lines, you should say Y (or M) here and to "Support
2911 synchronous PPP", below.
2913 If you said Y to "Version information on all symbols" above, then
2914 you cannot compile the PPP driver into the kernel; you can then only
2915 compile it as a module. To compile this driver as a module, choose M
2916 here. The module will be called ppp_generic.
2918 config PPP_MULTILINK
2919 bool "PPP multilink support (EXPERIMENTAL)"
2920 depends on PPP && EXPERIMENTAL
2922 PPP multilink is a protocol (defined in RFC 1990) which allows you
2923 to combine several (logical or physical) lines into one logical PPP
2924 connection, so that you can utilize your full bandwidth.
2926 This has to be supported at the other end as well and you need a
2927 version of the pppd daemon which understands the multilink protocol.
2932 bool "PPP filtering"
2935 Say Y here if you want to be able to filter the packets passing over
2936 PPP interfaces. This allows you to control which packets count as
2937 activity (i.e. which packets will reset the idle timer or bring up
2938 a demand-dialed link) and which packets are to be dropped entirely.
2939 You need to say Y here if you wish to use the pass-filter and
2940 active-filter options to pppd.
2945 tristate "PPP support for async serial ports"
2949 Say Y (or M) here if you want to be able to use PPP over standard
2950 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2951 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2954 To compile this driver as a module, choose M here.
2959 tristate "PPP support for sync tty ports"
2962 Say Y (or M) here if you want to be able to use PPP over synchronous
2963 (HDLC) tty devices, such as the SyncLink adapter. These devices
2964 are often used for high-speed leased lines like T1/E1.
2966 To compile this driver as a module, choose M here.
2969 tristate "PPP Deflate compression"
2974 Support for the Deflate compression method for PPP, which uses the
2975 Deflate algorithm (the same algorithm that gzip uses) to compress
2976 each PPP packet before it is sent over the wire. The machine at the
2977 other end of the PPP link (usually your ISP) has to support the
2978 Deflate compression method as well for this to be useful. Even if
2979 they don't support it, it is safe to say Y here.
2981 To compile this driver as a module, choose M here.
2984 tristate "PPP BSD-Compress compression"
2987 Support for the BSD-Compress compression method for PPP, which uses
2988 the LZW compression method to compress each PPP packet before it is
2989 sent over the wire. The machine at the other end of the PPP link
2990 (usually your ISP) has to support the BSD-Compress compression
2991 method as well for this to be useful. Even if they don't support it,
2992 it is safe to say Y here.
2994 The PPP Deflate compression method ("PPP Deflate compression",
2995 above) is preferable to BSD-Compress, because it compresses better
2998 Note that the BSD compression code will always be compiled as a
2999 module; it is called bsd_comp and will show up in the directory
3000 modules once you have said "make modules". If unsure, say N.
3003 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3004 depends on PPP && EXPERIMENTAL
3010 Support for the MPPE Encryption protocol, as employed by the
3011 Microsoft Point-to-Point Tunneling Protocol.
3013 See http://pptpclient.sourceforge.net/ for information on
3014 configuring PPTP clients and servers to utilize this method.
3017 tristate "PPP over Ethernet (EXPERIMENTAL)"
3018 depends on EXPERIMENTAL && PPP
3020 Support for PPP over Ethernet.
3022 This driver requires the latest version of pppd from the CVS
3023 repository at cvs.samba.org. Alternatively, see the
3024 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3025 which contains instruction on how to use this driver (under
3026 the heading "Kernel mode PPPoE").
3029 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3030 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3032 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3034 This driver requires pppd plugin to work in client mode or
3035 modified pptpd (poptop) to work in server mode.
3036 See http://accel-pptp.sourceforge.net/ for information how to
3037 utilize this module.
3040 tristate "PPP over ATM"
3041 depends on ATM && PPP
3043 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3044 This implementation does not yet comply with section 8 of RFC2364,
3045 which can lead to bad results if the ATM peer loses state and
3046 changes its encapsulation unilaterally.
3049 tristate "PPP over L2TP (EXPERIMENTAL)"
3050 depends on EXPERIMENTAL && L2TP && PPP
3052 Support for PPP-over-L2TP socket family. L2TP is a protocol
3053 used by ISPs and enterprises to tunnel PPP traffic over UDP
3054 tunnels. L2TP is replacing PPTP for VPN uses.
3057 tristate "SLIP (serial line) support"
3059 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3060 connect to your Internet service provider or to connect to some
3061 other local Unix box or if you want to configure your Linux box as a
3062 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3063 Internet Protocol) is a protocol used to send Internet traffic over
3064 serial connections such as telephone lines or null modem cables;
3065 nowadays, the protocol PPP is more commonly used for this same
3068 Normally, your access provider has to support SLIP in order for you
3069 to be able to use it, but there is now a SLIP emulator called SLiRP
3070 around (available from
3071 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3072 allows you to use SLIP over a regular dial up shell connection. If
3073 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3074 NET-3-HOWTO, available from
3075 <http://www.tldp.org/docs.html#howto>, explains how to
3076 configure SLIP. Note that you don't need this option if you just
3077 want to run term (term is a program which gives you almost full
3078 Internet connectivity if you have a regular dial up shell account on
3079 some Internet connected Unix computer. Read
3080 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3081 support will enlarge your kernel by about 4 KB. If unsure, say N.
3083 To compile this driver as a module, choose M here. The module
3084 will be called slip.
3086 config SLIP_COMPRESSED
3087 bool "CSLIP compressed headers"
3091 This protocol is faster than SLIP because it uses compression on the
3092 TCP/IP headers (not on the data itself), but it has to be supported
3093 on both ends. Ask your access provider if you are not sure and
3094 answer Y, just in case. You will still be able to use plain SLIP. If
3095 you plan to use SLiRP, the SLIP emulator (available from
3096 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3097 allows you to use SLIP over a regular dial up shell connection, you
3098 definitely want to say Y here. The NET-3-HOWTO, available from
3099 <http://www.tldp.org/docs.html#howto>, explains how to configure
3100 CSLIP. This won't enlarge your kernel.
3105 This option enables Van Jacobsen serial line header compression
3109 bool "Keepalive and linefill"
3112 Adds additional capabilities to the SLIP driver to support the
3113 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3116 config SLIP_MODE_SLIP6
3117 bool "Six bit SLIP encapsulation"
3120 Just occasionally you may need to run IP over hostile serial
3121 networks that don't pass all control characters or are only seven
3122 bit. Saying Y here adds an extra mode you can use with SLIP:
3123 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3124 the serial device. Naturally, this has to be supported at the other
3125 end of the link as well. It's good enough, for example, to run IP
3126 over the async ports of a Camtec JNT Pad. If unsure, say N.
3129 bool "Fibre Channel driver support"
3130 depends on SCSI && PCI
3132 Fibre Channel is a high speed serial protocol mainly used to connect
3133 large storage devices to the computer; it is compatible with and
3134 intended to replace SCSI.
3136 If you intend to use Fibre Channel, you need to have a Fibre channel
3137 adaptor card in your computer; say Y here and to the driver for your
3138 adaptor below. You also should have said Y to "SCSI support" and
3139 "SCSI generic support".
3142 tristate "Network console logging support"
3144 If you want to log kernel messages over the network, enable this.
3145 See <file:Documentation/networking/netconsole.txt> for details.
3147 config NETCONSOLE_DYNAMIC
3148 bool "Dynamic reconfiguration of logging targets"
3149 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
3150 !(NETCONSOLE=y && CONFIGFS_FS=m)
3152 This option enables the ability to dynamically reconfigure target
3153 parameters (interface, IP addresses, port numbers, MAC addresses)
3154 at runtime through a userspace interface exported using configfs.
3155 See <file:Documentation/networking/netconsole.txt> for details.
3161 bool "Netpoll traffic trapping"
3165 config NET_POLL_CONTROLLER
3169 tristate "Virtio network driver (EXPERIMENTAL)"
3170 depends on EXPERIMENTAL && VIRTIO
3172 This is the virtual network driver for virtio. It can be used with
3173 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3176 tristate "VMware VMXNET3 ethernet driver"
3177 depends on PCI && INET
3179 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3180 To compile this driver as a module, choose M here: the
3181 module will be called vmxnet3.