3 # Network device configuration
6 menu "Network device support"
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
67 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
68 Channels together. This is called 'Etherchannel' by Cisco,
69 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
71 The driver supports multiple bonding modes to allow for both high
72 performance and high availability operation.
74 Refer to <file:Documentation/networking/bonding.txt> for more
77 To compile this driver as a module, choose M here: the module
78 will be called bonding.
81 tristate "EQL (serial line load balancing) support"
83 If you have two serial connections to some other computer (this
84 usually requires two modems and two telephone lines) and you use
85 SLIP (the protocol for sending Internet traffic over telephone
86 lines) or PPP (a better SLIP) on them, you can make them behave like
87 one double speed connection using this driver. Naturally, this has
88 to be supported at the other end as well, either with a similar EQL
89 Linux driver or with a Livingston Portmaster 2e.
91 Say Y if you want this and read
92 <file:Documentation/networking/eql.txt>. You may also want to read
93 section 6.2 of the NET-3-HOWTO, available from
94 <http://www.tldp.org/docs.html#howto>.
96 To compile this driver as a module, choose M here: the module
97 will be called eql. If unsure, say N.
100 tristate "Universal TUN/TAP device driver support"
103 TUN/TAP provides packet reception and transmission for user space
104 programs. It can be viewed as a simple Point-to-Point or Ethernet
105 device, which instead of receiving packets from a physical media,
106 receives them from user space program and instead of sending packets
107 via physical media writes them to the user space program.
109 When a program opens /dev/net/tun, driver creates and registers
110 corresponding net device tunX or tapX. After a program closed above
111 devices, driver will automatically delete tunXX or tapXX device and
112 all routes corresponding to it.
114 Please read <file:Documentation/networking/tuntap.txt> for more
117 To compile this driver as a module, choose M here: the module
120 If you don't know what to use this for, you don't need it.
123 tristate "General Instruments Surfboard 1000"
126 This is a driver for the General Instrument (also known as
127 NextLevel) SURFboard 1000 internal
128 cable modem. This is an ISA card which is used by a number of cable
129 TV companies to provide cable modem access. It's a one-way
130 downstream-only cable modem, meaning that your upstream net link is
131 provided by your regular phone modem.
133 At present this driver only compiles as a module, so say M here if
134 you have this card. The module will be called sb1000. Then read
135 <file:Documentation/networking/README.sb1000> for information on how
136 to use this module, as it needs special ppp scripts for establishing
137 a connection. Further documentation and the necessary scripts can be
140 <http://www.jacksonville.net/~fventuri/>
141 <http://home.adelphia.net/~siglercm/sb1000.html>
142 <http://linuxpower.cx/~cable/>
144 If you don't have this card, of course say N.
146 source "drivers/net/arcnet/Kconfig"
148 source "drivers/net/phy/Kconfig"
154 menu "Ethernet (10 or 100Mbit)"
158 bool "Ethernet (10 or 100Mbit)"
160 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
161 type of Local Area Network (LAN) in universities and companies.
163 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
164 coaxial cable, linking computers in a chain), 10BASE-T or twisted
165 pair (10 Mbps over twisted pair cable, linking computers to central
166 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
167 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
168 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
169 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
170 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
171 Ethernet (1 Gbps over optical fiber or short copper links).
173 If your Linux machine will be connected to an Ethernet and you have
174 an Ethernet network interface card (NIC) installed in your computer,
175 say Y here and read the Ethernet-HOWTO, available from
176 <http://www.tldp.org/docs.html#howto>. You will then also have
177 to say Y to the driver for your particular NIC.
179 Note that the answer to this question won't directly affect the
180 kernel: saying N will just cause the configurator to skip all
181 the questions about Ethernet network cards. If unsure, say N.
184 tristate "Generic Media Independent Interface device support"
185 depends on NET_ETHERNET
187 Most ethernet controllers have MII transceiver either as an external
188 or internal device. It is safe to say Y or M here even if your
189 ethernet card lack MII.
192 tristate "Atmel MACB support"
193 depends on NET_ETHERNET && AVR32
196 The Atmel MACB ethernet interface is found on many AT32 and AT91
197 parts. Say Y to include support for the MACB chip.
199 To compile this driver as a module, choose M here: the module
202 source "drivers/net/arm/Kconfig"
205 tristate "MACE (Power Mac ethernet) support"
206 depends on NET_ETHERNET && PPC_PMAC && PPC32
209 Power Macintoshes and clones with Ethernet built-in on the
210 motherboard will usually use a MACE (Medium Access Control for
211 Ethernet) interface. Say Y to include support for the MACE chip.
213 To compile this driver as a module, choose M here: the module
216 config MACE_AAUI_PORT
217 bool "Use AAUI port instead of TP by default"
220 Some Apple machines (notably the Apple Network Server) which use the
221 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
222 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
223 Y here if you have such a machine. If unsure, say N.
224 The driver will default to AAUI on ANS anyway, and if you use it as
225 a module, you can provide the port_aaui=0|1 to force the driver.
228 tristate "BMAC (G3 ethernet) support"
229 depends on NET_ETHERNET && PPC_PMAC && PPC32
232 Say Y for support of BMAC Ethernet interfaces. These are used on G3
235 To compile this driver as a module, choose M here: the module
239 tristate "National DP83902AV (Oak ethernet) support"
240 depends on NET_ETHERNET && PPC && BROKEN
243 Say Y if your machine has this type of Ethernet network card.
245 To compile this driver as a module, choose M here: the module
246 will be called oaknet.
249 tristate "Ariadne support"
250 depends on NET_ETHERNET && ZORRO
252 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
255 To compile this driver as a module, choose M here: the module
256 will be called ariadne.
259 tristate "A2065 support"
260 depends on NET_ETHERNET && ZORRO
263 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
266 To compile this driver as a module, choose M here: the module
267 will be called a2065.
270 tristate "Hydra support"
271 depends on NET_ETHERNET && ZORRO
274 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
276 To compile this driver as a module, choose M here: the module
277 will be called hydra.
280 tristate "Zorro NS8390-based Ethernet support"
281 depends on NET_ETHERNET && ZORRO
284 This driver is for Zorro Ethernet cards using an NS8390-compatible
285 chipset, like the Village Tronic Ariadne II and the Individual
286 Computers X-Surf Ethernet cards. If you have such a card, say Y.
289 To compile this driver as a module, choose M here: the module
290 will be called zorro8390.
293 tristate "PCMCIA NE2000 support"
294 depends on NET_ETHERNET && AMIGA_PCMCIA
297 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
300 To compile this driver as a module, choose M here: the module
304 tristate "Apollo 3c505 support"
305 depends on NET_ETHERNET && APOLLO
307 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
308 If you don't have one made for Apollos, you can use one from a PC,
309 except that your Apollo won't be able to boot from it (because the
310 code in the ROM will be for a PC).
313 bool "Macintosh NS 8390 based ethernet cards"
314 depends on NET_ETHERNET && MAC
317 If you want to include a driver to support Nubus or LC-PDS
318 Ethernet cards using an NS8390 chipset or its equivalent, say Y
319 and read the Ethernet-HOWTO, available from
320 <http://www.tldp.org/docs.html#howto>.
323 tristate "Macintosh CS89x0 based ethernet cards"
324 depends on NET_ETHERNET && MAC && BROKEN
326 Support for CS89x0 chipset based Ethernet cards. If you have a
327 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
328 read the Ethernet-HOWTO, available from
329 <http://www.tldp.org/docs.html#howto>.
331 To compile this driver as a module, choose M here and read
332 <file:Documentation/networking/net-modules.txt>. This module will
336 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
337 depends on NET_ETHERNET && MAC
339 Support for NatSemi SONIC based Ethernet devices. This includes
340 the onboard Ethernet in many Quadras as well as some LC-PDS,
341 a few Nubus and all known Comm Slot Ethernet cards. If you have
342 one of these say Y and read the Ethernet-HOWTO, available from
343 <http://www.tldp.org/docs.html#howto>.
345 To compile this driver as a module, choose M here and read
346 <file:Documentation/networking/net-modules.txt>. This module will
350 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
351 depends on NET_ETHERNET && MAC && EXPERIMENTAL
354 Support for the onboard AMD 79C940 MACE Ethernet controller used in
355 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
356 say Y and read the Ethernet-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>.
360 tristate "MVME147 (Lance) Ethernet support"
361 depends on NET_ETHERNET && MVME147
364 Support for the on-board Ethernet interface on the Motorola MVME147
365 single-board computer. Say Y here to include the
366 driver for this chip in your kernel.
367 To compile this driver as a module, choose M here.
370 tristate "MVME16x Ethernet support"
371 depends on NET_ETHERNET && MVME16x
373 This is the driver for the Ethernet interface on the Motorola
374 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
375 driver for this chip in your kernel.
376 To compile this driver as a module, choose M here.
379 tristate "BVME6000 Ethernet support"
380 depends on NET_ETHERNET && BVME6000
382 This is the driver for the Ethernet interface on BVME4000 and
383 BVME6000 VME boards. Say Y here to include the driver for this chip
385 To compile this driver as a module, choose M here.
388 tristate "Atari Lance support"
389 depends on NET_ETHERNET && ATARI
391 Say Y to include support for several Atari Ethernet adapters based
392 on the AMD Lance chipset: RieblCard (with or without battery), or
393 PAMCard VME (also the version by Rhotron, with different addresses).
396 tristate "BioNet-100 support"
397 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
399 Say Y to include support for BioData's BioNet-100 Ethernet adapter
400 for the ACSI port. The driver works (has to work...) with a polled
401 I/O scheme, so it's rather slow :-(
404 tristate "PAMsNet support"
405 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
407 Say Y to include support for the PAMsNet Ethernet adapter for the
408 ACSI port ("ACSI node"). The driver works (has to work...) with a
409 polled I/O scheme, so it's rather slow :-(
412 tristate "Sun3/Sun3x on-board LANCE support"
413 depends on NET_ETHERNET && (SUN3 || SUN3X)
415 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
416 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
417 here to compile in the Linux driver for this and enable Ethernet.
418 General Linux information on the Sun 3 and 3x series (now
420 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
422 If you're not building a kernel for a Sun 3, say N.
425 bool "Sun3 on-board Intel 82586 support"
426 depends on NET_ETHERNET && SUN3
428 This driver enables support for the on-board Intel 82586 based
429 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
430 that this driver does not support 82586-based adapters on additional
434 bool "HP on-board LANCE support"
435 depends on NET_ETHERNET && DIO
438 If you want to use the builtin "LANCE" Ethernet controller on an
439 HP300 machine, say Y here.
442 tristate "Lasi ethernet"
443 depends on NET_ETHERNET && PARISC && GSC_LASI
445 Say Y here to support the on-board Intel 82596 ethernet controller
446 built into Hewlett-Packard PA-RISC machines.
448 config MIPS_JAZZ_SONIC
449 tristate "MIPS JAZZ onboard SONIC Ethernet support"
450 depends on NET_ETHERNET && MACH_JAZZ
452 This is the driver for the onboard card of MIPS Magnum 4000,
453 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
455 config MIPS_AU1X00_ENET
456 bool "MIPS AU1000 Ethernet support"
457 depends on NET_ETHERNET && SOC_AU1X00
461 If you have an Alchemy Semi AU1X00 based system
462 say Y. Otherwise, say N.
464 config NET_SB1250_MAC
465 tristate "SB1250 Ethernet support"
466 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
469 bool "SGI IOC3 Ethernet"
470 depends on NET_ETHERNET && PCI && SGI_IP27
474 If you have a network (Ethernet) card of this type, say Y and read
475 the Ethernet-HOWTO, available from
476 <http://www.tldp.org/docs.html#howto>.
478 config SGI_IOC3_ETH_HW_RX_CSUM
479 bool "Receive hardware checksums"
480 depends on SGI_IOC3_ETH && INET
483 The SGI IOC3 network adapter supports TCP and UDP checksums in
484 hardware to offload processing of these checksums from the CPU. At
485 the moment only acceleration of IPv4 is supported. This option
486 enables offloading for checksums on receive. If unsure, say Y.
488 config SGI_IOC3_ETH_HW_TX_CSUM
489 bool "Transmit hardware checksums"
490 depends on SGI_IOC3_ETH && INET
493 The SGI IOC3 network adapter supports TCP and UDP checksums in
494 hardware to offload processing of these checksums from the CPU. At
495 the moment only acceleration of IPv4 is supported. This option
496 enables offloading for checksums on transmit. If unsure, say Y.
499 tristate "MIPS simulator Network device (EXPERIMENTAL)"
500 depends on MIPS_SIM && EXPERIMENTAL
502 The MIPSNET device is a simple Ethernet network device which is
503 emulated by the MIPS Simulator.
504 If you are not using a MIPSsim or are unsure, say N.
506 config SGI_O2MACE_ETH
507 tristate "SGI O2 MACE Fast Ethernet support"
508 depends on NET_ETHERNET && SGI_IP32=y
511 tristate "National DP83902AV support"
512 depends on NET_ETHERNET && SUPERH
515 Support for cards based on the National Semiconductor DP83902AV
516 ST-NIC Serial Network Interface Controller for Twisted Pair. This
517 is a 10Mbit/sec Ethernet controller. Product overview and specs at
518 <http://www.national.com/pf/DP/DP83902A.html>.
523 tristate "Sun LANCE support"
524 depends on NET_ETHERNET && SBUS
527 This driver supports the "le" interface present on all 32-bit Sparc
528 systems, on some older Ultra systems and as an Sbus option. These
529 cards are based on the AMD Lance chipset, which is better known
530 via the NE2100 cards.
532 To compile this driver as a module, choose M here: the module
533 will be called sunlance.
536 tristate "Sun Happy Meal 10/100baseT support"
537 depends on NET_ETHERNET && (SBUS || PCI)
540 This driver supports the "hme" interface present on most Ultra
541 systems and as an option on older Sbus systems. This driver supports
542 both PCI and Sbus devices. This driver also supports the "qfe" quad
543 100baseT device available in both PCI and Sbus configurations.
545 To compile this driver as a module, choose M here: the module
546 will be called sunhme.
549 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
550 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
553 This driver supports the "be" interface available as an Sbus option.
554 This is Sun's older 100baseT Ethernet device.
556 To compile this driver as a module, choose M here: the module
557 will be called sunbmac.
560 tristate "Sun QuadEthernet support"
561 depends on NET_ETHERNET && SBUS
564 This driver supports the "qe" 10baseT Ethernet device, available as
565 an Sbus option. Note that this is not the same as Quad FastEthernet
566 "qfe" which is supported by the Happy Meal driver instead.
568 To compile this driver as a module, choose M here: the module
569 will be called sunqe.
572 tristate "Sun GEM support"
573 depends on NET_ETHERNET && PCI
576 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
577 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
580 tristate "Sun Cassini support"
581 depends on NET_ETHERNET && PCI
584 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
585 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
587 config NET_VENDOR_3COM
589 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
591 If you have a network (Ethernet) card belonging to this class, say Y
592 and read the Ethernet-HOWTO, available from
593 <http://www.tldp.org/docs.html#howto>.
595 Note that the answer to this question doesn't directly affect the
596 kernel: saying N will just cause the configurator to skip all
597 the questions about 3COM cards. If you say Y, you will be asked for
598 your specific card in the following questions.
601 tristate "3c501 \"EtherLink\" support"
602 depends on NET_VENDOR_3COM && ISA
604 If you have a network (Ethernet) card of this type, say Y and read
605 the Ethernet-HOWTO, available from
606 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
607 new card, since the 3c501 is slow, broken, and obsolete: you will
608 have problems. Some people suggest to ping ("man ping") a nearby
609 machine every minute ("man cron") when using this card.
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 3c501.
616 tristate "3c503 \"EtherLink II\" support"
617 depends on NET_VENDOR_3COM && ISA
620 If you have a network (Ethernet) card of this type, say Y and read
621 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 3c503.
629 tristate "3c505 \"EtherLink Plus\" support"
630 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
632 Information about this network (Ethernet) card can be found in
633 <file:Documentation/networking/3c505.txt>. If you have a card of
634 this type, say Y and read the Ethernet-HOWTO, available from
635 <http://www.tldp.org/docs.html#howto>.
637 To compile this driver as a module, choose M here and read
638 <file:Documentation/networking/net-modules.txt>. The module
639 will be called 3c505.
642 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
643 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
645 If you have a network (Ethernet) card of this type, say Y and read
646 the Ethernet-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here and read
650 <file:Documentation/networking/net-modules.txt>. The module
651 will be called 3c507.
654 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
655 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
657 If you have a network (Ethernet) card belonging to the 3Com
658 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
659 from <http://www.tldp.org/docs.html#howto>.
661 If your card is not working you may need to use the DOS
662 setup disk to disable Plug & Play mode, and to select the default
665 To compile this driver as a module, choose M here and read
666 <file:Documentation/networking/net-modules.txt>. The module
667 will be called 3c509.
670 tristate "3c515 ISA \"Fast EtherLink\""
671 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
673 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
674 network card, say Y and read the Ethernet-HOWTO, available from
675 <http://www.tldp.org/docs.html#howto>.
677 To compile this driver as a module, choose M here and read
678 <file:Documentation/networking/net-modules.txt>. The module
679 will be called 3c515.
682 tristate "3c523 \"EtherLink/MC\" support"
683 depends on NET_VENDOR_3COM && MCA_LEGACY
685 If you have a network (Ethernet) card of this type, say Y and read
686 the Ethernet-HOWTO, available from
687 <http://www.tldp.org/docs.html#howto>.
689 To compile this driver as a module, choose M here and read
690 <file:Documentation/networking/net-modules.txt>. The module
691 will be called 3c523.
694 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
695 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
697 If you have a network (Ethernet) card of this type, say Y and read
698 the Ethernet-HOWTO, available from
699 <http://www.tldp.org/docs.html#howto>.
701 To compile this driver as a module, choose M here and read
702 <file:Documentation/networking/net-modules.txt>. The module
703 will be called 3c527.
706 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
707 depends on NET_VENDOR_3COM && (PCI || EISA)
710 This option enables driver support for a large number of 10Mbps and
711 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
713 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
714 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
715 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
716 "Tornado" (3c905) PCI
717 "Hurricane" (3c555/3cSOHO) PCI
719 If you have such a card, say Y and read the Ethernet-HOWTO,
720 available from <http://www.tldp.org/docs.html#howto>. More
721 specific information is in
722 <file:Documentation/networking/vortex.txt> and in the comments at
723 the beginning of <file:drivers/net/3c59x.c>.
725 To compile this support as a module, choose M here and read
726 <file:Documentation/networking/net-modules.txt>.
729 tristate "3cr990 series \"Typhoon\" support"
730 depends on NET_VENDOR_3COM && PCI
733 This option enables driver support for the 3cr990 series of cards:
735 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
736 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
737 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
739 If you have a network (Ethernet) card of this type, say Y and read
740 the Ethernet-HOWTO, available from
741 <http://www.tldp.org/docs.html#howto>.
743 To compile this driver as a module, choose M here and read
744 <file:Documentation/networking/net-modules.txt>. The module
745 will be called typhoon.
748 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
749 depends on NET_ETHERNET && ISA && ISA_DMA_API
751 If you have a network (Ethernet) card of this type, say Y and read
752 the Ethernet-HOWTO, available from
753 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
756 To compile this driver as a module, choose M here: the module
757 will be called lance. This is recommended.
759 config NET_VENDOR_SMC
760 bool "Western Digital/SMC cards"
761 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
763 If you have a network (Ethernet) card belonging to this class, say Y
764 and read the Ethernet-HOWTO, available from
765 <http://www.tldp.org/docs.html#howto>.
767 Note that the answer to this question doesn't directly affect the
768 kernel: saying N will just cause the configurator to skip all
769 the questions about Western Digital cards. If you say Y, you will be
770 asked for your specific card in the following questions.
773 tristate "WD80*3 support"
774 depends on NET_VENDOR_SMC && ISA
777 If you have a network (Ethernet) card of this type, say Y and read
778 the Ethernet-HOWTO, available from
779 <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
786 tristate "SMC Ultra MCA support"
787 depends on NET_VENDOR_SMC && MCA
790 If you have a network (Ethernet) card of this type and are running
791 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
792 available from <http://www.tldp.org/docs.html#howto>.
794 To compile this driver as a module, choose M here and read
795 <file:Documentation/networking/net-modules.txt>. The module
796 will be called smc-mca.
799 tristate "SMC Ultra support"
800 depends on NET_VENDOR_SMC && ISA
803 If you have a network (Ethernet) card of this type, say Y and read
804 the Ethernet-HOWTO, available from
805 <http://www.tldp.org/docs.html#howto>.
807 Important: There have been many reports that, with some motherboards
808 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
809 such as some BusLogic models) causes corruption problems with many
810 operating systems. The Linux smc-ultra driver has a work-around for
811 this but keep it in mind if you have such a SCSI card and have
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-ultra.
819 tristate "SMC Ultra32 EISA support"
820 depends on NET_VENDOR_SMC && EISA
823 If you have a network (Ethernet) card of this type, say Y and read
824 the Ethernet-HOWTO, available from
825 <http://www.tldp.org/docs.html#howto>.
827 To compile this driver as a module, choose M here and read
828 <file:Documentation/networking/net-modules.txt>. The module
829 will be called smc-ultra32.
832 tristate "SMC 91C9x/91C1xxx support"
835 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00)
837 This is a driver for SMC's 91x series of Ethernet chipsets,
838 including the SMC91C94 and the SMC91C111. Say Y if you want it
839 compiled into the kernel, and read the file
840 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
841 available from <http://www.linuxdoc.org/docs.html#howto>.
843 This driver is also available as a module ( = code which can be
844 inserted in and removed from the running kernel whenever you want).
845 The module will be called smc91x. If you want to compile it as a
846 module, say M here and read <file:Documentation/modules.txt> as well
847 as <file:Documentation/networking/net-modules.txt>.
850 tristate "SMC 9194 support"
851 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
854 This is support for the SMC9xxx based Ethernet cards. Choose this
855 option if you have a DELL laptop with the docking station, or
856 another SMC9192/9194 based chipset. Say Y if you want it compiled
857 into the kernel, and read the file
858 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
859 available from <http://www.tldp.org/docs.html#howto>.
861 To compile this driver as a module, choose M here and read
862 <file:Documentation/networking/net-modules.txt>. The module
863 will be called smc9194.
866 tristate "NetX Ethernet support"
868 depends on NET_ETHERNET && ARCH_NETX
870 This is support for the Hilscher netX builtin Ethernet ports
872 To compile this driver as a module, choose M here and read
873 <file:Documentation/networking/net-modules.txt>. The module
874 will be called netx-eth.
877 tristate "DM9000 support"
878 depends on (ARM || MIPS) && NET_ETHERNET
882 Support for DM9000 chipset.
884 To compile this driver as a module, choose M here and read
885 <file:Documentation/networking/net-modules.txt>. The module will be
889 tristate "SMSC LAN911[5678] support"
892 depends on NET_ETHERNET && ARCH_PXA
894 This is a driver for SMSC's LAN911x series of Ethernet chipsets
895 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
896 Say Y if you want it compiled into the kernel,
897 and read the Ethernet-HOWTO, available from
898 <http://www.linuxdoc.org/docs.html#howto>.
900 This driver is also available as a module. The module will be
901 called smc911x. If you want to compile it as a module, say M
902 here and read <file:Documentation/modules.txt>
904 config NET_VENDOR_RACAL
905 bool "Racal-Interlan (Micom) NI cards"
906 depends on NET_ETHERNET && ISA
908 If you have a network (Ethernet) card belonging to this class, such
909 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
910 available from <http://www.tldp.org/docs.html#howto>.
912 Note that the answer to this question doesn't directly affect the
913 kernel: saying N will just cause the configurator to skip all
914 the questions about NI cards. If you say Y, you will be asked for
915 your specific card in the following questions.
918 tristate "NI5010 support (EXPERIMENTAL)"
919 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
921 If you have a network (Ethernet) card of this type, say Y and read
922 the Ethernet-HOWTO, available from
923 <http://www.tldp.org/docs.html#howto>. Note that this is still
926 To compile this driver as a module, choose M here and read
927 <file:Documentation/networking/net-modules.txt>. The module
928 will be called ni5010.
931 tristate "NI5210 support"
932 depends on NET_VENDOR_RACAL && ISA
934 If you have a network (Ethernet) card of this type, say Y and read
935 the Ethernet-HOWTO, available from
936 <http://www.tldp.org/docs.html#howto>.
938 To compile this driver as a module, choose M here and read
939 <file:Documentation/networking/net-modules.txt>. The module
943 tristate "NI6510 support"
944 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
946 If you have a network (Ethernet) card of this type, say Y and read
947 the Ethernet-HOWTO, available from
948 <http://www.tldp.org/docs.html#howto>.
950 To compile this driver as a module, choose M here and read
951 <file:Documentation/networking/net-modules.txt>. The module
954 source "drivers/net/tulip/Kconfig"
957 tristate "AT1700/1720 support (EXPERIMENTAL)"
958 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
961 If you have a network (Ethernet) card of this type, say Y and read
962 the Ethernet-HOWTO, available from
963 <http://www.tldp.org/docs.html#howto>.
965 To compile this driver as a module, choose M here and read
966 <file:Documentation/networking/net-modules.txt>. The module
967 will be called at1700.
970 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
971 depends on NET_ETHERNET && (ISA || EISA || MCA)
974 If you have a network (Ethernet) card of this type, say Y and read
975 the Ethernet-HOWTO, available from
976 <http://www.tldp.org/docs.html#howto> as well as
977 <file:drivers/net/depca.c>.
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 depca.
984 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
985 depends on NET_ETHERNET && (ISA || EISA || PCI)
987 If you have a network (Ethernet) card of this type, say Y and read
988 the Ethernet-HOWTO, available from
989 <http://www.tldp.org/docs.html#howto>.
991 To compile this driver as a module, choose M here and read
992 <file:Documentation/networking/net-modules.txt>. The module
993 will be called hp100.
996 bool "Other ISA cards"
997 depends on NET_ETHERNET && ISA
999 If your network (Ethernet) card hasn't been mentioned yet and its
1000 bus system (that's the way the cards talks to the other components
1001 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1002 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1003 available from <http://www.tldp.org/docs.html#howto>.
1007 Note that the answer to this question doesn't directly affect the
1008 kernel: saying N will just cause the configurator to skip all
1009 the remaining ISA network card questions. If you say Y, you will be
1010 asked for your specific card in the following questions.
1013 tristate "Cabletron E21xx 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 e2100.
1026 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1030 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1031 cards. If this is for you, say Y and read
1032 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1033 well as the Ethernet-HOWTO, available from
1034 <http://www.tldp.org/docs.html#howto>.
1036 To compile this driver as a module, choose M here and read
1037 <file:Documentation/networking/net-modules.txt>. The module
1038 will be called ewrk3.
1041 tristate "EtherExpress 16 support"
1044 If you have an EtherExpress16 network (Ethernet) card, say Y and
1045 read the Ethernet-HOWTO, available from
1046 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1047 EtherExpress16 card used to be regarded as a very poor choice
1048 because the driver was very unreliable. We now have a new driver
1049 that should do better.
1051 To compile this driver as a module, choose M here and read
1052 <file:Documentation/networking/net-modules.txt>. The module
1053 will be called eexpress.
1056 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1059 If you have a network (Ethernet) card of this type, say Y. This
1060 driver supports Intel i82595{FX,TX} based boards. Note however
1061 that the EtherExpress PRO/100 Ethernet card has its own separate
1062 driver. Please read the Ethernet-HOWTO, available from
1063 <http://www.tldp.org/docs.html#howto>.
1065 To compile this driver as a module, choose M here and read
1066 <file:Documentation/networking/net-modules.txt>. The module
1067 will be called eepro.
1070 tristate "HP PCLAN+ (27247B and 27252A) support"
1074 If you have a network (Ethernet) card of this type, say Y and read
1075 the Ethernet-HOWTO, available from
1076 <http://www.tldp.org/docs.html#howto>.
1078 To compile this driver as a module, choose M here and read
1079 <file:Documentation/networking/net-modules.txt>. The module
1080 will be called hp-plus.
1083 tristate "HP PCLAN (27245 and other 27xxx series) support"
1087 If you have a network (Ethernet) card of this type, say Y and read
1088 the Ethernet-HOWTO, available from
1089 <http://www.tldp.org/docs.html#howto>.
1091 To compile this driver as a module, choose M here and read
1092 <file:Documentation/networking/net-modules.txt>. The module
1096 tristate "LP486E on board Ethernet"
1099 Say Y here to support the 82596-based on-board Ethernet controller
1100 for the Panther motherboard, which is one of the two shipped in the
1101 Intel Professional Workstation.
1104 tristate "ICL EtherTeam 16i/32 support"
1107 If you have a network (Ethernet) card of this type, say Y and read
1108 the Ethernet-HOWTO, available from
1109 <http://www.tldp.org/docs.html#howto>.
1111 To compile this driver as a module, choose M here and read
1112 <file:Documentation/networking/net-modules.txt>. The module
1113 will be called eth16i.
1116 tristate "NE2000/NE1000 support"
1117 depends on NET_ISA || (Q40 && m) || M32R
1120 If you have a network (Ethernet) card of this type, say Y and read
1121 the Ethernet-HOWTO, available from
1122 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1123 without a specific driver are compatible with NE2000.
1125 If you have a PCI NE2000 card however, say N here and Y to "PCI
1126 NE2000 and clone support" under "EISA, VLB, PCI and on board
1127 controllers" below. If you have a NE2000 card and are running on
1128 an MCA system (a bus system used on some IBM PS/2 computers and
1129 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1132 To compile this driver as a module, choose M here and read
1133 <file:Documentation/networking/net-modules.txt>. The module
1137 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1138 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1140 The Zenith Z-Note notebook computer has a built-in network
1141 (Ethernet) card, and this is the Linux driver for it. Note that the
1142 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1143 by this driver. Read the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1147 tristate "SEEQ8005 support (EXPERIMENTAL)"
1148 depends on NET_ISA && EXPERIMENTAL
1150 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1151 is for you, read the Ethernet-HOWTO, available from
1152 <http://www.tldp.org/docs.html#howto>.
1154 To compile this driver as a module, choose M here and read
1155 <file:Documentation/networking/net-modules.txt>. The module
1156 will be called seeq8005.
1159 tristate "NE/2 (ne2000 MCA version) support"
1160 depends on NET_ETHERNET && MCA_LEGACY
1163 If you have a network (Ethernet) card of this type, say Y and read
1164 the Ethernet-HOWTO, available from
1165 <http://www.tldp.org/docs.html#howto>.
1167 To compile this driver as a module, choose M here and read
1168 <file:Documentation/networking/net-modules.txt>. The module
1172 tristate "IBM LAN Adapter/A support"
1173 depends on NET_ETHERNET && MCA && MCA_LEGACY
1175 This is a Micro Channel Ethernet adapter. You need to set
1176 CONFIG_MCA to use this driver. It is both available as an in-kernel
1177 driver and as a module.
1179 To compile this driver as a module, choose M here and read
1180 <file:Documentation/networking/net-modules.txt>. The only
1181 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1182 will both support 16K and 32K memory windows, however a 32K window
1183 gives a better security against packet losses. Usage of multiple
1184 boards with this driver should be possible, but has not been tested
1185 up to now due to lack of hardware.
1188 tristate "IBM LAN Virtual Ethernet support"
1189 depends on NET_ETHERNET && PPC_PSERIES
1191 This driver supports virtual ethernet adapters on newer IBM iSeries
1192 and pSeries systems.
1194 To compile this driver as a module, choose M here and read
1195 <file:Documentation/networking/net-modules.txt>. The module will
1199 tristate "PowerPC 4xx on-chip Ethernet support"
1202 This driver supports the PowerPC 4xx EMAC family of on-chip
1203 Ethernet controllers.
1206 int "Number of receive buffers"
1211 int "Number of transmit buffers"
1215 config IBM_EMAC_POLL_WEIGHT
1216 int "MAL NAPI polling weight"
1220 config IBM_EMAC_RX_COPY_THRESHOLD
1221 int "RX skb copy threshold (bytes)"
1225 config IBM_EMAC_RX_SKB_HEADROOM
1226 int "Additional RX skb headroom (bytes)"
1230 Additional receive skb headroom. Note, that driver
1231 will always reserve at least 2 bytes to make IP header
1232 aligned, so usually there is no need to add any additional
1235 If unsure, set to 0.
1237 config IBM_EMAC_PHY_RX_CLK_FIX
1238 bool "PHY Rx clock workaround"
1239 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1241 Enable this if EMAC attached to a PHY which doesn't generate
1242 RX clock if there is no link, if this is the case, you will
1243 see "TX disable timeout" or "RX disable timeout" in the system
1248 config IBM_EMAC_DEBUG
1253 config IBM_EMAC_ZMII
1255 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1258 config IBM_EMAC_RGMII
1260 depends on IBM_EMAC && 440GX
1265 depends on IBM_EMAC && 440GX
1269 bool "EISA, VLB, PCI and on board controllers"
1270 depends on NET_ETHERNET && (ISA || EISA || PCI)
1272 This is another class of network cards which attach directly to the
1273 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1274 available from <http://www.tldp.org/docs.html#howto>.
1276 Note that the answer to this question doesn't directly affect the
1277 kernel: saying N will just cause the configurator to skip all
1278 the questions about this class of network cards. If you say Y, you
1279 will be asked for your specific card in the following questions. If
1280 you are unsure, say Y.
1283 tristate "AMD PCnet32 PCI support"
1284 depends on NET_PCI && PCI
1288 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1289 answer Y here and read the Ethernet-HOWTO, available from
1290 <http://www.tldp.org/docs.html#howto>.
1292 To compile this driver as a module, choose M here and read
1293 <file:Documentation/networking/net-modules.txt>. The module
1294 will be called pcnet32.
1297 bool "Use RX polling (NAPI) (EXPERIMENTAL)"
1298 depends on PCNET32 && EXPERIMENTAL
1300 NAPI is a new driver API designed to reduce CPU and interrupt load
1301 when the driver is receiving lots of packets from the card. It is
1302 still somewhat experimental and thus not yet enabled by default.
1304 If your estimated Rx load is 10kpps or more, or if the card will be
1305 deployed on potentially unfriendly networks (e.g. in a firewall),
1308 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1314 tristate "AMD 8111 (new PCI lance) support"
1315 depends on NET_PCI && PCI
1319 If you have an AMD 8111-based PCI lance ethernet card,
1320 answer Y here and read the Ethernet-HOWTO, available from
1321 <http://www.tldp.org/docs.html#howto>.
1323 To compile this driver as a module, choose M here and read
1324 <file:Documentation/networking/net-modules.txt>. The module
1325 will be called amd8111e.
1326 config AMD8111E_NAPI
1327 bool "Enable NAPI support"
1328 depends on AMD8111_ETH
1330 NAPI is a new driver API designed to reduce CPU and interrupt load
1331 when the driver is receiving lots of packets from the card. It is
1332 still somewhat experimental and thus not yet enabled by default.
1334 If your estimated Rx load is 10kpps or more, or if the card will be
1335 deployed on potentially unfriendly networks (e.g. in a firewall),
1338 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1343 config ADAPTEC_STARFIRE
1344 tristate "Adaptec Starfire/DuraLAN support"
1345 depends on NET_PCI && PCI
1349 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1350 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1351 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1354 To compile this driver as a module, choose M here: the module
1355 will be called starfire. This is recommended.
1357 config ADAPTEC_STARFIRE_NAPI
1358 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1359 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1361 NAPI is a new driver API designed to reduce CPU and interrupt load
1362 when the driver is receiving lots of packets from the card. It is
1363 still somewhat experimental and thus not yet enabled by default.
1365 If your estimated Rx load is 10kpps or more, or if the card will be
1366 deployed on potentially unfriendly networks (e.g. in a firewall),
1369 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1375 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1376 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1379 If you have a network (Ethernet) card of this type, say Y and read
1380 the Ethernet-HOWTO, available from
1381 <http://www.tldp.org/docs.html#howto>.
1383 To compile this driver as a module, choose M here and read
1384 <file:Documentation/networking/net-modules.txt>. The module
1385 will be called ac3200.
1388 tristate "Apricot Xen-II on board Ethernet"
1389 depends on NET_PCI && ISA
1391 If you have a network (Ethernet) controller of this type, say Y and
1392 read the Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto>.
1395 To compile this driver as a module, choose M here and read
1396 <file:Documentation/networking/net-modules.txt>. The module will be
1400 tristate "Broadcom 4400 ethernet support"
1401 depends on NET_PCI && PCI
1404 If you have a network (Ethernet) controller of this type, say Y and
1405 read the Ethernet-HOWTO, available from
1406 <http://www.tldp.org/docs.html#howto>.
1408 To compile this driver as a module, choose M here and read
1409 <file:Documentation/networking/net-modules.txt>. The module will be
1413 tristate "nForce Ethernet support"
1414 depends on NET_PCI && PCI
1416 If you have a network (Ethernet) controller of this type, say Y and
1417 read the Ethernet-HOWTO, available from
1418 <http://www.tldp.org/docs.html#howto>.
1420 To compile this driver as a module, choose M here and read
1421 <file:Documentation/networking/net-modules.txt>. The module will be
1424 config FORCEDETH_NAPI
1425 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1426 depends on FORCEDETH && EXPERIMENTAL
1428 NAPI is a new driver API designed to reduce CPU and interrupt load
1429 when the driver is receiving lots of packets from the card. It is
1430 still somewhat experimental and thus not yet enabled by default.
1432 If your estimated Rx load is 10kpps or more, or if the card will be
1433 deployed on potentially unfriendly networks (e.g. in a firewall),
1436 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1442 tristate "CS89x0 support"
1443 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1445 Support for CS89x0 chipset based Ethernet cards. If you have a
1446 network (Ethernet) card of this type, say Y and read the
1447 Ethernet-HOWTO, available from
1448 <http://www.tldp.org/docs.html#howto> as well as
1449 <file:Documentation/networking/cs89x0.txt>.
1451 To compile this driver as a module, choose M here and read
1452 <file:Documentation/networking/net-modules.txt>. The module will be
1456 tristate "TOSHIBA TC35815 Ethernet support"
1457 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1460 tristate "Digi Intl. RightSwitch SE-X support"
1461 depends on NET_PCI && (PCI || EISA)
1463 This is support for the Digi International RightSwitch series of
1464 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1465 models. If you have a network card of this type, say Y and read the
1466 Ethernet-HOWTO, available from
1467 <http://www.tldp.org/docs.html#howto>. More specific
1468 information is contained in <file:Documentation/networking/dgrs.txt>.
1470 To compile this driver as a module, choose M here and read
1471 <file:Documentation/networking/net-modules.txt>. The module
1472 will be called dgrs.
1475 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1476 depends on NET_PCI && PCI
1479 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1480 card, say Y and read the Ethernet-HOWTO, available from
1481 <http://www.tldp.org/docs.html#howto>.
1483 To compile this driver as a module, choose M here and read
1484 <file:Documentation/networking/net-modules.txt>. The module
1485 will be called eepro100.
1489 tristate "Intel(R) PRO/100+ support"
1490 depends on NET_PCI && PCI
1493 This driver supports Intel(R) PRO/100 family of adapters.
1494 To verify that your adapter is supported, find the board ID number
1495 on the adapter. Look for a label that has a barcode and a number
1496 in the format 123456-001 (six digits hyphen three digits).
1498 Use the above information and the Adapter & Driver ID Guide at:
1500 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1502 to identify the adapter.
1504 For the latest Intel PRO/100 network driver for Linux, see:
1506 <http://appsr.intel.com/scripts-df/support_intel.asp>
1508 More specific information on configuring the driver is in
1509 <file:Documentation/networking/e100.txt>.
1511 To compile this driver as a module, choose M here and read
1512 <file:Documentation/networking/net-modules.txt>. The module
1513 will be called e100.
1516 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1517 depends on NET_PCI && EISA && EXPERIMENTAL
1520 If you have a network (Ethernet) card of this type, say Y and read
1521 the Ethernet-HOWTO, available from
1522 <http://www.tldp.org/docs.html#howto>.
1524 To compile this driver as a module, choose M here and read
1525 <file:Documentation/networking/net-modules.txt>. The module
1526 will be called lne390.
1529 tristate "Myson MTD-8xx PCI Ethernet support"
1530 depends on NET_PCI && PCI
1534 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1535 cards. Specifications and data at
1536 <http://www.myson.com.hk/mtd/datasheet/>.
1539 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1540 depends on NET_PCI && PCI
1543 This driver is for the National Semiconductor DP83810 series,
1544 which is used in cards from PureData, NetGear, Linksys
1545 and others, including the 83815 chip.
1546 More specific information and updates are available from
1547 <http://www.scyld.com/network/natsemi.html>.
1550 tristate "PCI NE2000 and clones support (see help)"
1551 depends on NET_PCI && PCI
1554 This driver is for NE2000 compatible PCI cards. It will not work
1555 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1556 support" below). If you have a PCI NE2000 network (Ethernet) card,
1557 say Y and read the Ethernet-HOWTO, available from
1558 <http://www.tldp.org/docs.html#howto>.
1560 This driver also works for the following NE2000 clone cards:
1561 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1562 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1563 Holtek HT80232 Holtek HT80229
1565 To compile this driver as a module, choose M here and read
1566 <file:Documentation/networking/net-modules.txt>. The module
1567 will be called ne2k-pci.
1570 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1571 depends on NET_PCI && EISA && EXPERIMENTAL
1574 If you have a network (Ethernet) card of this type, say Y and read
1575 the Ethernet-HOWTO, available from
1576 <http://www.tldp.org/docs.html#howto>. Note that this driver
1577 will NOT WORK for NE3200 cards as they are completely different.
1579 To compile this driver as a module, choose M here and read
1580 <file:Documentation/networking/net-modules.txt>. The module
1581 will be called ne3210.
1584 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1585 depends on NET_PCI && EISA && EXPERIMENTAL
1588 If you have a network (Ethernet) card of this type, say Y and read
1589 the Ethernet-HOWTO, available from
1590 <http://www.tldp.org/docs.html#howto>.
1592 To compile this driver as a module, choose M here and read
1593 <file:Documentation/networking/net-modules.txt>. The module
1594 will be called es3210.
1597 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1598 depends on NET_PCI && PCI && EXPERIMENTAL
1602 This is a driver for the Fast Ethernet PCI network cards based on
1603 the RTL8139C+ chips. If you have one of those, say Y and read
1604 the Ethernet-HOWTO, available from
1605 <http://www.tldp.org/docs.html#howto>.
1607 To compile this driver as a module, choose M here: the module
1608 will be called 8139cp. This is recommended.
1611 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1612 depends on NET_PCI && PCI
1616 This is a driver for the Fast Ethernet PCI network cards based on
1617 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1618 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1620 To compile this driver as a module, choose M here: the module
1621 will be called 8139too. This is recommended.
1624 bool "Use PIO instead of MMIO"
1628 This instructs the driver to use programmed I/O ports (PIO) instead
1629 of PCI shared memory (MMIO). This can possibly solve some problems
1630 in case your mainboard has memory consistency issues. If unsure,
1633 config 8139TOO_TUNE_TWISTER
1634 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1637 This implements a function which might come in handy in case you
1638 are using low quality on long cabling. It is required for RealTek
1639 RTL-8139 revision K boards, and totally unused otherwise. It tries
1640 to match the transceiver to the cable characteristics. This is
1641 experimental since hardly documented by the manufacturer.
1645 bool "Support for older RTL-8129/8130 boards"
1648 This enables support for the older and uncommon RTL-8129 and
1649 RTL-8130 chips, which support MII via an external transceiver,
1650 instead of an internal one. Disabling this option will save some
1651 memory by making the code size smaller. If unsure, say Y.
1653 config 8139_OLD_RX_RESET
1654 bool "Use older RX-reset method"
1657 The 8139too driver was recently updated to contain a more rapid
1658 reset sequence, in the face of severe receive errors. This "new"
1659 RX-reset method should be adequate for all boards. But if you
1660 experience problems, you can enable this option to restore the
1661 old RX-reset behavior. If unsure, say N.
1664 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1665 depends on NET_PCI && PCI
1669 This is a driver for the Fast Ethernet PCI network cards based on
1670 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1671 SiS 630 and SiS 540 chipsets.
1673 This driver also supports AMD 79C901 HomePNA so that you can use
1674 your phone line as a network cable.
1676 To compile this driver as a module, choose M here: the module
1677 will be called sis900. This is recommended.
1680 tristate "SMC EtherPower II"
1681 depends on NET_PCI && PCI
1685 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1686 which is based on the SMC83c17x (EPIC/100).
1687 More specific information and updates are available from
1688 <http://www.scyld.com/network/epic100.html>.
1691 tristate "Sundance Alta support"
1692 depends on NET_PCI && PCI
1696 This driver is for the Sundance "Alta" chip.
1697 More specific information and updates are available from
1698 <http://www.scyld.com/network/sundance.html>.
1700 config SUNDANCE_MMIO
1701 bool "Use MMIO instead of PIO"
1704 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1705 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1706 is known to solve bugs on certain chips.
1711 tristate "TI ThunderLAN support"
1712 depends on NET_PCI && (PCI || EISA) && !64BIT
1714 If you have a PCI Ethernet network card based on the ThunderLAN chip
1715 which is supported by this driver, say Y and read the
1716 Ethernet-HOWTO, available from
1717 <http://www.tldp.org/docs.html#howto>.
1719 Devices currently supported by this driver are Compaq Netelligent,
1720 Compaq NetFlex and Olicom cards. Please read the file
1721 <file:Documentation/networking/tlan.txt> for more details.
1723 To compile this driver as a module, choose M here and read
1724 <file:Documentation/networking/net-modules.txt>. The module
1725 will be called tlan.
1727 Please email feedback to <torben.mathiasen@compaq.com>.
1730 tristate "VIA Rhine support"
1731 depends on NET_PCI && PCI
1735 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1736 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1737 Ethernet functions can also be found integrated on South Bridges
1740 To compile this driver as a module, choose M here. The module
1741 will be called via-rhine.
1743 config VIA_RHINE_MMIO
1744 bool "Use MMIO instead of PIO"
1745 depends on VIA_RHINE
1747 This instructs the driver to use PCI shared memory (MMIO) instead of
1748 programmed I/O ports (PIO). Enabling this gives an improvement in
1749 processing time in parts of the driver.
1753 config VIA_RHINE_NAPI
1754 bool "Use Rx Polling (NAPI)"
1755 depends on VIA_RHINE
1757 NAPI is a new driver API designed to reduce CPU and interrupt load
1758 when the driver is receiving lots of packets from the card.
1760 If your estimated Rx load is 10kpps or more, or if the card will be
1761 deployed on potentially unfriendly networks (e.g. in a firewall),
1764 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1768 bool "Philips SAA9730 Ethernet support"
1769 depends on NET_PCI && PCI && MIPS_ATLAS
1771 The SAA9730 is a combined multimedia and peripheral controller used
1772 in thin clients, Internet access terminals, and diskless
1774 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1777 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1778 depends on NET_PCI && PCI && EXPERIMENTAL
1781 This is a driver for the Fast Ethernet PCI network cards based on
1782 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1783 have one of these, say Y here.
1785 To compile this driver as a module, choose M here: the module
1786 will be called sc92031. This is recommended.
1789 bool "Pocket and portable adapters"
1790 depends on NET_ETHERNET && PARPORT
1792 Cute little network (Ethernet) devices which attach to the parallel
1793 port ("pocket adapters"), commonly used with laptops. If you have
1794 one of those, say Y and read the Ethernet-HOWTO, available from
1795 <http://www.tldp.org/docs.html#howto>.
1797 If you want to plug a network (or some other) card into the PCMCIA
1798 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1799 credit card size extension cards used by all modern laptops), you
1800 need the pcmcia-cs package (location contained in the file
1801 <file:Documentation/Changes>) and you can say N here.
1803 Laptop users should read the Linux Laptop home page at
1804 <http://www.linux-on-laptops.com/> or
1805 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1807 Note that the answer to this question doesn't directly affect the
1808 kernel: saying N will just cause the configurator to skip all
1809 the questions about this class of network devices. If you say Y, you
1810 will be asked for your specific device in the following questions.
1813 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1814 depends on NET_POCKET && PARPORT && X86
1817 This is a network (Ethernet) device which attaches to your parallel
1818 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1819 available from <http://www.tldp.org/docs.html#howto>, if you
1820 want to use this. If you intend to use this driver, you should have
1821 said N to the "Parallel printer support", because the two drivers
1822 don't like each other.
1824 To compile this driver as a module, choose M here: the module
1828 tristate "D-Link DE600 pocket adapter support"
1829 depends on NET_POCKET && PARPORT
1831 This is a network (Ethernet) device which attaches to your parallel
1832 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1833 Ethernet-HOWTO, available from
1834 <http://www.tldp.org/docs.html#howto>, if you want to use
1835 this. It is possible to have several devices share a single parallel
1836 port and it is safe to compile the corresponding drivers into the
1839 To compile this driver as a module, choose M here: the module
1840 will be called de600.
1843 tristate "D-Link DE620 pocket adapter support"
1844 depends on NET_POCKET && PARPORT
1846 This is a network (Ethernet) device which attaches to your parallel
1847 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1848 Ethernet-HOWTO, available from
1849 <http://www.tldp.org/docs.html#howto>, if you want to use
1850 this. It is possible to have several devices share a single parallel
1851 port and it is safe to compile the corresponding drivers into the
1854 To compile this driver as a module, choose M here: the module
1855 will be called de620.
1858 tristate "SGI Seeq ethernet controller support"
1859 depends on NET_ETHERNET && SGI_IP22
1861 Say Y here if you have an Seeq based Ethernet network card. This is
1862 used in many Silicon Graphics machines.
1865 tristate "DEC LANCE ethernet controller support"
1866 depends on NET_ETHERNET && MACH_DECSTATION
1869 This driver is for the series of Ethernet controllers produced by
1870 DEC (now Compaq) based on the AMD Lance chipset, including the
1871 DEPCA series. (This chipset is better known via the NE2100 cards.)
1874 bool "Motorola 68360 ethernet controller"
1877 Say Y here if you want to use the built-in ethernet controller of
1878 the Motorola 68360 processor.
1881 bool "FEC ethernet controller (of ColdFire CPUs)"
1882 depends on M523x || M527x || M5272 || M528x || M520x
1884 Say Y here if you want to use the built-in 10/100 Fast ethernet
1885 controller on some Motorola ColdFire processors.
1888 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1891 Say Y here if you want to use the second built-in 10/100 Fast
1892 ethernet controller on some Motorola ColdFire processors.
1895 tristate "NE2000 compatible support for H8/300"
1896 depends on H8300 && NET_ETHERNET
1898 Say Y here if you want to use the NE2000 compatible
1899 controller on the Renesas H8/300 processor.
1901 source "drivers/net/fec_8xx/Kconfig"
1902 source "drivers/net/fs_enet/Kconfig"
1910 menu "Ethernet (1000 Mbit)"
1914 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1917 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1918 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1919 adapter. The driver allows for using the Jumbo Frame option (9000
1920 bytes/frame) however it requires that your switches can handle this
1921 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1924 To compile this driver as a module, choose M here: the
1925 module will be called acenic.
1927 config ACENIC_OMIT_TIGON_I
1928 bool "Omit support for old Tigon I based AceNICs"
1931 Say Y here if you only have Tigon II based AceNICs and want to leave
1932 out support for the older Tigon I based cards which are no longer
1933 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1934 version)). This will reduce the size of the driver object by
1935 app. 100KB. If you are not sure whether your card is a Tigon I or a
1936 Tigon II, say N here.
1938 The safe and default value for this is N.
1941 tristate "D-Link DL2000-based Gigabit Ethernet support"
1945 This driver supports D-Link 2000-based gigabit ethernet cards, which
1947 D-Link DGE-550T Gigabit Ethernet Adapter.
1948 D-Link DL2000-based Gigabit Ethernet Adapter.
1950 To compile this driver as a module, choose M here: the
1951 module will be called dl2k.
1954 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1957 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1958 adapters. For more information on how to identify your adapter, go
1959 to the Adapter & Driver ID Guide at:
1961 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1963 For general information and support, go to the Intel support
1966 <http://support.intel.com>
1968 More specific information on configuring the driver is in
1969 <file:Documentation/networking/e1000.txt>.
1971 To compile this driver as a module, choose M here and read
1972 <file:Documentation/networking/net-modules.txt>. The module
1973 will be called e1000.
1976 bool "Use Rx Polling (NAPI)"
1979 NAPI is a new driver API designed to reduce CPU and interrupt load
1980 when the driver is receiving lots of packets from the card. It is
1981 still somewhat experimental and thus not yet enabled by default.
1983 If your estimated Rx load is 10kpps or more, or if the card will be
1984 deployed on potentially unfriendly networks (e.g. in a firewall),
1987 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1992 config E1000_DISABLE_PACKET_SPLIT
1993 bool "Disable Packet Split for PCI express adapters"
1996 Say Y here if you want to use the legacy receive path for PCI express
2001 source "drivers/net/ixp2000/Kconfig"
2004 tristate "MyriCOM Gigabit Ethernet support"
2007 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2009 To compile this driver as a module, choose M here: the module
2010 will be called myri_sbus. This is recommended.
2013 tristate "National Semiconductor DP83820 support"
2016 This is a driver for the National Semiconductor DP83820 series
2017 of gigabit ethernet MACs. Cards using this chipset include
2018 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2019 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2023 tristate "Packet Engines Hamachi GNIC-II support"
2027 If you have a Gigabit Ethernet card of this type, say Y and read
2028 the Ethernet-HOWTO, available from
2029 <http://www.tldp.org/docs.html#howto>.
2031 To compile this driver as a module, choose M here and read
2032 <file:Documentation/networking/net-modules.txt>. The module will be
2036 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2037 depends on PCI && EXPERIMENTAL
2040 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2041 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2042 used by the Beowulf Linux cluster project. See
2043 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2044 information about this driver in particular and Beowulf in general.
2046 To compile this driver as a module, choose M here: the module
2047 will be called yellowfin. This is recommended.
2050 tristate "Realtek 8169 gigabit ethernet support"
2054 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2056 To compile this driver as a module, choose M here: the module
2057 will be called r8169. This is recommended.
2060 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2061 depends on R8169 && EXPERIMENTAL
2063 NAPI is a new driver API designed to reduce CPU and interrupt load
2064 when the driver is receiving lots of packets from the card. It is
2065 still somewhat experimental and thus not yet enabled by default.
2067 If your estimated Rx load is 10kpps or more, or if the card will be
2068 deployed on potentially unfriendly networks (e.g. in a firewall),
2071 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2078 depends on R8169 && VLAN_8021Q
2080 Say Y here for the r8169 driver to support the functions required
2081 by the kernel 802.1Q code.
2086 tristate "SiS190/SiS191 gigabit ethernet support"
2091 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2092 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2093 appear in lan on motherboard designs which are based on SiS 965
2094 and SiS 966 south bridge.
2096 To compile this driver as a module, choose M here: the module
2097 will be called sis190. This is recommended.
2100 tristate "New SysKonnect GigaEthernet support"
2104 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2105 and related Gigabit Ethernet adapters. It is a new smaller driver
2106 with better performance and more complete ethtool support.
2108 It does not support the link failover and network management
2109 features that "portable" vendor supplied sk98lin driver does.
2111 This driver supports adapters based on the original Yukon chipset:
2112 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2113 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2115 It does not support the newer Yukon2 chipset: a separate driver,
2116 sky2, is provided for Yukon2-based adapters.
2118 To compile this driver as a module, choose M here: the module
2119 will be called skge. This is recommended.
2122 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2126 This driver supports Gigabit Ethernet adapters based on the
2127 Marvell Yukon 2 chipset:
2128 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2129 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2131 There is companion driver for the older Marvell Yukon and
2132 Genesis based adapters: skge.
2134 To compile this driver as a module, choose M here: the module
2135 will be called sky2. This is recommended.
2138 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2141 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2142 compliant Gigabit Ethernet Adapter.
2144 This driver supports the original Yukon chipset. A cleaner driver is
2145 also available (skge) which seems to work better than this one.
2147 This driver does not support the newer Yukon2 chipset. A separate
2148 driver, sky2, is provided to support Yukon2-based adapters.
2150 The following adapters are supported by this driver:
2151 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2152 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2153 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2154 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2155 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2156 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2157 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2158 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2159 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2160 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2161 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2162 - EG1032 v2 Instant Gigabit Network Adapter
2163 - EG1064 v2 Instant Gigabit Network Adapter
2164 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2165 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2166 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2167 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2168 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2169 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2170 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2171 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2172 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2173 - Marvell RDK-8001 Adapter
2174 - Marvell RDK-8002 Adapter
2175 - Marvell RDK-8003 Adapter
2176 - Marvell RDK-8004 Adapter
2177 - Marvell RDK-8006 Adapter
2178 - Marvell RDK-8007 Adapter
2179 - Marvell RDK-8008 Adapter
2180 - Marvell RDK-8009 Adapter
2181 - Marvell RDK-8010 Adapter
2182 - Marvell RDK-8011 Adapter
2183 - Marvell RDK-8012 Adapter
2184 - Marvell RDK-8052 Adapter
2185 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2186 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2187 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2188 - SK-9521 10/100/1000Base-T Adapter
2189 - SK-9521 V2.0 10/100/1000Base-T Adapter
2190 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2191 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2192 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2193 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2194 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2195 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2196 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2197 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2198 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2199 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2200 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2201 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2202 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2203 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2204 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2205 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2206 - SMC EZ Card 1000 (SMC9452TXV.2)
2208 The adapters support Jumbo Frames.
2209 The dual link adapters support link-failover and dual port features.
2210 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2211 the scatter-gather functionality with sendfile(). Please refer to
2212 <file:Documentation/networking/sk98lin.txt> for more information about
2213 optional driver parameters.
2214 Questions concerning this driver may be addressed to:
2215 <linux@syskonnect.de>
2217 If you want to compile this driver as a module ( = code which can be
2218 inserted in and removed from the running kernel whenever you want),
2219 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2220 be called sk98lin. This is recommended.
2223 tristate "VIA Velocity support"
2224 depends on NET_PCI && PCI
2229 If you have a VIA "Velocity" based network card say Y here.
2231 To compile this driver as a module, choose M here. The module
2232 will be called via-velocity.
2235 tristate "Broadcom Tigon3 support"
2238 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2240 To compile this driver as a module, choose M here: the module
2241 will be called tg3. This is recommended.
2244 tristate "Broadcom NetXtremeII support"
2249 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2251 To compile this driver as a module, choose M here: the module
2252 will be called bnx2. This is recommended.
2255 tristate "Spider Gigabit Ethernet driver"
2256 depends on PCI && PPC_IBM_CELL_BLADE
2259 This driver supports the Gigabit Ethernet chips present on the
2260 Cell Processor-Based Blades from IBM.
2263 tristate "Tundra TSI108 gigabit Ethernet support"
2264 depends on TSI108_BRIDGE
2266 This driver supports Tundra TSI108 gigabit Ethernet ports.
2267 To compile this driver as a module, choose M here: the module
2268 will be called tsi108_eth.
2271 tristate "Gianfar Ethernet"
2272 depends on 85xx || 83xx || PPC_86xx
2275 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2276 and MPC86xx family of chips, and the FEC on the 8540.
2283 tristate "Freescale QE UCC GETH"
2284 depends on QUICC_ENGINE && UCC_FAST
2286 This driver supports the Gigabit Ethernet mode of QE UCC.
2287 QE can be found on MPC836x CPUs.
2293 config UGETH_MAGIC_PACKET
2294 bool "Magic Packet detection support"
2297 config UGETH_FILTERING
2298 bool "Mac address filtering support"
2301 config UGETH_TX_ON_DEMOND
2302 bool "Transmit on Demond support"
2305 config UGETH_HAS_GIGA
2307 depends on UCC_GETH && PPC_MPC836x
2310 tristate "MV-643XX Ethernet support"
2311 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || (PPC_MULTIPLATFORM && PPC32)
2314 This driver supports the gigabit Ethernet on the Marvell MV643XX
2315 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2316 Pegasos II, amongst other PPC and MIPS boards.
2318 config MV643XX_ETH_0
2319 bool "MV-643XX Port 0"
2320 depends on MV643XX_ETH
2322 This enables support for Port 0 of the Marvell MV643XX Gigabit
2325 config MV643XX_ETH_1
2326 bool "MV-643XX Port 1"
2327 depends on MV643XX_ETH
2329 This enables support for Port 1 of the Marvell MV643XX Gigabit
2332 config MV643XX_ETH_2
2333 bool "MV-643XX Port 2"
2334 depends on MV643XX_ETH
2336 This enables support for Port 2 of the Marvell MV643XX Gigabit
2340 tristate "QLogic QLA3XXX Network Driver Support"
2343 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2345 To compile this driver as a module, choose M here: the module
2346 will be called qla3xxx.
2351 # 10 Gigabit Ethernet
2354 menu "Ethernet (10000 Mbit)"
2358 tristate "Chelsio 10Gb Ethernet support"
2362 This driver supports Chelsio gigabit and 10-gigabit
2363 Ethernet cards. More information about adapter features and
2364 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2366 For general information about Chelsio and our products, visit
2367 our website at <http://www.chelsio.com>.
2369 For customer support, please visit our customer support page at
2370 <http://www.chelsio.com/support.htm>.
2372 Please send feedback to <linux-bugs@chelsio.com>.
2374 To compile this driver as a module, choose M here: the module
2375 will be called cxgb.
2377 config CHELSIO_T1_1G
2378 bool "Chelsio gigabit Ethernet support"
2379 depends on CHELSIO_T1
2381 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2382 are using only 10G cards say 'N' here.
2384 config CHELSIO_T1_NAPI
2385 bool "Use Rx Polling (NAPI)"
2386 depends on CHELSIO_T1
2389 NAPI is a driver API designed to reduce CPU and interrupt load
2390 when the driver is receiving lots of packets from the card.
2393 tristate "eHEA Ethernet support"
2396 This driver supports the IBM pSeries eHEA ethernet adapter.
2398 To compile the driver as a module, choose M here. The module
2399 will be called ehea.
2402 tristate "Intel(R) PRO/10GbE support"
2405 This driver supports Intel(R) PRO/10GbE family of
2406 adapters. For more information on how to identify your adapter, go
2407 to the Adapter & Driver ID Guide at:
2409 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2411 For general information and support, go to the Intel support
2414 <http://support.intel.com>
2416 More specific information on configuring the driver is in
2417 <file:Documentation/networking/ixgb.txt>.
2419 To compile this driver as a module, choose M here and read
2420 <file:Documentation/networking/net-modules.txt>. The module
2421 will be called ixgb.
2424 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2425 depends on IXGB && EXPERIMENTAL
2427 NAPI is a new driver API designed to reduce CPU and interrupt load
2428 when the driver is receiving lots of packets from the card. It is
2429 still somewhat experimental and thus not yet enabled by default.
2431 If your estimated Rx load is 10kpps or more, or if the card will be
2432 deployed on potentially unfriendly networks (e.g. in a firewall),
2435 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2441 tristate "S2IO 10Gbe XFrame NIC"
2444 This driver supports the 10Gbe XFrame NIC of S2IO.
2445 More specific information on configuring the driver is in
2446 <file:Documentation/networking/s2io.txt>.
2449 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2450 depends on S2IO && EXPERIMENTAL
2452 NAPI is a new driver API designed to reduce CPU and interrupt load
2453 when the driver is receiving lots of packets from the card. It is
2454 still somewhat experimental and thus not yet enabled by default.
2456 If your estimated Rx load is 10kpps or more, or if the card will be
2457 deployed on potentially unfriendly networks (e.g. in a firewall),
2460 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2466 tristate "Myricom Myri-10G Ethernet support"
2471 This driver supports Myricom Myri-10G Dual Protocol interface in
2472 Ethernet mode. If the eeprom on your board is not recent enough,
2473 you will need a newer firmware image.
2474 You may get this image or more information, at:
2476 <http://www.myri.com/scs/download-Myri10GE.html>
2478 To compile this driver as a module, choose M here and read
2479 <file:Documentation/networking/net-modules.txt>. The module
2480 will be called myri10ge.
2483 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2486 This enables the support for NetXen's Gigabit Ethernet card.
2490 source "drivers/net/tokenring/Kconfig"
2492 source "drivers/net/wireless/Kconfig"
2494 source "drivers/net/pcmcia/Kconfig"
2496 source "drivers/net/wan/Kconfig"
2498 source "drivers/atm/Kconfig"
2500 source "drivers/s390/net/Kconfig"
2503 tristate "iSeries Virtual Ethernet driver support"
2504 depends on PPC_ISERIES
2507 tristate "RapidIO Ethernet over messaging driver support"
2510 config RIONET_TX_SIZE
2511 int "Number of outbound queue entries"
2515 config RIONET_RX_SIZE
2516 int "Number of inbound queue entries"
2521 bool "FDDI driver support"
2522 depends on (PCI || EISA)
2524 Fiber Distributed Data Interface is a high speed local area network
2525 design; essentially a replacement for high speed Ethernet. FDDI can
2526 run over copper or fiber. If you are connected to such a network and
2527 want a driver for the FDDI card in your computer, say Y here (and
2528 then also Y to the driver for your FDDI card, below). Most people
2532 tristate "Digital DEFEA and DEFPA adapter support"
2533 depends on FDDI && (PCI || EISA)
2535 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2536 (DEFPA) controllers which can connect you to a local FDDI network.
2539 tristate "SysKonnect FDDI PCI support"
2540 depends on FDDI && PCI
2542 Say Y here if you have a SysKonnect FDDI PCI adapter.
2543 The following adapters are supported by this driver:
2544 - SK-5521 (SK-NET FDDI-UP)
2545 - SK-5522 (SK-NET FDDI-UP DAS)
2546 - SK-5541 (SK-NET FDDI-FP)
2547 - SK-5543 (SK-NET FDDI-LP)
2548 - SK-5544 (SK-NET FDDI-LP DAS)
2549 - SK-5821 (SK-NET FDDI-UP64)
2550 - SK-5822 (SK-NET FDDI-UP64 DAS)
2551 - SK-5841 (SK-NET FDDI-FP64)
2552 - SK-5843 (SK-NET FDDI-LP64)
2553 - SK-5844 (SK-NET FDDI-LP64 DAS)
2554 - Netelligent 100 FDDI DAS Fibre SC
2555 - Netelligent 100 FDDI SAS Fibre SC
2556 - Netelligent 100 FDDI DAS UTP
2557 - Netelligent 100 FDDI SAS UTP
2558 - Netelligent 100 FDDI SAS Fibre MIC
2560 Read <file:Documentation/networking/skfp.txt> for information about
2563 Questions concerning this driver can be addressed to:
2564 <linux@syskonnect.de>
2566 To compile this driver as a module, choose M here: the module
2567 will be called skfp. This is recommended.
2570 bool "HIPPI driver support (EXPERIMENTAL)"
2571 depends on EXPERIMENTAL && INET && PCI
2573 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2574 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2575 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2576 single-mode). HIPPI networks are commonly used for clusters and to
2577 connect to super computers. If you are connected to a HIPPI network
2578 and have a HIPPI network card in your computer that you want to use
2579 under Linux, say Y here (you must also remember to enable the driver
2580 for your HIPPI card below). Most people will say N here.
2583 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2584 depends on HIPPI && PCI
2586 Say Y here if this is your PCI HIPPI network card.
2588 To compile this driver as a module, choose M here: the module
2589 will be called rrunner. If unsure, say N.
2591 config ROADRUNNER_LARGE_RINGS
2592 bool "Use large TX/RX rings (EXPERIMENTAL)"
2593 depends on ROADRUNNER
2595 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2596 of additional memory to allow for fastest operation, both for
2597 transmitting and receiving. This memory cannot be used by any other
2598 kernel code or by user space programs. Say Y here only if you have
2602 tristate "PLIP (parallel port) support"
2605 PLIP (Parallel Line Internet Protocol) is used to create a
2606 reasonably fast mini network consisting of two (or, rarely, more)
2607 local machines. A PLIP link from a Linux box is a popular means to
2608 install a Linux distribution on a machine which doesn't have a
2609 CD-ROM drive (a minimal system has to be transferred with floppies
2610 first). The kernels on both machines need to have this PLIP option
2611 enabled for this to work.
2613 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2614 ports (the connectors at the computers with 25 holes) are connected
2615 with "null printer" or "Turbo Laplink" cables which can transmit 4
2616 bits at a time (mode 0) or with special PLIP cables, to be used on
2617 bidirectional parallel ports only, which can transmit 8 bits at a
2618 time (mode 1); you can find the wiring of these cables in
2619 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2620 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2621 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2622 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2623 and winsock or NCSA's telnet.
2625 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2626 as the NET-3-HOWTO, both available from
2627 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2628 protocol has been changed and this PLIP driver won't work together
2629 with the PLIP support in Linux versions 1.0.x. This option enlarges
2630 your kernel by about 8 KB.
2632 To compile this driver as a module, choose M here and read
2633 <file:Documentation/networking/net-modules.txt>. The module will be
2634 called plip. If unsure, say Y or M, in case you buy a laptop
2638 tristate "PPP (point-to-point protocol) support"
2641 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2642 the same purpose: sending Internet traffic over telephone (and other
2643 serial) lines. Ask your access provider if they support it, because
2644 otherwise you can't use it; most Internet access providers these
2645 days support PPP rather than SLIP.
2647 To use PPP, you need an additional program called pppd as described
2648 in the PPP-HOWTO, available at
2649 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2650 the version of pppd recommended in <file:Documentation/Changes>.
2651 The PPP option enlarges your kernel by about 16 KB.
2653 There are actually two versions of PPP: the traditional PPP for
2654 asynchronous lines, such as regular analog phone lines, and
2655 synchronous PPP which can be used over digital ISDN lines for
2656 example. If you want to use PPP over phone lines or other
2657 asynchronous serial lines, you need to say Y (or M) here and also to
2658 the next option, "PPP support for async serial ports". For PPP over
2659 synchronous lines, you should say Y (or M) here and to "Support
2660 synchronous PPP", below.
2662 If you said Y to "Version information on all symbols" above, then
2663 you cannot compile the PPP driver into the kernel; you can then only
2664 compile it as a module. To compile this driver as a module, choose M
2665 here and read <file:Documentation/networking/net-modules.txt>.
2666 The module will be called ppp_generic.
2668 config PPP_MULTILINK
2669 bool "PPP multilink support (EXPERIMENTAL)"
2670 depends on PPP && EXPERIMENTAL
2672 PPP multilink is a protocol (defined in RFC 1990) which allows you
2673 to combine several (logical or physical) lines into one logical PPP
2674 connection, so that you can utilize your full bandwidth.
2676 This has to be supported at the other end as well and you need a
2677 version of the pppd daemon which understands the multilink protocol.
2682 bool "PPP filtering"
2685 Say Y here if you want to be able to filter the packets passing over
2686 PPP interfaces. This allows you to control which packets count as
2687 activity (i.e. which packets will reset the idle timer or bring up
2688 a demand-dialed link) and which packets are to be dropped entirely.
2689 You need to say Y here if you wish to use the pass-filter and
2690 active-filter options to pppd.
2695 tristate "PPP support for async serial ports"
2699 Say Y (or M) here if you want to be able to use PPP over standard
2700 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2701 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2704 To compile this driver as a module, choose M here.
2709 tristate "PPP support for sync tty ports"
2712 Say Y (or M) here if you want to be able to use PPP over synchronous
2713 (HDLC) tty devices, such as the SyncLink adapter. These devices
2714 are often used for high-speed leased lines like T1/E1.
2716 To compile this driver as a module, choose M here.
2719 tristate "PPP Deflate compression"
2724 Support for the Deflate compression method for PPP, which uses the
2725 Deflate algorithm (the same algorithm that gzip uses) to compress
2726 each PPP packet before it is sent over the wire. The machine at the
2727 other end of the PPP link (usually your ISP) has to support the
2728 Deflate compression method as well for this to be useful. Even if
2729 they don't support it, it is safe to say Y here.
2731 To compile this driver as a module, choose M here.
2734 tristate "PPP BSD-Compress compression"
2737 Support for the BSD-Compress compression method for PPP, which uses
2738 the LZW compression method to compress each PPP packet before it is
2739 sent over the wire. The machine at the other end of the PPP link
2740 (usually your ISP) has to support the BSD-Compress compression
2741 method as well for this to be useful. Even if they don't support it,
2742 it is safe to say Y here.
2744 The PPP Deflate compression method ("PPP Deflate compression",
2745 above) is preferable to BSD-Compress, because it compresses better
2748 Note that the BSD compression code will always be compiled as a
2749 module; it is called bsd_comp and will show up in the directory
2750 modules once you have said "make modules". If unsure, say N.
2753 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2754 depends on PPP && EXPERIMENTAL
2760 Support for the MPPE Encryption protocol, as employed by the
2761 Microsoft Point-to-Point Tunneling Protocol.
2763 See http://pptpclient.sourceforge.net/ for information on
2764 configuring PPTP clients and servers to utilize this method.
2767 tristate "PPP over Ethernet (EXPERIMENTAL)"
2768 depends on EXPERIMENTAL && PPP
2770 Support for PPP over Ethernet.
2772 This driver requires the latest version of pppd from the CVS
2773 repository at cvs.samba.org. Alternatively, see the
2774 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2775 which contains instruction on how to use this driver (under
2776 the heading "Kernel mode PPPoE").
2779 tristate "PPP over ATM"
2780 depends on ATM && PPP
2782 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2783 This implementation does not yet comply with section 8 of RFC2364,
2784 which can lead to bad results if the ATM peer loses state and
2785 changes its encapsulation unilaterally.
2788 tristate "SLIP (serial line) support"
2790 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2791 connect to your Internet service provider or to connect to some
2792 other local Unix box or if you want to configure your Linux box as a
2793 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2794 Internet Protocol) is a protocol used to send Internet traffic over
2795 serial connections such as telephone lines or null modem cables;
2796 nowadays, the protocol PPP is more commonly used for this same
2799 Normally, your access provider has to support SLIP in order for you
2800 to be able to use it, but there is now a SLIP emulator called SLiRP
2801 around (available from
2802 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2803 allows you to use SLIP over a regular dial up shell connection. If
2804 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2805 NET-3-HOWTO, available from
2806 <http://www.tldp.org/docs.html#howto>, explains how to
2807 configure SLIP. Note that you don't need this option if you just
2808 want to run term (term is a program which gives you almost full
2809 Internet connectivity if you have a regular dial up shell account on
2810 some Internet connected Unix computer. Read
2811 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2812 support will enlarge your kernel by about 4 KB. If unsure, say N.
2814 To compile this driver as a module, choose M here and read
2815 <file:Documentation/networking/net-modules.txt>. The module will be
2818 config SLIP_COMPRESSED
2819 bool "CSLIP compressed headers"
2823 This protocol is faster than SLIP because it uses compression on the
2824 TCP/IP headers (not on the data itself), but it has to be supported
2825 on both ends. Ask your access provider if you are not sure and
2826 answer Y, just in case. You will still be able to use plain SLIP. If
2827 you plan to use SLiRP, the SLIP emulator (available from
2828 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2829 allows you to use SLIP over a regular dial up shell connection, you
2830 definitely want to say Y here. The NET-3-HOWTO, available from
2831 <http://www.tldp.org/docs.html#howto>, explains how to configure
2832 CSLIP. This won't enlarge your kernel.
2837 This option enables Van Jacobsen serial line header compression
2841 bool "Keepalive and linefill"
2844 Adds additional capabilities to the SLIP driver to support the
2845 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2848 config SLIP_MODE_SLIP6
2849 bool "Six bit SLIP encapsulation"
2852 Just occasionally you may need to run IP over hostile serial
2853 networks that don't pass all control characters or are only seven
2854 bit. Saying Y here adds an extra mode you can use with SLIP:
2855 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2856 the serial device. Naturally, this has to be supported at the other
2857 end of the link as well. It's good enough, for example, to run IP
2858 over the async ports of a Camtec JNT Pad. If unsure, say N.
2861 bool "Fibre Channel driver support"
2862 depends on SCSI && PCI
2864 Fibre Channel is a high speed serial protocol mainly used to connect
2865 large storage devices to the computer; it is compatible with and
2866 intended to replace SCSI.
2868 If you intend to use Fibre Channel, you need to have a Fibre channel
2869 adaptor card in your computer; say Y here and to the driver for your
2870 adaptor below. You also should have said Y to "SCSI support" and
2871 "SCSI generic support".
2874 tristate "Traffic Shaper (OBSOLETE)"
2875 depends on EXPERIMENTAL
2877 The traffic shaper is a virtual network device that allows you to
2878 limit the rate of outgoing data flow over some other network device.
2879 The traffic that you want to slow down can then be routed through
2880 these virtual devices. See
2881 <file:Documentation/networking/shaper.txt> for more information.
2883 An alternative to this traffic shaper are traffic schedulers which
2884 you'll get if you say Y to "QoS and/or fair queuing" in
2885 "Networking options".
2887 To compile this driver as a module, choose M here: the module
2888 will be called shaper. If unsure, say N.
2891 tristate "Network console logging support (EXPERIMENTAL)"
2892 depends on EXPERIMENTAL
2894 If you want to log kernel messages over the network, enable this.
2895 See <file:Documentation/networking/netconsole.txt> for details.
2903 bool "Netpoll support for trapping incoming packets"
2908 bool "Netpoll traffic trapping"
2912 config NET_POLL_CONTROLLER