3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
29 config NETDEVICES_MULTIQUEUE
30 bool "Netdevice multiple hardware queue support"
32 Say Y here if you want to allow the network stack to use multiple
33 hardware TX queues on an ethernet device.
35 Most people will say N here.
38 tristate "Intermediate Functional Block support"
39 depends on NET_CLS_ACT
41 This is an intermediate driver that allows sharing of
43 To compile this driver as a module, choose M here: the module
44 will be called ifb. If you want to use more than one ifb
45 device at a time, you need to compile this driver as a module.
46 Instead of 'ifb', the devices will then be called 'ifb0',
48 Look at the iproute2 documentation directory for usage etc
51 tristate "Dummy net driver support"
53 This is essentially a bit-bucket device (i.e. traffic you send to
54 this device is consigned into oblivion) with a configurable IP
55 address. It is most commonly used in order to make your currently
56 inactive SLIP address seem like a real address for local programs.
57 If you use SLIP or PPP, you might want to say Y here. Since this
58 thing often comes in handy, the default is Y. It won't enlarge your
59 kernel either. What a deal. Read about it in the Network
60 Administrator's Guide, available from
61 <http://www.tldp.org/docs.html#guide>.
63 To compile this driver as a module, choose M here: the module
64 will be called dummy. If you want to use more than one dummy
65 device at a time, you need to compile this driver as a module.
66 Instead of 'dummy', the devices will then be called 'dummy0',
70 tristate "Bonding driver support"
73 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
74 Channels together. This is called 'Etherchannel' by Cisco,
75 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
77 The driver supports multiple bonding modes to allow for both high
78 performance and high availability operation.
80 Refer to <file:Documentation/networking/bonding.txt> for more
83 To compile this driver as a module, choose M here: the module
84 will be called bonding.
87 tristate "MAC-VLAN support (EXPERIMENTAL)"
88 depends on EXPERIMENTAL
90 This allows one to create virtual interfaces that map packets to
91 or from specific MAC addresses to a particular interface.
93 Macvlan devices can be added using the "ip" command from the
94 iproute2 package starting with the iproute2-2.6.23 release:
96 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
98 To compile this driver as a module, choose M here: the module
99 will be called macvlan.
102 tristate "EQL (serial line load balancing) support"
104 If you have two serial connections to some other computer (this
105 usually requires two modems and two telephone lines) and you use
106 SLIP (the protocol for sending Internet traffic over telephone
107 lines) or PPP (a better SLIP) on them, you can make them behave like
108 one double speed connection using this driver. Naturally, this has
109 to be supported at the other end as well, either with a similar EQL
110 Linux driver or with a Livingston Portmaster 2e.
112 Say Y if you want this and read
113 <file:Documentation/networking/eql.txt>. You may also want to read
114 section 6.2 of the NET-3-HOWTO, available from
115 <http://www.tldp.org/docs.html#howto>.
117 To compile this driver as a module, choose M here: the module
118 will be called eql. If unsure, say N.
121 tristate "Universal TUN/TAP device driver support"
124 TUN/TAP provides packet reception and transmission for user space
125 programs. It can be viewed as a simple Point-to-Point or Ethernet
126 device, which instead of receiving packets from a physical media,
127 receives them from user space program and instead of sending packets
128 via physical media writes them to the user space program.
130 When a program opens /dev/net/tun, driver creates and registers
131 corresponding net device tunX or tapX. After a program closed above
132 devices, driver will automatically delete tunXX or tapXX device and
133 all routes corresponding to it.
135 Please read <file:Documentation/networking/tuntap.txt> for more
138 To compile this driver as a module, choose M here: the module
141 If you don't know what to use this for, you don't need it.
144 tristate "Virtual ethernet pair device"
146 This device is a local ethernet tunnel. Devices are created in pairs.
147 When one end receives the packet it appears on its pair and vice
151 tristate "General Instruments Surfboard 1000"
154 This is a driver for the General Instrument (also known as
155 NextLevel) SURFboard 1000 internal
156 cable modem. This is an ISA card which is used by a number of cable
157 TV companies to provide cable modem access. It's a one-way
158 downstream-only cable modem, meaning that your upstream net link is
159 provided by your regular phone modem.
161 At present this driver only compiles as a module, so say M here if
162 you have this card. The module will be called sb1000. Then read
163 <file:Documentation/networking/README.sb1000> for information on how
164 to use this module, as it needs special ppp scripts for establishing
165 a connection. Further documentation and the necessary scripts can be
168 <http://www.jacksonville.net/~fventuri/>
169 <http://home.adelphia.net/~siglercm/sb1000.html>
170 <http://linuxpower.cx/~cable/>
172 If you don't have this card, of course say N.
174 source "drivers/net/arcnet/Kconfig"
176 source "drivers/net/phy/Kconfig"
182 menuconfig NET_ETHERNET
183 bool "Ethernet (10 or 100Mbit)"
186 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
187 type of Local Area Network (LAN) in universities and companies.
189 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
190 coaxial cable, linking computers in a chain), 10BASE-T or twisted
191 pair (10 Mbps over twisted pair cable, linking computers to central
192 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
193 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
194 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
195 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
196 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
197 Ethernet (1 Gbps over optical fiber or short copper links).
199 If your Linux machine will be connected to an Ethernet and you have
200 an Ethernet network interface card (NIC) installed in your computer,
201 say Y here and read the Ethernet-HOWTO, available from
202 <http://www.tldp.org/docs.html#howto>. You will then also have
203 to say Y to the driver for your particular NIC.
205 Note that the answer to this question won't directly affect the
206 kernel: saying N will just cause the configurator to skip all
207 the questions about Ethernet network cards. If unsure, say N.
212 tristate "Generic Media Independent Interface device support"
214 Most ethernet controllers have MII transceiver either as an external
215 or internal device. It is safe to say Y or M here even if your
216 ethernet card lack MII.
219 tristate "Atmel MACB support"
220 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
223 The Atmel MACB ethernet interface is found on many AT32 and AT91
224 parts. Say Y to include support for the MACB chip.
226 To compile this driver as a module, choose M here: the module
229 source "drivers/net/arm/Kconfig"
232 tristate "ASIX AX88796 NE2000 clone support"
233 depends on ARM || MIPS || SUPERH
237 AX88796 driver, using platform bus to provide
238 chip detection and resources
241 bool "ASIX AX88796 external 93CX6 eeprom support"
245 Select this if your platform comes with an external 93CX6 eeprom.
248 tristate "MACE (Power Mac ethernet) support"
249 depends on PPC_PMAC && PPC32
252 Power Macintoshes and clones with Ethernet built-in on the
253 motherboard will usually use a MACE (Medium Access Control for
254 Ethernet) interface. Say Y to include support for the MACE chip.
256 To compile this driver as a module, choose M here: the module
259 config MACE_AAUI_PORT
260 bool "Use AAUI port instead of TP by default"
263 Some Apple machines (notably the Apple Network Server) which use the
264 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
265 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
266 Y here if you have such a machine. If unsure, say N.
267 The driver will default to AAUI on ANS anyway, and if you use it as
268 a module, you can provide the port_aaui=0|1 to force the driver.
271 tristate "BMAC (G3 ethernet) support"
272 depends on PPC_PMAC && PPC32
275 Say Y for support of BMAC Ethernet interfaces. These are used on G3
278 To compile this driver as a module, choose M here: the module
282 tristate "Ariadne support"
285 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
288 To compile this driver as a module, choose M here: the module
289 will be called ariadne.
292 tristate "A2065 support"
296 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
299 To compile this driver as a module, choose M here: the module
300 will be called a2065.
303 tristate "Hydra support"
307 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
309 To compile this driver as a module, choose M here: the module
310 will be called hydra.
313 tristate "Zorro NS8390-based Ethernet support"
317 This driver is for Zorro Ethernet cards using an NS8390-compatible
318 chipset, like the Village Tronic Ariadne II and the Individual
319 Computers X-Surf Ethernet cards. If you have such a card, say Y.
322 To compile this driver as a module, choose M here: the module
323 will be called zorro8390.
326 tristate "PCMCIA NE2000 support"
327 depends on AMIGA_PCMCIA
330 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
333 To compile this driver as a module, choose M here: the module
337 bool "Macintosh NS 8390 based ethernet cards"
341 If you want to include a driver to support Nubus or LC-PDS
342 Ethernet cards using an NS8390 chipset or its equivalent, say Y
343 and read the Ethernet-HOWTO, available from
344 <http://www.tldp.org/docs.html#howto>.
347 tristate "Macintosh CS89x0 based ethernet cards"
350 Support for CS89x0 chipset based Ethernet cards. If you have a
351 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
352 read the Ethernet-HOWTO, available from
353 <http://www.tldp.org/docs.html#howto>.
355 To compile this driver as a module, choose M here. This module will
359 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
362 Support for NatSemi SONIC based Ethernet devices. This includes
363 the onboard Ethernet in many Quadras as well as some LC-PDS,
364 a few Nubus and all known Comm Slot Ethernet cards. If you have
365 one of these say Y and read the Ethernet-HOWTO, available from
366 <http://www.tldp.org/docs.html#howto>.
368 To compile this driver as a module, choose M here. This module will
372 bool "Macintosh (AV) onboard MACE ethernet"
376 Support for the onboard AMD 79C940 MACE Ethernet controller used in
377 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
378 say Y and read the Ethernet-HOWTO, available from
379 <http://www.tldp.org/docs.html#howto>.
382 tristate "MVME147 (Lance) Ethernet support"
386 Support for the on-board Ethernet interface on the Motorola MVME147
387 single-board computer. Say Y here to include the
388 driver for this chip in your kernel.
389 To compile this driver as a module, choose M here.
392 tristate "MVME16x Ethernet support"
395 This is the driver for the Ethernet interface on the Motorola
396 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
397 driver for this chip in your kernel.
398 To compile this driver as a module, choose M here.
401 tristate "BVME6000 Ethernet support"
404 This is the driver for the Ethernet interface on BVME4000 and
405 BVME6000 VME boards. Say Y here to include the driver for this chip
407 To compile this driver as a module, choose M here.
410 tristate "Atari Lance support"
413 Say Y to include support for several Atari Ethernet adapters based
414 on the AMD Lance chipset: RieblCard (with or without battery), or
415 PAMCard VME (also the version by Rhotron, with different addresses).
418 tristate "Sun3/Sun3x on-board LANCE support"
419 depends on SUN3 || SUN3X
421 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
422 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
423 here to compile in the Linux driver for this and enable Ethernet.
424 General Linux information on the Sun 3 and 3x series (now
426 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
428 If you're not building a kernel for a Sun 3, say N.
431 bool "Sun3 on-board Intel 82586 support"
434 This driver enables support for the on-board Intel 82586 based
435 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
436 that this driver does not support 82586-based adapters on additional
440 bool "HP on-board LANCE support"
444 If you want to use the builtin "LANCE" Ethernet controller on an
445 HP300 machine, say Y here.
448 tristate "Lasi ethernet"
451 Say Y here to support the builtin Intel 82596 ethernet controller
452 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
455 tristate "SNI RM ethernet"
456 depends on NET_ETHERNET && SNI_RM
458 Say Y here to support the on-board Intel 82596 ethernet controller
459 built into SNI RM machines.
462 tristate "Korina (IDT RC32434) Ethernet support"
463 depends on NET_ETHERNET && MIKROTIK_RB532
465 If you have a Mikrotik RouterBoard 500 or IDT RC32434
466 based system say Y. Otherwise say N.
468 config MIPS_JAZZ_SONIC
469 tristate "MIPS JAZZ onboard SONIC Ethernet support"
472 This is the driver for the onboard card of MIPS Magnum 4000,
473 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
475 config MIPS_AU1X00_ENET
476 bool "MIPS AU1000 Ethernet support"
477 depends on SOC_AU1X00
481 If you have an Alchemy Semi AU1X00 based system
482 say Y. Otherwise, say N.
485 bool "SGI IOC3 Ethernet"
486 depends on PCI && SGI_IP27
490 If you have a network (Ethernet) card of this type, say Y and read
491 the Ethernet-HOWTO, available from
492 <http://www.tldp.org/docs.html#howto>.
495 tristate "MIPS simulator Network device"
498 The MIPSNET device is a simple Ethernet network device which is
499 emulated by the MIPS Simulator.
500 If you are not using a MIPSsim or are unsure, say N.
502 config SGI_O2MACE_ETH
503 tristate "SGI O2 MACE Fast Ethernet support"
504 depends on SGI_IP32=y
507 tristate "National DP83902AV support"
511 Support for cards based on the National Semiconductor DP83902AV
512 ST-NIC Serial Network Interface Controller for Twisted Pair. This
513 is a 10Mbit/sec Ethernet controller. Product overview and specs at
514 <http://www.national.com/pf/DP/DP83902A.html>.
519 tristate "Sun LANCE support"
523 This driver supports the "le" interface present on all 32-bit Sparc
524 systems, on some older Ultra systems and as an Sbus option. These
525 cards are based on the AMD Lance chipset, which is better known
526 via the NE2100 cards.
528 To compile this driver as a module, choose M here: the module
529 will be called sunlance.
532 tristate "Sun Happy Meal 10/100baseT support"
533 depends on SBUS || PCI
536 This driver supports the "hme" interface present on most Ultra
537 systems and as an option on older Sbus systems. This driver supports
538 both PCI and Sbus devices. This driver also supports the "qfe" quad
539 100baseT device available in both PCI and Sbus configurations.
541 To compile this driver as a module, choose M here: the module
542 will be called sunhme.
545 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
546 depends on SBUS && EXPERIMENTAL
549 This driver supports the "be" interface available as an Sbus option.
550 This is Sun's older 100baseT Ethernet device.
552 To compile this driver as a module, choose M here: the module
553 will be called sunbmac.
556 tristate "Sun QuadEthernet support"
560 This driver supports the "qe" 10baseT Ethernet device, available as
561 an Sbus option. Note that this is not the same as Quad FastEthernet
562 "qfe" which is supported by the Happy Meal driver instead.
564 To compile this driver as a module, choose M here: the module
565 will be called sunqe.
568 tristate "Sun GEM support"
572 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
573 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
576 tristate "Sun Cassini support"
580 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
581 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
584 tristate "Sun Virtual Network support"
587 Support for virtual network devices under Sun Logical Domains.
589 config NET_VENDOR_3COM
591 depends on ISA || EISA || MCA || PCI
593 If you have a network (Ethernet) card belonging to this class, say Y
594 and read the Ethernet-HOWTO, available from
595 <http://www.tldp.org/docs.html#howto>.
597 Note that the answer to this question doesn't directly affect the
598 kernel: saying N will just cause the configurator to skip all
599 the questions about 3COM cards. If you say Y, you will be asked for
600 your specific card in the following questions.
603 tristate "3c501 \"EtherLink\" support"
604 depends on NET_VENDOR_3COM && ISA
606 If you have a network (Ethernet) card of this type, say Y and read
607 the Ethernet-HOWTO, available from
608 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
609 new card, since the 3c501 is slow, broken, and obsolete: you will
610 have problems. Some people suggest to ping ("man ping") a nearby
611 machine every minute ("man cron") when using this card.
613 To compile this driver as a module, choose M here. The module
614 will be called 3c501.
617 tristate "3c503 \"EtherLink II\" support"
618 depends on NET_VENDOR_3COM && ISA
621 If you have a network (Ethernet) card of this type, say Y and read
622 the Ethernet-HOWTO, available from
623 <http://www.tldp.org/docs.html#howto>.
625 To compile this driver as a module, choose M here. The module
626 will be called 3c503.
629 tristate "3c505 \"EtherLink Plus\" support"
630 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
632 Information about this network (Ethernet) card can be found in
633 <file:Documentation/networking/3c505.txt>. If you have a card of
634 this type, say Y and read 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 3c505.
641 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
642 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
644 If you have a network (Ethernet) card of this type, say Y and read
645 the Ethernet-HOWTO, available from
646 <http://www.tldp.org/docs.html#howto>.
648 To compile this driver as a module, choose M here. The module
649 will be called 3c507.
652 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
653 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
655 If you have a network (Ethernet) card belonging to the 3Com
656 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
657 from <http://www.tldp.org/docs.html#howto>.
659 If your card is not working you may need to use the DOS
660 setup disk to disable Plug & Play mode, and to select the default
663 To compile this driver as a module, choose M here. The module
664 will be called 3c509.
667 tristate "3c515 ISA \"Fast EtherLink\""
668 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
670 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
671 network card, say Y and read the Ethernet-HOWTO, available from
672 <http://www.tldp.org/docs.html#howto>.
674 To compile this driver as a module, choose M here. The module
675 will be called 3c515.
678 tristate "3c523 \"EtherLink/MC\" support"
679 depends on NET_VENDOR_3COM && MCA_LEGACY
681 If you have a network (Ethernet) card of this type, say Y and read
682 the Ethernet-HOWTO, available from
683 <http://www.tldp.org/docs.html#howto>.
685 To compile this driver as a module, choose M here. The module
686 will be called 3c523.
689 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
690 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
692 If you have a network (Ethernet) card of this type, say Y and read
693 the Ethernet-HOWTO, available from
694 <http://www.tldp.org/docs.html#howto>.
696 To compile this driver as a module, choose M here. The module
697 will be called 3c527.
700 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
701 depends on NET_VENDOR_3COM && (PCI || EISA)
704 This option enables driver support for a large number of 10Mbps and
705 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
707 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
708 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
709 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
710 "Tornado" (3c905) PCI
711 "Hurricane" (3c555/3cSOHO) PCI
713 If you have such a card, say Y and read the Ethernet-HOWTO,
714 available from <http://www.tldp.org/docs.html#howto>. More
715 specific information is in
716 <file:Documentation/networking/vortex.txt> and in the comments at
717 the beginning of <file:drivers/net/3c59x.c>.
719 To compile this support as a module, choose M here.
722 tristate "3cr990 series \"Typhoon\" support"
723 depends on NET_VENDOR_3COM && PCI
726 This option enables driver support for the 3cr990 series of cards:
728 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
729 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
730 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
732 If you have a network (Ethernet) card of this type, say Y and read
733 the Ethernet-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
736 To compile this driver as a module, choose M here. The module
737 will be called typhoon.
740 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
741 depends on ISA && ISA_DMA_API
743 If you have a network (Ethernet) card of this type, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
748 To compile this driver as a module, choose M here: the module
749 will be called lance. This is recommended.
751 config NET_VENDOR_SMC
752 bool "Western Digital/SMC cards"
753 depends on ISA || MCA || EISA || MAC
755 If you have a network (Ethernet) card belonging to this class, say Y
756 and read the Ethernet-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>.
759 Note that the answer to this question doesn't directly affect the
760 kernel: saying N will just cause the configurator to skip all
761 the questions about Western Digital cards. If you say Y, you will be
762 asked for your specific card in the following questions.
765 tristate "WD80*3 support"
766 depends on NET_VENDOR_SMC && ISA
769 If you have a network (Ethernet) card of this type, say Y and read
770 the Ethernet-HOWTO, available from
771 <http://www.tldp.org/docs.html#howto>.
773 To compile this driver as a module, choose M here. The module
777 tristate "SMC Ultra MCA support"
778 depends on NET_VENDOR_SMC && MCA
781 If you have a network (Ethernet) card of this type and are running
782 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
783 available from <http://www.tldp.org/docs.html#howto>.
785 To compile this driver as a module, choose M here. The module
786 will be called smc-mca.
789 tristate "SMC Ultra support"
790 depends on NET_VENDOR_SMC && ISA
793 If you have a network (Ethernet) card of this type, say Y and read
794 the Ethernet-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 Important: There have been many reports that, with some motherboards
798 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
799 such as some BusLogic models) causes corruption problems with many
800 operating systems. The Linux smc-ultra driver has a work-around for
801 this but keep it in mind if you have such a SCSI card and have
804 To compile this driver as a module, choose M here. The module
805 will be called smc-ultra.
808 tristate "SMC Ultra32 EISA support"
809 depends on NET_VENDOR_SMC && EISA
812 If you have a network (Ethernet) card of this type, say Y and read
813 the Ethernet-HOWTO, available from
814 <http://www.tldp.org/docs.html#howto>.
816 To compile this driver as a module, choose M here. The module
817 will be called smc-ultra32.
820 tristate "Blackfin 527/536/537 on-chip mac support"
821 depends on NET_ETHERNET && (BF527 || BF537 || BF536)
825 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
827 This is the driver for blackfin on-chip mac device. Say Y if you want it
828 compiled into the kernel. This driver is also available as a module
829 ( = code which can be inserted in and removed from the running kernel
830 whenever you want). The module will be called bfin_mac.
832 config BFIN_MAC_USE_L1
833 bool "Use L1 memory for rx/tx packets"
834 depends on BFIN_MAC && (BF527 || BF537)
837 To get maximum network performance, you should use L1 memory as rx/tx buffers.
838 Say N here if you want to reserve L1 memory for other uses.
840 config BFIN_TX_DESC_NUM
841 int "Number of transmit buffer packets"
843 range 6 10 if BFIN_MAC_USE_L1
847 Set the number of buffer packets used in driver.
849 config BFIN_RX_DESC_NUM
850 int "Number of receive buffer packets"
852 range 20 100 if BFIN_MAC_USE_L1
856 Set the number of buffer packets used in driver.
859 bool "RMII PHY Interface (EXPERIMENTAL)"
860 depends on BFIN_MAC && EXPERIMENTAL
861 default y if BFIN527_EZKIT
862 default n if BFIN537_STAMP
864 Use Reduced PHY MII Interface
867 tristate "SMC 9194 support"
868 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
871 This is support for the SMC9xxx based Ethernet cards. Choose this
872 option if you have a DELL laptop with the docking station, or
873 another SMC9192/9194 based chipset. Say Y if you want it compiled
874 into the kernel, and read the file
875 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
876 available from <http://www.tldp.org/docs.html#howto>.
878 To compile this driver as a module, choose M here. The module
879 will be called smc9194.
882 tristate "SMC 91C9x/91C1xxx support"
885 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
886 SOC_AU1X00 || BLACKFIN || MN10300
888 This is a driver for SMC's 91x series of Ethernet chipsets,
889 including the SMC91C94 and the SMC91C111. Say Y if you want it
890 compiled into the kernel, and read the file
891 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
892 available from <http://www.linuxdoc.org/docs.html#howto>.
894 This driver is also available as a module ( = code which can be
895 inserted in and removed from the running kernel whenever you want).
896 The module will be called smc91x. If you want to compile it as a
897 module, say M here and read <file:Documentation/kbuild/modules.txt>.
900 tristate "NetX Ethernet support"
904 This is support for the Hilscher netX builtin Ethernet ports
906 To compile this driver as a module, choose M here. The module
907 will be called netx-eth.
910 tristate "DM9000 support"
911 depends on ARM || BLACKFIN || MIPS
915 Support for DM9000 chipset.
917 To compile this driver as a module, choose M here. The module
918 will be called dm9000.
921 tristate "ENC28J60 support"
922 depends on EXPERIMENTAL && SPI && NET_ETHERNET
925 Support for the Microchip EN28J60 ethernet chip.
927 To compile this driver as a module, choose M here. The module will be
930 config ENC28J60_WRITEVERIFY
931 bool "Enable write verify"
934 Enable the verify after the buffer write useful for debugging purpose.
937 config DM9000_DEBUGLEVEL
938 int "DM9000 maximum debug level"
942 The maximum level of debugging code compiled into the DM9000
946 tristate "SMSC LAN911[5678] support"
949 depends on ARCH_PXA || SH_MAGIC_PANEL_R2
951 This is a driver for SMSC's LAN911x series of Ethernet chipsets
952 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
953 Say Y if you want it compiled into the kernel,
954 and read the Ethernet-HOWTO, available from
955 <http://www.linuxdoc.org/docs.html#howto>.
957 This driver is also available as a module. The module will be
958 called smc911x. If you want to compile it as a module, say M
959 here and read <file:Documentation/kbuild/modules.txt>
961 config NET_VENDOR_RACAL
962 bool "Racal-Interlan (Micom) NI cards"
965 If you have a network (Ethernet) card belonging to this class, such
966 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
967 available from <http://www.tldp.org/docs.html#howto>.
969 Note that the answer to this question doesn't directly affect the
970 kernel: saying N will just cause the configurator to skip all
971 the questions about NI cards. If you say Y, you will be asked for
972 your specific card in the following questions.
975 tristate "NI5010 support (EXPERIMENTAL)"
976 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
978 If you have a network (Ethernet) card of this type, say Y and read
979 the Ethernet-HOWTO, available from
980 <http://www.tldp.org/docs.html#howto>. Note that this is still
983 To compile this driver as a module, choose M here. The module
984 will be called ni5010.
987 tristate "NI5210 support"
988 depends on NET_VENDOR_RACAL && ISA
990 If you have a network (Ethernet) card of this type, say Y and read
991 the Ethernet-HOWTO, available from
992 <http://www.tldp.org/docs.html#howto>.
994 To compile this driver as a module, choose M here. The module
998 tristate "NI6510 support"
999 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1001 If you have a network (Ethernet) card of this type, say Y and read
1002 the Ethernet-HOWTO, available from
1003 <http://www.tldp.org/docs.html#howto>.
1005 To compile this driver as a module, choose M here. The module
1006 will be called ni65.
1008 source "drivers/net/tulip/Kconfig"
1011 tristate "AT1700/1720 support (EXPERIMENTAL)"
1012 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1015 If you have a network (Ethernet) card of this type, say Y and read
1016 the Ethernet-HOWTO, available from
1017 <http://www.tldp.org/docs.html#howto>.
1019 To compile this driver as a module, choose M here. The module
1020 will be called at1700.
1023 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1024 depends on ISA || EISA || MCA
1027 If you have a network (Ethernet) card of this type, say Y and read
1028 the Ethernet-HOWTO, available from
1029 <http://www.tldp.org/docs.html#howto> as well as
1030 <file:drivers/net/depca.c>.
1032 To compile this driver as a module, choose M here. The module
1033 will be called depca.
1036 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1037 depends on ISA || EISA || PCI
1039 If you have a network (Ethernet) card of this type, say Y and read
1040 the Ethernet-HOWTO, available from
1041 <http://www.tldp.org/docs.html#howto>.
1043 To compile this driver as a module, choose M here. The module
1044 will be called hp100.
1047 bool "Other ISA cards"
1050 If your network (Ethernet) card hasn't been mentioned yet and its
1051 bus system (that's the way the cards talks to the other components
1052 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1053 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1054 available from <http://www.tldp.org/docs.html#howto>.
1058 Note that the answer to this question doesn't directly affect the
1059 kernel: saying N will just cause the configurator to skip all
1060 the remaining ISA network card questions. If you say Y, you will be
1061 asked for your specific card in the following questions.
1064 tristate "Cabletron E21xx support"
1068 If you have a network (Ethernet) card of this type, say Y and read
1069 the Ethernet-HOWTO, available from
1070 <http://www.tldp.org/docs.html#howto>.
1072 To compile this driver as a module, choose M here. The module
1073 will be called e2100.
1076 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1080 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1081 cards. If this is for you, say Y and read
1082 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1083 well as the Ethernet-HOWTO, available from
1084 <http://www.tldp.org/docs.html#howto>.
1086 To compile this driver as a module, choose M here. The module
1087 will be called ewrk3.
1090 tristate "EtherExpress 16 support"
1093 If you have an EtherExpress16 network (Ethernet) card, say Y and
1094 read the Ethernet-HOWTO, available from
1095 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1096 EtherExpress16 card used to be regarded as a very poor choice
1097 because the driver was very unreliable. We now have a new driver
1098 that should do better.
1100 To compile this driver as a module, choose M here. The module
1101 will be called eexpress.
1104 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1107 If you have a network (Ethernet) card of this type, say Y. This
1108 driver supports Intel i82595{FX,TX} based boards. Note however
1109 that the EtherExpress PRO/100 Ethernet card has its own separate
1110 driver. Please read the Ethernet-HOWTO, available from
1111 <http://www.tldp.org/docs.html#howto>.
1113 To compile this driver as a module, choose M here. The module
1114 will be called eepro.
1117 tristate "HP PCLAN+ (27247B and 27252A) support"
1121 If you have a network (Ethernet) card of this type, say Y and read
1122 the Ethernet-HOWTO, available from
1123 <http://www.tldp.org/docs.html#howto>.
1125 To compile this driver as a module, choose M here. The module
1126 will be called hp-plus.
1129 tristate "HP PCLAN (27245 and other 27xxx series) support"
1133 If you have a network (Ethernet) card of this type, say Y and read
1134 the Ethernet-HOWTO, available from
1135 <http://www.tldp.org/docs.html#howto>.
1137 To compile this driver as a module, choose M here. The module
1141 tristate "LP486E on board Ethernet"
1144 Say Y here to support the 82596-based on-board Ethernet controller
1145 for the Panther motherboard, which is one of the two shipped in the
1146 Intel Professional Workstation.
1149 tristate "ICL EtherTeam 16i/32 support"
1152 If you have a network (Ethernet) card of this type, say Y and read
1153 the Ethernet-HOWTO, available from
1154 <http://www.tldp.org/docs.html#howto>.
1156 To compile this driver as a module, choose M here. The module
1157 will be called eth16i.
1160 tristate "NE2000/NE1000 support"
1161 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1164 If you have a network (Ethernet) card of this type, say Y and read
1165 the Ethernet-HOWTO, available from
1166 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1167 without a specific driver are compatible with NE2000.
1169 If you have a PCI NE2000 card however, say N here and Y to "PCI
1170 NE2000 and clone support" under "EISA, VLB, PCI and on board
1171 controllers" below. If you have a NE2000 card and are running on
1172 an MCA system (a bus system used on some IBM PS/2 computers and
1173 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1176 To compile this driver as a module, choose M here. The module
1180 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1181 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1183 The Zenith Z-Note notebook computer has a built-in network
1184 (Ethernet) card, and this is the Linux driver for it. Note that the
1185 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1186 by this driver. Read the Ethernet-HOWTO, available from
1187 <http://www.tldp.org/docs.html#howto>.
1190 tristate "SEEQ8005 support (EXPERIMENTAL)"
1191 depends on NET_ISA && EXPERIMENTAL
1193 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1194 is for you, read the Ethernet-HOWTO, available from
1195 <http://www.tldp.org/docs.html#howto>.
1197 To compile this driver as a module, choose M here. The module
1198 will be called seeq8005.
1201 tristate "NE/2 (ne2000 MCA version) support"
1202 depends on MCA_LEGACY
1205 If you have a network (Ethernet) card of this type, say Y and read
1206 the Ethernet-HOWTO, available from
1207 <http://www.tldp.org/docs.html#howto>.
1209 To compile this driver as a module, choose M here. The module
1213 tristate "IBM LAN Adapter/A support"
1216 This is a Micro Channel Ethernet adapter. You need to set
1217 CONFIG_MCA to use this driver. It is both available as an in-kernel
1218 driver and as a module.
1220 To compile this driver as a module, choose M here. The only
1221 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1222 will both support 16K and 32K memory windows, however a 32K window
1223 gives a better security against packet losses. Usage of multiple
1224 boards with this driver should be possible, but has not been tested
1225 up to now due to lack of hardware.
1228 tristate "IBM LAN Virtual Ethernet support"
1229 depends on PPC_PSERIES
1231 This driver supports virtual ethernet adapters on newer IBM iSeries
1232 and pSeries systems.
1234 To compile this driver as a module, choose M here. The module will
1237 source "drivers/net/ibm_emac/Kconfig"
1238 source "drivers/net/ibm_newemac/Kconfig"
1241 bool "EISA, VLB, PCI and on board controllers"
1242 depends on ISA || EISA || PCI
1244 This is another class of network cards which attach directly to the
1245 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1246 available from <http://www.tldp.org/docs.html#howto>.
1248 Note that the answer to this question doesn't directly affect the
1249 kernel: saying N will just cause the configurator to skip all
1250 the questions about this class of network cards. If you say Y, you
1251 will be asked for your specific card in the following questions. If
1252 you are unsure, say Y.
1255 tristate "AMD PCnet32 PCI support"
1256 depends on NET_PCI && PCI
1260 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1261 answer Y here and read the Ethernet-HOWTO, available from
1262 <http://www.tldp.org/docs.html#howto>.
1264 To compile this driver as a module, choose M here. The module
1265 will be called pcnet32.
1268 tristate "AMD 8111 (new PCI lance) support"
1269 depends on NET_PCI && PCI
1273 If you have an AMD 8111-based PCI lance ethernet card,
1274 answer Y here and read the Ethernet-HOWTO, available from
1275 <http://www.tldp.org/docs.html#howto>.
1277 To compile this driver as a module, choose M here. The module
1278 will be called amd8111e.
1280 config AMD8111E_NAPI
1281 bool "Use RX polling (NAPI)"
1282 depends on AMD8111_ETH
1284 NAPI is a new driver API designed to reduce CPU and interrupt load
1285 when the driver is receiving lots of packets from the card. It is
1286 still somewhat experimental and thus not yet enabled by default.
1288 If your estimated Rx load is 10kpps or more, or if the card will be
1289 deployed on potentially unfriendly networks (e.g. in a firewall),
1294 config ADAPTEC_STARFIRE
1295 tristate "Adaptec Starfire/DuraLAN support"
1296 depends on NET_PCI && PCI
1300 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1301 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1302 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1305 To compile this driver as a module, choose M here: the module
1306 will be called starfire. This is recommended.
1308 config ADAPTEC_STARFIRE_NAPI
1309 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1310 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1312 NAPI is a new driver API designed to reduce CPU and interrupt load
1313 when the driver is receiving lots of packets from the card. It is
1314 still somewhat experimental and thus not yet enabled by default.
1316 If your estimated Rx load is 10kpps or more, or if the card will be
1317 deployed on potentially unfriendly networks (e.g. in a firewall),
1323 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1324 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1327 If you have a network (Ethernet) card of this type, say Y and read
1328 the Ethernet-HOWTO, available from
1329 <http://www.tldp.org/docs.html#howto>.
1331 To compile this driver as a module, choose M here. The module
1332 will be called ac3200.
1335 tristate "Apricot Xen-II on board Ethernet"
1336 depends on NET_PCI && ISA
1338 If you have a network (Ethernet) controller of this type, say Y and
1339 read the Ethernet-HOWTO, available from
1340 <http://www.tldp.org/docs.html#howto>.
1342 To compile this driver as a module, choose M here. The module
1343 will be called apricot.
1346 tristate "Broadcom 440x/47xx ethernet support"
1347 depends on SSB_POSSIBLE && HAS_DMA
1351 If you have a network (Ethernet) controller of this type, say Y
1352 or M and read the Ethernet-HOWTO, available from
1353 <http://www.tldp.org/docs.html#howto>.
1355 To compile this driver as a module, choose M here. The module
1358 # Auto-select SSB PCI-HOST support, if possible
1359 config B44_PCI_AUTOSELECT
1361 depends on B44 && SSB_PCIHOST_POSSIBLE
1365 # Auto-select SSB PCICORE driver, if possible
1366 config B44_PCICORE_AUTOSELECT
1368 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1369 select SSB_DRIVER_PCICORE
1374 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1378 tristate "nForce Ethernet support"
1379 depends on NET_PCI && PCI
1381 If you have a network (Ethernet) controller of this type, say Y and
1382 read the Ethernet-HOWTO, available from
1383 <http://www.tldp.org/docs.html#howto>.
1385 To compile this driver as a module, choose M here. The module
1386 will be called forcedeth.
1388 config FORCEDETH_NAPI
1389 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1390 depends on FORCEDETH && EXPERIMENTAL
1392 NAPI is a new driver API designed to reduce CPU and interrupt load
1393 when the driver is receiving lots of packets from the card. It is
1394 still somewhat experimental and thus not yet enabled by default.
1396 If your estimated Rx load is 10kpps or more, or if the card will be
1397 deployed on potentially unfriendly networks (e.g. in a firewall),
1403 tristate "CS89x0 support"
1404 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1406 Support for CS89x0 chipset based Ethernet cards. If you have a
1407 network (Ethernet) card of this type, say Y and read the
1408 Ethernet-HOWTO, available from
1409 <http://www.tldp.org/docs.html#howto> as well as
1410 <file:Documentation/networking/cs89x0.txt>.
1412 To compile this driver as a module, choose M here. The module
1413 will be called cs89x0.
1416 tristate "TOSHIBA TC35815 Ethernet support"
1417 depends on NET_PCI && PCI && MIPS
1421 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1422 depends on NET_PCI && PCI
1425 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1426 card, say Y and read the Ethernet-HOWTO, available from
1427 <http://www.tldp.org/docs.html#howto>.
1429 To compile this driver as a module, choose M here. The module
1430 will be called eepro100.
1434 tristate "Intel(R) PRO/100+ support"
1435 depends on NET_PCI && PCI
1438 This driver supports Intel(R) PRO/100 family of adapters.
1439 To verify that your adapter is supported, find the board ID number
1440 on the adapter. Look for a label that has a barcode and a number
1441 in the format 123456-001 (six digits hyphen three digits).
1443 Use the above information and the Adapter & Driver ID Guide at:
1445 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1447 to identify the adapter.
1449 For the latest Intel PRO/100 network driver for Linux, see:
1451 <http://appsr.intel.com/scripts-df/support_intel.asp>
1453 More specific information on configuring the driver is in
1454 <file:Documentation/networking/e100.txt>.
1456 To compile this driver as a module, choose M here. The module
1457 will be called e100.
1460 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1461 depends on NET_PCI && EISA && EXPERIMENTAL
1464 If you have a network (Ethernet) card of this type, say Y and read
1465 the Ethernet-HOWTO, available from
1466 <http://www.tldp.org/docs.html#howto>.
1468 To compile this driver as a module, choose M here. The module
1469 will be called lne390.
1472 tristate "Myson MTD-8xx PCI Ethernet support"
1473 depends on NET_PCI && PCI
1477 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1478 cards. Specifications and data at
1479 <http://www.myson.com.hk/mtd/datasheet/>.
1482 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1483 depends on NET_PCI && PCI
1486 This driver is for the National Semiconductor DP83810 series,
1487 which is used in cards from PureData, NetGear, Linksys
1488 and others, including the 83815 chip.
1489 More specific information and updates are available from
1490 <http://www.scyld.com/network/natsemi.html>.
1493 tristate "PCI NE2000 and clones support (see help)"
1494 depends on NET_PCI && PCI
1497 This driver is for NE2000 compatible PCI cards. It will not work
1498 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1499 support" below). If you have a PCI NE2000 network (Ethernet) card,
1500 say Y and read the Ethernet-HOWTO, available from
1501 <http://www.tldp.org/docs.html#howto>.
1503 This driver also works for the following NE2000 clone cards:
1504 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1505 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1506 Holtek HT80232 Holtek HT80229
1508 To compile this driver as a module, choose M here. The module
1509 will be called ne2k-pci.
1512 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1513 depends on NET_PCI && EISA && EXPERIMENTAL
1516 If you have a network (Ethernet) card of this type, say Y and read
1517 the Ethernet-HOWTO, available from
1518 <http://www.tldp.org/docs.html#howto>. Note that this driver
1519 will NOT WORK for NE3200 cards as they are completely different.
1521 To compile this driver as a module, choose M here. The module
1522 will be called ne3210.
1525 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1526 depends on NET_PCI && EISA && EXPERIMENTAL
1529 If you have a network (Ethernet) card of this type, say Y and read
1530 the Ethernet-HOWTO, available from
1531 <http://www.tldp.org/docs.html#howto>.
1533 To compile this driver as a module, choose M here. The module
1534 will be called es3210.
1537 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1538 depends on NET_PCI && PCI && EXPERIMENTAL
1542 This is a driver for the Fast Ethernet PCI network cards based on
1543 the RTL8139C+ chips. If you have one of those, say Y and read
1544 the Ethernet-HOWTO, available from
1545 <http://www.tldp.org/docs.html#howto>.
1547 To compile this driver as a module, choose M here: the module
1548 will be called 8139cp. This is recommended.
1551 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1552 depends on NET_PCI && PCI
1556 This is a driver for the Fast Ethernet PCI network cards based on
1557 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1558 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1560 To compile this driver as a module, choose M here: the module
1561 will be called 8139too. This is recommended.
1564 bool "Use PIO instead of MMIO"
1568 This instructs the driver to use programmed I/O ports (PIO) instead
1569 of PCI shared memory (MMIO). This can possibly solve some problems
1570 in case your mainboard has memory consistency issues. If unsure,
1573 config 8139TOO_TUNE_TWISTER
1574 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1577 This implements a function which might come in handy in case you
1578 are using low quality on long cabling. It is required for RealTek
1579 RTL-8139 revision K boards, and totally unused otherwise. It tries
1580 to match the transceiver to the cable characteristics. This is
1581 experimental since hardly documented by the manufacturer.
1585 bool "Support for older RTL-8129/8130 boards"
1588 This enables support for the older and uncommon RTL-8129 and
1589 RTL-8130 chips, which support MII via an external transceiver,
1590 instead of an internal one. Disabling this option will save some
1591 memory by making the code size smaller. If unsure, say Y.
1593 config 8139_OLD_RX_RESET
1594 bool "Use older RX-reset method"
1597 The 8139too driver was recently updated to contain a more rapid
1598 reset sequence, in the face of severe receive errors. This "new"
1599 RX-reset method should be adequate for all boards. But if you
1600 experience problems, you can enable this option to restore the
1601 old RX-reset behavior. If unsure, say N.
1604 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
1605 depends on NET_PCI && PCI
1609 This is a driver for the R6040 Fast Ethernet MACs found in the
1610 the RDC R-321x System-on-chips.
1612 To compile this driver as a module, choose M here: the module
1613 will be called r6040. This is recommended.
1616 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1617 depends on NET_PCI && PCI
1621 This is a driver for the Fast Ethernet PCI network cards based on
1622 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1623 SiS 630 and SiS 540 chipsets.
1625 This driver also supports AMD 79C901 HomePNA so that you can use
1626 your phone line as a network cable.
1628 To compile this driver as a module, choose M here: the module
1629 will be called sis900. This is recommended.
1632 tristate "SMC EtherPower II"
1633 depends on NET_PCI && PCI
1637 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1638 which is based on the SMC83c17x (EPIC/100).
1639 More specific information and updates are available from
1640 <http://www.scyld.com/network/epic100.html>.
1643 tristate "Sundance Alta support"
1644 depends on NET_PCI && PCI
1648 This driver is for the Sundance "Alta" chip.
1649 More specific information and updates are available from
1650 <http://www.scyld.com/network/sundance.html>.
1652 config SUNDANCE_MMIO
1653 bool "Use MMIO instead of PIO"
1656 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1657 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1658 is known to solve bugs on certain chips.
1663 tristate "TI ThunderLAN support"
1664 depends on NET_PCI && (PCI || EISA) && !64BIT
1666 If you have a PCI Ethernet network card based on the ThunderLAN chip
1667 which is supported by this driver, say Y and read the
1668 Ethernet-HOWTO, available from
1669 <http://www.tldp.org/docs.html#howto>.
1671 Devices currently supported by this driver are Compaq Netelligent,
1672 Compaq NetFlex and Olicom cards. Please read the file
1673 <file:Documentation/networking/tlan.txt> for more details.
1675 To compile this driver as a module, choose M here. The module
1676 will be called tlan.
1678 Please email feedback to <torben.mathiasen@compaq.com>.
1681 tristate "VIA Rhine support"
1682 depends on NET_PCI && PCI
1686 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1687 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1688 Ethernet functions can also be found integrated on South Bridges
1691 To compile this driver as a module, choose M here. The module
1692 will be called via-rhine.
1694 config VIA_RHINE_MMIO
1695 bool "Use MMIO instead of PIO"
1696 depends on VIA_RHINE
1698 This instructs the driver to use PCI shared memory (MMIO) instead of
1699 programmed I/O ports (PIO). Enabling this gives an improvement in
1700 processing time in parts of the driver.
1704 config VIA_RHINE_NAPI
1705 bool "Use Rx Polling (NAPI)"
1706 depends on VIA_RHINE
1708 NAPI is a new driver API designed to reduce CPU and interrupt load
1709 when the driver is receiving lots of packets from the card.
1711 If your estimated Rx load is 10kpps or more, or if the card will be
1712 deployed on potentially unfriendly networks (e.g. in a firewall),
1716 bool "Philips SAA9730 Ethernet support"
1717 depends on NET_PCI && PCI && MIPS_ATLAS
1719 The SAA9730 is a combined multimedia and peripheral controller used
1720 in thin clients, Internet access terminals, and diskless
1722 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1725 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1726 depends on NET_PCI && PCI && EXPERIMENTAL
1729 This is a driver for the Fast Ethernet PCI network cards based on
1730 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1731 have one of these, say Y here.
1733 To compile this driver as a module, choose M here: the module
1734 will be called sc92031. This is recommended.
1737 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1738 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1741 TI AR7 CPMAC Ethernet support
1744 bool "Pocket and portable adapters"
1747 Cute little network (Ethernet) devices which attach to the parallel
1748 port ("pocket adapters"), commonly used with laptops. If you have
1749 one of those, say Y and read the Ethernet-HOWTO, available from
1750 <http://www.tldp.org/docs.html#howto>.
1752 If you want to plug a network (or some other) card into the PCMCIA
1753 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1754 credit card size extension cards used by all modern laptops), you
1755 need the pcmcia-cs package (location contained in the file
1756 <file:Documentation/Changes>) and you can say N here.
1758 Laptop users should read the Linux Laptop home page at
1759 <http://www.linux-on-laptops.com/> or
1760 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1762 Note that the answer to this question doesn't directly affect the
1763 kernel: saying N will just cause the configurator to skip all
1764 the questions about this class of network devices. If you say Y, you
1765 will be asked for your specific device in the following questions.
1768 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1769 depends on NET_POCKET && PARPORT && X86
1772 This is a network (Ethernet) device which attaches to your parallel
1773 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1774 available from <http://www.tldp.org/docs.html#howto>, if you
1775 want to use this. If you intend to use this driver, you should have
1776 said N to the "Parallel printer support", because the two drivers
1777 don't like each other.
1779 To compile this driver as a module, choose M here: the module
1783 tristate "D-Link DE600 pocket adapter support"
1784 depends on NET_POCKET && PARPORT
1786 This is a network (Ethernet) device which attaches to your parallel
1787 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1788 Ethernet-HOWTO, available from
1789 <http://www.tldp.org/docs.html#howto>, if you want to use
1790 this. It is possible to have several devices share a single parallel
1791 port and it is safe to compile the corresponding drivers into the
1794 To compile this driver as a module, choose M here: the module
1795 will be called de600.
1798 tristate "D-Link DE620 pocket adapter support"
1799 depends on NET_POCKET && PARPORT
1801 This is a network (Ethernet) device which attaches to your parallel
1802 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1803 Ethernet-HOWTO, available from
1804 <http://www.tldp.org/docs.html#howto>, if you want to use
1805 this. It is possible to have several devices share a single parallel
1806 port and it is safe to compile the corresponding drivers into the
1809 To compile this driver as a module, choose M here: the module
1810 will be called de620.
1813 tristate "SGI Seeq ethernet controller support"
1814 depends on SGI_HAS_SEEQ
1816 Say Y here if you have an Seeq based Ethernet network card. This is
1817 used in many Silicon Graphics machines.
1820 tristate "DEC LANCE ethernet controller support"
1821 depends on MACH_DECSTATION
1824 This driver is for the series of Ethernet controllers produced by
1825 DEC (now Compaq) based on the AMD Lance chipset, including the
1826 DEPCA series. (This chipset is better known via the NE2100 cards.)
1829 bool "Motorola 68360 ethernet controller"
1832 Say Y here if you want to use the built-in ethernet controller of
1833 the Motorola 68360 processor.
1836 bool "FEC ethernet controller (of ColdFire CPUs)"
1837 depends on M523x || M527x || M5272 || M528x || M520x
1839 Say Y here if you want to use the built-in 10/100 Fast ethernet
1840 controller on some Motorola ColdFire processors.
1843 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1846 Say Y here if you want to use the second built-in 10/100 Fast
1847 ethernet controller on some Motorola ColdFire processors.
1850 tristate "MPC52xx FEC driver"
1851 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
1855 This option enables support for the MPC5200's on-chip
1856 Fast Ethernet Controller
1857 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1859 config FEC_MPC52xx_MDIO
1860 bool "MPC52xx FEC MDIO bus driver"
1861 depends on FEC_MPC52xx
1864 The MPC5200's FEC can connect to the Ethernet either with
1865 an external MII PHY chip or 10 Mbps 7-wire interface
1866 (Motorola? industry standard).
1867 If your board uses an external PHY connected to FEC, enable this.
1868 If not sure, enable.
1869 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1872 tristate "NE2000 compatible support for H8/300"
1875 Say Y here if you want to use the NE2000 compatible
1876 controller on the Renesas H8/300 processor.
1878 source "drivers/net/fs_enet/Kconfig"
1880 endif # NET_ETHERNET
1886 menuconfig NETDEV_1000
1887 bool "Ethernet (1000 Mbit)"
1891 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1892 type of Local Area Network (LAN) in universities and companies.
1894 Say Y here to get to see options for Gigabit Ethernet drivers.
1895 This option alone does not add any kernel code.
1896 Note that drivers supporting both 100 and 1000 MBit may be listed
1897 under "Ethernet (10 or 100MBit)" instead.
1899 If you say N, all options in this submenu will be skipped and disabled.
1904 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1907 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1908 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1909 adapter. The driver allows for using the Jumbo Frame option (9000
1910 bytes/frame) however it requires that your switches can handle this
1911 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1914 To compile this driver as a module, choose M here: the
1915 module will be called acenic.
1917 config ACENIC_OMIT_TIGON_I
1918 bool "Omit support for old Tigon I based AceNICs"
1921 Say Y here if you only have Tigon II based AceNICs and want to leave
1922 out support for the older Tigon I based cards which are no longer
1923 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1924 version)). This will reduce the size of the driver object by
1925 app. 100KB. If you are not sure whether your card is a Tigon I or a
1926 Tigon II, say N here.
1928 The safe and default value for this is N.
1931 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1935 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1937 D-Link DGE-550T Gigabit Ethernet Adapter.
1938 D-Link DL2000-based Gigabit Ethernet Adapter.
1939 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1941 To compile this driver as a module, choose M here: the
1942 module will be called dl2k.
1945 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1948 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1949 adapters. For more information on how to identify your adapter, go
1950 to the Adapter & Driver ID Guide at:
1952 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1954 For general information and support, go to the Intel support
1957 <http://support.intel.com>
1959 More specific information on configuring the driver is in
1960 <file:Documentation/networking/e1000.txt>.
1962 To compile this driver as a module, choose M here. The module
1963 will be called e1000.
1966 bool "Use Rx Polling (NAPI)"
1969 NAPI is a new driver API designed to reduce CPU and interrupt load
1970 when the driver is receiving lots of packets from the card. It is
1971 still somewhat experimental and thus not yet enabled by default.
1973 If your estimated Rx load is 10kpps or more, or if the card will be
1974 deployed on potentially unfriendly networks (e.g. in a firewall),
1979 config E1000_DISABLE_PACKET_SPLIT
1980 bool "Disable Packet Split for PCI express adapters"
1983 Say Y here if you want to use the legacy receive path for PCI express
1989 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1990 depends on PCI && (!SPARC32 || BROKEN)
1992 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1993 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1994 use the regular e1000 driver For more information on how to
1995 identify your adapter, go to the Adapter & Driver ID Guide at:
1997 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1999 For general information and support, go to the Intel support
2002 <http://support.intel.com>
2004 To compile this driver as a module, choose M here. The module
2005 will be called e1000e.
2007 config E1000E_ENABLED
2008 def_bool E1000E != n
2011 tristate "IP1000 Gigabit Ethernet support"
2012 depends on PCI && EXPERIMENTAL
2015 This driver supports IP1000 gigabit Ethernet cards.
2017 To compile this driver as a module, choose M here: the module
2018 will be called ipg. This is recommended.
2021 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
2024 This driver supports Intel(R) 82575 gigabit ethernet family of
2025 adapters. For more information on how to identify your adapter, go
2026 to the Adapter & Driver ID Guide at:
2028 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2030 For general information and support, go to the Intel support
2033 <http://support.intel.com>
2035 More specific information on configuring the driver is in
2036 <file:Documentation/networking/e1000.txt>.
2038 To compile this driver as a module, choose M here. The module
2041 source "drivers/net/ixp2000/Kconfig"
2044 tristate "MyriCOM Gigabit Ethernet support"
2047 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2049 To compile this driver as a module, choose M here: the module
2050 will be called myri_sbus. This is recommended.
2053 tristate "National Semiconductor DP83820 support"
2056 This is a driver for the National Semiconductor DP83820 series
2057 of gigabit ethernet MACs. Cards using this chipset include
2058 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2059 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2063 tristate "Packet Engines Hamachi GNIC-II support"
2067 If you have a Gigabit Ethernet card of this type, say Y and read
2068 the Ethernet-HOWTO, available from
2069 <http://www.tldp.org/docs.html#howto>.
2071 To compile this driver as a module, choose M here. The module will be
2075 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2076 depends on PCI && EXPERIMENTAL
2079 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2080 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2081 used by the Beowulf Linux cluster project. See
2082 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2083 information about this driver in particular and Beowulf in general.
2085 To compile this driver as a module, choose M here: the module
2086 will be called yellowfin. This is recommended.
2089 tristate "Realtek 8169 gigabit ethernet support"
2093 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2095 To compile this driver as a module, choose M here: the module
2096 will be called r8169. This is recommended.
2099 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2100 depends on R8169 && EXPERIMENTAL
2102 NAPI is a new driver API designed to reduce CPU and interrupt load
2103 when the driver is receiving lots of packets from the card. It is
2104 still somewhat experimental and thus not yet enabled by default.
2106 If your estimated Rx load is 10kpps or more, or if the card will be
2107 deployed on potentially unfriendly networks (e.g. in a firewall),
2114 depends on R8169 && VLAN_8021Q
2116 Say Y here for the r8169 driver to support the functions required
2117 by the kernel 802.1Q code.
2122 tristate "SB1250 Gigabit Ethernet support"
2123 depends on SIBYTE_SB1xxx_SOC
2126 This driver supports Gigabit Ethernet interfaces based on the
2127 Broadcom SiByte family of System-On-a-Chip parts. They include
2128 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2131 To compile this driver as a module, choose M here: the module
2132 will be called sb1250-mac.
2135 tristate "SiS190/SiS191 gigabit ethernet support"
2140 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2141 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2142 appear in lan on motherboard designs which are based on SiS 965
2143 and SiS 966 south bridge.
2145 To compile this driver as a module, choose M here: the module
2146 will be called sis190. This is recommended.
2149 tristate "New SysKonnect GigaEthernet support"
2153 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2154 and related Gigabit Ethernet adapters. It is a new smaller driver
2155 with better performance and more complete ethtool support.
2157 It does not support the link failover and network management
2158 features that "portable" vendor supplied sk98lin driver does.
2160 This driver supports adapters based on the original Yukon chipset:
2161 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2162 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2164 It does not support the newer Yukon2 chipset: a separate driver,
2165 sky2, is provided for Yukon2-based adapters.
2167 To compile this driver as a module, choose M here: the module
2168 will be called skge. This is recommended.
2171 bool "Debugging interface"
2172 depends on SKGE && DEBUG_FS
2174 This option adds the ability to dump driver state for debugging.
2175 The file debugfs/skge/ethX displays the state of the internal
2176 transmit and receive rings.
2181 tristate "SysKonnect Yukon2 support"
2185 This driver supports Gigabit Ethernet adapters based on the
2186 Marvell Yukon 2 chipset:
2187 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2188 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2190 There is companion driver for the older Marvell Yukon and
2191 Genesis based adapters: skge.
2193 To compile this driver as a module, choose M here: the module
2194 will be called sky2. This is recommended.
2197 bool "Debugging interface"
2198 depends on SKY2 && DEBUG_FS
2200 This option adds the ability to dump driver state for debugging.
2201 The file debugfs/sky2/ethX displays the state of the internal
2202 transmit and receive rings.
2207 tristate "VIA Velocity support"
2213 If you have a VIA "Velocity" based network card say Y here.
2215 To compile this driver as a module, choose M here. The module
2216 will be called via-velocity.
2219 tristate "Broadcom Tigon3 support"
2222 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2224 To compile this driver as a module, choose M here: the module
2225 will be called tg3. This is recommended.
2228 tristate "Broadcom NetXtremeII support"
2233 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2235 To compile this driver as a module, choose M here: the module
2236 will be called bnx2. This is recommended.
2239 tristate "Spider Gigabit Ethernet driver"
2240 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2243 This driver supports the Gigabit Ethernet chips present on the
2244 Cell Processor-Based Blades from IBM.
2247 tristate "Tundra TSI108 gigabit Ethernet support"
2248 depends on TSI108_BRIDGE
2250 This driver supports Tundra TSI108 gigabit Ethernet ports.
2251 To compile this driver as a module, choose M here: the module
2252 will be called tsi108_eth.
2255 tristate "PS3 Gigabit Ethernet driver"
2257 select PS3_SYS_MANAGER
2259 This driver supports the network device on the PS3 game
2260 console. This driver has built-in support for Ethernet.
2262 To compile this driver as a module, choose M here: the
2263 module will be called ps3_gelic.
2265 config GELIC_WIRELESS
2266 bool "PS3 Wireless support"
2267 depends on GELIC_NET
2270 This option adds the support for the wireless feature of PS3.
2271 If you have the wireless-less model of PS3 or have no plan to
2272 use wireless feature, disabling this option saves memory. As
2273 the driver automatically distinguishes the models, you can
2274 safely enable this option even if you have a wireless-less model.
2277 tristate "Gianfar Ethernet"
2282 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2283 and MPC86xx family of chips, and the FEC on the 8540.
2286 bool "Use Rx Polling (NAPI)"
2290 tristate "Freescale QE Gigabit Ethernet"
2291 depends on QUICC_ENGINE
2294 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2295 which is available on some Freescale SOCs.
2298 bool "Use Rx Polling (NAPI)"
2301 config UGETH_MAGIC_PACKET
2302 bool "Magic Packet detection support"
2305 config UGETH_FILTERING
2306 bool "Mac address filtering support"
2309 config UGETH_TX_ON_DEMAND
2310 bool "Transmit on Demand support"
2314 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2315 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2318 This driver supports the gigabit ethernet MACs in the
2319 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2320 in the Marvell Orion ARM SoC family.
2322 Some boards that use the Discovery chipset are the Momenco
2323 Ocelot C and Jaguar ATX and Pegasos II.
2326 tristate "QLogic QLA3XXX Network Driver Support"
2329 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2331 To compile this driver as a module, choose M here: the module
2332 will be called qla3xxx.
2335 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2336 depends on PCI && EXPERIMENTAL
2340 This driver supports the Attansic L1 gigabit ethernet adapter.
2342 To compile this driver as a module, choose M here. The module
2343 will be called atl1.
2348 # 10 Gigabit Ethernet
2351 menuconfig NETDEV_10000
2352 bool "Ethernet (10000 Mbit)"
2356 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2357 This option alone does not add any kernel code.
2359 If you say N, all options in this submenu will be skipped and disabled.
2364 tristate "Chelsio 10Gb Ethernet support"
2368 This driver supports Chelsio gigabit and 10-gigabit
2369 Ethernet cards. More information about adapter features and
2370 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2372 For general information about Chelsio and our products, visit
2373 our website at <http://www.chelsio.com>.
2375 For customer support, please visit our customer support page at
2376 <http://www.chelsio.com/support.htm>.
2378 Please send feedback to <linux-bugs@chelsio.com>.
2380 To compile this driver as a module, choose M here: the module
2381 will be called cxgb.
2383 config CHELSIO_T1_1G
2384 bool "Chelsio gigabit Ethernet support"
2385 depends on CHELSIO_T1
2387 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2388 are using only 10G cards say 'N' here.
2390 config CHELSIO_T1_NAPI
2391 bool "Use Rx Polling (NAPI)"
2392 depends on CHELSIO_T1
2395 NAPI is a driver API designed to reduce CPU and interrupt load
2396 when the driver is receiving lots of packets from the card.
2399 tristate "Chelsio Communications T3 10Gb Ethernet support"
2403 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2406 For general information about Chelsio and our products, visit
2407 our website at <http://www.chelsio.com>.
2409 For customer support, please visit our customer support page at
2410 <http://www.chelsio.com/support.htm>.
2412 Please send feedback to <linux-bugs@chelsio.com>.
2414 To compile this driver as a module, choose M here: the module
2415 will be called cxgb3.
2418 tristate "eHEA Ethernet support"
2419 depends on IBMEBUS && INET && SPARSEMEM
2422 This driver supports the IBM pSeries eHEA ethernet adapter.
2424 To compile the driver as a module, choose M here. The module
2425 will be called ehea.
2428 tristate "Intel(R) 10GbE PCI Express adapters support"
2431 This driver supports Intel(R) 10GbE PCI Express family of
2432 adapters. For more information on how to identify your adapter, go
2433 to the Adapter & Driver ID Guide at:
2435 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2437 For general information and support, go to the Intel support
2440 <http://support.intel.com>
2442 To compile this driver as a module, choose M here. The module
2443 will be called ixgbe.
2446 tristate "Intel(R) PRO/10GbE support"
2449 This driver supports Intel(R) PRO/10GbE family of adapters for
2450 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2451 instead. For more information on how to identify your adapter, go
2452 to the Adapter & Driver ID Guide at:
2454 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2456 For general information and support, go to the Intel support
2459 <http://support.intel.com>
2461 More specific information on configuring the driver is in
2462 <file:Documentation/networking/ixgb.txt>.
2464 To compile this driver as a module, choose M here. The module
2465 will be called ixgb.
2468 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2469 depends on IXGB && EXPERIMENTAL
2471 NAPI is a new driver API designed to reduce CPU and interrupt load
2472 when the driver is receiving lots of packets from the card. It is
2473 still somewhat experimental and thus not yet enabled by default.
2475 If your estimated Rx load is 10kpps or more, or if the card will be
2476 deployed on potentially unfriendly networks (e.g. in a firewall),
2482 tristate "S2IO 10Gbe XFrame NIC"
2485 This driver supports the 10Gbe XFrame NIC of S2IO.
2486 More specific information on configuring the driver is in
2487 <file:Documentation/networking/s2io.txt>.
2490 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2491 depends on S2IO && EXPERIMENTAL
2493 NAPI is a new driver API designed to reduce CPU and interrupt load
2494 when the driver is receiving lots of packets from the card. It is
2495 still somewhat experimental and thus not yet enabled by default.
2497 If your estimated Rx load is 10kpps or more, or if the card will be
2498 deployed on potentially unfriendly networks (e.g. in a firewall),
2504 tristate "Myricom Myri-10G Ethernet support"
2505 depends on PCI && INET
2510 This driver supports Myricom Myri-10G Dual Protocol interface in
2511 Ethernet mode. If the eeprom on your board is not recent enough,
2512 you will need a newer firmware image.
2513 You may get this image or more information, at:
2515 <http://www.myri.com/scs/download-Myri10GE.html>
2517 To compile this driver as a module, choose M here. The module
2518 will be called myri10ge.
2521 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2524 This enables the support for NetXen's Gigabit Ethernet card.
2527 tristate "Sun Neptune 10Gbit Ethernet support"
2530 This enables support for cards based upon Sun's
2534 tristate "PA Semi 1/10Gbit MAC"
2535 depends on PPC_PASEMI && PCI
2539 This driver supports the on-chip 1/10Gbit Ethernet controller on
2540 PA Semi's PWRficient line of chips.
2548 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2549 depends on MLX4_CORE
2552 This option causes debugging code to be compiled into the
2553 mlx4_core driver. The output can be turned on via the
2554 debug_level module parameter (which can also be set after
2555 the driver is loaded through sysfs).
2558 tristate "Tehuti Networks 10G Ethernet"
2561 Tehuti Networks 10G Ethernet NIC
2564 tristate "Broadcom NetXtremeII 10Gb support"
2568 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2569 To compile this driver as a module, choose M here: the module
2570 will be called bnx2x. This is recommended.
2572 source "drivers/net/sfc/Kconfig"
2574 endif # NETDEV_10000
2576 source "drivers/net/tokenring/Kconfig"
2578 source "drivers/net/wireless/Kconfig"
2580 source "drivers/net/usb/Kconfig"
2582 source "drivers/net/pcmcia/Kconfig"
2584 source "drivers/net/wan/Kconfig"
2586 source "drivers/atm/Kconfig"
2588 source "drivers/s390/net/Kconfig"
2590 config XEN_NETDEV_FRONTEND
2591 tristate "Xen network device frontend driver"
2595 The network device frontend driver allows the kernel to
2596 access network devices exported exported by a virtual
2597 machine containing a physical network device driver. The
2598 frontend driver is intended for unprivileged guest domains;
2599 if you are compiling a kernel for a Xen guest, you almost
2600 certainly want to enable this.
2603 tristate "iSeries Virtual Ethernet driver support"
2604 depends on PPC_ISERIES
2607 tristate "RapidIO Ethernet over messaging driver support"
2610 config RIONET_TX_SIZE
2611 int "Number of outbound queue entries"
2615 config RIONET_RX_SIZE
2616 int "Number of inbound queue entries"
2621 bool "FDDI driver support"
2622 depends on (PCI || EISA || TC)
2624 Fiber Distributed Data Interface is a high speed local area network
2625 design; essentially a replacement for high speed Ethernet. FDDI can
2626 run over copper or fiber. If you are connected to such a network and
2627 want a driver for the FDDI card in your computer, say Y here (and
2628 then also Y to the driver for your FDDI card, below). Most people
2632 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2633 depends on FDDI && (PCI || EISA || TC)
2635 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2636 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2637 to a local FDDI network.
2639 To compile this driver as a module, choose M here: the module
2640 will be called defxx. If unsure, say N.
2644 prompt "Use MMIO instead of PIO" if PCI || EISA
2646 default n if PCI || EISA
2649 This instructs the driver to use EISA or PCI memory-mapped I/O
2650 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2651 Enabling this gives an improvement in processing time in parts
2652 of the driver, but it may cause problems with EISA (DEFEA)
2653 adapters. TURBOchannel does not have the concept of I/O ports,
2654 so MMIO is always used for these (DEFTA) adapters.
2659 tristate "SysKonnect FDDI PCI support"
2660 depends on FDDI && PCI
2663 Say Y here if you have a SysKonnect FDDI PCI adapter.
2664 The following adapters are supported by this driver:
2665 - SK-5521 (SK-NET FDDI-UP)
2666 - SK-5522 (SK-NET FDDI-UP DAS)
2667 - SK-5541 (SK-NET FDDI-FP)
2668 - SK-5543 (SK-NET FDDI-LP)
2669 - SK-5544 (SK-NET FDDI-LP DAS)
2670 - SK-5821 (SK-NET FDDI-UP64)
2671 - SK-5822 (SK-NET FDDI-UP64 DAS)
2672 - SK-5841 (SK-NET FDDI-FP64)
2673 - SK-5843 (SK-NET FDDI-LP64)
2674 - SK-5844 (SK-NET FDDI-LP64 DAS)
2675 - Netelligent 100 FDDI DAS Fibre SC
2676 - Netelligent 100 FDDI SAS Fibre SC
2677 - Netelligent 100 FDDI DAS UTP
2678 - Netelligent 100 FDDI SAS UTP
2679 - Netelligent 100 FDDI SAS Fibre MIC
2681 Read <file:Documentation/networking/skfp.txt> for information about
2684 Questions concerning this driver can be addressed to:
2685 <linux@syskonnect.de>
2687 To compile this driver as a module, choose M here: the module
2688 will be called skfp. This is recommended.
2691 bool "HIPPI driver support (EXPERIMENTAL)"
2692 depends on EXPERIMENTAL && INET && PCI
2694 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2695 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2696 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2697 single-mode). HIPPI networks are commonly used for clusters and to
2698 connect to super computers. If you are connected to a HIPPI network
2699 and have a HIPPI network card in your computer that you want to use
2700 under Linux, say Y here (you must also remember to enable the driver
2701 for your HIPPI card below). Most people will say N here.
2704 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2705 depends on HIPPI && PCI
2707 Say Y here if this is your PCI HIPPI network card.
2709 To compile this driver as a module, choose M here: the module
2710 will be called rrunner. If unsure, say N.
2712 config ROADRUNNER_LARGE_RINGS
2713 bool "Use large TX/RX rings (EXPERIMENTAL)"
2714 depends on ROADRUNNER
2716 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2717 of additional memory to allow for fastest operation, both for
2718 transmitting and receiving. This memory cannot be used by any other
2719 kernel code or by user space programs. Say Y here only if you have
2723 tristate "PLIP (parallel port) support"
2726 PLIP (Parallel Line Internet Protocol) is used to create a
2727 reasonably fast mini network consisting of two (or, rarely, more)
2728 local machines. A PLIP link from a Linux box is a popular means to
2729 install a Linux distribution on a machine which doesn't have a
2730 CD-ROM drive (a minimal system has to be transferred with floppies
2731 first). The kernels on both machines need to have this PLIP option
2732 enabled for this to work.
2734 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2735 ports (the connectors at the computers with 25 holes) are connected
2736 with "null printer" or "Turbo Laplink" cables which can transmit 4
2737 bits at a time (mode 0) or with special PLIP cables, to be used on
2738 bidirectional parallel ports only, which can transmit 8 bits at a
2739 time (mode 1); you can find the wiring of these cables in
2740 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2741 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2742 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2743 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2744 and winsock or NCSA's telnet.
2746 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2747 as the NET-3-HOWTO, both available from
2748 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2749 protocol has been changed and this PLIP driver won't work together
2750 with the PLIP support in Linux versions 1.0.x. This option enlarges
2751 your kernel by about 8 KB.
2753 To compile this driver as a module, choose M here. The module
2754 will be called plip. If unsure, say Y or M, in case you buy
2758 tristate "PPP (point-to-point protocol) support"
2761 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2762 the same purpose: sending Internet traffic over telephone (and other
2763 serial) lines. Ask your access provider if they support it, because
2764 otherwise you can't use it; most Internet access providers these
2765 days support PPP rather than SLIP.
2767 To use PPP, you need an additional program called pppd as described
2768 in the PPP-HOWTO, available at
2769 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2770 the version of pppd recommended in <file:Documentation/Changes>.
2771 The PPP option enlarges your kernel by about 16 KB.
2773 There are actually two versions of PPP: the traditional PPP for
2774 asynchronous lines, such as regular analog phone lines, and
2775 synchronous PPP which can be used over digital ISDN lines for
2776 example. If you want to use PPP over phone lines or other
2777 asynchronous serial lines, you need to say Y (or M) here and also to
2778 the next option, "PPP support for async serial ports". For PPP over
2779 synchronous lines, you should say Y (or M) here and to "Support
2780 synchronous PPP", below.
2782 If you said Y to "Version information on all symbols" above, then
2783 you cannot compile the PPP driver into the kernel; you can then only
2784 compile it as a module. To compile this driver as a module, choose M
2785 here. The module will be called ppp_generic.
2787 config PPP_MULTILINK
2788 bool "PPP multilink support (EXPERIMENTAL)"
2789 depends on PPP && EXPERIMENTAL
2791 PPP multilink is a protocol (defined in RFC 1990) which allows you
2792 to combine several (logical or physical) lines into one logical PPP
2793 connection, so that you can utilize your full bandwidth.
2795 This has to be supported at the other end as well and you need a
2796 version of the pppd daemon which understands the multilink protocol.
2801 bool "PPP filtering"
2804 Say Y here if you want to be able to filter the packets passing over
2805 PPP interfaces. This allows you to control which packets count as
2806 activity (i.e. which packets will reset the idle timer or bring up
2807 a demand-dialed link) and which packets are to be dropped entirely.
2808 You need to say Y here if you wish to use the pass-filter and
2809 active-filter options to pppd.
2814 tristate "PPP support for async serial ports"
2818 Say Y (or M) here if you want to be able to use PPP over standard
2819 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2820 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2823 To compile this driver as a module, choose M here.
2828 tristate "PPP support for sync tty ports"
2831 Say Y (or M) here if you want to be able to use PPP over synchronous
2832 (HDLC) tty devices, such as the SyncLink adapter. These devices
2833 are often used for high-speed leased lines like T1/E1.
2835 To compile this driver as a module, choose M here.
2838 tristate "PPP Deflate compression"
2843 Support for the Deflate compression method for PPP, which uses the
2844 Deflate algorithm (the same algorithm that gzip uses) to compress
2845 each PPP packet before it is sent over the wire. The machine at the
2846 other end of the PPP link (usually your ISP) has to support the
2847 Deflate compression method as well for this to be useful. Even if
2848 they don't support it, it is safe to say Y here.
2850 To compile this driver as a module, choose M here.
2853 tristate "PPP BSD-Compress compression"
2856 Support for the BSD-Compress compression method for PPP, which uses
2857 the LZW compression method to compress each PPP packet before it is
2858 sent over the wire. The machine at the other end of the PPP link
2859 (usually your ISP) has to support the BSD-Compress compression
2860 method as well for this to be useful. Even if they don't support it,
2861 it is safe to say Y here.
2863 The PPP Deflate compression method ("PPP Deflate compression",
2864 above) is preferable to BSD-Compress, because it compresses better
2867 Note that the BSD compression code will always be compiled as a
2868 module; it is called bsd_comp and will show up in the directory
2869 modules once you have said "make modules". If unsure, say N.
2872 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2873 depends on PPP && EXPERIMENTAL
2879 Support for the MPPE Encryption protocol, as employed by the
2880 Microsoft Point-to-Point Tunneling Protocol.
2882 See http://pptpclient.sourceforge.net/ for information on
2883 configuring PPTP clients and servers to utilize this method.
2886 tristate "PPP over Ethernet (EXPERIMENTAL)"
2887 depends on EXPERIMENTAL && PPP
2889 Support for PPP over Ethernet.
2891 This driver requires the latest version of pppd from the CVS
2892 repository at cvs.samba.org. Alternatively, see the
2893 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2894 which contains instruction on how to use this driver (under
2895 the heading "Kernel mode PPPoE").
2898 tristate "PPP over ATM"
2899 depends on ATM && PPP
2901 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2902 This implementation does not yet comply with section 8 of RFC2364,
2903 which can lead to bad results if the ATM peer loses state and
2904 changes its encapsulation unilaterally.
2907 tristate "PPP over L2TP (EXPERIMENTAL)"
2908 depends on EXPERIMENTAL && PPP && INET
2910 Support for PPP-over-L2TP socket family. L2TP is a protocol
2911 used by ISPs and enterprises to tunnel PPP traffic over UDP
2912 tunnels. L2TP is replacing PPTP for VPN uses.
2914 This kernel component handles only L2TP data packets: a
2915 userland daemon handles L2TP the control protocol (tunnel
2916 and session setup). One such daemon is OpenL2TP
2917 (http://openl2tp.sourceforge.net/).
2920 tristate "SLIP (serial line) support"
2922 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2923 connect to your Internet service provider or to connect to some
2924 other local Unix box or if you want to configure your Linux box as a
2925 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2926 Internet Protocol) is a protocol used to send Internet traffic over
2927 serial connections such as telephone lines or null modem cables;
2928 nowadays, the protocol PPP is more commonly used for this same
2931 Normally, your access provider has to support SLIP in order for you
2932 to be able to use it, but there is now a SLIP emulator called SLiRP
2933 around (available from
2934 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2935 allows you to use SLIP over a regular dial up shell connection. If
2936 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2937 NET-3-HOWTO, available from
2938 <http://www.tldp.org/docs.html#howto>, explains how to
2939 configure SLIP. Note that you don't need this option if you just
2940 want to run term (term is a program which gives you almost full
2941 Internet connectivity if you have a regular dial up shell account on
2942 some Internet connected Unix computer. Read
2943 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2944 support will enlarge your kernel by about 4 KB. If unsure, say N.
2946 To compile this driver as a module, choose M here. The module
2947 will be called slip.
2949 config SLIP_COMPRESSED
2950 bool "CSLIP compressed headers"
2954 This protocol is faster than SLIP because it uses compression on the
2955 TCP/IP headers (not on the data itself), but it has to be supported
2956 on both ends. Ask your access provider if you are not sure and
2957 answer Y, just in case. You will still be able to use plain SLIP. If
2958 you plan to use SLiRP, the SLIP emulator (available from
2959 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2960 allows you to use SLIP over a regular dial up shell connection, you
2961 definitely want to say Y here. The NET-3-HOWTO, available from
2962 <http://www.tldp.org/docs.html#howto>, explains how to configure
2963 CSLIP. This won't enlarge your kernel.
2968 This option enables Van Jacobsen serial line header compression
2972 bool "Keepalive and linefill"
2975 Adds additional capabilities to the SLIP driver to support the
2976 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2979 config SLIP_MODE_SLIP6
2980 bool "Six bit SLIP encapsulation"
2983 Just occasionally you may need to run IP over hostile serial
2984 networks that don't pass all control characters or are only seven
2985 bit. Saying Y here adds an extra mode you can use with SLIP:
2986 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2987 the serial device. Naturally, this has to be supported at the other
2988 end of the link as well. It's good enough, for example, to run IP
2989 over the async ports of a Camtec JNT Pad. If unsure, say N.
2992 bool "Fibre Channel driver support"
2993 depends on SCSI && PCI
2995 Fibre Channel is a high speed serial protocol mainly used to connect
2996 large storage devices to the computer; it is compatible with and
2997 intended to replace SCSI.
2999 If you intend to use Fibre Channel, you need to have a Fibre channel
3000 adaptor card in your computer; say Y here and to the driver for your
3001 adaptor below. You also should have said Y to "SCSI support" and
3002 "SCSI generic support".
3005 tristate "Network console logging support (EXPERIMENTAL)"
3006 depends on EXPERIMENTAL
3008 If you want to log kernel messages over the network, enable this.
3009 See <file:Documentation/networking/netconsole.txt> for details.
3011 config NETCONSOLE_DYNAMIC
3012 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3013 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3016 This option enables the ability to dynamically reconfigure target
3017 parameters (interface, IP addresses, port numbers, MAC addresses)
3018 at runtime through a userspace interface exported using configfs.
3019 See <file:Documentation/networking/netconsole.txt> for details.
3025 bool "Netpoll traffic trapping"
3029 config NET_POLL_CONTROLLER
3033 tristate "Virtio network driver (EXPERIMENTAL)"
3034 depends on EXPERIMENTAL && VIRTIO
3036 This is the virtual network driver for virtio. It can be used with
3037 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.