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>.
25 tristate "Dummy net driver support"
28 This is essentially a bit-bucket device (i.e. traffic you send to
29 this device is consigned into oblivion) with a configurable IP
30 address. It is most commonly used in order to make your currently
31 inactive SLIP address seem like a real address for local programs.
32 If you use SLIP or PPP, you might want to say Y here. Since this
33 thing often comes in handy, the default is Y. It won't enlarge your
34 kernel either. What a deal. Read about it in the Network
35 Administrator's Guide, available from
36 <http://www.tldp.org/docs.html#guide>.
38 To compile this driver as a module, choose M here: the module
39 will be called dummy. If you want to use more than one dummy
40 device at a time, you need to compile this driver as a module.
41 Instead of 'dummy', the devices will then be called 'dummy0',
45 tristate "Bonding driver support"
49 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
50 Channels together. This is called 'Etherchannel' by Cisco,
51 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
53 The driver supports multiple bonding modes to allow for both high
54 perfomance and high availability operation.
56 Refer to <file:Documentation/networking/bonding.txt> for more
59 To compile this driver as a module, choose M here: the module
60 will be called bonding.
63 tristate "EQL (serial line load balancing) support"
66 If you have two serial connections to some other computer (this
67 usually requires two modems and two telephone lines) and you use
68 SLIP (the protocol for sending Internet traffic over telephone
69 lines) or PPP (a better SLIP) on them, you can make them behave like
70 one double speed connection using this driver. Naturally, this has
71 to be supported at the other end as well, either with a similar EQL
72 Linux driver or with a Livingston Portmaster 2e.
74 Say Y if you want this and read
75 <file:Documentation/networking/eql.txt>. You may also want to read
76 section 6.2 of the NET-3-HOWTO, available from
77 <http://www.tldp.org/docs.html#howto>.
79 To compile this driver as a module, choose M here: the module
80 will be called eql. If unsure, say N.
83 tristate "Universal TUN/TAP device driver support"
87 TUN/TAP provides packet reception and transmission for user space
88 programs. It can be viewed as a simple Point-to-Point or Ethernet
89 device, which instead of receiving packets from a physical media,
90 receives them from user space program and instead of sending packets
91 via physical media writes them to the user space program.
93 When a program opens /dev/net/tun, driver creates and registers
94 corresponding net device tunX or tapX. After a program closed above
95 devices, driver will automatically delete tunXX or tapXX device and
96 all routes corresponding to it.
98 Please read <file:Documentation/networking/tuntap.txt> for more
101 To compile this driver as a module, choose M here: the module
104 If you don't know what to use this for, you don't need it.
107 tristate "General Instruments Surfboard 1000"
108 depends on NETDEVICES && PNP
110 This is a driver for the General Instrument (also known as
111 NextLevel) SURFboard 1000 internal
112 cable modem. This is an ISA card which is used by a number of cable
113 TV companies to provide cable modem access. It's a one-way
114 downstream-only cable modem, meaning that your upstream net link is
115 provided by your regular phone modem.
117 At present this driver only compiles as a module, so say M here if
118 you have this card. The module will be called sb1000. Then read
119 <file:Documentation/networking/README.sb1000> for information on how
120 to use this module, as it needs special ppp scripts for establishing
121 a connection. Further documentation and the necessary scripts can be
124 <http://www.jacksonville.net/~fventuri/>
125 <http://home.adelphia.net/~siglercm/sb1000.html>
126 <http://linuxpower.cx/~cable/>
128 If you don't have this card, of course say N.
131 source "drivers/net/arcnet/Kconfig"
138 menu "Ethernet (10 or 100Mbit)"
139 depends on NETDEVICES && !UML
142 bool "Ethernet (10 or 100Mbit)"
144 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
145 type of Local Area Network (LAN) in universities and companies.
147 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
148 coaxial cable, linking computers in a chain), 10BASE-T or twisted
149 pair (10 Mbps over twisted pair cable, linking computers to central
150 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
151 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
152 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
153 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
154 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
155 Ethernet (1 Gbps over optical fiber or short copper links).
157 If your Linux machine will be connected to an Ethernet and you have
158 an Ethernet network interface card (NIC) installed in your computer,
159 say Y here and read the Ethernet-HOWTO, available from
160 <http://www.tldp.org/docs.html#howto>. You will then also have
161 to say Y to the driver for your particular NIC.
163 Note that the answer to this question won't directly affect the
164 kernel: saying N will just cause the configurator to skip all
165 the questions about Ethernet network cards. If unsure, say N.
168 tristate "Generic Media Independent Interface device support"
169 depends on NET_ETHERNET
171 Most ethernet controllers have MII transceiver either as an external
172 or internal device. It is safe to say Y or M here even if your
173 ethernet card lack MII.
175 source "drivers/net/arm/Kconfig"
178 tristate "MACE (Power Mac ethernet) support"
179 depends on NET_ETHERNET && PPC_PMAC && PPC32
182 Power Macintoshes and clones with Ethernet built-in on the
183 motherboard will usually use a MACE (Medium Access Control for
184 Ethernet) interface. Say Y to include support for the MACE chip.
186 To compile this driver as a module, choose M here: the module
189 config MACE_AAUI_PORT
190 bool "Use AAUI port instead of TP by default"
193 Some Apple machines (notably the Apple Network Server) which use the
194 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
195 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
196 Y here if you have such a machine. If unsure, say N.
197 The driver will default to AAUI on ANS anyway, and if you use it as
198 a module, you can provide the port_aaui=0|1 to force the driver.
201 tristate "BMAC (G3 ethernet) support"
202 depends on NET_ETHERNET && PPC_PMAC && PPC32
205 Say Y for support of BMAC Ethernet interfaces. These are used on G3
208 To compile this driver as a module, choose M here: the module
212 tristate "National DP83902AV (Oak ethernet) support"
213 depends on NET_ETHERNET && PPC && BROKEN
216 Say Y if your machine has this type of Ethernet network card.
218 To compile this driver as a module, choose M here: the module
219 will be called oaknet.
222 tristate "Ariadne support"
223 depends on NET_ETHERNET && ZORRO
225 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
228 To compile this driver as a module, choose M here: the module
229 will be called ariadne.
232 tristate "A2065 support"
233 depends on NET_ETHERNET && ZORRO
236 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
239 To compile this driver as a module, choose M here: the module
240 will be called a2065.
243 tristate "Hydra support"
244 depends on NET_ETHERNET && ZORRO
247 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
249 To compile this driver as a module, choose M here: the module
250 will be called hydra.
253 tristate "Zorro NS8390-based Ethernet support"
254 depends on NET_ETHERNET && ZORRO
257 This driver is for Zorro Ethernet cards using an NS8390-compatible
258 chipset, like the Village Tronic Ariadne II and the Individual
259 Computers X-Surf Ethernet cards. If you have such a card, say Y.
262 To compile this driver as a module, choose M here: the module
263 will be called zorro8390.
266 tristate "PCMCIA NE2000 support"
267 depends on NET_ETHERNET && AMIGA_PCMCIA
270 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
273 To compile this driver as a module, choose M here: the module
277 tristate "Apollo 3c505 support"
278 depends on NET_ETHERNET && APOLLO
280 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
281 If you don't have one made for Apollos, you can use one from a PC,
282 except that your Apollo won't be able to boot from it (because the
283 code in the ROM will be for a PC).
286 bool "Macintosh NS 8390 based ethernet cards"
287 depends on NET_ETHERNET && MAC
290 If you want to include a driver to support Nubus or LC-PDS
291 Ethernet cards using an NS8390 chipset or its equivalent, say Y
292 and read the Ethernet-HOWTO, available from
293 <http://www.tldp.org/docs.html#howto>.
296 tristate "Macintosh CS89x0 based ethernet cards"
297 depends on NET_ETHERNET && MAC && BROKEN
299 Support for CS89x0 chipset based Ethernet cards. If you have a
300 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
301 read the Ethernet-HOWTO, available from
302 <http://www.tldp.org/docs.html#howto>.
304 To compile this driver as a module, choose M here and read
305 <file:Documentation/networking/net-modules.txt>. This module will
309 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
310 depends on NET_ETHERNET && MAC
312 Support for NatSemi SONIC based Ethernet devices. This includes
313 the onboard Ethernet in many Quadras as well as some LC-PDS,
314 a few Nubus and all known Comm Slot Ethernet cards. If you have
315 one of these say Y and read the Ethernet-HOWTO, available from
316 <http://www.tldp.org/docs.html#howto>.
318 To compile this driver as a module, choose M here and read
319 <file:Documentation/networking/net-modules.txt>. This module will
323 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
324 depends on NET_ETHERNET && MAC && EXPERIMENTAL
327 Support for the onboard AMD 79C940 MACE Ethernet controller used in
328 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
329 say Y and read the Ethernet-HOWTO, available from
330 <http://www.tldp.org/docs.html#howto>.
333 tristate "MVME147 (Lance) Ethernet support"
334 depends on NET_ETHERNET && MVME147
337 Support for the on-board Ethernet interface on the Motorola MVME147
338 single-board computer. Say Y here to include the
339 driver for this chip in your kernel.
340 To compile this driver as a module, choose M here.
343 tristate "MVME16x Ethernet support"
344 depends on NET_ETHERNET && MVME16x
346 This is the driver for the Ethernet interface on the Motorola
347 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
348 driver for this chip in your kernel.
349 To compile this driver as a module, choose M here.
352 tristate "BVME6000 Ethernet support"
353 depends on NET_ETHERNET && BVME6000
355 This is the driver for the Ethernet interface on BVME4000 and
356 BVME6000 VME boards. Say Y here to include the driver for this chip
358 To compile this driver as a module, choose M here.
361 tristate "Atari Lance support"
362 depends on NET_ETHERNET && ATARI
364 Say Y to include support for several Atari Ethernet adapters based
365 on the AMD Lance chipset: RieblCard (with or without battery), or
366 PAMCard VME (also the version by Rhotron, with different addresses).
369 tristate "BioNet-100 support"
370 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
372 Say Y to include support for BioData's BioNet-100 Ethernet adapter
373 for the ACSI port. The driver works (has to work...) with a polled
374 I/O scheme, so it's rather slow :-(
377 tristate "PAMsNet support"
378 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
380 Say Y to include support for the PAMsNet Ethernet adapter for the
381 ACSI port ("ACSI node"). The driver works (has to work...) with a
382 polled I/O scheme, so it's rather slow :-(
385 tristate "Sun3/Sun3x on-board LANCE support"
386 depends on NET_ETHERNET && (SUN3 || SUN3X)
388 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
389 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
390 here to compile in the Linux driver for this and enable Ethernet.
391 General Linux information on the Sun 3 and 3x series (now
393 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
395 If you're not building a kernel for a Sun 3, say N.
398 tristate "Sun3 on-board Intel 82586 support"
399 depends on NET_ETHERNET && SUN3
401 This driver enables support for the on-board Intel 82586 based
402 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
403 that this driver does not support 82586-based adapters on additional
407 bool "HP on-board LANCE support"
408 depends on NET_ETHERNET && DIO
411 If you want to use the builtin "LANCE" Ethernet controller on an
412 HP300 machine, say Y here.
415 tristate "Lasi ethernet"
416 depends on NET_ETHERNET && PARISC && GSC_LASI
418 Say Y here to support the on-board Intel 82596 ethernet controller
419 built into Hewlett-Packard PA-RISC machines.
421 config MIPS_JAZZ_SONIC
422 tristate "MIPS JAZZ onboard SONIC Ethernet support"
423 depends on NET_ETHERNET && MACH_JAZZ
425 This is the driver for the onboard card of MIPS Magnum 4000,
426 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
428 config MIPS_GT96100ETH
429 bool "MIPS GT96100 Ethernet support"
430 depends on NET_ETHERNET && MIPS_GT96100
432 Say Y here to support the Ethernet subsystem on your GT96100 card.
434 config MIPS_AU1X00_ENET
435 bool "MIPS AU1000 Ethernet support"
436 depends on NET_ETHERNET && SOC_AU1X00
439 If you have an Alchemy Semi AU1X00 based system
440 say Y. Otherwise, say N.
442 config NET_SB1250_MAC
443 tristate "SB1250 Ethernet support"
444 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
447 bool "SGI IOC3 Ethernet"
448 depends on NET_ETHERNET && PCI && SGI_IP27
452 If you have a network (Ethernet) card of this type, say Y and read
453 the Ethernet-HOWTO, available from
454 <http://www.tldp.org/docs.html#howto>.
456 config SGI_IOC3_ETH_HW_RX_CSUM
457 bool "Receive hardware checksums"
458 depends on SGI_IOC3_ETH && INET
461 The SGI IOC3 network adapter supports TCP and UDP checksums in
462 hardware to offload processing of these checksums from the CPU. At
463 the moment only acceleration of IPv4 is supported. This option
464 enables offloading for checksums on receive. If unsure, say Y.
466 config SGI_IOC3_ETH_HW_TX_CSUM
467 bool "Transmit hardware checksums"
468 depends on SGI_IOC3_ETH && INET
471 The SGI IOC3 network adapter supports TCP and UDP checksums in
472 hardware to offload processing of these checksums from the CPU. At
473 the moment only acceleration of IPv4 is supported. This option
474 enables offloading for checksums on transmit. If unsure, say Y.
476 config SGI_O2MACE_ETH
477 tristate "SGI O2 MACE Fast Ethernet support"
478 depends on NET_ETHERNET && SGI_IP32=y
481 tristate "National DP83902AV support"
482 depends on NET_ETHERNET && SUPERH
485 Support for cards based on the National Semiconductor DP83902AV
486 ST-NIC Serial Network Interface Controller for Twisted Pair. This
487 is a 10Mbit/sec Ethernet controller. Product overview and specs at
488 <http://www.national.com/pf/DP/DP83902A.html>.
493 tristate "Sun LANCE support"
494 depends on NET_ETHERNET && SBUS
497 This driver supports the "le" interface present on all 32-bit Sparc
498 systems, on some older Ultra systems and as an Sbus option. These
499 cards are based on the AMD Lance chipset, which is better known
500 via the NE2100 cards.
502 To compile this driver as a module, choose M here: the module
503 will be called sunlance.
506 tristate "Sun Happy Meal 10/100baseT support"
507 depends on NET_ETHERNET && (SBUS || PCI)
510 This driver supports the "hme" interface present on most Ultra
511 systems and as an option on older Sbus systems. This driver supports
512 both PCI and Sbus devices. This driver also supports the "qfe" quad
513 100baseT device available in both PCI and Sbus configurations.
515 To compile this driver as a module, choose M here: the module
516 will be called sunhme.
519 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
520 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
523 This driver supports the "be" interface available as an Sbus option.
524 This is Sun's older 100baseT Ethernet device.
526 To compile this driver as a module, choose M here: the module
527 will be called sunbmac.
530 tristate "Sun QuadEthernet support"
531 depends on NET_ETHERNET && SBUS
534 This driver supports the "qe" 10baseT Ethernet device, available as
535 an Sbus option. Note that this is not the same as Quad FastEthernet
536 "qfe" which is supported by the Happy Meal driver instead.
538 To compile this driver as a module, choose M here: the module
539 will be called sunqe.
542 tristate "Sun GEM support"
543 depends on NET_ETHERNET && PCI
546 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
547 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
549 config NET_VENDOR_3COM
551 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
553 If you have a network (Ethernet) card belonging to this class, say Y
554 and read the Ethernet-HOWTO, available from
555 <http://www.tldp.org/docs.html#howto>.
557 Note that the answer to this question doesn't directly affect the
558 kernel: saying N will just cause the configurator to skip all
559 the questions about 3COM cards. If you say Y, you will be asked for
560 your specific card in the following questions.
563 tristate "3c501 \"EtherLink\" support"
564 depends on NET_VENDOR_3COM && ISA
566 If you have a network (Ethernet) card of this type, say Y and read
567 the Ethernet-HOWTO, available from
568 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
569 new card, since the 3c501 is slow, broken, and obsolete: you will
570 have problems. Some people suggest to ping ("man ping") a nearby
571 machine every minute ("man cron") when using this card.
573 To compile this driver as a module, choose M here and read
574 <file:Documentation/networking/net-modules.txt>. The module
575 will be called 3c501.
578 tristate "3c503 \"EtherLink II\" support"
579 depends on NET_VENDOR_3COM && ISA
582 If you have a network (Ethernet) card of this type, say Y and read
583 the Ethernet-HOWTO, available from
584 <http://www.tldp.org/docs.html#howto>.
586 To compile this driver as a module, choose M here and read
587 <file:Documentation/networking/net-modules.txt>. The module
588 will be called 3c503.
591 tristate "3c505 \"EtherLink Plus\" support"
592 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
594 Information about this network (Ethernet) card can be found in
595 <file:Documentation/networking/3c505.txt>. If you have a card of
596 this type, say Y and read the Ethernet-HOWTO, available from
597 <http://www.tldp.org/docs.html#howto>.
599 To compile this driver as a module, choose M here and read
600 <file:Documentation/networking/net-modules.txt>. The module
601 will be called 3c505.
604 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
605 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
607 If you have a network (Ethernet) card of this type, say Y and read
608 the Ethernet-HOWTO, available from
609 <http://www.tldp.org/docs.html#howto>.
611 To compile this driver as a module, choose M here and read
612 <file:Documentation/networking/net-modules.txt>. The module
613 will be called 3c507.
616 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
617 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
619 If you have a network (Ethernet) card belonging to the 3Com
620 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
621 from <http://www.tldp.org/docs.html#howto>.
623 If your card is not working you may need to use the DOS
624 setup disk to disable Plug & Play mode, and to select the default
627 To compile this driver as a module, choose M here and read
628 <file:Documentation/networking/net-modules.txt>. The module
629 will be called 3c509.
632 tristate "3c515 ISA \"Fast EtherLink\""
633 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
635 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
636 network card, say Y and read the Ethernet-HOWTO, available from
637 <http://www.tldp.org/docs.html#howto>.
639 To compile this driver as a module, choose M here and read
640 <file:Documentation/networking/net-modules.txt>. The module
641 will be called 3c515.
644 tristate "3c523 \"EtherLink/MC\" support"
645 depends on NET_VENDOR_3COM && MCA_LEGACY
647 If you have a network (Ethernet) card of this type, say Y and read
648 the Ethernet-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>.
651 To compile this driver as a module, choose M here and read
652 <file:Documentation/networking/net-modules.txt>. The module
653 will be called 3c523.
656 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
657 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
659 If you have a network (Ethernet) card of this type, say Y and read
660 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 3c527.
668 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
669 depends on NET_VENDOR_3COM && (PCI || EISA)
672 This option enables driver support for a large number of 10mbps and
673 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
675 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
676 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
677 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
678 "Tornado" (3c905) PCI
679 "Hurricane" (3c555/3cSOHO) PCI
681 If you have such a card, say Y and read the Ethernet-HOWTO,
682 available from <http://www.tldp.org/docs.html#howto>. More
683 specific information is in
684 <file:Documentation/networking/vortex.txt> and in the comments at
685 the beginning of <file:drivers/net/3c59x.c>.
687 To compile this support as a module, choose M here and read
688 <file:Documentation/networking/net-modules.txt>.
691 tristate "3cr990 series \"Typhoon\" support"
692 depends on NET_VENDOR_3COM && PCI
695 This option enables driver support for the 3cr990 series of cards:
697 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
698 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
699 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
701 If you have a network (Ethernet) card of this type, say Y and read
702 the Ethernet-HOWTO, available from
703 <http://www.tldp.org/docs.html#howto>.
705 To compile this driver as a module, choose M here and read
706 <file:Documentation/networking/net-modules.txt>. The module
707 will be called typhoon.
710 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
711 depends on NET_ETHERNET && ISA && ISA_DMA_API
713 If you have a network (Ethernet) card of this type, say Y and read
714 the Ethernet-HOWTO, available from
715 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
718 To compile this driver as a module, choose M here: the module
719 will be called lance. This is recommended.
721 config NET_VENDOR_SMC
722 bool "Western Digital/SMC cards"
723 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
725 If you have a network (Ethernet) card belonging to this class, say Y
726 and read the Ethernet-HOWTO, available from
727 <http://www.tldp.org/docs.html#howto>.
729 Note that the answer to this question doesn't directly affect the
730 kernel: saying N will just cause the configurator to skip all
731 the questions about Western Digital cards. If you say Y, you will be
732 asked for your specific card in the following questions.
735 tristate "WD80*3 support"
736 depends on NET_VENDOR_SMC && ISA
739 If you have a network (Ethernet) card of this type, say Y and read
740 the Ethernet-HOWTO, available from
741 <http://www.tldp.org/docs.html#howto>.
743 To compile this driver as a module, choose M here and read
744 <file:Documentation/networking/net-modules.txt>. The module
748 tristate "SMC Ultra MCA support"
749 depends on NET_VENDOR_SMC && MCA
752 If you have a network (Ethernet) card of this type and are running
753 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
754 available from <http://www.tldp.org/docs.html#howto>.
756 To compile this driver as a module, choose M here and read
757 <file:Documentation/networking/net-modules.txt>. The module
758 will be called smc-mca.
761 tristate "SMC Ultra support"
762 depends on NET_VENDOR_SMC && ISA
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 Important: There have been many reports that, with some motherboards
770 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
771 such as some BusLogic models) causes corruption problems with many
772 operating systems. The Linux smc-ultra driver has a work-around for
773 this but keep it in mind if you have such a SCSI card and have
776 To compile this driver as a module, choose M here and read
777 <file:Documentation/networking/net-modules.txt>. The module
778 will be called smc-ultra.
781 tristate "SMC Ultra32 EISA support"
782 depends on NET_VENDOR_SMC && EISA
785 If you have a network (Ethernet) card of this type, say Y and read
786 the Ethernet-HOWTO, available from
787 <http://www.tldp.org/docs.html#howto>.
789 To compile this driver as a module, choose M here and read
790 <file:Documentation/networking/net-modules.txt>. The module
791 will be called smc-ultra32.
794 tristate "SMC 91C9x/91C1xxx support"
797 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH)
799 This is a driver for SMC's 91x series of Ethernet chipsets,
800 including the SMC91C94 and the SMC91C111. Say Y if you want it
801 compiled into the kernel, and read the file
802 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
803 available from <http://www.linuxdoc.org/docs.html#howto>.
805 This driver is also available as a module ( = code which can be
806 inserted in and removed from the running kernel whenever you want).
807 The module will be called smc91x. If you want to compile it as a
808 module, say M here and read <file:Documentation/modules.txt> as well
809 as <file:Documentation/networking/net-modules.txt>.
812 tristate "SMC 9194 support"
813 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
816 This is support for the SMC9xxx based Ethernet cards. Choose this
817 option if you have a DELL laptop with the docking station, or
818 another SMC9192/9194 based chipset. Say Y if you want it compiled
819 into the kernel, and read the file
820 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
821 available from <http://www.tldp.org/docs.html#howto>.
823 To compile this driver as a module, choose M here and read
824 <file:Documentation/networking/net-modules.txt>. The module
825 will be called smc9194.
828 tristate "DM9000 support"
829 depends on ARM && NET_ETHERNET
833 Support for DM9000 chipset.
835 To compile this driver as a module, choose M here and read
836 <file:Documentation/networking/net-modules.txt>. The module will be
839 config NET_VENDOR_RACAL
840 bool "Racal-Interlan (Micom) NI cards"
841 depends on NET_ETHERNET && ISA
843 If you have a network (Ethernet) card belonging to this class, such
844 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
845 available from <http://www.tldp.org/docs.html#howto>.
847 Note that the answer to this question doesn't directly affect the
848 kernel: saying N will just cause the configurator to skip all
849 the questions about NI cards. If you say Y, you will be asked for
850 your specific card in the following questions.
853 tristate "NI5010 support (EXPERIMENTAL)"
854 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
856 If you have a network (Ethernet) card of this type, say Y and read
857 the Ethernet-HOWTO, available from
858 <http://www.tldp.org/docs.html#howto>. Note that this is still
861 To compile this driver as a module, choose M here and read
862 <file:Documentation/networking/net-modules.txt>. The module
863 will be called ni5010.
866 tristate "NI5210 support"
867 depends on NET_VENDOR_RACAL && ISA
869 If you have a network (Ethernet) card of this type, say Y and read
870 the Ethernet-HOWTO, available from
871 <http://www.tldp.org/docs.html#howto>.
873 To compile this driver as a module, choose M here and read
874 <file:Documentation/networking/net-modules.txt>. The module
878 tristate "NI6510 support"
879 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
881 If you have a network (Ethernet) card of this type, say Y and read
882 the Ethernet-HOWTO, available from
883 <http://www.tldp.org/docs.html#howto>.
885 To compile this driver as a module, choose M here and read
886 <file:Documentation/networking/net-modules.txt>. The module
889 source "drivers/net/tulip/Kconfig"
892 tristate "AT1700/1720 support (EXPERIMENTAL)"
893 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
896 If you have a network (Ethernet) card of this type, say Y and read
897 the Ethernet-HOWTO, available from
898 <http://www.tldp.org/docs.html#howto>.
900 To compile this driver as a module, choose M here and read
901 <file:Documentation/networking/net-modules.txt>. The module
902 will be called at1700.
905 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
906 depends on NET_ETHERNET && (ISA || EISA || MCA)
909 If you have a network (Ethernet) card of this type, say Y and read
910 the Ethernet-HOWTO, available from
911 <http://www.tldp.org/docs.html#howto> as well as
912 <file:drivers/net/depca.c>.
914 To compile this driver as a module, choose M here and read
915 <file:Documentation/networking/net-modules.txt>. The module
916 will be called depca.
919 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
920 depends on NET_ETHERNET && (ISA || EISA || PCI)
922 If you have a network (Ethernet) card of this type, say Y and read
923 the Ethernet-HOWTO, available from
924 <http://www.tldp.org/docs.html#howto>.
926 To compile this driver as a module, choose M here and read
927 <file:Documentation/networking/net-modules.txt>. The module
928 will be called hp100.
931 bool "Other ISA cards"
932 depends on NET_ETHERNET && ISA
934 If your network (Ethernet) card hasn't been mentioned yet and its
935 bus system (that's the way the cards talks to the other components
936 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
937 Make sure you know the name of your card. Read the Ethernet-HOWTO,
938 available from <http://www.tldp.org/docs.html#howto>.
942 Note that the answer to this question doesn't directly affect the
943 kernel: saying N will just cause the configurator to skip all
944 the remaining ISA network card questions. If you say Y, you will be
945 asked for your specific card in the following questions.
948 tristate "Cabletron E21xx support"
952 If you have a network (Ethernet) card of this type, say Y and read
953 the Ethernet-HOWTO, available from
954 <http://www.tldp.org/docs.html#howto>.
956 To compile this driver as a module, choose M here and read
957 <file:Documentation/networking/net-modules.txt>. The module
958 will be called e2100.
961 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
965 This driver supports the DE203, DE204 and DE205 network (Ethernet)
966 cards. If this is for you, say Y and read
967 <file:Documentation/networking/ewrk3.txt> in the kernel source as
968 well as the Ethernet-HOWTO, available from
969 <http://www.tldp.org/docs.html#howto>.
971 To compile this driver as a module, choose M here and read
972 <file:Documentation/networking/net-modules.txt>. The module
973 will be called ewrk3.
976 tristate "EtherExpress 16 support"
979 If you have an EtherExpress16 network (Ethernet) card, say Y and
980 read the Ethernet-HOWTO, available from
981 <http://www.tldp.org/docs.html#howto>. Note that the Intel
982 EtherExpress16 card used to be regarded as a very poor choice
983 because the driver was very unreliable. We now have a new driver
984 that should do better.
986 To compile this driver as a module, choose M here and read
987 <file:Documentation/networking/net-modules.txt>. The module
988 will be called eexpress.
991 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
994 If you have a network (Ethernet) card of this type, say Y. This
995 driver supports intel i82595{FX,TX} based boards. Note however
996 that the EtherExpress PRO/100 Ethernet card has its own separate
997 driver. Please read the Ethernet-HOWTO, available from
998 <http://www.tldp.org/docs.html#howto>.
1000 To compile this driver as a module, choose M here and read
1001 <file:Documentation/networking/net-modules.txt>. The module
1002 will be called eepro.
1005 tristate "FMV-181/182/183/184 support (OBSOLETE)"
1006 depends on NET_ISA && OBSOLETE
1008 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
1009 say Y and read the Ethernet-HOWTO, available from
1010 <http://www.tldp.org/docs.html#howto>.
1012 If you use an FMV-183 or FMV-184 and it is not working, you may need
1013 to disable Plug & Play mode of the card.
1015 To compile this driver as a module, choose M here and read
1016 <file:Documentation/networking/net-modules.txt>. The module
1017 will be called fmv18x.
1020 tristate "HP PCLAN+ (27247B and 27252A) support"
1024 If you have a network (Ethernet) card of this type, say Y and read
1025 the Ethernet-HOWTO, available from
1026 <http://www.tldp.org/docs.html#howto>.
1028 To compile this driver as a module, choose M here and read
1029 <file:Documentation/networking/net-modules.txt>. The module
1030 will be called hp-plus.
1033 tristate "HP PCLAN (27245 and other 27xxx series) support"
1037 If you have a network (Ethernet) card of this type, say Y and read
1038 the Ethernet-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here and read
1042 <file:Documentation/networking/net-modules.txt>. The module
1046 tristate "LP486E on board Ethernet"
1049 Say Y here to support the 82596-based on-board Ethernet controller
1050 for the Panther motherboard, which is one of the two shipped in the
1051 Intel Professional Workstation.
1054 tristate "ICL EtherTeam 16i/32 support"
1057 If you have a network (Ethernet) card of this type, say Y and read
1058 the Ethernet-HOWTO, available from
1059 <http://www.tldp.org/docs.html#howto>.
1061 To compile this driver as a module, choose M here and read
1062 <file:Documentation/networking/net-modules.txt>. The module
1063 will be called eth16i.
1066 tristate "NE2000/NE1000 support"
1067 depends on NET_ISA || (Q40 && m) || M32R
1070 If you have a network (Ethernet) card of this type, say Y and read
1071 the Ethernet-HOWTO, available from
1072 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1073 without a specific driver are compatible with NE2000.
1075 If you have a PCI NE2000 card however, say N here and Y to "PCI
1076 NE2000 support", above. If you have a NE2000 card and are running on
1077 an MCA system (a bus system used on some IBM PS/2 computers and
1078 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1081 To compile this driver as a module, choose M here and read
1082 <file:Documentation/networking/net-modules.txt>. The module
1086 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1087 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1089 The Zenith Z-Note notebook computer has a built-in network
1090 (Ethernet) card, and this is the Linux driver for it. Note that the
1091 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1092 by this driver. Read the Ethernet-HOWTO, available from
1093 <http://www.tldp.org/docs.html#howto>.
1096 tristate "SEEQ8005 support (EXPERIMENTAL)"
1097 depends on NET_ISA && EXPERIMENTAL
1099 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1100 is for you, read the Ethernet-HOWTO, available from
1101 <http://www.tldp.org/docs.html#howto>.
1103 To compile this driver as a module, choose M here and read
1104 <file:Documentation/networking/net-modules.txt>. The module
1105 will be called seeq8005.
1108 tristate "SK_G16 support (OBSOLETE)"
1109 depends on NET_ISA && OBSOLETE
1111 If you have a network (Ethernet) card of this type, say Y and read
1112 the Ethernet-HOWTO, available from
1113 <http://www.tldp.org/docs.html#howto>.
1116 tristate "SKnet MCA support"
1117 depends on NET_ETHERNET && MCA && BROKEN
1119 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1120 support" in order to use this driver. Supported cards are the SKnet
1121 Junior MC2 and the SKnet MC2(+). The driver automatically
1122 distinguishes between the two cards. Note that using multiple boards
1123 of different type hasn't been tested with this driver. Say Y if you
1124 have one of these Ethernet adapters.
1126 To compile this driver as a module, choose M here and read
1127 <file:Documentation/networking/net-modules.txt>. The module
1128 will be called sk_mca.
1131 tristate "NE/2 (ne2000 MCA version) support"
1132 depends on NET_ETHERNET && MCA_LEGACY
1135 If you have a network (Ethernet) card of this type, say Y and read
1136 the Ethernet-HOWTO, available from
1137 <http://www.tldp.org/docs.html#howto>.
1139 To compile this driver as a module, choose M here and read
1140 <file:Documentation/networking/net-modules.txt>. The module
1144 tristate "IBM LAN Adapter/A support"
1145 depends on NET_ETHERNET && MCA && MCA_LEGACY
1147 This is a Micro Channel Ethernet adapter. You need to set
1148 CONFIG_MCA to use this driver. It is both available as an in-kernel
1149 driver and as a module.
1151 To compile this driver as a module, choose M here and read
1152 <file:Documentation/networking/net-modules.txt>. The only
1153 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1154 will both support 16K and 32K memory windows, however a 32K window
1155 gives a better security against packet losses. Usage of multiple
1156 boards with this driver should be possible, but has not been tested
1157 up to now due to lack of hardware.
1160 tristate "IBM LAN Virtual Ethernet support"
1161 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1163 This driver supports virtual ethernet adapters on newer IBM iSeries
1164 and pSeries systems.
1166 To compile this driver as a module, choose M here and read
1167 <file:Documentation/networking/net-modules.txt>. The module will
1171 tristate "IBM PPC4xx EMAC driver support"
1175 This driver supports the IBM PPC4xx EMAC family of on-chip
1176 Ethernet controllers.
1178 config IBM_EMAC_ERRMSG
1179 bool "Verbose error messages"
1183 int "Number of receive buffers"
1185 default "128" if IBM_EMAC4
1189 int "Number of transmit buffers"
1191 default "128" if IBM_EMAC4
1194 config IBM_EMAC_FGAP
1199 config IBM_EMAC_SKBRES
1200 int "Skb reserve amount"
1205 bool "EISA, VLB, PCI and on board controllers"
1206 depends on NET_ETHERNET && (ISA || EISA || PCI)
1208 This is another class of network cards which attach directly to the
1209 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1210 available from <http://www.tldp.org/docs.html#howto>.
1212 Note that the answer to this question doesn't directly affect the
1213 kernel: saying N will just cause the configurator to skip all
1214 the questions about this class of network cards. If you say Y, you
1215 will be asked for your specific card in the following questions. If
1216 you are unsure, say Y.
1219 tristate "AMD PCnet32 PCI support"
1220 depends on NET_PCI && PCI
1224 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1225 answer Y here and read the Ethernet-HOWTO, available from
1226 <http://www.tldp.org/docs.html#howto>.
1228 To compile this driver as a module, choose M here and read
1229 <file:Documentation/networking/net-modules.txt>. The module
1230 will be called pcnet32.
1233 tristate "AMD 8111 (new PCI lance) support"
1234 depends on NET_PCI && PCI
1238 If you have an AMD 8111-based PCI lance ethernet card,
1239 answer Y here and read the Ethernet-HOWTO, available from
1240 <http://www.tldp.org/docs.html#howto>.
1242 To compile this driver as a module, choose M here and read
1243 <file:Documentation/networking/net-modules.txt>. The module
1244 will be called amd8111e.
1245 config AMD8111E_NAPI
1246 bool "Enable NAPI support"
1247 depends on AMD8111_ETH
1249 NAPI is a new driver API designed to reduce CPU and interrupt load
1250 when the driver is receiving lots of packets from the card. It is
1251 still somewhat experimental and thus not yet enabled by default.
1253 If your estimated Rx load is 10kpps or more, or if the card will be
1254 deployed on potentially unfriendly networks (e.g. in a firewall),
1257 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1262 config ADAPTEC_STARFIRE
1263 tristate "Adaptec Starfire/DuraLAN support"
1264 depends on NET_PCI && PCI
1268 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1269 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1270 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1273 To compile this driver as a module, choose M here: the module
1274 will be called starfire. This is recommended.
1276 config ADAPTEC_STARFIRE_NAPI
1277 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1278 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1280 NAPI is a new driver API designed to reduce CPU and interrupt load
1281 when the driver is receiving lots of packets from the card. It is
1282 still somewhat experimental and thus not yet enabled by default.
1284 If your estimated Rx load is 10kpps or more, or if the card will be
1285 deployed on potentially unfriendly networks (e.g. in a firewall),
1288 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1294 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1295 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1298 If you have a network (Ethernet) card of this type, say Y and read
1299 the Ethernet-HOWTO, available from
1300 <http://www.tldp.org/docs.html#howto>.
1302 To compile this driver as a module, choose M here and read
1303 <file:Documentation/networking/net-modules.txt>. The module
1304 will be called ac3200.
1307 tristate "Apricot Xen-II on board Ethernet"
1308 depends on NET_PCI && ISA
1310 If you have a network (Ethernet) controller of this type, say Y and
1311 read the Ethernet-HOWTO, available from
1312 <http://www.tldp.org/docs.html#howto>.
1314 To compile this driver as a module, choose M here and read
1315 <file:Documentation/networking/net-modules.txt>. The module will be
1319 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1320 depends on NET_PCI && PCI && EXPERIMENTAL
1323 If you have a network (Ethernet) controller of this type, say Y and
1324 read the Ethernet-HOWTO, available from
1325 <http://www.tldp.org/docs.html#howto>.
1327 To compile this driver as a module, choose M here and read
1328 <file:Documentation/networking/net-modules.txt>. The module will be
1332 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1333 depends on NET_PCI && PCI && EXPERIMENTAL
1335 If you have a network (Ethernet) controller of this type, say Y and
1336 read the Ethernet-HOWTO, available from
1337 <http://www.tldp.org/docs.html#howto>.
1339 To compile this driver as a module, choose M here and read
1340 <file:Documentation/networking/net-modules.txt>. The module will be
1345 tristate "CS89x0 support"
1346 depends on NET_PCI && (ISA || ARCH_IXDP2X01)
1348 Support for CS89x0 chipset based Ethernet cards. If you have a
1349 network (Ethernet) card of this type, say Y and read the
1350 Ethernet-HOWTO, available from
1351 <http://www.tldp.org/docs.html#howto> as well as
1352 <file:Documentation/networking/cs89x0.txt>.
1354 To compile this driver as a module, choose M here and read
1355 <file:Documentation/networking/net-modules.txt>. The module will be
1359 tristate "TOSHIBA TC35815 Ethernet support"
1360 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1363 tristate "Digi Intl. RightSwitch SE-X support"
1364 depends on NET_PCI && (PCI || EISA)
1366 This is support for the Digi International RightSwitch series of
1367 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1368 models. If you have a network card of this type, say Y and read the
1369 Ethernet-HOWTO, available from
1370 <http://www.tldp.org/docs.html#howto>. More specific
1371 information is contained in <file:Documentation/networking/dgrs.txt>.
1373 To compile this driver as a module, choose M here and read
1374 <file:Documentation/networking/net-modules.txt>. The module
1375 will be called dgrs.
1378 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1379 depends on NET_PCI && PCI
1382 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1383 card, say Y and read the Ethernet-HOWTO, available from
1384 <http://www.tldp.org/docs.html#howto>.
1386 To compile this driver as a module, choose M here and read
1387 <file:Documentation/networking/net-modules.txt>. The module
1388 will be called eepro100.
1392 tristate "Intel(R) PRO/100+ support"
1393 depends on NET_PCI && PCI
1396 This driver supports Intel(R) PRO/100 family of adapters.
1397 To verify that your adapter is supported, find the board ID number
1398 on the adapter. Look for a label that has a barcode and a number
1399 in the format 123456-001 (six digits hyphen three digits).
1401 Use the above information and the Adapter & Driver ID Guide at:
1403 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1405 to identify the adapter.
1407 For the latest Intel PRO/100 network driver for Linux, see:
1409 <http://appsr.intel.com/scripts-df/support_intel.asp>
1411 More specific information on configuring the driver is in
1412 <file:Documentation/networking/e100.txt>.
1414 To compile this driver as a module, choose M here and read
1415 <file:Documentation/networking/net-modules.txt>. The module
1416 will be called e100.
1419 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1420 depends on NET_PCI && EISA && EXPERIMENTAL
1423 If you have a network (Ethernet) card of this type, say Y and read
1424 the Ethernet-HOWTO, available from
1425 <http://www.tldp.org/docs.html#howto>.
1427 To compile this driver as a module, choose M here and read
1428 <file:Documentation/networking/net-modules.txt>. The module
1429 will be called lne390.
1432 tristate "Myson MTD-8xx PCI Ethernet support"
1433 depends on NET_PCI && PCI
1437 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1438 cards. Specifications and data at
1439 <http://www.myson.com.hk/mtd/datasheet/>.
1442 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1443 depends on NET_PCI && PCI
1446 This driver is for the National Semiconductor DP83810 series,
1447 which is used in cards from PureData, NetGear, Linksys
1448 and others, including the 83815 chip.
1449 More specific information and updates are available from
1450 <http://www.scyld.com/network/natsemi.html>.
1453 tristate "PCI NE2000 and clones support (see help)"
1454 depends on NET_PCI && PCI
1457 This driver is for NE2000 compatible PCI cards. It will not work
1458 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1459 support" below). If you have a PCI NE2000 network (Ethernet) card,
1460 say Y and read the Ethernet-HOWTO, available from
1461 <http://www.tldp.org/docs.html#howto>.
1463 This driver also works for the following NE2000 clone cards:
1464 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1465 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1466 Holtek HT80232 Holtek HT80229
1468 To compile this driver as a module, choose M here and read
1469 <file:Documentation/networking/net-modules.txt>. The module
1470 will be called ne2k-pci.
1473 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1474 depends on NET_PCI && EISA && EXPERIMENTAL
1477 If you have a network (Ethernet) card of this type, say Y and read
1478 the Ethernet-HOWTO, available from
1479 <http://www.tldp.org/docs.html#howto>. Note that this driver
1480 will NOT WORK for NE3200 cards as they are completely different.
1482 To compile this driver as a module, choose M here and read
1483 <file:Documentation/networking/net-modules.txt>. The module
1484 will be called ne3210.
1487 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1488 depends on NET_PCI && EISA && EXPERIMENTAL
1491 If you have a network (Ethernet) card of this type, say Y and read
1492 the Ethernet-HOWTO, available from
1493 <http://www.tldp.org/docs.html#howto>.
1495 To compile this driver as a module, choose M here and read
1496 <file:Documentation/networking/net-modules.txt>. The module
1497 will be called es3210.
1500 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1501 depends on NET_PCI && PCI && EXPERIMENTAL
1505 This is a driver for the Fast Ethernet PCI network cards based on
1506 the RTL8139C+ chips. If you have one of those, say Y and read
1507 the Ethernet-HOWTO, available from
1508 <http://www.tldp.org/docs.html#howto>.
1510 To compile this driver as a module, choose M here: the module
1511 will be called 8139cp. This is recommended.
1514 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1515 depends on NET_PCI && PCI
1519 This is a driver for the Fast Ethernet PCI network cards based on
1520 the RTL8139 chips. If you have one of those, say Y and read
1521 the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1523 To compile this driver as a module, choose M here: the module
1524 will be called 8139too. This is recommended.
1527 bool "Use PIO instead of MMIO"
1531 This instructs the driver to use programmed I/O ports (PIO) instead
1532 of PCI shared memory (MMIO). This can possibly solve some problems
1533 in case your mainboard has memory consistency issues. If unsure,
1536 config 8139TOO_TUNE_TWISTER
1537 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1540 This implements a function which might come in handy in case you
1541 are using low quality on long cabling. It is required for RealTek
1542 RTL-8139 revision K boards, and totally unused otherwise. It tries
1543 to match the transceiver to the cable characteristics. This is
1544 experimental since hardly documented by the manufacturer.
1548 bool "Support for older RTL-8129/8130 boards"
1551 This enables support for the older and uncommon RTL-8129 and
1552 RTL-8130 chips, which support MII via an external transceiver,
1553 instead of an internal one. Disabling this option will save some
1554 memory by making the code size smaller. If unsure, say Y.
1556 config 8139_OLD_RX_RESET
1557 bool "Use older RX-reset method"
1560 The 8139too driver was recently updated to contain a more rapid
1561 reset sequence, in the face of severe receive errors. This "new"
1562 RX-reset method should be adequate for all boards. But if you
1563 experience problems, you can enable this option to restore the
1564 old RX-reset behavior. If unsure, say N.
1567 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1568 depends on NET_PCI && PCI
1572 This is a driver for the Fast Ethernet PCI network cards based on
1573 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1574 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1575 read the Ethernet-HOWTO, available at
1576 <http://www.tldp.org/docs.html#howto>. Please read
1577 <file:Documentation/networking/sis900.txt> and comments at the
1578 beginning of <file:drivers/net/sis900.c> for more information.
1580 This driver also supports AMD 79C901 HomePNA so that you can use
1581 your phone line as a network cable.
1583 To compile this driver as a module, choose M here: the module
1584 will be called sis900. This is recommended.
1587 tristate "SMC EtherPower II"
1588 depends on NET_PCI && PCI
1592 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1593 which is based on the SMC83c17x (EPIC/100).
1594 More specific information and updates are available from
1595 <http://www.scyld.com/network/epic100.html>.
1598 tristate "Sundance Alta support"
1599 depends on NET_PCI && PCI
1603 This driver is for the Sundance "Alta" chip.
1604 More specific information and updates are available from
1605 <http://www.scyld.com/network/sundance.html>.
1607 config SUNDANCE_MMIO
1608 bool "Use MMIO instead of PIO"
1611 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1612 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1613 is known to solve bugs on certain chips.
1618 tristate "TI ThunderLAN support"
1619 depends on NET_PCI && (PCI || EISA) && !64BIT
1621 If you have a PCI Ethernet network card based on the ThunderLAN chip
1622 which is supported by this driver, say Y and read the
1623 Ethernet-HOWTO, available from
1624 <http://www.tldp.org/docs.html#howto>.
1626 Devices currently supported by this driver are Compaq Netelligent,
1627 Compaq NetFlex and Olicom cards. Please read the file
1628 <file:Documentation/networking/tlan.txt> for more details.
1630 To compile this driver as a module, choose M here and read
1631 <file:Documentation/networking/net-modules.txt>. The module
1632 will be called tlan.
1634 Please email feedback to <torben.mathiasen@compaq.com>.
1637 tristate "VIA Rhine support"
1638 depends on NET_PCI && PCI
1642 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1643 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1644 Ethernet functions can also be found integrated on South Bridges
1647 To compile this driver as a module, choose M here. The module
1648 will be called via-rhine.
1650 config VIA_RHINE_MMIO
1651 bool "Use MMIO instead of PIO"
1652 depends on VIA_RHINE
1654 This instructs the driver to use PCI shared memory (MMIO) instead of
1655 programmed I/O ports (PIO). Enabling this gives an improvement in
1656 processing time in parts of the driver.
1661 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1662 depends on NET_PCI && EXPERIMENTAL && MIPS
1664 The SAA9730 is a combined multimedia and peripheral controller used
1665 in thin clients, Internet access terminals, and diskless
1667 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1670 bool "Pocket and portable adapters"
1671 depends on NET_ETHERNET && ISA
1673 Cute little network (Ethernet) devices which attach to the parallel
1674 port ("pocket adapters"), commonly used with laptops. If you have
1675 one of those, say Y and read the Ethernet-HOWTO, available from
1676 <http://www.tldp.org/docs.html#howto>.
1678 If you want to plug a network (or some other) card into the PCMCIA
1679 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1680 credit card size extension cards used by all modern laptops), you
1681 need the pcmcia-cs package (location contained in the file
1682 <file:Documentation/Changes>) and you can say N here.
1684 Laptop users should read the Linux Laptop home page at
1685 <http://www.linux-on-laptops.com/> or
1686 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1688 Note that the answer to this question doesn't directly affect the
1689 kernel: saying N will just cause the configurator to skip all
1690 the questions about this class of network devices. If you say Y, you
1691 will be asked for your specific device in the following questions.
1694 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1695 depends on NET_POCKET && ISA && X86
1698 This is a network (Ethernet) device which attaches to your parallel
1699 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1700 available from <http://www.tldp.org/docs.html#howto>, if you
1701 want to use this. If you intend to use this driver, you should have
1702 said N to the "Parallel printer support", because the two drivers
1703 don't like each other.
1705 To compile this driver as a module, choose M here: the module
1709 tristate "D-Link DE600 pocket adapter support"
1710 depends on NET_POCKET && ISA
1712 This is a network (Ethernet) device which attaches to your parallel
1713 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1714 Ethernet-HOWTO, available from
1715 <http://www.tldp.org/docs.html#howto>, if you want to use
1716 this. It is possible to have several devices share a single parallel
1717 port and it is safe to compile the corresponding drivers into the
1720 To compile this driver as a module, choose M here: the module
1721 will be called de600.
1724 tristate "D-Link DE620 pocket adapter support"
1725 depends on NET_POCKET && ISA
1727 This is a network (Ethernet) device which attaches to your parallel
1728 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1729 Ethernet-HOWTO, available from
1730 <http://www.tldp.org/docs.html#howto>, if you want to use
1731 this. It is possible to have several devices share a single parallel
1732 port and it is safe to compile the corresponding drivers into the
1735 To compile this driver as a module, choose M here: the module
1736 will be called de620.
1739 tristate "SGI Seeq ethernet controller support"
1740 depends on NET_ETHERNET && SGI_IP22
1742 Say Y here if you have an Seeq based Ethernet network card. This is
1743 used in many Silicon Graphics machines.
1746 tristate "DEC LANCE ethernet controller support"
1747 depends on NET_ETHERNET && MACH_DECSTATION
1750 This driver is for the series of Ethernet controllers produced by
1751 DEC (now Compaq) based on the AMD Lance chipset, including the
1752 DEPCA series. (This chipset is better known via the NE2100 cards.)
1755 bool "Motorola 68360 ethernet controller"
1758 Say Y here if you want to use the built-in ethernet controller of
1759 the Motorola 68360 processor.
1762 bool "FEC ethernet controller (of ColdFire 5272)"
1763 depends on M5272 || M5282
1765 Say Y here if you want to use the built-in 10/100 Fast ethernet
1766 controller on the Motorola ColdFire 5272 processor.
1769 tristate "NE2000 compatible support for H8/300"
1770 depends on H8300 && NET_ETHERNET
1772 Say Y here if you want to use the NE2000 compatible
1773 controller on the Renesas H8/300 processor.
1775 source "drivers/net/fec_8xx/Kconfig"
1783 menu "Ethernet (1000 Mbit)"
1784 depends on NETDEVICES && !UML
1787 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1790 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1791 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1792 adapter. The driver allows for using the Jumbo Frame option (9000
1793 bytes/frame) however it requires that your switches can handle this
1794 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1797 To compile this driver as a module, choose M here: the
1798 module will be called acenic.
1800 config ACENIC_OMIT_TIGON_I
1801 bool "Omit support for old Tigon I based AceNICs"
1804 Say Y here if you only have Tigon II based AceNICs and want to leave
1805 out support for the older Tigon I based cards which are no longer
1806 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1807 version)). This will reduce the size of the driver object by
1808 app. 100KB. If you are not sure whether your card is a Tigon I or a
1809 Tigon II, say N here.
1811 The safe and default value for this is N.
1814 tristate "D-Link DL2000-based Gigabit Ethernet support"
1818 This driver supports D-Link 2000-based gigabit ethernet cards, which
1820 D-Link DGE-550T Gigabit Ethernet Adapter.
1821 D-Link DL2000-based Gigabit Ethernet Adapter.
1823 To compile this driver as a module, choose M here: the
1824 module will be called dl2k.
1827 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1830 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1831 adapters. For more information on how to identify your adapter, go
1832 to the Adapter & Driver ID Guide at:
1834 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1836 For general information and support, go to the Intel support
1839 <http://support.intel.com>
1841 More specific information on configuring the driver is in
1842 <file:Documentation/networking/e1000.txt>.
1844 To compile this driver as a module, choose M here and read
1845 <file:Documentation/networking/net-modules.txt>. The module
1846 will be called e1000.
1849 bool "Use Rx Polling (NAPI)"
1852 NAPI is a new driver API designed to reduce CPU and interrupt load
1853 when the driver is receiving lots of packets from the card. It is
1854 still somewhat experimental and thus not yet enabled by default.
1856 If your estimated Rx load is 10kpps or more, or if the card will be
1857 deployed on potentially unfriendly networks (e.g. in a firewall),
1860 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1866 tristate "MyriCOM Gigabit Ethernet support"
1869 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1871 To compile this driver as a module, choose M here: the module
1872 will be called myri_sbus. This is recommended.
1875 tristate "National Semiconduct DP83820 support"
1878 This is a driver for the National Semiconductor DP83820 series
1879 of gigabit ethernet MACs. Cards using this chipset include
1880 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1881 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1885 tristate "Packet Engines Hamachi GNIC-II support"
1889 If you have a Gigabit Ethernet card of this type, say Y and read
1890 the Ethernet-HOWTO, available from
1891 <http://www.tldp.org/docs.html#howto>.
1893 To compile this driver as a module, choose M here and read
1894 <file:Documentation/networking/net-modules.txt>. The module will be
1898 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1899 depends on PCI && EXPERIMENTAL
1902 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1903 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1904 used by the Beowulf Linux cluster project. See
1905 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1906 information about this driver in particular and Beowulf in general.
1908 To compile this driver as a module, choose M here: the module
1909 will be called yellowfin. This is recommended.
1912 tristate "Realtek 8169 gigabit ethernet support"
1916 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1918 To compile this driver as a module, choose M here: the module
1919 will be called r8169. This is recommended.
1922 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1923 depends on R8169 && EXPERIMENTAL
1925 NAPI is a new driver API designed to reduce CPU and interrupt load
1926 when the driver is receiving lots of packets from the card. It is
1927 still somewhat experimental and thus not yet enabled by default.
1929 If your estimated Rx load is 10kpps or more, or if the card will be
1930 deployed on potentially unfriendly networks (e.g. in a firewall),
1933 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1940 depends on R8169 && VLAN_8021Q
1942 Say Y here for the r8169 driver to support the functions required
1943 by the kernel 802.1Q code.
1948 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
1951 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1952 compliant Gigabit Ethernet Adapter. The following adapters are supported
1954 - 3Com 3C940 Gigabit LOM Ethernet Adapter
1955 - 3Com 3C941 Gigabit LOM Ethernet Adapter
1956 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
1957 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
1958 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
1959 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
1960 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
1961 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
1962 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
1963 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
1964 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
1965 - DGE-530T Gigabit Ethernet Adapter
1966 - EG1032 v2 Instant Gigabit Network Adapter
1967 - EG1064 v2 Instant Gigabit Network Adapter
1968 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
1969 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
1970 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
1971 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
1972 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
1973 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
1974 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
1975 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
1976 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
1977 - Marvell RDK-8001 Adapter
1978 - Marvell RDK-8002 Adapter
1979 - Marvell RDK-8003 Adapter
1980 - Marvell RDK-8004 Adapter
1981 - Marvell RDK-8006 Adapter
1982 - Marvell RDK-8007 Adapter
1983 - Marvell RDK-8008 Adapter
1984 - Marvell RDK-8009 Adapter
1985 - Marvell RDK-8010 Adapter
1986 - Marvell RDK-8011 Adapter
1987 - Marvell RDK-8012 Adapter
1988 - Marvell RDK-8052 Adapter
1989 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
1990 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
1991 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
1992 - SK-9521 10/100/1000Base-T Adapter
1993 - SK-9521 V2.0 10/100/1000Base-T Adapter
1994 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
1995 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
1996 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
1997 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
1998 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
1999 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2000 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2001 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2002 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2003 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2004 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2005 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2006 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2007 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2008 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2009 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2010 - SMC EZ Card 1000 (SMC9452TXV.2)
2012 The adapters support Jumbo Frames.
2013 The dual link adapters support link-failover and dual port features.
2014 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2015 the scatter-gather functionality with sendfile(). Please refer to
2016 <file:Documentation/networking/sk98lin.txt> for more information about
2017 optional driver parameters.
2018 Questions concerning this driver may be addressed to:
2019 <linux@syskonnect.de>
2021 If you want to compile this driver as a module ( = code which can be
2022 inserted in and removed from the running kernel whenever you want),
2023 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2024 be called sk98lin. This is recommended.
2027 tristate "VIA Velocity support"
2028 depends on NET_PCI && PCI
2033 If you have a VIA "Velocity" based network card say Y here.
2035 To compile this driver as a module, choose M here. The module
2036 will be called via-velocity.
2039 tristate "Broadcom Tigon3 support"
2042 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2044 To compile this driver as a module, choose M here: the module
2045 will be called tg3. This is recommended.
2048 tristate "Broadcom NetXtremeII support"
2051 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2053 To compile this driver as a module, choose M here: the module
2054 will be called bnx2. This is recommended.
2057 tristate "Gianfar Ethernet"
2058 depends on 85xx || 83xx
2060 This driver supports the Gigabit TSEC on the MPC85xx
2061 family of chips, and the FEC on the 8540
2068 tristate "MV-643XX Ethernet support"
2069 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
2071 This driver supports the gigabit Ethernet on the Marvell MV643XX
2072 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2073 Pegasos II, amongst other PPC and MIPS boards.
2075 config MV643XX_ETH_0
2076 bool "MV-643XX Port 0"
2077 depends on MV643XX_ETH
2079 This enables support for Port 0 of the Marvell MV643XX Gigabit
2082 config MV643XX_ETH_1
2083 bool "MV-643XX Port 1"
2084 depends on MV643XX_ETH
2086 This enables support for Port 1 of the Marvell MV643XX Gigabit
2089 config MV643XX_ETH_2
2090 bool "MV-643XX Port 2"
2091 depends on MV643XX_ETH
2093 This enables support for Port 2 of the Marvell MV643XX Gigabit
2099 # 10 Gigabit Ethernet
2102 menu "Ethernet (10000 Mbit)"
2103 depends on NETDEVICES && !UML
2106 tristate "Intel(R) PRO/10GbE support"
2109 This driver supports Intel(R) PRO/10GbE family of
2110 adapters. For more information on how to identify your adapter, go
2111 to the Adapter & Driver ID Guide at:
2113 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2115 For general information and support, go to the Intel support
2118 <http://support.intel.com>
2120 More specific information on configuring the driver is in
2121 <file:Documentation/networking/ixgb.txt>.
2123 To compile this driver as a module, choose M here and read
2124 <file:Documentation/networking/net-modules.txt>. The module
2125 will be called ixgb.
2128 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2129 depends on IXGB && EXPERIMENTAL
2131 NAPI is a new driver API designed to reduce CPU and interrupt load
2132 when the driver is receiving lots of packets from the card. It is
2133 still somewhat experimental and thus not yet enabled by default.
2135 If your estimated Rx load is 10kpps or more, or if the card will be
2136 deployed on potentially unfriendly networks (e.g. in a firewall),
2139 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2145 tristate "S2IO 10Gbe XFrame NIC"
2148 This driver supports the 10Gbe XFrame NIC of S2IO.
2149 For help regarding driver compilation, installation and
2150 tuning please look into ~/drivers/net/s2io/README.txt.
2153 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2154 depends on S2IO && EXPERIMENTAL
2156 NAPI is a new driver API designed to reduce CPU and interrupt load
2157 when the driver is receiving lots of packets from the card. It is
2158 still somewhat experimental and thus not yet enabled by default.
2160 If your estimated Rx load is 10kpps or more, or if the card will be
2161 deployed on potentially unfriendly networks (e.g. in a firewall),
2164 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2170 bool "Use 2 Buffer Mode on Rx side."
2173 On enabling the 2 buffer mode, the received frame will be
2174 split into 2 parts before being DMA'ed to the hosts memory.
2175 The parts are the ethernet header and ethernet payload.
2176 This is useful on systems where DMA'ing to to unaligned
2177 physical memory loactions comes with a heavy price.
2178 If not sure please say N.
2183 source "drivers/net/tokenring/Kconfig"
2185 source "drivers/net/wireless/Kconfig"
2187 source "drivers/net/pcmcia/Kconfig"
2190 source "drivers/net/wan/Kconfig"
2192 source "drivers/atm/Kconfig"
2194 source "drivers/s390/net/Kconfig"
2197 tristate "iSeries Virtual Ethernet driver support"
2198 depends on NETDEVICES && PPC_ISERIES
2201 bool "FDDI driver support"
2202 depends on NETDEVICES && (PCI || EISA)
2204 Fiber Distributed Data Interface is a high speed local area network
2205 design; essentially a replacement for high speed Ethernet. FDDI can
2206 run over copper or fiber. If you are connected to such a network and
2207 want a driver for the FDDI card in your computer, say Y here (and
2208 then also Y to the driver for your FDDI card, below). Most people
2212 tristate "Digital DEFEA and DEFPA adapter support"
2213 depends on FDDI && (PCI || EISA)
2215 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2216 (DEFPA) controllers which can connect you to a local FDDI network.
2219 tristate "SysKonnect FDDI PCI support"
2220 depends on FDDI && PCI
2222 Say Y here if you have a SysKonnect FDDI PCI adapter.
2223 The following adapters are supported by this driver:
2224 - SK-5521 (SK-NET FDDI-UP)
2225 - SK-5522 (SK-NET FDDI-UP DAS)
2226 - SK-5541 (SK-NET FDDI-FP)
2227 - SK-5543 (SK-NET FDDI-LP)
2228 - SK-5544 (SK-NET FDDI-LP DAS)
2229 - SK-5821 (SK-NET FDDI-UP64)
2230 - SK-5822 (SK-NET FDDI-UP64 DAS)
2231 - SK-5841 (SK-NET FDDI-FP64)
2232 - SK-5843 (SK-NET FDDI-LP64)
2233 - SK-5844 (SK-NET FDDI-LP64 DAS)
2234 - Netelligent 100 FDDI DAS Fibre SC
2235 - Netelligent 100 FDDI SAS Fibre SC
2236 - Netelligent 100 FDDI DAS UTP
2237 - Netelligent 100 FDDI SAS UTP
2238 - Netelligent 100 FDDI SAS Fibre MIC
2240 Read <file:Documentation/networking/skfp.txt> for information about
2243 Questions concerning this driver can be addressed to:
2244 <linux@syskonnect.de>
2246 To compile this driver as a module, choose M here: the module
2247 will be called skfp. This is recommended.
2250 bool "HIPPI driver support (EXPERIMENTAL)"
2251 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2253 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2254 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2255 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2256 single-mode). HIPPI networks are commonly used for clusters and to
2257 connect to super computers. If you are connected to a HIPPI network
2258 and have a HIPPI network card in your computer that you want to use
2259 under Linux, say Y here (you must also remember to enable the driver
2260 for your HIPPI card below). Most people will say N here.
2263 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2264 depends on HIPPI && PCI
2266 Say Y here if this is your PCI HIPPI network card.
2268 To compile this driver as a module, choose M here: the module
2269 will be called rrunner. If unsure, say N.
2271 config ROADRUNNER_LARGE_RINGS
2272 bool "Use large TX/RX rings (EXPERIMENTAL)"
2273 depends on ROADRUNNER
2275 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2276 of additional memory to allow for fastest operation, both for
2277 transmitting and receiving. This memory cannot be used by any other
2278 kernel code or by user space programs. Say Y here only if you have
2282 tristate "PLIP (parallel port) support"
2283 depends on NETDEVICES && PARPORT
2285 PLIP (Parallel Line Internet Protocol) is used to create a
2286 reasonably fast mini network consisting of two (or, rarely, more)
2287 local machines. A PLIP link from a Linux box is a popular means to
2288 install a Linux distribution on a machine which doesn't have a
2289 CD-ROM drive (a minimal system has to be transferred with floppies
2290 first). The kernels on both machines need to have this PLIP option
2291 enabled for this to work.
2293 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2294 ports (the connectors at the computers with 25 holes) are connected
2295 with "null printer" or "Turbo Laplink" cables which can transmit 4
2296 bits at a time (mode 0) or with special PLIP cables, to be used on
2297 bidirectional parallel ports only, which can transmit 8 bits at a
2298 time (mode 1); you can find the wiring of these cables in
2299 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2300 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2301 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2302 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2303 and winsock or NCSA's telnet.
2305 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2306 as the NET-3-HOWTO, both available from
2307 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2308 protocol has been changed and this PLIP driver won't work together
2309 with the PLIP support in Linux versions 1.0.x. This option enlarges
2310 your kernel by about 8 KB.
2312 To compile this driver as a module, choose M here and read
2313 <file:Documentation/networking/net-modules.txt>. The module will be
2314 called plip. If unsure, say Y or M, in case you buy a laptop
2318 tristate "PPP (point-to-point protocol) support"
2319 depends on NETDEVICES
2321 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2322 the same purpose: sending Internet traffic over telephone (and other
2323 serial) lines. Ask your access provider if they support it, because
2324 otherwise you can't use it; most Internet access providers these
2325 days support PPP rather than SLIP.
2327 To use PPP, you need an additional program called pppd as described
2328 in the PPP-HOWTO, available at
2329 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2330 the version of pppd recommended in <file:Documentation/Changes>.
2331 The PPP option enlarges your kernel by about 16 KB.
2333 There are actually two versions of PPP: the traditional PPP for
2334 asynchronous lines, such as regular analog phone lines, and
2335 synchronous PPP which can be used over digital ISDN lines for
2336 example. If you want to use PPP over phone lines or other
2337 asynchronous serial lines, you need to say Y (or M) here and also to
2338 the next option, "PPP support for async serial ports". For PPP over
2339 synchronous lines, you should say Y (or M) here and to "Support
2340 synchronous PPP", below.
2342 If you said Y to "Version information on all symbols" above, then
2343 you cannot compile the PPP driver into the kernel; you can then only
2344 compile it as a module. To compile this driver as a module, choose M
2345 here and read <file:Documentation/networking/net-modules.txt>.
2346 The module will be called ppp_generic.
2348 config PPP_MULTILINK
2349 bool "PPP multilink support (EXPERIMENTAL)"
2350 depends on PPP && EXPERIMENTAL
2352 PPP multilink is a protocol (defined in RFC 1990) which allows you
2353 to combine several (logical or physical) lines into one logical PPP
2354 connection, so that you can utilize your full bandwidth.
2356 This has to be supported at the other end as well and you need a
2357 version of the pppd daemon which understands the multilink protocol.
2362 bool "PPP filtering"
2365 Say Y here if you want to be able to filter the packets passing over
2366 PPP interfaces. This allows you to control which packets count as
2367 activity (i.e. which packets will reset the idle timer or bring up
2368 a demand-dialled link) and which packets are to be dropped entirely.
2369 You need to say Y here if you wish to use the pass-filter and
2370 active-filter options to pppd.
2375 tristate "PPP support for async serial ports"
2379 Say Y (or M) here if you want to be able to use PPP over standard
2380 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2381 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2384 To compile this driver as a module, choose M here.
2389 tristate "PPP support for sync tty ports"
2392 Say Y (or M) here if you want to be able to use PPP over synchronous
2393 (HDLC) tty devices, such as the SyncLink adapter. These devices
2394 are often used for high-speed leased lines like T1/E1.
2396 To compile this driver as a module, choose M here.
2399 tristate "PPP Deflate compression"
2404 Support for the Deflate compression method for PPP, which uses the
2405 Deflate algorithm (the same algorithm that gzip uses) to compress
2406 each PPP packet before it is sent over the wire. The machine at the
2407 other end of the PPP link (usually your ISP) has to support the
2408 Deflate compression method as well for this to be useful. Even if
2409 they don't support it, it is safe to say Y here.
2411 To compile this driver as a module, choose M here.
2414 tristate "PPP BSD-Compress compression"
2417 Support for the BSD-Compress compression method for PPP, which uses
2418 the LZW compression method to compress each PPP packet before it is
2419 sent over the wire. The machine at the other end of the PPP link
2420 (usually your ISP) has to support the BSD-Compress compression
2421 method as well for this to be useful. Even if they don't support it,
2422 it is safe to say Y here.
2424 The PPP Deflate compression method ("PPP Deflate compression",
2425 above) is preferable to BSD-Compress, because it compresses better
2428 Note that the BSD compression code will always be compiled as a
2429 module; it is called bsd_comp and will show up in the directory
2430 modules once you have said "make modules". If unsure, say N.
2433 tristate "PPP over Ethernet (EXPERIMENTAL)"
2434 depends on EXPERIMENTAL && PPP
2436 Support for PPP over Ethernet.
2438 This driver requires the latest version of pppd from the CVS
2439 repository at cvs.samba.org. Alternatively, see the
2440 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2441 which contains instruction on how to use this driver (under
2442 the heading "Kernel mode PPPoE").
2445 tristate "PPP over ATM"
2446 depends on ATM && PPP
2448 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2449 This implementation does not yet comply with section 8 of RFC2364,
2450 which can lead to bad results if the ATM peer loses state and
2451 changes its encapsulation unilaterally.
2454 tristate "SLIP (serial line) support"
2455 depends on NETDEVICES
2457 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2458 connect to your Internet service provider or to connect to some
2459 other local Unix box or if you want to configure your Linux box as a
2460 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2461 Internet Protocol) is a protocol used to send Internet traffic over
2462 serial connections such as telephone lines or null modem cables;
2463 nowadays, the protocol PPP is more commonly used for this same
2466 Normally, your access provider has to support SLIP in order for you
2467 to be able to use it, but there is now a SLIP emulator called SLiRP
2468 around (available from
2469 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2470 allows you to use SLIP over a regular dial up shell connection. If
2471 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2472 NET-3-HOWTO, available from
2473 <http://www.tldp.org/docs.html#howto>, explains how to
2474 configure SLIP. Note that you don't need this option if you just
2475 want to run term (term is a program which gives you almost full
2476 Internet connectivity if you have a regular dial up shell account on
2477 some Internet connected Unix computer. Read
2478 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2479 support will enlarge your kernel by about 4 KB. If unsure, say N.
2481 To compile this driver as a module, choose M here and read
2482 <file:Documentation/networking/net-modules.txt>. The module will be
2485 config SLIP_COMPRESSED
2486 bool "CSLIP compressed headers"
2489 This protocol is faster than SLIP because it uses compression on the
2490 TCP/IP headers (not on the data itself), but it has to be supported
2491 on both ends. Ask your access provider if you are not sure and
2492 answer Y, just in case. You will still be able to use plain SLIP. If
2493 you plan to use SLiRP, the SLIP emulator (available from
2494 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2495 allows you to use SLIP over a regular dial up shell connection, you
2496 definitely want to say Y here. The NET-3-HOWTO, available from
2497 <http://www.tldp.org/docs.html#howto>, explains how to configure
2498 CSLIP. This won't enlarge your kernel.
2501 bool "Keepalive and linefill"
2504 Adds additional capabilities to the SLIP driver to support the
2505 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2508 config SLIP_MODE_SLIP6
2509 bool "Six bit SLIP encapsulation"
2512 Just occasionally you may need to run IP over hostile serial
2513 networks that don't pass all control characters or are only seven
2514 bit. Saying Y here adds an extra mode you can use with SLIP:
2515 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2516 the serial device. Naturally, this has to be supported at the other
2517 end of the link as well. It's good enough, for example, to run IP
2518 over the async ports of a Camtec JNT Pad. If unsure, say N.
2521 bool "Fibre Channel driver support"
2522 depends on NETDEVICES && SCSI && PCI
2524 Fibre Channel is a high speed serial protocol mainly used to connect
2525 large storage devices to the computer; it is compatible with and
2526 intended to replace SCSI.
2528 If you intend to use Fibre Channel, you need to have a Fibre channel
2529 adaptor card in your computer; say Y here and to the driver for your
2530 adaptor below. You also should have said Y to "SCSI support" and
2531 "SCSI generic support".
2534 tristate "Traffic Shaper (EXPERIMENTAL)"
2535 depends on NETDEVICES && EXPERIMENTAL
2537 The traffic shaper is a virtual network device that allows you to
2538 limit the rate of outgoing data flow over some other network device.
2539 The traffic that you want to slow down can then be routed through
2540 these virtual devices. See
2541 <file:Documentation/networking/shaper.txt> for more information.
2543 An alternative to this traffic shaper is the experimental
2544 Class-Based Queueing (CBQ) scheduling support which you get if you
2545 say Y to "QoS and/or fair queueing" above.
2547 To set up and configure shaper devices, you need the shapecfg
2548 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2551 To compile this driver as a module, choose M here: the module
2552 will be called shaper. If unsure, say N.
2555 tristate "Network console logging support (EXPERIMENTAL)"
2556 depends on NETDEVICES && EXPERIMENTAL
2558 If you want to log kernel messages over the network, enable this.
2559 See <file:Documentation/networking/netconsole.txt> for details.