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>.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermidiate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
64 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
65 Channels together. This is called 'Etherchannel' by Cisco,
66 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
68 The driver supports multiple bonding modes to allow for both high
69 performance and high availability operation.
71 Refer to <file:Documentation/networking/bonding.txt> for more
74 To compile this driver as a module, choose M here: the module
75 will be called bonding.
78 tristate "EQL (serial line load balancing) support"
80 If you have two serial connections to some other computer (this
81 usually requires two modems and two telephone lines) and you use
82 SLIP (the protocol for sending Internet traffic over telephone
83 lines) or PPP (a better SLIP) on them, you can make them behave like
84 one double speed connection using this driver. Naturally, this has
85 to be supported at the other end as well, either with a similar EQL
86 Linux driver or with a Livingston Portmaster 2e.
88 Say Y if you want this and read
89 <file:Documentation/networking/eql.txt>. You may also want to read
90 section 6.2 of the NET-3-HOWTO, available from
91 <http://www.tldp.org/docs.html#howto>.
93 To compile this driver as a module, choose M here: the module
94 will be called eql. If unsure, say N.
97 tristate "Universal TUN/TAP device driver support"
100 TUN/TAP provides packet reception and transmission for user space
101 programs. It can be viewed as a simple Point-to-Point or Ethernet
102 device, which instead of receiving packets from a physical media,
103 receives them from user space program and instead of sending packets
104 via physical media writes them to the user space program.
106 When a program opens /dev/net/tun, driver creates and registers
107 corresponding net device tunX or tapX. After a program closed above
108 devices, driver will automatically delete tunXX or tapXX device and
109 all routes corresponding to it.
111 Please read <file:Documentation/networking/tuntap.txt> for more
114 To compile this driver as a module, choose M here: the module
117 If you don't know what to use this for, you don't need it.
120 tristate "General Instruments Surfboard 1000"
123 This is a driver for the General Instrument (also known as
124 NextLevel) SURFboard 1000 internal
125 cable modem. This is an ISA card which is used by a number of cable
126 TV companies to provide cable modem access. It's a one-way
127 downstream-only cable modem, meaning that your upstream net link is
128 provided by your regular phone modem.
130 At present this driver only compiles as a module, so say M here if
131 you have this card. The module will be called sb1000. Then read
132 <file:Documentation/networking/README.sb1000> for information on how
133 to use this module, as it needs special ppp scripts for establishing
134 a connection. Further documentation and the necessary scripts can be
137 <http://www.jacksonville.net/~fventuri/>
138 <http://home.adelphia.net/~siglercm/sb1000.html>
139 <http://linuxpower.cx/~cable/>
141 If you don't have this card, of course say N.
143 source "drivers/net/arcnet/Kconfig"
145 source "drivers/net/phy/Kconfig"
151 menu "Ethernet (10 or 100Mbit)"
155 bool "Ethernet (10 or 100Mbit)"
157 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
158 type of Local Area Network (LAN) in universities and companies.
160 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
161 coaxial cable, linking computers in a chain), 10BASE-T or twisted
162 pair (10 Mbps over twisted pair cable, linking computers to central
163 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
164 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
165 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
166 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
167 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
168 Ethernet (1 Gbps over optical fiber or short copper links).
170 If your Linux machine will be connected to an Ethernet and you have
171 an Ethernet network interface card (NIC) installed in your computer,
172 say Y here and read the Ethernet-HOWTO, available from
173 <http://www.tldp.org/docs.html#howto>. You will then also have
174 to say Y to the driver for your particular NIC.
176 Note that the answer to this question won't directly affect the
177 kernel: saying N will just cause the configurator to skip all
178 the questions about Ethernet network cards. If unsure, say N.
181 tristate "Generic Media Independent Interface device support"
182 depends on NET_ETHERNET
184 Most ethernet controllers have MII transceiver either as an external
185 or internal device. It is safe to say Y or M here even if your
186 ethernet card lack MII.
188 source "drivers/net/arm/Kconfig"
191 tristate "MACE (Power Mac ethernet) support"
192 depends on NET_ETHERNET && PPC_PMAC && PPC32
195 Power Macintoshes and clones with Ethernet built-in on the
196 motherboard will usually use a MACE (Medium Access Control for
197 Ethernet) interface. Say Y to include support for the MACE chip.
199 To compile this driver as a module, choose M here: the module
202 config MACE_AAUI_PORT
203 bool "Use AAUI port instead of TP by default"
206 Some Apple machines (notably the Apple Network Server) which use the
207 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
208 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
209 Y here if you have such a machine. If unsure, say N.
210 The driver will default to AAUI on ANS anyway, and if you use it as
211 a module, you can provide the port_aaui=0|1 to force the driver.
214 tristate "BMAC (G3 ethernet) support"
215 depends on NET_ETHERNET && PPC_PMAC && PPC32
218 Say Y for support of BMAC Ethernet interfaces. These are used on G3
221 To compile this driver as a module, choose M here: the module
225 tristate "National DP83902AV (Oak ethernet) support"
226 depends on NET_ETHERNET && PPC && BROKEN
229 Say Y if your machine has this type of Ethernet network card.
231 To compile this driver as a module, choose M here: the module
232 will be called oaknet.
235 tristate "Ariadne support"
236 depends on NET_ETHERNET && ZORRO
238 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
241 To compile this driver as a module, choose M here: the module
242 will be called ariadne.
245 tristate "A2065 support"
246 depends on NET_ETHERNET && ZORRO
249 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
252 To compile this driver as a module, choose M here: the module
253 will be called a2065.
256 tristate "Hydra support"
257 depends on NET_ETHERNET && ZORRO
260 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
262 To compile this driver as a module, choose M here: the module
263 will be called hydra.
266 tristate "Zorro NS8390-based Ethernet support"
267 depends on NET_ETHERNET && ZORRO
270 This driver is for Zorro Ethernet cards using an NS8390-compatible
271 chipset, like the Village Tronic Ariadne II and the Individual
272 Computers X-Surf Ethernet cards. If you have such a card, say Y.
275 To compile this driver as a module, choose M here: the module
276 will be called zorro8390.
279 tristate "PCMCIA NE2000 support"
280 depends on NET_ETHERNET && AMIGA_PCMCIA
283 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
286 To compile this driver as a module, choose M here: the module
290 tristate "Apollo 3c505 support"
291 depends on NET_ETHERNET && APOLLO
293 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
294 If you don't have one made for Apollos, you can use one from a PC,
295 except that your Apollo won't be able to boot from it (because the
296 code in the ROM will be for a PC).
299 bool "Macintosh NS 8390 based ethernet cards"
300 depends on NET_ETHERNET && MAC
303 If you want to include a driver to support Nubus or LC-PDS
304 Ethernet cards using an NS8390 chipset or its equivalent, say Y
305 and read the Ethernet-HOWTO, available from
306 <http://www.tldp.org/docs.html#howto>.
309 tristate "Macintosh CS89x0 based ethernet cards"
310 depends on NET_ETHERNET && MAC && BROKEN
312 Support for CS89x0 chipset based Ethernet cards. If you have a
313 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
314 read the Ethernet-HOWTO, available from
315 <http://www.tldp.org/docs.html#howto>.
317 To compile this driver as a module, choose M here and read
318 <file:Documentation/networking/net-modules.txt>. This module will
322 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
323 depends on NET_ETHERNET && MAC
325 Support for NatSemi SONIC based Ethernet devices. This includes
326 the onboard Ethernet in many Quadras as well as some LC-PDS,
327 a few Nubus and all known Comm Slot Ethernet cards. If you have
328 one of these say Y and read the Ethernet-HOWTO, available from
329 <http://www.tldp.org/docs.html#howto>.
331 To compile this driver as a module, choose M here and read
332 <file:Documentation/networking/net-modules.txt>. This module will
336 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
337 depends on NET_ETHERNET && MAC && EXPERIMENTAL
340 Support for the onboard AMD 79C940 MACE Ethernet controller used in
341 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
342 say Y and read the Ethernet-HOWTO, available from
343 <http://www.tldp.org/docs.html#howto>.
346 tristate "MVME147 (Lance) Ethernet support"
347 depends on NET_ETHERNET && MVME147
350 Support for the on-board Ethernet interface on the Motorola MVME147
351 single-board computer. Say Y here to include the
352 driver for this chip in your kernel.
353 To compile this driver as a module, choose M here.
356 tristate "MVME16x Ethernet support"
357 depends on NET_ETHERNET && MVME16x
359 This is the driver for the Ethernet interface on the Motorola
360 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
361 driver for this chip in your kernel.
362 To compile this driver as a module, choose M here.
365 tristate "BVME6000 Ethernet support"
366 depends on NET_ETHERNET && BVME6000
368 This is the driver for the Ethernet interface on BVME4000 and
369 BVME6000 VME boards. Say Y here to include the driver for this chip
371 To compile this driver as a module, choose M here.
374 tristate "Atari Lance support"
375 depends on NET_ETHERNET && ATARI
377 Say Y to include support for several Atari Ethernet adapters based
378 on the AMD Lance chipset: RieblCard (with or without battery), or
379 PAMCard VME (also the version by Rhotron, with different addresses).
382 tristate "BioNet-100 support"
383 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
385 Say Y to include support for BioData's BioNet-100 Ethernet adapter
386 for the ACSI port. The driver works (has to work...) with a polled
387 I/O scheme, so it's rather slow :-(
390 tristate "PAMsNet support"
391 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
393 Say Y to include support for the PAMsNet Ethernet adapter for the
394 ACSI port ("ACSI node"). The driver works (has to work...) with a
395 polled I/O scheme, so it's rather slow :-(
398 tristate "Sun3/Sun3x on-board LANCE support"
399 depends on NET_ETHERNET && (SUN3 || SUN3X)
401 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
402 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
403 here to compile in the Linux driver for this and enable Ethernet.
404 General Linux information on the Sun 3 and 3x series (now
406 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
408 If you're not building a kernel for a Sun 3, say N.
411 bool "Sun3 on-board Intel 82586 support"
412 depends on NET_ETHERNET && SUN3
414 This driver enables support for the on-board Intel 82586 based
415 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
416 that this driver does not support 82586-based adapters on additional
420 bool "HP on-board LANCE support"
421 depends on NET_ETHERNET && DIO
424 If you want to use the builtin "LANCE" Ethernet controller on an
425 HP300 machine, say Y here.
428 tristate "Lasi ethernet"
429 depends on NET_ETHERNET && PARISC && GSC_LASI
431 Say Y here to support the on-board Intel 82596 ethernet controller
432 built into Hewlett-Packard PA-RISC machines.
434 config MIPS_JAZZ_SONIC
435 tristate "MIPS JAZZ onboard SONIC Ethernet support"
436 depends on NET_ETHERNET && MACH_JAZZ
438 This is the driver for the onboard card of MIPS Magnum 4000,
439 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
441 config MIPS_GT96100ETH
442 bool "MIPS GT96100 Ethernet support"
443 depends on NET_ETHERNET && MIPS_GT96100
445 Say Y here to support the Ethernet subsystem on your GT96100 card.
447 config MIPS_AU1X00_ENET
448 bool "MIPS AU1000 Ethernet support"
449 depends on NET_ETHERNET && SOC_AU1X00
453 If you have an Alchemy Semi AU1X00 based system
454 say Y. Otherwise, say N.
456 config NET_SB1250_MAC
457 tristate "SB1250 Ethernet support"
458 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
461 bool "SGI IOC3 Ethernet"
462 depends on NET_ETHERNET && PCI && SGI_IP27
466 If you have a network (Ethernet) card of this type, say Y and read
467 the Ethernet-HOWTO, available from
468 <http://www.tldp.org/docs.html#howto>.
470 config SGI_IOC3_ETH_HW_RX_CSUM
471 bool "Receive hardware checksums"
472 depends on SGI_IOC3_ETH && INET
475 The SGI IOC3 network adapter supports TCP and UDP checksums in
476 hardware to offload processing of these checksums from the CPU. At
477 the moment only acceleration of IPv4 is supported. This option
478 enables offloading for checksums on receive. If unsure, say Y.
480 config SGI_IOC3_ETH_HW_TX_CSUM
481 bool "Transmit hardware checksums"
482 depends on SGI_IOC3_ETH && INET
485 The SGI IOC3 network adapter supports TCP and UDP checksums in
486 hardware to offload processing of these checksums from the CPU. At
487 the moment only acceleration of IPv4 is supported. This option
488 enables offloading for checksums on transmit. If unsure, say Y.
491 tristate "MIPS simulator Network device (EXPERIMENTAL)"
492 depends on NETDEVICES && MIPS_SIM && EXPERIMENTAL
494 The MIPSNET device is a simple Ethernet network device which is
495 emulated by the MIPS Simulator.
496 If you are not using a MIPSsim or are unsure, say N.
498 config SGI_O2MACE_ETH
499 tristate "SGI O2 MACE Fast Ethernet support"
500 depends on NET_ETHERNET && SGI_IP32=y
503 tristate "National DP83902AV support"
504 depends on NET_ETHERNET && SUPERH
507 Support for cards based on the National Semiconductor DP83902AV
508 ST-NIC Serial Network Interface Controller for Twisted Pair. This
509 is a 10Mbit/sec Ethernet controller. Product overview and specs at
510 <http://www.national.com/pf/DP/DP83902A.html>.
515 tristate "Sun LANCE support"
516 depends on NET_ETHERNET && SBUS
519 This driver supports the "le" interface present on all 32-bit Sparc
520 systems, on some older Ultra systems and as an Sbus option. These
521 cards are based on the AMD Lance chipset, which is better known
522 via the NE2100 cards.
524 To compile this driver as a module, choose M here: the module
525 will be called sunlance.
528 tristate "Sun Happy Meal 10/100baseT support"
529 depends on NET_ETHERNET && (SBUS || PCI)
532 This driver supports the "hme" interface present on most Ultra
533 systems and as an option on older Sbus systems. This driver supports
534 both PCI and Sbus devices. This driver also supports the "qfe" quad
535 100baseT device available in both PCI and Sbus configurations.
537 To compile this driver as a module, choose M here: the module
538 will be called sunhme.
541 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
542 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
545 This driver supports the "be" interface available as an Sbus option.
546 This is Sun's older 100baseT Ethernet device.
548 To compile this driver as a module, choose M here: the module
549 will be called sunbmac.
552 tristate "Sun QuadEthernet support"
553 depends on NET_ETHERNET && SBUS
556 This driver supports the "qe" 10baseT Ethernet device, available as
557 an Sbus option. Note that this is not the same as Quad FastEthernet
558 "qfe" which is supported by the Happy Meal driver instead.
560 To compile this driver as a module, choose M here: the module
561 will be called sunqe.
564 tristate "Sun GEM support"
565 depends on NET_ETHERNET && PCI
568 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
569 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
572 tristate "Sun Cassini support"
573 depends on NET_ETHERNET && PCI
576 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
577 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
579 config NET_VENDOR_3COM
581 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
583 If you have a network (Ethernet) card belonging to this class, say Y
584 and read the Ethernet-HOWTO, available from
585 <http://www.tldp.org/docs.html#howto>.
587 Note that the answer to this question doesn't directly affect the
588 kernel: saying N will just cause the configurator to skip all
589 the questions about 3COM cards. If you say Y, you will be asked for
590 your specific card in the following questions.
593 tristate "3c501 \"EtherLink\" support"
594 depends on NET_VENDOR_3COM && ISA
596 If you have a network (Ethernet) card of this type, say Y and read
597 the Ethernet-HOWTO, available from
598 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
599 new card, since the 3c501 is slow, broken, and obsolete: you will
600 have problems. Some people suggest to ping ("man ping") a nearby
601 machine every minute ("man cron") when using this card.
603 To compile this driver as a module, choose M here and read
604 <file:Documentation/networking/net-modules.txt>. The module
605 will be called 3c501.
608 tristate "3c503 \"EtherLink II\" support"
609 depends on NET_VENDOR_3COM && ISA
612 If you have a network (Ethernet) card of this type, say Y and read
613 the Ethernet-HOWTO, available from
614 <http://www.tldp.org/docs.html#howto>.
616 To compile this driver as a module, choose M here and read
617 <file:Documentation/networking/net-modules.txt>. The module
618 will be called 3c503.
621 tristate "3c505 \"EtherLink Plus\" support"
622 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
624 Information about this network (Ethernet) card can be found in
625 <file:Documentation/networking/3c505.txt>. If you have a card of
626 this type, say Y and read the Ethernet-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>.
629 To compile this driver as a module, choose M here and read
630 <file:Documentation/networking/net-modules.txt>. The module
631 will be called 3c505.
634 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
635 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
637 If you have a network (Ethernet) card of this type, say Y and read
638 the Ethernet-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
641 To compile this driver as a module, choose M here and read
642 <file:Documentation/networking/net-modules.txt>. The module
643 will be called 3c507.
646 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
647 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
649 If you have a network (Ethernet) card belonging to the 3Com
650 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
651 from <http://www.tldp.org/docs.html#howto>.
653 If your card is not working you may need to use the DOS
654 setup disk to disable Plug & Play mode, and to select the default
657 To compile this driver as a module, choose M here and read
658 <file:Documentation/networking/net-modules.txt>. The module
659 will be called 3c509.
662 tristate "3c515 ISA \"Fast EtherLink\""
663 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
665 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
666 network card, say Y and read the Ethernet-HOWTO, available from
667 <http://www.tldp.org/docs.html#howto>.
669 To compile this driver as a module, choose M here and read
670 <file:Documentation/networking/net-modules.txt>. The module
671 will be called 3c515.
674 tristate "3c523 \"EtherLink/MC\" support"
675 depends on NET_VENDOR_3COM && MCA_LEGACY
677 If you have a network (Ethernet) card of this type, say Y and read
678 the Ethernet-HOWTO, available from
679 <http://www.tldp.org/docs.html#howto>.
681 To compile this driver as a module, choose M here and read
682 <file:Documentation/networking/net-modules.txt>. The module
683 will be called 3c523.
686 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
687 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
689 If you have a network (Ethernet) card of this type, say Y and read
690 the Ethernet-HOWTO, available from
691 <http://www.tldp.org/docs.html#howto>.
693 To compile this driver as a module, choose M here and read
694 <file:Documentation/networking/net-modules.txt>. The module
695 will be called 3c527.
698 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
699 depends on NET_VENDOR_3COM && (PCI || EISA)
702 This option enables driver support for a large number of 10Mbps and
703 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
705 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
706 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
707 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
708 "Tornado" (3c905) PCI
709 "Hurricane" (3c555/3cSOHO) PCI
711 If you have such a card, say Y and read the Ethernet-HOWTO,
712 available from <http://www.tldp.org/docs.html#howto>. More
713 specific information is in
714 <file:Documentation/networking/vortex.txt> and in the comments at
715 the beginning of <file:drivers/net/3c59x.c>.
717 To compile this support as a module, choose M here and read
718 <file:Documentation/networking/net-modules.txt>.
721 tristate "3cr990 series \"Typhoon\" support"
722 depends on NET_VENDOR_3COM && PCI
725 This option enables driver support for the 3cr990 series of cards:
727 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
728 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
729 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
731 If you have a network (Ethernet) card of this type, say Y and read
732 the Ethernet-HOWTO, available from
733 <http://www.tldp.org/docs.html#howto>.
735 To compile this driver as a module, choose M here and read
736 <file:Documentation/networking/net-modules.txt>. The module
737 will be called typhoon.
740 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
741 depends on NET_ETHERNET && ISA && ISA_DMA_API
743 If you have a network (Ethernet) card of this type, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
748 To compile this driver as a module, choose M here: the module
749 will be called lance. This is recommended.
751 config NET_VENDOR_SMC
752 bool "Western Digital/SMC cards"
753 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
755 If you have a network (Ethernet) card belonging to this class, say Y
756 and read the Ethernet-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>.
759 Note that the answer to this question doesn't directly affect the
760 kernel: saying N will just cause the configurator to skip all
761 the questions about Western Digital cards. If you say Y, you will be
762 asked for your specific card in the following questions.
765 tristate "WD80*3 support"
766 depends on NET_VENDOR_SMC && ISA
769 If you have a network (Ethernet) card of this type, say Y and read
770 the Ethernet-HOWTO, available from
771 <http://www.tldp.org/docs.html#howto>.
773 To compile this driver as a module, choose M here and read
774 <file:Documentation/networking/net-modules.txt>. The module
778 tristate "SMC Ultra MCA support"
779 depends on NET_VENDOR_SMC && MCA
782 If you have a network (Ethernet) card of this type and are running
783 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
784 available from <http://www.tldp.org/docs.html#howto>.
786 To compile this driver as a module, choose M here and read
787 <file:Documentation/networking/net-modules.txt>. The module
788 will be called smc-mca.
791 tristate "SMC Ultra support"
792 depends on NET_VENDOR_SMC && ISA
795 If you have a network (Ethernet) card of this type, say Y and read
796 the Ethernet-HOWTO, available from
797 <http://www.tldp.org/docs.html#howto>.
799 Important: There have been many reports that, with some motherboards
800 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
801 such as some BusLogic models) causes corruption problems with many
802 operating systems. The Linux smc-ultra driver has a work-around for
803 this but keep it in mind if you have such a SCSI card and have
806 To compile this driver as a module, choose M here and read
807 <file:Documentation/networking/net-modules.txt>. The module
808 will be called smc-ultra.
811 tristate "SMC Ultra32 EISA support"
812 depends on NET_VENDOR_SMC && EISA
815 If you have a network (Ethernet) card of this type, say Y and read
816 the Ethernet-HOWTO, available from
817 <http://www.tldp.org/docs.html#howto>.
819 To compile this driver as a module, choose M here and read
820 <file:Documentation/networking/net-modules.txt>. The module
821 will be called smc-ultra32.
824 tristate "SMC 91C9x/91C1xxx support"
827 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00)
829 This is a driver for SMC's 91x series of Ethernet chipsets,
830 including the SMC91C94 and the SMC91C111. Say Y if you want it
831 compiled into the kernel, and read the file
832 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
833 available from <http://www.linuxdoc.org/docs.html#howto>.
835 This driver is also available as a module ( = code which can be
836 inserted in and removed from the running kernel whenever you want).
837 The module will be called smc91x. If you want to compile it as a
838 module, say M here and read <file:Documentation/modules.txt> as well
839 as <file:Documentation/networking/net-modules.txt>.
842 tristate "SMC 9194 support"
843 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
846 This is support for the SMC9xxx based Ethernet cards. Choose this
847 option if you have a DELL laptop with the docking station, or
848 another SMC9192/9194 based chipset. Say Y if you want it compiled
849 into the kernel, and read the file
850 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
851 available from <http://www.tldp.org/docs.html#howto>.
853 To compile this driver as a module, choose M here and read
854 <file:Documentation/networking/net-modules.txt>. The module
855 will be called smc9194.
858 tristate "NetX Ethernet support"
860 depends on NET_ETHERNET && ARCH_NETX
862 This is support for the Hilscher netX builtin Ethernet ports
864 To compile this driver as a module, choose M here and read
865 <file:Documentation/networking/net-modules.txt>. The module
866 will be called netx-eth.
869 tristate "DM9000 support"
870 depends on (ARM || MIPS) && NET_ETHERNET
874 Support for DM9000 chipset.
876 To compile this driver as a module, choose M here and read
877 <file:Documentation/networking/net-modules.txt>. The module will be
881 tristate "SMSC LAN911[5678] support"
884 depends on NET_ETHERNET && ARCH_PXA
886 This is a driver for SMSC's LAN911x series of Ethernet chipsets
887 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
888 Say Y if you want it compiled into the kernel,
889 and read the Ethernet-HOWTO, available from
890 <http://www.linuxdoc.org/docs.html#howto>.
892 This driver is also available as a module. The module will be
893 called smc911x. If you want to compile it as a module, say M
894 here and read <file:Documentation/modules.txt>
896 config NET_VENDOR_RACAL
897 bool "Racal-Interlan (Micom) NI cards"
898 depends on NET_ETHERNET && ISA
900 If you have a network (Ethernet) card belonging to this class, such
901 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
902 available from <http://www.tldp.org/docs.html#howto>.
904 Note that the answer to this question doesn't directly affect the
905 kernel: saying N will just cause the configurator to skip all
906 the questions about NI cards. If you say Y, you will be asked for
907 your specific card in the following questions.
910 tristate "NI5010 support (EXPERIMENTAL)"
911 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
913 If you have a network (Ethernet) card of this type, say Y and read
914 the Ethernet-HOWTO, available from
915 <http://www.tldp.org/docs.html#howto>. Note that this is still
918 To compile this driver as a module, choose M here and read
919 <file:Documentation/networking/net-modules.txt>. The module
920 will be called ni5010.
923 tristate "NI5210 support"
924 depends on NET_VENDOR_RACAL && ISA
926 If you have a network (Ethernet) card of this type, say Y and read
927 the Ethernet-HOWTO, available from
928 <http://www.tldp.org/docs.html#howto>.
930 To compile this driver as a module, choose M here and read
931 <file:Documentation/networking/net-modules.txt>. The module
935 tristate "NI6510 support"
936 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
938 If you have a network (Ethernet) card of this type, say Y and read
939 the Ethernet-HOWTO, available from
940 <http://www.tldp.org/docs.html#howto>.
942 To compile this driver as a module, choose M here and read
943 <file:Documentation/networking/net-modules.txt>. The module
946 source "drivers/net/tulip/Kconfig"
949 tristate "AT1700/1720 support (EXPERIMENTAL)"
950 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
953 If you have a network (Ethernet) card of this type, say Y and read
954 the Ethernet-HOWTO, available from
955 <http://www.tldp.org/docs.html#howto>.
957 To compile this driver as a module, choose M here and read
958 <file:Documentation/networking/net-modules.txt>. The module
959 will be called at1700.
962 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
963 depends on NET_ETHERNET && (ISA || EISA || MCA)
966 If you have a network (Ethernet) card of this type, say Y and read
967 the Ethernet-HOWTO, available from
968 <http://www.tldp.org/docs.html#howto> as well as
969 <file:drivers/net/depca.c>.
971 To compile this driver as a module, choose M here and read
972 <file:Documentation/networking/net-modules.txt>. The module
973 will be called depca.
976 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
977 depends on NET_ETHERNET && (ISA || EISA || PCI)
979 If you have a network (Ethernet) card of this type, say Y and read
980 the Ethernet-HOWTO, available from
981 <http://www.tldp.org/docs.html#howto>.
983 To compile this driver as a module, choose M here and read
984 <file:Documentation/networking/net-modules.txt>. The module
985 will be called hp100.
988 bool "Other ISA cards"
989 depends on NET_ETHERNET && ISA
991 If your network (Ethernet) card hasn't been mentioned yet and its
992 bus system (that's the way the cards talks to the other components
993 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
994 Make sure you know the name of your card. Read the Ethernet-HOWTO,
995 available from <http://www.tldp.org/docs.html#howto>.
999 Note that the answer to this question doesn't directly affect the
1000 kernel: saying N will just cause the configurator to skip all
1001 the remaining ISA network card questions. If you say Y, you will be
1002 asked for your specific card in the following questions.
1005 tristate "Cabletron E21xx support"
1009 If you have a network (Ethernet) card of this type, say Y and read
1010 the Ethernet-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1013 To compile this driver as a module, choose M here and read
1014 <file:Documentation/networking/net-modules.txt>. The module
1015 will be called e2100.
1018 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1022 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1023 cards. If this is for you, say Y and read
1024 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1025 well as the Ethernet-HOWTO, available from
1026 <http://www.tldp.org/docs.html#howto>.
1028 To compile this driver as a module, choose M here and read
1029 <file:Documentation/networking/net-modules.txt>. The module
1030 will be called ewrk3.
1033 tristate "EtherExpress 16 support"
1036 If you have an EtherExpress16 network (Ethernet) card, say Y and
1037 read the Ethernet-HOWTO, available from
1038 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1039 EtherExpress16 card used to be regarded as a very poor choice
1040 because the driver was very unreliable. We now have a new driver
1041 that should do better.
1043 To compile this driver as a module, choose M here and read
1044 <file:Documentation/networking/net-modules.txt>. The module
1045 will be called eexpress.
1048 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1051 If you have a network (Ethernet) card of this type, say Y. This
1052 driver supports Intel i82595{FX,TX} based boards. Note however
1053 that the EtherExpress PRO/100 Ethernet card has its own separate
1054 driver. Please read the Ethernet-HOWTO, available from
1055 <http://www.tldp.org/docs.html#howto>.
1057 To compile this driver as a module, choose M here and read
1058 <file:Documentation/networking/net-modules.txt>. The module
1059 will be called eepro.
1062 tristate "HP PCLAN+ (27247B and 27252A) support"
1066 If you have a network (Ethernet) card of this type, say Y and read
1067 the Ethernet-HOWTO, available from
1068 <http://www.tldp.org/docs.html#howto>.
1070 To compile this driver as a module, choose M here and read
1071 <file:Documentation/networking/net-modules.txt>. The module
1072 will be called hp-plus.
1075 tristate "HP PCLAN (27245 and other 27xxx series) support"
1079 If you have a network (Ethernet) card of this type, say Y and read
1080 the Ethernet-HOWTO, available from
1081 <http://www.tldp.org/docs.html#howto>.
1083 To compile this driver as a module, choose M here and read
1084 <file:Documentation/networking/net-modules.txt>. The module
1088 tristate "LP486E on board Ethernet"
1091 Say Y here to support the 82596-based on-board Ethernet controller
1092 for the Panther motherboard, which is one of the two shipped in the
1093 Intel Professional Workstation.
1096 tristate "ICL EtherTeam 16i/32 support"
1099 If you have a network (Ethernet) card of this type, say Y and read
1100 the Ethernet-HOWTO, available from
1101 <http://www.tldp.org/docs.html#howto>.
1103 To compile this driver as a module, choose M here and read
1104 <file:Documentation/networking/net-modules.txt>. The module
1105 will be called eth16i.
1108 tristate "NE2000/NE1000 support"
1109 depends on NET_ISA || (Q40 && m) || M32R
1112 If you have a network (Ethernet) card of this type, say Y and read
1113 the Ethernet-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1115 without a specific driver are compatible with NE2000.
1117 If you have a PCI NE2000 card however, say N here and Y to "PCI
1118 NE2000 and clone support" under "EISA, VLB, PCI and on board
1119 controllers" below. If you have a NE2000 card and are running on
1120 an MCA system (a bus system used on some IBM PS/2 computers and
1121 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1124 To compile this driver as a module, choose M here and read
1125 <file:Documentation/networking/net-modules.txt>. The module
1129 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1130 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1132 The Zenith Z-Note notebook computer has a built-in network
1133 (Ethernet) card, and this is the Linux driver for it. Note that the
1134 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1135 by this driver. Read the Ethernet-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1139 tristate "SEEQ8005 support (EXPERIMENTAL)"
1140 depends on NET_ISA && EXPERIMENTAL
1142 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1143 is for you, read the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1146 To compile this driver as a module, choose M here and read
1147 <file:Documentation/networking/net-modules.txt>. The module
1148 will be called seeq8005.
1151 tristate "SKnet MCA support"
1152 depends on NET_ETHERNET && MCA && BROKEN
1154 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1155 support" in order to use this driver. Supported cards are the SKnet
1156 Junior MC2 and the SKnet MC2(+). The driver automatically
1157 distinguishes between the two cards. Note that using multiple boards
1158 of different type hasn't been tested with this driver. Say Y if you
1159 have one of these Ethernet adapters.
1161 To compile this driver as a module, choose M here and read
1162 <file:Documentation/networking/net-modules.txt>. The module
1163 will be called sk_mca.
1166 tristate "NE/2 (ne2000 MCA version) support"
1167 depends on NET_ETHERNET && MCA_LEGACY
1170 If you have a network (Ethernet) card of this type, say Y and read
1171 the Ethernet-HOWTO, available from
1172 <http://www.tldp.org/docs.html#howto>.
1174 To compile this driver as a module, choose M here and read
1175 <file:Documentation/networking/net-modules.txt>. The module
1179 tristate "IBM LAN Adapter/A support"
1180 depends on NET_ETHERNET && MCA && MCA_LEGACY
1182 This is a Micro Channel Ethernet adapter. You need to set
1183 CONFIG_MCA to use this driver. It is both available as an in-kernel
1184 driver and as a module.
1186 To compile this driver as a module, choose M here and read
1187 <file:Documentation/networking/net-modules.txt>. The only
1188 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1189 will both support 16K and 32K memory windows, however a 32K window
1190 gives a better security against packet losses. Usage of multiple
1191 boards with this driver should be possible, but has not been tested
1192 up to now due to lack of hardware.
1195 tristate "IBM LAN Virtual Ethernet support"
1196 depends on NET_ETHERNET && PPC_PSERIES
1198 This driver supports virtual ethernet adapters on newer IBM iSeries
1199 and pSeries systems.
1201 To compile this driver as a module, choose M here and read
1202 <file:Documentation/networking/net-modules.txt>. The module will
1206 tristate "PowerPC 4xx on-chip Ethernet support"
1209 This driver supports the PowerPC 4xx EMAC family of on-chip
1210 Ethernet controllers.
1213 int "Number of receive buffers"
1218 int "Number of transmit buffers"
1222 config IBM_EMAC_POLL_WEIGHT
1223 int "MAL NAPI polling weight"
1227 config IBM_EMAC_RX_COPY_THRESHOLD
1228 int "RX skb copy threshold (bytes)"
1232 config IBM_EMAC_RX_SKB_HEADROOM
1233 int "Additional RX skb headroom (bytes)"
1237 Additional receive skb headroom. Note, that driver
1238 will always reserve at least 2 bytes to make IP header
1239 aligned, so usually there is no need to add any additional
1242 If unsure, set to 0.
1244 config IBM_EMAC_PHY_RX_CLK_FIX
1245 bool "PHY Rx clock workaround"
1246 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1248 Enable this if EMAC attached to a PHY which doesn't generate
1249 RX clock if there is no link, if this is the case, you will
1250 see "TX disable timeout" or "RX disable timeout" in the system
1255 config IBM_EMAC_DEBUG
1260 config IBM_EMAC_ZMII
1262 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1265 config IBM_EMAC_RGMII
1267 depends on IBM_EMAC && 440GX
1272 depends on IBM_EMAC && 440GX
1276 bool "EISA, VLB, PCI and on board controllers"
1277 depends on NET_ETHERNET && (ISA || EISA || PCI)
1279 This is another class of network cards which attach directly to the
1280 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1281 available from <http://www.tldp.org/docs.html#howto>.
1283 Note that the answer to this question doesn't directly affect the
1284 kernel: saying N will just cause the configurator to skip all
1285 the questions about this class of network cards. If you say Y, you
1286 will be asked for your specific card in the following questions. If
1287 you are unsure, say Y.
1290 tristate "AMD PCnet32 PCI support"
1291 depends on NET_PCI && PCI
1295 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1296 answer Y here and read the Ethernet-HOWTO, available from
1297 <http://www.tldp.org/docs.html#howto>.
1299 To compile this driver as a module, choose M here and read
1300 <file:Documentation/networking/net-modules.txt>. The module
1301 will be called pcnet32.
1304 bool "Use RX polling (NAPI) (EXPERIMENTAL)"
1305 depends on PCNET32 && EXPERIMENTAL
1307 NAPI is a new driver API designed to reduce CPU and interrupt load
1308 when the driver is receiving lots of packets from the card. It is
1309 still somewhat experimental and thus not yet enabled by default.
1311 If your estimated Rx load is 10kpps or more, or if the card will be
1312 deployed on potentially unfriendly networks (e.g. in a firewall),
1315 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1321 tristate "AMD 8111 (new PCI lance) support"
1322 depends on NET_PCI && PCI
1326 If you have an AMD 8111-based PCI lance ethernet card,
1327 answer Y here and read the Ethernet-HOWTO, available from
1328 <http://www.tldp.org/docs.html#howto>.
1330 To compile this driver as a module, choose M here and read
1331 <file:Documentation/networking/net-modules.txt>. The module
1332 will be called amd8111e.
1333 config AMD8111E_NAPI
1334 bool "Enable NAPI support"
1335 depends on AMD8111_ETH
1337 NAPI is a new driver API designed to reduce CPU and interrupt load
1338 when the driver is receiving lots of packets from the card. It is
1339 still somewhat experimental and thus not yet enabled by default.
1341 If your estimated Rx load is 10kpps or more, or if the card will be
1342 deployed on potentially unfriendly networks (e.g. in a firewall),
1345 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1350 config ADAPTEC_STARFIRE
1351 tristate "Adaptec Starfire/DuraLAN support"
1352 depends on NET_PCI && PCI
1356 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1357 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1358 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1361 To compile this driver as a module, choose M here: the module
1362 will be called starfire. This is recommended.
1364 config ADAPTEC_STARFIRE_NAPI
1365 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1366 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1368 NAPI is a new driver API designed to reduce CPU and interrupt load
1369 when the driver is receiving lots of packets from the card. It is
1370 still somewhat experimental and thus not yet enabled by default.
1372 If your estimated Rx load is 10kpps or more, or if the card will be
1373 deployed on potentially unfriendly networks (e.g. in a firewall),
1376 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1382 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1383 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1386 If you have a network (Ethernet) card of this type, say Y and read
1387 the Ethernet-HOWTO, available from
1388 <http://www.tldp.org/docs.html#howto>.
1390 To compile this driver as a module, choose M here and read
1391 <file:Documentation/networking/net-modules.txt>. The module
1392 will be called ac3200.
1395 tristate "Apricot Xen-II on board Ethernet"
1396 depends on NET_PCI && ISA
1398 If you have a network (Ethernet) controller of this type, say Y and
1399 read the Ethernet-HOWTO, available from
1400 <http://www.tldp.org/docs.html#howto>.
1402 To compile this driver as a module, choose M here and read
1403 <file:Documentation/networking/net-modules.txt>. The module will be
1407 tristate "Broadcom 4400 ethernet support"
1408 depends on NET_PCI && PCI
1411 If you have a network (Ethernet) controller of this type, say Y and
1412 read the Ethernet-HOWTO, available from
1413 <http://www.tldp.org/docs.html#howto>.
1415 To compile this driver as a module, choose M here and read
1416 <file:Documentation/networking/net-modules.txt>. The module will be
1420 tristate "nForce Ethernet support"
1421 depends on NET_PCI && PCI
1423 If you have a network (Ethernet) controller of this type, say Y and
1424 read the Ethernet-HOWTO, available from
1425 <http://www.tldp.org/docs.html#howto>.
1427 To compile this driver as a module, choose M here and read
1428 <file:Documentation/networking/net-modules.txt>. The module will be
1431 config FORCEDETH_NAPI
1432 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1433 depends on FORCEDETH && EXPERIMENTAL
1435 NAPI is a new driver API designed to reduce CPU and interrupt load
1436 when the driver is receiving lots of packets from the card. It is
1437 still somewhat experimental and thus not yet enabled by default.
1439 If your estimated Rx load is 10kpps or more, or if the card will be
1440 deployed on potentially unfriendly networks (e.g. in a firewall),
1443 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1449 tristate "CS89x0 support"
1450 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1452 Support for CS89x0 chipset based Ethernet cards. If you have a
1453 network (Ethernet) card of this type, say Y and read the
1454 Ethernet-HOWTO, available from
1455 <http://www.tldp.org/docs.html#howto> as well as
1456 <file:Documentation/networking/cs89x0.txt>.
1458 To compile this driver as a module, choose M here and read
1459 <file:Documentation/networking/net-modules.txt>. The module will be
1463 tristate "TOSHIBA TC35815 Ethernet support"
1464 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1467 tristate "Digi Intl. RightSwitch SE-X support"
1468 depends on NET_PCI && (PCI || EISA)
1470 This is support for the Digi International RightSwitch series of
1471 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1472 models. If you have a network card of this type, say Y and read the
1473 Ethernet-HOWTO, available from
1474 <http://www.tldp.org/docs.html#howto>. More specific
1475 information is contained in <file:Documentation/networking/dgrs.txt>.
1477 To compile this driver as a module, choose M here and read
1478 <file:Documentation/networking/net-modules.txt>. The module
1479 will be called dgrs.
1482 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1483 depends on NET_PCI && PCI
1486 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1487 card, say Y and read the Ethernet-HOWTO, available from
1488 <http://www.tldp.org/docs.html#howto>.
1490 To compile this driver as a module, choose M here and read
1491 <file:Documentation/networking/net-modules.txt>. The module
1492 will be called eepro100.
1496 tristate "Intel(R) PRO/100+ support"
1497 depends on NET_PCI && PCI
1500 This driver supports Intel(R) PRO/100 family of adapters.
1501 To verify that your adapter is supported, find the board ID number
1502 on the adapter. Look for a label that has a barcode and a number
1503 in the format 123456-001 (six digits hyphen three digits).
1505 Use the above information and the Adapter & Driver ID Guide at:
1507 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1509 to identify the adapter.
1511 For the latest Intel PRO/100 network driver for Linux, see:
1513 <http://appsr.intel.com/scripts-df/support_intel.asp>
1515 More specific information on configuring the driver is in
1516 <file:Documentation/networking/e100.txt>.
1518 To compile this driver as a module, choose M here and read
1519 <file:Documentation/networking/net-modules.txt>. The module
1520 will be called e100.
1523 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1524 depends on NET_PCI && EISA && EXPERIMENTAL
1527 If you have a network (Ethernet) card of this type, say Y and read
1528 the Ethernet-HOWTO, available from
1529 <http://www.tldp.org/docs.html#howto>.
1531 To compile this driver as a module, choose M here and read
1532 <file:Documentation/networking/net-modules.txt>. The module
1533 will be called lne390.
1536 tristate "Myson MTD-8xx PCI Ethernet support"
1537 depends on NET_PCI && PCI
1541 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1542 cards. Specifications and data at
1543 <http://www.myson.com.hk/mtd/datasheet/>.
1546 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1547 depends on NET_PCI && PCI
1550 This driver is for the National Semiconductor DP83810 series,
1551 which is used in cards from PureData, NetGear, Linksys
1552 and others, including the 83815 chip.
1553 More specific information and updates are available from
1554 <http://www.scyld.com/network/natsemi.html>.
1557 tristate "PCI NE2000 and clones support (see help)"
1558 depends on NET_PCI && PCI
1561 This driver is for NE2000 compatible PCI cards. It will not work
1562 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1563 support" below). If you have a PCI NE2000 network (Ethernet) card,
1564 say Y and read the Ethernet-HOWTO, available from
1565 <http://www.tldp.org/docs.html#howto>.
1567 This driver also works for the following NE2000 clone cards:
1568 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1569 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1570 Holtek HT80232 Holtek HT80229
1572 To compile this driver as a module, choose M here and read
1573 <file:Documentation/networking/net-modules.txt>. The module
1574 will be called ne2k-pci.
1577 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1578 depends on NET_PCI && EISA && EXPERIMENTAL
1581 If you have a network (Ethernet) card of this type, say Y and read
1582 the Ethernet-HOWTO, available from
1583 <http://www.tldp.org/docs.html#howto>. Note that this driver
1584 will NOT WORK for NE3200 cards as they are completely different.
1586 To compile this driver as a module, choose M here and read
1587 <file:Documentation/networking/net-modules.txt>. The module
1588 will be called ne3210.
1591 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1592 depends on NET_PCI && EISA && EXPERIMENTAL
1595 If you have a network (Ethernet) card of this type, say Y and read
1596 the Ethernet-HOWTO, available from
1597 <http://www.tldp.org/docs.html#howto>.
1599 To compile this driver as a module, choose M here and read
1600 <file:Documentation/networking/net-modules.txt>. The module
1601 will be called es3210.
1604 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1605 depends on NET_PCI && PCI && EXPERIMENTAL
1609 This is a driver for the Fast Ethernet PCI network cards based on
1610 the RTL8139C+ chips. If you have one of those, say Y and read
1611 the Ethernet-HOWTO, available from
1612 <http://www.tldp.org/docs.html#howto>.
1614 To compile this driver as a module, choose M here: the module
1615 will be called 8139cp. This is recommended.
1618 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1619 depends on NET_PCI && PCI
1623 This is a driver for the Fast Ethernet PCI network cards based on
1624 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1625 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1627 To compile this driver as a module, choose M here: the module
1628 will be called 8139too. This is recommended.
1631 bool "Use PIO instead of MMIO"
1635 This instructs the driver to use programmed I/O ports (PIO) instead
1636 of PCI shared memory (MMIO). This can possibly solve some problems
1637 in case your mainboard has memory consistency issues. If unsure,
1640 config 8139TOO_TUNE_TWISTER
1641 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1644 This implements a function which might come in handy in case you
1645 are using low quality on long cabling. It is required for RealTek
1646 RTL-8139 revision K boards, and totally unused otherwise. It tries
1647 to match the transceiver to the cable characteristics. This is
1648 experimental since hardly documented by the manufacturer.
1652 bool "Support for older RTL-8129/8130 boards"
1655 This enables support for the older and uncommon RTL-8129 and
1656 RTL-8130 chips, which support MII via an external transceiver,
1657 instead of an internal one. Disabling this option will save some
1658 memory by making the code size smaller. If unsure, say Y.
1660 config 8139_OLD_RX_RESET
1661 bool "Use older RX-reset method"
1664 The 8139too driver was recently updated to contain a more rapid
1665 reset sequence, in the face of severe receive errors. This "new"
1666 RX-reset method should be adequate for all boards. But if you
1667 experience problems, you can enable this option to restore the
1668 old RX-reset behavior. If unsure, say N.
1671 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1672 depends on NET_PCI && PCI
1676 This is a driver for the Fast Ethernet PCI network cards based on
1677 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1678 SiS 630 and SiS 540 chipsets.
1680 This driver also supports AMD 79C901 HomePNA so that you can use
1681 your phone line as a network cable.
1683 To compile this driver as a module, choose M here: the module
1684 will be called sis900. This is recommended.
1687 tristate "SMC EtherPower II"
1688 depends on NET_PCI && PCI
1692 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1693 which is based on the SMC83c17x (EPIC/100).
1694 More specific information and updates are available from
1695 <http://www.scyld.com/network/epic100.html>.
1698 tristate "Sundance Alta support"
1699 depends on NET_PCI && PCI
1703 This driver is for the Sundance "Alta" chip.
1704 More specific information and updates are available from
1705 <http://www.scyld.com/network/sundance.html>.
1707 config SUNDANCE_MMIO
1708 bool "Use MMIO instead of PIO"
1711 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1712 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1713 is known to solve bugs on certain chips.
1718 tristate "TI ThunderLAN support"
1719 depends on NET_PCI && (PCI || EISA) && !64BIT
1721 If you have a PCI Ethernet network card based on the ThunderLAN chip
1722 which is supported by this driver, say Y and read the
1723 Ethernet-HOWTO, available from
1724 <http://www.tldp.org/docs.html#howto>.
1726 Devices currently supported by this driver are Compaq Netelligent,
1727 Compaq NetFlex and Olicom cards. Please read the file
1728 <file:Documentation/networking/tlan.txt> for more details.
1730 To compile this driver as a module, choose M here and read
1731 <file:Documentation/networking/net-modules.txt>. The module
1732 will be called tlan.
1734 Please email feedback to <torben.mathiasen@compaq.com>.
1737 tristate "VIA Rhine support"
1738 depends on NET_PCI && PCI
1742 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1743 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1744 Ethernet functions can also be found integrated on South Bridges
1747 To compile this driver as a module, choose M here. The module
1748 will be called via-rhine.
1750 config VIA_RHINE_MMIO
1751 bool "Use MMIO instead of PIO"
1752 depends on VIA_RHINE
1754 This instructs the driver to use PCI shared memory (MMIO) instead of
1755 programmed I/O ports (PIO). Enabling this gives an improvement in
1756 processing time in parts of the driver.
1760 config VIA_RHINE_NAPI
1761 bool "Use Rx Polling (NAPI)"
1762 depends on VIA_RHINE
1764 NAPI is a new driver API designed to reduce CPU and interrupt load
1765 when the driver is receiving lots of packets from the card.
1767 If your estimated Rx load is 10kpps or more, or if the card will be
1768 deployed on potentially unfriendly networks (e.g. in a firewall),
1771 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1775 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1776 depends on NET_PCI && EXPERIMENTAL && MIPS
1778 The SAA9730 is a combined multimedia and peripheral controller used
1779 in thin clients, Internet access terminals, and diskless
1781 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1784 bool "Pocket and portable adapters"
1785 depends on NET_ETHERNET && PARPORT
1787 Cute little network (Ethernet) devices which attach to the parallel
1788 port ("pocket adapters"), commonly used with laptops. If you have
1789 one of those, say Y and read the Ethernet-HOWTO, available from
1790 <http://www.tldp.org/docs.html#howto>.
1792 If you want to plug a network (or some other) card into the PCMCIA
1793 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1794 credit card size extension cards used by all modern laptops), you
1795 need the pcmcia-cs package (location contained in the file
1796 <file:Documentation/Changes>) and you can say N here.
1798 Laptop users should read the Linux Laptop home page at
1799 <http://www.linux-on-laptops.com/> or
1800 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1802 Note that the answer to this question doesn't directly affect the
1803 kernel: saying N will just cause the configurator to skip all
1804 the questions about this class of network devices. If you say Y, you
1805 will be asked for your specific device in the following questions.
1808 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1809 depends on NET_POCKET && PARPORT && X86
1812 This is a network (Ethernet) device which attaches to your parallel
1813 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1814 available from <http://www.tldp.org/docs.html#howto>, if you
1815 want to use this. If you intend to use this driver, you should have
1816 said N to the "Parallel printer support", because the two drivers
1817 don't like each other.
1819 To compile this driver as a module, choose M here: the module
1823 tristate "D-Link DE600 pocket adapter support"
1824 depends on NET_POCKET && PARPORT
1826 This is a network (Ethernet) device which attaches to your parallel
1827 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1828 Ethernet-HOWTO, available from
1829 <http://www.tldp.org/docs.html#howto>, if you want to use
1830 this. It is possible to have several devices share a single parallel
1831 port and it is safe to compile the corresponding drivers into the
1834 To compile this driver as a module, choose M here: the module
1835 will be called de600.
1838 tristate "D-Link DE620 pocket adapter support"
1839 depends on NET_POCKET && PARPORT
1841 This is a network (Ethernet) device which attaches to your parallel
1842 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1843 Ethernet-HOWTO, available from
1844 <http://www.tldp.org/docs.html#howto>, if you want to use
1845 this. It is possible to have several devices share a single parallel
1846 port and it is safe to compile the corresponding drivers into the
1849 To compile this driver as a module, choose M here: the module
1850 will be called de620.
1853 tristate "SGI Seeq ethernet controller support"
1854 depends on NET_ETHERNET && SGI_IP22
1856 Say Y here if you have an Seeq based Ethernet network card. This is
1857 used in many Silicon Graphics machines.
1860 tristate "DEC LANCE ethernet controller support"
1861 depends on NET_ETHERNET && MACH_DECSTATION
1864 This driver is for the series of Ethernet controllers produced by
1865 DEC (now Compaq) based on the AMD Lance chipset, including the
1866 DEPCA series. (This chipset is better known via the NE2100 cards.)
1869 bool "Motorola 68360 ethernet controller"
1872 Say Y here if you want to use the built-in ethernet controller of
1873 the Motorola 68360 processor.
1876 bool "FEC ethernet controller (of ColdFire CPUs)"
1877 depends on M523x || M527x || M5272 || M528x || M520x
1879 Say Y here if you want to use the built-in 10/100 Fast ethernet
1880 controller on some Motorola ColdFire processors.
1883 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1886 Say Y here if you want to use the second built-in 10/100 Fast
1887 ethernet controller on some Motorola ColdFire processors.
1890 tristate "NE2000 compatible support for H8/300"
1891 depends on H8300 && NET_ETHERNET
1893 Say Y here if you want to use the NE2000 compatible
1894 controller on the Renesas H8/300 processor.
1896 source "drivers/net/fec_8xx/Kconfig"
1897 source "drivers/net/fs_enet/Kconfig"
1905 menu "Ethernet (1000 Mbit)"
1909 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1912 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1913 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1914 adapter. The driver allows for using the Jumbo Frame option (9000
1915 bytes/frame) however it requires that your switches can handle this
1916 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1919 To compile this driver as a module, choose M here: the
1920 module will be called acenic.
1922 config ACENIC_OMIT_TIGON_I
1923 bool "Omit support for old Tigon I based AceNICs"
1926 Say Y here if you only have Tigon II based AceNICs and want to leave
1927 out support for the older Tigon I based cards which are no longer
1928 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1929 version)). This will reduce the size of the driver object by
1930 app. 100KB. If you are not sure whether your card is a Tigon I or a
1931 Tigon II, say N here.
1933 The safe and default value for this is N.
1936 tristate "D-Link DL2000-based Gigabit Ethernet support"
1940 This driver supports D-Link 2000-based gigabit ethernet cards, which
1942 D-Link DGE-550T Gigabit Ethernet Adapter.
1943 D-Link DL2000-based Gigabit Ethernet Adapter.
1945 To compile this driver as a module, choose M here: the
1946 module will be called dl2k.
1949 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1952 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1953 adapters. For more information on how to identify your adapter, go
1954 to the Adapter & Driver ID Guide at:
1956 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1958 For general information and support, go to the Intel support
1961 <http://support.intel.com>
1963 More specific information on configuring the driver is in
1964 <file:Documentation/networking/e1000.txt>.
1966 To compile this driver as a module, choose M here and read
1967 <file:Documentation/networking/net-modules.txt>. The module
1968 will be called e1000.
1971 bool "Use Rx Polling (NAPI)"
1974 NAPI is a new driver API designed to reduce CPU and interrupt load
1975 when the driver is receiving lots of packets from the card. It is
1976 still somewhat experimental and thus not yet enabled by default.
1978 If your estimated Rx load is 10kpps or more, or if the card will be
1979 deployed on potentially unfriendly networks (e.g. in a firewall),
1982 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1987 config E1000_DISABLE_PACKET_SPLIT
1988 bool "Disable Packet Split for PCI express adapters"
1991 Say Y here if you want to use the legacy receive path for PCI express
1996 source "drivers/net/ixp2000/Kconfig"
1999 tristate "MyriCOM Gigabit Ethernet support"
2002 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2004 To compile this driver as a module, choose M here: the module
2005 will be called myri_sbus. This is recommended.
2008 tristate "National Semiconductor DP83820 support"
2011 This is a driver for the National Semiconductor DP83820 series
2012 of gigabit ethernet MACs. Cards using this chipset include
2013 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2014 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2018 tristate "Packet Engines Hamachi GNIC-II support"
2022 If you have a Gigabit Ethernet card of this type, say Y and read
2023 the Ethernet-HOWTO, available from
2024 <http://www.tldp.org/docs.html#howto>.
2026 To compile this driver as a module, choose M here and read
2027 <file:Documentation/networking/net-modules.txt>. The module will be
2031 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2032 depends on PCI && EXPERIMENTAL
2035 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2036 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2037 used by the Beowulf Linux cluster project. See
2038 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2039 information about this driver in particular and Beowulf in general.
2041 To compile this driver as a module, choose M here: the module
2042 will be called yellowfin. This is recommended.
2045 tristate "Realtek 8169 gigabit ethernet support"
2049 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2051 To compile this driver as a module, choose M here: the module
2052 will be called r8169. This is recommended.
2055 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2056 depends on R8169 && EXPERIMENTAL
2058 NAPI is a new driver API designed to reduce CPU and interrupt load
2059 when the driver is receiving lots of packets from the card. It is
2060 still somewhat experimental and thus not yet enabled by default.
2062 If your estimated Rx load is 10kpps or more, or if the card will be
2063 deployed on potentially unfriendly networks (e.g. in a firewall),
2066 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2073 depends on R8169 && VLAN_8021Q
2075 Say Y here for the r8169 driver to support the functions required
2076 by the kernel 802.1Q code.
2081 tristate "SiS190/SiS191 gigabit ethernet support"
2086 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2087 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2088 appear in lan on motherboard designs which are based on SiS 965
2089 and SiS 966 south bridge.
2091 To compile this driver as a module, choose M here: the module
2092 will be called sis190. This is recommended.
2095 tristate "New SysKonnect GigaEthernet support"
2099 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2100 and related Gigabit Ethernet adapters. It is a new smaller driver
2101 with better performance and more complete ethtool support.
2103 It does not support the link failover and network management
2104 features that "portable" vendor supplied sk98lin driver does.
2106 This driver supports adapters based on the original Yukon chipset:
2107 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2108 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2110 It does not support the newer Yukon2 chipset: a separate driver,
2111 sky2, is provided for Yukon2-based adapters.
2113 To compile this driver as a module, choose M here: the module
2114 will be called skge. This is recommended.
2117 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2118 depends on PCI && EXPERIMENTAL
2121 This driver supports Gigabit Ethernet adapters based on the the
2122 Marvell Yukon 2 chipset:
2123 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2124 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2126 This driver does not support the original Yukon chipset: a seperate
2127 driver, skge, is provided for Yukon-based adapters.
2129 To compile this driver as a module, choose M here: the module
2130 will be called sky2. This is recommended.
2133 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2136 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2137 compliant Gigabit Ethernet Adapter.
2139 This driver supports the original Yukon chipset. A cleaner driver is
2140 also available (skge) which seems to work better than this one.
2142 This driver does not support the newer Yukon2 chipset. A seperate
2143 driver, sky2, is provided to support Yukon2-based adapters.
2145 The following adapters are supported by this driver:
2146 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2147 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2148 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2149 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2150 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2151 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2152 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2153 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2154 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2155 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2156 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2157 - EG1032 v2 Instant Gigabit Network Adapter
2158 - EG1064 v2 Instant Gigabit Network Adapter
2159 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2160 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2161 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2162 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2163 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2164 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2165 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2166 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2167 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2168 - Marvell RDK-8001 Adapter
2169 - Marvell RDK-8002 Adapter
2170 - Marvell RDK-8003 Adapter
2171 - Marvell RDK-8004 Adapter
2172 - Marvell RDK-8006 Adapter
2173 - Marvell RDK-8007 Adapter
2174 - Marvell RDK-8008 Adapter
2175 - Marvell RDK-8009 Adapter
2176 - Marvell RDK-8010 Adapter
2177 - Marvell RDK-8011 Adapter
2178 - Marvell RDK-8012 Adapter
2179 - Marvell RDK-8052 Adapter
2180 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2181 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2182 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2183 - SK-9521 10/100/1000Base-T Adapter
2184 - SK-9521 V2.0 10/100/1000Base-T Adapter
2185 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2186 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2187 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2188 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2189 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2190 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2191 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2192 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2193 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2194 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2195 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2196 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2197 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2198 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2199 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2200 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2201 - SMC EZ Card 1000 (SMC9452TXV.2)
2203 The adapters support Jumbo Frames.
2204 The dual link adapters support link-failover and dual port features.
2205 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2206 the scatter-gather functionality with sendfile(). Please refer to
2207 <file:Documentation/networking/sk98lin.txt> for more information about
2208 optional driver parameters.
2209 Questions concerning this driver may be addressed to:
2210 <linux@syskonnect.de>
2212 If you want to compile this driver as a module ( = code which can be
2213 inserted in and removed from the running kernel whenever you want),
2214 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2215 be called sk98lin. This is recommended.
2218 tristate "VIA Velocity support"
2219 depends on NET_PCI && PCI
2224 If you have a VIA "Velocity" based network card say Y here.
2226 To compile this driver as a module, choose M here. The module
2227 will be called via-velocity.
2230 tristate "Broadcom Tigon3 support"
2233 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2235 To compile this driver as a module, choose M here: the module
2236 will be called tg3. This is recommended.
2239 tristate "Broadcom NetXtremeII support"
2244 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2246 To compile this driver as a module, choose M here: the module
2247 will be called bnx2. This is recommended.
2250 tristate "Spider Gigabit Ethernet driver"
2251 depends on PCI && PPC_IBM_CELL_BLADE
2254 This driver supports the Gigabit Ethernet chips present on the
2255 Cell Processor-Based Blades from IBM.
2258 tristate "Gianfar Ethernet"
2259 depends on 85xx || 83xx || PPC_86xx
2262 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2263 and MPC86xx family of chips, and the FEC on the 8540.
2270 tristate "Freescale QE UCC GETH"
2271 depends on QUICC_ENGINE && UCC_FAST
2273 This driver supports the Gigabit Ethernet mode of QE UCC.
2274 QE can be found on MPC836x CPUs.
2280 config UGETH_MAGIC_PACKET
2281 bool "Magic Packet detection support"
2284 config UGETH_FILTERING
2285 bool "Mac address filtering support"
2288 config UGETH_TX_ON_DEMOND
2289 bool "Transmit on Demond support"
2292 config UGETH_HAS_GIGA
2294 depends on UCC_GETH && MPC836x
2297 tristate "MV-643XX Ethernet support"
2298 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
2301 This driver supports the gigabit Ethernet on the Marvell MV643XX
2302 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2303 Pegasos II, amongst other PPC and MIPS boards.
2305 config MV643XX_ETH_0
2306 bool "MV-643XX Port 0"
2307 depends on MV643XX_ETH
2309 This enables support for Port 0 of the Marvell MV643XX Gigabit
2312 config MV643XX_ETH_1
2313 bool "MV-643XX Port 1"
2314 depends on MV643XX_ETH
2316 This enables support for Port 1 of the Marvell MV643XX Gigabit
2319 config MV643XX_ETH_2
2320 bool "MV-643XX Port 2"
2321 depends on MV643XX_ETH
2323 This enables support for Port 2 of the Marvell MV643XX Gigabit
2327 tristate "QLogic QLA3XXX Network Driver Support"
2330 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2332 To compile this driver as a module, choose M here: the module
2333 will be called qla3xxx.
2338 # 10 Gigabit Ethernet
2341 menu "Ethernet (10000 Mbit)"
2345 tristate "Chelsio 10Gb Ethernet support"
2348 This driver supports Chelsio N110 and N210 models 10Gb Ethernet
2349 cards. More information about adapter features and performance
2350 tuning is in <file:Documentation/networking/cxgb.txt>.
2352 For general information about Chelsio and our products, visit
2353 our website at <http://www.chelsio.com>.
2355 For customer support, please visit our customer support page at
2356 <http://www.chelsio.com/support.htm>.
2358 Please send feedback to <linux-bugs@chelsio.com>.
2360 To compile this driver as a module, choose M here: the module
2361 will be called cxgb.
2364 tristate "eHEA Ethernet support"
2367 This driver supports the IBM pSeries eHEA ethernet adapter.
2369 To compile the driver as a module, choose M here. The module
2370 will be called ehea.
2373 tristate "Intel(R) PRO/10GbE support"
2376 This driver supports Intel(R) PRO/10GbE family of
2377 adapters. For more information on how to identify your adapter, go
2378 to the Adapter & Driver ID Guide at:
2380 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2382 For general information and support, go to the Intel support
2385 <http://support.intel.com>
2387 More specific information on configuring the driver is in
2388 <file:Documentation/networking/ixgb.txt>.
2390 To compile this driver as a module, choose M here and read
2391 <file:Documentation/networking/net-modules.txt>. The module
2392 will be called ixgb.
2395 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2396 depends on IXGB && EXPERIMENTAL
2398 NAPI is a new driver API designed to reduce CPU and interrupt load
2399 when the driver is receiving lots of packets from the card. It is
2400 still somewhat experimental and thus not yet enabled by default.
2402 If your estimated Rx load is 10kpps or more, or if the card will be
2403 deployed on potentially unfriendly networks (e.g. in a firewall),
2406 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2412 tristate "S2IO 10Gbe XFrame NIC"
2415 This driver supports the 10Gbe XFrame NIC of S2IO.
2416 More specific information on configuring the driver is in
2417 <file:Documentation/networking/s2io.txt>.
2420 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2421 depends on S2IO && EXPERIMENTAL
2423 NAPI is a new driver API designed to reduce CPU and interrupt load
2424 when the driver is receiving lots of packets from the card. It is
2425 still somewhat experimental and thus not yet enabled by default.
2427 If your estimated Rx load is 10kpps or more, or if the card will be
2428 deployed on potentially unfriendly networks (e.g. in a firewall),
2431 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2437 tristate "Myricom Myri-10G Ethernet support"
2442 This driver supports Myricom Myri-10G Dual Protocol interface in
2443 Ethernet mode. If the eeprom on your board is not recent enough,
2444 you will need a newer firmware image.
2445 You may get this image or more information, at:
2447 <http://www.myri.com/scs/download-Myri10GE.html>
2449 To compile this driver as a module, choose M here and read
2450 <file:Documentation/networking/net-modules.txt>. The module
2451 will be called myri10ge.
2455 source "drivers/net/tokenring/Kconfig"
2457 source "drivers/net/wireless/Kconfig"
2459 source "drivers/net/pcmcia/Kconfig"
2461 source "drivers/net/wan/Kconfig"
2463 source "drivers/atm/Kconfig"
2465 source "drivers/s390/net/Kconfig"
2468 tristate "iSeries Virtual Ethernet driver support"
2469 depends on PPC_ISERIES
2472 tristate "RapidIO Ethernet over messaging driver support"
2473 depends on NETDEVICES && RAPIDIO
2475 config RIONET_TX_SIZE
2476 int "Number of outbound queue entries"
2480 config RIONET_RX_SIZE
2481 int "Number of inbound queue entries"
2486 bool "FDDI driver support"
2487 depends on (PCI || EISA)
2489 Fiber Distributed Data Interface is a high speed local area network
2490 design; essentially a replacement for high speed Ethernet. FDDI can
2491 run over copper or fiber. If you are connected to such a network and
2492 want a driver for the FDDI card in your computer, say Y here (and
2493 then also Y to the driver for your FDDI card, below). Most people
2497 tristate "Digital DEFEA and DEFPA adapter support"
2498 depends on FDDI && (PCI || EISA)
2500 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2501 (DEFPA) controllers which can connect you to a local FDDI network.
2504 tristate "SysKonnect FDDI PCI support"
2505 depends on FDDI && PCI
2507 Say Y here if you have a SysKonnect FDDI PCI adapter.
2508 The following adapters are supported by this driver:
2509 - SK-5521 (SK-NET FDDI-UP)
2510 - SK-5522 (SK-NET FDDI-UP DAS)
2511 - SK-5541 (SK-NET FDDI-FP)
2512 - SK-5543 (SK-NET FDDI-LP)
2513 - SK-5544 (SK-NET FDDI-LP DAS)
2514 - SK-5821 (SK-NET FDDI-UP64)
2515 - SK-5822 (SK-NET FDDI-UP64 DAS)
2516 - SK-5841 (SK-NET FDDI-FP64)
2517 - SK-5843 (SK-NET FDDI-LP64)
2518 - SK-5844 (SK-NET FDDI-LP64 DAS)
2519 - Netelligent 100 FDDI DAS Fibre SC
2520 - Netelligent 100 FDDI SAS Fibre SC
2521 - Netelligent 100 FDDI DAS UTP
2522 - Netelligent 100 FDDI SAS UTP
2523 - Netelligent 100 FDDI SAS Fibre MIC
2525 Read <file:Documentation/networking/skfp.txt> for information about
2528 Questions concerning this driver can be addressed to:
2529 <linux@syskonnect.de>
2531 To compile this driver as a module, choose M here: the module
2532 will be called skfp. This is recommended.
2535 bool "HIPPI driver support (EXPERIMENTAL)"
2536 depends on EXPERIMENTAL && INET && PCI
2538 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2539 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2540 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2541 single-mode). HIPPI networks are commonly used for clusters and to
2542 connect to super computers. If you are connected to a HIPPI network
2543 and have a HIPPI network card in your computer that you want to use
2544 under Linux, say Y here (you must also remember to enable the driver
2545 for your HIPPI card below). Most people will say N here.
2548 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2549 depends on HIPPI && PCI
2551 Say Y here if this is your PCI HIPPI network card.
2553 To compile this driver as a module, choose M here: the module
2554 will be called rrunner. If unsure, say N.
2556 config ROADRUNNER_LARGE_RINGS
2557 bool "Use large TX/RX rings (EXPERIMENTAL)"
2558 depends on ROADRUNNER
2560 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2561 of additional memory to allow for fastest operation, both for
2562 transmitting and receiving. This memory cannot be used by any other
2563 kernel code or by user space programs. Say Y here only if you have
2567 tristate "PLIP (parallel port) support"
2570 PLIP (Parallel Line Internet Protocol) is used to create a
2571 reasonably fast mini network consisting of two (or, rarely, more)
2572 local machines. A PLIP link from a Linux box is a popular means to
2573 install a Linux distribution on a machine which doesn't have a
2574 CD-ROM drive (a minimal system has to be transferred with floppies
2575 first). The kernels on both machines need to have this PLIP option
2576 enabled for this to work.
2578 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2579 ports (the connectors at the computers with 25 holes) are connected
2580 with "null printer" or "Turbo Laplink" cables which can transmit 4
2581 bits at a time (mode 0) or with special PLIP cables, to be used on
2582 bidirectional parallel ports only, which can transmit 8 bits at a
2583 time (mode 1); you can find the wiring of these cables in
2584 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2585 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2586 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2587 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2588 and winsock or NCSA's telnet.
2590 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2591 as the NET-3-HOWTO, both available from
2592 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2593 protocol has been changed and this PLIP driver won't work together
2594 with the PLIP support in Linux versions 1.0.x. This option enlarges
2595 your kernel by about 8 KB.
2597 To compile this driver as a module, choose M here and read
2598 <file:Documentation/networking/net-modules.txt>. The module will be
2599 called plip. If unsure, say Y or M, in case you buy a laptop
2603 tristate "PPP (point-to-point protocol) support"
2606 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2607 the same purpose: sending Internet traffic over telephone (and other
2608 serial) lines. Ask your access provider if they support it, because
2609 otherwise you can't use it; most Internet access providers these
2610 days support PPP rather than SLIP.
2612 To use PPP, you need an additional program called pppd as described
2613 in the PPP-HOWTO, available at
2614 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2615 the version of pppd recommended in <file:Documentation/Changes>.
2616 The PPP option enlarges your kernel by about 16 KB.
2618 There are actually two versions of PPP: the traditional PPP for
2619 asynchronous lines, such as regular analog phone lines, and
2620 synchronous PPP which can be used over digital ISDN lines for
2621 example. If you want to use PPP over phone lines or other
2622 asynchronous serial lines, you need to say Y (or M) here and also to
2623 the next option, "PPP support for async serial ports". For PPP over
2624 synchronous lines, you should say Y (or M) here and to "Support
2625 synchronous PPP", below.
2627 If you said Y to "Version information on all symbols" above, then
2628 you cannot compile the PPP driver into the kernel; you can then only
2629 compile it as a module. To compile this driver as a module, choose M
2630 here and read <file:Documentation/networking/net-modules.txt>.
2631 The module will be called ppp_generic.
2633 config PPP_MULTILINK
2634 bool "PPP multilink support (EXPERIMENTAL)"
2635 depends on PPP && EXPERIMENTAL
2637 PPP multilink is a protocol (defined in RFC 1990) which allows you
2638 to combine several (logical or physical) lines into one logical PPP
2639 connection, so that you can utilize your full bandwidth.
2641 This has to be supported at the other end as well and you need a
2642 version of the pppd daemon which understands the multilink protocol.
2647 bool "PPP filtering"
2650 Say Y here if you want to be able to filter the packets passing over
2651 PPP interfaces. This allows you to control which packets count as
2652 activity (i.e. which packets will reset the idle timer or bring up
2653 a demand-dialed link) and which packets are to be dropped entirely.
2654 You need to say Y here if you wish to use the pass-filter and
2655 active-filter options to pppd.
2660 tristate "PPP support for async serial ports"
2664 Say Y (or M) here if you want to be able to use PPP over standard
2665 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2666 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2669 To compile this driver as a module, choose M here.
2674 tristate "PPP support for sync tty ports"
2677 Say Y (or M) here if you want to be able to use PPP over synchronous
2678 (HDLC) tty devices, such as the SyncLink adapter. These devices
2679 are often used for high-speed leased lines like T1/E1.
2681 To compile this driver as a module, choose M here.
2684 tristate "PPP Deflate compression"
2689 Support for the Deflate compression method for PPP, which uses the
2690 Deflate algorithm (the same algorithm that gzip uses) to compress
2691 each PPP packet before it is sent over the wire. The machine at the
2692 other end of the PPP link (usually your ISP) has to support the
2693 Deflate compression method as well for this to be useful. Even if
2694 they don't support it, it is safe to say Y here.
2696 To compile this driver as a module, choose M here.
2699 tristate "PPP BSD-Compress compression"
2702 Support for the BSD-Compress compression method for PPP, which uses
2703 the LZW compression method to compress each PPP packet before it is
2704 sent over the wire. The machine at the other end of the PPP link
2705 (usually your ISP) has to support the BSD-Compress compression
2706 method as well for this to be useful. Even if they don't support it,
2707 it is safe to say Y here.
2709 The PPP Deflate compression method ("PPP Deflate compression",
2710 above) is preferable to BSD-Compress, because it compresses better
2713 Note that the BSD compression code will always be compiled as a
2714 module; it is called bsd_comp and will show up in the directory
2715 modules once you have said "make modules". If unsure, say N.
2718 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2719 depends on PPP && EXPERIMENTAL
2724 Support for the MPPE Encryption protocol, as employed by the
2725 Microsoft Point-to-Point Tunneling Protocol.
2727 See http://pptpclient.sourceforge.net/ for information on
2728 configuring PPTP clients and servers to utilize this method.
2731 tristate "PPP over Ethernet (EXPERIMENTAL)"
2732 depends on EXPERIMENTAL && PPP
2734 Support for PPP over Ethernet.
2736 This driver requires the latest version of pppd from the CVS
2737 repository at cvs.samba.org. Alternatively, see the
2738 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2739 which contains instruction on how to use this driver (under
2740 the heading "Kernel mode PPPoE").
2743 tristate "PPP over ATM"
2744 depends on ATM && PPP
2746 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2747 This implementation does not yet comply with section 8 of RFC2364,
2748 which can lead to bad results if the ATM peer loses state and
2749 changes its encapsulation unilaterally.
2752 tristate "SLIP (serial line) support"
2754 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2755 connect to your Internet service provider or to connect to some
2756 other local Unix box or if you want to configure your Linux box as a
2757 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2758 Internet Protocol) is a protocol used to send Internet traffic over
2759 serial connections such as telephone lines or null modem cables;
2760 nowadays, the protocol PPP is more commonly used for this same
2763 Normally, your access provider has to support SLIP in order for you
2764 to be able to use it, but there is now a SLIP emulator called SLiRP
2765 around (available from
2766 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2767 allows you to use SLIP over a regular dial up shell connection. If
2768 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2769 NET-3-HOWTO, available from
2770 <http://www.tldp.org/docs.html#howto>, explains how to
2771 configure SLIP. Note that you don't need this option if you just
2772 want to run term (term is a program which gives you almost full
2773 Internet connectivity if you have a regular dial up shell account on
2774 some Internet connected Unix computer. Read
2775 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2776 support will enlarge your kernel by about 4 KB. If unsure, say N.
2778 To compile this driver as a module, choose M here and read
2779 <file:Documentation/networking/net-modules.txt>. The module will be
2782 config SLIP_COMPRESSED
2783 bool "CSLIP compressed headers"
2787 This protocol is faster than SLIP because it uses compression on the
2788 TCP/IP headers (not on the data itself), but it has to be supported
2789 on both ends. Ask your access provider if you are not sure and
2790 answer Y, just in case. You will still be able to use plain SLIP. If
2791 you plan to use SLiRP, the SLIP emulator (available from
2792 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2793 allows you to use SLIP over a regular dial up shell connection, you
2794 definitely want to say Y here. The NET-3-HOWTO, available from
2795 <http://www.tldp.org/docs.html#howto>, explains how to configure
2796 CSLIP. This won't enlarge your kernel.
2801 This option enables Van Jacobsen serial line header compression
2805 bool "Keepalive and linefill"
2808 Adds additional capabilities to the SLIP driver to support the
2809 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2812 config SLIP_MODE_SLIP6
2813 bool "Six bit SLIP encapsulation"
2816 Just occasionally you may need to run IP over hostile serial
2817 networks that don't pass all control characters or are only seven
2818 bit. Saying Y here adds an extra mode you can use with SLIP:
2819 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2820 the serial device. Naturally, this has to be supported at the other
2821 end of the link as well. It's good enough, for example, to run IP
2822 over the async ports of a Camtec JNT Pad. If unsure, say N.
2825 bool "Fibre Channel driver support"
2826 depends on SCSI && PCI
2828 Fibre Channel is a high speed serial protocol mainly used to connect
2829 large storage devices to the computer; it is compatible with and
2830 intended to replace SCSI.
2832 If you intend to use Fibre Channel, you need to have a Fibre channel
2833 adaptor card in your computer; say Y here and to the driver for your
2834 adaptor below. You also should have said Y to "SCSI support" and
2835 "SCSI generic support".
2838 tristate "Traffic Shaper (EXPERIMENTAL)"
2839 depends on EXPERIMENTAL
2841 The traffic shaper is a virtual network device that allows you to
2842 limit the rate of outgoing data flow over some other network device.
2843 The traffic that you want to slow down can then be routed through
2844 these virtual devices. See
2845 <file:Documentation/networking/shaper.txt> for more information.
2847 An alternative to this traffic shaper is the experimental
2848 Class-Based Queuing (CBQ) scheduling support which you get if you
2849 say Y to "QoS and/or fair queuing" above.
2851 To compile this driver as a module, choose M here: the module
2852 will be called shaper. If unsure, say N.
2855 tristate "Network console logging support (EXPERIMENTAL)"
2856 depends on EXPERIMENTAL
2858 If you want to log kernel messages over the network, enable this.
2859 See <file:Documentation/networking/netconsole.txt> for details.
2865 bool "Netpoll support for trapping incoming packets"
2870 bool "Netpoll traffic trapping"
2874 config NET_POLL_CONTROLLER