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"
48 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
49 Channels together. This is called 'Etherchannel' by Cisco,
50 'Trunking' by Sun, and 'Bonding' in Linux.
52 If you have two Ethernet connections to some other computer, you can
53 make them behave like one double speed connection using this driver.
54 Naturally, this has to be supported at the other end as well, either
55 with a similar Bonding Linux driver, a Cisco 5500 switch or a
56 SunTrunking SunSoft driver.
58 This is similar to the EQL driver, but it merges Ethernet segments
59 instead of serial lines.
61 To compile this driver as a module, choose M here: the module
62 will be called bonding.
65 tristate "EQL (serial line load balancing) support"
68 If you have two serial connections to some other computer (this
69 usually requires two modems and two telephone lines) and you use
70 SLIP (the protocol for sending Internet traffic over telephone
71 lines) or PPP (a better SLIP) on them, you can make them behave like
72 one double speed connection using this driver. Naturally, this has
73 to be supported at the other end as well, either with a similar EQL
74 Linux driver or with a Livingston Portmaster 2e.
76 Say Y if you want this and read
77 <file:Documentation/networking/eql.txt>. You may also want to read
78 section 6.2 of the NET-3-HOWTO, available from
79 <http://www.tldp.org/docs.html#howto>.
81 To compile this driver as a module, choose M here: the module
82 will be called eql. If unsure, say N.
85 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 "Ethertap network tap"
110 depends on NETDEVICES && EXPERIMENTAL && NETLINK_DEV
112 If you say Y here (and have said Y to "Kernel/User network link
113 driver", above) and create a character special file /dev/tap0 with
114 major number 36 and minor number 16 using mknod ("man mknod"), you
115 will be able to have a user space program read and write raw
116 Ethernet frames from/to that special file. tap0 can be configured
117 with ifconfig and route like any other Ethernet device but it is not
118 connected to any physical LAN; everything written by the user to
119 /dev/tap0 is treated by the kernel as if it had come in from a LAN
120 to the device tap0; everything the kernel wants to send out over the
121 device tap0 can instead be read by the user from /dev/tap0: the user
122 mode program replaces the LAN that would be attached to an ordinary
123 Ethernet device. Please read the file
124 <file:Documentation/networking/ethertap.txt> for more information.
126 To compile this driver as a module, choose M here: the module
127 will be called ethertap.
129 If you don't know what to use this for, you don't need it.
132 tristate "General Instruments Surfboard 1000"
133 depends on NETDEVICES && PNP
135 This is a driver for the General Instrument (also known as
136 NextLevel) SURFboard 1000 internal
137 cable modem. This is an ISA card which is used by a number of cable
138 TV companies to provide cable modem access. It's a one-way
139 downstream-only cable modem, meaning that your upstream net link is
140 provided by your regular phone modem.
142 At present this driver only compiles as a module, so say M here if
143 you have this card. The module will be called sb1000. Then read
144 <file:Documentation/networking/README.sb1000> for information on how
145 to use this module, as it needs special ppp scripts for establishing
146 a connection. Further documentation and the necessary scripts can be
149 <http://www.jacksonville.net/~fventuri/>
150 <http://home.adelphia.net/~siglercm/sb1000.html>
151 <http://linuxpower.cx/~cable/>
153 If you don't have this card, of course say N.
156 source "drivers/net/arcnet/Kconfig"
163 menu "Ethernet (10 or 100Mbit)"
164 depends on NETDEVICES
167 bool "Ethernet (10 or 100Mbit)"
169 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
170 type of Local Area Network (LAN) in universities and companies.
172 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
173 coaxial cable, linking computers in a chain), 10BASE-T or twisted
174 pair (10 Mbps over twisted pair cable, linking computers to central
175 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
176 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
177 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
178 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
179 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
180 Ethernet (1 Gbps over optical fiber or short copper links).
182 If your Linux machine will be connected to an Ethernet and you have
183 an Ethernet network interface card (NIC) installed in your computer,
184 say Y here and read the Ethernet-HOWTO, available from
185 <http://www.tldp.org/docs.html#howto>. You will then also have
186 to say Y to the driver for your particular NIC.
188 Note that the answer to this question won't directly affect the
189 kernel: saying N will just cause the configurator to skip all
190 the questions about Ethernet network cards. If unsure, say N.
193 tristate "Generic Media Independent Interface device support"
194 depends on NET_ETHERNET
196 Most ethernet controllers have MII transceiver either as an external
197 or internal device. It is safe to say Y or M here even if your
198 ethernet card lack MII.
200 source "drivers/net/arm/Kconfig"
203 tristate "MACE (Power Mac ethernet) support"
204 depends on NET_ETHERNET && PPC_PMAC && PPC32
207 Power Macintoshes and clones with Ethernet built-in on the
208 motherboard will usually use a MACE (Medium Access Control for
209 Ethernet) interface. Say Y to include support for the MACE chip.
211 To compile this driver as a module, choose M here: the module
214 config MACE_AAUI_PORT
215 bool "Use AAUI port instead of TP by default"
218 Some Apple machines (notably the Apple Network Server) which use the
219 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
220 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
221 Y here if you have such a machine. If unsure, say N.
222 The driver will default to AAUI on ANS anyway, and if you use it as
223 a module, you can provide the port_aaui=0|1 to force the driver.
226 tristate "BMAC (G3 ethernet) support"
227 depends on NET_ETHERNET && PPC_PMAC && PPC32
230 Say Y for support of BMAC Ethernet interfaces. These are used on G3
233 To compile this driver as a module, choose M here: the module
237 tristate "National DP83902AV (Oak ethernet) support"
238 depends on NET_ETHERNET && PPC && BROKEN
241 Say Y if your machine has this type of Ethernet network card.
243 To compile this driver as a module, choose M here: the module
244 will be called oaknet.
247 tristate "Ariadne support"
248 depends on NET_ETHERNET && ZORRO
250 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
253 To compile this driver as a module, choose M here: the module
254 will be called ariadne.
257 tristate "A2065 support"
258 depends on NET_ETHERNET && ZORRO
261 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
264 To compile this driver as a module, choose M here: the module
265 will be called a2065.
268 tristate "Hydra support"
269 depends on NET_ETHERNET && ZORRO
272 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
274 To compile this driver as a module, choose M here: the module
275 will be called hydra.
278 tristate "Zorro NS8390-based Ethernet support"
279 depends on NET_ETHERNET && ZORRO
282 This driver is for Zorro Ethernet cards using an NS8390-compatible
283 chipset, like the Village Tronic Ariadne II and the Individual
284 Computers X-Surf Ethernet cards. If you have such a card, say Y.
287 To compile this driver as a module, choose M here: the module
288 will be called zorro8390.
291 tristate "PCMCIA NE2000 support"
292 depends on NET_ETHERNET && AMIGA_PCMCIA
295 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
298 To compile this driver as a module, choose M here: the module
302 tristate "Apollo 3c505 support"
303 depends on NET_ETHERNET && APOLLO
305 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
306 If you don't have one made for Apollos, you can use one from a PC,
307 except that your Apollo won't be able to boot from it (because the
308 code in the ROM will be for a PC).
311 bool "Macintosh NS 8390 based ethernet cards"
312 depends on NET_ETHERNET && MAC
315 If you want to include a driver to support Nubus or LC-PDS
316 Ethernet cards using an NS8390 chipset or its equivalent, say Y
317 and read the Ethernet-HOWTO, available from
318 <http://www.tldp.org/docs.html#howto>.
321 tristate "Macintosh CS89x0 based ethernet cards"
322 depends on NET_ETHERNET && MAC && BROKEN
324 Support for CS89x0 chipset based Ethernet cards. If you have a
325 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
326 read the Ethernet-HOWTO, available from
327 <http://www.tldp.org/docs.html#howto>.
329 To compile this driver as a module, choose M here and read
330 <file:Documentation/networking/net-modules.txt>. This module will
334 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
335 depends on NET_ETHERNET && MAC
337 Support for NatSemi SONIC based Ethernet devices. This includes
338 the onboard Ethernet in many Quadras as well as some LC-PDS,
339 a few Nubus and all known Comm Slot Ethernet cards. If you have
340 one of these say Y and read the Ethernet-HOWTO, available from
341 <http://www.tldp.org/docs.html#howto>.
343 To compile this driver as a module, choose M here and read
344 <file:Documentation/networking/net-modules.txt>. This module will
348 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
349 depends on NET_ETHERNET && MAC && EXPERIMENTAL
352 Support for the onboard AMD 79C940 MACE Ethernet controller used in
353 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
354 say Y and read the Ethernet-HOWTO, available from
355 <http://www.tldp.org/docs.html#howto>.
358 tristate "MVME147 (Lance) Ethernet support"
359 depends on NET_ETHERNET && MVME147
362 Support for the on-board Ethernet interface on the Motorola MVME147
363 single-board computer. Say Y here to include the
364 driver for this chip in your kernel.
365 To compile this driver as a module, choose M here.
368 tristate "MVME16x Ethernet support"
369 depends on NET_ETHERNET && MVME16x
371 This is the driver for the Ethernet interface on the Motorola
372 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
373 driver for this chip in your kernel.
374 To compile this driver as a module, choose M here.
377 tristate "BVME6000 Ethernet support"
378 depends on NET_ETHERNET && BVME6000
380 This is the driver for the Ethernet interface on BVME4000 and
381 BVME6000 VME boards. Say Y here to include the driver for this chip
383 To compile this driver as a module, choose M here.
386 tristate "Atari Lance support"
387 depends on NET_ETHERNET && ATARI
389 Say Y to include support for several Atari Ethernet adapters based
390 on the AMD Lance chipset: RieblCard (with or without battery), or
391 PAMCard VME (also the version by Rhotron, with different addresses).
394 tristate "BioNet-100 support"
395 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
397 Say Y to include support for BioData's BioNet-100 Ethernet adapter
398 for the ACSI port. The driver works (has to work...) with a polled
399 I/O scheme, so it's rather slow :-(
402 tristate "PAMsNet support"
403 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
405 Say Y to include support for the PAMsNet Ethernet adapter for the
406 ACSI port ("ACSI node"). The driver works (has to work...) with a
407 polled I/O scheme, so it's rather slow :-(
410 tristate "Sun3/Sun3x on-board LANCE support"
411 depends on NET_ETHERNET && (SUN3 || SUN3X)
413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
415 here to compile in the Linux driver for this and enable Ethernet.
416 General Linux information on the Sun 3 and 3x series (now
418 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
420 If you're not building a kernel for a Sun 3, say N.
423 tristate "Sun3 on-board Intel 82586 support"
424 depends on NET_ETHERNET && SUN3
426 This driver enables support for the on-board Intel 82586 based
427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
428 that this driver does not support 82586-based adapters on additional
432 bool "HP on-board LANCE support"
433 depends on NET_ETHERNET && DIO
436 If you want to use the builtin "LANCE" Ethernet controller on an
437 HP300 machine, say Y here.
440 tristate "Lasi ethernet"
441 depends on NET_ETHERNET && PARISC && GSC_LASI
443 Say Y here to support the on-board Intel 82596 ethernet controller
444 built into Hewlett-Packard PA-RISC machines.
446 config MIPS_JAZZ_SONIC
447 tristate "MIPS JAZZ onboard SONIC Ethernet support"
448 depends on NET_ETHERNET && MIPS_JAZZ
450 This is the driver for the onboard card of MIPS Magnum 4000,
451 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
453 config MIPS_GT96100ETH
454 bool "MIPS GT96100 Ethernet support"
455 depends on NET_ETHERNET && MIPS_GT96100
457 Say Y here to support the Ethernet subsystem on your GT96100 card.
459 config MIPS_AU1X00_ENET
460 bool "MIPS AU1000 Ethernet support"
461 depends on NET_ETHERNET && SOC_AU1X00
464 If you have an Alchemy Semi AU1X00 based system
465 say Y. Otherwise, say N.
467 config NET_SB1250_MAC
468 tristate "SB1250 Ethernet support"
469 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
472 bool "SGI IOC3 Ethernet"
473 depends on NET_ETHERNET && SGI_IP27
477 If you have a network (Ethernet) card of this type, say Y and read
478 the Ethernet-HOWTO, available from
479 <http://www.tldp.org/docs.html#howto>.
481 config SGI_IOC3_ETH_HW_RX_CSUM
482 bool "Receive hardware checksums"
483 depends on SGI_IOC3_ETH && INET
486 The SGI IOC3 network adapter supports TCP and UDP checksums in
487 hardware to offload processing of these checksums from the CPU. At
488 the moment only acceleration of IPv4 is supported. This option
489 enables offloading for checksums on receive. If unsure, say Y.
491 config SGI_IOC3_ETH_HW_TX_CSUM
492 bool "Transmit hardware checksums"
493 depends on SGI_IOC3_ETH && INET
496 The SGI IOC3 network adapter supports TCP and UDP checksums in
497 hardware to offload processing of these checksums from the CPU. At
498 the moment only acceleration of IPv4 is supported. This option
499 enables offloading for checksums on transmit. If unsure, say Y.
501 config SGI_O2MACE_ETH
502 tristate "SGI O2 MACE Fast Ethernet support"
503 depends on NET_ETHERNET && SGI_IP32=y
506 tristate "National DP83902AV support"
507 depends on NET_ETHERNET && SUPERH
510 Support for cards based on the National Semiconductor DP83902AV
511 ST-NIC Serial Network Interface Controller for Twisted Pair. This
512 is a 10Mbit/sec Ethernet controller. Product overview and specs at
513 <http://www.national.com/pf/DP/DP83902A.html>.
518 tristate "Sun LANCE support"
519 depends on NET_ETHERNET && SBUS
522 This driver supports the "le" interface present on all 32-bit Sparc
523 systems, on some older Ultra systems and as an Sbus option. These
524 cards are based on the AMD Lance chipset, which is better known
525 via the NE2100 cards.
527 To compile this driver as a module, choose M here: the module
528 will be called sunlance.
531 tristate "Sun Happy Meal 10/100baseT support"
532 depends on NET_ETHERNET && (SBUS || PCI)
535 This driver supports the "hme" interface present on most Ultra
536 systems and as an option on older Sbus systems. This driver supports
537 both PCI and Sbus devices. This driver also supports the "qfe" quad
538 100baseT device available in both PCI and Sbus configurations.
540 To compile this driver as a module, choose M here: the module
541 will be called sunhme.
544 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
545 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
548 This driver supports the "be" interface available as an Sbus option.
549 This is Sun's older 100baseT Ethernet device.
551 To compile this driver as a module, choose M here: the module
552 will be called sunbmac.
555 tristate "Sun QuadEthernet support"
556 depends on NET_ETHERNET && SBUS
559 This driver supports the "qe" 10baseT Ethernet device, available as
560 an Sbus option. Note that this is not the same as Quad FastEthernet
561 "qfe" which is supported by the Happy Meal driver instead.
563 To compile this driver as a module, choose M here: the module
564 will be called sunqe.
567 tristate "Sun GEM support"
568 depends on NET_ETHERNET && PCI
571 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
572 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
574 config NET_VENDOR_3COM
576 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
578 If you have a network (Ethernet) card belonging to this class, say Y
579 and read the Ethernet-HOWTO, available from
580 <http://www.tldp.org/docs.html#howto>.
582 Note that the answer to this question doesn't directly affect the
583 kernel: saying N will just cause the configurator to skip all
584 the questions about 3COM cards. If you say Y, you will be asked for
585 your specific card in the following questions.
588 tristate "3c501 \"EtherLink\" support"
589 depends on NET_VENDOR_3COM && ISA
591 If you have a network (Ethernet) card of this type, say Y and read
592 the Ethernet-HOWTO, available from
593 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
594 new card, since the 3c501 is slow, broken, and obsolete: you will
595 have problems. Some people suggest to ping ("man ping") a nearby
596 machine every minute ("man cron") when using this card.
598 To compile this driver as a module, choose M here and read
599 <file:Documentation/networking/net-modules.txt>. The module
600 will be called 3c501.
603 tristate "3c503 \"EtherLink II\" support"
604 depends on NET_VENDOR_3COM && ISA
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 3c503.
616 tristate "3c505 \"EtherLink Plus\" support"
617 depends on NET_VENDOR_3COM && ISA
619 Information about this network (Ethernet) card can be found in
620 <file:Documentation/networking/3c505.txt>. If you have a card of
621 this type, say Y and read the Ethernet-HOWTO, available from
622 <http://www.tldp.org/docs.html#howto>.
624 To compile this driver as a module, choose M here and read
625 <file:Documentation/networking/net-modules.txt>. The module
626 will be called 3c505.
629 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
630 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
632 If you have a network (Ethernet) card of this type, say Y and read
633 the Ethernet-HOWTO, available from
634 <http://www.tldp.org/docs.html#howto>.
636 To compile this driver as a module, choose M here and read
637 <file:Documentation/networking/net-modules.txt>. The module
638 will be called 3c507.
641 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support"
642 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
644 If you have a network (Ethernet) card belonging to the 3Com
645 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
646 from <http://www.tldp.org/docs.html#howto>.
648 If your card is not working you may need to use the DOS
649 setup disk to disable Plug & Play mode, and to select the default
652 To compile this driver as a module, choose M here and read
653 <file:Documentation/networking/net-modules.txt>. The module
654 will be called 3c509.
657 tristate "3c515 ISA \"Fast EtherLink\""
658 depends on NET_VENDOR_3COM && (ISA || EISA)
660 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
661 network card, say Y and read the Ethernet-HOWTO, available from
662 <http://www.tldp.org/docs.html#howto>.
664 To compile this driver as a module, choose M here and read
665 <file:Documentation/networking/net-modules.txt>. The module
666 will be called 3c515.
669 tristate "3c523 \"EtherLink/MC\" support"
670 depends on NET_VENDOR_3COM && MCA_LEGACY
672 If you have a network (Ethernet) card of this type, say Y and read
673 the Ethernet-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>.
676 To compile this driver as a module, choose M here and read
677 <file:Documentation/networking/net-modules.txt>. The module
678 will be called 3c523.
681 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
682 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
684 If you have a network (Ethernet) card of this type, say Y and read
685 the Ethernet-HOWTO, available from
686 <http://www.tldp.org/docs.html#howto>.
688 To compile this driver as a module, choose M here and read
689 <file:Documentation/networking/net-modules.txt>. The module
690 will be called 3c527.
693 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
694 depends on NET_VENDOR_3COM && (PCI || EISA)
697 This option enables driver support for a large number of 10mbps and
698 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
700 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
701 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
702 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
703 "Tornado" (3c905) PCI
704 "Hurricane" (3c555/3cSOHO) PCI
706 If you have such a card, say Y and read the Ethernet-HOWTO,
707 available from <http://www.tldp.org/docs.html#howto>. More
708 specific information is in
709 <file:Documentation/networking/vortex.txt> and in the comments at
710 the beginning of <file:drivers/net/3c59x.c>.
712 To compile this support as a module, choose M here and read
713 <file:Documentation/networking/net-modules.txt>.
716 tristate "3cr990 series \"Typhoon\" support"
717 depends on NET_VENDOR_3COM && PCI
720 This option enables driver support for the 3cr990 series of cards:
722 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
723 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
724 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
726 If you have a network (Ethernet) card of this type, say Y and read
727 the Ethernet-HOWTO, available from
728 <http://www.tldp.org/docs.html#howto>.
730 To compile this driver as a module, choose M here and read
731 <file:Documentation/networking/net-modules.txt>. The module
732 will be called typhoon.
735 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
736 depends on NET_ETHERNET && ISA
738 If you have a network (Ethernet) card of this type, say Y and read
739 the Ethernet-HOWTO, available from
740 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
743 To compile this driver as a module, choose M here: the module
744 will be called lance. This is recommended.
746 config NET_VENDOR_SMC
747 bool "Western Digital/SMC cards"
748 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
750 If you have a network (Ethernet) card belonging to this class, say Y
751 and read the Ethernet-HOWTO, available from
752 <http://www.tldp.org/docs.html#howto>.
754 Note that the answer to this question doesn't directly affect the
755 kernel: saying N will just cause the configurator to skip all
756 the questions about Western Digital cards. If you say Y, you will be
757 asked for your specific card in the following questions.
760 tristate "WD80*3 support"
761 depends on NET_VENDOR_SMC && ISA
764 If you have a network (Ethernet) card of this type, say Y and read
765 the Ethernet-HOWTO, available from
766 <http://www.tldp.org/docs.html#howto>.
768 To compile this driver as a module, choose M here and read
769 <file:Documentation/networking/net-modules.txt>. The module
773 tristate "SMC Ultra MCA support"
774 depends on NET_VENDOR_SMC && MCA
777 If you have a network (Ethernet) card of this type and are running
778 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
779 available from <http://www.tldp.org/docs.html#howto>.
781 To compile this driver as a module, choose M here and read
782 <file:Documentation/networking/net-modules.txt>. The module
783 will be called smc-mca.
786 tristate "SMC Ultra support"
787 depends on NET_VENDOR_SMC && ISA
790 If you have a network (Ethernet) card of this type, say Y and read
791 the Ethernet-HOWTO, available from
792 <http://www.tldp.org/docs.html#howto>.
794 Important: There have been many reports that, with some motherboards
795 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
796 such as some BusLogic models) causes corruption problems with many
797 operating systems. The Linux smc-ultra driver has a work-around for
798 this but keep it in mind if you have such a SCSI card and have
801 To compile this driver as a module, choose M here and read
802 <file:Documentation/networking/net-modules.txt>. The module
803 will be called smc-ultra.
806 tristate "SMC Ultra32 EISA support"
807 depends on NET_VENDOR_SMC && EISA
810 If you have a network (Ethernet) card of this type, say Y and read
811 the Ethernet-HOWTO, available from
812 <http://www.tldp.org/docs.html#howto>.
814 To compile this driver as a module, choose M here and read
815 <file:Documentation/networking/net-modules.txt>. The module
816 will be called smc-ultra32.
819 tristate "SMC 91C9x/91C1xxx support"
822 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R)
824 This is a driver for SMC's 91x series of Ethernet chipsets,
825 including the SMC91C94 and the SMC91C111. Say Y if you want it
826 compiled into the kernel, and read the file
827 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
828 available from <http://www.linuxdoc.org/docs.html#howto>.
830 This driver is also available as a module ( = code which can be
831 inserted in and removed from the running kernel whenever you want).
832 The module will be called smc91x. If you want to compile it as a
833 module, say M here and read <file:Documentation/modules.txt> as well
834 as <file:Documentation/networking/net-modules.txt>.
837 tristate "SMC 9194 support"
838 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
841 This is support for the SMC9xxx based Ethernet cards. Choose this
842 option if you have a DELL laptop with the docking station, or
843 another SMC9192/9194 based chipset. Say Y if you want it compiled
844 into the kernel, and read the file
845 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
846 available from <http://www.tldp.org/docs.html#howto>.
848 To compile this driver as a module, choose M here and read
849 <file:Documentation/networking/net-modules.txt>. The module
850 will be called smc9194.
852 config NET_VENDOR_RACAL
853 bool "Racal-Interlan (Micom) NI cards"
854 depends on NET_ETHERNET && ISA
856 If you have a network (Ethernet) card belonging to this class, such
857 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
858 available from <http://www.tldp.org/docs.html#howto>.
860 Note that the answer to this question doesn't directly affect the
861 kernel: saying N will just cause the configurator to skip all
862 the questions about NI cards. If you say Y, you will be asked for
863 your specific card in the following questions.
866 tristate "NI5010 support (EXPERIMENTAL)"
867 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
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>. Note that this is still
874 To compile this driver as a module, choose M here and read
875 <file:Documentation/networking/net-modules.txt>. The module
876 will be called ni5010.
879 tristate "NI5210 support"
880 depends on NET_VENDOR_RACAL && ISA
882 If you have a network (Ethernet) card of this type, say Y and read
883 the Ethernet-HOWTO, available from
884 <http://www.tldp.org/docs.html#howto>.
886 To compile this driver as a module, choose M here and read
887 <file:Documentation/networking/net-modules.txt>. The module
891 tristate "NI6510 support"
892 depends on NET_VENDOR_RACAL && ISA
894 If you have a network (Ethernet) card of this type, say Y and read
895 the Ethernet-HOWTO, available from
896 <http://www.tldp.org/docs.html#howto>.
898 To compile this driver as a module, choose M here and read
899 <file:Documentation/networking/net-modules.txt>. The module
902 source "drivers/net/tulip/Kconfig"
905 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)"
906 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
909 If you have a network (Ethernet) card of this type, say Y and read
910 the Ethernet-HOWTO, available from
911 <http://www.tldp.org/docs.html#howto>.
913 To compile this driver as a module, choose M here and read
914 <file:Documentation/networking/net-modules.txt>. The module
915 will be called at1700.
918 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
919 depends on NET_ETHERNET && (ISA || EISA || MCA)
922 If you have a network (Ethernet) card of this type, say Y and read
923 the Ethernet-HOWTO, available from
924 <http://www.tldp.org/docs.html#howto> as well as
925 <file:drivers/net/depca.c>.
927 To compile this driver as a module, choose M here and read
928 <file:Documentation/networking/net-modules.txt>. The module
929 will be called depca.
932 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
933 depends on NET_ETHERNET && (ISA || EISA || PCI)
935 If you have a network (Ethernet) card of this type, say Y and read
936 the Ethernet-HOWTO, available from
937 <http://www.tldp.org/docs.html#howto>.
939 To compile this driver as a module, choose M here and read
940 <file:Documentation/networking/net-modules.txt>. The module
941 will be called hp100.
944 bool "Other ISA cards"
945 depends on NET_ETHERNET && ISA
947 If your network (Ethernet) card hasn't been mentioned yet and its
948 bus system (that's the way the cards talks to the other components
949 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
950 Make sure you know the name of your card. Read the Ethernet-HOWTO,
951 available from <http://www.tldp.org/docs.html#howto>.
955 Note that the answer to this question doesn't directly affect the
956 kernel: saying N will just cause the configurator to skip all
957 the remaining ISA network card questions. If you say Y, you will be
958 asked for your specific card in the following questions.
961 tristate "Cabletron E21xx support"
965 If you have a network (Ethernet) card of this type, say Y and read
966 the Ethernet-HOWTO, available from
967 <http://www.tldp.org/docs.html#howto>.
969 To compile this driver as a module, choose M here and read
970 <file:Documentation/networking/net-modules.txt>. The module
971 will be called e2100.
974 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
978 This driver supports the DE203, DE204 and DE205 network (Ethernet)
979 cards. If this is for you, say Y and read
980 <file:Documentation/networking/ewrk3.txt> in the kernel source as
981 well as the Ethernet-HOWTO, available from
982 <http://www.tldp.org/docs.html#howto>.
984 To compile this driver as a module, choose M here and read
985 <file:Documentation/networking/net-modules.txt>. The module
986 will be called ewrk3.
989 tristate "EtherExpress 16 support"
992 If you have an EtherExpress16 network (Ethernet) card, say Y and
993 read the Ethernet-HOWTO, available from
994 <http://www.tldp.org/docs.html#howto>. Note that the Intel
995 EtherExpress16 card used to be regarded as a very poor choice
996 because the driver was very unreliable. We now have a new driver
997 that should do better.
999 To compile this driver as a module, choose M here and read
1000 <file:Documentation/networking/net-modules.txt>. The module
1001 will be called eexpress.
1004 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1007 If you have a network (Ethernet) card of this type, say Y. This
1008 driver supports intel i82595{FX,TX} based boards. Note however
1009 that the EtherExpress PRO/100 Ethernet card has its own separate
1010 driver. Please read the Ethernet-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1013 To compile this driver as a module, choose M here and read
1014 <file:Documentation/networking/net-modules.txt>. The module
1015 will be called eepro.
1018 tristate "FMV-181/182/183/184 support (OBSOLETE)"
1019 depends on NET_ISA && OBSOLETE
1021 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
1022 say Y and read the Ethernet-HOWTO, available from
1023 <http://www.tldp.org/docs.html#howto>.
1025 If you use an FMV-183 or FMV-184 and it is not working, you may need
1026 to disable Plug & Play mode of the card.
1028 To compile this driver as a module, choose M here and read
1029 <file:Documentation/networking/net-modules.txt>. The module
1030 will be called fmv18x.
1033 tristate "HP PCLAN+ (27247B and 27252A) support"
1037 If you have a network (Ethernet) card of this type, say Y and read
1038 the Ethernet-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here and read
1042 <file:Documentation/networking/net-modules.txt>. The module
1043 will be called hp-plus.
1046 tristate "HP PCLAN (27245 and other 27xxx series) support"
1050 If you have a network (Ethernet) card of this type, say Y and read
1051 the Ethernet-HOWTO, available from
1052 <http://www.tldp.org/docs.html#howto>.
1054 To compile this driver as a module, choose M here and read
1055 <file:Documentation/networking/net-modules.txt>. The module
1059 tristate "LP486E on board Ethernet"
1062 Say Y here to support the 82596-based on-board Ethernet controller
1063 for the Panther motherboard, which is one of the two shipped in the
1064 Intel Professional Workstation.
1067 tristate "ICL EtherTeam 16i/32 support"
1070 If you have a network (Ethernet) card of this type, say Y and read
1071 the Ethernet-HOWTO, available from
1072 <http://www.tldp.org/docs.html#howto>.
1074 To compile this driver as a module, choose M here and read
1075 <file:Documentation/networking/net-modules.txt>. The module
1076 will be called eth16i.
1079 tristate "NE2000/NE1000 support"
1080 depends on NET_ISA || (Q40 && m) || M32R
1083 If you have a network (Ethernet) card of this type, say Y and read
1084 the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1086 without a specific driver are compatible with NE2000.
1088 If you have a PCI NE2000 card however, say N here and Y to "PCI
1089 NE2000 support", above. If you have a NE2000 card and are running on
1090 an MCA system (a bus system used on some IBM PS/2 computers and
1091 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1094 To compile this driver as a module, choose M here and read
1095 <file:Documentation/networking/net-modules.txt>. The module
1099 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1100 depends on NET_ISA && EXPERIMENTAL
1102 The Zenith Z-Note notebook computer has a built-in network
1103 (Ethernet) card, and this is the Linux driver for it. Note that the
1104 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1105 by this driver. Read the Ethernet-HOWTO, available from
1106 <http://www.tldp.org/docs.html#howto>.
1109 tristate "SEEQ8005 support (EXPERIMENTAL)"
1110 depends on NET_ISA && EXPERIMENTAL
1112 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1113 is for you, read the Ethernet-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>.
1116 To compile this driver as a module, choose M here and read
1117 <file:Documentation/networking/net-modules.txt>. The module
1118 will be called seeq8005.
1121 tristate "SK_G16 support (OBSOLETE)"
1122 depends on NET_ISA && OBSOLETE
1124 If you have a network (Ethernet) card of this type, say Y and read
1125 the Ethernet-HOWTO, available from
1126 <http://www.tldp.org/docs.html#howto>.
1129 tristate "SKnet MCA support"
1130 depends on NET_ETHERNET && MCA && BROKEN
1132 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1133 support" in order to use this driver. Supported cards are the SKnet
1134 Junior MC2 and the SKnet MC2(+). The driver automatically
1135 distinguishes between the two cards. Note that using multiple boards
1136 of different type hasn't been tested with this driver. Say Y if you
1137 have one of these Ethernet adapters.
1139 To compile this driver as a module, choose M here and read
1140 <file:Documentation/networking/net-modules.txt>. The module
1141 will be called sk_mca.
1144 tristate "NE/2 (ne2000 MCA version) support"
1145 depends on NET_ETHERNET && MCA_LEGACY
1148 If you have a network (Ethernet) card of this type, say Y and read
1149 the Ethernet-HOWTO, available from
1150 <http://www.tldp.org/docs.html#howto>.
1152 To compile this driver as a module, choose M here and read
1153 <file:Documentation/networking/net-modules.txt>. The module
1157 tristate "IBM LAN Adapter/A support"
1158 depends on NET_ETHERNET && MCA && MCA_LEGACY
1160 This is a Micro Channel Ethernet adapter. You need to set
1161 CONFIG_MCA to use this driver. It is both available as an in-kernel
1162 driver and as a module.
1164 To compile this driver as a module, choose M here and read
1165 <file:Documentation/networking/net-modules.txt>. The only
1166 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1167 will both support 16K and 32K memory windows, however a 32K window
1168 gives a better security against packet losses. Usage of multiple
1169 boards with this driver should be possible, but has not been tested
1170 up to now due to lack of hardware.
1173 tristate "IBM LAN Virtual Ethernet support"
1174 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1176 This driver supports virtual ethernet adapters on newer IBM iSeries
1177 and pSeries systems.
1179 To compile this driver as a module, choose M here and read
1180 <file:Documentation/networking/net-modules.txt>. The module will
1184 tristate "IBM PPC4xx EMAC driver support"
1188 This driver supports the IBM PPC4xx EMAC family of on-chip
1189 Ethernet controllers.
1191 config IBM_EMAC_ERRMSG
1192 bool "Verbose error messages"
1196 int "Number of receive buffers"
1198 default "128" if IBM_EMAC4
1202 int "Number of transmit buffers"
1204 default "128" if IBM_EMAC4
1207 config IBM_EMAC_FGAP
1212 config IBM_EMAC_SKBRES
1213 int "Skb reserve amount"
1218 bool "EISA, VLB, PCI and on board controllers"
1219 depends on NET_ETHERNET && (ISA || EISA || PCI)
1221 This is another class of network cards which attach directly to the
1222 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1223 available from <http://www.tldp.org/docs.html#howto>.
1225 Note that the answer to this question doesn't directly affect the
1226 kernel: saying N will just cause the configurator to skip all
1227 the questions about this class of network cards. If you say Y, you
1228 will be asked for your specific card in the following questions. If
1229 you are unsure, say Y.
1232 tristate "AMD PCnet32 PCI support"
1233 depends on NET_PCI && PCI
1237 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1238 answer Y here and read the Ethernet-HOWTO, available from
1239 <http://www.tldp.org/docs.html#howto>.
1241 To compile this driver as a module, choose M here and read
1242 <file:Documentation/networking/net-modules.txt>. The module
1243 will be called pcnet32.
1246 tristate "AMD 8111 (new PCI lance) support"
1247 depends on NET_PCI && PCI
1251 If you have an AMD 8111-based PCI lance ethernet card,
1252 answer Y here and read the Ethernet-HOWTO, available from
1253 <http://www.tldp.org/docs.html#howto>.
1255 To compile this driver as a module, choose M here and read
1256 <file:Documentation/networking/net-modules.txt>. The module
1257 will be called amd8111e.
1258 config AMD8111E_NAPI
1259 bool "Enable NAPI support"
1260 depends on AMD8111_ETH
1262 NAPI is a new driver API designed to reduce CPU and interrupt load
1263 when the driver is receiving lots of packets from the card. It is
1264 still somewhat experimental and thus not yet enabled by default.
1266 If your estimated Rx load is 10kpps or more, or if the card will be
1267 deployed on potentially unfriendly networks (e.g. in a firewall),
1270 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1275 config ADAPTEC_STARFIRE
1276 tristate "Adaptec Starfire/DuraLAN support"
1277 depends on NET_PCI && PCI
1281 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1282 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1283 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1286 To compile this driver as a module, choose M here: the module
1287 will be called starfire. This is recommended.
1289 config ADAPTEC_STARFIRE_NAPI
1290 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1291 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1293 NAPI is a new driver API designed to reduce CPU and interrupt load
1294 when the driver is receiving lots of packets from the card. It is
1295 still somewhat experimental and thus not yet enabled by default.
1297 If your estimated Rx load is 10kpps or more, or if the card will be
1298 deployed on potentially unfriendly networks (e.g. in a firewall),
1301 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1307 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1308 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1311 If you have a network (Ethernet) card of this type, say Y and read
1312 the Ethernet-HOWTO, available from
1313 <http://www.tldp.org/docs.html#howto>.
1315 To compile this driver as a module, choose M here and read
1316 <file:Documentation/networking/net-modules.txt>. The module
1317 will be called ac3200.
1320 tristate "Apricot Xen-II on board Ethernet"
1321 depends on NET_PCI && ISA
1323 If you have a network (Ethernet) controller of this type, say Y and
1324 read the Ethernet-HOWTO, available from
1325 <http://www.tldp.org/docs.html#howto>.
1327 To compile this driver as a module, choose M here and read
1328 <file:Documentation/networking/net-modules.txt>. The module will be
1332 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1333 depends on NET_PCI && PCI && EXPERIMENTAL
1336 If you have a network (Ethernet) controller of this type, say Y and
1337 read the Ethernet-HOWTO, available from
1338 <http://www.tldp.org/docs.html#howto>.
1340 To compile this driver as a module, choose M here and read
1341 <file:Documentation/networking/net-modules.txt>. The module will be
1345 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1346 depends on NET_PCI && PCI && EXPERIMENTAL
1348 If you have a network (Ethernet) controller of this type, say Y and
1349 read the Ethernet-HOWTO, available from
1350 <http://www.tldp.org/docs.html#howto>.
1352 To compile this driver as a module, choose M here and read
1353 <file:Documentation/networking/net-modules.txt>. The module will be
1358 tristate "CS89x0 support"
1359 depends on NET_PCI && (ISA || ARCH_IXDP2X01)
1361 Support for CS89x0 chipset based Ethernet cards. If you have a
1362 network (Ethernet) card of this type, say Y and read the
1363 Ethernet-HOWTO, available from
1364 <http://www.tldp.org/docs.html#howto> as well as
1365 <file:Documentation/networking/cs89x0.txt>.
1367 To compile this driver as a module, choose M here and read
1368 <file:Documentation/networking/net-modules.txt>. The module will be
1372 tristate "TOSHIBA TC35815 Ethernet support"
1373 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1376 tristate "Digi Intl. RightSwitch SE-X support"
1377 depends on NET_PCI && (PCI || EISA)
1379 This is support for the Digi International RightSwitch series of
1380 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1381 models. If you have a network card of this type, say Y and read the
1382 Ethernet-HOWTO, available from
1383 <http://www.tldp.org/docs.html#howto>. More specific
1384 information is contained in <file:Documentation/networking/dgrs.txt>.
1386 To compile this driver as a module, choose M here and read
1387 <file:Documentation/networking/net-modules.txt>. The module
1388 will be called dgrs.
1391 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1392 depends on NET_PCI && PCI
1395 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1396 card, say Y and read the Ethernet-HOWTO, available from
1397 <http://www.tldp.org/docs.html#howto>.
1399 To compile this driver as a module, choose M here and read
1400 <file:Documentation/networking/net-modules.txt>. The module
1401 will be called eepro100.
1405 tristate "Intel(R) PRO/100+ support"
1406 depends on NET_PCI && PCI
1409 This driver supports Intel(R) PRO/100 family of adapters.
1410 To verify that your adapter is supported, find the board ID number
1411 on the adapter. Look for a label that has a barcode and a number
1412 in the format 123456-001 (six digits hyphen three digits).
1414 Use the above information and the Adapter & Driver ID Guide at:
1416 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1418 to identify the adapter.
1420 For the latest Intel PRO/100 network driver for Linux, see:
1422 <http://appsr.intel.com/scripts-df/support_intel.asp>
1424 More specific information on configuring the driver is in
1425 <file:Documentation/networking/e100.txt>.
1427 To compile this driver as a module, choose M here and read
1428 <file:Documentation/networking/net-modules.txt>. The module
1429 will be called e100.
1432 bool "Use Rx Polling (NAPI)"
1435 NAPI is a new driver API designed to reduce CPU and interrupt load
1436 when the driver is receiving lots of packets from the card. It is
1437 still somewhat experimental and thus not yet enabled by default.
1439 If your estimated Rx load is 10kpps or more, or if the card will be
1440 deployed on potentially unfriendly networks (e.g. in a firewall),
1443 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1449 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1450 depends on NET_PCI && EISA && EXPERIMENTAL
1453 If you have a network (Ethernet) card of this type, say Y and read
1454 the Ethernet-HOWTO, available from
1455 <http://www.tldp.org/docs.html#howto>.
1457 To compile this driver as a module, choose M here and read
1458 <file:Documentation/networking/net-modules.txt>. The module
1459 will be called lne390.
1462 tristate "Myson MTD-8xx PCI Ethernet support"
1463 depends on NET_PCI && PCI
1467 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1468 cards. Specifications and data at
1469 <http://www.myson.com.hk/mtd/datasheet/>.
1472 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1473 depends on NET_PCI && PCI
1476 This driver is for the National Semiconductor DP83810 series,
1477 which is used in cards from PureData, NetGear, Linksys
1478 and others, including the 83815 chip.
1479 More specific information and updates are available from
1480 <http://www.scyld.com/network/natsemi.html>.
1483 tristate "PCI NE2000 and clones support (see help)"
1484 depends on NET_PCI && PCI
1487 This driver is for NE2000 compatible PCI cards. It will not work
1488 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1489 support" below). If you have a PCI NE2000 network (Ethernet) card,
1490 say Y and read the Ethernet-HOWTO, available from
1491 <http://www.tldp.org/docs.html#howto>.
1493 This driver also works for the following NE2000 clone cards:
1494 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1495 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1496 Holtek HT80232 Holtek HT80229
1498 To compile this driver as a module, choose M here and read
1499 <file:Documentation/networking/net-modules.txt>. The module
1500 will be called ne2k-pci.
1503 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1504 depends on NET_PCI && EISA && EXPERIMENTAL
1507 If you have a network (Ethernet) card of this type, say Y and read
1508 the Ethernet-HOWTO, available from
1509 <http://www.tldp.org/docs.html#howto>. Note that this driver
1510 will NOT WORK for NE3200 cards as they are completely different.
1512 To compile this driver as a module, choose M here and read
1513 <file:Documentation/networking/net-modules.txt>. The module
1514 will be called ne3210.
1517 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1518 depends on NET_PCI && EISA && EXPERIMENTAL
1521 If you have a network (Ethernet) card of this type, say Y and read
1522 the Ethernet-HOWTO, available from
1523 <http://www.tldp.org/docs.html#howto>.
1525 To compile this driver as a module, choose M here and read
1526 <file:Documentation/networking/net-modules.txt>. The module
1527 will be called es3210.
1530 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1531 depends on NET_PCI && PCI && EXPERIMENTAL
1535 This is a driver for the Fast Ethernet PCI network cards based on
1536 the RTL8139C+ chips. If you have one of those, say Y and read
1537 the Ethernet-HOWTO, available from
1538 <http://www.tldp.org/docs.html#howto>.
1540 To compile this driver as a module, choose M here: the module
1541 will be called 8139cp. This is recommended.
1544 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1545 depends on NET_PCI && PCI
1549 This is a driver for the Fast Ethernet PCI network cards based on
1550 the RTL8139 chips. If you have one of those, say Y and read
1551 the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1553 To compile this driver as a module, choose M here: the module
1554 will be called 8139too. This is recommended.
1557 bool "Use PIO instead of MMIO"
1561 This instructs the driver to use programmed I/O ports (PIO) instead
1562 of PCI shared memory (MMIO). This can possibly solve some problems
1563 in case your mainboard has memory consistency issues. If unsure,
1566 config 8139TOO_TUNE_TWISTER
1567 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1570 This implements a function which might come in handy in case you
1571 are using low quality on long cabling. It is required for RealTek
1572 RTL-8139 revision K boards, and totally unused otherwise. It tries
1573 to match the transceiver to the cable characteristics. This is
1574 experimental since hardly documented by the manufacturer.
1578 bool "Support for older RTL-8129/8130 boards"
1581 This enables support for the older and uncommon RTL-8129 and
1582 RTL-8130 chips, which support MII via an external transceiver,
1583 instead of an internal one. Disabling this option will save some
1584 memory by making the code size smaller. If unsure, say Y.
1586 config 8139_OLD_RX_RESET
1587 bool "Use older RX-reset method"
1590 The 8139too driver was recently updated to contain a more rapid
1591 reset sequence, in the face of severe receive errors. This "new"
1592 RX-reset method should be adequate for all boards. But if you
1593 experience problems, you can enable this option to restore the
1594 old RX-reset behavior. If unsure, say N.
1597 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1598 depends on NET_PCI && PCI
1601 This is a driver for the Fast Ethernet PCI network cards based on
1602 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1603 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1604 read the Ethernet-HOWTO, available at
1605 <http://www.tldp.org/docs.html#howto>. Please read
1606 <file:Documentation/networking/sis900.txt> and comments at the
1607 beginning of <file:drivers/net/sis900.c> for more information.
1609 This driver also supports AMD 79C901 HomePNA so that you can use
1610 your phone line as a network cable.
1612 To compile this driver as a module, choose M here: the module
1613 will be called sis900. This is recommended.
1616 tristate "SMC EtherPower II"
1617 depends on NET_PCI && PCI
1621 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1622 which is based on the SMC83c17x (EPIC/100).
1623 More specific information and updates are available from
1624 <http://www.scyld.com/network/epic100.html>.
1627 tristate "Sundance Alta support"
1628 depends on NET_PCI && PCI
1632 This driver is for the Sundance "Alta" chip.
1633 More specific information and updates are available from
1634 <http://www.scyld.com/network/sundance.html>.
1636 config SUNDANCE_MMIO
1637 bool "Use MMIO instead of PIO"
1640 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1641 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1642 is known to solve bugs on certain chips.
1647 tristate "TI ThunderLAN support"
1648 depends on NET_PCI && (PCI || EISA) && !64BIT
1650 If you have a PCI Ethernet network card based on the ThunderLAN chip
1651 which is supported by this driver, say Y and read the
1652 Ethernet-HOWTO, available from
1653 <http://www.tldp.org/docs.html#howto>.
1655 Devices currently supported by this driver are Compaq Netelligent,
1656 Compaq NetFlex and Olicom cards. Please read the file
1657 <file:Documentation/networking/tlan.txt> for more details.
1659 To compile this driver as a module, choose M here and read
1660 <file:Documentation/networking/net-modules.txt>. The module
1661 will be called tlan.
1663 Please email feedback to <torben.mathiasen@compaq.com>.
1666 tristate "VIA Rhine support"
1667 depends on NET_PCI && PCI
1671 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1672 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1673 Ethernet functions can also be found integrated on South Bridges
1676 To compile this driver as a module, choose M here. The module
1677 will be called via-rhine.
1679 config VIA_RHINE_MMIO
1680 bool "Use MMIO instead of PIO"
1681 depends on VIA_RHINE
1683 This instructs the driver to use PCI shared memory (MMIO) instead of
1684 programmed I/O ports (PIO). Enabling this gives an improvement in
1685 processing time in parts of the driver.
1690 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1691 depends on NET_PCI && EXPERIMENTAL && MIPS
1693 The SAA9730 is a combined multimedia and peripheral controller used
1694 in thin clients, Internet access terminals, and diskless
1696 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1699 bool "Pocket and portable adapters"
1700 depends on NET_ETHERNET && ISA
1702 Cute little network (Ethernet) devices which attach to the parallel
1703 port ("pocket adapters"), commonly used with laptops. If you have
1704 one of those, say Y and read the Ethernet-HOWTO, available from
1705 <http://www.tldp.org/docs.html#howto>.
1707 If you want to plug a network (or some other) card into the PCMCIA
1708 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1709 credit card size extension cards used by all modern laptops), you
1710 need the pcmcia-cs package (location contained in the file
1711 <file:Documentation/Changes>) and you can say N here.
1713 Laptop users should read the Linux Laptop home page at
1714 <http://www.linux-on-laptops.com/> or
1715 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1717 Note that the answer to this question doesn't directly affect the
1718 kernel: saying N will just cause the configurator to skip all
1719 the questions about this class of network devices. If you say Y, you
1720 will be asked for your specific device in the following questions.
1723 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1724 depends on NET_POCKET && ISA && X86
1727 This is a network (Ethernet) device which attaches to your parallel
1728 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1729 available from <http://www.tldp.org/docs.html#howto>, if you
1730 want to use this. If you intend to use this driver, you should have
1731 said N to the "Parallel printer support", because the two drivers
1732 don't like each other.
1734 To compile this driver as a module, choose M here: the module
1738 tristate "D-Link DE600 pocket adapter support"
1739 depends on NET_POCKET && ISA
1741 This is a network (Ethernet) device which attaches to your parallel
1742 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1743 Ethernet-HOWTO, available from
1744 <http://www.tldp.org/docs.html#howto>, if you want to use
1745 this. It is possible to have several devices share a single parallel
1746 port and it is safe to compile the corresponding drivers into the
1749 To compile this driver as a module, choose M here: the module
1750 will be called de600.
1753 tristate "D-Link DE620 pocket adapter support"
1754 depends on NET_POCKET && ISA
1756 This is a network (Ethernet) device which attaches to your parallel
1757 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1758 Ethernet-HOWTO, available from
1759 <http://www.tldp.org/docs.html#howto>, if you want to use
1760 this. It is possible to have several devices share a single parallel
1761 port and it is safe to compile the corresponding drivers into the
1764 To compile this driver as a module, choose M here: the module
1765 will be called de620.
1768 tristate "SGI Seeq ethernet controller support"
1769 depends on NET_ETHERNET && SGI_IP22
1771 Say Y here if you have an Seeq based Ethernet network card. This is
1772 used in many Silicon Graphics machines.
1775 tristate "DEC LANCE ethernet controller support"
1776 depends on NET_ETHERNET && MACH_DECSTATION
1779 This driver is for the series of Ethernet controllers produced by
1780 DEC (now Compaq) based on the AMD Lance chipset, including the
1781 DEPCA series. (This chipset is better known via the NE2100 cards.)
1784 tristate "Baget AMD LANCE support"
1785 depends on NET_ETHERNET && BAGET_MIPS
1787 Say Y to enable kernel support for AMD Lance Ethernet cards on the
1788 MIPS-32-based Baget embedded system. This chipset is better known
1789 via the NE2100 cards.
1792 bool "Motorola 68360 ethernet controller"
1795 Say Y here if you want to use the built-in ethernet controller of
1796 the Motorola 68360 processor.
1799 bool "FEC ethernet controller (of ColdFire 5272)"
1800 depends on M5272 || M5282
1802 Say Y here if you want to use the built-in 10/100 Fast ethernet
1803 controller on the Motorola ColdFire 5272 processor.
1806 tristate "NE2000 compatible support for H8/300"
1807 depends on H8300 && NET_ETHERNET
1809 Say Y here if you want to use the NE2000 compatible
1810 controller on the Renesas H8/300 processor.
1812 source "drivers/net/fec_8xx/Kconfig"
1820 menu "Ethernet (1000 Mbit)"
1821 depends on NETDEVICES
1824 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1827 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1828 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1829 adapter. The driver allows for using the Jumbo Frame option (9000
1830 bytes/frame) however it requires that your switches can handle this
1831 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1834 To compile this driver as a module, choose M here: the
1835 module will be called acenic.
1837 config ACENIC_OMIT_TIGON_I
1838 bool "Omit support for old Tigon I based AceNICs"
1841 Say Y here if you only have Tigon II based AceNICs and want to leave
1842 out support for the older Tigon I based cards which are no longer
1843 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1844 version)). This will reduce the size of the driver object by
1845 app. 100KB. If you are not sure whether your card is a Tigon I or a
1846 Tigon II, say N here.
1848 The safe and default value for this is N.
1851 tristate "D-Link DL2000-based Gigabit Ethernet support"
1855 This driver supports D-Link 2000-based gigabit ethernet cards, which
1857 D-Link DGE-550T Gigabit Ethernet Adapter.
1858 D-Link DL2000-based Gigabit Ethernet Adapter.
1860 To compile this driver as a module, choose M here: the
1861 module will be called dl2k.
1864 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1867 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1868 adapters. For more information on how to identify your adapter, go
1869 to the Adapter & Driver ID Guide at:
1871 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1873 For general information and support, go to the Intel support
1876 <http://support.intel.com>
1878 More specific information on configuring the driver is in
1879 <file:Documentation/networking/e1000.txt>.
1881 To compile this driver as a module, choose M here and read
1882 <file:Documentation/networking/net-modules.txt>. The module
1883 will be called e1000.
1886 bool "Use Rx Polling (NAPI)"
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
1903 tristate "MyriCOM Gigabit Ethernet support"
1906 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1908 To compile this driver as a module, choose M here: the module
1909 will be called myri_sbus. This is recommended.
1912 tristate "National Semiconduct DP83820 support"
1915 This is a driver for the National Semiconductor DP83820 series
1916 of gigabit ethernet MACs. Cards using this chipset include
1917 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1918 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1922 tristate "Packet Engines Hamachi GNIC-II support"
1926 If you have a Gigabit Ethernet card of this type, say Y and read
1927 the Ethernet-HOWTO, available from
1928 <http://www.tldp.org/docs.html#howto>.
1930 To compile this driver as a module, choose M here and read
1931 <file:Documentation/networking/net-modules.txt>. The module will be
1935 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1936 depends on PCI && EXPERIMENTAL
1939 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1940 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1941 used by the Beowulf Linux cluster project. See
1942 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1943 information about this driver in particular and Beowulf in general.
1945 To compile this driver as a module, choose M here: the module
1946 will be called yellowfin. This is recommended.
1949 tristate "Realtek 8169 gigabit ethernet support"
1953 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1955 To compile this driver as a module, choose M here: the module
1956 will be called r8169. This is recommended.
1959 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1960 depends on R8169 && EXPERIMENTAL
1962 NAPI is a new driver API designed to reduce CPU and interrupt load
1963 when the driver is receiving lots of packets from the card. It is
1964 still somewhat experimental and thus not yet enabled by default.
1966 If your estimated Rx load is 10kpps or more, or if the card will be
1967 deployed on potentially unfriendly networks (e.g. in a firewall),
1970 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1977 depends on R8169 && VLAN_8021Q
1979 Say Y here for the r8169 driver to support the functions required
1980 by the kernel 802.1Q code.
1985 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
1988 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1989 compliant Gigabit Ethernet Adapter. The following adapters are supported
1991 - 3Com 3C940 Gigabit LOM Ethernet Adapter
1992 - 3Com 3C941 Gigabit LOM Ethernet Adapter
1993 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
1994 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
1995 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
1996 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
1997 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
1998 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
1999 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2000 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2001 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2002 - DGE-530T Gigabit Ethernet Adapter
2003 - EG1032 v2 Instant Gigabit Network Adapter
2004 - EG1064 v2 Instant Gigabit Network Adapter
2005 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2006 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2007 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2008 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2009 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2010 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2011 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2012 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2013 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2014 - Marvell RDK-8001 Adapter
2015 - Marvell RDK-8002 Adapter
2016 - Marvell RDK-8003 Adapter
2017 - Marvell RDK-8004 Adapter
2018 - Marvell RDK-8006 Adapter
2019 - Marvell RDK-8007 Adapter
2020 - Marvell RDK-8008 Adapter
2021 - Marvell RDK-8009 Adapter
2022 - Marvell RDK-8010 Adapter
2023 - Marvell RDK-8011 Adapter
2024 - Marvell RDK-8012 Adapter
2025 - Marvell RDK-8052 Adapter
2026 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2027 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2028 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2029 - SK-9521 10/100/1000Base-T Adapter
2030 - SK-9521 V2.0 10/100/1000Base-T Adapter
2031 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2032 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2033 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2034 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2035 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2036 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2037 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2038 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2039 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2040 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2041 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2042 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2043 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2044 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2045 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2046 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2047 - SMC EZ Card 1000 (SMC9452TXV.2)
2049 The adapters support Jumbo Frames.
2050 The dual link adapters support link-failover and dual port features.
2051 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2052 the scatter-gather functionality with sendfile(). Please refer to
2053 <file:Documentation/networking/sk98lin.txt> for more information about
2054 optional driver parameters.
2055 Questions concerning this driver may be addressed to:
2056 <linux@syskonnect.de>
2058 If you want to compile this driver as a module ( = code which can be
2059 inserted in and removed from the running kernel whenever you want),
2060 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2061 be called sk98lin. This is recommended.
2064 tristate "VIA Velocity support"
2065 depends on NET_PCI && PCI
2070 If you have a VIA "Velocity" based network card say Y here.
2072 To compile this driver as a module, choose M here. The module
2073 will be called via-velocity.
2076 tristate "Broadcom Tigon3 support"
2079 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2081 To compile this driver as a module, choose M here: the module
2082 will be called tg3. This is recommended.
2085 tristate "Gianfar Ethernet"
2088 This driver supports the Gigabit TSEC on the MPC85xx
2089 family of chips, and the FEC on the 8540
2096 tristate "MV-643XX Ethernet support"
2097 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX
2099 This driver supports the gigabit Ethernet on the Marvell MV643XX
2100 chipset which is used in the Momenco Ocelot C and Jaguar ATX.
2102 config MV643XX_ETH_0
2103 bool "MV-643XX Port 0"
2104 depends on MV643XX_ETH
2106 This enables support for Port 0 of the Marvell MV643XX Gigabit
2109 config MV643XX_ETH_1
2110 bool "MV-643XX Port 1"
2111 depends on MV643XX_ETH
2113 This enables support for Port 1 of the Marvell MV643XX Gigabit
2116 config MV643XX_ETH_2
2117 bool "MV-643XX Port 2"
2118 depends on MV643XX_ETH
2120 This enables support for Port 2 of the Marvell MV643XX Gigabit
2126 # 10 Gigabit Ethernet
2129 menu "Ethernet (10000 Mbit)"
2130 depends on NETDEVICES
2133 tristate "Intel(R) PRO/10GbE support"
2136 This driver supports Intel(R) PRO/10GbE family of
2137 adapters. For more information on how to identify your adapter, go
2138 to the Adapter & Driver ID Guide at:
2140 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2142 For general information and support, go to the Intel support
2145 <http://support.intel.com>
2147 More specific information on configuring the driver is in
2148 <file:Documentation/networking/ixgb.txt>.
2150 To compile this driver as a module, choose M here and read
2151 <file:Documentation/networking/net-modules.txt>. The module
2152 will be called ixgb.
2155 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2156 depends on IXGB && EXPERIMENTAL
2158 NAPI is a new driver API designed to reduce CPU and interrupt load
2159 when the driver is receiving lots of packets from the card. It is
2160 still somewhat experimental and thus not yet enabled by default.
2162 If your estimated Rx load is 10kpps or more, or if the card will be
2163 deployed on potentially unfriendly networks (e.g. in a firewall),
2166 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2172 tristate "S2IO 10Gbe XFrame NIC"
2175 This driver supports the 10Gbe XFrame NIC of S2IO.
2176 For help regarding driver compilation, installation and
2177 tuning please look into ~/drivers/net/s2io/README.txt.
2180 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2181 depends on S2IO && EXPERIMENTAL
2183 NAPI is a new driver API designed to reduce CPU and interrupt load
2184 when the driver is receiving lots of packets from the card. It is
2185 still somewhat experimental and thus not yet enabled by default.
2187 If your estimated Rx load is 10kpps or more, or if the card will be
2188 deployed on potentially unfriendly networks (e.g. in a firewall),
2191 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2197 bool "Use 2 Buffer Mode on Rx side."
2200 On enabling the 2 buffer mode, the received frame will be
2201 split into 2 parts before being DMA'ed to the hosts memory.
2202 The parts are the ethernet header and ethernet payload.
2203 This is useful on systems where DMA'ing to to unaligned
2204 physical memory loactions comes with a heavy price.
2205 If not sure please say N.
2209 source "drivers/net/tokenring/Kconfig"
2211 source "drivers/net/wireless/Kconfig"
2213 source "drivers/net/pcmcia/Kconfig"
2215 source "drivers/net/wan/Kconfig"
2217 source "drivers/atm/Kconfig"
2219 source "drivers/s390/net/Kconfig"
2222 tristate "iSeries Virtual Ethernet driver support"
2223 depends on NETDEVICES && PPC_ISERIES
2226 bool "FDDI driver support"
2227 depends on NETDEVICES && (PCI || EISA)
2229 Fiber Distributed Data Interface is a high speed local area network
2230 design; essentially a replacement for high speed Ethernet. FDDI can
2231 run over copper or fiber. If you are connected to such a network and
2232 want a driver for the FDDI card in your computer, say Y here (and
2233 then also Y to the driver for your FDDI card, below). Most people
2237 tristate "Digital DEFEA and DEFPA adapter support"
2238 depends on FDDI && (PCI || EISA)
2240 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2241 (DEFPA) controllers which can connect you to a local FDDI network.
2244 tristate "SysKonnect FDDI PCI support"
2245 depends on FDDI && PCI
2247 Say Y here if you have a SysKonnect FDDI PCI adapter.
2248 The following adapters are supported by this driver:
2249 - SK-5521 (SK-NET FDDI-UP)
2250 - SK-5522 (SK-NET FDDI-UP DAS)
2251 - SK-5541 (SK-NET FDDI-FP)
2252 - SK-5543 (SK-NET FDDI-LP)
2253 - SK-5544 (SK-NET FDDI-LP DAS)
2254 - SK-5821 (SK-NET FDDI-UP64)
2255 - SK-5822 (SK-NET FDDI-UP64 DAS)
2256 - SK-5841 (SK-NET FDDI-FP64)
2257 - SK-5843 (SK-NET FDDI-LP64)
2258 - SK-5844 (SK-NET FDDI-LP64 DAS)
2259 - Netelligent 100 FDDI DAS Fibre SC
2260 - Netelligent 100 FDDI SAS Fibre SC
2261 - Netelligent 100 FDDI DAS UTP
2262 - Netelligent 100 FDDI SAS UTP
2263 - Netelligent 100 FDDI SAS Fibre MIC
2265 Read <file:Documentation/networking/skfp.txt> for information about
2268 Questions concerning this driver can be addressed to:
2269 <linux@syskonnect.de>
2271 To compile this driver as a module, choose M here: the module
2272 will be called skfp. This is recommended.
2275 bool "HIPPI driver support (EXPERIMENTAL)"
2276 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2278 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2279 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2280 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2281 single-mode). HIPPI networks are commonly used for clusters and to
2282 connect to super computers. If you are connected to a HIPPI network
2283 and have a HIPPI network card in your computer that you want to use
2284 under Linux, say Y here (you must also remember to enable the driver
2285 for your HIPPI card below). Most people will say N here.
2288 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2289 depends on HIPPI && PCI
2291 Say Y here if this is your PCI HIPPI network card.
2293 To compile this driver as a module, choose M here: the module
2294 will be called rrunner. If unsure, say N.
2296 config ROADRUNNER_LARGE_RINGS
2297 bool "Use large TX/RX rings (EXPERIMENTAL)"
2298 depends on ROADRUNNER
2300 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2301 of additional memory to allow for fastest operation, both for
2302 transmitting and receiving. This memory cannot be used by any other
2303 kernel code or by user space programs. Say Y here only if you have
2307 tristate "PLIP (parallel port) support"
2308 depends on NETDEVICES && PARPORT
2310 PLIP (Parallel Line Internet Protocol) is used to create a
2311 reasonably fast mini network consisting of two (or, rarely, more)
2312 local machines. A PLIP link from a Linux box is a popular means to
2313 install a Linux distribution on a machine which doesn't have a
2314 CD-ROM drive (a minimal system has to be transferred with floppies
2315 first). The kernels on both machines need to have this PLIP option
2316 enabled for this to work.
2318 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2319 ports (the connectors at the computers with 25 holes) are connected
2320 with "null printer" or "Turbo Laplink" cables which can transmit 4
2321 bits at a time (mode 0) or with special PLIP cables, to be used on
2322 bidirectional parallel ports only, which can transmit 8 bits at a
2323 time (mode 1); you can find the wiring of these cables in
2324 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2325 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2326 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2327 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2328 and winsock or NCSA's telnet.
2330 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2331 as the NET-3-HOWTO, both available from
2332 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2333 protocol has been changed and this PLIP driver won't work together
2334 with the PLIP support in Linux versions 1.0.x. This option enlarges
2335 your kernel by about 8 KB.
2337 To compile this driver as a module, choose M here and read
2338 <file:Documentation/networking/net-modules.txt>. The module will be
2339 called plip. If unsure, say Y or M, in case you buy a laptop
2343 tristate "PPP (point-to-point protocol) support"
2344 depends on NETDEVICES
2346 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2347 the same purpose: sending Internet traffic over telephone (and other
2348 serial) lines. Ask your access provider if they support it, because
2349 otherwise you can't use it; most Internet access providers these
2350 days support PPP rather than SLIP.
2352 To use PPP, you need an additional program called pppd as described
2353 in the PPP-HOWTO, available at
2354 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2355 the version of pppd recommended in <file:Documentation/Changes>.
2356 The PPP option enlarges your kernel by about 16 KB.
2358 There are actually two versions of PPP: the traditional PPP for
2359 asynchronous lines, such as regular analog phone lines, and
2360 synchronous PPP which can be used over digital ISDN lines for
2361 example. If you want to use PPP over phone lines or other
2362 asynchronous serial lines, you need to say Y (or M) here and also to
2363 the next option, "PPP support for async serial ports". For PPP over
2364 synchronous lines, you should say Y (or M) here and to "Support
2365 synchronous PPP", below.
2367 If you said Y to "Version information on all symbols" above, then
2368 you cannot compile the PPP driver into the kernel; you can then only
2369 compile it as a module. To compile this driver as a module, choose M
2370 here and read <file:Documentation/networking/net-modules.txt>.
2371 The module will be called ppp_generic.
2373 config PPP_MULTILINK
2374 bool "PPP multilink support (EXPERIMENTAL)"
2375 depends on PPP && EXPERIMENTAL
2377 PPP multilink is a protocol (defined in RFC 1990) which allows you
2378 to combine several (logical or physical) lines into one logical PPP
2379 connection, so that you can utilize your full bandwidth.
2381 This has to be supported at the other end as well and you need a
2382 version of the pppd daemon which understands the multilink protocol.
2387 bool "PPP filtering"
2390 Say Y here if you want to be able to filter the packets passing over
2391 PPP interfaces. This allows you to control which packets count as
2392 activity (i.e. which packets will reset the idle timer or bring up
2393 a demand-dialled link) and which packets are to be dropped entirely.
2394 You need to say Y here if you wish to use the pass-filter and
2395 active-filter options to pppd.
2400 tristate "PPP support for async serial ports"
2404 Say Y (or M) here if you want to be able to use PPP over standard
2405 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2406 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2409 To compile this driver as a module, choose M here.
2414 tristate "PPP support for sync tty ports"
2417 Say Y (or M) here if you want to be able to use PPP over synchronous
2418 (HDLC) tty devices, such as the SyncLink adapter. These devices
2419 are often used for high-speed leased lines like T1/E1.
2421 To compile this driver as a module, choose M here.
2424 tristate "PPP Deflate compression"
2429 Support for the Deflate compression method for PPP, which uses the
2430 Deflate algorithm (the same algorithm that gzip uses) to compress
2431 each PPP packet before it is sent over the wire. The machine at the
2432 other end of the PPP link (usually your ISP) has to support the
2433 Deflate compression method as well for this to be useful. Even if
2434 they don't support it, it is safe to say Y here.
2436 To compile this driver as a module, choose M here.
2439 tristate "PPP BSD-Compress compression"
2442 Support for the BSD-Compress compression method for PPP, which uses
2443 the LZW compression method to compress each PPP packet before it is
2444 sent over the wire. The machine at the other end of the PPP link
2445 (usually your ISP) has to support the BSD-Compress compression
2446 method as well for this to be useful. Even if they don't support it,
2447 it is safe to say Y here.
2449 The PPP Deflate compression method ("PPP Deflate compression",
2450 above) is preferable to BSD-Compress, because it compresses better
2453 Note that the BSD compression code will always be compiled as a
2454 module; it is called bsd_comp and will show up in the directory
2455 modules once you have said "make modules". If unsure, say N.
2458 tristate "PPP over Ethernet (EXPERIMENTAL)"
2459 depends on EXPERIMENTAL && PPP
2461 Support for PPP over Ethernet.
2463 This driver requires the latest version of pppd from the CVS
2464 repository at cvs.samba.org. Alternatively, see the
2465 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2466 which contains instruction on how to use this driver (under
2467 the heading "Kernel mode PPPoE").
2470 tristate "PPP over ATM"
2471 depends on ATM && PPP
2473 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2474 This implementation does not yet comply with section 8 of RFC2364,
2475 which can lead to bad results if the ATM peer loses state and
2476 changes its encapsulation unilaterally.
2479 tristate "SLIP (serial line) support"
2480 depends on NETDEVICES
2482 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2483 connect to your Internet service provider or to connect to some
2484 other local Unix box or if you want to configure your Linux box as a
2485 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2486 Internet Protocol) is a protocol used to send Internet traffic over
2487 serial connections such as telephone lines or null modem cables;
2488 nowadays, the protocol PPP is more commonly used for this same
2491 Normally, your access provider has to support SLIP in order for you
2492 to be able to use it, but there is now a SLIP emulator called SLiRP
2493 around (available from
2494 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2495 allows you to use SLIP over a regular dial up shell connection. If
2496 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2497 NET-3-HOWTO, available from
2498 <http://www.tldp.org/docs.html#howto>, explains how to
2499 configure SLIP. Note that you don't need this option if you just
2500 want to run term (term is a program which gives you almost full
2501 Internet connectivity if you have a regular dial up shell account on
2502 some Internet connected Unix computer. Read
2503 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2504 support will enlarge your kernel by about 4 KB. If unsure, say N.
2506 To compile this driver as a module, choose M here and read
2507 <file:Documentation/networking/net-modules.txt>. The module will be
2510 config SLIP_COMPRESSED
2511 bool "CSLIP compressed headers"
2514 This protocol is faster than SLIP because it uses compression on the
2515 TCP/IP headers (not on the data itself), but it has to be supported
2516 on both ends. Ask your access provider if you are not sure and
2517 answer Y, just in case. You will still be able to use plain SLIP. If
2518 you plan to use SLiRP, the SLIP emulator (available from
2519 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2520 allows you to use SLIP over a regular dial up shell connection, you
2521 definitely want to say Y here. The NET-3-HOWTO, available from
2522 <http://www.tldp.org/docs.html#howto>, explains how to configure
2523 CSLIP. This won't enlarge your kernel.
2526 bool "Keepalive and linefill"
2529 Adds additional capabilities to the SLIP driver to support the
2530 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2533 config SLIP_MODE_SLIP6
2534 bool "Six bit SLIP encapsulation"
2537 Just occasionally you may need to run IP over hostile serial
2538 networks that don't pass all control characters or are only seven
2539 bit. Saying Y here adds an extra mode you can use with SLIP:
2540 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2541 the serial device. Naturally, this has to be supported at the other
2542 end of the link as well. It's good enough, for example, to run IP
2543 over the async ports of a Camtec JNT Pad. If unsure, say N.
2546 bool "Fibre Channel driver support"
2547 depends on NETDEVICES && SCSI && PCI
2549 Fibre Channel is a high speed serial protocol mainly used to connect
2550 large storage devices to the computer; it is compatible with and
2551 intended to replace SCSI.
2553 If you intend to use Fibre Channel, you need to have a Fibre channel
2554 adaptor card in your computer; say Y here and to the driver for your
2555 adaptor below. You also should have said Y to "SCSI support" and
2556 "SCSI generic support".
2559 tristate "Interphase 5526 Tachyon chipset based adapter support"
2560 depends on NET_FC && SCSI && PCI && BROKEN
2562 Say Y here if you have a Fibre Channel adaptor of this kind.
2564 To compile this driver as a module, choose M here: the module
2565 will be called iph5526.
2568 tristate "Traffic Shaper (EXPERIMENTAL)"
2569 depends on NETDEVICES && EXPERIMENTAL
2571 The traffic shaper is a virtual network device that allows you to
2572 limit the rate of outgoing data flow over some other network device.
2573 The traffic that you want to slow down can then be routed through
2574 these virtual devices. See
2575 <file:Documentation/networking/shaper.txt> for more information.
2577 An alternative to this traffic shaper is the experimental
2578 Class-Based Queueing (CBQ) scheduling support which you get if you
2579 say Y to "QoS and/or fair queueing" above.
2581 To set up and configure shaper devices, you need the shapecfg
2582 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2585 To compile this driver as a module, choose M here: the module
2586 will be called shaper. If unsure, say N.
2589 tristate "Network console logging support (EXPERIMENTAL)"
2590 depends on NETDEVICES && EXPERIMENTAL
2592 If you want to log kernel messages over the network, enable this.
2593 See <file:Documentation/networking/netconsole.txt> for details.