3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
30 tristate "Intermediate Functional Block support"
31 depends on NET_CLS_ACT
33 This is an intermediate driver that allows sharing of
35 To compile this driver as a module, choose M here: the module
36 will be called ifb. If you want to use more than one ifb
37 device at a time, you need to compile this driver as a module.
38 Instead of 'ifb', the devices will then be called 'ifb0',
40 Look at the iproute2 documentation directory for usage etc
43 tristate "Dummy net driver support"
45 This is essentially a bit-bucket device (i.e. traffic you send to
46 this device is consigned into oblivion) with a configurable IP
47 address. It is most commonly used in order to make your currently
48 inactive SLIP address seem like a real address for local programs.
49 If you use SLIP or PPP, you might want to say Y here. Since this
50 thing often comes in handy, the default is Y. It won't enlarge your
51 kernel either. What a deal. Read about it in the Network
52 Administrator's Guide, available from
53 <http://www.tldp.org/docs.html#guide>.
55 To compile this driver as a module, choose M here: the module
56 will be called dummy. If you want to use more than one dummy
57 device at a time, you need to compile this driver as a module.
58 Instead of 'dummy', the devices will then be called 'dummy0',
62 tristate "Bonding driver support"
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "EQL (serial line load balancing) support"
96 If you have two serial connections to some other computer (this
97 usually requires two modems and two telephone lines) and you use
98 SLIP (the protocol for sending Internet traffic over telephone
99 lines) or PPP (a better SLIP) on them, you can make them behave like
100 one double speed connection using this driver. Naturally, this has
101 to be supported at the other end as well, either with a similar EQL
102 Linux driver or with a Livingston Portmaster 2e.
104 Say Y if you want this and read
105 <file:Documentation/networking/eql.txt>. You may also want to read
106 section 6.2 of the NET-3-HOWTO, available from
107 <http://www.tldp.org/docs.html#howto>.
109 To compile this driver as a module, choose M here: the module
110 will be called eql. If unsure, say N.
113 tristate "Universal TUN/TAP device driver support"
116 TUN/TAP provides packet reception and transmission for user space
117 programs. It can be viewed as a simple Point-to-Point or Ethernet
118 device, which instead of receiving packets from a physical media,
119 receives them from user space program and instead of sending packets
120 via physical media writes them to the user space program.
122 When a program opens /dev/net/tun, driver creates and registers
123 corresponding net device tunX or tapX. After a program closed above
124 devices, driver will automatically delete tunXX or tapXX device and
125 all routes corresponding to it.
127 Please read <file:Documentation/networking/tuntap.txt> for more
130 To compile this driver as a module, choose M here: the module
133 If you don't know what to use this for, you don't need it.
136 tristate "Virtual ethernet pair device"
138 This device is a local ethernet tunnel. Devices are created in pairs.
139 When one end receives the packet it appears on its pair and vice
143 tristate "General Instruments Surfboard 1000"
146 This is a driver for the General Instrument (also known as
147 NextLevel) SURFboard 1000 internal
148 cable modem. This is an ISA card which is used by a number of cable
149 TV companies to provide cable modem access. It's a one-way
150 downstream-only cable modem, meaning that your upstream net link is
151 provided by your regular phone modem.
153 At present this driver only compiles as a module, so say M here if
154 you have this card. The module will be called sb1000. Then read
155 <file:Documentation/networking/README.sb1000> for information on how
156 to use this module, as it needs special ppp scripts for establishing
157 a connection. Further documentation and the necessary scripts can be
160 <http://www.jacksonville.net/~fventuri/>
161 <http://home.adelphia.net/~siglercm/sb1000.html>
162 <http://linuxpower.cx/~cable/>
164 If you don't have this card, of course say N.
166 source "drivers/net/arcnet/Kconfig"
168 source "drivers/net/phy/Kconfig"
174 menuconfig NET_ETHERNET
175 bool "Ethernet (10 or 100Mbit)"
178 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
179 type of Local Area Network (LAN) in universities and companies.
181 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
182 coaxial cable, linking computers in a chain), 10BASE-T or twisted
183 pair (10 Mbps over twisted pair cable, linking computers to central
184 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
185 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
186 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
187 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
188 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
189 Ethernet (1 Gbps over optical fiber or short copper links).
191 If your Linux machine will be connected to an Ethernet and you have
192 an Ethernet network interface card (NIC) installed in your computer,
193 say Y here and read the Ethernet-HOWTO, available from
194 <http://www.tldp.org/docs.html#howto>. You will then also have
195 to say Y to the driver for your particular NIC.
197 Note that the answer to this question won't directly affect the
198 kernel: saying N will just cause the configurator to skip all
199 the questions about Ethernet network cards. If unsure, say N.
204 tristate "Generic Media Independent Interface device support"
206 Most ethernet controllers have MII transceiver either as an external
207 or internal device. It is safe to say Y or M here even if your
208 ethernet card lack MII.
211 tristate "Atmel MACB support"
212 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
215 The Atmel MACB ethernet interface is found on many AT32 and AT91
216 parts. Say Y to include support for the MACB chip.
218 To compile this driver as a module, choose M here: the module
221 source "drivers/net/arm/Kconfig"
224 tristate "ASIX AX88796 NE2000 clone support"
225 depends on ARM || MIPS || SUPERH
229 AX88796 driver, using platform bus to provide
230 chip detection and resources
233 bool "ASIX AX88796 external 93CX6 eeprom support"
237 Select this if your platform comes with an external 93CX6 eeprom.
240 tristate "MACE (Power Mac ethernet) support"
241 depends on PPC_PMAC && PPC32
244 Power Macintoshes and clones with Ethernet built-in on the
245 motherboard will usually use a MACE (Medium Access Control for
246 Ethernet) interface. Say Y to include support for the MACE chip.
248 To compile this driver as a module, choose M here: the module
251 config MACE_AAUI_PORT
252 bool "Use AAUI port instead of TP by default"
255 Some Apple machines (notably the Apple Network Server) which use the
256 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
257 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
258 Y here if you have such a machine. If unsure, say N.
259 The driver will default to AAUI on ANS anyway, and if you use it as
260 a module, you can provide the port_aaui=0|1 to force the driver.
263 tristate "BMAC (G3 ethernet) support"
264 depends on PPC_PMAC && PPC32
267 Say Y for support of BMAC Ethernet interfaces. These are used on G3
270 To compile this driver as a module, choose M here: the module
274 tristate "Ariadne support"
277 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
280 To compile this driver as a module, choose M here: the module
281 will be called ariadne.
284 tristate "A2065 support"
288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
291 To compile this driver as a module, choose M here: the module
292 will be called a2065.
295 tristate "Hydra support"
299 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
301 To compile this driver as a module, choose M here: the module
302 will be called hydra.
305 tristate "Zorro NS8390-based Ethernet support"
309 This driver is for Zorro Ethernet cards using an NS8390-compatible
310 chipset, like the Village Tronic Ariadne II and the Individual
311 Computers X-Surf Ethernet cards. If you have such a card, say Y.
314 To compile this driver as a module, choose M here: the module
315 will be called zorro8390.
318 tristate "PCMCIA NE2000 support"
319 depends on AMIGA_PCMCIA
322 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
325 To compile this driver as a module, choose M here: the module
329 bool "Macintosh NS 8390 based ethernet cards"
333 If you want to include a driver to support Nubus or LC-PDS
334 Ethernet cards using an NS8390 chipset or its equivalent, say Y
335 and read the Ethernet-HOWTO, available from
336 <http://www.tldp.org/docs.html#howto>.
339 tristate "Macintosh CS89x0 based ethernet cards"
342 Support for CS89x0 chipset based Ethernet cards. If you have a
343 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
344 read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
347 To compile this driver as a module, choose M here. This module will
351 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
354 Support for NatSemi SONIC based Ethernet devices. This includes
355 the onboard Ethernet in many Quadras as well as some LC-PDS,
356 a few Nubus and all known Comm Slot Ethernet cards. If you have
357 one of these say Y and read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 To compile this driver as a module, choose M here. This module will
364 bool "Macintosh (AV) onboard MACE ethernet"
368 Support for the onboard AMD 79C940 MACE Ethernet controller used in
369 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
370 say Y and read the Ethernet-HOWTO, available from
371 <http://www.tldp.org/docs.html#howto>.
374 tristate "MVME147 (Lance) Ethernet support"
378 Support for the on-board Ethernet interface on the Motorola MVME147
379 single-board computer. Say Y here to include the
380 driver for this chip in your kernel.
381 To compile this driver as a module, choose M here.
384 tristate "MVME16x Ethernet support"
387 This is the driver for the Ethernet interface on the Motorola
388 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
389 driver for this chip in your kernel.
390 To compile this driver as a module, choose M here.
393 tristate "BVME6000 Ethernet support"
396 This is the driver for the Ethernet interface on BVME4000 and
397 BVME6000 VME boards. Say Y here to include the driver for this chip
399 To compile this driver as a module, choose M here.
402 tristate "Atari Lance support"
405 Say Y to include support for several Atari Ethernet adapters based
406 on the AMD Lance chipset: RieblCard (with or without battery), or
407 PAMCard VME (also the version by Rhotron, with different addresses).
410 tristate "Sun3/Sun3x on-board LANCE support"
411 depends on SUN3 || SUN3X
413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
415 here to compile in the Linux driver for this and enable Ethernet.
416 General Linux information on the Sun 3 and 3x series (now
418 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
420 If you're not building a kernel for a Sun 3, say N.
423 bool "Sun3 on-board Intel 82586 support"
426 This driver enables support for the on-board Intel 82586 based
427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
428 that this driver does not support 82586-based adapters on additional
432 bool "HP on-board LANCE support"
436 If you want to use the builtin "LANCE" Ethernet controller on an
437 HP300 machine, say Y here.
440 tristate "Lasi ethernet"
443 Say Y here to support the builtin Intel 82596 ethernet controller
444 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
447 tristate "SNI RM ethernet"
448 depends on NET_ETHERNET && SNI_RM
450 Say Y here to support the on-board Intel 82596 ethernet controller
451 built into SNI RM machines.
454 tristate "Korina (IDT RC32434) Ethernet support"
455 depends on NET_ETHERNET && MIKROTIK_RB532
457 If you have a Mikrotik RouterBoard 500 or IDT RC32434
458 based system say Y. Otherwise say N.
460 config MIPS_JAZZ_SONIC
461 tristate "MIPS JAZZ onboard SONIC Ethernet support"
464 This is the driver for the onboard card of MIPS Magnum 4000,
465 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
467 config XTENSA_XT2000_SONIC
468 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
469 depends on XTENSA_PLATFORM_XT2000
471 This is the driver for the onboard card of the Xtensa XT2000 board.
473 config MIPS_AU1X00_ENET
474 bool "MIPS AU1000 Ethernet support"
475 depends on SOC_AU1X00
479 If you have an Alchemy Semi AU1X00 based system
480 say Y. Otherwise, say N.
483 bool "SGI IOC3 Ethernet"
484 depends on PCI && SGI_IP27
488 If you have a network (Ethernet) card of this type, say Y and read
489 the Ethernet-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>.
493 tristate "MIPS simulator Network device"
496 The MIPSNET device is a simple Ethernet network device which is
497 emulated by the MIPS Simulator.
498 If you are not using a MIPSsim or are unsure, say N.
500 config SGI_O2MACE_ETH
501 tristate "SGI O2 MACE Fast Ethernet support"
502 depends on SGI_IP32=y
505 tristate "National DP83902AV support"
509 Support for cards based on the National Semiconductor DP83902AV
510 ST-NIC Serial Network Interface Controller for Twisted Pair. This
511 is a 10Mbit/sec Ethernet controller. Product overview and specs at
512 <http://www.national.com/pf/DP/DP83902A.html>.
517 tristate "Renesas SuperH Ethernet support"
518 depends on SUPERH && \
519 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
526 Renesas SuperH Ethernet device driver.
527 This driver support SH7710, SH7712, SH7763 and SH7619.
530 tristate "Sun LANCE support"
534 This driver supports the "le" interface present on all 32-bit Sparc
535 systems, on some older Ultra systems and as an Sbus option. These
536 cards are based on the AMD Lance chipset, which is better known
537 via the NE2100 cards.
539 To compile this driver as a module, choose M here: the module
540 will be called sunlance.
543 tristate "Sun Happy Meal 10/100baseT support"
544 depends on SBUS || PCI
547 This driver supports the "hme" interface present on most Ultra
548 systems and as an option on older Sbus systems. This driver supports
549 both PCI and Sbus devices. This driver also supports the "qfe" quad
550 100baseT device available in both PCI and Sbus configurations.
552 To compile this driver as a module, choose M here: the module
553 will be called sunhme.
556 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
557 depends on SBUS && EXPERIMENTAL
560 This driver supports the "be" interface available as an Sbus option.
561 This is Sun's older 100baseT Ethernet device.
563 To compile this driver as a module, choose M here: the module
564 will be called sunbmac.
567 tristate "Sun QuadEthernet support"
571 This driver supports the "qe" 10baseT Ethernet device, available as
572 an Sbus option. Note that this is not the same as Quad FastEthernet
573 "qfe" which is supported by the Happy Meal driver instead.
575 To compile this driver as a module, choose M here: the module
576 will be called sunqe.
579 tristate "Sun GEM support"
583 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
584 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
587 tristate "Sun Cassini support"
591 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
592 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
595 tristate "Sun Virtual Network support"
598 Support for virtual network devices under Sun Logical Domains.
600 config NET_VENDOR_3COM
602 depends on ISA || EISA || MCA || PCI
604 If you have a network (Ethernet) card belonging to this class, say Y
605 and read the Ethernet-HOWTO, available from
606 <http://www.tldp.org/docs.html#howto>.
608 Note that the answer to this question doesn't directly affect the
609 kernel: saying N will just cause the configurator to skip all
610 the questions about 3COM cards. If you say Y, you will be asked for
611 your specific card in the following questions.
614 tristate "3c501 \"EtherLink\" support"
615 depends on NET_VENDOR_3COM && ISA
617 If you have a network (Ethernet) card of this type, say Y and read
618 the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
620 new card, since the 3c501 is slow, broken, and obsolete: you will
621 have problems. Some people suggest to ping ("man ping") a nearby
622 machine every minute ("man cron") when using this card.
624 To compile this driver as a module, choose M here. The module
625 will be called 3c501.
628 tristate "3c503 \"EtherLink II\" support"
629 depends on NET_VENDOR_3COM && ISA
632 If you have a network (Ethernet) card of this type, say Y and read
633 the Ethernet-HOWTO, available from
634 <http://www.tldp.org/docs.html#howto>.
636 To compile this driver as a module, choose M here. The module
637 will be called 3c503.
640 tristate "3c505 \"EtherLink Plus\" support"
641 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
643 Information about this network (Ethernet) card can be found in
644 <file:Documentation/networking/3c505.txt>. If you have a card of
645 this type, say Y and read the Ethernet-HOWTO, available from
646 <http://www.tldp.org/docs.html#howto>.
648 To compile this driver as a module, choose M here. The module
649 will be called 3c505.
652 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
653 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
655 If you have a network (Ethernet) card of this type, say Y and read
656 the Ethernet-HOWTO, available from
657 <http://www.tldp.org/docs.html#howto>.
659 To compile this driver as a module, choose M here. The module
660 will be called 3c507.
663 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
664 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
666 If you have a network (Ethernet) card belonging to the 3Com
667 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
668 from <http://www.tldp.org/docs.html#howto>.
670 If your card is not working you may need to use the DOS
671 setup disk to disable Plug & Play mode, and to select the default
674 To compile this driver as a module, choose M here. The module
675 will be called 3c509.
678 tristate "3c515 ISA \"Fast EtherLink\""
679 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
681 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
682 network card, say Y and read the Ethernet-HOWTO, available from
683 <http://www.tldp.org/docs.html#howto>.
685 To compile this driver as a module, choose M here. The module
686 will be called 3c515.
689 tristate "3c523 \"EtherLink/MC\" support"
690 depends on NET_VENDOR_3COM && MCA_LEGACY
692 If you have a network (Ethernet) card of this type, say Y and read
693 the Ethernet-HOWTO, available from
694 <http://www.tldp.org/docs.html#howto>.
696 To compile this driver as a module, choose M here. The module
697 will be called 3c523.
700 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
701 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
703 If you have a network (Ethernet) card of this type, say Y and read
704 the Ethernet-HOWTO, available from
705 <http://www.tldp.org/docs.html#howto>.
707 To compile this driver as a module, choose M here. The module
708 will be called 3c527.
711 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
712 depends on NET_VENDOR_3COM && (PCI || EISA)
715 This option enables driver support for a large number of 10Mbps and
716 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
718 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
719 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
720 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
721 "Tornado" (3c905) PCI
722 "Hurricane" (3c555/3cSOHO) PCI
724 If you have such a card, say Y and read the Ethernet-HOWTO,
725 available from <http://www.tldp.org/docs.html#howto>. More
726 specific information is in
727 <file:Documentation/networking/vortex.txt> and in the comments at
728 the beginning of <file:drivers/net/3c59x.c>.
730 To compile this support as a module, choose M here.
733 tristate "3cr990 series \"Typhoon\" support"
734 depends on NET_VENDOR_3COM && PCI
737 This option enables driver support for the 3cr990 series of cards:
739 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
740 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
741 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
743 If you have a network (Ethernet) card of this type, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>.
747 To compile this driver as a module, choose M here. The module
748 will be called typhoon.
751 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
752 depends on ISA && ISA_DMA_API
754 If you have a network (Ethernet) card of this type, say Y and read
755 the Ethernet-HOWTO, available from
756 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
759 To compile this driver as a module, choose M here: the module
760 will be called lance. This is recommended.
762 config NET_VENDOR_SMC
763 bool "Western Digital/SMC cards"
764 depends on ISA || MCA || EISA || MAC
766 If you have a network (Ethernet) card belonging to this class, say Y
767 and read the Ethernet-HOWTO, available from
768 <http://www.tldp.org/docs.html#howto>.
770 Note that the answer to this question doesn't directly affect the
771 kernel: saying N will just cause the configurator to skip all
772 the questions about Western Digital cards. If you say Y, you will be
773 asked for your specific card in the following questions.
776 tristate "WD80*3 support"
777 depends on NET_VENDOR_SMC && ISA
780 If you have a network (Ethernet) card of this type, say Y and read
781 the Ethernet-HOWTO, available from
782 <http://www.tldp.org/docs.html#howto>.
784 To compile this driver as a module, choose M here. The module
788 tristate "SMC Ultra MCA support"
789 depends on NET_VENDOR_SMC && MCA
792 If you have a network (Ethernet) card of this type and are running
793 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
794 available from <http://www.tldp.org/docs.html#howto>.
796 To compile this driver as a module, choose M here. The module
797 will be called smc-mca.
800 tristate "SMC Ultra support"
801 depends on NET_VENDOR_SMC && ISA
804 If you have a network (Ethernet) card of this type, say Y and read
805 the Ethernet-HOWTO, available from
806 <http://www.tldp.org/docs.html#howto>.
808 Important: There have been many reports that, with some motherboards
809 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
810 such as some BusLogic models) causes corruption problems with many
811 operating systems. The Linux smc-ultra driver has a work-around for
812 this but keep it in mind if you have such a SCSI card and have
815 To compile this driver as a module, choose M here. The module
816 will be called smc-ultra.
819 tristate "SMC Ultra32 EISA support"
820 depends on NET_VENDOR_SMC && EISA
823 If you have a network (Ethernet) card of this type, say Y and read
824 the Ethernet-HOWTO, available from
825 <http://www.tldp.org/docs.html#howto>.
827 To compile this driver as a module, choose M here. The module
828 will be called smc-ultra32.
831 tristate "Blackfin on-chip MAC support"
832 depends on NET_ETHERNET && (BF526 || BF527 || BF536 || BF537)
836 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
838 This is the driver for Blackfin on-chip mac device. Say Y if you want it
839 compiled into the kernel. This driver is also available as a module
840 ( = code which can be inserted in and removed from the running kernel
841 whenever you want). The module will be called bfin_mac.
843 config BFIN_MAC_USE_L1
844 bool "Use L1 memory for rx/tx packets"
845 depends on BFIN_MAC && (BF527 || BF537)
848 To get maximum network performance, you should use L1 memory as rx/tx buffers.
849 Say N here if you want to reserve L1 memory for other uses.
851 config BFIN_TX_DESC_NUM
852 int "Number of transmit buffer packets"
854 range 6 10 if BFIN_MAC_USE_L1
858 Set the number of buffer packets used in driver.
860 config BFIN_RX_DESC_NUM
861 int "Number of receive buffer packets"
863 range 20 100 if BFIN_MAC_USE_L1
867 Set the number of buffer packets used in driver.
870 bool "RMII PHY Interface (EXPERIMENTAL)"
871 depends on BFIN_MAC && EXPERIMENTAL
872 default y if BFIN527_EZKIT
873 default n if BFIN537_STAMP
875 Use Reduced PHY MII Interface
878 tristate "SMC 9194 support"
879 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
882 This is support for the SMC9xxx based Ethernet cards. Choose this
883 option if you have a DELL laptop with the docking station, or
884 another SMC9192/9194 based chipset. Say Y if you want it compiled
885 into the kernel, and read the file
886 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
887 available from <http://www.tldp.org/docs.html#howto>.
889 To compile this driver as a module, choose M here. The module
890 will be called smc9194.
893 tristate "SMC 91C9x/91C1xxx support"
896 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
897 MIPS || BLACKFIN || MN10300
899 This is a driver for SMC's 91x series of Ethernet chipsets,
900 including the SMC91C94 and the SMC91C111. Say Y if you want it
901 compiled into the kernel, and read the file
902 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
903 available from <http://www.linuxdoc.org/docs.html#howto>.
905 This driver is also available as a module ( = code which can be
906 inserted in and removed from the running kernel whenever you want).
907 The module will be called smc91x. If you want to compile it as a
908 module, say M here and read <file:Documentation/kbuild/modules.txt>.
911 tristate "NetX Ethernet support"
915 This is support for the Hilscher netX builtin Ethernet ports
917 To compile this driver as a module, choose M here. The module
918 will be called netx-eth.
921 tristate "DM9000 support"
922 depends on ARM || BLACKFIN || MIPS
926 Support for DM9000 chipset.
928 To compile this driver as a module, choose M here. The module
929 will be called dm9000.
931 config DM9000_DEBUGLEVEL
932 int "DM9000 maximum debug level"
936 The maximum level of debugging code compiled into the DM9000
939 config DM9000_FORCE_SIMPLE_PHY_POLL
940 bool "Force simple NSR based PHY polling"
943 This configuration forces the DM9000 to use the NSR's LinkStatus
944 bit to determine if the link is up or down instead of the more
945 costly MII PHY reads. Note, this will not work if the chip is
946 operating with an external PHY.
949 tristate "ENC28J60 support"
950 depends on EXPERIMENTAL && SPI && NET_ETHERNET
953 Support for the Microchip EN28J60 ethernet chip.
955 To compile this driver as a module, choose M here. The module will be
958 config ENC28J60_WRITEVERIFY
959 bool "Enable write verify"
962 Enable the verify after the buffer write useful for debugging purpose.
966 tristate "SMSC LAN911[5678] support"
969 depends on ARM || SUPERH
971 This is a driver for SMSC's LAN911x series of Ethernet chipsets
972 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
973 Say Y if you want it compiled into the kernel,
974 and read the Ethernet-HOWTO, available from
975 <http://www.linuxdoc.org/docs.html#howto>.
977 This driver is also available as a module. The module will be
978 called smc911x. If you want to compile it as a module, say M
979 here and read <file:Documentation/kbuild/modules.txt>
981 config NET_VENDOR_RACAL
982 bool "Racal-Interlan (Micom) NI cards"
985 If you have a network (Ethernet) card belonging to this class, such
986 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
987 available from <http://www.tldp.org/docs.html#howto>.
989 Note that the answer to this question doesn't directly affect the
990 kernel: saying N will just cause the configurator to skip all
991 the questions about NI cards. If you say Y, you will be asked for
992 your specific card in the following questions.
995 tristate "NI5010 support (EXPERIMENTAL)"
996 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
998 If you have a network (Ethernet) card of this type, say Y and read
999 the Ethernet-HOWTO, available from
1000 <http://www.tldp.org/docs.html#howto>. Note that this is still
1003 To compile this driver as a module, choose M here. The module
1004 will be called ni5010.
1007 tristate "NI5210 support"
1008 depends on NET_VENDOR_RACAL && ISA
1010 If you have a network (Ethernet) card of this type, say Y and read
1011 the Ethernet-HOWTO, available from
1012 <http://www.tldp.org/docs.html#howto>.
1014 To compile this driver as a module, choose M here. The module
1015 will be called ni52.
1018 tristate "NI6510 support"
1019 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1021 If you have a network (Ethernet) card of this type, say Y and read
1022 the Ethernet-HOWTO, available from
1023 <http://www.tldp.org/docs.html#howto>.
1025 To compile this driver as a module, choose M here. The module
1026 will be called ni65.
1028 source "drivers/net/tulip/Kconfig"
1031 tristate "AT1700/1720 support (EXPERIMENTAL)"
1032 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1035 If you have a network (Ethernet) card of this type, say Y and read
1036 the Ethernet-HOWTO, available from
1037 <http://www.tldp.org/docs.html#howto>.
1039 To compile this driver as a module, choose M here. The module
1040 will be called at1700.
1043 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1044 depends on ISA || EISA || MCA
1047 If you have a network (Ethernet) card of this type, say Y and read
1048 the Ethernet-HOWTO, available from
1049 <http://www.tldp.org/docs.html#howto> as well as
1050 <file:drivers/net/depca.c>.
1052 To compile this driver as a module, choose M here. The module
1053 will be called depca.
1056 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1057 depends on ISA || EISA || PCI
1059 If you have a network (Ethernet) card of this type, say Y and read
1060 the Ethernet-HOWTO, available from
1061 <http://www.tldp.org/docs.html#howto>.
1063 To compile this driver as a module, choose M here. The module
1064 will be called hp100.
1067 bool "Other ISA cards"
1070 If your network (Ethernet) card hasn't been mentioned yet and its
1071 bus system (that's the way the cards talks to the other components
1072 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1073 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1074 available from <http://www.tldp.org/docs.html#howto>.
1078 Note that the answer to this question doesn't directly affect the
1079 kernel: saying N will just cause the configurator to skip all
1080 the remaining ISA network card questions. If you say Y, you will be
1081 asked for your specific card in the following questions.
1084 tristate "Cabletron E21xx support"
1088 If you have a network (Ethernet) card of this type, say Y and read
1089 the Ethernet-HOWTO, available from
1090 <http://www.tldp.org/docs.html#howto>.
1092 To compile this driver as a module, choose M here. The module
1093 will be called e2100.
1096 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1100 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1101 cards. If this is for you, say Y and read
1102 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1103 well as the Ethernet-HOWTO, available from
1104 <http://www.tldp.org/docs.html#howto>.
1106 To compile this driver as a module, choose M here. The module
1107 will be called ewrk3.
1110 tristate "EtherExpress 16 support"
1113 If you have an EtherExpress16 network (Ethernet) card, say Y and
1114 read the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1116 EtherExpress16 card used to be regarded as a very poor choice
1117 because the driver was very unreliable. We now have a new driver
1118 that should do better.
1120 To compile this driver as a module, choose M here. The module
1121 will be called eexpress.
1124 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1127 If you have a network (Ethernet) card of this type, say Y. This
1128 driver supports Intel i82595{FX,TX} based boards. Note however
1129 that the EtherExpress PRO/100 Ethernet card has its own separate
1130 driver. Please read the Ethernet-HOWTO, available from
1131 <http://www.tldp.org/docs.html#howto>.
1133 To compile this driver as a module, choose M here. The module
1134 will be called eepro.
1137 tristate "HP PCLAN+ (27247B and 27252A) support"
1141 If you have a network (Ethernet) card of this type, say Y and read
1142 the Ethernet-HOWTO, available from
1143 <http://www.tldp.org/docs.html#howto>.
1145 To compile this driver as a module, choose M here. The module
1146 will be called hp-plus.
1149 tristate "HP PCLAN (27245 and other 27xxx series) support"
1153 If you have a network (Ethernet) card of this type, say Y and read
1154 the Ethernet-HOWTO, available from
1155 <http://www.tldp.org/docs.html#howto>.
1157 To compile this driver as a module, choose M here. The module
1161 tristate "LP486E on board Ethernet"
1164 Say Y here to support the 82596-based on-board Ethernet controller
1165 for the Panther motherboard, which is one of the two shipped in the
1166 Intel Professional Workstation.
1169 tristate "ICL EtherTeam 16i/32 support"
1172 If you have a network (Ethernet) card of this type, say Y and read
1173 the Ethernet-HOWTO, available from
1174 <http://www.tldp.org/docs.html#howto>.
1176 To compile this driver as a module, choose M here. The module
1177 will be called eth16i.
1180 tristate "NE2000/NE1000 support"
1181 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1184 If you have a network (Ethernet) card of this type, say Y and read
1185 the Ethernet-HOWTO, available from
1186 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1187 without a specific driver are compatible with NE2000.
1189 If you have a PCI NE2000 card however, say N here and Y to "PCI
1190 NE2000 and clone support" under "EISA, VLB, PCI and on board
1191 controllers" below. If you have a NE2000 card and are running on
1192 an MCA system (a bus system used on some IBM PS/2 computers and
1193 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1196 To compile this driver as a module, choose M here. The module
1200 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1201 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1203 The Zenith Z-Note notebook computer has a built-in network
1204 (Ethernet) card, and this is the Linux driver for it. Note that the
1205 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1206 by this driver. Read the Ethernet-HOWTO, available from
1207 <http://www.tldp.org/docs.html#howto>.
1210 tristate "SEEQ8005 support (EXPERIMENTAL)"
1211 depends on NET_ISA && EXPERIMENTAL
1213 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1214 is for you, read the Ethernet-HOWTO, available from
1215 <http://www.tldp.org/docs.html#howto>.
1217 To compile this driver as a module, choose M here. The module
1218 will be called seeq8005.
1221 tristate "NE/2 (ne2000 MCA version) support"
1222 depends on MCA_LEGACY
1225 If you have a network (Ethernet) card of this type, say Y and read
1226 the Ethernet-HOWTO, available from
1227 <http://www.tldp.org/docs.html#howto>.
1229 To compile this driver as a module, choose M here. The module
1233 tristate "IBM LAN Adapter/A support"
1236 This is a Micro Channel Ethernet adapter. You need to set
1237 CONFIG_MCA to use this driver. It is both available as an in-kernel
1238 driver and as a module.
1240 To compile this driver as a module, choose M here. The only
1241 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1242 will both support 16K and 32K memory windows, however a 32K window
1243 gives a better security against packet losses. Usage of multiple
1244 boards with this driver should be possible, but has not been tested
1245 up to now due to lack of hardware.
1248 tristate "IBM LAN Virtual Ethernet support"
1249 depends on PPC_PSERIES
1251 This driver supports virtual ethernet adapters on newer IBM iSeries
1252 and pSeries systems.
1254 To compile this driver as a module, choose M here. The module will
1257 source "drivers/net/ibm_newemac/Kconfig"
1260 bool "EISA, VLB, PCI and on board controllers"
1261 depends on ISA || EISA || PCI
1263 This is another class of network cards which attach directly to the
1264 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1265 available from <http://www.tldp.org/docs.html#howto>.
1267 Note that the answer to this question doesn't directly affect the
1268 kernel: saying N will just cause the configurator to skip all
1269 the questions about this class of network cards. If you say Y, you
1270 will be asked for your specific card in the following questions. If
1271 you are unsure, say Y.
1274 tristate "AMD PCnet32 PCI support"
1275 depends on NET_PCI && PCI
1279 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1280 answer Y here and read the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1283 To compile this driver as a module, choose M here. The module
1284 will be called pcnet32.
1287 tristate "AMD 8111 (new PCI lance) support"
1288 depends on NET_PCI && PCI
1292 If you have an AMD 8111-based PCI lance ethernet card,
1293 answer Y here and read the Ethernet-HOWTO, available from
1294 <http://www.tldp.org/docs.html#howto>.
1296 To compile this driver as a module, choose M here. The module
1297 will be called amd8111e.
1299 config ADAPTEC_STARFIRE
1300 tristate "Adaptec Starfire/DuraLAN support"
1301 depends on NET_PCI && PCI
1305 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1306 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1307 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1310 To compile this driver as a module, choose M here: the module
1311 will be called starfire. This is recommended.
1314 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1315 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1318 If you have a network (Ethernet) card of this type, say Y and read
1319 the Ethernet-HOWTO, available from
1320 <http://www.tldp.org/docs.html#howto>.
1322 To compile this driver as a module, choose M here. The module
1323 will be called ac3200.
1326 tristate "Apricot Xen-II on board Ethernet"
1327 depends on NET_PCI && ISA
1329 If you have a network (Ethernet) controller of this type, say Y and
1330 read the Ethernet-HOWTO, available from
1331 <http://www.tldp.org/docs.html#howto>.
1333 To compile this driver as a module, choose M here. The module
1334 will be called apricot.
1337 tristate "Broadcom 440x/47xx ethernet support"
1338 depends on SSB_POSSIBLE && HAS_DMA
1342 If you have a network (Ethernet) controller of this type, say Y
1343 or M and read the Ethernet-HOWTO, available from
1344 <http://www.tldp.org/docs.html#howto>.
1346 To compile this driver as a module, choose M here. The module
1349 # Auto-select SSB PCI-HOST support, if possible
1350 config B44_PCI_AUTOSELECT
1352 depends on B44 && SSB_PCIHOST_POSSIBLE
1356 # Auto-select SSB PCICORE driver, if possible
1357 config B44_PCICORE_AUTOSELECT
1359 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1360 select SSB_DRIVER_PCICORE
1365 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1369 tristate "nForce Ethernet support"
1370 depends on NET_PCI && PCI
1372 If you have a network (Ethernet) controller of this type, say Y and
1373 read the Ethernet-HOWTO, available from
1374 <http://www.tldp.org/docs.html#howto>.
1376 To compile this driver as a module, choose M here. The module
1377 will be called forcedeth.
1379 config FORCEDETH_NAPI
1380 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1381 depends on FORCEDETH && EXPERIMENTAL
1383 NAPI is a new driver API designed to reduce CPU and interrupt load
1384 when the driver is receiving lots of packets from the card. It is
1385 still somewhat experimental and thus not yet enabled by default.
1387 If your estimated Rx load is 10kpps or more, or if the card will be
1388 deployed on potentially unfriendly networks (e.g. in a firewall),
1394 tristate "CS89x0 support"
1395 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1396 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1398 Support for CS89x0 chipset based Ethernet cards. If you have a
1399 network (Ethernet) card of this type, say Y and read the
1400 Ethernet-HOWTO, available from
1401 <http://www.tldp.org/docs.html#howto> as well as
1402 <file:Documentation/networking/cs89x0.txt>.
1404 To compile this driver as a module, choose M here. The module
1405 will be called cs89x0.
1407 config CS89x0_NONISA_IRQ
1409 depends on CS89x0 != n
1410 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1413 tristate "TOSHIBA TC35815 Ethernet support"
1414 depends on NET_PCI && PCI && MIPS
1418 tristate "Intel(R) PRO/100+ support"
1419 depends on NET_PCI && PCI
1422 This driver supports Intel(R) PRO/100 family of adapters.
1423 To verify that your adapter is supported, find the board ID number
1424 on the adapter. Look for a label that has a barcode and a number
1425 in the format 123456-001 (six digits hyphen three digits).
1427 Use the above information and the Adapter & Driver ID Guide at:
1429 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1431 to identify the adapter.
1433 For the latest Intel PRO/100 network driver for Linux, see:
1435 <http://appsr.intel.com/scripts-df/support_intel.asp>
1437 More specific information on configuring the driver is in
1438 <file:Documentation/networking/e100.txt>.
1440 To compile this driver as a module, choose M here. The module
1441 will be called e100.
1444 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1445 depends on NET_PCI && EISA && EXPERIMENTAL
1448 If you have a network (Ethernet) card of this type, say Y and read
1449 the Ethernet-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>.
1452 To compile this driver as a module, choose M here. The module
1453 will be called lne390.
1456 tristate "Myson MTD-8xx PCI Ethernet support"
1457 depends on NET_PCI && PCI
1461 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1462 cards. Specifications and data at
1463 <http://www.myson.com.hk/mtd/datasheet/>.
1466 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1467 depends on NET_PCI && PCI
1470 This driver is for the National Semiconductor DP83810 series,
1471 which is used in cards from PureData, NetGear, Linksys
1472 and others, including the 83815 chip.
1473 More specific information and updates are available from
1474 <http://www.scyld.com/network/natsemi.html>.
1477 tristate "PCI NE2000 and clones support (see help)"
1478 depends on NET_PCI && PCI
1481 This driver is for NE2000 compatible PCI cards. It will not work
1482 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1483 support" below). If you have a PCI NE2000 network (Ethernet) card,
1484 say Y and read the Ethernet-HOWTO, available from
1485 <http://www.tldp.org/docs.html#howto>.
1487 This driver also works for the following NE2000 clone cards:
1488 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1489 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1490 Holtek HT80232 Holtek HT80229
1492 To compile this driver as a module, choose M here. The module
1493 will be called ne2k-pci.
1496 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1497 depends on NET_PCI && EISA && EXPERIMENTAL
1500 If you have a network (Ethernet) card of this type, say Y and read
1501 the Ethernet-HOWTO, available from
1502 <http://www.tldp.org/docs.html#howto>. Note that this driver
1503 will NOT WORK for NE3200 cards as they are completely different.
1505 To compile this driver as a module, choose M here. The module
1506 will be called ne3210.
1509 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1510 depends on NET_PCI && EISA && EXPERIMENTAL
1513 If you have a network (Ethernet) card of this type, say Y and read
1514 the Ethernet-HOWTO, available from
1515 <http://www.tldp.org/docs.html#howto>.
1517 To compile this driver as a module, choose M here. The module
1518 will be called es3210.
1521 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1522 depends on NET_PCI && PCI && EXPERIMENTAL
1526 This is a driver for the Fast Ethernet PCI network cards based on
1527 the RTL8139C+ chips. If you have one of those, say Y and read
1528 the Ethernet-HOWTO, available from
1529 <http://www.tldp.org/docs.html#howto>.
1531 To compile this driver as a module, choose M here: the module
1532 will be called 8139cp. This is recommended.
1535 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1536 depends on NET_PCI && PCI
1540 This is a driver for the Fast Ethernet PCI network cards based on
1541 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1542 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1544 To compile this driver as a module, choose M here: the module
1545 will be called 8139too. This is recommended.
1548 bool "Use PIO instead of MMIO"
1552 This instructs the driver to use programmed I/O ports (PIO) instead
1553 of PCI shared memory (MMIO). This can possibly solve some problems
1554 in case your mainboard has memory consistency issues. If unsure,
1557 config 8139TOO_TUNE_TWISTER
1558 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1561 This implements a function which might come in handy in case you
1562 are using low quality on long cabling. It is required for RealTek
1563 RTL-8139 revision K boards, and totally unused otherwise. It tries
1564 to match the transceiver to the cable characteristics. This is
1565 experimental since hardly documented by the manufacturer.
1569 bool "Support for older RTL-8129/8130 boards"
1572 This enables support for the older and uncommon RTL-8129 and
1573 RTL-8130 chips, which support MII via an external transceiver,
1574 instead of an internal one. Disabling this option will save some
1575 memory by making the code size smaller. If unsure, say Y.
1577 config 8139_OLD_RX_RESET
1578 bool "Use older RX-reset method"
1581 The 8139too driver was recently updated to contain a more rapid
1582 reset sequence, in the face of severe receive errors. This "new"
1583 RX-reset method should be adequate for all boards. But if you
1584 experience problems, you can enable this option to restore the
1585 old RX-reset behavior. If unsure, say N.
1588 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1589 depends on NET_PCI && PCI
1593 This is a driver for the R6040 Fast Ethernet MACs found in the
1594 the RDC R-321x System-on-chips.
1596 To compile this driver as a module, choose M here: the module
1597 will be called r6040. This is recommended.
1600 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1601 depends on NET_PCI && PCI
1605 This is a driver for the Fast Ethernet PCI network cards based on
1606 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1607 SiS 630 and SiS 540 chipsets.
1609 This driver also supports AMD 79C901 HomePNA so that you can use
1610 your phone line as a network cable.
1612 To compile this driver as a module, choose M here: the module
1613 will be called sis900. This is recommended.
1616 tristate "SMC EtherPower II"
1617 depends on NET_PCI && PCI
1621 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1622 which is based on the SMC83c17x (EPIC/100).
1623 More specific information and updates are available from
1624 <http://www.scyld.com/network/epic100.html>.
1627 tristate "Sundance Alta support"
1628 depends on NET_PCI && PCI
1632 This driver is for the Sundance "Alta" chip.
1633 More specific information and updates are available from
1634 <http://www.scyld.com/network/sundance.html>.
1636 config SUNDANCE_MMIO
1637 bool "Use MMIO instead of PIO"
1640 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1641 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1642 is known to solve bugs on certain chips.
1647 tristate "TI ThunderLAN support"
1648 depends on NET_PCI && (PCI || EISA)
1650 If you have a PCI Ethernet network card based on the ThunderLAN chip
1651 which is supported by this driver, say Y and read the
1652 Ethernet-HOWTO, available from
1653 <http://www.tldp.org/docs.html#howto>.
1655 Devices currently supported by this driver are Compaq Netelligent,
1656 Compaq NetFlex and Olicom cards. Please read the file
1657 <file:Documentation/networking/tlan.txt> for more details.
1659 To compile this driver as a module, choose M here. The module
1660 will be called tlan.
1662 Please email feedback to <torben.mathiasen@compaq.com>.
1665 tristate "VIA Rhine support"
1666 depends on NET_PCI && PCI
1670 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1671 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1672 Ethernet functions can also be found integrated on South Bridges
1675 To compile this driver as a module, choose M here. The module
1676 will be called via-rhine.
1678 config VIA_RHINE_MMIO
1679 bool "Use MMIO instead of PIO"
1680 depends on VIA_RHINE
1682 This instructs the driver to use PCI shared memory (MMIO) instead of
1683 programmed I/O ports (PIO). Enabling this gives an improvement in
1684 processing time in parts of the driver.
1689 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1690 depends on NET_PCI && PCI && EXPERIMENTAL
1693 This is a driver for the Fast Ethernet PCI network cards based on
1694 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1695 have one of these, say Y here.
1697 To compile this driver as a module, choose M here: the module
1698 will be called sc92031. This is recommended.
1701 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1702 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1705 TI AR7 CPMAC Ethernet support
1708 bool "Pocket and portable adapters"
1711 Cute little network (Ethernet) devices which attach to the parallel
1712 port ("pocket adapters"), commonly used with laptops. If you have
1713 one of those, say Y and read the Ethernet-HOWTO, available from
1714 <http://www.tldp.org/docs.html#howto>.
1716 If you want to plug a network (or some other) card into the PCMCIA
1717 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1718 credit card size extension cards used by all modern laptops), you
1719 need the pcmcia-cs package (location contained in the file
1720 <file:Documentation/Changes>) and you can say N here.
1722 Laptop users should read the Linux Laptop home page at
1723 <http://www.linux-on-laptops.com/> or
1724 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1726 Note that the answer to this question doesn't directly affect the
1727 kernel: saying N will just cause the configurator to skip all
1728 the questions about this class of network devices. If you say Y, you
1729 will be asked for your specific device in the following questions.
1732 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1733 depends on NET_POCKET && PARPORT && X86
1736 This is a network (Ethernet) device which attaches to your parallel
1737 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1738 available from <http://www.tldp.org/docs.html#howto>, if you
1739 want to use this. If you intend to use this driver, you should have
1740 said N to the "Parallel printer support", because the two drivers
1741 don't like each other.
1743 To compile this driver as a module, choose M here: the module
1747 tristate "D-Link DE600 pocket adapter support"
1748 depends on NET_POCKET && PARPORT
1750 This is a network (Ethernet) device which attaches to your parallel
1751 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1752 Ethernet-HOWTO, available from
1753 <http://www.tldp.org/docs.html#howto>, if you want to use
1754 this. It is possible to have several devices share a single parallel
1755 port and it is safe to compile the corresponding drivers into the
1758 To compile this driver as a module, choose M here: the module
1759 will be called de600.
1762 tristate "D-Link DE620 pocket adapter support"
1763 depends on NET_POCKET && PARPORT
1765 This is a network (Ethernet) device which attaches to your parallel
1766 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1767 Ethernet-HOWTO, available from
1768 <http://www.tldp.org/docs.html#howto>, if you want to use
1769 this. It is possible to have several devices share a single parallel
1770 port and it is safe to compile the corresponding drivers into the
1773 To compile this driver as a module, choose M here: the module
1774 will be called de620.
1777 tristate "SGI Seeq ethernet controller support"
1778 depends on SGI_HAS_SEEQ
1780 Say Y here if you have an Seeq based Ethernet network card. This is
1781 used in many Silicon Graphics machines.
1784 tristate "DEC LANCE ethernet controller support"
1785 depends on MACH_DECSTATION
1788 This driver is for the series of Ethernet controllers produced by
1789 DEC (now Compaq) based on the AMD Lance chipset, including the
1790 DEPCA series. (This chipset is better known via the NE2100 cards.)
1793 bool "Motorola 68360 ethernet controller"
1796 Say Y here if you want to use the built-in ethernet controller of
1797 the Motorola 68360 processor.
1800 bool "FEC ethernet controller (of ColdFire CPUs)"
1801 depends on M523x || M527x || M5272 || M528x || M520x
1803 Say Y here if you want to use the built-in 10/100 Fast ethernet
1804 controller on some Motorola ColdFire processors.
1807 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1810 Say Y here if you want to use the second built-in 10/100 Fast
1811 ethernet controller on some Motorola ColdFire processors.
1814 tristate "MPC52xx FEC driver"
1815 depends on PPC_MPC52xx && PPC_BESTCOMM_FEC
1819 This option enables support for the MPC5200's on-chip
1820 Fast Ethernet Controller
1821 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1823 config FEC_MPC52xx_MDIO
1824 bool "MPC52xx FEC MDIO bus driver"
1825 depends on FEC_MPC52xx
1828 The MPC5200's FEC can connect to the Ethernet either with
1829 an external MII PHY chip or 10 Mbps 7-wire interface
1830 (Motorola? industry standard).
1831 If your board uses an external PHY connected to FEC, enable this.
1832 If not sure, enable.
1833 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1836 tristate "NE2000 compatible support for H8/300"
1839 Say Y here if you want to use the NE2000 compatible
1840 controller on the Renesas H8/300 processor.
1843 tristate "Atheros L2 Fast Ethernet support"
1848 This driver supports the Atheros L2 fast ethernet adapter.
1850 To compile this driver as a module, choose M here. The module
1851 will be called atl2.
1853 source "drivers/net/fs_enet/Kconfig"
1855 endif # NET_ETHERNET
1861 menuconfig NETDEV_1000
1862 bool "Ethernet (1000 Mbit)"
1866 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1867 type of Local Area Network (LAN) in universities and companies.
1869 Say Y here to get to see options for Gigabit Ethernet drivers.
1870 This option alone does not add any kernel code.
1871 Note that drivers supporting both 100 and 1000 MBit may be listed
1872 under "Ethernet (10 or 100MBit)" instead.
1874 If you say N, all options in this submenu will be skipped and disabled.
1879 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1882 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1883 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1884 adapter. The driver allows for using the Jumbo Frame option (9000
1885 bytes/frame) however it requires that your switches can handle this
1886 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1889 To compile this driver as a module, choose M here: the
1890 module will be called acenic.
1892 config ACENIC_OMIT_TIGON_I
1893 bool "Omit support for old Tigon I based AceNICs"
1896 Say Y here if you only have Tigon II based AceNICs and want to leave
1897 out support for the older Tigon I based cards which are no longer
1898 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1899 version)). This will reduce the size of the driver object by
1900 app. 100KB. If you are not sure whether your card is a Tigon I or a
1901 Tigon II, say N here.
1903 The safe and default value for this is N.
1906 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1910 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1912 D-Link DGE-550T Gigabit Ethernet Adapter.
1913 D-Link DL2000-based Gigabit Ethernet Adapter.
1914 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1916 To compile this driver as a module, choose M here: the
1917 module will be called dl2k.
1920 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1923 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1924 adapters. For more information on how to identify your adapter, go
1925 to the Adapter & Driver ID Guide at:
1927 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1929 For general information and support, go to the Intel support
1932 <http://support.intel.com>
1934 More specific information on configuring the driver is in
1935 <file:Documentation/networking/e1000.txt>.
1937 To compile this driver as a module, choose M here. The module
1938 will be called e1000.
1941 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1942 depends on PCI && (!SPARC32 || BROKEN)
1944 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1945 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1946 use the regular e1000 driver For more information on how to
1947 identify your adapter, go to the Adapter & Driver ID Guide at:
1949 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1951 For general information and support, go to the Intel support
1954 <http://support.intel.com>
1956 To compile this driver as a module, choose M here. The module
1957 will be called e1000e.
1960 tristate "IP1000 Gigabit Ethernet support"
1961 depends on PCI && EXPERIMENTAL
1964 This driver supports IP1000 gigabit Ethernet cards.
1966 To compile this driver as a module, choose M here: the module
1967 will be called ipg. This is recommended.
1970 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
1973 This driver supports Intel(R) 82575 gigabit ethernet family of
1974 adapters. For more information on how to identify your adapter, go
1975 to the Adapter & Driver ID Guide at:
1977 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1979 For general information and support, go to the Intel support
1982 <http://support.intel.com>
1984 More specific information on configuring the driver is in
1985 <file:Documentation/networking/e1000.txt>.
1987 To compile this driver as a module, choose M here. The module
1991 bool "Use software LRO"
1992 depends on IGB && INET
1995 Say Y here if you want to use large receive offload.
2000 bool "Direct Cache Access (DCA) Support"
2002 depends on IGB && DCA && !(IGB=y && DCA=m)
2004 Say Y here if you want to use Direct Cache Access (DCA) in the
2005 driver. DCA is a method for warming the CPU cache before data
2006 is used, with the intent of lessening the impact of cache misses.
2008 source "drivers/net/ixp2000/Kconfig"
2011 tristate "MyriCOM Gigabit Ethernet support"
2014 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2016 To compile this driver as a module, choose M here: the module
2017 will be called myri_sbus. This is recommended.
2020 tristate "National Semiconductor DP83820 support"
2023 This is a driver for the National Semiconductor DP83820 series
2024 of gigabit ethernet MACs. Cards using this chipset include
2025 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2026 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2030 tristate "Packet Engines Hamachi GNIC-II support"
2034 If you have a Gigabit Ethernet card of this type, say Y and read
2035 the Ethernet-HOWTO, available from
2036 <http://www.tldp.org/docs.html#howto>.
2038 To compile this driver as a module, choose M here. The module will be
2042 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2043 depends on PCI && EXPERIMENTAL
2046 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2047 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2048 used by the Beowulf Linux cluster project. See
2049 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2050 information about this driver in particular and Beowulf in general.
2052 To compile this driver as a module, choose M here: the module
2053 will be called yellowfin. This is recommended.
2056 tristate "Realtek 8169 gigabit ethernet support"
2061 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2063 To compile this driver as a module, choose M here: the module
2064 will be called r8169. This is recommended.
2068 depends on R8169 && VLAN_8021Q
2070 Say Y here for the r8169 driver to support the functions required
2071 by the kernel 802.1Q code.
2076 tristate "SB1250 Gigabit Ethernet support"
2077 depends on SIBYTE_SB1xxx_SOC
2080 This driver supports Gigabit Ethernet interfaces based on the
2081 Broadcom SiByte family of System-On-a-Chip parts. They include
2082 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2085 To compile this driver as a module, choose M here: the module
2086 will be called sb1250-mac.
2089 tristate "SiS190/SiS191 gigabit ethernet support"
2094 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2095 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2096 appear in lan on motherboard designs which are based on SiS 965
2097 and SiS 966 south bridge.
2099 To compile this driver as a module, choose M here: the module
2100 will be called sis190. This is recommended.
2103 tristate "New SysKonnect GigaEthernet support"
2107 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2108 and related Gigabit Ethernet adapters. It is a new smaller driver
2109 with better performance and more complete ethtool support.
2111 It does not support the link failover and network management
2112 features that "portable" vendor supplied sk98lin driver does.
2114 This driver supports adapters based on the original Yukon chipset:
2115 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2116 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2118 It does not support the newer Yukon2 chipset: a separate driver,
2119 sky2, is provided for Yukon2-based adapters.
2121 To compile this driver as a module, choose M here: the module
2122 will be called skge. This is recommended.
2125 bool "Debugging interface"
2126 depends on SKGE && DEBUG_FS
2128 This option adds the ability to dump driver state for debugging.
2129 The file debugfs/skge/ethX displays the state of the internal
2130 transmit and receive rings.
2135 tristate "SysKonnect Yukon2 support"
2139 This driver supports Gigabit Ethernet adapters based on the
2140 Marvell Yukon 2 chipset:
2141 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2142 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2144 There is companion driver for the older Marvell Yukon and
2145 Genesis based adapters: skge.
2147 To compile this driver as a module, choose M here: the module
2148 will be called sky2. This is recommended.
2151 bool "Debugging interface"
2152 depends on SKY2 && DEBUG_FS
2154 This option adds the ability to dump driver state for debugging.
2155 The file debugfs/sky2/ethX displays the state of the internal
2156 transmit and receive rings.
2161 tristate "VIA Velocity support"
2167 If you have a VIA "Velocity" based network card say Y here.
2169 To compile this driver as a module, choose M here. The module
2170 will be called via-velocity.
2173 tristate "Broadcom Tigon3 support"
2177 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2179 To compile this driver as a module, choose M here: the module
2180 will be called tg3. This is recommended.
2183 tristate "Broadcom NetXtremeII support"
2188 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2190 To compile this driver as a module, choose M here: the module
2191 will be called bnx2. This is recommended.
2194 tristate "Spider Gigabit Ethernet driver"
2195 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2198 This driver supports the Gigabit Ethernet chips present on the
2199 Cell Processor-Based Blades from IBM.
2202 tristate "Tundra TSI108 gigabit Ethernet support"
2203 depends on TSI108_BRIDGE
2205 This driver supports Tundra TSI108 gigabit Ethernet ports.
2206 To compile this driver as a module, choose M here: the module
2207 will be called tsi108_eth.
2210 tristate "PS3 Gigabit Ethernet driver"
2212 select PS3_SYS_MANAGER
2214 This driver supports the network device on the PS3 game
2215 console. This driver has built-in support for Ethernet.
2217 To compile this driver as a module, choose M here: the
2218 module will be called ps3_gelic.
2220 config GELIC_WIRELESS
2221 bool "PS3 Wireless support"
2222 depends on GELIC_NET
2225 This option adds the support for the wireless feature of PS3.
2226 If you have the wireless-less model of PS3 or have no plan to
2227 use wireless feature, disabling this option saves memory. As
2228 the driver automatically distinguishes the models, you can
2229 safely enable this option even if you have a wireless-less model.
2231 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2232 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2233 depends on GELIC_WIRELESS
2235 This option retains the obsolete private interface to pass
2236 the PSK from user space programs to the driver. The PSK
2237 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2238 (WPA-Personal) environment.
2239 If WPA[2]-PSK is used and you need to use old programs that
2240 support only this old interface, say Y. Otherwise N.
2245 tristate "Gianfar Ethernet"
2250 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2251 and MPC86xx family of chips, and the FEC on the 8540.
2254 tristate "Freescale QE Gigabit Ethernet"
2255 depends on QUICC_ENGINE
2258 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2259 which is available on some Freescale SOCs.
2261 config UGETH_MAGIC_PACKET
2262 bool "Magic Packet detection support"
2265 config UGETH_FILTERING
2266 bool "Mac address filtering support"
2269 config UGETH_TX_ON_DEMAND
2270 bool "Transmit on Demand support"
2274 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2275 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2278 This driver supports the gigabit ethernet MACs in the
2279 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2280 in the Marvell Orion ARM SoC family.
2282 Some boards that use the Discovery chipset are the Momenco
2283 Ocelot C and Jaguar ATX and Pegasos II.
2286 tristate "QLogic QLA3XXX Network Driver Support"
2289 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2291 To compile this driver as a module, choose M here: the module
2292 will be called qla3xxx.
2295 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2300 This driver supports the Atheros/Attansic L1 gigabit ethernet
2303 To compile this driver as a module, choose M here. The module
2304 will be called atl1.
2307 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2308 depends on PCI && EXPERIMENTAL
2312 This driver supports the Atheros L1E gigabit ethernet adapter.
2314 To compile this driver as a module, choose M here. The module
2315 will be called atl1e.
2318 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2323 This driver supports the PCI-Express gigabit ethernet adapters
2324 based on JMicron JMC250 chipset.
2326 To compile this driver as a module, choose M here. The module
2332 # 10 Gigabit Ethernet
2335 menuconfig NETDEV_10000
2336 bool "Ethernet (10000 Mbit)"
2340 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2341 This option alone does not add any kernel code.
2343 If you say N, all options in this submenu will be skipped and disabled.
2348 tristate "Chelsio 10Gb Ethernet support"
2352 This driver supports Chelsio gigabit and 10-gigabit
2353 Ethernet cards. More information about adapter features and
2354 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2356 For general information about Chelsio and our products, visit
2357 our website at <http://www.chelsio.com>.
2359 For customer support, please visit our customer support page at
2360 <http://www.chelsio.com/support.htm>.
2362 Please send feedback to <linux-bugs@chelsio.com>.
2364 To compile this driver as a module, choose M here: the module
2365 will be called cxgb.
2367 config CHELSIO_T1_1G
2368 bool "Chelsio gigabit Ethernet support"
2369 depends on CHELSIO_T1
2371 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2372 are using only 10G cards say 'N' here.
2375 tristate "Chelsio Communications T3 10Gb Ethernet support"
2376 depends on PCI && INET
2380 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2383 For general information about Chelsio and our products, visit
2384 our website at <http://www.chelsio.com>.
2386 For customer support, please visit our customer support page at
2387 <http://www.chelsio.com/support.htm>.
2389 Please send feedback to <linux-bugs@chelsio.com>.
2391 To compile this driver as a module, choose M here: the module
2392 will be called cxgb3.
2395 tristate "eHEA Ethernet support"
2396 depends on IBMEBUS && INET && SPARSEMEM
2399 This driver supports the IBM pSeries eHEA ethernet adapter.
2401 To compile the driver as a module, choose M here. The module
2402 will be called ehea.
2405 tristate "Cisco 10G Ethernet NIC support"
2406 depends on PCI && INET
2409 This enables the support for the Cisco 10G Ethernet card.
2412 tristate "Intel(R) 10GbE PCI Express adapters support"
2413 depends on PCI && INET
2416 This driver supports Intel(R) 10GbE PCI Express family of
2417 adapters. For more information on how to identify your adapter, go
2418 to the Adapter & Driver ID Guide at:
2420 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2422 For general information and support, go to the Intel support
2425 <http://support.intel.com>
2427 To compile this driver as a module, choose M here. The module
2428 will be called ixgbe.
2431 bool "Direct Cache Access (DCA) Support"
2433 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2435 Say Y here if you want to use Direct Cache Access (DCA) in the
2436 driver. DCA is a method for warming the CPU cache before data
2437 is used, with the intent of lessening the impact of cache misses.
2440 tristate "Intel(R) PRO/10GbE support"
2443 This driver supports Intel(R) PRO/10GbE family of adapters for
2444 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2445 instead. For more information on how to identify your adapter, go
2446 to the Adapter & Driver ID Guide at:
2448 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2450 For general information and support, go to the Intel support
2453 <http://support.intel.com>
2455 More specific information on configuring the driver is in
2456 <file:Documentation/networking/ixgb.txt>.
2458 To compile this driver as a module, choose M here. The module
2459 will be called ixgb.
2462 tristate "S2IO 10Gbe XFrame NIC"
2465 This driver supports the 10Gbe XFrame NIC of S2IO.
2466 More specific information on configuring the driver is in
2467 <file:Documentation/networking/s2io.txt>.
2470 tristate "Myricom Myri-10G Ethernet support"
2471 depends on PCI && INET
2476 This driver supports Myricom Myri-10G Dual Protocol interface in
2477 Ethernet mode. If the eeprom on your board is not recent enough,
2478 you will need a newer firmware image.
2479 You may get this image or more information, at:
2481 <http://www.myri.com/scs/download-Myri10GE.html>
2483 To compile this driver as a module, choose M here. The module
2484 will be called myri10ge.
2487 bool "Direct Cache Access (DCA) Support"
2489 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2491 Say Y here if you want to use Direct Cache Access (DCA) in the
2492 driver. DCA is a method for warming the CPU cache before data
2493 is used, with the intent of lessening the impact of cache misses.
2496 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2499 This enables the support for NetXen's Gigabit Ethernet card.
2502 tristate "Sun Neptune 10Gbit Ethernet support"
2505 This enables support for cards based upon Sun's
2509 tristate "PA Semi 1/10Gbit MAC"
2510 depends on PPC_PASEMI && PCI
2514 This driver supports the on-chip 1/10Gbit Ethernet controller on
2515 PA Semi's PWRficient line of chips.
2518 tristate "Mellanox Technologies 10Gbit Ethernet support"
2519 depends on PCI && INET
2523 This driver supports Mellanox Technologies ConnectX Ethernet
2532 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2533 depends on MLX4_CORE
2536 This option causes debugging code to be compiled into the
2537 mlx4_core driver. The output can be turned on via the
2538 debug_level module parameter (which can also be set after
2539 the driver is loaded through sysfs).
2542 tristate "Tehuti Networks 10G Ethernet"
2545 Tehuti Networks 10G Ethernet NIC
2548 tristate "Broadcom NetXtremeII 10Gb support"
2553 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2554 To compile this driver as a module, choose M here: the module
2555 will be called bnx2x. This is recommended.
2558 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2561 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2563 To compile this driver as a module, choose M here: the module
2564 will be called qlge.
2566 source "drivers/net/sfc/Kconfig"
2568 endif # NETDEV_10000
2570 source "drivers/net/tokenring/Kconfig"
2572 source "drivers/net/wireless/Kconfig"
2574 source "drivers/net/usb/Kconfig"
2576 source "drivers/net/pcmcia/Kconfig"
2578 source "drivers/net/wan/Kconfig"
2580 source "drivers/atm/Kconfig"
2582 source "drivers/s390/net/Kconfig"
2584 config XEN_NETDEV_FRONTEND
2585 tristate "Xen network device frontend driver"
2589 The network device frontend driver allows the kernel to
2590 access network devices exported exported by a virtual
2591 machine containing a physical network device driver. The
2592 frontend driver is intended for unprivileged guest domains;
2593 if you are compiling a kernel for a Xen guest, you almost
2594 certainly want to enable this.
2597 tristate "iSeries Virtual Ethernet driver support"
2598 depends on PPC_ISERIES
2601 tristate "RapidIO Ethernet over messaging driver support"
2604 config RIONET_TX_SIZE
2605 int "Number of outbound queue entries"
2609 config RIONET_RX_SIZE
2610 int "Number of inbound queue entries"
2615 bool "FDDI driver support"
2616 depends on (PCI || EISA || TC)
2618 Fiber Distributed Data Interface is a high speed local area network
2619 design; essentially a replacement for high speed Ethernet. FDDI can
2620 run over copper or fiber. If you are connected to such a network and
2621 want a driver for the FDDI card in your computer, say Y here (and
2622 then also Y to the driver for your FDDI card, below). Most people
2626 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2627 depends on FDDI && (PCI || EISA || TC)
2629 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2630 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2631 to a local FDDI network.
2633 To compile this driver as a module, choose M here: the module
2634 will be called defxx. If unsure, say N.
2638 prompt "Use MMIO instead of PIO" if PCI || EISA
2640 default n if PCI || EISA
2643 This instructs the driver to use EISA or PCI memory-mapped I/O
2644 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2645 Enabling this gives an improvement in processing time in parts
2646 of the driver, but it may cause problems with EISA (DEFEA)
2647 adapters. TURBOchannel does not have the concept of I/O ports,
2648 so MMIO is always used for these (DEFTA) adapters.
2653 tristate "SysKonnect FDDI PCI support"
2654 depends on FDDI && PCI
2657 Say Y here if you have a SysKonnect FDDI PCI adapter.
2658 The following adapters are supported by this driver:
2659 - SK-5521 (SK-NET FDDI-UP)
2660 - SK-5522 (SK-NET FDDI-UP DAS)
2661 - SK-5541 (SK-NET FDDI-FP)
2662 - SK-5543 (SK-NET FDDI-LP)
2663 - SK-5544 (SK-NET FDDI-LP DAS)
2664 - SK-5821 (SK-NET FDDI-UP64)
2665 - SK-5822 (SK-NET FDDI-UP64 DAS)
2666 - SK-5841 (SK-NET FDDI-FP64)
2667 - SK-5843 (SK-NET FDDI-LP64)
2668 - SK-5844 (SK-NET FDDI-LP64 DAS)
2669 - Netelligent 100 FDDI DAS Fibre SC
2670 - Netelligent 100 FDDI SAS Fibre SC
2671 - Netelligent 100 FDDI DAS UTP
2672 - Netelligent 100 FDDI SAS UTP
2673 - Netelligent 100 FDDI SAS Fibre MIC
2675 Read <file:Documentation/networking/skfp.txt> for information about
2678 Questions concerning this driver can be addressed to:
2679 <linux@syskonnect.de>
2681 To compile this driver as a module, choose M here: the module
2682 will be called skfp. This is recommended.
2685 bool "HIPPI driver support (EXPERIMENTAL)"
2686 depends on EXPERIMENTAL && INET && PCI
2688 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2689 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2690 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2691 single-mode). HIPPI networks are commonly used for clusters and to
2692 connect to super computers. If you are connected to a HIPPI network
2693 and have a HIPPI network card in your computer that you want to use
2694 under Linux, say Y here (you must also remember to enable the driver
2695 for your HIPPI card below). Most people will say N here.
2698 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2699 depends on HIPPI && PCI
2701 Say Y here if this is your PCI HIPPI network card.
2703 To compile this driver as a module, choose M here: the module
2704 will be called rrunner. If unsure, say N.
2706 config ROADRUNNER_LARGE_RINGS
2707 bool "Use large TX/RX rings (EXPERIMENTAL)"
2708 depends on ROADRUNNER
2710 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2711 of additional memory to allow for fastest operation, both for
2712 transmitting and receiving. This memory cannot be used by any other
2713 kernel code or by user space programs. Say Y here only if you have
2717 tristate "PLIP (parallel port) support"
2720 PLIP (Parallel Line Internet Protocol) is used to create a
2721 reasonably fast mini network consisting of two (or, rarely, more)
2722 local machines. A PLIP link from a Linux box is a popular means to
2723 install a Linux distribution on a machine which doesn't have a
2724 CD-ROM drive (a minimal system has to be transferred with floppies
2725 first). The kernels on both machines need to have this PLIP option
2726 enabled for this to work.
2728 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2729 ports (the connectors at the computers with 25 holes) are connected
2730 with "null printer" or "Turbo Laplink" cables which can transmit 4
2731 bits at a time (mode 0) or with special PLIP cables, to be used on
2732 bidirectional parallel ports only, which can transmit 8 bits at a
2733 time (mode 1); you can find the wiring of these cables in
2734 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2735 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2736 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2737 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2738 and winsock or NCSA's telnet.
2740 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2741 as the NET-3-HOWTO, both available from
2742 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2743 protocol has been changed and this PLIP driver won't work together
2744 with the PLIP support in Linux versions 1.0.x. This option enlarges
2745 your kernel by about 8 KB.
2747 To compile this driver as a module, choose M here. The module
2748 will be called plip. If unsure, say Y or M, in case you buy
2752 tristate "PPP (point-to-point protocol) support"
2755 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2756 the same purpose: sending Internet traffic over telephone (and other
2757 serial) lines. Ask your access provider if they support it, because
2758 otherwise you can't use it; most Internet access providers these
2759 days support PPP rather than SLIP.
2761 To use PPP, you need an additional program called pppd as described
2762 in the PPP-HOWTO, available at
2763 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2764 the version of pppd recommended in <file:Documentation/Changes>.
2765 The PPP option enlarges your kernel by about 16 KB.
2767 There are actually two versions of PPP: the traditional PPP for
2768 asynchronous lines, such as regular analog phone lines, and
2769 synchronous PPP which can be used over digital ISDN lines for
2770 example. If you want to use PPP over phone lines or other
2771 asynchronous serial lines, you need to say Y (or M) here and also to
2772 the next option, "PPP support for async serial ports". For PPP over
2773 synchronous lines, you should say Y (or M) here and to "Support
2774 synchronous PPP", below.
2776 If you said Y to "Version information on all symbols" above, then
2777 you cannot compile the PPP driver into the kernel; you can then only
2778 compile it as a module. To compile this driver as a module, choose M
2779 here. The module will be called ppp_generic.
2781 config PPP_MULTILINK
2782 bool "PPP multilink support (EXPERIMENTAL)"
2783 depends on PPP && EXPERIMENTAL
2785 PPP multilink is a protocol (defined in RFC 1990) which allows you
2786 to combine several (logical or physical) lines into one logical PPP
2787 connection, so that you can utilize your full bandwidth.
2789 This has to be supported at the other end as well and you need a
2790 version of the pppd daemon which understands the multilink protocol.
2795 bool "PPP filtering"
2798 Say Y here if you want to be able to filter the packets passing over
2799 PPP interfaces. This allows you to control which packets count as
2800 activity (i.e. which packets will reset the idle timer or bring up
2801 a demand-dialed link) and which packets are to be dropped entirely.
2802 You need to say Y here if you wish to use the pass-filter and
2803 active-filter options to pppd.
2808 tristate "PPP support for async serial ports"
2812 Say Y (or M) here if you want to be able to use PPP over standard
2813 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2814 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2817 To compile this driver as a module, choose M here.
2822 tristate "PPP support for sync tty ports"
2825 Say Y (or M) here if you want to be able to use PPP over synchronous
2826 (HDLC) tty devices, such as the SyncLink adapter. These devices
2827 are often used for high-speed leased lines like T1/E1.
2829 To compile this driver as a module, choose M here.
2832 tristate "PPP Deflate compression"
2837 Support for the Deflate compression method for PPP, which uses the
2838 Deflate algorithm (the same algorithm that gzip uses) to compress
2839 each PPP packet before it is sent over the wire. The machine at the
2840 other end of the PPP link (usually your ISP) has to support the
2841 Deflate compression method as well for this to be useful. Even if
2842 they don't support it, it is safe to say Y here.
2844 To compile this driver as a module, choose M here.
2847 tristate "PPP BSD-Compress compression"
2850 Support for the BSD-Compress compression method for PPP, which uses
2851 the LZW compression method to compress each PPP packet before it is
2852 sent over the wire. The machine at the other end of the PPP link
2853 (usually your ISP) has to support the BSD-Compress compression
2854 method as well for this to be useful. Even if they don't support it,
2855 it is safe to say Y here.
2857 The PPP Deflate compression method ("PPP Deflate compression",
2858 above) is preferable to BSD-Compress, because it compresses better
2861 Note that the BSD compression code will always be compiled as a
2862 module; it is called bsd_comp and will show up in the directory
2863 modules once you have said "make modules". If unsure, say N.
2866 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2867 depends on PPP && EXPERIMENTAL
2873 Support for the MPPE Encryption protocol, as employed by the
2874 Microsoft Point-to-Point Tunneling Protocol.
2876 See http://pptpclient.sourceforge.net/ for information on
2877 configuring PPTP clients and servers to utilize this method.
2880 tristate "PPP over Ethernet (EXPERIMENTAL)"
2881 depends on EXPERIMENTAL && PPP
2883 Support for PPP over Ethernet.
2885 This driver requires the latest version of pppd from the CVS
2886 repository at cvs.samba.org. Alternatively, see the
2887 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2888 which contains instruction on how to use this driver (under
2889 the heading "Kernel mode PPPoE").
2892 tristate "PPP over ATM"
2893 depends on ATM && PPP
2895 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2896 This implementation does not yet comply with section 8 of RFC2364,
2897 which can lead to bad results if the ATM peer loses state and
2898 changes its encapsulation unilaterally.
2901 tristate "PPP over L2TP (EXPERIMENTAL)"
2902 depends on EXPERIMENTAL && PPP && INET
2904 Support for PPP-over-L2TP socket family. L2TP is a protocol
2905 used by ISPs and enterprises to tunnel PPP traffic over UDP
2906 tunnels. L2TP is replacing PPTP for VPN uses.
2908 This kernel component handles only L2TP data packets: a
2909 userland daemon handles L2TP the control protocol (tunnel
2910 and session setup). One such daemon is OpenL2TP
2911 (http://openl2tp.sourceforge.net/).
2914 tristate "SLIP (serial line) support"
2916 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2917 connect to your Internet service provider or to connect to some
2918 other local Unix box or if you want to configure your Linux box as a
2919 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2920 Internet Protocol) is a protocol used to send Internet traffic over
2921 serial connections such as telephone lines or null modem cables;
2922 nowadays, the protocol PPP is more commonly used for this same
2925 Normally, your access provider has to support SLIP in order for you
2926 to be able to use it, but there is now a SLIP emulator called SLiRP
2927 around (available from
2928 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2929 allows you to use SLIP over a regular dial up shell connection. If
2930 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2931 NET-3-HOWTO, available from
2932 <http://www.tldp.org/docs.html#howto>, explains how to
2933 configure SLIP. Note that you don't need this option if you just
2934 want to run term (term is a program which gives you almost full
2935 Internet connectivity if you have a regular dial up shell account on
2936 some Internet connected Unix computer. Read
2937 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2938 support will enlarge your kernel by about 4 KB. If unsure, say N.
2940 To compile this driver as a module, choose M here. The module
2941 will be called slip.
2943 config SLIP_COMPRESSED
2944 bool "CSLIP compressed headers"
2948 This protocol is faster than SLIP because it uses compression on the
2949 TCP/IP headers (not on the data itself), but it has to be supported
2950 on both ends. Ask your access provider if you are not sure and
2951 answer Y, just in case. You will still be able to use plain SLIP. If
2952 you plan to use SLiRP, the SLIP emulator (available from
2953 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2954 allows you to use SLIP over a regular dial up shell connection, you
2955 definitely want to say Y here. The NET-3-HOWTO, available from
2956 <http://www.tldp.org/docs.html#howto>, explains how to configure
2957 CSLIP. This won't enlarge your kernel.
2962 This option enables Van Jacobsen serial line header compression
2966 bool "Keepalive and linefill"
2969 Adds additional capabilities to the SLIP driver to support the
2970 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2973 config SLIP_MODE_SLIP6
2974 bool "Six bit SLIP encapsulation"
2977 Just occasionally you may need to run IP over hostile serial
2978 networks that don't pass all control characters or are only seven
2979 bit. Saying Y here adds an extra mode you can use with SLIP:
2980 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2981 the serial device. Naturally, this has to be supported at the other
2982 end of the link as well. It's good enough, for example, to run IP
2983 over the async ports of a Camtec JNT Pad. If unsure, say N.
2986 bool "Fibre Channel driver support"
2987 depends on SCSI && PCI
2989 Fibre Channel is a high speed serial protocol mainly used to connect
2990 large storage devices to the computer; it is compatible with and
2991 intended to replace SCSI.
2993 If you intend to use Fibre Channel, you need to have a Fibre channel
2994 adaptor card in your computer; say Y here and to the driver for your
2995 adaptor below. You also should have said Y to "SCSI support" and
2996 "SCSI generic support".
2999 tristate "Network console logging support (EXPERIMENTAL)"
3000 depends on EXPERIMENTAL
3002 If you want to log kernel messages over the network, enable this.
3003 See <file:Documentation/networking/netconsole.txt> for details.
3005 config NETCONSOLE_DYNAMIC
3006 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3007 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3010 This option enables the ability to dynamically reconfigure target
3011 parameters (interface, IP addresses, port numbers, MAC addresses)
3012 at runtime through a userspace interface exported using configfs.
3013 See <file:Documentation/networking/netconsole.txt> for details.
3019 bool "Netpoll traffic trapping"
3023 config NET_POLL_CONTROLLER
3027 tristate "Virtio network driver (EXPERIMENTAL)"
3028 depends on EXPERIMENTAL && VIRTIO
3030 This is the virtual network driver for virtio. It can be used with
3031 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.