3 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
28 config NETDEVICES_MULTIQUEUE
29 bool "Netdevice multiple hardware queue support"
31 Say Y here if you want to allow the network stack to use multiple
32 hardware TX queues on an ethernet device.
34 Most people will say N here.
37 tristate "Intermediate Functional Block support"
38 depends on NET_CLS_ACT
40 This is an intermediate driver that allows sharing of
42 To compile this driver as a module, choose M here: the module
43 will be called ifb. If you want to use more than one ifb
44 device at a time, you need to compile this driver as a module.
45 Instead of 'ifb', the devices will then be called 'ifb0',
47 Look at the iproute2 documentation directory for usage etc
50 tristate "Dummy net driver support"
52 This is essentially a bit-bucket device (i.e. traffic you send to
53 this device is consigned into oblivion) with a configurable IP
54 address. It is most commonly used in order to make your currently
55 inactive SLIP address seem like a real address for local programs.
56 If you use SLIP or PPP, you might want to say Y here. Since this
57 thing often comes in handy, the default is Y. It won't enlarge your
58 kernel either. What a deal. Read about it in the Network
59 Administrator's Guide, available from
60 <http://www.tldp.org/docs.html#guide>.
62 To compile this driver as a module, choose M here: the module
63 will be called dummy. If you want to use more than one dummy
64 device at a time, you need to compile this driver as a module.
65 Instead of 'dummy', the devices will then be called 'dummy0',
69 tristate "Bonding driver support"
72 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
73 Channels together. This is called 'Etherchannel' by Cisco,
74 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
76 The driver supports multiple bonding modes to allow for both high
77 performance and high availability operation.
79 Refer to <file:Documentation/networking/bonding.txt> for more
82 To compile this driver as a module, choose M here: the module
83 will be called bonding.
86 tristate "MAC-VLAN support (EXPERIMENTAL)"
87 depends on EXPERIMENTAL
89 This allows one to create virtual interfaces that map packets to
90 or from specific MAC addresses to a particular interface.
92 To compile this driver as a module, choose M here: the module
93 will be called macvlan.
96 tristate "EQL (serial line load balancing) support"
98 If you have two serial connections to some other computer (this
99 usually requires two modems and two telephone lines) and you use
100 SLIP (the protocol for sending Internet traffic over telephone
101 lines) or PPP (a better SLIP) on them, you can make them behave like
102 one double speed connection using this driver. Naturally, this has
103 to be supported at the other end as well, either with a similar EQL
104 Linux driver or with a Livingston Portmaster 2e.
106 Say Y if you want this and read
107 <file:Documentation/networking/eql.txt>. You may also want to read
108 section 6.2 of the NET-3-HOWTO, available from
109 <http://www.tldp.org/docs.html#howto>.
111 To compile this driver as a module, choose M here: the module
112 will be called eql. If unsure, say N.
115 tristate "Universal TUN/TAP device driver support"
118 TUN/TAP provides packet reception and transmission for user space
119 programs. It can be viewed as a simple Point-to-Point or Ethernet
120 device, which instead of receiving packets from a physical media,
121 receives them from user space program and instead of sending packets
122 via physical media writes them to the user space program.
124 When a program opens /dev/net/tun, driver creates and registers
125 corresponding net device tunX or tapX. After a program closed above
126 devices, driver will automatically delete tunXX or tapXX device and
127 all routes corresponding to it.
129 Please read <file:Documentation/networking/tuntap.txt> for more
132 To compile this driver as a module, choose M here: the module
135 If you don't know what to use this for, you don't need it.
138 tristate "General Instruments Surfboard 1000"
141 This is a driver for the General Instrument (also known as
142 NextLevel) SURFboard 1000 internal
143 cable modem. This is an ISA card which is used by a number of cable
144 TV companies to provide cable modem access. It's a one-way
145 downstream-only cable modem, meaning that your upstream net link is
146 provided by your regular phone modem.
148 At present this driver only compiles as a module, so say M here if
149 you have this card. The module will be called sb1000. Then read
150 <file:Documentation/networking/README.sb1000> for information on how
151 to use this module, as it needs special ppp scripts for establishing
152 a connection. Further documentation and the necessary scripts can be
155 <http://www.jacksonville.net/~fventuri/>
156 <http://home.adelphia.net/~siglercm/sb1000.html>
157 <http://linuxpower.cx/~cable/>
159 If you don't have this card, of course say N.
161 source "drivers/net/arcnet/Kconfig"
163 source "drivers/net/phy/Kconfig"
169 menuconfig NET_ETHERNET
170 bool "Ethernet (10 or 100Mbit)"
173 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
174 type of Local Area Network (LAN) in universities and companies.
176 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
177 coaxial cable, linking computers in a chain), 10BASE-T or twisted
178 pair (10 Mbps over twisted pair cable, linking computers to central
179 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
180 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
181 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
182 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
183 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
184 Ethernet (1 Gbps over optical fiber or short copper links).
186 If your Linux machine will be connected to an Ethernet and you have
187 an Ethernet network interface card (NIC) installed in your computer,
188 say Y here and read the Ethernet-HOWTO, available from
189 <http://www.tldp.org/docs.html#howto>. You will then also have
190 to say Y to the driver for your particular NIC.
192 Note that the answer to this question won't directly affect the
193 kernel: saying N will just cause the configurator to skip all
194 the questions about Ethernet network cards. If unsure, say N.
199 tristate "Generic Media Independent Interface device support"
201 Most ethernet controllers have MII transceiver either as an external
202 or internal device. It is safe to say Y or M here even if your
203 ethernet card lack MII.
206 tristate "Atmel MACB support"
207 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263
210 The Atmel MACB ethernet interface is found on many AT32 and AT91
211 parts. Say Y to include support for the MACB chip.
213 To compile this driver as a module, choose M here: the module
216 source "drivers/net/arm/Kconfig"
219 tristate "ASIX AX88796 NE2000 clone support"
220 depends on ARM || MIPS
224 AX88796 driver, using platform bus to provide
225 chip detection and resources
228 tristate "MACE (Power Mac ethernet) support"
229 depends on PPC_PMAC && PPC32
232 Power Macintoshes and clones with Ethernet built-in on the
233 motherboard will usually use a MACE (Medium Access Control for
234 Ethernet) interface. Say Y to include support for the MACE chip.
236 To compile this driver as a module, choose M here: the module
239 config MACE_AAUI_PORT
240 bool "Use AAUI port instead of TP by default"
243 Some Apple machines (notably the Apple Network Server) which use the
244 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
245 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
246 Y here if you have such a machine. If unsure, say N.
247 The driver will default to AAUI on ANS anyway, and if you use it as
248 a module, you can provide the port_aaui=0|1 to force the driver.
251 tristate "BMAC (G3 ethernet) support"
252 depends on PPC_PMAC && PPC32
255 Say Y for support of BMAC Ethernet interfaces. These are used on G3
258 To compile this driver as a module, choose M here: the module
262 tristate "Ariadne support"
265 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
268 To compile this driver as a module, choose M here: the module
269 will be called ariadne.
272 tristate "A2065 support"
276 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
279 To compile this driver as a module, choose M here: the module
280 will be called a2065.
283 tristate "Hydra support"
287 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
289 To compile this driver as a module, choose M here: the module
290 will be called hydra.
293 tristate "Zorro NS8390-based Ethernet support"
297 This driver is for Zorro Ethernet cards using an NS8390-compatible
298 chipset, like the Village Tronic Ariadne II and the Individual
299 Computers X-Surf Ethernet cards. If you have such a card, say Y.
302 To compile this driver as a module, choose M here: the module
303 will be called zorro8390.
306 tristate "PCMCIA NE2000 support"
307 depends on AMIGA_PCMCIA
310 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
313 To compile this driver as a module, choose M here: the module
317 tristate "Apollo 3c505 support"
320 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
321 If you don't have one made for Apollos, you can use one from a PC,
322 except that your Apollo won't be able to boot from it (because the
323 code in the ROM will be for a PC).
326 bool "Macintosh NS 8390 based ethernet cards"
330 If you want to include a driver to support Nubus or LC-PDS
331 Ethernet cards using an NS8390 chipset or its equivalent, say Y
332 and read the Ethernet-HOWTO, available from
333 <http://www.tldp.org/docs.html#howto>.
336 tristate "Macintosh CS89x0 based ethernet cards"
339 Support for CS89x0 chipset based Ethernet cards. If you have a
340 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
341 read the Ethernet-HOWTO, available from
342 <http://www.tldp.org/docs.html#howto>.
344 To compile this driver as a module, choose M here and read
345 <file:Documentation/networking/net-modules.txt>. This module will
349 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
352 Support for NatSemi SONIC based Ethernet devices. This includes
353 the onboard Ethernet in many Quadras as well as some LC-PDS,
354 a few Nubus and all known Comm Slot Ethernet cards. If you have
355 one of these say Y and read the Ethernet-HOWTO, available from
356 <http://www.tldp.org/docs.html#howto>.
358 To compile this driver as a module, choose M here and read
359 <file:Documentation/networking/net-modules.txt>. This module will
363 bool "Macintosh (AV) onboard MACE ethernet"
367 Support for the onboard AMD 79C940 MACE Ethernet controller used in
368 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
369 say Y and read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
373 tristate "MVME147 (Lance) Ethernet support"
377 Support for the on-board Ethernet interface on the Motorola MVME147
378 single-board computer. Say Y here to include the
379 driver for this chip in your kernel.
380 To compile this driver as a module, choose M here.
383 tristate "MVME16x Ethernet support"
386 This is the driver for the Ethernet interface on the Motorola
387 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
388 driver for this chip in your kernel.
389 To compile this driver as a module, choose M here.
392 tristate "BVME6000 Ethernet support"
395 This is the driver for the Ethernet interface on BVME4000 and
396 BVME6000 VME boards. Say Y here to include the driver for this chip
398 To compile this driver as a module, choose M here.
401 tristate "Atari Lance support"
404 Say Y to include support for several Atari Ethernet adapters based
405 on the AMD Lance chipset: RieblCard (with or without battery), or
406 PAMCard VME (also the version by Rhotron, with different addresses).
409 tristate "BioNet-100 support"
410 depends on ATARI && ATARI_ACSI && BROKEN
412 Say Y to include support for BioData's BioNet-100 Ethernet adapter
413 for the ACSI port. The driver works (has to work...) with a polled
414 I/O scheme, so it's rather slow :-(
417 tristate "PAMsNet support"
418 depends on ATARI && ATARI_ACSI && BROKEN
420 Say Y to include support for the PAMsNet Ethernet adapter for the
421 ACSI port ("ACSI node"). The driver works (has to work...) with a
422 polled I/O scheme, so it's rather slow :-(
425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
435 If you're not building a kernel for a Sun 3, say N.
438 bool "Sun3 on-board Intel 82586 support"
441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional
447 bool "HP on-board LANCE support"
451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here.
455 tristate "Lasi ethernet"
458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM
465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines.
468 config MIPS_JAZZ_SONIC
469 tristate "MIPS JAZZ onboard SONIC Ethernet support"
472 This is the driver for the onboard card of MIPS Magnum 4000,
473 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
475 config MIPS_AU1X00_ENET
476 bool "MIPS AU1000 Ethernet support"
477 depends on SOC_AU1X00
481 If you have an Alchemy Semi AU1X00 based system
482 say Y. Otherwise, say N.
484 config NET_SB1250_MAC
485 tristate "SB1250 Ethernet support"
486 depends on SIBYTE_SB1xxx_SOC
489 bool "SGI IOC3 Ethernet"
490 depends on PCI && SGI_IP27
494 If you have a network (Ethernet) card of this type, say Y and read
495 the Ethernet-HOWTO, available from
496 <http://www.tldp.org/docs.html#howto>.
498 config SGI_IOC3_ETH_HW_RX_CSUM
499 bool "Receive hardware checksums"
500 depends on SGI_IOC3_ETH && INET
503 The SGI IOC3 network adapter supports TCP and UDP checksums in
504 hardware to offload processing of these checksums from the CPU. At
505 the moment only acceleration of IPv4 is supported. This option
506 enables offloading for checksums on receive. If unsure, say Y.
508 config SGI_IOC3_ETH_HW_TX_CSUM
509 bool "Transmit hardware checksums"
510 depends on SGI_IOC3_ETH && INET
513 The SGI IOC3 network adapter supports TCP and UDP checksums in
514 hardware to offload processing of these checksums from the CPU. At
515 the moment only acceleration of IPv4 is supported. This option
516 enables offloading for checksums on transmit. If unsure, say Y.
519 tristate "MIPS simulator Network device"
522 The MIPSNET device is a simple Ethernet network device which is
523 emulated by the MIPS Simulator.
524 If you are not using a MIPSsim or are unsure, say N.
526 config SGI_O2MACE_ETH
527 tristate "SGI O2 MACE Fast Ethernet support"
528 depends on SGI_IP32=y
531 tristate "National DP83902AV support"
535 Support for cards based on the National Semiconductor DP83902AV
536 ST-NIC Serial Network Interface Controller for Twisted Pair. This
537 is a 10Mbit/sec Ethernet controller. Product overview and specs at
538 <http://www.national.com/pf/DP/DP83902A.html>.
543 tristate "Sun LANCE support"
547 This driver supports the "le" interface present on all 32-bit Sparc
548 systems, on some older Ultra systems and as an Sbus option. These
549 cards are based on the AMD Lance chipset, which is better known
550 via the NE2100 cards.
552 To compile this driver as a module, choose M here: the module
553 will be called sunlance.
556 tristate "Sun Happy Meal 10/100baseT support"
557 depends on SBUS || PCI
560 This driver supports the "hme" interface present on most Ultra
561 systems and as an option on older Sbus systems. This driver supports
562 both PCI and Sbus devices. This driver also supports the "qfe" quad
563 100baseT device available in both PCI and Sbus configurations.
565 To compile this driver as a module, choose M here: the module
566 will be called sunhme.
569 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
570 depends on SBUS && EXPERIMENTAL
573 This driver supports the "be" interface available as an Sbus option.
574 This is Sun's older 100baseT Ethernet device.
576 To compile this driver as a module, choose M here: the module
577 will be called sunbmac.
580 tristate "Sun QuadEthernet support"
584 This driver supports the "qe" 10baseT Ethernet device, available as
585 an Sbus option. Note that this is not the same as Quad FastEthernet
586 "qfe" which is supported by the Happy Meal driver instead.
588 To compile this driver as a module, choose M here: the module
589 will be called sunqe.
592 tristate "Sun GEM support"
596 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
597 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
600 tristate "Sun Cassini support"
604 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
605 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
608 tristate "Sun Virtual Network support"
611 Support for virtual network devices under Sun Logical Domains.
613 config NET_VENDOR_3COM
615 depends on ISA || EISA || MCA || PCI
617 If you have a network (Ethernet) card belonging to this class, say Y
618 and read the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 Note that the answer to this question doesn't directly affect the
622 kernel: saying N will just cause the configurator to skip all
623 the questions about 3COM cards. If you say Y, you will be asked for
624 your specific card in the following questions.
627 tristate "3c501 \"EtherLink\" support"
628 depends on NET_VENDOR_3COM && ISA
630 If you have a network (Ethernet) card of this type, say Y and read
631 the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
633 new card, since the 3c501 is slow, broken, and obsolete: you will
634 have problems. Some people suggest to ping ("man ping") a nearby
635 machine every minute ("man cron") when using this card.
637 To compile this driver as a module, choose M here and read
638 <file:Documentation/networking/net-modules.txt>. The module
639 will be called 3c501.
642 tristate "3c503 \"EtherLink II\" support"
643 depends on NET_VENDOR_3COM && ISA
646 If you have a network (Ethernet) card of this type, say Y and read
647 the Ethernet-HOWTO, available from
648 <http://www.tldp.org/docs.html#howto>.
650 To compile this driver as a module, choose M here and read
651 <file:Documentation/networking/net-modules.txt>. The module
652 will be called 3c503.
655 tristate "3c505 \"EtherLink Plus\" support"
656 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
658 Information about this network (Ethernet) card can be found in
659 <file:Documentation/networking/3c505.txt>. If you have a card of
660 this type, say Y and read the Ethernet-HOWTO, available from
661 <http://www.tldp.org/docs.html#howto>.
663 To compile this driver as a module, choose M here and read
664 <file:Documentation/networking/net-modules.txt>. The module
665 will be called 3c505.
668 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
669 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
671 If you have a network (Ethernet) card of this type, say Y and read
672 the Ethernet-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 To compile this driver as a module, choose M here and read
676 <file:Documentation/networking/net-modules.txt>. The module
677 will be called 3c507.
680 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
681 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
683 If you have a network (Ethernet) card belonging to the 3Com
684 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
685 from <http://www.tldp.org/docs.html#howto>.
687 If your card is not working you may need to use the DOS
688 setup disk to disable Plug & Play mode, and to select the default
691 To compile this driver as a module, choose M here and read
692 <file:Documentation/networking/net-modules.txt>. The module
693 will be called 3c509.
696 tristate "3c515 ISA \"Fast EtherLink\""
697 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
699 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
700 network card, say Y and read the Ethernet-HOWTO, available from
701 <http://www.tldp.org/docs.html#howto>.
703 To compile this driver as a module, choose M here and read
704 <file:Documentation/networking/net-modules.txt>. The module
705 will be called 3c515.
708 tristate "3c523 \"EtherLink/MC\" support"
709 depends on NET_VENDOR_3COM && MCA_LEGACY
711 If you have a network (Ethernet) card of this type, say Y and read
712 the Ethernet-HOWTO, available from
713 <http://www.tldp.org/docs.html#howto>.
715 To compile this driver as a module, choose M here and read
716 <file:Documentation/networking/net-modules.txt>. The module
717 will be called 3c523.
720 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
721 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
723 If you have a network (Ethernet) card of this type, say Y and read
724 the Ethernet-HOWTO, available from
725 <http://www.tldp.org/docs.html#howto>.
727 To compile this driver as a module, choose M here and read
728 <file:Documentation/networking/net-modules.txt>. The module
729 will be called 3c527.
732 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
733 depends on NET_VENDOR_3COM && (PCI || EISA)
736 This option enables driver support for a large number of 10Mbps and
737 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
739 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
740 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
741 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
742 "Tornado" (3c905) PCI
743 "Hurricane" (3c555/3cSOHO) PCI
745 If you have such a card, say Y and read the Ethernet-HOWTO,
746 available from <http://www.tldp.org/docs.html#howto>. More
747 specific information is in
748 <file:Documentation/networking/vortex.txt> and in the comments at
749 the beginning of <file:drivers/net/3c59x.c>.
751 To compile this support as a module, choose M here and read
752 <file:Documentation/networking/net-modules.txt>.
755 tristate "3cr990 series \"Typhoon\" support"
756 depends on NET_VENDOR_3COM && PCI
759 This option enables driver support for the 3cr990 series of cards:
761 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
762 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
763 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
765 If you have a network (Ethernet) card of this type, say Y and read
766 the Ethernet-HOWTO, available from
767 <http://www.tldp.org/docs.html#howto>.
769 To compile this driver as a module, choose M here and read
770 <file:Documentation/networking/net-modules.txt>. The module
771 will be called typhoon.
774 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
775 depends on ISA && ISA_DMA_API
777 If you have a network (Ethernet) card of this type, say Y and read
778 the Ethernet-HOWTO, available from
779 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
782 To compile this driver as a module, choose M here: the module
783 will be called lance. This is recommended.
785 config NET_VENDOR_SMC
786 bool "Western Digital/SMC cards"
787 depends on ISA || MCA || EISA || MAC
789 If you have a network (Ethernet) card belonging to this class, say Y
790 and read the Ethernet-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>.
793 Note that the answer to this question doesn't directly affect the
794 kernel: saying N will just cause the configurator to skip all
795 the questions about Western Digital cards. If you say Y, you will be
796 asked for your specific card in the following questions.
799 tristate "WD80*3 support"
800 depends on NET_VENDOR_SMC && ISA
803 If you have a network (Ethernet) card of this type, say Y and read
804 the Ethernet-HOWTO, available from
805 <http://www.tldp.org/docs.html#howto>.
807 To compile this driver as a module, choose M here and read
808 <file:Documentation/networking/net-modules.txt>. The module
812 tristate "SMC Ultra MCA support"
813 depends on NET_VENDOR_SMC && MCA
816 If you have a network (Ethernet) card of this type and are running
817 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
818 available from <http://www.tldp.org/docs.html#howto>.
820 To compile this driver as a module, choose M here and read
821 <file:Documentation/networking/net-modules.txt>. The module
822 will be called smc-mca.
825 tristate "SMC Ultra support"
826 depends on NET_VENDOR_SMC && ISA
829 If you have a network (Ethernet) card of this type, say Y and read
830 the Ethernet-HOWTO, available from
831 <http://www.tldp.org/docs.html#howto>.
833 Important: There have been many reports that, with some motherboards
834 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
835 such as some BusLogic models) causes corruption problems with many
836 operating systems. The Linux smc-ultra driver has a work-around for
837 this but keep it in mind if you have such a SCSI card and have
840 To compile this driver as a module, choose M here and read
841 <file:Documentation/networking/net-modules.txt>. The module
842 will be called smc-ultra.
845 tristate "SMC Ultra32 EISA support"
846 depends on NET_VENDOR_SMC && EISA
849 If you have a network (Ethernet) card of this type, say Y and read
850 the Ethernet-HOWTO, available from
851 <http://www.tldp.org/docs.html#howto>.
853 To compile this driver as a module, choose M here and read
854 <file:Documentation/networking/net-modules.txt>. The module
855 will be called smc-ultra32.
858 tristate "SMC 9194 support"
859 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
862 This is support for the SMC9xxx based Ethernet cards. Choose this
863 option if you have a DELL laptop with the docking station, or
864 another SMC9192/9194 based chipset. Say Y if you want it compiled
865 into the kernel, and read the file
866 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
867 available from <http://www.tldp.org/docs.html#howto>.
869 To compile this driver as a module, choose M here and read
870 <file:Documentation/networking/net-modules.txt>. The module
871 will be called smc9194.
874 tristate "SMC 91C9x/91C1xxx support"
877 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
879 This is a driver for SMC's 91x series of Ethernet chipsets,
880 including the SMC91C94 and the SMC91C111. Say Y if you want it
881 compiled into the kernel, and read the file
882 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
883 available from <http://www.linuxdoc.org/docs.html#howto>.
885 This driver is also available as a module ( = code which can be
886 inserted in and removed from the running kernel whenever you want).
887 The module will be called smc91x. If you want to compile it as a
888 module, say M here and read <file:Documentation/kbuild/modules.txt>
889 as well as <file:Documentation/networking/net-modules.txt>.
892 tristate "NetX Ethernet support"
896 This is support for the Hilscher netX builtin Ethernet ports
898 To compile this driver as a module, choose M here and read
899 <file:Documentation/networking/net-modules.txt>. The module
900 will be called netx-eth.
903 tristate "DM9000 support"
904 depends on ARM || BLACKFIN || MIPS
908 Support for DM9000 chipset.
910 To compile this driver as a module, choose M here and read
911 <file:Documentation/networking/net-modules.txt>. The module will be
915 tristate "SMSC LAN911[5678] support"
920 This is a driver for SMSC's LAN911x series of Ethernet chipsets
921 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
922 Say Y if you want it compiled into the kernel,
923 and read the Ethernet-HOWTO, available from
924 <http://www.linuxdoc.org/docs.html#howto>.
926 This driver is also available as a module. The module will be
927 called smc911x. If you want to compile it as a module, say M
928 here and read <file:Documentation/kbuild/modules.txt>
930 config NET_VENDOR_RACAL
931 bool "Racal-Interlan (Micom) NI cards"
934 If you have a network (Ethernet) card belonging to this class, such
935 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
936 available from <http://www.tldp.org/docs.html#howto>.
938 Note that the answer to this question doesn't directly affect the
939 kernel: saying N will just cause the configurator to skip all
940 the questions about NI cards. If you say Y, you will be asked for
941 your specific card in the following questions.
944 tristate "NI5010 support (EXPERIMENTAL)"
945 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
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>. Note that this is still
952 To compile this driver as a module, choose M here and read
953 <file:Documentation/networking/net-modules.txt>. The module
954 will be called ni5010.
957 tristate "NI5210 support"
958 depends on NET_VENDOR_RACAL && ISA
960 If you have a network (Ethernet) card of this type, say Y and read
961 the Ethernet-HOWTO, available from
962 <http://www.tldp.org/docs.html#howto>.
964 To compile this driver as a module, choose M here and read
965 <file:Documentation/networking/net-modules.txt>. The module
969 tristate "NI6510 support"
970 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
972 If you have a network (Ethernet) card of this type, say Y and read
973 the Ethernet-HOWTO, available from
974 <http://www.tldp.org/docs.html#howto>.
976 To compile this driver as a module, choose M here and read
977 <file:Documentation/networking/net-modules.txt>. The module
980 source "drivers/net/tulip/Kconfig"
983 tristate "AT1700/1720 support (EXPERIMENTAL)"
984 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
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 and read
992 <file:Documentation/networking/net-modules.txt>. The module
993 will be called at1700.
996 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
997 depends on ISA || EISA || MCA
1000 If you have a network (Ethernet) card of this type, say Y and read
1001 the Ethernet-HOWTO, available from
1002 <http://www.tldp.org/docs.html#howto> as well as
1003 <file:drivers/net/depca.c>.
1005 To compile this driver as a module, choose M here and read
1006 <file:Documentation/networking/net-modules.txt>. The module
1007 will be called depca.
1010 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1011 depends on ISA || EISA || PCI
1013 If you have a network (Ethernet) card of this type, say Y and read
1014 the Ethernet-HOWTO, available from
1015 <http://www.tldp.org/docs.html#howto>.
1017 To compile this driver as a module, choose M here and read
1018 <file:Documentation/networking/net-modules.txt>. The module
1019 will be called hp100.
1022 bool "Other ISA cards"
1025 If your network (Ethernet) card hasn't been mentioned yet and its
1026 bus system (that's the way the cards talks to the other components
1027 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1028 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1029 available from <http://www.tldp.org/docs.html#howto>.
1033 Note that the answer to this question doesn't directly affect the
1034 kernel: saying N will just cause the configurator to skip all
1035 the remaining ISA network card questions. If you say Y, you will be
1036 asked for your specific card in the following questions.
1039 tristate "Cabletron E21xx support"
1043 If you have a network (Ethernet) card of this type, say Y and read
1044 the Ethernet-HOWTO, available from
1045 <http://www.tldp.org/docs.html#howto>.
1047 To compile this driver as a module, choose M here and read
1048 <file:Documentation/networking/net-modules.txt>. The module
1049 will be called e2100.
1052 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1056 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1057 cards. If this is for you, say Y and read
1058 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1059 well as the Ethernet-HOWTO, available from
1060 <http://www.tldp.org/docs.html#howto>.
1062 To compile this driver as a module, choose M here and read
1063 <file:Documentation/networking/net-modules.txt>. The module
1064 will be called ewrk3.
1067 tristate "EtherExpress 16 support"
1070 If you have an EtherExpress16 network (Ethernet) card, say Y and
1071 read the Ethernet-HOWTO, available from
1072 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1073 EtherExpress16 card used to be regarded as a very poor choice
1074 because the driver was very unreliable. We now have a new driver
1075 that should do better.
1077 To compile this driver as a module, choose M here and read
1078 <file:Documentation/networking/net-modules.txt>. The module
1079 will be called eexpress.
1082 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1085 If you have a network (Ethernet) card of this type, say Y. This
1086 driver supports Intel i82595{FX,TX} based boards. Note however
1087 that the EtherExpress PRO/100 Ethernet card has its own separate
1088 driver. Please read the Ethernet-HOWTO, available from
1089 <http://www.tldp.org/docs.html#howto>.
1091 To compile this driver as a module, choose M here and read
1092 <file:Documentation/networking/net-modules.txt>. The module
1093 will be called eepro.
1096 tristate "HP PCLAN+ (27247B and 27252A) support"
1100 If you have a network (Ethernet) card of this type, say Y and read
1101 the Ethernet-HOWTO, available from
1102 <http://www.tldp.org/docs.html#howto>.
1104 To compile this driver as a module, choose M here and read
1105 <file:Documentation/networking/net-modules.txt>. The module
1106 will be called hp-plus.
1109 tristate "HP PCLAN (27245 and other 27xxx series) support"
1113 If you have a network (Ethernet) card of this type, say Y and read
1114 the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>.
1117 To compile this driver as a module, choose M here and read
1118 <file:Documentation/networking/net-modules.txt>. The module
1122 tristate "LP486E on board Ethernet"
1125 Say Y here to support the 82596-based on-board Ethernet controller
1126 for the Panther motherboard, which is one of the two shipped in the
1127 Intel Professional Workstation.
1130 tristate "ICL EtherTeam 16i/32 support"
1133 If you have a network (Ethernet) card of this type, say Y and read
1134 the Ethernet-HOWTO, available from
1135 <http://www.tldp.org/docs.html#howto>.
1137 To compile this driver as a module, choose M here and read
1138 <file:Documentation/networking/net-modules.txt>. The module
1139 will be called eth16i.
1142 tristate "NE2000/NE1000 support"
1143 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1146 If you have a network (Ethernet) card of this type, say Y and read
1147 the Ethernet-HOWTO, available from
1148 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1149 without a specific driver are compatible with NE2000.
1151 If you have a PCI NE2000 card however, say N here and Y to "PCI
1152 NE2000 and clone support" under "EISA, VLB, PCI and on board
1153 controllers" below. If you have a NE2000 card and are running on
1154 an MCA system (a bus system used on some IBM PS/2 computers and
1155 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1158 To compile this driver as a module, choose M here and read
1159 <file:Documentation/networking/net-modules.txt>. The module
1163 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1164 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1166 The Zenith Z-Note notebook computer has a built-in network
1167 (Ethernet) card, and this is the Linux driver for it. Note that the
1168 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1169 by this driver. Read the Ethernet-HOWTO, available from
1170 <http://www.tldp.org/docs.html#howto>.
1173 tristate "SEEQ8005 support (EXPERIMENTAL)"
1174 depends on NET_ISA && EXPERIMENTAL
1176 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1177 is for you, read the Ethernet-HOWTO, available from
1178 <http://www.tldp.org/docs.html#howto>.
1180 To compile this driver as a module, choose M here and read
1181 <file:Documentation/networking/net-modules.txt>. The module
1182 will be called seeq8005.
1185 tristate "NE/2 (ne2000 MCA version) support"
1186 depends on MCA_LEGACY
1189 If you have a network (Ethernet) card of this type, say Y and read
1190 the Ethernet-HOWTO, available from
1191 <http://www.tldp.org/docs.html#howto>.
1193 To compile this driver as a module, choose M here and read
1194 <file:Documentation/networking/net-modules.txt>. The module
1198 tristate "IBM LAN Adapter/A support"
1199 depends on MCA && MCA_LEGACY
1201 This is a Micro Channel Ethernet adapter. You need to set
1202 CONFIG_MCA to use this driver. It is both available as an in-kernel
1203 driver and as a module.
1205 To compile this driver as a module, choose M here and read
1206 <file:Documentation/networking/net-modules.txt>. The only
1207 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1208 will both support 16K and 32K memory windows, however a 32K window
1209 gives a better security against packet losses. Usage of multiple
1210 boards with this driver should be possible, but has not been tested
1211 up to now due to lack of hardware.
1214 tristate "IBM LAN Virtual Ethernet support"
1215 depends on PPC_PSERIES
1217 This driver supports virtual ethernet adapters on newer IBM iSeries
1218 and pSeries systems.
1220 To compile this driver as a module, choose M here and read
1221 <file:Documentation/networking/net-modules.txt>. The module will
1225 tristate "PowerPC 4xx on-chip Ethernet support"
1226 depends on 4xx && !PPC_MERGE
1228 This driver supports the PowerPC 4xx EMAC family of on-chip
1229 Ethernet controllers.
1232 int "Number of receive buffers"
1237 int "Number of transmit buffers"
1241 config IBM_EMAC_POLL_WEIGHT
1242 int "MAL NAPI polling weight"
1246 config IBM_EMAC_RX_COPY_THRESHOLD
1247 int "RX skb copy threshold (bytes)"
1251 config IBM_EMAC_RX_SKB_HEADROOM
1252 int "Additional RX skb headroom (bytes)"
1256 Additional receive skb headroom. Note, that driver
1257 will always reserve at least 2 bytes to make IP header
1258 aligned, so usually there is no need to add any additional
1261 If unsure, set to 0.
1263 config IBM_EMAC_PHY_RX_CLK_FIX
1264 bool "PHY Rx clock workaround"
1265 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1267 Enable this if EMAC attached to a PHY which doesn't generate
1268 RX clock if there is no link, if this is the case, you will
1269 see "TX disable timeout" or "RX disable timeout" in the system
1274 config IBM_EMAC_DEBUG
1279 config IBM_EMAC_ZMII
1281 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1284 config IBM_EMAC_RGMII
1286 depends on IBM_EMAC && 440GX
1291 depends on IBM_EMAC && 440GX
1295 bool "EISA, VLB, PCI and on board controllers"
1296 depends on ISA || EISA || PCI
1298 This is another class of network cards which attach directly to the
1299 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1300 available from <http://www.tldp.org/docs.html#howto>.
1302 Note that the answer to this question doesn't directly affect the
1303 kernel: saying N will just cause the configurator to skip all
1304 the questions about this class of network cards. If you say Y, you
1305 will be asked for your specific card in the following questions. If
1306 you are unsure, say Y.
1309 tristate "AMD PCnet32 PCI support"
1310 depends on NET_PCI && PCI
1314 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1315 answer Y here and read the Ethernet-HOWTO, available from
1316 <http://www.tldp.org/docs.html#howto>.
1318 To compile this driver as a module, choose M here and read
1319 <file:Documentation/networking/net-modules.txt>. The module
1320 will be called pcnet32.
1323 bool "Use RX polling (NAPI)"
1326 NAPI is a new driver API designed to reduce CPU and interrupt load
1327 when the driver is receiving lots of packets from the card. It is
1328 still somewhat experimental and thus not yet enabled by default.
1330 If your estimated Rx load is 10kpps or more, or if the card will be
1331 deployed on potentially unfriendly networks (e.g. in a firewall),
1334 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1340 tristate "AMD 8111 (new PCI lance) support"
1341 depends on NET_PCI && PCI
1345 If you have an AMD 8111-based PCI lance ethernet card,
1346 answer Y here and read the Ethernet-HOWTO, available from
1347 <http://www.tldp.org/docs.html#howto>.
1349 To compile this driver as a module, choose M here and read
1350 <file:Documentation/networking/net-modules.txt>. The module
1351 will be called amd8111e.
1353 config AMD8111E_NAPI
1354 bool "Enable NAPI support"
1355 depends on AMD8111_ETH
1357 NAPI is a new driver API designed to reduce CPU and interrupt load
1358 when the driver is receiving lots of packets from the card. It is
1359 still somewhat experimental and thus not yet enabled by default.
1361 If your estimated Rx load is 10kpps or more, or if the card will be
1362 deployed on potentially unfriendly networks (e.g. in a firewall),
1365 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1370 config ADAPTEC_STARFIRE
1371 tristate "Adaptec Starfire/DuraLAN support"
1372 depends on NET_PCI && PCI
1376 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1377 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1378 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1381 To compile this driver as a module, choose M here: the module
1382 will be called starfire. This is recommended.
1384 config ADAPTEC_STARFIRE_NAPI
1385 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1386 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1388 NAPI is a new driver API designed to reduce CPU and interrupt load
1389 when the driver is receiving lots of packets from the card. It is
1390 still somewhat experimental and thus not yet enabled by default.
1392 If your estimated Rx load is 10kpps or more, or if the card will be
1393 deployed on potentially unfriendly networks (e.g. in a firewall),
1396 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1402 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1403 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1406 If you have a network (Ethernet) card of this type, say Y and read
1407 the Ethernet-HOWTO, available from
1408 <http://www.tldp.org/docs.html#howto>.
1410 To compile this driver as a module, choose M here and read
1411 <file:Documentation/networking/net-modules.txt>. The module
1412 will be called ac3200.
1415 tristate "Apricot Xen-II on board Ethernet"
1416 depends on NET_PCI && ISA
1418 If you have a network (Ethernet) controller of this type, say Y and
1419 read the Ethernet-HOWTO, available from
1420 <http://www.tldp.org/docs.html#howto>.
1422 To compile this driver as a module, choose M here and read
1423 <file:Documentation/networking/net-modules.txt>. The module will be
1427 tristate "Broadcom 4400 ethernet support"
1428 depends on NET_PCI && PCI
1431 If you have a network (Ethernet) controller of this type, say Y and
1432 read the Ethernet-HOWTO, available from
1433 <http://www.tldp.org/docs.html#howto>.
1435 To compile this driver as a module, choose M here and read
1436 <file:Documentation/networking/net-modules.txt>. The module will be
1440 tristate "nForce Ethernet support"
1441 depends on NET_PCI && PCI
1443 If you have a network (Ethernet) controller of this type, say Y and
1444 read the Ethernet-HOWTO, available from
1445 <http://www.tldp.org/docs.html#howto>.
1447 To compile this driver as a module, choose M here and read
1448 <file:Documentation/networking/net-modules.txt>. The module will be
1451 config FORCEDETH_NAPI
1452 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1453 depends on FORCEDETH && EXPERIMENTAL
1455 NAPI is a new driver API designed to reduce CPU and interrupt load
1456 when the driver is receiving lots of packets from the card. It is
1457 still somewhat experimental and thus not yet enabled by default.
1459 If your estimated Rx load is 10kpps or more, or if the card will be
1460 deployed on potentially unfriendly networks (e.g. in a firewall),
1463 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1469 tristate "CS89x0 support"
1470 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1472 Support for CS89x0 chipset based Ethernet cards. If you have a
1473 network (Ethernet) card of this type, say Y and read the
1474 Ethernet-HOWTO, available from
1475 <http://www.tldp.org/docs.html#howto> as well as
1476 <file:Documentation/networking/cs89x0.txt>.
1478 To compile this driver as a module, choose M here and read
1479 <file:Documentation/networking/net-modules.txt>. The module will be
1483 tristate "TOSHIBA TC35815 Ethernet support"
1484 depends on NET_PCI && PCI && MIPS
1488 tristate "Digi Intl. RightSwitch SE-X support"
1489 depends on NET_PCI && (PCI || EISA)
1491 This is support for the Digi International RightSwitch series of
1492 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1493 models. If you have a network card of this type, say Y and read the
1494 Ethernet-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>. More specific
1496 information is contained in <file:Documentation/networking/dgrs.txt>.
1498 To compile this driver as a module, choose M here and read
1499 <file:Documentation/networking/net-modules.txt>. The module
1500 will be called dgrs.
1503 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1504 depends on NET_PCI && PCI
1507 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1508 card, say Y and read the Ethernet-HOWTO, available from
1509 <http://www.tldp.org/docs.html#howto>.
1511 To compile this driver as a module, choose M here and read
1512 <file:Documentation/networking/net-modules.txt>. The module
1513 will be called eepro100.
1517 tristate "Intel(R) PRO/100+ support"
1518 depends on NET_PCI && PCI
1521 This driver supports Intel(R) PRO/100 family of adapters.
1522 To verify that your adapter is supported, find the board ID number
1523 on the adapter. Look for a label that has a barcode and a number
1524 in the format 123456-001 (six digits hyphen three digits).
1526 Use the above information and the Adapter & Driver ID Guide at:
1528 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1530 to identify the adapter.
1532 For the latest Intel PRO/100 network driver for Linux, see:
1534 <http://appsr.intel.com/scripts-df/support_intel.asp>
1536 More specific information on configuring the driver is in
1537 <file:Documentation/networking/e100.txt>.
1539 To compile this driver as a module, choose M here and read
1540 <file:Documentation/networking/net-modules.txt>. The module
1541 will be called e100.
1544 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1545 depends on NET_PCI && EISA && EXPERIMENTAL
1548 If you have a network (Ethernet) card of this type, say Y and read
1549 the Ethernet-HOWTO, available from
1550 <http://www.tldp.org/docs.html#howto>.
1552 To compile this driver as a module, choose M here and read
1553 <file:Documentation/networking/net-modules.txt>. The module
1554 will be called lne390.
1557 tristate "Myson MTD-8xx PCI Ethernet support"
1558 depends on NET_PCI && PCI
1562 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1563 cards. Specifications and data at
1564 <http://www.myson.com.hk/mtd/datasheet/>.
1567 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1568 depends on NET_PCI && PCI
1571 This driver is for the National Semiconductor DP83810 series,
1572 which is used in cards from PureData, NetGear, Linksys
1573 and others, including the 83815 chip.
1574 More specific information and updates are available from
1575 <http://www.scyld.com/network/natsemi.html>.
1578 tristate "PCI NE2000 and clones support (see help)"
1579 depends on NET_PCI && PCI
1582 This driver is for NE2000 compatible PCI cards. It will not work
1583 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1584 support" below). If you have a PCI NE2000 network (Ethernet) card,
1585 say Y and read the Ethernet-HOWTO, available from
1586 <http://www.tldp.org/docs.html#howto>.
1588 This driver also works for the following NE2000 clone cards:
1589 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1590 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1591 Holtek HT80232 Holtek HT80229
1593 To compile this driver as a module, choose M here and read
1594 <file:Documentation/networking/net-modules.txt>. The module
1595 will be called ne2k-pci.
1598 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1599 depends on NET_PCI && EISA && EXPERIMENTAL
1602 If you have a network (Ethernet) card of this type, say Y and read
1603 the Ethernet-HOWTO, available from
1604 <http://www.tldp.org/docs.html#howto>. Note that this driver
1605 will NOT WORK for NE3200 cards as they are completely different.
1607 To compile this driver as a module, choose M here and read
1608 <file:Documentation/networking/net-modules.txt>. The module
1609 will be called ne3210.
1612 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1613 depends on NET_PCI && EISA && EXPERIMENTAL
1616 If you have a network (Ethernet) card of this type, say Y and read
1617 the Ethernet-HOWTO, available from
1618 <http://www.tldp.org/docs.html#howto>.
1620 To compile this driver as a module, choose M here and read
1621 <file:Documentation/networking/net-modules.txt>. The module
1622 will be called es3210.
1625 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1626 depends on NET_PCI && PCI && EXPERIMENTAL
1630 This is a driver for the Fast Ethernet PCI network cards based on
1631 the RTL8139C+ chips. If you have one of those, say Y and read
1632 the Ethernet-HOWTO, available from
1633 <http://www.tldp.org/docs.html#howto>.
1635 To compile this driver as a module, choose M here: the module
1636 will be called 8139cp. This is recommended.
1639 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1640 depends on NET_PCI && PCI
1644 This is a driver for the Fast Ethernet PCI network cards based on
1645 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1646 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1648 To compile this driver as a module, choose M here: the module
1649 will be called 8139too. This is recommended.
1652 bool "Use PIO instead of MMIO"
1656 This instructs the driver to use programmed I/O ports (PIO) instead
1657 of PCI shared memory (MMIO). This can possibly solve some problems
1658 in case your mainboard has memory consistency issues. If unsure,
1661 config 8139TOO_TUNE_TWISTER
1662 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1665 This implements a function which might come in handy in case you
1666 are using low quality on long cabling. It is required for RealTek
1667 RTL-8139 revision K boards, and totally unused otherwise. It tries
1668 to match the transceiver to the cable characteristics. This is
1669 experimental since hardly documented by the manufacturer.
1673 bool "Support for older RTL-8129/8130 boards"
1676 This enables support for the older and uncommon RTL-8129 and
1677 RTL-8130 chips, which support MII via an external transceiver,
1678 instead of an internal one. Disabling this option will save some
1679 memory by making the code size smaller. If unsure, say Y.
1681 config 8139_OLD_RX_RESET
1682 bool "Use older RX-reset method"
1685 The 8139too driver was recently updated to contain a more rapid
1686 reset sequence, in the face of severe receive errors. This "new"
1687 RX-reset method should be adequate for all boards. But if you
1688 experience problems, you can enable this option to restore the
1689 old RX-reset behavior. If unsure, say N.
1692 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1693 depends on NET_PCI && PCI
1697 This is a driver for the Fast Ethernet PCI network cards based on
1698 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1699 SiS 630 and SiS 540 chipsets.
1701 This driver also supports AMD 79C901 HomePNA so that you can use
1702 your phone line as a network cable.
1704 To compile this driver as a module, choose M here: the module
1705 will be called sis900. This is recommended.
1708 tristate "SMC EtherPower II"
1709 depends on NET_PCI && PCI
1713 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1714 which is based on the SMC83c17x (EPIC/100).
1715 More specific information and updates are available from
1716 <http://www.scyld.com/network/epic100.html>.
1719 tristate "Sundance Alta support"
1720 depends on NET_PCI && PCI
1724 This driver is for the Sundance "Alta" chip.
1725 More specific information and updates are available from
1726 <http://www.scyld.com/network/sundance.html>.
1728 config SUNDANCE_MMIO
1729 bool "Use MMIO instead of PIO"
1732 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1733 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1734 is known to solve bugs on certain chips.
1739 tristate "TI ThunderLAN support"
1740 depends on NET_PCI && (PCI || EISA) && !64BIT
1742 If you have a PCI Ethernet network card based on the ThunderLAN chip
1743 which is supported by this driver, say Y and read the
1744 Ethernet-HOWTO, available from
1745 <http://www.tldp.org/docs.html#howto>.
1747 Devices currently supported by this driver are Compaq Netelligent,
1748 Compaq NetFlex and Olicom cards. Please read the file
1749 <file:Documentation/networking/tlan.txt> for more details.
1751 To compile this driver as a module, choose M here and read
1752 <file:Documentation/networking/net-modules.txt>. The module
1753 will be called tlan.
1755 Please email feedback to <torben.mathiasen@compaq.com>.
1758 tristate "VIA Rhine support"
1759 depends on NET_PCI && PCI
1763 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1764 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1765 Ethernet functions can also be found integrated on South Bridges
1768 To compile this driver as a module, choose M here. The module
1769 will be called via-rhine.
1771 config VIA_RHINE_MMIO
1772 bool "Use MMIO instead of PIO"
1773 depends on VIA_RHINE
1775 This instructs the driver to use PCI shared memory (MMIO) instead of
1776 programmed I/O ports (PIO). Enabling this gives an improvement in
1777 processing time in parts of the driver.
1781 config VIA_RHINE_NAPI
1782 bool "Use Rx Polling (NAPI)"
1783 depends on VIA_RHINE
1785 NAPI is a new driver API designed to reduce CPU and interrupt load
1786 when the driver is receiving lots of packets from the card.
1788 If your estimated Rx load is 10kpps or more, or if the card will be
1789 deployed on potentially unfriendly networks (e.g. in a firewall),
1792 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1796 bool "Philips SAA9730 Ethernet support"
1797 depends on NET_PCI && PCI && MIPS_ATLAS
1799 The SAA9730 is a combined multimedia and peripheral controller used
1800 in thin clients, Internet access terminals, and diskless
1802 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1805 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1806 depends on NET_PCI && PCI && EXPERIMENTAL
1809 This is a driver for the Fast Ethernet PCI network cards based on
1810 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1811 have one of these, say Y here.
1813 To compile this driver as a module, choose M here: the module
1814 will be called sc92031. This is recommended.
1817 bool "Pocket and portable adapters"
1820 Cute little network (Ethernet) devices which attach to the parallel
1821 port ("pocket adapters"), commonly used with laptops. If you have
1822 one of those, say Y and read the Ethernet-HOWTO, available from
1823 <http://www.tldp.org/docs.html#howto>.
1825 If you want to plug a network (or some other) card into the PCMCIA
1826 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1827 credit card size extension cards used by all modern laptops), you
1828 need the pcmcia-cs package (location contained in the file
1829 <file:Documentation/Changes>) and you can say N here.
1831 Laptop users should read the Linux Laptop home page at
1832 <http://www.linux-on-laptops.com/> or
1833 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1835 Note that the answer to this question doesn't directly affect the
1836 kernel: saying N will just cause the configurator to skip all
1837 the questions about this class of network devices. If you say Y, you
1838 will be asked for your specific device in the following questions.
1841 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1842 depends on NET_POCKET && PARPORT && X86
1845 This is a network (Ethernet) device which attaches to your parallel
1846 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1847 available from <http://www.tldp.org/docs.html#howto>, if you
1848 want to use this. If you intend to use this driver, you should have
1849 said N to the "Parallel printer support", because the two drivers
1850 don't like each other.
1852 To compile this driver as a module, choose M here: the module
1856 tristate "D-Link DE600 pocket adapter support"
1857 depends on NET_POCKET && PARPORT
1859 This is a network (Ethernet) device which attaches to your parallel
1860 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1861 Ethernet-HOWTO, available from
1862 <http://www.tldp.org/docs.html#howto>, if you want to use
1863 this. It is possible to have several devices share a single parallel
1864 port and it is safe to compile the corresponding drivers into the
1867 To compile this driver as a module, choose M here: the module
1868 will be called de600.
1871 tristate "D-Link DE620 pocket adapter support"
1872 depends on NET_POCKET && PARPORT
1874 This is a network (Ethernet) device which attaches to your parallel
1875 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1876 Ethernet-HOWTO, available from
1877 <http://www.tldp.org/docs.html#howto>, if you want to use
1878 this. It is possible to have several devices share a single parallel
1879 port and it is safe to compile the corresponding drivers into the
1882 To compile this driver as a module, choose M here: the module
1883 will be called de620.
1886 tristate "SGI Seeq ethernet controller support"
1889 Say Y here if you have an Seeq based Ethernet network card. This is
1890 used in many Silicon Graphics machines.
1893 tristate "DEC LANCE ethernet controller support"
1894 depends on MACH_DECSTATION
1897 This driver is for the series of Ethernet controllers produced by
1898 DEC (now Compaq) based on the AMD Lance chipset, including the
1899 DEPCA series. (This chipset is better known via the NE2100 cards.)
1902 bool "Motorola 68360 ethernet controller"
1905 Say Y here if you want to use the built-in ethernet controller of
1906 the Motorola 68360 processor.
1909 bool "FEC ethernet controller (of ColdFire CPUs)"
1910 depends on M523x || M527x || M5272 || M528x || M520x
1912 Say Y here if you want to use the built-in 10/100 Fast ethernet
1913 controller on some Motorola ColdFire processors.
1916 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1919 Say Y here if you want to use the second built-in 10/100 Fast
1920 ethernet controller on some Motorola ColdFire processors.
1923 tristate "NE2000 compatible support for H8/300"
1926 Say Y here if you want to use the NE2000 compatible
1927 controller on the Renesas H8/300 processor.
1929 source "drivers/net/fec_8xx/Kconfig"
1930 source "drivers/net/fs_enet/Kconfig"
1932 endif # NET_ETHERNET
1938 menuconfig NETDEV_1000
1939 bool "Ethernet (1000 Mbit)"
1946 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1949 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1950 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1951 adapter. The driver allows for using the Jumbo Frame option (9000
1952 bytes/frame) however it requires that your switches can handle this
1953 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1956 To compile this driver as a module, choose M here: the
1957 module will be called acenic.
1959 config ACENIC_OMIT_TIGON_I
1960 bool "Omit support for old Tigon I based AceNICs"
1963 Say Y here if you only have Tigon II based AceNICs and want to leave
1964 out support for the older Tigon I based cards which are no longer
1965 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1966 version)). This will reduce the size of the driver object by
1967 app. 100KB. If you are not sure whether your card is a Tigon I or a
1968 Tigon II, say N here.
1970 The safe and default value for this is N.
1973 tristate "D-Link DL2000-based Gigabit Ethernet support"
1977 This driver supports D-Link 2000-based gigabit ethernet cards, which
1979 D-Link DGE-550T Gigabit Ethernet Adapter.
1980 D-Link DL2000-based Gigabit Ethernet Adapter.
1982 To compile this driver as a module, choose M here: the
1983 module will be called dl2k.
1986 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1989 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1990 adapters. For more information on how to identify your adapter, go
1991 to the Adapter & Driver ID Guide at:
1993 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1995 For general information and support, go to the Intel support
1998 <http://support.intel.com>
2000 More specific information on configuring the driver is in
2001 <file:Documentation/networking/e1000.txt>.
2003 To compile this driver as a module, choose M here and read
2004 <file:Documentation/networking/net-modules.txt>. The module
2005 will be called e1000.
2008 bool "Use Rx Polling (NAPI)"
2011 NAPI is a new driver API designed to reduce CPU and interrupt load
2012 when the driver is receiving lots of packets from the card. It is
2013 still somewhat experimental and thus not yet enabled by default.
2015 If your estimated Rx load is 10kpps or more, or if the card will be
2016 deployed on potentially unfriendly networks (e.g. in a firewall),
2019 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2024 config E1000_DISABLE_PACKET_SPLIT
2025 bool "Disable Packet Split for PCI express adapters"
2028 Say Y here if you want to use the legacy receive path for PCI express
2033 source "drivers/net/ixp2000/Kconfig"
2036 tristate "MyriCOM Gigabit Ethernet support"
2039 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2041 To compile this driver as a module, choose M here: the module
2042 will be called myri_sbus. This is recommended.
2045 tristate "National Semiconductor DP83820 support"
2048 This is a driver for the National Semiconductor DP83820 series
2049 of gigabit ethernet MACs. Cards using this chipset include
2050 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2051 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2055 tristate "Packet Engines Hamachi GNIC-II support"
2059 If you have a Gigabit Ethernet card of this type, say Y and read
2060 the Ethernet-HOWTO, available from
2061 <http://www.tldp.org/docs.html#howto>.
2063 To compile this driver as a module, choose M here and read
2064 <file:Documentation/networking/net-modules.txt>. The module will be
2068 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2069 depends on PCI && EXPERIMENTAL
2072 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2073 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2074 used by the Beowulf Linux cluster project. See
2075 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2076 information about this driver in particular and Beowulf in general.
2078 To compile this driver as a module, choose M here: the module
2079 will be called yellowfin. This is recommended.
2082 tristate "Realtek 8169 gigabit ethernet support"
2086 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2088 To compile this driver as a module, choose M here: the module
2089 will be called r8169. This is recommended.
2092 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2093 depends on R8169 && EXPERIMENTAL
2095 NAPI is a new driver API designed to reduce CPU and interrupt load
2096 when the driver is receiving lots of packets from the card. It is
2097 still somewhat experimental and thus not yet enabled by default.
2099 If your estimated Rx load is 10kpps or more, or if the card will be
2100 deployed on potentially unfriendly networks (e.g. in a firewall),
2103 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2110 depends on R8169 && VLAN_8021Q
2112 Say Y here for the r8169 driver to support the functions required
2113 by the kernel 802.1Q code.
2118 tristate "SiS190/SiS191 gigabit ethernet support"
2123 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2124 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2125 appear in lan on motherboard designs which are based on SiS 965
2126 and SiS 966 south bridge.
2128 To compile this driver as a module, choose M here: the module
2129 will be called sis190. This is recommended.
2132 tristate "New SysKonnect GigaEthernet support"
2136 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2137 and related Gigabit Ethernet adapters. It is a new smaller driver
2138 with better performance and more complete ethtool support.
2140 It does not support the link failover and network management
2141 features available in the hardware.
2143 This driver supports adapters based on the original Yukon chipset:
2144 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2145 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2147 It does not support the newer Yukon2 chipset: a separate driver,
2148 sky2, is provided for Yukon2-based adapters.
2150 To compile this driver as a module, choose M here: the module
2151 will be called skge. This is recommended.
2154 tristate "SysKonnect Yukon2 support"
2158 This driver supports Gigabit Ethernet adapters based on the
2159 Marvell Yukon 2 chipset:
2160 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2161 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2163 There is companion driver for the older Marvell Yukon and
2164 Genesis based adapters: skge.
2166 To compile this driver as a module, choose M here: the module
2167 will be called sky2. This is recommended.
2170 bool "Debugging interface"
2171 depends on SKY2 && DEBUG_FS
2173 This option adds the ability to dump driver state for debugging.
2174 The file debugfs/sky2/ethX displays the state of the internal
2175 transmit and receive rings.
2180 tristate "VIA Velocity support"
2186 If you have a VIA "Velocity" based network card say Y here.
2188 To compile this driver as a module, choose M here. The module
2189 will be called via-velocity.
2192 tristate "Broadcom Tigon3 support"
2195 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2197 To compile this driver as a module, choose M here: the module
2198 will be called tg3. This is recommended.
2201 tristate "Broadcom NetXtremeII support"
2206 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2208 To compile this driver as a module, choose M here: the module
2209 will be called bnx2. This is recommended.
2212 tristate "Spider Gigabit Ethernet driver"
2213 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2216 This driver supports the Gigabit Ethernet chips present on the
2217 Cell Processor-Based Blades from IBM.
2220 tristate "Tundra TSI108 gigabit Ethernet support"
2221 depends on TSI108_BRIDGE
2223 This driver supports Tundra TSI108 gigabit Ethernet ports.
2224 To compile this driver as a module, choose M here: the module
2225 will be called tsi108_eth.
2228 tristate "PS3 Gigabit Ethernet driver"
2231 This driver supports the network device on the PS3 game
2232 console. This driver has built-in support for Ethernet.
2234 To compile this driver as a module, choose M here: the
2235 module will be called ps3_gelic.
2238 tristate "Gianfar Ethernet"
2239 depends on 85xx || 83xx || PPC_86xx
2243 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2244 and MPC86xx family of chips, and the FEC on the 8540.
2251 tristate "Freescale QE Gigabit Ethernet"
2252 depends on QUICC_ENGINE
2255 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2256 which is available on some Freescale SOCs.
2262 config UGETH_MAGIC_PACKET
2263 bool "Magic Packet detection support"
2266 config UGETH_FILTERING
2267 bool "Mac address filtering support"
2270 config UGETH_TX_ON_DEMAND
2271 bool "Transmit on Demand support"
2275 tristate "MV-643XX Ethernet support"
2276 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32)
2279 This driver supports the gigabit Ethernet on the Marvell MV643XX
2280 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2281 Pegasos II, amongst other PPC and MIPS boards.
2284 tristate "QLogic QLA3XXX Network Driver Support"
2287 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2289 To compile this driver as a module, choose M here: the module
2290 will be called qla3xxx.
2293 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2294 depends on PCI && EXPERIMENTAL
2298 This driver supports the Attansic L1 gigabit ethernet adapter.
2300 To compile this driver as a module, choose M here. The module
2301 will be called atl1.
2306 # 10 Gigabit Ethernet
2309 menuconfig NETDEV_10000
2310 bool "Ethernet (10000 Mbit)"
2317 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.htm>.
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.
2343 config CHELSIO_T1_NAPI
2344 bool "Use Rx Polling (NAPI)"
2345 depends on CHELSIO_T1
2348 NAPI is a driver API designed to reduce CPU and interrupt load
2349 when the driver is receiving lots of packets from the card.
2352 tristate "Chelsio Communications T3 10Gb Ethernet support"
2356 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2359 For general information about Chelsio and our products, visit
2360 our website at <http://www.chelsio.com>.
2362 For customer support, please visit our customer support page at
2363 <http://www.chelsio.com/support.htm>.
2365 Please send feedback to <linux-bugs@chelsio.com>.
2367 To compile this driver as a module, choose M here: the module
2368 will be called cxgb3.
2371 tristate "eHEA Ethernet support"
2374 This driver supports the IBM pSeries eHEA ethernet adapter.
2376 To compile the driver as a module, choose M here. The module
2377 will be called ehea.
2380 tristate "Intel(R) PRO/10GbE support"
2383 This driver supports Intel(R) PRO/10GbE family of
2384 adapters. For more information on how to identify your adapter, go
2385 to the Adapter & Driver ID Guide at:
2387 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2389 For general information and support, go to the Intel support
2392 <http://support.intel.com>
2394 More specific information on configuring the driver is in
2395 <file:Documentation/networking/ixgb.txt>.
2397 To compile this driver as a module, choose M here and read
2398 <file:Documentation/networking/net-modules.txt>. The module
2399 will be called ixgb.
2402 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2403 depends on IXGB && EXPERIMENTAL
2405 NAPI is a new driver API designed to reduce CPU and interrupt load
2406 when the driver is receiving lots of packets from the card. It is
2407 still somewhat experimental and thus not yet enabled by default.
2409 If your estimated Rx load is 10kpps or more, or if the card will be
2410 deployed on potentially unfriendly networks (e.g. in a firewall),
2413 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2419 tristate "S2IO 10Gbe XFrame NIC"
2422 This driver supports the 10Gbe XFrame NIC of S2IO.
2423 More specific information on configuring the driver is in
2424 <file:Documentation/networking/s2io.txt>.
2427 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2428 depends on S2IO && EXPERIMENTAL
2430 NAPI is a new driver API designed to reduce CPU and interrupt load
2431 when the driver is receiving lots of packets from the card. It is
2432 still somewhat experimental and thus not yet enabled by default.
2434 If your estimated Rx load is 10kpps or more, or if the card will be
2435 deployed on potentially unfriendly networks (e.g. in a firewall),
2438 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2444 tristate "Myricom Myri-10G Ethernet support"
2449 This driver supports Myricom Myri-10G Dual Protocol interface in
2450 Ethernet mode. If the eeprom on your board is not recent enough,
2451 you will need a newer firmware image.
2452 You may get this image or more information, at:
2454 <http://www.myri.com/scs/download-Myri10GE.html>
2456 To compile this driver as a module, choose M here and read
2457 <file:Documentation/networking/net-modules.txt>. The module
2458 will be called myri10ge.
2461 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2464 This enables the support for NetXen's Gigabit Ethernet card.
2467 tristate "PA Semi 1/10Gbit MAC"
2468 depends on PPC64 && PCI
2471 This driver supports the on-chip 1/10Gbit Ethernet controller on
2472 PA Semi's PWRficient line of chips.
2480 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2481 depends on MLX4_CORE
2484 This option causes debugging code to be compiled into the
2485 mlx4_core driver. The output can be turned on via the
2486 debug_level module parameter (which can also be set after
2487 the driver is loaded through sysfs).
2489 endif # NETDEV_10000
2491 source "drivers/net/tokenring/Kconfig"
2493 source "drivers/net/wireless/Kconfig"
2495 source "drivers/net/usb/Kconfig"
2497 source "drivers/net/pcmcia/Kconfig"
2499 source "drivers/net/wan/Kconfig"
2501 source "drivers/atm/Kconfig"
2503 source "drivers/s390/net/Kconfig"
2506 tristate "iSeries Virtual Ethernet driver support"
2507 depends on PPC_ISERIES
2510 tristate "RapidIO Ethernet over messaging driver support"
2513 config RIONET_TX_SIZE
2514 int "Number of outbound queue entries"
2518 config RIONET_RX_SIZE
2519 int "Number of inbound queue entries"
2524 bool "FDDI driver support"
2525 depends on (PCI || EISA || TC)
2527 Fiber Distributed Data Interface is a high speed local area network
2528 design; essentially a replacement for high speed Ethernet. FDDI can
2529 run over copper or fiber. If you are connected to such a network and
2530 want a driver for the FDDI card in your computer, say Y here (and
2531 then also Y to the driver for your FDDI card, below). Most people
2535 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2536 depends on FDDI && (PCI || EISA || TC)
2538 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2539 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2540 to a local FDDI network.
2542 To compile this driver as a module, choose M here: the module
2543 will be called defxx. If unsure, say N.
2547 prompt "Use MMIO instead of PIO" if PCI || EISA
2549 default n if PCI || EISA
2552 This instructs the driver to use EISA or PCI memory-mapped I/O
2553 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2554 Enabling this gives an improvement in processing time in parts
2555 of the driver, but it may cause problems with EISA (DEFEA)
2556 adapters. TURBOchannel does not have the concept of I/O ports,
2557 so MMIO is always used for these (DEFTA) adapters.
2562 tristate "SysKonnect FDDI PCI support"
2563 depends on FDDI && PCI
2566 Say Y here if you have a SysKonnect FDDI PCI adapter.
2567 The following adapters are supported by this driver:
2568 - SK-5521 (SK-NET FDDI-UP)
2569 - SK-5522 (SK-NET FDDI-UP DAS)
2570 - SK-5541 (SK-NET FDDI-FP)
2571 - SK-5543 (SK-NET FDDI-LP)
2572 - SK-5544 (SK-NET FDDI-LP DAS)
2573 - SK-5821 (SK-NET FDDI-UP64)
2574 - SK-5822 (SK-NET FDDI-UP64 DAS)
2575 - SK-5841 (SK-NET FDDI-FP64)
2576 - SK-5843 (SK-NET FDDI-LP64)
2577 - SK-5844 (SK-NET FDDI-LP64 DAS)
2578 - Netelligent 100 FDDI DAS Fibre SC
2579 - Netelligent 100 FDDI SAS Fibre SC
2580 - Netelligent 100 FDDI DAS UTP
2581 - Netelligent 100 FDDI SAS UTP
2582 - Netelligent 100 FDDI SAS Fibre MIC
2584 Read <file:Documentation/networking/skfp.txt> for information about
2587 Questions concerning this driver can be addressed to:
2588 <linux@syskonnect.de>
2590 To compile this driver as a module, choose M here: the module
2591 will be called skfp. This is recommended.
2594 bool "HIPPI driver support (EXPERIMENTAL)"
2595 depends on EXPERIMENTAL && INET && PCI
2597 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2598 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2599 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2600 single-mode). HIPPI networks are commonly used for clusters and to
2601 connect to super computers. If you are connected to a HIPPI network
2602 and have a HIPPI network card in your computer that you want to use
2603 under Linux, say Y here (you must also remember to enable the driver
2604 for your HIPPI card below). Most people will say N here.
2607 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2608 depends on HIPPI && PCI
2610 Say Y here if this is your PCI HIPPI network card.
2612 To compile this driver as a module, choose M here: the module
2613 will be called rrunner. If unsure, say N.
2615 config ROADRUNNER_LARGE_RINGS
2616 bool "Use large TX/RX rings (EXPERIMENTAL)"
2617 depends on ROADRUNNER
2619 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2620 of additional memory to allow for fastest operation, both for
2621 transmitting and receiving. This memory cannot be used by any other
2622 kernel code or by user space programs. Say Y here only if you have
2626 tristate "PLIP (parallel port) support"
2629 PLIP (Parallel Line Internet Protocol) is used to create a
2630 reasonably fast mini network consisting of two (or, rarely, more)
2631 local machines. A PLIP link from a Linux box is a popular means to
2632 install a Linux distribution on a machine which doesn't have a
2633 CD-ROM drive (a minimal system has to be transferred with floppies
2634 first). The kernels on both machines need to have this PLIP option
2635 enabled for this to work.
2637 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2638 ports (the connectors at the computers with 25 holes) are connected
2639 with "null printer" or "Turbo Laplink" cables which can transmit 4
2640 bits at a time (mode 0) or with special PLIP cables, to be used on
2641 bidirectional parallel ports only, which can transmit 8 bits at a
2642 time (mode 1); you can find the wiring of these cables in
2643 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2644 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2645 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2646 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2647 and winsock or NCSA's telnet.
2649 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2650 as the NET-3-HOWTO, both available from
2651 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2652 protocol has been changed and this PLIP driver won't work together
2653 with the PLIP support in Linux versions 1.0.x. This option enlarges
2654 your kernel by about 8 KB.
2656 To compile this driver as a module, choose M here and read
2657 <file:Documentation/networking/net-modules.txt>. The module will be
2658 called plip. If unsure, say Y or M, in case you buy a laptop
2662 tristate "PPP (point-to-point protocol) support"
2665 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2666 the same purpose: sending Internet traffic over telephone (and other
2667 serial) lines. Ask your access provider if they support it, because
2668 otherwise you can't use it; most Internet access providers these
2669 days support PPP rather than SLIP.
2671 To use PPP, you need an additional program called pppd as described
2672 in the PPP-HOWTO, available at
2673 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2674 the version of pppd recommended in <file:Documentation/Changes>.
2675 The PPP option enlarges your kernel by about 16 KB.
2677 There are actually two versions of PPP: the traditional PPP for
2678 asynchronous lines, such as regular analog phone lines, and
2679 synchronous PPP which can be used over digital ISDN lines for
2680 example. If you want to use PPP over phone lines or other
2681 asynchronous serial lines, you need to say Y (or M) here and also to
2682 the next option, "PPP support for async serial ports". For PPP over
2683 synchronous lines, you should say Y (or M) here and to "Support
2684 synchronous PPP", below.
2686 If you said Y to "Version information on all symbols" above, then
2687 you cannot compile the PPP driver into the kernel; you can then only
2688 compile it as a module. To compile this driver as a module, choose M
2689 here and read <file:Documentation/networking/net-modules.txt>.
2690 The module will be called ppp_generic.
2692 config PPP_MULTILINK
2693 bool "PPP multilink support (EXPERIMENTAL)"
2694 depends on PPP && EXPERIMENTAL
2696 PPP multilink is a protocol (defined in RFC 1990) which allows you
2697 to combine several (logical or physical) lines into one logical PPP
2698 connection, so that you can utilize your full bandwidth.
2700 This has to be supported at the other end as well and you need a
2701 version of the pppd daemon which understands the multilink protocol.
2706 bool "PPP filtering"
2709 Say Y here if you want to be able to filter the packets passing over
2710 PPP interfaces. This allows you to control which packets count as
2711 activity (i.e. which packets will reset the idle timer or bring up
2712 a demand-dialed link) and which packets are to be dropped entirely.
2713 You need to say Y here if you wish to use the pass-filter and
2714 active-filter options to pppd.
2719 tristate "PPP support for async serial ports"
2723 Say Y (or M) here if you want to be able to use PPP over standard
2724 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2725 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2728 To compile this driver as a module, choose M here.
2733 tristate "PPP support for sync tty ports"
2736 Say Y (or M) here if you want to be able to use PPP over synchronous
2737 (HDLC) tty devices, such as the SyncLink adapter. These devices
2738 are often used for high-speed leased lines like T1/E1.
2740 To compile this driver as a module, choose M here.
2743 tristate "PPP Deflate compression"
2748 Support for the Deflate compression method for PPP, which uses the
2749 Deflate algorithm (the same algorithm that gzip uses) to compress
2750 each PPP packet before it is sent over the wire. The machine at the
2751 other end of the PPP link (usually your ISP) has to support the
2752 Deflate compression method as well for this to be useful. Even if
2753 they don't support it, it is safe to say Y here.
2755 To compile this driver as a module, choose M here.
2758 tristate "PPP BSD-Compress compression"
2761 Support for the BSD-Compress compression method for PPP, which uses
2762 the LZW compression method to compress each PPP packet before it is
2763 sent over the wire. The machine at the other end of the PPP link
2764 (usually your ISP) has to support the BSD-Compress compression
2765 method as well for this to be useful. Even if they don't support it,
2766 it is safe to say Y here.
2768 The PPP Deflate compression method ("PPP Deflate compression",
2769 above) is preferable to BSD-Compress, because it compresses better
2772 Note that the BSD compression code will always be compiled as a
2773 module; it is called bsd_comp and will show up in the directory
2774 modules once you have said "make modules". If unsure, say N.
2777 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2778 depends on PPP && EXPERIMENTAL
2784 Support for the MPPE Encryption protocol, as employed by the
2785 Microsoft Point-to-Point Tunneling Protocol.
2787 See http://pptpclient.sourceforge.net/ for information on
2788 configuring PPTP clients and servers to utilize this method.
2791 tristate "PPP over Ethernet (EXPERIMENTAL)"
2792 depends on EXPERIMENTAL && PPP
2794 Support for PPP over Ethernet.
2796 This driver requires the latest version of pppd from the CVS
2797 repository at cvs.samba.org. Alternatively, see the
2798 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2799 which contains instruction on how to use this driver (under
2800 the heading "Kernel mode PPPoE").
2803 tristate "PPP over ATM"
2804 depends on ATM && PPP
2806 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2807 This implementation does not yet comply with section 8 of RFC2364,
2808 which can lead to bad results if the ATM peer loses state and
2809 changes its encapsulation unilaterally.
2812 tristate "PPP over L2TP (EXPERIMENTAL)"
2813 depends on EXPERIMENTAL && PPP
2815 Support for PPP-over-L2TP socket family. L2TP is a protocol
2816 used by ISPs and enterprises to tunnel PPP traffic over UDP
2817 tunnels. L2TP is replacing PPTP for VPN uses.
2819 This kernel component handles only L2TP data packets: a
2820 userland daemon handles L2TP the control protocol (tunnel
2821 and session setup). One such daemon is OpenL2TP
2822 (http://openl2tp.sourceforge.net/).
2825 tristate "SLIP (serial line) support"
2827 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2828 connect to your Internet service provider or to connect to some
2829 other local Unix box or if you want to configure your Linux box as a
2830 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2831 Internet Protocol) is a protocol used to send Internet traffic over
2832 serial connections such as telephone lines or null modem cables;
2833 nowadays, the protocol PPP is more commonly used for this same
2836 Normally, your access provider has to support SLIP in order for you
2837 to be able to use it, but there is now a SLIP emulator called SLiRP
2838 around (available from
2839 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2840 allows you to use SLIP over a regular dial up shell connection. If
2841 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2842 NET-3-HOWTO, available from
2843 <http://www.tldp.org/docs.html#howto>, explains how to
2844 configure SLIP. Note that you don't need this option if you just
2845 want to run term (term is a program which gives you almost full
2846 Internet connectivity if you have a regular dial up shell account on
2847 some Internet connected Unix computer. Read
2848 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2849 support will enlarge your kernel by about 4 KB. If unsure, say N.
2851 To compile this driver as a module, choose M here and read
2852 <file:Documentation/networking/net-modules.txt>. The module will be
2855 config SLIP_COMPRESSED
2856 bool "CSLIP compressed headers"
2860 This protocol is faster than SLIP because it uses compression on the
2861 TCP/IP headers (not on the data itself), but it has to be supported
2862 on both ends. Ask your access provider if you are not sure and
2863 answer Y, just in case. You will still be able to use plain SLIP. If
2864 you plan to use SLiRP, the SLIP emulator (available from
2865 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2866 allows you to use SLIP over a regular dial up shell connection, you
2867 definitely want to say Y here. The NET-3-HOWTO, available from
2868 <http://www.tldp.org/docs.html#howto>, explains how to configure
2869 CSLIP. This won't enlarge your kernel.
2874 This option enables Van Jacobsen serial line header compression
2878 bool "Keepalive and linefill"
2881 Adds additional capabilities to the SLIP driver to support the
2882 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2885 config SLIP_MODE_SLIP6
2886 bool "Six bit SLIP encapsulation"
2889 Just occasionally you may need to run IP over hostile serial
2890 networks that don't pass all control characters or are only seven
2891 bit. Saying Y here adds an extra mode you can use with SLIP:
2892 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2893 the serial device. Naturally, this has to be supported at the other
2894 end of the link as well. It's good enough, for example, to run IP
2895 over the async ports of a Camtec JNT Pad. If unsure, say N.
2898 bool "Fibre Channel driver support"
2899 depends on SCSI && PCI
2901 Fibre Channel is a high speed serial protocol mainly used to connect
2902 large storage devices to the computer; it is compatible with and
2903 intended to replace SCSI.
2905 If you intend to use Fibre Channel, you need to have a Fibre channel
2906 adaptor card in your computer; say Y here and to the driver for your
2907 adaptor below. You also should have said Y to "SCSI support" and
2908 "SCSI generic support".
2911 tristate "Traffic Shaper (OBSOLETE)"
2912 depends on EXPERIMENTAL
2914 The traffic shaper is a virtual network device that allows you to
2915 limit the rate of outgoing data flow over some other network device.
2916 The traffic that you want to slow down can then be routed through
2917 these virtual devices. See
2918 <file:Documentation/networking/shaper.txt> for more information.
2920 An alternative to this traffic shaper are traffic schedulers which
2921 you'll get if you say Y to "QoS and/or fair queuing" in
2922 "Networking options".
2924 To compile this driver as a module, choose M here: the module
2925 will be called shaper. If unsure, say N.
2928 tristate "Network console logging support (EXPERIMENTAL)"
2929 depends on EXPERIMENTAL
2931 If you want to log kernel messages over the network, enable this.
2932 See <file:Documentation/networking/netconsole.txt> for details.
2938 bool "Netpoll traffic trapping"
2942 config NET_POLL_CONTROLLER