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 intermidiate 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.
191 source "drivers/net/arm/Kconfig"
194 tristate "MACE (Power Mac ethernet) support"
195 depends on NET_ETHERNET && PPC_PMAC && PPC32
198 Power Macintoshes and clones with Ethernet built-in on the
199 motherboard will usually use a MACE (Medium Access Control for
200 Ethernet) interface. Say Y to include support for the MACE chip.
202 To compile this driver as a module, choose M here: the module
205 config MACE_AAUI_PORT
206 bool "Use AAUI port instead of TP by default"
209 Some Apple machines (notably the Apple Network Server) which use the
210 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
211 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
212 Y here if you have such a machine. If unsure, say N.
213 The driver will default to AAUI on ANS anyway, and if you use it as
214 a module, you can provide the port_aaui=0|1 to force the driver.
217 tristate "BMAC (G3 ethernet) support"
218 depends on NET_ETHERNET && PPC_PMAC && PPC32
221 Say Y for support of BMAC Ethernet interfaces. These are used on G3
224 To compile this driver as a module, choose M here: the module
228 tristate "National DP83902AV (Oak ethernet) support"
229 depends on NET_ETHERNET && PPC && BROKEN
232 Say Y if your machine has this type of Ethernet network card.
234 To compile this driver as a module, choose M here: the module
235 will be called oaknet.
238 tristate "Ariadne support"
239 depends on NET_ETHERNET && ZORRO
241 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
244 To compile this driver as a module, choose M here: the module
245 will be called ariadne.
248 tristate "A2065 support"
249 depends on NET_ETHERNET && ZORRO
252 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
255 To compile this driver as a module, choose M here: the module
256 will be called a2065.
259 tristate "Hydra support"
260 depends on NET_ETHERNET && ZORRO
263 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
265 To compile this driver as a module, choose M here: the module
266 will be called hydra.
269 tristate "Zorro NS8390-based Ethernet support"
270 depends on NET_ETHERNET && ZORRO
273 This driver is for Zorro Ethernet cards using an NS8390-compatible
274 chipset, like the Village Tronic Ariadne II and the Individual
275 Computers X-Surf Ethernet cards. If you have such a card, say Y.
278 To compile this driver as a module, choose M here: the module
279 will be called zorro8390.
282 tristate "PCMCIA NE2000 support"
283 depends on NET_ETHERNET && AMIGA_PCMCIA
286 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
289 To compile this driver as a module, choose M here: the module
293 tristate "Apollo 3c505 support"
294 depends on NET_ETHERNET && APOLLO
296 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
297 If you don't have one made for Apollos, you can use one from a PC,
298 except that your Apollo won't be able to boot from it (because the
299 code in the ROM will be for a PC).
302 bool "Macintosh NS 8390 based ethernet cards"
303 depends on NET_ETHERNET && MAC
306 If you want to include a driver to support Nubus or LC-PDS
307 Ethernet cards using an NS8390 chipset or its equivalent, say Y
308 and read the Ethernet-HOWTO, available from
309 <http://www.tldp.org/docs.html#howto>.
312 tristate "Macintosh CS89x0 based ethernet cards"
313 depends on NET_ETHERNET && MAC && BROKEN
315 Support for CS89x0 chipset based Ethernet cards. If you have a
316 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
317 read the Ethernet-HOWTO, available from
318 <http://www.tldp.org/docs.html#howto>.
320 To compile this driver as a module, choose M here and read
321 <file:Documentation/networking/net-modules.txt>. This module will
325 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
326 depends on NET_ETHERNET && MAC
328 Support for NatSemi SONIC based Ethernet devices. This includes
329 the onboard Ethernet in many Quadras as well as some LC-PDS,
330 a few Nubus and all known Comm Slot Ethernet cards. If you have
331 one of these say Y and read the Ethernet-HOWTO, available from
332 <http://www.tldp.org/docs.html#howto>.
334 To compile this driver as a module, choose M here and read
335 <file:Documentation/networking/net-modules.txt>. This module will
339 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
340 depends on NET_ETHERNET && MAC && EXPERIMENTAL
343 Support for the onboard AMD 79C940 MACE Ethernet controller used in
344 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
345 say Y and read the Ethernet-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>.
349 tristate "MVME147 (Lance) Ethernet support"
350 depends on NET_ETHERNET && MVME147
353 Support for the on-board Ethernet interface on the Motorola MVME147
354 single-board computer. Say Y here to include the
355 driver for this chip in your kernel.
356 To compile this driver as a module, choose M here.
359 tristate "MVME16x Ethernet support"
360 depends on NET_ETHERNET && MVME16x
362 This is the driver for the Ethernet interface on the Motorola
363 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
364 driver for this chip in your kernel.
365 To compile this driver as a module, choose M here.
368 tristate "BVME6000 Ethernet support"
369 depends on NET_ETHERNET && BVME6000
371 This is the driver for the Ethernet interface on BVME4000 and
372 BVME6000 VME boards. Say Y here to include the driver for this chip
374 To compile this driver as a module, choose M here.
377 tristate "Atari Lance support"
378 depends on NET_ETHERNET && ATARI
380 Say Y to include support for several Atari Ethernet adapters based
381 on the AMD Lance chipset: RieblCard (with or without battery), or
382 PAMCard VME (also the version by Rhotron, with different addresses).
385 tristate "BioNet-100 support"
386 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
388 Say Y to include support for BioData's BioNet-100 Ethernet adapter
389 for the ACSI port. The driver works (has to work...) with a polled
390 I/O scheme, so it's rather slow :-(
393 tristate "PAMsNet support"
394 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
396 Say Y to include support for the PAMsNet Ethernet adapter for the
397 ACSI port ("ACSI node"). The driver works (has to work...) with a
398 polled I/O scheme, so it's rather slow :-(
401 tristate "Sun3/Sun3x on-board LANCE support"
402 depends on NET_ETHERNET && (SUN3 || SUN3X)
404 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
405 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
406 here to compile in the Linux driver for this and enable Ethernet.
407 General Linux information on the Sun 3 and 3x series (now
409 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
411 If you're not building a kernel for a Sun 3, say N.
414 bool "Sun3 on-board Intel 82586 support"
415 depends on NET_ETHERNET && SUN3
417 This driver enables support for the on-board Intel 82586 based
418 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
419 that this driver does not support 82586-based adapters on additional
423 bool "HP on-board LANCE support"
424 depends on NET_ETHERNET && DIO
427 If you want to use the builtin "LANCE" Ethernet controller on an
428 HP300 machine, say Y here.
431 tristate "Lasi ethernet"
432 depends on NET_ETHERNET && PARISC && GSC_LASI
434 Say Y here to support the on-board Intel 82596 ethernet controller
435 built into Hewlett-Packard PA-RISC machines.
437 config MIPS_JAZZ_SONIC
438 tristate "MIPS JAZZ onboard SONIC Ethernet support"
439 depends on NET_ETHERNET && MACH_JAZZ
441 This is the driver for the onboard card of MIPS Magnum 4000,
442 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
444 config MIPS_AU1X00_ENET
445 bool "MIPS AU1000 Ethernet support"
446 depends on NET_ETHERNET && SOC_AU1X00
450 If you have an Alchemy Semi AU1X00 based system
451 say Y. Otherwise, say N.
453 config NET_SB1250_MAC
454 tristate "SB1250 Ethernet support"
455 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
458 bool "SGI IOC3 Ethernet"
459 depends on NET_ETHERNET && PCI && SGI_IP27
463 If you have a network (Ethernet) card of this type, say Y and read
464 the Ethernet-HOWTO, available from
465 <http://www.tldp.org/docs.html#howto>.
467 config SGI_IOC3_ETH_HW_RX_CSUM
468 bool "Receive hardware checksums"
469 depends on SGI_IOC3_ETH && INET
472 The SGI IOC3 network adapter supports TCP and UDP checksums in
473 hardware to offload processing of these checksums from the CPU. At
474 the moment only acceleration of IPv4 is supported. This option
475 enables offloading for checksums on receive. If unsure, say Y.
477 config SGI_IOC3_ETH_HW_TX_CSUM
478 bool "Transmit hardware checksums"
479 depends on SGI_IOC3_ETH && INET
482 The SGI IOC3 network adapter supports TCP and UDP checksums in
483 hardware to offload processing of these checksums from the CPU. At
484 the moment only acceleration of IPv4 is supported. This option
485 enables offloading for checksums on transmit. If unsure, say Y.
488 tristate "MIPS simulator Network device (EXPERIMENTAL)"
489 depends on MIPS_SIM && EXPERIMENTAL
491 The MIPSNET device is a simple Ethernet network device which is
492 emulated by the MIPS Simulator.
493 If you are not using a MIPSsim or are unsure, say N.
495 config SGI_O2MACE_ETH
496 tristate "SGI O2 MACE Fast Ethernet support"
497 depends on NET_ETHERNET && SGI_IP32=y
500 tristate "National DP83902AV support"
501 depends on NET_ETHERNET && SUPERH
504 Support for cards based on the National Semiconductor DP83902AV
505 ST-NIC Serial Network Interface Controller for Twisted Pair. This
506 is a 10Mbit/sec Ethernet controller. Product overview and specs at
507 <http://www.national.com/pf/DP/DP83902A.html>.
512 tristate "Sun LANCE support"
513 depends on NET_ETHERNET && SBUS
516 This driver supports the "le" interface present on all 32-bit Sparc
517 systems, on some older Ultra systems and as an Sbus option. These
518 cards are based on the AMD Lance chipset, which is better known
519 via the NE2100 cards.
521 To compile this driver as a module, choose M here: the module
522 will be called sunlance.
525 tristate "Sun Happy Meal 10/100baseT support"
526 depends on NET_ETHERNET && (SBUS || PCI)
529 This driver supports the "hme" interface present on most Ultra
530 systems and as an option on older Sbus systems. This driver supports
531 both PCI and Sbus devices. This driver also supports the "qfe" quad
532 100baseT device available in both PCI and Sbus configurations.
534 To compile this driver as a module, choose M here: the module
535 will be called sunhme.
538 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
539 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
542 This driver supports the "be" interface available as an Sbus option.
543 This is Sun's older 100baseT Ethernet device.
545 To compile this driver as a module, choose M here: the module
546 will be called sunbmac.
549 tristate "Sun QuadEthernet support"
550 depends on NET_ETHERNET && SBUS
553 This driver supports the "qe" 10baseT Ethernet device, available as
554 an Sbus option. Note that this is not the same as Quad FastEthernet
555 "qfe" which is supported by the Happy Meal driver instead.
557 To compile this driver as a module, choose M here: the module
558 will be called sunqe.
561 tristate "Sun GEM support"
562 depends on NET_ETHERNET && PCI
565 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
566 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
569 tristate "Sun Cassini support"
570 depends on NET_ETHERNET && PCI
573 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
574 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
576 config NET_VENDOR_3COM
578 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
580 If you have a network (Ethernet) card belonging to this class, say Y
581 and read the Ethernet-HOWTO, available from
582 <http://www.tldp.org/docs.html#howto>.
584 Note that the answer to this question doesn't directly affect the
585 kernel: saying N will just cause the configurator to skip all
586 the questions about 3COM cards. If you say Y, you will be asked for
587 your specific card in the following questions.
590 tristate "3c501 \"EtherLink\" support"
591 depends on NET_VENDOR_3COM && ISA
593 If you have a network (Ethernet) card of this type, say Y and read
594 the Ethernet-HOWTO, available from
595 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
596 new card, since the 3c501 is slow, broken, and obsolete: you will
597 have problems. Some people suggest to ping ("man ping") a nearby
598 machine every minute ("man cron") when using this card.
600 To compile this driver as a module, choose M here and read
601 <file:Documentation/networking/net-modules.txt>. The module
602 will be called 3c501.
605 tristate "3c503 \"EtherLink II\" support"
606 depends on NET_VENDOR_3COM && ISA
609 If you have a network (Ethernet) card of this type, say Y and read
610 the Ethernet-HOWTO, available from
611 <http://www.tldp.org/docs.html#howto>.
613 To compile this driver as a module, choose M here and read
614 <file:Documentation/networking/net-modules.txt>. The module
615 will be called 3c503.
618 tristate "3c505 \"EtherLink Plus\" support"
619 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
621 Information about this network (Ethernet) card can be found in
622 <file:Documentation/networking/3c505.txt>. If you have a card of
623 this type, say Y and read the Ethernet-HOWTO, available from
624 <http://www.tldp.org/docs.html#howto>.
626 To compile this driver as a module, choose M here and read
627 <file:Documentation/networking/net-modules.txt>. The module
628 will be called 3c505.
631 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
632 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
634 If you have a network (Ethernet) card of this type, say Y and read
635 the Ethernet-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>.
638 To compile this driver as a module, choose M here and read
639 <file:Documentation/networking/net-modules.txt>. The module
640 will be called 3c507.
643 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
644 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
646 If you have a network (Ethernet) card belonging to the 3Com
647 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
648 from <http://www.tldp.org/docs.html#howto>.
650 If your card is not working you may need to use the DOS
651 setup disk to disable Plug & Play mode, and to select the default
654 To compile this driver as a module, choose M here and read
655 <file:Documentation/networking/net-modules.txt>. The module
656 will be called 3c509.
659 tristate "3c515 ISA \"Fast EtherLink\""
660 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
662 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
663 network card, say Y and read the Ethernet-HOWTO, available from
664 <http://www.tldp.org/docs.html#howto>.
666 To compile this driver as a module, choose M here and read
667 <file:Documentation/networking/net-modules.txt>. The module
668 will be called 3c515.
671 tristate "3c523 \"EtherLink/MC\" support"
672 depends on NET_VENDOR_3COM && MCA_LEGACY
674 If you have a network (Ethernet) card of this type, say Y and read
675 the Ethernet-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>.
678 To compile this driver as a module, choose M here and read
679 <file:Documentation/networking/net-modules.txt>. The module
680 will be called 3c523.
683 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
684 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
686 If you have a network (Ethernet) card of this type, say Y and read
687 the Ethernet-HOWTO, available from
688 <http://www.tldp.org/docs.html#howto>.
690 To compile this driver as a module, choose M here and read
691 <file:Documentation/networking/net-modules.txt>. The module
692 will be called 3c527.
695 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
696 depends on NET_VENDOR_3COM && (PCI || EISA)
699 This option enables driver support for a large number of 10Mbps and
700 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
702 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
703 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
704 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
705 "Tornado" (3c905) PCI
706 "Hurricane" (3c555/3cSOHO) PCI
708 If you have such a card, say Y and read the Ethernet-HOWTO,
709 available from <http://www.tldp.org/docs.html#howto>. More
710 specific information is in
711 <file:Documentation/networking/vortex.txt> and in the comments at
712 the beginning of <file:drivers/net/3c59x.c>.
714 To compile this support as a module, choose M here and read
715 <file:Documentation/networking/net-modules.txt>.
718 tristate "3cr990 series \"Typhoon\" support"
719 depends on NET_VENDOR_3COM && PCI
722 This option enables driver support for the 3cr990 series of cards:
724 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
725 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
726 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
728 If you have a network (Ethernet) card of this type, say Y and read
729 the Ethernet-HOWTO, available from
730 <http://www.tldp.org/docs.html#howto>.
732 To compile this driver as a module, choose M here and read
733 <file:Documentation/networking/net-modules.txt>. The module
734 will be called typhoon.
737 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
738 depends on NET_ETHERNET && ISA && ISA_DMA_API
740 If you have a network (Ethernet) card of this type, say Y and read
741 the Ethernet-HOWTO, available from
742 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
745 To compile this driver as a module, choose M here: the module
746 will be called lance. This is recommended.
748 config NET_VENDOR_SMC
749 bool "Western Digital/SMC cards"
750 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC || EMBEDDED)
752 If you have a network (Ethernet) card belonging to this class, say Y
753 and read the Ethernet-HOWTO, available from
754 <http://www.tldp.org/docs.html#howto>.
756 Note that the answer to this question doesn't directly affect the
757 kernel: saying N will just cause the configurator to skip all
758 the questions about Western Digital cards. If you say Y, you will be
759 asked for your specific card in the following questions.
762 tristate "WD80*3 support"
763 depends on NET_VENDOR_SMC && ISA
766 If you have a network (Ethernet) card of this type, say Y and read
767 the Ethernet-HOWTO, available from
768 <http://www.tldp.org/docs.html#howto>.
770 To compile this driver as a module, choose M here and read
771 <file:Documentation/networking/net-modules.txt>. The module
775 tristate "SMC Ultra MCA support"
776 depends on NET_VENDOR_SMC && MCA
779 If you have a network (Ethernet) card of this type and are running
780 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
781 available from <http://www.tldp.org/docs.html#howto>.
783 To compile this driver as a module, choose M here and read
784 <file:Documentation/networking/net-modules.txt>. The module
785 will be called smc-mca.
788 tristate "SMC Ultra support"
789 depends on NET_VENDOR_SMC && ISA
792 If you have a network (Ethernet) card of this type, say Y and read
793 the Ethernet-HOWTO, available from
794 <http://www.tldp.org/docs.html#howto>.
796 Important: There have been many reports that, with some motherboards
797 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
798 such as some BusLogic models) causes corruption problems with many
799 operating systems. The Linux smc-ultra driver has a work-around for
800 this but keep it in mind if you have such a SCSI card and have
803 To compile this driver as a module, choose M here and read
804 <file:Documentation/networking/net-modules.txt>. The module
805 will be called smc-ultra.
808 tristate "SMC Ultra32 EISA support"
809 depends on NET_VENDOR_SMC && EISA
812 If you have a network (Ethernet) card of this type, say Y and read
813 the Ethernet-HOWTO, available from
814 <http://www.tldp.org/docs.html#howto>.
816 To compile this driver as a module, choose M here and read
817 <file:Documentation/networking/net-modules.txt>. The module
818 will be called smc-ultra32.
821 tristate "SMC 91C9x/91C1xxx support"
824 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00)
826 This is a driver for SMC's 91x series of Ethernet chipsets,
827 including the SMC91C94 and the SMC91C111. Say Y if you want it
828 compiled into the kernel, and read the file
829 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
830 available from <http://www.linuxdoc.org/docs.html#howto>.
832 This driver is also available as a module ( = code which can be
833 inserted in and removed from the running kernel whenever you want).
834 The module will be called smc91x. If you want to compile it as a
835 module, say M here and read <file:Documentation/modules.txt> as well
836 as <file:Documentation/networking/net-modules.txt>.
839 tristate "SMC 9194 support"
840 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN || EMBEDDED)
843 This is support for the SMC9xxx based Ethernet cards. Choose this
844 option if you have a DELL laptop with the docking station, or
845 another SMC9192/9194 based chipset. Say Y if you want it compiled
846 into the kernel, and read the file
847 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
848 available from <http://www.tldp.org/docs.html#howto>.
850 To compile this driver as a module, choose M here and read
851 <file:Documentation/networking/net-modules.txt>. The module
852 will be called smc9194.
855 bool "Opencores (Igor) Emac support"
857 This is support for the opencores Igor emac driver implemented
861 bool "MoreThanIP 10_100_1000 Emac support"
863 This is support for the MoreThanIP 10_100_1000 emac driver implemented
867 tristate "NetX Ethernet support"
869 depends on NET_ETHERNET && ARCH_NETX
871 This is support for the Hilscher netX builtin Ethernet ports
873 To compile this driver as a module, choose M here and read
874 <file:Documentation/networking/net-modules.txt>. The module
875 will be called netx-eth.
878 tristate "DM9000 support"
879 depends on (ARM || MIPS) && NET_ETHERNET
883 Support for DM9000 chipset.
885 To compile this driver as a module, choose M here and read
886 <file:Documentation/networking/net-modules.txt>. The module will be
890 tristate "KS8695 ethernet support"
891 depends on ARCH_KS8695
893 Say 'Y' here to enable support for the Kendin-Micrel KS8695 internal
897 tristate "SMSC LAN911[5678] support"
900 depends on NET_ETHERNET && ARCH_PXA
902 This is a driver for SMSC's LAN911x series of Ethernet chipsets
903 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
904 Say Y if you want it compiled into the kernel,
905 and read the Ethernet-HOWTO, available from
906 <http://www.linuxdoc.org/docs.html#howto>.
908 This driver is also available as a module. The module will be
909 called smc911x. If you want to compile it as a module, say M
910 here and read <file:Documentation/modules.txt>
912 config NET_VENDOR_RACAL
913 bool "Racal-Interlan (Micom) NI cards"
914 depends on NET_ETHERNET && ISA
916 If you have a network (Ethernet) card belonging to this class, such
917 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
918 available from <http://www.tldp.org/docs.html#howto>.
920 Note that the answer to this question doesn't directly affect the
921 kernel: saying N will just cause the configurator to skip all
922 the questions about NI cards. If you say Y, you will be asked for
923 your specific card in the following questions.
926 tristate "NI5010 support (EXPERIMENTAL)"
927 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
929 If you have a network (Ethernet) card of this type, say Y and read
930 the Ethernet-HOWTO, available from
931 <http://www.tldp.org/docs.html#howto>. Note that this is still
934 To compile this driver as a module, choose M here and read
935 <file:Documentation/networking/net-modules.txt>. The module
936 will be called ni5010.
939 tristate "NI5210 support"
940 depends on NET_VENDOR_RACAL && ISA
942 If you have a network (Ethernet) card of this type, say Y and read
943 the Ethernet-HOWTO, available from
944 <http://www.tldp.org/docs.html#howto>.
946 To compile this driver as a module, choose M here and read
947 <file:Documentation/networking/net-modules.txt>. The module
951 tristate "NI6510 support"
952 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
954 If you have a network (Ethernet) card of this type, say Y and read
955 the Ethernet-HOWTO, available from
956 <http://www.tldp.org/docs.html#howto>.
958 To compile this driver as a module, choose M here and read
959 <file:Documentation/networking/net-modules.txt>. The module
962 source "drivers/net/tulip/Kconfig"
965 tristate "AT1700/1720 support (EXPERIMENTAL)"
966 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
969 If you have a network (Ethernet) card of this type, say Y and read
970 the Ethernet-HOWTO, available from
971 <http://www.tldp.org/docs.html#howto>.
973 To compile this driver as a module, choose M here and read
974 <file:Documentation/networking/net-modules.txt>. The module
975 will be called at1700.
978 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
979 depends on NET_ETHERNET && (ISA || EISA || MCA)
982 If you have a network (Ethernet) card of this type, say Y and read
983 the Ethernet-HOWTO, available from
984 <http://www.tldp.org/docs.html#howto> as well as
985 <file:drivers/net/depca.c>.
987 To compile this driver as a module, choose M here and read
988 <file:Documentation/networking/net-modules.txt>. The module
989 will be called depca.
992 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
993 depends on NET_ETHERNET && (ISA || EISA || PCI)
995 If you have a network (Ethernet) card of this type, say Y and read
996 the Ethernet-HOWTO, available from
997 <http://www.tldp.org/docs.html#howto>.
999 To compile this driver as a module, choose M here and read
1000 <file:Documentation/networking/net-modules.txt>. The module
1001 will be called hp100.
1004 bool "Other ISA cards"
1005 depends on NET_ETHERNET && ISA
1007 If your network (Ethernet) card hasn't been mentioned yet and its
1008 bus system (that's the way the cards talks to the other components
1009 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1010 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1011 available from <http://www.tldp.org/docs.html#howto>.
1015 Note that the answer to this question doesn't directly affect the
1016 kernel: saying N will just cause the configurator to skip all
1017 the remaining ISA network card questions. If you say Y, you will be
1018 asked for your specific card in the following questions.
1021 tristate "Cabletron E21xx support"
1025 If you have a network (Ethernet) card of this type, say Y and read
1026 the Ethernet-HOWTO, available from
1027 <http://www.tldp.org/docs.html#howto>.
1029 To compile this driver as a module, choose M here and read
1030 <file:Documentation/networking/net-modules.txt>. The module
1031 will be called e2100.
1034 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1038 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1039 cards. If this is for you, say Y and read
1040 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1041 well as the Ethernet-HOWTO, available from
1042 <http://www.tldp.org/docs.html#howto>.
1044 To compile this driver as a module, choose M here and read
1045 <file:Documentation/networking/net-modules.txt>. The module
1046 will be called ewrk3.
1049 tristate "EtherExpress 16 support"
1052 If you have an EtherExpress16 network (Ethernet) card, say Y and
1053 read the Ethernet-HOWTO, available from
1054 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1055 EtherExpress16 card used to be regarded as a very poor choice
1056 because the driver was very unreliable. We now have a new driver
1057 that should do better.
1059 To compile this driver as a module, choose M here and read
1060 <file:Documentation/networking/net-modules.txt>. The module
1061 will be called eexpress.
1064 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1067 If you have a network (Ethernet) card of this type, say Y. This
1068 driver supports Intel i82595{FX,TX} based boards. Note however
1069 that the EtherExpress PRO/100 Ethernet card has its own separate
1070 driver. Please read the Ethernet-HOWTO, available from
1071 <http://www.tldp.org/docs.html#howto>.
1073 To compile this driver as a module, choose M here and read
1074 <file:Documentation/networking/net-modules.txt>. The module
1075 will be called eepro.
1078 tristate "HP PCLAN+ (27247B and 27252A) support"
1082 If you have a network (Ethernet) card of this type, say Y and read
1083 the Ethernet-HOWTO, available from
1084 <http://www.tldp.org/docs.html#howto>.
1086 To compile this driver as a module, choose M here and read
1087 <file:Documentation/networking/net-modules.txt>. The module
1088 will be called hp-plus.
1091 tristate "HP PCLAN (27245 and other 27xxx series) support"
1095 If you have a network (Ethernet) card of this type, say Y and read
1096 the Ethernet-HOWTO, available from
1097 <http://www.tldp.org/docs.html#howto>.
1099 To compile this driver as a module, choose M here and read
1100 <file:Documentation/networking/net-modules.txt>. The module
1104 tristate "LP486E on board Ethernet"
1107 Say Y here to support the 82596-based on-board Ethernet controller
1108 for the Panther motherboard, which is one of the two shipped in the
1109 Intel Professional Workstation.
1112 tristate "ICL EtherTeam 16i/32 support"
1115 If you have a network (Ethernet) card of this type, say Y and read
1116 the Ethernet-HOWTO, available from
1117 <http://www.tldp.org/docs.html#howto>.
1119 To compile this driver as a module, choose M here and read
1120 <file:Documentation/networking/net-modules.txt>. The module
1121 will be called eth16i.
1124 tristate "NE2000/NE1000 support"
1125 depends on NET_ISA || (Q40 && m) || M32R || EMBEDDED
1128 If you have a network (Ethernet) card of this type, say Y and read
1129 the Ethernet-HOWTO, available from
1130 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1131 without a specific driver are compatible with NE2000.
1133 If you have a PCI NE2000 card however, say N here and Y to "PCI
1134 NE2000 and clone support" under "EISA, VLB, PCI and on board
1135 controllers" below. If you have a NE2000 card and are running on
1136 an MCA system (a bus system used on some IBM PS/2 computers and
1137 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1140 To compile this driver as a module, choose M here and read
1141 <file:Documentation/networking/net-modules.txt>. The module
1145 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1146 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1148 The Zenith Z-Note notebook computer has a built-in network
1149 (Ethernet) card, and this is the Linux driver for it. Note that the
1150 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1151 by this driver. Read the Ethernet-HOWTO, available from
1152 <http://www.tldp.org/docs.html#howto>.
1155 tristate "SEEQ8005 support (EXPERIMENTAL)"
1156 depends on NET_ISA && EXPERIMENTAL
1158 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1159 is for you, read the Ethernet-HOWTO, available from
1160 <http://www.tldp.org/docs.html#howto>.
1162 To compile this driver as a module, choose M here and read
1163 <file:Documentation/networking/net-modules.txt>. The module
1164 will be called seeq8005.
1167 tristate "SKnet MCA support"
1168 depends on NET_ETHERNET && MCA && BROKEN
1170 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1171 support" in order to use this driver. Supported cards are the SKnet
1172 Junior MC2 and the SKnet MC2(+). The driver automatically
1173 distinguishes between the two cards. Note that using multiple boards
1174 of different type hasn't been tested with this driver. Say Y if you
1175 have one of these Ethernet adapters.
1177 To compile this driver as a module, choose M here and read
1178 <file:Documentation/networking/net-modules.txt>. The module
1179 will be called sk_mca.
1182 tristate "NE/2 (ne2000 MCA version) support"
1183 depends on NET_ETHERNET && MCA_LEGACY
1186 If you have a network (Ethernet) card of this type, say Y and read
1187 the Ethernet-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>.
1190 To compile this driver as a module, choose M here and read
1191 <file:Documentation/networking/net-modules.txt>. The module
1195 tristate "IBM LAN Adapter/A support"
1196 depends on NET_ETHERNET && MCA && MCA_LEGACY
1198 This is a Micro Channel Ethernet adapter. You need to set
1199 CONFIG_MCA to use this driver. It is both available as an in-kernel
1200 driver and as a module.
1202 To compile this driver as a module, choose M here and read
1203 <file:Documentation/networking/net-modules.txt>. The only
1204 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1205 will both support 16K and 32K memory windows, however a 32K window
1206 gives a better security against packet losses. Usage of multiple
1207 boards with this driver should be possible, but has not been tested
1208 up to now due to lack of hardware.
1211 tristate "IBM LAN Virtual Ethernet support"
1212 depends on NET_ETHERNET && PPC_PSERIES
1214 This driver supports virtual ethernet adapters on newer IBM iSeries
1215 and pSeries systems.
1217 To compile this driver as a module, choose M here and read
1218 <file:Documentation/networking/net-modules.txt>. The module will
1222 tristate "PowerPC 4xx on-chip Ethernet support"
1225 This driver supports the PowerPC 4xx EMAC family of on-chip
1226 Ethernet controllers.
1229 int "Number of receive buffers"
1234 int "Number of transmit buffers"
1238 config IBM_EMAC_POLL_WEIGHT
1239 int "MAL NAPI polling weight"
1243 config IBM_EMAC_RX_COPY_THRESHOLD
1244 int "RX skb copy threshold (bytes)"
1248 config IBM_EMAC_RX_SKB_HEADROOM
1249 int "Additional RX skb headroom (bytes)"
1253 Additional receive skb headroom. Note, that driver
1254 will always reserve at least 2 bytes to make IP header
1255 aligned, so usually there is no need to add any additional
1258 If unsure, set to 0.
1260 config IBM_EMAC_PHY_RX_CLK_FIX
1261 bool "PHY Rx clock workaround"
1262 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1264 Enable this if EMAC attached to a PHY which doesn't generate
1265 RX clock if there is no link, if this is the case, you will
1266 see "TX disable timeout" or "RX disable timeout" in the system
1271 config IBM_EMAC_DEBUG
1276 config IBM_EMAC_ZMII
1278 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1281 config IBM_EMAC_RGMII
1283 depends on IBM_EMAC && 440GX
1288 depends on IBM_EMAC && 440GX
1292 bool "EISA, VLB, PCI and on board controllers"
1293 depends on NET_ETHERNET && (ISA || EISA || PCI || EMBEDDED)
1295 This is another class of network cards which attach directly to the
1296 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1297 available from <http://www.tldp.org/docs.html#howto>.
1299 Note that the answer to this question doesn't directly affect the
1300 kernel: saying N will just cause the configurator to skip all
1301 the questions about this class of network cards. If you say Y, you
1302 will be asked for your specific card in the following questions. If
1303 you are unsure, say Y.
1306 tristate "AMD PCnet32 PCI support"
1307 depends on NET_PCI && PCI
1311 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1312 answer Y here and read the Ethernet-HOWTO, available from
1313 <http://www.tldp.org/docs.html#howto>.
1315 To compile this driver as a module, choose M here and read
1316 <file:Documentation/networking/net-modules.txt>. The module
1317 will be called pcnet32.
1320 bool "Use RX polling (NAPI) (EXPERIMENTAL)"
1321 depends on PCNET32 && EXPERIMENTAL
1323 NAPI is a new driver API designed to reduce CPU and interrupt load
1324 when the driver is receiving lots of packets from the card. It is
1325 still somewhat experimental and thus not yet enabled by default.
1327 If your estimated Rx load is 10kpps or more, or if the card will be
1328 deployed on potentially unfriendly networks (e.g. in a firewall),
1331 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1337 tristate "AMD 8111 (new PCI lance) support"
1338 depends on NET_PCI && PCI
1342 If you have an AMD 8111-based PCI lance ethernet card,
1343 answer Y here and read the Ethernet-HOWTO, available from
1344 <http://www.tldp.org/docs.html#howto>.
1346 To compile this driver as a module, choose M here and read
1347 <file:Documentation/networking/net-modules.txt>. The module
1348 will be called amd8111e.
1349 config AMD8111E_NAPI
1350 bool "Enable NAPI support"
1351 depends on AMD8111_ETH
1353 NAPI is a new driver API designed to reduce CPU and interrupt load
1354 when the driver is receiving lots of packets from the card. It is
1355 still somewhat experimental and thus not yet enabled by default.
1357 If your estimated Rx load is 10kpps or more, or if the card will be
1358 deployed on potentially unfriendly networks (e.g. in a firewall),
1361 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1366 config ADAPTEC_STARFIRE
1367 tristate "Adaptec Starfire/DuraLAN support"
1368 depends on NET_PCI && PCI
1372 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1373 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1374 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1377 To compile this driver as a module, choose M here: the module
1378 will be called starfire. This is recommended.
1380 config ADAPTEC_STARFIRE_NAPI
1381 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1382 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1384 NAPI is a new driver API designed to reduce CPU and interrupt load
1385 when the driver is receiving lots of packets from the card. It is
1386 still somewhat experimental and thus not yet enabled by default.
1388 If your estimated Rx load is 10kpps or more, or if the card will be
1389 deployed on potentially unfriendly networks (e.g. in a firewall),
1392 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1398 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1399 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1402 If you have a network (Ethernet) card of this type, say Y and read
1403 the Ethernet-HOWTO, available from
1404 <http://www.tldp.org/docs.html#howto>.
1406 To compile this driver as a module, choose M here and read
1407 <file:Documentation/networking/net-modules.txt>. The module
1408 will be called ac3200.
1411 tristate "Apricot Xen-II on board Ethernet"
1412 depends on NET_PCI && ISA
1414 If you have a network (Ethernet) controller of this type, say Y and
1415 read the Ethernet-HOWTO, available from
1416 <http://www.tldp.org/docs.html#howto>.
1418 To compile this driver as a module, choose M here and read
1419 <file:Documentation/networking/net-modules.txt>. The module will be
1423 tristate "Broadcom 4400 ethernet support"
1424 depends on NET_PCI && PCI
1427 If you have a network (Ethernet) controller of this type, say Y and
1428 read the Ethernet-HOWTO, available from
1429 <http://www.tldp.org/docs.html#howto>.
1431 To compile this driver as a module, choose M here and read
1432 <file:Documentation/networking/net-modules.txt>. The module will be
1436 tristate "nForce Ethernet support"
1437 depends on NET_PCI && PCI
1439 If you have a network (Ethernet) controller of this type, say Y and
1440 read the Ethernet-HOWTO, available from
1441 <http://www.tldp.org/docs.html#howto>.
1443 To compile this driver as a module, choose M here and read
1444 <file:Documentation/networking/net-modules.txt>. The module will be
1447 config FORCEDETH_NAPI
1448 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1449 depends on FORCEDETH && EXPERIMENTAL
1451 NAPI is a new driver API designed to reduce CPU and interrupt load
1452 when the driver is receiving lots of packets from the card. It is
1453 still somewhat experimental and thus not yet enabled by default.
1455 If your estimated Rx load is 10kpps or more, or if the card will be
1456 deployed on potentially unfriendly networks (e.g. in a firewall),
1459 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1465 tristate "CS89x0 support"
1466 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || M68328 || M68EZ328 || M68VZ328 || MACH_DM270)
1468 Support for CS89x0 chipset based Ethernet cards. If you have a
1469 network (Ethernet) card of this type, say Y and read the
1470 Ethernet-HOWTO, available from
1471 <http://www.tldp.org/docs.html#howto> as well as
1472 <file:Documentation/networking/cs89x0.txt>.
1474 To compile this driver as a module, choose M here and read
1475 <file:Documentation/networking/net-modules.txt>. The module will be
1478 config CS89x0_SWAPPED
1479 bool "Hardware swapped CS89x0"
1480 depends on CS89x0 && !NET_PCI && !ISA
1482 Say Y if your CS89x0 data bus is swapped.
1483 This option is for single board computers using a CS89x0 chip. If you
1484 are using a regular Ethernet card, say N.
1487 tristate "TOSHIBA TC35815 Ethernet support"
1488 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1491 tristate "Digi Intl. RightSwitch SE-X support"
1492 depends on NET_PCI && (PCI || EISA)
1494 This is support for the Digi International RightSwitch series of
1495 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1496 models. If you have a network card of this type, say Y and read the
1497 Ethernet-HOWTO, available from
1498 <http://www.tldp.org/docs.html#howto>. More specific
1499 information is contained in <file:Documentation/networking/dgrs.txt>.
1501 To compile this driver as a module, choose M here and read
1502 <file:Documentation/networking/net-modules.txt>. The module
1503 will be called dgrs.
1506 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1507 depends on NET_PCI && PCI
1510 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1511 card, say Y and read the Ethernet-HOWTO, available from
1512 <http://www.tldp.org/docs.html#howto>.
1514 To compile this driver as a module, choose M here and read
1515 <file:Documentation/networking/net-modules.txt>. The module
1516 will be called eepro100.
1520 tristate "Intel(R) PRO/100+ support"
1521 depends on NET_PCI && PCI
1524 This driver supports Intel(R) PRO/100 family of adapters.
1525 To verify that your adapter is supported, find the board ID number
1526 on the adapter. Look for a label that has a barcode and a number
1527 in the format 123456-001 (six digits hyphen three digits).
1529 Use the above information and the Adapter & Driver ID Guide at:
1531 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1533 to identify the adapter.
1535 For the latest Intel PRO/100 network driver for Linux, see:
1537 <http://appsr.intel.com/scripts-df/support_intel.asp>
1539 More specific information on configuring the driver is in
1540 <file:Documentation/networking/e100.txt>.
1542 To compile this driver as a module, choose M here and read
1543 <file:Documentation/networking/net-modules.txt>. The module
1544 will be called e100.
1547 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1548 depends on NET_PCI && EISA && EXPERIMENTAL
1551 If you have a network (Ethernet) card of this type, say Y and read
1552 the Ethernet-HOWTO, available from
1553 <http://www.tldp.org/docs.html#howto>.
1555 To compile this driver as a module, choose M here and read
1556 <file:Documentation/networking/net-modules.txt>. The module
1557 will be called lne390.
1560 tristate "Myson MTD-8xx PCI Ethernet support"
1561 depends on NET_PCI && PCI
1565 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1566 cards. Specifications and data at
1567 <http://www.myson.com.hk/mtd/datasheet/>.
1570 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1571 depends on NET_PCI && PCI
1574 This driver is for the National Semiconductor DP83810 series,
1575 which is used in cards from PureData, NetGear, Linksys
1576 and others, including the 83815 chip.
1577 More specific information and updates are available from
1578 <http://www.scyld.com/network/natsemi.html>.
1581 tristate "PCI NE2000 and clones support (see help)"
1582 depends on NET_PCI && PCI
1585 This driver is for NE2000 compatible PCI cards. It will not work
1586 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1587 support" below). If you have a PCI NE2000 network (Ethernet) card,
1588 say Y and read the Ethernet-HOWTO, available from
1589 <http://www.tldp.org/docs.html#howto>.
1591 This driver also works for the following NE2000 clone cards:
1592 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1593 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1594 Holtek HT80232 Holtek HT80229
1596 To compile this driver as a module, choose M here and read
1597 <file:Documentation/networking/net-modules.txt>. The module
1598 will be called ne2k-pci.
1601 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1602 depends on NET_PCI && EISA && EXPERIMENTAL
1605 If you have a network (Ethernet) card of this type, say Y and read
1606 the Ethernet-HOWTO, available from
1607 <http://www.tldp.org/docs.html#howto>. Note that this driver
1608 will NOT WORK for NE3200 cards as they are completely different.
1610 To compile this driver as a module, choose M here and read
1611 <file:Documentation/networking/net-modules.txt>. The module
1612 will be called ne3210.
1615 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1616 depends on NET_PCI && EISA && EXPERIMENTAL
1619 If you have a network (Ethernet) card of this type, say Y and read
1620 the Ethernet-HOWTO, available from
1621 <http://www.tldp.org/docs.html#howto>.
1623 To compile this driver as a module, choose M here and read
1624 <file:Documentation/networking/net-modules.txt>. The module
1625 will be called es3210.
1628 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1629 depends on NET_PCI && PCI && EXPERIMENTAL
1633 This is a driver for the Fast Ethernet PCI network cards based on
1634 the RTL8139C+ chips. If you have one of those, say Y and read
1635 the Ethernet-HOWTO, available from
1636 <http://www.tldp.org/docs.html#howto>.
1638 To compile this driver as a module, choose M here: the module
1639 will be called 8139cp. This is recommended.
1641 config 8139CP_EXTERNAL_PHY
1642 bool "External PHY support for the 8139C+ driver"
1645 Allows for an external PHY (ie., hub chip)
1647 config 8139CP_PHY_NUM
1648 int "External PHY number for the 8139C+ driver"
1649 depends on 8139CP_EXTERNAL_PHY
1652 The PHY number for the external PHY.
1655 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1656 depends on NET_PCI && PCI
1660 This is a driver for the Fast Ethernet PCI network cards based on
1661 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1662 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1664 To compile this driver as a module, choose M here: the module
1665 will be called 8139too. This is recommended.
1668 bool "Use PIO instead of MMIO"
1672 This instructs the driver to use programmed I/O ports (PIO) instead
1673 of PCI shared memory (MMIO). This can possibly solve some problems
1674 in case your mainboard has memory consistency issues. If unsure,
1677 config 8139TOO_TUNE_TWISTER
1678 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1681 This implements a function which might come in handy in case you
1682 are using low quality on long cabling. It is required for RealTek
1683 RTL-8139 revision K boards, and totally unused otherwise. It tries
1684 to match the transceiver to the cable characteristics. This is
1685 experimental since hardly documented by the manufacturer.
1689 bool "Support for older RTL-8129/8130 boards"
1692 This enables support for the older and uncommon RTL-8129 and
1693 RTL-8130 chips, which support MII via an external transceiver,
1694 instead of an internal one. Disabling this option will save some
1695 memory by making the code size smaller. If unsure, say Y.
1697 config 8139_OLD_RX_RESET
1698 bool "Use older RX-reset method"
1701 The 8139too driver was recently updated to contain a more rapid
1702 reset sequence, in the face of severe receive errors. This "new"
1703 RX-reset method should be adequate for all boards. But if you
1704 experience problems, you can enable this option to restore the
1705 old RX-reset behavior. If unsure, say N.
1708 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1709 depends on NET_PCI && PCI
1713 This is a driver for the Fast Ethernet PCI network cards based on
1714 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1715 SiS 630 and SiS 540 chipsets.
1717 This driver also supports AMD 79C901 HomePNA so that you can use
1718 your phone line as a network cable.
1720 To compile this driver as a module, choose M here: the module
1721 will be called sis900. This is recommended.
1724 tristate "SMC EtherPower II"
1725 depends on NET_PCI && PCI
1729 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1730 which is based on the SMC83c17x (EPIC/100).
1731 More specific information and updates are available from
1732 <http://www.scyld.com/network/epic100.html>.
1735 tristate "Sundance Alta support"
1736 depends on NET_PCI && PCI
1740 This driver is for the Sundance "Alta" chip.
1741 More specific information and updates are available from
1742 <http://www.scyld.com/network/sundance.html>.
1744 config SUNDANCE_MMIO
1745 bool "Use MMIO instead of PIO"
1748 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1749 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1750 is known to solve bugs on certain chips.
1755 tristate "TI ThunderLAN support"
1756 depends on NET_PCI && (PCI || EISA) && !64BIT
1758 If you have a PCI Ethernet network card based on the ThunderLAN chip
1759 which is supported by this driver, say Y and read the
1760 Ethernet-HOWTO, available from
1761 <http://www.tldp.org/docs.html#howto>.
1763 Devices currently supported by this driver are Compaq Netelligent,
1764 Compaq NetFlex and Olicom cards. Please read the file
1765 <file:Documentation/networking/tlan.txt> for more details.
1767 To compile this driver as a module, choose M here and read
1768 <file:Documentation/networking/net-modules.txt>. The module
1769 will be called tlan.
1771 Please email feedback to <torben.mathiasen@compaq.com>.
1774 tristate "VIA Rhine support"
1775 depends on NET_PCI && PCI
1779 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1780 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1781 Ethernet functions can also be found integrated on South Bridges
1784 To compile this driver as a module, choose M here. The module
1785 will be called via-rhine.
1787 config VIA_RHINE_MMIO
1788 bool "Use MMIO instead of PIO"
1789 depends on VIA_RHINE
1791 This instructs the driver to use PCI shared memory (MMIO) instead of
1792 programmed I/O ports (PIO). Enabling this gives an improvement in
1793 processing time in parts of the driver.
1797 config VIA_RHINE_NAPI
1798 bool "Use Rx Polling (NAPI)"
1799 depends on VIA_RHINE
1801 NAPI is a new driver API designed to reduce CPU and interrupt load
1802 when the driver is receiving lots of packets from the card.
1804 If your estimated Rx load is 10kpps or more, or if the card will be
1805 deployed on potentially unfriendly networks (e.g. in a firewall),
1808 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1812 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1813 depends on NET_PCI && EXPERIMENTAL && MIPS
1815 The SAA9730 is a combined multimedia and peripheral controller used
1816 in thin clients, Internet access terminals, and diskless
1818 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1821 bool "Pocket and portable adapters"
1822 depends on NET_ETHERNET && PARPORT
1824 Cute little network (Ethernet) devices which attach to the parallel
1825 port ("pocket adapters"), commonly used with laptops. If you have
1826 one of those, say Y and read the Ethernet-HOWTO, available from
1827 <http://www.tldp.org/docs.html#howto>.
1829 If you want to plug a network (or some other) card into the PCMCIA
1830 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1831 credit card size extension cards used by all modern laptops), you
1832 need the pcmcia-cs package (location contained in the file
1833 <file:Documentation/Changes>) and you can say N here.
1835 Laptop users should read the Linux Laptop home page at
1836 <http://www.linux-on-laptops.com/> or
1837 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1839 Note that the answer to this question doesn't directly affect the
1840 kernel: saying N will just cause the configurator to skip all
1841 the questions about this class of network devices. If you say Y, you
1842 will be asked for your specific device in the following questions.
1845 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1846 depends on NET_POCKET && PARPORT && X86
1849 This is a network (Ethernet) device which attaches to your parallel
1850 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1851 available from <http://www.tldp.org/docs.html#howto>, if you
1852 want to use this. If you intend to use this driver, you should have
1853 said N to the "Parallel printer support", because the two drivers
1854 don't like each other.
1856 To compile this driver as a module, choose M here: the module
1860 tristate "D-Link DE600 pocket adapter support"
1861 depends on NET_POCKET && PARPORT
1863 This is a network (Ethernet) device which attaches to your parallel
1864 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1865 Ethernet-HOWTO, available from
1866 <http://www.tldp.org/docs.html#howto>, if you want to use
1867 this. It is possible to have several devices share a single parallel
1868 port and it is safe to compile the corresponding drivers into the
1871 To compile this driver as a module, choose M here: the module
1872 will be called de600.
1875 tristate "D-Link DE620 pocket adapter support"
1876 depends on NET_POCKET && PARPORT
1878 This is a network (Ethernet) device which attaches to your parallel
1879 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1880 Ethernet-HOWTO, available from
1881 <http://www.tldp.org/docs.html#howto>, if you want to use
1882 this. It is possible to have several devices share a single parallel
1883 port and it is safe to compile the corresponding drivers into the
1886 To compile this driver as a module, choose M here: the module
1887 will be called de620.
1890 tristate "SGI Seeq ethernet controller support"
1891 depends on NET_ETHERNET && SGI_IP22
1893 Say Y here if you have an Seeq based Ethernet network card. This is
1894 used in many Silicon Graphics machines.
1897 tristate "DEC LANCE ethernet controller support"
1898 depends on NET_ETHERNET && MACH_DECSTATION
1901 This driver is for the series of Ethernet controllers produced by
1902 DEC (now Compaq) based on the AMD Lance chipset, including the
1903 DEPCA series. (This chipset is better known via the NE2100 cards.)
1906 bool "FEC ethernet controller (of ColdFire CPUs)"
1907 depends on M523x || M527x || M5272 || M528x || M520x || M532x
1909 Say Y here if you want to use the built-in 10/100 Fast ethernet
1910 controller on some Motorola ColdFire processors.
1913 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1916 Say Y here if you want to use the second built-in 10/100 Fast
1917 ethernet controller on some Motorola ColdFire processors.
1920 tristate "NE2000 compatible support for H8/300"
1921 depends on H8300 && NET_ETHERNET
1923 Say Y here if you want to use the NE2000 compatible
1924 controller on the Renesas H8/300 processor.
1926 source "drivers/net/fec_8xx/Kconfig"
1927 source "drivers/net/fs_enet/Kconfig"
1935 menu "Ethernet (1000 Mbit)"
1939 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1942 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1943 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1944 adapter. The driver allows for using the Jumbo Frame option (9000
1945 bytes/frame) however it requires that your switches can handle this
1946 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1949 To compile this driver as a module, choose M here: the
1950 module will be called acenic.
1952 config ACENIC_OMIT_TIGON_I
1953 bool "Omit support for old Tigon I based AceNICs"
1956 Say Y here if you only have Tigon II based AceNICs and want to leave
1957 out support for the older Tigon I based cards which are no longer
1958 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1959 version)). This will reduce the size of the driver object by
1960 app. 100KB. If you are not sure whether your card is a Tigon I or a
1961 Tigon II, say N here.
1963 The safe and default value for this is N.
1966 tristate "D-Link DL2000-based Gigabit Ethernet support"
1970 This driver supports D-Link 2000-based gigabit ethernet cards, which
1972 D-Link DGE-550T Gigabit Ethernet Adapter.
1973 D-Link DL2000-based Gigabit Ethernet Adapter.
1975 To compile this driver as a module, choose M here: the
1976 module will be called dl2k.
1979 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1982 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1983 adapters. For more information on how to identify your adapter, go
1984 to the Adapter & Driver ID Guide at:
1986 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1988 For general information and support, go to the Intel support
1991 <http://support.intel.com>
1993 More specific information on configuring the driver is in
1994 <file:Documentation/networking/e1000.txt>.
1996 To compile this driver as a module, choose M here and read
1997 <file:Documentation/networking/net-modules.txt>. The module
1998 will be called e1000.
2001 bool "Use Rx Polling (NAPI)"
2004 NAPI is a new driver API designed to reduce CPU and interrupt load
2005 when the driver is receiving lots of packets from the card. It is
2006 still somewhat experimental and thus not yet enabled by default.
2008 If your estimated Rx load is 10kpps or more, or if the card will be
2009 deployed on potentially unfriendly networks (e.g. in a firewall),
2012 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2017 config E1000_DISABLE_PACKET_SPLIT
2018 bool "Disable Packet Split for PCI express adapters"
2021 Say Y here if you want to use the legacy receive path for PCI express
2026 source "drivers/net/ixp2000/Kconfig"
2029 tristate "MyriCOM Gigabit Ethernet support"
2032 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2034 To compile this driver as a module, choose M here: the module
2035 will be called myri_sbus. This is recommended.
2038 tristate "National Semiconductor DP83820 support"
2041 This is a driver for the National Semiconductor DP83820 series
2042 of gigabit ethernet MACs. Cards using this chipset include
2043 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2044 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2048 tristate "Packet Engines Hamachi GNIC-II support"
2052 If you have a Gigabit Ethernet card of this type, say Y and read
2053 the Ethernet-HOWTO, available from
2054 <http://www.tldp.org/docs.html#howto>.
2056 To compile this driver as a module, choose M here and read
2057 <file:Documentation/networking/net-modules.txt>. The module will be
2061 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2062 depends on PCI && EXPERIMENTAL
2065 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2066 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2067 used by the Beowulf Linux cluster project. See
2068 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2069 information about this driver in particular and Beowulf in general.
2071 To compile this driver as a module, choose M here: the module
2072 will be called yellowfin. This is recommended.
2075 tristate "Realtek 8169 gigabit ethernet support"
2079 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2081 To compile this driver as a module, choose M here: the module
2082 will be called r8169. This is recommended.
2085 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2086 depends on R8169 && EXPERIMENTAL
2088 NAPI is a new driver API designed to reduce CPU and interrupt load
2089 when the driver is receiving lots of packets from the card. It is
2090 still somewhat experimental and thus not yet enabled by default.
2092 If your estimated Rx load is 10kpps or more, or if the card will be
2093 deployed on potentially unfriendly networks (e.g. in a firewall),
2096 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2103 depends on R8169 && VLAN_8021Q
2105 Say Y here for the r8169 driver to support the functions required
2106 by the kernel 802.1Q code.
2111 tristate "SiS190/SiS191 gigabit ethernet support"
2116 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2117 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2118 appear in lan on motherboard designs which are based on SiS 965
2119 and SiS 966 south bridge.
2121 To compile this driver as a module, choose M here: the module
2122 will be called sis190. This is recommended.
2125 tristate "New SysKonnect GigaEthernet support"
2129 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2130 and related Gigabit Ethernet adapters. It is a new smaller driver
2131 with better performance and more complete ethtool support.
2133 It does not support the link failover and network management
2134 features that "portable" vendor supplied sk98lin driver does.
2136 This driver supports adapters based on the original Yukon chipset:
2137 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2138 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2140 It does not support the newer Yukon2 chipset: a separate driver,
2141 sky2, is provided for Yukon2-based adapters.
2143 To compile this driver as a module, choose M here: the module
2144 will be called skge. This is recommended.
2147 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2151 This driver supports Gigabit Ethernet adapters based on the
2152 Marvell Yukon 2 chipset:
2153 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2154 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2156 There is companion driver for the older Marvell Yukon and
2157 Genesis based adapters: skge.
2159 To compile this driver as a module, choose M here: the module
2160 will be called sky2. This is recommended.
2163 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2166 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2167 compliant Gigabit Ethernet Adapter.
2169 This driver supports the original Yukon chipset. A cleaner driver is
2170 also available (skge) which seems to work better than this one.
2172 This driver does not support the newer Yukon2 chipset. A seperate
2173 driver, sky2, is provided to support Yukon2-based adapters.
2175 The following adapters are supported by this driver:
2176 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2177 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2178 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2179 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2180 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2181 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2182 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2183 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2184 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2185 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2186 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2187 - EG1032 v2 Instant Gigabit Network Adapter
2188 - EG1064 v2 Instant Gigabit Network Adapter
2189 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2190 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2191 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2192 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2193 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2194 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2195 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2196 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2197 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2198 - Marvell RDK-8001 Adapter
2199 - Marvell RDK-8002 Adapter
2200 - Marvell RDK-8003 Adapter
2201 - Marvell RDK-8004 Adapter
2202 - Marvell RDK-8006 Adapter
2203 - Marvell RDK-8007 Adapter
2204 - Marvell RDK-8008 Adapter
2205 - Marvell RDK-8009 Adapter
2206 - Marvell RDK-8010 Adapter
2207 - Marvell RDK-8011 Adapter
2208 - Marvell RDK-8012 Adapter
2209 - Marvell RDK-8052 Adapter
2210 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2211 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2212 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2213 - SK-9521 10/100/1000Base-T Adapter
2214 - SK-9521 V2.0 10/100/1000Base-T Adapter
2215 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2216 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2217 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2218 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2219 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2220 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2221 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2222 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2223 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2224 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2225 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2226 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2227 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2228 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2229 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2230 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2231 - SMC EZ Card 1000 (SMC9452TXV.2)
2233 The adapters support Jumbo Frames.
2234 The dual link adapters support link-failover and dual port features.
2235 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2236 the scatter-gather functionality with sendfile(). Please refer to
2237 <file:Documentation/networking/sk98lin.txt> for more information about
2238 optional driver parameters.
2239 Questions concerning this driver may be addressed to:
2240 <linux@syskonnect.de>
2242 If you want to compile this driver as a module ( = code which can be
2243 inserted in and removed from the running kernel whenever you want),
2244 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2245 be called sk98lin. This is recommended.
2248 tristate "VIA Velocity support"
2249 depends on NET_PCI && PCI
2254 If you have a VIA "Velocity" based network card say Y here.
2256 To compile this driver as a module, choose M here. The module
2257 will be called via-velocity.
2260 tristate "Broadcom Tigon3 support"
2263 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2265 To compile this driver as a module, choose M here: the module
2266 will be called tg3. This is recommended.
2269 tristate "Broadcom NetXtremeII support"
2274 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2276 To compile this driver as a module, choose M here: the module
2277 will be called bnx2. This is recommended.
2280 tristate "Spider Gigabit Ethernet driver"
2281 depends on PCI && PPC_IBM_CELL_BLADE
2284 This driver supports the Gigabit Ethernet chips present on the
2285 Cell Processor-Based Blades from IBM.
2288 tristate "Gianfar Ethernet"
2289 depends on 85xx || 83xx || PPC_86xx
2292 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2293 and MPC86xx family of chips, and the FEC on the 8540.
2300 tristate "Freescale QE UCC GETH"
2301 depends on QUICC_ENGINE && UCC_FAST
2303 This driver supports the Gigabit Ethernet mode of QE UCC.
2304 QE can be found on MPC836x CPUs.
2310 config UGETH_MAGIC_PACKET
2311 bool "Magic Packet detection support"
2314 config UGETH_FILTERING
2315 bool "Mac address filtering support"
2318 config UGETH_TX_ON_DEMOND
2319 bool "Transmit on Demond support"
2322 config UGETH_HAS_GIGA
2324 depends on UCC_GETH && PPC_MPC836x
2327 tristate "MV-643XX Ethernet support"
2328 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || (PPC_MULTIPLATFORM && PPC32)
2331 This driver supports the gigabit Ethernet on the Marvell MV643XX
2332 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2333 Pegasos II, amongst other PPC and MIPS boards.
2335 config MV643XX_ETH_0
2336 bool "MV-643XX Port 0"
2337 depends on MV643XX_ETH
2339 This enables support for Port 0 of the Marvell MV643XX Gigabit
2342 config MV643XX_ETH_1
2343 bool "MV-643XX Port 1"
2344 depends on MV643XX_ETH
2346 This enables support for Port 1 of the Marvell MV643XX Gigabit
2349 config MV643XX_ETH_2
2350 bool "MV-643XX Port 2"
2351 depends on MV643XX_ETH
2353 This enables support for Port 2 of the Marvell MV643XX Gigabit
2357 tristate "QLogic QLA3XXX Network Driver Support"
2360 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2362 To compile this driver as a module, choose M here: the module
2363 will be called qla3xxx.
2368 # 10 Gigabit Ethernet
2371 menu "Ethernet (10000 Mbit)"
2375 tristate "Chelsio 10Gb Ethernet support"
2378 This driver supports Chelsio N110 and N210 models 10Gb Ethernet
2379 cards. More information about adapter features and performance
2380 tuning is in <file:Documentation/networking/cxgb.txt>.
2382 For general information about Chelsio and our products, visit
2383 our website at <http://www.chelsio.com>.
2385 For customer support, please visit our customer support page at
2386 <http://www.chelsio.com/support.htm>.
2388 Please send feedback to <linux-bugs@chelsio.com>.
2390 To compile this driver as a module, choose M here: the module
2391 will be called cxgb.
2394 tristate "eHEA Ethernet support"
2397 This driver supports the IBM pSeries eHEA ethernet adapter.
2399 To compile the driver as a module, choose M here. The module
2400 will be called ehea.
2403 tristate "Intel(R) PRO/10GbE support"
2406 This driver supports Intel(R) PRO/10GbE family of
2407 adapters. For more information on how to identify your adapter, go
2408 to the Adapter & Driver ID Guide at:
2410 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2412 For general information and support, go to the Intel support
2415 <http://support.intel.com>
2417 More specific information on configuring the driver is in
2418 <file:Documentation/networking/ixgb.txt>.
2420 To compile this driver as a module, choose M here and read
2421 <file:Documentation/networking/net-modules.txt>. The module
2422 will be called ixgb.
2425 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2426 depends on IXGB && EXPERIMENTAL
2428 NAPI is a new driver API designed to reduce CPU and interrupt load
2429 when the driver is receiving lots of packets from the card. It is
2430 still somewhat experimental and thus not yet enabled by default.
2432 If your estimated Rx load is 10kpps or more, or if the card will be
2433 deployed on potentially unfriendly networks (e.g. in a firewall),
2436 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2442 tristate "S2IO 10Gbe XFrame NIC"
2445 This driver supports the 10Gbe XFrame NIC of S2IO.
2446 More specific information on configuring the driver is in
2447 <file:Documentation/networking/s2io.txt>.
2450 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2451 depends on S2IO && EXPERIMENTAL
2453 NAPI is a new driver API designed to reduce CPU and interrupt load
2454 when the driver is receiving lots of packets from the card. It is
2455 still somewhat experimental and thus not yet enabled by default.
2457 If your estimated Rx load is 10kpps or more, or if the card will be
2458 deployed on potentially unfriendly networks (e.g. in a firewall),
2461 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2467 tristate "Myricom Myri-10G Ethernet support"
2472 This driver supports Myricom Myri-10G Dual Protocol interface in
2473 Ethernet mode. If the eeprom on your board is not recent enough,
2474 you will need a newer firmware image.
2475 You may get this image or more information, at:
2477 <http://www.myri.com/scs/download-Myri10GE.html>
2479 To compile this driver as a module, choose M here and read
2480 <file:Documentation/networking/net-modules.txt>. The module
2481 will be called myri10ge.
2485 source "drivers/net/tokenring/Kconfig"
2487 source "drivers/net/wireless/Kconfig"
2489 source "drivers/net/pcmcia/Kconfig"
2491 source "drivers/net/wan/Kconfig"
2493 source "drivers/atm/Kconfig"
2495 source "drivers/s390/net/Kconfig"
2498 tristate "iSeries Virtual Ethernet driver support"
2499 depends on PPC_ISERIES
2502 tristate "RapidIO Ethernet over messaging driver support"
2505 config RIONET_TX_SIZE
2506 int "Number of outbound queue entries"
2510 config RIONET_RX_SIZE
2511 int "Number of inbound queue entries"
2516 bool "FDDI driver support"
2517 depends on (PCI || EISA)
2519 Fiber Distributed Data Interface is a high speed local area network
2520 design; essentially a replacement for high speed Ethernet. FDDI can
2521 run over copper or fiber. If you are connected to such a network and
2522 want a driver for the FDDI card in your computer, say Y here (and
2523 then also Y to the driver for your FDDI card, below). Most people
2527 tristate "Digital DEFEA and DEFPA adapter support"
2528 depends on FDDI && (PCI || EISA)
2530 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2531 (DEFPA) controllers which can connect you to a local FDDI network.
2534 tristate "SysKonnect FDDI PCI support"
2535 depends on FDDI && PCI
2537 Say Y here if you have a SysKonnect FDDI PCI adapter.
2538 The following adapters are supported by this driver:
2539 - SK-5521 (SK-NET FDDI-UP)
2540 - SK-5522 (SK-NET FDDI-UP DAS)
2541 - SK-5541 (SK-NET FDDI-FP)
2542 - SK-5543 (SK-NET FDDI-LP)
2543 - SK-5544 (SK-NET FDDI-LP DAS)
2544 - SK-5821 (SK-NET FDDI-UP64)
2545 - SK-5822 (SK-NET FDDI-UP64 DAS)
2546 - SK-5841 (SK-NET FDDI-FP64)
2547 - SK-5843 (SK-NET FDDI-LP64)
2548 - SK-5844 (SK-NET FDDI-LP64 DAS)
2549 - Netelligent 100 FDDI DAS Fibre SC
2550 - Netelligent 100 FDDI SAS Fibre SC
2551 - Netelligent 100 FDDI DAS UTP
2552 - Netelligent 100 FDDI SAS UTP
2553 - Netelligent 100 FDDI SAS Fibre MIC
2555 Read <file:Documentation/networking/skfp.txt> for information about
2558 Questions concerning this driver can be addressed to:
2559 <linux@syskonnect.de>
2561 To compile this driver as a module, choose M here: the module
2562 will be called skfp. This is recommended.
2565 bool "HIPPI driver support (EXPERIMENTAL)"
2566 depends on EXPERIMENTAL && INET && PCI
2568 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2569 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2570 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2571 single-mode). HIPPI networks are commonly used for clusters and to
2572 connect to super computers. If you are connected to a HIPPI network
2573 and have a HIPPI network card in your computer that you want to use
2574 under Linux, say Y here (you must also remember to enable the driver
2575 for your HIPPI card below). Most people will say N here.
2578 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2579 depends on HIPPI && PCI
2581 Say Y here if this is your PCI HIPPI network card.
2583 To compile this driver as a module, choose M here: the module
2584 will be called rrunner. If unsure, say N.
2586 config ROADRUNNER_LARGE_RINGS
2587 bool "Use large TX/RX rings (EXPERIMENTAL)"
2588 depends on ROADRUNNER
2590 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2591 of additional memory to allow for fastest operation, both for
2592 transmitting and receiving. This memory cannot be used by any other
2593 kernel code or by user space programs. Say Y here only if you have
2597 tristate "PLIP (parallel port) support"
2600 PLIP (Parallel Line Internet Protocol) is used to create a
2601 reasonably fast mini network consisting of two (or, rarely, more)
2602 local machines. A PLIP link from a Linux box is a popular means to
2603 install a Linux distribution on a machine which doesn't have a
2604 CD-ROM drive (a minimal system has to be transferred with floppies
2605 first). The kernels on both machines need to have this PLIP option
2606 enabled for this to work.
2608 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2609 ports (the connectors at the computers with 25 holes) are connected
2610 with "null printer" or "Turbo Laplink" cables which can transmit 4
2611 bits at a time (mode 0) or with special PLIP cables, to be used on
2612 bidirectional parallel ports only, which can transmit 8 bits at a
2613 time (mode 1); you can find the wiring of these cables in
2614 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2615 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2616 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2617 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2618 and winsock or NCSA's telnet.
2620 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2621 as the NET-3-HOWTO, both available from
2622 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2623 protocol has been changed and this PLIP driver won't work together
2624 with the PLIP support in Linux versions 1.0.x. This option enlarges
2625 your kernel by about 8 KB.
2627 To compile this driver as a module, choose M here and read
2628 <file:Documentation/networking/net-modules.txt>. The module will be
2629 called plip. If unsure, say Y or M, in case you buy a laptop
2633 tristate "PPP (point-to-point protocol) support"
2636 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2637 the same purpose: sending Internet traffic over telephone (and other
2638 serial) lines. Ask your access provider if they support it, because
2639 otherwise you can't use it; most Internet access providers these
2640 days support PPP rather than SLIP.
2642 To use PPP, you need an additional program called pppd as described
2643 in the PPP-HOWTO, available at
2644 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2645 the version of pppd recommended in <file:Documentation/Changes>.
2646 The PPP option enlarges your kernel by about 16 KB.
2648 There are actually two versions of PPP: the traditional PPP for
2649 asynchronous lines, such as regular analog phone lines, and
2650 synchronous PPP which can be used over digital ISDN lines for
2651 example. If you want to use PPP over phone lines or other
2652 asynchronous serial lines, you need to say Y (or M) here and also to
2653 the next option, "PPP support for async serial ports". For PPP over
2654 synchronous lines, you should say Y (or M) here and to "Support
2655 synchronous PPP", below.
2657 If you said Y to "Version information on all symbols" above, then
2658 you cannot compile the PPP driver into the kernel; you can then only
2659 compile it as a module. To compile this driver as a module, choose M
2660 here and read <file:Documentation/networking/net-modules.txt>.
2661 The module will be called ppp_generic.
2663 config PPP_MULTILINK
2664 bool "PPP multilink support (EXPERIMENTAL)"
2665 depends on PPP && EXPERIMENTAL
2667 PPP multilink is a protocol (defined in RFC 1990) which allows you
2668 to combine several (logical or physical) lines into one logical PPP
2669 connection, so that you can utilize your full bandwidth.
2671 This has to be supported at the other end as well and you need a
2672 version of the pppd daemon which understands the multilink protocol.
2677 bool "PPP filtering"
2680 Say Y here if you want to be able to filter the packets passing over
2681 PPP interfaces. This allows you to control which packets count as
2682 activity (i.e. which packets will reset the idle timer or bring up
2683 a demand-dialed link) and which packets are to be dropped entirely.
2684 You need to say Y here if you wish to use the pass-filter and
2685 active-filter options to pppd.
2690 tristate "PPP support for async serial ports"
2694 Say Y (or M) here if you want to be able to use PPP over standard
2695 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2696 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2699 To compile this driver as a module, choose M here.
2704 tristate "PPP support for sync tty ports"
2707 Say Y (or M) here if you want to be able to use PPP over synchronous
2708 (HDLC) tty devices, such as the SyncLink adapter. These devices
2709 are often used for high-speed leased lines like T1/E1.
2711 To compile this driver as a module, choose M here.
2714 tristate "PPP Deflate compression"
2719 Support for the Deflate compression method for PPP, which uses the
2720 Deflate algorithm (the same algorithm that gzip uses) to compress
2721 each PPP packet before it is sent over the wire. The machine at the
2722 other end of the PPP link (usually your ISP) has to support the
2723 Deflate compression method as well for this to be useful. Even if
2724 they don't support it, it is safe to say Y here.
2726 To compile this driver as a module, choose M here.
2729 tristate "PPP BSD-Compress compression"
2732 Support for the BSD-Compress compression method for PPP, which uses
2733 the LZW compression method to compress each PPP packet before it is
2734 sent over the wire. The machine at the other end of the PPP link
2735 (usually your ISP) has to support the BSD-Compress compression
2736 method as well for this to be useful. Even if they don't support it,
2737 it is safe to say Y here.
2739 The PPP Deflate compression method ("PPP Deflate compression",
2740 above) is preferable to BSD-Compress, because it compresses better
2743 Note that the BSD compression code will always be compiled as a
2744 module; it is called bsd_comp and will show up in the directory
2745 modules once you have said "make modules". If unsure, say N.
2748 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2749 depends on PPP && EXPERIMENTAL
2755 Support for the MPPE Encryption protocol, as employed by the
2756 Microsoft Point-to-Point Tunneling Protocol.
2758 See http://pptpclient.sourceforge.net/ for information on
2759 configuring PPTP clients and servers to utilize this method.
2762 tristate "PPP over Ethernet (EXPERIMENTAL)"
2763 depends on EXPERIMENTAL && PPP
2765 Support for PPP over Ethernet.
2767 This driver requires the latest version of pppd from the CVS
2768 repository at cvs.samba.org. Alternatively, see the
2769 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2770 which contains instruction on how to use this driver (under
2771 the heading "Kernel mode PPPoE").
2774 tristate "PPP over ATM"
2775 depends on ATM && PPP
2777 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2778 This implementation does not yet comply with section 8 of RFC2364,
2779 which can lead to bad results if the ATM peer loses state and
2780 changes its encapsulation unilaterally.
2783 tristate "SLIP (serial line) support"
2785 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2786 connect to your Internet service provider or to connect to some
2787 other local Unix box or if you want to configure your Linux box as a
2788 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2789 Internet Protocol) is a protocol used to send Internet traffic over
2790 serial connections such as telephone lines or null modem cables;
2791 nowadays, the protocol PPP is more commonly used for this same
2794 Normally, your access provider has to support SLIP in order for you
2795 to be able to use it, but there is now a SLIP emulator called SLiRP
2796 around (available from
2797 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2798 allows you to use SLIP over a regular dial up shell connection. If
2799 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2800 NET-3-HOWTO, available from
2801 <http://www.tldp.org/docs.html#howto>, explains how to
2802 configure SLIP. Note that you don't need this option if you just
2803 want to run term (term is a program which gives you almost full
2804 Internet connectivity if you have a regular dial up shell account on
2805 some Internet connected Unix computer. Read
2806 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2807 support will enlarge your kernel by about 4 KB. If unsure, say N.
2809 To compile this driver as a module, choose M here and read
2810 <file:Documentation/networking/net-modules.txt>. The module will be
2813 config SLIP_COMPRESSED
2814 bool "CSLIP compressed headers"
2818 This protocol is faster than SLIP because it uses compression on the
2819 TCP/IP headers (not on the data itself), but it has to be supported
2820 on both ends. Ask your access provider if you are not sure and
2821 answer Y, just in case. You will still be able to use plain SLIP. If
2822 you plan to use SLiRP, the SLIP emulator (available from
2823 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2824 allows you to use SLIP over a regular dial up shell connection, you
2825 definitely want to say Y here. The NET-3-HOWTO, available from
2826 <http://www.tldp.org/docs.html#howto>, explains how to configure
2827 CSLIP. This won't enlarge your kernel.
2832 This option enables Van Jacobsen serial line header compression
2836 bool "Keepalive and linefill"
2839 Adds additional capabilities to the SLIP driver to support the
2840 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2843 config SLIP_MODE_SLIP6
2844 bool "Six bit SLIP encapsulation"
2847 Just occasionally you may need to run IP over hostile serial
2848 networks that don't pass all control characters or are only seven
2849 bit. Saying Y here adds an extra mode you can use with SLIP:
2850 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2851 the serial device. Naturally, this has to be supported at the other
2852 end of the link as well. It's good enough, for example, to run IP
2853 over the async ports of a Camtec JNT Pad. If unsure, say N.
2856 bool "Fibre Channel driver support"
2857 depends on SCSI && PCI
2859 Fibre Channel is a high speed serial protocol mainly used to connect
2860 large storage devices to the computer; it is compatible with and
2861 intended to replace SCSI.
2863 If you intend to use Fibre Channel, you need to have a Fibre channel
2864 adaptor card in your computer; say Y here and to the driver for your
2865 adaptor below. You also should have said Y to "SCSI support" and
2866 "SCSI generic support".
2869 tristate "Traffic Shaper (OBSOLETE)"
2870 depends on EXPERIMENTAL
2872 The traffic shaper is a virtual network device that allows you to
2873 limit the rate of outgoing data flow over some other network device.
2874 The traffic that you want to slow down can then be routed through
2875 these virtual devices. See
2876 <file:Documentation/networking/shaper.txt> for more information.
2878 An alternative to this traffic shaper are traffic schedulers which
2879 you'll get if you say Y to "QoS and/or fair queuing" in
2880 "Networking options".
2882 To compile this driver as a module, choose M here: the module
2883 will be called shaper. If unsure, say N.
2886 tristate "Network console logging support (EXPERIMENTAL)"
2887 depends on EXPERIMENTAL
2889 If you want to log kernel messages over the network, enable this.
2890 See <file:Documentation/networking/netconsole.txt> for details.
2898 bool "Netpoll support for trapping incoming packets"
2903 bool "Netpoll traffic trapping"
2907 config NET_POLL_CONTROLLER