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.
827 config NET_VENDOR_RACAL
828 bool "Racal-Interlan (Micom) NI cards"
829 depends on NET_ETHERNET && ISA
831 If you have a network (Ethernet) card belonging to this class, such
832 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
833 available from <http://www.tldp.org/docs.html#howto>.
835 Note that the answer to this question doesn't directly affect the
836 kernel: saying N will just cause the configurator to skip all
837 the questions about NI cards. If you say Y, you will be asked for
838 your specific card in the following questions.
841 tristate "NI5010 support (EXPERIMENTAL)"
842 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
844 If you have a network (Ethernet) card of this type, say Y and read
845 the Ethernet-HOWTO, available from
846 <http://www.tldp.org/docs.html#howto>. Note that this is still
849 To compile this driver as a module, choose M here and read
850 <file:Documentation/networking/net-modules.txt>. The module
851 will be called ni5010.
854 tristate "NI5210 support"
855 depends on NET_VENDOR_RACAL && ISA
857 If you have a network (Ethernet) card of this type, say Y and read
858 the Ethernet-HOWTO, available from
859 <http://www.tldp.org/docs.html#howto>.
861 To compile this driver as a module, choose M here and read
862 <file:Documentation/networking/net-modules.txt>. The module
866 tristate "NI6510 support"
867 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
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
877 source "drivers/net/tulip/Kconfig"
880 tristate "AT1700/1720 support (EXPERIMENTAL)"
881 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
884 If you have a network (Ethernet) card of this type, say Y and read
885 the Ethernet-HOWTO, available from
886 <http://www.tldp.org/docs.html#howto>.
888 To compile this driver as a module, choose M here and read
889 <file:Documentation/networking/net-modules.txt>. The module
890 will be called at1700.
893 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
894 depends on NET_ETHERNET && (ISA || EISA || MCA)
897 If you have a network (Ethernet) card of this type, say Y and read
898 the Ethernet-HOWTO, available from
899 <http://www.tldp.org/docs.html#howto> as well as
900 <file:drivers/net/depca.c>.
902 To compile this driver as a module, choose M here and read
903 <file:Documentation/networking/net-modules.txt>. The module
904 will be called depca.
907 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
908 depends on NET_ETHERNET && (ISA || EISA || PCI)
910 If you have a network (Ethernet) card of this type, say Y and read
911 the Ethernet-HOWTO, available from
912 <http://www.tldp.org/docs.html#howto>.
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 hp100.
919 bool "Other ISA cards"
920 depends on NET_ETHERNET && ISA
922 If your network (Ethernet) card hasn't been mentioned yet and its
923 bus system (that's the way the cards talks to the other components
924 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
925 Make sure you know the name of your card. Read the Ethernet-HOWTO,
926 available from <http://www.tldp.org/docs.html#howto>.
930 Note that the answer to this question doesn't directly affect the
931 kernel: saying N will just cause the configurator to skip all
932 the remaining ISA network card questions. If you say Y, you will be
933 asked for your specific card in the following questions.
936 tristate "Cabletron E21xx support"
940 If you have a network (Ethernet) card of this type, say Y and read
941 the Ethernet-HOWTO, available from
942 <http://www.tldp.org/docs.html#howto>.
944 To compile this driver as a module, choose M here and read
945 <file:Documentation/networking/net-modules.txt>. The module
946 will be called e2100.
949 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
953 This driver supports the DE203, DE204 and DE205 network (Ethernet)
954 cards. If this is for you, say Y and read
955 <file:Documentation/networking/ewrk3.txt> in the kernel source as
956 well as the Ethernet-HOWTO, available from
957 <http://www.tldp.org/docs.html#howto>.
959 To compile this driver as a module, choose M here and read
960 <file:Documentation/networking/net-modules.txt>. The module
961 will be called ewrk3.
964 tristate "EtherExpress 16 support"
967 If you have an EtherExpress16 network (Ethernet) card, say Y and
968 read the Ethernet-HOWTO, available from
969 <http://www.tldp.org/docs.html#howto>. Note that the Intel
970 EtherExpress16 card used to be regarded as a very poor choice
971 because the driver was very unreliable. We now have a new driver
972 that should do better.
974 To compile this driver as a module, choose M here and read
975 <file:Documentation/networking/net-modules.txt>. The module
976 will be called eexpress.
979 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
982 If you have a network (Ethernet) card of this type, say Y. This
983 driver supports intel i82595{FX,TX} based boards. Note however
984 that the EtherExpress PRO/100 Ethernet card has its own separate
985 driver. Please read the Ethernet-HOWTO, available from
986 <http://www.tldp.org/docs.html#howto>.
988 To compile this driver as a module, choose M here and read
989 <file:Documentation/networking/net-modules.txt>. The module
990 will be called eepro.
993 tristate "HP PCLAN+ (27247B and 27252A) support"
997 If you have a network (Ethernet) card of this type, say Y and read
998 the Ethernet-HOWTO, available from
999 <http://www.tldp.org/docs.html#howto>.
1001 To compile this driver as a module, choose M here and read
1002 <file:Documentation/networking/net-modules.txt>. The module
1003 will be called hp-plus.
1006 tristate "HP PCLAN (27245 and other 27xxx series) support"
1010 If you have a network (Ethernet) card of this type, say Y and read
1011 the Ethernet-HOWTO, available from
1012 <http://www.tldp.org/docs.html#howto>.
1014 To compile this driver as a module, choose M here and read
1015 <file:Documentation/networking/net-modules.txt>. The module
1019 tristate "LP486E on board Ethernet"
1022 Say Y here to support the 82596-based on-board Ethernet controller
1023 for the Panther motherboard, which is one of the two shipped in the
1024 Intel Professional Workstation.
1027 tristate "ICL EtherTeam 16i/32 support"
1030 If you have a network (Ethernet) card of this type, say Y and read
1031 the Ethernet-HOWTO, available from
1032 <http://www.tldp.org/docs.html#howto>.
1034 To compile this driver as a module, choose M here and read
1035 <file:Documentation/networking/net-modules.txt>. The module
1036 will be called eth16i.
1039 tristate "NE2000/NE1000 support"
1040 depends on NET_ISA || (Q40 && m) || M32R
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>. Many Ethernet cards
1046 without a specific driver are compatible with NE2000.
1048 If you have a PCI NE2000 card however, say N here and Y to "PCI
1049 NE2000 support", above. If you have a NE2000 card and are running on
1050 an MCA system (a bus system used on some IBM PS/2 computers and
1051 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1054 To compile this driver as a module, choose M here and read
1055 <file:Documentation/networking/net-modules.txt>. The module
1059 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1060 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1062 The Zenith Z-Note notebook computer has a built-in network
1063 (Ethernet) card, and this is the Linux driver for it. Note that the
1064 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1065 by this driver. Read the Ethernet-HOWTO, available from
1066 <http://www.tldp.org/docs.html#howto>.
1069 tristate "SEEQ8005 support (EXPERIMENTAL)"
1070 depends on NET_ISA && EXPERIMENTAL
1072 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1073 is for you, read the Ethernet-HOWTO, available from
1074 <http://www.tldp.org/docs.html#howto>.
1076 To compile this driver as a module, choose M here and read
1077 <file:Documentation/networking/net-modules.txt>. The module
1078 will be called seeq8005.
1081 tristate "SKnet MCA support"
1082 depends on NET_ETHERNET && MCA && BROKEN
1084 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1085 support" in order to use this driver. Supported cards are the SKnet
1086 Junior MC2 and the SKnet MC2(+). The driver automatically
1087 distinguishes between the two cards. Note that using multiple boards
1088 of different type hasn't been tested with this driver. Say Y if you
1089 have one of these Ethernet adapters.
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 sk_mca.
1096 tristate "NE/2 (ne2000 MCA version) support"
1097 depends on NET_ETHERNET && MCA_LEGACY
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
1109 tristate "IBM LAN Adapter/A support"
1110 depends on NET_ETHERNET && MCA && MCA_LEGACY
1112 This is a Micro Channel Ethernet adapter. You need to set
1113 CONFIG_MCA to use this driver. It is both available as an in-kernel
1114 driver and as a module.
1116 To compile this driver as a module, choose M here and read
1117 <file:Documentation/networking/net-modules.txt>. The only
1118 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1119 will both support 16K and 32K memory windows, however a 32K window
1120 gives a better security against packet losses. Usage of multiple
1121 boards with this driver should be possible, but has not been tested
1122 up to now due to lack of hardware.
1125 tristate "IBM LAN Virtual Ethernet support"
1126 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1128 This driver supports virtual ethernet adapters on newer IBM iSeries
1129 and pSeries systems.
1131 To compile this driver as a module, choose M here and read
1132 <file:Documentation/networking/net-modules.txt>. The module will
1136 tristate "IBM PPC4xx EMAC driver support"
1140 This driver supports the IBM PPC4xx EMAC family of on-chip
1141 Ethernet controllers.
1143 config IBM_EMAC_ERRMSG
1144 bool "Verbose error messages"
1148 int "Number of receive buffers"
1150 default "128" if IBM_EMAC4
1154 int "Number of transmit buffers"
1156 default "128" if IBM_EMAC4
1159 config IBM_EMAC_FGAP
1164 config IBM_EMAC_SKBRES
1165 int "Skb reserve amount"
1170 bool "EISA, VLB, PCI and on board controllers"
1171 depends on NET_ETHERNET && (ISA || EISA || PCI)
1173 This is another class of network cards which attach directly to the
1174 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1175 available from <http://www.tldp.org/docs.html#howto>.
1177 Note that the answer to this question doesn't directly affect the
1178 kernel: saying N will just cause the configurator to skip all
1179 the questions about this class of network cards. If you say Y, you
1180 will be asked for your specific card in the following questions. If
1181 you are unsure, say Y.
1184 tristate "AMD PCnet32 PCI support"
1185 depends on NET_PCI && PCI
1189 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1190 answer Y here and read 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
1195 will be called pcnet32.
1198 tristate "AMD 8111 (new PCI lance) support"
1199 depends on NET_PCI && PCI
1203 If you have an AMD 8111-based PCI lance ethernet card,
1204 answer Y here and read the Ethernet-HOWTO, available from
1205 <http://www.tldp.org/docs.html#howto>.
1207 To compile this driver as a module, choose M here and read
1208 <file:Documentation/networking/net-modules.txt>. The module
1209 will be called amd8111e.
1210 config AMD8111E_NAPI
1211 bool "Enable NAPI support"
1212 depends on AMD8111_ETH
1214 NAPI is a new driver API designed to reduce CPU and interrupt load
1215 when the driver is receiving lots of packets from the card. It is
1216 still somewhat experimental and thus not yet enabled by default.
1218 If your estimated Rx load is 10kpps or more, or if the card will be
1219 deployed on potentially unfriendly networks (e.g. in a firewall),
1222 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1227 config ADAPTEC_STARFIRE
1228 tristate "Adaptec Starfire/DuraLAN support"
1229 depends on NET_PCI && PCI
1233 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1234 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1235 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1238 To compile this driver as a module, choose M here: the module
1239 will be called starfire. This is recommended.
1241 config ADAPTEC_STARFIRE_NAPI
1242 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1243 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1245 NAPI is a new driver API designed to reduce CPU and interrupt load
1246 when the driver is receiving lots of packets from the card. It is
1247 still somewhat experimental and thus not yet enabled by default.
1249 If your estimated Rx load is 10kpps or more, or if the card will be
1250 deployed on potentially unfriendly networks (e.g. in a firewall),
1253 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1259 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1260 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1263 If you have a network (Ethernet) card of this type, say Y and read
1264 the Ethernet-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>.
1267 To compile this driver as a module, choose M here and read
1268 <file:Documentation/networking/net-modules.txt>. The module
1269 will be called ac3200.
1272 tristate "Apricot Xen-II on board Ethernet"
1273 depends on NET_PCI && ISA
1275 If you have a network (Ethernet) controller of this type, say Y and
1276 read the Ethernet-HOWTO, available from
1277 <http://www.tldp.org/docs.html#howto>.
1279 To compile this driver as a module, choose M here and read
1280 <file:Documentation/networking/net-modules.txt>. The module will be
1284 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1285 depends on NET_PCI && PCI && EXPERIMENTAL
1288 If you have a network (Ethernet) controller of this type, say Y and
1289 read the Ethernet-HOWTO, available from
1290 <http://www.tldp.org/docs.html#howto>.
1292 To compile this driver as a module, choose M here and read
1293 <file:Documentation/networking/net-modules.txt>. The module will be
1297 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1298 depends on NET_PCI && PCI && EXPERIMENTAL
1300 If you have a network (Ethernet) controller of this type, say Y and
1301 read the Ethernet-HOWTO, available from
1302 <http://www.tldp.org/docs.html#howto>.
1304 To compile this driver as a module, choose M here and read
1305 <file:Documentation/networking/net-modules.txt>. The module will be
1310 tristate "CS89x0 support"
1311 depends on NET_PCI && (ISA || ARCH_IXDP2X01)
1313 Support for CS89x0 chipset based Ethernet cards. If you have a
1314 network (Ethernet) card of this type, say Y and read the
1315 Ethernet-HOWTO, available from
1316 <http://www.tldp.org/docs.html#howto> as well as
1317 <file:Documentation/networking/cs89x0.txt>.
1319 To compile this driver as a module, choose M here and read
1320 <file:Documentation/networking/net-modules.txt>. The module will be
1324 tristate "TOSHIBA TC35815 Ethernet support"
1325 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1328 tristate "Digi Intl. RightSwitch SE-X support"
1329 depends on NET_PCI && (PCI || EISA)
1331 This is support for the Digi International RightSwitch series of
1332 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1333 models. If you have a network card of this type, say Y and read the
1334 Ethernet-HOWTO, available from
1335 <http://www.tldp.org/docs.html#howto>. More specific
1336 information is contained in <file:Documentation/networking/dgrs.txt>.
1338 To compile this driver as a module, choose M here and read
1339 <file:Documentation/networking/net-modules.txt>. The module
1340 will be called dgrs.
1343 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1344 depends on NET_PCI && PCI
1347 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1348 card, say Y and read the Ethernet-HOWTO, available from
1349 <http://www.tldp.org/docs.html#howto>.
1351 To compile this driver as a module, choose M here and read
1352 <file:Documentation/networking/net-modules.txt>. The module
1353 will be called eepro100.
1357 tristate "Intel(R) PRO/100+ support"
1358 depends on NET_PCI && PCI
1361 This driver supports Intel(R) PRO/100 family of adapters.
1362 To verify that your adapter is supported, find the board ID number
1363 on the adapter. Look for a label that has a barcode and a number
1364 in the format 123456-001 (six digits hyphen three digits).
1366 Use the above information and the Adapter & Driver ID Guide at:
1368 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1370 to identify the adapter.
1372 For the latest Intel PRO/100 network driver for Linux, see:
1374 <http://appsr.intel.com/scripts-df/support_intel.asp>
1376 More specific information on configuring the driver is in
1377 <file:Documentation/networking/e100.txt>.
1379 To compile this driver as a module, choose M here and read
1380 <file:Documentation/networking/net-modules.txt>. The module
1381 will be called e100.
1384 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1385 depends on NET_PCI && EISA && EXPERIMENTAL
1388 If you have a network (Ethernet) card of this type, say Y and read
1389 the Ethernet-HOWTO, available from
1390 <http://www.tldp.org/docs.html#howto>.
1392 To compile this driver as a module, choose M here and read
1393 <file:Documentation/networking/net-modules.txt>. The module
1394 will be called lne390.
1397 tristate "Myson MTD-8xx PCI Ethernet support"
1398 depends on NET_PCI && PCI
1402 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1403 cards. Specifications and data at
1404 <http://www.myson.com.hk/mtd/datasheet/>.
1407 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1408 depends on NET_PCI && PCI
1411 This driver is for the National Semiconductor DP83810 series,
1412 which is used in cards from PureData, NetGear, Linksys
1413 and others, including the 83815 chip.
1414 More specific information and updates are available from
1415 <http://www.scyld.com/network/natsemi.html>.
1418 tristate "PCI NE2000 and clones support (see help)"
1419 depends on NET_PCI && PCI
1422 This driver is for NE2000 compatible PCI cards. It will not work
1423 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1424 support" below). If you have a PCI NE2000 network (Ethernet) card,
1425 say Y and read the Ethernet-HOWTO, available from
1426 <http://www.tldp.org/docs.html#howto>.
1428 This driver also works for the following NE2000 clone cards:
1429 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1430 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1431 Holtek HT80232 Holtek HT80229
1433 To compile this driver as a module, choose M here and read
1434 <file:Documentation/networking/net-modules.txt>. The module
1435 will be called ne2k-pci.
1438 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1439 depends on NET_PCI && EISA && EXPERIMENTAL
1442 If you have a network (Ethernet) card of this type, say Y and read
1443 the Ethernet-HOWTO, available from
1444 <http://www.tldp.org/docs.html#howto>. Note that this driver
1445 will NOT WORK for NE3200 cards as they are completely different.
1447 To compile this driver as a module, choose M here and read
1448 <file:Documentation/networking/net-modules.txt>. The module
1449 will be called ne3210.
1452 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1453 depends on NET_PCI && EISA && EXPERIMENTAL
1456 If you have a network (Ethernet) card of this type, say Y and read
1457 the Ethernet-HOWTO, available from
1458 <http://www.tldp.org/docs.html#howto>.
1460 To compile this driver as a module, choose M here and read
1461 <file:Documentation/networking/net-modules.txt>. The module
1462 will be called es3210.
1465 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1466 depends on NET_PCI && PCI && EXPERIMENTAL
1470 This is a driver for the Fast Ethernet PCI network cards based on
1471 the RTL8139C+ chips. If you have one of those, say Y and read
1472 the Ethernet-HOWTO, available from
1473 <http://www.tldp.org/docs.html#howto>.
1475 To compile this driver as a module, choose M here: the module
1476 will be called 8139cp. This is recommended.
1479 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1480 depends on NET_PCI && PCI
1484 This is a driver for the Fast Ethernet PCI network cards based on
1485 the RTL8139 chips. If you have one of those, say Y and read
1486 the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1488 To compile this driver as a module, choose M here: the module
1489 will be called 8139too. This is recommended.
1492 bool "Use PIO instead of MMIO"
1496 This instructs the driver to use programmed I/O ports (PIO) instead
1497 of PCI shared memory (MMIO). This can possibly solve some problems
1498 in case your mainboard has memory consistency issues. If unsure,
1501 config 8139TOO_TUNE_TWISTER
1502 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1505 This implements a function which might come in handy in case you
1506 are using low quality on long cabling. It is required for RealTek
1507 RTL-8139 revision K boards, and totally unused otherwise. It tries
1508 to match the transceiver to the cable characteristics. This is
1509 experimental since hardly documented by the manufacturer.
1513 bool "Support for older RTL-8129/8130 boards"
1516 This enables support for the older and uncommon RTL-8129 and
1517 RTL-8130 chips, which support MII via an external transceiver,
1518 instead of an internal one. Disabling this option will save some
1519 memory by making the code size smaller. If unsure, say Y.
1521 config 8139_OLD_RX_RESET
1522 bool "Use older RX-reset method"
1525 The 8139too driver was recently updated to contain a more rapid
1526 reset sequence, in the face of severe receive errors. This "new"
1527 RX-reset method should be adequate for all boards. But if you
1528 experience problems, you can enable this option to restore the
1529 old RX-reset behavior. If unsure, say N.
1532 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1533 depends on NET_PCI && PCI
1536 This is a driver for the Fast Ethernet PCI network cards based on
1537 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1538 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1539 read the Ethernet-HOWTO, available at
1540 <http://www.tldp.org/docs.html#howto>. Please read
1541 <file:Documentation/networking/sis900.txt> and comments at the
1542 beginning of <file:drivers/net/sis900.c> for more information.
1544 This driver also supports AMD 79C901 HomePNA so that you can use
1545 your phone line as a network cable.
1547 To compile this driver as a module, choose M here: the module
1548 will be called sis900. This is recommended.
1551 tristate "SMC EtherPower II"
1552 depends on NET_PCI && PCI
1556 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1557 which is based on the SMC83c17x (EPIC/100).
1558 More specific information and updates are available from
1559 <http://www.scyld.com/network/epic100.html>.
1562 tristate "Sundance Alta support"
1563 depends on NET_PCI && PCI
1567 This driver is for the Sundance "Alta" chip.
1568 More specific information and updates are available from
1569 <http://www.scyld.com/network/sundance.html>.
1571 config SUNDANCE_MMIO
1572 bool "Use MMIO instead of PIO"
1575 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1576 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1577 is known to solve bugs on certain chips.
1582 tristate "TI ThunderLAN support"
1583 depends on NET_PCI && (PCI || EISA) && !64BIT
1585 If you have a PCI Ethernet network card based on the ThunderLAN chip
1586 which is supported by this driver, say Y and read the
1587 Ethernet-HOWTO, available from
1588 <http://www.tldp.org/docs.html#howto>.
1590 Devices currently supported by this driver are Compaq Netelligent,
1591 Compaq NetFlex and Olicom cards. Please read the file
1592 <file:Documentation/networking/tlan.txt> for more details.
1594 To compile this driver as a module, choose M here and read
1595 <file:Documentation/networking/net-modules.txt>. The module
1596 will be called tlan.
1598 Please email feedback to <torben.mathiasen@compaq.com>.
1601 tristate "VIA Rhine support"
1602 depends on NET_PCI && PCI
1606 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1607 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1608 Ethernet functions can also be found integrated on South Bridges
1611 To compile this driver as a module, choose M here. The module
1612 will be called via-rhine.
1614 config VIA_RHINE_MMIO
1615 bool "Use MMIO instead of PIO"
1616 depends on VIA_RHINE
1618 This instructs the driver to use PCI shared memory (MMIO) instead of
1619 programmed I/O ports (PIO). Enabling this gives an improvement in
1620 processing time in parts of the driver.
1625 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1626 depends on NET_PCI && EXPERIMENTAL && MIPS
1628 The SAA9730 is a combined multimedia and peripheral controller used
1629 in thin clients, Internet access terminals, and diskless
1631 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1634 bool "Pocket and portable adapters"
1635 depends on NET_ETHERNET && ISA
1637 Cute little network (Ethernet) devices which attach to the parallel
1638 port ("pocket adapters"), commonly used with laptops. If you have
1639 one of those, say Y and read the Ethernet-HOWTO, available from
1640 <http://www.tldp.org/docs.html#howto>.
1642 If you want to plug a network (or some other) card into the PCMCIA
1643 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1644 credit card size extension cards used by all modern laptops), you
1645 need the pcmcia-cs package (location contained in the file
1646 <file:Documentation/Changes>) and you can say N here.
1648 Laptop users should read the Linux Laptop home page at
1649 <http://www.linux-on-laptops.com/> or
1650 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1652 Note that the answer to this question doesn't directly affect the
1653 kernel: saying N will just cause the configurator to skip all
1654 the questions about this class of network devices. If you say Y, you
1655 will be asked for your specific device in the following questions.
1658 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1659 depends on NET_POCKET && ISA && X86
1662 This is a network (Ethernet) device which attaches to your parallel
1663 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1664 available from <http://www.tldp.org/docs.html#howto>, if you
1665 want to use this. If you intend to use this driver, you should have
1666 said N to the "Parallel printer support", because the two drivers
1667 don't like each other.
1669 To compile this driver as a module, choose M here: the module
1673 tristate "D-Link DE600 pocket adapter support"
1674 depends on NET_POCKET && ISA
1676 This is a network (Ethernet) device which attaches to your parallel
1677 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1678 Ethernet-HOWTO, available from
1679 <http://www.tldp.org/docs.html#howto>, if you want to use
1680 this. It is possible to have several devices share a single parallel
1681 port and it is safe to compile the corresponding drivers into the
1684 To compile this driver as a module, choose M here: the module
1685 will be called de600.
1688 tristate "D-Link DE620 pocket adapter support"
1689 depends on NET_POCKET && ISA
1691 This is a network (Ethernet) device which attaches to your parallel
1692 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1693 Ethernet-HOWTO, available from
1694 <http://www.tldp.org/docs.html#howto>, if you want to use
1695 this. It is possible to have several devices share a single parallel
1696 port and it is safe to compile the corresponding drivers into the
1699 To compile this driver as a module, choose M here: the module
1700 will be called de620.
1703 tristate "SGI Seeq ethernet controller support"
1704 depends on NET_ETHERNET && SGI_IP22
1706 Say Y here if you have an Seeq based Ethernet network card. This is
1707 used in many Silicon Graphics machines.
1710 tristate "DEC LANCE ethernet controller support"
1711 depends on NET_ETHERNET && MACH_DECSTATION
1714 This driver is for the series of Ethernet controllers produced by
1715 DEC (now Compaq) based on the AMD Lance chipset, including the
1716 DEPCA series. (This chipset is better known via the NE2100 cards.)
1719 bool "Motorola 68360 ethernet controller"
1722 Say Y here if you want to use the built-in ethernet controller of
1723 the Motorola 68360 processor.
1726 bool "FEC ethernet controller (of ColdFire 5272)"
1727 depends on M5272 || M5282
1729 Say Y here if you want to use the built-in 10/100 Fast ethernet
1730 controller on the Motorola ColdFire 5272 processor.
1733 tristate "NE2000 compatible support for H8/300"
1734 depends on H8300 && NET_ETHERNET
1736 Say Y here if you want to use the NE2000 compatible
1737 controller on the Renesas H8/300 processor.
1739 source "drivers/net/fec_8xx/Kconfig"
1747 menu "Ethernet (1000 Mbit)"
1748 depends on NETDEVICES && !UML
1751 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1754 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1755 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1756 adapter. The driver allows for using the Jumbo Frame option (9000
1757 bytes/frame) however it requires that your switches can handle this
1758 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1761 To compile this driver as a module, choose M here: the
1762 module will be called acenic.
1764 config ACENIC_OMIT_TIGON_I
1765 bool "Omit support for old Tigon I based AceNICs"
1768 Say Y here if you only have Tigon II based AceNICs and want to leave
1769 out support for the older Tigon I based cards which are no longer
1770 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1771 version)). This will reduce the size of the driver object by
1772 app. 100KB. If you are not sure whether your card is a Tigon I or a
1773 Tigon II, say N here.
1775 The safe and default value for this is N.
1778 tristate "D-Link DL2000-based Gigabit Ethernet support"
1782 This driver supports D-Link 2000-based gigabit ethernet cards, which
1784 D-Link DGE-550T Gigabit Ethernet Adapter.
1785 D-Link DL2000-based Gigabit Ethernet Adapter.
1787 To compile this driver as a module, choose M here: the
1788 module will be called dl2k.
1791 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1794 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1795 adapters. For more information on how to identify your adapter, go
1796 to the Adapter & Driver ID Guide at:
1798 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1800 For general information and support, go to the Intel support
1803 <http://support.intel.com>
1805 More specific information on configuring the driver is in
1806 <file:Documentation/networking/e1000.txt>.
1808 To compile this driver as a module, choose M here and read
1809 <file:Documentation/networking/net-modules.txt>. The module
1810 will be called e1000.
1813 bool "Use Rx Polling (NAPI)"
1816 NAPI is a new driver API designed to reduce CPU and interrupt load
1817 when the driver is receiving lots of packets from the card. It is
1818 still somewhat experimental and thus not yet enabled by default.
1820 If your estimated Rx load is 10kpps or more, or if the card will be
1821 deployed on potentially unfriendly networks (e.g. in a firewall),
1824 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1830 tristate "MyriCOM Gigabit Ethernet support"
1833 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1835 To compile this driver as a module, choose M here: the module
1836 will be called myri_sbus. This is recommended.
1839 tristate "National Semiconduct DP83820 support"
1842 This is a driver for the National Semiconductor DP83820 series
1843 of gigabit ethernet MACs. Cards using this chipset include
1844 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1845 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1849 tristate "Packet Engines Hamachi GNIC-II support"
1853 If you have a Gigabit Ethernet card of this type, say Y and read
1854 the Ethernet-HOWTO, available from
1855 <http://www.tldp.org/docs.html#howto>.
1857 To compile this driver as a module, choose M here and read
1858 <file:Documentation/networking/net-modules.txt>. The module will be
1862 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1863 depends on PCI && EXPERIMENTAL
1866 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1867 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1868 used by the Beowulf Linux cluster project. See
1869 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1870 information about this driver in particular and Beowulf in general.
1872 To compile this driver as a module, choose M here: the module
1873 will be called yellowfin. This is recommended.
1876 tristate "Realtek 8169 gigabit ethernet support"
1880 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1882 To compile this driver as a module, choose M here: the module
1883 will be called r8169. This is recommended.
1886 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1887 depends on R8169 && EXPERIMENTAL
1889 NAPI is a new driver API designed to reduce CPU and interrupt load
1890 when the driver is receiving lots of packets from the card. It is
1891 still somewhat experimental and thus not yet enabled by default.
1893 If your estimated Rx load is 10kpps or more, or if the card will be
1894 deployed on potentially unfriendly networks (e.g. in a firewall),
1897 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1904 depends on R8169 && VLAN_8021Q
1906 Say Y here for the r8169 driver to support the functions required
1907 by the kernel 802.1Q code.
1912 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
1915 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1916 compliant Gigabit Ethernet Adapter. The following adapters are supported
1918 - 3Com 3C940 Gigabit LOM Ethernet Adapter
1919 - 3Com 3C941 Gigabit LOM Ethernet Adapter
1920 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
1921 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
1922 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
1923 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
1924 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
1925 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
1926 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
1927 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
1928 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
1929 - DGE-530T Gigabit Ethernet Adapter
1930 - EG1032 v2 Instant Gigabit Network Adapter
1931 - EG1064 v2 Instant Gigabit Network Adapter
1932 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
1933 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
1934 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
1935 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
1936 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
1937 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
1938 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
1939 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
1940 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
1941 - Marvell RDK-8001 Adapter
1942 - Marvell RDK-8002 Adapter
1943 - Marvell RDK-8003 Adapter
1944 - Marvell RDK-8004 Adapter
1945 - Marvell RDK-8006 Adapter
1946 - Marvell RDK-8007 Adapter
1947 - Marvell RDK-8008 Adapter
1948 - Marvell RDK-8009 Adapter
1949 - Marvell RDK-8010 Adapter
1950 - Marvell RDK-8011 Adapter
1951 - Marvell RDK-8012 Adapter
1952 - Marvell RDK-8052 Adapter
1953 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
1954 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
1955 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
1956 - SK-9521 10/100/1000Base-T Adapter
1957 - SK-9521 V2.0 10/100/1000Base-T Adapter
1958 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
1959 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
1960 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
1961 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
1962 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
1963 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
1964 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
1965 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
1966 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
1967 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
1968 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
1969 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
1970 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
1971 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
1972 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
1973 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
1974 - SMC EZ Card 1000 (SMC9452TXV.2)
1976 The adapters support Jumbo Frames.
1977 The dual link adapters support link-failover and dual port features.
1978 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
1979 the scatter-gather functionality with sendfile(). Please refer to
1980 <file:Documentation/networking/sk98lin.txt> for more information about
1981 optional driver parameters.
1982 Questions concerning this driver may be addressed to:
1983 <linux@syskonnect.de>
1985 If you want to compile this driver as a module ( = code which can be
1986 inserted in and removed from the running kernel whenever you want),
1987 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
1988 be called sk98lin. This is recommended.
1991 tristate "VIA Velocity support"
1992 depends on NET_PCI && PCI
1997 If you have a VIA "Velocity" based network card say Y here.
1999 To compile this driver as a module, choose M here. The module
2000 will be called via-velocity.
2003 tristate "Broadcom Tigon3 support"
2006 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2008 To compile this driver as a module, choose M here: the module
2009 will be called tg3. This is recommended.
2012 tristate "Gianfar Ethernet"
2013 depends on 85xx || 83xx
2015 This driver supports the Gigabit TSEC on the MPC85xx
2016 family of chips, and the FEC on the 8540
2023 tristate "MV-643XX Ethernet support"
2024 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
2026 This driver supports the gigabit Ethernet on the Marvell MV643XX
2027 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2028 Pegasos II, amongst other PPC and MIPS boards.
2030 config MV643XX_ETH_0
2031 bool "MV-643XX Port 0"
2032 depends on MV643XX_ETH
2034 This enables support for Port 0 of the Marvell MV643XX Gigabit
2037 config MV643XX_ETH_1
2038 bool "MV-643XX Port 1"
2039 depends on MV643XX_ETH
2041 This enables support for Port 1 of the Marvell MV643XX Gigabit
2044 config MV643XX_ETH_2
2045 bool "MV-643XX Port 2"
2046 depends on MV643XX_ETH
2048 This enables support for Port 2 of the Marvell MV643XX Gigabit
2054 # 10 Gigabit Ethernet
2057 menu "Ethernet (10000 Mbit)"
2058 depends on NETDEVICES && !UML
2061 tristate "Intel(R) PRO/10GbE support"
2064 This driver supports Intel(R) PRO/10GbE family of
2065 adapters. For more information on how to identify your adapter, go
2066 to the Adapter & Driver ID Guide at:
2068 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2070 For general information and support, go to the Intel support
2073 <http://support.intel.com>
2075 More specific information on configuring the driver is in
2076 <file:Documentation/networking/ixgb.txt>.
2078 To compile this driver as a module, choose M here and read
2079 <file:Documentation/networking/net-modules.txt>. The module
2080 will be called ixgb.
2083 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2084 depends on IXGB && EXPERIMENTAL
2086 NAPI is a new driver API designed to reduce CPU and interrupt load
2087 when the driver is receiving lots of packets from the card. It is
2088 still somewhat experimental and thus not yet enabled by default.
2090 If your estimated Rx load is 10kpps or more, or if the card will be
2091 deployed on potentially unfriendly networks (e.g. in a firewall),
2094 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2100 tristate "S2IO 10Gbe XFrame NIC"
2103 This driver supports the 10Gbe XFrame NIC of S2IO.
2104 For help regarding driver compilation, installation and
2105 tuning please look into ~/drivers/net/s2io/README.txt.
2108 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2109 depends on S2IO && EXPERIMENTAL
2111 NAPI is a new driver API designed to reduce CPU and interrupt load
2112 when the driver is receiving lots of packets from the card. It is
2113 still somewhat experimental and thus not yet enabled by default.
2115 If your estimated Rx load is 10kpps or more, or if the card will be
2116 deployed on potentially unfriendly networks (e.g. in a firewall),
2119 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2125 bool "Use 2 Buffer Mode on Rx side."
2128 On enabling the 2 buffer mode, the received frame will be
2129 split into 2 parts before being DMA'ed to the hosts memory.
2130 The parts are the ethernet header and ethernet payload.
2131 This is useful on systems where DMA'ing to to unaligned
2132 physical memory loactions comes with a heavy price.
2133 If not sure please say N.
2138 source "drivers/net/tokenring/Kconfig"
2140 source "drivers/net/wireless/Kconfig"
2142 source "drivers/net/pcmcia/Kconfig"
2145 source "drivers/net/wan/Kconfig"
2147 source "drivers/atm/Kconfig"
2149 source "drivers/s390/net/Kconfig"
2152 tristate "iSeries Virtual Ethernet driver support"
2153 depends on NETDEVICES && PPC_ISERIES
2156 bool "FDDI driver support"
2157 depends on NETDEVICES && (PCI || EISA)
2159 Fiber Distributed Data Interface is a high speed local area network
2160 design; essentially a replacement for high speed Ethernet. FDDI can
2161 run over copper or fiber. If you are connected to such a network and
2162 want a driver for the FDDI card in your computer, say Y here (and
2163 then also Y to the driver for your FDDI card, below). Most people
2167 tristate "Digital DEFEA and DEFPA adapter support"
2168 depends on FDDI && (PCI || EISA)
2170 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2171 (DEFPA) controllers which can connect you to a local FDDI network.
2174 tristate "SysKonnect FDDI PCI support"
2175 depends on FDDI && PCI
2177 Say Y here if you have a SysKonnect FDDI PCI adapter.
2178 The following adapters are supported by this driver:
2179 - SK-5521 (SK-NET FDDI-UP)
2180 - SK-5522 (SK-NET FDDI-UP DAS)
2181 - SK-5541 (SK-NET FDDI-FP)
2182 - SK-5543 (SK-NET FDDI-LP)
2183 - SK-5544 (SK-NET FDDI-LP DAS)
2184 - SK-5821 (SK-NET FDDI-UP64)
2185 - SK-5822 (SK-NET FDDI-UP64 DAS)
2186 - SK-5841 (SK-NET FDDI-FP64)
2187 - SK-5843 (SK-NET FDDI-LP64)
2188 - SK-5844 (SK-NET FDDI-LP64 DAS)
2189 - Netelligent 100 FDDI DAS Fibre SC
2190 - Netelligent 100 FDDI SAS Fibre SC
2191 - Netelligent 100 FDDI DAS UTP
2192 - Netelligent 100 FDDI SAS UTP
2193 - Netelligent 100 FDDI SAS Fibre MIC
2195 Read <file:Documentation/networking/skfp.txt> for information about
2198 Questions concerning this driver can be addressed to:
2199 <linux@syskonnect.de>
2201 To compile this driver as a module, choose M here: the module
2202 will be called skfp. This is recommended.
2205 bool "HIPPI driver support (EXPERIMENTAL)"
2206 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2208 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2209 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2210 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2211 single-mode). HIPPI networks are commonly used for clusters and to
2212 connect to super computers. If you are connected to a HIPPI network
2213 and have a HIPPI network card in your computer that you want to use
2214 under Linux, say Y here (you must also remember to enable the driver
2215 for your HIPPI card below). Most people will say N here.
2218 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2219 depends on HIPPI && PCI
2221 Say Y here if this is your PCI HIPPI network card.
2223 To compile this driver as a module, choose M here: the module
2224 will be called rrunner. If unsure, say N.
2226 config ROADRUNNER_LARGE_RINGS
2227 bool "Use large TX/RX rings (EXPERIMENTAL)"
2228 depends on ROADRUNNER
2230 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2231 of additional memory to allow for fastest operation, both for
2232 transmitting and receiving. This memory cannot be used by any other
2233 kernel code or by user space programs. Say Y here only if you have
2237 tristate "PLIP (parallel port) support"
2238 depends on NETDEVICES && PARPORT
2240 PLIP (Parallel Line Internet Protocol) is used to create a
2241 reasonably fast mini network consisting of two (or, rarely, more)
2242 local machines. A PLIP link from a Linux box is a popular means to
2243 install a Linux distribution on a machine which doesn't have a
2244 CD-ROM drive (a minimal system has to be transferred with floppies
2245 first). The kernels on both machines need to have this PLIP option
2246 enabled for this to work.
2248 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2249 ports (the connectors at the computers with 25 holes) are connected
2250 with "null printer" or "Turbo Laplink" cables which can transmit 4
2251 bits at a time (mode 0) or with special PLIP cables, to be used on
2252 bidirectional parallel ports only, which can transmit 8 bits at a
2253 time (mode 1); you can find the wiring of these cables in
2254 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2255 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2256 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2257 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2258 and winsock or NCSA's telnet.
2260 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2261 as the NET-3-HOWTO, both available from
2262 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2263 protocol has been changed and this PLIP driver won't work together
2264 with the PLIP support in Linux versions 1.0.x. This option enlarges
2265 your kernel by about 8 KB.
2267 To compile this driver as a module, choose M here and read
2268 <file:Documentation/networking/net-modules.txt>. The module will be
2269 called plip. If unsure, say Y or M, in case you buy a laptop
2273 tristate "PPP (point-to-point protocol) support"
2274 depends on NETDEVICES
2276 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2277 the same purpose: sending Internet traffic over telephone (and other
2278 serial) lines. Ask your access provider if they support it, because
2279 otherwise you can't use it; most Internet access providers these
2280 days support PPP rather than SLIP.
2282 To use PPP, you need an additional program called pppd as described
2283 in the PPP-HOWTO, available at
2284 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2285 the version of pppd recommended in <file:Documentation/Changes>.
2286 The PPP option enlarges your kernel by about 16 KB.
2288 There are actually two versions of PPP: the traditional PPP for
2289 asynchronous lines, such as regular analog phone lines, and
2290 synchronous PPP which can be used over digital ISDN lines for
2291 example. If you want to use PPP over phone lines or other
2292 asynchronous serial lines, you need to say Y (or M) here and also to
2293 the next option, "PPP support for async serial ports". For PPP over
2294 synchronous lines, you should say Y (or M) here and to "Support
2295 synchronous PPP", below.
2297 If you said Y to "Version information on all symbols" above, then
2298 you cannot compile the PPP driver into the kernel; you can then only
2299 compile it as a module. To compile this driver as a module, choose M
2300 here and read <file:Documentation/networking/net-modules.txt>.
2301 The module will be called ppp_generic.
2303 config PPP_MULTILINK
2304 bool "PPP multilink support (EXPERIMENTAL)"
2305 depends on PPP && EXPERIMENTAL
2307 PPP multilink is a protocol (defined in RFC 1990) which allows you
2308 to combine several (logical or physical) lines into one logical PPP
2309 connection, so that you can utilize your full bandwidth.
2311 This has to be supported at the other end as well and you need a
2312 version of the pppd daemon which understands the multilink protocol.
2317 bool "PPP filtering"
2320 Say Y here if you want to be able to filter the packets passing over
2321 PPP interfaces. This allows you to control which packets count as
2322 activity (i.e. which packets will reset the idle timer or bring up
2323 a demand-dialled link) and which packets are to be dropped entirely.
2324 You need to say Y here if you wish to use the pass-filter and
2325 active-filter options to pppd.
2330 tristate "PPP support for async serial ports"
2334 Say Y (or M) here if you want to be able to use PPP over standard
2335 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2336 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2339 To compile this driver as a module, choose M here.
2344 tristate "PPP support for sync tty ports"
2347 Say Y (or M) here if you want to be able to use PPP over synchronous
2348 (HDLC) tty devices, such as the SyncLink adapter. These devices
2349 are often used for high-speed leased lines like T1/E1.
2351 To compile this driver as a module, choose M here.
2354 tristate "PPP Deflate compression"
2359 Support for the Deflate compression method for PPP, which uses the
2360 Deflate algorithm (the same algorithm that gzip uses) to compress
2361 each PPP packet before it is sent over the wire. The machine at the
2362 other end of the PPP link (usually your ISP) has to support the
2363 Deflate compression method as well for this to be useful. Even if
2364 they don't support it, it is safe to say Y here.
2366 To compile this driver as a module, choose M here.
2369 tristate "PPP BSD-Compress compression"
2372 Support for the BSD-Compress compression method for PPP, which uses
2373 the LZW compression method to compress each PPP packet before it is
2374 sent over the wire. The machine at the other end of the PPP link
2375 (usually your ISP) has to support the BSD-Compress compression
2376 method as well for this to be useful. Even if they don't support it,
2377 it is safe to say Y here.
2379 The PPP Deflate compression method ("PPP Deflate compression",
2380 above) is preferable to BSD-Compress, because it compresses better
2383 Note that the BSD compression code will always be compiled as a
2384 module; it is called bsd_comp and will show up in the directory
2385 modules once you have said "make modules". If unsure, say N.
2388 tristate "PPP over Ethernet (EXPERIMENTAL)"
2389 depends on EXPERIMENTAL && PPP
2391 Support for PPP over Ethernet.
2393 This driver requires the latest version of pppd from the CVS
2394 repository at cvs.samba.org. Alternatively, see the
2395 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2396 which contains instruction on how to use this driver (under
2397 the heading "Kernel mode PPPoE").
2400 tristate "PPP over ATM"
2401 depends on ATM && PPP
2403 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2404 This implementation does not yet comply with section 8 of RFC2364,
2405 which can lead to bad results if the ATM peer loses state and
2406 changes its encapsulation unilaterally.
2409 tristate "SLIP (serial line) support"
2410 depends on NETDEVICES
2412 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2413 connect to your Internet service provider or to connect to some
2414 other local Unix box or if you want to configure your Linux box as a
2415 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2416 Internet Protocol) is a protocol used to send Internet traffic over
2417 serial connections such as telephone lines or null modem cables;
2418 nowadays, the protocol PPP is more commonly used for this same
2421 Normally, your access provider has to support SLIP in order for you
2422 to be able to use it, but there is now a SLIP emulator called SLiRP
2423 around (available from
2424 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2425 allows you to use SLIP over a regular dial up shell connection. If
2426 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2427 NET-3-HOWTO, available from
2428 <http://www.tldp.org/docs.html#howto>, explains how to
2429 configure SLIP. Note that you don't need this option if you just
2430 want to run term (term is a program which gives you almost full
2431 Internet connectivity if you have a regular dial up shell account on
2432 some Internet connected Unix computer. Read
2433 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2434 support will enlarge your kernel by about 4 KB. If unsure, say N.
2436 To compile this driver as a module, choose M here and read
2437 <file:Documentation/networking/net-modules.txt>. The module will be
2440 config SLIP_COMPRESSED
2441 bool "CSLIP compressed headers"
2444 This protocol is faster than SLIP because it uses compression on the
2445 TCP/IP headers (not on the data itself), but it has to be supported
2446 on both ends. Ask your access provider if you are not sure and
2447 answer Y, just in case. You will still be able to use plain SLIP. If
2448 you plan to use SLiRP, the SLIP emulator (available from
2449 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2450 allows you to use SLIP over a regular dial up shell connection, you
2451 definitely want to say Y here. The NET-3-HOWTO, available from
2452 <http://www.tldp.org/docs.html#howto>, explains how to configure
2453 CSLIP. This won't enlarge your kernel.
2456 bool "Keepalive and linefill"
2459 Adds additional capabilities to the SLIP driver to support the
2460 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2463 config SLIP_MODE_SLIP6
2464 bool "Six bit SLIP encapsulation"
2467 Just occasionally you may need to run IP over hostile serial
2468 networks that don't pass all control characters or are only seven
2469 bit. Saying Y here adds an extra mode you can use with SLIP:
2470 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2471 the serial device. Naturally, this has to be supported at the other
2472 end of the link as well. It's good enough, for example, to run IP
2473 over the async ports of a Camtec JNT Pad. If unsure, say N.
2476 bool "Fibre Channel driver support"
2477 depends on NETDEVICES && SCSI && PCI
2479 Fibre Channel is a high speed serial protocol mainly used to connect
2480 large storage devices to the computer; it is compatible with and
2481 intended to replace SCSI.
2483 If you intend to use Fibre Channel, you need to have a Fibre channel
2484 adaptor card in your computer; say Y here and to the driver for your
2485 adaptor below. You also should have said Y to "SCSI support" and
2486 "SCSI generic support".
2489 tristate "Traffic Shaper (EXPERIMENTAL)"
2490 depends on NETDEVICES && EXPERIMENTAL
2492 The traffic shaper is a virtual network device that allows you to
2493 limit the rate of outgoing data flow over some other network device.
2494 The traffic that you want to slow down can then be routed through
2495 these virtual devices. See
2496 <file:Documentation/networking/shaper.txt> for more information.
2498 An alternative to this traffic shaper is the experimental
2499 Class-Based Queueing (CBQ) scheduling support which you get if you
2500 say Y to "QoS and/or fair queueing" above.
2502 To set up and configure shaper devices, you need the shapecfg
2503 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2506 To compile this driver as a module, choose M here: the module
2507 will be called shaper. If unsure, say N.
2510 tristate "Network console logging support (EXPERIMENTAL)"
2511 depends on NETDEVICES && EXPERIMENTAL
2513 If you want to log kernel messages over the network, enable this.
2514 See <file:Documentation/networking/netconsole.txt> for details.