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 "Renesas SuperH Ethernet support"
529 depends on SUPERH && \
530 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)
536 Renesas SuperH Ethernet device driver.
537 This driver support SH7710 and SH7712.
540 tristate "Sun LANCE support"
544 This driver supports the "le" interface present on all 32-bit Sparc
545 systems, on some older Ultra systems and as an Sbus option. These
546 cards are based on the AMD Lance chipset, which is better known
547 via the NE2100 cards.
549 To compile this driver as a module, choose M here: the module
550 will be called sunlance.
553 tristate "Sun Happy Meal 10/100baseT support"
554 depends on SBUS || PCI
557 This driver supports the "hme" interface present on most Ultra
558 systems and as an option on older Sbus systems. This driver supports
559 both PCI and Sbus devices. This driver also supports the "qfe" quad
560 100baseT device available in both PCI and Sbus configurations.
562 To compile this driver as a module, choose M here: the module
563 will be called sunhme.
566 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
567 depends on SBUS && EXPERIMENTAL
570 This driver supports the "be" interface available as an Sbus option.
571 This is Sun's older 100baseT Ethernet device.
573 To compile this driver as a module, choose M here: the module
574 will be called sunbmac.
577 tristate "Sun QuadEthernet support"
581 This driver supports the "qe" 10baseT Ethernet device, available as
582 an Sbus option. Note that this is not the same as Quad FastEthernet
583 "qfe" which is supported by the Happy Meal driver instead.
585 To compile this driver as a module, choose M here: the module
586 will be called sunqe.
589 tristate "Sun GEM support"
593 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
594 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
597 tristate "Sun Cassini support"
601 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
602 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
605 tristate "Sun Virtual Network support"
608 Support for virtual network devices under Sun Logical Domains.
610 config NET_VENDOR_3COM
612 depends on ISA || EISA || MCA || PCI
614 If you have a network (Ethernet) card belonging to this class, say Y
615 and read the Ethernet-HOWTO, available from
616 <http://www.tldp.org/docs.html#howto>.
618 Note that the answer to this question doesn't directly affect the
619 kernel: saying N will just cause the configurator to skip all
620 the questions about 3COM cards. If you say Y, you will be asked for
621 your specific card in the following questions.
624 tristate "3c501 \"EtherLink\" support"
625 depends on NET_VENDOR_3COM && ISA
627 If you have a network (Ethernet) card of this type, say Y and read
628 the Ethernet-HOWTO, available from
629 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
630 new card, since the 3c501 is slow, broken, and obsolete: you will
631 have problems. Some people suggest to ping ("man ping") a nearby
632 machine every minute ("man cron") when using this card.
634 To compile this driver as a module, choose M here. The module
635 will be called 3c501.
638 tristate "3c503 \"EtherLink II\" support"
639 depends on NET_VENDOR_3COM && ISA
642 If you have a network (Ethernet) card of this type, say Y and read
643 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 3c503.
650 tristate "3c505 \"EtherLink Plus\" support"
651 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
653 Information about this network (Ethernet) card can be found in
654 <file:Documentation/networking/3c505.txt>. If you have a card of
655 this type, say Y and read the Ethernet-HOWTO, available from
656 <http://www.tldp.org/docs.html#howto>.
658 To compile this driver as a module, choose M here. The module
659 will be called 3c505.
662 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
663 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
665 If you have a network (Ethernet) card of this type, say Y and read
666 the Ethernet-HOWTO, available from
667 <http://www.tldp.org/docs.html#howto>.
669 To compile this driver as a module, choose M here. The module
670 will be called 3c507.
673 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
674 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
676 If you have a network (Ethernet) card belonging to the 3Com
677 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
678 from <http://www.tldp.org/docs.html#howto>.
680 If your card is not working you may need to use the DOS
681 setup disk to disable Plug & Play mode, and to select the default
684 To compile this driver as a module, choose M here. The module
685 will be called 3c509.
688 tristate "3c515 ISA \"Fast EtherLink\""
689 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
691 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
692 network card, say Y and read the Ethernet-HOWTO, available from
693 <http://www.tldp.org/docs.html#howto>.
695 To compile this driver as a module, choose M here. The module
696 will be called 3c515.
699 tristate "3c523 \"EtherLink/MC\" support"
700 depends on NET_VENDOR_3COM && MCA_LEGACY
702 If you have a network (Ethernet) card of this type, say Y and read
703 the Ethernet-HOWTO, available from
704 <http://www.tldp.org/docs.html#howto>.
706 To compile this driver as a module, choose M here. The module
707 will be called 3c523.
710 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
711 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
713 If you have a network (Ethernet) card of this type, say Y and read
714 the Ethernet-HOWTO, available from
715 <http://www.tldp.org/docs.html#howto>.
717 To compile this driver as a module, choose M here. The module
718 will be called 3c527.
721 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
722 depends on NET_VENDOR_3COM && (PCI || EISA)
725 This option enables driver support for a large number of 10Mbps and
726 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
728 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
729 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
730 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
731 "Tornado" (3c905) PCI
732 "Hurricane" (3c555/3cSOHO) PCI
734 If you have such a card, say Y and read the Ethernet-HOWTO,
735 available from <http://www.tldp.org/docs.html#howto>. More
736 specific information is in
737 <file:Documentation/networking/vortex.txt> and in the comments at
738 the beginning of <file:drivers/net/3c59x.c>.
740 To compile this support as a module, choose M here.
743 tristate "3cr990 series \"Typhoon\" support"
744 depends on NET_VENDOR_3COM && PCI
747 This option enables driver support for the 3cr990 series of cards:
749 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
750 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
751 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
753 If you have a network (Ethernet) card of this type, say Y and read
754 the Ethernet-HOWTO, available from
755 <http://www.tldp.org/docs.html#howto>.
757 To compile this driver as a module, choose M here. The module
758 will be called typhoon.
761 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
762 depends on ISA && ISA_DMA_API
764 If you have a network (Ethernet) card of this type, say Y and read
765 the Ethernet-HOWTO, available from
766 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
769 To compile this driver as a module, choose M here: the module
770 will be called lance. This is recommended.
772 config NET_VENDOR_SMC
773 bool "Western Digital/SMC cards"
774 depends on ISA || MCA || EISA || MAC
776 If you have a network (Ethernet) card belonging to this class, say Y
777 and read the Ethernet-HOWTO, available from
778 <http://www.tldp.org/docs.html#howto>.
780 Note that the answer to this question doesn't directly affect the
781 kernel: saying N will just cause the configurator to skip all
782 the questions about Western Digital cards. If you say Y, you will be
783 asked for your specific card in the following questions.
786 tristate "WD80*3 support"
787 depends on NET_VENDOR_SMC && ISA
790 If you have a network (Ethernet) card of this type, say Y and read
791 the Ethernet-HOWTO, available from
792 <http://www.tldp.org/docs.html#howto>.
794 To compile this driver as a module, choose M here. The module
798 tristate "SMC Ultra MCA support"
799 depends on NET_VENDOR_SMC && MCA
802 If you have a network (Ethernet) card of this type and are running
803 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
804 available from <http://www.tldp.org/docs.html#howto>.
806 To compile this driver as a module, choose M here. The module
807 will be called smc-mca.
810 tristate "SMC Ultra support"
811 depends on NET_VENDOR_SMC && ISA
814 If you have a network (Ethernet) card of this type, say Y and read
815 the Ethernet-HOWTO, available from
816 <http://www.tldp.org/docs.html#howto>.
818 Important: There have been many reports that, with some motherboards
819 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
820 such as some BusLogic models) causes corruption problems with many
821 operating systems. The Linux smc-ultra driver has a work-around for
822 this but keep it in mind if you have such a SCSI card and have
825 To compile this driver as a module, choose M here. The module
826 will be called smc-ultra.
829 tristate "SMC Ultra32 EISA support"
830 depends on NET_VENDOR_SMC && EISA
833 If you have a network (Ethernet) card of this type, say Y and read
834 the Ethernet-HOWTO, available from
835 <http://www.tldp.org/docs.html#howto>.
837 To compile this driver as a module, choose M here. The module
838 will be called smc-ultra32.
841 tristate "Blackfin 527/536/537 on-chip mac support"
842 depends on NET_ETHERNET && (BF527 || BF537 || BF536)
846 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
848 This is the driver for blackfin on-chip mac device. Say Y if you want it
849 compiled into the kernel. This driver is also available as a module
850 ( = code which can be inserted in and removed from the running kernel
851 whenever you want). The module will be called bfin_mac.
853 config BFIN_MAC_USE_L1
854 bool "Use L1 memory for rx/tx packets"
855 depends on BFIN_MAC && (BF527 || BF537)
858 To get maximum network performance, you should use L1 memory as rx/tx buffers.
859 Say N here if you want to reserve L1 memory for other uses.
861 config BFIN_TX_DESC_NUM
862 int "Number of transmit buffer packets"
864 range 6 10 if BFIN_MAC_USE_L1
868 Set the number of buffer packets used in driver.
870 config BFIN_RX_DESC_NUM
871 int "Number of receive buffer packets"
873 range 20 100 if BFIN_MAC_USE_L1
877 Set the number of buffer packets used in driver.
880 bool "RMII PHY Interface (EXPERIMENTAL)"
881 depends on BFIN_MAC && EXPERIMENTAL
882 default y if BFIN527_EZKIT
883 default n if BFIN537_STAMP
885 Use Reduced PHY MII Interface
888 tristate "SMC 9194 support"
889 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
892 This is support for the SMC9xxx based Ethernet cards. Choose this
893 option if you have a DELL laptop with the docking station, or
894 another SMC9192/9194 based chipset. Say Y if you want it compiled
895 into the kernel, and read the file
896 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
897 available from <http://www.tldp.org/docs.html#howto>.
899 To compile this driver as a module, choose M here. The module
900 will be called smc9194.
903 tristate "SMC 91C9x/91C1xxx support"
906 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
907 SOC_AU1X00 || BLACKFIN || MN10300
909 This is a driver for SMC's 91x series of Ethernet chipsets,
910 including the SMC91C94 and the SMC91C111. Say Y if you want it
911 compiled into the kernel, and read the file
912 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
913 available from <http://www.linuxdoc.org/docs.html#howto>.
915 This driver is also available as a module ( = code which can be
916 inserted in and removed from the running kernel whenever you want).
917 The module will be called smc91x. If you want to compile it as a
918 module, say M here and read <file:Documentation/kbuild/modules.txt>.
921 tristate "NetX Ethernet support"
925 This is support for the Hilscher netX builtin Ethernet ports
927 To compile this driver as a module, choose M here. The module
928 will be called netx-eth.
931 tristate "DM9000 support"
932 depends on ARM || BLACKFIN || MIPS
936 Support for DM9000 chipset.
938 To compile this driver as a module, choose M here. The module
939 will be called dm9000.
941 config DM9000_DEBUGLEVEL
942 int "DM9000 maximum debug level"
946 The maximum level of debugging code compiled into the DM9000
949 config DM9000_FORCE_SIMPLE_PHY_POLL
950 bool "Force simple NSR based PHY polling"
953 This configuration forces the DM9000 to use the NSR's LinkStatus
954 bit to determine if the link is up or down instead of the more
955 costly MII PHY reads. Note, this will not work if the chip is
956 operating with an external PHY.
959 tristate "ENC28J60 support"
960 depends on EXPERIMENTAL && SPI && NET_ETHERNET
963 Support for the Microchip EN28J60 ethernet chip.
965 To compile this driver as a module, choose M here. The module will be
968 config ENC28J60_WRITEVERIFY
969 bool "Enable write verify"
972 Enable the verify after the buffer write useful for debugging purpose.
976 tristate "SMSC LAN911[5678] support"
979 depends on ARCH_PXA || SUPERH
981 This is a driver for SMSC's LAN911x series of Ethernet chipsets
982 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
983 Say Y if you want it compiled into the kernel,
984 and read the Ethernet-HOWTO, available from
985 <http://www.linuxdoc.org/docs.html#howto>.
987 This driver is also available as a module. The module will be
988 called smc911x. If you want to compile it as a module, say M
989 here and read <file:Documentation/kbuild/modules.txt>
991 config NET_VENDOR_RACAL
992 bool "Racal-Interlan (Micom) NI cards"
995 If you have a network (Ethernet) card belonging to this class, such
996 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
997 available from <http://www.tldp.org/docs.html#howto>.
999 Note that the answer to this question doesn't directly affect the
1000 kernel: saying N will just cause the configurator to skip all
1001 the questions about NI cards. If you say Y, you will be asked for
1002 your specific card in the following questions.
1005 tristate "NI5010 support (EXPERIMENTAL)"
1006 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1008 If you have a network (Ethernet) card of this type, say Y and read
1009 the Ethernet-HOWTO, available from
1010 <http://www.tldp.org/docs.html#howto>. Note that this is still
1013 To compile this driver as a module, choose M here. The module
1014 will be called ni5010.
1017 tristate "NI5210 support"
1018 depends on NET_VENDOR_RACAL && ISA
1020 If you have a network (Ethernet) card of this type, say Y and read
1021 the Ethernet-HOWTO, available from
1022 <http://www.tldp.org/docs.html#howto>.
1024 To compile this driver as a module, choose M here. The module
1025 will be called ni52.
1028 tristate "NI6510 support"
1029 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1031 If you have a network (Ethernet) card of this type, say Y and read
1032 the Ethernet-HOWTO, available from
1033 <http://www.tldp.org/docs.html#howto>.
1035 To compile this driver as a module, choose M here. The module
1036 will be called ni65.
1038 source "drivers/net/tulip/Kconfig"
1041 tristate "AT1700/1720 support (EXPERIMENTAL)"
1042 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1045 If you have a network (Ethernet) card of this type, say Y and read
1046 the Ethernet-HOWTO, available from
1047 <http://www.tldp.org/docs.html#howto>.
1049 To compile this driver as a module, choose M here. The module
1050 will be called at1700.
1053 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1054 depends on ISA || EISA || MCA
1057 If you have a network (Ethernet) card of this type, say Y and read
1058 the Ethernet-HOWTO, available from
1059 <http://www.tldp.org/docs.html#howto> as well as
1060 <file:drivers/net/depca.c>.
1062 To compile this driver as a module, choose M here. The module
1063 will be called depca.
1066 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1067 depends on ISA || EISA || PCI
1069 If you have a network (Ethernet) card of this type, say Y and read
1070 the Ethernet-HOWTO, available from
1071 <http://www.tldp.org/docs.html#howto>.
1073 To compile this driver as a module, choose M here. The module
1074 will be called hp100.
1077 bool "Other ISA cards"
1080 If your network (Ethernet) card hasn't been mentioned yet and its
1081 bus system (that's the way the cards talks to the other components
1082 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1083 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1084 available from <http://www.tldp.org/docs.html#howto>.
1088 Note that the answer to this question doesn't directly affect the
1089 kernel: saying N will just cause the configurator to skip all
1090 the remaining ISA network card questions. If you say Y, you will be
1091 asked for your specific card in the following questions.
1094 tristate "Cabletron E21xx support"
1098 If you have a network (Ethernet) card of this type, say Y and read
1099 the Ethernet-HOWTO, available from
1100 <http://www.tldp.org/docs.html#howto>.
1102 To compile this driver as a module, choose M here. The module
1103 will be called e2100.
1106 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1110 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1111 cards. If this is for you, say Y and read
1112 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1113 well as the Ethernet-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>.
1116 To compile this driver as a module, choose M here. The module
1117 will be called ewrk3.
1120 tristate "EtherExpress 16 support"
1123 If you have an EtherExpress16 network (Ethernet) card, say Y and
1124 read the Ethernet-HOWTO, available from
1125 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1126 EtherExpress16 card used to be regarded as a very poor choice
1127 because the driver was very unreliable. We now have a new driver
1128 that should do better.
1130 To compile this driver as a module, choose M here. The module
1131 will be called eexpress.
1134 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1137 If you have a network (Ethernet) card of this type, say Y. This
1138 driver supports Intel i82595{FX,TX} based boards. Note however
1139 that the EtherExpress PRO/100 Ethernet card has its own separate
1140 driver. Please read the Ethernet-HOWTO, available from
1141 <http://www.tldp.org/docs.html#howto>.
1143 To compile this driver as a module, choose M here. The module
1144 will be called eepro.
1147 tristate "HP PCLAN+ (27247B and 27252A) support"
1151 If you have a network (Ethernet) card of this type, say Y and read
1152 the Ethernet-HOWTO, available from
1153 <http://www.tldp.org/docs.html#howto>.
1155 To compile this driver as a module, choose M here. The module
1156 will be called hp-plus.
1159 tristate "HP PCLAN (27245 and other 27xxx series) support"
1163 If you have a network (Ethernet) card of this type, say Y and read
1164 the Ethernet-HOWTO, available from
1165 <http://www.tldp.org/docs.html#howto>.
1167 To compile this driver as a module, choose M here. The module
1171 tristate "LP486E on board Ethernet"
1174 Say Y here to support the 82596-based on-board Ethernet controller
1175 for the Panther motherboard, which is one of the two shipped in the
1176 Intel Professional Workstation.
1179 tristate "ICL EtherTeam 16i/32 support"
1182 If you have a network (Ethernet) card of this type, say Y and read
1183 the Ethernet-HOWTO, available from
1184 <http://www.tldp.org/docs.html#howto>.
1186 To compile this driver as a module, choose M here. The module
1187 will be called eth16i.
1190 tristate "NE2000/NE1000 support"
1191 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1194 If you have a network (Ethernet) card of this type, say Y and read
1195 the Ethernet-HOWTO, available from
1196 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1197 without a specific driver are compatible with NE2000.
1199 If you have a PCI NE2000 card however, say N here and Y to "PCI
1200 NE2000 and clone support" under "EISA, VLB, PCI and on board
1201 controllers" below. If you have a NE2000 card and are running on
1202 an MCA system (a bus system used on some IBM PS/2 computers and
1203 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1206 To compile this driver as a module, choose M here. The module
1210 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1211 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1213 The Zenith Z-Note notebook computer has a built-in network
1214 (Ethernet) card, and this is the Linux driver for it. Note that the
1215 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1216 by this driver. Read the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1220 tristate "SEEQ8005 support (EXPERIMENTAL)"
1221 depends on NET_ISA && EXPERIMENTAL
1223 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1224 is for you, read the Ethernet-HOWTO, available from
1225 <http://www.tldp.org/docs.html#howto>.
1227 To compile this driver as a module, choose M here. The module
1228 will be called seeq8005.
1231 tristate "NE/2 (ne2000 MCA version) support"
1232 depends on MCA_LEGACY
1235 If you have a network (Ethernet) card of this type, say Y and read
1236 the Ethernet-HOWTO, available from
1237 <http://www.tldp.org/docs.html#howto>.
1239 To compile this driver as a module, choose M here. The module
1243 tristate "IBM LAN Adapter/A support"
1246 This is a Micro Channel Ethernet adapter. You need to set
1247 CONFIG_MCA to use this driver. It is both available as an in-kernel
1248 driver and as a module.
1250 To compile this driver as a module, choose M here. The only
1251 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1252 will both support 16K and 32K memory windows, however a 32K window
1253 gives a better security against packet losses. Usage of multiple
1254 boards with this driver should be possible, but has not been tested
1255 up to now due to lack of hardware.
1258 tristate "IBM LAN Virtual Ethernet support"
1259 depends on PPC_PSERIES
1261 This driver supports virtual ethernet adapters on newer IBM iSeries
1262 and pSeries systems.
1264 To compile this driver as a module, choose M here. The module will
1267 source "drivers/net/ibm_newemac/Kconfig"
1270 bool "EISA, VLB, PCI and on board controllers"
1271 depends on ISA || EISA || PCI
1273 This is another class of network cards which attach directly to the
1274 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1275 available from <http://www.tldp.org/docs.html#howto>.
1277 Note that the answer to this question doesn't directly affect the
1278 kernel: saying N will just cause the configurator to skip all
1279 the questions about this class of network cards. If you say Y, you
1280 will be asked for your specific card in the following questions. If
1281 you are unsure, say Y.
1284 tristate "AMD PCnet32 PCI support"
1285 depends on NET_PCI && PCI
1289 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1290 answer Y here and read the Ethernet-HOWTO, available from
1291 <http://www.tldp.org/docs.html#howto>.
1293 To compile this driver as a module, choose M here. The module
1294 will be called pcnet32.
1297 tristate "AMD 8111 (new PCI lance) support"
1298 depends on NET_PCI && PCI
1302 If you have an AMD 8111-based PCI lance ethernet card,
1303 answer Y here and read the Ethernet-HOWTO, available from
1304 <http://www.tldp.org/docs.html#howto>.
1306 To compile this driver as a module, choose M here. The module
1307 will be called amd8111e.
1309 config AMD8111E_NAPI
1310 bool "Use RX polling (NAPI)"
1311 depends on AMD8111_ETH
1313 NAPI is a new driver API designed to reduce CPU and interrupt load
1314 when the driver is receiving lots of packets from the card. It is
1315 still somewhat experimental and thus not yet enabled by default.
1317 If your estimated Rx load is 10kpps or more, or if the card will be
1318 deployed on potentially unfriendly networks (e.g. in a firewall),
1323 config ADAPTEC_STARFIRE
1324 tristate "Adaptec Starfire/DuraLAN support"
1325 depends on NET_PCI && PCI
1329 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1330 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1331 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1334 To compile this driver as a module, choose M here: the module
1335 will be called starfire. This is recommended.
1338 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1339 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1342 If you have a network (Ethernet) card of this type, say Y and read
1343 the Ethernet-HOWTO, available from
1344 <http://www.tldp.org/docs.html#howto>.
1346 To compile this driver as a module, choose M here. The module
1347 will be called ac3200.
1350 tristate "Apricot Xen-II on board Ethernet"
1351 depends on NET_PCI && ISA
1353 If you have a network (Ethernet) controller of this type, say Y and
1354 read the Ethernet-HOWTO, available from
1355 <http://www.tldp.org/docs.html#howto>.
1357 To compile this driver as a module, choose M here. The module
1358 will be called apricot.
1361 tristate "Broadcom 440x/47xx ethernet support"
1362 depends on SSB_POSSIBLE && HAS_DMA
1366 If you have a network (Ethernet) controller of this type, say Y
1367 or M and read the Ethernet-HOWTO, available from
1368 <http://www.tldp.org/docs.html#howto>.
1370 To compile this driver as a module, choose M here. The module
1373 # Auto-select SSB PCI-HOST support, if possible
1374 config B44_PCI_AUTOSELECT
1376 depends on B44 && SSB_PCIHOST_POSSIBLE
1380 # Auto-select SSB PCICORE driver, if possible
1381 config B44_PCICORE_AUTOSELECT
1383 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1384 select SSB_DRIVER_PCICORE
1389 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1393 tristate "nForce Ethernet support"
1394 depends on NET_PCI && PCI
1396 If you have a network (Ethernet) controller of this type, say Y and
1397 read the Ethernet-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>.
1400 To compile this driver as a module, choose M here. The module
1401 will be called forcedeth.
1403 config FORCEDETH_NAPI
1404 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1405 depends on FORCEDETH && EXPERIMENTAL
1407 NAPI is a new driver API designed to reduce CPU and interrupt load
1408 when the driver is receiving lots of packets from the card. It is
1409 still somewhat experimental and thus not yet enabled by default.
1411 If your estimated Rx load is 10kpps or more, or if the card will be
1412 deployed on potentially unfriendly networks (e.g. in a firewall),
1418 tristate "CS89x0 support"
1419 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1421 Support for CS89x0 chipset based Ethernet cards. If you have a
1422 network (Ethernet) card of this type, say Y and read the
1423 Ethernet-HOWTO, available from
1424 <http://www.tldp.org/docs.html#howto> as well as
1425 <file:Documentation/networking/cs89x0.txt>.
1427 To compile this driver as a module, choose M here. The module
1428 will be called cs89x0.
1431 tristate "TOSHIBA TC35815 Ethernet support"
1432 depends on NET_PCI && PCI && MIPS
1436 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1437 depends on NET_PCI && PCI
1440 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1441 card, say Y and read the Ethernet-HOWTO, available from
1442 <http://www.tldp.org/docs.html#howto>.
1444 To compile this driver as a module, choose M here. The module
1445 will be called eepro100.
1449 tristate "Intel(R) PRO/100+ support"
1450 depends on NET_PCI && PCI
1453 This driver supports Intel(R) PRO/100 family of adapters.
1454 To verify that your adapter is supported, find the board ID number
1455 on the adapter. Look for a label that has a barcode and a number
1456 in the format 123456-001 (six digits hyphen three digits).
1458 Use the above information and the Adapter & Driver ID Guide at:
1460 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1462 to identify the adapter.
1464 For the latest Intel PRO/100 network driver for Linux, see:
1466 <http://appsr.intel.com/scripts-df/support_intel.asp>
1468 More specific information on configuring the driver is in
1469 <file:Documentation/networking/e100.txt>.
1471 To compile this driver as a module, choose M here. The module
1472 will be called e100.
1475 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1476 depends on NET_PCI && EISA && EXPERIMENTAL
1479 If you have a network (Ethernet) card of this type, say Y and read
1480 the Ethernet-HOWTO, available from
1481 <http://www.tldp.org/docs.html#howto>.
1483 To compile this driver as a module, choose M here. The module
1484 will be called lne390.
1487 tristate "Myson MTD-8xx PCI Ethernet support"
1488 depends on NET_PCI && PCI
1492 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1493 cards. Specifications and data at
1494 <http://www.myson.com.hk/mtd/datasheet/>.
1497 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1498 depends on NET_PCI && PCI
1501 This driver is for the National Semiconductor DP83810 series,
1502 which is used in cards from PureData, NetGear, Linksys
1503 and others, including the 83815 chip.
1504 More specific information and updates are available from
1505 <http://www.scyld.com/network/natsemi.html>.
1508 tristate "PCI NE2000 and clones support (see help)"
1509 depends on NET_PCI && PCI
1512 This driver is for NE2000 compatible PCI cards. It will not work
1513 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1514 support" below). If you have a PCI NE2000 network (Ethernet) card,
1515 say Y and read the Ethernet-HOWTO, available from
1516 <http://www.tldp.org/docs.html#howto>.
1518 This driver also works for the following NE2000 clone cards:
1519 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1520 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1521 Holtek HT80232 Holtek HT80229
1523 To compile this driver as a module, choose M here. The module
1524 will be called ne2k-pci.
1527 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1528 depends on NET_PCI && EISA && EXPERIMENTAL
1531 If you have a network (Ethernet) card of this type, say Y and read
1532 the Ethernet-HOWTO, available from
1533 <http://www.tldp.org/docs.html#howto>. Note that this driver
1534 will NOT WORK for NE3200 cards as they are completely different.
1536 To compile this driver as a module, choose M here. The module
1537 will be called ne3210.
1540 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1541 depends on NET_PCI && EISA && EXPERIMENTAL
1544 If you have a network (Ethernet) card of this type, say Y and read
1545 the Ethernet-HOWTO, available from
1546 <http://www.tldp.org/docs.html#howto>.
1548 To compile this driver as a module, choose M here. The module
1549 will be called es3210.
1552 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1553 depends on NET_PCI && PCI && EXPERIMENTAL
1557 This is a driver for the Fast Ethernet PCI network cards based on
1558 the RTL8139C+ chips. If you have one of those, say Y and read
1559 the Ethernet-HOWTO, available from
1560 <http://www.tldp.org/docs.html#howto>.
1562 To compile this driver as a module, choose M here: the module
1563 will be called 8139cp. This is recommended.
1566 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1567 depends on NET_PCI && PCI
1571 This is a driver for the Fast Ethernet PCI network cards based on
1572 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1573 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1575 To compile this driver as a module, choose M here: the module
1576 will be called 8139too. This is recommended.
1579 bool "Use PIO instead of MMIO"
1583 This instructs the driver to use programmed I/O ports (PIO) instead
1584 of PCI shared memory (MMIO). This can possibly solve some problems
1585 in case your mainboard has memory consistency issues. If unsure,
1588 config 8139TOO_TUNE_TWISTER
1589 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1592 This implements a function which might come in handy in case you
1593 are using low quality on long cabling. It is required for RealTek
1594 RTL-8139 revision K boards, and totally unused otherwise. It tries
1595 to match the transceiver to the cable characteristics. This is
1596 experimental since hardly documented by the manufacturer.
1600 bool "Support for older RTL-8129/8130 boards"
1603 This enables support for the older and uncommon RTL-8129 and
1604 RTL-8130 chips, which support MII via an external transceiver,
1605 instead of an internal one. Disabling this option will save some
1606 memory by making the code size smaller. If unsure, say Y.
1608 config 8139_OLD_RX_RESET
1609 bool "Use older RX-reset method"
1612 The 8139too driver was recently updated to contain a more rapid
1613 reset sequence, in the face of severe receive errors. This "new"
1614 RX-reset method should be adequate for all boards. But if you
1615 experience problems, you can enable this option to restore the
1616 old RX-reset behavior. If unsure, say N.
1619 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1620 depends on NET_PCI && PCI
1624 This is a driver for the R6040 Fast Ethernet MACs found in the
1625 the RDC R-321x System-on-chips.
1627 To compile this driver as a module, choose M here: the module
1628 will be called r6040. This is recommended.
1631 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1632 depends on NET_PCI && PCI
1636 This is a driver for the Fast Ethernet PCI network cards based on
1637 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1638 SiS 630 and SiS 540 chipsets.
1640 This driver also supports AMD 79C901 HomePNA so that you can use
1641 your phone line as a network cable.
1643 To compile this driver as a module, choose M here: the module
1644 will be called sis900. This is recommended.
1647 tristate "SMC EtherPower II"
1648 depends on NET_PCI && PCI
1652 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1653 which is based on the SMC83c17x (EPIC/100).
1654 More specific information and updates are available from
1655 <http://www.scyld.com/network/epic100.html>.
1658 tristate "Sundance Alta support"
1659 depends on NET_PCI && PCI
1663 This driver is for the Sundance "Alta" chip.
1664 More specific information and updates are available from
1665 <http://www.scyld.com/network/sundance.html>.
1667 config SUNDANCE_MMIO
1668 bool "Use MMIO instead of PIO"
1671 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1672 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1673 is known to solve bugs on certain chips.
1678 tristate "TI ThunderLAN support"
1679 depends on NET_PCI && (PCI || EISA)
1681 If you have a PCI Ethernet network card based on the ThunderLAN chip
1682 which is supported by this driver, say Y and read the
1683 Ethernet-HOWTO, available from
1684 <http://www.tldp.org/docs.html#howto>.
1686 Devices currently supported by this driver are Compaq Netelligent,
1687 Compaq NetFlex and Olicom cards. Please read the file
1688 <file:Documentation/networking/tlan.txt> for more details.
1690 To compile this driver as a module, choose M here. The module
1691 will be called tlan.
1693 Please email feedback to <torben.mathiasen@compaq.com>.
1696 tristate "VIA Rhine support"
1697 depends on NET_PCI && PCI
1701 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1702 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1703 Ethernet functions can also be found integrated on South Bridges
1706 To compile this driver as a module, choose M here. The module
1707 will be called via-rhine.
1709 config VIA_RHINE_MMIO
1710 bool "Use MMIO instead of PIO"
1711 depends on VIA_RHINE
1713 This instructs the driver to use PCI shared memory (MMIO) instead of
1714 programmed I/O ports (PIO). Enabling this gives an improvement in
1715 processing time in parts of the driver.
1719 config VIA_RHINE_NAPI
1720 bool "Use Rx Polling (NAPI)"
1721 depends on VIA_RHINE
1723 NAPI is a new driver API designed to reduce CPU and interrupt load
1724 when the driver is receiving lots of packets from the card.
1726 If your estimated Rx load is 10kpps or more, or if the card will be
1727 deployed on potentially unfriendly networks (e.g. in a firewall),
1731 bool "Philips SAA9730 Ethernet support"
1732 depends on NET_PCI && PCI && MIPS_ATLAS
1734 The SAA9730 is a combined multimedia and peripheral controller used
1735 in thin clients, Internet access terminals, and diskless
1737 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1740 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1741 depends on NET_PCI && PCI && EXPERIMENTAL
1744 This is a driver for the Fast Ethernet PCI network cards based on
1745 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1746 have one of these, say Y here.
1748 To compile this driver as a module, choose M here: the module
1749 will be called sc92031. This is recommended.
1752 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1753 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1756 TI AR7 CPMAC Ethernet support
1759 bool "Pocket and portable adapters"
1762 Cute little network (Ethernet) devices which attach to the parallel
1763 port ("pocket adapters"), commonly used with laptops. If you have
1764 one of those, say Y and read the Ethernet-HOWTO, available from
1765 <http://www.tldp.org/docs.html#howto>.
1767 If you want to plug a network (or some other) card into the PCMCIA
1768 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1769 credit card size extension cards used by all modern laptops), you
1770 need the pcmcia-cs package (location contained in the file
1771 <file:Documentation/Changes>) and you can say N here.
1773 Laptop users should read the Linux Laptop home page at
1774 <http://www.linux-on-laptops.com/> or
1775 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1777 Note that the answer to this question doesn't directly affect the
1778 kernel: saying N will just cause the configurator to skip all
1779 the questions about this class of network devices. If you say Y, you
1780 will be asked for your specific device in the following questions.
1783 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1784 depends on NET_POCKET && PARPORT && X86
1787 This is a network (Ethernet) device which attaches to your parallel
1788 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1789 available from <http://www.tldp.org/docs.html#howto>, if you
1790 want to use this. If you intend to use this driver, you should have
1791 said N to the "Parallel printer support", because the two drivers
1792 don't like each other.
1794 To compile this driver as a module, choose M here: the module
1798 tristate "D-Link DE600 pocket adapter support"
1799 depends on NET_POCKET && PARPORT
1801 This is a network (Ethernet) device which attaches to your parallel
1802 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1803 Ethernet-HOWTO, available from
1804 <http://www.tldp.org/docs.html#howto>, if you want to use
1805 this. It is possible to have several devices share a single parallel
1806 port and it is safe to compile the corresponding drivers into the
1809 To compile this driver as a module, choose M here: the module
1810 will be called de600.
1813 tristate "D-Link DE620 pocket adapter support"
1814 depends on NET_POCKET && PARPORT
1816 This is a network (Ethernet) device which attaches to your parallel
1817 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1818 Ethernet-HOWTO, available from
1819 <http://www.tldp.org/docs.html#howto>, if you want to use
1820 this. It is possible to have several devices share a single parallel
1821 port and it is safe to compile the corresponding drivers into the
1824 To compile this driver as a module, choose M here: the module
1825 will be called de620.
1828 tristate "SGI Seeq ethernet controller support"
1829 depends on SGI_HAS_SEEQ
1831 Say Y here if you have an Seeq based Ethernet network card. This is
1832 used in many Silicon Graphics machines.
1835 tristate "DEC LANCE ethernet controller support"
1836 depends on MACH_DECSTATION
1839 This driver is for the series of Ethernet controllers produced by
1840 DEC (now Compaq) based on the AMD Lance chipset, including the
1841 DEPCA series. (This chipset is better known via the NE2100 cards.)
1844 bool "Motorola 68360 ethernet controller"
1847 Say Y here if you want to use the built-in ethernet controller of
1848 the Motorola 68360 processor.
1851 bool "FEC ethernet controller (of ColdFire CPUs)"
1852 depends on M523x || M527x || M5272 || M528x || M520x
1854 Say Y here if you want to use the built-in 10/100 Fast ethernet
1855 controller on some Motorola ColdFire processors.
1858 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1861 Say Y here if you want to use the second built-in 10/100 Fast
1862 ethernet controller on some Motorola ColdFire processors.
1865 tristate "MPC52xx FEC driver"
1866 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
1870 This option enables support for the MPC5200's on-chip
1871 Fast Ethernet Controller
1872 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1874 config FEC_MPC52xx_MDIO
1875 bool "MPC52xx FEC MDIO bus driver"
1876 depends on FEC_MPC52xx
1879 The MPC5200's FEC can connect to the Ethernet either with
1880 an external MII PHY chip or 10 Mbps 7-wire interface
1881 (Motorola? industry standard).
1882 If your board uses an external PHY connected to FEC, enable this.
1883 If not sure, enable.
1884 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1887 tristate "NE2000 compatible support for H8/300"
1890 Say Y here if you want to use the NE2000 compatible
1891 controller on the Renesas H8/300 processor.
1893 source "drivers/net/fec_8xx/Kconfig"
1894 source "drivers/net/fs_enet/Kconfig"
1896 endif # NET_ETHERNET
1902 menuconfig NETDEV_1000
1903 bool "Ethernet (1000 Mbit)"
1907 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1908 type of Local Area Network (LAN) in universities and companies.
1910 Say Y here to get to see options for Gigabit Ethernet drivers.
1911 This option alone does not add any kernel code.
1912 Note that drivers supporting both 100 and 1000 MBit may be listed
1913 under "Ethernet (10 or 100MBit)" instead.
1915 If you say N, all options in this submenu will be skipped and disabled.
1920 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1923 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1924 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1925 adapter. The driver allows for using the Jumbo Frame option (9000
1926 bytes/frame) however it requires that your switches can handle this
1927 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1930 To compile this driver as a module, choose M here: the
1931 module will be called acenic.
1933 config ACENIC_OMIT_TIGON_I
1934 bool "Omit support for old Tigon I based AceNICs"
1937 Say Y here if you only have Tigon II based AceNICs and want to leave
1938 out support for the older Tigon I based cards which are no longer
1939 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1940 version)). This will reduce the size of the driver object by
1941 app. 100KB. If you are not sure whether your card is a Tigon I or a
1942 Tigon II, say N here.
1944 The safe and default value for this is N.
1947 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1951 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1953 D-Link DGE-550T Gigabit Ethernet Adapter.
1954 D-Link DL2000-based Gigabit Ethernet Adapter.
1955 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1957 To compile this driver as a module, choose M here: the
1958 module will be called dl2k.
1961 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1964 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1965 adapters. For more information on how to identify your adapter, go
1966 to the Adapter & Driver ID Guide at:
1968 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1970 For general information and support, go to the Intel support
1973 <http://support.intel.com>
1975 More specific information on configuring the driver is in
1976 <file:Documentation/networking/e1000.txt>.
1978 To compile this driver as a module, choose M here. The module
1979 will be called e1000.
1982 bool "Use Rx Polling (NAPI)"
1985 NAPI is a new driver API designed to reduce CPU and interrupt load
1986 when the driver is receiving lots of packets from the card. It is
1987 still somewhat experimental and thus not yet enabled by default.
1989 If your estimated Rx load is 10kpps or more, or if the card will be
1990 deployed on potentially unfriendly networks (e.g. in a firewall),
1995 config E1000_DISABLE_PACKET_SPLIT
1996 bool "Disable Packet Split for PCI express adapters"
1999 Say Y here if you want to use the legacy receive path for PCI express
2005 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2006 depends on PCI && (!SPARC32 || BROKEN)
2008 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2009 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2010 use the regular e1000 driver For more information on how to
2011 identify your adapter, go to the Adapter & Driver ID Guide at:
2013 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2015 For general information and support, go to the Intel support
2018 <http://support.intel.com>
2020 To compile this driver as a module, choose M here. The module
2021 will be called e1000e.
2024 tristate "IP1000 Gigabit Ethernet support"
2025 depends on PCI && EXPERIMENTAL
2028 This driver supports IP1000 gigabit Ethernet cards.
2030 To compile this driver as a module, choose M here: the module
2031 will be called ipg. This is recommended.
2034 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
2037 This driver supports Intel(R) 82575 gigabit ethernet family of
2038 adapters. For more information on how to identify your adapter, go
2039 to the Adapter & Driver ID Guide at:
2041 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2043 For general information and support, go to the Intel support
2046 <http://support.intel.com>
2048 More specific information on configuring the driver is in
2049 <file:Documentation/networking/e1000.txt>.
2051 To compile this driver as a module, choose M here. The module
2054 source "drivers/net/ixp2000/Kconfig"
2057 tristate "MyriCOM Gigabit Ethernet support"
2060 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2062 To compile this driver as a module, choose M here: the module
2063 will be called myri_sbus. This is recommended.
2066 tristate "National Semiconductor DP83820 support"
2069 This is a driver for the National Semiconductor DP83820 series
2070 of gigabit ethernet MACs. Cards using this chipset include
2071 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2072 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2076 tristate "Packet Engines Hamachi GNIC-II support"
2080 If you have a Gigabit Ethernet card of this type, say Y and read
2081 the Ethernet-HOWTO, available from
2082 <http://www.tldp.org/docs.html#howto>.
2084 To compile this driver as a module, choose M here. The module will be
2088 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2089 depends on PCI && EXPERIMENTAL
2092 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2093 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2094 used by the Beowulf Linux cluster project. See
2095 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2096 information about this driver in particular and Beowulf in general.
2098 To compile this driver as a module, choose M here: the module
2099 will be called yellowfin. This is recommended.
2102 tristate "Realtek 8169 gigabit ethernet support"
2106 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2108 To compile this driver as a module, choose M here: the module
2109 will be called r8169. This is recommended.
2113 depends on R8169 && VLAN_8021Q
2115 Say Y here for the r8169 driver to support the functions required
2116 by the kernel 802.1Q code.
2121 tristate "SB1250 Gigabit Ethernet support"
2122 depends on SIBYTE_SB1xxx_SOC
2125 This driver supports Gigabit Ethernet interfaces based on the
2126 Broadcom SiByte family of System-On-a-Chip parts. They include
2127 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2130 To compile this driver as a module, choose M here: the module
2131 will be called sb1250-mac.
2134 tristate "SiS190/SiS191 gigabit ethernet support"
2139 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2140 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2141 appear in lan on motherboard designs which are based on SiS 965
2142 and SiS 966 south bridge.
2144 To compile this driver as a module, choose M here: the module
2145 will be called sis190. This is recommended.
2148 tristate "New SysKonnect GigaEthernet support"
2152 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2153 and related Gigabit Ethernet adapters. It is a new smaller driver
2154 with better performance and more complete ethtool support.
2156 It does not support the link failover and network management
2157 features that "portable" vendor supplied sk98lin driver does.
2159 This driver supports adapters based on the original Yukon chipset:
2160 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2161 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2163 It does not support the newer Yukon2 chipset: a separate driver,
2164 sky2, is provided for Yukon2-based adapters.
2166 To compile this driver as a module, choose M here: the module
2167 will be called skge. This is recommended.
2170 bool "Debugging interface"
2171 depends on SKGE && DEBUG_FS
2173 This option adds the ability to dump driver state for debugging.
2174 The file debugfs/skge/ethX displays the state of the internal
2175 transmit and receive rings.
2180 tristate "SysKonnect Yukon2 support"
2184 This driver supports Gigabit Ethernet adapters based on the
2185 Marvell Yukon 2 chipset:
2186 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2187 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2189 There is companion driver for the older Marvell Yukon and
2190 Genesis based adapters: skge.
2192 To compile this driver as a module, choose M here: the module
2193 will be called sky2. This is recommended.
2196 bool "Debugging interface"
2197 depends on SKY2 && DEBUG_FS
2199 This option adds the ability to dump driver state for debugging.
2200 The file debugfs/sky2/ethX displays the state of the internal
2201 transmit and receive rings.
2206 tristate "VIA Velocity support"
2212 If you have a VIA "Velocity" based network card say Y here.
2214 To compile this driver as a module, choose M here. The module
2215 will be called via-velocity.
2218 tristate "Broadcom Tigon3 support"
2222 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2224 To compile this driver as a module, choose M here: the module
2225 will be called tg3. This is recommended.
2228 tristate "Broadcom NetXtremeII support"
2233 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2235 To compile this driver as a module, choose M here: the module
2236 will be called bnx2. This is recommended.
2239 tristate "Spider Gigabit Ethernet driver"
2240 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2243 This driver supports the Gigabit Ethernet chips present on the
2244 Cell Processor-Based Blades from IBM.
2247 tristate "Tundra TSI108 gigabit Ethernet support"
2248 depends on TSI108_BRIDGE
2250 This driver supports Tundra TSI108 gigabit Ethernet ports.
2251 To compile this driver as a module, choose M here: the module
2252 will be called tsi108_eth.
2255 tristate "PS3 Gigabit Ethernet driver"
2257 select PS3_SYS_MANAGER
2259 This driver supports the network device on the PS3 game
2260 console. This driver has built-in support for Ethernet.
2262 To compile this driver as a module, choose M here: the
2263 module will be called ps3_gelic.
2265 config GELIC_WIRELESS
2266 bool "PS3 Wireless support"
2267 depends on GELIC_NET
2270 This option adds the support for the wireless feature of PS3.
2271 If you have the wireless-less model of PS3 or have no plan to
2272 use wireless feature, disabling this option saves memory. As
2273 the driver automatically distinguishes the models, you can
2274 safely enable this option even if you have a wireless-less model.
2276 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2277 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2278 depends on GELIC_WIRELESS
2280 This option retains the obsolete private interface to pass
2281 the PSK from user space programs to the driver. The PSK
2282 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2283 (WPA-Personal) environment.
2284 If WPA[2]-PSK is used and you need to use old programs that
2285 support only this old interface, say Y. Otherwise N.
2290 tristate "Gianfar Ethernet"
2295 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2296 and MPC86xx family of chips, and the FEC on the 8540.
2299 bool "Use Rx Polling (NAPI)"
2303 tristate "Freescale QE Gigabit Ethernet"
2304 depends on QUICC_ENGINE
2307 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2308 which is available on some Freescale SOCs.
2311 bool "Use Rx Polling (NAPI)"
2314 config UGETH_MAGIC_PACKET
2315 bool "Magic Packet detection support"
2318 config UGETH_FILTERING
2319 bool "Mac address filtering support"
2322 config UGETH_TX_ON_DEMAND
2323 bool "Transmit on Demand support"
2327 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2328 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2331 This driver supports the gigabit ethernet MACs in the
2332 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2333 in the Marvell Orion ARM SoC family.
2335 Some boards that use the Discovery chipset are the Momenco
2336 Ocelot C and Jaguar ATX and Pegasos II.
2339 tristate "QLogic QLA3XXX Network Driver Support"
2342 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2344 To compile this driver as a module, choose M here: the module
2345 will be called qla3xxx.
2348 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2349 depends on PCI && EXPERIMENTAL
2353 This driver supports the Attansic L1 gigabit ethernet adapter.
2355 To compile this driver as a module, choose M here. The module
2356 will be called atl1.
2361 # 10 Gigabit Ethernet
2364 menuconfig NETDEV_10000
2365 bool "Ethernet (10000 Mbit)"
2369 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2370 This option alone does not add any kernel code.
2372 If you say N, all options in this submenu will be skipped and disabled.
2377 tristate "Chelsio 10Gb Ethernet support"
2381 This driver supports Chelsio gigabit and 10-gigabit
2382 Ethernet cards. More information about adapter features and
2383 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2385 For general information about Chelsio and our products, visit
2386 our website at <http://www.chelsio.com>.
2388 For customer support, please visit our customer support page at
2389 <http://www.chelsio.com/support.htm>.
2391 Please send feedback to <linux-bugs@chelsio.com>.
2393 To compile this driver as a module, choose M here: the module
2394 will be called cxgb.
2396 config CHELSIO_T1_1G
2397 bool "Chelsio gigabit Ethernet support"
2398 depends on CHELSIO_T1
2400 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2401 are using only 10G cards say 'N' here.
2403 config CHELSIO_T1_NAPI
2404 bool "Use Rx Polling (NAPI)"
2405 depends on CHELSIO_T1
2408 NAPI is a driver API designed to reduce CPU and interrupt load
2409 when the driver is receiving lots of packets from the card.
2412 tristate "Chelsio Communications T3 10Gb Ethernet support"
2413 depends on PCI && INET
2417 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2420 For general information about Chelsio and our products, visit
2421 our website at <http://www.chelsio.com>.
2423 For customer support, please visit our customer support page at
2424 <http://www.chelsio.com/support.htm>.
2426 Please send feedback to <linux-bugs@chelsio.com>.
2428 To compile this driver as a module, choose M here: the module
2429 will be called cxgb3.
2432 tristate "eHEA Ethernet support"
2433 depends on IBMEBUS && INET && SPARSEMEM
2436 This driver supports the IBM pSeries eHEA ethernet adapter.
2438 To compile the driver as a module, choose M here. The module
2439 will be called ehea.
2442 tristate "Intel(R) 10GbE PCI Express adapters support"
2443 depends on PCI && INET
2446 This driver supports Intel(R) 10GbE PCI Express family of
2447 adapters. For more information on how to identify your adapter, go
2448 to the Adapter & Driver ID Guide at:
2450 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2452 For general information and support, go to the Intel support
2455 <http://support.intel.com>
2457 To compile this driver as a module, choose M here. The module
2458 will be called ixgbe.
2461 tristate "Intel(R) PRO/10GbE support"
2464 This driver supports Intel(R) PRO/10GbE family of adapters for
2465 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2466 instead. For more information on how to identify your adapter, go
2467 to the Adapter & Driver ID Guide at:
2469 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2471 For general information and support, go to the Intel support
2474 <http://support.intel.com>
2476 More specific information on configuring the driver is in
2477 <file:Documentation/networking/ixgb.txt>.
2479 To compile this driver as a module, choose M here. The module
2480 will be called ixgb.
2483 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2484 depends on IXGB && EXPERIMENTAL
2486 NAPI is a new driver API designed to reduce CPU and interrupt load
2487 when the driver is receiving lots of packets from the card. It is
2488 still somewhat experimental and thus not yet enabled by default.
2490 If your estimated Rx load is 10kpps or more, or if the card will be
2491 deployed on potentially unfriendly networks (e.g. in a firewall),
2497 tristate "S2IO 10Gbe XFrame NIC"
2500 This driver supports the 10Gbe XFrame NIC of S2IO.
2501 More specific information on configuring the driver is in
2502 <file:Documentation/networking/s2io.txt>.
2505 tristate "Myricom Myri-10G Ethernet support"
2506 depends on PCI && INET
2511 This driver supports Myricom Myri-10G Dual Protocol interface in
2512 Ethernet mode. If the eeprom on your board is not recent enough,
2513 you will need a newer firmware image.
2514 You may get this image or more information, at:
2516 <http://www.myri.com/scs/download-Myri10GE.html>
2518 To compile this driver as a module, choose M here. The module
2519 will be called myri10ge.
2522 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2525 This enables the support for NetXen's Gigabit Ethernet card.
2528 tristate "Sun Neptune 10Gbit Ethernet support"
2531 This enables support for cards based upon Sun's
2535 tristate "PA Semi 1/10Gbit MAC"
2536 depends on PPC_PASEMI && PCI
2540 This driver supports the on-chip 1/10Gbit Ethernet controller on
2541 PA Semi's PWRficient line of chips.
2549 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2550 depends on MLX4_CORE
2553 This option causes debugging code to be compiled into the
2554 mlx4_core driver. The output can be turned on via the
2555 debug_level module parameter (which can also be set after
2556 the driver is loaded through sysfs).
2559 tristate "Tehuti Networks 10G Ethernet"
2562 Tehuti Networks 10G Ethernet NIC
2565 tristate "Broadcom NetXtremeII 10Gb support"
2570 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2571 To compile this driver as a module, choose M here: the module
2572 will be called bnx2x. This is recommended.
2574 source "drivers/net/sfc/Kconfig"
2576 endif # NETDEV_10000
2578 source "drivers/net/tokenring/Kconfig"
2580 source "drivers/net/wireless/Kconfig"
2582 source "drivers/net/usb/Kconfig"
2584 source "drivers/net/pcmcia/Kconfig"
2586 source "drivers/net/wan/Kconfig"
2588 source "drivers/atm/Kconfig"
2590 source "drivers/s390/net/Kconfig"
2592 config XEN_NETDEV_FRONTEND
2593 tristate "Xen network device frontend driver"
2597 The network device frontend driver allows the kernel to
2598 access network devices exported exported by a virtual
2599 machine containing a physical network device driver. The
2600 frontend driver is intended for unprivileged guest domains;
2601 if you are compiling a kernel for a Xen guest, you almost
2602 certainly want to enable this.
2605 tristate "iSeries Virtual Ethernet driver support"
2606 depends on PPC_ISERIES
2609 tristate "RapidIO Ethernet over messaging driver support"
2612 config RIONET_TX_SIZE
2613 int "Number of outbound queue entries"
2617 config RIONET_RX_SIZE
2618 int "Number of inbound queue entries"
2623 bool "FDDI driver support"
2624 depends on (PCI || EISA || TC)
2626 Fiber Distributed Data Interface is a high speed local area network
2627 design; essentially a replacement for high speed Ethernet. FDDI can
2628 run over copper or fiber. If you are connected to such a network and
2629 want a driver for the FDDI card in your computer, say Y here (and
2630 then also Y to the driver for your FDDI card, below). Most people
2634 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2635 depends on FDDI && (PCI || EISA || TC)
2637 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2638 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2639 to a local FDDI network.
2641 To compile this driver as a module, choose M here: the module
2642 will be called defxx. If unsure, say N.
2646 prompt "Use MMIO instead of PIO" if PCI || EISA
2648 default n if PCI || EISA
2651 This instructs the driver to use EISA or PCI memory-mapped I/O
2652 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2653 Enabling this gives an improvement in processing time in parts
2654 of the driver, but it may cause problems with EISA (DEFEA)
2655 adapters. TURBOchannel does not have the concept of I/O ports,
2656 so MMIO is always used for these (DEFTA) adapters.
2661 tristate "SysKonnect FDDI PCI support"
2662 depends on FDDI && PCI
2665 Say Y here if you have a SysKonnect FDDI PCI adapter.
2666 The following adapters are supported by this driver:
2667 - SK-5521 (SK-NET FDDI-UP)
2668 - SK-5522 (SK-NET FDDI-UP DAS)
2669 - SK-5541 (SK-NET FDDI-FP)
2670 - SK-5543 (SK-NET FDDI-LP)
2671 - SK-5544 (SK-NET FDDI-LP DAS)
2672 - SK-5821 (SK-NET FDDI-UP64)
2673 - SK-5822 (SK-NET FDDI-UP64 DAS)
2674 - SK-5841 (SK-NET FDDI-FP64)
2675 - SK-5843 (SK-NET FDDI-LP64)
2676 - SK-5844 (SK-NET FDDI-LP64 DAS)
2677 - Netelligent 100 FDDI DAS Fibre SC
2678 - Netelligent 100 FDDI SAS Fibre SC
2679 - Netelligent 100 FDDI DAS UTP
2680 - Netelligent 100 FDDI SAS UTP
2681 - Netelligent 100 FDDI SAS Fibre MIC
2683 Read <file:Documentation/networking/skfp.txt> for information about
2686 Questions concerning this driver can be addressed to:
2687 <linux@syskonnect.de>
2689 To compile this driver as a module, choose M here: the module
2690 will be called skfp. This is recommended.
2693 bool "HIPPI driver support (EXPERIMENTAL)"
2694 depends on EXPERIMENTAL && INET && PCI
2696 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2697 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2698 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2699 single-mode). HIPPI networks are commonly used for clusters and to
2700 connect to super computers. If you are connected to a HIPPI network
2701 and have a HIPPI network card in your computer that you want to use
2702 under Linux, say Y here (you must also remember to enable the driver
2703 for your HIPPI card below). Most people will say N here.
2706 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2707 depends on HIPPI && PCI
2709 Say Y here if this is your PCI HIPPI network card.
2711 To compile this driver as a module, choose M here: the module
2712 will be called rrunner. If unsure, say N.
2714 config ROADRUNNER_LARGE_RINGS
2715 bool "Use large TX/RX rings (EXPERIMENTAL)"
2716 depends on ROADRUNNER
2718 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2719 of additional memory to allow for fastest operation, both for
2720 transmitting and receiving. This memory cannot be used by any other
2721 kernel code or by user space programs. Say Y here only if you have
2725 tristate "PLIP (parallel port) support"
2728 PLIP (Parallel Line Internet Protocol) is used to create a
2729 reasonably fast mini network consisting of two (or, rarely, more)
2730 local machines. A PLIP link from a Linux box is a popular means to
2731 install a Linux distribution on a machine which doesn't have a
2732 CD-ROM drive (a minimal system has to be transferred with floppies
2733 first). The kernels on both machines need to have this PLIP option
2734 enabled for this to work.
2736 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2737 ports (the connectors at the computers with 25 holes) are connected
2738 with "null printer" or "Turbo Laplink" cables which can transmit 4
2739 bits at a time (mode 0) or with special PLIP cables, to be used on
2740 bidirectional parallel ports only, which can transmit 8 bits at a
2741 time (mode 1); you can find the wiring of these cables in
2742 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2743 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2744 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2745 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2746 and winsock or NCSA's telnet.
2748 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2749 as the NET-3-HOWTO, both available from
2750 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2751 protocol has been changed and this PLIP driver won't work together
2752 with the PLIP support in Linux versions 1.0.x. This option enlarges
2753 your kernel by about 8 KB.
2755 To compile this driver as a module, choose M here. The module
2756 will be called plip. If unsure, say Y or M, in case you buy
2760 tristate "PPP (point-to-point protocol) support"
2763 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2764 the same purpose: sending Internet traffic over telephone (and other
2765 serial) lines. Ask your access provider if they support it, because
2766 otherwise you can't use it; most Internet access providers these
2767 days support PPP rather than SLIP.
2769 To use PPP, you need an additional program called pppd as described
2770 in the PPP-HOWTO, available at
2771 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2772 the version of pppd recommended in <file:Documentation/Changes>.
2773 The PPP option enlarges your kernel by about 16 KB.
2775 There are actually two versions of PPP: the traditional PPP for
2776 asynchronous lines, such as regular analog phone lines, and
2777 synchronous PPP which can be used over digital ISDN lines for
2778 example. If you want to use PPP over phone lines or other
2779 asynchronous serial lines, you need to say Y (or M) here and also to
2780 the next option, "PPP support for async serial ports". For PPP over
2781 synchronous lines, you should say Y (or M) here and to "Support
2782 synchronous PPP", below.
2784 If you said Y to "Version information on all symbols" above, then
2785 you cannot compile the PPP driver into the kernel; you can then only
2786 compile it as a module. To compile this driver as a module, choose M
2787 here. The module will be called ppp_generic.
2789 config PPP_MULTILINK
2790 bool "PPP multilink support (EXPERIMENTAL)"
2791 depends on PPP && EXPERIMENTAL
2793 PPP multilink is a protocol (defined in RFC 1990) which allows you
2794 to combine several (logical or physical) lines into one logical PPP
2795 connection, so that you can utilize your full bandwidth.
2797 This has to be supported at the other end as well and you need a
2798 version of the pppd daemon which understands the multilink protocol.
2803 bool "PPP filtering"
2806 Say Y here if you want to be able to filter the packets passing over
2807 PPP interfaces. This allows you to control which packets count as
2808 activity (i.e. which packets will reset the idle timer or bring up
2809 a demand-dialed link) and which packets are to be dropped entirely.
2810 You need to say Y here if you wish to use the pass-filter and
2811 active-filter options to pppd.
2816 tristate "PPP support for async serial ports"
2820 Say Y (or M) here if you want to be able to use PPP over standard
2821 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2822 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2825 To compile this driver as a module, choose M here.
2830 tristate "PPP support for sync tty ports"
2833 Say Y (or M) here if you want to be able to use PPP over synchronous
2834 (HDLC) tty devices, such as the SyncLink adapter. These devices
2835 are often used for high-speed leased lines like T1/E1.
2837 To compile this driver as a module, choose M here.
2840 tristate "PPP Deflate compression"
2845 Support for the Deflate compression method for PPP, which uses the
2846 Deflate algorithm (the same algorithm that gzip uses) to compress
2847 each PPP packet before it is sent over the wire. The machine at the
2848 other end of the PPP link (usually your ISP) has to support the
2849 Deflate compression method as well for this to be useful. Even if
2850 they don't support it, it is safe to say Y here.
2852 To compile this driver as a module, choose M here.
2855 tristate "PPP BSD-Compress compression"
2858 Support for the BSD-Compress compression method for PPP, which uses
2859 the LZW compression method to compress each PPP packet before it is
2860 sent over the wire. The machine at the other end of the PPP link
2861 (usually your ISP) has to support the BSD-Compress compression
2862 method as well for this to be useful. Even if they don't support it,
2863 it is safe to say Y here.
2865 The PPP Deflate compression method ("PPP Deflate compression",
2866 above) is preferable to BSD-Compress, because it compresses better
2869 Note that the BSD compression code will always be compiled as a
2870 module; it is called bsd_comp and will show up in the directory
2871 modules once you have said "make modules". If unsure, say N.
2874 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2875 depends on PPP && EXPERIMENTAL
2881 Support for the MPPE Encryption protocol, as employed by the
2882 Microsoft Point-to-Point Tunneling Protocol.
2884 See http://pptpclient.sourceforge.net/ for information on
2885 configuring PPTP clients and servers to utilize this method.
2888 tristate "PPP over Ethernet (EXPERIMENTAL)"
2889 depends on EXPERIMENTAL && PPP
2891 Support for PPP over Ethernet.
2893 This driver requires the latest version of pppd from the CVS
2894 repository at cvs.samba.org. Alternatively, see the
2895 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2896 which contains instruction on how to use this driver (under
2897 the heading "Kernel mode PPPoE").
2900 tristate "PPP over ATM"
2901 depends on ATM && PPP
2903 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2904 This implementation does not yet comply with section 8 of RFC2364,
2905 which can lead to bad results if the ATM peer loses state and
2906 changes its encapsulation unilaterally.
2909 tristate "PPP over L2TP (EXPERIMENTAL)"
2910 depends on EXPERIMENTAL && PPP && INET
2912 Support for PPP-over-L2TP socket family. L2TP is a protocol
2913 used by ISPs and enterprises to tunnel PPP traffic over UDP
2914 tunnels. L2TP is replacing PPTP for VPN uses.
2916 This kernel component handles only L2TP data packets: a
2917 userland daemon handles L2TP the control protocol (tunnel
2918 and session setup). One such daemon is OpenL2TP
2919 (http://openl2tp.sourceforge.net/).
2922 tristate "SLIP (serial line) support"
2924 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2925 connect to your Internet service provider or to connect to some
2926 other local Unix box or if you want to configure your Linux box as a
2927 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2928 Internet Protocol) is a protocol used to send Internet traffic over
2929 serial connections such as telephone lines or null modem cables;
2930 nowadays, the protocol PPP is more commonly used for this same
2933 Normally, your access provider has to support SLIP in order for you
2934 to be able to use it, but there is now a SLIP emulator called SLiRP
2935 around (available from
2936 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2937 allows you to use SLIP over a regular dial up shell connection. If
2938 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2939 NET-3-HOWTO, available from
2940 <http://www.tldp.org/docs.html#howto>, explains how to
2941 configure SLIP. Note that you don't need this option if you just
2942 want to run term (term is a program which gives you almost full
2943 Internet connectivity if you have a regular dial up shell account on
2944 some Internet connected Unix computer. Read
2945 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2946 support will enlarge your kernel by about 4 KB. If unsure, say N.
2948 To compile this driver as a module, choose M here. The module
2949 will be called slip.
2951 config SLIP_COMPRESSED
2952 bool "CSLIP compressed headers"
2956 This protocol is faster than SLIP because it uses compression on the
2957 TCP/IP headers (not on the data itself), but it has to be supported
2958 on both ends. Ask your access provider if you are not sure and
2959 answer Y, just in case. You will still be able to use plain SLIP. If
2960 you plan to use SLiRP, the SLIP emulator (available from
2961 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2962 allows you to use SLIP over a regular dial up shell connection, you
2963 definitely want to say Y here. The NET-3-HOWTO, available from
2964 <http://www.tldp.org/docs.html#howto>, explains how to configure
2965 CSLIP. This won't enlarge your kernel.
2970 This option enables Van Jacobsen serial line header compression
2974 bool "Keepalive and linefill"
2977 Adds additional capabilities to the SLIP driver to support the
2978 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2981 config SLIP_MODE_SLIP6
2982 bool "Six bit SLIP encapsulation"
2985 Just occasionally you may need to run IP over hostile serial
2986 networks that don't pass all control characters or are only seven
2987 bit. Saying Y here adds an extra mode you can use with SLIP:
2988 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2989 the serial device. Naturally, this has to be supported at the other
2990 end of the link as well. It's good enough, for example, to run IP
2991 over the async ports of a Camtec JNT Pad. If unsure, say N.
2994 bool "Fibre Channel driver support"
2995 depends on SCSI && PCI
2997 Fibre Channel is a high speed serial protocol mainly used to connect
2998 large storage devices to the computer; it is compatible with and
2999 intended to replace SCSI.
3001 If you intend to use Fibre Channel, you need to have a Fibre channel
3002 adaptor card in your computer; say Y here and to the driver for your
3003 adaptor below. You also should have said Y to "SCSI support" and
3004 "SCSI generic support".
3007 tristate "Network console logging support (EXPERIMENTAL)"
3008 depends on EXPERIMENTAL
3010 If you want to log kernel messages over the network, enable this.
3011 See <file:Documentation/networking/netconsole.txt> for details.
3013 config NETCONSOLE_DYNAMIC
3014 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3015 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3018 This option enables the ability to dynamically reconfigure target
3019 parameters (interface, IP addresses, port numbers, MAC addresses)
3020 at runtime through a userspace interface exported using configfs.
3021 See <file:Documentation/networking/netconsole.txt> for details.
3027 bool "Netpoll traffic trapping"
3031 config NET_POLL_CONTROLLER
3035 tristate "Virtio network driver (EXPERIMENTAL)"
3036 depends on EXPERIMENTAL && VIRTIO
3038 This is the virtual network driver for virtio. It can be used with
3039 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.