3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
30 tristate "Intermediate Functional Block support"
31 depends on NET_CLS_ACT
33 This is an intermediate driver that allows sharing of
35 To compile this driver as a module, choose M here: the module
36 will be called ifb. If you want to use more than one ifb
37 device at a time, you need to compile this driver as a module.
38 Instead of 'ifb', the devices will then be called 'ifb0',
40 Look at the iproute2 documentation directory for usage etc
43 tristate "Dummy net driver support"
45 This is essentially a bit-bucket device (i.e. traffic you send to
46 this device is consigned into oblivion) with a configurable IP
47 address. It is most commonly used in order to make your currently
48 inactive SLIP address seem like a real address for local programs.
49 If you use SLIP or PPP, you might want to say Y here. Since this
50 thing often comes in handy, the default is Y. It won't enlarge your
51 kernel either. What a deal. Read about it in the Network
52 Administrator's Guide, available from
53 <http://www.tldp.org/docs.html#guide>.
55 To compile this driver as a module, choose M here: the module
56 will be called dummy. If you want to use more than one dummy
57 device at a time, you need to compile this driver as a module.
58 Instead of 'dummy', the devices will then be called 'dummy0',
62 tristate "Bonding driver support"
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "EQL (serial line load balancing) support"
96 If you have two serial connections to some other computer (this
97 usually requires two modems and two telephone lines) and you use
98 SLIP (the protocol for sending Internet traffic over telephone
99 lines) or PPP (a better SLIP) on them, you can make them behave like
100 one double speed connection using this driver. Naturally, this has
101 to be supported at the other end as well, either with a similar EQL
102 Linux driver or with a Livingston Portmaster 2e.
104 Say Y if you want this and read
105 <file:Documentation/networking/eql.txt>. You may also want to read
106 section 6.2 of the NET-3-HOWTO, available from
107 <http://www.tldp.org/docs.html#howto>.
109 To compile this driver as a module, choose M here: the module
110 will be called eql. If unsure, say N.
113 tristate "Universal TUN/TAP device driver support"
116 TUN/TAP provides packet reception and transmission for user space
117 programs. It can be viewed as a simple Point-to-Point or Ethernet
118 device, which instead of receiving packets from a physical media,
119 receives them from user space program and instead of sending packets
120 via physical media writes them to the user space program.
122 When a program opens /dev/net/tun, driver creates and registers
123 corresponding net device tunX or tapX. After a program closed above
124 devices, driver will automatically delete tunXX or tapXX device and
125 all routes corresponding to it.
127 Please read <file:Documentation/networking/tuntap.txt> for more
130 To compile this driver as a module, choose M here: the module
133 If you don't know what to use this for, you don't need it.
136 tristate "Virtual ethernet pair device"
138 This device is a local ethernet tunnel. Devices are created in pairs.
139 When one end receives the packet it appears on its pair and vice
143 tristate "General Instruments Surfboard 1000"
146 This is a driver for the General Instrument (also known as
147 NextLevel) SURFboard 1000 internal
148 cable modem. This is an ISA card which is used by a number of cable
149 TV companies to provide cable modem access. It's a one-way
150 downstream-only cable modem, meaning that your upstream net link is
151 provided by your regular phone modem.
153 At present this driver only compiles as a module, so say M here if
154 you have this card. The module will be called sb1000. Then read
155 <file:Documentation/networking/README.sb1000> for information on how
156 to use this module, as it needs special ppp scripts for establishing
157 a connection. Further documentation and the necessary scripts can be
160 <http://www.jacksonville.net/~fventuri/>
161 <http://home.adelphia.net/~siglercm/sb1000.html>
162 <http://linuxpower.cx/~cable/>
164 If you don't have this card, of course say N.
166 source "drivers/net/arcnet/Kconfig"
168 source "drivers/net/phy/Kconfig"
174 menuconfig NET_ETHERNET
175 bool "Ethernet (10 or 100Mbit)"
178 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
179 type of Local Area Network (LAN) in universities and companies.
181 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
182 coaxial cable, linking computers in a chain), 10BASE-T or twisted
183 pair (10 Mbps over twisted pair cable, linking computers to central
184 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
185 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
186 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
187 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
188 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
189 Ethernet (1 Gbps over optical fiber or short copper links).
191 If your Linux machine will be connected to an Ethernet and you have
192 an Ethernet network interface card (NIC) installed in your computer,
193 say Y here and read the Ethernet-HOWTO, available from
194 <http://www.tldp.org/docs.html#howto>. You will then also have
195 to say Y to the driver for your particular NIC.
197 Note that the answer to this question won't directly affect the
198 kernel: saying N will just cause the configurator to skip all
199 the questions about Ethernet network cards. If unsure, say N.
204 tristate "Generic Media Independent Interface device support"
206 Most ethernet controllers have MII transceiver either as an external
207 or internal device. It is safe to say Y or M here even if your
208 ethernet card lack MII.
211 tristate "Atmel MACB support"
212 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
215 The Atmel MACB ethernet interface is found on many AT32 and AT91
216 parts. Say Y to include support for the MACB chip.
218 To compile this driver as a module, choose M here: the module
221 source "drivers/net/arm/Kconfig"
224 tristate "ASIX AX88796 NE2000 clone support"
225 depends on ARM || MIPS || SUPERH
229 AX88796 driver, using platform bus to provide
230 chip detection and resources
233 bool "ASIX AX88796 external 93CX6 eeprom support"
237 Select this if your platform comes with an external 93CX6 eeprom.
240 tristate "MACE (Power Mac ethernet) support"
241 depends on PPC_PMAC && PPC32
244 Power Macintoshes and clones with Ethernet built-in on the
245 motherboard will usually use a MACE (Medium Access Control for
246 Ethernet) interface. Say Y to include support for the MACE chip.
248 To compile this driver as a module, choose M here: the module
251 config MACE_AAUI_PORT
252 bool "Use AAUI port instead of TP by default"
255 Some Apple machines (notably the Apple Network Server) which use the
256 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
257 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
258 Y here if you have such a machine. If unsure, say N.
259 The driver will default to AAUI on ANS anyway, and if you use it as
260 a module, you can provide the port_aaui=0|1 to force the driver.
263 tristate "BMAC (G3 ethernet) support"
264 depends on PPC_PMAC && PPC32
267 Say Y for support of BMAC Ethernet interfaces. These are used on G3
270 To compile this driver as a module, choose M here: the module
274 tristate "Ariadne support"
277 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
280 To compile this driver as a module, choose M here: the module
281 will be called ariadne.
284 tristate "A2065 support"
288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
291 To compile this driver as a module, choose M here: the module
292 will be called a2065.
295 tristate "Hydra support"
299 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
301 To compile this driver as a module, choose M here: the module
302 will be called hydra.
305 tristate "Zorro NS8390-based Ethernet support"
309 This driver is for Zorro Ethernet cards using an NS8390-compatible
310 chipset, like the Village Tronic Ariadne II and the Individual
311 Computers X-Surf Ethernet cards. If you have such a card, say Y.
314 To compile this driver as a module, choose M here: the module
315 will be called zorro8390.
318 tristate "PCMCIA NE2000 support"
319 depends on AMIGA_PCMCIA
322 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
325 To compile this driver as a module, choose M here: the module
329 bool "Macintosh NS 8390 based ethernet cards"
333 If you want to include a driver to support Nubus or LC-PDS
334 Ethernet cards using an NS8390 chipset or its equivalent, say Y
335 and read the Ethernet-HOWTO, available from
336 <http://www.tldp.org/docs.html#howto>.
339 tristate "Macintosh CS89x0 based ethernet cards"
342 Support for CS89x0 chipset based Ethernet cards. If you have a
343 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
344 read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
347 To compile this driver as a module, choose M here. This module will
351 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
354 Support for NatSemi SONIC based Ethernet devices. This includes
355 the onboard Ethernet in many Quadras as well as some LC-PDS,
356 a few Nubus and all known Comm Slot Ethernet cards. If you have
357 one of these say Y and read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 To compile this driver as a module, choose M here. This module will
364 bool "Macintosh (AV) onboard MACE ethernet"
368 Support for the onboard AMD 79C940 MACE Ethernet controller used in
369 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
370 say Y and read the Ethernet-HOWTO, available from
371 <http://www.tldp.org/docs.html#howto>.
374 tristate "MVME147 (Lance) Ethernet support"
378 Support for the on-board Ethernet interface on the Motorola MVME147
379 single-board computer. Say Y here to include the
380 driver for this chip in your kernel.
381 To compile this driver as a module, choose M here.
384 tristate "MVME16x Ethernet support"
387 This is the driver for the Ethernet interface on the Motorola
388 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
389 driver for this chip in your kernel.
390 To compile this driver as a module, choose M here.
393 tristate "BVME6000 Ethernet support"
396 This is the driver for the Ethernet interface on BVME4000 and
397 BVME6000 VME boards. Say Y here to include the driver for this chip
399 To compile this driver as a module, choose M here.
402 tristate "Atari Lance support"
405 Say Y to include support for several Atari Ethernet adapters based
406 on the AMD Lance chipset: RieblCard (with or without battery), or
407 PAMCard VME (also the version by Rhotron, with different addresses).
410 tristate "Sun3/Sun3x on-board LANCE support"
411 depends on SUN3 || SUN3X
413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
415 here to compile in the Linux driver for this and enable Ethernet.
416 General Linux information on the Sun 3 and 3x series (now
418 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
420 If you're not building a kernel for a Sun 3, say N.
423 bool "Sun3 on-board Intel 82586 support"
426 This driver enables support for the on-board Intel 82586 based
427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
428 that this driver does not support 82586-based adapters on additional
432 bool "HP on-board LANCE support"
436 If you want to use the builtin "LANCE" Ethernet controller on an
437 HP300 machine, say Y here.
440 tristate "Lasi ethernet"
443 Say Y here to support the builtin Intel 82596 ethernet controller
444 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
447 tristate "SNI RM ethernet"
448 depends on NET_ETHERNET && SNI_RM
450 Say Y here to support the on-board Intel 82596 ethernet controller
451 built into SNI RM machines.
454 tristate "Korina (IDT RC32434) Ethernet support"
455 depends on NET_ETHERNET && MIKROTIK_RB532
457 If you have a Mikrotik RouterBoard 500 or IDT RC32434
458 based system say Y. Otherwise say N.
460 config MIPS_JAZZ_SONIC
461 tristate "MIPS JAZZ onboard SONIC Ethernet support"
464 This is the driver for the onboard card of MIPS Magnum 4000,
465 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
467 config MIPS_AU1X00_ENET
468 bool "MIPS AU1000 Ethernet support"
469 depends on SOC_AU1X00
473 If you have an Alchemy Semi AU1X00 based system
474 say Y. Otherwise, say N.
477 bool "SGI IOC3 Ethernet"
478 depends on PCI && SGI_IP27
482 If you have a network (Ethernet) card of this type, say Y and read
483 the Ethernet-HOWTO, available from
484 <http://www.tldp.org/docs.html#howto>.
487 tristate "MIPS simulator Network device"
490 The MIPSNET device is a simple Ethernet network device which is
491 emulated by the MIPS Simulator.
492 If you are not using a MIPSsim or are unsure, say N.
494 config SGI_O2MACE_ETH
495 tristate "SGI O2 MACE Fast Ethernet support"
496 depends on SGI_IP32=y
499 tristate "National DP83902AV support"
503 Support for cards based on the National Semiconductor DP83902AV
504 ST-NIC Serial Network Interface Controller for Twisted Pair. This
505 is a 10Mbit/sec Ethernet controller. Product overview and specs at
506 <http://www.national.com/pf/DP/DP83902A.html>.
511 tristate "Renesas SuperH Ethernet support"
512 depends on SUPERH && \
513 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)
519 Renesas SuperH Ethernet device driver.
520 This driver support SH7710 and SH7712.
523 tristate "Sun LANCE support"
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 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 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"
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"
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"
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>
588 tristate "Sun Virtual Network support"
591 Support for virtual network devices under Sun Logical Domains.
593 config NET_VENDOR_3COM
595 depends on ISA || EISA || MCA || PCI
597 If you have a network (Ethernet) card belonging to this class, say Y
598 and read the Ethernet-HOWTO, available from
599 <http://www.tldp.org/docs.html#howto>.
601 Note that the answer to this question doesn't directly affect the
602 kernel: saying N will just cause the configurator to skip all
603 the questions about 3COM cards. If you say Y, you will be asked for
604 your specific card in the following questions.
607 tristate "3c501 \"EtherLink\" support"
608 depends on NET_VENDOR_3COM && ISA
610 If you have a network (Ethernet) card of this type, say Y and read
611 the Ethernet-HOWTO, available from
612 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
613 new card, since the 3c501 is slow, broken, and obsolete: you will
614 have problems. Some people suggest to ping ("man ping") a nearby
615 machine every minute ("man cron") when using this card.
617 To compile this driver as a module, choose M here. The module
618 will be called 3c501.
621 tristate "3c503 \"EtherLink II\" support"
622 depends on NET_VENDOR_3COM && ISA
625 If you have a network (Ethernet) card of this type, say Y and read
626 the Ethernet-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>.
629 To compile this driver as a module, choose M here. The module
630 will be called 3c503.
633 tristate "3c505 \"EtherLink Plus\" support"
634 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
636 Information about this network (Ethernet) card can be found in
637 <file:Documentation/networking/3c505.txt>. If you have a card of
638 this type, say Y and read the Ethernet-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
641 To compile this driver as a module, choose M here. The module
642 will be called 3c505.
645 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
646 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
648 If you have a network (Ethernet) card of this type, say Y and read
649 the Ethernet-HOWTO, available from
650 <http://www.tldp.org/docs.html#howto>.
652 To compile this driver as a module, choose M here. The module
653 will be called 3c507.
656 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
657 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
659 If you have a network (Ethernet) card belonging to the 3Com
660 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
661 from <http://www.tldp.org/docs.html#howto>.
663 If your card is not working you may need to use the DOS
664 setup disk to disable Plug & Play mode, and to select the default
667 To compile this driver as a module, choose M here. The module
668 will be called 3c509.
671 tristate "3c515 ISA \"Fast EtherLink\""
672 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
674 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
675 network card, say Y and read the Ethernet-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>.
678 To compile this driver as a module, choose M here. 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. The module
690 will be called 3c523.
693 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
694 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
696 If you have a network (Ethernet) card of this type, say Y and read
697 the Ethernet-HOWTO, available from
698 <http://www.tldp.org/docs.html#howto>.
700 To compile this driver as a module, choose M here. The module
701 will be called 3c527.
704 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
705 depends on NET_VENDOR_3COM && (PCI || EISA)
708 This option enables driver support for a large number of 10Mbps and
709 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
711 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
712 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
713 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
714 "Tornado" (3c905) PCI
715 "Hurricane" (3c555/3cSOHO) PCI
717 If you have such a card, say Y and read the Ethernet-HOWTO,
718 available from <http://www.tldp.org/docs.html#howto>. More
719 specific information is in
720 <file:Documentation/networking/vortex.txt> and in the comments at
721 the beginning of <file:drivers/net/3c59x.c>.
723 To compile this support as a module, choose M here.
726 tristate "3cr990 series \"Typhoon\" support"
727 depends on NET_VENDOR_3COM && PCI
730 This option enables driver support for the 3cr990 series of cards:
732 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
733 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
734 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
736 If you have a network (Ethernet) card of this type, say Y and read
737 the Ethernet-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>.
740 To compile this driver as a module, choose M here. The module
741 will be called typhoon.
744 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
745 depends on ISA && ISA_DMA_API
747 If you have a network (Ethernet) card of this type, say Y and read
748 the Ethernet-HOWTO, available from
749 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
752 To compile this driver as a module, choose M here: the module
753 will be called lance. This is recommended.
755 config NET_VENDOR_SMC
756 bool "Western Digital/SMC cards"
757 depends on ISA || MCA || EISA || MAC
759 If you have a network (Ethernet) card belonging to this class, say Y
760 and read the Ethernet-HOWTO, available from
761 <http://www.tldp.org/docs.html#howto>.
763 Note that the answer to this question doesn't directly affect the
764 kernel: saying N will just cause the configurator to skip all
765 the questions about Western Digital cards. If you say Y, you will be
766 asked for your specific card in the following questions.
769 tristate "WD80*3 support"
770 depends on NET_VENDOR_SMC && ISA
773 If you have a network (Ethernet) card of this type, say Y and read
774 the Ethernet-HOWTO, available from
775 <http://www.tldp.org/docs.html#howto>.
777 To compile this driver as a module, choose M here. The module
781 tristate "SMC Ultra MCA support"
782 depends on NET_VENDOR_SMC && MCA
785 If you have a network (Ethernet) card of this type and are running
786 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
787 available from <http://www.tldp.org/docs.html#howto>.
789 To compile this driver as a module, choose M here. The module
790 will be called smc-mca.
793 tristate "SMC Ultra support"
794 depends on NET_VENDOR_SMC && ISA
797 If you have a network (Ethernet) card of this type, say Y and read
798 the Ethernet-HOWTO, available from
799 <http://www.tldp.org/docs.html#howto>.
801 Important: There have been many reports that, with some motherboards
802 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
803 such as some BusLogic models) causes corruption problems with many
804 operating systems. The Linux smc-ultra driver has a work-around for
805 this but keep it in mind if you have such a SCSI card and have
808 To compile this driver as a module, choose M here. The module
809 will be called smc-ultra.
812 tristate "SMC Ultra32 EISA support"
813 depends on NET_VENDOR_SMC && EISA
816 If you have a network (Ethernet) card of this type, say Y and read
817 the Ethernet-HOWTO, available from
818 <http://www.tldp.org/docs.html#howto>.
820 To compile this driver as a module, choose M here. The module
821 will be called smc-ultra32.
824 tristate "Blackfin 527/536/537 on-chip mac support"
825 depends on NET_ETHERNET && (BF527 || BF537 || BF536)
829 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
831 This is the driver for blackfin on-chip mac device. Say Y if you want it
832 compiled into the kernel. This driver is also available as a module
833 ( = code which can be inserted in and removed from the running kernel
834 whenever you want). The module will be called bfin_mac.
836 config BFIN_MAC_USE_L1
837 bool "Use L1 memory for rx/tx packets"
838 depends on BFIN_MAC && (BF527 || BF537)
841 To get maximum network performance, you should use L1 memory as rx/tx buffers.
842 Say N here if you want to reserve L1 memory for other uses.
844 config BFIN_TX_DESC_NUM
845 int "Number of transmit buffer packets"
847 range 6 10 if BFIN_MAC_USE_L1
851 Set the number of buffer packets used in driver.
853 config BFIN_RX_DESC_NUM
854 int "Number of receive buffer packets"
856 range 20 100 if BFIN_MAC_USE_L1
860 Set the number of buffer packets used in driver.
863 bool "RMII PHY Interface (EXPERIMENTAL)"
864 depends on BFIN_MAC && EXPERIMENTAL
865 default y if BFIN527_EZKIT
866 default n if BFIN537_STAMP
868 Use Reduced PHY MII Interface
871 tristate "SMC 9194 support"
872 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
875 This is support for the SMC9xxx based Ethernet cards. Choose this
876 option if you have a DELL laptop with the docking station, or
877 another SMC9192/9194 based chipset. Say Y if you want it compiled
878 into the kernel, and read the file
879 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
880 available from <http://www.tldp.org/docs.html#howto>.
882 To compile this driver as a module, choose M here. The module
883 will be called smc9194.
886 tristate "SMC 91C9x/91C1xxx support"
889 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
890 SOC_AU1X00 || BLACKFIN || MN10300
892 This is a driver for SMC's 91x series of Ethernet chipsets,
893 including the SMC91C94 and the SMC91C111. Say Y if you want it
894 compiled into the kernel, and read the file
895 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
896 available from <http://www.linuxdoc.org/docs.html#howto>.
898 This driver is also available as a module ( = code which can be
899 inserted in and removed from the running kernel whenever you want).
900 The module will be called smc91x. If you want to compile it as a
901 module, say M here and read <file:Documentation/kbuild/modules.txt>.
904 tristate "NetX Ethernet support"
908 This is support for the Hilscher netX builtin Ethernet ports
910 To compile this driver as a module, choose M here. The module
911 will be called netx-eth.
914 tristate "DM9000 support"
915 depends on ARM || BLACKFIN || MIPS
919 Support for DM9000 chipset.
921 To compile this driver as a module, choose M here. The module
922 will be called dm9000.
924 config DM9000_DEBUGLEVEL
925 int "DM9000 maximum debug level"
929 The maximum level of debugging code compiled into the DM9000
932 config DM9000_FORCE_SIMPLE_PHY_POLL
933 bool "Force simple NSR based PHY polling"
936 This configuration forces the DM9000 to use the NSR's LinkStatus
937 bit to determine if the link is up or down instead of the more
938 costly MII PHY reads. Note, this will not work if the chip is
939 operating with an external PHY.
942 tristate "ENC28J60 support"
943 depends on EXPERIMENTAL && SPI && NET_ETHERNET
946 Support for the Microchip EN28J60 ethernet chip.
948 To compile this driver as a module, choose M here. The module will be
951 config ENC28J60_WRITEVERIFY
952 bool "Enable write verify"
955 Enable the verify after the buffer write useful for debugging purpose.
959 tristate "SMSC LAN911[5678] support"
962 depends on ARCH_PXA || SUPERH
964 This is a driver for SMSC's LAN911x series of Ethernet chipsets
965 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
966 Say Y if you want it compiled into the kernel,
967 and read the Ethernet-HOWTO, available from
968 <http://www.linuxdoc.org/docs.html#howto>.
970 This driver is also available as a module. The module will be
971 called smc911x. If you want to compile it as a module, say M
972 here and read <file:Documentation/kbuild/modules.txt>
974 config NET_VENDOR_RACAL
975 bool "Racal-Interlan (Micom) NI cards"
978 If you have a network (Ethernet) card belonging to this class, such
979 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
980 available from <http://www.tldp.org/docs.html#howto>.
982 Note that the answer to this question doesn't directly affect the
983 kernel: saying N will just cause the configurator to skip all
984 the questions about NI cards. If you say Y, you will be asked for
985 your specific card in the following questions.
988 tristate "NI5010 support (EXPERIMENTAL)"
989 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
991 If you have a network (Ethernet) card of this type, say Y and read
992 the Ethernet-HOWTO, available from
993 <http://www.tldp.org/docs.html#howto>. Note that this is still
996 To compile this driver as a module, choose M here. The module
997 will be called ni5010.
1000 tristate "NI5210 support"
1001 depends on NET_VENDOR_RACAL && ISA
1003 If you have a network (Ethernet) card of this type, say Y and read
1004 the Ethernet-HOWTO, available from
1005 <http://www.tldp.org/docs.html#howto>.
1007 To compile this driver as a module, choose M here. The module
1008 will be called ni52.
1011 tristate "NI6510 support"
1012 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1014 If you have a network (Ethernet) card of this type, say Y and read
1015 the Ethernet-HOWTO, available from
1016 <http://www.tldp.org/docs.html#howto>.
1018 To compile this driver as a module, choose M here. The module
1019 will be called ni65.
1021 source "drivers/net/tulip/Kconfig"
1024 tristate "AT1700/1720 support (EXPERIMENTAL)"
1025 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1028 If you have a network (Ethernet) card of this type, say Y and read
1029 the Ethernet-HOWTO, available from
1030 <http://www.tldp.org/docs.html#howto>.
1032 To compile this driver as a module, choose M here. The module
1033 will be called at1700.
1036 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1037 depends on ISA || EISA || MCA
1040 If you have a network (Ethernet) card of this type, say Y and read
1041 the Ethernet-HOWTO, available from
1042 <http://www.tldp.org/docs.html#howto> as well as
1043 <file:drivers/net/depca.c>.
1045 To compile this driver as a module, choose M here. The module
1046 will be called depca.
1049 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1050 depends on ISA || EISA || PCI
1052 If you have a network (Ethernet) card of this type, say Y and read
1053 the Ethernet-HOWTO, available from
1054 <http://www.tldp.org/docs.html#howto>.
1056 To compile this driver as a module, choose M here. The module
1057 will be called hp100.
1060 bool "Other ISA cards"
1063 If your network (Ethernet) card hasn't been mentioned yet and its
1064 bus system (that's the way the cards talks to the other components
1065 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1066 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1067 available from <http://www.tldp.org/docs.html#howto>.
1071 Note that the answer to this question doesn't directly affect the
1072 kernel: saying N will just cause the configurator to skip all
1073 the remaining ISA network card questions. If you say Y, you will be
1074 asked for your specific card in the following questions.
1077 tristate "Cabletron E21xx support"
1081 If you have a network (Ethernet) card of this type, say Y and read
1082 the Ethernet-HOWTO, available from
1083 <http://www.tldp.org/docs.html#howto>.
1085 To compile this driver as a module, choose M here. The module
1086 will be called e2100.
1089 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1093 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1094 cards. If this is for you, say Y and read
1095 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1096 well as the Ethernet-HOWTO, available from
1097 <http://www.tldp.org/docs.html#howto>.
1099 To compile this driver as a module, choose M here. The module
1100 will be called ewrk3.
1103 tristate "EtherExpress 16 support"
1106 If you have an EtherExpress16 network (Ethernet) card, say Y and
1107 read the Ethernet-HOWTO, available from
1108 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1109 EtherExpress16 card used to be regarded as a very poor choice
1110 because the driver was very unreliable. We now have a new driver
1111 that should do better.
1113 To compile this driver as a module, choose M here. The module
1114 will be called eexpress.
1117 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1120 If you have a network (Ethernet) card of this type, say Y. This
1121 driver supports Intel i82595{FX,TX} based boards. Note however
1122 that the EtherExpress PRO/100 Ethernet card has its own separate
1123 driver. Please read the Ethernet-HOWTO, available from
1124 <http://www.tldp.org/docs.html#howto>.
1126 To compile this driver as a module, choose M here. The module
1127 will be called eepro.
1130 tristate "HP PCLAN+ (27247B and 27252A) support"
1134 If you have a network (Ethernet) card of this type, say Y and read
1135 the Ethernet-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1138 To compile this driver as a module, choose M here. The module
1139 will be called hp-plus.
1142 tristate "HP PCLAN (27245 and other 27xxx series) support"
1146 If you have a network (Ethernet) card of this type, say Y and read
1147 the Ethernet-HOWTO, available from
1148 <http://www.tldp.org/docs.html#howto>.
1150 To compile this driver as a module, choose M here. The module
1154 tristate "LP486E on board Ethernet"
1157 Say Y here to support the 82596-based on-board Ethernet controller
1158 for the Panther motherboard, which is one of the two shipped in the
1159 Intel Professional Workstation.
1162 tristate "ICL EtherTeam 16i/32 support"
1165 If you have a network (Ethernet) card of this type, say Y and read
1166 the Ethernet-HOWTO, available from
1167 <http://www.tldp.org/docs.html#howto>.
1169 To compile this driver as a module, choose M here. The module
1170 will be called eth16i.
1173 tristate "NE2000/NE1000 support"
1174 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1177 If you have a network (Ethernet) card of this type, say Y and read
1178 the Ethernet-HOWTO, available from
1179 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1180 without a specific driver are compatible with NE2000.
1182 If you have a PCI NE2000 card however, say N here and Y to "PCI
1183 NE2000 and clone support" under "EISA, VLB, PCI and on board
1184 controllers" below. If you have a NE2000 card and are running on
1185 an MCA system (a bus system used on some IBM PS/2 computers and
1186 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1189 To compile this driver as a module, choose M here. The module
1193 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1194 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1196 The Zenith Z-Note notebook computer has a built-in network
1197 (Ethernet) card, and this is the Linux driver for it. Note that the
1198 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1199 by this driver. Read the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1203 tristate "SEEQ8005 support (EXPERIMENTAL)"
1204 depends on NET_ISA && EXPERIMENTAL
1206 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1207 is for you, read the Ethernet-HOWTO, available from
1208 <http://www.tldp.org/docs.html#howto>.
1210 To compile this driver as a module, choose M here. The module
1211 will be called seeq8005.
1214 tristate "NE/2 (ne2000 MCA version) support"
1215 depends on MCA_LEGACY
1218 If you have a network (Ethernet) card of this type, say Y and read
1219 the Ethernet-HOWTO, available from
1220 <http://www.tldp.org/docs.html#howto>.
1222 To compile this driver as a module, choose M here. The module
1226 tristate "IBM LAN Adapter/A support"
1229 This is a Micro Channel Ethernet adapter. You need to set
1230 CONFIG_MCA to use this driver. It is both available as an in-kernel
1231 driver and as a module.
1233 To compile this driver as a module, choose M here. The only
1234 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1235 will both support 16K and 32K memory windows, however a 32K window
1236 gives a better security against packet losses. Usage of multiple
1237 boards with this driver should be possible, but has not been tested
1238 up to now due to lack of hardware.
1241 tristate "IBM LAN Virtual Ethernet support"
1242 depends on PPC_PSERIES
1244 This driver supports virtual ethernet adapters on newer IBM iSeries
1245 and pSeries systems.
1247 To compile this driver as a module, choose M here. The module will
1250 source "drivers/net/ibm_newemac/Kconfig"
1253 bool "EISA, VLB, PCI and on board controllers"
1254 depends on ISA || EISA || PCI
1256 This is another class of network cards which attach directly to the
1257 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1258 available from <http://www.tldp.org/docs.html#howto>.
1260 Note that the answer to this question doesn't directly affect the
1261 kernel: saying N will just cause the configurator to skip all
1262 the questions about this class of network cards. If you say Y, you
1263 will be asked for your specific card in the following questions. If
1264 you are unsure, say Y.
1267 tristate "AMD PCnet32 PCI support"
1268 depends on NET_PCI && PCI
1272 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1273 answer Y here and read the Ethernet-HOWTO, available from
1274 <http://www.tldp.org/docs.html#howto>.
1276 To compile this driver as a module, choose M here. The module
1277 will be called pcnet32.
1280 tristate "AMD 8111 (new PCI lance) support"
1281 depends on NET_PCI && PCI
1285 If you have an AMD 8111-based PCI lance ethernet card,
1286 answer Y here and read the Ethernet-HOWTO, available from
1287 <http://www.tldp.org/docs.html#howto>.
1289 To compile this driver as a module, choose M here. The module
1290 will be called amd8111e.
1292 config ADAPTEC_STARFIRE
1293 tristate "Adaptec Starfire/DuraLAN support"
1294 depends on NET_PCI && PCI
1298 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1299 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1300 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1303 To compile this driver as a module, choose M here: the module
1304 will be called starfire. This is recommended.
1307 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1308 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1311 If you have a network (Ethernet) card of this type, say Y and read
1312 the Ethernet-HOWTO, available from
1313 <http://www.tldp.org/docs.html#howto>.
1315 To compile this driver as a module, choose M here. The module
1316 will be called ac3200.
1319 tristate "Apricot Xen-II on board Ethernet"
1320 depends on NET_PCI && ISA
1322 If you have a network (Ethernet) controller of this type, say Y and
1323 read the Ethernet-HOWTO, available from
1324 <http://www.tldp.org/docs.html#howto>.
1326 To compile this driver as a module, choose M here. The module
1327 will be called apricot.
1330 tristate "Broadcom 440x/47xx ethernet support"
1331 depends on SSB_POSSIBLE && HAS_DMA
1335 If you have a network (Ethernet) controller of this type, say Y
1336 or M and read the Ethernet-HOWTO, available from
1337 <http://www.tldp.org/docs.html#howto>.
1339 To compile this driver as a module, choose M here. The module
1342 # Auto-select SSB PCI-HOST support, if possible
1343 config B44_PCI_AUTOSELECT
1345 depends on B44 && SSB_PCIHOST_POSSIBLE
1349 # Auto-select SSB PCICORE driver, if possible
1350 config B44_PCICORE_AUTOSELECT
1352 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1353 select SSB_DRIVER_PCICORE
1358 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1362 tristate "nForce Ethernet support"
1363 depends on NET_PCI && PCI
1365 If you have a network (Ethernet) controller of this type, say Y and
1366 read the Ethernet-HOWTO, available from
1367 <http://www.tldp.org/docs.html#howto>.
1369 To compile this driver as a module, choose M here. The module
1370 will be called forcedeth.
1372 config FORCEDETH_NAPI
1373 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1374 depends on FORCEDETH && 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),
1387 tristate "CS89x0 support"
1388 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1390 Support for CS89x0 chipset based Ethernet cards. If you have a
1391 network (Ethernet) card of this type, say Y and read the
1392 Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto> as well as
1394 <file:Documentation/networking/cs89x0.txt>.
1396 To compile this driver as a module, choose M here. The module
1397 will be called cs89x0.
1400 tristate "TOSHIBA TC35815 Ethernet support"
1401 depends on NET_PCI && PCI && MIPS
1405 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1406 depends on NET_PCI && PCI
1409 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1410 card, say Y and read the Ethernet-HOWTO, available from
1411 <http://www.tldp.org/docs.html#howto>.
1413 To compile this driver as a module, choose M here. The module
1414 will be called eepro100.
1418 tristate "Intel(R) PRO/100+ support"
1419 depends on NET_PCI && PCI
1422 This driver supports Intel(R) PRO/100 family of adapters.
1423 To verify that your adapter is supported, find the board ID number
1424 on the adapter. Look for a label that has a barcode and a number
1425 in the format 123456-001 (six digits hyphen three digits).
1427 Use the above information and the Adapter & Driver ID Guide at:
1429 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1431 to identify the adapter.
1433 For the latest Intel PRO/100 network driver for Linux, see:
1435 <http://appsr.intel.com/scripts-df/support_intel.asp>
1437 More specific information on configuring the driver is in
1438 <file:Documentation/networking/e100.txt>.
1440 To compile this driver as a module, choose M here. The module
1441 will be called e100.
1444 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1445 depends on NET_PCI && EISA && EXPERIMENTAL
1448 If you have a network (Ethernet) card of this type, say Y and read
1449 the Ethernet-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>.
1452 To compile this driver as a module, choose M here. The module
1453 will be called lne390.
1456 tristate "Myson MTD-8xx PCI Ethernet support"
1457 depends on NET_PCI && PCI
1461 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1462 cards. Specifications and data at
1463 <http://www.myson.com.hk/mtd/datasheet/>.
1466 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1467 depends on NET_PCI && PCI
1470 This driver is for the National Semiconductor DP83810 series,
1471 which is used in cards from PureData, NetGear, Linksys
1472 and others, including the 83815 chip.
1473 More specific information and updates are available from
1474 <http://www.scyld.com/network/natsemi.html>.
1477 tristate "PCI NE2000 and clones support (see help)"
1478 depends on NET_PCI && PCI
1481 This driver is for NE2000 compatible PCI cards. It will not work
1482 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1483 support" below). If you have a PCI NE2000 network (Ethernet) card,
1484 say Y and read the Ethernet-HOWTO, available from
1485 <http://www.tldp.org/docs.html#howto>.
1487 This driver also works for the following NE2000 clone cards:
1488 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1489 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1490 Holtek HT80232 Holtek HT80229
1492 To compile this driver as a module, choose M here. The module
1493 will be called ne2k-pci.
1496 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1497 depends on NET_PCI && EISA && EXPERIMENTAL
1500 If you have a network (Ethernet) card of this type, say Y and read
1501 the Ethernet-HOWTO, available from
1502 <http://www.tldp.org/docs.html#howto>. Note that this driver
1503 will NOT WORK for NE3200 cards as they are completely different.
1505 To compile this driver as a module, choose M here. The module
1506 will be called ne3210.
1509 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1510 depends on NET_PCI && EISA && EXPERIMENTAL
1513 If you have a network (Ethernet) card of this type, say Y and read
1514 the Ethernet-HOWTO, available from
1515 <http://www.tldp.org/docs.html#howto>.
1517 To compile this driver as a module, choose M here. The module
1518 will be called es3210.
1521 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1522 depends on NET_PCI && PCI && EXPERIMENTAL
1526 This is a driver for the Fast Ethernet PCI network cards based on
1527 the RTL8139C+ chips. If you have one of those, say Y and read
1528 the Ethernet-HOWTO, available from
1529 <http://www.tldp.org/docs.html#howto>.
1531 To compile this driver as a module, choose M here: the module
1532 will be called 8139cp. This is recommended.
1535 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1536 depends on NET_PCI && PCI
1540 This is a driver for the Fast Ethernet PCI network cards based on
1541 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1542 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1544 To compile this driver as a module, choose M here: the module
1545 will be called 8139too. This is recommended.
1548 bool "Use PIO instead of MMIO"
1552 This instructs the driver to use programmed I/O ports (PIO) instead
1553 of PCI shared memory (MMIO). This can possibly solve some problems
1554 in case your mainboard has memory consistency issues. If unsure,
1557 config 8139TOO_TUNE_TWISTER
1558 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1561 This implements a function which might come in handy in case you
1562 are using low quality on long cabling. It is required for RealTek
1563 RTL-8139 revision K boards, and totally unused otherwise. It tries
1564 to match the transceiver to the cable characteristics. This is
1565 experimental since hardly documented by the manufacturer.
1569 bool "Support for older RTL-8129/8130 boards"
1572 This enables support for the older and uncommon RTL-8129 and
1573 RTL-8130 chips, which support MII via an external transceiver,
1574 instead of an internal one. Disabling this option will save some
1575 memory by making the code size smaller. If unsure, say Y.
1577 config 8139_OLD_RX_RESET
1578 bool "Use older RX-reset method"
1581 The 8139too driver was recently updated to contain a more rapid
1582 reset sequence, in the face of severe receive errors. This "new"
1583 RX-reset method should be adequate for all boards. But if you
1584 experience problems, you can enable this option to restore the
1585 old RX-reset behavior. If unsure, say N.
1588 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1589 depends on NET_PCI && PCI
1593 This is a driver for the R6040 Fast Ethernet MACs found in the
1594 the RDC R-321x System-on-chips.
1596 To compile this driver as a module, choose M here: the module
1597 will be called r6040. This is recommended.
1600 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1601 depends on NET_PCI && PCI
1605 This is a driver for the Fast Ethernet PCI network cards based on
1606 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1607 SiS 630 and SiS 540 chipsets.
1609 This driver also supports AMD 79C901 HomePNA so that you can use
1610 your phone line as a network cable.
1612 To compile this driver as a module, choose M here: the module
1613 will be called sis900. This is recommended.
1616 tristate "SMC EtherPower II"
1617 depends on NET_PCI && PCI
1621 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1622 which is based on the SMC83c17x (EPIC/100).
1623 More specific information and updates are available from
1624 <http://www.scyld.com/network/epic100.html>.
1627 tristate "Sundance Alta support"
1628 depends on NET_PCI && PCI
1632 This driver is for the Sundance "Alta" chip.
1633 More specific information and updates are available from
1634 <http://www.scyld.com/network/sundance.html>.
1636 config SUNDANCE_MMIO
1637 bool "Use MMIO instead of PIO"
1640 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1641 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1642 is known to solve bugs on certain chips.
1647 tristate "TI ThunderLAN support"
1648 depends on NET_PCI && (PCI || EISA)
1650 If you have a PCI Ethernet network card based on the ThunderLAN chip
1651 which is supported by this driver, say Y and read the
1652 Ethernet-HOWTO, available from
1653 <http://www.tldp.org/docs.html#howto>.
1655 Devices currently supported by this driver are Compaq Netelligent,
1656 Compaq NetFlex and Olicom cards. Please read the file
1657 <file:Documentation/networking/tlan.txt> for more details.
1659 To compile this driver as a module, choose M here. The module
1660 will be called tlan.
1662 Please email feedback to <torben.mathiasen@compaq.com>.
1665 tristate "VIA Rhine support"
1666 depends on NET_PCI && PCI
1670 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1671 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1672 Ethernet functions can also be found integrated on South Bridges
1675 To compile this driver as a module, choose M here. The module
1676 will be called via-rhine.
1678 config VIA_RHINE_MMIO
1679 bool "Use MMIO instead of PIO"
1680 depends on VIA_RHINE
1682 This instructs the driver to use PCI shared memory (MMIO) instead of
1683 programmed I/O ports (PIO). Enabling this gives an improvement in
1684 processing time in parts of the driver.
1689 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1690 depends on NET_PCI && PCI && EXPERIMENTAL
1693 This is a driver for the Fast Ethernet PCI network cards based on
1694 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1695 have one of these, say Y here.
1697 To compile this driver as a module, choose M here: the module
1698 will be called sc92031. This is recommended.
1701 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1702 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1705 TI AR7 CPMAC Ethernet support
1708 bool "Pocket and portable adapters"
1711 Cute little network (Ethernet) devices which attach to the parallel
1712 port ("pocket adapters"), commonly used with laptops. If you have
1713 one of those, say Y and read the Ethernet-HOWTO, available from
1714 <http://www.tldp.org/docs.html#howto>.
1716 If you want to plug a network (or some other) card into the PCMCIA
1717 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1718 credit card size extension cards used by all modern laptops), you
1719 need the pcmcia-cs package (location contained in the file
1720 <file:Documentation/Changes>) and you can say N here.
1722 Laptop users should read the Linux Laptop home page at
1723 <http://www.linux-on-laptops.com/> or
1724 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1726 Note that the answer to this question doesn't directly affect the
1727 kernel: saying N will just cause the configurator to skip all
1728 the questions about this class of network devices. If you say Y, you
1729 will be asked for your specific device in the following questions.
1732 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1733 depends on NET_POCKET && PARPORT && X86
1736 This is a network (Ethernet) device which attaches to your parallel
1737 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1738 available from <http://www.tldp.org/docs.html#howto>, if you
1739 want to use this. If you intend to use this driver, you should have
1740 said N to the "Parallel printer support", because the two drivers
1741 don't like each other.
1743 To compile this driver as a module, choose M here: the module
1747 tristate "D-Link DE600 pocket adapter support"
1748 depends on NET_POCKET && PARPORT
1750 This is a network (Ethernet) device which attaches to your parallel
1751 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1752 Ethernet-HOWTO, available from
1753 <http://www.tldp.org/docs.html#howto>, if you want to use
1754 this. It is possible to have several devices share a single parallel
1755 port and it is safe to compile the corresponding drivers into the
1758 To compile this driver as a module, choose M here: the module
1759 will be called de600.
1762 tristate "D-Link DE620 pocket adapter support"
1763 depends on NET_POCKET && PARPORT
1765 This is a network (Ethernet) device which attaches to your parallel
1766 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1767 Ethernet-HOWTO, available from
1768 <http://www.tldp.org/docs.html#howto>, if you want to use
1769 this. It is possible to have several devices share a single parallel
1770 port and it is safe to compile the corresponding drivers into the
1773 To compile this driver as a module, choose M here: the module
1774 will be called de620.
1777 tristate "SGI Seeq ethernet controller support"
1778 depends on SGI_HAS_SEEQ
1780 Say Y here if you have an Seeq based Ethernet network card. This is
1781 used in many Silicon Graphics machines.
1784 tristate "DEC LANCE ethernet controller support"
1785 depends on MACH_DECSTATION
1788 This driver is for the series of Ethernet controllers produced by
1789 DEC (now Compaq) based on the AMD Lance chipset, including the
1790 DEPCA series. (This chipset is better known via the NE2100 cards.)
1793 bool "Motorola 68360 ethernet controller"
1796 Say Y here if you want to use the built-in ethernet controller of
1797 the Motorola 68360 processor.
1800 bool "FEC ethernet controller (of ColdFire CPUs)"
1801 depends on M523x || M527x || M5272 || M528x || M520x
1803 Say Y here if you want to use the built-in 10/100 Fast ethernet
1804 controller on some Motorola ColdFire processors.
1807 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1810 Say Y here if you want to use the second built-in 10/100 Fast
1811 ethernet controller on some Motorola ColdFire processors.
1814 tristate "MPC52xx FEC driver"
1815 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
1819 This option enables support for the MPC5200's on-chip
1820 Fast Ethernet Controller
1821 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1823 config FEC_MPC52xx_MDIO
1824 bool "MPC52xx FEC MDIO bus driver"
1825 depends on FEC_MPC52xx
1828 The MPC5200's FEC can connect to the Ethernet either with
1829 an external MII PHY chip or 10 Mbps 7-wire interface
1830 (Motorola? industry standard).
1831 If your board uses an external PHY connected to FEC, enable this.
1832 If not sure, enable.
1833 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1836 tristate "NE2000 compatible support for H8/300"
1839 Say Y here if you want to use the NE2000 compatible
1840 controller on the Renesas H8/300 processor.
1842 source "drivers/net/fs_enet/Kconfig"
1844 endif # NET_ETHERNET
1850 menuconfig NETDEV_1000
1851 bool "Ethernet (1000 Mbit)"
1855 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1856 type of Local Area Network (LAN) in universities and companies.
1858 Say Y here to get to see options for Gigabit Ethernet drivers.
1859 This option alone does not add any kernel code.
1860 Note that drivers supporting both 100 and 1000 MBit may be listed
1861 under "Ethernet (10 or 100MBit)" instead.
1863 If you say N, all options in this submenu will be skipped and disabled.
1868 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1871 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1872 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1873 adapter. The driver allows for using the Jumbo Frame option (9000
1874 bytes/frame) however it requires that your switches can handle this
1875 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1878 To compile this driver as a module, choose M here: the
1879 module will be called acenic.
1881 config ACENIC_OMIT_TIGON_I
1882 bool "Omit support for old Tigon I based AceNICs"
1885 Say Y here if you only have Tigon II based AceNICs and want to leave
1886 out support for the older Tigon I based cards which are no longer
1887 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1888 version)). This will reduce the size of the driver object by
1889 app. 100KB. If you are not sure whether your card is a Tigon I or a
1890 Tigon II, say N here.
1892 The safe and default value for this is N.
1895 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1899 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1901 D-Link DGE-550T Gigabit Ethernet Adapter.
1902 D-Link DL2000-based Gigabit Ethernet Adapter.
1903 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1905 To compile this driver as a module, choose M here: the
1906 module will be called dl2k.
1909 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1912 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1913 adapters. For more information on how to identify your adapter, go
1914 to the Adapter & Driver ID Guide at:
1916 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1918 For general information and support, go to the Intel support
1921 <http://support.intel.com>
1923 More specific information on configuring the driver is in
1924 <file:Documentation/networking/e1000.txt>.
1926 To compile this driver as a module, choose M here. The module
1927 will be called e1000.
1930 bool "Use Rx Polling (NAPI)"
1933 NAPI is a new driver API designed to reduce CPU and interrupt load
1934 when the driver is receiving lots of packets from the card. It is
1935 still somewhat experimental and thus not yet enabled by default.
1937 If your estimated Rx load is 10kpps or more, or if the card will be
1938 deployed on potentially unfriendly networks (e.g. in a firewall),
1943 config E1000_DISABLE_PACKET_SPLIT
1944 bool "Disable Packet Split for PCI express adapters"
1947 Say Y here if you want to use the legacy receive path for PCI express
1953 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1954 depends on PCI && (!SPARC32 || BROKEN)
1956 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1957 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1958 use the regular e1000 driver For more information on how to
1959 identify your adapter, go to the Adapter & Driver ID Guide at:
1961 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1963 For general information and support, go to the Intel support
1966 <http://support.intel.com>
1968 To compile this driver as a module, choose M here. The module
1969 will be called e1000e.
1972 tristate "IP1000 Gigabit Ethernet support"
1973 depends on PCI && EXPERIMENTAL
1976 This driver supports IP1000 gigabit Ethernet cards.
1978 To compile this driver as a module, choose M here: the module
1979 will be called ipg. This is recommended.
1982 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
1985 This driver supports Intel(R) 82575 gigabit ethernet family of
1986 adapters. For more information on how to identify your adapter, go
1987 to the Adapter & Driver ID Guide at:
1989 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1991 For general information and support, go to the Intel support
1994 <http://support.intel.com>
1996 More specific information on configuring the driver is in
1997 <file:Documentation/networking/e1000.txt>.
1999 To compile this driver as a module, choose M here. The module
2003 bool "Use software LRO"
2004 depends on IGB && INET
2007 Say Y here if you want to use large receive offload.
2011 source "drivers/net/ixp2000/Kconfig"
2014 tristate "MyriCOM Gigabit Ethernet support"
2017 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2019 To compile this driver as a module, choose M here: the module
2020 will be called myri_sbus. This is recommended.
2023 tristate "National Semiconductor DP83820 support"
2026 This is a driver for the National Semiconductor DP83820 series
2027 of gigabit ethernet MACs. Cards using this chipset include
2028 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2029 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2033 tristate "Packet Engines Hamachi GNIC-II support"
2037 If you have a Gigabit Ethernet card of this type, say Y and read
2038 the Ethernet-HOWTO, available from
2039 <http://www.tldp.org/docs.html#howto>.
2041 To compile this driver as a module, choose M here. The module will be
2045 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2046 depends on PCI && EXPERIMENTAL
2049 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2050 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2051 used by the Beowulf Linux cluster project. See
2052 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2053 information about this driver in particular and Beowulf in general.
2055 To compile this driver as a module, choose M here: the module
2056 will be called yellowfin. This is recommended.
2059 tristate "Realtek 8169 gigabit ethernet support"
2063 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2065 To compile this driver as a module, choose M here: the module
2066 will be called r8169. This is recommended.
2070 depends on R8169 && VLAN_8021Q
2072 Say Y here for the r8169 driver to support the functions required
2073 by the kernel 802.1Q code.
2078 tristate "SB1250 Gigabit Ethernet support"
2079 depends on SIBYTE_SB1xxx_SOC
2082 This driver supports Gigabit Ethernet interfaces based on the
2083 Broadcom SiByte family of System-On-a-Chip parts. They include
2084 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2087 To compile this driver as a module, choose M here: the module
2088 will be called sb1250-mac.
2091 tristate "SiS190/SiS191 gigabit ethernet support"
2096 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2097 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2098 appear in lan on motherboard designs which are based on SiS 965
2099 and SiS 966 south bridge.
2101 To compile this driver as a module, choose M here: the module
2102 will be called sis190. This is recommended.
2105 tristate "New SysKonnect GigaEthernet support"
2109 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2110 and related Gigabit Ethernet adapters. It is a new smaller driver
2111 with better performance and more complete ethtool support.
2113 It does not support the link failover and network management
2114 features that "portable" vendor supplied sk98lin driver does.
2116 This driver supports adapters based on the original Yukon chipset:
2117 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2118 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2120 It does not support the newer Yukon2 chipset: a separate driver,
2121 sky2, is provided for Yukon2-based adapters.
2123 To compile this driver as a module, choose M here: the module
2124 will be called skge. This is recommended.
2127 bool "Debugging interface"
2128 depends on SKGE && DEBUG_FS
2130 This option adds the ability to dump driver state for debugging.
2131 The file debugfs/skge/ethX displays the state of the internal
2132 transmit and receive rings.
2137 tristate "SysKonnect Yukon2 support"
2141 This driver supports Gigabit Ethernet adapters based on the
2142 Marvell Yukon 2 chipset:
2143 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2144 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2146 There is companion driver for the older Marvell Yukon and
2147 Genesis based adapters: skge.
2149 To compile this driver as a module, choose M here: the module
2150 will be called sky2. This is recommended.
2153 bool "Debugging interface"
2154 depends on SKY2 && DEBUG_FS
2156 This option adds the ability to dump driver state for debugging.
2157 The file debugfs/sky2/ethX displays the state of the internal
2158 transmit and receive rings.
2163 tristate "VIA Velocity support"
2169 If you have a VIA "Velocity" based network card say Y here.
2171 To compile this driver as a module, choose M here. The module
2172 will be called via-velocity.
2175 tristate "Broadcom Tigon3 support"
2179 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2181 To compile this driver as a module, choose M here: the module
2182 will be called tg3. This is recommended.
2185 tristate "Broadcom NetXtremeII support"
2190 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2192 To compile this driver as a module, choose M here: the module
2193 will be called bnx2. This is recommended.
2196 tristate "Spider Gigabit Ethernet driver"
2197 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2200 This driver supports the Gigabit Ethernet chips present on the
2201 Cell Processor-Based Blades from IBM.
2204 tristate "Tundra TSI108 gigabit Ethernet support"
2205 depends on TSI108_BRIDGE
2207 This driver supports Tundra TSI108 gigabit Ethernet ports.
2208 To compile this driver as a module, choose M here: the module
2209 will be called tsi108_eth.
2212 tristate "PS3 Gigabit Ethernet driver"
2214 select PS3_SYS_MANAGER
2216 This driver supports the network device on the PS3 game
2217 console. This driver has built-in support for Ethernet.
2219 To compile this driver as a module, choose M here: the
2220 module will be called ps3_gelic.
2222 config GELIC_WIRELESS
2223 bool "PS3 Wireless support"
2224 depends on GELIC_NET
2227 This option adds the support for the wireless feature of PS3.
2228 If you have the wireless-less model of PS3 or have no plan to
2229 use wireless feature, disabling this option saves memory. As
2230 the driver automatically distinguishes the models, you can
2231 safely enable this option even if you have a wireless-less model.
2233 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2234 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2235 depends on GELIC_WIRELESS
2237 This option retains the obsolete private interface to pass
2238 the PSK from user space programs to the driver. The PSK
2239 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2240 (WPA-Personal) environment.
2241 If WPA[2]-PSK is used and you need to use old programs that
2242 support only this old interface, say Y. Otherwise N.
2247 tristate "Gianfar Ethernet"
2252 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2253 and MPC86xx family of chips, and the FEC on the 8540.
2256 tristate "Freescale QE Gigabit Ethernet"
2257 depends on QUICC_ENGINE
2260 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2261 which is available on some Freescale SOCs.
2263 config UGETH_MAGIC_PACKET
2264 bool "Magic Packet detection support"
2267 config UGETH_FILTERING
2268 bool "Mac address filtering support"
2271 config UGETH_TX_ON_DEMAND
2272 bool "Transmit on Demand support"
2276 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2277 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2280 This driver supports the gigabit ethernet MACs in the
2281 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2282 in the Marvell Orion ARM SoC family.
2284 Some boards that use the Discovery chipset are the Momenco
2285 Ocelot C and Jaguar ATX and Pegasos II.
2288 tristate "QLogic QLA3XXX Network Driver Support"
2291 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2293 To compile this driver as a module, choose M here: the module
2294 will be called qla3xxx.
2297 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2298 depends on PCI && EXPERIMENTAL
2302 This driver supports the Attansic L1 gigabit ethernet adapter.
2304 To compile this driver as a module, choose M here. The module
2305 will be called atl1.
2310 # 10 Gigabit Ethernet
2313 menuconfig NETDEV_10000
2314 bool "Ethernet (10000 Mbit)"
2318 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2319 This option alone does not add any kernel code.
2321 If you say N, all options in this submenu will be skipped and disabled.
2326 tristate "Chelsio 10Gb Ethernet support"
2330 This driver supports Chelsio gigabit and 10-gigabit
2331 Ethernet cards. More information about adapter features and
2332 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2334 For general information about Chelsio and our products, visit
2335 our website at <http://www.chelsio.com>.
2337 For customer support, please visit our customer support page at
2338 <http://www.chelsio.com/support.htm>.
2340 Please send feedback to <linux-bugs@chelsio.com>.
2342 To compile this driver as a module, choose M here: the module
2343 will be called cxgb.
2345 config CHELSIO_T1_1G
2346 bool "Chelsio gigabit Ethernet support"
2347 depends on CHELSIO_T1
2349 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2350 are using only 10G cards say 'N' here.
2353 tristate "Chelsio Communications T3 10Gb Ethernet support"
2354 depends on PCI && INET
2358 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2361 For general information about Chelsio and our products, visit
2362 our website at <http://www.chelsio.com>.
2364 For customer support, please visit our customer support page at
2365 <http://www.chelsio.com/support.htm>.
2367 Please send feedback to <linux-bugs@chelsio.com>.
2369 To compile this driver as a module, choose M here: the module
2370 will be called cxgb3.
2373 tristate "eHEA Ethernet support"
2374 depends on IBMEBUS && INET && SPARSEMEM
2377 This driver supports the IBM pSeries eHEA ethernet adapter.
2379 To compile the driver as a module, choose M here. The module
2380 will be called ehea.
2383 tristate "Intel(R) 10GbE PCI Express adapters support"
2384 depends on PCI && INET
2387 This driver supports Intel(R) 10GbE PCI Express family of
2388 adapters. For more information on how to identify your adapter, go
2389 to the Adapter & Driver ID Guide at:
2391 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2393 For general information and support, go to the Intel support
2396 <http://support.intel.com>
2398 To compile this driver as a module, choose M here. The module
2399 will be called ixgbe.
2402 tristate "Intel(R) PRO/10GbE support"
2405 This driver supports Intel(R) PRO/10GbE family of adapters for
2406 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2407 instead. For more information on how to identify your adapter, go
2408 to the Adapter & Driver ID Guide at:
2410 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2412 For general information and support, go to the Intel support
2415 <http://support.intel.com>
2417 More specific information on configuring the driver is in
2418 <file:Documentation/networking/ixgb.txt>.
2420 To compile this driver as a module, choose M here. The module
2421 will be called ixgb.
2424 tristate "S2IO 10Gbe XFrame NIC"
2427 This driver supports the 10Gbe XFrame NIC of S2IO.
2428 More specific information on configuring the driver is in
2429 <file:Documentation/networking/s2io.txt>.
2432 tristate "Myricom Myri-10G Ethernet support"
2433 depends on PCI && INET
2438 This driver supports Myricom Myri-10G Dual Protocol interface in
2439 Ethernet mode. If the eeprom on your board is not recent enough,
2440 you will need a newer firmware image.
2441 You may get this image or more information, at:
2443 <http://www.myri.com/scs/download-Myri10GE.html>
2445 To compile this driver as a module, choose M here. The module
2446 will be called myri10ge.
2449 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2452 This enables the support for NetXen's Gigabit Ethernet card.
2455 tristate "Sun Neptune 10Gbit Ethernet support"
2458 This enables support for cards based upon Sun's
2462 tristate "PA Semi 1/10Gbit MAC"
2463 depends on PPC_PASEMI && PCI
2467 This driver supports the on-chip 1/10Gbit Ethernet controller on
2468 PA Semi's PWRficient line of chips.
2476 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2477 depends on MLX4_CORE
2480 This option causes debugging code to be compiled into the
2481 mlx4_core driver. The output can be turned on via the
2482 debug_level module parameter (which can also be set after
2483 the driver is loaded through sysfs).
2486 tristate "Tehuti Networks 10G Ethernet"
2489 Tehuti Networks 10G Ethernet NIC
2492 tristate "Broadcom NetXtremeII 10Gb support"
2497 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2498 To compile this driver as a module, choose M here: the module
2499 will be called bnx2x. This is recommended.
2501 source "drivers/net/sfc/Kconfig"
2503 endif # NETDEV_10000
2505 source "drivers/net/tokenring/Kconfig"
2507 source "drivers/net/wireless/Kconfig"
2509 source "drivers/net/usb/Kconfig"
2511 source "drivers/net/pcmcia/Kconfig"
2513 source "drivers/net/wan/Kconfig"
2515 source "drivers/atm/Kconfig"
2517 source "drivers/s390/net/Kconfig"
2519 config XEN_NETDEV_FRONTEND
2520 tristate "Xen network device frontend driver"
2524 The network device frontend driver allows the kernel to
2525 access network devices exported exported by a virtual
2526 machine containing a physical network device driver. The
2527 frontend driver is intended for unprivileged guest domains;
2528 if you are compiling a kernel for a Xen guest, you almost
2529 certainly want to enable this.
2532 tristate "iSeries Virtual Ethernet driver support"
2533 depends on PPC_ISERIES
2536 tristate "RapidIO Ethernet over messaging driver support"
2539 config RIONET_TX_SIZE
2540 int "Number of outbound queue entries"
2544 config RIONET_RX_SIZE
2545 int "Number of inbound queue entries"
2550 bool "FDDI driver support"
2551 depends on (PCI || EISA || TC)
2553 Fiber Distributed Data Interface is a high speed local area network
2554 design; essentially a replacement for high speed Ethernet. FDDI can
2555 run over copper or fiber. If you are connected to such a network and
2556 want a driver for the FDDI card in your computer, say Y here (and
2557 then also Y to the driver for your FDDI card, below). Most people
2561 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2562 depends on FDDI && (PCI || EISA || TC)
2564 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2565 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2566 to a local FDDI network.
2568 To compile this driver as a module, choose M here: the module
2569 will be called defxx. If unsure, say N.
2573 prompt "Use MMIO instead of PIO" if PCI || EISA
2575 default n if PCI || EISA
2578 This instructs the driver to use EISA or PCI memory-mapped I/O
2579 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2580 Enabling this gives an improvement in processing time in parts
2581 of the driver, but it may cause problems with EISA (DEFEA)
2582 adapters. TURBOchannel does not have the concept of I/O ports,
2583 so MMIO is always used for these (DEFTA) adapters.
2588 tristate "SysKonnect FDDI PCI support"
2589 depends on FDDI && PCI
2592 Say Y here if you have a SysKonnect FDDI PCI adapter.
2593 The following adapters are supported by this driver:
2594 - SK-5521 (SK-NET FDDI-UP)
2595 - SK-5522 (SK-NET FDDI-UP DAS)
2596 - SK-5541 (SK-NET FDDI-FP)
2597 - SK-5543 (SK-NET FDDI-LP)
2598 - SK-5544 (SK-NET FDDI-LP DAS)
2599 - SK-5821 (SK-NET FDDI-UP64)
2600 - SK-5822 (SK-NET FDDI-UP64 DAS)
2601 - SK-5841 (SK-NET FDDI-FP64)
2602 - SK-5843 (SK-NET FDDI-LP64)
2603 - SK-5844 (SK-NET FDDI-LP64 DAS)
2604 - Netelligent 100 FDDI DAS Fibre SC
2605 - Netelligent 100 FDDI SAS Fibre SC
2606 - Netelligent 100 FDDI DAS UTP
2607 - Netelligent 100 FDDI SAS UTP
2608 - Netelligent 100 FDDI SAS Fibre MIC
2610 Read <file:Documentation/networking/skfp.txt> for information about
2613 Questions concerning this driver can be addressed to:
2614 <linux@syskonnect.de>
2616 To compile this driver as a module, choose M here: the module
2617 will be called skfp. This is recommended.
2620 bool "HIPPI driver support (EXPERIMENTAL)"
2621 depends on EXPERIMENTAL && INET && PCI
2623 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2624 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2625 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2626 single-mode). HIPPI networks are commonly used for clusters and to
2627 connect to super computers. If you are connected to a HIPPI network
2628 and have a HIPPI network card in your computer that you want to use
2629 under Linux, say Y here (you must also remember to enable the driver
2630 for your HIPPI card below). Most people will say N here.
2633 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2634 depends on HIPPI && PCI
2636 Say Y here if this is your PCI HIPPI network card.
2638 To compile this driver as a module, choose M here: the module
2639 will be called rrunner. If unsure, say N.
2641 config ROADRUNNER_LARGE_RINGS
2642 bool "Use large TX/RX rings (EXPERIMENTAL)"
2643 depends on ROADRUNNER
2645 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2646 of additional memory to allow for fastest operation, both for
2647 transmitting and receiving. This memory cannot be used by any other
2648 kernel code or by user space programs. Say Y here only if you have
2652 tristate "PLIP (parallel port) support"
2655 PLIP (Parallel Line Internet Protocol) is used to create a
2656 reasonably fast mini network consisting of two (or, rarely, more)
2657 local machines. A PLIP link from a Linux box is a popular means to
2658 install a Linux distribution on a machine which doesn't have a
2659 CD-ROM drive (a minimal system has to be transferred with floppies
2660 first). The kernels on both machines need to have this PLIP option
2661 enabled for this to work.
2663 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2664 ports (the connectors at the computers with 25 holes) are connected
2665 with "null printer" or "Turbo Laplink" cables which can transmit 4
2666 bits at a time (mode 0) or with special PLIP cables, to be used on
2667 bidirectional parallel ports only, which can transmit 8 bits at a
2668 time (mode 1); you can find the wiring of these cables in
2669 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2670 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2671 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2672 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2673 and winsock or NCSA's telnet.
2675 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2676 as the NET-3-HOWTO, both available from
2677 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2678 protocol has been changed and this PLIP driver won't work together
2679 with the PLIP support in Linux versions 1.0.x. This option enlarges
2680 your kernel by about 8 KB.
2682 To compile this driver as a module, choose M here. The module
2683 will be called plip. If unsure, say Y or M, in case you buy
2687 tristate "PPP (point-to-point protocol) support"
2690 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2691 the same purpose: sending Internet traffic over telephone (and other
2692 serial) lines. Ask your access provider if they support it, because
2693 otherwise you can't use it; most Internet access providers these
2694 days support PPP rather than SLIP.
2696 To use PPP, you need an additional program called pppd as described
2697 in the PPP-HOWTO, available at
2698 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2699 the version of pppd recommended in <file:Documentation/Changes>.
2700 The PPP option enlarges your kernel by about 16 KB.
2702 There are actually two versions of PPP: the traditional PPP for
2703 asynchronous lines, such as regular analog phone lines, and
2704 synchronous PPP which can be used over digital ISDN lines for
2705 example. If you want to use PPP over phone lines or other
2706 asynchronous serial lines, you need to say Y (or M) here and also to
2707 the next option, "PPP support for async serial ports". For PPP over
2708 synchronous lines, you should say Y (or M) here and to "Support
2709 synchronous PPP", below.
2711 If you said Y to "Version information on all symbols" above, then
2712 you cannot compile the PPP driver into the kernel; you can then only
2713 compile it as a module. To compile this driver as a module, choose M
2714 here. The module will be called ppp_generic.
2716 config PPP_MULTILINK
2717 bool "PPP multilink support (EXPERIMENTAL)"
2718 depends on PPP && EXPERIMENTAL
2720 PPP multilink is a protocol (defined in RFC 1990) which allows you
2721 to combine several (logical or physical) lines into one logical PPP
2722 connection, so that you can utilize your full bandwidth.
2724 This has to be supported at the other end as well and you need a
2725 version of the pppd daemon which understands the multilink protocol.
2730 bool "PPP filtering"
2733 Say Y here if you want to be able to filter the packets passing over
2734 PPP interfaces. This allows you to control which packets count as
2735 activity (i.e. which packets will reset the idle timer or bring up
2736 a demand-dialed link) and which packets are to be dropped entirely.
2737 You need to say Y here if you wish to use the pass-filter and
2738 active-filter options to pppd.
2743 tristate "PPP support for async serial ports"
2747 Say Y (or M) here if you want to be able to use PPP over standard
2748 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2749 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2752 To compile this driver as a module, choose M here.
2757 tristate "PPP support for sync tty ports"
2760 Say Y (or M) here if you want to be able to use PPP over synchronous
2761 (HDLC) tty devices, such as the SyncLink adapter. These devices
2762 are often used for high-speed leased lines like T1/E1.
2764 To compile this driver as a module, choose M here.
2767 tristate "PPP Deflate compression"
2772 Support for the Deflate compression method for PPP, which uses the
2773 Deflate algorithm (the same algorithm that gzip uses) to compress
2774 each PPP packet before it is sent over the wire. The machine at the
2775 other end of the PPP link (usually your ISP) has to support the
2776 Deflate compression method as well for this to be useful. Even if
2777 they don't support it, it is safe to say Y here.
2779 To compile this driver as a module, choose M here.
2782 tristate "PPP BSD-Compress compression"
2785 Support for the BSD-Compress compression method for PPP, which uses
2786 the LZW compression method to compress each PPP packet before it is
2787 sent over the wire. The machine at the other end of the PPP link
2788 (usually your ISP) has to support the BSD-Compress compression
2789 method as well for this to be useful. Even if they don't support it,
2790 it is safe to say Y here.
2792 The PPP Deflate compression method ("PPP Deflate compression",
2793 above) is preferable to BSD-Compress, because it compresses better
2796 Note that the BSD compression code will always be compiled as a
2797 module; it is called bsd_comp and will show up in the directory
2798 modules once you have said "make modules". If unsure, say N.
2801 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2802 depends on PPP && EXPERIMENTAL
2808 Support for the MPPE Encryption protocol, as employed by the
2809 Microsoft Point-to-Point Tunneling Protocol.
2811 See http://pptpclient.sourceforge.net/ for information on
2812 configuring PPTP clients and servers to utilize this method.
2815 tristate "PPP over Ethernet (EXPERIMENTAL)"
2816 depends on EXPERIMENTAL && PPP
2818 Support for PPP over Ethernet.
2820 This driver requires the latest version of pppd from the CVS
2821 repository at cvs.samba.org. Alternatively, see the
2822 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2823 which contains instruction on how to use this driver (under
2824 the heading "Kernel mode PPPoE").
2827 tristate "PPP over ATM"
2828 depends on ATM && PPP
2830 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2831 This implementation does not yet comply with section 8 of RFC2364,
2832 which can lead to bad results if the ATM peer loses state and
2833 changes its encapsulation unilaterally.
2836 tristate "PPP over L2TP (EXPERIMENTAL)"
2837 depends on EXPERIMENTAL && PPP && INET
2839 Support for PPP-over-L2TP socket family. L2TP is a protocol
2840 used by ISPs and enterprises to tunnel PPP traffic over UDP
2841 tunnels. L2TP is replacing PPTP for VPN uses.
2843 This kernel component handles only L2TP data packets: a
2844 userland daemon handles L2TP the control protocol (tunnel
2845 and session setup). One such daemon is OpenL2TP
2846 (http://openl2tp.sourceforge.net/).
2849 tristate "SLIP (serial line) support"
2851 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2852 connect to your Internet service provider or to connect to some
2853 other local Unix box or if you want to configure your Linux box as a
2854 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2855 Internet Protocol) is a protocol used to send Internet traffic over
2856 serial connections such as telephone lines or null modem cables;
2857 nowadays, the protocol PPP is more commonly used for this same
2860 Normally, your access provider has to support SLIP in order for you
2861 to be able to use it, but there is now a SLIP emulator called SLiRP
2862 around (available from
2863 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2864 allows you to use SLIP over a regular dial up shell connection. If
2865 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2866 NET-3-HOWTO, available from
2867 <http://www.tldp.org/docs.html#howto>, explains how to
2868 configure SLIP. Note that you don't need this option if you just
2869 want to run term (term is a program which gives you almost full
2870 Internet connectivity if you have a regular dial up shell account on
2871 some Internet connected Unix computer. Read
2872 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2873 support will enlarge your kernel by about 4 KB. If unsure, say N.
2875 To compile this driver as a module, choose M here. The module
2876 will be called slip.
2878 config SLIP_COMPRESSED
2879 bool "CSLIP compressed headers"
2883 This protocol is faster than SLIP because it uses compression on the
2884 TCP/IP headers (not on the data itself), but it has to be supported
2885 on both ends. Ask your access provider if you are not sure and
2886 answer Y, just in case. You will still be able to use plain SLIP. If
2887 you plan to use SLiRP, the SLIP emulator (available from
2888 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2889 allows you to use SLIP over a regular dial up shell connection, you
2890 definitely want to say Y here. The NET-3-HOWTO, available from
2891 <http://www.tldp.org/docs.html#howto>, explains how to configure
2892 CSLIP. This won't enlarge your kernel.
2897 This option enables Van Jacobsen serial line header compression
2901 bool "Keepalive and linefill"
2904 Adds additional capabilities to the SLIP driver to support the
2905 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2908 config SLIP_MODE_SLIP6
2909 bool "Six bit SLIP encapsulation"
2912 Just occasionally you may need to run IP over hostile serial
2913 networks that don't pass all control characters or are only seven
2914 bit. Saying Y here adds an extra mode you can use with SLIP:
2915 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2916 the serial device. Naturally, this has to be supported at the other
2917 end of the link as well. It's good enough, for example, to run IP
2918 over the async ports of a Camtec JNT Pad. If unsure, say N.
2921 bool "Fibre Channel driver support"
2922 depends on SCSI && PCI
2924 Fibre Channel is a high speed serial protocol mainly used to connect
2925 large storage devices to the computer; it is compatible with and
2926 intended to replace SCSI.
2928 If you intend to use Fibre Channel, you need to have a Fibre channel
2929 adaptor card in your computer; say Y here and to the driver for your
2930 adaptor below. You also should have said Y to "SCSI support" and
2931 "SCSI generic support".
2934 tristate "Network console logging support (EXPERIMENTAL)"
2935 depends on EXPERIMENTAL
2937 If you want to log kernel messages over the network, enable this.
2938 See <file:Documentation/networking/netconsole.txt> for details.
2940 config NETCONSOLE_DYNAMIC
2941 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
2942 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
2945 This option enables the ability to dynamically reconfigure target
2946 parameters (interface, IP addresses, port numbers, MAC addresses)
2947 at runtime through a userspace interface exported using configfs.
2948 See <file:Documentation/networking/netconsole.txt> for details.
2954 bool "Netpoll traffic trapping"
2958 config NET_POLL_CONTROLLER
2962 tristate "Virtio network driver (EXPERIMENTAL)"
2963 depends on EXPERIMENTAL && VIRTIO
2965 This is the virtual network driver for virtio. It can be used with
2966 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.