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"
64 depends on IPV6 || IPV6=n
66 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
67 Channels together. This is called 'Etherchannel' by Cisco,
68 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
70 The driver supports multiple bonding modes to allow for both high
71 performance and high availability operation.
73 Refer to <file:Documentation/networking/bonding.txt> for more
76 To compile this driver as a module, choose M here: the module
77 will be called bonding.
80 tristate "MAC-VLAN support (EXPERIMENTAL)"
81 depends on EXPERIMENTAL
83 This allows one to create virtual interfaces that map packets to
84 or from specific MAC addresses to a particular interface.
86 Macvlan devices can be added using the "ip" command from the
87 iproute2 package starting with the iproute2-2.6.23 release:
89 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
91 To compile this driver as a module, choose M here: the module
92 will be called macvlan.
95 tristate "EQL (serial line load balancing) support"
97 If you have two serial connections to some other computer (this
98 usually requires two modems and two telephone lines) and you use
99 SLIP (the protocol for sending Internet traffic over telephone
100 lines) or PPP (a better SLIP) on them, you can make them behave like
101 one double speed connection using this driver. Naturally, this has
102 to be supported at the other end as well, either with a similar EQL
103 Linux driver or with a Livingston Portmaster 2e.
105 Say Y if you want this and read
106 <file:Documentation/networking/eql.txt>. You may also want to read
107 section 6.2 of the NET-3-HOWTO, available from
108 <http://www.tldp.org/docs.html#howto>.
110 To compile this driver as a module, choose M here: the module
111 will be called eql. If unsure, say N.
114 tristate "Universal TUN/TAP device driver support"
117 TUN/TAP provides packet reception and transmission for user space
118 programs. It can be viewed as a simple Point-to-Point or Ethernet
119 device, which instead of receiving packets from a physical media,
120 receives them from user space program and instead of sending packets
121 via physical media writes them to the user space program.
123 When a program opens /dev/net/tun, driver creates and registers
124 corresponding net device tunX or tapX. After a program closed above
125 devices, driver will automatically delete tunXX or tapXX device and
126 all routes corresponding to it.
128 Please read <file:Documentation/networking/tuntap.txt> for more
131 To compile this driver as a module, choose M here: the module
134 If you don't know what to use this for, you don't need it.
137 tristate "Virtual ethernet pair device"
139 This device is a local ethernet tunnel. Devices are created in pairs.
140 When one end receives the packet it appears on its pair and vice
144 tristate "General Instruments Surfboard 1000"
147 This is a driver for the General Instrument (also known as
148 NextLevel) SURFboard 1000 internal
149 cable modem. This is an ISA card which is used by a number of cable
150 TV companies to provide cable modem access. It's a one-way
151 downstream-only cable modem, meaning that your upstream net link is
152 provided by your regular phone modem.
154 At present this driver only compiles as a module, so say M here if
155 you have this card. The module will be called sb1000. Then read
156 <file:Documentation/networking/README.sb1000> for information on how
157 to use this module, as it needs special ppp scripts for establishing
158 a connection. Further documentation and the necessary scripts can be
161 <http://www.jacksonville.net/~fventuri/>
162 <http://home.adelphia.net/~siglercm/sb1000.html>
163 <http://linuxpower.cx/~cable/>
165 If you don't have this card, of course say N.
167 source "drivers/net/arcnet/Kconfig"
169 source "drivers/net/phy/Kconfig"
175 menuconfig NET_ETHERNET
176 bool "Ethernet (10 or 100Mbit)"
179 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
180 type of Local Area Network (LAN) in universities and companies.
182 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
183 coaxial cable, linking computers in a chain), 10BASE-T or twisted
184 pair (10 Mbps over twisted pair cable, linking computers to central
185 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
186 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
187 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
188 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
189 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
190 Ethernet (1 Gbps over optical fiber or short copper links).
192 If your Linux machine will be connected to an Ethernet and you have
193 an Ethernet network interface card (NIC) installed in your computer,
194 say Y here and read the Ethernet-HOWTO, available from
195 <http://www.tldp.org/docs.html#howto>. You will then also have
196 to say Y to the driver for your particular NIC.
198 Note that the answer to this question won't directly affect the
199 kernel: saying N will just cause the configurator to skip all
200 the questions about Ethernet network cards. If unsure, say N.
205 tristate "Generic Media Independent Interface device support"
207 Most ethernet controllers have MII transceiver either as an external
208 or internal device. It is safe to say Y or M here even if your
209 ethernet card lack MII.
212 tristate "Atmel MACB support"
213 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
216 The Atmel MACB ethernet interface is found on many AT32 and AT91
217 parts. Say Y to include support for the MACB chip.
219 To compile this driver as a module, choose M here: the module
222 source "drivers/net/arm/Kconfig"
225 tristate "ASIX AX88796 NE2000 clone support"
226 depends on ARM || MIPS || SUPERH
230 AX88796 driver, using platform bus to provide
231 chip detection and resources
234 bool "ASIX AX88796 external 93CX6 eeprom support"
238 Select this if your platform comes with an external 93CX6 eeprom.
241 tristate "MACE (Power Mac ethernet) support"
242 depends on PPC_PMAC && PPC32
245 Power Macintoshes and clones with Ethernet built-in on the
246 motherboard will usually use a MACE (Medium Access Control for
247 Ethernet) interface. Say Y to include support for the MACE chip.
249 To compile this driver as a module, choose M here: the module
252 config MACE_AAUI_PORT
253 bool "Use AAUI port instead of TP by default"
256 Some Apple machines (notably the Apple Network Server) which use the
257 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
258 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
259 Y here if you have such a machine. If unsure, say N.
260 The driver will default to AAUI on ANS anyway, and if you use it as
261 a module, you can provide the port_aaui=0|1 to force the driver.
264 tristate "BMAC (G3 ethernet) support"
265 depends on PPC_PMAC && PPC32
268 Say Y for support of BMAC Ethernet interfaces. These are used on G3
271 To compile this driver as a module, choose M here: the module
275 tristate "Ariadne support"
278 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
281 To compile this driver as a module, choose M here: the module
282 will be called ariadne.
285 tristate "A2065 support"
289 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
292 To compile this driver as a module, choose M here: the module
293 will be called a2065.
296 tristate "Hydra support"
300 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
302 To compile this driver as a module, choose M here: the module
303 will be called hydra.
306 tristate "Zorro NS8390-based Ethernet support"
310 This driver is for Zorro Ethernet cards using an NS8390-compatible
311 chipset, like the Village Tronic Ariadne II and the Individual
312 Computers X-Surf Ethernet cards. If you have such a card, say Y.
315 To compile this driver as a module, choose M here: the module
316 will be called zorro8390.
319 tristate "PCMCIA NE2000 support"
320 depends on AMIGA_PCMCIA
323 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
326 To compile this driver as a module, choose M here: the module
330 bool "Macintosh NS 8390 based ethernet cards"
334 If you want to include a driver to support Nubus or LC-PDS
335 Ethernet cards using an NS8390 chipset or its equivalent, say Y
336 and read the Ethernet-HOWTO, available from
337 <http://www.tldp.org/docs.html#howto>.
340 tristate "Macintosh CS89x0 based ethernet cards"
343 Support for CS89x0 chipset based Ethernet cards. If you have a
344 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
345 read the Ethernet-HOWTO, available from
346 <http://www.tldp.org/docs.html#howto>.
348 To compile this driver as a module, choose M here. This module will
352 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
355 Support for NatSemi SONIC based Ethernet devices. This includes
356 the onboard Ethernet in many Quadras as well as some LC-PDS,
357 a few Nubus and all known Comm Slot Ethernet cards. If you have
358 one of these say Y and read the Ethernet-HOWTO, available from
359 <http://www.tldp.org/docs.html#howto>.
361 To compile this driver as a module, choose M here. This module will
365 bool "Macintosh (AV) onboard MACE ethernet"
369 Support for the onboard AMD 79C940 MACE Ethernet controller used in
370 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
371 say Y and read the Ethernet-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>.
375 tristate "MVME147 (Lance) Ethernet support"
379 Support for the on-board Ethernet interface on the Motorola MVME147
380 single-board computer. Say Y here to include the
381 driver for this chip in your kernel.
382 To compile this driver as a module, choose M here.
385 tristate "MVME16x Ethernet support"
388 This is the driver for the Ethernet interface on the Motorola
389 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
390 driver for this chip in your kernel.
391 To compile this driver as a module, choose M here.
394 tristate "BVME6000 Ethernet support"
397 This is the driver for the Ethernet interface on BVME4000 and
398 BVME6000 VME boards. Say Y here to include the driver for this chip
400 To compile this driver as a module, choose M here.
403 tristate "Atari Lance support"
406 Say Y to include support for several Atari Ethernet adapters based
407 on the AMD Lance chipset: RieblCard (with or without battery), or
408 PAMCard VME (also the version by Rhotron, with different addresses).
411 tristate "Sun3/Sun3x on-board LANCE support"
412 depends on SUN3 || SUN3X
414 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
415 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
416 here to compile in the Linux driver for this and enable Ethernet.
417 General Linux information on the Sun 3 and 3x series (now
419 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
421 If you're not building a kernel for a Sun 3, say N.
424 bool "Sun3 on-board Intel 82586 support"
427 This driver enables support for the on-board Intel 82586 based
428 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
429 that this driver does not support 82586-based adapters on additional
433 bool "HP on-board LANCE support"
437 If you want to use the builtin "LANCE" Ethernet controller on an
438 HP300 machine, say Y here.
441 tristate "Lasi ethernet"
444 Say Y here to support the builtin Intel 82596 ethernet controller
445 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
448 tristate "SNI RM ethernet"
449 depends on NET_ETHERNET && SNI_RM
451 Say Y here to support the on-board Intel 82596 ethernet controller
452 built into SNI RM machines.
455 tristate "Korina (IDT RC32434) Ethernet support"
456 depends on NET_ETHERNET && MIKROTIK_RB532
458 If you have a Mikrotik RouterBoard 500 or IDT RC32434
459 based system say Y. Otherwise say N.
461 config MIPS_JAZZ_SONIC
462 tristate "MIPS JAZZ onboard SONIC Ethernet support"
465 This is the driver for the onboard card of MIPS Magnum 4000,
466 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
468 config XTENSA_XT2000_SONIC
469 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
470 depends on XTENSA_PLATFORM_XT2000
472 This is the driver for the onboard card of the Xtensa XT2000 board.
474 config MIPS_AU1X00_ENET
475 bool "MIPS AU1000 Ethernet support"
476 depends on SOC_AU1X00
480 If you have an Alchemy Semi AU1X00 based system
481 say Y. Otherwise, say N.
484 bool "SGI IOC3 Ethernet"
485 depends on PCI && SGI_IP27
489 If you have a network (Ethernet) card of this type, say Y and read
490 the Ethernet-HOWTO, available from
491 <http://www.tldp.org/docs.html#howto>.
494 tristate "MIPS simulator Network device"
497 The MIPSNET device is a simple Ethernet network device which is
498 emulated by the MIPS Simulator.
499 If you are not using a MIPSsim or are unsure, say N.
501 config SGI_O2MACE_ETH
502 tristate "SGI O2 MACE Fast Ethernet support"
503 depends on SGI_IP32=y
506 tristate "National DP83902AV support"
510 Support for cards based on the National Semiconductor DP83902AV
511 ST-NIC Serial Network Interface Controller for Twisted Pair. This
512 is a 10Mbit/sec Ethernet controller. Product overview and specs at
513 <http://www.national.com/pf/DP/DP83902A.html>.
518 tristate "Renesas SuperH Ethernet support"
519 depends on SUPERH && \
520 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
527 Renesas SuperH Ethernet device driver.
528 This driver support SH7710, SH7712, SH7763 and SH7619.
531 tristate "Sun LANCE support"
535 This driver supports the "le" interface present on all 32-bit Sparc
536 systems, on some older Ultra systems and as an Sbus option. These
537 cards are based on the AMD Lance chipset, which is better known
538 via the NE2100 cards.
540 To compile this driver as a module, choose M here: the module
541 will be called sunlance.
544 tristate "Sun Happy Meal 10/100baseT support"
545 depends on SBUS || PCI
548 This driver supports the "hme" interface present on most Ultra
549 systems and as an option on older Sbus systems. This driver supports
550 both PCI and Sbus devices. This driver also supports the "qfe" quad
551 100baseT device available in both PCI and Sbus configurations.
553 To compile this driver as a module, choose M here: the module
554 will be called sunhme.
557 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
558 depends on SBUS && EXPERIMENTAL
561 This driver supports the "be" interface available as an Sbus option.
562 This is Sun's older 100baseT Ethernet device.
564 To compile this driver as a module, choose M here: the module
565 will be called sunbmac.
568 tristate "Sun QuadEthernet support"
572 This driver supports the "qe" 10baseT Ethernet device, available as
573 an Sbus option. Note that this is not the same as Quad FastEthernet
574 "qfe" which is supported by the Happy Meal driver instead.
576 To compile this driver as a module, choose M here: the module
577 will be called sunqe.
580 tristate "Sun GEM support"
584 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
585 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
588 tristate "Sun Cassini support"
592 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
593 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
596 tristate "Sun Virtual Network support"
599 Support for virtual network devices under Sun Logical Domains.
601 config NET_VENDOR_3COM
603 depends on ISA || EISA || MCA || PCI
605 If you have a network (Ethernet) card belonging to this class, say Y
606 and read the Ethernet-HOWTO, available from
607 <http://www.tldp.org/docs.html#howto>.
609 Note that the answer to this question doesn't directly affect the
610 kernel: saying N will just cause the configurator to skip all
611 the questions about 3COM cards. If you say Y, you will be asked for
612 your specific card in the following questions.
615 tristate "3c501 \"EtherLink\" support"
616 depends on NET_VENDOR_3COM && ISA
618 If you have a network (Ethernet) card of this type, say Y and read
619 the Ethernet-HOWTO, available from
620 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
621 new card, since the 3c501 is slow, broken, and obsolete: you will
622 have problems. Some people suggest to ping ("man ping") a nearby
623 machine every minute ("man cron") when using this card.
625 To compile this driver as a module, choose M here. The module
626 will be called 3c501.
629 tristate "3c503 \"EtherLink II\" support"
630 depends on NET_VENDOR_3COM && ISA
633 If you have a network (Ethernet) card of this type, say Y and read
634 the Ethernet-HOWTO, available from
635 <http://www.tldp.org/docs.html#howto>.
637 To compile this driver as a module, choose M here. The module
638 will be called 3c503.
641 tristate "3c505 \"EtherLink Plus\" support"
642 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
644 Information about this network (Ethernet) card can be found in
645 <file:Documentation/networking/3c505.txt>. If you have a card of
646 this type, say Y and read the Ethernet-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here. The module
650 will be called 3c505.
653 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
654 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
656 If you have a network (Ethernet) card of this type, say Y and read
657 the Ethernet-HOWTO, available from
658 <http://www.tldp.org/docs.html#howto>.
660 To compile this driver as a module, choose M here. The module
661 will be called 3c507.
664 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
665 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
667 If you have a network (Ethernet) card belonging to the 3Com
668 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
669 from <http://www.tldp.org/docs.html#howto>.
671 If your card is not working you may need to use the DOS
672 setup disk to disable Plug & Play mode, and to select the default
675 To compile this driver as a module, choose M here. The module
676 will be called 3c509.
679 tristate "3c515 ISA \"Fast EtherLink\""
680 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
682 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
683 network card, say Y and read the Ethernet-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>.
686 To compile this driver as a module, choose M here. The module
687 will be called 3c515.
690 tristate "3c523 \"EtherLink/MC\" support"
691 depends on NET_VENDOR_3COM && MCA_LEGACY
693 If you have a network (Ethernet) card of this type, say Y and read
694 the Ethernet-HOWTO, available from
695 <http://www.tldp.org/docs.html#howto>.
697 To compile this driver as a module, choose M here. The module
698 will be called 3c523.
701 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
702 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
704 If you have a network (Ethernet) card of this type, say Y and read
705 the Ethernet-HOWTO, available from
706 <http://www.tldp.org/docs.html#howto>.
708 To compile this driver as a module, choose M here. The module
709 will be called 3c527.
712 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
713 depends on NET_VENDOR_3COM && (PCI || EISA)
716 This option enables driver support for a large number of 10Mbps and
717 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
719 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
720 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
721 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
722 "Tornado" (3c905) PCI
723 "Hurricane" (3c555/3cSOHO) PCI
725 If you have such a card, say Y and read the Ethernet-HOWTO,
726 available from <http://www.tldp.org/docs.html#howto>. More
727 specific information is in
728 <file:Documentation/networking/vortex.txt> and in the comments at
729 the beginning of <file:drivers/net/3c59x.c>.
731 To compile this support as a module, choose M here.
734 tristate "3cr990 series \"Typhoon\" support"
735 depends on NET_VENDOR_3COM && PCI
738 This option enables driver support for the 3cr990 series of cards:
740 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
741 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
742 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
744 If you have a network (Ethernet) card of this type, say Y and read
745 the Ethernet-HOWTO, available from
746 <http://www.tldp.org/docs.html#howto>.
748 To compile this driver as a module, choose M here. The module
749 will be called typhoon.
752 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
753 depends on ISA && ISA_DMA_API
755 If you have a network (Ethernet) card of this type, say Y and read
756 the Ethernet-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
760 To compile this driver as a module, choose M here: the module
761 will be called lance. This is recommended.
763 config NET_VENDOR_SMC
764 bool "Western Digital/SMC cards"
765 depends on ISA || MCA || EISA || MAC
767 If you have a network (Ethernet) card belonging to this class, say Y
768 and read the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>.
771 Note that the answer to this question doesn't directly affect the
772 kernel: saying N will just cause the configurator to skip all
773 the questions about Western Digital cards. If you say Y, you will be
774 asked for your specific card in the following questions.
777 tristate "WD80*3 support"
778 depends on NET_VENDOR_SMC && ISA
781 If you have a network (Ethernet) card of this type, say Y and read
782 the Ethernet-HOWTO, available from
783 <http://www.tldp.org/docs.html#howto>.
785 To compile this driver as a module, choose M here. The module
789 tristate "SMC Ultra MCA support"
790 depends on NET_VENDOR_SMC && MCA
793 If you have a network (Ethernet) card of this type and are running
794 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
795 available from <http://www.tldp.org/docs.html#howto>.
797 To compile this driver as a module, choose M here. The module
798 will be called smc-mca.
801 tristate "SMC Ultra support"
802 depends on NET_VENDOR_SMC && ISA
805 If you have a network (Ethernet) card of this type, say Y and read
806 the Ethernet-HOWTO, available from
807 <http://www.tldp.org/docs.html#howto>.
809 Important: There have been many reports that, with some motherboards
810 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
811 such as some BusLogic models) causes corruption problems with many
812 operating systems. The Linux smc-ultra driver has a work-around for
813 this but keep it in mind if you have such a SCSI card and have
816 To compile this driver as a module, choose M here. The module
817 will be called smc-ultra.
820 tristate "SMC Ultra32 EISA support"
821 depends on NET_VENDOR_SMC && EISA
824 If you have a network (Ethernet) card of this type, say Y and read
825 the Ethernet-HOWTO, available from
826 <http://www.tldp.org/docs.html#howto>.
828 To compile this driver as a module, choose M here. The module
829 will be called smc-ultra32.
832 tristate "Blackfin on-chip MAC support"
833 depends on NET_ETHERNET && (BF526 || BF527 || BF536 || BF537)
837 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
839 This is the driver for Blackfin on-chip mac device. Say Y if you want it
840 compiled into the kernel. This driver is also available as a module
841 ( = code which can be inserted in and removed from the running kernel
842 whenever you want). The module will be called bfin_mac.
844 config BFIN_MAC_USE_L1
845 bool "Use L1 memory for rx/tx packets"
846 depends on BFIN_MAC && (BF527 || BF537)
849 To get maximum network performance, you should use L1 memory as rx/tx buffers.
850 Say N here if you want to reserve L1 memory for other uses.
852 config BFIN_TX_DESC_NUM
853 int "Number of transmit buffer packets"
855 range 6 10 if BFIN_MAC_USE_L1
859 Set the number of buffer packets used in driver.
861 config BFIN_RX_DESC_NUM
862 int "Number of receive buffer packets"
864 range 20 100 if BFIN_MAC_USE_L1
868 Set the number of buffer packets used in driver.
871 bool "RMII PHY Interface (EXPERIMENTAL)"
872 depends on BFIN_MAC && EXPERIMENTAL
873 default y if BFIN527_EZKIT
874 default n if BFIN537_STAMP
876 Use Reduced PHY MII Interface
879 tristate "SMC 9194 support"
880 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
883 This is support for the SMC9xxx based Ethernet cards. Choose this
884 option if you have a DELL laptop with the docking station, or
885 another SMC9192/9194 based chipset. Say Y if you want it compiled
886 into the kernel, and read the file
887 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
888 available from <http://www.tldp.org/docs.html#howto>.
890 To compile this driver as a module, choose M here. The module
891 will be called smc9194.
894 tristate "SMC 91C9x/91C1xxx support"
897 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
898 MIPS || BLACKFIN || MN10300
900 This is a driver for SMC's 91x series of Ethernet chipsets,
901 including the SMC91C94 and the SMC91C111. Say Y if you want it
902 compiled into the kernel, and read the file
903 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
904 available from <http://www.linuxdoc.org/docs.html#howto>.
906 This driver is also available as a module ( = code which can be
907 inserted in and removed from the running kernel whenever you want).
908 The module will be called smc91x. If you want to compile it as a
909 module, say M here and read <file:Documentation/kbuild/modules.txt>.
912 tristate "NetX Ethernet support"
916 This is support for the Hilscher netX builtin Ethernet ports
918 To compile this driver as a module, choose M here. The module
919 will be called netx-eth.
922 tristate "DM9000 support"
923 depends on ARM || BLACKFIN || MIPS
927 Support for DM9000 chipset.
929 To compile this driver as a module, choose M here. The module
930 will be called dm9000.
932 config DM9000_DEBUGLEVEL
933 int "DM9000 maximum debug level"
937 The maximum level of debugging code compiled into the DM9000
940 config DM9000_FORCE_SIMPLE_PHY_POLL
941 bool "Force simple NSR based PHY polling"
944 This configuration forces the DM9000 to use the NSR's LinkStatus
945 bit to determine if the link is up or down instead of the more
946 costly MII PHY reads. Note, this will not work if the chip is
947 operating with an external PHY.
950 tristate "ENC28J60 support"
951 depends on EXPERIMENTAL && SPI && NET_ETHERNET
954 Support for the Microchip EN28J60 ethernet chip.
956 To compile this driver as a module, choose M here. The module will be
959 config ENC28J60_WRITEVERIFY
960 bool "Enable write verify"
963 Enable the verify after the buffer write useful for debugging purpose.
967 tristate "SMSC LAN911[5678] support"
970 depends on ARM || SUPERH
972 This is a driver for SMSC's LAN911x series of Ethernet chipsets
973 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
974 Say Y if you want it compiled into the kernel,
975 and read the Ethernet-HOWTO, available from
976 <http://www.linuxdoc.org/docs.html#howto>.
978 This driver is also available as a module. The module will be
979 called smc911x. If you want to compile it as a module, say M
980 here and read <file:Documentation/kbuild/modules.txt>
982 config NET_VENDOR_RACAL
983 bool "Racal-Interlan (Micom) NI cards"
986 If you have a network (Ethernet) card belonging to this class, such
987 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
988 available from <http://www.tldp.org/docs.html#howto>.
990 Note that the answer to this question doesn't directly affect the
991 kernel: saying N will just cause the configurator to skip all
992 the questions about NI cards. If you say Y, you will be asked for
993 your specific card in the following questions.
996 tristate "NI5010 support (EXPERIMENTAL)"
997 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
999 If you have a network (Ethernet) card of this type, say Y and read
1000 the Ethernet-HOWTO, available from
1001 <http://www.tldp.org/docs.html#howto>. Note that this is still
1004 To compile this driver as a module, choose M here. The module
1005 will be called ni5010.
1008 tristate "NI5210 support"
1009 depends on NET_VENDOR_RACAL && ISA
1011 If you have a network (Ethernet) card of this type, say Y and read
1012 the Ethernet-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
1015 To compile this driver as a module, choose M here. The module
1016 will be called ni52.
1019 tristate "NI6510 support"
1020 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1022 If you have a network (Ethernet) card of this type, say Y and read
1023 the Ethernet-HOWTO, available from
1024 <http://www.tldp.org/docs.html#howto>.
1026 To compile this driver as a module, choose M here. The module
1027 will be called ni65.
1029 source "drivers/net/tulip/Kconfig"
1032 tristate "AT1700/1720 support (EXPERIMENTAL)"
1033 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1036 If you have a network (Ethernet) card of this type, say Y and read
1037 the Ethernet-HOWTO, available from
1038 <http://www.tldp.org/docs.html#howto>.
1040 To compile this driver as a module, choose M here. The module
1041 will be called at1700.
1044 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1045 depends on ISA || EISA || MCA
1048 If you have a network (Ethernet) card of this type, say Y and read
1049 the Ethernet-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto> as well as
1051 <file:drivers/net/depca.c>.
1053 To compile this driver as a module, choose M here. The module
1054 will be called depca.
1057 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1058 depends on ISA || EISA || PCI
1060 If you have a network (Ethernet) card of this type, say Y and read
1061 the Ethernet-HOWTO, available from
1062 <http://www.tldp.org/docs.html#howto>.
1064 To compile this driver as a module, choose M here. The module
1065 will be called hp100.
1068 bool "Other ISA cards"
1071 If your network (Ethernet) card hasn't been mentioned yet and its
1072 bus system (that's the way the cards talks to the other components
1073 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1074 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1075 available from <http://www.tldp.org/docs.html#howto>.
1079 Note that the answer to this question doesn't directly affect the
1080 kernel: saying N will just cause the configurator to skip all
1081 the remaining ISA network card questions. If you say Y, you will be
1082 asked for your specific card in the following questions.
1085 tristate "Cabletron E21xx support"
1089 If you have a network (Ethernet) card of this type, say Y and read
1090 the Ethernet-HOWTO, available from
1091 <http://www.tldp.org/docs.html#howto>.
1093 To compile this driver as a module, choose M here. The module
1094 will be called e2100.
1097 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1101 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1102 cards. If this is for you, say Y and read
1103 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1104 well as the Ethernet-HOWTO, available from
1105 <http://www.tldp.org/docs.html#howto>.
1107 To compile this driver as a module, choose M here. The module
1108 will be called ewrk3.
1111 tristate "EtherExpress 16 support"
1114 If you have an EtherExpress16 network (Ethernet) card, say Y and
1115 read the Ethernet-HOWTO, available from
1116 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1117 EtherExpress16 card used to be regarded as a very poor choice
1118 because the driver was very unreliable. We now have a new driver
1119 that should do better.
1121 To compile this driver as a module, choose M here. The module
1122 will be called eexpress.
1125 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1128 If you have a network (Ethernet) card of this type, say Y. This
1129 driver supports Intel i82595{FX,TX} based boards. Note however
1130 that the EtherExpress PRO/100 Ethernet card has its own separate
1131 driver. Please read the Ethernet-HOWTO, available from
1132 <http://www.tldp.org/docs.html#howto>.
1134 To compile this driver as a module, choose M here. The module
1135 will be called eepro.
1138 tristate "HP PCLAN+ (27247B and 27252A) support"
1142 If you have a network (Ethernet) card of this type, say Y and read
1143 the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1146 To compile this driver as a module, choose M here. The module
1147 will be called hp-plus.
1150 tristate "HP PCLAN (27245 and other 27xxx series) support"
1154 If you have a network (Ethernet) card of this type, say Y and read
1155 the Ethernet-HOWTO, available from
1156 <http://www.tldp.org/docs.html#howto>.
1158 To compile this driver as a module, choose M here. The module
1162 tristate "LP486E on board Ethernet"
1165 Say Y here to support the 82596-based on-board Ethernet controller
1166 for the Panther motherboard, which is one of the two shipped in the
1167 Intel Professional Workstation.
1170 tristate "ICL EtherTeam 16i/32 support"
1173 If you have a network (Ethernet) card of this type, say Y and read
1174 the Ethernet-HOWTO, available from
1175 <http://www.tldp.org/docs.html#howto>.
1177 To compile this driver as a module, choose M here. The module
1178 will be called eth16i.
1181 tristate "NE2000/NE1000 support"
1182 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1185 If you have a network (Ethernet) card of this type, say Y and read
1186 the Ethernet-HOWTO, available from
1187 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1188 without a specific driver are compatible with NE2000.
1190 If you have a PCI NE2000 card however, say N here and Y to "PCI
1191 NE2000 and clone support" under "EISA, VLB, PCI and on board
1192 controllers" below. If you have a NE2000 card and are running on
1193 an MCA system (a bus system used on some IBM PS/2 computers and
1194 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1197 To compile this driver as a module, choose M here. The module
1201 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1202 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1204 The Zenith Z-Note notebook computer has a built-in network
1205 (Ethernet) card, and this is the Linux driver for it. Note that the
1206 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1207 by this driver. Read the Ethernet-HOWTO, available from
1208 <http://www.tldp.org/docs.html#howto>.
1211 tristate "SEEQ8005 support (EXPERIMENTAL)"
1212 depends on NET_ISA && EXPERIMENTAL
1214 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1215 is for you, read the Ethernet-HOWTO, available from
1216 <http://www.tldp.org/docs.html#howto>.
1218 To compile this driver as a module, choose M here. The module
1219 will be called seeq8005.
1222 tristate "NE/2 (ne2000 MCA version) support"
1223 depends on MCA_LEGACY
1226 If you have a network (Ethernet) card of this type, say Y and read
1227 the Ethernet-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here. The module
1234 tristate "IBM LAN Adapter/A support"
1237 This is a Micro Channel Ethernet adapter. You need to set
1238 CONFIG_MCA to use this driver. It is both available as an in-kernel
1239 driver and as a module.
1241 To compile this driver as a module, choose M here. The only
1242 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1243 will both support 16K and 32K memory windows, however a 32K window
1244 gives a better security against packet losses. Usage of multiple
1245 boards with this driver should be possible, but has not been tested
1246 up to now due to lack of hardware.
1249 tristate "IBM LAN Virtual Ethernet support"
1250 depends on PPC_PSERIES
1252 This driver supports virtual ethernet adapters on newer IBM iSeries
1253 and pSeries systems.
1255 To compile this driver as a module, choose M here. The module will
1258 source "drivers/net/ibm_newemac/Kconfig"
1261 bool "EISA, VLB, PCI and on board controllers"
1262 depends on ISA || EISA || PCI
1264 This is another class of network cards which attach directly to the
1265 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1266 available from <http://www.tldp.org/docs.html#howto>.
1268 Note that the answer to this question doesn't directly affect the
1269 kernel: saying N will just cause the configurator to skip all
1270 the questions about this class of network cards. If you say Y, you
1271 will be asked for your specific card in the following questions. If
1272 you are unsure, say Y.
1275 tristate "AMD PCnet32 PCI support"
1276 depends on NET_PCI && PCI
1280 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1281 answer Y here and read the Ethernet-HOWTO, available from
1282 <http://www.tldp.org/docs.html#howto>.
1284 To compile this driver as a module, choose M here. The module
1285 will be called pcnet32.
1288 tristate "AMD 8111 (new PCI lance) support"
1289 depends on NET_PCI && PCI
1293 If you have an AMD 8111-based PCI lance ethernet card,
1294 answer Y here and read the Ethernet-HOWTO, available from
1295 <http://www.tldp.org/docs.html#howto>.
1297 To compile this driver as a module, choose M here. The module
1298 will be called amd8111e.
1300 config ADAPTEC_STARFIRE
1301 tristate "Adaptec Starfire/DuraLAN support"
1302 depends on NET_PCI && PCI
1306 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1307 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1308 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1311 To compile this driver as a module, choose M here: the module
1312 will be called starfire. This is recommended.
1315 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1316 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1319 If you have a network (Ethernet) card of this type, say Y and read
1320 the Ethernet-HOWTO, available from
1321 <http://www.tldp.org/docs.html#howto>.
1323 To compile this driver as a module, choose M here. The module
1324 will be called ac3200.
1327 tristate "Apricot Xen-II on board Ethernet"
1328 depends on NET_PCI && ISA
1330 If you have a network (Ethernet) controller of this type, say Y and
1331 read the Ethernet-HOWTO, available from
1332 <http://www.tldp.org/docs.html#howto>.
1334 To compile this driver as a module, choose M here. The module
1335 will be called apricot.
1338 tristate "Broadcom 440x/47xx ethernet support"
1339 depends on SSB_POSSIBLE && HAS_DMA
1343 If you have a network (Ethernet) controller of this type, say Y
1344 or M and read the Ethernet-HOWTO, available from
1345 <http://www.tldp.org/docs.html#howto>.
1347 To compile this driver as a module, choose M here. The module
1350 # Auto-select SSB PCI-HOST support, if possible
1351 config B44_PCI_AUTOSELECT
1353 depends on B44 && SSB_PCIHOST_POSSIBLE
1357 # Auto-select SSB PCICORE driver, if possible
1358 config B44_PCICORE_AUTOSELECT
1360 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1361 select SSB_DRIVER_PCICORE
1366 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1370 tristate "nForce Ethernet support"
1371 depends on NET_PCI && PCI
1373 If you have a network (Ethernet) controller of this type, say Y and
1374 read the Ethernet-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>.
1377 To compile this driver as a module, choose M here. The module
1378 will be called forcedeth.
1380 config FORCEDETH_NAPI
1381 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1382 depends on FORCEDETH && EXPERIMENTAL
1384 NAPI is a new driver API designed to reduce CPU and interrupt load
1385 when the driver is receiving lots of packets from the card. It is
1386 still somewhat experimental and thus not yet enabled by default.
1388 If your estimated Rx load is 10kpps or more, or if the card will be
1389 deployed on potentially unfriendly networks (e.g. in a firewall),
1395 tristate "CS89x0 support"
1396 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1397 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1399 Support for CS89x0 chipset based Ethernet cards. If you have a
1400 network (Ethernet) card of this type, say Y and read the
1401 Ethernet-HOWTO, available from
1402 <http://www.tldp.org/docs.html#howto> as well as
1403 <file:Documentation/networking/cs89x0.txt>.
1405 To compile this driver as a module, choose M here. The module
1406 will be called cs89x0.
1408 config CS89x0_NONISA_IRQ
1410 depends on CS89x0 != n
1411 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1414 tristate "TOSHIBA TC35815 Ethernet support"
1415 depends on NET_PCI && PCI && MIPS
1419 tristate "Intel(R) PRO/100+ support"
1420 depends on NET_PCI && PCI
1423 This driver supports Intel(R) PRO/100 family of adapters.
1424 To verify that your adapter is supported, find the board ID number
1425 on the adapter. Look for a label that has a barcode and a number
1426 in the format 123456-001 (six digits hyphen three digits).
1428 Use the above information and the Adapter & Driver ID Guide at:
1430 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1432 to identify the adapter.
1434 For the latest Intel PRO/100 network driver for Linux, see:
1436 <http://appsr.intel.com/scripts-df/support_intel.asp>
1438 More specific information on configuring the driver is in
1439 <file:Documentation/networking/e100.txt>.
1441 To compile this driver as a module, choose M here. The module
1442 will be called e100.
1445 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1446 depends on NET_PCI && EISA && EXPERIMENTAL
1449 If you have a network (Ethernet) card of this type, say Y and read
1450 the Ethernet-HOWTO, available from
1451 <http://www.tldp.org/docs.html#howto>.
1453 To compile this driver as a module, choose M here. The module
1454 will be called lne390.
1457 tristate "Myson MTD-8xx PCI Ethernet support"
1458 depends on NET_PCI && PCI
1462 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1463 cards. Specifications and data at
1464 <http://www.myson.com.hk/mtd/datasheet/>.
1467 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1468 depends on NET_PCI && PCI
1471 This driver is for the National Semiconductor DP83810 series,
1472 which is used in cards from PureData, NetGear, Linksys
1473 and others, including the 83815 chip.
1474 More specific information and updates are available from
1475 <http://www.scyld.com/network/natsemi.html>.
1478 tristate "PCI NE2000 and clones support (see help)"
1479 depends on NET_PCI && PCI
1482 This driver is for NE2000 compatible PCI cards. It will not work
1483 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1484 support" below). If you have a PCI NE2000 network (Ethernet) card,
1485 say Y and read the Ethernet-HOWTO, available from
1486 <http://www.tldp.org/docs.html#howto>.
1488 This driver also works for the following NE2000 clone cards:
1489 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1490 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1491 Holtek HT80232 Holtek HT80229
1493 To compile this driver as a module, choose M here. The module
1494 will be called ne2k-pci.
1497 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1498 depends on NET_PCI && EISA && EXPERIMENTAL
1501 If you have a network (Ethernet) card of this type, say Y and read
1502 the Ethernet-HOWTO, available from
1503 <http://www.tldp.org/docs.html#howto>. Note that this driver
1504 will NOT WORK for NE3200 cards as they are completely different.
1506 To compile this driver as a module, choose M here. The module
1507 will be called ne3210.
1510 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1511 depends on NET_PCI && EISA && EXPERIMENTAL
1514 If you have a network (Ethernet) card of this type, say Y and read
1515 the Ethernet-HOWTO, available from
1516 <http://www.tldp.org/docs.html#howto>.
1518 To compile this driver as a module, choose M here. The module
1519 will be called es3210.
1522 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1523 depends on NET_PCI && PCI && EXPERIMENTAL
1527 This is a driver for the Fast Ethernet PCI network cards based on
1528 the RTL8139C+ chips. If you have one of those, say Y and read
1529 the Ethernet-HOWTO, available from
1530 <http://www.tldp.org/docs.html#howto>.
1532 To compile this driver as a module, choose M here: the module
1533 will be called 8139cp. This is recommended.
1536 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1537 depends on NET_PCI && PCI
1541 This is a driver for the Fast Ethernet PCI network cards based on
1542 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1543 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1545 To compile this driver as a module, choose M here: the module
1546 will be called 8139too. This is recommended.
1549 bool "Use PIO instead of MMIO"
1553 This instructs the driver to use programmed I/O ports (PIO) instead
1554 of PCI shared memory (MMIO). This can possibly solve some problems
1555 in case your mainboard has memory consistency issues. If unsure,
1558 config 8139TOO_TUNE_TWISTER
1559 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1562 This implements a function which might come in handy in case you
1563 are using low quality on long cabling. It is required for RealTek
1564 RTL-8139 revision K boards, and totally unused otherwise. It tries
1565 to match the transceiver to the cable characteristics. This is
1566 experimental since hardly documented by the manufacturer.
1570 bool "Support for older RTL-8129/8130 boards"
1573 This enables support for the older and uncommon RTL-8129 and
1574 RTL-8130 chips, which support MII via an external transceiver,
1575 instead of an internal one. Disabling this option will save some
1576 memory by making the code size smaller. If unsure, say Y.
1578 config 8139_OLD_RX_RESET
1579 bool "Use older RX-reset method"
1582 The 8139too driver was recently updated to contain a more rapid
1583 reset sequence, in the face of severe receive errors. This "new"
1584 RX-reset method should be adequate for all boards. But if you
1585 experience problems, you can enable this option to restore the
1586 old RX-reset behavior. If unsure, say N.
1589 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1590 depends on NET_PCI && PCI
1594 This is a driver for the R6040 Fast Ethernet MACs found in the
1595 the RDC R-321x System-on-chips.
1597 To compile this driver as a module, choose M here: the module
1598 will be called r6040. This is recommended.
1601 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1602 depends on NET_PCI && PCI
1606 This is a driver for the Fast Ethernet PCI network cards based on
1607 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1608 SiS 630 and SiS 540 chipsets.
1610 This driver also supports AMD 79C901 HomePNA so that you can use
1611 your phone line as a network cable.
1613 To compile this driver as a module, choose M here: the module
1614 will be called sis900. This is recommended.
1617 tristate "SMC EtherPower II"
1618 depends on NET_PCI && PCI
1622 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1623 which is based on the SMC83c17x (EPIC/100).
1624 More specific information and updates are available from
1625 <http://www.scyld.com/network/epic100.html>.
1628 tristate "Sundance Alta support"
1629 depends on NET_PCI && PCI
1633 This driver is for the Sundance "Alta" chip.
1634 More specific information and updates are available from
1635 <http://www.scyld.com/network/sundance.html>.
1637 config SUNDANCE_MMIO
1638 bool "Use MMIO instead of PIO"
1641 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1642 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1643 is known to solve bugs on certain chips.
1648 tristate "TI ThunderLAN support"
1649 depends on NET_PCI && (PCI || EISA)
1651 If you have a PCI Ethernet network card based on the ThunderLAN chip
1652 which is supported by this driver, say Y and read the
1653 Ethernet-HOWTO, available from
1654 <http://www.tldp.org/docs.html#howto>.
1656 Devices currently supported by this driver are Compaq Netelligent,
1657 Compaq NetFlex and Olicom cards. Please read the file
1658 <file:Documentation/networking/tlan.txt> for more details.
1660 To compile this driver as a module, choose M here. The module
1661 will be called tlan.
1663 Please email feedback to <torben.mathiasen@compaq.com>.
1666 tristate "VIA Rhine support"
1667 depends on NET_PCI && PCI
1671 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1672 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1673 Ethernet functions can also be found integrated on South Bridges
1676 To compile this driver as a module, choose M here. The module
1677 will be called via-rhine.
1679 config VIA_RHINE_MMIO
1680 bool "Use MMIO instead of PIO"
1681 depends on VIA_RHINE
1683 This instructs the driver to use PCI shared memory (MMIO) instead of
1684 programmed I/O ports (PIO). Enabling this gives an improvement in
1685 processing time in parts of the driver.
1690 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1691 depends on NET_PCI && PCI && EXPERIMENTAL
1694 This is a driver for the Fast Ethernet PCI network cards based on
1695 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1696 have one of these, say Y here.
1698 To compile this driver as a module, choose M here: the module
1699 will be called sc92031. This is recommended.
1702 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1703 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1706 TI AR7 CPMAC Ethernet support
1709 bool "Pocket and portable adapters"
1712 Cute little network (Ethernet) devices which attach to the parallel
1713 port ("pocket adapters"), commonly used with laptops. If you have
1714 one of those, say Y and read the Ethernet-HOWTO, available from
1715 <http://www.tldp.org/docs.html#howto>.
1717 If you want to plug a network (or some other) card into the PCMCIA
1718 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1719 credit card size extension cards used by all modern laptops), you
1720 need the pcmcia-cs package (location contained in the file
1721 <file:Documentation/Changes>) and you can say N here.
1723 Laptop users should read the Linux Laptop home page at
1724 <http://www.linux-on-laptops.com/> or
1725 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1727 Note that the answer to this question doesn't directly affect the
1728 kernel: saying N will just cause the configurator to skip all
1729 the questions about this class of network devices. If you say Y, you
1730 will be asked for your specific device in the following questions.
1733 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1734 depends on NET_POCKET && PARPORT && X86
1737 This is a network (Ethernet) device which attaches to your parallel
1738 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1739 available from <http://www.tldp.org/docs.html#howto>, if you
1740 want to use this. If you intend to use this driver, you should have
1741 said N to the "Parallel printer support", because the two drivers
1742 don't like each other.
1744 To compile this driver as a module, choose M here: the module
1748 tristate "D-Link DE600 pocket adapter support"
1749 depends on NET_POCKET && PARPORT
1751 This is a network (Ethernet) device which attaches to your parallel
1752 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1753 Ethernet-HOWTO, available from
1754 <http://www.tldp.org/docs.html#howto>, if you want to use
1755 this. It is possible to have several devices share a single parallel
1756 port and it is safe to compile the corresponding drivers into the
1759 To compile this driver as a module, choose M here: the module
1760 will be called de600.
1763 tristate "D-Link DE620 pocket adapter support"
1764 depends on NET_POCKET && PARPORT
1766 This is a network (Ethernet) device which attaches to your parallel
1767 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1768 Ethernet-HOWTO, available from
1769 <http://www.tldp.org/docs.html#howto>, if you want to use
1770 this. It is possible to have several devices share a single parallel
1771 port and it is safe to compile the corresponding drivers into the
1774 To compile this driver as a module, choose M here: the module
1775 will be called de620.
1778 tristate "SGI Seeq ethernet controller support"
1779 depends on SGI_HAS_SEEQ
1781 Say Y here if you have an Seeq based Ethernet network card. This is
1782 used in many Silicon Graphics machines.
1785 tristate "DEC LANCE ethernet controller support"
1786 depends on MACH_DECSTATION
1789 This driver is for the series of Ethernet controllers produced by
1790 DEC (now Compaq) based on the AMD Lance chipset, including the
1791 DEPCA series. (This chipset is better known via the NE2100 cards.)
1794 bool "Motorola 68360 ethernet controller"
1797 Say Y here if you want to use the built-in ethernet controller of
1798 the Motorola 68360 processor.
1801 bool "FEC ethernet controller (of ColdFire CPUs)"
1802 depends on M523x || M527x || M5272 || M528x || M520x
1804 Say Y here if you want to use the built-in 10/100 Fast ethernet
1805 controller on some Motorola ColdFire processors.
1808 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1811 Say Y here if you want to use the second built-in 10/100 Fast
1812 ethernet controller on some Motorola ColdFire processors.
1815 tristate "MPC52xx FEC driver"
1816 depends on PPC_MPC52xx && PPC_BESTCOMM_FEC
1820 This option enables support for the MPC5200's on-chip
1821 Fast Ethernet Controller
1822 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1824 config FEC_MPC52xx_MDIO
1825 bool "MPC52xx FEC MDIO bus driver"
1826 depends on FEC_MPC52xx
1829 The MPC5200's FEC can connect to the Ethernet either with
1830 an external MII PHY chip or 10 Mbps 7-wire interface
1831 (Motorola? industry standard).
1832 If your board uses an external PHY connected to FEC, enable this.
1833 If not sure, enable.
1834 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1837 tristate "NE2000 compatible support for H8/300"
1840 Say Y here if you want to use the NE2000 compatible
1841 controller on the Renesas H8/300 processor.
1844 tristate "Atheros L2 Fast Ethernet support"
1849 This driver supports the Atheros L2 fast ethernet adapter.
1851 To compile this driver as a module, choose M here. The module
1852 will be called atl2.
1854 source "drivers/net/fs_enet/Kconfig"
1856 endif # NET_ETHERNET
1862 menuconfig NETDEV_1000
1863 bool "Ethernet (1000 Mbit)"
1867 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1868 type of Local Area Network (LAN) in universities and companies.
1870 Say Y here to get to see options for Gigabit Ethernet drivers.
1871 This option alone does not add any kernel code.
1872 Note that drivers supporting both 100 and 1000 MBit may be listed
1873 under "Ethernet (10 or 100MBit)" instead.
1875 If you say N, all options in this submenu will be skipped and disabled.
1880 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1883 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1884 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1885 adapter. The driver allows for using the Jumbo Frame option (9000
1886 bytes/frame) however it requires that your switches can handle this
1887 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1890 To compile this driver as a module, choose M here: the
1891 module will be called acenic.
1893 config ACENIC_OMIT_TIGON_I
1894 bool "Omit support for old Tigon I based AceNICs"
1897 Say Y here if you only have Tigon II based AceNICs and want to leave
1898 out support for the older Tigon I based cards which are no longer
1899 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1900 version)). This will reduce the size of the driver object by
1901 app. 100KB. If you are not sure whether your card is a Tigon I or a
1902 Tigon II, say N here.
1904 The safe and default value for this is N.
1907 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1911 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1913 D-Link DGE-550T Gigabit Ethernet Adapter.
1914 D-Link DL2000-based Gigabit Ethernet Adapter.
1915 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1917 To compile this driver as a module, choose M here: the
1918 module will be called dl2k.
1921 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1924 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1925 adapters. For more information on how to identify your adapter, go
1926 to the Adapter & Driver ID Guide at:
1928 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1930 For general information and support, go to the Intel support
1933 <http://support.intel.com>
1935 More specific information on configuring the driver is in
1936 <file:Documentation/networking/e1000.txt>.
1938 To compile this driver as a module, choose M here. The module
1939 will be called e1000.
1942 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1943 depends on PCI && (!SPARC32 || BROKEN)
1945 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1946 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1947 use the regular e1000 driver For more information on how to
1948 identify your adapter, go to the Adapter & Driver ID Guide at:
1950 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1952 For general information and support, go to the Intel support
1955 <http://support.intel.com>
1957 To compile this driver as a module, choose M here. The module
1958 will be called e1000e.
1961 tristate "IP1000 Gigabit Ethernet support"
1962 depends on PCI && EXPERIMENTAL
1965 This driver supports IP1000 gigabit Ethernet cards.
1967 To compile this driver as a module, choose M here: the module
1968 will be called ipg. This is recommended.
1971 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
1974 This driver supports Intel(R) 82575 gigabit ethernet family of
1975 adapters. For more information on how to identify your adapter, go
1976 to the Adapter & Driver ID Guide at:
1978 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1980 For general information and support, go to the Intel support
1983 <http://support.intel.com>
1985 More specific information on configuring the driver is in
1986 <file:Documentation/networking/e1000.txt>.
1988 To compile this driver as a module, choose M here. The module
1992 bool "Use software LRO"
1993 depends on IGB && INET
1996 Say Y here if you want to use large receive offload.
2003 depends on IGB && DCA && !(IGB=y && DCA=m)
2005 source "drivers/net/ixp2000/Kconfig"
2008 tristate "MyriCOM Gigabit Ethernet support"
2011 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2013 To compile this driver as a module, choose M here: the module
2014 will be called myri_sbus. This is recommended.
2017 tristate "National Semiconductor DP83820 support"
2020 This is a driver for the National Semiconductor DP83820 series
2021 of gigabit ethernet MACs. Cards using this chipset include
2022 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2023 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2027 tristate "Packet Engines Hamachi GNIC-II support"
2031 If you have a Gigabit Ethernet card of this type, say Y and read
2032 the Ethernet-HOWTO, available from
2033 <http://www.tldp.org/docs.html#howto>.
2035 To compile this driver as a module, choose M here. The module will be
2039 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2040 depends on PCI && EXPERIMENTAL
2043 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2044 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2045 used by the Beowulf Linux cluster project. See
2046 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2047 information about this driver in particular and Beowulf in general.
2049 To compile this driver as a module, choose M here: the module
2050 will be called yellowfin. This is recommended.
2053 tristate "Realtek 8169 gigabit ethernet support"
2058 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2060 To compile this driver as a module, choose M here: the module
2061 will be called r8169. This is recommended.
2065 depends on R8169 && VLAN_8021Q
2067 Say Y here for the r8169 driver to support the functions required
2068 by the kernel 802.1Q code.
2073 tristate "SB1250 Gigabit Ethernet support"
2074 depends on SIBYTE_SB1xxx_SOC
2077 This driver supports Gigabit Ethernet interfaces based on the
2078 Broadcom SiByte family of System-On-a-Chip parts. They include
2079 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2082 To compile this driver as a module, choose M here: the module
2083 will be called sb1250-mac.
2086 tristate "SiS190/SiS191 gigabit ethernet support"
2091 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2092 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2093 appear in lan on motherboard designs which are based on SiS 965
2094 and SiS 966 south bridge.
2096 To compile this driver as a module, choose M here: the module
2097 will be called sis190. This is recommended.
2100 tristate "New SysKonnect GigaEthernet support"
2104 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2105 and related Gigabit Ethernet adapters. It is a new smaller driver
2106 with better performance and more complete ethtool support.
2108 It does not support the link failover and network management
2109 features that "portable" vendor supplied sk98lin driver does.
2111 This driver supports adapters based on the original Yukon chipset:
2112 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2113 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2115 It does not support the newer Yukon2 chipset: a separate driver,
2116 sky2, is provided for Yukon2-based adapters.
2118 To compile this driver as a module, choose M here: the module
2119 will be called skge. This is recommended.
2122 bool "Debugging interface"
2123 depends on SKGE && DEBUG_FS
2125 This option adds the ability to dump driver state for debugging.
2126 The file debugfs/skge/ethX displays the state of the internal
2127 transmit and receive rings.
2132 tristate "SysKonnect Yukon2 support"
2136 This driver supports Gigabit Ethernet adapters based on the
2137 Marvell Yukon 2 chipset:
2138 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2139 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2141 There is companion driver for the older Marvell Yukon and
2142 Genesis based adapters: skge.
2144 To compile this driver as a module, choose M here: the module
2145 will be called sky2. This is recommended.
2148 bool "Debugging interface"
2149 depends on SKY2 && DEBUG_FS
2151 This option adds the ability to dump driver state for debugging.
2152 The file debugfs/sky2/ethX displays the state of the internal
2153 transmit and receive rings.
2158 tristate "VIA Velocity support"
2164 If you have a VIA "Velocity" based network card say Y here.
2166 To compile this driver as a module, choose M here. The module
2167 will be called via-velocity.
2170 tristate "Broadcom Tigon3 support"
2174 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2176 To compile this driver as a module, choose M here: the module
2177 will be called tg3. This is recommended.
2180 tristate "Broadcom NetXtremeII support"
2185 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2187 To compile this driver as a module, choose M here: the module
2188 will be called bnx2. This is recommended.
2191 tristate "Spider Gigabit Ethernet driver"
2192 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2195 This driver supports the Gigabit Ethernet chips present on the
2196 Cell Processor-Based Blades from IBM.
2199 tristate "Tundra TSI108 gigabit Ethernet support"
2200 depends on TSI108_BRIDGE
2202 This driver supports Tundra TSI108 gigabit Ethernet ports.
2203 To compile this driver as a module, choose M here: the module
2204 will be called tsi108_eth.
2207 tristate "PS3 Gigabit Ethernet driver"
2209 select PS3_SYS_MANAGER
2211 This driver supports the network device on the PS3 game
2212 console. This driver has built-in support for Ethernet.
2214 To compile this driver as a module, choose M here: the
2215 module will be called ps3_gelic.
2217 config GELIC_WIRELESS
2218 bool "PS3 Wireless support"
2219 depends on GELIC_NET
2222 This option adds the support for the wireless feature of PS3.
2223 If you have the wireless-less model of PS3 or have no plan to
2224 use wireless feature, disabling this option saves memory. As
2225 the driver automatically distinguishes the models, you can
2226 safely enable this option even if you have a wireless-less model.
2228 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2229 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2230 depends on GELIC_WIRELESS
2232 This option retains the obsolete private interface to pass
2233 the PSK from user space programs to the driver. The PSK
2234 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2235 (WPA-Personal) environment.
2236 If WPA[2]-PSK is used and you need to use old programs that
2237 support only this old interface, say Y. Otherwise N.
2242 tristate "Gianfar Ethernet"
2247 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2248 and MPC86xx family of chips, and the FEC on the 8540.
2251 tristate "Freescale QE Gigabit Ethernet"
2252 depends on QUICC_ENGINE
2255 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2256 which is available on some Freescale SOCs.
2258 config UGETH_MAGIC_PACKET
2259 bool "Magic Packet detection support"
2262 config UGETH_FILTERING
2263 bool "Mac address filtering support"
2266 config UGETH_TX_ON_DEMAND
2267 bool "Transmit on Demand support"
2271 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2272 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2275 This driver supports the gigabit ethernet MACs in the
2276 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2277 in the Marvell Orion ARM SoC family.
2279 Some boards that use the Discovery chipset are the Momenco
2280 Ocelot C and Jaguar ATX and Pegasos II.
2283 tristate "QLogic QLA3XXX Network Driver Support"
2286 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2288 To compile this driver as a module, choose M here: the module
2289 will be called qla3xxx.
2292 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2297 This driver supports the Atheros/Attansic L1 gigabit ethernet
2300 To compile this driver as a module, choose M here. The module
2301 will be called atl1.
2304 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2305 depends on PCI && EXPERIMENTAL
2309 This driver supports the Atheros L1E gigabit ethernet adapter.
2311 To compile this driver as a module, choose M here. The module
2312 will be called atl1e.
2315 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2320 This driver supports the PCI-Express gigabit ethernet adapters
2321 based on JMicron JMC250 chipset.
2323 To compile this driver as a module, choose M here. The module
2329 # 10 Gigabit Ethernet
2332 menuconfig NETDEV_10000
2333 bool "Ethernet (10000 Mbit)"
2337 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2338 This option alone does not add any kernel code.
2340 If you say N, all options in this submenu will be skipped and disabled.
2345 tristate "Chelsio 10Gb Ethernet support"
2349 This driver supports Chelsio gigabit and 10-gigabit
2350 Ethernet cards. More information about adapter features and
2351 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2353 For general information about Chelsio and our products, visit
2354 our website at <http://www.chelsio.com>.
2356 For customer support, please visit our customer support page at
2357 <http://www.chelsio.com/support.htm>.
2359 Please send feedback to <linux-bugs@chelsio.com>.
2361 To compile this driver as a module, choose M here: the module
2362 will be called cxgb.
2364 config CHELSIO_T1_1G
2365 bool "Chelsio gigabit Ethernet support"
2366 depends on CHELSIO_T1
2368 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2369 are using only 10G cards say 'N' here.
2372 tristate "Chelsio Communications T3 10Gb Ethernet support"
2373 depends on PCI && INET
2377 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2380 For general information about Chelsio and our products, visit
2381 our website at <http://www.chelsio.com>.
2383 For customer support, please visit our customer support page at
2384 <http://www.chelsio.com/support.htm>.
2386 Please send feedback to <linux-bugs@chelsio.com>.
2388 To compile this driver as a module, choose M here: the module
2389 will be called cxgb3.
2392 tristate "eHEA Ethernet support"
2393 depends on IBMEBUS && INET && SPARSEMEM
2396 This driver supports the IBM pSeries eHEA ethernet adapter.
2398 To compile the driver as a module, choose M here. The module
2399 will be called ehea.
2402 tristate "Cisco 10G Ethernet NIC support"
2403 depends on PCI && INET
2406 This enables the support for the Cisco 10G Ethernet card.
2409 tristate "Intel(R) 10GbE PCI Express adapters support"
2410 depends on PCI && INET
2413 This driver supports Intel(R) 10GbE PCI Express family of
2414 adapters. For more information on how to identify your adapter, go
2415 to the Adapter & Driver ID Guide at:
2417 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2419 For general information and support, go to the Intel support
2422 <http://support.intel.com>
2424 To compile this driver as a module, choose M here. The module
2425 will be called ixgbe.
2430 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2433 tristate "Intel(R) PRO/10GbE support"
2436 This driver supports Intel(R) PRO/10GbE family of adapters for
2437 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2438 instead. For more information on how to identify your adapter, go
2439 to the Adapter & Driver ID Guide at:
2441 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2443 For general information and support, go to the Intel support
2446 <http://support.intel.com>
2448 More specific information on configuring the driver is in
2449 <file:Documentation/networking/ixgb.txt>.
2451 To compile this driver as a module, choose M here. The module
2452 will be called ixgb.
2455 tristate "S2IO 10Gbe XFrame NIC"
2458 This driver supports the 10Gbe XFrame NIC of S2IO.
2459 More specific information on configuring the driver is in
2460 <file:Documentation/networking/s2io.txt>.
2463 tristate "Myricom Myri-10G Ethernet support"
2464 depends on PCI && INET
2469 This driver supports Myricom Myri-10G Dual Protocol interface in
2470 Ethernet mode. If the eeprom on your board is not recent enough,
2471 you will need a newer firmware image.
2472 You may get this image or more information, at:
2474 <http://www.myri.com/scs/download-Myri10GE.html>
2476 To compile this driver as a module, choose M here. The module
2477 will be called myri10ge.
2482 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2485 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2488 This enables the support for NetXen's Gigabit Ethernet card.
2491 tristate "Sun Neptune 10Gbit Ethernet support"
2494 This enables support for cards based upon Sun's
2498 tristate "PA Semi 1/10Gbit MAC"
2499 depends on PPC_PASEMI && PCI
2503 This driver supports the on-chip 1/10Gbit Ethernet controller on
2504 PA Semi's PWRficient line of chips.
2507 tristate "Mellanox Technologies 10Gbit Ethernet support"
2508 depends on PCI && INET
2512 This driver supports Mellanox Technologies ConnectX Ethernet
2521 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2522 depends on MLX4_CORE
2525 This option causes debugging code to be compiled into the
2526 mlx4_core driver. The output can be turned on via the
2527 debug_level module parameter (which can also be set after
2528 the driver is loaded through sysfs).
2531 tristate "Tehuti Networks 10G Ethernet"
2534 Tehuti Networks 10G Ethernet NIC
2537 tristate "Broadcom NetXtremeII 10Gb support"
2542 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2543 To compile this driver as a module, choose M here: the module
2544 will be called bnx2x. This is recommended.
2547 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2550 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2552 To compile this driver as a module, choose M here: the module
2553 will be called qlge.
2555 source "drivers/net/sfc/Kconfig"
2557 endif # NETDEV_10000
2559 source "drivers/net/tokenring/Kconfig"
2561 source "drivers/net/wireless/Kconfig"
2563 source "drivers/net/usb/Kconfig"
2565 source "drivers/net/pcmcia/Kconfig"
2567 source "drivers/net/wan/Kconfig"
2569 source "drivers/atm/Kconfig"
2571 source "drivers/s390/net/Kconfig"
2573 config XEN_NETDEV_FRONTEND
2574 tristate "Xen network device frontend driver"
2578 The network device frontend driver allows the kernel to
2579 access network devices exported exported by a virtual
2580 machine containing a physical network device driver. The
2581 frontend driver is intended for unprivileged guest domains;
2582 if you are compiling a kernel for a Xen guest, you almost
2583 certainly want to enable this.
2586 tristate "iSeries Virtual Ethernet driver support"
2587 depends on PPC_ISERIES
2590 tristate "RapidIO Ethernet over messaging driver support"
2593 config RIONET_TX_SIZE
2594 int "Number of outbound queue entries"
2598 config RIONET_RX_SIZE
2599 int "Number of inbound queue entries"
2604 bool "FDDI driver support"
2605 depends on (PCI || EISA || TC)
2607 Fiber Distributed Data Interface is a high speed local area network
2608 design; essentially a replacement for high speed Ethernet. FDDI can
2609 run over copper or fiber. If you are connected to such a network and
2610 want a driver for the FDDI card in your computer, say Y here (and
2611 then also Y to the driver for your FDDI card, below). Most people
2615 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2616 depends on FDDI && (PCI || EISA || TC)
2618 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2619 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2620 to a local FDDI network.
2622 To compile this driver as a module, choose M here: the module
2623 will be called defxx. If unsure, say N.
2627 prompt "Use MMIO instead of PIO" if PCI || EISA
2629 default n if PCI || EISA
2632 This instructs the driver to use EISA or PCI memory-mapped I/O
2633 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2634 Enabling this gives an improvement in processing time in parts
2635 of the driver, but it may cause problems with EISA (DEFEA)
2636 adapters. TURBOchannel does not have the concept of I/O ports,
2637 so MMIO is always used for these (DEFTA) adapters.
2642 tristate "SysKonnect FDDI PCI support"
2643 depends on FDDI && PCI
2646 Say Y here if you have a SysKonnect FDDI PCI adapter.
2647 The following adapters are supported by this driver:
2648 - SK-5521 (SK-NET FDDI-UP)
2649 - SK-5522 (SK-NET FDDI-UP DAS)
2650 - SK-5541 (SK-NET FDDI-FP)
2651 - SK-5543 (SK-NET FDDI-LP)
2652 - SK-5544 (SK-NET FDDI-LP DAS)
2653 - SK-5821 (SK-NET FDDI-UP64)
2654 - SK-5822 (SK-NET FDDI-UP64 DAS)
2655 - SK-5841 (SK-NET FDDI-FP64)
2656 - SK-5843 (SK-NET FDDI-LP64)
2657 - SK-5844 (SK-NET FDDI-LP64 DAS)
2658 - Netelligent 100 FDDI DAS Fibre SC
2659 - Netelligent 100 FDDI SAS Fibre SC
2660 - Netelligent 100 FDDI DAS UTP
2661 - Netelligent 100 FDDI SAS UTP
2662 - Netelligent 100 FDDI SAS Fibre MIC
2664 Read <file:Documentation/networking/skfp.txt> for information about
2667 Questions concerning this driver can be addressed to:
2668 <linux@syskonnect.de>
2670 To compile this driver as a module, choose M here: the module
2671 will be called skfp. This is recommended.
2674 bool "HIPPI driver support (EXPERIMENTAL)"
2675 depends on EXPERIMENTAL && INET && PCI
2677 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2678 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2679 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2680 single-mode). HIPPI networks are commonly used for clusters and to
2681 connect to super computers. If you are connected to a HIPPI network
2682 and have a HIPPI network card in your computer that you want to use
2683 under Linux, say Y here (you must also remember to enable the driver
2684 for your HIPPI card below). Most people will say N here.
2687 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2688 depends on HIPPI && PCI
2690 Say Y here if this is your PCI HIPPI network card.
2692 To compile this driver as a module, choose M here: the module
2693 will be called rrunner. If unsure, say N.
2695 config ROADRUNNER_LARGE_RINGS
2696 bool "Use large TX/RX rings (EXPERIMENTAL)"
2697 depends on ROADRUNNER
2699 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2700 of additional memory to allow for fastest operation, both for
2701 transmitting and receiving. This memory cannot be used by any other
2702 kernel code or by user space programs. Say Y here only if you have
2706 tristate "PLIP (parallel port) support"
2709 PLIP (Parallel Line Internet Protocol) is used to create a
2710 reasonably fast mini network consisting of two (or, rarely, more)
2711 local machines. A PLIP link from a Linux box is a popular means to
2712 install a Linux distribution on a machine which doesn't have a
2713 CD-ROM drive (a minimal system has to be transferred with floppies
2714 first). The kernels on both machines need to have this PLIP option
2715 enabled for this to work.
2717 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2718 ports (the connectors at the computers with 25 holes) are connected
2719 with "null printer" or "Turbo Laplink" cables which can transmit 4
2720 bits at a time (mode 0) or with special PLIP cables, to be used on
2721 bidirectional parallel ports only, which can transmit 8 bits at a
2722 time (mode 1); you can find the wiring of these cables in
2723 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2724 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2725 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2726 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2727 and winsock or NCSA's telnet.
2729 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2730 as the NET-3-HOWTO, both available from
2731 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2732 protocol has been changed and this PLIP driver won't work together
2733 with the PLIP support in Linux versions 1.0.x. This option enlarges
2734 your kernel by about 8 KB.
2736 To compile this driver as a module, choose M here. The module
2737 will be called plip. If unsure, say Y or M, in case you buy
2741 tristate "PPP (point-to-point protocol) support"
2744 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2745 the same purpose: sending Internet traffic over telephone (and other
2746 serial) lines. Ask your access provider if they support it, because
2747 otherwise you can't use it; most Internet access providers these
2748 days support PPP rather than SLIP.
2750 To use PPP, you need an additional program called pppd as described
2751 in the PPP-HOWTO, available at
2752 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2753 the version of pppd recommended in <file:Documentation/Changes>.
2754 The PPP option enlarges your kernel by about 16 KB.
2756 There are actually two versions of PPP: the traditional PPP for
2757 asynchronous lines, such as regular analog phone lines, and
2758 synchronous PPP which can be used over digital ISDN lines for
2759 example. If you want to use PPP over phone lines or other
2760 asynchronous serial lines, you need to say Y (or M) here and also to
2761 the next option, "PPP support for async serial ports". For PPP over
2762 synchronous lines, you should say Y (or M) here and to "Support
2763 synchronous PPP", below.
2765 If you said Y to "Version information on all symbols" above, then
2766 you cannot compile the PPP driver into the kernel; you can then only
2767 compile it as a module. To compile this driver as a module, choose M
2768 here. The module will be called ppp_generic.
2770 config PPP_MULTILINK
2771 bool "PPP multilink support (EXPERIMENTAL)"
2772 depends on PPP && EXPERIMENTAL
2774 PPP multilink is a protocol (defined in RFC 1990) which allows you
2775 to combine several (logical or physical) lines into one logical PPP
2776 connection, so that you can utilize your full bandwidth.
2778 This has to be supported at the other end as well and you need a
2779 version of the pppd daemon which understands the multilink protocol.
2784 bool "PPP filtering"
2787 Say Y here if you want to be able to filter the packets passing over
2788 PPP interfaces. This allows you to control which packets count as
2789 activity (i.e. which packets will reset the idle timer or bring up
2790 a demand-dialed link) and which packets are to be dropped entirely.
2791 You need to say Y here if you wish to use the pass-filter and
2792 active-filter options to pppd.
2797 tristate "PPP support for async serial ports"
2801 Say Y (or M) here if you want to be able to use PPP over standard
2802 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2803 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2806 To compile this driver as a module, choose M here.
2811 tristate "PPP support for sync tty ports"
2814 Say Y (or M) here if you want to be able to use PPP over synchronous
2815 (HDLC) tty devices, such as the SyncLink adapter. These devices
2816 are often used for high-speed leased lines like T1/E1.
2818 To compile this driver as a module, choose M here.
2821 tristate "PPP Deflate compression"
2826 Support for the Deflate compression method for PPP, which uses the
2827 Deflate algorithm (the same algorithm that gzip uses) to compress
2828 each PPP packet before it is sent over the wire. The machine at the
2829 other end of the PPP link (usually your ISP) has to support the
2830 Deflate compression method as well for this to be useful. Even if
2831 they don't support it, it is safe to say Y here.
2833 To compile this driver as a module, choose M here.
2836 tristate "PPP BSD-Compress compression"
2839 Support for the BSD-Compress compression method for PPP, which uses
2840 the LZW compression method to compress each PPP packet before it is
2841 sent over the wire. The machine at the other end of the PPP link
2842 (usually your ISP) has to support the BSD-Compress compression
2843 method as well for this to be useful. Even if they don't support it,
2844 it is safe to say Y here.
2846 The PPP Deflate compression method ("PPP Deflate compression",
2847 above) is preferable to BSD-Compress, because it compresses better
2850 Note that the BSD compression code will always be compiled as a
2851 module; it is called bsd_comp and will show up in the directory
2852 modules once you have said "make modules". If unsure, say N.
2855 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2856 depends on PPP && EXPERIMENTAL
2862 Support for the MPPE Encryption protocol, as employed by the
2863 Microsoft Point-to-Point Tunneling Protocol.
2865 See http://pptpclient.sourceforge.net/ for information on
2866 configuring PPTP clients and servers to utilize this method.
2869 tristate "PPP over Ethernet (EXPERIMENTAL)"
2870 depends on EXPERIMENTAL && PPP
2872 Support for PPP over Ethernet.
2874 This driver requires the latest version of pppd from the CVS
2875 repository at cvs.samba.org. Alternatively, see the
2876 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2877 which contains instruction on how to use this driver (under
2878 the heading "Kernel mode PPPoE").
2881 tristate "PPP over ATM"
2882 depends on ATM && PPP
2884 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2885 This implementation does not yet comply with section 8 of RFC2364,
2886 which can lead to bad results if the ATM peer loses state and
2887 changes its encapsulation unilaterally.
2890 tristate "PPP over L2TP (EXPERIMENTAL)"
2891 depends on EXPERIMENTAL && PPP && INET
2893 Support for PPP-over-L2TP socket family. L2TP is a protocol
2894 used by ISPs and enterprises to tunnel PPP traffic over UDP
2895 tunnels. L2TP is replacing PPTP for VPN uses.
2897 This kernel component handles only L2TP data packets: a
2898 userland daemon handles L2TP the control protocol (tunnel
2899 and session setup). One such daemon is OpenL2TP
2900 (http://openl2tp.sourceforge.net/).
2903 tristate "SLIP (serial line) support"
2905 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2906 connect to your Internet service provider or to connect to some
2907 other local Unix box or if you want to configure your Linux box as a
2908 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2909 Internet Protocol) is a protocol used to send Internet traffic over
2910 serial connections such as telephone lines or null modem cables;
2911 nowadays, the protocol PPP is more commonly used for this same
2914 Normally, your access provider has to support SLIP in order for you
2915 to be able to use it, but there is now a SLIP emulator called SLiRP
2916 around (available from
2917 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2918 allows you to use SLIP over a regular dial up shell connection. If
2919 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2920 NET-3-HOWTO, available from
2921 <http://www.tldp.org/docs.html#howto>, explains how to
2922 configure SLIP. Note that you don't need this option if you just
2923 want to run term (term is a program which gives you almost full
2924 Internet connectivity if you have a regular dial up shell account on
2925 some Internet connected Unix computer. Read
2926 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2927 support will enlarge your kernel by about 4 KB. If unsure, say N.
2929 To compile this driver as a module, choose M here. The module
2930 will be called slip.
2932 config SLIP_COMPRESSED
2933 bool "CSLIP compressed headers"
2937 This protocol is faster than SLIP because it uses compression on the
2938 TCP/IP headers (not on the data itself), but it has to be supported
2939 on both ends. Ask your access provider if you are not sure and
2940 answer Y, just in case. You will still be able to use plain SLIP. If
2941 you plan to use SLiRP, the SLIP emulator (available from
2942 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2943 allows you to use SLIP over a regular dial up shell connection, you
2944 definitely want to say Y here. The NET-3-HOWTO, available from
2945 <http://www.tldp.org/docs.html#howto>, explains how to configure
2946 CSLIP. This won't enlarge your kernel.
2951 This option enables Van Jacobsen serial line header compression
2955 bool "Keepalive and linefill"
2958 Adds additional capabilities to the SLIP driver to support the
2959 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2962 config SLIP_MODE_SLIP6
2963 bool "Six bit SLIP encapsulation"
2966 Just occasionally you may need to run IP over hostile serial
2967 networks that don't pass all control characters or are only seven
2968 bit. Saying Y here adds an extra mode you can use with SLIP:
2969 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2970 the serial device. Naturally, this has to be supported at the other
2971 end of the link as well. It's good enough, for example, to run IP
2972 over the async ports of a Camtec JNT Pad. If unsure, say N.
2975 bool "Fibre Channel driver support"
2976 depends on SCSI && PCI
2978 Fibre Channel is a high speed serial protocol mainly used to connect
2979 large storage devices to the computer; it is compatible with and
2980 intended to replace SCSI.
2982 If you intend to use Fibre Channel, you need to have a Fibre channel
2983 adaptor card in your computer; say Y here and to the driver for your
2984 adaptor below. You also should have said Y to "SCSI support" and
2985 "SCSI generic support".
2988 tristate "Network console logging support (EXPERIMENTAL)"
2989 depends on EXPERIMENTAL
2991 If you want to log kernel messages over the network, enable this.
2992 See <file:Documentation/networking/netconsole.txt> for details.
2994 config NETCONSOLE_DYNAMIC
2995 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
2996 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
2999 This option enables the ability to dynamically reconfigure target
3000 parameters (interface, IP addresses, port numbers, MAC addresses)
3001 at runtime through a userspace interface exported using configfs.
3002 See <file:Documentation/networking/netconsole.txt> for details.
3008 bool "Netpoll traffic trapping"
3012 config NET_POLL_CONTROLLER
3016 tristate "Virtio network driver (EXPERIMENTAL)"
3017 depends on EXPERIMENTAL && VIRTIO
3019 This is the virtual network driver for virtio. It can be used with
3020 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.