3 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate 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 menuconfig NET_ETHERNET
152 bool "Ethernet (10 or 100Mbit)"
155 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
156 type of Local Area Network (LAN) in universities and companies.
158 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
159 coaxial cable, linking computers in a chain), 10BASE-T or twisted
160 pair (10 Mbps over twisted pair cable, linking computers to central
161 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
162 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
163 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
164 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
165 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
166 Ethernet (1 Gbps over optical fiber or short copper links).
168 If your Linux machine will be connected to an Ethernet and you have
169 an Ethernet network interface card (NIC) installed in your computer,
170 say Y here and read the Ethernet-HOWTO, available from
171 <http://www.tldp.org/docs.html#howto>. You will then also have
172 to say Y to the driver for your particular NIC.
174 Note that the answer to this question won't directly affect the
175 kernel: saying N will just cause the configurator to skip all
176 the questions about Ethernet network cards. If unsure, say N.
181 tristate "Generic Media Independent Interface device support"
183 Most ethernet controllers have MII transceiver either as an external
184 or internal device. It is safe to say Y or M here even if your
185 ethernet card lack MII.
188 tristate "Atmel MACB support"
189 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263
192 The Atmel MACB ethernet interface is found on many AT32 and AT91
193 parts. Say Y to include support for the MACB chip.
195 To compile this driver as a module, choose M here: the module
198 source "drivers/net/arm/Kconfig"
201 tristate "MACE (Power Mac ethernet) support"
202 depends on PPC_PMAC && PPC32
205 Power Macintoshes and clones with Ethernet built-in on the
206 motherboard will usually use a MACE (Medium Access Control for
207 Ethernet) interface. Say Y to include support for the MACE chip.
209 To compile this driver as a module, choose M here: the module
212 config MACE_AAUI_PORT
213 bool "Use AAUI port instead of TP by default"
216 Some Apple machines (notably the Apple Network Server) which use the
217 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
218 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
219 Y here if you have such a machine. If unsure, say N.
220 The driver will default to AAUI on ANS anyway, and if you use it as
221 a module, you can provide the port_aaui=0|1 to force the driver.
224 tristate "BMAC (G3 ethernet) support"
225 depends on PPC_PMAC && PPC32
228 Say Y for support of BMAC Ethernet interfaces. These are used on G3
231 To compile this driver as a module, choose M here: the module
235 tristate "Ariadne support"
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"
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"
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"
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 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"
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"
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"
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)"
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"
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"
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"
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"
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"
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 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 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 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"
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"
424 If you want to use the builtin "LANCE" Ethernet controller on an
425 HP300 machine, say Y here.
428 tristate "Lasi ethernet"
431 Say Y here to support the builtin Intel 82596 ethernet controller
432 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
435 tristate "SNI RM ethernet"
436 depends on NET_ETHERNET && SNI_RM
438 Say Y here to support the on-board Intel 82596 ethernet controller
439 built into SNI RM machines.
441 config MIPS_JAZZ_SONIC
442 tristate "MIPS JAZZ onboard SONIC Ethernet support"
445 This is the driver for the onboard card of MIPS Magnum 4000,
446 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
448 config MIPS_AU1X00_ENET
449 bool "MIPS AU1000 Ethernet support"
450 depends on SOC_AU1X00
454 If you have an Alchemy Semi AU1X00 based system
455 say Y. Otherwise, say N.
457 config NET_SB1250_MAC
458 tristate "SB1250 Ethernet support"
459 depends on SIBYTE_SB1xxx_SOC
462 bool "SGI IOC3 Ethernet"
463 depends on PCI && SGI_IP27
467 If you have a network (Ethernet) card of this type, say Y and read
468 the Ethernet-HOWTO, available from
469 <http://www.tldp.org/docs.html#howto>.
471 config SGI_IOC3_ETH_HW_RX_CSUM
472 bool "Receive hardware checksums"
473 depends on SGI_IOC3_ETH && INET
476 The SGI IOC3 network adapter supports TCP and UDP checksums in
477 hardware to offload processing of these checksums from the CPU. At
478 the moment only acceleration of IPv4 is supported. This option
479 enables offloading for checksums on receive. If unsure, say Y.
481 config SGI_IOC3_ETH_HW_TX_CSUM
482 bool "Transmit hardware checksums"
483 depends on SGI_IOC3_ETH && INET
486 The SGI IOC3 network adapter supports TCP and UDP checksums in
487 hardware to offload processing of these checksums from the CPU. At
488 the moment only acceleration of IPv4 is supported. This option
489 enables offloading for checksums on transmit. If unsure, say Y.
492 tristate "MIPS simulator Network device"
495 The MIPSNET device is a simple Ethernet network device which is
496 emulated by the MIPS Simulator.
497 If you are not using a MIPSsim or are unsure, say N.
499 config SGI_O2MACE_ETH
500 tristate "SGI O2 MACE Fast Ethernet support"
501 depends on SGI_IP32=y
504 tristate "National DP83902AV support"
508 Support for cards based on the National Semiconductor DP83902AV
509 ST-NIC Serial Network Interface Controller for Twisted Pair. This
510 is a 10Mbit/sec Ethernet controller. Product overview and specs at
511 <http://www.national.com/pf/DP/DP83902A.html>.
516 tristate "Sun LANCE support"
520 This driver supports the "le" interface present on all 32-bit Sparc
521 systems, on some older Ultra systems and as an Sbus option. These
522 cards are based on the AMD Lance chipset, which is better known
523 via the NE2100 cards.
525 To compile this driver as a module, choose M here: the module
526 will be called sunlance.
529 tristate "Sun Happy Meal 10/100baseT support"
530 depends on SBUS || PCI
533 This driver supports the "hme" interface present on most Ultra
534 systems and as an option on older Sbus systems. This driver supports
535 both PCI and Sbus devices. This driver also supports the "qfe" quad
536 100baseT device available in both PCI and Sbus configurations.
538 To compile this driver as a module, choose M here: the module
539 will be called sunhme.
542 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
543 depends on SBUS && EXPERIMENTAL
546 This driver supports the "be" interface available as an Sbus option.
547 This is Sun's older 100baseT Ethernet device.
549 To compile this driver as a module, choose M here: the module
550 will be called sunbmac.
553 tristate "Sun QuadEthernet support"
557 This driver supports the "qe" 10baseT Ethernet device, available as
558 an Sbus option. Note that this is not the same as Quad FastEthernet
559 "qfe" which is supported by the Happy Meal driver instead.
561 To compile this driver as a module, choose M here: the module
562 will be called sunqe.
565 tristate "Sun GEM support"
569 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
570 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
573 tristate "Sun Cassini support"
577 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
578 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
580 config NET_VENDOR_3COM
582 depends on ISA || EISA || MCA || PCI
584 If you have a network (Ethernet) card belonging to this class, say Y
585 and read the Ethernet-HOWTO, available from
586 <http://www.tldp.org/docs.html#howto>.
588 Note that the answer to this question doesn't directly affect the
589 kernel: saying N will just cause the configurator to skip all
590 the questions about 3COM cards. If you say Y, you will be asked for
591 your specific card in the following questions.
594 tristate "3c501 \"EtherLink\" support"
595 depends on NET_VENDOR_3COM && ISA
597 If you have a network (Ethernet) card of this type, say Y and read
598 the Ethernet-HOWTO, available from
599 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
600 new card, since the 3c501 is slow, broken, and obsolete: you will
601 have problems. Some people suggest to ping ("man ping") a nearby
602 machine every minute ("man cron") when using this card.
604 To compile this driver as a module, choose M here and read
605 <file:Documentation/networking/net-modules.txt>. The module
606 will be called 3c501.
609 tristate "3c503 \"EtherLink II\" support"
610 depends on NET_VENDOR_3COM && ISA
613 If you have a network (Ethernet) card of this type, say Y and read
614 the Ethernet-HOWTO, available from
615 <http://www.tldp.org/docs.html#howto>.
617 To compile this driver as a module, choose M here and read
618 <file:Documentation/networking/net-modules.txt>. The module
619 will be called 3c503.
622 tristate "3c505 \"EtherLink Plus\" support"
623 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
625 Information about this network (Ethernet) card can be found in
626 <file:Documentation/networking/3c505.txt>. If you have a card of
627 this type, say Y and read the Ethernet-HOWTO, available from
628 <http://www.tldp.org/docs.html#howto>.
630 To compile this driver as a module, choose M here and read
631 <file:Documentation/networking/net-modules.txt>. The module
632 will be called 3c505.
635 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
636 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
638 If you have a network (Ethernet) card of this type, say Y and read
639 the Ethernet-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>.
642 To compile this driver as a module, choose M here and read
643 <file:Documentation/networking/net-modules.txt>. The module
644 will be called 3c507.
647 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
648 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
650 If you have a network (Ethernet) card belonging to the 3Com
651 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
652 from <http://www.tldp.org/docs.html#howto>.
654 If your card is not working you may need to use the DOS
655 setup disk to disable Plug & Play mode, and to select the default
658 To compile this driver as a module, choose M here and read
659 <file:Documentation/networking/net-modules.txt>. The module
660 will be called 3c509.
663 tristate "3c515 ISA \"Fast EtherLink\""
664 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
666 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
667 network card, say Y and read the Ethernet-HOWTO, available from
668 <http://www.tldp.org/docs.html#howto>.
670 To compile this driver as a module, choose M here and read
671 <file:Documentation/networking/net-modules.txt>. The module
672 will be called 3c515.
675 tristate "3c523 \"EtherLink/MC\" support"
676 depends on NET_VENDOR_3COM && MCA_LEGACY
678 If you have a network (Ethernet) card of this type, say Y and read
679 the Ethernet-HOWTO, available from
680 <http://www.tldp.org/docs.html#howto>.
682 To compile this driver as a module, choose M here and read
683 <file:Documentation/networking/net-modules.txt>. The module
684 will be called 3c523.
687 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
688 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
690 If you have a network (Ethernet) card of this type, say Y and read
691 the Ethernet-HOWTO, available from
692 <http://www.tldp.org/docs.html#howto>.
694 To compile this driver as a module, choose M here and read
695 <file:Documentation/networking/net-modules.txt>. The module
696 will be called 3c527.
699 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
700 depends on NET_VENDOR_3COM && (PCI || EISA)
703 This option enables driver support for a large number of 10Mbps and
704 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
706 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
707 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
708 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
709 "Tornado" (3c905) PCI
710 "Hurricane" (3c555/3cSOHO) PCI
712 If you have such a card, say Y and read the Ethernet-HOWTO,
713 available from <http://www.tldp.org/docs.html#howto>. More
714 specific information is in
715 <file:Documentation/networking/vortex.txt> and in the comments at
716 the beginning of <file:drivers/net/3c59x.c>.
718 To compile this support as a module, choose M here and read
719 <file:Documentation/networking/net-modules.txt>.
722 tristate "3cr990 series \"Typhoon\" support"
723 depends on NET_VENDOR_3COM && PCI
726 This option enables driver support for the 3cr990 series of cards:
728 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
729 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
730 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
732 If you have a network (Ethernet) card of this type, say Y and read
733 the Ethernet-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
736 To compile this driver as a module, choose M here and read
737 <file:Documentation/networking/net-modules.txt>. The module
738 will be called typhoon.
741 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
742 depends on ISA && ISA_DMA_API
744 If you have a network (Ethernet) card of this type, say Y and read
745 the Ethernet-HOWTO, available from
746 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
749 To compile this driver as a module, choose M here: the module
750 will be called lance. This is recommended.
752 config NET_VENDOR_SMC
753 bool "Western Digital/SMC cards"
754 depends on ISA || MCA || EISA || MAC
756 If you have a network (Ethernet) card belonging to this class, say Y
757 and read the Ethernet-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>.
760 Note that the answer to this question doesn't directly affect the
761 kernel: saying N will just cause the configurator to skip all
762 the questions about Western Digital cards. If you say Y, you will be
763 asked for your specific card in the following questions.
766 tristate "WD80*3 support"
767 depends on NET_VENDOR_SMC && ISA
770 If you have a network (Ethernet) card of this type, say Y and read
771 the Ethernet-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>.
774 To compile this driver as a module, choose M here and read
775 <file:Documentation/networking/net-modules.txt>. The module
779 tristate "SMC Ultra MCA support"
780 depends on NET_VENDOR_SMC && MCA
783 If you have a network (Ethernet) card of this type and are running
784 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
785 available from <http://www.tldp.org/docs.html#howto>.
787 To compile this driver as a module, choose M here and read
788 <file:Documentation/networking/net-modules.txt>. The module
789 will be called smc-mca.
792 tristate "SMC Ultra support"
793 depends on NET_VENDOR_SMC && ISA
796 If you have a network (Ethernet) card of this type, say Y and read
797 the Ethernet-HOWTO, available from
798 <http://www.tldp.org/docs.html#howto>.
800 Important: There have been many reports that, with some motherboards
801 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
802 such as some BusLogic models) causes corruption problems with many
803 operating systems. The Linux smc-ultra driver has a work-around for
804 this but keep it in mind if you have such a SCSI card and have
807 To compile this driver as a module, choose M here and read
808 <file:Documentation/networking/net-modules.txt>. The module
809 will be called smc-ultra.
812 tristate "SMC Ultra32 EISA support"
813 depends on NET_VENDOR_SMC && EISA
816 If you have a network (Ethernet) card of this type, say Y and read
817 the Ethernet-HOWTO, available from
818 <http://www.tldp.org/docs.html#howto>.
820 To compile this driver as a module, choose M here and read
821 <file:Documentation/networking/net-modules.txt>. The module
822 will be called smc-ultra32.
825 tristate "SMC 9194 support"
826 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
829 This is support for the SMC9xxx based Ethernet cards. Choose this
830 option if you have a DELL laptop with the docking station, or
831 another SMC9192/9194 based chipset. Say Y if you want it compiled
832 into the kernel, and read the file
833 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
834 available from <http://www.tldp.org/docs.html#howto>.
836 To compile this driver as a module, choose M here and read
837 <file:Documentation/networking/net-modules.txt>. The module
838 will be called smc9194.
841 tristate "SMC 91C9x/91C1xxx support"
844 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
846 This is a driver for SMC's 91x series of Ethernet chipsets,
847 including the SMC91C94 and the SMC91C111. Say Y if you want it
848 compiled into the kernel, and read the file
849 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
850 available from <http://www.linuxdoc.org/docs.html#howto>.
852 This driver is also available as a module ( = code which can be
853 inserted in and removed from the running kernel whenever you want).
854 The module will be called smc91x. If you want to compile it as a
855 module, say M here and read <file:Documentation/kbuild/modules.txt>
856 as well as <file:Documentation/networking/net-modules.txt>.
859 tristate "NetX Ethernet support"
863 This is support for the Hilscher netX builtin Ethernet ports
865 To compile this driver as a module, choose M here and read
866 <file:Documentation/networking/net-modules.txt>. The module
867 will be called netx-eth.
870 tristate "DM9000 support"
871 depends on ARM || MIPS
875 Support for DM9000 chipset.
877 To compile this driver as a module, choose M here and read
878 <file:Documentation/networking/net-modules.txt>. The module will be
882 tristate "SMSC LAN911[5678] support"
887 This is a driver for SMSC's LAN911x series of Ethernet chipsets
888 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
889 Say Y if you want it compiled into the kernel,
890 and read the Ethernet-HOWTO, available from
891 <http://www.linuxdoc.org/docs.html#howto>.
893 This driver is also available as a module. The module will be
894 called smc911x. If you want to compile it as a module, say M
895 here and read <file:Documentation/kbuild/modules.txt>
897 config NET_VENDOR_RACAL
898 bool "Racal-Interlan (Micom) NI cards"
901 If you have a network (Ethernet) card belonging to this class, such
902 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
903 available from <http://www.tldp.org/docs.html#howto>.
905 Note that the answer to this question doesn't directly affect the
906 kernel: saying N will just cause the configurator to skip all
907 the questions about NI cards. If you say Y, you will be asked for
908 your specific card in the following questions.
911 tristate "NI5010 support (EXPERIMENTAL)"
912 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
914 If you have a network (Ethernet) card of this type, say Y and read
915 the Ethernet-HOWTO, available from
916 <http://www.tldp.org/docs.html#howto>. Note that this is still
919 To compile this driver as a module, choose M here and read
920 <file:Documentation/networking/net-modules.txt>. The module
921 will be called ni5010.
924 tristate "NI5210 support"
925 depends on NET_VENDOR_RACAL && ISA
927 If you have a network (Ethernet) card of this type, say Y and read
928 the Ethernet-HOWTO, available from
929 <http://www.tldp.org/docs.html#howto>.
931 To compile this driver as a module, choose M here and read
932 <file:Documentation/networking/net-modules.txt>. The module
936 tristate "NI6510 support"
937 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
939 If you have a network (Ethernet) card of this type, say Y and read
940 the Ethernet-HOWTO, available from
941 <http://www.tldp.org/docs.html#howto>.
943 To compile this driver as a module, choose M here and read
944 <file:Documentation/networking/net-modules.txt>. The module
947 source "drivers/net/tulip/Kconfig"
950 tristate "AT1700/1720 support (EXPERIMENTAL)"
951 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
954 If you have a network (Ethernet) card of this type, say Y and read
955 the Ethernet-HOWTO, available from
956 <http://www.tldp.org/docs.html#howto>.
958 To compile this driver as a module, choose M here and read
959 <file:Documentation/networking/net-modules.txt>. The module
960 will be called at1700.
963 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
964 depends on ISA || EISA || MCA
967 If you have a network (Ethernet) card of this type, say Y and read
968 the Ethernet-HOWTO, available from
969 <http://www.tldp.org/docs.html#howto> as well as
970 <file:drivers/net/depca.c>.
972 To compile this driver as a module, choose M here and read
973 <file:Documentation/networking/net-modules.txt>. The module
974 will be called depca.
977 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
978 depends on ISA || EISA || PCI
980 If you have a network (Ethernet) card of this type, say Y and read
981 the Ethernet-HOWTO, available from
982 <http://www.tldp.org/docs.html#howto>.
984 To compile this driver as a module, choose M here and read
985 <file:Documentation/networking/net-modules.txt>. The module
986 will be called hp100.
989 bool "Other ISA cards"
992 If your network (Ethernet) card hasn't been mentioned yet and its
993 bus system (that's the way the cards talks to the other components
994 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
995 Make sure you know the name of your card. Read the Ethernet-HOWTO,
996 available from <http://www.tldp.org/docs.html#howto>.
1000 Note that the answer to this question doesn't directly affect the
1001 kernel: saying N will just cause the configurator to skip all
1002 the remaining ISA network card questions. If you say Y, you will be
1003 asked for your specific card in the following questions.
1006 tristate "Cabletron E21xx support"
1010 If you have a network (Ethernet) card of this type, say Y and read
1011 the Ethernet-HOWTO, available from
1012 <http://www.tldp.org/docs.html#howto>.
1014 To compile this driver as a module, choose M here and read
1015 <file:Documentation/networking/net-modules.txt>. The module
1016 will be called e2100.
1019 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1023 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1024 cards. If this is for you, say Y and read
1025 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1026 well as the Ethernet-HOWTO, available from
1027 <http://www.tldp.org/docs.html#howto>.
1029 To compile this driver as a module, choose M here and read
1030 <file:Documentation/networking/net-modules.txt>. The module
1031 will be called ewrk3.
1034 tristate "EtherExpress 16 support"
1037 If you have an EtherExpress16 network (Ethernet) card, say Y and
1038 read the Ethernet-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1040 EtherExpress16 card used to be regarded as a very poor choice
1041 because the driver was very unreliable. We now have a new driver
1042 that should do better.
1044 To compile this driver as a module, choose M here and read
1045 <file:Documentation/networking/net-modules.txt>. The module
1046 will be called eexpress.
1049 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1052 If you have a network (Ethernet) card of this type, say Y. This
1053 driver supports Intel i82595{FX,TX} based boards. Note however
1054 that the EtherExpress PRO/100 Ethernet card has its own separate
1055 driver. Please read the Ethernet-HOWTO, available from
1056 <http://www.tldp.org/docs.html#howto>.
1058 To compile this driver as a module, choose M here and read
1059 <file:Documentation/networking/net-modules.txt>. The module
1060 will be called eepro.
1063 tristate "HP PCLAN+ (27247B and 27252A) support"
1067 If you have a network (Ethernet) card of this type, say Y and read
1068 the Ethernet-HOWTO, available from
1069 <http://www.tldp.org/docs.html#howto>.
1071 To compile this driver as a module, choose M here and read
1072 <file:Documentation/networking/net-modules.txt>. The module
1073 will be called hp-plus.
1076 tristate "HP PCLAN (27245 and other 27xxx series) support"
1080 If you have a network (Ethernet) card of this type, say Y and read
1081 the Ethernet-HOWTO, available from
1082 <http://www.tldp.org/docs.html#howto>.
1084 To compile this driver as a module, choose M here and read
1085 <file:Documentation/networking/net-modules.txt>. The module
1089 tristate "LP486E on board Ethernet"
1092 Say Y here to support the 82596-based on-board Ethernet controller
1093 for the Panther motherboard, which is one of the two shipped in the
1094 Intel Professional Workstation.
1097 tristate "ICL EtherTeam 16i/32 support"
1100 If you have a network (Ethernet) card of this type, say Y and read
1101 the Ethernet-HOWTO, available from
1102 <http://www.tldp.org/docs.html#howto>.
1104 To compile this driver as a module, choose M here and read
1105 <file:Documentation/networking/net-modules.txt>. The module
1106 will be called eth16i.
1109 tristate "NE2000/NE1000 support"
1110 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1113 If you have a network (Ethernet) card of this type, say Y and read
1114 the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1116 without a specific driver are compatible with NE2000.
1118 If you have a PCI NE2000 card however, say N here and Y to "PCI
1119 NE2000 and clone support" under "EISA, VLB, PCI and on board
1120 controllers" below. If you have a NE2000 card and are running on
1121 an MCA system (a bus system used on some IBM PS/2 computers and
1122 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1125 To compile this driver as a module, choose M here and read
1126 <file:Documentation/networking/net-modules.txt>. The module
1130 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1131 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1133 The Zenith Z-Note notebook computer has a built-in network
1134 (Ethernet) card, and this is the Linux driver for it. Note that the
1135 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1136 by this driver. Read the Ethernet-HOWTO, available from
1137 <http://www.tldp.org/docs.html#howto>.
1140 tristate "SEEQ8005 support (EXPERIMENTAL)"
1141 depends on NET_ISA && EXPERIMENTAL
1143 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1144 is for you, read the Ethernet-HOWTO, available from
1145 <http://www.tldp.org/docs.html#howto>.
1147 To compile this driver as a module, choose M here and read
1148 <file:Documentation/networking/net-modules.txt>. The module
1149 will be called seeq8005.
1152 tristate "NE/2 (ne2000 MCA version) support"
1153 depends on MCA_LEGACY
1156 If you have a network (Ethernet) card of this type, say Y and read
1157 the Ethernet-HOWTO, available from
1158 <http://www.tldp.org/docs.html#howto>.
1160 To compile this driver as a module, choose M here and read
1161 <file:Documentation/networking/net-modules.txt>. The module
1165 tristate "IBM LAN Adapter/A support"
1166 depends on MCA && MCA_LEGACY
1168 This is a Micro Channel Ethernet adapter. You need to set
1169 CONFIG_MCA to use this driver. It is both available as an in-kernel
1170 driver and as a module.
1172 To compile this driver as a module, choose M here and read
1173 <file:Documentation/networking/net-modules.txt>. The only
1174 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1175 will both support 16K and 32K memory windows, however a 32K window
1176 gives a better security against packet losses. Usage of multiple
1177 boards with this driver should be possible, but has not been tested
1178 up to now due to lack of hardware.
1181 tristate "IBM LAN Virtual Ethernet support"
1182 depends on PPC_PSERIES
1184 This driver supports virtual ethernet adapters on newer IBM iSeries
1185 and pSeries systems.
1187 To compile this driver as a module, choose M here and read
1188 <file:Documentation/networking/net-modules.txt>. The module will
1192 tristate "PowerPC 4xx on-chip Ethernet support"
1193 depends on 4xx && !PPC_MERGE
1195 This driver supports the PowerPC 4xx EMAC family of on-chip
1196 Ethernet controllers.
1199 int "Number of receive buffers"
1204 int "Number of transmit buffers"
1208 config IBM_EMAC_POLL_WEIGHT
1209 int "MAL NAPI polling weight"
1213 config IBM_EMAC_RX_COPY_THRESHOLD
1214 int "RX skb copy threshold (bytes)"
1218 config IBM_EMAC_RX_SKB_HEADROOM
1219 int "Additional RX skb headroom (bytes)"
1223 Additional receive skb headroom. Note, that driver
1224 will always reserve at least 2 bytes to make IP header
1225 aligned, so usually there is no need to add any additional
1228 If unsure, set to 0.
1230 config IBM_EMAC_PHY_RX_CLK_FIX
1231 bool "PHY Rx clock workaround"
1232 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1234 Enable this if EMAC attached to a PHY which doesn't generate
1235 RX clock if there is no link, if this is the case, you will
1236 see "TX disable timeout" or "RX disable timeout" in the system
1241 config IBM_EMAC_DEBUG
1246 config IBM_EMAC_ZMII
1248 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1251 config IBM_EMAC_RGMII
1253 depends on IBM_EMAC && 440GX
1258 depends on IBM_EMAC && 440GX
1262 bool "EISA, VLB, PCI and on board controllers"
1263 depends on ISA || EISA || PCI
1265 This is another class of network cards which attach directly to the
1266 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1267 available from <http://www.tldp.org/docs.html#howto>.
1269 Note that the answer to this question doesn't directly affect the
1270 kernel: saying N will just cause the configurator to skip all
1271 the questions about this class of network cards. If you say Y, you
1272 will be asked for your specific card in the following questions. If
1273 you are unsure, say Y.
1276 tristate "AMD PCnet32 PCI support"
1277 depends on NET_PCI && PCI
1281 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1282 answer Y here and read the Ethernet-HOWTO, available from
1283 <http://www.tldp.org/docs.html#howto>.
1285 To compile this driver as a module, choose M here and read
1286 <file:Documentation/networking/net-modules.txt>. The module
1287 will be called pcnet32.
1290 bool "Use RX polling (NAPI)"
1293 NAPI is a new driver API designed to reduce CPU and interrupt load
1294 when the driver is receiving lots of packets from the card. It is
1295 still somewhat experimental and thus not yet enabled by default.
1297 If your estimated Rx load is 10kpps or more, or if the card will be
1298 deployed on potentially unfriendly networks (e.g. in a firewall),
1301 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1307 tristate "AMD 8111 (new PCI lance) support"
1308 depends on NET_PCI && PCI
1312 If you have an AMD 8111-based PCI lance ethernet card,
1313 answer Y here and read the Ethernet-HOWTO, available from
1314 <http://www.tldp.org/docs.html#howto>.
1316 To compile this driver as a module, choose M here and read
1317 <file:Documentation/networking/net-modules.txt>. The module
1318 will be called amd8111e.
1320 config AMD8111E_NAPI
1321 bool "Enable NAPI support"
1322 depends on AMD8111_ETH
1324 NAPI is a new driver API designed to reduce CPU and interrupt load
1325 when the driver is receiving lots of packets from the card. It is
1326 still somewhat experimental and thus not yet enabled by default.
1328 If your estimated Rx load is 10kpps or more, or if the card will be
1329 deployed on potentially unfriendly networks (e.g. in a firewall),
1332 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1337 config ADAPTEC_STARFIRE
1338 tristate "Adaptec Starfire/DuraLAN support"
1339 depends on NET_PCI && PCI
1343 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1344 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1345 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1348 To compile this driver as a module, choose M here: the module
1349 will be called starfire. This is recommended.
1351 config ADAPTEC_STARFIRE_NAPI
1352 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1353 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1355 NAPI is a new driver API designed to reduce CPU and interrupt load
1356 when the driver is receiving lots of packets from the card. It is
1357 still somewhat experimental and thus not yet enabled by default.
1359 If your estimated Rx load is 10kpps or more, or if the card will be
1360 deployed on potentially unfriendly networks (e.g. in a firewall),
1363 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1369 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1370 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1373 If you have a network (Ethernet) card of this type, say Y and read
1374 the Ethernet-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>.
1377 To compile this driver as a module, choose M here and read
1378 <file:Documentation/networking/net-modules.txt>. The module
1379 will be called ac3200.
1382 tristate "Apricot Xen-II on board Ethernet"
1383 depends on NET_PCI && ISA
1385 If you have a network (Ethernet) controller of this type, say Y and
1386 read the Ethernet-HOWTO, available from
1387 <http://www.tldp.org/docs.html#howto>.
1389 To compile this driver as a module, choose M here and read
1390 <file:Documentation/networking/net-modules.txt>. The module will be
1394 tristate "Broadcom 4400 ethernet support"
1395 depends on NET_PCI && PCI
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 "nForce Ethernet support"
1408 depends on NET_PCI && PCI
1410 If you have a network (Ethernet) controller of this type, say Y and
1411 read the Ethernet-HOWTO, available from
1412 <http://www.tldp.org/docs.html#howto>.
1414 To compile this driver as a module, choose M here and read
1415 <file:Documentation/networking/net-modules.txt>. The module will be
1418 config FORCEDETH_NAPI
1419 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1420 depends on FORCEDETH && EXPERIMENTAL
1422 NAPI is a new driver API designed to reduce CPU and interrupt load
1423 when the driver is receiving lots of packets from the card. It is
1424 still somewhat experimental and thus not yet enabled by default.
1426 If your estimated Rx load is 10kpps or more, or if the card will be
1427 deployed on potentially unfriendly networks (e.g. in a firewall),
1430 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1436 tristate "CS89x0 support"
1437 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1439 Support for CS89x0 chipset based Ethernet cards. If you have a
1440 network (Ethernet) card of this type, say Y and read the
1441 Ethernet-HOWTO, available from
1442 <http://www.tldp.org/docs.html#howto> as well as
1443 <file:Documentation/networking/cs89x0.txt>.
1445 To compile this driver as a module, choose M here and read
1446 <file:Documentation/networking/net-modules.txt>. The module will be
1450 tristate "TOSHIBA TC35815 Ethernet support"
1451 depends on NET_PCI && PCI && MIPS
1455 tristate "Digi Intl. RightSwitch SE-X support"
1456 depends on NET_PCI && (PCI || EISA)
1458 This is support for the Digi International RightSwitch series of
1459 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1460 models. If you have a network card of this type, say Y and read the
1461 Ethernet-HOWTO, available from
1462 <http://www.tldp.org/docs.html#howto>. More specific
1463 information is contained in <file:Documentation/networking/dgrs.txt>.
1465 To compile this driver as a module, choose M here and read
1466 <file:Documentation/networking/net-modules.txt>. The module
1467 will be called dgrs.
1470 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1471 depends on NET_PCI && PCI
1474 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1475 card, say Y and read the Ethernet-HOWTO, available from
1476 <http://www.tldp.org/docs.html#howto>.
1478 To compile this driver as a module, choose M here and read
1479 <file:Documentation/networking/net-modules.txt>. The module
1480 will be called eepro100.
1484 tristate "Intel(R) PRO/100+ support"
1485 depends on NET_PCI && PCI
1488 This driver supports Intel(R) PRO/100 family of adapters.
1489 To verify that your adapter is supported, find the board ID number
1490 on the adapter. Look for a label that has a barcode and a number
1491 in the format 123456-001 (six digits hyphen three digits).
1493 Use the above information and the Adapter & Driver ID Guide at:
1495 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1497 to identify the adapter.
1499 For the latest Intel PRO/100 network driver for Linux, see:
1501 <http://appsr.intel.com/scripts-df/support_intel.asp>
1503 More specific information on configuring the driver is in
1504 <file:Documentation/networking/e100.txt>.
1506 To compile this driver as a module, choose M here and read
1507 <file:Documentation/networking/net-modules.txt>. The module
1508 will be called e100.
1511 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1512 depends on NET_PCI && EISA && EXPERIMENTAL
1515 If you have a network (Ethernet) card of this type, say Y and read
1516 the Ethernet-HOWTO, available from
1517 <http://www.tldp.org/docs.html#howto>.
1519 To compile this driver as a module, choose M here and read
1520 <file:Documentation/networking/net-modules.txt>. The module
1521 will be called lne390.
1524 tristate "Myson MTD-8xx PCI Ethernet support"
1525 depends on NET_PCI && PCI
1529 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1530 cards. Specifications and data at
1531 <http://www.myson.com.hk/mtd/datasheet/>.
1534 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1535 depends on NET_PCI && PCI
1538 This driver is for the National Semiconductor DP83810 series,
1539 which is used in cards from PureData, NetGear, Linksys
1540 and others, including the 83815 chip.
1541 More specific information and updates are available from
1542 <http://www.scyld.com/network/natsemi.html>.
1545 tristate "PCI NE2000 and clones support (see help)"
1546 depends on NET_PCI && PCI
1549 This driver is for NE2000 compatible PCI cards. It will not work
1550 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1551 support" below). If you have a PCI NE2000 network (Ethernet) card,
1552 say Y and read the Ethernet-HOWTO, available from
1553 <http://www.tldp.org/docs.html#howto>.
1555 This driver also works for the following NE2000 clone cards:
1556 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1557 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1558 Holtek HT80232 Holtek HT80229
1560 To compile this driver as a module, choose M here and read
1561 <file:Documentation/networking/net-modules.txt>. The module
1562 will be called ne2k-pci.
1565 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1566 depends on NET_PCI && EISA && EXPERIMENTAL
1569 If you have a network (Ethernet) card of this type, say Y and read
1570 the Ethernet-HOWTO, available from
1571 <http://www.tldp.org/docs.html#howto>. Note that this driver
1572 will NOT WORK for NE3200 cards as they are completely different.
1574 To compile this driver as a module, choose M here and read
1575 <file:Documentation/networking/net-modules.txt>. The module
1576 will be called ne3210.
1579 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1580 depends on NET_PCI && EISA && EXPERIMENTAL
1583 If you have a network (Ethernet) card of this type, say Y and read
1584 the Ethernet-HOWTO, available from
1585 <http://www.tldp.org/docs.html#howto>.
1587 To compile this driver as a module, choose M here and read
1588 <file:Documentation/networking/net-modules.txt>. The module
1589 will be called es3210.
1592 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1593 depends on NET_PCI && PCI && EXPERIMENTAL
1597 This is a driver for the Fast Ethernet PCI network cards based on
1598 the RTL8139C+ chips. If you have one of those, say Y and read
1599 the Ethernet-HOWTO, available from
1600 <http://www.tldp.org/docs.html#howto>.
1602 To compile this driver as a module, choose M here: the module
1603 will be called 8139cp. This is recommended.
1606 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1607 depends on NET_PCI && PCI
1611 This is a driver for the Fast Ethernet PCI network cards based on
1612 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1613 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1615 To compile this driver as a module, choose M here: the module
1616 will be called 8139too. This is recommended.
1619 bool "Use PIO instead of MMIO"
1623 This instructs the driver to use programmed I/O ports (PIO) instead
1624 of PCI shared memory (MMIO). This can possibly solve some problems
1625 in case your mainboard has memory consistency issues. If unsure,
1628 config 8139TOO_TUNE_TWISTER
1629 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1632 This implements a function which might come in handy in case you
1633 are using low quality on long cabling. It is required for RealTek
1634 RTL-8139 revision K boards, and totally unused otherwise. It tries
1635 to match the transceiver to the cable characteristics. This is
1636 experimental since hardly documented by the manufacturer.
1640 bool "Support for older RTL-8129/8130 boards"
1643 This enables support for the older and uncommon RTL-8129 and
1644 RTL-8130 chips, which support MII via an external transceiver,
1645 instead of an internal one. Disabling this option will save some
1646 memory by making the code size smaller. If unsure, say Y.
1648 config 8139_OLD_RX_RESET
1649 bool "Use older RX-reset method"
1652 The 8139too driver was recently updated to contain a more rapid
1653 reset sequence, in the face of severe receive errors. This "new"
1654 RX-reset method should be adequate for all boards. But if you
1655 experience problems, you can enable this option to restore the
1656 old RX-reset behavior. If unsure, say N.
1659 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1660 depends on NET_PCI && PCI
1664 This is a driver for the Fast Ethernet PCI network cards based on
1665 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1666 SiS 630 and SiS 540 chipsets.
1668 This driver also supports AMD 79C901 HomePNA so that you can use
1669 your phone line as a network cable.
1671 To compile this driver as a module, choose M here: the module
1672 will be called sis900. This is recommended.
1675 tristate "SMC EtherPower II"
1676 depends on NET_PCI && PCI
1680 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1681 which is based on the SMC83c17x (EPIC/100).
1682 More specific information and updates are available from
1683 <http://www.scyld.com/network/epic100.html>.
1686 tristate "Sundance Alta support"
1687 depends on NET_PCI && PCI
1691 This driver is for the Sundance "Alta" chip.
1692 More specific information and updates are available from
1693 <http://www.scyld.com/network/sundance.html>.
1695 config SUNDANCE_MMIO
1696 bool "Use MMIO instead of PIO"
1699 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1700 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1701 is known to solve bugs on certain chips.
1706 tristate "TI ThunderLAN support"
1707 depends on NET_PCI && (PCI || EISA) && !64BIT
1709 If you have a PCI Ethernet network card based on the ThunderLAN chip
1710 which is supported by this driver, say Y and read the
1711 Ethernet-HOWTO, available from
1712 <http://www.tldp.org/docs.html#howto>.
1714 Devices currently supported by this driver are Compaq Netelligent,
1715 Compaq NetFlex and Olicom cards. Please read the file
1716 <file:Documentation/networking/tlan.txt> for more details.
1718 To compile this driver as a module, choose M here and read
1719 <file:Documentation/networking/net-modules.txt>. The module
1720 will be called tlan.
1722 Please email feedback to <torben.mathiasen@compaq.com>.
1725 tristate "VIA Rhine support"
1726 depends on NET_PCI && PCI
1730 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1731 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1732 Ethernet functions can also be found integrated on South Bridges
1735 To compile this driver as a module, choose M here. The module
1736 will be called via-rhine.
1738 config VIA_RHINE_MMIO
1739 bool "Use MMIO instead of PIO"
1740 depends on VIA_RHINE
1742 This instructs the driver to use PCI shared memory (MMIO) instead of
1743 programmed I/O ports (PIO). Enabling this gives an improvement in
1744 processing time in parts of the driver.
1748 config VIA_RHINE_NAPI
1749 bool "Use Rx Polling (NAPI)"
1750 depends on VIA_RHINE
1752 NAPI is a new driver API designed to reduce CPU and interrupt load
1753 when the driver is receiving lots of packets from the card.
1755 If your estimated Rx load is 10kpps or more, or if the card will be
1756 deployed on potentially unfriendly networks (e.g. in a firewall),
1759 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1763 bool "Philips SAA9730 Ethernet support"
1764 depends on NET_PCI && PCI && MIPS_ATLAS
1766 The SAA9730 is a combined multimedia and peripheral controller used
1767 in thin clients, Internet access terminals, and diskless
1769 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1772 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1773 depends on NET_PCI && PCI && EXPERIMENTAL
1776 This is a driver for the Fast Ethernet PCI network cards based on
1777 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1778 have one of these, say Y here.
1780 To compile this driver as a module, choose M here: the module
1781 will be called sc92031. This is recommended.
1784 bool "Pocket and portable adapters"
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"
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 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"
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"
1899 endif # NET_ETHERNET
1905 menuconfig NETDEV_1000
1906 bool "Ethernet (1000 Mbit)"
1913 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1916 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1917 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1918 adapter. The driver allows for using the Jumbo Frame option (9000
1919 bytes/frame) however it requires that your switches can handle this
1920 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1923 To compile this driver as a module, choose M here: the
1924 module will be called acenic.
1926 config ACENIC_OMIT_TIGON_I
1927 bool "Omit support for old Tigon I based AceNICs"
1930 Say Y here if you only have Tigon II based AceNICs and want to leave
1931 out support for the older Tigon I based cards which are no longer
1932 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1933 version)). This will reduce the size of the driver object by
1934 app. 100KB. If you are not sure whether your card is a Tigon I or a
1935 Tigon II, say N here.
1937 The safe and default value for this is N.
1940 tristate "D-Link DL2000-based Gigabit Ethernet support"
1944 This driver supports D-Link 2000-based gigabit ethernet cards, which
1946 D-Link DGE-550T Gigabit Ethernet Adapter.
1947 D-Link DL2000-based Gigabit Ethernet Adapter.
1949 To compile this driver as a module, choose M here: the
1950 module will be called dl2k.
1953 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1956 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1957 adapters. For more information on how to identify your adapter, go
1958 to the Adapter & Driver ID Guide at:
1960 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1962 For general information and support, go to the Intel support
1965 <http://support.intel.com>
1967 More specific information on configuring the driver is in
1968 <file:Documentation/networking/e1000.txt>.
1970 To compile this driver as a module, choose M here and read
1971 <file:Documentation/networking/net-modules.txt>. The module
1972 will be called e1000.
1975 bool "Use Rx Polling (NAPI)"
1978 NAPI is a new driver API designed to reduce CPU and interrupt load
1979 when the driver is receiving lots of packets from the card. It is
1980 still somewhat experimental and thus not yet enabled by default.
1982 If your estimated Rx load is 10kpps or more, or if the card will be
1983 deployed on potentially unfriendly networks (e.g. in a firewall),
1986 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1991 config E1000_DISABLE_PACKET_SPLIT
1992 bool "Disable Packet Split for PCI express adapters"
1995 Say Y here if you want to use the legacy receive path for PCI express
2000 source "drivers/net/ixp2000/Kconfig"
2003 tristate "MyriCOM Gigabit Ethernet support"
2006 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2008 To compile this driver as a module, choose M here: the module
2009 will be called myri_sbus. This is recommended.
2012 tristate "National Semiconductor DP83820 support"
2015 This is a driver for the National Semiconductor DP83820 series
2016 of gigabit ethernet MACs. Cards using this chipset include
2017 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2018 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2022 tristate "Packet Engines Hamachi GNIC-II support"
2026 If you have a Gigabit Ethernet card of this type, say Y and read
2027 the Ethernet-HOWTO, available from
2028 <http://www.tldp.org/docs.html#howto>.
2030 To compile this driver as a module, choose M here and read
2031 <file:Documentation/networking/net-modules.txt>. The module will be
2035 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2036 depends on PCI && EXPERIMENTAL
2039 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2040 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2041 used by the Beowulf Linux cluster project. See
2042 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2043 information about this driver in particular and Beowulf in general.
2045 To compile this driver as a module, choose M here: the module
2046 will be called yellowfin. This is recommended.
2049 tristate "Realtek 8169 gigabit ethernet support"
2053 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2055 To compile this driver as a module, choose M here: the module
2056 will be called r8169. This is recommended.
2059 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2060 depends on R8169 && EXPERIMENTAL
2062 NAPI is a new driver API designed to reduce CPU and interrupt load
2063 when the driver is receiving lots of packets from the card. It is
2064 still somewhat experimental and thus not yet enabled by default.
2066 If your estimated Rx load is 10kpps or more, or if the card will be
2067 deployed on potentially unfriendly networks (e.g. in a firewall),
2070 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2077 depends on R8169 && VLAN_8021Q
2079 Say Y here for the r8169 driver to support the functions required
2080 by the kernel 802.1Q code.
2085 tristate "SiS190/SiS191 gigabit ethernet support"
2090 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2091 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2092 appear in lan on motherboard designs which are based on SiS 965
2093 and SiS 966 south bridge.
2095 To compile this driver as a module, choose M here: the module
2096 will be called sis190. This is recommended.
2099 tristate "New SysKonnect GigaEthernet support"
2103 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2104 and related Gigabit Ethernet adapters. It is a new smaller driver
2105 with better performance and more complete ethtool support.
2107 It does not support the link failover and network management
2108 features that "portable" vendor supplied sk98lin driver does.
2110 This driver supports adapters based on the original Yukon chipset:
2111 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2112 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2114 It does not support the newer Yukon2 chipset: a separate driver,
2115 sky2, is provided for Yukon2-based adapters.
2117 To compile this driver as a module, choose M here: the module
2118 will be called skge. This is recommended.
2121 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2125 This driver supports Gigabit Ethernet adapters based on the
2126 Marvell Yukon 2 chipset:
2127 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2128 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2130 There is companion driver for the older Marvell Yukon and
2131 Genesis based adapters: skge.
2133 To compile this driver as a module, choose M here: the module
2134 will be called sky2. This is recommended.
2137 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2140 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2141 compliant Gigabit Ethernet Adapter.
2143 This driver supports the original Yukon chipset. This driver is
2144 deprecated and will be removed from the kernel in the near future,
2145 it has been replaced by the skge driver. skge is cleaner and
2146 seems to work better.
2148 This driver does not support the newer Yukon2 chipset. A separate
2149 driver, sky2, is provided to support Yukon2-based adapters.
2151 The following adapters are supported by this driver:
2152 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2153 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2154 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2155 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2156 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2157 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2158 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2159 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2160 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2161 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2162 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2163 - EG1032 v2 Instant Gigabit Network Adapter
2164 - EG1064 v2 Instant Gigabit Network Adapter
2165 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2166 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2167 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2168 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2169 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2170 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2171 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2172 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2173 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2174 - Marvell RDK-8001 Adapter
2175 - Marvell RDK-8002 Adapter
2176 - Marvell RDK-8003 Adapter
2177 - Marvell RDK-8004 Adapter
2178 - Marvell RDK-8006 Adapter
2179 - Marvell RDK-8007 Adapter
2180 - Marvell RDK-8008 Adapter
2181 - Marvell RDK-8009 Adapter
2182 - Marvell RDK-8010 Adapter
2183 - Marvell RDK-8011 Adapter
2184 - Marvell RDK-8012 Adapter
2185 - Marvell RDK-8052 Adapter
2186 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2187 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2188 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2189 - SK-9521 10/100/1000Base-T Adapter
2190 - SK-9521 V2.0 10/100/1000Base-T Adapter
2191 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2192 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2193 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2194 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2195 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2196 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2197 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2198 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2199 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2200 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2201 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2202 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2203 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2204 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2205 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2206 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2207 - SMC EZ Card 1000 (SMC9452TXV.2)
2209 The adapters support Jumbo Frames.
2210 The dual link adapters support link-failover and dual port features.
2211 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2212 the scatter-gather functionality with sendfile(). Please refer to
2213 <file:Documentation/networking/sk98lin.txt> for more information about
2214 optional driver parameters.
2215 Questions concerning this driver may be addressed to:
2216 <linux@syskonnect.de>
2218 If you want to compile this driver as a module ( = code which can be
2219 inserted in and removed from the running kernel whenever you want),
2220 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2221 be called sk98lin. This is recommended.
2224 tristate "VIA Velocity support"
2230 If you have a VIA "Velocity" based network card say Y here.
2232 To compile this driver as a module, choose M here. The module
2233 will be called via-velocity.
2236 tristate "Broadcom Tigon3 support"
2239 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2241 To compile this driver as a module, choose M here: the module
2242 will be called tg3. This is recommended.
2245 tristate "Broadcom NetXtremeII support"
2250 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2252 To compile this driver as a module, choose M here: the module
2253 will be called bnx2. This is recommended.
2256 tristate "Spider Gigabit Ethernet driver"
2257 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2260 This driver supports the Gigabit Ethernet chips present on the
2261 Cell Processor-Based Blades from IBM.
2264 tristate "Tundra TSI108 gigabit Ethernet support"
2265 depends on TSI108_BRIDGE
2267 This driver supports Tundra TSI108 gigabit Ethernet ports.
2268 To compile this driver as a module, choose M here: the module
2269 will be called tsi108_eth.
2272 tristate "Gianfar Ethernet"
2273 depends on 85xx || 83xx || PPC_86xx
2277 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2278 and MPC86xx family of chips, and the FEC on the 8540.
2285 tristate "Freescale QE Gigabit Ethernet"
2286 depends on QUICC_ENGINE
2289 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2290 which is available on some Freescale SOCs.
2296 config UGETH_MAGIC_PACKET
2297 bool "Magic Packet detection support"
2300 config UGETH_FILTERING
2301 bool "Mac address filtering support"
2304 config UGETH_TX_ON_DEMAND
2305 bool "Transmit on Demand support"
2309 tristate "MV-643XX Ethernet support"
2310 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MV64X60 || MOMENCO_OCELOT_3 || (PPC_MULTIPLATFORM && PPC32)
2313 This driver supports the gigabit Ethernet on the Marvell MV643XX
2314 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2315 Pegasos II, amongst other PPC and MIPS boards.
2318 tristate "QLogic QLA3XXX Network Driver Support"
2321 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2323 To compile this driver as a module, choose M here: the module
2324 will be called qla3xxx.
2327 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2328 depends on PCI && EXPERIMENTAL
2332 This driver supports the Attansic L1 gigabit ethernet adapter.
2334 To compile this driver as a module, choose M here. The module
2335 will be called atl1.
2340 # 10 Gigabit Ethernet
2343 menuconfig NETDEV_10000
2344 bool "Ethernet (10000 Mbit)"
2351 tristate "Chelsio 10Gb Ethernet support"
2355 This driver supports Chelsio gigabit and 10-gigabit
2356 Ethernet cards. More information about adapter features and
2357 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2359 For general information about Chelsio and our products, visit
2360 our website at <http://www.chelsio.com>.
2362 For customer support, please visit our customer support page at
2363 <http://www.chelsio.com/support.htm>.
2365 Please send feedback to <linux-bugs@chelsio.com>.
2367 To compile this driver as a module, choose M here: the module
2368 will be called cxgb.
2370 config CHELSIO_T1_1G
2371 bool "Chelsio gigabit Ethernet support"
2372 depends on CHELSIO_T1
2374 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2375 are using only 10G cards say 'N' here.
2377 config CHELSIO_T1_NAPI
2378 bool "Use Rx Polling (NAPI)"
2379 depends on CHELSIO_T1
2382 NAPI is a driver API designed to reduce CPU and interrupt load
2383 when the driver is receiving lots of packets from the card.
2386 tristate "Chelsio Communications T3 10Gb Ethernet support"
2390 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2393 For general information about Chelsio and our products, visit
2394 our website at <http://www.chelsio.com>.
2396 For customer support, please visit our customer support page at
2397 <http://www.chelsio.com/support.htm>.
2399 Please send feedback to <linux-bugs@chelsio.com>.
2401 To compile this driver as a module, choose M here: the module
2402 will be called cxgb3.
2405 tristate "eHEA Ethernet support"
2408 This driver supports the IBM pSeries eHEA ethernet adapter.
2410 To compile the driver as a module, choose M here. The module
2411 will be called ehea.
2414 tristate "Intel(R) PRO/10GbE support"
2417 This driver supports Intel(R) PRO/10GbE family of
2418 adapters. For more information on how to identify your adapter, go
2419 to the Adapter & Driver ID Guide at:
2421 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2423 For general information and support, go to the Intel support
2426 <http://support.intel.com>
2428 More specific information on configuring the driver is in
2429 <file:Documentation/networking/ixgb.txt>.
2431 To compile this driver as a module, choose M here and read
2432 <file:Documentation/networking/net-modules.txt>. The module
2433 will be called ixgb.
2436 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2437 depends on IXGB && EXPERIMENTAL
2439 NAPI is a new driver API designed to reduce CPU and interrupt load
2440 when the driver is receiving lots of packets from the card. It is
2441 still somewhat experimental and thus not yet enabled by default.
2443 If your estimated Rx load is 10kpps or more, or if the card will be
2444 deployed on potentially unfriendly networks (e.g. in a firewall),
2447 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2453 tristate "S2IO 10Gbe XFrame NIC"
2456 This driver supports the 10Gbe XFrame NIC of S2IO.
2457 More specific information on configuring the driver is in
2458 <file:Documentation/networking/s2io.txt>.
2461 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2462 depends on S2IO && EXPERIMENTAL
2464 NAPI is a new driver API designed to reduce CPU and interrupt load
2465 when the driver is receiving lots of packets from the card. It is
2466 still somewhat experimental and thus not yet enabled by default.
2468 If your estimated Rx load is 10kpps or more, or if the card will be
2469 deployed on potentially unfriendly networks (e.g. in a firewall),
2472 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2478 tristate "Myricom Myri-10G Ethernet support"
2483 This driver supports Myricom Myri-10G Dual Protocol interface in
2484 Ethernet mode. If the eeprom on your board is not recent enough,
2485 you will need a newer firmware image.
2486 You may get this image or more information, at:
2488 <http://www.myri.com/scs/download-Myri10GE.html>
2490 To compile this driver as a module, choose M here and read
2491 <file:Documentation/networking/net-modules.txt>. The module
2492 will be called myri10ge.
2495 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2498 This enables the support for NetXen's Gigabit Ethernet card.
2501 tristate "PA Semi 1/10Gbit MAC"
2502 depends on PPC64 && PCI
2505 This driver supports the on-chip 1/10Gbit Ethernet controller on
2506 PA Semi's PWRficient line of chips.
2514 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2515 depends on MLX4_CORE
2518 This option causes debugging code to be compiled into the
2519 mlx4_core driver. The output can be turned on via the
2520 debug_level module parameter (which can also be set after
2521 the driver is loaded through sysfs).
2523 endif # NETDEV_10000
2525 source "drivers/net/tokenring/Kconfig"
2527 source "drivers/net/wireless/Kconfig"
2529 source "drivers/net/usb/Kconfig"
2531 source "drivers/net/pcmcia/Kconfig"
2533 source "drivers/net/wan/Kconfig"
2535 source "drivers/atm/Kconfig"
2537 source "drivers/s390/net/Kconfig"
2540 tristate "iSeries Virtual Ethernet driver support"
2541 depends on PPC_ISERIES
2544 tristate "RapidIO Ethernet over messaging driver support"
2547 config RIONET_TX_SIZE
2548 int "Number of outbound queue entries"
2552 config RIONET_RX_SIZE
2553 int "Number of inbound queue entries"
2558 bool "FDDI driver support"
2559 depends on (PCI || EISA || TC)
2561 Fiber Distributed Data Interface is a high speed local area network
2562 design; essentially a replacement for high speed Ethernet. FDDI can
2563 run over copper or fiber. If you are connected to such a network and
2564 want a driver for the FDDI card in your computer, say Y here (and
2565 then also Y to the driver for your FDDI card, below). Most people
2569 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2570 depends on FDDI && (PCI || EISA || TC)
2572 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2573 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2574 to a local FDDI network.
2576 To compile this driver as a module, choose M here: the module
2577 will be called defxx. If unsure, say N.
2581 prompt "Use MMIO instead of PIO" if PCI || EISA
2583 default n if PCI || EISA
2586 This instructs the driver to use EISA or PCI memory-mapped I/O
2587 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2588 Enabling this gives an improvement in processing time in parts
2589 of the driver, but it may cause problems with EISA (DEFEA)
2590 adapters. TURBOchannel does not have the concept of I/O ports,
2591 so MMIO is always used for these (DEFTA) adapters.
2596 tristate "SysKonnect FDDI PCI support"
2597 depends on FDDI && PCI
2600 Say Y here if you have a SysKonnect FDDI PCI adapter.
2601 The following adapters are supported by this driver:
2602 - SK-5521 (SK-NET FDDI-UP)
2603 - SK-5522 (SK-NET FDDI-UP DAS)
2604 - SK-5541 (SK-NET FDDI-FP)
2605 - SK-5543 (SK-NET FDDI-LP)
2606 - SK-5544 (SK-NET FDDI-LP DAS)
2607 - SK-5821 (SK-NET FDDI-UP64)
2608 - SK-5822 (SK-NET FDDI-UP64 DAS)
2609 - SK-5841 (SK-NET FDDI-FP64)
2610 - SK-5843 (SK-NET FDDI-LP64)
2611 - SK-5844 (SK-NET FDDI-LP64 DAS)
2612 - Netelligent 100 FDDI DAS Fibre SC
2613 - Netelligent 100 FDDI SAS Fibre SC
2614 - Netelligent 100 FDDI DAS UTP
2615 - Netelligent 100 FDDI SAS UTP
2616 - Netelligent 100 FDDI SAS Fibre MIC
2618 Read <file:Documentation/networking/skfp.txt> for information about
2621 Questions concerning this driver can be addressed to:
2622 <linux@syskonnect.de>
2624 To compile this driver as a module, choose M here: the module
2625 will be called skfp. This is recommended.
2628 bool "HIPPI driver support (EXPERIMENTAL)"
2629 depends on EXPERIMENTAL && INET && PCI
2631 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2632 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2633 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2634 single-mode). HIPPI networks are commonly used for clusters and to
2635 connect to super computers. If you are connected to a HIPPI network
2636 and have a HIPPI network card in your computer that you want to use
2637 under Linux, say Y here (you must also remember to enable the driver
2638 for your HIPPI card below). Most people will say N here.
2641 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2642 depends on HIPPI && PCI
2644 Say Y here if this is your PCI HIPPI network card.
2646 To compile this driver as a module, choose M here: the module
2647 will be called rrunner. If unsure, say N.
2649 config ROADRUNNER_LARGE_RINGS
2650 bool "Use large TX/RX rings (EXPERIMENTAL)"
2651 depends on ROADRUNNER
2653 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2654 of additional memory to allow for fastest operation, both for
2655 transmitting and receiving. This memory cannot be used by any other
2656 kernel code or by user space programs. Say Y here only if you have
2660 tristate "PLIP (parallel port) support"
2663 PLIP (Parallel Line Internet Protocol) is used to create a
2664 reasonably fast mini network consisting of two (or, rarely, more)
2665 local machines. A PLIP link from a Linux box is a popular means to
2666 install a Linux distribution on a machine which doesn't have a
2667 CD-ROM drive (a minimal system has to be transferred with floppies
2668 first). The kernels on both machines need to have this PLIP option
2669 enabled for this to work.
2671 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2672 ports (the connectors at the computers with 25 holes) are connected
2673 with "null printer" or "Turbo Laplink" cables which can transmit 4
2674 bits at a time (mode 0) or with special PLIP cables, to be used on
2675 bidirectional parallel ports only, which can transmit 8 bits at a
2676 time (mode 1); you can find the wiring of these cables in
2677 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2678 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2679 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2680 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2681 and winsock or NCSA's telnet.
2683 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2684 as the NET-3-HOWTO, both available from
2685 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2686 protocol has been changed and this PLIP driver won't work together
2687 with the PLIP support in Linux versions 1.0.x. This option enlarges
2688 your kernel by about 8 KB.
2690 To compile this driver as a module, choose M here and read
2691 <file:Documentation/networking/net-modules.txt>. The module will be
2692 called plip. If unsure, say Y or M, in case you buy a laptop
2696 tristate "PPP (point-to-point protocol) support"
2699 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2700 the same purpose: sending Internet traffic over telephone (and other
2701 serial) lines. Ask your access provider if they support it, because
2702 otherwise you can't use it; most Internet access providers these
2703 days support PPP rather than SLIP.
2705 To use PPP, you need an additional program called pppd as described
2706 in the PPP-HOWTO, available at
2707 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2708 the version of pppd recommended in <file:Documentation/Changes>.
2709 The PPP option enlarges your kernel by about 16 KB.
2711 There are actually two versions of PPP: the traditional PPP for
2712 asynchronous lines, such as regular analog phone lines, and
2713 synchronous PPP which can be used over digital ISDN lines for
2714 example. If you want to use PPP over phone lines or other
2715 asynchronous serial lines, you need to say Y (or M) here and also to
2716 the next option, "PPP support for async serial ports". For PPP over
2717 synchronous lines, you should say Y (or M) here and to "Support
2718 synchronous PPP", below.
2720 If you said Y to "Version information on all symbols" above, then
2721 you cannot compile the PPP driver into the kernel; you can then only
2722 compile it as a module. To compile this driver as a module, choose M
2723 here and read <file:Documentation/networking/net-modules.txt>.
2724 The module will be called ppp_generic.
2726 config PPP_MULTILINK
2727 bool "PPP multilink support (EXPERIMENTAL)"
2728 depends on PPP && EXPERIMENTAL
2730 PPP multilink is a protocol (defined in RFC 1990) which allows you
2731 to combine several (logical or physical) lines into one logical PPP
2732 connection, so that you can utilize your full bandwidth.
2734 This has to be supported at the other end as well and you need a
2735 version of the pppd daemon which understands the multilink protocol.
2740 bool "PPP filtering"
2743 Say Y here if you want to be able to filter the packets passing over
2744 PPP interfaces. This allows you to control which packets count as
2745 activity (i.e. which packets will reset the idle timer or bring up
2746 a demand-dialed link) and which packets are to be dropped entirely.
2747 You need to say Y here if you wish to use the pass-filter and
2748 active-filter options to pppd.
2753 tristate "PPP support for async serial ports"
2757 Say Y (or M) here if you want to be able to use PPP over standard
2758 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2759 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2762 To compile this driver as a module, choose M here.
2767 tristate "PPP support for sync tty ports"
2770 Say Y (or M) here if you want to be able to use PPP over synchronous
2771 (HDLC) tty devices, such as the SyncLink adapter. These devices
2772 are often used for high-speed leased lines like T1/E1.
2774 To compile this driver as a module, choose M here.
2777 tristate "PPP Deflate compression"
2782 Support for the Deflate compression method for PPP, which uses the
2783 Deflate algorithm (the same algorithm that gzip uses) to compress
2784 each PPP packet before it is sent over the wire. The machine at the
2785 other end of the PPP link (usually your ISP) has to support the
2786 Deflate compression method as well for this to be useful. Even if
2787 they don't support it, it is safe to say Y here.
2789 To compile this driver as a module, choose M here.
2792 tristate "PPP BSD-Compress compression"
2795 Support for the BSD-Compress compression method for PPP, which uses
2796 the LZW compression method to compress each PPP packet before it is
2797 sent over the wire. The machine at the other end of the PPP link
2798 (usually your ISP) has to support the BSD-Compress compression
2799 method as well for this to be useful. Even if they don't support it,
2800 it is safe to say Y here.
2802 The PPP Deflate compression method ("PPP Deflate compression",
2803 above) is preferable to BSD-Compress, because it compresses better
2806 Note that the BSD compression code will always be compiled as a
2807 module; it is called bsd_comp and will show up in the directory
2808 modules once you have said "make modules". If unsure, say N.
2811 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2812 depends on PPP && EXPERIMENTAL
2818 Support for the MPPE Encryption protocol, as employed by the
2819 Microsoft Point-to-Point Tunneling Protocol.
2821 See http://pptpclient.sourceforge.net/ for information on
2822 configuring PPTP clients and servers to utilize this method.
2825 tristate "PPP over Ethernet (EXPERIMENTAL)"
2826 depends on EXPERIMENTAL && PPP
2828 Support for PPP over Ethernet.
2830 This driver requires the latest version of pppd from the CVS
2831 repository at cvs.samba.org. Alternatively, see the
2832 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2833 which contains instruction on how to use this driver (under
2834 the heading "Kernel mode PPPoE").
2837 tristate "PPP over ATM"
2838 depends on ATM && PPP
2840 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2841 This implementation does not yet comply with section 8 of RFC2364,
2842 which can lead to bad results if the ATM peer loses state and
2843 changes its encapsulation unilaterally.
2846 tristate "SLIP (serial line) support"
2848 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2849 connect to your Internet service provider or to connect to some
2850 other local Unix box or if you want to configure your Linux box as a
2851 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2852 Internet Protocol) is a protocol used to send Internet traffic over
2853 serial connections such as telephone lines or null modem cables;
2854 nowadays, the protocol PPP is more commonly used for this same
2857 Normally, your access provider has to support SLIP in order for you
2858 to be able to use it, but there is now a SLIP emulator called SLiRP
2859 around (available from
2860 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2861 allows you to use SLIP over a regular dial up shell connection. If
2862 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2863 NET-3-HOWTO, available from
2864 <http://www.tldp.org/docs.html#howto>, explains how to
2865 configure SLIP. Note that you don't need this option if you just
2866 want to run term (term is a program which gives you almost full
2867 Internet connectivity if you have a regular dial up shell account on
2868 some Internet connected Unix computer. Read
2869 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2870 support will enlarge your kernel by about 4 KB. If unsure, say N.
2872 To compile this driver as a module, choose M here and read
2873 <file:Documentation/networking/net-modules.txt>. The module will be
2876 config SLIP_COMPRESSED
2877 bool "CSLIP compressed headers"
2881 This protocol is faster than SLIP because it uses compression on the
2882 TCP/IP headers (not on the data itself), but it has to be supported
2883 on both ends. Ask your access provider if you are not sure and
2884 answer Y, just in case. You will still be able to use plain SLIP. If
2885 you plan to use SLiRP, the SLIP emulator (available from
2886 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2887 allows you to use SLIP over a regular dial up shell connection, you
2888 definitely want to say Y here. The NET-3-HOWTO, available from
2889 <http://www.tldp.org/docs.html#howto>, explains how to configure
2890 CSLIP. This won't enlarge your kernel.
2895 This option enables Van Jacobsen serial line header compression
2899 bool "Keepalive and linefill"
2902 Adds additional capabilities to the SLIP driver to support the
2903 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2906 config SLIP_MODE_SLIP6
2907 bool "Six bit SLIP encapsulation"
2910 Just occasionally you may need to run IP over hostile serial
2911 networks that don't pass all control characters or are only seven
2912 bit. Saying Y here adds an extra mode you can use with SLIP:
2913 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2914 the serial device. Naturally, this has to be supported at the other
2915 end of the link as well. It's good enough, for example, to run IP
2916 over the async ports of a Camtec JNT Pad. If unsure, say N.
2919 bool "Fibre Channel driver support"
2920 depends on SCSI && PCI
2922 Fibre Channel is a high speed serial protocol mainly used to connect
2923 large storage devices to the computer; it is compatible with and
2924 intended to replace SCSI.
2926 If you intend to use Fibre Channel, you need to have a Fibre channel
2927 adaptor card in your computer; say Y here and to the driver for your
2928 adaptor below. You also should have said Y to "SCSI support" and
2929 "SCSI generic support".
2932 tristate "Traffic Shaper (OBSOLETE)"
2933 depends on EXPERIMENTAL
2935 The traffic shaper is a virtual network device that allows you to
2936 limit the rate of outgoing data flow over some other network device.
2937 The traffic that you want to slow down can then be routed through
2938 these virtual devices. See
2939 <file:Documentation/networking/shaper.txt> for more information.
2941 An alternative to this traffic shaper are traffic schedulers which
2942 you'll get if you say Y to "QoS and/or fair queuing" in
2943 "Networking options".
2945 To compile this driver as a module, choose M here: the module
2946 will be called shaper. If unsure, say N.
2949 tristate "Network console logging support (EXPERIMENTAL)"
2950 depends on EXPERIMENTAL
2952 If you want to log kernel messages over the network, enable this.
2953 See <file:Documentation/networking/netconsole.txt> for details.
2959 bool "Netpoll traffic trapping"
2963 config NET_POLL_CONTROLLER