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 tristate "Apollo 3c505 support"
332 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
333 If you don't have one made for Apollos, you can use one from a PC,
334 except that your Apollo won't be able to boot from it (because the
335 code in the ROM will be for a PC).
338 bool "Macintosh NS 8390 based ethernet cards"
342 If you want to include a driver to support Nubus or LC-PDS
343 Ethernet cards using an NS8390 chipset or its equivalent, say Y
344 and read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
348 tristate "Macintosh CS89x0 based ethernet cards"
351 Support for CS89x0 chipset based Ethernet cards. If you have a
352 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
353 read the Ethernet-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>.
356 To compile this driver as a module, choose M here. This module will
360 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
363 Support for NatSemi SONIC based Ethernet devices. This includes
364 the onboard Ethernet in many Quadras as well as some LC-PDS,
365 a few Nubus and all known Comm Slot Ethernet cards. If you have
366 one of these say Y and read the Ethernet-HOWTO, available from
367 <http://www.tldp.org/docs.html#howto>.
369 To compile this driver as a module, choose M here. This module will
373 bool "Macintosh (AV) onboard MACE ethernet"
377 Support for the onboard AMD 79C940 MACE Ethernet controller used in
378 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
379 say Y and read the Ethernet-HOWTO, available from
380 <http://www.tldp.org/docs.html#howto>.
383 tristate "MVME147 (Lance) Ethernet support"
387 Support for the on-board Ethernet interface on the Motorola MVME147
388 single-board computer. 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 "MVME16x Ethernet support"
396 This is the driver for the Ethernet interface on the Motorola
397 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
398 driver for this chip in your kernel.
399 To compile this driver as a module, choose M here.
402 tristate "BVME6000 Ethernet support"
405 This is the driver for the Ethernet interface on BVME4000 and
406 BVME6000 VME boards. Say Y here to include the driver for this chip
408 To compile this driver as a module, choose M here.
411 tristate "Atari Lance support"
414 Say Y to include support for several Atari Ethernet adapters based
415 on the AMD Lance chipset: RieblCard (with or without battery), or
416 PAMCard VME (also the version by Rhotron, with different addresses).
419 tristate "Sun3/Sun3x on-board LANCE support"
420 depends on SUN3 || SUN3X
422 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
423 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
424 here to compile in the Linux driver for this and enable Ethernet.
425 General Linux information on the Sun 3 and 3x series (now
427 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
429 If you're not building a kernel for a Sun 3, say N.
432 bool "Sun3 on-board Intel 82586 support"
435 This driver enables support for the on-board Intel 82586 based
436 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
437 that this driver does not support 82586-based adapters on additional
441 bool "HP on-board LANCE support"
445 If you want to use the builtin "LANCE" Ethernet controller on an
446 HP300 machine, say Y here.
449 tristate "Lasi ethernet"
452 Say Y here to support the builtin Intel 82596 ethernet controller
453 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
456 tristate "SNI RM ethernet"
457 depends on NET_ETHERNET && SNI_RM
459 Say Y here to support the on-board Intel 82596 ethernet controller
460 built into SNI RM machines.
463 tristate "Korina (IDT RC32434) Ethernet support"
464 depends on NET_ETHERNET && MIKROTIK_RB532
466 If you have a Mikrotik RouterBoard 500 or IDT RC32434
467 based system say Y. Otherwise say N.
469 config MIPS_JAZZ_SONIC
470 tristate "MIPS JAZZ onboard SONIC Ethernet support"
473 This is the driver for the onboard card of MIPS Magnum 4000,
474 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
476 config MIPS_AU1X00_ENET
477 bool "MIPS AU1000 Ethernet support"
478 depends on SOC_AU1X00
482 If you have an Alchemy Semi AU1X00 based system
483 say Y. Otherwise, say N.
486 bool "SGI IOC3 Ethernet"
487 depends on PCI && SGI_IP27
491 If you have a network (Ethernet) card of this type, say Y and read
492 the Ethernet-HOWTO, available from
493 <http://www.tldp.org/docs.html#howto>.
496 tristate "MIPS simulator Network device"
499 The MIPSNET device is a simple Ethernet network device which is
500 emulated by the MIPS Simulator.
501 If you are not using a MIPSsim or are unsure, say N.
503 config SGI_O2MACE_ETH
504 tristate "SGI O2 MACE Fast Ethernet support"
505 depends on SGI_IP32=y
508 tristate "National DP83902AV support"
512 Support for cards based on the National Semiconductor DP83902AV
513 ST-NIC Serial Network Interface Controller for Twisted Pair. This
514 is a 10Mbit/sec Ethernet controller. Product overview and specs at
515 <http://www.national.com/pf/DP/DP83902A.html>.
520 tristate "Renesas SuperH Ethernet support"
521 depends on SUPERH && \
522 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)
528 Renesas SuperH Ethernet device driver.
529 This driver support SH7710 and SH7712.
532 tristate "Sun LANCE support"
536 This driver supports the "le" interface present on all 32-bit Sparc
537 systems, on some older Ultra systems and as an Sbus option. These
538 cards are based on the AMD Lance chipset, which is better known
539 via the NE2100 cards.
541 To compile this driver as a module, choose M here: the module
542 will be called sunlance.
545 tristate "Sun Happy Meal 10/100baseT support"
546 depends on SBUS || PCI
549 This driver supports the "hme" interface present on most Ultra
550 systems and as an option on older Sbus systems. This driver supports
551 both PCI and Sbus devices. This driver also supports the "qfe" quad
552 100baseT device available in both PCI and Sbus configurations.
554 To compile this driver as a module, choose M here: the module
555 will be called sunhme.
558 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
559 depends on SBUS && EXPERIMENTAL
562 This driver supports the "be" interface available as an Sbus option.
563 This is Sun's older 100baseT Ethernet device.
565 To compile this driver as a module, choose M here: the module
566 will be called sunbmac.
569 tristate "Sun QuadEthernet support"
573 This driver supports the "qe" 10baseT Ethernet device, available as
574 an Sbus option. Note that this is not the same as Quad FastEthernet
575 "qfe" which is supported by the Happy Meal driver instead.
577 To compile this driver as a module, choose M here: the module
578 will be called sunqe.
581 tristate "Sun GEM support"
585 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
586 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
589 tristate "Sun Cassini support"
593 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
594 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
597 tristate "Sun Virtual Network support"
600 Support for virtual network devices under Sun Logical Domains.
602 config NET_VENDOR_3COM
604 depends on ISA || EISA || MCA || PCI
606 If you have a network (Ethernet) card belonging to this class, say Y
607 and read the Ethernet-HOWTO, available from
608 <http://www.tldp.org/docs.html#howto>.
610 Note that the answer to this question doesn't directly affect the
611 kernel: saying N will just cause the configurator to skip all
612 the questions about 3COM cards. If you say Y, you will be asked for
613 your specific card in the following questions.
616 tristate "3c501 \"EtherLink\" support"
617 depends on NET_VENDOR_3COM && ISA
619 If you have a network (Ethernet) card of this type, say Y and read
620 the Ethernet-HOWTO, available from
621 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
622 new card, since the 3c501 is slow, broken, and obsolete: you will
623 have problems. Some people suggest to ping ("man ping") a nearby
624 machine every minute ("man cron") when using this card.
626 To compile this driver as a module, choose M here. The module
627 will be called 3c501.
630 tristate "3c503 \"EtherLink II\" support"
631 depends on NET_VENDOR_3COM && ISA
634 If you have a network (Ethernet) card of this type, say Y and read
635 the Ethernet-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>.
638 To compile this driver as a module, choose M here. The module
639 will be called 3c503.
642 tristate "3c505 \"EtherLink Plus\" support"
643 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
645 Information about this network (Ethernet) card can be found in
646 <file:Documentation/networking/3c505.txt>. If you have a card of
647 this type, say Y and read the Ethernet-HOWTO, available from
648 <http://www.tldp.org/docs.html#howto>.
650 To compile this driver as a module, choose M here. The module
651 will be called 3c505.
654 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
655 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
657 If you have a network (Ethernet) card of this type, say Y and read
658 the Ethernet-HOWTO, available from
659 <http://www.tldp.org/docs.html#howto>.
661 To compile this driver as a module, choose M here. The module
662 will be called 3c507.
665 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
666 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
668 If you have a network (Ethernet) card belonging to the 3Com
669 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
670 from <http://www.tldp.org/docs.html#howto>.
672 If your card is not working you may need to use the DOS
673 setup disk to disable Plug & Play mode, and to select the default
676 To compile this driver as a module, choose M here. The module
677 will be called 3c509.
680 tristate "3c515 ISA \"Fast EtherLink\""
681 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
683 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
684 network card, say Y and read the Ethernet-HOWTO, available from
685 <http://www.tldp.org/docs.html#howto>.
687 To compile this driver as a module, choose M here. The module
688 will be called 3c515.
691 tristate "3c523 \"EtherLink/MC\" support"
692 depends on NET_VENDOR_3COM && MCA_LEGACY
694 If you have a network (Ethernet) card of this type, say Y and read
695 the Ethernet-HOWTO, available from
696 <http://www.tldp.org/docs.html#howto>.
698 To compile this driver as a module, choose M here. The module
699 will be called 3c523.
702 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
703 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
705 If you have a network (Ethernet) card of this type, say Y and read
706 the Ethernet-HOWTO, available from
707 <http://www.tldp.org/docs.html#howto>.
709 To compile this driver as a module, choose M here. The module
710 will be called 3c527.
713 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
714 depends on NET_VENDOR_3COM && (PCI || EISA)
717 This option enables driver support for a large number of 10Mbps and
718 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
720 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
721 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
722 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
723 "Tornado" (3c905) PCI
724 "Hurricane" (3c555/3cSOHO) PCI
726 If you have such a card, say Y and read the Ethernet-HOWTO,
727 available from <http://www.tldp.org/docs.html#howto>. More
728 specific information is in
729 <file:Documentation/networking/vortex.txt> and in the comments at
730 the beginning of <file:drivers/net/3c59x.c>.
732 To compile this support as a module, choose M here.
735 tristate "3cr990 series \"Typhoon\" support"
736 depends on NET_VENDOR_3COM && PCI
739 This option enables driver support for the 3cr990 series of cards:
741 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
742 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
743 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
745 If you have a network (Ethernet) card of this type, say Y and read
746 the Ethernet-HOWTO, available from
747 <http://www.tldp.org/docs.html#howto>.
749 To compile this driver as a module, choose M here. The module
750 will be called typhoon.
753 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
754 depends on ISA && ISA_DMA_API
756 If you have a network (Ethernet) card of this type, say Y and read
757 the Ethernet-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
761 To compile this driver as a module, choose M here: the module
762 will be called lance. This is recommended.
764 config NET_VENDOR_SMC
765 bool "Western Digital/SMC cards"
766 depends on ISA || MCA || EISA || MAC
768 If you have a network (Ethernet) card belonging to this class, say Y
769 and read the Ethernet-HOWTO, available from
770 <http://www.tldp.org/docs.html#howto>.
772 Note that the answer to this question doesn't directly affect the
773 kernel: saying N will just cause the configurator to skip all
774 the questions about Western Digital cards. If you say Y, you will be
775 asked for your specific card in the following questions.
778 tristate "WD80*3 support"
779 depends on NET_VENDOR_SMC && ISA
782 If you have a network (Ethernet) card of this type, say Y and read
783 the Ethernet-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>.
786 To compile this driver as a module, choose M here. The module
790 tristate "SMC Ultra MCA support"
791 depends on NET_VENDOR_SMC && MCA
794 If you have a network (Ethernet) card of this type and are running
795 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
796 available from <http://www.tldp.org/docs.html#howto>.
798 To compile this driver as a module, choose M here. The module
799 will be called smc-mca.
802 tristate "SMC Ultra support"
803 depends on NET_VENDOR_SMC && ISA
806 If you have a network (Ethernet) card of this type, say Y and read
807 the Ethernet-HOWTO, available from
808 <http://www.tldp.org/docs.html#howto>.
810 Important: There have been many reports that, with some motherboards
811 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
812 such as some BusLogic models) causes corruption problems with many
813 operating systems. The Linux smc-ultra driver has a work-around for
814 this but keep it in mind if you have such a SCSI card and have
817 To compile this driver as a module, choose M here. The module
818 will be called smc-ultra.
821 tristate "SMC Ultra32 EISA support"
822 depends on NET_VENDOR_SMC && EISA
825 If you have a network (Ethernet) card of this type, say Y and read
826 the Ethernet-HOWTO, available from
827 <http://www.tldp.org/docs.html#howto>.
829 To compile this driver as a module, choose M here. The module
830 will be called smc-ultra32.
833 tristate "Blackfin 527/536/537 on-chip mac support"
834 depends on NET_ETHERNET && (BF527 || BF537 || BF536)
838 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
840 This is the driver for blackfin on-chip mac device. Say Y if you want it
841 compiled into the kernel. This driver is also available as a module
842 ( = code which can be inserted in and removed from the running kernel
843 whenever you want). The module will be called bfin_mac.
845 config BFIN_MAC_USE_L1
846 bool "Use L1 memory for rx/tx packets"
847 depends on BFIN_MAC && (BF527 || BF537)
850 To get maximum network performance, you should use L1 memory as rx/tx buffers.
851 Say N here if you want to reserve L1 memory for other uses.
853 config BFIN_TX_DESC_NUM
854 int "Number of transmit buffer packets"
856 range 6 10 if BFIN_MAC_USE_L1
860 Set the number of buffer packets used in driver.
862 config BFIN_RX_DESC_NUM
863 int "Number of receive buffer packets"
865 range 20 100 if BFIN_MAC_USE_L1
869 Set the number of buffer packets used in driver.
872 bool "RMII PHY Interface (EXPERIMENTAL)"
873 depends on BFIN_MAC && EXPERIMENTAL
874 default y if BFIN527_EZKIT
875 default n if BFIN537_STAMP
877 Use Reduced PHY MII Interface
880 tristate "SMC 9194 support"
881 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
884 This is support for the SMC9xxx based Ethernet cards. Choose this
885 option if you have a DELL laptop with the docking station, or
886 another SMC9192/9194 based chipset. Say Y if you want it compiled
887 into the kernel, and read the file
888 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
889 available from <http://www.tldp.org/docs.html#howto>.
891 To compile this driver as a module, choose M here. The module
892 will be called smc9194.
895 tristate "SMC 91C9x/91C1xxx support"
898 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
899 SOC_AU1X00 || BLACKFIN || MN10300
901 This is a driver for SMC's 91x series of Ethernet chipsets,
902 including the SMC91C94 and the SMC91C111. Say Y if you want it
903 compiled into the kernel, and read the file
904 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
905 available from <http://www.linuxdoc.org/docs.html#howto>.
907 This driver is also available as a module ( = code which can be
908 inserted in and removed from the running kernel whenever you want).
909 The module will be called smc91x. If you want to compile it as a
910 module, say M here and read <file:Documentation/kbuild/modules.txt>.
913 tristate "NetX Ethernet support"
917 This is support for the Hilscher netX builtin Ethernet ports
919 To compile this driver as a module, choose M here. The module
920 will be called netx-eth.
923 tristate "DM9000 support"
924 depends on ARM || BLACKFIN || MIPS
928 Support for DM9000 chipset.
930 To compile this driver as a module, choose M here. The module
931 will be called dm9000.
933 config DM9000_DEBUGLEVEL
934 int "DM9000 maximum debug level"
938 The maximum level of debugging code compiled into the DM9000
941 config DM9000_FORCE_SIMPLE_PHY_POLL
942 bool "Force simple NSR based PHY polling"
945 This configuration forces the DM9000 to use the NSR's LinkStatus
946 bit to determine if the link is up or down instead of the more
947 costly MII PHY reads. Note, this will not work if the chip is
948 operating with an external PHY.
951 tristate "ENC28J60 support"
952 depends on EXPERIMENTAL && SPI && NET_ETHERNET
955 Support for the Microchip EN28J60 ethernet chip.
957 To compile this driver as a module, choose M here. The module will be
960 config ENC28J60_WRITEVERIFY
961 bool "Enable write verify"
964 Enable the verify after the buffer write useful for debugging purpose.
968 tristate "SMSC LAN911[5678] support"
971 depends on ARCH_PXA || SUPERH
973 This is a driver for SMSC's LAN911x series of Ethernet chipsets
974 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
975 Say Y if you want it compiled into the kernel,
976 and read the Ethernet-HOWTO, available from
977 <http://www.linuxdoc.org/docs.html#howto>.
979 This driver is also available as a module. The module will be
980 called smc911x. If you want to compile it as a module, say M
981 here and read <file:Documentation/kbuild/modules.txt>
983 config NET_VENDOR_RACAL
984 bool "Racal-Interlan (Micom) NI cards"
987 If you have a network (Ethernet) card belonging to this class, such
988 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
989 available from <http://www.tldp.org/docs.html#howto>.
991 Note that the answer to this question doesn't directly affect the
992 kernel: saying N will just cause the configurator to skip all
993 the questions about NI cards. If you say Y, you will be asked for
994 your specific card in the following questions.
997 tristate "NI5010 support (EXPERIMENTAL)"
998 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1000 If you have a network (Ethernet) card of this type, say Y and read
1001 the Ethernet-HOWTO, available from
1002 <http://www.tldp.org/docs.html#howto>. Note that this is still
1005 To compile this driver as a module, choose M here. The module
1006 will be called ni5010.
1009 tristate "NI5210 support"
1010 depends on NET_VENDOR_RACAL && ISA
1012 If you have a network (Ethernet) card of this type, say Y and read
1013 the Ethernet-HOWTO, available from
1014 <http://www.tldp.org/docs.html#howto>.
1016 To compile this driver as a module, choose M here. The module
1017 will be called ni52.
1020 tristate "NI6510 support"
1021 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1023 If you have a network (Ethernet) card of this type, say Y and read
1024 the Ethernet-HOWTO, available from
1025 <http://www.tldp.org/docs.html#howto>.
1027 To compile this driver as a module, choose M here. The module
1028 will be called ni65.
1030 source "drivers/net/tulip/Kconfig"
1033 tristate "AT1700/1720 support (EXPERIMENTAL)"
1034 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1037 If you have a network (Ethernet) card of this type, say Y and read
1038 the Ethernet-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here. The module
1042 will be called at1700.
1045 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1046 depends on ISA || EISA || MCA
1049 If you have a network (Ethernet) card of this type, say Y and read
1050 the Ethernet-HOWTO, available from
1051 <http://www.tldp.org/docs.html#howto> as well as
1052 <file:drivers/net/depca.c>.
1054 To compile this driver as a module, choose M here. The module
1055 will be called depca.
1058 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1059 depends on ISA || EISA || PCI
1061 If you have a network (Ethernet) card of this type, say Y and read
1062 the Ethernet-HOWTO, available from
1063 <http://www.tldp.org/docs.html#howto>.
1065 To compile this driver as a module, choose M here. The module
1066 will be called hp100.
1069 bool "Other ISA cards"
1072 If your network (Ethernet) card hasn't been mentioned yet and its
1073 bus system (that's the way the cards talks to the other components
1074 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1075 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1076 available from <http://www.tldp.org/docs.html#howto>.
1080 Note that the answer to this question doesn't directly affect the
1081 kernel: saying N will just cause the configurator to skip all
1082 the remaining ISA network card questions. If you say Y, you will be
1083 asked for your specific card in the following questions.
1086 tristate "Cabletron E21xx support"
1090 If you have a network (Ethernet) card of this type, say Y and read
1091 the Ethernet-HOWTO, available from
1092 <http://www.tldp.org/docs.html#howto>.
1094 To compile this driver as a module, choose M here. The module
1095 will be called e2100.
1098 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1102 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1103 cards. If this is for you, say Y and read
1104 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1105 well as the Ethernet-HOWTO, available from
1106 <http://www.tldp.org/docs.html#howto>.
1108 To compile this driver as a module, choose M here. The module
1109 will be called ewrk3.
1112 tristate "EtherExpress 16 support"
1115 If you have an EtherExpress16 network (Ethernet) card, say Y and
1116 read the Ethernet-HOWTO, available from
1117 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1118 EtherExpress16 card used to be regarded as a very poor choice
1119 because the driver was very unreliable. We now have a new driver
1120 that should do better.
1122 To compile this driver as a module, choose M here. The module
1123 will be called eexpress.
1126 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1129 If you have a network (Ethernet) card of this type, say Y. This
1130 driver supports Intel i82595{FX,TX} based boards. Note however
1131 that the EtherExpress PRO/100 Ethernet card has its own separate
1132 driver. Please read the Ethernet-HOWTO, available from
1133 <http://www.tldp.org/docs.html#howto>.
1135 To compile this driver as a module, choose M here. The module
1136 will be called eepro.
1139 tristate "HP PCLAN+ (27247B and 27252A) support"
1143 If you have a network (Ethernet) card of this type, say Y and read
1144 the Ethernet-HOWTO, available from
1145 <http://www.tldp.org/docs.html#howto>.
1147 To compile this driver as a module, choose M here. The module
1148 will be called hp-plus.
1151 tristate "HP PCLAN (27245 and other 27xxx series) support"
1155 If you have a network (Ethernet) card of this type, say Y and read
1156 the Ethernet-HOWTO, available from
1157 <http://www.tldp.org/docs.html#howto>.
1159 To compile this driver as a module, choose M here. The module
1163 tristate "LP486E on board Ethernet"
1166 Say Y here to support the 82596-based on-board Ethernet controller
1167 for the Panther motherboard, which is one of the two shipped in the
1168 Intel Professional Workstation.
1171 tristate "ICL EtherTeam 16i/32 support"
1174 If you have a network (Ethernet) card of this type, say Y and read
1175 the Ethernet-HOWTO, available from
1176 <http://www.tldp.org/docs.html#howto>.
1178 To compile this driver as a module, choose M here. The module
1179 will be called eth16i.
1182 tristate "NE2000/NE1000 support"
1183 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1186 If you have a network (Ethernet) card of this type, say Y and read
1187 the Ethernet-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1189 without a specific driver are compatible with NE2000.
1191 If you have a PCI NE2000 card however, say N here and Y to "PCI
1192 NE2000 and clone support" under "EISA, VLB, PCI and on board
1193 controllers" below. If you have a NE2000 card and are running on
1194 an MCA system (a bus system used on some IBM PS/2 computers and
1195 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1198 To compile this driver as a module, choose M here. The module
1202 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1203 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1205 The Zenith Z-Note notebook computer has a built-in network
1206 (Ethernet) card, and this is the Linux driver for it. Note that the
1207 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1208 by this driver. Read the Ethernet-HOWTO, available from
1209 <http://www.tldp.org/docs.html#howto>.
1212 tristate "SEEQ8005 support (EXPERIMENTAL)"
1213 depends on NET_ISA && EXPERIMENTAL
1215 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1216 is for you, read the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here. The module
1220 will be called seeq8005.
1223 tristate "NE/2 (ne2000 MCA version) support"
1224 depends on MCA_LEGACY
1227 If you have a network (Ethernet) card of this type, say Y and read
1228 the Ethernet-HOWTO, available from
1229 <http://www.tldp.org/docs.html#howto>.
1231 To compile this driver as a module, choose M here. The module
1235 tristate "IBM LAN Adapter/A support"
1238 This is a Micro Channel Ethernet adapter. You need to set
1239 CONFIG_MCA to use this driver. It is both available as an in-kernel
1240 driver and as a module.
1242 To compile this driver as a module, choose M here. The only
1243 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1244 will both support 16K and 32K memory windows, however a 32K window
1245 gives a better security against packet losses. Usage of multiple
1246 boards with this driver should be possible, but has not been tested
1247 up to now due to lack of hardware.
1250 tristate "IBM LAN Virtual Ethernet support"
1251 depends on PPC_PSERIES
1253 This driver supports virtual ethernet adapters on newer IBM iSeries
1254 and pSeries systems.
1256 To compile this driver as a module, choose M here. The module will
1259 source "drivers/net/ibm_newemac/Kconfig"
1262 bool "EISA, VLB, PCI and on board controllers"
1263 depends on ISA || EISA || PCI
1265 This is another class of network cards which attach directly to the
1266 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1267 available from <http://www.tldp.org/docs.html#howto>.
1269 Note that the answer to this question doesn't directly affect the
1270 kernel: saying N will just cause the configurator to skip all
1271 the questions about this class of network cards. If you say Y, you
1272 will be asked for your specific card in the following questions. If
1273 you are unsure, say Y.
1276 tristate "AMD PCnet32 PCI support"
1277 depends on NET_PCI && PCI
1281 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1282 answer Y here and read the Ethernet-HOWTO, available from
1283 <http://www.tldp.org/docs.html#howto>.
1285 To compile this driver as a module, choose M here. The module
1286 will be called pcnet32.
1289 tristate "AMD 8111 (new PCI lance) support"
1290 depends on NET_PCI && PCI
1294 If you have an AMD 8111-based PCI lance ethernet card,
1295 answer Y here and read the Ethernet-HOWTO, available from
1296 <http://www.tldp.org/docs.html#howto>.
1298 To compile this driver as a module, choose M here. The module
1299 will be called amd8111e.
1301 config ADAPTEC_STARFIRE
1302 tristate "Adaptec Starfire/DuraLAN support"
1303 depends on NET_PCI && PCI
1307 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1308 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1309 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1312 To compile this driver as a module, choose M here: the module
1313 will be called starfire. This is recommended.
1316 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1317 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1320 If you have a network (Ethernet) card of this type, say Y and read
1321 the Ethernet-HOWTO, available from
1322 <http://www.tldp.org/docs.html#howto>.
1324 To compile this driver as a module, choose M here. The module
1325 will be called ac3200.
1328 tristate "Apricot Xen-II on board Ethernet"
1329 depends on NET_PCI && ISA
1331 If you have a network (Ethernet) controller of this type, say Y and
1332 read the Ethernet-HOWTO, available from
1333 <http://www.tldp.org/docs.html#howto>.
1335 To compile this driver as a module, choose M here. The module
1336 will be called apricot.
1339 tristate "Broadcom 440x/47xx ethernet support"
1340 depends on SSB_POSSIBLE && HAS_DMA
1344 If you have a network (Ethernet) controller of this type, say Y
1345 or M and read the Ethernet-HOWTO, available from
1346 <http://www.tldp.org/docs.html#howto>.
1348 To compile this driver as a module, choose M here. The module
1351 # Auto-select SSB PCI-HOST support, if possible
1352 config B44_PCI_AUTOSELECT
1354 depends on B44 && SSB_PCIHOST_POSSIBLE
1358 # Auto-select SSB PCICORE driver, if possible
1359 config B44_PCICORE_AUTOSELECT
1361 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1362 select SSB_DRIVER_PCICORE
1367 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1371 tristate "nForce Ethernet support"
1372 depends on NET_PCI && PCI
1374 If you have a network (Ethernet) controller of this type, say Y and
1375 read the Ethernet-HOWTO, available from
1376 <http://www.tldp.org/docs.html#howto>.
1378 To compile this driver as a module, choose M here. The module
1379 will be called forcedeth.
1381 config FORCEDETH_NAPI
1382 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1383 depends on FORCEDETH && EXPERIMENTAL
1385 NAPI is a new driver API designed to reduce CPU and interrupt load
1386 when the driver is receiving lots of packets from the card. It is
1387 still somewhat experimental and thus not yet enabled by default.
1389 If your estimated Rx load is 10kpps or more, or if the card will be
1390 deployed on potentially unfriendly networks (e.g. in a firewall),
1396 tristate "CS89x0 support"
1397 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1399 Support for CS89x0 chipset based Ethernet cards. If you have a
1400 network (Ethernet) card of this type, say Y and read the
1401 Ethernet-HOWTO, available from
1402 <http://www.tldp.org/docs.html#howto> as well as
1403 <file:Documentation/networking/cs89x0.txt>.
1405 To compile this driver as a module, choose M here. The module
1406 will be called cs89x0.
1409 tristate "TOSHIBA TC35815 Ethernet support"
1410 depends on NET_PCI && PCI && MIPS
1414 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1415 depends on NET_PCI && PCI
1418 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1419 card, say Y and read the Ethernet-HOWTO, available from
1420 <http://www.tldp.org/docs.html#howto>.
1422 To compile this driver as a module, choose M here. The module
1423 will be called eepro100.
1427 tristate "Intel(R) PRO/100+ support"
1428 depends on NET_PCI && PCI
1431 This driver supports Intel(R) PRO/100 family of adapters.
1432 To verify that your adapter is supported, find the board ID number
1433 on the adapter. Look for a label that has a barcode and a number
1434 in the format 123456-001 (six digits hyphen three digits).
1436 Use the above information and the Adapter & Driver ID Guide at:
1438 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1440 to identify the adapter.
1442 For the latest Intel PRO/100 network driver for Linux, see:
1444 <http://appsr.intel.com/scripts-df/support_intel.asp>
1446 More specific information on configuring the driver is in
1447 <file:Documentation/networking/e100.txt>.
1449 To compile this driver as a module, choose M here. The module
1450 will be called e100.
1453 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1454 depends on NET_PCI && EISA && EXPERIMENTAL
1457 If you have a network (Ethernet) card of this type, say Y and read
1458 the Ethernet-HOWTO, available from
1459 <http://www.tldp.org/docs.html#howto>.
1461 To compile this driver as a module, choose M here. The module
1462 will be called lne390.
1465 tristate "Myson MTD-8xx PCI Ethernet support"
1466 depends on NET_PCI && PCI
1470 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1471 cards. Specifications and data at
1472 <http://www.myson.com.hk/mtd/datasheet/>.
1475 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1476 depends on NET_PCI && PCI
1479 This driver is for the National Semiconductor DP83810 series,
1480 which is used in cards from PureData, NetGear, Linksys
1481 and others, including the 83815 chip.
1482 More specific information and updates are available from
1483 <http://www.scyld.com/network/natsemi.html>.
1486 tristate "PCI NE2000 and clones support (see help)"
1487 depends on NET_PCI && PCI
1490 This driver is for NE2000 compatible PCI cards. It will not work
1491 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1492 support" below). If you have a PCI NE2000 network (Ethernet) card,
1493 say Y and read the Ethernet-HOWTO, available from
1494 <http://www.tldp.org/docs.html#howto>.
1496 This driver also works for the following NE2000 clone cards:
1497 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1498 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1499 Holtek HT80232 Holtek HT80229
1501 To compile this driver as a module, choose M here. The module
1502 will be called ne2k-pci.
1505 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1506 depends on NET_PCI && EISA && EXPERIMENTAL
1509 If you have a network (Ethernet) card of this type, say Y and read
1510 the Ethernet-HOWTO, available from
1511 <http://www.tldp.org/docs.html#howto>. Note that this driver
1512 will NOT WORK for NE3200 cards as they are completely different.
1514 To compile this driver as a module, choose M here. The module
1515 will be called ne3210.
1518 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1519 depends on NET_PCI && EISA && EXPERIMENTAL
1522 If you have a network (Ethernet) card of this type, say Y and read
1523 the Ethernet-HOWTO, available from
1524 <http://www.tldp.org/docs.html#howto>.
1526 To compile this driver as a module, choose M here. The module
1527 will be called es3210.
1530 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1531 depends on NET_PCI && PCI && EXPERIMENTAL
1535 This is a driver for the Fast Ethernet PCI network cards based on
1536 the RTL8139C+ chips. If you have one of those, say Y and read
1537 the Ethernet-HOWTO, available from
1538 <http://www.tldp.org/docs.html#howto>.
1540 To compile this driver as a module, choose M here: the module
1541 will be called 8139cp. This is recommended.
1544 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1545 depends on NET_PCI && PCI
1549 This is a driver for the Fast Ethernet PCI network cards based on
1550 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1551 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1553 To compile this driver as a module, choose M here: the module
1554 will be called 8139too. This is recommended.
1557 bool "Use PIO instead of MMIO"
1561 This instructs the driver to use programmed I/O ports (PIO) instead
1562 of PCI shared memory (MMIO). This can possibly solve some problems
1563 in case your mainboard has memory consistency issues. If unsure,
1566 config 8139TOO_TUNE_TWISTER
1567 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1570 This implements a function which might come in handy in case you
1571 are using low quality on long cabling. It is required for RealTek
1572 RTL-8139 revision K boards, and totally unused otherwise. It tries
1573 to match the transceiver to the cable characteristics. This is
1574 experimental since hardly documented by the manufacturer.
1578 bool "Support for older RTL-8129/8130 boards"
1581 This enables support for the older and uncommon RTL-8129 and
1582 RTL-8130 chips, which support MII via an external transceiver,
1583 instead of an internal one. Disabling this option will save some
1584 memory by making the code size smaller. If unsure, say Y.
1586 config 8139_OLD_RX_RESET
1587 bool "Use older RX-reset method"
1590 The 8139too driver was recently updated to contain a more rapid
1591 reset sequence, in the face of severe receive errors. This "new"
1592 RX-reset method should be adequate for all boards. But if you
1593 experience problems, you can enable this option to restore the
1594 old RX-reset behavior. If unsure, say N.
1597 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1598 depends on NET_PCI && PCI
1602 This is a driver for the R6040 Fast Ethernet MACs found in the
1603 the RDC R-321x System-on-chips.
1605 To compile this driver as a module, choose M here: the module
1606 will be called r6040. This is recommended.
1609 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1610 depends on NET_PCI && PCI
1614 This is a driver for the Fast Ethernet PCI network cards based on
1615 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1616 SiS 630 and SiS 540 chipsets.
1618 This driver also supports AMD 79C901 HomePNA so that you can use
1619 your phone line as a network cable.
1621 To compile this driver as a module, choose M here: the module
1622 will be called sis900. This is recommended.
1625 tristate "SMC EtherPower II"
1626 depends on NET_PCI && PCI
1630 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1631 which is based on the SMC83c17x (EPIC/100).
1632 More specific information and updates are available from
1633 <http://www.scyld.com/network/epic100.html>.
1636 tristate "Sundance Alta support"
1637 depends on NET_PCI && PCI
1641 This driver is for the Sundance "Alta" chip.
1642 More specific information and updates are available from
1643 <http://www.scyld.com/network/sundance.html>.
1645 config SUNDANCE_MMIO
1646 bool "Use MMIO instead of PIO"
1649 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1650 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1651 is known to solve bugs on certain chips.
1656 tristate "TI ThunderLAN support"
1657 depends on NET_PCI && (PCI || EISA)
1659 If you have a PCI Ethernet network card based on the ThunderLAN chip
1660 which is supported by this driver, say Y and read the
1661 Ethernet-HOWTO, available from
1662 <http://www.tldp.org/docs.html#howto>.
1664 Devices currently supported by this driver are Compaq Netelligent,
1665 Compaq NetFlex and Olicom cards. Please read the file
1666 <file:Documentation/networking/tlan.txt> for more details.
1668 To compile this driver as a module, choose M here. The module
1669 will be called tlan.
1671 Please email feedback to <torben.mathiasen@compaq.com>.
1674 tristate "VIA Rhine support"
1675 depends on NET_PCI && PCI
1679 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1680 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1681 Ethernet functions can also be found integrated on South Bridges
1684 To compile this driver as a module, choose M here. The module
1685 will be called via-rhine.
1687 config VIA_RHINE_MMIO
1688 bool "Use MMIO instead of PIO"
1689 depends on VIA_RHINE
1691 This instructs the driver to use PCI shared memory (MMIO) instead of
1692 programmed I/O ports (PIO). Enabling this gives an improvement in
1693 processing time in parts of the driver.
1698 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1699 depends on NET_PCI && PCI && EXPERIMENTAL
1702 This is a driver for the Fast Ethernet PCI network cards based on
1703 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1704 have one of these, say Y here.
1706 To compile this driver as a module, choose M here: the module
1707 will be called sc92031. This is recommended.
1710 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1711 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1714 TI AR7 CPMAC Ethernet support
1717 bool "Pocket and portable adapters"
1720 Cute little network (Ethernet) devices which attach to the parallel
1721 port ("pocket adapters"), commonly used with laptops. If you have
1722 one of those, say Y and read the Ethernet-HOWTO, available from
1723 <http://www.tldp.org/docs.html#howto>.
1725 If you want to plug a network (or some other) card into the PCMCIA
1726 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1727 credit card size extension cards used by all modern laptops), you
1728 need the pcmcia-cs package (location contained in the file
1729 <file:Documentation/Changes>) and you can say N here.
1731 Laptop users should read the Linux Laptop home page at
1732 <http://www.linux-on-laptops.com/> or
1733 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1735 Note that the answer to this question doesn't directly affect the
1736 kernel: saying N will just cause the configurator to skip all
1737 the questions about this class of network devices. If you say Y, you
1738 will be asked for your specific device in the following questions.
1741 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1742 depends on NET_POCKET && PARPORT && X86
1745 This is a network (Ethernet) device which attaches to your parallel
1746 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1747 available from <http://www.tldp.org/docs.html#howto>, if you
1748 want to use this. If you intend to use this driver, you should have
1749 said N to the "Parallel printer support", because the two drivers
1750 don't like each other.
1752 To compile this driver as a module, choose M here: the module
1756 tristate "D-Link DE600 pocket adapter support"
1757 depends on NET_POCKET && PARPORT
1759 This is a network (Ethernet) device which attaches to your parallel
1760 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1761 Ethernet-HOWTO, available from
1762 <http://www.tldp.org/docs.html#howto>, if you want to use
1763 this. It is possible to have several devices share a single parallel
1764 port and it is safe to compile the corresponding drivers into the
1767 To compile this driver as a module, choose M here: the module
1768 will be called de600.
1771 tristate "D-Link DE620 pocket adapter support"
1772 depends on NET_POCKET && PARPORT
1774 This is a network (Ethernet) device which attaches to your parallel
1775 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1776 Ethernet-HOWTO, available from
1777 <http://www.tldp.org/docs.html#howto>, if you want to use
1778 this. It is possible to have several devices share a single parallel
1779 port and it is safe to compile the corresponding drivers into the
1782 To compile this driver as a module, choose M here: the module
1783 will be called de620.
1786 tristate "SGI Seeq ethernet controller support"
1787 depends on SGI_HAS_SEEQ
1789 Say Y here if you have an Seeq based Ethernet network card. This is
1790 used in many Silicon Graphics machines.
1793 tristate "DEC LANCE ethernet controller support"
1794 depends on MACH_DECSTATION
1797 This driver is for the series of Ethernet controllers produced by
1798 DEC (now Compaq) based on the AMD Lance chipset, including the
1799 DEPCA series. (This chipset is better known via the NE2100 cards.)
1802 bool "Motorola 68360 ethernet controller"
1805 Say Y here if you want to use the built-in ethernet controller of
1806 the Motorola 68360 processor.
1809 bool "FEC ethernet controller (of ColdFire CPUs)"
1810 depends on M523x || M527x || M5272 || M528x || M520x
1812 Say Y here if you want to use the built-in 10/100 Fast ethernet
1813 controller on some Motorola ColdFire processors.
1816 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1819 Say Y here if you want to use the second built-in 10/100 Fast
1820 ethernet controller on some Motorola ColdFire processors.
1823 tristate "MPC52xx FEC driver"
1824 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
1828 This option enables support for the MPC5200's on-chip
1829 Fast Ethernet Controller
1830 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1832 config FEC_MPC52xx_MDIO
1833 bool "MPC52xx FEC MDIO bus driver"
1834 depends on FEC_MPC52xx
1837 The MPC5200's FEC can connect to the Ethernet either with
1838 an external MII PHY chip or 10 Mbps 7-wire interface
1839 (Motorola? industry standard).
1840 If your board uses an external PHY connected to FEC, enable this.
1841 If not sure, enable.
1842 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1845 tristate "NE2000 compatible support for H8/300"
1848 Say Y here if you want to use the NE2000 compatible
1849 controller on the Renesas H8/300 processor.
1851 source "drivers/net/fs_enet/Kconfig"
1853 endif # NET_ETHERNET
1859 menuconfig NETDEV_1000
1860 bool "Ethernet (1000 Mbit)"
1864 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1865 type of Local Area Network (LAN) in universities and companies.
1867 Say Y here to get to see options for Gigabit Ethernet drivers.
1868 This option alone does not add any kernel code.
1869 Note that drivers supporting both 100 and 1000 MBit may be listed
1870 under "Ethernet (10 or 100MBit)" instead.
1872 If you say N, all options in this submenu will be skipped and disabled.
1877 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1880 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1881 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1882 adapter. The driver allows for using the Jumbo Frame option (9000
1883 bytes/frame) however it requires that your switches can handle this
1884 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1887 To compile this driver as a module, choose M here: the
1888 module will be called acenic.
1890 config ACENIC_OMIT_TIGON_I
1891 bool "Omit support for old Tigon I based AceNICs"
1894 Say Y here if you only have Tigon II based AceNICs and want to leave
1895 out support for the older Tigon I based cards which are no longer
1896 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1897 version)). This will reduce the size of the driver object by
1898 app. 100KB. If you are not sure whether your card is a Tigon I or a
1899 Tigon II, say N here.
1901 The safe and default value for this is N.
1904 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1908 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1910 D-Link DGE-550T Gigabit Ethernet Adapter.
1911 D-Link DL2000-based Gigabit Ethernet Adapter.
1912 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1914 To compile this driver as a module, choose M here: the
1915 module will be called dl2k.
1918 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1921 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1922 adapters. For more information on how to identify your adapter, go
1923 to the Adapter & Driver ID Guide at:
1925 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1927 For general information and support, go to the Intel support
1930 <http://support.intel.com>
1932 More specific information on configuring the driver is in
1933 <file:Documentation/networking/e1000.txt>.
1935 To compile this driver as a module, choose M here. The module
1936 will be called e1000.
1939 bool "Use Rx Polling (NAPI)"
1942 NAPI is a new driver API designed to reduce CPU and interrupt load
1943 when the driver is receiving lots of packets from the card. It is
1944 still somewhat experimental and thus not yet enabled by default.
1946 If your estimated Rx load is 10kpps or more, or if the card will be
1947 deployed on potentially unfriendly networks (e.g. in a firewall),
1952 config E1000_DISABLE_PACKET_SPLIT
1953 bool "Disable Packet Split for PCI express adapters"
1956 Say Y here if you want to use the legacy receive path for PCI express
1962 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1963 depends on PCI && (!SPARC32 || BROKEN)
1965 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1966 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1967 use the regular e1000 driver For more information on how to
1968 identify your adapter, go to the Adapter & Driver ID Guide at:
1970 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1972 For general information and support, go to the Intel support
1975 <http://support.intel.com>
1977 To compile this driver as a module, choose M here. The module
1978 will be called e1000e.
1981 tristate "IP1000 Gigabit Ethernet support"
1982 depends on PCI && EXPERIMENTAL
1985 This driver supports IP1000 gigabit Ethernet cards.
1987 To compile this driver as a module, choose M here: the module
1988 will be called ipg. This is recommended.
1991 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
1994 This driver supports Intel(R) 82575 gigabit ethernet family of
1995 adapters. For more information on how to identify your adapter, go
1996 to the Adapter & Driver ID Guide at:
1998 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2000 For general information and support, go to the Intel support
2003 <http://support.intel.com>
2005 More specific information on configuring the driver is in
2006 <file:Documentation/networking/e1000.txt>.
2008 To compile this driver as a module, choose M here. The module
2012 bool "Use software LRO"
2013 depends on IGB && INET
2016 Say Y here if you want to use large receive offload.
2020 source "drivers/net/ixp2000/Kconfig"
2023 tristate "MyriCOM Gigabit Ethernet support"
2026 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2028 To compile this driver as a module, choose M here: the module
2029 will be called myri_sbus. This is recommended.
2032 tristate "National Semiconductor DP83820 support"
2035 This is a driver for the National Semiconductor DP83820 series
2036 of gigabit ethernet MACs. Cards using this chipset include
2037 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2038 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2042 tristate "Packet Engines Hamachi GNIC-II support"
2046 If you have a Gigabit Ethernet card of this type, say Y and read
2047 the Ethernet-HOWTO, available from
2048 <http://www.tldp.org/docs.html#howto>.
2050 To compile this driver as a module, choose M here. The module will be
2054 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2055 depends on PCI && EXPERIMENTAL
2058 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2059 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2060 used by the Beowulf Linux cluster project. See
2061 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2062 information about this driver in particular and Beowulf in general.
2064 To compile this driver as a module, choose M here: the module
2065 will be called yellowfin. This is recommended.
2068 tristate "Realtek 8169 gigabit ethernet support"
2072 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2074 To compile this driver as a module, choose M here: the module
2075 will be called r8169. This is recommended.
2079 depends on R8169 && VLAN_8021Q
2081 Say Y here for the r8169 driver to support the functions required
2082 by the kernel 802.1Q code.
2087 tristate "SB1250 Gigabit Ethernet support"
2088 depends on SIBYTE_SB1xxx_SOC
2091 This driver supports Gigabit Ethernet interfaces based on the
2092 Broadcom SiByte family of System-On-a-Chip parts. They include
2093 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2096 To compile this driver as a module, choose M here: the module
2097 will be called sb1250-mac.
2100 tristate "SiS190/SiS191 gigabit ethernet support"
2105 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2106 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2107 appear in lan on motherboard designs which are based on SiS 965
2108 and SiS 966 south bridge.
2110 To compile this driver as a module, choose M here: the module
2111 will be called sis190. This is recommended.
2114 tristate "New SysKonnect GigaEthernet support"
2118 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2119 and related Gigabit Ethernet adapters. It is a new smaller driver
2120 with better performance and more complete ethtool support.
2122 It does not support the link failover and network management
2123 features that "portable" vendor supplied sk98lin driver does.
2125 This driver supports adapters based on the original Yukon chipset:
2126 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2127 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2129 It does not support the newer Yukon2 chipset: a separate driver,
2130 sky2, is provided for Yukon2-based adapters.
2132 To compile this driver as a module, choose M here: the module
2133 will be called skge. This is recommended.
2136 bool "Debugging interface"
2137 depends on SKGE && DEBUG_FS
2139 This option adds the ability to dump driver state for debugging.
2140 The file debugfs/skge/ethX displays the state of the internal
2141 transmit and receive rings.
2146 tristate "SysKonnect Yukon2 support"
2150 This driver supports Gigabit Ethernet adapters based on the
2151 Marvell Yukon 2 chipset:
2152 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2153 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2155 There is companion driver for the older Marvell Yukon and
2156 Genesis based adapters: skge.
2158 To compile this driver as a module, choose M here: the module
2159 will be called sky2. This is recommended.
2162 bool "Debugging interface"
2163 depends on SKY2 && DEBUG_FS
2165 This option adds the ability to dump driver state for debugging.
2166 The file debugfs/sky2/ethX displays the state of the internal
2167 transmit and receive rings.
2172 tristate "VIA Velocity support"
2178 If you have a VIA "Velocity" based network card say Y here.
2180 To compile this driver as a module, choose M here. The module
2181 will be called via-velocity.
2184 tristate "Broadcom Tigon3 support"
2188 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2190 To compile this driver as a module, choose M here: the module
2191 will be called tg3. This is recommended.
2194 tristate "Broadcom NetXtremeII support"
2199 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2201 To compile this driver as a module, choose M here: the module
2202 will be called bnx2. This is recommended.
2205 tristate "Spider Gigabit Ethernet driver"
2206 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2209 This driver supports the Gigabit Ethernet chips present on the
2210 Cell Processor-Based Blades from IBM.
2213 tristate "Tundra TSI108 gigabit Ethernet support"
2214 depends on TSI108_BRIDGE
2216 This driver supports Tundra TSI108 gigabit Ethernet ports.
2217 To compile this driver as a module, choose M here: the module
2218 will be called tsi108_eth.
2221 tristate "PS3 Gigabit Ethernet driver"
2223 select PS3_SYS_MANAGER
2225 This driver supports the network device on the PS3 game
2226 console. This driver has built-in support for Ethernet.
2228 To compile this driver as a module, choose M here: the
2229 module will be called ps3_gelic.
2231 config GELIC_WIRELESS
2232 bool "PS3 Wireless support"
2233 depends on GELIC_NET
2236 This option adds the support for the wireless feature of PS3.
2237 If you have the wireless-less model of PS3 or have no plan to
2238 use wireless feature, disabling this option saves memory. As
2239 the driver automatically distinguishes the models, you can
2240 safely enable this option even if you have a wireless-less model.
2242 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2243 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2244 depends on GELIC_WIRELESS
2246 This option retains the obsolete private interface to pass
2247 the PSK from user space programs to the driver. The PSK
2248 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2249 (WPA-Personal) environment.
2250 If WPA[2]-PSK is used and you need to use old programs that
2251 support only this old interface, say Y. Otherwise N.
2256 tristate "Gianfar Ethernet"
2261 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2262 and MPC86xx family of chips, and the FEC on the 8540.
2265 tristate "Freescale QE Gigabit Ethernet"
2266 depends on QUICC_ENGINE
2269 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2270 which is available on some Freescale SOCs.
2272 config UGETH_MAGIC_PACKET
2273 bool "Magic Packet detection support"
2276 config UGETH_FILTERING
2277 bool "Mac address filtering support"
2280 config UGETH_TX_ON_DEMAND
2281 bool "Transmit on Demand support"
2285 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2286 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2289 This driver supports the gigabit ethernet MACs in the
2290 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2291 in the Marvell Orion ARM SoC family.
2293 Some boards that use the Discovery chipset are the Momenco
2294 Ocelot C and Jaguar ATX and Pegasos II.
2297 tristate "QLogic QLA3XXX Network Driver Support"
2300 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2302 To compile this driver as a module, choose M here: the module
2303 will be called qla3xxx.
2306 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2307 depends on PCI && EXPERIMENTAL
2311 This driver supports the Attansic L1 gigabit ethernet adapter.
2313 To compile this driver as a module, choose M here. The module
2314 will be called atl1.
2319 # 10 Gigabit Ethernet
2322 menuconfig NETDEV_10000
2323 bool "Ethernet (10000 Mbit)"
2327 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2328 This option alone does not add any kernel code.
2330 If you say N, all options in this submenu will be skipped and disabled.
2335 tristate "Chelsio 10Gb Ethernet support"
2339 This driver supports Chelsio gigabit and 10-gigabit
2340 Ethernet cards. More information about adapter features and
2341 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2343 For general information about Chelsio and our products, visit
2344 our website at <http://www.chelsio.com>.
2346 For customer support, please visit our customer support page at
2347 <http://www.chelsio.com/support.htm>.
2349 Please send feedback to <linux-bugs@chelsio.com>.
2351 To compile this driver as a module, choose M here: the module
2352 will be called cxgb.
2354 config CHELSIO_T1_1G
2355 bool "Chelsio gigabit Ethernet support"
2356 depends on CHELSIO_T1
2358 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2359 are using only 10G cards say 'N' here.
2362 tristate "Chelsio Communications T3 10Gb Ethernet support"
2363 depends on PCI && INET
2367 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2370 For general information about Chelsio and our products, visit
2371 our website at <http://www.chelsio.com>.
2373 For customer support, please visit our customer support page at
2374 <http://www.chelsio.com/support.htm>.
2376 Please send feedback to <linux-bugs@chelsio.com>.
2378 To compile this driver as a module, choose M here: the module
2379 will be called cxgb3.
2382 tristate "eHEA Ethernet support"
2383 depends on IBMEBUS && INET && SPARSEMEM
2386 This driver supports the IBM pSeries eHEA ethernet adapter.
2388 To compile the driver as a module, choose M here. The module
2389 will be called ehea.
2392 tristate "Intel(R) 10GbE PCI Express adapters support"
2393 depends on PCI && INET
2396 This driver supports Intel(R) 10GbE PCI Express family of
2397 adapters. For more information on how to identify your adapter, go
2398 to the Adapter & Driver ID Guide at:
2400 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2402 For general information and support, go to the Intel support
2405 <http://support.intel.com>
2407 To compile this driver as a module, choose M here. The module
2408 will be called ixgbe.
2411 tristate "Intel(R) PRO/10GbE support"
2414 This driver supports Intel(R) PRO/10GbE family of adapters for
2415 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2416 instead. For more information on how to identify your adapter, go
2417 to the Adapter & Driver ID Guide at:
2419 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2421 For general information and support, go to the Intel support
2424 <http://support.intel.com>
2426 More specific information on configuring the driver is in
2427 <file:Documentation/networking/ixgb.txt>.
2429 To compile this driver as a module, choose M here. The module
2430 will be called ixgb.
2433 tristate "S2IO 10Gbe XFrame NIC"
2436 This driver supports the 10Gbe XFrame NIC of S2IO.
2437 More specific information on configuring the driver is in
2438 <file:Documentation/networking/s2io.txt>.
2441 tristate "Myricom Myri-10G Ethernet support"
2442 depends on PCI && INET
2447 This driver supports Myricom Myri-10G Dual Protocol interface in
2448 Ethernet mode. If the eeprom on your board is not recent enough,
2449 you will need a newer firmware image.
2450 You may get this image or more information, at:
2452 <http://www.myri.com/scs/download-Myri10GE.html>
2454 To compile this driver as a module, choose M here. The module
2455 will be called myri10ge.
2458 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2461 This enables the support for NetXen's Gigabit Ethernet card.
2464 tristate "Sun Neptune 10Gbit Ethernet support"
2467 This enables support for cards based upon Sun's
2471 tristate "PA Semi 1/10Gbit MAC"
2472 depends on PPC_PASEMI && PCI
2476 This driver supports the on-chip 1/10Gbit Ethernet controller on
2477 PA Semi's PWRficient line of chips.
2485 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2486 depends on MLX4_CORE
2489 This option causes debugging code to be compiled into the
2490 mlx4_core driver. The output can be turned on via the
2491 debug_level module parameter (which can also be set after
2492 the driver is loaded through sysfs).
2495 tristate "Tehuti Networks 10G Ethernet"
2498 Tehuti Networks 10G Ethernet NIC
2501 tristate "Broadcom NetXtremeII 10Gb support"
2506 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2507 To compile this driver as a module, choose M here: the module
2508 will be called bnx2x. This is recommended.
2510 source "drivers/net/sfc/Kconfig"
2512 endif # NETDEV_10000
2514 source "drivers/net/tokenring/Kconfig"
2516 source "drivers/net/wireless/Kconfig"
2518 source "drivers/net/usb/Kconfig"
2520 source "drivers/net/pcmcia/Kconfig"
2522 source "drivers/net/wan/Kconfig"
2524 source "drivers/atm/Kconfig"
2526 source "drivers/s390/net/Kconfig"
2528 config XEN_NETDEV_FRONTEND
2529 tristate "Xen network device frontend driver"
2533 The network device frontend driver allows the kernel to
2534 access network devices exported exported by a virtual
2535 machine containing a physical network device driver. The
2536 frontend driver is intended for unprivileged guest domains;
2537 if you are compiling a kernel for a Xen guest, you almost
2538 certainly want to enable this.
2541 tristate "iSeries Virtual Ethernet driver support"
2542 depends on PPC_ISERIES
2545 tristate "RapidIO Ethernet over messaging driver support"
2548 config RIONET_TX_SIZE
2549 int "Number of outbound queue entries"
2553 config RIONET_RX_SIZE
2554 int "Number of inbound queue entries"
2559 bool "FDDI driver support"
2560 depends on (PCI || EISA || TC)
2562 Fiber Distributed Data Interface is a high speed local area network
2563 design; essentially a replacement for high speed Ethernet. FDDI can
2564 run over copper or fiber. If you are connected to such a network and
2565 want a driver for the FDDI card in your computer, say Y here (and
2566 then also Y to the driver for your FDDI card, below). Most people
2570 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2571 depends on FDDI && (PCI || EISA || TC)
2573 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2574 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2575 to a local FDDI network.
2577 To compile this driver as a module, choose M here: the module
2578 will be called defxx. If unsure, say N.
2582 prompt "Use MMIO instead of PIO" if PCI || EISA
2584 default n if PCI || EISA
2587 This instructs the driver to use EISA or PCI memory-mapped I/O
2588 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2589 Enabling this gives an improvement in processing time in parts
2590 of the driver, but it may cause problems with EISA (DEFEA)
2591 adapters. TURBOchannel does not have the concept of I/O ports,
2592 so MMIO is always used for these (DEFTA) adapters.
2597 tristate "SysKonnect FDDI PCI support"
2598 depends on FDDI && PCI
2601 Say Y here if you have a SysKonnect FDDI PCI adapter.
2602 The following adapters are supported by this driver:
2603 - SK-5521 (SK-NET FDDI-UP)
2604 - SK-5522 (SK-NET FDDI-UP DAS)
2605 - SK-5541 (SK-NET FDDI-FP)
2606 - SK-5543 (SK-NET FDDI-LP)
2607 - SK-5544 (SK-NET FDDI-LP DAS)
2608 - SK-5821 (SK-NET FDDI-UP64)
2609 - SK-5822 (SK-NET FDDI-UP64 DAS)
2610 - SK-5841 (SK-NET FDDI-FP64)
2611 - SK-5843 (SK-NET FDDI-LP64)
2612 - SK-5844 (SK-NET FDDI-LP64 DAS)
2613 - Netelligent 100 FDDI DAS Fibre SC
2614 - Netelligent 100 FDDI SAS Fibre SC
2615 - Netelligent 100 FDDI DAS UTP
2616 - Netelligent 100 FDDI SAS UTP
2617 - Netelligent 100 FDDI SAS Fibre MIC
2619 Read <file:Documentation/networking/skfp.txt> for information about
2622 Questions concerning this driver can be addressed to:
2623 <linux@syskonnect.de>
2625 To compile this driver as a module, choose M here: the module
2626 will be called skfp. This is recommended.
2629 bool "HIPPI driver support (EXPERIMENTAL)"
2630 depends on EXPERIMENTAL && INET && PCI
2632 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2633 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2634 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2635 single-mode). HIPPI networks are commonly used for clusters and to
2636 connect to super computers. If you are connected to a HIPPI network
2637 and have a HIPPI network card in your computer that you want to use
2638 under Linux, say Y here (you must also remember to enable the driver
2639 for your HIPPI card below). Most people will say N here.
2642 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2643 depends on HIPPI && PCI
2645 Say Y here if this is your PCI HIPPI network card.
2647 To compile this driver as a module, choose M here: the module
2648 will be called rrunner. If unsure, say N.
2650 config ROADRUNNER_LARGE_RINGS
2651 bool "Use large TX/RX rings (EXPERIMENTAL)"
2652 depends on ROADRUNNER
2654 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2655 of additional memory to allow for fastest operation, both for
2656 transmitting and receiving. This memory cannot be used by any other
2657 kernel code or by user space programs. Say Y here only if you have
2661 tristate "PLIP (parallel port) support"
2664 PLIP (Parallel Line Internet Protocol) is used to create a
2665 reasonably fast mini network consisting of two (or, rarely, more)
2666 local machines. A PLIP link from a Linux box is a popular means to
2667 install a Linux distribution on a machine which doesn't have a
2668 CD-ROM drive (a minimal system has to be transferred with floppies
2669 first). The kernels on both machines need to have this PLIP option
2670 enabled for this to work.
2672 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2673 ports (the connectors at the computers with 25 holes) are connected
2674 with "null printer" or "Turbo Laplink" cables which can transmit 4
2675 bits at a time (mode 0) or with special PLIP cables, to be used on
2676 bidirectional parallel ports only, which can transmit 8 bits at a
2677 time (mode 1); you can find the wiring of these cables in
2678 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2679 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2680 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2681 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2682 and winsock or NCSA's telnet.
2684 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2685 as the NET-3-HOWTO, both available from
2686 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2687 protocol has been changed and this PLIP driver won't work together
2688 with the PLIP support in Linux versions 1.0.x. This option enlarges
2689 your kernel by about 8 KB.
2691 To compile this driver as a module, choose M here. The module
2692 will be called plip. If unsure, say Y or M, in case you buy
2696 tristate "PPP (point-to-point protocol) support"
2699 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2700 the same purpose: sending Internet traffic over telephone (and other
2701 serial) lines. Ask your access provider if they support it, because
2702 otherwise you can't use it; most Internet access providers these
2703 days support PPP rather than SLIP.
2705 To use PPP, you need an additional program called pppd as described
2706 in the PPP-HOWTO, available at
2707 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2708 the version of pppd recommended in <file:Documentation/Changes>.
2709 The PPP option enlarges your kernel by about 16 KB.
2711 There are actually two versions of PPP: the traditional PPP for
2712 asynchronous lines, such as regular analog phone lines, and
2713 synchronous PPP which can be used over digital ISDN lines for
2714 example. If you want to use PPP over phone lines or other
2715 asynchronous serial lines, you need to say Y (or M) here and also to
2716 the next option, "PPP support for async serial ports". For PPP over
2717 synchronous lines, you should say Y (or M) here and to "Support
2718 synchronous PPP", below.
2720 If you said Y to "Version information on all symbols" above, then
2721 you cannot compile the PPP driver into the kernel; you can then only
2722 compile it as a module. To compile this driver as a module, choose M
2723 here. The module will be called ppp_generic.
2725 config PPP_MULTILINK
2726 bool "PPP multilink support (EXPERIMENTAL)"
2727 depends on PPP && EXPERIMENTAL
2729 PPP multilink is a protocol (defined in RFC 1990) which allows you
2730 to combine several (logical or physical) lines into one logical PPP
2731 connection, so that you can utilize your full bandwidth.
2733 This has to be supported at the other end as well and you need a
2734 version of the pppd daemon which understands the multilink protocol.
2739 bool "PPP filtering"
2742 Say Y here if you want to be able to filter the packets passing over
2743 PPP interfaces. This allows you to control which packets count as
2744 activity (i.e. which packets will reset the idle timer or bring up
2745 a demand-dialed link) and which packets are to be dropped entirely.
2746 You need to say Y here if you wish to use the pass-filter and
2747 active-filter options to pppd.
2752 tristate "PPP support for async serial ports"
2756 Say Y (or M) here if you want to be able to use PPP over standard
2757 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2758 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2761 To compile this driver as a module, choose M here.
2766 tristate "PPP support for sync tty ports"
2769 Say Y (or M) here if you want to be able to use PPP over synchronous
2770 (HDLC) tty devices, such as the SyncLink adapter. These devices
2771 are often used for high-speed leased lines like T1/E1.
2773 To compile this driver as a module, choose M here.
2776 tristate "PPP Deflate compression"
2781 Support for the Deflate compression method for PPP, which uses the
2782 Deflate algorithm (the same algorithm that gzip uses) to compress
2783 each PPP packet before it is sent over the wire. The machine at the
2784 other end of the PPP link (usually your ISP) has to support the
2785 Deflate compression method as well for this to be useful. Even if
2786 they don't support it, it is safe to say Y here.
2788 To compile this driver as a module, choose M here.
2791 tristate "PPP BSD-Compress compression"
2794 Support for the BSD-Compress compression method for PPP, which uses
2795 the LZW compression method to compress each PPP packet before it is
2796 sent over the wire. The machine at the other end of the PPP link
2797 (usually your ISP) has to support the BSD-Compress compression
2798 method as well for this to be useful. Even if they don't support it,
2799 it is safe to say Y here.
2801 The PPP Deflate compression method ("PPP Deflate compression",
2802 above) is preferable to BSD-Compress, because it compresses better
2805 Note that the BSD compression code will always be compiled as a
2806 module; it is called bsd_comp and will show up in the directory
2807 modules once you have said "make modules". If unsure, say N.
2810 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2811 depends on PPP && EXPERIMENTAL
2817 Support for the MPPE Encryption protocol, as employed by the
2818 Microsoft Point-to-Point Tunneling Protocol.
2820 See http://pptpclient.sourceforge.net/ for information on
2821 configuring PPTP clients and servers to utilize this method.
2824 tristate "PPP over Ethernet (EXPERIMENTAL)"
2825 depends on EXPERIMENTAL && PPP
2827 Support for PPP over Ethernet.
2829 This driver requires the latest version of pppd from the CVS
2830 repository at cvs.samba.org. Alternatively, see the
2831 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2832 which contains instruction on how to use this driver (under
2833 the heading "Kernel mode PPPoE").
2836 tristate "PPP over ATM"
2837 depends on ATM && PPP
2839 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2840 This implementation does not yet comply with section 8 of RFC2364,
2841 which can lead to bad results if the ATM peer loses state and
2842 changes its encapsulation unilaterally.
2845 tristate "PPP over L2TP (EXPERIMENTAL)"
2846 depends on EXPERIMENTAL && PPP && INET
2848 Support for PPP-over-L2TP socket family. L2TP is a protocol
2849 used by ISPs and enterprises to tunnel PPP traffic over UDP
2850 tunnels. L2TP is replacing PPTP for VPN uses.
2852 This kernel component handles only L2TP data packets: a
2853 userland daemon handles L2TP the control protocol (tunnel
2854 and session setup). One such daemon is OpenL2TP
2855 (http://openl2tp.sourceforge.net/).
2858 tristate "SLIP (serial line) support"
2860 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2861 connect to your Internet service provider or to connect to some
2862 other local Unix box or if you want to configure your Linux box as a
2863 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2864 Internet Protocol) is a protocol used to send Internet traffic over
2865 serial connections such as telephone lines or null modem cables;
2866 nowadays, the protocol PPP is more commonly used for this same
2869 Normally, your access provider has to support SLIP in order for you
2870 to be able to use it, but there is now a SLIP emulator called SLiRP
2871 around (available from
2872 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2873 allows you to use SLIP over a regular dial up shell connection. If
2874 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2875 NET-3-HOWTO, available from
2876 <http://www.tldp.org/docs.html#howto>, explains how to
2877 configure SLIP. Note that you don't need this option if you just
2878 want to run term (term is a program which gives you almost full
2879 Internet connectivity if you have a regular dial up shell account on
2880 some Internet connected Unix computer. Read
2881 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2882 support will enlarge your kernel by about 4 KB. If unsure, say N.
2884 To compile this driver as a module, choose M here. The module
2885 will be called slip.
2887 config SLIP_COMPRESSED
2888 bool "CSLIP compressed headers"
2892 This protocol is faster than SLIP because it uses compression on the
2893 TCP/IP headers (not on the data itself), but it has to be supported
2894 on both ends. Ask your access provider if you are not sure and
2895 answer Y, just in case. You will still be able to use plain SLIP. If
2896 you plan to use SLiRP, the SLIP emulator (available from
2897 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2898 allows you to use SLIP over a regular dial up shell connection, you
2899 definitely want to say Y here. The NET-3-HOWTO, available from
2900 <http://www.tldp.org/docs.html#howto>, explains how to configure
2901 CSLIP. This won't enlarge your kernel.
2906 This option enables Van Jacobsen serial line header compression
2910 bool "Keepalive and linefill"
2913 Adds additional capabilities to the SLIP driver to support the
2914 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2917 config SLIP_MODE_SLIP6
2918 bool "Six bit SLIP encapsulation"
2921 Just occasionally you may need to run IP over hostile serial
2922 networks that don't pass all control characters or are only seven
2923 bit. Saying Y here adds an extra mode you can use with SLIP:
2924 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2925 the serial device. Naturally, this has to be supported at the other
2926 end of the link as well. It's good enough, for example, to run IP
2927 over the async ports of a Camtec JNT Pad. If unsure, say N.
2930 bool "Fibre Channel driver support"
2931 depends on SCSI && PCI
2933 Fibre Channel is a high speed serial protocol mainly used to connect
2934 large storage devices to the computer; it is compatible with and
2935 intended to replace SCSI.
2937 If you intend to use Fibre Channel, you need to have a Fibre channel
2938 adaptor card in your computer; say Y here and to the driver for your
2939 adaptor below. You also should have said Y to "SCSI support" and
2940 "SCSI generic support".
2943 tristate "Network console logging support (EXPERIMENTAL)"
2944 depends on EXPERIMENTAL
2946 If you want to log kernel messages over the network, enable this.
2947 See <file:Documentation/networking/netconsole.txt> for details.
2949 config NETCONSOLE_DYNAMIC
2950 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
2951 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
2954 This option enables the ability to dynamically reconfigure target
2955 parameters (interface, IP addresses, port numbers, MAC addresses)
2956 at runtime through a userspace interface exported using configfs.
2957 See <file:Documentation/networking/netconsole.txt> for details.
2963 bool "Netpoll traffic trapping"
2967 config NET_POLL_CONTROLLER
2971 tristate "Virtio network driver (EXPERIMENTAL)"
2972 depends on EXPERIMENTAL && VIRTIO
2974 This is the virtual network driver for virtio. It can be used with
2975 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.