3 # Network device configuration
6 menu "Network device support"
10 bool "Network device support"
12 You can say N here if you don't intend to connect your Linux box to
13 any other computer at all.
15 You'll have to say Y if your computer contains a network card that
16 you want to use under Linux. If you are going to run SLIP or PPP over
17 telephone line or null modem cable you need say Y here. Connecting
18 two machines with parallel ports using PLIP needs this, as well as
19 AX.25/KISS for sending Internet traffic over amateur radio links.
21 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
22 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
26 # All the following symbols are dependent on NETDEVICES - do not repeat
27 # that for each of the symbols.
31 tristate "Dummy net driver support"
33 This is essentially a bit-bucket device (i.e. traffic you send to
34 this device is consigned into oblivion) with a configurable IP
35 address. It is most commonly used in order to make your currently
36 inactive SLIP address seem like a real address for local programs.
37 If you use SLIP or PPP, you might want to say Y here. Since this
38 thing often comes in handy, the default is Y. It won't enlarge your
39 kernel either. What a deal. Read about it in the Network
40 Administrator's Guide, available from
41 <http://www.tldp.org/docs.html#guide>.
43 To compile this driver as a module, choose M here: the module
44 will be called dummy. If you want to use more than one dummy
45 device at a time, you need to compile this driver as a module.
46 Instead of 'dummy', the devices will then be called 'dummy0',
50 tristate "Bonding driver support"
53 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
54 Channels together. This is called 'Etherchannel' by Cisco,
55 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
57 The driver supports multiple bonding modes to allow for both high
58 perfomance and high availability operation.
60 Refer to <file:Documentation/networking/bonding.txt> for more
63 To compile this driver as a module, choose M here: the module
64 will be called bonding.
67 tristate "EQL (serial line load balancing) support"
69 If you have two serial connections to some other computer (this
70 usually requires two modems and two telephone lines) and you use
71 SLIP (the protocol for sending Internet traffic over telephone
72 lines) or PPP (a better SLIP) on them, you can make them behave like
73 one double speed connection using this driver. Naturally, this has
74 to be supported at the other end as well, either with a similar EQL
75 Linux driver or with a Livingston Portmaster 2e.
77 Say Y if you want this and read
78 <file:Documentation/networking/eql.txt>. You may also want to read
79 section 6.2 of the NET-3-HOWTO, available from
80 <http://www.tldp.org/docs.html#howto>.
82 To compile this driver as a module, choose M here: the module
83 will be called eql. If unsure, say N.
86 tristate "Universal TUN/TAP device driver support"
89 TUN/TAP provides packet reception and transmission for user space
90 programs. It can be viewed as a simple Point-to-Point or Ethernet
91 device, which instead of receiving packets from a physical media,
92 receives them from user space program and instead of sending packets
93 via physical media writes them to the user space program.
95 When a program opens /dev/net/tun, driver creates and registers
96 corresponding net device tunX or tapX. After a program closed above
97 devices, driver will automatically delete tunXX or tapXX device and
98 all routes corresponding to it.
100 Please read <file:Documentation/networking/tuntap.txt> for more
103 To compile this driver as a module, choose M here: the module
106 If you don't know what to use this for, you don't need it.
109 tristate "General Instruments Surfboard 1000"
112 This is a driver for the General Instrument (also known as
113 NextLevel) SURFboard 1000 internal
114 cable modem. This is an ISA card which is used by a number of cable
115 TV companies to provide cable modem access. It's a one-way
116 downstream-only cable modem, meaning that your upstream net link is
117 provided by your regular phone modem.
119 At present this driver only compiles as a module, so say M here if
120 you have this card. The module will be called sb1000. Then read
121 <file:Documentation/networking/README.sb1000> for information on how
122 to use this module, as it needs special ppp scripts for establishing
123 a connection. Further documentation and the necessary scripts can be
126 <http://www.jacksonville.net/~fventuri/>
127 <http://home.adelphia.net/~siglercm/sb1000.html>
128 <http://linuxpower.cx/~cable/>
130 If you don't have this card, of course say N.
132 source "drivers/net/arcnet/Kconfig"
134 source "drivers/net/phy/Kconfig"
140 menu "Ethernet (10 or 100Mbit)"
144 bool "Ethernet (10 or 100Mbit)"
146 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
147 type of Local Area Network (LAN) in universities and companies.
149 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
150 coaxial cable, linking computers in a chain), 10BASE-T or twisted
151 pair (10 Mbps over twisted pair cable, linking computers to central
152 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
153 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
154 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
155 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
156 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
157 Ethernet (1 Gbps over optical fiber or short copper links).
159 If your Linux machine will be connected to an Ethernet and you have
160 an Ethernet network interface card (NIC) installed in your computer,
161 say Y here and read the Ethernet-HOWTO, available from
162 <http://www.tldp.org/docs.html#howto>. You will then also have
163 to say Y to the driver for your particular NIC.
165 Note that the answer to this question won't directly affect the
166 kernel: saying N will just cause the configurator to skip all
167 the questions about Ethernet network cards. If unsure, say N.
170 tristate "Generic Media Independent Interface device support"
171 depends on NET_ETHERNET
173 Most ethernet controllers have MII transceiver either as an external
174 or internal device. It is safe to say Y or M here even if your
175 ethernet card lack MII.
177 source "drivers/net/arm/Kconfig"
180 tristate "MACE (Power Mac ethernet) support"
181 depends on NET_ETHERNET && PPC_PMAC && PPC32
184 Power Macintoshes and clones with Ethernet built-in on the
185 motherboard will usually use a MACE (Medium Access Control for
186 Ethernet) interface. Say Y to include support for the MACE chip.
188 To compile this driver as a module, choose M here: the module
191 config MACE_AAUI_PORT
192 bool "Use AAUI port instead of TP by default"
195 Some Apple machines (notably the Apple Network Server) which use the
196 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
197 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
198 Y here if you have such a machine. If unsure, say N.
199 The driver will default to AAUI on ANS anyway, and if you use it as
200 a module, you can provide the port_aaui=0|1 to force the driver.
203 tristate "BMAC (G3 ethernet) support"
204 depends on NET_ETHERNET && PPC_PMAC && PPC32
207 Say Y for support of BMAC Ethernet interfaces. These are used on G3
210 To compile this driver as a module, choose M here: the module
214 tristate "National DP83902AV (Oak ethernet) support"
215 depends on NET_ETHERNET && PPC && BROKEN
218 Say Y if your machine has this type of Ethernet network card.
220 To compile this driver as a module, choose M here: the module
221 will be called oaknet.
224 tristate "Ariadne support"
225 depends on NET_ETHERNET && ZORRO
227 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
230 To compile this driver as a module, choose M here: the module
231 will be called ariadne.
234 tristate "A2065 support"
235 depends on NET_ETHERNET && ZORRO
238 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
241 To compile this driver as a module, choose M here: the module
242 will be called a2065.
245 tristate "Hydra support"
246 depends on NET_ETHERNET && ZORRO
249 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
251 To compile this driver as a module, choose M here: the module
252 will be called hydra.
255 tristate "Zorro NS8390-based Ethernet support"
256 depends on NET_ETHERNET && ZORRO
259 This driver is for Zorro Ethernet cards using an NS8390-compatible
260 chipset, like the Village Tronic Ariadne II and the Individual
261 Computers X-Surf Ethernet cards. If you have such a card, say Y.
264 To compile this driver as a module, choose M here: the module
265 will be called zorro8390.
268 tristate "PCMCIA NE2000 support"
269 depends on NET_ETHERNET && AMIGA_PCMCIA
272 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
275 To compile this driver as a module, choose M here: the module
279 tristate "Apollo 3c505 support"
280 depends on NET_ETHERNET && APOLLO
282 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
283 If you don't have one made for Apollos, you can use one from a PC,
284 except that your Apollo won't be able to boot from it (because the
285 code in the ROM will be for a PC).
288 bool "Macintosh NS 8390 based ethernet cards"
289 depends on NET_ETHERNET && MAC
292 If you want to include a driver to support Nubus or LC-PDS
293 Ethernet cards using an NS8390 chipset or its equivalent, say Y
294 and read the Ethernet-HOWTO, available from
295 <http://www.tldp.org/docs.html#howto>.
298 tristate "Macintosh CS89x0 based ethernet cards"
299 depends on NET_ETHERNET && MAC && BROKEN
301 Support for CS89x0 chipset based Ethernet cards. If you have a
302 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
303 read the Ethernet-HOWTO, available from
304 <http://www.tldp.org/docs.html#howto>.
306 To compile this driver as a module, choose M here and read
307 <file:Documentation/networking/net-modules.txt>. This module will
311 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
312 depends on NET_ETHERNET && MAC
314 Support for NatSemi SONIC based Ethernet devices. This includes
315 the onboard Ethernet in many Quadras as well as some LC-PDS,
316 a few Nubus and all known Comm Slot Ethernet cards. If you have
317 one of these say Y and read the Ethernet-HOWTO, available from
318 <http://www.tldp.org/docs.html#howto>.
320 To compile this driver as a module, choose M here and read
321 <file:Documentation/networking/net-modules.txt>. This module will
325 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
326 depends on NET_ETHERNET && MAC && EXPERIMENTAL
329 Support for the onboard AMD 79C940 MACE Ethernet controller used in
330 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
331 say Y and read the Ethernet-HOWTO, available from
332 <http://www.tldp.org/docs.html#howto>.
335 tristate "MVME147 (Lance) Ethernet support"
336 depends on NET_ETHERNET && MVME147
339 Support for the on-board Ethernet interface on the Motorola MVME147
340 single-board computer. Say Y here to include the
341 driver for this chip in your kernel.
342 To compile this driver as a module, choose M here.
345 tristate "MVME16x Ethernet support"
346 depends on NET_ETHERNET && MVME16x
348 This is the driver for the Ethernet interface on the Motorola
349 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
350 driver for this chip in your kernel.
351 To compile this driver as a module, choose M here.
354 tristate "BVME6000 Ethernet support"
355 depends on NET_ETHERNET && BVME6000
357 This is the driver for the Ethernet interface on BVME4000 and
358 BVME6000 VME boards. Say Y here to include the driver for this chip
360 To compile this driver as a module, choose M here.
363 tristate "Atari Lance support"
364 depends on NET_ETHERNET && ATARI
366 Say Y to include support for several Atari Ethernet adapters based
367 on the AMD Lance chipset: RieblCard (with or without battery), or
368 PAMCard VME (also the version by Rhotron, with different addresses).
371 tristate "BioNet-100 support"
372 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
374 Say Y to include support for BioData's BioNet-100 Ethernet adapter
375 for the ACSI port. The driver works (has to work...) with a polled
376 I/O scheme, so it's rather slow :-(
379 tristate "PAMsNet support"
380 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
382 Say Y to include support for the PAMsNet Ethernet adapter for the
383 ACSI port ("ACSI node"). The driver works (has to work...) with a
384 polled I/O scheme, so it's rather slow :-(
387 tristate "Sun3/Sun3x on-board LANCE support"
388 depends on NET_ETHERNET && (SUN3 || SUN3X)
390 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
391 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
392 here to compile in the Linux driver for this and enable Ethernet.
393 General Linux information on the Sun 3 and 3x series (now
395 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
397 If you're not building a kernel for a Sun 3, say N.
400 bool "Sun3 on-board Intel 82586 support"
401 depends on NET_ETHERNET && SUN3
403 This driver enables support for the on-board Intel 82586 based
404 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
405 that this driver does not support 82586-based adapters on additional
409 bool "HP on-board LANCE support"
410 depends on NET_ETHERNET && DIO
413 If you want to use the builtin "LANCE" Ethernet controller on an
414 HP300 machine, say Y here.
417 tristate "Lasi ethernet"
418 depends on NET_ETHERNET && PARISC && GSC_LASI
420 Say Y here to support the on-board Intel 82596 ethernet controller
421 built into Hewlett-Packard PA-RISC machines.
423 config MIPS_JAZZ_SONIC
424 tristate "MIPS JAZZ onboard SONIC Ethernet support"
425 depends on NET_ETHERNET && MACH_JAZZ
427 This is the driver for the onboard card of MIPS Magnum 4000,
428 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
430 config MIPS_GT96100ETH
431 bool "MIPS GT96100 Ethernet support"
432 depends on NET_ETHERNET && MIPS_GT96100
434 Say Y here to support the Ethernet subsystem on your GT96100 card.
436 config MIPS_AU1X00_ENET
437 bool "MIPS AU1000 Ethernet support"
438 depends on NET_ETHERNET && SOC_AU1X00
441 If you have an Alchemy Semi AU1X00 based system
442 say Y. Otherwise, say N.
444 config NET_SB1250_MAC
445 tristate "SB1250 Ethernet support"
446 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
449 bool "SGI IOC3 Ethernet"
450 depends on NET_ETHERNET && PCI && SGI_IP27 && BROKEN
454 If you have a network (Ethernet) card of this type, say Y and read
455 the Ethernet-HOWTO, available from
456 <http://www.tldp.org/docs.html#howto>.
458 config SGI_IOC3_ETH_HW_RX_CSUM
459 bool "Receive hardware checksums"
460 depends on SGI_IOC3_ETH && INET
463 The SGI IOC3 network adapter supports TCP and UDP checksums in
464 hardware to offload processing of these checksums from the CPU. At
465 the moment only acceleration of IPv4 is supported. This option
466 enables offloading for checksums on receive. If unsure, say Y.
468 config SGI_IOC3_ETH_HW_TX_CSUM
469 bool "Transmit hardware checksums"
470 depends on SGI_IOC3_ETH && INET
473 The SGI IOC3 network adapter supports TCP and UDP checksums in
474 hardware to offload processing of these checksums from the CPU. At
475 the moment only acceleration of IPv4 is supported. This option
476 enables offloading for checksums on transmit. If unsure, say Y.
478 config SGI_O2MACE_ETH
479 tristate "SGI O2 MACE Fast Ethernet support"
480 depends on NET_ETHERNET && SGI_IP32=y
483 tristate "National DP83902AV support"
484 depends on NET_ETHERNET && SUPERH
487 Support for cards based on the National Semiconductor DP83902AV
488 ST-NIC Serial Network Interface Controller for Twisted Pair. This
489 is a 10Mbit/sec Ethernet controller. Product overview and specs at
490 <http://www.national.com/pf/DP/DP83902A.html>.
495 tristate "Sun LANCE support"
496 depends on NET_ETHERNET && SBUS
499 This driver supports the "le" interface present on all 32-bit Sparc
500 systems, on some older Ultra systems and as an Sbus option. These
501 cards are based on the AMD Lance chipset, which is better known
502 via the NE2100 cards.
504 To compile this driver as a module, choose M here: the module
505 will be called sunlance.
508 tristate "Sun Happy Meal 10/100baseT support"
509 depends on NET_ETHERNET && (SBUS || PCI)
512 This driver supports the "hme" interface present on most Ultra
513 systems and as an option on older Sbus systems. This driver supports
514 both PCI and Sbus devices. This driver also supports the "qfe" quad
515 100baseT device available in both PCI and Sbus configurations.
517 To compile this driver as a module, choose M here: the module
518 will be called sunhme.
521 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
522 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
525 This driver supports the "be" interface available as an Sbus option.
526 This is Sun's older 100baseT Ethernet device.
528 To compile this driver as a module, choose M here: the module
529 will be called sunbmac.
532 tristate "Sun QuadEthernet support"
533 depends on NET_ETHERNET && SBUS
536 This driver supports the "qe" 10baseT Ethernet device, available as
537 an Sbus option. Note that this is not the same as Quad FastEthernet
538 "qfe" which is supported by the Happy Meal driver instead.
540 To compile this driver as a module, choose M here: the module
541 will be called sunqe.
544 tristate "Sun GEM support"
545 depends on NET_ETHERNET && PCI
548 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
549 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
551 config NET_VENDOR_3COM
553 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
555 If you have a network (Ethernet) card belonging to this class, say Y
556 and read the Ethernet-HOWTO, available from
557 <http://www.tldp.org/docs.html#howto>.
559 Note that the answer to this question doesn't directly affect the
560 kernel: saying N will just cause the configurator to skip all
561 the questions about 3COM cards. If you say Y, you will be asked for
562 your specific card in the following questions.
565 tristate "3c501 \"EtherLink\" support"
566 depends on NET_VENDOR_3COM && ISA
568 If you have a network (Ethernet) card of this type, say Y and read
569 the Ethernet-HOWTO, available from
570 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
571 new card, since the 3c501 is slow, broken, and obsolete: you will
572 have problems. Some people suggest to ping ("man ping") a nearby
573 machine every minute ("man cron") when using this card.
575 To compile this driver as a module, choose M here and read
576 <file:Documentation/networking/net-modules.txt>. The module
577 will be called 3c501.
580 tristate "3c503 \"EtherLink II\" support"
581 depends on NET_VENDOR_3COM && ISA
584 If you have a network (Ethernet) card of this type, say Y and read
585 the Ethernet-HOWTO, available from
586 <http://www.tldp.org/docs.html#howto>.
588 To compile this driver as a module, choose M here and read
589 <file:Documentation/networking/net-modules.txt>. The module
590 will be called 3c503.
593 tristate "3c505 \"EtherLink Plus\" support"
594 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
596 Information about this network (Ethernet) card can be found in
597 <file:Documentation/networking/3c505.txt>. If you have a card of
598 this type, say Y and read the Ethernet-HOWTO, available from
599 <http://www.tldp.org/docs.html#howto>.
601 To compile this driver as a module, choose M here and read
602 <file:Documentation/networking/net-modules.txt>. The module
603 will be called 3c505.
606 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
607 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
609 If you have a network (Ethernet) card of this type, say Y and read
610 the Ethernet-HOWTO, available from
611 <http://www.tldp.org/docs.html#howto>.
613 To compile this driver as a module, choose M here and read
614 <file:Documentation/networking/net-modules.txt>. The module
615 will be called 3c507.
618 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
619 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
621 If you have a network (Ethernet) card belonging to the 3Com
622 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
623 from <http://www.tldp.org/docs.html#howto>.
625 If your card is not working you may need to use the DOS
626 setup disk to disable Plug & Play mode, and to select the default
629 To compile this driver as a module, choose M here and read
630 <file:Documentation/networking/net-modules.txt>. The module
631 will be called 3c509.
634 tristate "3c515 ISA \"Fast EtherLink\""
635 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
637 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
638 network card, say Y and read the Ethernet-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
641 To compile this driver as a module, choose M here and read
642 <file:Documentation/networking/net-modules.txt>. The module
643 will be called 3c515.
646 tristate "3c523 \"EtherLink/MC\" support"
647 depends on NET_VENDOR_3COM && MCA_LEGACY
649 If you have a network (Ethernet) card of this type, say Y and read
650 the Ethernet-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>.
653 To compile this driver as a module, choose M here and read
654 <file:Documentation/networking/net-modules.txt>. The module
655 will be called 3c523.
658 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
659 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
661 If you have a network (Ethernet) card of this type, say Y and read
662 the Ethernet-HOWTO, available from
663 <http://www.tldp.org/docs.html#howto>.
665 To compile this driver as a module, choose M here and read
666 <file:Documentation/networking/net-modules.txt>. The module
667 will be called 3c527.
670 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
671 depends on NET_VENDOR_3COM && (PCI || EISA)
674 This option enables driver support for a large number of 10mbps and
675 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
677 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
678 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
679 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
680 "Tornado" (3c905) PCI
681 "Hurricane" (3c555/3cSOHO) PCI
683 If you have such a card, say Y and read the Ethernet-HOWTO,
684 available from <http://www.tldp.org/docs.html#howto>. More
685 specific information is in
686 <file:Documentation/networking/vortex.txt> and in the comments at
687 the beginning of <file:drivers/net/3c59x.c>.
689 To compile this support as a module, choose M here and read
690 <file:Documentation/networking/net-modules.txt>.
693 tristate "3cr990 series \"Typhoon\" support"
694 depends on NET_VENDOR_3COM && PCI
697 This option enables driver support for the 3cr990 series of cards:
699 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
700 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
701 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
703 If you have a network (Ethernet) card of this type, say Y and read
704 the Ethernet-HOWTO, available from
705 <http://www.tldp.org/docs.html#howto>.
707 To compile this driver as a module, choose M here and read
708 <file:Documentation/networking/net-modules.txt>. The module
709 will be called typhoon.
712 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
713 depends on NET_ETHERNET && ISA && ISA_DMA_API
715 If you have a network (Ethernet) card of this type, say Y and read
716 the Ethernet-HOWTO, available from
717 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
720 To compile this driver as a module, choose M here: the module
721 will be called lance. This is recommended.
723 config NET_VENDOR_SMC
724 bool "Western Digital/SMC cards"
725 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
727 If you have a network (Ethernet) card belonging to this class, say Y
728 and read the Ethernet-HOWTO, available from
729 <http://www.tldp.org/docs.html#howto>.
731 Note that the answer to this question doesn't directly affect the
732 kernel: saying N will just cause the configurator to skip all
733 the questions about Western Digital cards. If you say Y, you will be
734 asked for your specific card in the following questions.
737 tristate "WD80*3 support"
738 depends on NET_VENDOR_SMC && ISA
741 If you have a network (Ethernet) card of this type, say Y and read
742 the Ethernet-HOWTO, available from
743 <http://www.tldp.org/docs.html#howto>.
745 To compile this driver as a module, choose M here and read
746 <file:Documentation/networking/net-modules.txt>. The module
750 tristate "SMC Ultra MCA support"
751 depends on NET_VENDOR_SMC && MCA
754 If you have a network (Ethernet) card of this type and are running
755 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
756 available from <http://www.tldp.org/docs.html#howto>.
758 To compile this driver as a module, choose M here and read
759 <file:Documentation/networking/net-modules.txt>. The module
760 will be called smc-mca.
763 tristate "SMC Ultra support"
764 depends on NET_VENDOR_SMC && ISA
767 If you have a network (Ethernet) card of this type, say Y and read
768 the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>.
771 Important: There have been many reports that, with some motherboards
772 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
773 such as some BusLogic models) causes corruption problems with many
774 operating systems. The Linux smc-ultra driver has a work-around for
775 this but keep it in mind if you have such a SCSI card and have
778 To compile this driver as a module, choose M here and read
779 <file:Documentation/networking/net-modules.txt>. The module
780 will be called smc-ultra.
783 tristate "SMC Ultra32 EISA support"
784 depends on NET_VENDOR_SMC && EISA
787 If you have a network (Ethernet) card of this type, say Y and read
788 the Ethernet-HOWTO, available from
789 <http://www.tldp.org/docs.html#howto>.
791 To compile this driver as a module, choose M here and read
792 <file:Documentation/networking/net-modules.txt>. The module
793 will be called smc-ultra32.
796 tristate "SMC 91C9x/91C1xxx support"
799 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH)
801 This is a driver for SMC's 91x series of Ethernet chipsets,
802 including the SMC91C94 and the SMC91C111. Say Y if you want it
803 compiled into the kernel, and read the file
804 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
805 available from <http://www.linuxdoc.org/docs.html#howto>.
807 This driver is also available as a module ( = code which can be
808 inserted in and removed from the running kernel whenever you want).
809 The module will be called smc91x. If you want to compile it as a
810 module, say M here and read <file:Documentation/modules.txt> as well
811 as <file:Documentation/networking/net-modules.txt>.
814 tristate "SMC 9194 support"
815 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
818 This is support for the SMC9xxx based Ethernet cards. Choose this
819 option if you have a DELL laptop with the docking station, or
820 another SMC9192/9194 based chipset. Say Y if you want it compiled
821 into the kernel, and read the file
822 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
823 available from <http://www.tldp.org/docs.html#howto>.
825 To compile this driver as a module, choose M here and read
826 <file:Documentation/networking/net-modules.txt>. The module
827 will be called smc9194.
830 tristate "DM9000 support"
831 depends on ARM && NET_ETHERNET
835 Support for DM9000 chipset.
837 To compile this driver as a module, choose M here and read
838 <file:Documentation/networking/net-modules.txt>. The module will be
841 config NET_VENDOR_RACAL
842 bool "Racal-Interlan (Micom) NI cards"
843 depends on NET_ETHERNET && ISA
845 If you have a network (Ethernet) card belonging to this class, such
846 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
847 available from <http://www.tldp.org/docs.html#howto>.
849 Note that the answer to this question doesn't directly affect the
850 kernel: saying N will just cause the configurator to skip all
851 the questions about NI cards. If you say Y, you will be asked for
852 your specific card in the following questions.
855 tristate "NI5010 support (EXPERIMENTAL)"
856 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
858 If you have a network (Ethernet) card of this type, say Y and read
859 the Ethernet-HOWTO, available from
860 <http://www.tldp.org/docs.html#howto>. Note that this is still
863 To compile this driver as a module, choose M here and read
864 <file:Documentation/networking/net-modules.txt>. The module
865 will be called ni5010.
868 tristate "NI5210 support"
869 depends on NET_VENDOR_RACAL && ISA
871 If you have a network (Ethernet) card of this type, say Y and read
872 the Ethernet-HOWTO, available from
873 <http://www.tldp.org/docs.html#howto>.
875 To compile this driver as a module, choose M here and read
876 <file:Documentation/networking/net-modules.txt>. The module
880 tristate "NI6510 support"
881 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
883 If you have a network (Ethernet) card of this type, say Y and read
884 the Ethernet-HOWTO, available from
885 <http://www.tldp.org/docs.html#howto>.
887 To compile this driver as a module, choose M here and read
888 <file:Documentation/networking/net-modules.txt>. The module
891 source "drivers/net/tulip/Kconfig"
894 tristate "AT1700/1720 support (EXPERIMENTAL)"
895 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
898 If you have a network (Ethernet) card of this type, say Y and read
899 the Ethernet-HOWTO, available from
900 <http://www.tldp.org/docs.html#howto>.
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 at1700.
907 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
908 depends on NET_ETHERNET && (ISA || EISA || MCA)
911 If you have a network (Ethernet) card of this type, say Y and read
912 the Ethernet-HOWTO, available from
913 <http://www.tldp.org/docs.html#howto> as well as
914 <file:drivers/net/depca.c>.
916 To compile this driver as a module, choose M here and read
917 <file:Documentation/networking/net-modules.txt>. The module
918 will be called depca.
921 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
922 depends on NET_ETHERNET && (ISA || EISA || PCI)
924 If you have a network (Ethernet) card of this type, say Y and read
925 the Ethernet-HOWTO, available from
926 <http://www.tldp.org/docs.html#howto>.
928 To compile this driver as a module, choose M here and read
929 <file:Documentation/networking/net-modules.txt>. The module
930 will be called hp100.
933 bool "Other ISA cards"
934 depends on NET_ETHERNET && ISA
936 If your network (Ethernet) card hasn't been mentioned yet and its
937 bus system (that's the way the cards talks to the other components
938 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
939 Make sure you know the name of your card. Read the Ethernet-HOWTO,
940 available from <http://www.tldp.org/docs.html#howto>.
944 Note that the answer to this question doesn't directly affect the
945 kernel: saying N will just cause the configurator to skip all
946 the remaining ISA network card questions. If you say Y, you will be
947 asked for your specific card in the following questions.
950 tristate "Cabletron E21xx support"
954 If you have a network (Ethernet) card of this type, say Y and read
955 the Ethernet-HOWTO, available from
956 <http://www.tldp.org/docs.html#howto>.
958 To compile this driver as a module, choose M here and read
959 <file:Documentation/networking/net-modules.txt>. The module
960 will be called e2100.
963 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
967 This driver supports the DE203, DE204 and DE205 network (Ethernet)
968 cards. If this is for you, say Y and read
969 <file:Documentation/networking/ewrk3.txt> in the kernel source as
970 well as the Ethernet-HOWTO, available from
971 <http://www.tldp.org/docs.html#howto>.
973 To compile this driver as a module, choose M here and read
974 <file:Documentation/networking/net-modules.txt>. The module
975 will be called ewrk3.
978 tristate "EtherExpress 16 support"
981 If you have an EtherExpress16 network (Ethernet) card, say Y and
982 read the Ethernet-HOWTO, available from
983 <http://www.tldp.org/docs.html#howto>. Note that the Intel
984 EtherExpress16 card used to be regarded as a very poor choice
985 because the driver was very unreliable. We now have a new driver
986 that should do better.
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 eexpress.
993 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
996 If you have a network (Ethernet) card of this type, say Y. This
997 driver supports intel i82595{FX,TX} based boards. Note however
998 that the EtherExpress PRO/100 Ethernet card has its own separate
999 driver. Please read the Ethernet-HOWTO, available from
1000 <http://www.tldp.org/docs.html#howto>.
1002 To compile this driver as a module, choose M here and read
1003 <file:Documentation/networking/net-modules.txt>. The module
1004 will be called eepro.
1007 tristate "HP PCLAN+ (27247B and 27252A) support"
1011 If you have a network (Ethernet) card of this type, say Y and read
1012 the Ethernet-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
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 hp-plus.
1020 tristate "HP PCLAN (27245 and other 27xxx series) 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
1033 tristate "LP486E on board Ethernet"
1036 Say Y here to support the 82596-based on-board Ethernet controller
1037 for the Panther motherboard, which is one of the two shipped in the
1038 Intel Professional Workstation.
1041 tristate "ICL EtherTeam 16i/32 support"
1044 If you have a network (Ethernet) card of this type, say Y and read
1045 the Ethernet-HOWTO, available from
1046 <http://www.tldp.org/docs.html#howto>.
1048 To compile this driver as a module, choose M here and read
1049 <file:Documentation/networking/net-modules.txt>. The module
1050 will be called eth16i.
1053 tristate "NE2000/NE1000 support"
1054 depends on NET_ISA || (Q40 && m) || M32R
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>. Many Ethernet cards
1060 without a specific driver are compatible with NE2000.
1062 If you have a PCI NE2000 card however, say N here and Y to "PCI
1063 NE2000 support", above. If you have a NE2000 card and are running on
1064 an MCA system (a bus system used on some IBM PS/2 computers and
1065 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1068 To compile this driver as a module, choose M here and read
1069 <file:Documentation/networking/net-modules.txt>. The module
1073 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1074 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1076 The Zenith Z-Note notebook computer has a built-in network
1077 (Ethernet) card, and this is the Linux driver for it. Note that the
1078 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1079 by this driver. Read the Ethernet-HOWTO, available from
1080 <http://www.tldp.org/docs.html#howto>.
1083 tristate "SEEQ8005 support (EXPERIMENTAL)"
1084 depends on NET_ISA && EXPERIMENTAL
1086 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1087 is for you, read the Ethernet-HOWTO, available from
1088 <http://www.tldp.org/docs.html#howto>.
1090 To compile this driver as a module, choose M here and read
1091 <file:Documentation/networking/net-modules.txt>. The module
1092 will be called seeq8005.
1095 tristate "SKnet MCA support"
1096 depends on NET_ETHERNET && MCA && BROKEN
1098 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1099 support" in order to use this driver. Supported cards are the SKnet
1100 Junior MC2 and the SKnet MC2(+). The driver automatically
1101 distinguishes between the two cards. Note that using multiple boards
1102 of different type hasn't been tested with this driver. Say Y if you
1103 have one of these Ethernet adapters.
1105 To compile this driver as a module, choose M here and read
1106 <file:Documentation/networking/net-modules.txt>. The module
1107 will be called sk_mca.
1110 tristate "NE/2 (ne2000 MCA version) support"
1111 depends on NET_ETHERNET && MCA_LEGACY
1114 If you have a network (Ethernet) card of this type, say Y and read
1115 the Ethernet-HOWTO, available from
1116 <http://www.tldp.org/docs.html#howto>.
1118 To compile this driver as a module, choose M here and read
1119 <file:Documentation/networking/net-modules.txt>. The module
1123 tristate "IBM LAN Adapter/A support"
1124 depends on NET_ETHERNET && MCA && MCA_LEGACY
1126 This is a Micro Channel Ethernet adapter. You need to set
1127 CONFIG_MCA to use this driver. It is both available as an in-kernel
1128 driver and as a module.
1130 To compile this driver as a module, choose M here and read
1131 <file:Documentation/networking/net-modules.txt>. The only
1132 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1133 will both support 16K and 32K memory windows, however a 32K window
1134 gives a better security against packet losses. Usage of multiple
1135 boards with this driver should be possible, but has not been tested
1136 up to now due to lack of hardware.
1139 tristate "IBM LAN Virtual Ethernet support"
1140 depends on NET_ETHERNET && PPC_PSERIES
1142 This driver supports virtual ethernet adapters on newer IBM iSeries
1143 and pSeries systems.
1145 To compile this driver as a module, choose M here and read
1146 <file:Documentation/networking/net-modules.txt>. The module will
1150 bool "IBM PPC4xx EMAC driver support"
1154 This driver supports the IBM PPC4xx EMAC family of on-chip
1155 Ethernet controllers.
1157 config IBM_EMAC_ERRMSG
1158 bool "Verbose error messages"
1159 depends on IBM_EMAC && BROKEN
1162 int "Number of receive buffers"
1164 default "128" if IBM_EMAC4
1168 int "Number of transmit buffers"
1170 default "128" if IBM_EMAC4
1173 config IBM_EMAC_FGAP
1178 config IBM_EMAC_SKBRES
1179 int "Skb reserve amount"
1184 bool "EISA, VLB, PCI and on board controllers"
1185 depends on NET_ETHERNET && (ISA || EISA || PCI)
1187 This is another class of network cards which attach directly to the
1188 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1189 available from <http://www.tldp.org/docs.html#howto>.
1191 Note that the answer to this question doesn't directly affect the
1192 kernel: saying N will just cause the configurator to skip all
1193 the questions about this class of network cards. If you say Y, you
1194 will be asked for your specific card in the following questions. If
1195 you are unsure, say Y.
1198 tristate "AMD PCnet32 PCI support"
1199 depends on NET_PCI && PCI
1203 If you have a PCnet32 or PCnetPCI based network (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 pcnet32.
1212 tristate "AMD 8111 (new PCI lance) support"
1213 depends on NET_PCI && PCI
1217 If you have an AMD 8111-based PCI lance ethernet card,
1218 answer Y here and read the Ethernet-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here and read
1222 <file:Documentation/networking/net-modules.txt>. The module
1223 will be called amd8111e.
1224 config AMD8111E_NAPI
1225 bool "Enable NAPI support"
1226 depends on AMD8111_ETH
1228 NAPI is a new driver API designed to reduce CPU and interrupt load
1229 when the driver is receiving lots of packets from the card. It is
1230 still somewhat experimental and thus not yet enabled by default.
1232 If your estimated Rx load is 10kpps or more, or if the card will be
1233 deployed on potentially unfriendly networks (e.g. in a firewall),
1236 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1241 config ADAPTEC_STARFIRE
1242 tristate "Adaptec Starfire/DuraLAN support"
1243 depends on NET_PCI && PCI
1247 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1248 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1249 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1252 To compile this driver as a module, choose M here: the module
1253 will be called starfire. This is recommended.
1255 config ADAPTEC_STARFIRE_NAPI
1256 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1257 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1259 NAPI is a new driver API designed to reduce CPU and interrupt load
1260 when the driver is receiving lots of packets from the card. It is
1261 still somewhat experimental and thus not yet enabled by default.
1263 If your estimated Rx load is 10kpps or more, or if the card will be
1264 deployed on potentially unfriendly networks (e.g. in a firewall),
1267 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1273 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1274 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1277 If you have a network (Ethernet) card of this type, say Y and read
1278 the Ethernet-HOWTO, available from
1279 <http://www.tldp.org/docs.html#howto>.
1281 To compile this driver as a module, choose M here and read
1282 <file:Documentation/networking/net-modules.txt>. The module
1283 will be called ac3200.
1286 tristate "Apricot Xen-II on board Ethernet"
1287 depends on NET_PCI && ISA
1289 If you have a network (Ethernet) controller of this type, say Y and
1290 read the Ethernet-HOWTO, available from
1291 <http://www.tldp.org/docs.html#howto>.
1293 To compile this driver as a module, choose M here and read
1294 <file:Documentation/networking/net-modules.txt>. The module will be
1298 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1299 depends on NET_PCI && PCI && EXPERIMENTAL
1302 If you have a network (Ethernet) controller of this type, say Y and
1303 read the Ethernet-HOWTO, available from
1304 <http://www.tldp.org/docs.html#howto>.
1306 To compile this driver as a module, choose M here and read
1307 <file:Documentation/networking/net-modules.txt>. The module will be
1311 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1312 depends on NET_PCI && PCI && EXPERIMENTAL
1314 If you have a network (Ethernet) controller of this type, say Y and
1315 read the Ethernet-HOWTO, available from
1316 <http://www.tldp.org/docs.html#howto>.
1318 To compile this driver as a module, choose M here and read
1319 <file:Documentation/networking/net-modules.txt>. The module will be
1324 tristate "CS89x0 support"
1325 depends on (NET_PCI && (ISA || ARCH_IXDP2X01)) || ARCH_PNX0105
1327 Support for CS89x0 chipset based Ethernet cards. If you have a
1328 network (Ethernet) card of this type, say Y and read the
1329 Ethernet-HOWTO, available from
1330 <http://www.tldp.org/docs.html#howto> as well as
1331 <file:Documentation/networking/cs89x0.txt>.
1333 To compile this driver as a module, choose M here and read
1334 <file:Documentation/networking/net-modules.txt>. The module will be
1338 tristate "TOSHIBA TC35815 Ethernet support"
1339 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1342 tristate "Digi Intl. RightSwitch SE-X support"
1343 depends on NET_PCI && (PCI || EISA)
1345 This is support for the Digi International RightSwitch series of
1346 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1347 models. If you have a network card of this type, say Y and read the
1348 Ethernet-HOWTO, available from
1349 <http://www.tldp.org/docs.html#howto>. More specific
1350 information is contained in <file:Documentation/networking/dgrs.txt>.
1352 To compile this driver as a module, choose M here and read
1353 <file:Documentation/networking/net-modules.txt>. The module
1354 will be called dgrs.
1357 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1358 depends on NET_PCI && PCI
1361 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1362 card, say Y and read the Ethernet-HOWTO, available from
1363 <http://www.tldp.org/docs.html#howto>.
1365 To compile this driver as a module, choose M here and read
1366 <file:Documentation/networking/net-modules.txt>. The module
1367 will be called eepro100.
1371 tristate "Intel(R) PRO/100+ support"
1372 depends on NET_PCI && PCI
1375 This driver supports Intel(R) PRO/100 family of adapters.
1376 To verify that your adapter is supported, find the board ID number
1377 on the adapter. Look for a label that has a barcode and a number
1378 in the format 123456-001 (six digits hyphen three digits).
1380 Use the above information and the Adapter & Driver ID Guide at:
1382 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1384 to identify the adapter.
1386 For the latest Intel PRO/100 network driver for Linux, see:
1388 <http://appsr.intel.com/scripts-df/support_intel.asp>
1390 More specific information on configuring the driver is in
1391 <file:Documentation/networking/e100.txt>.
1393 To compile this driver as a module, choose M here and read
1394 <file:Documentation/networking/net-modules.txt>. The module
1395 will be called e100.
1398 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1399 depends on NET_PCI && EISA && EXPERIMENTAL
1402 If you have a network (Ethernet) card of this type, say Y and read
1403 the Ethernet-HOWTO, available from
1404 <http://www.tldp.org/docs.html#howto>.
1406 To compile this driver as a module, choose M here and read
1407 <file:Documentation/networking/net-modules.txt>. The module
1408 will be called lne390.
1411 tristate "Myson MTD-8xx PCI Ethernet support"
1412 depends on NET_PCI && PCI
1416 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1417 cards. Specifications and data at
1418 <http://www.myson.com.hk/mtd/datasheet/>.
1421 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1422 depends on NET_PCI && PCI
1425 This driver is for the National Semiconductor DP83810 series,
1426 which is used in cards from PureData, NetGear, Linksys
1427 and others, including the 83815 chip.
1428 More specific information and updates are available from
1429 <http://www.scyld.com/network/natsemi.html>.
1432 tristate "PCI NE2000 and clones support (see help)"
1433 depends on NET_PCI && PCI
1436 This driver is for NE2000 compatible PCI cards. It will not work
1437 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1438 support" below). If you have a PCI NE2000 network (Ethernet) card,
1439 say Y and read the Ethernet-HOWTO, available from
1440 <http://www.tldp.org/docs.html#howto>.
1442 This driver also works for the following NE2000 clone cards:
1443 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1444 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1445 Holtek HT80232 Holtek HT80229
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 ne2k-pci.
1452 tristate "Novell/Eagle/Microdyne NE3210 EISA 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>. Note that this driver
1459 will NOT WORK for NE3200 cards as they are completely different.
1461 To compile this driver as a module, choose M here and read
1462 <file:Documentation/networking/net-modules.txt>. The module
1463 will be called ne3210.
1466 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1467 depends on NET_PCI && EISA && EXPERIMENTAL
1470 If you have a network (Ethernet) card of this type, say Y and read
1471 the Ethernet-HOWTO, available from
1472 <http://www.tldp.org/docs.html#howto>.
1474 To compile this driver as a module, choose M here and read
1475 <file:Documentation/networking/net-modules.txt>. The module
1476 will be called es3210.
1479 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1480 depends on NET_PCI && PCI && EXPERIMENTAL
1484 This is a driver for the Fast Ethernet PCI network cards based on
1485 the RTL8139C+ chips. If you have one of those, say Y and read
1486 the Ethernet-HOWTO, available from
1487 <http://www.tldp.org/docs.html#howto>.
1489 To compile this driver as a module, choose M here: the module
1490 will be called 8139cp. This is recommended.
1493 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1494 depends on NET_PCI && PCI
1498 This is a driver for the Fast Ethernet PCI network cards based on
1499 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1500 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1502 To compile this driver as a module, choose M here: the module
1503 will be called 8139too. This is recommended.
1506 bool "Use PIO instead of MMIO"
1510 This instructs the driver to use programmed I/O ports (PIO) instead
1511 of PCI shared memory (MMIO). This can possibly solve some problems
1512 in case your mainboard has memory consistency issues. If unsure,
1515 config 8139TOO_TUNE_TWISTER
1516 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1519 This implements a function which might come in handy in case you
1520 are using low quality on long cabling. It is required for RealTek
1521 RTL-8139 revision K boards, and totally unused otherwise. It tries
1522 to match the transceiver to the cable characteristics. This is
1523 experimental since hardly documented by the manufacturer.
1527 bool "Support for older RTL-8129/8130 boards"
1530 This enables support for the older and uncommon RTL-8129 and
1531 RTL-8130 chips, which support MII via an external transceiver,
1532 instead of an internal one. Disabling this option will save some
1533 memory by making the code size smaller. If unsure, say Y.
1535 config 8139_OLD_RX_RESET
1536 bool "Use older RX-reset method"
1539 The 8139too driver was recently updated to contain a more rapid
1540 reset sequence, in the face of severe receive errors. This "new"
1541 RX-reset method should be adequate for all boards. But if you
1542 experience problems, you can enable this option to restore the
1543 old RX-reset behavior. If unsure, say N.
1546 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1547 depends on NET_PCI && PCI
1551 This is a driver for the Fast Ethernet PCI network cards based on
1552 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1553 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1554 read the Ethernet-HOWTO, available at
1555 <http://www.tldp.org/docs.html#howto>. Please read
1556 <file:Documentation/networking/sis900.txt> and comments at the
1557 beginning of <file:drivers/net/sis900.c> for more information.
1559 This driver also supports AMD 79C901 HomePNA so that you can use
1560 your phone line as a network cable.
1562 To compile this driver as a module, choose M here: the module
1563 will be called sis900. This is recommended.
1566 tristate "SMC EtherPower II"
1567 depends on NET_PCI && PCI
1571 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1572 which is based on the SMC83c17x (EPIC/100).
1573 More specific information and updates are available from
1574 <http://www.scyld.com/network/epic100.html>.
1577 tristate "Sundance Alta support"
1578 depends on NET_PCI && PCI
1582 This driver is for the Sundance "Alta" chip.
1583 More specific information and updates are available from
1584 <http://www.scyld.com/network/sundance.html>.
1586 config SUNDANCE_MMIO
1587 bool "Use MMIO instead of PIO"
1590 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1591 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1592 is known to solve bugs on certain chips.
1597 tristate "TI ThunderLAN support"
1598 depends on NET_PCI && (PCI || EISA) && !64BIT
1600 If you have a PCI Ethernet network card based on the ThunderLAN chip
1601 which is supported by this driver, say Y and read the
1602 Ethernet-HOWTO, available from
1603 <http://www.tldp.org/docs.html#howto>.
1605 Devices currently supported by this driver are Compaq Netelligent,
1606 Compaq NetFlex and Olicom cards. Please read the file
1607 <file:Documentation/networking/tlan.txt> for more details.
1609 To compile this driver as a module, choose M here and read
1610 <file:Documentation/networking/net-modules.txt>. The module
1611 will be called tlan.
1613 Please email feedback to <torben.mathiasen@compaq.com>.
1616 tristate "VIA Rhine support"
1617 depends on NET_PCI && PCI
1621 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1622 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1623 Ethernet functions can also be found integrated on South Bridges
1626 To compile this driver as a module, choose M here. The module
1627 will be called via-rhine.
1629 config VIA_RHINE_MMIO
1630 bool "Use MMIO instead of PIO"
1631 depends on VIA_RHINE
1633 This instructs the driver to use PCI shared memory (MMIO) instead of
1634 programmed I/O ports (PIO). Enabling this gives an improvement in
1635 processing time in parts of the driver.
1640 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1641 depends on NET_PCI && EXPERIMENTAL && MIPS
1643 The SAA9730 is a combined multimedia and peripheral controller used
1644 in thin clients, Internet access terminals, and diskless
1646 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1649 bool "Pocket and portable adapters"
1650 depends on NET_ETHERNET && ISA
1652 Cute little network (Ethernet) devices which attach to the parallel
1653 port ("pocket adapters"), commonly used with laptops. If you have
1654 one of those, say Y and read the Ethernet-HOWTO, available from
1655 <http://www.tldp.org/docs.html#howto>.
1657 If you want to plug a network (or some other) card into the PCMCIA
1658 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1659 credit card size extension cards used by all modern laptops), you
1660 need the pcmcia-cs package (location contained in the file
1661 <file:Documentation/Changes>) and you can say N here.
1663 Laptop users should read the Linux Laptop home page at
1664 <http://www.linux-on-laptops.com/> or
1665 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1667 Note that the answer to this question doesn't directly affect the
1668 kernel: saying N will just cause the configurator to skip all
1669 the questions about this class of network devices. If you say Y, you
1670 will be asked for your specific device in the following questions.
1673 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1674 depends on NET_POCKET && ISA && X86
1677 This is a network (Ethernet) device which attaches to your parallel
1678 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1679 available from <http://www.tldp.org/docs.html#howto>, if you
1680 want to use this. If you intend to use this driver, you should have
1681 said N to the "Parallel printer support", because the two drivers
1682 don't like each other.
1684 To compile this driver as a module, choose M here: the module
1688 tristate "D-Link DE600 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 de600.
1703 tristate "D-Link DE620 pocket adapter support"
1704 depends on NET_POCKET && ISA
1706 This is a network (Ethernet) device which attaches to your parallel
1707 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1708 Ethernet-HOWTO, available from
1709 <http://www.tldp.org/docs.html#howto>, if you want to use
1710 this. It is possible to have several devices share a single parallel
1711 port and it is safe to compile the corresponding drivers into the
1714 To compile this driver as a module, choose M here: the module
1715 will be called de620.
1718 tristate "SGI Seeq ethernet controller support"
1719 depends on NET_ETHERNET && SGI_IP22
1721 Say Y here if you have an Seeq based Ethernet network card. This is
1722 used in many Silicon Graphics machines.
1725 tristate "DEC LANCE ethernet controller support"
1726 depends on NET_ETHERNET && MACH_DECSTATION
1729 This driver is for the series of Ethernet controllers produced by
1730 DEC (now Compaq) based on the AMD Lance chipset, including the
1731 DEPCA series. (This chipset is better known via the NE2100 cards.)
1734 bool "Motorola 68360 ethernet controller"
1737 Say Y here if you want to use the built-in ethernet controller of
1738 the Motorola 68360 processor.
1741 bool "FEC ethernet controller (of ColdFire 5272)"
1742 depends on M5272 || M5282
1744 Say Y here if you want to use the built-in 10/100 Fast ethernet
1745 controller on the Motorola ColdFire 5272 processor.
1748 tristate "NE2000 compatible support for H8/300"
1749 depends on H8300 && NET_ETHERNET
1751 Say Y here if you want to use the NE2000 compatible
1752 controller on the Renesas H8/300 processor.
1754 source "drivers/net/fec_8xx/Kconfig"
1762 menu "Ethernet (1000 Mbit)"
1766 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1769 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1770 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1771 adapter. The driver allows for using the Jumbo Frame option (9000
1772 bytes/frame) however it requires that your switches can handle this
1773 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1776 To compile this driver as a module, choose M here: the
1777 module will be called acenic.
1779 config ACENIC_OMIT_TIGON_I
1780 bool "Omit support for old Tigon I based AceNICs"
1783 Say Y here if you only have Tigon II based AceNICs and want to leave
1784 out support for the older Tigon I based cards which are no longer
1785 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1786 version)). This will reduce the size of the driver object by
1787 app. 100KB. If you are not sure whether your card is a Tigon I or a
1788 Tigon II, say N here.
1790 The safe and default value for this is N.
1793 tristate "D-Link DL2000-based Gigabit Ethernet support"
1797 This driver supports D-Link 2000-based gigabit ethernet cards, which
1799 D-Link DGE-550T Gigabit Ethernet Adapter.
1800 D-Link DL2000-based Gigabit Ethernet Adapter.
1802 To compile this driver as a module, choose M here: the
1803 module will be called dl2k.
1806 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1809 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1810 adapters. For more information on how to identify your adapter, go
1811 to the Adapter & Driver ID Guide at:
1813 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1815 For general information and support, go to the Intel support
1818 <http://support.intel.com>
1820 More specific information on configuring the driver is in
1821 <file:Documentation/networking/e1000.txt>.
1823 To compile this driver as a module, choose M here and read
1824 <file:Documentation/networking/net-modules.txt>. The module
1825 will be called e1000.
1828 bool "Use Rx Polling (NAPI)"
1831 NAPI is a new driver API designed to reduce CPU and interrupt load
1832 when the driver is receiving lots of packets from the card. It is
1833 still somewhat experimental and thus not yet enabled by default.
1835 If your estimated Rx load is 10kpps or more, or if the card will be
1836 deployed on potentially unfriendly networks (e.g. in a firewall),
1839 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1845 tristate "MyriCOM Gigabit Ethernet support"
1848 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1850 To compile this driver as a module, choose M here: the module
1851 will be called myri_sbus. This is recommended.
1854 tristate "National Semiconduct DP83820 support"
1857 This is a driver for the National Semiconductor DP83820 series
1858 of gigabit ethernet MACs. Cards using this chipset include
1859 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1860 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1864 tristate "Packet Engines Hamachi GNIC-II support"
1868 If you have a Gigabit Ethernet card of this type, say Y and read
1869 the Ethernet-HOWTO, available from
1870 <http://www.tldp.org/docs.html#howto>.
1872 To compile this driver as a module, choose M here and read
1873 <file:Documentation/networking/net-modules.txt>. The module will be
1877 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1878 depends on PCI && EXPERIMENTAL
1881 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1882 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1883 used by the Beowulf Linux cluster project. See
1884 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1885 information about this driver in particular and Beowulf in general.
1887 To compile this driver as a module, choose M here: the module
1888 will be called yellowfin. This is recommended.
1891 tristate "Realtek 8169 gigabit ethernet support"
1895 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1897 To compile this driver as a module, choose M here: the module
1898 will be called r8169. This is recommended.
1901 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1902 depends on R8169 && EXPERIMENTAL
1904 NAPI is a new driver API designed to reduce CPU and interrupt load
1905 when the driver is receiving lots of packets from the card. It is
1906 still somewhat experimental and thus not yet enabled by default.
1908 If your estimated Rx load is 10kpps or more, or if the card will be
1909 deployed on potentially unfriendly networks (e.g. in a firewall),
1912 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1919 depends on R8169 && VLAN_8021Q
1921 Say Y here for the r8169 driver to support the functions required
1922 by the kernel 802.1Q code.
1927 tristate "SiS190/SiS191 gigabit ethernet support"
1932 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1933 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1934 appear in lan on motherboard designs which are based on SiS 965
1935 and SiS 966 south bridge.
1937 To compile this driver as a module, choose M here: the module
1938 will be called sis190. This is recommended.
1941 tristate "New SysKonnect GigaEthernet support (EXPERIMENTAL)"
1942 depends on PCI && EXPERIMENTAL
1945 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1946 and related Gigabit Ethernet adapters. It is a new smaller driver
1947 driver with better performance and more complete ethtool support.
1949 It does not support the link failover and network management
1950 features that "portable" vendor supplied sk98lin driver does.
1953 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
1956 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1957 compliant Gigabit Ethernet Adapter. The following adapters are supported
1959 - 3Com 3C940 Gigabit LOM Ethernet Adapter
1960 - 3Com 3C941 Gigabit LOM Ethernet Adapter
1961 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
1962 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
1963 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
1964 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
1965 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
1966 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
1967 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
1968 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
1969 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
1970 - DGE-530T Gigabit Ethernet Adapter
1971 - EG1032 v2 Instant Gigabit Network Adapter
1972 - EG1064 v2 Instant Gigabit Network Adapter
1973 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
1974 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
1975 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
1976 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
1977 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
1978 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
1979 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
1980 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
1981 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
1982 - Marvell RDK-8001 Adapter
1983 - Marvell RDK-8002 Adapter
1984 - Marvell RDK-8003 Adapter
1985 - Marvell RDK-8004 Adapter
1986 - Marvell RDK-8006 Adapter
1987 - Marvell RDK-8007 Adapter
1988 - Marvell RDK-8008 Adapter
1989 - Marvell RDK-8009 Adapter
1990 - Marvell RDK-8010 Adapter
1991 - Marvell RDK-8011 Adapter
1992 - Marvell RDK-8012 Adapter
1993 - Marvell RDK-8052 Adapter
1994 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
1995 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
1996 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
1997 - SK-9521 10/100/1000Base-T Adapter
1998 - SK-9521 V2.0 10/100/1000Base-T Adapter
1999 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2000 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2001 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2002 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2003 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2004 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2005 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2006 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2007 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2008 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2009 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2010 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2011 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2012 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2013 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2014 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2015 - SMC EZ Card 1000 (SMC9452TXV.2)
2017 The adapters support Jumbo Frames.
2018 The dual link adapters support link-failover and dual port features.
2019 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2020 the scatter-gather functionality with sendfile(). Please refer to
2021 <file:Documentation/networking/sk98lin.txt> for more information about
2022 optional driver parameters.
2023 Questions concerning this driver may be addressed to:
2024 <linux@syskonnect.de>
2026 If you want to compile this driver as a module ( = code which can be
2027 inserted in and removed from the running kernel whenever you want),
2028 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2029 be called sk98lin. This is recommended.
2032 tristate "VIA Velocity support"
2033 depends on NET_PCI && PCI
2038 If you have a VIA "Velocity" based network card say Y here.
2040 To compile this driver as a module, choose M here. The module
2041 will be called via-velocity.
2044 tristate "Broadcom Tigon3 support"
2047 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2049 To compile this driver as a module, choose M here: the module
2050 will be called tg3. This is recommended.
2053 tristate "Broadcom NetXtremeII support"
2056 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2058 To compile this driver as a module, choose M here: the module
2059 will be called bnx2. This is recommended.
2062 tristate "Gianfar Ethernet"
2063 depends on 85xx || 83xx
2065 This driver supports the Gigabit TSEC on the MPC85xx
2066 family of chips, and the FEC on the 8540
2073 tristate "MV-643XX Ethernet support"
2074 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
2076 This driver supports the gigabit Ethernet on the Marvell MV643XX
2077 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2078 Pegasos II, amongst other PPC and MIPS boards.
2080 config MV643XX_ETH_0
2081 bool "MV-643XX Port 0"
2082 depends on MV643XX_ETH
2084 This enables support for Port 0 of the Marvell MV643XX Gigabit
2087 config MV643XX_ETH_1
2088 bool "MV-643XX Port 1"
2089 depends on MV643XX_ETH
2091 This enables support for Port 1 of the Marvell MV643XX Gigabit
2094 config MV643XX_ETH_2
2095 bool "MV-643XX Port 2"
2096 depends on MV643XX_ETH
2098 This enables support for Port 2 of the Marvell MV643XX Gigabit
2104 # 10 Gigabit Ethernet
2107 menu "Ethernet (10000 Mbit)"
2111 tristate "Chelsio 10Gb Ethernet support"
2114 This driver supports Chelsio N110 and N210 models 10Gb Ethernet
2115 cards. More information about adapter features and performance
2116 tuning is in <file:Documentation/networking/cxgb.txt>.
2118 For general information about Chelsio and our products, visit
2119 our website at <http://www.chelsio.com>.
2121 For customer support, please visit our customer support page at
2122 <http://www.chelsio.com/support.htm>.
2124 Please send feedback to <linux-bugs@chelsio.com>.
2126 To compile this driver as a module, choose M here: the module
2127 will be called cxgb.
2130 tristate "Intel(R) PRO/10GbE support"
2133 This driver supports Intel(R) PRO/10GbE family of
2134 adapters. For more information on how to identify your adapter, go
2135 to the Adapter & Driver ID Guide at:
2137 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2139 For general information and support, go to the Intel support
2142 <http://support.intel.com>
2144 More specific information on configuring the driver is in
2145 <file:Documentation/networking/ixgb.txt>.
2147 To compile this driver as a module, choose M here and read
2148 <file:Documentation/networking/net-modules.txt>. The module
2149 will be called ixgb.
2152 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2153 depends on IXGB && EXPERIMENTAL
2155 NAPI is a new driver API designed to reduce CPU and interrupt load
2156 when the driver is receiving lots of packets from the card. It is
2157 still somewhat experimental and thus not yet enabled by default.
2159 If your estimated Rx load is 10kpps or more, or if the card will be
2160 deployed on potentially unfriendly networks (e.g. in a firewall),
2163 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2169 tristate "S2IO 10Gbe XFrame NIC"
2172 This driver supports the 10Gbe XFrame NIC of S2IO.
2173 For help regarding driver compilation, installation and
2174 tuning please look into ~/drivers/net/s2io/README.txt.
2177 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2178 depends on S2IO && EXPERIMENTAL
2180 NAPI is a new driver API designed to reduce CPU and interrupt load
2181 when the driver is receiving lots of packets from the card. It is
2182 still somewhat experimental and thus not yet enabled by default.
2184 If your estimated Rx load is 10kpps or more, or if the card will be
2185 deployed on potentially unfriendly networks (e.g. in a firewall),
2188 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2194 bool "Use 2 Buffer Mode on Rx side."
2197 On enabling the 2 buffer mode, the received frame will be
2198 split into 2 parts before being DMA'ed to the hosts memory.
2199 The parts are the ethernet header and ethernet payload.
2200 This is useful on systems where DMA'ing to to unaligned
2201 physical memory loactions comes with a heavy price.
2202 If not sure please say N.
2207 source "drivers/net/tokenring/Kconfig"
2209 source "drivers/net/wireless/Kconfig"
2211 source "drivers/net/pcmcia/Kconfig"
2214 source "drivers/net/wan/Kconfig"
2216 source "drivers/atm/Kconfig"
2218 source "drivers/s390/net/Kconfig"
2221 tristate "iSeries Virtual Ethernet driver support"
2222 depends on PPC_ISERIES
2225 bool "FDDI driver support"
2226 depends on (PCI || EISA)
2228 Fiber Distributed Data Interface is a high speed local area network
2229 design; essentially a replacement for high speed Ethernet. FDDI can
2230 run over copper or fiber. If you are connected to such a network and
2231 want a driver for the FDDI card in your computer, say Y here (and
2232 then also Y to the driver for your FDDI card, below). Most people
2236 tristate "Digital DEFEA and DEFPA adapter support"
2237 depends on FDDI && (PCI || EISA)
2239 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2240 (DEFPA) controllers which can connect you to a local FDDI network.
2243 tristate "SysKonnect FDDI PCI support"
2244 depends on FDDI && PCI
2246 Say Y here if you have a SysKonnect FDDI PCI adapter.
2247 The following adapters are supported by this driver:
2248 - SK-5521 (SK-NET FDDI-UP)
2249 - SK-5522 (SK-NET FDDI-UP DAS)
2250 - SK-5541 (SK-NET FDDI-FP)
2251 - SK-5543 (SK-NET FDDI-LP)
2252 - SK-5544 (SK-NET FDDI-LP DAS)
2253 - SK-5821 (SK-NET FDDI-UP64)
2254 - SK-5822 (SK-NET FDDI-UP64 DAS)
2255 - SK-5841 (SK-NET FDDI-FP64)
2256 - SK-5843 (SK-NET FDDI-LP64)
2257 - SK-5844 (SK-NET FDDI-LP64 DAS)
2258 - Netelligent 100 FDDI DAS Fibre SC
2259 - Netelligent 100 FDDI SAS Fibre SC
2260 - Netelligent 100 FDDI DAS UTP
2261 - Netelligent 100 FDDI SAS UTP
2262 - Netelligent 100 FDDI SAS Fibre MIC
2264 Read <file:Documentation/networking/skfp.txt> for information about
2267 Questions concerning this driver can be addressed to:
2268 <linux@syskonnect.de>
2270 To compile this driver as a module, choose M here: the module
2271 will be called skfp. This is recommended.
2274 bool "HIPPI driver support (EXPERIMENTAL)"
2275 depends on EXPERIMENTAL && INET && PCI
2277 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2278 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2279 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2280 single-mode). HIPPI networks are commonly used for clusters and to
2281 connect to super computers. If you are connected to a HIPPI network
2282 and have a HIPPI network card in your computer that you want to use
2283 under Linux, say Y here (you must also remember to enable the driver
2284 for your HIPPI card below). Most people will say N here.
2287 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2288 depends on HIPPI && PCI
2290 Say Y here if this is your PCI HIPPI network card.
2292 To compile this driver as a module, choose M here: the module
2293 will be called rrunner. If unsure, say N.
2295 config ROADRUNNER_LARGE_RINGS
2296 bool "Use large TX/RX rings (EXPERIMENTAL)"
2297 depends on ROADRUNNER
2299 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2300 of additional memory to allow for fastest operation, both for
2301 transmitting and receiving. This memory cannot be used by any other
2302 kernel code or by user space programs. Say Y here only if you have
2306 tristate "PLIP (parallel port) support"
2309 PLIP (Parallel Line Internet Protocol) is used to create a
2310 reasonably fast mini network consisting of two (or, rarely, more)
2311 local machines. A PLIP link from a Linux box is a popular means to
2312 install a Linux distribution on a machine which doesn't have a
2313 CD-ROM drive (a minimal system has to be transferred with floppies
2314 first). The kernels on both machines need to have this PLIP option
2315 enabled for this to work.
2317 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2318 ports (the connectors at the computers with 25 holes) are connected
2319 with "null printer" or "Turbo Laplink" cables which can transmit 4
2320 bits at a time (mode 0) or with special PLIP cables, to be used on
2321 bidirectional parallel ports only, which can transmit 8 bits at a
2322 time (mode 1); you can find the wiring of these cables in
2323 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2324 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2325 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2326 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2327 and winsock or NCSA's telnet.
2329 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2330 as the NET-3-HOWTO, both available from
2331 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2332 protocol has been changed and this PLIP driver won't work together
2333 with the PLIP support in Linux versions 1.0.x. This option enlarges
2334 your kernel by about 8 KB.
2336 To compile this driver as a module, choose M here and read
2337 <file:Documentation/networking/net-modules.txt>. The module will be
2338 called plip. If unsure, say Y or M, in case you buy a laptop
2342 tristate "PPP (point-to-point protocol) support"
2344 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2345 the same purpose: sending Internet traffic over telephone (and other
2346 serial) lines. Ask your access provider if they support it, because
2347 otherwise you can't use it; most Internet access providers these
2348 days support PPP rather than SLIP.
2350 To use PPP, you need an additional program called pppd as described
2351 in the PPP-HOWTO, available at
2352 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2353 the version of pppd recommended in <file:Documentation/Changes>.
2354 The PPP option enlarges your kernel by about 16 KB.
2356 There are actually two versions of PPP: the traditional PPP for
2357 asynchronous lines, such as regular analog phone lines, and
2358 synchronous PPP which can be used over digital ISDN lines for
2359 example. If you want to use PPP over phone lines or other
2360 asynchronous serial lines, you need to say Y (or M) here and also to
2361 the next option, "PPP support for async serial ports". For PPP over
2362 synchronous lines, you should say Y (or M) here and to "Support
2363 synchronous PPP", below.
2365 If you said Y to "Version information on all symbols" above, then
2366 you cannot compile the PPP driver into the kernel; you can then only
2367 compile it as a module. To compile this driver as a module, choose M
2368 here and read <file:Documentation/networking/net-modules.txt>.
2369 The module will be called ppp_generic.
2371 config PPP_MULTILINK
2372 bool "PPP multilink support (EXPERIMENTAL)"
2373 depends on PPP && EXPERIMENTAL
2375 PPP multilink is a protocol (defined in RFC 1990) which allows you
2376 to combine several (logical or physical) lines into one logical PPP
2377 connection, so that you can utilize your full bandwidth.
2379 This has to be supported at the other end as well and you need a
2380 version of the pppd daemon which understands the multilink protocol.
2385 bool "PPP filtering"
2388 Say Y here if you want to be able to filter the packets passing over
2389 PPP interfaces. This allows you to control which packets count as
2390 activity (i.e. which packets will reset the idle timer or bring up
2391 a demand-dialled link) and which packets are to be dropped entirely.
2392 You need to say Y here if you wish to use the pass-filter and
2393 active-filter options to pppd.
2398 tristate "PPP support for async serial ports"
2402 Say Y (or M) here if you want to be able to use PPP over standard
2403 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2404 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2407 To compile this driver as a module, choose M here.
2412 tristate "PPP support for sync tty ports"
2415 Say Y (or M) here if you want to be able to use PPP over synchronous
2416 (HDLC) tty devices, such as the SyncLink adapter. These devices
2417 are often used for high-speed leased lines like T1/E1.
2419 To compile this driver as a module, choose M here.
2422 tristate "PPP Deflate compression"
2427 Support for the Deflate compression method for PPP, which uses the
2428 Deflate algorithm (the same algorithm that gzip uses) to compress
2429 each PPP packet before it is sent over the wire. The machine at the
2430 other end of the PPP link (usually your ISP) has to support the
2431 Deflate compression method as well for this to be useful. Even if
2432 they don't support it, it is safe to say Y here.
2434 To compile this driver as a module, choose M here.
2437 tristate "PPP BSD-Compress compression"
2440 Support for the BSD-Compress compression method for PPP, which uses
2441 the LZW compression method to compress each PPP packet before it is
2442 sent over the wire. The machine at the other end of the PPP link
2443 (usually your ISP) has to support the BSD-Compress compression
2444 method as well for this to be useful. Even if they don't support it,
2445 it is safe to say Y here.
2447 The PPP Deflate compression method ("PPP Deflate compression",
2448 above) is preferable to BSD-Compress, because it compresses better
2451 Note that the BSD compression code will always be compiled as a
2452 module; it is called bsd_comp and will show up in the directory
2453 modules once you have said "make modules". If unsure, say N.
2456 tristate "PPP over Ethernet (EXPERIMENTAL)"
2457 depends on EXPERIMENTAL && PPP
2459 Support for PPP over Ethernet.
2461 This driver requires the latest version of pppd from the CVS
2462 repository at cvs.samba.org. Alternatively, see the
2463 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2464 which contains instruction on how to use this driver (under
2465 the heading "Kernel mode PPPoE").
2468 tristate "PPP over ATM"
2469 depends on ATM && PPP
2471 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2472 This implementation does not yet comply with section 8 of RFC2364,
2473 which can lead to bad results if the ATM peer loses state and
2474 changes its encapsulation unilaterally.
2477 tristate "SLIP (serial line) support"
2479 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2480 connect to your Internet service provider or to connect to some
2481 other local Unix box or if you want to configure your Linux box as a
2482 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2483 Internet Protocol) is a protocol used to send Internet traffic over
2484 serial connections such as telephone lines or null modem cables;
2485 nowadays, the protocol PPP is more commonly used for this same
2488 Normally, your access provider has to support SLIP in order for you
2489 to be able to use it, but there is now a SLIP emulator called SLiRP
2490 around (available from
2491 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2492 allows you to use SLIP over a regular dial up shell connection. If
2493 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2494 NET-3-HOWTO, available from
2495 <http://www.tldp.org/docs.html#howto>, explains how to
2496 configure SLIP. Note that you don't need this option if you just
2497 want to run term (term is a program which gives you almost full
2498 Internet connectivity if you have a regular dial up shell account on
2499 some Internet connected Unix computer. Read
2500 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2501 support will enlarge your kernel by about 4 KB. If unsure, say N.
2503 To compile this driver as a module, choose M here and read
2504 <file:Documentation/networking/net-modules.txt>. The module will be
2507 config SLIP_COMPRESSED
2508 bool "CSLIP compressed headers"
2511 This protocol is faster than SLIP because it uses compression on the
2512 TCP/IP headers (not on the data itself), but it has to be supported
2513 on both ends. Ask your access provider if you are not sure and
2514 answer Y, just in case. You will still be able to use plain SLIP. If
2515 you plan to use SLiRP, the SLIP emulator (available from
2516 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2517 allows you to use SLIP over a regular dial up shell connection, you
2518 definitely want to say Y here. The NET-3-HOWTO, available from
2519 <http://www.tldp.org/docs.html#howto>, explains how to configure
2520 CSLIP. This won't enlarge your kernel.
2523 bool "Keepalive and linefill"
2526 Adds additional capabilities to the SLIP driver to support the
2527 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2530 config SLIP_MODE_SLIP6
2531 bool "Six bit SLIP encapsulation"
2534 Just occasionally you may need to run IP over hostile serial
2535 networks that don't pass all control characters or are only seven
2536 bit. Saying Y here adds an extra mode you can use with SLIP:
2537 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2538 the serial device. Naturally, this has to be supported at the other
2539 end of the link as well. It's good enough, for example, to run IP
2540 over the async ports of a Camtec JNT Pad. If unsure, say N.
2543 bool "Fibre Channel driver support"
2544 depends on SCSI && PCI
2546 Fibre Channel is a high speed serial protocol mainly used to connect
2547 large storage devices to the computer; it is compatible with and
2548 intended to replace SCSI.
2550 If you intend to use Fibre Channel, you need to have a Fibre channel
2551 adaptor card in your computer; say Y here and to the driver for your
2552 adaptor below. You also should have said Y to "SCSI support" and
2553 "SCSI generic support".
2556 tristate "Traffic Shaper (EXPERIMENTAL)"
2557 depends on EXPERIMENTAL
2559 The traffic shaper is a virtual network device that allows you to
2560 limit the rate of outgoing data flow over some other network device.
2561 The traffic that you want to slow down can then be routed through
2562 these virtual devices. See
2563 <file:Documentation/networking/shaper.txt> for more information.
2565 An alternative to this traffic shaper is the experimental
2566 Class-Based Queueing (CBQ) scheduling support which you get if you
2567 say Y to "QoS and/or fair queueing" above.
2569 To set up and configure shaper devices, you need the shapecfg
2570 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2573 To compile this driver as a module, choose M here: the module
2574 will be called shaper. If unsure, say N.
2577 tristate "Network console logging support (EXPERIMENTAL)"
2578 depends on EXPERIMENTAL
2580 If you want to log kernel messages over the network, enable this.
2581 See <file:Documentation/networking/netconsole.txt> for details.
2589 bool "Netpoll support for trapping incoming packets"
2594 bool "Netpoll traffic trapping"
2598 config NET_POLL_CONTROLLER