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