2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 menuconfig NET_ETHERNET
199 bool "Ethernet (10 or 100Mbit)"
202 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
203 type of Local Area Network (LAN) in universities and companies.
205 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
206 coaxial cable, linking computers in a chain), 10BASE-T or twisted
207 pair (10 Mbps over twisted pair cable, linking computers to central
208 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
209 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
210 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
211 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
212 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
213 Ethernet (1 Gbps over optical fiber or short copper links).
215 If your Linux machine will be connected to an Ethernet and you have
216 an Ethernet network interface card (NIC) installed in your computer,
217 say Y here and read the Ethernet-HOWTO, available from
218 <http://www.tldp.org/docs.html#howto>. You will then also have
219 to say Y to the driver for your particular NIC.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about Ethernet network cards. If unsure, say N.
228 tristate "Atmel MACB support"
229 depends on HAVE_NET_MACB
232 The Atmel MACB ethernet interface is found on many AT32 and AT91
233 parts. Say Y to include support for the MACB chip.
235 To compile this driver as a module, choose M here: the module
238 source "drivers/net/arm/Kconfig"
241 tristate "ASIX AX88796 NE2000 clone support"
242 depends on ARM || MIPS || SUPERH
246 AX88796 driver, using platform bus to provide
247 chip detection and resources
250 bool "ASIX AX88796 external 93CX6 eeprom support"
254 Select this if your platform comes with an external 93CX6 eeprom.
257 tristate "MACE (Power Mac ethernet) support"
258 depends on PPC_PMAC && PPC32
261 Power Macintoshes and clones with Ethernet built-in on the
262 motherboard will usually use a MACE (Medium Access Control for
263 Ethernet) interface. Say Y to include support for the MACE chip.
265 To compile this driver as a module, choose M here: the module
268 config MACE_AAUI_PORT
269 bool "Use AAUI port instead of TP by default"
272 Some Apple machines (notably the Apple Network Server) which use the
273 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
274 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
275 Y here if you have such a machine. If unsure, say N.
276 The driver will default to AAUI on ANS anyway, and if you use it as
277 a module, you can provide the port_aaui=0|1 to force the driver.
280 tristate "BMAC (G3 ethernet) support"
281 depends on PPC_PMAC && PPC32
284 Say Y for support of BMAC Ethernet interfaces. These are used on G3
287 To compile this driver as a module, choose M here: the module
291 tristate "Ariadne support"
294 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
297 To compile this driver as a module, choose M here: the module
298 will be called ariadne.
301 tristate "A2065 support"
305 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
308 To compile this driver as a module, choose M here: the module
309 will be called a2065.
312 tristate "Hydra support"
316 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
318 To compile this driver as a module, choose M here: the module
319 will be called hydra.
322 tristate "Zorro NS8390-based Ethernet support"
326 This driver is for Zorro Ethernet cards using an NS8390-compatible
327 chipset, like the Village Tronic Ariadne II and the Individual
328 Computers X-Surf Ethernet cards. If you have such a card, say Y.
331 To compile this driver as a module, choose M here: the module
332 will be called zorro8390.
335 tristate "PCMCIA NE2000 support"
336 depends on AMIGA_PCMCIA
339 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
342 To compile this driver as a module, choose M here: the module
346 bool "Macintosh NS 8390 based ethernet cards"
350 If you want to include a driver to support Nubus or LC-PDS
351 Ethernet cards using an NS8390 chipset or its equivalent, say Y
352 and read the Ethernet-HOWTO, available from
353 <http://www.tldp.org/docs.html#howto>.
356 tristate "Macintosh CS89x0 based ethernet cards"
359 Support for CS89x0 chipset based Ethernet cards. If you have a
360 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
361 read the Ethernet-HOWTO, available from
362 <http://www.tldp.org/docs.html#howto>.
364 To compile this driver as a module, choose M here. This module will
368 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
371 Support for NatSemi SONIC based Ethernet devices. This includes
372 the onboard Ethernet in many Quadras as well as some LC-PDS,
373 a few Nubus and all known Comm Slot Ethernet cards. If you have
374 one of these say Y and read the Ethernet-HOWTO, available from
375 <http://www.tldp.org/docs.html#howto>.
377 To compile this driver as a module, choose M here. This module will
381 bool "Macintosh (AV) onboard MACE ethernet"
385 Support for the onboard AMD 79C940 MACE Ethernet controller used in
386 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
387 say Y and read the Ethernet-HOWTO, available from
388 <http://www.tldp.org/docs.html#howto>.
391 tristate "MVME147 (Lance) Ethernet support"
395 Support for the on-board Ethernet interface on the Motorola MVME147
396 single-board computer. Say Y here to include the
397 driver for this chip in your kernel.
398 To compile this driver as a module, choose M here.
401 tristate "MVME16x Ethernet support"
404 This is the driver for the Ethernet interface on the Motorola
405 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
406 driver for this chip in your kernel.
407 To compile this driver as a module, choose M here.
410 tristate "BVME6000 Ethernet support"
413 This is the driver for the Ethernet interface on BVME4000 and
414 BVME6000 VME boards. Say Y here to include the driver for this chip
416 To compile this driver as a module, choose M here.
419 tristate "Atari Lance support"
422 Say Y to include support for several Atari Ethernet adapters based
423 on the AMD Lance chipset: RieblCard (with or without battery), or
424 PAMCard VME (also the version by Rhotron, with different addresses).
427 tristate "Sun3/Sun3x on-board LANCE support"
428 depends on SUN3 || SUN3X
430 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
431 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
432 here to compile in the Linux driver for this and enable Ethernet.
433 General Linux information on the Sun 3 and 3x series (now
435 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
437 If you're not building a kernel for a Sun 3, say N.
440 bool "Sun3 on-board Intel 82586 support"
443 This driver enables support for the on-board Intel 82586 based
444 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
445 that this driver does not support 82586-based adapters on additional
449 bool "HP on-board LANCE support"
453 If you want to use the builtin "LANCE" Ethernet controller on an
454 HP300 machine, say Y here.
457 tristate "Lasi ethernet"
460 Say Y here to support the builtin Intel 82596 ethernet controller
461 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
464 tristate "SNI RM ethernet"
465 depends on NET_ETHERNET && SNI_RM
467 Say Y here to support the on-board Intel 82596 ethernet controller
468 built into SNI RM machines.
471 tristate "Korina (IDT RC32434) Ethernet support"
472 depends on NET_ETHERNET && MIKROTIK_RB532
474 If you have a Mikrotik RouterBoard 500 or IDT RC32434
475 based system say Y. Otherwise say N.
477 config MIPS_JAZZ_SONIC
478 tristate "MIPS JAZZ onboard SONIC Ethernet support"
481 This is the driver for the onboard card of MIPS Magnum 4000,
482 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
484 config XTENSA_XT2000_SONIC
485 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
486 depends on XTENSA_PLATFORM_XT2000
488 This is the driver for the onboard card of the Xtensa XT2000 board.
490 config MIPS_AU1X00_ENET
491 tristate "MIPS AU1000 Ethernet support"
492 depends on MIPS_ALCHEMY
496 If you have an Alchemy Semi AU1X00 based system
497 say Y. Otherwise, say N.
500 bool "SGI IOC3 Ethernet"
501 depends on PCI && SGI_IP27
505 If you have a network (Ethernet) card of this type, say Y and read
506 the Ethernet-HOWTO, available from
507 <http://www.tldp.org/docs.html#howto>.
510 tristate "MIPS simulator Network device"
513 The MIPSNET device is a simple Ethernet network device which is
514 emulated by the MIPS Simulator.
515 If you are not using a MIPSsim or are unsure, say N.
517 config SGI_O2MACE_ETH
518 tristate "SGI O2 MACE Fast Ethernet support"
519 depends on SGI_IP32=y
522 tristate "National DP83902AV support"
526 Support for cards based on the National Semiconductor DP83902AV
527 ST-NIC Serial Network Interface Controller for Twisted Pair. This
528 is a 10Mbit/sec Ethernet controller. Product overview and specs at
529 <http://www.national.com/pf/DP/DP83902A.html>.
534 tristate "Renesas SuperH Ethernet support"
535 depends on SUPERH && \
536 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
537 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
538 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
544 Renesas SuperH Ethernet device driver.
545 This driver supporting CPUs are:
546 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
549 tristate "Sun LANCE support"
553 This driver supports the "le" interface present on all 32-bit Sparc
554 systems, on some older Ultra systems and as an Sbus option. These
555 cards are based on the AMD Lance chipset, which is better known
556 via the NE2100 cards.
558 To compile this driver as a module, choose M here: the module
559 will be called sunlance.
562 tristate "Sun Happy Meal 10/100baseT support"
563 depends on SBUS || PCI
566 This driver supports the "hme" interface present on most Ultra
567 systems and as an option on older Sbus systems. This driver supports
568 both PCI and Sbus devices. This driver also supports the "qfe" quad
569 100baseT device available in both PCI and Sbus configurations.
571 To compile this driver as a module, choose M here: the module
572 will be called sunhme.
575 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
576 depends on SBUS && EXPERIMENTAL
579 This driver supports the "be" interface available as an Sbus option.
580 This is Sun's older 100baseT Ethernet device.
582 To compile this driver as a module, choose M here: the module
583 will be called sunbmac.
586 tristate "Sun QuadEthernet support"
590 This driver supports the "qe" 10baseT Ethernet device, available as
591 an Sbus option. Note that this is not the same as Quad FastEthernet
592 "qfe" which is supported by the Happy Meal driver instead.
594 To compile this driver as a module, choose M here: the module
595 will be called sunqe.
598 tristate "Sun GEM support"
602 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
603 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
606 tristate "Sun Cassini support"
610 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
611 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
614 tristate "Sun Virtual Network support"
617 Support for virtual network devices under Sun Logical Domains.
619 config NET_VENDOR_3COM
621 depends on ISA || EISA || MCA || PCI
623 If you have a network (Ethernet) card belonging to this class, say Y
624 and read the Ethernet-HOWTO, available from
625 <http://www.tldp.org/docs.html#howto>.
627 Note that the answer to this question doesn't directly affect the
628 kernel: saying N will just cause the configurator to skip all
629 the questions about 3COM cards. If you say Y, you will be asked for
630 your specific card in the following questions.
633 tristate "3c501 \"EtherLink\" support"
634 depends on NET_VENDOR_3COM && ISA
636 If you have a network (Ethernet) card of this type, say Y and read
637 the Ethernet-HOWTO, available from
638 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
639 new card, since the 3c501 is slow, broken, and obsolete: you will
640 have problems. Some people suggest to ping ("man ping") a nearby
641 machine every minute ("man cron") when using this card.
643 To compile this driver as a module, choose M here. The module
644 will be called 3c501.
647 tristate "3c503 \"EtherLink II\" support"
648 depends on NET_VENDOR_3COM && ISA
651 If you have a network (Ethernet) card of this type, say Y and read
652 the Ethernet-HOWTO, available from
653 <http://www.tldp.org/docs.html#howto>.
655 To compile this driver as a module, choose M here. The module
656 will be called 3c503.
659 tristate "3c505 \"EtherLink Plus\" support"
660 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
662 Information about this network (Ethernet) card can be found in
663 <file:Documentation/networking/3c505.txt>. If you have a card of
664 this type, say Y and read the Ethernet-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>.
667 To compile this driver as a module, choose M here. The module
668 will be called 3c505.
671 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
672 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
674 If you have a network (Ethernet) card of this type, say Y and read
675 the Ethernet-HOWTO, available from
676 <http://www.tldp.org/docs.html#howto>.
678 To compile this driver as a module, choose M here. The module
679 will be called 3c507.
682 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
683 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
685 If you have a network (Ethernet) card belonging to the 3Com
686 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
687 from <http://www.tldp.org/docs.html#howto>.
689 If your card is not working you may need to use the DOS
690 setup disk to disable Plug & Play mode, and to select the default
693 To compile this driver as a module, choose M here. The module
694 will be called 3c509.
697 tristate "3c515 ISA \"Fast EtherLink\""
698 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
700 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
701 network card, say Y and read the Ethernet-HOWTO, available from
702 <http://www.tldp.org/docs.html#howto>.
704 To compile this driver as a module, choose M here. The module
705 will be called 3c515.
708 tristate "3c523 \"EtherLink/MC\" support"
709 depends on NET_VENDOR_3COM && MCA_LEGACY
711 If you have a network (Ethernet) card of this type, say Y and read
712 the Ethernet-HOWTO, available from
713 <http://www.tldp.org/docs.html#howto>.
715 To compile this driver as a module, choose M here. The module
716 will be called 3c523.
719 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
720 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
722 If you have a network (Ethernet) card of this type, say Y and read
723 the Ethernet-HOWTO, available from
724 <http://www.tldp.org/docs.html#howto>.
726 To compile this driver as a module, choose M here. The module
727 will be called 3c527.
730 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
731 depends on NET_VENDOR_3COM && (PCI || EISA)
734 This option enables driver support for a large number of 10Mbps and
735 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
737 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
738 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
739 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
740 "Tornado" (3c905) PCI
741 "Hurricane" (3c555/3cSOHO) PCI
743 If you have such a card, say Y and read the Ethernet-HOWTO,
744 available from <http://www.tldp.org/docs.html#howto>. More
745 specific information is in
746 <file:Documentation/networking/vortex.txt> and in the comments at
747 the beginning of <file:drivers/net/3c59x.c>.
749 To compile this support as a module, choose M here.
752 tristate "3cr990 series \"Typhoon\" support"
753 depends on NET_VENDOR_3COM && PCI
756 This option enables driver support for the 3cr990 series of cards:
758 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
759 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
760 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
762 If you have a network (Ethernet) card of this type, say Y and read
763 the Ethernet-HOWTO, available from
764 <http://www.tldp.org/docs.html#howto>.
766 To compile this driver as a module, choose M here. The module
767 will be called typhoon.
770 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
771 depends on ISA && ISA_DMA_API
773 If you have a network (Ethernet) card of this type, say Y and read
774 the Ethernet-HOWTO, available from
775 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
778 To compile this driver as a module, choose M here: the module
779 will be called lance. This is recommended.
781 config NET_VENDOR_SMC
782 bool "Western Digital/SMC cards"
783 depends on ISA || MCA || EISA || MAC
785 If you have a network (Ethernet) card belonging to this class, say Y
786 and read the Ethernet-HOWTO, available from
787 <http://www.tldp.org/docs.html#howto>.
789 Note that the answer to this question doesn't directly affect the
790 kernel: saying N will just cause the configurator to skip all
791 the questions about Western Digital cards. If you say Y, you will be
792 asked for your specific card in the following questions.
795 tristate "WD80*3 support"
796 depends on NET_VENDOR_SMC && ISA
799 If you have a network (Ethernet) card of this type, say Y and read
800 the Ethernet-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>.
803 To compile this driver as a module, choose M here. The module
807 tristate "SMC Ultra MCA support"
808 depends on NET_VENDOR_SMC && MCA
811 If you have a network (Ethernet) card of this type and are running
812 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
813 available from <http://www.tldp.org/docs.html#howto>.
815 To compile this driver as a module, choose M here. The module
816 will be called smc-mca.
819 tristate "SMC Ultra support"
820 depends on NET_VENDOR_SMC && ISA
823 If you have a network (Ethernet) card of this type, say Y and read
824 the Ethernet-HOWTO, available from
825 <http://www.tldp.org/docs.html#howto>.
827 Important: There have been many reports that, with some motherboards
828 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
829 such as some BusLogic models) causes corruption problems with many
830 operating systems. The Linux smc-ultra driver has a work-around for
831 this but keep it in mind if you have such a SCSI card and have
834 To compile this driver as a module, choose M here. The module
835 will be called smc-ultra.
838 tristate "SMC Ultra32 EISA support"
839 depends on NET_VENDOR_SMC && EISA
842 If you have a network (Ethernet) card of this type, say Y and read
843 the Ethernet-HOWTO, available from
844 <http://www.tldp.org/docs.html#howto>.
846 To compile this driver as a module, choose M here. The module
847 will be called smc-ultra32.
850 tristate "Blackfin on-chip MAC support"
851 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
855 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
857 This is the driver for Blackfin on-chip mac device. Say Y if you want it
858 compiled into the kernel. This driver is also available as a module
859 ( = code which can be inserted in and removed from the running kernel
860 whenever you want). The module will be called bfin_mac.
862 config BFIN_MAC_USE_L1
863 bool "Use L1 memory for rx/tx packets"
864 depends on BFIN_MAC && (BF527 || BF537)
867 To get maximum network performance, you should use L1 memory as rx/tx buffers.
868 Say N here if you want to reserve L1 memory for other uses.
870 config BFIN_TX_DESC_NUM
871 int "Number of transmit buffer packets"
873 range 6 10 if BFIN_MAC_USE_L1
877 Set the number of buffer packets used in driver.
879 config BFIN_RX_DESC_NUM
880 int "Number of receive buffer packets"
882 range 20 100 if BFIN_MAC_USE_L1
886 Set the number of buffer packets used in driver.
888 config BFIN_MAC_USE_HWSTAMP
889 bool "Use IEEE 1588 hwstamp"
890 depends on BFIN_MAC && BF518
893 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
896 tristate "SMC 9194 support"
897 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
900 This is support for the SMC9xxx based Ethernet cards. Choose this
901 option if you have a DELL laptop with the docking station, or
902 another SMC9192/9194 based chipset. Say Y if you want it compiled
903 into the kernel, and read the file
904 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
905 available from <http://www.tldp.org/docs.html#howto>.
907 To compile this driver as a module, choose M here. The module
908 will be called smc9194.
911 tristate "SMC 91C9x/91C1xxx support"
914 depends on ARM || M32R || SUPERH || \
915 MIPS || BLACKFIN || MN10300 || COLDFIRE
917 This is a driver for SMC's 91x series of Ethernet chipsets,
918 including the SMC91C94 and the SMC91C111. Say Y if you want it
919 compiled into the kernel, and read the file
920 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
921 available from <http://www.tldp.org/docs.html#howto>.
923 This driver is also available as a module ( = code which can be
924 inserted in and removed from the running kernel whenever you want).
925 The module will be called smc91x. If you want to compile it as a
926 module, say M here and read <file:Documentation/kbuild/modules.txt>.
929 tristate "Marvell pxa168 ethernet support"
930 depends on CPU_PXA168
933 This driver supports the pxa168 Ethernet ports.
935 To compile this driver as a module, choose M here. The module
936 will be called pxa168_eth.
939 tristate "NetX Ethernet support"
943 This is support for the Hilscher netX builtin Ethernet ports
945 To compile this driver as a module, choose M here. The module
946 will be called netx-eth.
948 config TI_DAVINCI_EMAC
949 tristate "TI DaVinci EMAC Support"
950 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
951 select TI_DAVINCI_MDIO
952 select TI_DAVINCI_CPDMA
955 This driver supports TI's DaVinci Ethernet .
957 To compile this driver as a module, choose M here: the module
958 will be called davinci_emac_driver. This is recommended.
960 config TI_DAVINCI_MDIO
961 tristate "TI DaVinci MDIO Support"
962 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
965 This driver supports TI's DaVinci MDIO module.
967 To compile this driver as a module, choose M here: the module
968 will be called davinci_mdio. This is recommended.
970 config TI_DAVINCI_CPDMA
971 tristate "TI DaVinci CPDMA Support"
972 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
974 This driver supports TI's DaVinci CPDMA dma engine.
976 To compile this driver as a module, choose M here: the module
977 will be called davinci_cpdma. This is recommended.
980 tristate "DM9000 support"
981 depends on ARM || BLACKFIN || MIPS
985 Support for DM9000 chipset.
987 To compile this driver as a module, choose M here. The module
988 will be called dm9000.
990 config DM9000_DEBUGLEVEL
991 int "DM9000 maximum debug level"
995 The maximum level of debugging code compiled into the DM9000
998 config DM9000_FORCE_SIMPLE_PHY_POLL
999 bool "Force simple NSR based PHY polling"
1002 This configuration forces the DM9000 to use the NSR's LinkStatus
1003 bit to determine if the link is up or down instead of the more
1004 costly MII PHY reads. Note, this will not work if the chip is
1005 operating with an external PHY.
1008 tristate "ENC28J60 support"
1009 depends on EXPERIMENTAL && SPI && NET_ETHERNET
1012 Support for the Microchip EN28J60 ethernet chip.
1014 To compile this driver as a module, choose M here. The module will be
1017 config ENC28J60_WRITEVERIFY
1018 bool "Enable write verify"
1021 Enable the verify after the buffer write useful for debugging purpose.
1025 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
1026 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1032 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1035 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1040 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1043 tristate "SMSC LAN911[5678] support"
1046 depends on ARM || SUPERH || MN10300
1048 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1049 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1050 Say Y if you want it compiled into the kernel,
1051 and read the Ethernet-HOWTO, available from
1052 <http://www.tldp.org/docs.html#howto>.
1054 This driver is also available as a module. The module will be
1055 called smc911x. If you want to compile it as a module, say M
1056 here and read <file:Documentation/kbuild/modules.txt>
1059 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1060 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
1065 Say Y here if you want support for SMSC LAN911x and LAN921x families
1066 of ethernet controllers.
1068 To compile this driver as a module, choose M here and read
1069 <file:Documentation/networking/net-modules.txt>. The module
1070 will be called smsc911x.
1072 config SMSC911X_ARCH_HOOKS
1076 If the arch enables this, it allows the arch to implement various
1077 hooks for more comprehensive interrupt control and also to override
1078 the source of the MAC address.
1080 config NET_VENDOR_RACAL
1081 bool "Racal-Interlan (Micom) NI cards"
1084 If you have a network (Ethernet) card belonging to this class, such
1085 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1086 available from <http://www.tldp.org/docs.html#howto>.
1088 Note that the answer to this question doesn't directly affect the
1089 kernel: saying N will just cause the configurator to skip all
1090 the questions about NI cards. If you say Y, you will be asked for
1091 your specific card in the following questions.
1094 tristate "NI5010 support (EXPERIMENTAL)"
1095 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1097 If you have a network (Ethernet) card of this type, say Y and read
1098 the Ethernet-HOWTO, available from
1099 <http://www.tldp.org/docs.html#howto>. Note that this is still
1102 To compile this driver as a module, choose M here. The module
1103 will be called ni5010.
1106 tristate "NI5210 support"
1107 depends on NET_VENDOR_RACAL && ISA
1109 If you have a network (Ethernet) card of this type, say Y and read
1110 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 ni52.
1117 tristate "NI6510 support"
1118 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1120 If you have a network (Ethernet) card of this type, say Y and read
1121 the Ethernet-HOWTO, available from
1122 <http://www.tldp.org/docs.html#howto>.
1124 To compile this driver as a module, choose M here. The module
1125 will be called ni65.
1128 tristate "Dave ethernet support (DNET)"
1129 depends on NET_ETHERNET && HAS_IOMEM
1132 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1133 Say Y to include support for the DNET chip.
1135 To compile this driver as a module, choose M here: the module
1136 will be called dnet.
1138 source "drivers/net/tulip/Kconfig"
1141 tristate "AT1700/1720 support (EXPERIMENTAL)"
1142 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1145 If you have a network (Ethernet) card of this type, say Y and read
1146 the Ethernet-HOWTO, available from
1147 <http://www.tldp.org/docs.html#howto>.
1149 To compile this driver as a module, choose M here. The module
1150 will be called at1700.
1153 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1154 depends on ISA || EISA || MCA
1157 If you have a network (Ethernet) card of this type, say Y and read
1158 the Ethernet-HOWTO, available from
1159 <http://www.tldp.org/docs.html#howto> as well as
1160 <file:drivers/net/depca.c>.
1162 To compile this driver as a module, choose M here. The module
1163 will be called depca.
1166 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1167 depends on ISA || EISA || PCI
1169 If you have a network (Ethernet) card of this type, say Y and read
1170 the Ethernet-HOWTO, available from
1171 <http://www.tldp.org/docs.html#howto>.
1173 To compile this driver as a module, choose M here. The module
1174 will be called hp100.
1177 bool "Other ISA cards"
1180 If your network (Ethernet) card hasn't been mentioned yet and its
1181 bus system (that's the way the cards talks to the other components
1182 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1183 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1184 available from <http://www.tldp.org/docs.html#howto>.
1188 Note that the answer to this question doesn't directly affect the
1189 kernel: saying N will just cause the configurator to skip all
1190 the remaining ISA network card questions. If you say Y, you will be
1191 asked for your specific card in the following questions.
1194 tristate "Cabletron E21xx support"
1198 If you have a network (Ethernet) card of this type, say Y and read
1199 the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here. The module
1203 will be called e2100.
1206 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1210 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1211 cards. If this is for you, say Y and read
1212 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1213 well as the Ethernet-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>.
1216 To compile this driver as a module, choose M here. The module
1217 will be called ewrk3.
1220 tristate "EtherExpress 16 support"
1223 If you have an EtherExpress16 network (Ethernet) card, say Y and
1224 read the Ethernet-HOWTO, available from
1225 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1226 EtherExpress16 card used to be regarded as a very poor choice
1227 because the driver was very unreliable. We now have a new driver
1228 that should do better.
1230 To compile this driver as a module, choose M here. The module
1231 will be called eexpress.
1234 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1237 If you have a network (Ethernet) card of this type, say Y. This
1238 driver supports Intel i82595{FX,TX} based boards. Note however
1239 that the EtherExpress PRO/100 Ethernet card has its own separate
1240 driver. Please read the Ethernet-HOWTO, available from
1241 <http://www.tldp.org/docs.html#howto>.
1243 To compile this driver as a module, choose M here. The module
1244 will be called eepro.
1247 tristate "HP PCLAN+ (27247B and 27252A) support"
1251 If you have a network (Ethernet) card of this type, say Y and read
1252 the Ethernet-HOWTO, available from
1253 <http://www.tldp.org/docs.html#howto>.
1255 To compile this driver as a module, choose M here. The module
1256 will be called hp-plus.
1259 tristate "HP PCLAN (27245 and other 27xxx series) support"
1263 If you have a network (Ethernet) card of this type, say Y and read
1264 the Ethernet-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>.
1267 To compile this driver as a module, choose M here. The module
1271 tristate "LP486E on board Ethernet"
1274 Say Y here to support the 82596-based on-board Ethernet controller
1275 for the Panther motherboard, which is one of the two shipped in the
1276 Intel Professional Workstation.
1279 tristate "ICL EtherTeam 16i/32 support"
1282 If you have a network (Ethernet) card of this type, say Y and read
1283 the Ethernet-HOWTO, available from
1284 <http://www.tldp.org/docs.html#howto>.
1286 To compile this driver as a module, choose M here. The module
1287 will be called eth16i.
1290 tristate "NE2000/NE1000 support"
1291 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1294 If you have a network (Ethernet) card of this type, say Y and read
1295 the Ethernet-HOWTO, available from
1296 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1297 without a specific driver are compatible with NE2000.
1299 If you have a PCI NE2000 card however, say N here and Y to "PCI
1300 NE2000 and clone support" under "EISA, VLB, PCI and on board
1301 controllers" below. If you have a NE2000 card and are running on
1302 an MCA system (a bus system used on some IBM PS/2 computers and
1303 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1306 To compile this driver as a module, choose M here. The module
1310 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1311 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1313 The Zenith Z-Note notebook computer has a built-in network
1314 (Ethernet) card, and this is the Linux driver for it. Note that the
1315 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1316 by this driver. Read the Ethernet-HOWTO, available from
1317 <http://www.tldp.org/docs.html#howto>.
1320 tristate "SEEQ8005 support (EXPERIMENTAL)"
1321 depends on NET_ISA && EXPERIMENTAL
1323 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1324 is for you, read the Ethernet-HOWTO, available from
1325 <http://www.tldp.org/docs.html#howto>.
1327 To compile this driver as a module, choose M here. The module
1328 will be called seeq8005.
1331 tristate "NE/2 (ne2000 MCA version) support"
1332 depends on MCA_LEGACY
1335 If you have a network (Ethernet) card of this type, say Y and read
1336 the Ethernet-HOWTO, available from
1337 <http://www.tldp.org/docs.html#howto>.
1339 To compile this driver as a module, choose M here. The module
1343 tristate "IBM LAN Adapter/A support"
1346 This is a Micro Channel Ethernet adapter. You need to set
1347 CONFIG_MCA to use this driver. It is both available as an in-kernel
1348 driver and as a module.
1350 To compile this driver as a module, choose M here. The only
1351 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1352 will both support 16K and 32K memory windows, however a 32K window
1353 gives a better security against packet losses. Usage of multiple
1354 boards with this driver should be possible, but has not been tested
1355 up to now due to lack of hardware.
1358 tristate "IBM LAN Virtual Ethernet support"
1359 depends on PPC_PSERIES
1361 This driver supports virtual ethernet adapters on newer IBM iSeries
1362 and pSeries systems.
1364 To compile this driver as a module, choose M here. The module will
1367 source "drivers/net/ibm_newemac/Kconfig"
1370 bool "EISA, VLB, PCI and on board controllers"
1371 depends on ISA || EISA || PCI
1373 This is another class of network cards which attach directly to the
1374 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1375 available from <http://www.tldp.org/docs.html#howto>.
1377 Note that the answer to this question doesn't directly affect the
1378 kernel: saying N will just cause the configurator to skip all
1379 the questions about this class of network cards. If you say Y, you
1380 will be asked for your specific card in the following questions. If
1381 you are unsure, say Y.
1384 tristate "AMD PCnet32 PCI support"
1385 depends on NET_PCI && PCI
1389 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1390 answer Y here and read the Ethernet-HOWTO, available from
1391 <http://www.tldp.org/docs.html#howto>.
1393 To compile this driver as a module, choose M here. The module
1394 will be called pcnet32.
1397 tristate "AMD 8111 (new PCI lance) support"
1398 depends on NET_PCI && PCI
1402 If you have an AMD 8111-based PCI lance ethernet card,
1403 answer Y here and read the Ethernet-HOWTO, available from
1404 <http://www.tldp.org/docs.html#howto>.
1406 To compile this driver as a module, choose M here. The module
1407 will be called amd8111e.
1409 config ADAPTEC_STARFIRE
1410 tristate "Adaptec Starfire/DuraLAN support"
1411 depends on NET_PCI && PCI
1415 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1416 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1417 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1420 To compile this driver as a module, choose M here: the module
1421 will be called starfire. This is recommended.
1424 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1425 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1428 If you have a network (Ethernet) card of this type, say Y and read
1429 the Ethernet-HOWTO, available from
1430 <http://www.tldp.org/docs.html#howto>.
1432 To compile this driver as a module, choose M here. The module
1433 will be called ac3200.
1436 tristate "Micrel KSZ8841/2 PCI"
1437 depends on NET_PCI && PCI
1441 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1443 To compile this driver as a module, choose M here. The module
1444 will be called ksz884x.
1447 tristate "Apricot Xen-II on board Ethernet"
1448 depends on NET_PCI && ISA
1450 If you have a network (Ethernet) controller of this type, say Y and
1451 read the Ethernet-HOWTO, available from
1452 <http://www.tldp.org/docs.html#howto>.
1454 To compile this driver as a module, choose M here. The module
1455 will be called apricot.
1458 tristate "Broadcom 440x/47xx ethernet support"
1459 depends on SSB_POSSIBLE && HAS_DMA
1463 If you have a network (Ethernet) controller of this type, say Y
1464 or M and read the Ethernet-HOWTO, available from
1465 <http://www.tldp.org/docs.html#howto>.
1467 To compile this driver as a module, choose M here. The module
1470 # Auto-select SSB PCI-HOST support, if possible
1471 config B44_PCI_AUTOSELECT
1473 depends on B44 && SSB_PCIHOST_POSSIBLE
1477 # Auto-select SSB PCICORE driver, if possible
1478 config B44_PCICORE_AUTOSELECT
1480 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1481 select SSB_DRIVER_PCICORE
1486 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1490 tristate "nForce Ethernet support"
1491 depends on NET_PCI && PCI
1493 If you have a network (Ethernet) controller of this type, say Y and
1494 read the Ethernet-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>.
1497 To compile this driver as a module, choose M here. The module
1498 will be called forcedeth.
1501 tristate "CS89x0 support"
1502 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1503 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1505 Support for CS89x0 chipset based Ethernet cards. If you have a
1506 network (Ethernet) card of this type, say Y and read the
1507 Ethernet-HOWTO, available from
1508 <http://www.tldp.org/docs.html#howto> as well as
1509 <file:Documentation/networking/cs89x0.txt>.
1511 To compile this driver as a module, choose M here. The module
1512 will be called cs89x0.
1514 config CS89x0_NONISA_IRQ
1516 depends on CS89x0 != n
1517 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1520 tristate "TOSHIBA TC35815 Ethernet support"
1521 depends on NET_PCI && PCI && MIPS
1525 tristate "Intel(R) PRO/100+ support"
1526 depends on NET_PCI && PCI
1529 This driver supports Intel(R) PRO/100 family of adapters.
1530 To verify that your adapter is supported, find the board ID number
1531 on the adapter. Look for a label that has a barcode and a number
1532 in the format 123456-001 (six digits hyphen three digits).
1534 Use the above information and the Adapter & Driver ID Guide at:
1536 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1538 to identify the adapter.
1540 For the latest Intel PRO/100 network driver for Linux, see:
1542 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1544 More specific information on configuring the driver is in
1545 <file:Documentation/networking/e100.txt>.
1547 To compile this driver as a module, choose M here. The module
1548 will be called e100.
1551 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1552 depends on NET_PCI && EISA && EXPERIMENTAL
1555 If you have a network (Ethernet) card of this type, say Y and read
1556 the Ethernet-HOWTO, available from
1557 <http://www.tldp.org/docs.html#howto>.
1559 To compile this driver as a module, choose M here. The module
1560 will be called lne390.
1563 tristate "Myson MTD-8xx PCI Ethernet support"
1564 depends on NET_PCI && PCI
1568 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1569 cards. <http://www.myson.com.tw/>
1572 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1573 depends on NET_PCI && PCI
1576 This driver is for the National Semiconductor DP83810 series,
1577 which is used in cards from PureData, NetGear, Linksys
1578 and others, including the 83815 chip.
1579 More specific information and updates are available from
1580 <http://www.scyld.com/network/natsemi.html>.
1583 tristate "PCI NE2000 and clones support (see help)"
1584 depends on NET_PCI && PCI
1587 This driver is for NE2000 compatible PCI cards. It will not work
1588 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1589 support" below). If you have a PCI NE2000 network (Ethernet) card,
1590 say Y and read the Ethernet-HOWTO, available from
1591 <http://www.tldp.org/docs.html#howto>.
1593 This driver also works for the following NE2000 clone cards:
1594 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1595 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1596 Holtek HT80232 Holtek HT80229
1598 To compile this driver as a module, choose M here. The module
1599 will be called ne2k-pci.
1602 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1603 depends on NET_PCI && EISA && EXPERIMENTAL
1606 If you have a network (Ethernet) card of this type, say Y and read
1607 the Ethernet-HOWTO, available from
1608 <http://www.tldp.org/docs.html#howto>. Note that this driver
1609 will NOT WORK for NE3200 cards as they are completely different.
1611 To compile this driver as a module, choose M here. The module
1612 will be called ne3210.
1615 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1616 depends on NET_PCI && EISA && EXPERIMENTAL
1619 If you have a network (Ethernet) card of this type, say Y and read
1620 the Ethernet-HOWTO, available from
1621 <http://www.tldp.org/docs.html#howto>.
1623 To compile this driver as a module, choose M here. The module
1624 will be called es3210.
1627 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1628 depends on NET_PCI && PCI && EXPERIMENTAL
1632 This is a driver for the Fast Ethernet PCI network cards based on
1633 the RTL8139C+ chips. If you have one of those, say Y and read
1634 the Ethernet-HOWTO, available from
1635 <http://www.tldp.org/docs.html#howto>.
1637 To compile this driver as a module, choose M here: the module
1638 will be called 8139cp. This is recommended.
1641 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1642 depends on NET_PCI && PCI
1646 This is a driver for the Fast Ethernet PCI network cards based on
1647 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1648 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1650 To compile this driver as a module, choose M here: the module
1651 will be called 8139too. This is recommended.
1654 bool "Use PIO instead of MMIO"
1658 This instructs the driver to use programmed I/O ports (PIO) instead
1659 of PCI shared memory (MMIO). This can possibly solve some problems
1660 in case your mainboard has memory consistency issues. If unsure,
1663 config 8139TOO_TUNE_TWISTER
1664 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1667 This implements a function which might come in handy in case you
1668 are using low quality on long cabling. It is required for RealTek
1669 RTL-8139 revision K boards, and totally unused otherwise. It tries
1670 to match the transceiver to the cable characteristics. This is
1671 experimental since hardly documented by the manufacturer.
1675 bool "Support for older RTL-8129/8130 boards"
1678 This enables support for the older and uncommon RTL-8129 and
1679 RTL-8130 chips, which support MII via an external transceiver,
1680 instead of an internal one. Disabling this option will save some
1681 memory by making the code size smaller. If unsure, say Y.
1683 config 8139_OLD_RX_RESET
1684 bool "Use older RX-reset method"
1687 The 8139too driver was recently updated to contain a more rapid
1688 reset sequence, in the face of severe receive errors. This "new"
1689 RX-reset method should be adequate for all boards. But if you
1690 experience problems, you can enable this option to restore the
1691 old RX-reset behavior. If unsure, say N.
1694 tristate "RDC R6040 Fast Ethernet Adapter support"
1695 depends on NET_PCI && PCI
1700 This is a driver for the R6040 Fast Ethernet MACs found in the
1701 the RDC R-321x System-on-chips.
1703 To compile this driver as a module, choose M here: the module
1704 will be called r6040. This is recommended.
1707 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1708 depends on NET_PCI && PCI
1712 This is a driver for the Fast Ethernet PCI network cards based on
1713 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1714 SiS 630 and SiS 540 chipsets.
1716 This driver also supports AMD 79C901 HomePNA so that you can use
1717 your phone line as a network cable.
1719 To compile this driver as a module, choose M here: the module
1720 will be called sis900. This is recommended.
1723 tristate "SMC EtherPower II"
1724 depends on NET_PCI && PCI
1728 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1729 which is based on the SMC83c17x (EPIC/100).
1730 More specific information and updates are available from
1731 <http://www.scyld.com/network/epic100.html>.
1734 tristate "SMSC LAN9420 PCI ethernet adapter support"
1735 depends on NET_PCI && PCI
1740 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1741 Say Y if you want it compiled into the kernel,
1742 and read the Ethernet-HOWTO, available from
1743 <http://www.tldp.org/docs.html#howto>.
1745 This driver is also available as a module. The module will be
1746 called smsc9420. If you want to compile it as a module, say M
1747 here and read <file:Documentation/kbuild/modules.txt>
1750 tristate "Sundance Alta support"
1751 depends on NET_PCI && PCI
1755 This driver is for the Sundance "Alta" chip.
1756 More specific information and updates are available from
1757 <http://www.scyld.com/network/sundance.html>.
1759 config SUNDANCE_MMIO
1760 bool "Use MMIO instead of PIO"
1763 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1764 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1765 is known to solve bugs on certain chips.
1770 tristate "TI ThunderLAN support"
1771 depends on NET_PCI && (PCI || EISA)
1773 If you have a PCI Ethernet network card based on the ThunderLAN chip
1774 which is supported by this driver, say Y and read the
1775 Ethernet-HOWTO, available from
1776 <http://www.tldp.org/docs.html#howto>.
1778 Devices currently supported by this driver are Compaq Netelligent,
1779 Compaq NetFlex and Olicom cards. Please read the file
1780 <file:Documentation/networking/tlan.txt> for more details.
1782 To compile this driver as a module, choose M here. The module
1783 will be called tlan.
1785 Please email feedback to <torben.mathiasen@compaq.com>.
1788 tristate "Micrel KSZ8841/42 with generic bus interface"
1789 depends on HAS_IOMEM && DMA_ENGINE
1791 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1792 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1796 tristate "Micrel KS8851 SPI"
1801 SPI driver for Micrel KS8851 SPI attached network chip.
1804 tristate "Micrel KS8851 MLL"
1805 depends on HAS_IOMEM
1808 This platform driver is for Micrel KS8851 Address/data bus
1809 multiplexed network chip.
1812 tristate "VIA Rhine support"
1813 depends on NET_PCI && PCI
1817 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1818 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1819 Ethernet functions can also be found integrated on South Bridges
1822 To compile this driver as a module, choose M here. The module
1823 will be called via-rhine.
1825 config VIA_RHINE_MMIO
1826 bool "Use MMIO instead of PIO"
1827 depends on VIA_RHINE
1829 This instructs the driver to use PCI shared memory (MMIO) instead of
1830 programmed I/O ports (PIO). Enabling this gives an improvement in
1831 processing time in parts of the driver.
1836 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1837 depends on NET_PCI && PCI && EXPERIMENTAL
1840 This is a driver for the Fast Ethernet PCI network cards based on
1841 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1842 have one of these, say Y here.
1844 To compile this driver as a module, choose M here: the module
1845 will be called sc92031. This is recommended.
1848 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1849 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1852 TI AR7 CPMAC Ethernet support
1855 bool "Pocket and portable adapters"
1858 Cute little network (Ethernet) devices which attach to the parallel
1859 port ("pocket adapters"), commonly used with laptops. If you have
1860 one of those, say Y and read the Ethernet-HOWTO, available from
1861 <http://www.tldp.org/docs.html#howto>.
1863 If you want to plug a network (or some other) card into the PCMCIA
1864 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1865 credit card size extension cards used by all modern laptops), you
1866 need the pcmcia-cs package (location contained in the file
1867 <file:Documentation/Changes>) and you can say N here.
1869 Laptop users should read the Linux Laptop home page at
1870 <http://www.linux-on-laptops.com/> or
1871 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1873 Note that the answer to this question doesn't directly affect the
1874 kernel: saying N will just cause the configurator to skip all
1875 the questions about this class of network devices. If you say Y, you
1876 will be asked for your specific device in the following questions.
1879 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1880 depends on NET_POCKET && PARPORT && X86
1883 This is a network (Ethernet) device which attaches to your parallel
1884 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1885 available from <http://www.tldp.org/docs.html#howto>, if you
1886 want to use this. If you intend to use this driver, you should have
1887 said N to the "Parallel printer support", because the two drivers
1888 don't like each other.
1890 To compile this driver as a module, choose M here: the module
1894 tristate "D-Link DE600 pocket adapter support"
1895 depends on NET_POCKET && PARPORT
1897 This is a network (Ethernet) device which attaches to your parallel
1898 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1899 Ethernet-HOWTO, available from
1900 <http://www.tldp.org/docs.html#howto>, if you want to use
1901 this. It is possible to have several devices share a single parallel
1902 port and it is safe to compile the corresponding drivers into the
1905 To compile this driver as a module, choose M here: the module
1906 will be called de600.
1909 tristate "D-Link DE620 pocket adapter support"
1910 depends on NET_POCKET && PARPORT
1912 This is a network (Ethernet) device which attaches to your parallel
1913 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1914 Ethernet-HOWTO, available from
1915 <http://www.tldp.org/docs.html#howto>, if you want to use
1916 this. It is possible to have several devices share a single parallel
1917 port and it is safe to compile the corresponding drivers into the
1920 To compile this driver as a module, choose M here: the module
1921 will be called de620.
1924 tristate "SGI Seeq ethernet controller support"
1925 depends on SGI_HAS_SEEQ
1927 Say Y here if you have an Seeq based Ethernet network card. This is
1928 used in many Silicon Graphics machines.
1931 tristate "DEC LANCE ethernet controller support"
1932 depends on MACH_DECSTATION
1935 This driver is for the series of Ethernet controllers produced by
1936 DEC (now Compaq) based on the AMD Lance chipset, including the
1937 DEPCA series. (This chipset is better known via the NE2100 cards.)
1940 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1941 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1942 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1943 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1946 Say Y here if you want to use the built-in 10/100 Fast ethernet
1947 controller on some Motorola ColdFire and Freescale i.MX processors.
1950 tristate "MPC52xx FEC driver"
1951 depends on PPC_MPC52xx && PPC_BESTCOMM
1954 select PPC_BESTCOMM_FEC
1956 This option enables support for the MPC5200's on-chip
1957 Fast Ethernet Controller
1958 If compiled as module, it will be called fec_mpc52xx.
1960 config FEC_MPC52xx_MDIO
1961 bool "MPC52xx FEC MDIO bus driver"
1962 depends on FEC_MPC52xx
1965 The MPC5200's FEC can connect to the Ethernet either with
1966 an external MII PHY chip or 10 Mbps 7-wire interface
1967 (Motorola? industry standard).
1968 If your board uses an external PHY connected to FEC, enable this.
1969 If not sure, enable.
1970 If compiled as module, it will be called fec_mpc52xx_phy.
1973 tristate "NE2000 compatible support for H8/300"
1976 Say Y here if you want to use the NE2000 compatible
1977 controller on the Renesas H8/300 processor.
1980 tristate "Atheros L2 Fast Ethernet support"
1985 This driver supports the Atheros L2 fast ethernet adapter.
1987 To compile this driver as a module, choose M here. The module
1988 will be called atl2.
1990 config XILINX_EMACLITE
1991 tristate "Xilinx 10/100 Ethernet Lite support"
1992 depends on PPC32 || MICROBLAZE
1995 This driver supports the 10/100 Ethernet Lite from Xilinx.
1998 tristate "Broadcom 63xx internal mac support"
2003 This driver supports the ethernet MACs in the Broadcom 63xx
2004 MIPS chipset family (BCM63XX).
2007 tristate "Faraday FTMAC100 10/100 Ethernet support"
2011 This driver supports the FTMAC100 10/100 Ethernet controller
2012 from Faraday. It is used on Faraday A320, Andes AG101 and some
2013 other ARM/NDS32 SoC's.
2016 tristate "Lantiq SoC ETOP driver"
2017 depends on SOC_TYPE_XWAY
2019 Support for the MII0 inside the Lantiq SoC
2022 source "drivers/net/fs_enet/Kconfig"
2024 source "drivers/net/octeon/Kconfig"
2026 endif # NET_ETHERNET
2032 menuconfig NETDEV_1000
2033 bool "Ethernet (1000 Mbit)"
2037 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2038 type of Local Area Network (LAN) in universities and companies.
2040 Say Y here to get to see options for Gigabit Ethernet drivers.
2041 This option alone does not add any kernel code.
2042 Note that drivers supporting both 100 and 1000 MBit may be listed
2043 under "Ethernet (10 or 100MBit)" instead.
2045 If you say N, all options in this submenu will be skipped and disabled.
2050 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2053 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2054 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2055 adapter. The driver allows for using the Jumbo Frame option (9000
2056 bytes/frame) however it requires that your switches can handle this
2057 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2060 To compile this driver as a module, choose M here: the
2061 module will be called acenic.
2063 config ACENIC_OMIT_TIGON_I
2064 bool "Omit support for old Tigon I based AceNICs"
2067 Say Y here if you only have Tigon II based AceNICs and want to leave
2068 out support for the older Tigon I based cards which are no longer
2069 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2070 version)). This will reduce the size of the driver object by
2071 app. 100KB. If you are not sure whether your card is a Tigon I or a
2072 Tigon II, say N here.
2074 The safe and default value for this is N.
2077 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2081 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2083 D-Link DGE-550T Gigabit Ethernet Adapter.
2084 D-Link DL2000-based Gigabit Ethernet Adapter.
2085 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2087 To compile this driver as a module, choose M here: the
2088 module will be called dl2k.
2091 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2094 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2095 adapters. For more information on how to identify your adapter, go
2096 to the Adapter & Driver ID Guide at:
2098 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2100 For general information and support, go to the Intel support
2103 <http://support.intel.com>
2105 More specific information on configuring the driver is in
2106 <file:Documentation/networking/e1000.txt>.
2108 To compile this driver as a module, choose M here. The module
2109 will be called e1000.
2112 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2113 depends on PCI && (!SPARC32 || BROKEN)
2116 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2117 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2118 use the regular e1000 driver For more information on how to
2119 identify your adapter, go to the Adapter & Driver ID Guide at:
2121 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2123 For general information and support, go to the Intel support
2126 <http://support.intel.com>
2128 To compile this driver as a module, choose M here. The module
2129 will be called e1000e.
2132 tristate "IP1000 Gigabit Ethernet support"
2133 depends on PCI && EXPERIMENTAL
2136 This driver supports IP1000 gigabit Ethernet cards.
2138 To compile this driver as a module, choose M here: the module
2139 will be called ipg. This is recommended.
2142 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2145 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2146 adapters. For more information on how to identify your adapter, go
2147 to the Adapter & Driver ID Guide at:
2149 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2151 For general information and support, go to the Intel support
2154 <http://support.intel.com>
2156 More specific information on configuring the driver is in
2157 <file:Documentation/networking/e1000.txt>.
2159 To compile this driver as a module, choose M here. The module
2163 bool "Direct Cache Access (DCA) Support"
2165 depends on IGB && DCA && !(IGB=y && DCA=m)
2167 Say Y here if you want to use Direct Cache Access (DCA) in the
2168 driver. DCA is a method for warming the CPU cache before data
2169 is used, with the intent of lessening the impact of cache misses.
2172 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2175 This driver supports Intel(R) 82576 virtual functions. For more
2176 information on how to identify your adapter, go to the Adapter &
2179 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2181 For general information and support, go to the Intel support
2184 <http://support.intel.com>
2186 More specific information on configuring the driver is in
2187 <file:Documentation/networking/e1000.txt>.
2189 To compile this driver as a module, choose M here. The module
2190 will be called igbvf.
2192 source "drivers/net/ixp2000/Kconfig"
2195 tristate "National Semiconductor DP83820 support"
2198 This is a driver for the National Semiconductor DP83820 series
2199 of gigabit ethernet MACs. Cards using this chipset include
2200 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2201 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2205 tristate "Packet Engines Hamachi GNIC-II support"
2209 If you have a Gigabit Ethernet card of this type, say Y and read
2210 the Ethernet-HOWTO, available from
2211 <http://www.tldp.org/docs.html#howto>.
2213 To compile this driver as a module, choose M here. The module will be
2217 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2218 depends on PCI && EXPERIMENTAL
2221 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2222 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2223 used by the Beowulf Linux cluster project. See
2224 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2225 information about this driver in particular and Beowulf in general.
2227 To compile this driver as a module, choose M here: the module
2228 will be called yellowfin. This is recommended.
2231 tristate "Realtek 8169 gigabit ethernet support"
2237 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2239 To compile this driver as a module, choose M here: the module
2240 will be called r8169. This is recommended.
2243 tristate "SB1250 Gigabit Ethernet support"
2244 depends on SIBYTE_SB1xxx_SOC
2247 This driver supports Gigabit Ethernet interfaces based on the
2248 Broadcom SiByte family of System-On-a-Chip parts. They include
2249 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2252 To compile this driver as a module, choose M here: the module
2253 will be called sb1250-mac.
2256 tristate "SiS190/SiS191 gigabit ethernet support"
2261 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2262 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2263 appear in lan on motherboard designs which are based on SiS 965
2264 and SiS 966 south bridge.
2266 To compile this driver as a module, choose M here: the module
2267 will be called sis190. This is recommended.
2270 tristate "Marvell Yukon Gigabit Ethernet support"
2274 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2275 and related Gigabit Ethernet adapters. It is a new smaller driver
2276 with better performance and more complete ethtool support.
2278 It does not support the link failover and network management
2279 features that "portable" vendor supplied sk98lin driver does.
2281 This driver supports adapters based on the original Yukon chipset:
2282 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2283 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2285 It does not support the newer Yukon2 chipset: a separate driver,
2286 sky2, is provided for these adapters.
2288 To compile this driver as a module, choose M here: the module
2289 will be called skge. This is recommended.
2292 bool "Debugging interface"
2293 depends on SKGE && DEBUG_FS
2295 This option adds the ability to dump driver state for debugging.
2296 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2297 transmit and receive rings.
2302 bool "Support for older SysKonnect Genesis boards"
2305 This enables support for the older and uncommon SysKonnect Genesis
2306 chips, which support MII via an external transceiver, instead of
2307 an internal one. Disabling this option will save some memory
2308 by making code smaller. If unsure say Y.
2311 tristate "Marvell Yukon 2 support"
2315 This driver supports Gigabit Ethernet adapters based on the
2316 Marvell Yukon 2 chipset:
2317 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2318 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2320 There is companion driver for the older Marvell Yukon and
2321 SysKonnect Genesis based adapters: skge.
2323 To compile this driver as a module, choose M here: the module
2324 will be called sky2. This is recommended.
2327 bool "Debugging interface"
2328 depends on SKY2 && DEBUG_FS
2330 This option adds the ability to dump driver state for debugging.
2331 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2332 transmit and receive rings.
2337 tristate "VIA Velocity support"
2343 If you have a VIA "Velocity" based network card say Y here.
2345 To compile this driver as a module, choose M here. The module
2346 will be called via-velocity.
2349 tristate "Broadcom Tigon3 support"
2353 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2355 To compile this driver as a module, choose M here: the module
2356 will be called tg3. This is recommended.
2359 tristate "Broadcom NetXtremeII support"
2364 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2366 To compile this driver as a module, choose M here: the module
2367 will be called bnx2. This is recommended.
2370 tristate "Broadcom CNIC support"
2375 This driver supports offload features of Broadcom NetXtremeII
2376 gigabit Ethernet cards.
2378 To compile this driver as a module, choose M here: the module
2379 will be called cnic. This is recommended.
2382 tristate "Spider Gigabit Ethernet driver"
2383 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2386 This driver supports the Gigabit Ethernet chips present on the
2387 Cell Processor-Based Blades from IBM.
2390 tristate "Tundra TSI108 gigabit Ethernet support"
2391 depends on TSI108_BRIDGE
2393 This driver supports Tundra TSI108 gigabit Ethernet ports.
2394 To compile this driver as a module, choose M here: the module
2395 will be called tsi108_eth.
2398 tristate "PS3 Gigabit Ethernet driver"
2400 select PS3_SYS_MANAGER
2402 This driver supports the network device on the PS3 game
2403 console. This driver has built-in support for Ethernet.
2405 To compile this driver as a module, choose M here: the
2406 module will be called ps3_gelic.
2408 config GELIC_WIRELESS
2409 bool "PS3 Wireless support"
2411 depends on GELIC_NET
2414 This option adds the support for the wireless feature of PS3.
2415 If you have the wireless-less model of PS3 or have no plan to
2416 use wireless feature, disabling this option saves memory. As
2417 the driver automatically distinguishes the models, you can
2418 safely enable this option even if you have a wireless-less model.
2421 tristate "Freescale PQ MDIO"
2425 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2428 tristate "Gianfar Ethernet"
2434 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2435 and MPC86xx family of chips, and the FEC on the 8540.
2438 tristate "Freescale QE Gigabit Ethernet"
2439 depends on QUICC_ENGINE
2443 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2444 which is available on some Freescale SOCs.
2446 config UGETH_TX_ON_DEMAND
2447 bool "Transmit on Demand support"
2451 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2452 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2456 This driver supports the gigabit ethernet MACs in the
2457 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2458 in the Marvell Orion ARM SoC family.
2460 Some boards that use the Discovery chipset are the Momenco
2461 Ocelot C and Jaguar ATX and Pegasos II.
2463 config XILINX_LL_TEMAC
2464 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2465 depends on PPC || MICROBLAZE
2468 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2469 core used in Xilinx Spartan and Virtex FPGAs
2472 tristate "QLogic QLA3XXX Network Driver Support"
2475 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2477 To compile this driver as a module, choose M here: the module
2478 will be called qla3xxx.
2481 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2486 This driver supports the Atheros/Attansic L1 gigabit ethernet
2489 To compile this driver as a module, choose M here. The module
2490 will be called atl1.
2493 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2494 depends on PCI && EXPERIMENTAL
2498 This driver supports the Atheros L1E gigabit ethernet adapter.
2500 To compile this driver as a module, choose M here. The module
2501 will be called atl1e.
2504 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2505 depends on PCI && EXPERIMENTAL
2509 This driver supports the Atheros L1C gigabit ethernet adapter.
2511 To compile this driver as a module, choose M here. The module
2512 will be called atl1c.
2515 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2520 This driver supports the PCI-Express gigabit ethernet adapters
2521 based on JMicron JMC250 chipset.
2523 To compile this driver as a module, choose M here. The module
2527 tristate "S6105 GMAC ethernet support"
2528 depends on XTENSA_VARIANT_S6000
2531 This driver supports the on chip ethernet device on the
2532 S6105 xtensa processor.
2534 To compile this driver as a module, choose M here. The module
2535 will be called s6gmac.
2537 source "drivers/net/stmmac/Kconfig"
2540 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
2544 This is a gigabit ethernet driver for EG20T PCH.
2545 EG20T PCH is the platform controller hub that is used in Intel's
2546 general embedded platform.
2547 EG20T PCH has Gigabit Ethernet interface.
2548 Using this interface, it is able to access system devices connected
2549 to Gigabit Ethernet.
2550 This driver enables Gigabit Ethernet function.
2552 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
2553 Output Hub), ML7223.
2554 ML7223 IOH is for MP(Media Phone) use.
2555 ML7223 is companion chip for Intel Atom E6xx series.
2556 ML7223 is completely compatible for Intel EG20T PCH.
2559 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
2563 This driver supports the FTGMAC100 Gigabit Ethernet controller
2564 from Faraday. It is used on Faraday A369, Andes AG102 and some
2565 other ARM/NDS32 SoC's.
2570 # 10 Gigabit Ethernet
2573 menuconfig NETDEV_10000
2574 bool "Ethernet (10000 Mbit)"
2578 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2579 This option alone does not add any kernel code.
2581 If you say N, all options in this submenu will be skipped and disabled.
2589 tristate "Chelsio 10Gb Ethernet support"
2594 This driver supports Chelsio gigabit and 10-gigabit
2595 Ethernet cards. More information about adapter features and
2596 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2598 For general information about Chelsio and our products, visit
2599 our website at <http://www.chelsio.com>.
2601 For customer support, please visit our customer support page at
2602 <http://www.chelsio.com/support.html>.
2604 Please send feedback to <linux-bugs@chelsio.com>.
2606 To compile this driver as a module, choose M here: the module
2607 will be called cxgb.
2609 config CHELSIO_T1_1G
2610 bool "Chelsio gigabit Ethernet support"
2611 depends on CHELSIO_T1
2613 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2614 are using only 10G cards say 'N' here.
2617 tristate "Chelsio Communications T3 10Gb Ethernet support"
2618 depends on PCI && INET
2622 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2625 For general information about Chelsio and our products, visit
2626 our website at <http://www.chelsio.com>.
2628 For customer support, please visit our customer support page at
2629 <http://www.chelsio.com/support.html>.
2631 Please send feedback to <linux-bugs@chelsio.com>.
2633 To compile this driver as a module, choose M here: the module
2634 will be called cxgb3.
2637 tristate "Chelsio Communications T4 Ethernet support"
2642 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2645 For general information about Chelsio and our products, visit
2646 our website at <http://www.chelsio.com>.
2648 For customer support, please visit our customer support page at
2649 <http://www.chelsio.com/support.html>.
2651 Please send feedback to <linux-bugs@chelsio.com>.
2653 To compile this driver as a module choose M here; the module
2654 will be called cxgb4.
2657 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2660 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2661 adapters with PCI-E SR-IOV Virtual Functions.
2663 For general information about Chelsio and our products, visit
2664 our website at <http://www.chelsio.com>.
2666 For customer support, please visit our customer support page at
2667 <http://www.chelsio.com/support.html>.
2669 Please send feedback to <linux-bugs@chelsio.com>.
2671 To compile this driver as a module choose M here; the module
2672 will be called cxgb4vf.
2675 tristate "eHEA Ethernet support"
2676 depends on IBMEBUS && INET && SPARSEMEM
2679 This driver supports the IBM pSeries eHEA ethernet adapter.
2681 To compile the driver as a module, choose M here. The module
2682 will be called ehea.
2685 tristate "Cisco VIC Ethernet NIC Support"
2686 depends on PCI && INET
2688 This enables the support for the Cisco VIC Ethernet card.
2691 tristate "Intel(R) 10GbE PCI Express adapters support"
2692 depends on PCI && INET
2695 This driver supports Intel(R) 10GbE PCI Express family of
2696 adapters. For more information on how to identify your adapter, go
2697 to the Adapter & Driver ID Guide at:
2699 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2701 For general information and support, go to the Intel support
2704 <http://support.intel.com>
2706 To compile this driver as a module, choose M here. The module
2707 will be called ixgbe.
2710 bool "Direct Cache Access (DCA) Support"
2712 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2714 Say Y here if you want to use Direct Cache Access (DCA) in the
2715 driver. DCA is a method for warming the CPU cache before data
2716 is used, with the intent of lessening the impact of cache misses.
2719 bool "Data Center Bridging (DCB) Support"
2721 depends on IXGBE && DCB
2723 Say Y here if you want to use Data Center Bridging (DCB) in the
2729 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2732 This driver supports Intel(R) 82599 virtual functions. For more
2733 information on how to identify your adapter, go to the Adapter &
2736 <http://support.intel.com/support/network/sb/CS-008441.htm>
2738 For general information and support, go to the Intel support
2741 <http://support.intel.com>
2743 More specific information on configuring the driver is in
2744 <file:Documentation/networking/ixgbevf.txt>.
2746 To compile this driver as a module, choose M here. The module
2747 will be called ixgbevf. MSI-X interrupt support is required
2748 for this driver to work correctly.
2751 tristate "Intel(R) PRO/10GbE support"
2754 This driver supports Intel(R) PRO/10GbE family of adapters for
2755 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2756 instead. For more information on how to identify your adapter, go
2757 to the Adapter & Driver ID Guide at:
2759 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2761 For general information and support, go to the Intel support
2764 <http://support.intel.com>
2766 More specific information on configuring the driver is in
2767 <file:Documentation/networking/ixgb.txt>.
2769 To compile this driver as a module, choose M here. The module
2770 will be called ixgb.
2773 tristate "Exar Xframe 10Gb Ethernet Adapter"
2776 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2778 More specific information on configuring the driver is in
2779 <file:Documentation/networking/s2io.txt>.
2781 To compile this driver as a module, choose M here. The module
2782 will be called s2io.
2785 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2786 depends on PCI && INET
2788 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2789 I/O Virtualized Server Adapter.
2791 More specific information on configuring the driver is in
2792 <file:Documentation/networking/vxge.txt>.
2794 To compile this driver as a module, choose M here. The module
2795 will be called vxge.
2797 config VXGE_DEBUG_TRACE_ALL
2798 bool "Enabling All Debug trace statments in driver"
2802 Say Y here if you want to enabling all the debug trace statements in
2803 the vxge driver. By default only few debug trace statements are
2807 tristate "Myricom Myri-10G Ethernet support"
2808 depends on PCI && INET
2813 This driver supports Myricom Myri-10G Dual Protocol interface in
2814 Ethernet mode. If the eeprom on your board is not recent enough,
2815 you will need a newer firmware image.
2816 You may get this image or more information, at:
2818 <http://www.myri.com/scs/download-Myri10GE.html>
2820 To compile this driver as a module, choose M here. The module
2821 will be called myri10ge.
2824 bool "Direct Cache Access (DCA) Support"
2826 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2828 Say Y here if you want to use Direct Cache Access (DCA) in the
2829 driver. DCA is a method for warming the CPU cache before data
2830 is used, with the intent of lessening the impact of cache misses.
2833 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2837 This enables the support for NetXen's Gigabit Ethernet card.
2840 tristate "Sun Neptune 10Gbit Ethernet support"
2844 This enables support for cards based upon Sun's
2848 tristate "PA Semi 1/10Gbit MAC"
2849 depends on PPC_PASEMI && PCI && INET
2853 This driver supports the on-chip 1/10Gbit Ethernet controller on
2854 PA Semi's PWRficient line of chips.
2857 tristate "Mellanox Technologies 10Gbit Ethernet support"
2858 depends on PCI && INET
2862 This driver supports Mellanox Technologies ConnectX Ethernet
2871 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2872 depends on MLX4_CORE
2875 This option causes debugging code to be compiled into the
2876 mlx4_core driver. The output can be turned on via the
2877 debug_level module parameter (which can also be set after
2878 the driver is loaded through sysfs).
2881 tristate "Tehuti Networks 10G Ethernet"
2884 Tehuti Networks 10G Ethernet NIC
2887 tristate "Broadcom NetXtremeII 10Gb support"
2894 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2895 To compile this driver as a module, choose M here: the module
2896 will be called bnx2x. This is recommended.
2899 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2903 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2907 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2910 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2912 To compile this driver as a module, choose M here: the module
2913 will be called qlge.
2916 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2919 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2921 To compile this driver as a module, choose M here: the module
2924 For general information and support, go to the Brocade support
2927 <http://support.brocade.com>
2929 source "drivers/net/sfc/Kconfig"
2931 source "drivers/net/benet/Kconfig"
2933 endif # NETDEV_10000
2935 source "drivers/net/tokenring/Kconfig"
2937 source "drivers/net/wireless/Kconfig"
2939 source "drivers/net/wimax/Kconfig"
2941 source "drivers/net/usb/Kconfig"
2943 source "drivers/net/pcmcia/Kconfig"
2945 source "drivers/net/wan/Kconfig"
2947 source "drivers/atm/Kconfig"
2949 source "drivers/ieee802154/Kconfig"
2951 source "drivers/s390/net/Kconfig"
2953 source "drivers/net/caif/Kconfig"
2956 tristate "Tilera GBE/XGBE network driver support"
2961 This is a standard Linux network device driver for the
2962 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2964 To compile this driver as a module, choose M here: the module
2965 will be called tile_net.
2967 config XEN_NETDEV_FRONTEND
2968 tristate "Xen network device frontend driver"
2970 select XEN_XENBUS_FRONTEND
2973 This driver provides support for Xen paravirtual network
2974 devices exported by a Xen network driver domain (often
2977 The corresponding Linux backend driver is enabled by the
2978 CONFIG_XEN_NETDEV_BACKEND option.
2980 If you are compiling a kernel for use as Xen guest, you
2981 should say Y here. To compile this driver as a module, chose
2982 M here: the module will be called xen-netfront.
2984 config XEN_NETDEV_BACKEND
2985 tristate "Xen backend network device"
2986 depends on XEN_BACKEND
2988 This driver allows the kernel to act as a Xen network driver
2989 domain which exports paravirtual network devices to other
2990 Xen domains. These devices can be accessed by any operating
2991 system that implements a compatible front end.
2993 The corresponding Linux frontend driver is enabled by the
2994 CONFIG_XEN_NETDEV_FRONTEND configuration option.
2996 The backend driver presents a standard network device
2997 endpoint for each paravirtual network device to the driver
2998 domain network stack. These can then be bridged or routed
2999 etc in order to provide full network connectivity.
3001 If you are compiling a kernel to run in a Xen network driver
3002 domain (often this is domain 0) you should say Y here. To
3003 compile this driver as a module, chose M here: the module
3004 will be called xen-netback.
3007 tristate "iSeries Virtual Ethernet driver support"
3008 depends on PPC_ISERIES
3011 tristate "RapidIO Ethernet over messaging driver support"
3014 config RIONET_TX_SIZE
3015 int "Number of outbound queue entries"
3019 config RIONET_RX_SIZE
3020 int "Number of inbound queue entries"
3025 tristate "FDDI driver support"
3026 depends on (PCI || EISA || TC)
3028 Fiber Distributed Data Interface is a high speed local area network
3029 design; essentially a replacement for high speed Ethernet. FDDI can
3030 run over copper or fiber. If you are connected to such a network and
3031 want a driver for the FDDI card in your computer, say Y here (and
3032 then also Y to the driver for your FDDI card, below). Most people
3036 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
3037 depends on FDDI && (PCI || EISA || TC)
3039 This is support for the DIGITAL series of TURBOchannel (DEFTA),
3040 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
3041 to a local FDDI network.
3043 To compile this driver as a module, choose M here: the module
3044 will be called defxx. If unsure, say N.
3048 prompt "Use MMIO instead of PIO" if PCI || EISA
3050 default n if PCI || EISA
3053 This instructs the driver to use EISA or PCI memory-mapped I/O
3054 (MMIO) as appropriate instead of programmed I/O ports (PIO).
3055 Enabling this gives an improvement in processing time in parts
3056 of the driver, but it may cause problems with EISA (DEFEA)
3057 adapters. TURBOchannel does not have the concept of I/O ports,
3058 so MMIO is always used for these (DEFTA) adapters.
3063 tristate "SysKonnect FDDI PCI support"
3064 depends on FDDI && PCI
3067 Say Y here if you have a SysKonnect FDDI PCI adapter.
3068 The following adapters are supported by this driver:
3069 - SK-5521 (SK-NET FDDI-UP)
3070 - SK-5522 (SK-NET FDDI-UP DAS)
3071 - SK-5541 (SK-NET FDDI-FP)
3072 - SK-5543 (SK-NET FDDI-LP)
3073 - SK-5544 (SK-NET FDDI-LP DAS)
3074 - SK-5821 (SK-NET FDDI-UP64)
3075 - SK-5822 (SK-NET FDDI-UP64 DAS)
3076 - SK-5841 (SK-NET FDDI-FP64)
3077 - SK-5843 (SK-NET FDDI-LP64)
3078 - SK-5844 (SK-NET FDDI-LP64 DAS)
3079 - Netelligent 100 FDDI DAS Fibre SC
3080 - Netelligent 100 FDDI SAS Fibre SC
3081 - Netelligent 100 FDDI DAS UTP
3082 - Netelligent 100 FDDI SAS UTP
3083 - Netelligent 100 FDDI SAS Fibre MIC
3085 Read <file:Documentation/networking/skfp.txt> for information about
3088 Questions concerning this driver can be addressed to:
3089 <linux@syskonnect.de>
3091 To compile this driver as a module, choose M here: the module
3092 will be called skfp. This is recommended.
3095 bool "HIPPI driver support (EXPERIMENTAL)"
3096 depends on EXPERIMENTAL && INET && PCI
3098 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3099 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3100 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3101 single-mode). HIPPI networks are commonly used for clusters and to
3102 connect to super computers. If you are connected to a HIPPI network
3103 and have a HIPPI network card in your computer that you want to use
3104 under Linux, say Y here (you must also remember to enable the driver
3105 for your HIPPI card below). Most people will say N here.
3108 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3109 depends on HIPPI && PCI
3111 Say Y here if this is your PCI HIPPI network card.
3113 To compile this driver as a module, choose M here: the module
3114 will be called rrunner. If unsure, say N.
3116 config ROADRUNNER_LARGE_RINGS
3117 bool "Use large TX/RX rings (EXPERIMENTAL)"
3118 depends on ROADRUNNER
3120 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3121 of additional memory to allow for fastest operation, both for
3122 transmitting and receiving. This memory cannot be used by any other
3123 kernel code or by user space programs. Say Y here only if you have
3127 tristate "PLIP (parallel port) support"
3130 PLIP (Parallel Line Internet Protocol) is used to create a
3131 reasonably fast mini network consisting of two (or, rarely, more)
3132 local machines. A PLIP link from a Linux box is a popular means to
3133 install a Linux distribution on a machine which doesn't have a
3134 CD-ROM drive (a minimal system has to be transferred with floppies
3135 first). The kernels on both machines need to have this PLIP option
3136 enabled for this to work.
3138 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3139 ports (the connectors at the computers with 25 holes) are connected
3140 with "null printer" or "Turbo Laplink" cables which can transmit 4
3141 bits at a time (mode 0) or with special PLIP cables, to be used on
3142 bidirectional parallel ports only, which can transmit 8 bits at a
3143 time (mode 1); you can find the wiring of these cables in
3144 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3145 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3146 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3147 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3148 and winsock or NCSA's telnet.
3150 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3151 as the NET-3-HOWTO, both available from
3152 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3153 protocol has been changed and this PLIP driver won't work together
3154 with the PLIP support in Linux versions 1.0.x. This option enlarges
3155 your kernel by about 8 KB.
3157 To compile this driver as a module, choose M here. The module
3158 will be called plip. If unsure, say Y or M, in case you buy
3162 tristate "PPP (point-to-point protocol) support"
3165 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3166 the same purpose: sending Internet traffic over telephone (and other
3167 serial) lines. Ask your access provider if they support it, because
3168 otherwise you can't use it; most Internet access providers these
3169 days support PPP rather than SLIP.
3171 To use PPP, you need an additional program called pppd as described
3172 in the PPP-HOWTO, available at
3173 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3174 the version of pppd recommended in <file:Documentation/Changes>.
3175 The PPP option enlarges your kernel by about 16 KB.
3177 There are actually two versions of PPP: the traditional PPP for
3178 asynchronous lines, such as regular analog phone lines, and
3179 synchronous PPP which can be used over digital ISDN lines for
3180 example. If you want to use PPP over phone lines or other
3181 asynchronous serial lines, you need to say Y (or M) here and also to
3182 the next option, "PPP support for async serial ports". For PPP over
3183 synchronous lines, you should say Y (or M) here and to "Support
3184 synchronous PPP", below.
3186 If you said Y to "Version information on all symbols" above, then
3187 you cannot compile the PPP driver into the kernel; you can then only
3188 compile it as a module. To compile this driver as a module, choose M
3189 here. The module will be called ppp_generic.
3191 config PPP_MULTILINK
3192 bool "PPP multilink support (EXPERIMENTAL)"
3193 depends on PPP && EXPERIMENTAL
3195 PPP multilink is a protocol (defined in RFC 1990) which allows you
3196 to combine several (logical or physical) lines into one logical PPP
3197 connection, so that you can utilize your full bandwidth.
3199 This has to be supported at the other end as well and you need a
3200 version of the pppd daemon which understands the multilink protocol.
3205 bool "PPP filtering"
3208 Say Y here if you want to be able to filter the packets passing over
3209 PPP interfaces. This allows you to control which packets count as
3210 activity (i.e. which packets will reset the idle timer or bring up
3211 a demand-dialed link) and which packets are to be dropped entirely.
3212 You need to say Y here if you wish to use the pass-filter and
3213 active-filter options to pppd.
3218 tristate "PPP support for async serial ports"
3222 Say Y (or M) here if you want to be able to use PPP over standard
3223 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3224 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3227 To compile this driver as a module, choose M here.
3232 tristate "PPP support for sync tty ports"
3235 Say Y (or M) here if you want to be able to use PPP over synchronous
3236 (HDLC) tty devices, such as the SyncLink adapter. These devices
3237 are often used for high-speed leased lines like T1/E1.
3239 To compile this driver as a module, choose M here.
3242 tristate "PPP Deflate compression"
3247 Support for the Deflate compression method for PPP, which uses the
3248 Deflate algorithm (the same algorithm that gzip uses) to compress
3249 each PPP packet before it is sent over the wire. The machine at the
3250 other end of the PPP link (usually your ISP) has to support the
3251 Deflate compression method as well for this to be useful. Even if
3252 they don't support it, it is safe to say Y here.
3254 To compile this driver as a module, choose M here.
3257 tristate "PPP BSD-Compress compression"
3260 Support for the BSD-Compress compression method for PPP, which uses
3261 the LZW compression method to compress each PPP packet before it is
3262 sent over the wire. The machine at the other end of the PPP link
3263 (usually your ISP) has to support the BSD-Compress compression
3264 method as well for this to be useful. Even if they don't support it,
3265 it is safe to say Y here.
3267 The PPP Deflate compression method ("PPP Deflate compression",
3268 above) is preferable to BSD-Compress, because it compresses better
3271 Note that the BSD compression code will always be compiled as a
3272 module; it is called bsd_comp and will show up in the directory
3273 modules once you have said "make modules". If unsure, say N.
3276 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3277 depends on PPP && EXPERIMENTAL
3283 Support for the MPPE Encryption protocol, as employed by the
3284 Microsoft Point-to-Point Tunneling Protocol.
3286 See http://pptpclient.sourceforge.net/ for information on
3287 configuring PPTP clients and servers to utilize this method.
3290 tristate "PPP over Ethernet (EXPERIMENTAL)"
3291 depends on EXPERIMENTAL && PPP
3293 Support for PPP over Ethernet.
3295 This driver requires the latest version of pppd from the CVS
3296 repository at cvs.samba.org. Alternatively, see the
3297 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3298 which contains instruction on how to use this driver (under
3299 the heading "Kernel mode PPPoE").
3302 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3303 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3305 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3307 This driver requires pppd plugin to work in client mode or
3308 modified pptpd (poptop) to work in server mode.
3309 See http://accel-pptp.sourceforge.net/ for information how to
3310 utilize this module.
3313 tristate "PPP over ATM"
3314 depends on ATM && PPP
3316 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3317 This implementation does not yet comply with section 8 of RFC2364,
3318 which can lead to bad results if the ATM peer loses state and
3319 changes its encapsulation unilaterally.
3322 tristate "PPP over L2TP (EXPERIMENTAL)"
3323 depends on EXPERIMENTAL && L2TP && PPP
3325 Support for PPP-over-L2TP socket family. L2TP is a protocol
3326 used by ISPs and enterprises to tunnel PPP traffic over UDP
3327 tunnels. L2TP is replacing PPTP for VPN uses.
3330 tristate "SLIP (serial line) support"
3332 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3333 connect to your Internet service provider or to connect to some
3334 other local Unix box or if you want to configure your Linux box as a
3335 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3336 Internet Protocol) is a protocol used to send Internet traffic over
3337 serial connections such as telephone lines or null modem cables;
3338 nowadays, the protocol PPP is more commonly used for this same
3341 Normally, your access provider has to support SLIP in order for you
3342 to be able to use it, but there is now a SLIP emulator called SLiRP
3343 around (available from
3344 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3345 allows you to use SLIP over a regular dial up shell connection. If
3346 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3347 NET-3-HOWTO, available from
3348 <http://www.tldp.org/docs.html#howto>, explains how to
3349 configure SLIP. Note that you don't need this option if you just
3350 want to run term (term is a program which gives you almost full
3351 Internet connectivity if you have a regular dial up shell account on
3352 some Internet connected Unix computer. Read
3353 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3354 support will enlarge your kernel by about 4 KB. If unsure, say N.
3356 To compile this driver as a module, choose M here. The module
3357 will be called slip.
3359 config SLIP_COMPRESSED
3360 bool "CSLIP compressed headers"
3364 This protocol is faster than SLIP because it uses compression on the
3365 TCP/IP headers (not on the data itself), but it has to be supported
3366 on both ends. Ask your access provider if you are not sure and
3367 answer Y, just in case. You will still be able to use plain SLIP. If
3368 you plan to use SLiRP, the SLIP emulator (available from
3369 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3370 allows you to use SLIP over a regular dial up shell connection, you
3371 definitely want to say Y here. The NET-3-HOWTO, available from
3372 <http://www.tldp.org/docs.html#howto>, explains how to configure
3373 CSLIP. This won't enlarge your kernel.
3378 This option enables Van Jacobsen serial line header compression
3382 bool "Keepalive and linefill"
3385 Adds additional capabilities to the SLIP driver to support the
3386 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3389 config SLIP_MODE_SLIP6
3390 bool "Six bit SLIP encapsulation"
3393 Just occasionally you may need to run IP over hostile serial
3394 networks that don't pass all control characters or are only seven
3395 bit. Saying Y here adds an extra mode you can use with SLIP:
3396 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3397 the serial device. Naturally, this has to be supported at the other
3398 end of the link as well. It's good enough, for example, to run IP
3399 over the async ports of a Camtec JNT Pad. If unsure, say N.
3402 bool "Fibre Channel driver support"
3403 depends on SCSI && PCI
3405 Fibre Channel is a high speed serial protocol mainly used to connect
3406 large storage devices to the computer; it is compatible with and
3407 intended to replace SCSI.
3409 If you intend to use Fibre Channel, you need to have a Fibre channel
3410 adaptor card in your computer; say Y here and to the driver for your
3411 adaptor below. You also should have said Y to "SCSI support" and
3412 "SCSI generic support".
3415 tristate "Network console logging support"
3417 If you want to log kernel messages over the network, enable this.
3418 See <file:Documentation/networking/netconsole.txt> for details.
3420 config NETCONSOLE_DYNAMIC
3421 bool "Dynamic reconfiguration of logging targets"
3422 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
3423 !(NETCONSOLE=y && CONFIGFS_FS=m)
3425 This option enables the ability to dynamically reconfigure target
3426 parameters (interface, IP addresses, port numbers, MAC addresses)
3427 at runtime through a userspace interface exported using configfs.
3428 See <file:Documentation/networking/netconsole.txt> for details.
3434 bool "Netpoll traffic trapping"
3438 config NET_POLL_CONTROLLER
3442 tristate "Virtio network driver (EXPERIMENTAL)"
3443 depends on EXPERIMENTAL && VIRTIO
3445 This is the virtual network driver for virtio. It can be used with
3446 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3449 tristate "VMware VMXNET3 ethernet driver"
3450 depends on PCI && INET
3452 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3453 To compile this driver as a module, choose M here: the
3454 module will be called vmxnet3.