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 COMPAT_NET_DEV_OPS
31 bool "Enable older network device API compatiablity"
33 This option enables kernel compatiability with older network devices
34 that do not use net_device_ops interface.
39 tristate "Intermediate Functional Block support"
40 depends on NET_CLS_ACT
42 This is an intermediate driver that allows sharing of
44 To compile this driver as a module, choose M here: the module
45 will be called ifb. If you want to use more than one ifb
46 device at a time, you need to compile this driver as a module.
47 Instead of 'ifb', the devices will then be called 'ifb0',
49 Look at the iproute2 documentation directory for usage etc
52 tristate "Dummy net driver support"
54 This is essentially a bit-bucket device (i.e. traffic you send to
55 this device is consigned into oblivion) with a configurable IP
56 address. It is most commonly used in order to make your currently
57 inactive SLIP address seem like a real address for local programs.
58 If you use SLIP or PPP, you might want to say Y here. Since this
59 thing often comes in handy, the default is Y. It won't enlarge your
60 kernel either. What a deal. Read about it in the Network
61 Administrator's Guide, available from
62 <http://www.tldp.org/docs.html#guide>.
64 To compile this driver as a module, choose M here: the module
65 will be called dummy. If you want to use more than one dummy
66 device at a time, you need to compile this driver as a module.
67 Instead of 'dummy', the devices will then be called 'dummy0',
71 tristate "Bonding driver support"
73 depends on IPV6 || IPV6=n
75 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
76 Channels together. This is called 'Etherchannel' by Cisco,
77 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
79 The driver supports multiple bonding modes to allow for both high
80 performance and high availability operation.
82 Refer to <file:Documentation/networking/bonding.txt> for more
85 To compile this driver as a module, choose M here: the module
86 will be called bonding.
89 tristate "MAC-VLAN support (EXPERIMENTAL)"
90 depends on EXPERIMENTAL
92 This allows one to create virtual interfaces that map packets to
93 or from specific MAC addresses to a particular interface.
95 Macvlan devices can be added using the "ip" command from the
96 iproute2 package starting with the iproute2-2.6.23 release:
98 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
100 To compile this driver as a module, choose M here: the module
101 will be called macvlan.
104 tristate "EQL (serial line load balancing) support"
106 If you have two serial connections to some other computer (this
107 usually requires two modems and two telephone lines) and you use
108 SLIP (the protocol for sending Internet traffic over telephone
109 lines) or PPP (a better SLIP) on them, you can make them behave like
110 one double speed connection using this driver. Naturally, this has
111 to be supported at the other end as well, either with a similar EQL
112 Linux driver or with a Livingston Portmaster 2e.
114 Say Y if you want this and read
115 <file:Documentation/networking/eql.txt>. You may also want to read
116 section 6.2 of the NET-3-HOWTO, available from
117 <http://www.tldp.org/docs.html#howto>.
119 To compile this driver as a module, choose M here: the module
120 will be called eql. If unsure, say N.
123 tristate "Universal TUN/TAP device driver support"
126 TUN/TAP provides packet reception and transmission for user space
127 programs. It can be viewed as a simple Point-to-Point or Ethernet
128 device, which instead of receiving packets from a physical media,
129 receives them from user space program and instead of sending packets
130 via physical media writes them to the user space program.
132 When a program opens /dev/net/tun, driver creates and registers
133 corresponding net device tunX or tapX. After a program closed above
134 devices, driver will automatically delete tunXX or tapXX device and
135 all routes corresponding to it.
137 Please read <file:Documentation/networking/tuntap.txt> for more
140 To compile this driver as a module, choose M here: the module
143 If you don't know what to use this for, you don't need it.
146 tristate "Virtual ethernet pair device"
148 This device is a local ethernet tunnel. Devices are created in pairs.
149 When one end receives the packet it appears on its pair and vice
153 tristate "General Instruments Surfboard 1000"
156 This is a driver for the General Instrument (also known as
157 NextLevel) SURFboard 1000 internal
158 cable modem. This is an ISA card which is used by a number of cable
159 TV companies to provide cable modem access. It's a one-way
160 downstream-only cable modem, meaning that your upstream net link is
161 provided by your regular phone modem.
163 At present this driver only compiles as a module, so say M here if
164 you have this card. The module will be called sb1000. Then read
165 <file:Documentation/networking/README.sb1000> for information on how
166 to use this module, as it needs special ppp scripts for establishing
167 a connection. Further documentation and the necessary scripts can be
170 <http://www.jacksonville.net/~fventuri/>
171 <http://home.adelphia.net/~siglercm/sb1000.html>
172 <http://linuxpower.cx/~cable/>
174 If you don't have this card, of course say N.
176 source "drivers/net/arcnet/Kconfig"
178 source "drivers/net/phy/Kconfig"
184 menuconfig NET_ETHERNET
185 bool "Ethernet (10 or 100Mbit)"
188 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
189 type of Local Area Network (LAN) in universities and companies.
191 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
192 coaxial cable, linking computers in a chain), 10BASE-T or twisted
193 pair (10 Mbps over twisted pair cable, linking computers to central
194 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
195 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
196 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
197 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
198 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
199 Ethernet (1 Gbps over optical fiber or short copper links).
201 If your Linux machine will be connected to an Ethernet and you have
202 an Ethernet network interface card (NIC) installed in your computer,
203 say Y here and read the Ethernet-HOWTO, available from
204 <http://www.tldp.org/docs.html#howto>. You will then also have
205 to say Y to the driver for your particular NIC.
207 Note that the answer to this question won't directly affect the
208 kernel: saying N will just cause the configurator to skip all
209 the questions about Ethernet network cards. If unsure, say N.
214 tristate "Generic Media Independent Interface device support"
216 Most ethernet controllers have MII transceiver either as an external
217 or internal device. It is safe to say Y or M here even if your
218 ethernet card lack MII.
221 tristate "Atmel MACB support"
222 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
225 The Atmel MACB ethernet interface is found on many AT32 and AT91
226 parts. Say Y to include support for the MACB chip.
228 To compile this driver as a module, choose M here: the module
231 source "drivers/net/arm/Kconfig"
234 tristate "ASIX AX88796 NE2000 clone support"
235 depends on ARM || MIPS || SUPERH
239 AX88796 driver, using platform bus to provide
240 chip detection and resources
243 bool "ASIX AX88796 external 93CX6 eeprom support"
247 Select this if your platform comes with an external 93CX6 eeprom.
250 tristate "MACE (Power Mac ethernet) support"
251 depends on PPC_PMAC && PPC32
254 Power Macintoshes and clones with Ethernet built-in on the
255 motherboard will usually use a MACE (Medium Access Control for
256 Ethernet) interface. Say Y to include support for the MACE chip.
258 To compile this driver as a module, choose M here: the module
261 config MACE_AAUI_PORT
262 bool "Use AAUI port instead of TP by default"
265 Some Apple machines (notably the Apple Network Server) which use the
266 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
267 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
268 Y here if you have such a machine. If unsure, say N.
269 The driver will default to AAUI on ANS anyway, and if you use it as
270 a module, you can provide the port_aaui=0|1 to force the driver.
273 tristate "BMAC (G3 ethernet) support"
274 depends on PPC_PMAC && PPC32
277 Say Y for support of BMAC Ethernet interfaces. These are used on G3
280 To compile this driver as a module, choose M here: the module
284 tristate "Ariadne support"
287 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
290 To compile this driver as a module, choose M here: the module
291 will be called ariadne.
294 tristate "A2065 support"
298 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
301 To compile this driver as a module, choose M here: the module
302 will be called a2065.
305 tristate "Hydra support"
309 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
311 To compile this driver as a module, choose M here: the module
312 will be called hydra.
315 tristate "Zorro NS8390-based Ethernet support"
319 This driver is for Zorro Ethernet cards using an NS8390-compatible
320 chipset, like the Village Tronic Ariadne II and the Individual
321 Computers X-Surf Ethernet cards. If you have such a card, say Y.
324 To compile this driver as a module, choose M here: the module
325 will be called zorro8390.
328 tristate "PCMCIA NE2000 support"
329 depends on AMIGA_PCMCIA
332 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
335 To compile this driver as a module, choose M here: the module
339 bool "Macintosh NS 8390 based ethernet cards"
343 If you want to include a driver to support Nubus or LC-PDS
344 Ethernet cards using an NS8390 chipset or its equivalent, say Y
345 and read the Ethernet-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>.
349 tristate "Macintosh CS89x0 based ethernet cards"
352 Support for CS89x0 chipset based Ethernet cards. If you have a
353 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
354 read the Ethernet-HOWTO, available from
355 <http://www.tldp.org/docs.html#howto>.
357 To compile this driver as a module, choose M here. This module will
361 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
364 Support for NatSemi SONIC based Ethernet devices. This includes
365 the onboard Ethernet in many Quadras as well as some LC-PDS,
366 a few Nubus and all known Comm Slot Ethernet cards. If you have
367 one of these say Y and read the Ethernet-HOWTO, available from
368 <http://www.tldp.org/docs.html#howto>.
370 To compile this driver as a module, choose M here. This module will
374 bool "Macintosh (AV) onboard MACE ethernet"
378 Support for the onboard AMD 79C940 MACE Ethernet controller used in
379 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
380 say Y and read the Ethernet-HOWTO, available from
381 <http://www.tldp.org/docs.html#howto>.
384 tristate "MVME147 (Lance) Ethernet support"
388 Support for the on-board Ethernet interface on the Motorola MVME147
389 single-board computer. Say Y here to include the
390 driver for this chip in your kernel.
391 To compile this driver as a module, choose M here.
394 tristate "MVME16x Ethernet support"
397 This is the driver for the Ethernet interface on the Motorola
398 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
399 driver for this chip in your kernel.
400 To compile this driver as a module, choose M here.
403 tristate "BVME6000 Ethernet support"
406 This is the driver for the Ethernet interface on BVME4000 and
407 BVME6000 VME boards. Say Y here to include the driver for this chip
409 To compile this driver as a module, choose M here.
412 tristate "Atari Lance support"
415 Say Y to include support for several Atari Ethernet adapters based
416 on the AMD Lance chipset: RieblCard (with or without battery), or
417 PAMCard VME (also the version by Rhotron, with different addresses).
420 tristate "Sun3/Sun3x on-board LANCE support"
421 depends on SUN3 || SUN3X
423 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
424 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
425 here to compile in the Linux driver for this and enable Ethernet.
426 General Linux information on the Sun 3 and 3x series (now
428 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
430 If you're not building a kernel for a Sun 3, say N.
433 bool "Sun3 on-board Intel 82586 support"
436 This driver enables support for the on-board Intel 82586 based
437 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
438 that this driver does not support 82586-based adapters on additional
442 bool "HP on-board LANCE support"
446 If you want to use the builtin "LANCE" Ethernet controller on an
447 HP300 machine, say Y here.
450 tristate "Lasi ethernet"
453 Say Y here to support the builtin Intel 82596 ethernet controller
454 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
457 tristate "SNI RM ethernet"
458 depends on NET_ETHERNET && SNI_RM
460 Say Y here to support the on-board Intel 82596 ethernet controller
461 built into SNI RM machines.
464 tristate "Korina (IDT RC32434) Ethernet support"
465 depends on NET_ETHERNET && MIKROTIK_RB532
467 If you have a Mikrotik RouterBoard 500 or IDT RC32434
468 based system say Y. Otherwise say N.
470 config MIPS_JAZZ_SONIC
471 tristate "MIPS JAZZ onboard SONIC Ethernet support"
474 This is the driver for the onboard card of MIPS Magnum 4000,
475 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
477 config XTENSA_XT2000_SONIC
478 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
479 depends on XTENSA_PLATFORM_XT2000
481 This is the driver for the onboard card of the Xtensa XT2000 board.
483 config MIPS_AU1X00_ENET
484 bool "MIPS AU1000 Ethernet support"
485 depends on SOC_AU1X00
489 If you have an Alchemy Semi AU1X00 based system
490 say Y. Otherwise, say N.
493 bool "SGI IOC3 Ethernet"
494 depends on PCI && SGI_IP27
498 If you have a network (Ethernet) card of this type, say Y and read
499 the Ethernet-HOWTO, available from
500 <http://www.tldp.org/docs.html#howto>.
503 tristate "MIPS simulator Network device"
506 The MIPSNET device is a simple Ethernet network device which is
507 emulated by the MIPS Simulator.
508 If you are not using a MIPSsim or are unsure, say N.
510 config SGI_O2MACE_ETH
511 tristate "SGI O2 MACE Fast Ethernet support"
512 depends on SGI_IP32=y
515 tristate "National DP83902AV support"
519 Support for cards based on the National Semiconductor DP83902AV
520 ST-NIC Serial Network Interface Controller for Twisted Pair. This
521 is a 10Mbit/sec Ethernet controller. Product overview and specs at
522 <http://www.national.com/pf/DP/DP83902A.html>.
527 tristate "Renesas SuperH Ethernet support"
528 depends on SUPERH && \
529 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
536 Renesas SuperH Ethernet device driver.
537 This driver support SH7710, SH7712, SH7763 and SH7619.
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 on-chip MAC support"
842 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
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 MIPS || 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 "OpenCores 10/100 Mbps Ethernet MAC support"
977 depends on NET_ETHERNET && HAS_IOMEM
983 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
986 tristate "SMSC LAN911[5678] support"
989 depends on ARM || SUPERH
991 This is a driver for SMSC's LAN911x series of Ethernet chipsets
992 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
993 Say Y if you want it compiled into the kernel,
994 and read the Ethernet-HOWTO, available from
995 <http://www.linuxdoc.org/docs.html#howto>.
997 This driver is also available as a module. The module will be
998 called smc911x. If you want to compile it as a module, say M
999 here and read <file:Documentation/kbuild/modules.txt>
1002 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1003 depends on ARM || SUPERH
1008 Say Y here if you want support for SMSC LAN911x and LAN921x families
1009 of ethernet controllers.
1011 To compile this driver as a module, choose M here and read
1012 <file:Documentation/networking/net-modules.txt>. The module
1013 will be called smsc911x.
1015 config NET_VENDOR_RACAL
1016 bool "Racal-Interlan (Micom) NI cards"
1019 If you have a network (Ethernet) card belonging to this class, such
1020 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1021 available from <http://www.tldp.org/docs.html#howto>.
1023 Note that the answer to this question doesn't directly affect the
1024 kernel: saying N will just cause the configurator to skip all
1025 the questions about NI cards. If you say Y, you will be asked for
1026 your specific card in the following questions.
1029 tristate "NI5010 support (EXPERIMENTAL)"
1030 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1032 If you have a network (Ethernet) card of this type, say Y and read
1033 the Ethernet-HOWTO, available from
1034 <http://www.tldp.org/docs.html#howto>. Note that this is still
1037 To compile this driver as a module, choose M here. The module
1038 will be called ni5010.
1041 tristate "NI5210 support"
1042 depends on NET_VENDOR_RACAL && ISA
1044 If you have a network (Ethernet) card of this type, say Y and read
1045 the Ethernet-HOWTO, available from
1046 <http://www.tldp.org/docs.html#howto>.
1048 To compile this driver as a module, choose M here. The module
1049 will be called ni52.
1052 tristate "NI6510 support"
1053 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1055 If you have a network (Ethernet) card of this type, say Y and read
1056 the Ethernet-HOWTO, available from
1057 <http://www.tldp.org/docs.html#howto>.
1059 To compile this driver as a module, choose M here. The module
1060 will be called ni65.
1063 tristate "Dave ethernet support (DNET)"
1064 depends on NET_ETHERNET && HAS_IOMEM
1067 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1068 Say Y to include support for the DNET chip.
1070 To compile this driver as a module, choose M here: the module
1071 will be called dnet.
1073 source "drivers/net/tulip/Kconfig"
1076 tristate "AT1700/1720 support (EXPERIMENTAL)"
1077 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1080 If you have a network (Ethernet) card of this type, say Y and read
1081 the Ethernet-HOWTO, available from
1082 <http://www.tldp.org/docs.html#howto>.
1084 To compile this driver as a module, choose M here. The module
1085 will be called at1700.
1088 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1089 depends on ISA || EISA || MCA
1092 If you have a network (Ethernet) card of this type, say Y and read
1093 the Ethernet-HOWTO, available from
1094 <http://www.tldp.org/docs.html#howto> as well as
1095 <file:drivers/net/depca.c>.
1097 To compile this driver as a module, choose M here. The module
1098 will be called depca.
1101 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1102 depends on ISA || EISA || PCI
1104 If you have a network (Ethernet) card of this type, say Y and read
1105 the Ethernet-HOWTO, available from
1106 <http://www.tldp.org/docs.html#howto>.
1108 To compile this driver as a module, choose M here. The module
1109 will be called hp100.
1112 bool "Other ISA cards"
1115 If your network (Ethernet) card hasn't been mentioned yet and its
1116 bus system (that's the way the cards talks to the other components
1117 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1118 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1119 available from <http://www.tldp.org/docs.html#howto>.
1123 Note that the answer to this question doesn't directly affect the
1124 kernel: saying N will just cause the configurator to skip all
1125 the remaining ISA network card questions. If you say Y, you will be
1126 asked for your specific card in the following questions.
1129 tristate "Cabletron E21xx support"
1133 If you have a network (Ethernet) card of this type, say Y and read
1134 the Ethernet-HOWTO, available from
1135 <http://www.tldp.org/docs.html#howto>.
1137 To compile this driver as a module, choose M here. The module
1138 will be called e2100.
1141 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1145 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1146 cards. If this is for you, say Y and read
1147 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1148 well as the Ethernet-HOWTO, available from
1149 <http://www.tldp.org/docs.html#howto>.
1151 To compile this driver as a module, choose M here. The module
1152 will be called ewrk3.
1155 tristate "EtherExpress 16 support"
1158 If you have an EtherExpress16 network (Ethernet) card, say Y and
1159 read the Ethernet-HOWTO, available from
1160 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1161 EtherExpress16 card used to be regarded as a very poor choice
1162 because the driver was very unreliable. We now have a new driver
1163 that should do better.
1165 To compile this driver as a module, choose M here. The module
1166 will be called eexpress.
1169 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1172 If you have a network (Ethernet) card of this type, say Y. This
1173 driver supports Intel i82595{FX,TX} based boards. Note however
1174 that the EtherExpress PRO/100 Ethernet card has its own separate
1175 driver. Please read the Ethernet-HOWTO, available from
1176 <http://www.tldp.org/docs.html#howto>.
1178 To compile this driver as a module, choose M here. The module
1179 will be called eepro.
1182 tristate "HP PCLAN+ (27247B and 27252A) support"
1186 If you have a network (Ethernet) card of this type, say Y and read
1187 the Ethernet-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>.
1190 To compile this driver as a module, choose M here. The module
1191 will be called hp-plus.
1194 tristate "HP PCLAN (27245 and other 27xxx series) support"
1198 If you have a network (Ethernet) card of this type, say Y and read
1199 the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here. The module
1206 tristate "LP486E on board Ethernet"
1209 Say Y here to support the 82596-based on-board Ethernet controller
1210 for the Panther motherboard, which is one of the two shipped in the
1211 Intel Professional Workstation.
1214 tristate "ICL EtherTeam 16i/32 support"
1217 If you have a network (Ethernet) card of this type, say Y and read
1218 the Ethernet-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here. The module
1222 will be called eth16i.
1225 tristate "NE2000/NE1000 support"
1226 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1229 If you have a network (Ethernet) card of this type, say Y and read
1230 the Ethernet-HOWTO, available from
1231 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1232 without a specific driver are compatible with NE2000.
1234 If you have a PCI NE2000 card however, say N here and Y to "PCI
1235 NE2000 and clone support" under "EISA, VLB, PCI and on board
1236 controllers" below. If you have a NE2000 card and are running on
1237 an MCA system (a bus system used on some IBM PS/2 computers and
1238 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1241 To compile this driver as a module, choose M here. The module
1245 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1246 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1248 The Zenith Z-Note notebook computer has a built-in network
1249 (Ethernet) card, and this is the Linux driver for it. Note that the
1250 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1251 by this driver. Read the Ethernet-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>.
1255 tristate "SEEQ8005 support (EXPERIMENTAL)"
1256 depends on NET_ISA && EXPERIMENTAL
1258 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1259 is for you, read the Ethernet-HOWTO, available from
1260 <http://www.tldp.org/docs.html#howto>.
1262 To compile this driver as a module, choose M here. The module
1263 will be called seeq8005.
1266 tristate "NE/2 (ne2000 MCA version) support"
1267 depends on MCA_LEGACY
1270 If you have a network (Ethernet) card of this type, say Y and read
1271 the Ethernet-HOWTO, available from
1272 <http://www.tldp.org/docs.html#howto>.
1274 To compile this driver as a module, choose M here. The module
1278 tristate "IBM LAN Adapter/A support"
1281 This is a Micro Channel Ethernet adapter. You need to set
1282 CONFIG_MCA to use this driver. It is both available as an in-kernel
1283 driver and as a module.
1285 To compile this driver as a module, choose M here. The only
1286 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1287 will both support 16K and 32K memory windows, however a 32K window
1288 gives a better security against packet losses. Usage of multiple
1289 boards with this driver should be possible, but has not been tested
1290 up to now due to lack of hardware.
1293 tristate "IBM LAN Virtual Ethernet support"
1294 depends on PPC_PSERIES
1296 This driver supports virtual ethernet adapters on newer IBM iSeries
1297 and pSeries systems.
1299 To compile this driver as a module, choose M here. The module will
1302 source "drivers/net/ibm_newemac/Kconfig"
1305 bool "EISA, VLB, PCI and on board controllers"
1306 depends on ISA || EISA || PCI
1308 This is another class of network cards which attach directly to the
1309 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1310 available from <http://www.tldp.org/docs.html#howto>.
1312 Note that the answer to this question doesn't directly affect the
1313 kernel: saying N will just cause the configurator to skip all
1314 the questions about this class of network cards. If you say Y, you
1315 will be asked for your specific card in the following questions. If
1316 you are unsure, say Y.
1319 tristate "AMD PCnet32 PCI support"
1320 depends on NET_PCI && PCI
1324 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1325 answer Y here and read the Ethernet-HOWTO, available from
1326 <http://www.tldp.org/docs.html#howto>.
1328 To compile this driver as a module, choose M here. The module
1329 will be called pcnet32.
1332 tristate "AMD 8111 (new PCI lance) support"
1333 depends on NET_PCI && PCI
1337 If you have an AMD 8111-based PCI lance ethernet card,
1338 answer Y here and read the Ethernet-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here. The module
1342 will be called amd8111e.
1344 config ADAPTEC_STARFIRE
1345 tristate "Adaptec Starfire/DuraLAN support"
1346 depends on NET_PCI && PCI
1350 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1351 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1352 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1355 To compile this driver as a module, choose M here: the module
1356 will be called starfire. This is recommended.
1359 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1360 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1363 If you have a network (Ethernet) card of this type, say Y and read
1364 the Ethernet-HOWTO, available from
1365 <http://www.tldp.org/docs.html#howto>.
1367 To compile this driver as a module, choose M here. The module
1368 will be called ac3200.
1371 tristate "Apricot Xen-II on board Ethernet"
1372 depends on NET_PCI && ISA
1374 If you have a network (Ethernet) controller of this type, say Y and
1375 read the Ethernet-HOWTO, available from
1376 <http://www.tldp.org/docs.html#howto>.
1378 To compile this driver as a module, choose M here. The module
1379 will be called apricot.
1382 tristate "Broadcom 440x/47xx ethernet support"
1383 depends on SSB_POSSIBLE && HAS_DMA
1387 If you have a network (Ethernet) controller of this type, say Y
1388 or M and read the Ethernet-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>.
1391 To compile this driver as a module, choose M here. The module
1394 # Auto-select SSB PCI-HOST support, if possible
1395 config B44_PCI_AUTOSELECT
1397 depends on B44 && SSB_PCIHOST_POSSIBLE
1401 # Auto-select SSB PCICORE driver, if possible
1402 config B44_PCICORE_AUTOSELECT
1404 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1405 select SSB_DRIVER_PCICORE
1410 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1414 tristate "nForce Ethernet support"
1415 depends on NET_PCI && PCI
1417 If you have a network (Ethernet) controller of this type, say Y and
1418 read the Ethernet-HOWTO, available from
1419 <http://www.tldp.org/docs.html#howto>.
1421 To compile this driver as a module, choose M here. The module
1422 will be called forcedeth.
1424 config FORCEDETH_NAPI
1425 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1426 depends on FORCEDETH && EXPERIMENTAL
1428 NAPI is a new driver API designed to reduce CPU and interrupt load
1429 when the driver is receiving lots of packets from the card. It is
1430 still somewhat experimental and thus not yet enabled by default.
1432 If your estimated Rx load is 10kpps or more, or if the card will be
1433 deployed on potentially unfriendly networks (e.g. in a firewall),
1439 tristate "CS89x0 support"
1440 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1441 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1443 Support for CS89x0 chipset based Ethernet cards. If you have a
1444 network (Ethernet) card of this type, say Y and read the
1445 Ethernet-HOWTO, available from
1446 <http://www.tldp.org/docs.html#howto> as well as
1447 <file:Documentation/networking/cs89x0.txt>.
1449 To compile this driver as a module, choose M here. The module
1450 will be called cs89x0.
1452 config CS89x0_NONISA_IRQ
1454 depends on CS89x0 != n
1455 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1458 tristate "TOSHIBA TC35815 Ethernet support"
1459 depends on NET_PCI && PCI && MIPS
1463 tristate "Intel(R) PRO/100+ support"
1464 depends on NET_PCI && PCI
1467 This driver supports Intel(R) PRO/100 family of adapters.
1468 To verify that your adapter is supported, find the board ID number
1469 on the adapter. Look for a label that has a barcode and a number
1470 in the format 123456-001 (six digits hyphen three digits).
1472 Use the above information and the Adapter & Driver ID Guide at:
1474 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1476 to identify the adapter.
1478 For the latest Intel PRO/100 network driver for Linux, see:
1480 <http://appsr.intel.com/scripts-df/support_intel.asp>
1482 More specific information on configuring the driver is in
1483 <file:Documentation/networking/e100.txt>.
1485 To compile this driver as a module, choose M here. The module
1486 will be called e100.
1489 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1490 depends on NET_PCI && EISA && EXPERIMENTAL
1493 If you have a network (Ethernet) card of this type, say Y and read
1494 the Ethernet-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>.
1497 To compile this driver as a module, choose M here. The module
1498 will be called lne390.
1501 tristate "Myson MTD-8xx PCI Ethernet support"
1502 depends on NET_PCI && PCI
1506 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1507 cards. Specifications and data at
1508 <http://www.myson.com.hk/mtd/datasheet/>.
1511 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1512 depends on NET_PCI && PCI
1515 This driver is for the National Semiconductor DP83810 series,
1516 which is used in cards from PureData, NetGear, Linksys
1517 and others, including the 83815 chip.
1518 More specific information and updates are available from
1519 <http://www.scyld.com/network/natsemi.html>.
1522 tristate "PCI NE2000 and clones support (see help)"
1523 depends on NET_PCI && PCI
1526 This driver is for NE2000 compatible PCI cards. It will not work
1527 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1528 support" below). If you have a PCI NE2000 network (Ethernet) card,
1529 say Y and read the Ethernet-HOWTO, available from
1530 <http://www.tldp.org/docs.html#howto>.
1532 This driver also works for the following NE2000 clone cards:
1533 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1534 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1535 Holtek HT80232 Holtek HT80229
1537 To compile this driver as a module, choose M here. The module
1538 will be called ne2k-pci.
1541 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1542 depends on NET_PCI && EISA && EXPERIMENTAL
1545 If you have a network (Ethernet) card of this type, say Y and read
1546 the Ethernet-HOWTO, available from
1547 <http://www.tldp.org/docs.html#howto>. Note that this driver
1548 will NOT WORK for NE3200 cards as they are completely different.
1550 To compile this driver as a module, choose M here. The module
1551 will be called ne3210.
1554 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1555 depends on NET_PCI && EISA && EXPERIMENTAL
1558 If you have a network (Ethernet) card of this type, 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 es3210.
1566 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1567 depends on NET_PCI && PCI && EXPERIMENTAL
1571 This is a driver for the Fast Ethernet PCI network cards based on
1572 the RTL8139C+ chips. If you have one of those, say Y and read
1573 the Ethernet-HOWTO, available from
1574 <http://www.tldp.org/docs.html#howto>.
1576 To compile this driver as a module, choose M here: the module
1577 will be called 8139cp. This is recommended.
1580 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1581 depends on NET_PCI && PCI
1585 This is a driver for the Fast Ethernet PCI network cards based on
1586 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1587 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1589 To compile this driver as a module, choose M here: the module
1590 will be called 8139too. This is recommended.
1593 bool "Use PIO instead of MMIO"
1597 This instructs the driver to use programmed I/O ports (PIO) instead
1598 of PCI shared memory (MMIO). This can possibly solve some problems
1599 in case your mainboard has memory consistency issues. If unsure,
1602 config 8139TOO_TUNE_TWISTER
1603 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1606 This implements a function which might come in handy in case you
1607 are using low quality on long cabling. It is required for RealTek
1608 RTL-8139 revision K boards, and totally unused otherwise. It tries
1609 to match the transceiver to the cable characteristics. This is
1610 experimental since hardly documented by the manufacturer.
1614 bool "Support for older RTL-8129/8130 boards"
1617 This enables support for the older and uncommon RTL-8129 and
1618 RTL-8130 chips, which support MII via an external transceiver,
1619 instead of an internal one. Disabling this option will save some
1620 memory by making the code size smaller. If unsure, say Y.
1622 config 8139_OLD_RX_RESET
1623 bool "Use older RX-reset method"
1626 The 8139too driver was recently updated to contain a more rapid
1627 reset sequence, in the face of severe receive errors. This "new"
1628 RX-reset method should be adequate for all boards. But if you
1629 experience problems, you can enable this option to restore the
1630 old RX-reset behavior. If unsure, say N.
1633 tristate "RDC R6040 Fast Ethernet Adapter support"
1634 depends on NET_PCI && PCI
1638 This is a driver for the R6040 Fast Ethernet MACs found in the
1639 the RDC R-321x System-on-chips.
1641 To compile this driver as a module, choose M here: the module
1642 will be called r6040. This is recommended.
1645 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1646 depends on NET_PCI && PCI
1650 This is a driver for the Fast Ethernet PCI network cards based on
1651 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1652 SiS 630 and SiS 540 chipsets.
1654 This driver also supports AMD 79C901 HomePNA so that you can use
1655 your phone line as a network cable.
1657 To compile this driver as a module, choose M here: the module
1658 will be called sis900. This is recommended.
1661 tristate "SMC EtherPower II"
1662 depends on NET_PCI && PCI
1666 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1667 which is based on the SMC83c17x (EPIC/100).
1668 More specific information and updates are available from
1669 <http://www.scyld.com/network/epic100.html>.
1672 tristate "SMSC LAN9420 PCI ethernet adapter support"
1673 depends on NET_PCI && PCI
1678 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1679 Say Y if you want it compiled into the kernel,
1680 and read the Ethernet-HOWTO, available from
1681 <http://www.linuxdoc.org/docs.html#howto>.
1683 This driver is also available as a module. The module will be
1684 called smsc9420. If you want to compile it as a module, say M
1685 here and read <file:Documentation/kbuild/modules.txt>
1688 tristate "Sundance Alta support"
1689 depends on NET_PCI && PCI
1693 This driver is for the Sundance "Alta" chip.
1694 More specific information and updates are available from
1695 <http://www.scyld.com/network/sundance.html>.
1697 config SUNDANCE_MMIO
1698 bool "Use MMIO instead of PIO"
1701 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1702 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1703 is known to solve bugs on certain chips.
1708 tristate "TI ThunderLAN support"
1709 depends on NET_PCI && (PCI || EISA)
1711 If you have a PCI Ethernet network card based on the ThunderLAN chip
1712 which is supported by this driver, say Y and read the
1713 Ethernet-HOWTO, available from
1714 <http://www.tldp.org/docs.html#howto>.
1716 Devices currently supported by this driver are Compaq Netelligent,
1717 Compaq NetFlex and Olicom cards. Please read the file
1718 <file:Documentation/networking/tlan.txt> for more details.
1720 To compile this driver as a module, choose M here. The module
1721 will be called tlan.
1723 Please email feedback to <torben.mathiasen@compaq.com>.
1726 tristate "VIA Rhine support"
1727 depends on NET_PCI && PCI
1731 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1732 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1733 Ethernet functions can also be found integrated on South Bridges
1736 To compile this driver as a module, choose M here. The module
1737 will be called via-rhine.
1739 config VIA_RHINE_MMIO
1740 bool "Use MMIO instead of PIO"
1741 depends on VIA_RHINE
1743 This instructs the driver to use PCI shared memory (MMIO) instead of
1744 programmed I/O ports (PIO). Enabling this gives an improvement in
1745 processing time in parts of the driver.
1750 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1751 depends on NET_PCI && PCI && EXPERIMENTAL
1754 This is a driver for the Fast Ethernet PCI network cards based on
1755 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1756 have one of these, say Y here.
1758 To compile this driver as a module, choose M here: the module
1759 will be called sc92031. This is recommended.
1762 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1763 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1766 TI AR7 CPMAC Ethernet support
1769 bool "Pocket and portable adapters"
1772 Cute little network (Ethernet) devices which attach to the parallel
1773 port ("pocket adapters"), commonly used with laptops. If you have
1774 one of those, say Y and read the Ethernet-HOWTO, available from
1775 <http://www.tldp.org/docs.html#howto>.
1777 If you want to plug a network (or some other) card into the PCMCIA
1778 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1779 credit card size extension cards used by all modern laptops), you
1780 need the pcmcia-cs package (location contained in the file
1781 <file:Documentation/Changes>) and you can say N here.
1783 Laptop users should read the Linux Laptop home page at
1784 <http://www.linux-on-laptops.com/> or
1785 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1787 Note that the answer to this question doesn't directly affect the
1788 kernel: saying N will just cause the configurator to skip all
1789 the questions about this class of network devices. If you say Y, you
1790 will be asked for your specific device in the following questions.
1793 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1794 depends on NET_POCKET && PARPORT && X86
1797 This is a network (Ethernet) device which attaches to your parallel
1798 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1799 available from <http://www.tldp.org/docs.html#howto>, if you
1800 want to use this. If you intend to use this driver, you should have
1801 said N to the "Parallel printer support", because the two drivers
1802 don't like each other.
1804 To compile this driver as a module, choose M here: the module
1808 tristate "D-Link DE600 pocket adapter support"
1809 depends on NET_POCKET && PARPORT
1811 This is a network (Ethernet) device which attaches to your parallel
1812 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1813 Ethernet-HOWTO, available from
1814 <http://www.tldp.org/docs.html#howto>, if you want to use
1815 this. It is possible to have several devices share a single parallel
1816 port and it is safe to compile the corresponding drivers into the
1819 To compile this driver as a module, choose M here: the module
1820 will be called de600.
1823 tristate "D-Link DE620 pocket adapter support"
1824 depends on NET_POCKET && PARPORT
1826 This is a network (Ethernet) device which attaches to your parallel
1827 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1828 Ethernet-HOWTO, available from
1829 <http://www.tldp.org/docs.html#howto>, if you want to use
1830 this. It is possible to have several devices share a single parallel
1831 port and it is safe to compile the corresponding drivers into the
1834 To compile this driver as a module, choose M here: the module
1835 will be called de620.
1838 tristate "SGI Seeq ethernet controller support"
1839 depends on SGI_HAS_SEEQ
1841 Say Y here if you have an Seeq based Ethernet network card. This is
1842 used in many Silicon Graphics machines.
1845 tristate "DEC LANCE ethernet controller support"
1846 depends on MACH_DECSTATION
1849 This driver is for the series of Ethernet controllers produced by
1850 DEC (now Compaq) based on the AMD Lance chipset, including the
1851 DEPCA series. (This chipset is better known via the NE2100 cards.)
1854 bool "Motorola 68360 ethernet controller"
1857 Say Y here if you want to use the built-in ethernet controller of
1858 the Motorola 68360 processor.
1861 bool "FEC ethernet controller (of ColdFire CPUs)"
1862 depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27
1864 Say Y here if you want to use the built-in 10/100 Fast ethernet
1865 controller on some Motorola ColdFire and Freescale i.MX processors.
1868 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1871 Say Y here if you want to use the second built-in 10/100 Fast
1872 ethernet controller on some Motorola ColdFire processors.
1875 tristate "MPC52xx FEC driver"
1876 depends on PPC_MPC52xx && PPC_BESTCOMM
1879 select PPC_BESTCOMM_FEC
1881 This option enables support for the MPC5200's on-chip
1882 Fast Ethernet Controller
1883 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1885 config FEC_MPC52xx_MDIO
1886 bool "MPC52xx FEC MDIO bus driver"
1887 depends on FEC_MPC52xx
1890 The MPC5200's FEC can connect to the Ethernet either with
1891 an external MII PHY chip or 10 Mbps 7-wire interface
1892 (Motorola? industry standard).
1893 If your board uses an external PHY connected to FEC, enable this.
1894 If not sure, enable.
1895 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1898 tristate "NE2000 compatible support for H8/300"
1901 Say Y here if you want to use the NE2000 compatible
1902 controller on the Renesas H8/300 processor.
1905 tristate "Atheros L2 Fast Ethernet support"
1910 This driver supports the Atheros L2 fast ethernet adapter.
1912 To compile this driver as a module, choose M here. The module
1913 will be called atl2.
1915 source "drivers/net/fs_enet/Kconfig"
1917 endif # NET_ETHERNET
1923 menuconfig NETDEV_1000
1924 bool "Ethernet (1000 Mbit)"
1928 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1929 type of Local Area Network (LAN) in universities and companies.
1931 Say Y here to get to see options for Gigabit Ethernet drivers.
1932 This option alone does not add any kernel code.
1933 Note that drivers supporting both 100 and 1000 MBit may be listed
1934 under "Ethernet (10 or 100MBit)" instead.
1936 If you say N, all options in this submenu will be skipped and disabled.
1941 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1944 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1945 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1946 adapter. The driver allows for using the Jumbo Frame option (9000
1947 bytes/frame) however it requires that your switches can handle this
1948 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1951 To compile this driver as a module, choose M here: the
1952 module will be called acenic.
1954 config ACENIC_OMIT_TIGON_I
1955 bool "Omit support for old Tigon I based AceNICs"
1958 Say Y here if you only have Tigon II based AceNICs and want to leave
1959 out support for the older Tigon I based cards which are no longer
1960 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1961 version)). This will reduce the size of the driver object by
1962 app. 100KB. If you are not sure whether your card is a Tigon I or a
1963 Tigon II, say N here.
1965 The safe and default value for this is N.
1968 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1972 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1974 D-Link DGE-550T Gigabit Ethernet Adapter.
1975 D-Link DL2000-based Gigabit Ethernet Adapter.
1976 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1978 To compile this driver as a module, choose M here: the
1979 module will be called dl2k.
1982 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1985 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1986 adapters. For more information on how to identify your adapter, go
1987 to the Adapter & Driver ID Guide at:
1989 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1991 For general information and support, go to the Intel support
1994 <http://support.intel.com>
1996 More specific information on configuring the driver is in
1997 <file:Documentation/networking/e1000.txt>.
1999 To compile this driver as a module, choose M here. The module
2000 will be called e1000.
2003 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2004 depends on PCI && (!SPARC32 || BROKEN)
2006 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2007 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2008 use the regular e1000 driver For more information on how to
2009 identify your adapter, go to the Adapter & Driver ID Guide at:
2011 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2013 For general information and support, go to the Intel support
2016 <http://support.intel.com>
2018 To compile this driver as a module, choose M here. The module
2019 will be called e1000e.
2022 tristate "IP1000 Gigabit Ethernet support"
2023 depends on PCI && EXPERIMENTAL
2026 This driver supports IP1000 gigabit Ethernet cards.
2028 To compile this driver as a module, choose M here: the module
2029 will be called ipg. This is recommended.
2032 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2035 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2036 adapters. For more information on how to identify your adapter, go
2037 to the Adapter & Driver ID Guide at:
2039 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2041 For general information and support, go to the Intel support
2044 <http://support.intel.com>
2046 More specific information on configuring the driver is in
2047 <file:Documentation/networking/e1000.txt>.
2049 To compile this driver as a module, choose M here. The module
2053 bool "Direct Cache Access (DCA) Support"
2055 depends on IGB && DCA && !(IGB=y && DCA=m)
2057 Say Y here if you want to use Direct Cache Access (DCA) in the
2058 driver. DCA is a method for warming the CPU cache before data
2059 is used, with the intent of lessening the impact of cache misses.
2061 source "drivers/net/ixp2000/Kconfig"
2064 tristate "MyriCOM Gigabit Ethernet support"
2067 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2069 To compile this driver as a module, choose M here: the module
2070 will be called myri_sbus. This is recommended.
2073 tristate "National Semiconductor DP83820 support"
2076 This is a driver for the National Semiconductor DP83820 series
2077 of gigabit ethernet MACs. Cards using this chipset include
2078 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2079 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2083 tristate "Packet Engines Hamachi GNIC-II support"
2087 If you have a Gigabit Ethernet card of this type, say Y and read
2088 the Ethernet-HOWTO, available from
2089 <http://www.tldp.org/docs.html#howto>.
2091 To compile this driver as a module, choose M here. The module will be
2095 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2096 depends on PCI && EXPERIMENTAL
2099 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2100 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2101 used by the Beowulf Linux cluster project. See
2102 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2103 information about this driver in particular and Beowulf in general.
2105 To compile this driver as a module, choose M here: the module
2106 will be called yellowfin. This is recommended.
2109 tristate "Realtek 8169 gigabit ethernet support"
2114 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2116 To compile this driver as a module, choose M here: the module
2117 will be called r8169. This is recommended.
2121 depends on R8169 && VLAN_8021Q
2123 Say Y here for the r8169 driver to support the functions required
2124 by the kernel 802.1Q code.
2129 tristate "SB1250 Gigabit Ethernet support"
2130 depends on SIBYTE_SB1xxx_SOC
2133 This driver supports Gigabit Ethernet interfaces based on the
2134 Broadcom SiByte family of System-On-a-Chip parts. They include
2135 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2138 To compile this driver as a module, choose M here: the module
2139 will be called sb1250-mac.
2142 tristate "SiS190/SiS191 gigabit ethernet support"
2147 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2148 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2149 appear in lan on motherboard designs which are based on SiS 965
2150 and SiS 966 south bridge.
2152 To compile this driver as a module, choose M here: the module
2153 will be called sis190. This is recommended.
2156 tristate "New SysKonnect GigaEthernet support"
2160 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2161 and related Gigabit Ethernet adapters. It is a new smaller driver
2162 with better performance and more complete ethtool support.
2164 It does not support the link failover and network management
2165 features that "portable" vendor supplied sk98lin driver does.
2167 This driver supports adapters based on the original Yukon chipset:
2168 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2169 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2171 It does not support the newer Yukon2 chipset: a separate driver,
2172 sky2, is provided for Yukon2-based adapters.
2174 To compile this driver as a module, choose M here: the module
2175 will be called skge. This is recommended.
2178 bool "Debugging interface"
2179 depends on SKGE && DEBUG_FS
2181 This option adds the ability to dump driver state for debugging.
2182 The file debugfs/skge/ethX displays the state of the internal
2183 transmit and receive rings.
2188 tristate "SysKonnect Yukon2 support"
2192 This driver supports Gigabit Ethernet adapters based on the
2193 Marvell Yukon 2 chipset:
2194 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2195 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2197 There is companion driver for the older Marvell Yukon and
2198 Genesis based adapters: skge.
2200 To compile this driver as a module, choose M here: the module
2201 will be called sky2. This is recommended.
2204 bool "Debugging interface"
2205 depends on SKY2 && DEBUG_FS
2207 This option adds the ability to dump driver state for debugging.
2208 The file debugfs/sky2/ethX displays the state of the internal
2209 transmit and receive rings.
2214 tristate "VIA Velocity support"
2220 If you have a VIA "Velocity" based network card say Y here.
2222 To compile this driver as a module, choose M here. The module
2223 will be called via-velocity.
2226 tristate "Broadcom Tigon3 support"
2230 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2232 To compile this driver as a module, choose M here: the module
2233 will be called tg3. This is recommended.
2236 tristate "Broadcom NetXtremeII support"
2241 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2243 To compile this driver as a module, choose M here: the module
2244 will be called bnx2. This is recommended.
2247 tristate "Spider Gigabit Ethernet driver"
2248 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2251 This driver supports the Gigabit Ethernet chips present on the
2252 Cell Processor-Based Blades from IBM.
2255 tristate "Tundra TSI108 gigabit Ethernet support"
2256 depends on TSI108_BRIDGE
2258 This driver supports Tundra TSI108 gigabit Ethernet ports.
2259 To compile this driver as a module, choose M here: the module
2260 will be called tsi108_eth.
2263 tristate "PS3 Gigabit Ethernet driver"
2265 select PS3_SYS_MANAGER
2267 This driver supports the network device on the PS3 game
2268 console. This driver has built-in support for Ethernet.
2270 To compile this driver as a module, choose M here: the
2271 module will be called ps3_gelic.
2273 config GELIC_WIRELESS
2274 bool "PS3 Wireless support"
2275 depends on GELIC_NET
2278 This option adds the support for the wireless feature of PS3.
2279 If you have the wireless-less model of PS3 or have no plan to
2280 use wireless feature, disabling this option saves memory. As
2281 the driver automatically distinguishes the models, you can
2282 safely enable this option even if you have a wireless-less model.
2284 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2285 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2286 depends on GELIC_WIRELESS
2288 This option retains the obsolete private interface to pass
2289 the PSK from user space programs to the driver. The PSK
2290 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2291 (WPA-Personal) environment.
2292 If WPA[2]-PSK is used and you need to use old programs that
2293 support only this old interface, say Y. Otherwise N.
2298 tristate "Freescale PQ MDIO"
2302 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2305 tristate "Gianfar Ethernet"
2311 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2312 and MPC86xx family of chips, and the FEC on the 8540.
2315 tristate "Freescale QE Gigabit Ethernet"
2316 depends on QUICC_ENGINE
2320 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2321 which is available on some Freescale SOCs.
2323 config UGETH_MAGIC_PACKET
2324 bool "Magic Packet detection support"
2327 config UGETH_TX_ON_DEMAND
2328 bool "Transmit on Demand support"
2332 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2333 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2337 This driver supports the gigabit ethernet MACs in the
2338 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2339 in the Marvell Orion ARM SoC family.
2341 Some boards that use the Discovery chipset are the Momenco
2342 Ocelot C and Jaguar ATX and Pegasos II.
2345 tristate "QLogic QLA3XXX Network Driver Support"
2348 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2350 To compile this driver as a module, choose M here: the module
2351 will be called qla3xxx.
2354 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2359 This driver supports the Atheros/Attansic L1 gigabit ethernet
2362 To compile this driver as a module, choose M here. The module
2363 will be called atl1.
2366 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2367 depends on PCI && EXPERIMENTAL
2371 This driver supports the Atheros L1E gigabit ethernet adapter.
2373 To compile this driver as a module, choose M here. The module
2374 will be called atl1e.
2377 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2378 depends on PCI && EXPERIMENTAL
2382 This driver supports the Atheros L1C gigabit ethernet adapter.
2384 To compile this driver as a module, choose M here. The module
2385 will be called atl1c.
2388 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2393 This driver supports the PCI-Express gigabit ethernet adapters
2394 based on JMicron JMC250 chipset.
2396 To compile this driver as a module, choose M here. The module
2402 # 10 Gigabit Ethernet
2405 menuconfig NETDEV_10000
2406 bool "Ethernet (10000 Mbit)"
2410 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2411 This option alone does not add any kernel code.
2413 If you say N, all options in this submenu will be skipped and disabled.
2418 tristate "Chelsio 10Gb Ethernet support"
2422 This driver supports Chelsio gigabit and 10-gigabit
2423 Ethernet cards. More information about adapter features and
2424 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2426 For general information about Chelsio and our products, visit
2427 our website at <http://www.chelsio.com>.
2429 For customer support, please visit our customer support page at
2430 <http://www.chelsio.com/support.htm>.
2432 Please send feedback to <linux-bugs@chelsio.com>.
2434 To compile this driver as a module, choose M here: the module
2435 will be called cxgb.
2437 config CHELSIO_T1_1G
2438 bool "Chelsio gigabit Ethernet support"
2439 depends on CHELSIO_T1
2441 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2442 are using only 10G cards say 'N' here.
2444 config CHELSIO_T3_DEPENDS
2446 depends on PCI && INET
2450 tristate "Chelsio Communications T3 10Gb Ethernet support"
2451 depends on CHELSIO_T3_DEPENDS
2454 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2457 For general information about Chelsio and our products, visit
2458 our website at <http://www.chelsio.com>.
2460 For customer support, please visit our customer support page at
2461 <http://www.chelsio.com/support.htm>.
2463 Please send feedback to <linux-bugs@chelsio.com>.
2465 To compile this driver as a module, choose M here: the module
2466 will be called cxgb3.
2469 tristate "eHEA Ethernet support"
2470 depends on IBMEBUS && INET && SPARSEMEM
2473 This driver supports the IBM pSeries eHEA ethernet adapter.
2475 To compile the driver as a module, choose M here. The module
2476 will be called ehea.
2479 tristate "Cisco 10G Ethernet NIC support"
2480 depends on PCI && INET
2483 This enables the support for the Cisco 10G Ethernet card.
2486 tristate "Intel(R) 10GbE PCI Express adapters support"
2487 depends on PCI && INET
2489 This driver supports Intel(R) 10GbE PCI Express family of
2490 adapters. For more information on how to identify your adapter, go
2491 to the Adapter & Driver ID Guide at:
2493 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2495 For general information and support, go to the Intel support
2498 <http://support.intel.com>
2500 To compile this driver as a module, choose M here. The module
2501 will be called ixgbe.
2504 bool "Direct Cache Access (DCA) Support"
2506 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2508 Say Y here if you want to use Direct Cache Access (DCA) in the
2509 driver. DCA is a method for warming the CPU cache before data
2510 is used, with the intent of lessening the impact of cache misses.
2513 bool "Data Center Bridging (DCB) Support"
2515 depends on IXGBE && DCB
2517 Say Y here if you want to use Data Center Bridging (DCB) in the
2523 tristate "Intel(R) PRO/10GbE support"
2526 This driver supports Intel(R) PRO/10GbE family of adapters for
2527 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2528 instead. For more information on how to identify your adapter, go
2529 to the Adapter & Driver ID Guide at:
2531 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2533 For general information and support, go to the Intel support
2536 <http://support.intel.com>
2538 More specific information on configuring the driver is in
2539 <file:Documentation/networking/ixgb.txt>.
2541 To compile this driver as a module, choose M here. The module
2542 will be called ixgb.
2545 tristate "S2IO 10Gbe XFrame NIC"
2548 This driver supports the 10Gbe XFrame NIC of S2IO.
2549 More specific information on configuring the driver is in
2550 <file:Documentation/networking/s2io.txt>.
2553 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2554 depends on PCI && INET
2556 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2557 I/O Virtualized Server Adapter.
2558 More specific information on configuring the driver is in
2559 <file:Documentation/networking/vxge.txt>.
2561 config VXGE_DEBUG_TRACE_ALL
2562 bool "Enabling All Debug trace statments in driver"
2566 Say Y here if you want to enabling all the debug trace statements in
2567 driver. By default only few debug trace statements are enabled.
2570 tristate "Myricom Myri-10G Ethernet support"
2571 depends on PCI && INET
2576 This driver supports Myricom Myri-10G Dual Protocol interface in
2577 Ethernet mode. If the eeprom on your board is not recent enough,
2578 you will need a newer firmware image.
2579 You may get this image or more information, at:
2581 <http://www.myri.com/scs/download-Myri10GE.html>
2583 To compile this driver as a module, choose M here. The module
2584 will be called myri10ge.
2587 bool "Direct Cache Access (DCA) Support"
2589 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2591 Say Y here if you want to use Direct Cache Access (DCA) in the
2592 driver. DCA is a method for warming the CPU cache before data
2593 is used, with the intent of lessening the impact of cache misses.
2596 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2599 This enables the support for NetXen's Gigabit Ethernet card.
2602 tristate "Sun Neptune 10Gbit Ethernet support"
2605 This enables support for cards based upon Sun's
2609 tristate "PA Semi 1/10Gbit MAC"
2610 depends on PPC_PASEMI && PCI
2614 This driver supports the on-chip 1/10Gbit Ethernet controller on
2615 PA Semi's PWRficient line of chips.
2618 tristate "Mellanox Technologies 10Gbit Ethernet support"
2619 depends on PCI && INET
2623 This driver supports Mellanox Technologies ConnectX Ethernet
2632 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2633 depends on MLX4_CORE
2636 This option causes debugging code to be compiled into the
2637 mlx4_core driver. The output can be turned on via the
2638 debug_level module parameter (which can also be set after
2639 the driver is loaded through sysfs).
2642 tristate "Tehuti Networks 10G Ethernet"
2645 Tehuti Networks 10G Ethernet NIC
2648 tristate "Broadcom NetXtremeII 10Gb support"
2653 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2654 To compile this driver as a module, choose M here: the module
2655 will be called bnx2x. This is recommended.
2658 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2661 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2663 To compile this driver as a module, choose M here: the module
2664 will be called qlge.
2666 source "drivers/net/sfc/Kconfig"
2668 source "drivers/net/benet/Kconfig"
2670 endif # NETDEV_10000
2672 source "drivers/net/tokenring/Kconfig"
2674 source "drivers/net/wireless/Kconfig"
2676 source "drivers/net/wimax/Kconfig"
2678 source "drivers/net/usb/Kconfig"
2680 source "drivers/net/pcmcia/Kconfig"
2682 source "drivers/net/wan/Kconfig"
2684 source "drivers/atm/Kconfig"
2686 source "drivers/s390/net/Kconfig"
2688 config XEN_NETDEV_FRONTEND
2689 tristate "Xen network device frontend driver"
2693 The network device frontend driver allows the kernel to
2694 access network devices exported exported by a virtual
2695 machine containing a physical network device driver. The
2696 frontend driver is intended for unprivileged guest domains;
2697 if you are compiling a kernel for a Xen guest, you almost
2698 certainly want to enable this.
2701 tristate "iSeries Virtual Ethernet driver support"
2702 depends on PPC_ISERIES
2705 tristate "RapidIO Ethernet over messaging driver support"
2708 config RIONET_TX_SIZE
2709 int "Number of outbound queue entries"
2713 config RIONET_RX_SIZE
2714 int "Number of inbound queue entries"
2719 tristate "FDDI driver support"
2720 depends on (PCI || EISA || TC)
2722 Fiber Distributed Data Interface is a high speed local area network
2723 design; essentially a replacement for high speed Ethernet. FDDI can
2724 run over copper or fiber. If you are connected to such a network and
2725 want a driver for the FDDI card in your computer, say Y here (and
2726 then also Y to the driver for your FDDI card, below). Most people
2730 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2731 depends on FDDI && (PCI || EISA || TC)
2733 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2734 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2735 to a local FDDI network.
2737 To compile this driver as a module, choose M here: the module
2738 will be called defxx. If unsure, say N.
2742 prompt "Use MMIO instead of PIO" if PCI || EISA
2744 default n if PCI || EISA
2747 This instructs the driver to use EISA or PCI memory-mapped I/O
2748 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2749 Enabling this gives an improvement in processing time in parts
2750 of the driver, but it may cause problems with EISA (DEFEA)
2751 adapters. TURBOchannel does not have the concept of I/O ports,
2752 so MMIO is always used for these (DEFTA) adapters.
2757 tristate "SysKonnect FDDI PCI support"
2758 depends on FDDI && PCI
2761 Say Y here if you have a SysKonnect FDDI PCI adapter.
2762 The following adapters are supported by this driver:
2763 - SK-5521 (SK-NET FDDI-UP)
2764 - SK-5522 (SK-NET FDDI-UP DAS)
2765 - SK-5541 (SK-NET FDDI-FP)
2766 - SK-5543 (SK-NET FDDI-LP)
2767 - SK-5544 (SK-NET FDDI-LP DAS)
2768 - SK-5821 (SK-NET FDDI-UP64)
2769 - SK-5822 (SK-NET FDDI-UP64 DAS)
2770 - SK-5841 (SK-NET FDDI-FP64)
2771 - SK-5843 (SK-NET FDDI-LP64)
2772 - SK-5844 (SK-NET FDDI-LP64 DAS)
2773 - Netelligent 100 FDDI DAS Fibre SC
2774 - Netelligent 100 FDDI SAS Fibre SC
2775 - Netelligent 100 FDDI DAS UTP
2776 - Netelligent 100 FDDI SAS UTP
2777 - Netelligent 100 FDDI SAS Fibre MIC
2779 Read <file:Documentation/networking/skfp.txt> for information about
2782 Questions concerning this driver can be addressed to:
2783 <linux@syskonnect.de>
2785 To compile this driver as a module, choose M here: the module
2786 will be called skfp. This is recommended.
2789 bool "HIPPI driver support (EXPERIMENTAL)"
2790 depends on EXPERIMENTAL && INET && PCI
2792 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2793 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2794 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2795 single-mode). HIPPI networks are commonly used for clusters and to
2796 connect to super computers. If you are connected to a HIPPI network
2797 and have a HIPPI network card in your computer that you want to use
2798 under Linux, say Y here (you must also remember to enable the driver
2799 for your HIPPI card below). Most people will say N here.
2802 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2803 depends on HIPPI && PCI
2805 Say Y here if this is your PCI HIPPI network card.
2807 To compile this driver as a module, choose M here: the module
2808 will be called rrunner. If unsure, say N.
2810 config ROADRUNNER_LARGE_RINGS
2811 bool "Use large TX/RX rings (EXPERIMENTAL)"
2812 depends on ROADRUNNER
2814 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2815 of additional memory to allow for fastest operation, both for
2816 transmitting and receiving. This memory cannot be used by any other
2817 kernel code or by user space programs. Say Y here only if you have
2821 tristate "PLIP (parallel port) support"
2824 PLIP (Parallel Line Internet Protocol) is used to create a
2825 reasonably fast mini network consisting of two (or, rarely, more)
2826 local machines. A PLIP link from a Linux box is a popular means to
2827 install a Linux distribution on a machine which doesn't have a
2828 CD-ROM drive (a minimal system has to be transferred with floppies
2829 first). The kernels on both machines need to have this PLIP option
2830 enabled for this to work.
2832 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2833 ports (the connectors at the computers with 25 holes) are connected
2834 with "null printer" or "Turbo Laplink" cables which can transmit 4
2835 bits at a time (mode 0) or with special PLIP cables, to be used on
2836 bidirectional parallel ports only, which can transmit 8 bits at a
2837 time (mode 1); you can find the wiring of these cables in
2838 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2839 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2840 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2841 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2842 and winsock or NCSA's telnet.
2844 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2845 as the NET-3-HOWTO, both available from
2846 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2847 protocol has been changed and this PLIP driver won't work together
2848 with the PLIP support in Linux versions 1.0.x. This option enlarges
2849 your kernel by about 8 KB.
2851 To compile this driver as a module, choose M here. The module
2852 will be called plip. If unsure, say Y or M, in case you buy
2856 tristate "PPP (point-to-point protocol) support"
2859 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2860 the same purpose: sending Internet traffic over telephone (and other
2861 serial) lines. Ask your access provider if they support it, because
2862 otherwise you can't use it; most Internet access providers these
2863 days support PPP rather than SLIP.
2865 To use PPP, you need an additional program called pppd as described
2866 in the PPP-HOWTO, available at
2867 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2868 the version of pppd recommended in <file:Documentation/Changes>.
2869 The PPP option enlarges your kernel by about 16 KB.
2871 There are actually two versions of PPP: the traditional PPP for
2872 asynchronous lines, such as regular analog phone lines, and
2873 synchronous PPP which can be used over digital ISDN lines for
2874 example. If you want to use PPP over phone lines or other
2875 asynchronous serial lines, you need to say Y (or M) here and also to
2876 the next option, "PPP support for async serial ports". For PPP over
2877 synchronous lines, you should say Y (or M) here and to "Support
2878 synchronous PPP", below.
2880 If you said Y to "Version information on all symbols" above, then
2881 you cannot compile the PPP driver into the kernel; you can then only
2882 compile it as a module. To compile this driver as a module, choose M
2883 here. The module will be called ppp_generic.
2885 config PPP_MULTILINK
2886 bool "PPP multilink support (EXPERIMENTAL)"
2887 depends on PPP && EXPERIMENTAL
2889 PPP multilink is a protocol (defined in RFC 1990) which allows you
2890 to combine several (logical or physical) lines into one logical PPP
2891 connection, so that you can utilize your full bandwidth.
2893 This has to be supported at the other end as well and you need a
2894 version of the pppd daemon which understands the multilink protocol.
2899 bool "PPP filtering"
2902 Say Y here if you want to be able to filter the packets passing over
2903 PPP interfaces. This allows you to control which packets count as
2904 activity (i.e. which packets will reset the idle timer or bring up
2905 a demand-dialed link) and which packets are to be dropped entirely.
2906 You need to say Y here if you wish to use the pass-filter and
2907 active-filter options to pppd.
2912 tristate "PPP support for async serial ports"
2916 Say Y (or M) here if you want to be able to use PPP over standard
2917 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2918 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2921 To compile this driver as a module, choose M here.
2926 tristate "PPP support for sync tty ports"
2929 Say Y (or M) here if you want to be able to use PPP over synchronous
2930 (HDLC) tty devices, such as the SyncLink adapter. These devices
2931 are often used for high-speed leased lines like T1/E1.
2933 To compile this driver as a module, choose M here.
2936 tristate "PPP Deflate compression"
2941 Support for the Deflate compression method for PPP, which uses the
2942 Deflate algorithm (the same algorithm that gzip uses) to compress
2943 each PPP packet before it is sent over the wire. The machine at the
2944 other end of the PPP link (usually your ISP) has to support the
2945 Deflate compression method as well for this to be useful. Even if
2946 they don't support it, it is safe to say Y here.
2948 To compile this driver as a module, choose M here.
2951 tristate "PPP BSD-Compress compression"
2954 Support for the BSD-Compress compression method for PPP, which uses
2955 the LZW compression method to compress each PPP packet before it is
2956 sent over the wire. The machine at the other end of the PPP link
2957 (usually your ISP) has to support the BSD-Compress compression
2958 method as well for this to be useful. Even if they don't support it,
2959 it is safe to say Y here.
2961 The PPP Deflate compression method ("PPP Deflate compression",
2962 above) is preferable to BSD-Compress, because it compresses better
2965 Note that the BSD compression code will always be compiled as a
2966 module; it is called bsd_comp and will show up in the directory
2967 modules once you have said "make modules". If unsure, say N.
2970 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2971 depends on PPP && EXPERIMENTAL
2977 Support for the MPPE Encryption protocol, as employed by the
2978 Microsoft Point-to-Point Tunneling Protocol.
2980 See http://pptpclient.sourceforge.net/ for information on
2981 configuring PPTP clients and servers to utilize this method.
2984 tristate "PPP over Ethernet (EXPERIMENTAL)"
2985 depends on EXPERIMENTAL && PPP
2987 Support for PPP over Ethernet.
2989 This driver requires the latest version of pppd from the CVS
2990 repository at cvs.samba.org. Alternatively, see the
2991 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2992 which contains instruction on how to use this driver (under
2993 the heading "Kernel mode PPPoE").
2996 tristate "PPP over ATM"
2997 depends on ATM && PPP
2999 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3000 This implementation does not yet comply with section 8 of RFC2364,
3001 which can lead to bad results if the ATM peer loses state and
3002 changes its encapsulation unilaterally.
3005 tristate "PPP over L2TP (EXPERIMENTAL)"
3006 depends on EXPERIMENTAL && PPP && INET
3008 Support for PPP-over-L2TP socket family. L2TP is a protocol
3009 used by ISPs and enterprises to tunnel PPP traffic over UDP
3010 tunnels. L2TP is replacing PPTP for VPN uses.
3012 This kernel component handles only L2TP data packets: a
3013 userland daemon handles L2TP the control protocol (tunnel
3014 and session setup). One such daemon is OpenL2TP
3015 (http://openl2tp.sourceforge.net/).
3018 tristate "SLIP (serial line) support"
3020 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3021 connect to your Internet service provider or to connect to some
3022 other local Unix box or if you want to configure your Linux box as a
3023 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3024 Internet Protocol) is a protocol used to send Internet traffic over
3025 serial connections such as telephone lines or null modem cables;
3026 nowadays, the protocol PPP is more commonly used for this same
3029 Normally, your access provider has to support SLIP in order for you
3030 to be able to use it, but there is now a SLIP emulator called SLiRP
3031 around (available from
3032 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3033 allows you to use SLIP over a regular dial up shell connection. If
3034 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3035 NET-3-HOWTO, available from
3036 <http://www.tldp.org/docs.html#howto>, explains how to
3037 configure SLIP. Note that you don't need this option if you just
3038 want to run term (term is a program which gives you almost full
3039 Internet connectivity if you have a regular dial up shell account on
3040 some Internet connected Unix computer. Read
3041 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3042 support will enlarge your kernel by about 4 KB. If unsure, say N.
3044 To compile this driver as a module, choose M here. The module
3045 will be called slip.
3047 config SLIP_COMPRESSED
3048 bool "CSLIP compressed headers"
3052 This protocol is faster than SLIP because it uses compression on the
3053 TCP/IP headers (not on the data itself), but it has to be supported
3054 on both ends. Ask your access provider if you are not sure and
3055 answer Y, just in case. You will still be able to use plain SLIP. If
3056 you plan to use SLiRP, the SLIP emulator (available from
3057 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3058 allows you to use SLIP over a regular dial up shell connection, you
3059 definitely want to say Y here. The NET-3-HOWTO, available from
3060 <http://www.tldp.org/docs.html#howto>, explains how to configure
3061 CSLIP. This won't enlarge your kernel.
3066 This option enables Van Jacobsen serial line header compression
3070 bool "Keepalive and linefill"
3073 Adds additional capabilities to the SLIP driver to support the
3074 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3077 config SLIP_MODE_SLIP6
3078 bool "Six bit SLIP encapsulation"
3081 Just occasionally you may need to run IP over hostile serial
3082 networks that don't pass all control characters or are only seven
3083 bit. Saying Y here adds an extra mode you can use with SLIP:
3084 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3085 the serial device. Naturally, this has to be supported at the other
3086 end of the link as well. It's good enough, for example, to run IP
3087 over the async ports of a Camtec JNT Pad. If unsure, say N.
3090 bool "Fibre Channel driver support"
3091 depends on SCSI && PCI
3093 Fibre Channel is a high speed serial protocol mainly used to connect
3094 large storage devices to the computer; it is compatible with and
3095 intended to replace SCSI.
3097 If you intend to use Fibre Channel, you need to have a Fibre channel
3098 adaptor card in your computer; say Y here and to the driver for your
3099 adaptor below. You also should have said Y to "SCSI support" and
3100 "SCSI generic support".
3103 tristate "Network console logging support (EXPERIMENTAL)"
3104 depends on EXPERIMENTAL
3106 If you want to log kernel messages over the network, enable this.
3107 See <file:Documentation/networking/netconsole.txt> for details.
3109 config NETCONSOLE_DYNAMIC
3110 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3111 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3114 This option enables the ability to dynamically reconfigure target
3115 parameters (interface, IP addresses, port numbers, MAC addresses)
3116 at runtime through a userspace interface exported using configfs.
3117 See <file:Documentation/networking/netconsole.txt> for details.
3123 bool "Netpoll traffic trapping"
3127 config NET_POLL_CONTROLLER
3131 tristate "Virtio network driver (EXPERIMENTAL)"
3132 depends on EXPERIMENTAL && VIRTIO
3134 This is the virtual network driver for virtio. It can be used with
3135 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.