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"
88 TUN/TAP provides packet reception and transmission for user space
89 programs. It can be viewed as a simple Point-to-Point or Ethernet
90 device, which instead of receiving packets from a physical media,
91 receives them from user space program and instead of sending packets
92 via physical media writes them to the user space program.
94 When a program opens /dev/net/tun, driver creates and registers
95 corresponding net device tunX or tapX. After a program closed above
96 devices, driver will automatically delete tunXX or tapXX device and
97 all routes corresponding to it.
99 Please read <file:Documentation/networking/tuntap.txt> for more
102 To compile this driver as a module, choose M here: the module
105 If you don't know what to use this for, you don't need it.
108 tristate "Ethertap network tap"
109 depends on NETDEVICES && EXPERIMENTAL && NETLINK_DEV
111 If you say Y here (and have said Y to "Kernel/User network link
112 driver", above) and create a character special file /dev/tap0 with
113 major number 36 and minor number 16 using mknod ("man mknod"), you
114 will be able to have a user space program read and write raw
115 Ethernet frames from/to that special file. tap0 can be configured
116 with ifconfig and route like any other Ethernet device but it is not
117 connected to any physical LAN; everything written by the user to
118 /dev/tap0 is treated by the kernel as if it had come in from a LAN
119 to the device tap0; everything the kernel wants to send out over the
120 device tap0 can instead be read by the user from /dev/tap0: the user
121 mode program replaces the LAN that would be attached to an ordinary
122 Ethernet device. Please read the file
123 <file:Documentation/networking/ethertap.txt> for more information.
125 To compile this driver as a module, choose M here: the module
126 will be called ethertap.
128 If you don't know what to use this for, you don't need it.
131 tristate "General Instruments Surfboard 1000"
132 depends on NETDEVICES && PNP
134 This is a driver for the General Instrument (also known as
135 NextLevel) SURFboard 1000 internal
136 cable modem. This is an ISA card which is used by a number of cable
137 TV companies to provide cable modem access. It's a one-way
138 downstream-only cable modem, meaning that your upstream net link is
139 provided by your regular phone modem.
141 At present this driver only compiles as a module, so say M here if
142 you have this card. The module will be called sb1000. Then read
143 <file:Documentation/networking/README.sb1000> for information on how
144 to use this module, as it needs special ppp scripts for establishing
145 a connection. Further documentation and the necessary scripts can be
148 <http://www.jacksonville.net/~fventuri/>
149 <http://home.adelphia.net/~siglercm/sb1000.html>
150 <http://linuxpower.cx/~cable/>
152 If you don't have this card, of course say N.
155 source "drivers/net/arcnet/Kconfig"
162 menu "Ethernet (10 or 100Mbit)"
163 depends on NETDEVICES
166 bool "Ethernet (10 or 100Mbit)"
168 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
169 type of Local Area Network (LAN) in universities and companies.
171 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
172 coaxial cable, linking computers in a chain), 10BASE-T or twisted
173 pair (10 Mbps over twisted pair cable, linking computers to central
174 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
175 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
176 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
177 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
178 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
179 Ethernet (1 Gbps over optical fiber or short copper links).
181 If your Linux machine will be connected to an Ethernet and you have
182 an Ethernet network interface card (NIC) installed in your computer,
183 say Y here and read the Ethernet-HOWTO, available from
184 <http://www.tldp.org/docs.html#howto>. You will then also have
185 to say Y to the driver for your particular NIC.
187 Note that the answer to this question won't directly affect the
188 kernel: saying N will just cause the configurator to skip all
189 the questions about Ethernet network cards. If unsure, say N.
192 tristate "Generic Media Independent Interface device support"
193 depends on NET_ETHERNET
195 Most ethernet controllers have MII transceiver either as an external
196 or internal device. It is safe to say Y or M here even if your
197 ethernet card lack MII.
199 source "drivers/net/arm/Kconfig"
202 tristate "MACE (Power Mac ethernet) support"
203 depends on NET_ETHERNET && PPC_PMAC
206 Power Macintoshes and clones with Ethernet built-in on the
207 motherboard will usually use a MACE (Medium Access Control for
208 Ethernet) interface. Say Y to include support for the MACE chip.
210 To compile this driver as a module, choose M here: the module
213 config MACE_AAUI_PORT
214 bool "Use AAUI port instead of TP by default"
217 Some Apple machines (notably the Apple Network Server) which use the
218 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
219 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
220 Y here if you have such a machine. If unsure, say N.
221 The driver will default to AAUI on ANS anyway, and if you use it as
222 a module, you can provide the port_aaui=0|1 to force the driver.
225 tristate "BMAC (G3 ethernet) support"
226 depends on NET_ETHERNET && PPC_PMAC
229 Say Y for support of BMAC Ethernet interfaces. These are used on G3
232 To compile this driver as a module, choose M here: the module
236 tristate "National DP83902AV (Oak ethernet) support"
237 depends on NET_ETHERNET && PPC
240 Say Y if your machine has this type of Ethernet network card.
242 To compile this driver as a module, choose M here: the module
243 will be called oaknet.
246 tristate "Ariadne support"
247 depends on NET_ETHERNET && ZORRO
249 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
252 To compile this driver as a module, choose M here: the module
253 will be called ariadne.
256 tristate "A2065 support"
257 depends on NET_ETHERNET && ZORRO
260 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
263 To compile this driver as a module, choose M here: the module
264 will be called a2065.
267 tristate "Hydra support"
268 depends on NET_ETHERNET && ZORRO
271 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
273 To compile this driver as a module, choose M here: the module
274 will be called hydra.
277 tristate "Zorro NS8390-based Ethernet support"
278 depends on NET_ETHERNET && ZORRO
281 This driver is for Zorro Ethernet cards using an NS8390-compatible
282 chipset, like the Village Tronic Ariadne II and the Individual
283 Computers X-Surf Ethernet cards. If you have such a card, say Y.
286 To compile this driver as a module, choose M here: the module
287 will be called zorro8390.
290 tristate "PCMCIA NE2000 support"
291 depends on NETDEVICES && AMIGA_PCMCIA
294 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
297 To compile this driver as a module, choose M here: the module
301 tristate "Apollo 3c505 support"
302 depends on NETDEVICES && APOLLO
304 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
305 If you don't have one made for Apollos, you can use one from a PC,
306 except that your Apollo won't be able to boot from it (because the
307 code in the ROM will be for a PC).
310 bool "Macintosh NS 8390 based ethernet cards"
311 depends on NETDEVICES && MAC
314 If you want to include a driver to support Nubus or LC-PDS
315 Ethernet cards using an NS8390 chipset or its equivalent, say Y
316 and read the Ethernet-HOWTO, available from
317 <http://www.tldp.org/docs.html#howto>.
320 tristate "Macintosh CS89x0 based ethernet cards"
321 depends on NETDEVICES && MAC && BROKEN
323 Support for CS89x0 chipset based Ethernet cards. If you have a
324 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
325 read the Ethernet-HOWTO, available from
326 <http://www.tldp.org/docs.html#howto>.
328 To compile this driver as a module, choose M here and read
329 <file:Documentation/networking/net-modules.txt>. This module will
333 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
334 depends on NETDEVICES && MAC
336 Support for NatSemi SONIC based Ethernet devices. This includes
337 the onboard Ethernet in many Quadras as well as some LC-PDS,
338 a few Nubus and all known Comm Slot Ethernet cards. If you have
339 one of these say Y and read the Ethernet-HOWTO, available from
340 <http://www.tldp.org/docs.html#howto>.
342 To compile this driver as a module, choose M here and read
343 <file:Documentation/networking/net-modules.txt>. This module will
347 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
348 depends on NETDEVICES && MAC && EXPERIMENTAL
351 Support for the onboard AMD 79C940 MACE Ethernet controller used in
352 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
353 say Y and read the Ethernet-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>.
357 tristate "MVME147 (Lance) Ethernet support"
358 depends on NETDEVICES && MVME147
361 Support for the on-board Ethernet interface on the Motorola MVME147
362 single-board computer. Say Y here to include the
363 driver for this chip in your kernel.
364 To compile this driver as a module, choose M here.
367 tristate "MVME16x Ethernet support"
368 depends on NETDEVICES && MVME16x
370 This is the driver for the Ethernet interface on the Motorola
371 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
372 driver for this chip in your kernel.
373 To compile this driver as a module, choose M here.
376 tristate "BVME6000 Ethernet support"
377 depends on NETDEVICES && BVME6000
379 This is the driver for the Ethernet interface on BVME4000 and
380 BVME6000 VME boards. Say Y here to include the driver for this chip
382 To compile this driver as a module, choose M here.
385 tristate "Atari Lance support"
386 depends on NETDEVICES && ATARI
388 Say Y to include support for several Atari Ethernet adapters based
389 on the AMD Lance chipset: RieblCard (with or without battery), or
390 PAMCard VME (also the version by Rhotron, with different addresses).
393 tristate "BioNet-100 support"
394 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
396 Say Y to include support for BioData's BioNet-100 Ethernet adapter
397 for the ACSI port. The driver works (has to work...) with a polled
398 I/O scheme, so it's rather slow :-(
401 tristate "PAMsNet support"
402 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
404 Say Y to include support for the PAMsNet Ethernet adapter for the
405 ACSI port ("ACSI node"). The driver works (has to work...) with a
406 polled I/O scheme, so it's rather slow :-(
409 tristate "Sun3/Sun3x on-board LANCE support"
410 depends on NETDEVICES && (SUN3 || SUN3X)
412 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
413 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
414 here to compile in the Linux driver for this and enable Ethernet.
415 General Linux information on the Sun 3 and 3x series (now
417 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
419 If you're not building a kernel for a Sun 3, say N.
422 tristate "Sun3 on-board Intel 82586 support"
423 depends on NETDEVICES && SUN3
425 This driver enables support for the on-board Intel 82586 based
426 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
427 that this driver does not support 82586-based adapters on additional
431 bool "HP on-board LANCE support"
432 depends on NETDEVICES && HP300
435 If you want to use the builtin "LANCE" Ethernet controller on an
436 HP300 machine, say Y here.
439 tristate "Lasi ethernet"
440 depends on NET_ETHERNET && PARISC && GSC_LASI
442 Say Y here to support the on-board Intel 82596 ethernet controller
443 built into Hewlett-Packard PA-RISC machines.
445 config MIPS_JAZZ_SONIC
446 tristate "MIPS JAZZ onboard SONIC Ethernet support"
447 depends on NET_ETHERNET && MIPS_JAZZ
449 This is the driver for the onboard card of MIPS Magnum 4000,
450 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
452 config MIPS_GT96100ETH
453 bool "MIPS GT96100 Ethernet support"
454 depends on NET_ETHERNET && MIPS_GT96100
456 Say Y here to support the Ethernet subsystem on your GT96100 card.
458 config MIPS_AU1X00_ENET
459 bool "MIPS AU1000 Ethernet support"
460 depends on NET_ETHERNET && SOC_AU1X00
463 If you have an Alchemy Semi AU1X00 based system
464 say Y. Otherwise, say N.
466 config NET_SB1250_MAC
467 tristate "SB1250 Ethernet support"
468 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
471 bool "SGI IOC3 Ethernet"
472 depends on NET_ETHERNET && SGI_IP27
476 If you have a network (Ethernet) card of this type, say Y and read
477 the Ethernet-HOWTO, available from
478 <http://www.tldp.org/docs.html#howto>.
480 config SGI_IOC3_ETH_HW_RX_CSUM
481 bool "Receive hardware checksums"
482 depends on SGI_IOC3_ETH && INET
485 The SGI IOC3 network adapter supports TCP and UDP checksums in
486 hardware to offload processing of these checksums from the CPU. At
487 the moment only acceleration of IPv4 is supported. This option
488 enables offloading for checksums on receive. If unsure, say Y.
490 config SGI_IOC3_ETH_HW_TX_CSUM
491 bool "Transmit hardware checksums"
492 depends on SGI_IOC3_ETH && INET
495 The SGI IOC3 network adapter supports TCP and UDP checksums in
496 hardware to offload processing of these checksums from the CPU. At
497 the moment only acceleration of IPv4 is supported. This option
498 enables offloading for checksums on transmit. If unsure, say Y.
500 config SGI_O2MACE_ETH
501 tristate "SGI O2 MACE Fast Ethernet support"
502 depends on NET_ETHERNET && SGI_IP32=y
505 tristate "National DP83902AV support"
506 depends on NET_ETHERNET && SUPERH
509 Support for cards based on the National Semiconductor DP83902AV
510 ST-NIC Serial Network Interface Controller for Twisted Pair. This
511 is a 10Mbit/sec Ethernet controller. Product overview and specs at
512 <http://www.national.com/pf/DP/DP83902A.html>.
517 tristate "Sun LANCE support"
518 depends on NET_ETHERNET && SBUS
521 This driver supports the "le" interface present on all 32-bit Sparc
522 systems, on some older Ultra systems and as an Sbus option. These
523 cards are based on the AMD Lance chipset, which is better known
524 via the NE2100 cards.
526 To compile this driver as a module, choose M here: the module
527 will be called sunlance.
530 tristate "Sun Happy Meal 10/100baseT support"
531 depends on NET_ETHERNET && (SBUS || PCI)
534 This driver supports the "hme" interface present on most Ultra
535 systems and as an option on older Sbus systems. This driver supports
536 both PCI and Sbus devices. This driver also supports the "qfe" quad
537 100baseT device available in both PCI and Sbus configurations.
539 To compile this driver as a module, choose M here: the module
540 will be called sunhme.
543 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
544 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
547 This driver supports the "be" interface available as an Sbus option.
548 This is Sun's older 100baseT Ethernet device.
550 To compile this driver as a module, choose M here: the module
551 will be called sunbmac.
554 tristate "Sun QuadEthernet support"
555 depends on NET_ETHERNET && SBUS
558 This driver supports the "qe" 10baseT Ethernet device, available as
559 an Sbus option. Note that this is not the same as Quad FastEthernet
560 "qfe" which is supported by the Happy Meal driver instead.
562 To compile this driver as a module, choose M here: the module
563 will be called sunqe.
566 tristate "Sun GEM support"
567 depends on NET_ETHERNET && PCI
570 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
571 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
573 config NET_VENDOR_3COM
575 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
577 If you have a network (Ethernet) card belonging to this class, say Y
578 and read the Ethernet-HOWTO, available from
579 <http://www.tldp.org/docs.html#howto>.
581 Note that the answer to this question doesn't directly affect the
582 kernel: saying N will just cause the configurator to skip all
583 the questions about 3COM cards. If you say Y, you will be asked for
584 your specific card in the following questions.
587 tristate "3c501 \"EtherLink\" support"
588 depends on NET_VENDOR_3COM && ISA
590 If you have a network (Ethernet) card of this type, say Y and read
591 the Ethernet-HOWTO, available from
592 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
593 new card, since the 3c501 is slow, broken, and obsolete: you will
594 have problems. Some people suggest to ping ("man ping") a nearby
595 machine every minute ("man cron") when using this card.
597 To compile this driver as a module, choose M here and read
598 <file:Documentation/networking/net-modules.txt>. The module
599 will be called 3c501.
602 tristate "3c503 \"EtherLink II\" support"
603 depends on NET_VENDOR_3COM && ISA
606 If you have a network (Ethernet) card of this type, say Y and read
607 the Ethernet-HOWTO, available from
608 <http://www.tldp.org/docs.html#howto>.
610 To compile this driver as a module, choose M here and read
611 <file:Documentation/networking/net-modules.txt>. The module
612 will be called 3c503.
615 tristate "3c505 \"EtherLink Plus\" support"
616 depends on NET_VENDOR_3COM && ISA
618 Information about this network (Ethernet) card can be found in
619 <file:Documentation/networking/3c505.txt>. If you have a card of
620 this type, say Y and read the Ethernet-HOWTO, available from
621 <http://www.tldp.org/docs.html#howto>.
623 To compile this driver as a module, choose M here and read
624 <file:Documentation/networking/net-modules.txt>. The module
625 will be called 3c505.
628 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
629 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
631 If you have a network (Ethernet) card of this type, say Y and read
632 the Ethernet-HOWTO, available from
633 <http://www.tldp.org/docs.html#howto>.
635 To compile this driver as a module, choose M here and read
636 <file:Documentation/networking/net-modules.txt>. The module
637 will be called 3c507.
640 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support"
641 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
643 If you have a network (Ethernet) card belonging to the 3Com
644 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
645 from <http://www.tldp.org/docs.html#howto>.
647 If your card is not working you may need to use the DOS
648 setup disk to disable Plug & Play mode, and to select the default
651 To compile this driver as a module, choose M here and read
652 <file:Documentation/networking/net-modules.txt>. The module
653 will be called 3c509.
656 tristate "3c515 ISA \"Fast EtherLink\""
657 depends on NET_VENDOR_3COM && (ISA || EISA)
659 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
660 network card, say Y and read the Ethernet-HOWTO, available from
661 <http://www.tldp.org/docs.html#howto>.
663 To compile this driver as a module, choose M here and read
664 <file:Documentation/networking/net-modules.txt>. The module
665 will be called 3c515.
668 tristate "3c523 \"EtherLink/MC\" support"
669 depends on NET_VENDOR_3COM && MCA
671 If you have a network (Ethernet) card of this type, say Y and read
672 the Ethernet-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 To compile this driver as a module, choose M here and read
676 <file:Documentation/networking/net-modules.txt>. The module
677 will be called 3c523.
680 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
681 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
683 If you have a network (Ethernet) card of this type, say Y and read
684 the Ethernet-HOWTO, available from
685 <http://www.tldp.org/docs.html#howto>.
687 To compile this driver as a module, choose M here and read
688 <file:Documentation/networking/net-modules.txt>. The module
689 will be called 3c527.
692 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
693 depends on NET_VENDOR_3COM && (PCI || EISA)
695 This option enables driver support for a large number of 10mbps and
696 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
698 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
699 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
700 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
701 "Tornado" (3c905) PCI
702 "Hurricane" (3c555/3cSOHO) PCI
704 If you have such a card, say Y and read the Ethernet-HOWTO,
705 available from <http://www.tldp.org/docs.html#howto>. More
706 specific information is in
707 <file:Documentation/networking/vortex.txt> and in the comments at
708 the beginning of <file:drivers/net/3c59x.c>.
710 To compile this support as a module, choose M here and read
711 <file:Documentation/networking/net-modules.txt>.
714 tristate "3cr990 series \"Typhoon\" support"
715 depends on NET_VENDOR_3COM && PCI
718 This option enables driver support for the 3cr990 series of cards:
720 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
721 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
722 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
724 If you have a network (Ethernet) card of this type, say Y and read
725 the Ethernet-HOWTO, available from
726 <http://www.tldp.org/docs.html#howto>.
728 To compile this driver as a module, choose M here and read
729 <file:Documentation/networking/net-modules.txt>. The module
730 will be called typhoon.
733 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
734 depends on NET_ETHERNET && ISA
736 If you have a network (Ethernet) card of this type, say Y and read
737 the Ethernet-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
741 To compile this driver as a module, choose M here: the module
742 will be called lance. This is recommended.
744 config NET_VENDOR_SMC
745 bool "Western Digital/SMC cards"
746 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
748 If you have a network (Ethernet) card belonging to this class, say Y
749 and read the Ethernet-HOWTO, available from
750 <http://www.tldp.org/docs.html#howto>.
752 Note that the answer to this question doesn't directly affect the
753 kernel: saying N will just cause the configurator to skip all
754 the questions about Western Digital cards. If you say Y, you will be
755 asked for your specific card in the following questions.
758 tristate "WD80*3 support"
759 depends on NET_VENDOR_SMC && ISA
762 If you have a network (Ethernet) card of this type, say Y and read
763 the Ethernet-HOWTO, available from
764 <http://www.tldp.org/docs.html#howto>.
766 To compile this driver as a module, choose M here and read
767 <file:Documentation/networking/net-modules.txt>. The module
771 tristate "SMC Ultra MCA support"
772 depends on NET_VENDOR_SMC && MCA
775 If you have a network (Ethernet) card of this type and are running
776 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
777 available from <http://www.tldp.org/docs.html#howto>.
779 To compile this driver as a module, choose M here and read
780 <file:Documentation/networking/net-modules.txt>. The module
781 will be called smc-mca.
784 tristate "SMC Ultra support"
785 depends on NET_VENDOR_SMC && ISA
788 If you have a network (Ethernet) card of this type, say Y and read
789 the Ethernet-HOWTO, available from
790 <http://www.tldp.org/docs.html#howto>.
792 Important: There have been many reports that, with some motherboards
793 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
794 such as some BusLogic models) causes corruption problems with many
795 operating systems. The Linux smc-ultra driver has a work-around for
796 this but keep it in mind if you have such a SCSI card and have
799 To compile this driver as a module, choose M here and read
800 <file:Documentation/networking/net-modules.txt>. The module
801 will be called smc-ultra.
804 tristate "SMC Ultra32 EISA support"
805 depends on NET_VENDOR_SMC && EISA
808 If you have a network (Ethernet) card of this type, say Y and read
809 the Ethernet-HOWTO, available from
810 <http://www.tldp.org/docs.html#howto>.
812 To compile this driver as a module, choose M here and read
813 <file:Documentation/networking/net-modules.txt>. The module
814 will be called smc-ultra32.
817 tristate "SMC 9194 support"
818 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
821 This is support for the SMC9xxx based Ethernet cards. Choose this
822 option if you have a DELL laptop with the docking station, or
823 another SMC9192/9194 based chipset. Say Y if you want it compiled
824 into the kernel, and read the file
825 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
826 available from <http://www.tldp.org/docs.html#howto>.
828 To compile this driver as a module, choose M here and read
829 <file:Documentation/networking/net-modules.txt>. The module
830 will be called smc9194.
832 config NET_VENDOR_RACAL
833 bool "Racal-Interlan (Micom) NI cards"
834 depends on NET_ETHERNET && ISA
836 If you have a network (Ethernet) card belonging to this class, such
837 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
838 available from <http://www.tldp.org/docs.html#howto>.
840 Note that the answer to this question doesn't directly affect the
841 kernel: saying N will just cause the configurator to skip all
842 the questions about NI cards. If you say Y, you will be asked for
843 your specific card in the following questions.
846 tristate "NI5010 support (EXPERIMENTAL)"
847 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
849 If you have a network (Ethernet) card of this type, say Y and read
850 the Ethernet-HOWTO, available from
851 <http://www.tldp.org/docs.html#howto>. Note that this is still
854 To compile this driver as a module, choose M here and read
855 <file:Documentation/networking/net-modules.txt>. The module
856 will be called ni5010.
859 tristate "NI5210 support"
860 depends on NET_VENDOR_RACAL && ISA
862 If you have a network (Ethernet) card of this type, say Y and read
863 the Ethernet-HOWTO, available from
864 <http://www.tldp.org/docs.html#howto>.
866 To compile this driver as a module, choose M here and read
867 <file:Documentation/networking/net-modules.txt>. The module
871 tristate "NI6510 support"
872 depends on NET_VENDOR_RACAL && ISA
874 If you have a network (Ethernet) card of this type, say Y and read
875 the Ethernet-HOWTO, available from
876 <http://www.tldp.org/docs.html#howto>.
878 To compile this driver as a module, choose M here and read
879 <file:Documentation/networking/net-modules.txt>. The module
882 source "drivers/net/tulip/Kconfig"
885 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)"
886 depends on NET_ETHERNET && (ISA || MCA) && EXPERIMENTAL
889 If you have a network (Ethernet) card of this type, say Y and read
890 the Ethernet-HOWTO, available from
891 <http://www.tldp.org/docs.html#howto>.
893 To compile this driver as a module, choose M here and read
894 <file:Documentation/networking/net-modules.txt>. The module
895 will be called at1700.
898 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
899 depends on NET_ETHERNET && (ISA || EISA || MCA)
902 If you have a network (Ethernet) card of this type, say Y and read
903 the Ethernet-HOWTO, available from
904 <http://www.tldp.org/docs.html#howto> as well as
905 <file:drivers/net/depca.c>.
907 To compile this driver as a module, choose M here and read
908 <file:Documentation/networking/net-modules.txt>. The module
909 will be called depca.
912 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
913 depends on NET_ETHERNET && (ISA || EISA || PCI)
915 If you have a network (Ethernet) card of this type, say Y and read
916 the Ethernet-HOWTO, available from
917 <http://www.tldp.org/docs.html#howto>.
919 To compile this driver as a module, choose M here and read
920 <file:Documentation/networking/net-modules.txt>. The module
921 will be called hp100.
924 bool "Other ISA cards"
925 depends on NET_ETHERNET && ISA
927 If your network (Ethernet) card hasn't been mentioned yet and its
928 bus system (that's the way the cards talks to the other components
929 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
930 Make sure you know the name of your card. Read the Ethernet-HOWTO,
931 available from <http://www.tldp.org/docs.html#howto>.
935 Note that the answer to this question doesn't directly affect the
936 kernel: saying N will just cause the configurator to skip all
937 the remaining ISA network card questions. If you say Y, you will be
938 asked for your specific card in the following questions.
941 tristate "Cabletron E21xx support"
945 If you have a network (Ethernet) card of this type, say Y and read
946 the Ethernet-HOWTO, available from
947 <http://www.tldp.org/docs.html#howto>.
949 To compile this driver as a module, choose M here and read
950 <file:Documentation/networking/net-modules.txt>. The module
951 will be called e2100.
954 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
958 This driver supports the DE203, DE204 and DE205 network (Ethernet)
959 cards. If this is for you, say Y and read
960 <file:Documentation/networking/ewrk3.txt> in the kernel source as
961 well as the Ethernet-HOWTO, available from
962 <http://www.tldp.org/docs.html#howto>.
964 To compile this driver as a module, choose M here and read
965 <file:Documentation/networking/net-modules.txt>. The module
966 will be called ewrk3.
969 tristate "EtherExpress 16 support"
972 If you have an EtherExpress16 network (Ethernet) card, say Y and
973 read the Ethernet-HOWTO, available from
974 <http://www.tldp.org/docs.html#howto>. Note that the Intel
975 EtherExpress16 card used to be regarded as a very poor choice
976 because the driver was very unreliable. We now have a new driver
977 that should do better.
979 To compile this driver as a module, choose M here and read
980 <file:Documentation/networking/net-modules.txt>. The module
981 will be called eexpress.
984 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
987 If you have a network (Ethernet) card of this type, say Y. This
988 driver supports intel i82595{FX,TX} based boards. Note however
989 that the EtherExpress PRO/100 Ethernet card has its own separate
990 driver. Please read the Ethernet-HOWTO, available from
991 <http://www.tldp.org/docs.html#howto>.
993 To compile this driver as a module, choose M here and read
994 <file:Documentation/networking/net-modules.txt>. The module
995 will be called eepro.
998 tristate "FMV-181/182/183/184 support (OBSOLETE)"
999 depends on NET_ISA && OBSOLETE
1001 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
1002 say Y and read the Ethernet-HOWTO, available from
1003 <http://www.tldp.org/docs.html#howto>.
1005 If you use an FMV-183 or FMV-184 and it is not working, you may need
1006 to disable Plug & Play mode of the card.
1008 To compile this driver as a module, choose M here and read
1009 <file:Documentation/networking/net-modules.txt>. The module
1010 will be called fmv18x.
1013 tristate "HP PCLAN+ (27247B and 27252A) support"
1017 If you have a network (Ethernet) card of this type, say Y and read
1018 the Ethernet-HOWTO, available from
1019 <http://www.tldp.org/docs.html#howto>.
1021 To compile this driver as a module, choose M here and read
1022 <file:Documentation/networking/net-modules.txt>. The module
1023 will be called hp-plus.
1026 tristate "HP PCLAN (27245 and other 27xxx series) support"
1030 If you have a network (Ethernet) card of this type, say Y and read
1031 the Ethernet-HOWTO, available from
1032 <http://www.tldp.org/docs.html#howto>.
1034 To compile this driver as a module, choose M here and read
1035 <file:Documentation/networking/net-modules.txt>. The module
1039 tristate "LP486E on board Ethernet"
1042 Say Y here to support the 82596-based on-board Ethernet controller
1043 for the Panther motherboard, which is one of the two shipped in the
1044 Intel Professional Workstation.
1047 tristate "ICL EtherTeam 16i/32 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
1056 will be called eth16i.
1059 tristate "NE2000/NE1000 support"
1062 If you have a network (Ethernet) card of this type, say Y and read
1063 the Ethernet-HOWTO, available from
1064 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1065 without a specific driver are compatible with NE2000.
1067 If you have a PCI NE2000 card however, say N here and Y to "PCI
1068 NE2000 support", above. If you have a NE2000 card and are running on
1069 an MCA system (a bus system used on some IBM PS/2 computers and
1070 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1073 To compile this driver as a module, choose M here and read
1074 <file:Documentation/networking/net-modules.txt>. The module
1078 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1079 depends on NET_ISA && EXPERIMENTAL
1081 The Zenith Z-Note notebook computer has a built-in network
1082 (Ethernet) card, and this is the Linux driver for it. Note that the
1083 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1084 by this driver. Read the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1088 tristate "SEEQ8005 support (EXPERIMENTAL)"
1089 depends on NET_ISA && EXPERIMENTAL
1091 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1092 is for you, read the Ethernet-HOWTO, available from
1093 <http://www.tldp.org/docs.html#howto>.
1095 To compile this driver as a module, choose M here and read
1096 <file:Documentation/networking/net-modules.txt>. The module
1097 will be called seeq8005.
1100 tristate "SK_G16 support (OBSOLETE)"
1101 depends on NET_ISA && OBSOLETE
1103 If you have a network (Ethernet) card of this type, say Y and read
1104 the Ethernet-HOWTO, available from
1105 <http://www.tldp.org/docs.html#howto>.
1108 tristate "SKnet MCA support"
1109 depends on NET_ETHERNET && MCA && BROKEN
1111 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1112 support" in order to use this driver. Supported cards are the SKnet
1113 Junior MC2 and the SKnet MC2(+). The driver automatically
1114 distinguishes between the two cards. Note that using multiple boards
1115 of different type hasn't been tested with this driver. Say Y if you
1116 have one of these Ethernet adapters.
1118 To compile this driver as a module, choose M here and read
1119 <file:Documentation/networking/net-modules.txt>. The module
1120 will be called sk_mca.
1123 tristate "NE/2 (ne2000 MCA version) support"
1124 depends on NET_ETHERNET && MCA
1127 If you have a network (Ethernet) card of this type, say Y and read
1128 the Ethernet-HOWTO, available from
1129 <http://www.tldp.org/docs.html#howto>.
1131 To compile this driver as a module, choose M here and read
1132 <file:Documentation/networking/net-modules.txt>. The module
1136 tristate "IBM LAN Adapter/A support"
1137 depends on NET_ETHERNET && MCA && MCA_LEGACY
1139 This is a Micro Channel Ethernet adapter. You need to set
1140 CONFIG_MCA to use this driver. It is both available as an in-kernel
1141 driver and as a module.
1143 To compile this driver as a module, choose M here and read
1144 <file:Documentation/networking/net-modules.txt>. The only
1145 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1146 will both support 16K and 32K memory windows, however a 32K window
1147 gives a better security against packet losses. Usage of multiple
1148 boards with this driver should be possible, but has not been tested
1149 up to now due to lack of hardware.
1152 tristate "IBM LAN Virtual Ethernet support"
1153 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1155 This driver supports virtual ethernet adapters on newer IBM iSeries
1156 and pSeries systems.
1158 To compile this driver as a module, choose M here and read
1159 <file:Documentation/networking/net-modules.txt>. The module will
1163 tristate "IBM PPC4xx EMAC driver support"
1166 This driver supports the IBM PPC4xx EMAC family of on-chip
1167 Ethernet controllers.
1169 config IBM_EMAC_ERRMSG
1170 bool "Verbose error messages"
1174 int "Number of receive buffers"
1176 default "128" if IBM_EMAC4
1180 int "Number of transmit buffers"
1182 default "128" if IBM_EMAC4
1185 config IBM_EMAC_FGAP
1190 config IBM_EMAC_SKBRES
1191 int "Skb reserve amount"
1196 bool "EISA, VLB, PCI and on board controllers"
1197 depends on NET_ETHERNET && (ISA || EISA || PCI)
1199 This is another class of network cards which attach directly to the
1200 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1201 available from <http://www.tldp.org/docs.html#howto>.
1203 Note that the answer to this question doesn't directly affect the
1204 kernel: saying N will just cause the configurator to skip all
1205 the questions about this class of network cards. If you say Y, you
1206 will be asked for your specific card in the following questions. If
1207 you are unsure, say Y.
1210 tristate "AMD PCnet32 PCI support"
1211 depends on NET_PCI && PCI
1215 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1216 answer Y here and read the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here and read
1220 <file:Documentation/networking/net-modules.txt>. The module
1221 will be called pcnet32.
1224 tristate "AMD 8111 (new PCI lance) support"
1225 depends on NET_PCI && PCI
1229 If you have an AMD 8111-based PCI lance ethernet card,
1230 answer Y here and read the Ethernet-HOWTO, available from
1231 <http://www.tldp.org/docs.html#howto>.
1233 To compile this driver as a module, choose M here and read
1234 <file:Documentation/networking/net-modules.txt>. The module
1235 will be called amd8111e.
1236 config AMD8111E_NAPI
1237 bool "Enable NAPI support"
1238 depends on AMD8111_ETH
1240 NAPI is a new driver API designed to reduce CPU and interrupt load
1241 when the driver is receiving lots of packets from the card. It is
1242 still somewhat experimental and thus not yet enabled by default.
1244 If your estimated Rx load is 10kpps or more, or if the card will be
1245 deployed on potentially unfriendly networks (e.g. in a firewall),
1248 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1253 config ADAPTEC_STARFIRE
1254 tristate "Adaptec Starfire/DuraLAN support"
1255 depends on NET_PCI && PCI
1259 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1260 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1261 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1264 To compile this driver as a module, choose M here: the module
1265 will be called starfire. This is recommended.
1267 config ADAPTEC_STARFIRE_NAPI
1268 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1269 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1271 NAPI is a new driver API designed to reduce CPU and interrupt load
1272 when the driver is receiving lots of packets from the card. It is
1273 still somewhat experimental and thus not yet enabled by default.
1275 If your estimated Rx load is 10kpps or more, or if the card will be
1276 deployed on potentially unfriendly networks (e.g. in a firewall),
1279 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1285 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1286 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1289 If you have a network (Ethernet) card of this type, say Y and read
1290 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
1295 will be called ac3200.
1298 tristate "Apricot Xen-II on board Ethernet"
1299 depends on NET_PCI && ISA
1301 If you have a network (Ethernet) controller of this type, say Y and
1302 read the Ethernet-HOWTO, available from
1303 <http://www.tldp.org/docs.html#howto>.
1305 To compile this driver as a module, choose M here and read
1306 <file:Documentation/networking/net-modules.txt>. The module will be
1310 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1311 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
1323 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1324 depends on NET_PCI && PCI && EXPERIMENTAL
1326 If you have a network (Ethernet) controller of this type, say Y and
1327 read the Ethernet-HOWTO, available from
1328 <http://www.tldp.org/docs.html#howto>.
1330 To compile this driver as a module, choose M here and read
1331 <file:Documentation/networking/net-modules.txt>. The module will be
1336 tristate "CS89x0 support"
1337 depends on NET_PCI && ISA
1339 Support for CS89x0 chipset based Ethernet cards. If you have a
1340 network (Ethernet) card of this type, say Y and read the
1341 Ethernet-HOWTO, available from
1342 <http://www.tldp.org/docs.html#howto> as well as
1343 <file:Documentation/networking/cs89x0.txt>.
1345 To compile this driver as a module, choose M here and read
1346 <file:Documentation/networking/net-modules.txt>. The module will be
1350 tristate "TOSHIBA TC35815 Ethernet support"
1351 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1354 tristate "Digi Intl. RightSwitch SE-X support"
1355 depends on NET_PCI && (PCI || EISA)
1357 This is support for the Digi International RightSwitch series of
1358 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1359 models. If you have a network card of this type, say Y and read the
1360 Ethernet-HOWTO, available from
1361 <http://www.tldp.org/docs.html#howto>. More specific
1362 information is contained in <file:Documentation/networking/dgrs.txt>.
1364 To compile this driver as a module, choose M here and read
1365 <file:Documentation/networking/net-modules.txt>. The module
1366 will be called dgrs.
1369 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1370 depends on NET_PCI && PCI
1373 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1374 card, say Y and read the Ethernet-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>.
1377 To compile this driver as a module, choose M here and read
1378 <file:Documentation/networking/net-modules.txt>. The module
1379 will be called eepro100.
1383 bool "Use PIO instead of MMIO" if !X86_VISWS
1385 default y if X86_VISWS
1387 This instructs the driver to use programmed I/O ports (PIO) instead
1388 of PCI shared memory (MMIO). This can possibly solve some problems
1389 in case your mainboard has memory consistency issues. If unsure,
1393 tristate "Intel(R) PRO/100+ support"
1394 depends on NET_PCI && PCI
1397 This driver supports Intel(R) PRO/100 family of adapters, which
1400 Controller Adapter Name Board IDs
1401 ---------- ------------ ---------
1403 82558 PRO/100+ PCI Adapter 668081-xxx,
1405 82558 PRO/100+ Management Adapter 691334-xxx,
1408 82558 PRO/100+ Dual Port Server Adapter 714303-xxx,
1411 82558 PRO/100+ PCI Server Adapter 710550-xxx
1412 82550 PRO/100 S Server Adapter 752438-xxx
1421 82550 PRO/100 S Desktop Adapter 751767-xxx
1428 82559 PRO/100+ Server Adapter 729757-xxx
1429 82559 PRO/100 S Management Adapter 748566-xxx,
1431 82550 PRO/100 S Dual Port Server Adapter A56831-xxx
1432 82551 PRO/100 M Desktop Adapter A80897-xxx
1433 PRO/100 S Advanced Management Adapter
1436 CNR PRO/100 VE Desktop Adapter A10386-xxx,
1440 PRO/100 VM Desktop Adapter A14323-xxx,
1447 To verify that your adapter is supported, find the board ID number
1448 on the adapter. Look for a label that has a barcode and a number
1449 in the format 123456-001 (six digits hyphen three digits). Match
1450 this to the list of numbers above.
1452 For more information on how to identify your adapter, go to the
1453 Adapter & Driver ID Guide at:
1455 http://support.intel.com/support/network/adapter/pro100/21397.htm
1457 For the latest Intel PRO/100 network driver for Linux, see:
1459 http://appsr.intel.com/scripts-df/support_intel.asp
1461 More specific information on configuring the driver is in
1462 <file:Documentation/networking/e100.txt>.
1464 To compile this driver as a module, choose M here and read
1465 <file:Documentation/networking/net-modules.txt>. The module
1466 will be called e100.
1469 bool "Use Rx Polling (NAPI)"
1472 NAPI is a new driver API designed to reduce CPU and interrupt load
1473 when the driver is receiving lots of packets from the card. It is
1474 still somewhat experimental and thus not yet enabled by default.
1476 If your estimated Rx load is 10kpps or more, or if the card will be
1477 deployed on potentially unfriendly networks (e.g. in a firewall),
1480 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1486 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1487 depends on NET_PCI && EISA && EXPERIMENTAL
1490 If you have a network (Ethernet) card of this type, say Y and read
1491 the Ethernet-HOWTO, available from
1492 <http://www.tldp.org/docs.html#howto>.
1494 To compile this driver as a module, choose M here and read
1495 <file:Documentation/networking/net-modules.txt>. The module
1496 will be called lne390.
1499 tristate "Myson MTD-8xx PCI Ethernet support"
1500 depends on NET_PCI && PCI
1504 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1505 cards. Specifications and data at
1506 <http://www.myson.com.hk/mtd/datasheet/>.
1509 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1510 depends on NET_PCI && PCI
1513 This driver is for the National Semiconductor DP83810 series,
1514 which is used in cards from PureData, NetGear, Linksys
1515 and others, including the 83815 chip.
1516 More specific information and updates are available from
1517 <http://www.scyld.com/network/natsemi.html>.
1520 tristate "PCI NE2000 and clones support (see help)"
1521 depends on NET_PCI && PCI
1524 This driver is for NE2000 compatible PCI cards. It will not work
1525 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1526 support" below). If you have a PCI NE2000 network (Ethernet) card,
1527 say Y and read the Ethernet-HOWTO, available from
1528 <http://www.tldp.org/docs.html#howto>.
1530 This driver also works for the following NE2000 clone cards:
1531 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1532 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1533 Holtek HT80232 Holtek HT80229
1535 To compile this driver as a module, choose M here and read
1536 <file:Documentation/networking/net-modules.txt>. The module
1537 will be called ne2k-pci.
1540 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1541 depends on NET_PCI && EISA && EXPERIMENTAL
1544 If you have a network (Ethernet) card of this type, say Y and read
1545 the Ethernet-HOWTO, available from
1546 <http://www.tldp.org/docs.html#howto>. Note that this driver
1547 will NOT WORK for NE3200 cards as they are completely different.
1549 To compile this driver as a module, choose M here and read
1550 <file:Documentation/networking/net-modules.txt>. The module
1551 will be called ne3210.
1554 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1555 depends on NET_PCI && EISA && EXPERIMENTAL
1558 If you have a network (Ethernet) card of this type, say Y and read
1559 the Ethernet-HOWTO, available from
1560 <http://www.tldp.org/docs.html#howto>.
1562 To compile this driver as a module, choose M here and read
1563 <file:Documentation/networking/net-modules.txt>. The module
1564 will be called es3210.
1567 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1568 depends on NET_PCI && PCI && EXPERIMENTAL
1572 This is a driver for the Fast Ethernet PCI network cards based on
1573 the RTL8139C+ chips. If you have one of those, say Y and read
1574 the Ethernet-HOWTO, available from
1575 <http://www.tldp.org/docs.html#howto>.
1577 To compile this driver as a module, choose M here: the module
1578 will be called 8139cp. This is recommended.
1581 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1582 depends on NET_PCI && PCI
1586 This is a driver for the Fast Ethernet PCI network cards based on
1587 the RTL8139 chips. If you have one of those, say Y and read
1588 the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1590 To compile this driver as a module, choose M here: the module
1591 will be called 8139too. This is recommended.
1594 bool "Use PIO instead of MMIO"
1598 This instructs the driver to use programmed I/O ports (PIO) instead
1599 of PCI shared memory (MMIO). This can possibly solve some problems
1600 in case your mainboard has memory consistency issues. If unsure,
1603 config 8139TOO_TUNE_TWISTER
1604 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1607 This implements a function which might come in handy in case you
1608 are using low quality on long cabling. It is required for RealTek
1609 RTL-8139 revision K boards, and totally unused otherwise. It tries
1610 to match the transceiver to the cable characteristics. This is
1611 experimental since hardly documented by the manufacturer.
1615 bool "Support for older RTL-8129/8130 boards"
1618 This enables support for the older and uncommon RTL-8129 and
1619 RTL-8130 chips, which support MII via an external transceiver,
1620 instead of an internal one. Disabling this option will save some
1621 memory by making the code size smaller. If unsure, say Y.
1623 config 8139_OLD_RX_RESET
1624 bool "Use older RX-reset method"
1627 The 8139too driver was recently updated to contain a more rapid
1628 reset sequence, in the face of severe receive errors. This "new"
1629 RX-reset method should be adequate for all boards. But if you
1630 experience problems, you can enable this option to restore the
1631 old RX-reset behavior. If unsure, say N.
1634 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1635 depends on NET_PCI && PCI
1638 This is a driver for the Fast Ethernet PCI network cards based on
1639 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1640 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1641 read the Ethernet-HOWTO, available at
1642 <http://www.tldp.org/docs.html#howto>. Please read
1643 <file:Documentation/networking/sis900.txt> and comments at the
1644 beginning of <file:drivers/net/sis900.c> for more information.
1646 This driver also supports AMD 79C901 HomePNA so that you can use
1647 your phone line as a network cable.
1649 To compile this driver as a module, choose M here: the module
1650 will be called sis900. This is recommended.
1653 tristate "SMC EtherPower II"
1654 depends on NET_PCI && PCI
1658 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1659 which is based on the SMC83c17x (EPIC/100).
1660 More specific information and updates are available from
1661 <http://www.scyld.com/network/epic100.html>.
1664 tristate "Sundance Alta support"
1665 depends on NET_PCI && PCI
1669 This driver is for the Sundance "Alta" chip.
1670 More specific information and updates are available from
1671 <http://www.scyld.com/network/sundance.html>.
1673 config SUNDANCE_MMIO
1674 bool "Use MMIO instead of PIO"
1677 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1678 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1679 is known to solve bugs on certain chips.
1684 tristate "TI ThunderLAN support"
1685 depends on NET_PCI && (PCI || EISA) && !64BIT
1687 If you have a PCI Ethernet network card based on the ThunderLAN chip
1688 which is supported by this driver, say Y and read the
1689 Ethernet-HOWTO, available from
1690 <http://www.tldp.org/docs.html#howto>.
1692 Devices currently supported by this driver are Compaq Netelligent,
1693 Compaq NetFlex and Olicom cards. Please read the file
1694 <file:Documentation/networking/tlan.txt> for more details.
1696 To compile this driver as a module, choose M here and read
1697 <file:Documentation/networking/net-modules.txt>. The module
1698 will be called tlan.
1700 Please email feedback to torben.mathiasen@compaq.com.
1703 tristate "VIA Rhine support"
1704 depends on NET_PCI && PCI
1708 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1709 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1710 Ethernet functions can also be found integrated on South Bridges
1713 To compile this driver as a module, choose M here. The module
1714 will be called via-rhine.
1716 config VIA_RHINE_MMIO
1717 bool "Use MMIO instead of PIO"
1718 depends on VIA_RHINE
1720 This instructs the driver to use PCI shared memory (MMIO) instead of
1721 programmed I/O ports (PIO). Enabling this gives an improvement in
1722 processing time in parts of the driver.
1727 tristate "VIA Velocity support"
1728 depends on NET_PCI && PCI
1732 If you have a VIA "Velocity" based network card say Y here.
1734 To compile this driver as a module, choose M here. The module
1735 will be called via-rhine.
1738 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1739 depends on NET_PCI && EXPERIMENTAL && MIPS
1741 The SAA9730 is a combined multimedia and peripheral controller used
1742 in thin clients, Internet access terminals, and diskless
1744 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1747 bool "Pocket and portable adapters"
1748 depends on NET_ETHERNET && ISA
1750 Cute little network (Ethernet) devices which attach to the parallel
1751 port ("pocket adapters"), commonly used with laptops. If you have
1752 one of those, say Y and read the Ethernet-HOWTO, available from
1753 <http://www.tldp.org/docs.html#howto>.
1755 If you want to plug a network (or some other) card into the PCMCIA
1756 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1757 credit card size extension cards used by all modern laptops), you
1758 need the pcmcia-cs package (location contained in the file
1759 <file:Documentation/Changes>) and you can say N here.
1761 Laptop users should read the Linux Laptop home page at
1762 <http://www.linux-on-laptops.com/> or
1763 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1765 Note that the answer to this question doesn't directly affect the
1766 kernel: saying N will just cause the configurator to skip all
1767 the questions about this class of network devices. If you say Y, you
1768 will be asked for your specific device in the following questions.
1771 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1772 depends on NET_POCKET && ISA && X86
1775 This is a network (Ethernet) device which attaches to your parallel
1776 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1777 available from <http://www.tldp.org/docs.html#howto>, if you
1778 want to use this. If you intend to use this driver, you should have
1779 said N to the "Parallel printer support", because the two drivers
1780 don't like each other.
1782 To compile this driver as a module, choose M here: the module
1786 tristate "D-Link DE600 pocket adapter support"
1787 depends on NET_POCKET && ISA
1789 This is a network (Ethernet) device which attaches to your parallel
1790 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1791 Ethernet-HOWTO, available from
1792 <http://www.tldp.org/docs.html#howto>, if you want to use
1793 this. It is possible to have several devices share a single parallel
1794 port and it is safe to compile the corresponding drivers into the
1797 To compile this driver as a module, choose M here: the module
1798 will be called de600.
1801 tristate "D-Link DE620 pocket adapter support"
1802 depends on NET_POCKET && ISA
1804 This is a network (Ethernet) device which attaches to your parallel
1805 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1806 Ethernet-HOWTO, available from
1807 <http://www.tldp.org/docs.html#howto>, if you want to use
1808 this. It is possible to have several devices share a single parallel
1809 port and it is safe to compile the corresponding drivers into the
1812 To compile this driver as a module, choose M here: the module
1813 will be called de620.
1816 tristate "SGI Seeq ethernet controller support"
1817 depends on NET_ETHERNET && SGI_IP22
1819 Say Y here if you have an Seeq based Ethernet network card. This is
1820 used in many Silicon Graphics machines.
1823 tristate "DEC LANCE ethernet controller support"
1824 depends on NET_ETHERNET && MACH_DECSTATION
1827 This driver is for the series of Ethernet controllers produced by
1828 DEC (now Compaq) based on the AMD Lance chipset, including the
1829 DEPCA series. (This chipset is better known via the NE2100 cards.)
1832 tristate "Baget AMD LANCE support"
1833 depends on NET_ETHERNET && BAGET_MIPS
1835 Say Y to enable kernel support for AMD Lance Ethernet cards on the
1836 MIPS-32-based Baget embedded system. This chipset is better known
1837 via the NE2100 cards.
1840 bool "Motorola 68360 ethernet controller"
1843 Say Y here if you want to use the built-in ethernet controller of
1844 the Motorola 68360 processor.
1847 bool "FEC ethernet controller (of ColdFire 5272)"
1848 depends on M5272 || M5282
1850 Say Y here if you want to use the built-in 10/100 Fast ethernet
1851 controller on the Motorola ColdFire 5272 processor.
1854 tristate "NE2000 compatible support for H8/300"
1855 depends on H8300 && NET_ETHERNET
1857 Say Y here if you want to use the NE2000 compatible
1858 controller on the Renesas H8/300 processor.
1866 menu "Ethernet (1000 Mbit)"
1867 depends on NETDEVICES
1870 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1873 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1874 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1875 adapter. The driver allows for using the Jumbo Frame option (9000
1876 bytes/frame) however it requires that your switches can handle this
1877 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1880 To compile this driver as a module, choose M here: the
1881 module will be called acenic.
1883 config ACENIC_OMIT_TIGON_I
1884 bool "Omit support for old Tigon I based AceNICs"
1887 Say Y here if you only have Tigon II based AceNICs and want to leave
1888 out support for the older Tigon I based cards which are no longer
1889 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1890 version)). This will reduce the size of the driver object by
1891 app. 100KB. If you are not sure whether your card is a Tigon I or a
1892 Tigon II, say N here.
1894 The safe and default value for this is N.
1897 tristate "D-Link DL2000-based Gigabit Ethernet support"
1901 This driver supports D-Link 2000-based gigabit ethernet cards, which
1903 D-Link DGE-550T Gigabit Ethernet Adapter.
1904 D-Link DL2000-based Gigabit Ethernet Adapter.
1906 To compile this driver as a module, choose M here: the
1907 module will be called dl2k.
1910 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1913 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1914 adapters, which includes:
1916 Controller Adapter Name Board IDs
1917 ---------- ------------ ---------
1918 82542 PRO/1000 Gigabit Server Adapter 700262-xxx,
1920 82543 PRO/1000 F Server Adapter 738640-xxx,
1922 82543 PRO/1000 T Server Adapter A19845-xxx,
1924 82544 PRO/1000 XT Server Adapter A51580-xxx
1925 82544 PRO/1000 XF Server Adapter A50484-xxx
1926 82544 PRO/1000 T Desktop Adapter A62947-xxx
1927 82540 PRO/1000 MT Desktop Adapter A78408-xxx
1928 82541 PRO/1000 MT Desktop Adapter C91016-xxx
1929 82545 PRO/1000 MT Server Adapter A92165-xxx
1930 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx
1931 82545 PRO/1000 MF Server Adapter A91622-xxx
1932 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx
1933 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx
1935 For more information on how to identify your adapter, go to the
1936 Adapter & Driver ID Guide at:
1938 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1940 For general information and support, go to the Intel support
1943 <http://support.intel.com>
1945 More specific information on configuring the driver is in
1946 <file:Documentation/networking/e1000.txt>.
1948 To compile this driver as a module, choose M here and read
1949 <file:Documentation/networking/net-modules.txt>. The module
1950 will be called e1000.
1953 bool "Use Rx Polling (NAPI)"
1956 NAPI is a new driver API designed to reduce CPU and interrupt load
1957 when the driver is receiving lots of packets from the card. It is
1958 still somewhat experimental and thus not yet enabled by default.
1960 If your estimated Rx load is 10kpps or more, or if the card will be
1961 deployed on potentially unfriendly networks (e.g. in a firewall),
1964 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1970 tristate "MyriCOM Gigabit Ethernet support"
1973 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1975 To compile this driver as a module, choose M here: the module
1976 will be called myri_sbus. This is recommended.
1979 tristate "National Semiconduct DP83820 support"
1982 This is a driver for the National Semiconductor DP83820 series
1983 of gigabit ethernet MACs. Cards using this chipset include
1984 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1985 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1989 tristate "Packet Engines Hamachi GNIC-II support"
1993 If you have a Gigabit Ethernet card of this type, say Y and read
1994 the Ethernet-HOWTO, available from
1995 <http://www.tldp.org/docs.html#howto>.
1997 To compile this driver as a module, choose M here and read
1998 <file:Documentation/networking/net-modules.txt>. The module will be
2002 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2003 depends on PCI && EXPERIMENTAL
2006 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2007 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2008 used by the Beowulf Linux cluster project. See
2009 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2010 information about this driver in particular and Beowulf in general.
2012 To compile this driver as a module, choose M here: the module
2013 will be called yellowfin. This is recommended.
2016 tristate "Realtek 8169 gigabit ethernet support"
2020 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2022 To compile this driver as a module, choose M here: the module
2023 will be called r8169. This is recommended.
2026 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2029 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2030 compliant Gigabit Ethernet Adapter. The following adapters are supported
2032 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2033 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2034 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2035 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2036 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2037 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2038 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2039 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2040 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2041 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2042 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2043 - DGE-530T Gigabit Ethernet Adapter
2044 - EG1032 v2 Instant Gigabit Network Adapter
2045 - EG1064 v2 Instant Gigabit Network Adapter
2046 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2047 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2048 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2049 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2050 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2051 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2052 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2053 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2054 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2055 - Marvell RDK-8001 Adapter
2056 - Marvell RDK-8002 Adapter
2057 - Marvell RDK-8003 Adapter
2058 - Marvell RDK-8004 Adapter
2059 - Marvell RDK-8006 Adapter
2060 - Marvell RDK-8007 Adapter
2061 - Marvell RDK-8008 Adapter
2062 - Marvell RDK-8009 Adapter
2063 - Marvell RDK-8010 Adapter
2064 - Marvell RDK-8011 Adapter
2065 - Marvell RDK-8012 Adapter
2066 - Marvell RDK-8052 Adapter
2067 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2068 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2069 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2070 - SK-9521 10/100/1000Base-T Adapter
2071 - SK-9521 V2.0 10/100/1000Base-T Adapter
2072 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2073 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2074 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2075 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2076 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2077 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2078 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2079 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2080 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2081 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2082 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2083 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2084 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2085 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2086 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2087 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2088 - SMC EZ Card 1000 (SMC9452TXV.2)
2090 The adapters support Jumbo Frames.
2091 The dual link adapters support link-failover and dual port features.
2092 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2093 the scatter-gather functionality with sendfile(). Please refer to
2094 Documentation/networking/sk98lin.txt for more information about
2095 optional driver parameters.
2096 Questions concerning this driver may be addressed to:
2099 If you want to compile this driver as a module ( = code which can be
2100 inserted in and removed from the running kernel whenever you want),
2101 say M here and read Documentation/kbuild/modules.txt. The module will
2102 be called sk98lin. This is recommended.
2105 tristate "Broadcom Tigon3 support"
2108 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2110 To compile this driver as a module, choose M here: the module
2111 will be called tg3. This is recommended.
2116 # 10 Gigabit Ethernet
2119 menu "Ethernet (10000 Mbit)"
2120 depends on NETDEVICES
2123 tristate "Intel(R) PRO/10GbE support"
2126 This driver supports Intel(R) PRO/10GbE family of
2127 adapters, which includes:
2129 Controller Adapter Name Board IDs
2130 ---------- ------------ ---------
2131 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx
2133 For more information on how to identify your adapter, go to the
2134 Adapter & Driver ID Guide at:
2136 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2138 For general information and support, go to the Intel support
2141 <http://support.intel.com>
2143 More specific information on configuring the driver is in
2144 <file:Documentation/networking/ixgb.txt>.
2146 To compile this driver as a module, choose M here and read
2147 <file:Documentation/networking/net-modules.txt>. The module
2148 will be called ixgb.
2151 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2152 depends on IXGB && EXPERIMENTAL
2154 NAPI is a new driver API designed to reduce CPU and interrupt load
2155 when the driver is receiving lots of packets from the card. It is
2156 still somewhat experimental and thus not yet enabled by default.
2158 If your estimated Rx load is 10kpps or more, or if the card will be
2159 deployed on potentially unfriendly networks (e.g. in a firewall),
2162 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2168 tristate "S2IO 10Gbe XFrame NIC"
2171 This driver supports the 10Gbe XFrame NIC of S2IO.
2172 For help regarding driver compilation, installation and
2173 tuning please look into ~/drivers/net/s2io/README.txt.
2176 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2177 depends on S2IO && EXPERIMENTAL
2179 NAPI is a new driver API designed to reduce CPU and interrupt load
2180 when the driver is receiving lots of packets from the card. It is
2181 still somewhat experimental and thus not yet enabled by default.
2183 If your estimated Rx load is 10kpps or more, or if the card will be
2184 deployed on potentially unfriendly networks (e.g. in a firewall),
2187 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2194 source "drivers/net/tokenring/Kconfig"
2196 source "drivers/net/wireless/Kconfig"
2198 source "drivers/net/pcmcia/Kconfig"
2200 source "drivers/net/wan/Kconfig"
2202 source "drivers/atm/Kconfig"
2204 source "drivers/s390/net/Kconfig"
2207 tristate "iSeries Virtual Ethernet driver support"
2208 depends on NETDEVICES && PPC_ISERIES
2211 bool "FDDI driver support"
2212 depends on NETDEVICES && (PCI || EISA)
2214 Fiber Distributed Data Interface is a high speed local area network
2215 design; essentially a replacement for high speed Ethernet. FDDI can
2216 run over copper or fiber. If you are connected to such a network and
2217 want a driver for the FDDI card in your computer, say Y here (and
2218 then also Y to the driver for your FDDI card, below). Most people
2222 tristate "Digital DEFEA and DEFPA adapter support"
2223 depends on FDDI && (PCI || EISA)
2225 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2226 (DEFPA) controllers which can connect you to a local FDDI network.
2229 tristate "SysKonnect FDDI PCI support"
2230 depends on FDDI && PCI
2232 Say Y here if you have a SysKonnect FDDI PCI adapter.
2233 The following adapters are supported by this driver:
2234 - SK-5521 (SK-NET FDDI-UP)
2235 - SK-5522 (SK-NET FDDI-UP DAS)
2236 - SK-5541 (SK-NET FDDI-FP)
2237 - SK-5543 (SK-NET FDDI-LP)
2238 - SK-5544 (SK-NET FDDI-LP DAS)
2239 - SK-5821 (SK-NET FDDI-UP64)
2240 - SK-5822 (SK-NET FDDI-UP64 DAS)
2241 - SK-5841 (SK-NET FDDI-FP64)
2242 - SK-5843 (SK-NET FDDI-LP64)
2243 - SK-5844 (SK-NET FDDI-LP64 DAS)
2244 - Netelligent 100 FDDI DAS Fibre SC
2245 - Netelligent 100 FDDI SAS Fibre SC
2246 - Netelligent 100 FDDI DAS UTP
2247 - Netelligent 100 FDDI SAS UTP
2248 - Netelligent 100 FDDI SAS Fibre MIC
2250 Read <file:Documentation/networking/skfp.txt> for information about
2253 Questions concerning this driver can be addressed to:
2256 To compile this driver as a module, choose M here: the module
2257 will be called skfp. This is recommended.
2260 bool "HIPPI driver support (EXPERIMENTAL)"
2261 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2263 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2264 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2265 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2266 single-mode). HIPPI networks are commonly used for clusters and to
2267 connect to super computers. If you are connected to a HIPPI network
2268 and have a HIPPI network card in your computer that you want to use
2269 under Linux, say Y here (you must also remember to enable the driver
2270 for your HIPPI card below). Most people will say N here.
2273 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2274 depends on HIPPI && PCI
2276 Say Y here if this is your PCI HIPPI network card.
2278 To compile this driver as a module, choose M here: the module
2279 will be called rrunner. If unsure, say N.
2281 config ROADRUNNER_LARGE_RINGS
2282 bool "Use large TX/RX rings (EXPERIMENTAL)"
2283 depends on ROADRUNNER
2285 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2286 of additional memory to allow for fastest operation, both for
2287 transmitting and receiving. This memory cannot be used by any other
2288 kernel code or by user space programs. Say Y here only if you have
2292 tristate "PLIP (parallel port) support"
2293 depends on NETDEVICES && PARPORT
2295 PLIP (Parallel Line Internet Protocol) is used to create a
2296 reasonably fast mini network consisting of two (or, rarely, more)
2297 local machines. A PLIP link from a Linux box is a popular means to
2298 install a Linux distribution on a machine which doesn't have a
2299 CD-ROM drive (a minimal system has to be transferred with floppies
2300 first). The kernels on both machines need to have this PLIP option
2301 enabled for this to work.
2303 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2304 ports (the connectors at the computers with 25 holes) are connected
2305 with "null printer" or "Turbo Laplink" cables which can transmit 4
2306 bits at a time (mode 0) or with special PLIP cables, to be used on
2307 bidirectional parallel ports only, which can transmit 8 bits at a
2308 time (mode 1); you can find the wiring of these cables in
2309 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2310 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2311 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2312 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2313 and winsock or NCSA's telnet.
2315 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2316 as the NET-3-HOWTO, both available from
2317 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2318 protocol has been changed and this PLIP driver won't work together
2319 with the PLIP support in Linux versions 1.0.x. This option enlarges
2320 your kernel by about 8 KB.
2322 To compile this driver as a module, choose M here and read
2323 <file:Documentation/networking/net-modules.txt>. The module will be
2324 called plip. If unsure, say Y or M, in case you buy a laptop
2328 tristate "PPP (point-to-point protocol) support"
2329 depends on NETDEVICES
2331 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2332 the same purpose: sending Internet traffic over telephone (and other
2333 serial) lines. Ask your access provider if they support it, because
2334 otherwise you can't use it; most Internet access providers these
2335 days support PPP rather than SLIP.
2337 To use PPP, you need an additional program called pppd as described
2338 in the PPP-HOWTO, available at
2339 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2340 the version of pppd recommended in <file:Documentation/Changes>.
2341 The PPP option enlarges your kernel by about 16 KB.
2343 There are actually two versions of PPP: the traditional PPP for
2344 asynchronous lines, such as regular analog phone lines, and
2345 synchronous PPP which can be used over digital ISDN lines for
2346 example. If you want to use PPP over phone lines or other
2347 asynchronous serial lines, you need to say Y (or M) here and also to
2348 the next option, "PPP support for async serial ports". For PPP over
2349 synchronous lines, you should say Y (or M) here and to "Support
2350 synchronous PPP", below.
2352 If you said Y to "Version information on all symbols" above, then
2353 you cannot compile the PPP driver into the kernel; you can then only
2354 compile it as a module. To compile this driver as a module, choose M
2355 here and read <file:Documentation/networking/net-modules.txt>.
2356 The module will be called ppp_generic.
2358 config PPP_MULTILINK
2359 bool "PPP multilink support (EXPERIMENTAL)"
2360 depends on PPP && EXPERIMENTAL
2362 PPP multilink is a protocol (defined in RFC 1990) which allows you
2363 to combine several (logical or physical) lines into one logical PPP
2364 connection, so that you can utilize your full bandwidth.
2366 This has to be supported at the other end as well and you need a
2367 version of the pppd daemon which understands the multilink protocol.
2372 bool "PPP filtering"
2375 Say Y here if you want to be able to filter the packets passing over
2376 PPP interfaces. This allows you to control which packets count as
2377 activity (i.e. which packets will reset the idle timer or bring up
2378 a demand-dialled link) and which packets are to be dropped entirely.
2379 You need to say Y here if you wish to use the pass-filter and
2380 active-filter options to pppd.
2385 tristate "PPP support for async serial ports"
2388 Say Y (or M) here if you want to be able to use PPP over standard
2389 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2390 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2393 To compile this driver as a module, choose M here.
2398 tristate "PPP support for sync tty ports"
2401 Say Y (or M) here if you want to be able to use PPP over synchronous
2402 (HDLC) tty devices, such as the SyncLink adapter. These devices
2403 are often used for high-speed leased lines like T1/E1.
2405 To compile this driver as a module, choose M here.
2408 tristate "PPP Deflate compression"
2413 Support for the Deflate compression method for PPP, which uses the
2414 Deflate algorithm (the same algorithm that gzip uses) to compress
2415 each PPP packet before it is sent over the wire. The machine at the
2416 other end of the PPP link (usually your ISP) has to support the
2417 Deflate compression method as well for this to be useful. Even if
2418 they don't support it, it is safe to say Y here.
2420 To compile this driver as a module, choose M here.
2423 tristate "PPP BSD-Compress compression"
2426 Support for the BSD-Compress compression method for PPP, which uses
2427 the LZW compression method to compress each PPP packet before it is
2428 sent over the wire. The machine at the other end of the PPP link
2429 (usually your ISP) has to support the BSD-Compress compression
2430 method as well for this to be useful. Even if they don't support it,
2431 it is safe to say Y here.
2433 The PPP Deflate compression method ("PPP Deflate compression",
2434 above) is preferable to BSD-Compress, because it compresses better
2437 Note that the BSD compression code will always be compiled as a
2438 module; it is called bsd_comp and will show up in the directory
2439 modules once you have said "make modules". If unsure, say N.
2442 tristate "PPP over Ethernet (EXPERIMENTAL)"
2443 depends on EXPERIMENTAL && PPP
2445 Support for PPP over Ethernet.
2447 This driver requires the latest version of pppd from the CVS
2448 repository at cvs.samba.org. Alternatively, see the
2449 RoaringPenguin package (http://www.roaringpenguin.com/pppoe)
2450 which contains instruction on how to use this driver (under
2451 the heading "Kernel mode PPPoE").
2454 tristate "PPP over ATM"
2455 depends on ATM && PPP
2457 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2458 This implementation does not yet comply with section 8 of RFC2364,
2459 which can lead to bad results if the ATM peer loses state and
2460 changes its encapsulation unilaterally.
2463 tristate "SLIP (serial line) support"
2464 depends on NETDEVICES
2466 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2467 connect to your Internet service provider or to connect to some
2468 other local Unix box or if you want to configure your Linux box as a
2469 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2470 Internet Protocol) is a protocol used to send Internet traffic over
2471 serial connections such as telephone lines or null modem cables;
2472 nowadays, the protocol PPP is more commonly used for this same
2475 Normally, your access provider has to support SLIP in order for you
2476 to be able to use it, but there is now a SLIP emulator called SLiRP
2477 around (available from
2478 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2479 allows you to use SLIP over a regular dial up shell connection. If
2480 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2481 NET-3-HOWTO, available from
2482 <http://www.tldp.org/docs.html#howto>, explains how to
2483 configure SLIP. Note that you don't need this option if you just
2484 want to run term (term is a program which gives you almost full
2485 Internet connectivity if you have a regular dial up shell account on
2486 some Internet connected Unix computer. Read
2487 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2488 support will enlarge your kernel by about 4 KB. If unsure, say N.
2490 To compile this driver as a module, choose M here and read
2491 <file:Documentation/networking/net-modules.txt>. The module will be
2494 config SLIP_COMPRESSED
2495 bool "CSLIP compressed headers"
2498 This protocol is faster than SLIP because it uses compression on the
2499 TCP/IP headers (not on the data itself), but it has to be supported
2500 on both ends. Ask your access provider if you are not sure and
2501 answer Y, just in case. You will still be able to use plain SLIP. If
2502 you plan to use SLiRP, the SLIP emulator (available from
2503 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2504 allows you to use SLIP over a regular dial up shell connection, you
2505 definitely want to say Y here. The NET-3-HOWTO, available from
2506 <http://www.tldp.org/docs.html#howto>, explains how to configure
2507 CSLIP. This won't enlarge your kernel.
2510 bool "Keepalive and linefill"
2513 Adds additional capabilities to the SLIP driver to support the
2514 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2517 config SLIP_MODE_SLIP6
2518 bool "Six bit SLIP encapsulation"
2521 Just occasionally you may need to run IP over hostile serial
2522 networks that don't pass all control characters or are only seven
2523 bit. Saying Y here adds an extra mode you can use with SLIP:
2524 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2525 the serial device. Naturally, this has to be supported at the other
2526 end of the link as well. It's good enough, for example, to run IP
2527 over the async ports of a Camtec JNT Pad. If unsure, say N.
2530 bool "Fibre Channel driver support"
2531 depends on NETDEVICES && SCSI && PCI
2533 Fibre Channel is a high speed serial protocol mainly used to connect
2534 large storage devices to the computer; it is compatible with and
2535 intended to replace SCSI.
2537 If you intend to use Fibre Channel, you need to have a Fibre channel
2538 adaptor card in your computer; say Y here and to the driver for your
2539 adaptor below. You also should have said Y to "SCSI support" and
2540 "SCSI generic support".
2543 tristate "Interphase 5526 Tachyon chipset based adapter support"
2544 depends on NET_FC && SCSI && PCI && BROKEN
2546 Say Y here if you have a Fibre Channel adaptor of this kind.
2548 To compile this driver as a module, choose M here: the module
2549 will be called iph5526.
2552 tristate "Traffic Shaper (EXPERIMENTAL)"
2553 depends on NETDEVICES && EXPERIMENTAL
2555 The traffic shaper is a virtual network device that allows you to
2556 limit the rate of outgoing data flow over some other network device.
2557 The traffic that you want to slow down can then be routed through
2558 these virtual devices. See
2559 <file:Documentation/networking/shaper.txt> for more information.
2561 An alternative to this traffic shaper is the experimental
2562 Class-Based Queueing (CBQ) scheduling support which you get if you
2563 say Y to "QoS and/or fair queueing" above.
2565 To set up and configure shaper devices, you need the shapecfg
2566 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2569 To compile this driver as a module, choose M here: the module
2570 will be called shaper. If unsure, say N.
2573 tristate "Network console logging support (EXPERIMENTAL)"
2574 depends on NETDEVICES && EXPERIMENTAL
2576 If you want to log kernel messages over the network, enable this.
2577 See Documentation/networking/netconsole.txt for details.