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.
29 config NETDEVICES_MULTIQUEUE
30 bool "Netdevice multiple hardware queue support"
32 Say Y here if you want to allow the network stack to use multiple
33 hardware TX queues on an ethernet device.
35 Most people will say N here.
38 tristate "Intermediate Functional Block support"
39 depends on NET_CLS_ACT
41 This is an intermediate driver that allows sharing of
43 To compile this driver as a module, choose M here: the module
44 will be called ifb. If you want to use more than one ifb
45 device at a time, you need to compile this driver as a module.
46 Instead of 'ifb', the devices will then be called 'ifb0',
48 Look at the iproute2 documentation directory for usage etc
51 tristate "Dummy net driver support"
53 This is essentially a bit-bucket device (i.e. traffic you send to
54 this device is consigned into oblivion) with a configurable IP
55 address. It is most commonly used in order to make your currently
56 inactive SLIP address seem like a real address for local programs.
57 If you use SLIP or PPP, you might want to say Y here. Since this
58 thing often comes in handy, the default is Y. It won't enlarge your
59 kernel either. What a deal. Read about it in the Network
60 Administrator's Guide, available from
61 <http://www.tldp.org/docs.html#guide>.
63 To compile this driver as a module, choose M here: the module
64 will be called dummy. If you want to use more than one dummy
65 device at a time, you need to compile this driver as a module.
66 Instead of 'dummy', the devices will then be called 'dummy0',
70 tristate "Bonding driver support"
73 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
74 Channels together. This is called 'Etherchannel' by Cisco,
75 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
77 The driver supports multiple bonding modes to allow for both high
78 performance and high availability operation.
80 Refer to <file:Documentation/networking/bonding.txt> for more
83 To compile this driver as a module, choose M here: the module
84 will be called bonding.
87 tristate "MAC-VLAN support (EXPERIMENTAL)"
88 depends on EXPERIMENTAL
90 This allows one to create virtual interfaces that map packets to
91 or from specific MAC addresses to a particular interface.
93 Macvlan devices can be added using the "ip" command from the
94 iproute2 package starting with the iproute2-2.6.23 release:
96 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
98 To compile this driver as a module, choose M here: the module
99 will be called macvlan.
102 tristate "EQL (serial line load balancing) support"
104 If you have two serial connections to some other computer (this
105 usually requires two modems and two telephone lines) and you use
106 SLIP (the protocol for sending Internet traffic over telephone
107 lines) or PPP (a better SLIP) on them, you can make them behave like
108 one double speed connection using this driver. Naturally, this has
109 to be supported at the other end as well, either with a similar EQL
110 Linux driver or with a Livingston Portmaster 2e.
112 Say Y if you want this and read
113 <file:Documentation/networking/eql.txt>. You may also want to read
114 section 6.2 of the NET-3-HOWTO, available from
115 <http://www.tldp.org/docs.html#howto>.
117 To compile this driver as a module, choose M here: the module
118 will be called eql. If unsure, say N.
121 tristate "Universal TUN/TAP device driver support"
124 TUN/TAP provides packet reception and transmission for user space
125 programs. It can be viewed as a simple Point-to-Point or Ethernet
126 device, which instead of receiving packets from a physical media,
127 receives them from user space program and instead of sending packets
128 via physical media writes them to the user space program.
130 When a program opens /dev/net/tun, driver creates and registers
131 corresponding net device tunX or tapX. After a program closed above
132 devices, driver will automatically delete tunXX or tapXX device and
133 all routes corresponding to it.
135 Please read <file:Documentation/networking/tuntap.txt> for more
138 To compile this driver as a module, choose M here: the module
141 If you don't know what to use this for, you don't need it.
144 tristate "Virtual ethernet pair device"
146 This device is a local ethernet tunnel. Devices are created in pairs.
147 When one end receives the packet it appears on its pair and vice
151 tristate "General Instruments Surfboard 1000"
154 This is a driver for the General Instrument (also known as
155 NextLevel) SURFboard 1000 internal
156 cable modem. This is an ISA card which is used by a number of cable
157 TV companies to provide cable modem access. It's a one-way
158 downstream-only cable modem, meaning that your upstream net link is
159 provided by your regular phone modem.
161 At present this driver only compiles as a module, so say M here if
162 you have this card. The module will be called sb1000. Then read
163 <file:Documentation/networking/README.sb1000> for information on how
164 to use this module, as it needs special ppp scripts for establishing
165 a connection. Further documentation and the necessary scripts can be
168 <http://www.jacksonville.net/~fventuri/>
169 <http://home.adelphia.net/~siglercm/sb1000.html>
170 <http://linuxpower.cx/~cable/>
172 If you don't have this card, of course say N.
174 source "drivers/net/arcnet/Kconfig"
176 source "drivers/net/phy/Kconfig"
182 menuconfig NET_ETHERNET
183 bool "Ethernet (10 or 100Mbit)"
186 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
187 type of Local Area Network (LAN) in universities and companies.
189 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
190 coaxial cable, linking computers in a chain), 10BASE-T or twisted
191 pair (10 Mbps over twisted pair cable, linking computers to central
192 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
193 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
194 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
195 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
196 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
197 Ethernet (1 Gbps over optical fiber or short copper links).
199 If your Linux machine will be connected to an Ethernet and you have
200 an Ethernet network interface card (NIC) installed in your computer,
201 say Y here and read the Ethernet-HOWTO, available from
202 <http://www.tldp.org/docs.html#howto>. You will then also have
203 to say Y to the driver for your particular NIC.
205 Note that the answer to this question won't directly affect the
206 kernel: saying N will just cause the configurator to skip all
207 the questions about Ethernet network cards. If unsure, say N.
212 tristate "Generic Media Independent Interface device support"
214 Most ethernet controllers have MII transceiver either as an external
215 or internal device. It is safe to say Y or M here even if your
216 ethernet card lack MII.
219 tristate "Atmel MACB support"
220 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91CAP9
223 The Atmel MACB ethernet interface is found on many AT32 and AT91
224 parts. Say Y to include support for the MACB chip.
226 To compile this driver as a module, choose M here: the module
229 source "drivers/net/arm/Kconfig"
232 tristate "ASIX AX88796 NE2000 clone support"
233 depends on ARM || MIPS || SUPERH
237 AX88796 driver, using platform bus to provide
238 chip detection and resources
241 bool "ASIX AX88796 external 93CX6 eeprom support"
245 Select this if your platform comes with an external 93CX6 eeprom.
248 tristate "MACE (Power Mac ethernet) support"
249 depends on PPC_PMAC && PPC32
252 Power Macintoshes and clones with Ethernet built-in on the
253 motherboard will usually use a MACE (Medium Access Control for
254 Ethernet) interface. Say Y to include support for the MACE chip.
256 To compile this driver as a module, choose M here: the module
259 config MACE_AAUI_PORT
260 bool "Use AAUI port instead of TP by default"
263 Some Apple machines (notably the Apple Network Server) which use the
264 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
265 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
266 Y here if you have such a machine. If unsure, say N.
267 The driver will default to AAUI on ANS anyway, and if you use it as
268 a module, you can provide the port_aaui=0|1 to force the driver.
271 tristate "BMAC (G3 ethernet) support"
272 depends on PPC_PMAC && PPC32
275 Say Y for support of BMAC Ethernet interfaces. These are used on G3
278 To compile this driver as a module, choose M here: the module
282 tristate "Ariadne support"
285 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
288 To compile this driver as a module, choose M here: the module
289 will be called ariadne.
292 tristate "A2065 support"
296 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
299 To compile this driver as a module, choose M here: the module
300 will be called a2065.
303 tristate "Hydra support"
307 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
309 To compile this driver as a module, choose M here: the module
310 will be called hydra.
313 tristate "Zorro NS8390-based Ethernet support"
317 This driver is for Zorro Ethernet cards using an NS8390-compatible
318 chipset, like the Village Tronic Ariadne II and the Individual
319 Computers X-Surf Ethernet cards. If you have such a card, say Y.
322 To compile this driver as a module, choose M here: the module
323 will be called zorro8390.
326 tristate "PCMCIA NE2000 support"
327 depends on AMIGA_PCMCIA
330 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
333 To compile this driver as a module, choose M here: the module
337 tristate "Apollo 3c505 support"
340 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
341 If you don't have one made for Apollos, you can use one from a PC,
342 except that your Apollo won't be able to boot from it (because the
343 code in the ROM will be for a PC).
346 bool "Macintosh NS 8390 based ethernet cards"
350 If you want to include a driver to support Nubus or LC-PDS
351 Ethernet cards using an NS8390 chipset or its equivalent, say Y
352 and read the Ethernet-HOWTO, available from
353 <http://www.tldp.org/docs.html#howto>.
356 tristate "Macintosh CS89x0 based ethernet cards"
359 Support for CS89x0 chipset based Ethernet cards. If you have a
360 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
361 read the Ethernet-HOWTO, available from
362 <http://www.tldp.org/docs.html#howto>.
364 To compile this driver as a module, choose M here. This module will
368 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
371 Support for NatSemi SONIC based Ethernet devices. This includes
372 the onboard Ethernet in many Quadras as well as some LC-PDS,
373 a few Nubus and all known Comm Slot Ethernet cards. If you have
374 one of these say Y and read the Ethernet-HOWTO, available from
375 <http://www.tldp.org/docs.html#howto>.
377 To compile this driver as a module, choose M here. This module will
381 bool "Macintosh (AV) onboard MACE ethernet"
385 Support for the onboard AMD 79C940 MACE Ethernet controller used in
386 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
387 say Y and read the Ethernet-HOWTO, available from
388 <http://www.tldp.org/docs.html#howto>.
391 tristate "MVME147 (Lance) Ethernet support"
395 Support for the on-board Ethernet interface on the Motorola MVME147
396 single-board computer. Say Y here to include the
397 driver for this chip in your kernel.
398 To compile this driver as a module, choose M here.
401 tristate "MVME16x Ethernet support"
404 This is the driver for the Ethernet interface on the Motorola
405 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
406 driver for this chip in your kernel.
407 To compile this driver as a module, choose M here.
410 tristate "BVME6000 Ethernet support"
413 This is the driver for the Ethernet interface on BVME4000 and
414 BVME6000 VME boards. Say Y here to include the driver for this chip
416 To compile this driver as a module, choose M here.
419 tristate "Atari Lance support"
422 Say Y to include support for several Atari Ethernet adapters based
423 on the AMD Lance chipset: RieblCard (with or without battery), or
424 PAMCard VME (also the version by Rhotron, with different addresses).
427 tristate "Sun3/Sun3x on-board LANCE support"
428 depends on SUN3 || SUN3X
430 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
431 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
432 here to compile in the Linux driver for this and enable Ethernet.
433 General Linux information on the Sun 3 and 3x series (now
435 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
437 If you're not building a kernel for a Sun 3, say N.
440 bool "Sun3 on-board Intel 82586 support"
443 This driver enables support for the on-board Intel 82586 based
444 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
445 that this driver does not support 82586-based adapters on additional
449 bool "HP on-board LANCE support"
453 If you want to use the builtin "LANCE" Ethernet controller on an
454 HP300 machine, say Y here.
457 tristate "Lasi ethernet"
460 Say Y here to support the builtin Intel 82596 ethernet controller
461 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
464 tristate "SNI RM ethernet"
465 depends on NET_ETHERNET && SNI_RM
467 Say Y here to support the on-board Intel 82596 ethernet controller
468 built into SNI RM machines.
471 tristate "Korina (IDT RC32434) Ethernet support"
472 depends on NET_ETHERNET && MIKROTIK_RB532
474 If you have a Mikrotik RouterBoard 500 or IDT RC32434
475 based system say Y. Otherwise say N.
477 config MIPS_JAZZ_SONIC
478 tristate "MIPS JAZZ onboard SONIC Ethernet support"
481 This is the driver for the onboard card of MIPS Magnum 4000,
482 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
484 config MIPS_AU1X00_ENET
485 bool "MIPS AU1000 Ethernet support"
486 depends on SOC_AU1X00
490 If you have an Alchemy Semi AU1X00 based system
491 say Y. Otherwise, say N.
494 bool "SGI IOC3 Ethernet"
495 depends on PCI && SGI_IP27
499 If you have a network (Ethernet) card of this type, say Y and read
500 the Ethernet-HOWTO, available from
501 <http://www.tldp.org/docs.html#howto>.
504 tristate "MIPS simulator Network device"
507 The MIPSNET device is a simple Ethernet network device which is
508 emulated by the MIPS Simulator.
509 If you are not using a MIPSsim or are unsure, say N.
511 config SGI_O2MACE_ETH
512 tristate "SGI O2 MACE Fast Ethernet support"
513 depends on SGI_IP32=y
516 tristate "National DP83902AV support"
520 Support for cards based on the National Semiconductor DP83902AV
521 ST-NIC Serial Network Interface Controller for Twisted Pair. This
522 is a 10Mbit/sec Ethernet controller. Product overview and specs at
523 <http://www.national.com/pf/DP/DP83902A.html>.
528 tristate "Sun LANCE support"
532 This driver supports the "le" interface present on all 32-bit Sparc
533 systems, on some older Ultra systems and as an Sbus option. These
534 cards are based on the AMD Lance chipset, which is better known
535 via the NE2100 cards.
537 To compile this driver as a module, choose M here: the module
538 will be called sunlance.
541 tristate "Sun Happy Meal 10/100baseT support"
542 depends on SBUS || PCI
545 This driver supports the "hme" interface present on most Ultra
546 systems and as an option on older Sbus systems. This driver supports
547 both PCI and Sbus devices. This driver also supports the "qfe" quad
548 100baseT device available in both PCI and Sbus configurations.
550 To compile this driver as a module, choose M here: the module
551 will be called sunhme.
554 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
555 depends on SBUS && EXPERIMENTAL
558 This driver supports the "be" interface available as an Sbus option.
559 This is Sun's older 100baseT Ethernet device.
561 To compile this driver as a module, choose M here: the module
562 will be called sunbmac.
565 tristate "Sun QuadEthernet support"
569 This driver supports the "qe" 10baseT Ethernet device, available as
570 an Sbus option. Note that this is not the same as Quad FastEthernet
571 "qfe" which is supported by the Happy Meal driver instead.
573 To compile this driver as a module, choose M here: the module
574 will be called sunqe.
577 tristate "Sun GEM support"
581 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
582 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
585 tristate "Sun Cassini support"
589 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
590 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
593 tristate "Sun Virtual Network support"
596 Support for virtual network devices under Sun Logical Domains.
598 config NET_VENDOR_3COM
600 depends on ISA || EISA || MCA || PCI
602 If you have a network (Ethernet) card belonging to this class, say Y
603 and read the Ethernet-HOWTO, available from
604 <http://www.tldp.org/docs.html#howto>.
606 Note that the answer to this question doesn't directly affect the
607 kernel: saying N will just cause the configurator to skip all
608 the questions about 3COM cards. If you say Y, you will be asked for
609 your specific card in the following questions.
612 tristate "3c501 \"EtherLink\" support"
613 depends on NET_VENDOR_3COM && ISA
615 If you have a network (Ethernet) card of this type, say Y and read
616 the Ethernet-HOWTO, available from
617 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
618 new card, since the 3c501 is slow, broken, and obsolete: you will
619 have problems. Some people suggest to ping ("man ping") a nearby
620 machine every minute ("man cron") when using this card.
622 To compile this driver as a module, choose M here. The module
623 will be called 3c501.
626 tristate "3c503 \"EtherLink II\" support"
627 depends on NET_VENDOR_3COM && ISA
630 If you have a network (Ethernet) card of this type, say Y and read
631 the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>.
634 To compile this driver as a module, choose M here. The module
635 will be called 3c503.
638 tristate "3c505 \"EtherLink Plus\" support"
639 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
641 Information about this network (Ethernet) card can be found in
642 <file:Documentation/networking/3c505.txt>. If you have a card of
643 this type, say Y and read the Ethernet-HOWTO, available from
644 <http://www.tldp.org/docs.html#howto>.
646 To compile this driver as a module, choose M here. The module
647 will be called 3c505.
650 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
651 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
653 If you have a network (Ethernet) card of this type, say Y and read
654 the Ethernet-HOWTO, available from
655 <http://www.tldp.org/docs.html#howto>.
657 To compile this driver as a module, choose M here. The module
658 will be called 3c507.
661 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
662 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
664 If you have a network (Ethernet) card belonging to the 3Com
665 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
666 from <http://www.tldp.org/docs.html#howto>.
668 If your card is not working you may need to use the DOS
669 setup disk to disable Plug & Play mode, and to select the default
672 To compile this driver as a module, choose M here. The module
673 will be called 3c509.
676 tristate "3c515 ISA \"Fast EtherLink\""
677 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
679 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
680 network card, say Y and read the Ethernet-HOWTO, available from
681 <http://www.tldp.org/docs.html#howto>.
683 To compile this driver as a module, choose M here. The module
684 will be called 3c515.
687 tristate "3c523 \"EtherLink/MC\" support"
688 depends on NET_VENDOR_3COM && MCA_LEGACY
690 If you have a network (Ethernet) card of this type, say Y and read
691 the Ethernet-HOWTO, available from
692 <http://www.tldp.org/docs.html#howto>.
694 To compile this driver as a module, choose M here. The module
695 will be called 3c523.
698 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
699 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
701 If you have a network (Ethernet) card of this type, say Y and read
702 the Ethernet-HOWTO, available from
703 <http://www.tldp.org/docs.html#howto>.
705 To compile this driver as a module, choose M here. The module
706 will be called 3c527.
709 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
710 depends on NET_VENDOR_3COM && (PCI || EISA)
713 This option enables driver support for a large number of 10Mbps and
714 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
716 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
717 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
718 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
719 "Tornado" (3c905) PCI
720 "Hurricane" (3c555/3cSOHO) PCI
722 If you have such a card, say Y and read the Ethernet-HOWTO,
723 available from <http://www.tldp.org/docs.html#howto>. More
724 specific information is in
725 <file:Documentation/networking/vortex.txt> and in the comments at
726 the beginning of <file:drivers/net/3c59x.c>.
728 To compile this support as a module, choose M here.
731 tristate "3cr990 series \"Typhoon\" support"
732 depends on NET_VENDOR_3COM && PCI
735 This option enables driver support for the 3cr990 series of cards:
737 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
738 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
739 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
741 If you have a network (Ethernet) card of this type, say Y and read
742 the Ethernet-HOWTO, available from
743 <http://www.tldp.org/docs.html#howto>.
745 To compile this driver as a module, choose M here. The module
746 will be called typhoon.
749 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
750 depends on ISA && ISA_DMA_API
752 If you have a network (Ethernet) card of this type, say Y and read
753 the Ethernet-HOWTO, available from
754 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
757 To compile this driver as a module, choose M here: the module
758 will be called lance. This is recommended.
760 config NET_VENDOR_SMC
761 bool "Western Digital/SMC cards"
762 depends on ISA || MCA || EISA || MAC
764 If you have a network (Ethernet) card belonging to this class, say Y
765 and read the Ethernet-HOWTO, available from
766 <http://www.tldp.org/docs.html#howto>.
768 Note that the answer to this question doesn't directly affect the
769 kernel: saying N will just cause the configurator to skip all
770 the questions about Western Digital cards. If you say Y, you will be
771 asked for your specific card in the following questions.
774 tristate "WD80*3 support"
775 depends on NET_VENDOR_SMC && ISA
778 If you have a network (Ethernet) card of this type, say Y and read
779 the Ethernet-HOWTO, available from
780 <http://www.tldp.org/docs.html#howto>.
782 To compile this driver as a module, choose M here. The module
786 tristate "SMC Ultra MCA support"
787 depends on NET_VENDOR_SMC && MCA
790 If you have a network (Ethernet) card of this type and are running
791 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
792 available from <http://www.tldp.org/docs.html#howto>.
794 To compile this driver as a module, choose M here. The module
795 will be called smc-mca.
798 tristate "SMC Ultra support"
799 depends on NET_VENDOR_SMC && ISA
802 If you have a network (Ethernet) card of this type, say Y and read
803 the Ethernet-HOWTO, available from
804 <http://www.tldp.org/docs.html#howto>.
806 Important: There have been many reports that, with some motherboards
807 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
808 such as some BusLogic models) causes corruption problems with many
809 operating systems. The Linux smc-ultra driver has a work-around for
810 this but keep it in mind if you have such a SCSI card and have
813 To compile this driver as a module, choose M here. The module
814 will be called smc-ultra.
817 tristate "SMC Ultra32 EISA support"
818 depends on NET_VENDOR_SMC && EISA
821 If you have a network (Ethernet) card of this type, say Y and read
822 the Ethernet-HOWTO, available from
823 <http://www.tldp.org/docs.html#howto>.
825 To compile this driver as a module, choose M here. The module
826 will be called smc-ultra32.
829 tristate "Blackfin 527/536/537 on-chip mac support"
830 depends on NET_ETHERNET && (BF527 || BF537 || BF536)
834 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
836 This is the driver for blackfin on-chip mac device. Say Y if you want it
837 compiled into the kernel. This driver is also available as a module
838 ( = code which can be inserted in and removed from the running kernel
839 whenever you want). The module will be called bfin_mac.
841 config BFIN_MAC_USE_L1
842 bool "Use L1 memory for rx/tx packets"
843 depends on BFIN_MAC && (BF527 || BF537)
846 To get maximum network performance, you should use L1 memory as rx/tx buffers.
847 Say N here if you want to reserve L1 memory for other uses.
849 config BFIN_TX_DESC_NUM
850 int "Number of transmit buffer packets"
852 range 6 10 if BFIN_MAC_USE_L1
856 Set the number of buffer packets used in driver.
858 config BFIN_RX_DESC_NUM
859 int "Number of receive buffer packets"
861 range 20 100 if BFIN_MAC_USE_L1
865 Set the number of buffer packets used in driver.
868 bool "RMII PHY Interface (EXPERIMENTAL)"
869 depends on BFIN_MAC && EXPERIMENTAL
870 default y if BFIN527_EZKIT
871 default n if BFIN537_STAMP
873 Use Reduced PHY MII Interface
876 tristate "SMC 9194 support"
877 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
880 This is support for the SMC9xxx based Ethernet cards. Choose this
881 option if you have a DELL laptop with the docking station, or
882 another SMC9192/9194 based chipset. Say Y if you want it compiled
883 into the kernel, and read the file
884 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
885 available from <http://www.tldp.org/docs.html#howto>.
887 To compile this driver as a module, choose M here. The module
888 will be called smc9194.
891 tristate "SMC 91C9x/91C1xxx support"
894 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
895 SOC_AU1X00 || BLACKFIN || MN10300
897 This is a driver for SMC's 91x series of Ethernet chipsets,
898 including the SMC91C94 and the SMC91C111. Say Y if you want it
899 compiled into the kernel, and read the file
900 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
901 available from <http://www.linuxdoc.org/docs.html#howto>.
903 This driver is also available as a module ( = code which can be
904 inserted in and removed from the running kernel whenever you want).
905 The module will be called smc91x. If you want to compile it as a
906 module, say M here and read <file:Documentation/kbuild/modules.txt>.
909 tristate "NetX Ethernet support"
913 This is support for the Hilscher netX builtin Ethernet ports
915 To compile this driver as a module, choose M here. The module
916 will be called netx-eth.
919 tristate "DM9000 support"
920 depends on ARM || BLACKFIN || MIPS
924 Support for DM9000 chipset.
926 To compile this driver as a module, choose M here. The module
927 will be called dm9000.
930 tristate "ENC28J60 support"
931 depends on EXPERIMENTAL && SPI && NET_ETHERNET
934 Support for the Microchip EN28J60 ethernet chip.
936 To compile this driver as a module, choose M here. The module will be
939 config ENC28J60_WRITEVERIFY
940 bool "Enable write verify"
943 Enable the verify after the buffer write useful for debugging purpose.
946 config DM9000_DEBUGLEVEL
947 int "DM9000 maximum debug level"
951 The maximum level of debugging code compiled into the DM9000
955 tristate "SMSC LAN911[5678] support"
958 depends on ARCH_PXA || SH_MAGIC_PANEL_R2
960 This is a driver for SMSC's LAN911x series of Ethernet chipsets
961 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
962 Say Y if you want it compiled into the kernel,
963 and read the Ethernet-HOWTO, available from
964 <http://www.linuxdoc.org/docs.html#howto>.
966 This driver is also available as a module. The module will be
967 called smc911x. If you want to compile it as a module, say M
968 here and read <file:Documentation/kbuild/modules.txt>
970 config NET_VENDOR_RACAL
971 bool "Racal-Interlan (Micom) NI cards"
974 If you have a network (Ethernet) card belonging to this class, such
975 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
976 available from <http://www.tldp.org/docs.html#howto>.
978 Note that the answer to this question doesn't directly affect the
979 kernel: saying N will just cause the configurator to skip all
980 the questions about NI cards. If you say Y, you will be asked for
981 your specific card in the following questions.
984 tristate "NI5010 support (EXPERIMENTAL)"
985 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
987 If you have a network (Ethernet) card of this type, say Y and read
988 the Ethernet-HOWTO, available from
989 <http://www.tldp.org/docs.html#howto>. Note that this is still
992 To compile this driver as a module, choose M here. The module
993 will be called ni5010.
996 tristate "NI5210 support"
997 depends on NET_VENDOR_RACAL && ISA
999 If you have a network (Ethernet) card of this type, say Y and read
1000 the Ethernet-HOWTO, available from
1001 <http://www.tldp.org/docs.html#howto>.
1003 To compile this driver as a module, choose M here. The module
1004 will be called ni52.
1007 tristate "NI6510 support"
1008 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1010 If you have a network (Ethernet) card of this type, say Y and read
1011 the Ethernet-HOWTO, available from
1012 <http://www.tldp.org/docs.html#howto>.
1014 To compile this driver as a module, choose M here. The module
1015 will be called ni65.
1017 source "drivers/net/tulip/Kconfig"
1020 tristate "AT1700/1720 support (EXPERIMENTAL)"
1021 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1024 If you have a network (Ethernet) card of this type, say Y and read
1025 the Ethernet-HOWTO, available from
1026 <http://www.tldp.org/docs.html#howto>.
1028 To compile this driver as a module, choose M here. The module
1029 will be called at1700.
1032 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1033 depends on ISA || EISA || MCA
1036 If you have a network (Ethernet) card of this type, say Y and read
1037 the Ethernet-HOWTO, available from
1038 <http://www.tldp.org/docs.html#howto> as well as
1039 <file:drivers/net/depca.c>.
1041 To compile this driver as a module, choose M here. The module
1042 will be called depca.
1045 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1046 depends on ISA || EISA || PCI
1048 If you have a network (Ethernet) card of this type, say Y and read
1049 the Ethernet-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto>.
1052 To compile this driver as a module, choose M here. The module
1053 will be called hp100.
1056 bool "Other ISA cards"
1059 If your network (Ethernet) card hasn't been mentioned yet and its
1060 bus system (that's the way the cards talks to the other components
1061 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1062 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1063 available from <http://www.tldp.org/docs.html#howto>.
1067 Note that the answer to this question doesn't directly affect the
1068 kernel: saying N will just cause the configurator to skip all
1069 the remaining ISA network card questions. If you say Y, you will be
1070 asked for your specific card in the following questions.
1073 tristate "Cabletron E21xx support"
1077 If you have a network (Ethernet) card of this type, say Y and read
1078 the Ethernet-HOWTO, available from
1079 <http://www.tldp.org/docs.html#howto>.
1081 To compile this driver as a module, choose M here. The module
1082 will be called e2100.
1085 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1089 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1090 cards. If this is for you, say Y and read
1091 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1092 well as the Ethernet-HOWTO, available from
1093 <http://www.tldp.org/docs.html#howto>.
1095 To compile this driver as a module, choose M here. The module
1096 will be called ewrk3.
1099 tristate "EtherExpress 16 support"
1102 If you have an EtherExpress16 network (Ethernet) card, say Y and
1103 read the Ethernet-HOWTO, available from
1104 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1105 EtherExpress16 card used to be regarded as a very poor choice
1106 because the driver was very unreliable. We now have a new driver
1107 that should do better.
1109 To compile this driver as a module, choose M here. The module
1110 will be called eexpress.
1113 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1116 If you have a network (Ethernet) card of this type, say Y. This
1117 driver supports Intel i82595{FX,TX} based boards. Note however
1118 that the EtherExpress PRO/100 Ethernet card has its own separate
1119 driver. Please read the Ethernet-HOWTO, available from
1120 <http://www.tldp.org/docs.html#howto>.
1122 To compile this driver as a module, choose M here. The module
1123 will be called eepro.
1126 tristate "HP PCLAN+ (27247B and 27252A) support"
1130 If you have a network (Ethernet) card of this type, say Y and read
1131 the Ethernet-HOWTO, available from
1132 <http://www.tldp.org/docs.html#howto>.
1134 To compile this driver as a module, choose M here. The module
1135 will be called hp-plus.
1138 tristate "HP PCLAN (27245 and other 27xxx series) support"
1142 If you have a network (Ethernet) card of this type, say Y and read
1143 the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1146 To compile this driver as a module, choose M here. The module
1150 tristate "LP486E on board Ethernet"
1153 Say Y here to support the 82596-based on-board Ethernet controller
1154 for the Panther motherboard, which is one of the two shipped in the
1155 Intel Professional Workstation.
1158 tristate "ICL EtherTeam 16i/32 support"
1161 If you have a network (Ethernet) card of this type, say Y and read
1162 the Ethernet-HOWTO, available from
1163 <http://www.tldp.org/docs.html#howto>.
1165 To compile this driver as a module, choose M here. The module
1166 will be called eth16i.
1169 tristate "NE2000/NE1000 support"
1170 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1173 If you have a network (Ethernet) card of this type, say Y and read
1174 the Ethernet-HOWTO, available from
1175 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1176 without a specific driver are compatible with NE2000.
1178 If you have a PCI NE2000 card however, say N here and Y to "PCI
1179 NE2000 and clone support" under "EISA, VLB, PCI and on board
1180 controllers" below. If you have a NE2000 card and are running on
1181 an MCA system (a bus system used on some IBM PS/2 computers and
1182 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1185 To compile this driver as a module, choose M here. The module
1189 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1190 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1192 The Zenith Z-Note notebook computer has a built-in network
1193 (Ethernet) card, and this is the Linux driver for it. Note that the
1194 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1195 by this driver. Read the Ethernet-HOWTO, available from
1196 <http://www.tldp.org/docs.html#howto>.
1199 tristate "SEEQ8005 support (EXPERIMENTAL)"
1200 depends on NET_ISA && EXPERIMENTAL
1202 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1203 is for you, read the Ethernet-HOWTO, available from
1204 <http://www.tldp.org/docs.html#howto>.
1206 To compile this driver as a module, choose M here. The module
1207 will be called seeq8005.
1210 tristate "NE/2 (ne2000 MCA version) support"
1211 depends on MCA_LEGACY
1214 If you have a network (Ethernet) card of this type, say Y and read
1215 the Ethernet-HOWTO, available from
1216 <http://www.tldp.org/docs.html#howto>.
1218 To compile this driver as a module, choose M here. The module
1222 tristate "IBM LAN Adapter/A support"
1225 This is a Micro Channel Ethernet adapter. You need to set
1226 CONFIG_MCA to use this driver. It is both available as an in-kernel
1227 driver and as a module.
1229 To compile this driver as a module, choose M here. The only
1230 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1231 will both support 16K and 32K memory windows, however a 32K window
1232 gives a better security against packet losses. Usage of multiple
1233 boards with this driver should be possible, but has not been tested
1234 up to now due to lack of hardware.
1237 tristate "IBM LAN Virtual Ethernet support"
1238 depends on PPC_PSERIES
1240 This driver supports virtual ethernet adapters on newer IBM iSeries
1241 and pSeries systems.
1243 To compile this driver as a module, choose M here. The module will
1246 source "drivers/net/ibm_emac/Kconfig"
1247 source "drivers/net/ibm_newemac/Kconfig"
1250 bool "EISA, VLB, PCI and on board controllers"
1251 depends on ISA || EISA || PCI
1253 This is another class of network cards which attach directly to the
1254 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1255 available from <http://www.tldp.org/docs.html#howto>.
1257 Note that the answer to this question doesn't directly affect the
1258 kernel: saying N will just cause the configurator to skip all
1259 the questions about this class of network cards. If you say Y, you
1260 will be asked for your specific card in the following questions. If
1261 you are unsure, say Y.
1264 tristate "AMD PCnet32 PCI support"
1265 depends on NET_PCI && PCI
1269 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1270 answer Y here and read the Ethernet-HOWTO, available from
1271 <http://www.tldp.org/docs.html#howto>.
1273 To compile this driver as a module, choose M here. The module
1274 will be called pcnet32.
1277 bool "Use RX polling (NAPI)"
1280 NAPI is a new driver API designed to reduce CPU and interrupt load
1281 when the driver is receiving lots of packets from the card. It is
1282 still somewhat experimental and thus not yet enabled by default.
1284 If your estimated Rx load is 10kpps or more, or if the card will be
1285 deployed on potentially unfriendly networks (e.g. in a firewall),
1291 tristate "AMD 8111 (new PCI lance) support"
1292 depends on NET_PCI && PCI
1296 If you have an AMD 8111-based PCI lance ethernet card,
1297 answer Y here and read the Ethernet-HOWTO, available from
1298 <http://www.tldp.org/docs.html#howto>.
1300 To compile this driver as a module, choose M here. The module
1301 will be called amd8111e.
1303 config AMD8111E_NAPI
1304 bool "Use RX polling (NAPI)"
1305 depends on AMD8111_ETH
1307 NAPI is a new driver API designed to reduce CPU and interrupt load
1308 when the driver is receiving lots of packets from the card. It is
1309 still somewhat experimental and thus not yet enabled by default.
1311 If your estimated Rx load is 10kpps or more, or if the card will be
1312 deployed on potentially unfriendly networks (e.g. in a firewall),
1317 config ADAPTEC_STARFIRE
1318 tristate "Adaptec Starfire/DuraLAN support"
1319 depends on NET_PCI && PCI
1323 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1324 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1325 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1328 To compile this driver as a module, choose M here: the module
1329 will be called starfire. This is recommended.
1331 config ADAPTEC_STARFIRE_NAPI
1332 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1333 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1335 NAPI is a new driver API designed to reduce CPU and interrupt load
1336 when the driver is receiving lots of packets from the card. It is
1337 still somewhat experimental and thus not yet enabled by default.
1339 If your estimated Rx load is 10kpps or more, or if the card will be
1340 deployed on potentially unfriendly networks (e.g. in a firewall),
1346 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1347 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1350 If you have a network (Ethernet) card of this type, say Y and read
1351 the Ethernet-HOWTO, available from
1352 <http://www.tldp.org/docs.html#howto>.
1354 To compile this driver as a module, choose M here. The module
1355 will be called ac3200.
1358 tristate "Apricot Xen-II on board Ethernet"
1359 depends on NET_PCI && ISA
1361 If you have a network (Ethernet) controller of this type, say Y and
1362 read the Ethernet-HOWTO, available from
1363 <http://www.tldp.org/docs.html#howto>.
1365 To compile this driver as a module, choose M here. The module
1366 will be called apricot.
1369 tristate "Broadcom 440x/47xx ethernet support"
1370 depends on SSB_POSSIBLE
1374 If you have a network (Ethernet) controller of this type, say Y
1375 or M and 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
1381 # Auto-select SSB PCI-HOST support, if possible
1382 config B44_PCI_AUTOSELECT
1384 depends on B44 && SSB_PCIHOST_POSSIBLE
1388 # Auto-select SSB PCICORE driver, if possible
1389 config B44_PCICORE_AUTOSELECT
1391 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1392 select SSB_DRIVER_PCICORE
1397 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1401 tristate "nForce Ethernet support"
1402 depends on NET_PCI && PCI
1404 If you have a network (Ethernet) controller of this type, say Y and
1405 read the Ethernet-HOWTO, available from
1406 <http://www.tldp.org/docs.html#howto>.
1408 To compile this driver as a module, choose M here. The module
1409 will be called forcedeth.
1411 config FORCEDETH_NAPI
1412 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1413 depends on FORCEDETH && EXPERIMENTAL
1415 NAPI is a new driver API designed to reduce CPU and interrupt load
1416 when the driver is receiving lots of packets from the card. It is
1417 still somewhat experimental and thus not yet enabled by default.
1419 If your estimated Rx load is 10kpps or more, or if the card will be
1420 deployed on potentially unfriendly networks (e.g. in a firewall),
1426 tristate "CS89x0 support"
1427 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1429 Support for CS89x0 chipset based Ethernet cards. If you have a
1430 network (Ethernet) card of this type, say Y and read the
1431 Ethernet-HOWTO, available from
1432 <http://www.tldp.org/docs.html#howto> as well as
1433 <file:Documentation/networking/cs89x0.txt>.
1435 To compile this driver as a module, choose M here. The module
1436 will be called cs89x0.
1439 tristate "TOSHIBA TC35815 Ethernet support"
1440 depends on NET_PCI && PCI && MIPS
1444 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1445 depends on NET_PCI && PCI
1448 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1449 card, say Y and read 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 eepro100.
1457 tristate "Intel(R) PRO/100+ support"
1458 depends on NET_PCI && PCI
1461 This driver supports Intel(R) PRO/100 family of adapters.
1462 To verify that your adapter is supported, find the board ID number
1463 on the adapter. Look for a label that has a barcode and a number
1464 in the format 123456-001 (six digits hyphen three digits).
1466 Use the above information and the Adapter & Driver ID Guide at:
1468 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1470 to identify the adapter.
1472 For the latest Intel PRO/100 network driver for Linux, see:
1474 <http://appsr.intel.com/scripts-df/support_intel.asp>
1476 More specific information on configuring the driver is in
1477 <file:Documentation/networking/e100.txt>.
1479 To compile this driver as a module, choose M here. The module
1480 will be called e100.
1483 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1484 depends on NET_PCI && EISA && EXPERIMENTAL
1487 If you have a network (Ethernet) card of this type, say Y and read
1488 the Ethernet-HOWTO, available from
1489 <http://www.tldp.org/docs.html#howto>.
1491 To compile this driver as a module, choose M here. The module
1492 will be called lne390.
1495 tristate "Myson MTD-8xx PCI Ethernet support"
1496 depends on NET_PCI && PCI
1500 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1501 cards. Specifications and data at
1502 <http://www.myson.com.hk/mtd/datasheet/>.
1505 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1506 depends on NET_PCI && PCI
1509 This driver is for the National Semiconductor DP83810 series,
1510 which is used in cards from PureData, NetGear, Linksys
1511 and others, including the 83815 chip.
1512 More specific information and updates are available from
1513 <http://www.scyld.com/network/natsemi.html>.
1516 tristate "PCI NE2000 and clones support (see help)"
1517 depends on NET_PCI && PCI
1520 This driver is for NE2000 compatible PCI cards. It will not work
1521 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1522 support" below). If you have a PCI NE2000 network (Ethernet) card,
1523 say Y and read the Ethernet-HOWTO, available from
1524 <http://www.tldp.org/docs.html#howto>.
1526 This driver also works for the following NE2000 clone cards:
1527 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1528 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1529 Holtek HT80232 Holtek HT80229
1531 To compile this driver as a module, choose M here. The module
1532 will be called ne2k-pci.
1535 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1536 depends on NET_PCI && EISA && EXPERIMENTAL
1539 If you have a network (Ethernet) card of this type, say Y and read
1540 the Ethernet-HOWTO, available from
1541 <http://www.tldp.org/docs.html#howto>. Note that this driver
1542 will NOT WORK for NE3200 cards as they are completely different.
1544 To compile this driver as a module, choose M here. The module
1545 will be called ne3210.
1548 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1549 depends on NET_PCI && EISA && EXPERIMENTAL
1552 If you have a network (Ethernet) card of this type, say Y and read
1553 the Ethernet-HOWTO, available from
1554 <http://www.tldp.org/docs.html#howto>.
1556 To compile this driver as a module, choose M here. The module
1557 will be called es3210.
1560 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1561 depends on NET_PCI && PCI && EXPERIMENTAL
1565 This is a driver for the Fast Ethernet PCI network cards based on
1566 the RTL8139C+ chips. If you have one of those, say Y and read
1567 the Ethernet-HOWTO, available from
1568 <http://www.tldp.org/docs.html#howto>.
1570 To compile this driver as a module, choose M here: the module
1571 will be called 8139cp. This is recommended.
1574 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1575 depends on NET_PCI && PCI
1579 This is a driver for the Fast Ethernet PCI network cards based on
1580 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1581 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1583 To compile this driver as a module, choose M here: the module
1584 will be called 8139too. This is recommended.
1587 bool "Use PIO instead of MMIO"
1591 This instructs the driver to use programmed I/O ports (PIO) instead
1592 of PCI shared memory (MMIO). This can possibly solve some problems
1593 in case your mainboard has memory consistency issues. If unsure,
1596 config 8139TOO_TUNE_TWISTER
1597 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1600 This implements a function which might come in handy in case you
1601 are using low quality on long cabling. It is required for RealTek
1602 RTL-8139 revision K boards, and totally unused otherwise. It tries
1603 to match the transceiver to the cable characteristics. This is
1604 experimental since hardly documented by the manufacturer.
1608 bool "Support for older RTL-8129/8130 boards"
1611 This enables support for the older and uncommon RTL-8129 and
1612 RTL-8130 chips, which support MII via an external transceiver,
1613 instead of an internal one. Disabling this option will save some
1614 memory by making the code size smaller. If unsure, say Y.
1616 config 8139_OLD_RX_RESET
1617 bool "Use older RX-reset method"
1620 The 8139too driver was recently updated to contain a more rapid
1621 reset sequence, in the face of severe receive errors. This "new"
1622 RX-reset method should be adequate for all boards. But if you
1623 experience problems, you can enable this option to restore the
1624 old RX-reset behavior. If unsure, say N.
1627 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1628 depends on NET_PCI && PCI
1632 This is a driver for the R6040 Fast Ethernet MACs found in the
1633 the RDC R-321x System-on-chips.
1635 To compile this driver as a module, choose M here: the module
1636 will be called r6040. This is recommended.
1639 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1640 depends on NET_PCI && PCI
1644 This is a driver for the Fast Ethernet PCI network cards based on
1645 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1646 SiS 630 and SiS 540 chipsets.
1648 This driver also supports AMD 79C901 HomePNA so that you can use
1649 your phone line as a network cable.
1651 To compile this driver as a module, choose M here: the module
1652 will be called sis900. This is recommended.
1655 tristate "SMC EtherPower II"
1656 depends on NET_PCI && PCI
1660 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1661 which is based on the SMC83c17x (EPIC/100).
1662 More specific information and updates are available from
1663 <http://www.scyld.com/network/epic100.html>.
1666 tristate "Sundance Alta support"
1667 depends on NET_PCI && PCI
1671 This driver is for the Sundance "Alta" chip.
1672 More specific information and updates are available from
1673 <http://www.scyld.com/network/sundance.html>.
1675 config SUNDANCE_MMIO
1676 bool "Use MMIO instead of PIO"
1679 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1680 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1681 is known to solve bugs on certain chips.
1686 tristate "TI ThunderLAN support"
1687 depends on NET_PCI && (PCI || EISA) && !64BIT
1689 If you have a PCI Ethernet network card based on the ThunderLAN chip
1690 which is supported by this driver, say Y and read the
1691 Ethernet-HOWTO, available from
1692 <http://www.tldp.org/docs.html#howto>.
1694 Devices currently supported by this driver are Compaq Netelligent,
1695 Compaq NetFlex and Olicom cards. Please read the file
1696 <file:Documentation/networking/tlan.txt> for more details.
1698 To compile this driver as a module, choose M here. The module
1699 will be called tlan.
1701 Please email feedback to <torben.mathiasen@compaq.com>.
1704 tristate "VIA Rhine support"
1705 depends on NET_PCI && PCI
1709 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1710 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1711 Ethernet functions can also be found integrated on South Bridges
1714 To compile this driver as a module, choose M here. The module
1715 will be called via-rhine.
1717 config VIA_RHINE_MMIO
1718 bool "Use MMIO instead of PIO"
1719 depends on VIA_RHINE
1721 This instructs the driver to use PCI shared memory (MMIO) instead of
1722 programmed I/O ports (PIO). Enabling this gives an improvement in
1723 processing time in parts of the driver.
1727 config VIA_RHINE_NAPI
1728 bool "Use Rx Polling (NAPI)"
1729 depends on VIA_RHINE
1731 NAPI is a new driver API designed to reduce CPU and interrupt load
1732 when the driver is receiving lots of packets from the card.
1734 If your estimated Rx load is 10kpps or more, or if the card will be
1735 deployed on potentially unfriendly networks (e.g. in a firewall),
1739 bool "Philips SAA9730 Ethernet support"
1740 depends on NET_PCI && PCI && MIPS_ATLAS
1742 The SAA9730 is a combined multimedia and peripheral controller used
1743 in thin clients, Internet access terminals, and diskless
1745 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1748 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1749 depends on NET_PCI && PCI && EXPERIMENTAL
1752 This is a driver for the Fast Ethernet PCI network cards based on
1753 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1754 have one of these, say Y here.
1756 To compile this driver as a module, choose M here: the module
1757 will be called sc92031. This is recommended.
1760 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1761 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1764 TI AR7 CPMAC Ethernet support
1767 bool "Pocket and portable adapters"
1770 Cute little network (Ethernet) devices which attach to the parallel
1771 port ("pocket adapters"), commonly used with laptops. If you have
1772 one of those, say Y and read the Ethernet-HOWTO, available from
1773 <http://www.tldp.org/docs.html#howto>.
1775 If you want to plug a network (or some other) card into the PCMCIA
1776 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1777 credit card size extension cards used by all modern laptops), you
1778 need the pcmcia-cs package (location contained in the file
1779 <file:Documentation/Changes>) and you can say N here.
1781 Laptop users should read the Linux Laptop home page at
1782 <http://www.linux-on-laptops.com/> or
1783 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1785 Note that the answer to this question doesn't directly affect the
1786 kernel: saying N will just cause the configurator to skip all
1787 the questions about this class of network devices. If you say Y, you
1788 will be asked for your specific device in the following questions.
1791 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1792 depends on NET_POCKET && PARPORT && X86
1795 This is a network (Ethernet) device which attaches to your parallel
1796 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1797 available from <http://www.tldp.org/docs.html#howto>, if you
1798 want to use this. If you intend to use this driver, you should have
1799 said N to the "Parallel printer support", because the two drivers
1800 don't like each other.
1802 To compile this driver as a module, choose M here: the module
1806 tristate "D-Link DE600 pocket adapter support"
1807 depends on NET_POCKET && PARPORT
1809 This is a network (Ethernet) device which attaches to your parallel
1810 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1811 Ethernet-HOWTO, available from
1812 <http://www.tldp.org/docs.html#howto>, if you want to use
1813 this. It is possible to have several devices share a single parallel
1814 port and it is safe to compile the corresponding drivers into the
1817 To compile this driver as a module, choose M here: the module
1818 will be called de600.
1821 tristate "D-Link DE620 pocket adapter support"
1822 depends on NET_POCKET && PARPORT
1824 This is a network (Ethernet) device which attaches to your parallel
1825 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1826 Ethernet-HOWTO, available from
1827 <http://www.tldp.org/docs.html#howto>, if you want to use
1828 this. It is possible to have several devices share a single parallel
1829 port and it is safe to compile the corresponding drivers into the
1832 To compile this driver as a module, choose M here: the module
1833 will be called de620.
1836 tristate "SGI Seeq ethernet controller support"
1837 depends on SGI_HAS_SEEQ
1839 Say Y here if you have an Seeq based Ethernet network card. This is
1840 used in many Silicon Graphics machines.
1843 tristate "DEC LANCE ethernet controller support"
1844 depends on MACH_DECSTATION
1847 This driver is for the series of Ethernet controllers produced by
1848 DEC (now Compaq) based on the AMD Lance chipset, including the
1849 DEPCA series. (This chipset is better known via the NE2100 cards.)
1852 bool "Motorola 68360 ethernet controller"
1855 Say Y here if you want to use the built-in ethernet controller of
1856 the Motorola 68360 processor.
1859 bool "FEC ethernet controller (of ColdFire CPUs)"
1860 depends on M523x || M527x || M5272 || M528x || M520x
1862 Say Y here if you want to use the built-in 10/100 Fast ethernet
1863 controller on some Motorola ColdFire processors.
1866 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1869 Say Y here if you want to use the second built-in 10/100 Fast
1870 ethernet controller on some Motorola ColdFire processors.
1873 tristate "MPC52xx FEC driver"
1874 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
1878 This option enables support for the MPC5200's on-chip
1879 Fast Ethernet Controller
1880 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1882 config FEC_MPC52xx_MDIO
1883 bool "MPC52xx FEC MDIO bus driver"
1884 depends on FEC_MPC52xx
1887 The MPC5200's FEC can connect to the Ethernet either with
1888 an external MII PHY chip or 10 Mbps 7-wire interface
1889 (Motorola? industry standard).
1890 If your board uses an external PHY connected to FEC, enable this.
1891 If not sure, enable.
1892 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1895 tristate "NE2000 compatible support for H8/300"
1898 Say Y here if you want to use the NE2000 compatible
1899 controller on the Renesas H8/300 processor.
1901 source "drivers/net/fec_8xx/Kconfig"
1902 source "drivers/net/fs_enet/Kconfig"
1904 endif # NET_ETHERNET
1910 menuconfig NETDEV_1000
1911 bool "Ethernet (1000 Mbit)"
1915 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1916 type of Local Area Network (LAN) in universities and companies.
1918 Say Y here to get to see options for Gigabit Ethernet drivers.
1919 This option alone does not add any kernel code.
1920 Note that drivers supporting both 100 and 1000 MBit may be listed
1921 under "Ethernet (10 or 100MBit)" instead.
1923 If you say N, all options in this submenu will be skipped and disabled.
1928 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1931 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1932 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1933 adapter. The driver allows for using the Jumbo Frame option (9000
1934 bytes/frame) however it requires that your switches can handle this
1935 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1938 To compile this driver as a module, choose M here: the
1939 module will be called acenic.
1941 config ACENIC_OMIT_TIGON_I
1942 bool "Omit support for old Tigon I based AceNICs"
1945 Say Y here if you only have Tigon II based AceNICs and want to leave
1946 out support for the older Tigon I based cards which are no longer
1947 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1948 version)). This will reduce the size of the driver object by
1949 app. 100KB. If you are not sure whether your card is a Tigon I or a
1950 Tigon II, say N here.
1952 The safe and default value for this is N.
1955 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1959 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1961 D-Link DGE-550T Gigabit Ethernet Adapter.
1962 D-Link DL2000-based Gigabit Ethernet Adapter.
1963 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1965 To compile this driver as a module, choose M here: the
1966 module will be called dl2k.
1969 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1972 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1973 adapters. For more information on how to identify your adapter, go
1974 to the Adapter & Driver ID Guide at:
1976 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1978 For general information and support, go to the Intel support
1981 <http://support.intel.com>
1983 More specific information on configuring the driver is in
1984 <file:Documentation/networking/e1000.txt>.
1986 To compile this driver as a module, choose M here. The module
1987 will be called e1000.
1990 bool "Use Rx Polling (NAPI)"
1993 NAPI is a new driver API designed to reduce CPU and interrupt load
1994 when the driver is receiving lots of packets from the card. It is
1995 still somewhat experimental and thus not yet enabled by default.
1997 If your estimated Rx load is 10kpps or more, or if the card will be
1998 deployed on potentially unfriendly networks (e.g. in a firewall),
2003 config E1000_DISABLE_PACKET_SPLIT
2004 bool "Disable Packet Split for PCI express adapters"
2007 Say Y here if you want to use the legacy receive path for PCI express
2013 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2014 depends on PCI && (!SPARC32 || BROKEN)
2016 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2017 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2018 use the regular e1000 driver For more information on how to
2019 identify your adapter, go to the Adapter & Driver ID Guide at:
2021 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2023 For general information and support, go to the Intel support
2026 <http://support.intel.com>
2028 To compile this driver as a module, choose M here. The module
2029 will be called e1000e.
2031 config E1000E_ENABLED
2032 def_bool E1000E != n
2035 tristate "IP1000 Gigabit Ethernet support"
2036 depends on PCI && EXPERIMENTAL
2039 This driver supports IP1000 gigabit Ethernet cards.
2041 To compile this driver as a module, choose M here: the module
2042 will be called ipg. This is recommended.
2045 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
2048 This driver supports Intel(R) 82575 gigabit ethernet family of
2049 adapters. For more information on how to identify your adapter, go
2050 to the Adapter & Driver ID Guide at:
2052 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2054 For general information and support, go to the Intel support
2057 <http://support.intel.com>
2059 More specific information on configuring the driver is in
2060 <file:Documentation/networking/e1000.txt>.
2062 To compile this driver as a module, choose M here. The module
2065 source "drivers/net/ixp2000/Kconfig"
2068 tristate "MyriCOM Gigabit Ethernet support"
2071 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2073 To compile this driver as a module, choose M here: the module
2074 will be called myri_sbus. This is recommended.
2077 tristate "National Semiconductor DP83820 support"
2080 This is a driver for the National Semiconductor DP83820 series
2081 of gigabit ethernet MACs. Cards using this chipset include
2082 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2083 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2087 tristate "Packet Engines Hamachi GNIC-II support"
2091 If you have a Gigabit Ethernet card of this type, say Y and read
2092 the Ethernet-HOWTO, available from
2093 <http://www.tldp.org/docs.html#howto>.
2095 To compile this driver as a module, choose M here. The module will be
2099 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2100 depends on PCI && EXPERIMENTAL
2103 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2104 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2105 used by the Beowulf Linux cluster project. See
2106 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2107 information about this driver in particular and Beowulf in general.
2109 To compile this driver as a module, choose M here: the module
2110 will be called yellowfin. This is recommended.
2113 tristate "Realtek 8169 gigabit ethernet support"
2117 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2119 To compile this driver as a module, choose M here: the module
2120 will be called r8169. This is recommended.
2123 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2124 depends on R8169 && EXPERIMENTAL
2126 NAPI is a new driver API designed to reduce CPU and interrupt load
2127 when the driver is receiving lots of packets from the card. It is
2128 still somewhat experimental and thus not yet enabled by default.
2130 If your estimated Rx load is 10kpps or more, or if the card will be
2131 deployed on potentially unfriendly networks (e.g. in a firewall),
2138 depends on R8169 && VLAN_8021Q
2140 Say Y here for the r8169 driver to support the functions required
2141 by the kernel 802.1Q code.
2146 tristate "SB1250 Gigabit Ethernet support"
2147 depends on SIBYTE_SB1xxx_SOC
2150 This driver supports Gigabit Ethernet interfaces based on the
2151 Broadcom SiByte family of System-On-a-Chip parts. They include
2152 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2155 To compile this driver as a module, choose M here: the module
2156 will be called sb1250-mac.
2159 tristate "SiS190/SiS191 gigabit ethernet support"
2164 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2165 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2166 appear in lan on motherboard designs which are based on SiS 965
2167 and SiS 966 south bridge.
2169 To compile this driver as a module, choose M here: the module
2170 will be called sis190. This is recommended.
2173 tristate "New SysKonnect GigaEthernet support"
2177 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2178 and related Gigabit Ethernet adapters. It is a new smaller driver
2179 with better performance and more complete ethtool support.
2181 It does not support the link failover and network management
2182 features that "portable" vendor supplied sk98lin driver does.
2184 This driver supports adapters based on the original Yukon chipset:
2185 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2186 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2188 It does not support the newer Yukon2 chipset: a separate driver,
2189 sky2, is provided for Yukon2-based adapters.
2191 To compile this driver as a module, choose M here: the module
2192 will be called skge. This is recommended.
2195 bool "Debugging interface"
2196 depends on SKGE && DEBUG_FS
2198 This option adds the ability to dump driver state for debugging.
2199 The file debugfs/skge/ethX displays the state of the internal
2200 transmit and receive rings.
2205 tristate "SysKonnect Yukon2 support"
2209 This driver supports Gigabit Ethernet adapters based on the
2210 Marvell Yukon 2 chipset:
2211 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2212 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2214 There is companion driver for the older Marvell Yukon and
2215 Genesis based adapters: skge.
2217 To compile this driver as a module, choose M here: the module
2218 will be called sky2. This is recommended.
2221 bool "Debugging interface"
2222 depends on SKY2 && DEBUG_FS
2224 This option adds the ability to dump driver state for debugging.
2225 The file debugfs/sky2/ethX displays the state of the internal
2226 transmit and receive rings.
2231 tristate "VIA Velocity support"
2237 If you have a VIA "Velocity" based network card say Y here.
2239 To compile this driver as a module, choose M here. The module
2240 will be called via-velocity.
2243 tristate "Broadcom Tigon3 support"
2246 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2248 To compile this driver as a module, choose M here: the module
2249 will be called tg3. This is recommended.
2252 tristate "Broadcom NetXtremeII support"
2257 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2259 To compile this driver as a module, choose M here: the module
2260 will be called bnx2. This is recommended.
2263 tristate "Spider Gigabit Ethernet driver"
2264 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2267 This driver supports the Gigabit Ethernet chips present on the
2268 Cell Processor-Based Blades from IBM.
2271 tristate "Tundra TSI108 gigabit Ethernet support"
2272 depends on TSI108_BRIDGE
2274 This driver supports Tundra TSI108 gigabit Ethernet ports.
2275 To compile this driver as a module, choose M here: the module
2276 will be called tsi108_eth.
2279 tristate "PS3 Gigabit Ethernet driver"
2281 select PS3_SYS_MANAGER
2283 This driver supports the network device on the PS3 game
2284 console. This driver has built-in support for Ethernet.
2286 To compile this driver as a module, choose M here: the
2287 module will be called ps3_gelic.
2289 config GELIC_WIRELESS
2290 bool "PS3 Wireless support"
2291 depends on GELIC_NET
2294 This option adds the support for the wireless feature of PS3.
2295 If you have the wireless-less model of PS3 or have no plan to
2296 use wireless feature, disabling this option saves memory. As
2297 the driver automatically distinguishes the models, you can
2298 safely enable this option even if you have a wireless-less model.
2301 tristate "Gianfar Ethernet"
2306 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2307 and MPC86xx family of chips, and the FEC on the 8540.
2310 bool "Use Rx Polling (NAPI)"
2314 tristate "Freescale QE Gigabit Ethernet"
2315 depends on QUICC_ENGINE
2318 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2319 which is available on some Freescale SOCs.
2322 bool "Use Rx Polling (NAPI)"
2325 config UGETH_MAGIC_PACKET
2326 bool "Magic Packet detection support"
2329 config UGETH_FILTERING
2330 bool "Mac address filtering support"
2333 config UGETH_TX_ON_DEMAND
2334 bool "Transmit on Demand support"
2338 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2339 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2342 This driver supports the gigabit ethernet MACs in the
2343 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2344 in the Marvell Orion ARM SoC family.
2346 Some boards that use the Discovery chipset are the Momenco
2347 Ocelot C and Jaguar ATX and Pegasos II.
2350 tristate "QLogic QLA3XXX Network Driver Support"
2353 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2355 To compile this driver as a module, choose M here: the module
2356 will be called qla3xxx.
2359 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2360 depends on PCI && EXPERIMENTAL
2364 This driver supports the Attansic L1 gigabit ethernet adapter.
2366 To compile this driver as a module, choose M here. The module
2367 will be called atl1.
2372 # 10 Gigabit Ethernet
2375 menuconfig NETDEV_10000
2376 bool "Ethernet (10000 Mbit)"
2380 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2381 This option alone does not add any kernel code.
2383 If you say N, all options in this submenu will be skipped and disabled.
2388 tristate "Chelsio 10Gb Ethernet support"
2392 This driver supports Chelsio gigabit and 10-gigabit
2393 Ethernet cards. More information about adapter features and
2394 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2396 For general information about Chelsio and our products, visit
2397 our website at <http://www.chelsio.com>.
2399 For customer support, please visit our customer support page at
2400 <http://www.chelsio.com/support.htm>.
2402 Please send feedback to <linux-bugs@chelsio.com>.
2404 To compile this driver as a module, choose M here: the module
2405 will be called cxgb.
2407 config CHELSIO_T1_1G
2408 bool "Chelsio gigabit Ethernet support"
2409 depends on CHELSIO_T1
2411 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2412 are using only 10G cards say 'N' here.
2414 config CHELSIO_T1_NAPI
2415 bool "Use Rx Polling (NAPI)"
2416 depends on CHELSIO_T1
2419 NAPI is a driver API designed to reduce CPU and interrupt load
2420 when the driver is receiving lots of packets from the card.
2423 tristate "Chelsio Communications T3 10Gb Ethernet support"
2427 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2430 For general information about Chelsio and our products, visit
2431 our website at <http://www.chelsio.com>.
2433 For customer support, please visit our customer support page at
2434 <http://www.chelsio.com/support.htm>.
2436 Please send feedback to <linux-bugs@chelsio.com>.
2438 To compile this driver as a module, choose M here: the module
2439 will be called cxgb3.
2442 tristate "eHEA Ethernet support"
2443 depends on IBMEBUS && INET && SPARSEMEM
2446 This driver supports the IBM pSeries eHEA ethernet adapter.
2448 To compile the driver as a module, choose M here. The module
2449 will be called ehea.
2452 tristate "Intel(R) 10GbE PCI Express adapters support"
2455 This driver supports Intel(R) 10GbE PCI Express family of
2456 adapters. For more information on how to identify your adapter, go
2457 to the Adapter & Driver ID Guide at:
2459 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2461 For general information and support, go to the Intel support
2464 <http://support.intel.com>
2466 To compile this driver as a module, choose M here. The module
2467 will be called ixgbe.
2470 tristate "Intel(R) PRO/10GbE support"
2473 This driver supports Intel(R) PRO/10GbE family of adapters for
2474 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2475 instead. For more information on how to identify your adapter, go
2476 to the Adapter & Driver ID Guide at:
2478 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2480 For general information and support, go to the Intel support
2483 <http://support.intel.com>
2485 More specific information on configuring the driver is in
2486 <file:Documentation/networking/ixgb.txt>.
2488 To compile this driver as a module, choose M here. The module
2489 will be called ixgb.
2492 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2493 depends on IXGB && EXPERIMENTAL
2495 NAPI is a new driver API designed to reduce CPU and interrupt load
2496 when the driver is receiving lots of packets from the card. It is
2497 still somewhat experimental and thus not yet enabled by default.
2499 If your estimated Rx load is 10kpps or more, or if the card will be
2500 deployed on potentially unfriendly networks (e.g. in a firewall),
2506 tristate "S2IO 10Gbe XFrame NIC"
2509 This driver supports the 10Gbe XFrame NIC of S2IO.
2510 More specific information on configuring the driver is in
2511 <file:Documentation/networking/s2io.txt>.
2514 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2515 depends on S2IO && EXPERIMENTAL
2517 NAPI is a new driver API designed to reduce CPU and interrupt load
2518 when the driver is receiving lots of packets from the card. It is
2519 still somewhat experimental and thus not yet enabled by default.
2521 If your estimated Rx load is 10kpps or more, or if the card will be
2522 deployed on potentially unfriendly networks (e.g. in a firewall),
2528 tristate "Myricom Myri-10G Ethernet support"
2529 depends on PCI && INET
2534 This driver supports Myricom Myri-10G Dual Protocol interface in
2535 Ethernet mode. If the eeprom on your board is not recent enough,
2536 you will need a newer firmware image.
2537 You may get this image or more information, at:
2539 <http://www.myri.com/scs/download-Myri10GE.html>
2541 To compile this driver as a module, choose M here. The module
2542 will be called myri10ge.
2545 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2548 This enables the support for NetXen's Gigabit Ethernet card.
2551 tristate "Sun Neptune 10Gbit Ethernet support"
2554 This enables support for cards based upon Sun's
2558 tristate "PA Semi 1/10Gbit MAC"
2559 depends on PPC_PASEMI && PCI
2563 This driver supports the on-chip 1/10Gbit Ethernet controller on
2564 PA Semi's PWRficient line of chips.
2572 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2573 depends on MLX4_CORE
2576 This option causes debugging code to be compiled into the
2577 mlx4_core driver. The output can be turned on via the
2578 debug_level module parameter (which can also be set after
2579 the driver is loaded through sysfs).
2582 tristate "Tehuti Networks 10G Ethernet"
2585 Tehuti Networks 10G Ethernet NIC
2588 tristate "Broadcom NetXtremeII 10Gb support"
2592 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2593 To compile this driver as a module, choose M here: the module
2594 will be called bnx2x. This is recommended.
2597 endif # NETDEV_10000
2599 source "drivers/net/tokenring/Kconfig"
2601 source "drivers/net/wireless/Kconfig"
2603 source "drivers/net/usb/Kconfig"
2605 source "drivers/net/pcmcia/Kconfig"
2607 source "drivers/net/wan/Kconfig"
2609 source "drivers/atm/Kconfig"
2611 source "drivers/s390/net/Kconfig"
2613 config XEN_NETDEV_FRONTEND
2614 tristate "Xen network device frontend driver"
2618 The network device frontend driver allows the kernel to
2619 access network devices exported exported by a virtual
2620 machine containing a physical network device driver. The
2621 frontend driver is intended for unprivileged guest domains;
2622 if you are compiling a kernel for a Xen guest, you almost
2623 certainly want to enable this.
2626 tristate "iSeries Virtual Ethernet driver support"
2627 depends on PPC_ISERIES
2630 tristate "RapidIO Ethernet over messaging driver support"
2633 config RIONET_TX_SIZE
2634 int "Number of outbound queue entries"
2638 config RIONET_RX_SIZE
2639 int "Number of inbound queue entries"
2644 bool "FDDI driver support"
2645 depends on (PCI || EISA || TC)
2647 Fiber Distributed Data Interface is a high speed local area network
2648 design; essentially a replacement for high speed Ethernet. FDDI can
2649 run over copper or fiber. If you are connected to such a network and
2650 want a driver for the FDDI card in your computer, say Y here (and
2651 then also Y to the driver for your FDDI card, below). Most people
2655 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2656 depends on FDDI && (PCI || EISA || TC)
2658 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2659 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2660 to a local FDDI network.
2662 To compile this driver as a module, choose M here: the module
2663 will be called defxx. If unsure, say N.
2667 prompt "Use MMIO instead of PIO" if PCI || EISA
2669 default n if PCI || EISA
2672 This instructs the driver to use EISA or PCI memory-mapped I/O
2673 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2674 Enabling this gives an improvement in processing time in parts
2675 of the driver, but it may cause problems with EISA (DEFEA)
2676 adapters. TURBOchannel does not have the concept of I/O ports,
2677 so MMIO is always used for these (DEFTA) adapters.
2682 tristate "SysKonnect FDDI PCI support"
2683 depends on FDDI && PCI
2686 Say Y here if you have a SysKonnect FDDI PCI adapter.
2687 The following adapters are supported by this driver:
2688 - SK-5521 (SK-NET FDDI-UP)
2689 - SK-5522 (SK-NET FDDI-UP DAS)
2690 - SK-5541 (SK-NET FDDI-FP)
2691 - SK-5543 (SK-NET FDDI-LP)
2692 - SK-5544 (SK-NET FDDI-LP DAS)
2693 - SK-5821 (SK-NET FDDI-UP64)
2694 - SK-5822 (SK-NET FDDI-UP64 DAS)
2695 - SK-5841 (SK-NET FDDI-FP64)
2696 - SK-5843 (SK-NET FDDI-LP64)
2697 - SK-5844 (SK-NET FDDI-LP64 DAS)
2698 - Netelligent 100 FDDI DAS Fibre SC
2699 - Netelligent 100 FDDI SAS Fibre SC
2700 - Netelligent 100 FDDI DAS UTP
2701 - Netelligent 100 FDDI SAS UTP
2702 - Netelligent 100 FDDI SAS Fibre MIC
2704 Read <file:Documentation/networking/skfp.txt> for information about
2707 Questions concerning this driver can be addressed to:
2708 <linux@syskonnect.de>
2710 To compile this driver as a module, choose M here: the module
2711 will be called skfp. This is recommended.
2714 bool "HIPPI driver support (EXPERIMENTAL)"
2715 depends on EXPERIMENTAL && INET && PCI
2717 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2718 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2719 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2720 single-mode). HIPPI networks are commonly used for clusters and to
2721 connect to super computers. If you are connected to a HIPPI network
2722 and have a HIPPI network card in your computer that you want to use
2723 under Linux, say Y here (you must also remember to enable the driver
2724 for your HIPPI card below). Most people will say N here.
2727 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2728 depends on HIPPI && PCI
2730 Say Y here if this is your PCI HIPPI network card.
2732 To compile this driver as a module, choose M here: the module
2733 will be called rrunner. If unsure, say N.
2735 config ROADRUNNER_LARGE_RINGS
2736 bool "Use large TX/RX rings (EXPERIMENTAL)"
2737 depends on ROADRUNNER
2739 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2740 of additional memory to allow for fastest operation, both for
2741 transmitting and receiving. This memory cannot be used by any other
2742 kernel code or by user space programs. Say Y here only if you have
2746 tristate "PLIP (parallel port) support"
2749 PLIP (Parallel Line Internet Protocol) is used to create a
2750 reasonably fast mini network consisting of two (or, rarely, more)
2751 local machines. A PLIP link from a Linux box is a popular means to
2752 install a Linux distribution on a machine which doesn't have a
2753 CD-ROM drive (a minimal system has to be transferred with floppies
2754 first). The kernels on both machines need to have this PLIP option
2755 enabled for this to work.
2757 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2758 ports (the connectors at the computers with 25 holes) are connected
2759 with "null printer" or "Turbo Laplink" cables which can transmit 4
2760 bits at a time (mode 0) or with special PLIP cables, to be used on
2761 bidirectional parallel ports only, which can transmit 8 bits at a
2762 time (mode 1); you can find the wiring of these cables in
2763 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2764 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2765 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2766 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2767 and winsock or NCSA's telnet.
2769 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2770 as the NET-3-HOWTO, both available from
2771 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2772 protocol has been changed and this PLIP driver won't work together
2773 with the PLIP support in Linux versions 1.0.x. This option enlarges
2774 your kernel by about 8 KB.
2776 To compile this driver as a module, choose M here. The module
2777 will be called plip. If unsure, say Y or M, in case you buy
2781 tristate "PPP (point-to-point protocol) support"
2784 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2785 the same purpose: sending Internet traffic over telephone (and other
2786 serial) lines. Ask your access provider if they support it, because
2787 otherwise you can't use it; most Internet access providers these
2788 days support PPP rather than SLIP.
2790 To use PPP, you need an additional program called pppd as described
2791 in the PPP-HOWTO, available at
2792 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2793 the version of pppd recommended in <file:Documentation/Changes>.
2794 The PPP option enlarges your kernel by about 16 KB.
2796 There are actually two versions of PPP: the traditional PPP for
2797 asynchronous lines, such as regular analog phone lines, and
2798 synchronous PPP which can be used over digital ISDN lines for
2799 example. If you want to use PPP over phone lines or other
2800 asynchronous serial lines, you need to say Y (or M) here and also to
2801 the next option, "PPP support for async serial ports". For PPP over
2802 synchronous lines, you should say Y (or M) here and to "Support
2803 synchronous PPP", below.
2805 If you said Y to "Version information on all symbols" above, then
2806 you cannot compile the PPP driver into the kernel; you can then only
2807 compile it as a module. To compile this driver as a module, choose M
2808 here. The module will be called ppp_generic.
2810 config PPP_MULTILINK
2811 bool "PPP multilink support (EXPERIMENTAL)"
2812 depends on PPP && EXPERIMENTAL
2814 PPP multilink is a protocol (defined in RFC 1990) which allows you
2815 to combine several (logical or physical) lines into one logical PPP
2816 connection, so that you can utilize your full bandwidth.
2818 This has to be supported at the other end as well and you need a
2819 version of the pppd daemon which understands the multilink protocol.
2824 bool "PPP filtering"
2827 Say Y here if you want to be able to filter the packets passing over
2828 PPP interfaces. This allows you to control which packets count as
2829 activity (i.e. which packets will reset the idle timer or bring up
2830 a demand-dialed link) and which packets are to be dropped entirely.
2831 You need to say Y here if you wish to use the pass-filter and
2832 active-filter options to pppd.
2837 tristate "PPP support for async serial ports"
2841 Say Y (or M) here if you want to be able to use PPP over standard
2842 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2843 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2846 To compile this driver as a module, choose M here.
2851 tristate "PPP support for sync tty ports"
2854 Say Y (or M) here if you want to be able to use PPP over synchronous
2855 (HDLC) tty devices, such as the SyncLink adapter. These devices
2856 are often used for high-speed leased lines like T1/E1.
2858 To compile this driver as a module, choose M here.
2861 tristate "PPP Deflate compression"
2866 Support for the Deflate compression method for PPP, which uses the
2867 Deflate algorithm (the same algorithm that gzip uses) to compress
2868 each PPP packet before it is sent over the wire. The machine at the
2869 other end of the PPP link (usually your ISP) has to support the
2870 Deflate compression method as well for this to be useful. Even if
2871 they don't support it, it is safe to say Y here.
2873 To compile this driver as a module, choose M here.
2876 tristate "PPP BSD-Compress compression"
2879 Support for the BSD-Compress compression method for PPP, which uses
2880 the LZW compression method to compress each PPP packet before it is
2881 sent over the wire. The machine at the other end of the PPP link
2882 (usually your ISP) has to support the BSD-Compress compression
2883 method as well for this to be useful. Even if they don't support it,
2884 it is safe to say Y here.
2886 The PPP Deflate compression method ("PPP Deflate compression",
2887 above) is preferable to BSD-Compress, because it compresses better
2890 Note that the BSD compression code will always be compiled as a
2891 module; it is called bsd_comp and will show up in the directory
2892 modules once you have said "make modules". If unsure, say N.
2895 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2896 depends on PPP && EXPERIMENTAL
2902 Support for the MPPE Encryption protocol, as employed by the
2903 Microsoft Point-to-Point Tunneling Protocol.
2905 See http://pptpclient.sourceforge.net/ for information on
2906 configuring PPTP clients and servers to utilize this method.
2909 tristate "PPP over Ethernet (EXPERIMENTAL)"
2910 depends on EXPERIMENTAL && PPP
2912 Support for PPP over Ethernet.
2914 This driver requires the latest version of pppd from the CVS
2915 repository at cvs.samba.org. Alternatively, see the
2916 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2917 which contains instruction on how to use this driver (under
2918 the heading "Kernel mode PPPoE").
2921 tristate "PPP over ATM"
2922 depends on ATM && PPP
2924 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2925 This implementation does not yet comply with section 8 of RFC2364,
2926 which can lead to bad results if the ATM peer loses state and
2927 changes its encapsulation unilaterally.
2930 tristate "PPP over L2TP (EXPERIMENTAL)"
2931 depends on EXPERIMENTAL && PPP && INET
2933 Support for PPP-over-L2TP socket family. L2TP is a protocol
2934 used by ISPs and enterprises to tunnel PPP traffic over UDP
2935 tunnels. L2TP is replacing PPTP for VPN uses.
2937 This kernel component handles only L2TP data packets: a
2938 userland daemon handles L2TP the control protocol (tunnel
2939 and session setup). One such daemon is OpenL2TP
2940 (http://openl2tp.sourceforge.net/).
2943 tristate "SLIP (serial line) support"
2945 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2946 connect to your Internet service provider or to connect to some
2947 other local Unix box or if you want to configure your Linux box as a
2948 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2949 Internet Protocol) is a protocol used to send Internet traffic over
2950 serial connections such as telephone lines or null modem cables;
2951 nowadays, the protocol PPP is more commonly used for this same
2954 Normally, your access provider has to support SLIP in order for you
2955 to be able to use it, but there is now a SLIP emulator called SLiRP
2956 around (available from
2957 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2958 allows you to use SLIP over a regular dial up shell connection. If
2959 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2960 NET-3-HOWTO, available from
2961 <http://www.tldp.org/docs.html#howto>, explains how to
2962 configure SLIP. Note that you don't need this option if you just
2963 want to run term (term is a program which gives you almost full
2964 Internet connectivity if you have a regular dial up shell account on
2965 some Internet connected Unix computer. Read
2966 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2967 support will enlarge your kernel by about 4 KB. If unsure, say N.
2969 To compile this driver as a module, choose M here. The module
2970 will be called slip.
2972 config SLIP_COMPRESSED
2973 bool "CSLIP compressed headers"
2977 This protocol is faster than SLIP because it uses compression on the
2978 TCP/IP headers (not on the data itself), but it has to be supported
2979 on both ends. Ask your access provider if you are not sure and
2980 answer Y, just in case. You will still be able to use plain SLIP. If
2981 you plan to use SLiRP, the SLIP emulator (available from
2982 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2983 allows you to use SLIP over a regular dial up shell connection, you
2984 definitely want to say Y here. The NET-3-HOWTO, available from
2985 <http://www.tldp.org/docs.html#howto>, explains how to configure
2986 CSLIP. This won't enlarge your kernel.
2991 This option enables Van Jacobsen serial line header compression
2995 bool "Keepalive and linefill"
2998 Adds additional capabilities to the SLIP driver to support the
2999 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3002 config SLIP_MODE_SLIP6
3003 bool "Six bit SLIP encapsulation"
3006 Just occasionally you may need to run IP over hostile serial
3007 networks that don't pass all control characters or are only seven
3008 bit. Saying Y here adds an extra mode you can use with SLIP:
3009 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3010 the serial device. Naturally, this has to be supported at the other
3011 end of the link as well. It's good enough, for example, to run IP
3012 over the async ports of a Camtec JNT Pad. If unsure, say N.
3015 bool "Fibre Channel driver support"
3016 depends on SCSI && PCI
3018 Fibre Channel is a high speed serial protocol mainly used to connect
3019 large storage devices to the computer; it is compatible with and
3020 intended to replace SCSI.
3022 If you intend to use Fibre Channel, you need to have a Fibre channel
3023 adaptor card in your computer; say Y here and to the driver for your
3024 adaptor below. You also should have said Y to "SCSI support" and
3025 "SCSI generic support".
3028 tristate "Network console logging support (EXPERIMENTAL)"
3029 depends on EXPERIMENTAL
3031 If you want to log kernel messages over the network, enable this.
3032 See <file:Documentation/networking/netconsole.txt> for details.
3034 config NETCONSOLE_DYNAMIC
3035 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3036 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3039 This option enables the ability to dynamically reconfigure target
3040 parameters (interface, IP addresses, port numbers, MAC addresses)
3041 at runtime through a userspace interface exported using configfs.
3042 See <file:Documentation/networking/netconsole.txt> for details.
3048 bool "Netpoll traffic trapping"
3052 config NET_POLL_CONTROLLER
3056 tristate "Virtio network driver (EXPERIMENTAL)"
3057 depends on EXPERIMENTAL && VIRTIO
3059 This is the virtual network driver for virtio. It can be used with
3060 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.