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 menuconfig NET_ETHERNET
197 bool "Ethernet (10 or 100Mbit)"
200 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
201 type of Local Area Network (LAN) in universities and companies.
203 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
204 coaxial cable, linking computers in a chain), 10BASE-T or twisted
205 pair (10 Mbps over twisted pair cable, linking computers to central
206 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
207 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
208 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
209 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
210 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
211 Ethernet (1 Gbps over optical fiber or short copper links).
213 If your Linux machine will be connected to an Ethernet and you have
214 an Ethernet network interface card (NIC) installed in your computer,
215 say Y here and read the Ethernet-HOWTO, available from
216 <http://www.tldp.org/docs.html#howto>. You will then also have
217 to say Y to the driver for your particular NIC.
219 Note that the answer to this question won't directly affect the
220 kernel: saying N will just cause the configurator to skip all
221 the questions about Ethernet network cards. If unsure, say N.
226 tristate "Atmel MACB support"
227 depends on HAVE_NET_MACB
230 The Atmel MACB ethernet interface is found on many AT32 and AT91
231 parts. Say Y to include support for the MACB chip.
233 To compile this driver as a module, choose M here: the module
236 source "drivers/net/arm/Kconfig"
239 tristate "ASIX AX88796 NE2000 clone support"
240 depends on ARM || MIPS || SUPERH
244 AX88796 driver, using platform bus to provide
245 chip detection and resources
248 bool "ASIX AX88796 external 93CX6 eeprom support"
252 Select this if your platform comes with an external 93CX6 eeprom.
255 tristate "RK29 VMAC ethernet support"
261 MAC device present on rockchip rk29xx
265 tristate "MACE (Power Mac ethernet) support"
266 depends on PPC_PMAC && PPC32
269 Power Macintoshes and clones with Ethernet built-in on the
270 motherboard will usually use a MACE (Medium Access Control for
271 Ethernet) interface. Say Y to include support for the MACE chip.
273 To compile this driver as a module, choose M here: the module
276 config MACE_AAUI_PORT
277 bool "Use AAUI port instead of TP by default"
280 Some Apple machines (notably the Apple Network Server) which use the
281 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
282 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
283 Y here if you have such a machine. If unsure, say N.
284 The driver will default to AAUI on ANS anyway, and if you use it as
285 a module, you can provide the port_aaui=0|1 to force the driver.
288 tristate "BMAC (G3 ethernet) support"
289 depends on PPC_PMAC && PPC32
292 Say Y for support of BMAC Ethernet interfaces. These are used on G3
295 To compile this driver as a module, choose M here: the module
299 tristate "Ariadne support"
302 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
305 To compile this driver as a module, choose M here: the module
306 will be called ariadne.
309 tristate "A2065 support"
313 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
316 To compile this driver as a module, choose M here: the module
317 will be called a2065.
320 tristate "Hydra support"
324 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
326 To compile this driver as a module, choose M here: the module
327 will be called hydra.
330 tristate "Zorro NS8390-based Ethernet support"
334 This driver is for Zorro Ethernet cards using an NS8390-compatible
335 chipset, like the Village Tronic Ariadne II and the Individual
336 Computers X-Surf Ethernet cards. If you have such a card, say Y.
339 To compile this driver as a module, choose M here: the module
340 will be called zorro8390.
343 tristate "PCMCIA NE2000 support"
344 depends on AMIGA_PCMCIA
347 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
350 To compile this driver as a module, choose M here: the module
354 bool "Macintosh NS 8390 based ethernet cards"
358 If you want to include a driver to support Nubus or LC-PDS
359 Ethernet cards using an NS8390 chipset or its equivalent, say Y
360 and read the Ethernet-HOWTO, available from
361 <http://www.tldp.org/docs.html#howto>.
364 tristate "Macintosh CS89x0 based ethernet cards"
367 Support for CS89x0 chipset based Ethernet cards. If you have a
368 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
369 read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
372 To compile this driver as a module, choose M here. This module will
376 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
379 Support for NatSemi SONIC based Ethernet devices. This includes
380 the onboard Ethernet in many Quadras as well as some LC-PDS,
381 a few Nubus and all known Comm Slot Ethernet cards. If you have
382 one of these say Y and read the Ethernet-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>.
385 To compile this driver as a module, choose M here. This module will
389 bool "Macintosh (AV) onboard MACE ethernet"
393 Support for the onboard AMD 79C940 MACE Ethernet controller used in
394 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
395 say Y and read the Ethernet-HOWTO, available from
396 <http://www.tldp.org/docs.html#howto>.
399 tristate "MVME147 (Lance) Ethernet support"
403 Support for the on-board Ethernet interface on the Motorola MVME147
404 single-board computer. Say Y here to include the
405 driver for this chip in your kernel.
406 To compile this driver as a module, choose M here.
409 tristate "MVME16x Ethernet support"
412 This is the driver for the Ethernet interface on the Motorola
413 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
414 driver for this chip in your kernel.
415 To compile this driver as a module, choose M here.
418 tristate "BVME6000 Ethernet support"
421 This is the driver for the Ethernet interface on BVME4000 and
422 BVME6000 VME boards. Say Y here to include the driver for this chip
424 To compile this driver as a module, choose M here.
427 tristate "Atari Lance support"
430 Say Y to include support for several Atari Ethernet adapters based
431 on the AMD Lance chipset: RieblCard (with or without battery), or
432 PAMCard VME (also the version by Rhotron, with different addresses).
435 tristate "Sun3/Sun3x on-board LANCE support"
436 depends on SUN3 || SUN3X
438 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
439 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
440 here to compile in the Linux driver for this and enable Ethernet.
441 General Linux information on the Sun 3 and 3x series (now
443 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
445 If you're not building a kernel for a Sun 3, say N.
448 bool "Sun3 on-board Intel 82586 support"
451 This driver enables support for the on-board Intel 82586 based
452 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
453 that this driver does not support 82586-based adapters on additional
457 bool "HP on-board LANCE support"
461 If you want to use the builtin "LANCE" Ethernet controller on an
462 HP300 machine, say Y here.
465 tristate "Lasi ethernet"
468 Say Y here to support the builtin Intel 82596 ethernet controller
469 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
472 tristate "SNI RM ethernet"
473 depends on NET_ETHERNET && SNI_RM
475 Say Y here to support the on-board Intel 82596 ethernet controller
476 built into SNI RM machines.
479 tristate "Korina (IDT RC32434) Ethernet support"
480 depends on NET_ETHERNET && MIKROTIK_RB532
482 If you have a Mikrotik RouterBoard 500 or IDT RC32434
483 based system say Y. Otherwise say N.
485 config MIPS_JAZZ_SONIC
486 tristate "MIPS JAZZ onboard SONIC Ethernet support"
489 This is the driver for the onboard card of MIPS Magnum 4000,
490 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
492 config XTENSA_XT2000_SONIC
493 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
494 depends on XTENSA_PLATFORM_XT2000
496 This is the driver for the onboard card of the Xtensa XT2000 board.
498 config MIPS_AU1X00_ENET
499 tristate "MIPS AU1000 Ethernet support"
500 depends on MIPS_ALCHEMY
504 If you have an Alchemy Semi AU1X00 based system
505 say Y. Otherwise, say N.
508 bool "SGI IOC3 Ethernet"
509 depends on PCI && SGI_IP27
513 If you have a network (Ethernet) card of this type, say Y and read
514 the Ethernet-HOWTO, available from
515 <http://www.tldp.org/docs.html#howto>.
518 tristate "MIPS simulator Network device"
521 The MIPSNET device is a simple Ethernet network device which is
522 emulated by the MIPS Simulator.
523 If you are not using a MIPSsim or are unsure, say N.
525 config SGI_O2MACE_ETH
526 tristate "SGI O2 MACE Fast Ethernet support"
527 depends on SGI_IP32=y
530 tristate "National DP83902AV support"
534 Support for cards based on the National Semiconductor DP83902AV
535 ST-NIC Serial Network Interface Controller for Twisted Pair. This
536 is a 10Mbit/sec Ethernet controller. Product overview and specs at
537 <http://www.national.com/pf/DP/DP83902A.html>.
542 tristate "Renesas SuperH Ethernet support"
543 depends on SUPERH && \
544 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
545 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
546 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
552 Renesas SuperH Ethernet device driver.
553 This driver supporting CPUs are:
554 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
557 tristate "Sun LANCE support"
561 This driver supports the "le" interface present on all 32-bit Sparc
562 systems, on some older Ultra systems and as an Sbus option. These
563 cards are based on the AMD Lance chipset, which is better known
564 via the NE2100 cards.
566 To compile this driver as a module, choose M here: the module
567 will be called sunlance.
570 tristate "Sun Happy Meal 10/100baseT support"
571 depends on SBUS || PCI
574 This driver supports the "hme" interface present on most Ultra
575 systems and as an option on older Sbus systems. This driver supports
576 both PCI and Sbus devices. This driver also supports the "qfe" quad
577 100baseT device available in both PCI and Sbus configurations.
579 To compile this driver as a module, choose M here: the module
580 will be called sunhme.
583 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
584 depends on SBUS && EXPERIMENTAL
587 This driver supports the "be" interface available as an Sbus option.
588 This is Sun's older 100baseT Ethernet device.
590 To compile this driver as a module, choose M here: the module
591 will be called sunbmac.
594 tristate "Sun QuadEthernet support"
598 This driver supports the "qe" 10baseT Ethernet device, available as
599 an Sbus option. Note that this is not the same as Quad FastEthernet
600 "qfe" which is supported by the Happy Meal driver instead.
602 To compile this driver as a module, choose M here: the module
603 will be called sunqe.
606 tristate "Sun GEM support"
610 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
611 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
614 tristate "Sun Cassini support"
618 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
619 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
622 tristate "Sun Virtual Network support"
625 Support for virtual network devices under Sun Logical Domains.
627 config NET_VENDOR_3COM
629 depends on ISA || EISA || MCA || PCI
631 If you have a network (Ethernet) card belonging to this class, say Y
632 and read the Ethernet-HOWTO, available from
633 <http://www.tldp.org/docs.html#howto>.
635 Note that the answer to this question doesn't directly affect the
636 kernel: saying N will just cause the configurator to skip all
637 the questions about 3COM cards. If you say Y, you will be asked for
638 your specific card in the following questions.
641 tristate "3c501 \"EtherLink\" support"
642 depends on NET_VENDOR_3COM && ISA
644 If you have a network (Ethernet) card of this type, say Y and read
645 the Ethernet-HOWTO, available from
646 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
647 new card, since the 3c501 is slow, broken, and obsolete: you will
648 have problems. Some people suggest to ping ("man ping") a nearby
649 machine every minute ("man cron") when using this card.
651 To compile this driver as a module, choose M here. The module
652 will be called 3c501.
655 tristate "3c503 \"EtherLink II\" support"
656 depends on NET_VENDOR_3COM && ISA
659 If you have a network (Ethernet) card of this type, say Y and read
660 the Ethernet-HOWTO, available from
661 <http://www.tldp.org/docs.html#howto>.
663 To compile this driver as a module, choose M here. The module
664 will be called 3c503.
667 tristate "3c505 \"EtherLink Plus\" support"
668 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
670 Information about this network (Ethernet) card can be found in
671 <file:Documentation/networking/3c505.txt>. If you have a card of
672 this type, say Y and read the Ethernet-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 To compile this driver as a module, choose M here. The module
676 will be called 3c505.
679 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
680 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
682 If you have a network (Ethernet) card of this type, say Y and read
683 the Ethernet-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>.
686 To compile this driver as a module, choose M here. The module
687 will be called 3c507.
690 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
691 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
693 If you have a network (Ethernet) card belonging to the 3Com
694 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
695 from <http://www.tldp.org/docs.html#howto>.
697 If your card is not working you may need to use the DOS
698 setup disk to disable Plug & Play mode, and to select the default
701 To compile this driver as a module, choose M here. The module
702 will be called 3c509.
705 tristate "3c515 ISA \"Fast EtherLink\""
706 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
708 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
709 network card, say Y and read the Ethernet-HOWTO, available from
710 <http://www.tldp.org/docs.html#howto>.
712 To compile this driver as a module, choose M here. The module
713 will be called 3c515.
716 tristate "3c523 \"EtherLink/MC\" support"
717 depends on NET_VENDOR_3COM && MCA_LEGACY
719 If you have a network (Ethernet) card of this type, say Y and read
720 the Ethernet-HOWTO, available from
721 <http://www.tldp.org/docs.html#howto>.
723 To compile this driver as a module, choose M here. The module
724 will be called 3c523.
727 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
728 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
730 If you have a network (Ethernet) card of this type, say Y and read
731 the Ethernet-HOWTO, available from
732 <http://www.tldp.org/docs.html#howto>.
734 To compile this driver as a module, choose M here. The module
735 will be called 3c527.
738 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
739 depends on NET_VENDOR_3COM && (PCI || EISA)
742 This option enables driver support for a large number of 10Mbps and
743 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
745 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
746 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
747 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
748 "Tornado" (3c905) PCI
749 "Hurricane" (3c555/3cSOHO) PCI
751 If you have such a card, say Y and read the Ethernet-HOWTO,
752 available from <http://www.tldp.org/docs.html#howto>. More
753 specific information is in
754 <file:Documentation/networking/vortex.txt> and in the comments at
755 the beginning of <file:drivers/net/3c59x.c>.
757 To compile this support as a module, choose M here.
760 tristate "3cr990 series \"Typhoon\" support"
761 depends on NET_VENDOR_3COM && PCI
764 This option enables driver support for the 3cr990 series of cards:
766 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
767 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
768 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
770 If you have a network (Ethernet) card of this type, say Y and read
771 the Ethernet-HOWTO, available from
772 <http://www.tldp.org/docs.html#howto>.
774 To compile this driver as a module, choose M here. The module
775 will be called typhoon.
778 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
779 depends on ISA && ISA_DMA_API
781 If you have a network (Ethernet) card of this type, say Y and read
782 the Ethernet-HOWTO, available from
783 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
786 To compile this driver as a module, choose M here: the module
787 will be called lance. This is recommended.
789 config NET_VENDOR_SMC
790 bool "Western Digital/SMC cards"
791 depends on ISA || MCA || EISA || MAC
793 If you have a network (Ethernet) card belonging to this class, say Y
794 and read the Ethernet-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 Note that the answer to this question doesn't directly affect the
798 kernel: saying N will just cause the configurator to skip all
799 the questions about Western Digital cards. If you say Y, you will be
800 asked for your specific card in the following questions.
803 tristate "WD80*3 support"
804 depends on NET_VENDOR_SMC && ISA
807 If you have a network (Ethernet) card of this type, say Y and read
808 the Ethernet-HOWTO, available from
809 <http://www.tldp.org/docs.html#howto>.
811 To compile this driver as a module, choose M here. The module
815 tristate "SMC Ultra MCA support"
816 depends on NET_VENDOR_SMC && MCA
819 If you have a network (Ethernet) card of this type and are running
820 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
821 available from <http://www.tldp.org/docs.html#howto>.
823 To compile this driver as a module, choose M here. The module
824 will be called smc-mca.
827 tristate "SMC Ultra support"
828 depends on NET_VENDOR_SMC && ISA
831 If you have a network (Ethernet) card of this type, say Y and read
832 the Ethernet-HOWTO, available from
833 <http://www.tldp.org/docs.html#howto>.
835 Important: There have been many reports that, with some motherboards
836 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
837 such as some BusLogic models) causes corruption problems with many
838 operating systems. The Linux smc-ultra driver has a work-around for
839 this but keep it in mind if you have such a SCSI card and have
842 To compile this driver as a module, choose M here. The module
843 will be called smc-ultra.
846 tristate "SMC Ultra32 EISA support"
847 depends on NET_VENDOR_SMC && EISA
850 If you have a network (Ethernet) card of this type, say Y and read
851 the Ethernet-HOWTO, available from
852 <http://www.tldp.org/docs.html#howto>.
854 To compile this driver as a module, choose M here. The module
855 will be called smc-ultra32.
858 tristate "Blackfin on-chip MAC support"
859 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
863 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
865 This is the driver for Blackfin on-chip mac device. Say Y if you want it
866 compiled into the kernel. This driver is also available as a module
867 ( = code which can be inserted in and removed from the running kernel
868 whenever you want). The module will be called bfin_mac.
870 config BFIN_MAC_USE_L1
871 bool "Use L1 memory for rx/tx packets"
872 depends on BFIN_MAC && (BF527 || BF537)
875 To get maximum network performance, you should use L1 memory as rx/tx buffers.
876 Say N here if you want to reserve L1 memory for other uses.
878 config BFIN_TX_DESC_NUM
879 int "Number of transmit buffer packets"
881 range 6 10 if BFIN_MAC_USE_L1
885 Set the number of buffer packets used in driver.
887 config BFIN_RX_DESC_NUM
888 int "Number of receive buffer packets"
890 range 20 100 if BFIN_MAC_USE_L1
894 Set the number of buffer packets used in driver.
896 config BFIN_MAC_USE_HWSTAMP
897 bool "Use IEEE 1588 hwstamp"
898 depends on BFIN_MAC && BF518
901 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
904 tristate "SMC 9194 support"
905 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
908 This is support for the SMC9xxx based Ethernet cards. Choose this
909 option if you have a DELL laptop with the docking station, or
910 another SMC9192/9194 based chipset. Say Y if you want it compiled
911 into the kernel, and read the file
912 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
913 available from <http://www.tldp.org/docs.html#howto>.
915 To compile this driver as a module, choose M here. The module
916 will be called smc9194.
919 tristate "SMC 91C9x/91C1xxx support"
922 depends on ARM || M32R || SUPERH || \
923 MIPS || BLACKFIN || MN10300 || COLDFIRE
925 This is a driver for SMC's 91x series of Ethernet chipsets,
926 including the SMC91C94 and the SMC91C111. Say Y if you want it
927 compiled into the kernel, and read the file
928 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
929 available from <http://www.tldp.org/docs.html#howto>.
931 This driver is also available as a module ( = code which can be
932 inserted in and removed from the running kernel whenever you want).
933 The module will be called smc91x. If you want to compile it as a
934 module, say M here and read <file:Documentation/kbuild/modules.txt>.
937 tristate "Marvell pxa168 ethernet support"
938 depends on CPU_PXA168
941 This driver supports the pxa168 Ethernet ports.
943 To compile this driver as a module, choose M here. The module
944 will be called pxa168_eth.
947 tristate "NetX Ethernet support"
951 This is support for the Hilscher netX builtin Ethernet ports
953 To compile this driver as a module, choose M here. The module
954 will be called netx-eth.
956 config TI_DAVINCI_EMAC
957 tristate "TI DaVinci EMAC Support"
958 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
959 select TI_DAVINCI_MDIO
960 select TI_DAVINCI_CPDMA
963 This driver supports TI's DaVinci Ethernet .
965 To compile this driver as a module, choose M here: the module
966 will be called davinci_emac_driver. This is recommended.
968 config TI_DAVINCI_MDIO
969 tristate "TI DaVinci MDIO Support"
970 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
973 This driver supports TI's DaVinci MDIO module.
975 To compile this driver as a module, choose M here: the module
976 will be called davinci_mdio. This is recommended.
978 config TI_DAVINCI_CPDMA
979 tristate "TI DaVinci CPDMA Support"
980 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
982 This driver supports TI's DaVinci CPDMA dma engine.
984 To compile this driver as a module, choose M here: the module
985 will be called davinci_cpdma. This is recommended.
988 tristate "DM9000 support"
989 depends on ARM || BLACKFIN || MIPS
993 Support for DM9000 chipset.
995 To compile this driver as a module, choose M here. The module
996 will be called dm9000.
998 config DM9000_DEBUGLEVEL
999 int "DM9000 maximum debug level"
1003 The maximum level of debugging code compiled into the DM9000
1008 prompt "choose control"
1009 config DM9000_USE_NAND_CONTROL
1010 tristate "DM9000 with NANDC Interface"
1012 config DM9000_USE_NOR_CONTROL
1013 tristate "DM9000 with NOR Interface"
1017 config DM9000_FORCE_SIMPLE_PHY_POLL
1018 bool "Force simple NSR based PHY polling"
1021 This configuration forces the DM9000 to use the NSR's LinkStatus
1022 bit to determine if the link is up or down instead of the more
1023 costly MII PHY reads. Note, this will not work if the chip is
1024 operating with an external PHY.
1027 tristate "ENC28J60 support"
1028 depends on EXPERIMENTAL && SPI && NET_ETHERNET
1031 Support for the Microchip EN28J60 ethernet chip.
1033 To compile this driver as a module, choose M here. The module will be
1036 config ENC28J60_WRITEVERIFY
1037 bool "Enable write verify"
1040 Enable the verify after the buffer write useful for debugging purpose.
1044 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
1045 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1051 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1054 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1059 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1062 tristate "SMSC LAN911[5678] support"
1065 depends on ARM || SUPERH || MN10300
1067 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1068 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1069 Say Y if you want it compiled into the kernel,
1070 and read the Ethernet-HOWTO, available from
1071 <http://www.tldp.org/docs.html#howto>.
1073 This driver is also available as a module. The module will be
1074 called smc911x. If you want to compile it as a module, say M
1075 here and read <file:Documentation/kbuild/modules.txt>
1078 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1079 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
1084 Say Y here if you want support for SMSC LAN911x and LAN921x families
1085 of ethernet controllers.
1087 To compile this driver as a module, choose M here and read
1088 <file:Documentation/networking/net-modules.txt>. The module
1089 will be called smsc911x.
1091 config SMSC911X_ARCH_HOOKS
1095 If the arch enables this, it allows the arch to implement various
1096 hooks for more comprehensive interrupt control and also to override
1097 the source of the MAC address.
1099 config NET_VENDOR_RACAL
1100 bool "Racal-Interlan (Micom) NI cards"
1103 If you have a network (Ethernet) card belonging to this class, such
1104 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1105 available from <http://www.tldp.org/docs.html#howto>.
1107 Note that the answer to this question doesn't directly affect the
1108 kernel: saying N will just cause the configurator to skip all
1109 the questions about NI cards. If you say Y, you will be asked for
1110 your specific card in the following questions.
1113 tristate "NI5010 support (EXPERIMENTAL)"
1114 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1116 If you have a network (Ethernet) card of this type, say Y and read
1117 the Ethernet-HOWTO, available from
1118 <http://www.tldp.org/docs.html#howto>. Note that this is still
1121 To compile this driver as a module, choose M here. The module
1122 will be called ni5010.
1125 tristate "NI5210 support"
1126 depends on NET_VENDOR_RACAL && ISA
1128 If you have a network (Ethernet) card of this type, say Y and read
1129 the Ethernet-HOWTO, available from
1130 <http://www.tldp.org/docs.html#howto>.
1132 To compile this driver as a module, choose M here. The module
1133 will be called ni52.
1136 tristate "NI6510 support"
1137 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1139 If you have a network (Ethernet) card of this type, say Y and read
1140 the Ethernet-HOWTO, available from
1141 <http://www.tldp.org/docs.html#howto>.
1143 To compile this driver as a module, choose M here. The module
1144 will be called ni65.
1147 tristate "Dave ethernet support (DNET)"
1148 depends on NET_ETHERNET && HAS_IOMEM
1151 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1152 Say Y to include support for the DNET chip.
1154 To compile this driver as a module, choose M here: the module
1155 will be called dnet.
1157 source "drivers/net/tulip/Kconfig"
1160 tristate "AT1700/1720 support (EXPERIMENTAL)"
1161 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1164 If you have a network (Ethernet) card of this type, say Y and read
1165 the Ethernet-HOWTO, available from
1166 <http://www.tldp.org/docs.html#howto>.
1168 To compile this driver as a module, choose M here. The module
1169 will be called at1700.
1172 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1173 depends on ISA || EISA || MCA
1176 If you have a network (Ethernet) card of this type, say Y and read
1177 the Ethernet-HOWTO, available from
1178 <http://www.tldp.org/docs.html#howto> as well as
1179 <file:drivers/net/depca.c>.
1181 To compile this driver as a module, choose M here. The module
1182 will be called depca.
1185 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1186 depends on ISA || EISA || PCI
1188 If you have a network (Ethernet) card of this type, say Y and read
1189 the Ethernet-HOWTO, available from
1190 <http://www.tldp.org/docs.html#howto>.
1192 To compile this driver as a module, choose M here. The module
1193 will be called hp100.
1196 bool "Other ISA cards"
1199 If your network (Ethernet) card hasn't been mentioned yet and its
1200 bus system (that's the way the cards talks to the other components
1201 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1202 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1203 available from <http://www.tldp.org/docs.html#howto>.
1207 Note that the answer to this question doesn't directly affect the
1208 kernel: saying N will just cause the configurator to skip all
1209 the remaining ISA network card questions. If you say Y, you will be
1210 asked for your specific card in the following questions.
1213 tristate "Cabletron E21xx support"
1217 If you have a network (Ethernet) card of this type, say Y and read
1218 the Ethernet-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here. The module
1222 will be called e2100.
1225 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1229 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1230 cards. If this is for you, say Y and read
1231 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1232 well as the Ethernet-HOWTO, available from
1233 <http://www.tldp.org/docs.html#howto>.
1235 To compile this driver as a module, choose M here. The module
1236 will be called ewrk3.
1239 tristate "EtherExpress 16 support"
1242 If you have an EtherExpress16 network (Ethernet) card, say Y and
1243 read the Ethernet-HOWTO, available from
1244 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1245 EtherExpress16 card used to be regarded as a very poor choice
1246 because the driver was very unreliable. We now have a new driver
1247 that should do better.
1249 To compile this driver as a module, choose M here. The module
1250 will be called eexpress.
1253 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1256 If you have a network (Ethernet) card of this type, say Y. This
1257 driver supports Intel i82595{FX,TX} based boards. Note however
1258 that the EtherExpress PRO/100 Ethernet card has its own separate
1259 driver. Please read the Ethernet-HOWTO, available from
1260 <http://www.tldp.org/docs.html#howto>.
1262 To compile this driver as a module, choose M here. The module
1263 will be called eepro.
1266 tristate "HP PCLAN+ (27247B and 27252A) support"
1270 If you have a network (Ethernet) card of this type, say Y and read
1271 the Ethernet-HOWTO, available from
1272 <http://www.tldp.org/docs.html#howto>.
1274 To compile this driver as a module, choose M here. The module
1275 will be called hp-plus.
1278 tristate "HP PCLAN (27245 and other 27xxx series) 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
1290 tristate "LP486E on board Ethernet"
1293 Say Y here to support the 82596-based on-board Ethernet controller
1294 for the Panther motherboard, which is one of the two shipped in the
1295 Intel Professional Workstation.
1298 tristate "ICL EtherTeam 16i/32 support"
1301 If you have a network (Ethernet) card of this type, say Y and read
1302 the Ethernet-HOWTO, available from
1303 <http://www.tldp.org/docs.html#howto>.
1305 To compile this driver as a module, choose M here. The module
1306 will be called eth16i.
1309 tristate "NE2000/NE1000 support"
1310 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1313 If you have a network (Ethernet) card of this type, say Y and read
1314 the Ethernet-HOWTO, available from
1315 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1316 without a specific driver are compatible with NE2000.
1318 If you have a PCI NE2000 card however, say N here and Y to "PCI
1319 NE2000 and clone support" under "EISA, VLB, PCI and on board
1320 controllers" below. If you have a NE2000 card and are running on
1321 an MCA system (a bus system used on some IBM PS/2 computers and
1322 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1325 To compile this driver as a module, choose M here. The module
1329 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1330 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1332 The Zenith Z-Note notebook computer has a built-in network
1333 (Ethernet) card, and this is the Linux driver for it. Note that the
1334 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1335 by this driver. Read the Ethernet-HOWTO, available from
1336 <http://www.tldp.org/docs.html#howto>.
1339 tristate "SEEQ8005 support (EXPERIMENTAL)"
1340 depends on NET_ISA && EXPERIMENTAL
1342 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1343 is for you, read the Ethernet-HOWTO, available from
1344 <http://www.tldp.org/docs.html#howto>.
1346 To compile this driver as a module, choose M here. The module
1347 will be called seeq8005.
1350 tristate "NE/2 (ne2000 MCA version) support"
1351 depends on MCA_LEGACY
1354 If you have a network (Ethernet) card of this type, say Y and read
1355 the Ethernet-HOWTO, available from
1356 <http://www.tldp.org/docs.html#howto>.
1358 To compile this driver as a module, choose M here. The module
1362 tristate "IBM LAN Adapter/A support"
1365 This is a Micro Channel Ethernet adapter. You need to set
1366 CONFIG_MCA to use this driver. It is both available as an in-kernel
1367 driver and as a module.
1369 To compile this driver as a module, choose M here. The only
1370 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1371 will both support 16K and 32K memory windows, however a 32K window
1372 gives a better security against packet losses. Usage of multiple
1373 boards with this driver should be possible, but has not been tested
1374 up to now due to lack of hardware.
1377 tristate "IBM LAN Virtual Ethernet support"
1378 depends on PPC_PSERIES
1380 This driver supports virtual ethernet adapters on newer IBM iSeries
1381 and pSeries systems.
1383 To compile this driver as a module, choose M here. The module will
1386 source "drivers/net/ibm_newemac/Kconfig"
1389 bool "EISA, VLB, PCI and on board controllers"
1390 depends on ISA || EISA || PCI
1392 This is another class of network cards which attach directly to the
1393 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1394 available from <http://www.tldp.org/docs.html#howto>.
1396 Note that the answer to this question doesn't directly affect the
1397 kernel: saying N will just cause the configurator to skip all
1398 the questions about this class of network cards. If you say Y, you
1399 will be asked for your specific card in the following questions. If
1400 you are unsure, say Y.
1403 tristate "AMD PCnet32 PCI support"
1404 depends on NET_PCI && PCI
1408 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1409 answer Y here and read the Ethernet-HOWTO, available from
1410 <http://www.tldp.org/docs.html#howto>.
1412 To compile this driver as a module, choose M here. The module
1413 will be called pcnet32.
1416 tristate "AMD 8111 (new PCI lance) support"
1417 depends on NET_PCI && PCI
1421 If you have an AMD 8111-based PCI lance ethernet card,
1422 answer Y here and read the Ethernet-HOWTO, available from
1423 <http://www.tldp.org/docs.html#howto>.
1425 To compile this driver as a module, choose M here. The module
1426 will be called amd8111e.
1428 config ADAPTEC_STARFIRE
1429 tristate "Adaptec Starfire/DuraLAN support"
1430 depends on NET_PCI && PCI
1434 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1435 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1436 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1439 To compile this driver as a module, choose M here: the module
1440 will be called starfire. This is recommended.
1443 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1444 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1447 If you have a network (Ethernet) card of this type, say Y and read
1448 the Ethernet-HOWTO, available from
1449 <http://www.tldp.org/docs.html#howto>.
1451 To compile this driver as a module, choose M here. The module
1452 will be called ac3200.
1455 tristate "Micrel KSZ8841/2 PCI"
1456 depends on NET_PCI && PCI
1460 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1462 To compile this driver as a module, choose M here. The module
1463 will be called ksz884x.
1466 tristate "Apricot Xen-II on board Ethernet"
1467 depends on NET_PCI && ISA
1469 If you have a network (Ethernet) controller of this type, say Y and
1470 read the Ethernet-HOWTO, available from
1471 <http://www.tldp.org/docs.html#howto>.
1473 To compile this driver as a module, choose M here. The module
1474 will be called apricot.
1477 tristate "Broadcom 440x/47xx ethernet support"
1478 depends on SSB_POSSIBLE && HAS_DMA
1482 If you have a network (Ethernet) controller of this type, say Y
1483 or M and read the Ethernet-HOWTO, available from
1484 <http://www.tldp.org/docs.html#howto>.
1486 To compile this driver as a module, choose M here. The module
1489 # Auto-select SSB PCI-HOST support, if possible
1490 config B44_PCI_AUTOSELECT
1492 depends on B44 && SSB_PCIHOST_POSSIBLE
1496 # Auto-select SSB PCICORE driver, if possible
1497 config B44_PCICORE_AUTOSELECT
1499 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1500 select SSB_DRIVER_PCICORE
1505 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1509 tristate "nForce Ethernet support"
1510 depends on NET_PCI && PCI
1512 If you have a network (Ethernet) controller of this type, say Y and
1513 read the Ethernet-HOWTO, available from
1514 <http://www.tldp.org/docs.html#howto>.
1516 To compile this driver as a module, choose M here. The module
1517 will be called forcedeth.
1520 tristate "CS89x0 support"
1521 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1522 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1524 Support for CS89x0 chipset based Ethernet cards. If you have a
1525 network (Ethernet) card of this type, say Y and read the
1526 Ethernet-HOWTO, available from
1527 <http://www.tldp.org/docs.html#howto> as well as
1528 <file:Documentation/networking/cs89x0.txt>.
1530 To compile this driver as a module, choose M here. The module
1531 will be called cs89x0.
1533 config CS89x0_NONISA_IRQ
1535 depends on CS89x0 != n
1536 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1539 tristate "TOSHIBA TC35815 Ethernet support"
1540 depends on NET_PCI && PCI && MIPS
1544 tristate "Intel(R) PRO/100+ support"
1545 depends on NET_PCI && PCI
1548 This driver supports Intel(R) PRO/100 family of adapters.
1549 To verify that your adapter is supported, find the board ID number
1550 on the adapter. Look for a label that has a barcode and a number
1551 in the format 123456-001 (six digits hyphen three digits).
1553 Use the above information and the Adapter & Driver ID Guide at:
1555 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1557 to identify the adapter.
1559 For the latest Intel PRO/100 network driver for Linux, see:
1561 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1563 More specific information on configuring the driver is in
1564 <file:Documentation/networking/e100.txt>.
1566 To compile this driver as a module, choose M here. The module
1567 will be called e100.
1570 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1571 depends on NET_PCI && EISA && EXPERIMENTAL
1574 If you have a network (Ethernet) card of this type, say Y and read
1575 the Ethernet-HOWTO, available from
1576 <http://www.tldp.org/docs.html#howto>.
1578 To compile this driver as a module, choose M here. The module
1579 will be called lne390.
1582 tristate "Myson MTD-8xx PCI Ethernet support"
1583 depends on NET_PCI && PCI
1587 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1588 cards. <http://www.myson.com.tw/>
1591 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1592 depends on NET_PCI && PCI
1595 This driver is for the National Semiconductor DP83810 series,
1596 which is used in cards from PureData, NetGear, Linksys
1597 and others, including the 83815 chip.
1598 More specific information and updates are available from
1599 <http://www.scyld.com/network/natsemi.html>.
1602 tristate "PCI NE2000 and clones support (see help)"
1603 depends on NET_PCI && PCI
1606 This driver is for NE2000 compatible PCI cards. It will not work
1607 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1608 support" below). If you have a PCI NE2000 network (Ethernet) card,
1609 say Y and read the Ethernet-HOWTO, available from
1610 <http://www.tldp.org/docs.html#howto>.
1612 This driver also works for the following NE2000 clone cards:
1613 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1614 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1615 Holtek HT80232 Holtek HT80229
1617 To compile this driver as a module, choose M here. The module
1618 will be called ne2k-pci.
1621 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1622 depends on NET_PCI && EISA && EXPERIMENTAL
1625 If you have a network (Ethernet) card of this type, say Y and read
1626 the Ethernet-HOWTO, available from
1627 <http://www.tldp.org/docs.html#howto>. Note that this driver
1628 will NOT WORK for NE3200 cards as they are completely different.
1630 To compile this driver as a module, choose M here. The module
1631 will be called ne3210.
1634 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1635 depends on NET_PCI && EISA && EXPERIMENTAL
1638 If you have a network (Ethernet) card of this type, say Y and read
1639 the Ethernet-HOWTO, available from
1640 <http://www.tldp.org/docs.html#howto>.
1642 To compile this driver as a module, choose M here. The module
1643 will be called es3210.
1646 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1647 depends on NET_PCI && PCI && EXPERIMENTAL
1651 This is a driver for the Fast Ethernet PCI network cards based on
1652 the RTL8139C+ chips. If you have one of those, say Y and read
1653 the Ethernet-HOWTO, available from
1654 <http://www.tldp.org/docs.html#howto>.
1656 To compile this driver as a module, choose M here: the module
1657 will be called 8139cp. This is recommended.
1660 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1661 depends on NET_PCI && PCI
1665 This is a driver for the Fast Ethernet PCI network cards based on
1666 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1667 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1669 To compile this driver as a module, choose M here: the module
1670 will be called 8139too. This is recommended.
1673 bool "Use PIO instead of MMIO"
1677 This instructs the driver to use programmed I/O ports (PIO) instead
1678 of PCI shared memory (MMIO). This can possibly solve some problems
1679 in case your mainboard has memory consistency issues. If unsure,
1682 config 8139TOO_TUNE_TWISTER
1683 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1686 This implements a function which might come in handy in case you
1687 are using low quality on long cabling. It is required for RealTek
1688 RTL-8139 revision K boards, and totally unused otherwise. It tries
1689 to match the transceiver to the cable characteristics. This is
1690 experimental since hardly documented by the manufacturer.
1694 bool "Support for older RTL-8129/8130 boards"
1697 This enables support for the older and uncommon RTL-8129 and
1698 RTL-8130 chips, which support MII via an external transceiver,
1699 instead of an internal one. Disabling this option will save some
1700 memory by making the code size smaller. If unsure, say Y.
1702 config 8139_OLD_RX_RESET
1703 bool "Use older RX-reset method"
1706 The 8139too driver was recently updated to contain a more rapid
1707 reset sequence, in the face of severe receive errors. This "new"
1708 RX-reset method should be adequate for all boards. But if you
1709 experience problems, you can enable this option to restore the
1710 old RX-reset behavior. If unsure, say N.
1713 tristate "RDC R6040 Fast Ethernet Adapter support"
1714 depends on NET_PCI && PCI
1719 This is a driver for the R6040 Fast Ethernet MACs found in the
1720 the RDC R-321x System-on-chips.
1722 To compile this driver as a module, choose M here: the module
1723 will be called r6040. This is recommended.
1726 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1727 depends on NET_PCI && PCI
1731 This is a driver for the Fast Ethernet PCI network cards based on
1732 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1733 SiS 630 and SiS 540 chipsets.
1735 This driver also supports AMD 79C901 HomePNA so that you can use
1736 your phone line as a network cable.
1738 To compile this driver as a module, choose M here: the module
1739 will be called sis900. This is recommended.
1742 tristate "SMC EtherPower II"
1743 depends on NET_PCI && PCI
1747 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1748 which is based on the SMC83c17x (EPIC/100).
1749 More specific information and updates are available from
1750 <http://www.scyld.com/network/epic100.html>.
1753 tristate "SMSC LAN9420 PCI ethernet adapter support"
1754 depends on NET_PCI && PCI
1759 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1760 Say Y if you want it compiled into the kernel,
1761 and read the Ethernet-HOWTO, available from
1762 <http://www.tldp.org/docs.html#howto>.
1764 This driver is also available as a module. The module will be
1765 called smsc9420. If you want to compile it as a module, say M
1766 here and read <file:Documentation/kbuild/modules.txt>
1769 tristate "Sundance Alta support"
1770 depends on NET_PCI && PCI
1774 This driver is for the Sundance "Alta" chip.
1775 More specific information and updates are available from
1776 <http://www.scyld.com/network/sundance.html>.
1778 config SUNDANCE_MMIO
1779 bool "Use MMIO instead of PIO"
1782 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1783 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1784 is known to solve bugs on certain chips.
1789 tristate "TI ThunderLAN support"
1790 depends on NET_PCI && (PCI || EISA)
1792 If you have a PCI Ethernet network card based on the ThunderLAN chip
1793 which is supported by this driver, say Y and read the
1794 Ethernet-HOWTO, available from
1795 <http://www.tldp.org/docs.html#howto>.
1797 Devices currently supported by this driver are Compaq Netelligent,
1798 Compaq NetFlex and Olicom cards. Please read the file
1799 <file:Documentation/networking/tlan.txt> for more details.
1801 To compile this driver as a module, choose M here. The module
1802 will be called tlan.
1804 Please email feedback to <torben.mathiasen@compaq.com>.
1807 tristate "Micrel KSZ8841/42 with generic bus interface"
1808 depends on HAS_IOMEM && DMA_ENGINE
1810 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1811 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1815 tristate "Micrel KS8851 SPI"
1820 SPI driver for Micrel KS8851 SPI attached network chip.
1823 tristate "Micrel KS8851 MLL"
1824 depends on HAS_IOMEM
1827 This platform driver is for Micrel KS8851 Address/data bus
1828 multiplexed network chip.
1831 tristate "VIA Rhine support"
1832 depends on NET_PCI && PCI
1836 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1837 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1838 Ethernet functions can also be found integrated on South Bridges
1841 To compile this driver as a module, choose M here. The module
1842 will be called via-rhine.
1844 config VIA_RHINE_MMIO
1845 bool "Use MMIO instead of PIO"
1846 depends on VIA_RHINE
1848 This instructs the driver to use PCI shared memory (MMIO) instead of
1849 programmed I/O ports (PIO). Enabling this gives an improvement in
1850 processing time in parts of the driver.
1855 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1856 depends on NET_PCI && PCI && EXPERIMENTAL
1859 This is a driver for the Fast Ethernet PCI network cards based on
1860 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1861 have one of these, say Y here.
1863 To compile this driver as a module, choose M here: the module
1864 will be called sc92031. This is recommended.
1867 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1868 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1871 TI AR7 CPMAC Ethernet support
1874 bool "Pocket and portable adapters"
1877 Cute little network (Ethernet) devices which attach to the parallel
1878 port ("pocket adapters"), commonly used with laptops. If you have
1879 one of those, say Y and read the Ethernet-HOWTO, available from
1880 <http://www.tldp.org/docs.html#howto>.
1882 If you want to plug a network (or some other) card into the PCMCIA
1883 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1884 credit card size extension cards used by all modern laptops), you
1885 need the pcmcia-cs package (location contained in the file
1886 <file:Documentation/Changes>) and you can say N here.
1888 Laptop users should read the Linux Laptop home page at
1889 <http://www.linux-on-laptops.com/> or
1890 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1892 Note that the answer to this question doesn't directly affect the
1893 kernel: saying N will just cause the configurator to skip all
1894 the questions about this class of network devices. If you say Y, you
1895 will be asked for your specific device in the following questions.
1898 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1899 depends on NET_POCKET && PARPORT && X86
1902 This is a network (Ethernet) device which attaches to your parallel
1903 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1904 available from <http://www.tldp.org/docs.html#howto>, if you
1905 want to use this. If you intend to use this driver, you should have
1906 said N to the "Parallel printer support", because the two drivers
1907 don't like each other.
1909 To compile this driver as a module, choose M here: the module
1913 tristate "D-Link DE600 pocket adapter support"
1914 depends on NET_POCKET && PARPORT
1916 This is a network (Ethernet) device which attaches to your parallel
1917 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1918 Ethernet-HOWTO, available from
1919 <http://www.tldp.org/docs.html#howto>, if you want to use
1920 this. It is possible to have several devices share a single parallel
1921 port and it is safe to compile the corresponding drivers into the
1924 To compile this driver as a module, choose M here: the module
1925 will be called de600.
1928 tristate "D-Link DE620 pocket adapter support"
1929 depends on NET_POCKET && PARPORT
1931 This is a network (Ethernet) device which attaches to your parallel
1932 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1933 Ethernet-HOWTO, available from
1934 <http://www.tldp.org/docs.html#howto>, if you want to use
1935 this. It is possible to have several devices share a single parallel
1936 port and it is safe to compile the corresponding drivers into the
1939 To compile this driver as a module, choose M here: the module
1940 will be called de620.
1943 tristate "SGI Seeq ethernet controller support"
1944 depends on SGI_HAS_SEEQ
1946 Say Y here if you have an Seeq based Ethernet network card. This is
1947 used in many Silicon Graphics machines.
1950 tristate "DEC LANCE ethernet controller support"
1951 depends on MACH_DECSTATION
1954 This driver is for the series of Ethernet controllers produced by
1955 DEC (now Compaq) based on the AMD Lance chipset, including the
1956 DEPCA series. (This chipset is better known via the NE2100 cards.)
1959 bool "Motorola 68360 ethernet controller"
1962 Say Y here if you want to use the built-in ethernet controller of
1963 the Motorola 68360 processor.
1966 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1967 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1968 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1969 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1972 Say Y here if you want to use the built-in 10/100 Fast ethernet
1973 controller on some Motorola ColdFire and Freescale i.MX processors.
1976 tristate "MPC52xx FEC driver"
1977 depends on PPC_MPC52xx && PPC_BESTCOMM
1980 select PPC_BESTCOMM_FEC
1982 This option enables support for the MPC5200's on-chip
1983 Fast Ethernet Controller
1984 If compiled as module, it will be called fec_mpc52xx.
1986 config FEC_MPC52xx_MDIO
1987 bool "MPC52xx FEC MDIO bus driver"
1988 depends on FEC_MPC52xx
1991 The MPC5200's FEC can connect to the Ethernet either with
1992 an external MII PHY chip or 10 Mbps 7-wire interface
1993 (Motorola? industry standard).
1994 If your board uses an external PHY connected to FEC, enable this.
1995 If not sure, enable.
1996 If compiled as module, it will be called fec_mpc52xx_phy.
1999 tristate "NE2000 compatible support for H8/300"
2002 Say Y here if you want to use the NE2000 compatible
2003 controller on the Renesas H8/300 processor.
2006 tristate "Atheros L2 Fast Ethernet support"
2011 This driver supports the Atheros L2 fast ethernet adapter.
2013 To compile this driver as a module, choose M here. The module
2014 will be called atl2.
2016 config XILINX_EMACLITE
2017 tristate "Xilinx 10/100 Ethernet Lite support"
2018 depends on PPC32 || MICROBLAZE
2021 This driver supports the 10/100 Ethernet Lite from Xilinx.
2024 tristate "Broadcom 63xx internal mac support"
2029 This driver supports the ethernet MACs in the Broadcom 63xx
2030 MIPS chipset family (BCM63XX).
2033 tristate "Faraday FTMAC100 10/100 Ethernet support"
2037 This driver supports the FTMAC100 10/100 Ethernet controller
2038 from Faraday. It is used on Faraday A320, Andes AG101 and some
2039 other ARM/NDS32 SoC's.
2042 tristate "Lantiq SoC ETOP driver"
2043 depends on SOC_TYPE_XWAY
2045 Support for the MII0 inside the Lantiq SoC
2048 source "drivers/net/fs_enet/Kconfig"
2050 source "drivers/net/octeon/Kconfig"
2052 endif # NET_ETHERNET
2058 menuconfig NETDEV_1000
2059 bool "Ethernet (1000 Mbit)"
2063 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2064 type of Local Area Network (LAN) in universities and companies.
2066 Say Y here to get to see options for Gigabit Ethernet drivers.
2067 This option alone does not add any kernel code.
2068 Note that drivers supporting both 100 and 1000 MBit may be listed
2069 under "Ethernet (10 or 100MBit)" instead.
2071 If you say N, all options in this submenu will be skipped and disabled.
2076 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2079 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2080 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2081 adapter. The driver allows for using the Jumbo Frame option (9000
2082 bytes/frame) however it requires that your switches can handle this
2083 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2086 To compile this driver as a module, choose M here: the
2087 module will be called acenic.
2089 config ACENIC_OMIT_TIGON_I
2090 bool "Omit support for old Tigon I based AceNICs"
2093 Say Y here if you only have Tigon II based AceNICs and want to leave
2094 out support for the older Tigon I based cards which are no longer
2095 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2096 version)). This will reduce the size of the driver object by
2097 app. 100KB. If you are not sure whether your card is a Tigon I or a
2098 Tigon II, say N here.
2100 The safe and default value for this is N.
2103 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2107 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2109 D-Link DGE-550T Gigabit Ethernet Adapter.
2110 D-Link DL2000-based Gigabit Ethernet Adapter.
2111 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2113 To compile this driver as a module, choose M here: the
2114 module will be called dl2k.
2117 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2120 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2121 adapters. For more information on how to identify your adapter, go
2122 to the Adapter & Driver ID Guide at:
2124 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2126 For general information and support, go to the Intel support
2129 <http://support.intel.com>
2131 More specific information on configuring the driver is in
2132 <file:Documentation/networking/e1000.txt>.
2134 To compile this driver as a module, choose M here. The module
2135 will be called e1000.
2138 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2140 depends on PCI && (!SPARC32 || BROKEN)
2143 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2144 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2145 use the regular e1000 driver For more information on how to
2146 identify your adapter, go to the Adapter & Driver ID Guide at:
2148 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2150 For general information and support, go to the Intel support
2153 <http://support.intel.com>
2155 To compile this driver as a module, choose M here. The module
2156 will be called e1000e.
2159 tristate "IP1000 Gigabit Ethernet support"
2160 depends on PCI && EXPERIMENTAL
2163 This driver supports IP1000 gigabit Ethernet cards.
2165 To compile this driver as a module, choose M here: the module
2166 will be called ipg. This is recommended.
2169 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2172 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2173 adapters. For more information on how to identify your adapter, go
2174 to the Adapter & Driver ID Guide at:
2176 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2178 For general information and support, go to the Intel support
2181 <http://support.intel.com>
2183 More specific information on configuring the driver is in
2184 <file:Documentation/networking/e1000.txt>.
2186 To compile this driver as a module, choose M here. The module
2190 bool "Direct Cache Access (DCA) Support"
2192 depends on IGB && DCA && !(IGB=y && DCA=m)
2194 Say Y here if you want to use Direct Cache Access (DCA) in the
2195 driver. DCA is a method for warming the CPU cache before data
2196 is used, with the intent of lessening the impact of cache misses.
2199 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2202 This driver supports Intel(R) 82576 virtual functions. For more
2203 information on how to identify your adapter, go to the Adapter &
2206 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2208 For general information and support, go to the Intel support
2211 <http://support.intel.com>
2213 More specific information on configuring the driver is in
2214 <file:Documentation/networking/e1000.txt>.
2216 To compile this driver as a module, choose M here. The module
2217 will be called igbvf.
2219 source "drivers/net/ixp2000/Kconfig"
2222 tristate "MyriCOM Gigabit Ethernet support"
2225 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2227 To compile this driver as a module, choose M here: the module
2228 will be called myri_sbus. This is recommended.
2231 tristate "National Semiconductor DP83820 support"
2234 This is a driver for the National Semiconductor DP83820 series
2235 of gigabit ethernet MACs. Cards using this chipset include
2236 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2237 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2241 tristate "Packet Engines Hamachi GNIC-II support"
2245 If you have a Gigabit Ethernet card of this type, say Y and read
2246 the Ethernet-HOWTO, available from
2247 <http://www.tldp.org/docs.html#howto>.
2249 To compile this driver as a module, choose M here. The module will be
2253 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2254 depends on PCI && EXPERIMENTAL
2257 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2258 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2259 used by the Beowulf Linux cluster project. See
2260 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2261 information about this driver in particular and Beowulf in general.
2263 To compile this driver as a module, choose M here: the module
2264 will be called yellowfin. This is recommended.
2267 tristate "Realtek 8169 gigabit ethernet support"
2273 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2275 To compile this driver as a module, choose M here: the module
2276 will be called r8169. This is recommended.
2279 tristate "SB1250 Gigabit Ethernet support"
2280 depends on SIBYTE_SB1xxx_SOC
2283 This driver supports Gigabit Ethernet interfaces based on the
2284 Broadcom SiByte family of System-On-a-Chip parts. They include
2285 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2288 To compile this driver as a module, choose M here: the module
2289 will be called sb1250-mac.
2292 tristate "SiS190/SiS191 gigabit ethernet support"
2297 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2298 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2299 appear in lan on motherboard designs which are based on SiS 965
2300 and SiS 966 south bridge.
2302 To compile this driver as a module, choose M here: the module
2303 will be called sis190. This is recommended.
2306 tristate "New SysKonnect GigaEthernet support"
2310 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2311 and related Gigabit Ethernet adapters. It is a new smaller driver
2312 with better performance and more complete ethtool support.
2314 It does not support the link failover and network management
2315 features that "portable" vendor supplied sk98lin driver does.
2317 This driver supports adapters based on the original Yukon chipset:
2318 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2319 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2321 It does not support the newer Yukon2 chipset: a separate driver,
2322 sky2, is provided for Yukon2-based adapters.
2324 To compile this driver as a module, choose M here: the module
2325 will be called skge. This is recommended.
2328 bool "Debugging interface"
2329 depends on SKGE && DEBUG_FS
2331 This option adds the ability to dump driver state for debugging.
2332 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2333 transmit and receive rings.
2338 tristate "SysKonnect Yukon2 support"
2342 This driver supports Gigabit Ethernet adapters based on the
2343 Marvell Yukon 2 chipset:
2344 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2345 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2347 There is companion driver for the older Marvell Yukon and
2348 Genesis based adapters: skge.
2350 To compile this driver as a module, choose M here: the module
2351 will be called sky2. This is recommended.
2354 bool "Debugging interface"
2355 depends on SKY2 && DEBUG_FS
2357 This option adds the ability to dump driver state for debugging.
2358 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2359 transmit and receive rings.
2364 tristate "VIA Velocity support"
2370 If you have a VIA "Velocity" based network card say Y here.
2372 To compile this driver as a module, choose M here. The module
2373 will be called via-velocity.
2376 tristate "Broadcom Tigon3 support"
2380 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2382 To compile this driver as a module, choose M here: the module
2383 will be called tg3. This is recommended.
2386 tristate "Broadcom NetXtremeII support"
2391 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2393 To compile this driver as a module, choose M here: the module
2394 will be called bnx2. This is recommended.
2397 tristate "Broadcom CNIC support"
2402 This driver supports offload features of Broadcom NetXtremeII
2403 gigabit Ethernet cards.
2405 To compile this driver as a module, choose M here: the module
2406 will be called cnic. This is recommended.
2409 tristate "Spider Gigabit Ethernet driver"
2410 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2413 This driver supports the Gigabit Ethernet chips present on the
2414 Cell Processor-Based Blades from IBM.
2417 tristate "Tundra TSI108 gigabit Ethernet support"
2418 depends on TSI108_BRIDGE
2420 This driver supports Tundra TSI108 gigabit Ethernet ports.
2421 To compile this driver as a module, choose M here: the module
2422 will be called tsi108_eth.
2425 tristate "PS3 Gigabit Ethernet driver"
2427 select PS3_SYS_MANAGER
2429 This driver supports the network device on the PS3 game
2430 console. This driver has built-in support for Ethernet.
2432 To compile this driver as a module, choose M here: the
2433 module will be called ps3_gelic.
2435 config GELIC_WIRELESS
2436 bool "PS3 Wireless support"
2438 depends on GELIC_NET
2441 This option adds the support for the wireless feature of PS3.
2442 If you have the wireless-less model of PS3 or have no plan to
2443 use wireless feature, disabling this option saves memory. As
2444 the driver automatically distinguishes the models, you can
2445 safely enable this option even if you have a wireless-less model.
2448 tristate "Freescale PQ MDIO"
2452 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2455 tristate "Gianfar Ethernet"
2461 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2462 and MPC86xx family of chips, and the FEC on the 8540.
2465 tristate "Freescale QE Gigabit Ethernet"
2466 depends on QUICC_ENGINE
2470 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2471 which is available on some Freescale SOCs.
2473 config UGETH_TX_ON_DEMAND
2474 bool "Transmit on Demand support"
2478 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2479 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2483 This driver supports the gigabit ethernet MACs in the
2484 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2485 in the Marvell Orion ARM SoC family.
2487 Some boards that use the Discovery chipset are the Momenco
2488 Ocelot C and Jaguar ATX and Pegasos II.
2490 config XILINX_LL_TEMAC
2491 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2492 depends on PPC || MICROBLAZE
2495 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2496 core used in Xilinx Spartan and Virtex FPGAs
2499 tristate "QLogic QLA3XXX Network Driver Support"
2502 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2504 To compile this driver as a module, choose M here: the module
2505 will be called qla3xxx.
2508 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2513 This driver supports the Atheros/Attansic L1 gigabit ethernet
2516 To compile this driver as a module, choose M here. The module
2517 will be called atl1.
2520 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2521 depends on PCI && EXPERIMENTAL
2525 This driver supports the Atheros L1E gigabit ethernet adapter.
2527 To compile this driver as a module, choose M here. The module
2528 will be called atl1e.
2531 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2532 depends on PCI && EXPERIMENTAL
2536 This driver supports the Atheros L1C gigabit ethernet adapter.
2538 To compile this driver as a module, choose M here. The module
2539 will be called atl1c.
2542 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2547 This driver supports the PCI-Express gigabit ethernet adapters
2548 based on JMicron JMC250 chipset.
2550 To compile this driver as a module, choose M here. The module
2554 tristate "S6105 GMAC ethernet support"
2555 depends on XTENSA_VARIANT_S6000
2558 This driver supports the on chip ethernet device on the
2559 S6105 xtensa processor.
2561 To compile this driver as a module, choose M here. The module
2562 will be called s6gmac.
2564 source "drivers/net/stmmac/Kconfig"
2567 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
2571 This is a gigabit ethernet driver for EG20T PCH.
2572 EG20T PCH is the platform controller hub that is used in Intel's
2573 general embedded platform.
2574 EG20T PCH has Gigabit Ethernet interface.
2575 Using this interface, it is able to access system devices connected
2576 to Gigabit Ethernet.
2577 This driver enables Gigabit Ethernet function.
2579 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
2580 Output Hub), ML7223.
2581 ML7223 IOH is for MP(Media Phone) use.
2582 ML7223 is companion chip for Intel Atom E6xx series.
2583 ML7223 is completely compatible for Intel EG20T PCH.
2588 # 10 Gigabit Ethernet
2591 menuconfig NETDEV_10000
2592 bool "Ethernet (10000 Mbit)"
2596 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2597 This option alone does not add any kernel code.
2599 If you say N, all options in this submenu will be skipped and disabled.
2607 tristate "Chelsio 10Gb Ethernet support"
2612 This driver supports Chelsio gigabit and 10-gigabit
2613 Ethernet cards. More information about adapter features and
2614 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2616 For general information about Chelsio and our products, visit
2617 our website at <http://www.chelsio.com>.
2619 For customer support, please visit our customer support page at
2620 <http://www.chelsio.com/support.html>.
2622 Please send feedback to <linux-bugs@chelsio.com>.
2624 To compile this driver as a module, choose M here: the module
2625 will be called cxgb.
2627 config CHELSIO_T1_1G
2628 bool "Chelsio gigabit Ethernet support"
2629 depends on CHELSIO_T1
2631 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2632 are using only 10G cards say 'N' here.
2635 tristate "Chelsio Communications T3 10Gb Ethernet support"
2636 depends on PCI && INET
2640 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2643 For general information about Chelsio and our products, visit
2644 our website at <http://www.chelsio.com>.
2646 For customer support, please visit our customer support page at
2647 <http://www.chelsio.com/support.html>.
2649 Please send feedback to <linux-bugs@chelsio.com>.
2651 To compile this driver as a module, choose M here: the module
2652 will be called cxgb3.
2655 tristate "Chelsio Communications T4 Ethernet support"
2660 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
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 cxgb4.
2675 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2678 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2679 adapters with PCI-E SR-IOV Virtual Functions.
2681 For general information about Chelsio and our products, visit
2682 our website at <http://www.chelsio.com>.
2684 For customer support, please visit our customer support page at
2685 <http://www.chelsio.com/support.html>.
2687 Please send feedback to <linux-bugs@chelsio.com>.
2689 To compile this driver as a module choose M here; the module
2690 will be called cxgb4vf.
2693 tristate "eHEA Ethernet support"
2694 depends on IBMEBUS && INET && SPARSEMEM
2697 This driver supports the IBM pSeries eHEA ethernet adapter.
2699 To compile the driver as a module, choose M here. The module
2700 will be called ehea.
2703 tristate "Cisco VIC Ethernet NIC Support"
2704 depends on PCI && INET
2706 This enables the support for the Cisco VIC Ethernet card.
2709 tristate "Intel(R) 10GbE PCI Express adapters support"
2710 depends on PCI && INET
2713 This driver supports Intel(R) 10GbE PCI Express family of
2714 adapters. For more information on how to identify your adapter, go
2715 to the Adapter & Driver ID Guide at:
2717 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2719 For general information and support, go to the Intel support
2722 <http://support.intel.com>
2724 To compile this driver as a module, choose M here. The module
2725 will be called ixgbe.
2728 bool "Direct Cache Access (DCA) Support"
2730 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2732 Say Y here if you want to use Direct Cache Access (DCA) in the
2733 driver. DCA is a method for warming the CPU cache before data
2734 is used, with the intent of lessening the impact of cache misses.
2737 bool "Data Center Bridging (DCB) Support"
2739 depends on IXGBE && DCB
2741 Say Y here if you want to use Data Center Bridging (DCB) in the
2747 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2750 This driver supports Intel(R) 82599 virtual functions. For more
2751 information on how to identify your adapter, go to the Adapter &
2754 <http://support.intel.com/support/network/sb/CS-008441.htm>
2756 For general information and support, go to the Intel support
2759 <http://support.intel.com>
2761 More specific information on configuring the driver is in
2762 <file:Documentation/networking/ixgbevf.txt>.
2764 To compile this driver as a module, choose M here. The module
2765 will be called ixgbevf. MSI-X interrupt support is required
2766 for this driver to work correctly.
2769 tristate "Intel(R) PRO/10GbE support"
2772 This driver supports Intel(R) PRO/10GbE family of adapters for
2773 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2774 instead. For more information on how to identify your adapter, go
2775 to the Adapter & Driver ID Guide at:
2777 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2779 For general information and support, go to the Intel support
2782 <http://support.intel.com>
2784 More specific information on configuring the driver is in
2785 <file:Documentation/networking/ixgb.txt>.
2787 To compile this driver as a module, choose M here. The module
2788 will be called ixgb.
2791 tristate "Exar Xframe 10Gb Ethernet Adapter"
2794 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2796 More specific information on configuring the driver is in
2797 <file:Documentation/networking/s2io.txt>.
2799 To compile this driver as a module, choose M here. The module
2800 will be called s2io.
2803 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2804 depends on PCI && INET
2806 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2807 I/O Virtualized Server Adapter.
2809 More specific information on configuring the driver is in
2810 <file:Documentation/networking/vxge.txt>.
2812 To compile this driver as a module, choose M here. The module
2813 will be called vxge.
2815 config VXGE_DEBUG_TRACE_ALL
2816 bool "Enabling All Debug trace statments in driver"
2820 Say Y here if you want to enabling all the debug trace statements in
2821 the vxge driver. By default only few debug trace statements are
2825 tristate "Myricom Myri-10G Ethernet support"
2826 depends on PCI && INET
2831 This driver supports Myricom Myri-10G Dual Protocol interface in
2832 Ethernet mode. If the eeprom on your board is not recent enough,
2833 you will need a newer firmware image.
2834 You may get this image or more information, at:
2836 <http://www.myri.com/scs/download-Myri10GE.html>
2838 To compile this driver as a module, choose M here. The module
2839 will be called myri10ge.
2842 bool "Direct Cache Access (DCA) Support"
2844 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2846 Say Y here if you want to use Direct Cache Access (DCA) in the
2847 driver. DCA is a method for warming the CPU cache before data
2848 is used, with the intent of lessening the impact of cache misses.
2851 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2855 This enables the support for NetXen's Gigabit Ethernet card.
2858 tristate "Sun Neptune 10Gbit Ethernet support"
2862 This enables support for cards based upon Sun's
2866 tristate "PA Semi 1/10Gbit MAC"
2867 depends on PPC_PASEMI && PCI && INET
2871 This driver supports the on-chip 1/10Gbit Ethernet controller on
2872 PA Semi's PWRficient line of chips.
2875 tristate "Mellanox Technologies 10Gbit Ethernet support"
2876 depends on PCI && INET
2880 This driver supports Mellanox Technologies ConnectX Ethernet
2889 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2890 depends on MLX4_CORE
2893 This option causes debugging code to be compiled into the
2894 mlx4_core driver. The output can be turned on via the
2895 debug_level module parameter (which can also be set after
2896 the driver is loaded through sysfs).
2899 tristate "Tehuti Networks 10G Ethernet"
2902 Tehuti Networks 10G Ethernet NIC
2905 tristate "Broadcom NetXtremeII 10Gb support"
2912 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2913 To compile this driver as a module, choose M here: the module
2914 will be called bnx2x. This is recommended.
2917 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2921 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2925 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2928 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2930 To compile this driver as a module, choose M here: the module
2931 will be called qlge.
2934 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2937 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2939 To compile this driver as a module, choose M here: the module
2942 For general information and support, go to the Brocade support
2945 <http://support.brocade.com>
2947 source "drivers/net/sfc/Kconfig"
2949 source "drivers/net/benet/Kconfig"
2951 endif # NETDEV_10000
2953 source "drivers/net/tokenring/Kconfig"
2955 source "drivers/net/wireless/Kconfig"
2957 source "drivers/net/wimax/Kconfig"
2959 source "drivers/net/usb/Kconfig"
2961 source "drivers/net/pcmcia/Kconfig"
2963 source "drivers/net/wan/Kconfig"
2965 source "drivers/atm/Kconfig"
2967 source "drivers/ieee802154/Kconfig"
2969 source "drivers/s390/net/Kconfig"
2971 source "drivers/net/caif/Kconfig"
2974 tristate "Tilera GBE/XGBE network driver support"
2979 This is a standard Linux network device driver for the
2980 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2982 To compile this driver as a module, choose M here: the module
2983 will be called tile_net.
2985 config XEN_NETDEV_FRONTEND
2986 tristate "Xen network device frontend driver"
2988 select XEN_XENBUS_FRONTEND
2991 This driver provides support for Xen paravirtual network
2992 devices exported by a Xen network driver domain (often
2995 The corresponding Linux backend driver is enabled by the
2996 CONFIG_XEN_NETDEV_BACKEND option.
2998 If you are compiling a kernel for use as Xen guest, you
2999 should say Y here. To compile this driver as a module, chose
3000 M here: the module will be called xen-netfront.
3002 config XEN_NETDEV_BACKEND
3003 tristate "Xen backend network device"
3004 depends on XEN_BACKEND
3006 This driver allows the kernel to act as a Xen network driver
3007 domain which exports paravirtual network devices to other
3008 Xen domains. These devices can be accessed by any operating
3009 system that implements a compatible front end.
3011 The corresponding Linux frontend driver is enabled by the
3012 CONFIG_XEN_NETDEV_FRONTEND configuration option.
3014 The backend driver presents a standard network device
3015 endpoint for each paravirtual network device to the driver
3016 domain network stack. These can then be bridged or routed
3017 etc in order to provide full network connectivity.
3019 If you are compiling a kernel to run in a Xen network driver
3020 domain (often this is domain 0) you should say Y here. To
3021 compile this driver as a module, chose M here: the module
3022 will be called xen-netback.
3025 tristate "iSeries Virtual Ethernet driver support"
3026 depends on PPC_ISERIES
3029 tristate "RapidIO Ethernet over messaging driver support"
3032 config RIONET_TX_SIZE
3033 int "Number of outbound queue entries"
3037 config RIONET_RX_SIZE
3038 int "Number of inbound queue entries"
3043 tristate "FDDI driver support"
3044 depends on (PCI || EISA || TC)
3046 Fiber Distributed Data Interface is a high speed local area network
3047 design; essentially a replacement for high speed Ethernet. FDDI can
3048 run over copper or fiber. If you are connected to such a network and
3049 want a driver for the FDDI card in your computer, say Y here (and
3050 then also Y to the driver for your FDDI card, below). Most people
3054 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
3055 depends on FDDI && (PCI || EISA || TC)
3057 This is support for the DIGITAL series of TURBOchannel (DEFTA),
3058 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
3059 to a local FDDI network.
3061 To compile this driver as a module, choose M here: the module
3062 will be called defxx. If unsure, say N.
3066 prompt "Use MMIO instead of PIO" if PCI || EISA
3068 default n if PCI || EISA
3071 This instructs the driver to use EISA or PCI memory-mapped I/O
3072 (MMIO) as appropriate instead of programmed I/O ports (PIO).
3073 Enabling this gives an improvement in processing time in parts
3074 of the driver, but it may cause problems with EISA (DEFEA)
3075 adapters. TURBOchannel does not have the concept of I/O ports,
3076 so MMIO is always used for these (DEFTA) adapters.
3081 tristate "SysKonnect FDDI PCI support"
3082 depends on FDDI && PCI
3085 Say Y here if you have a SysKonnect FDDI PCI adapter.
3086 The following adapters are supported by this driver:
3087 - SK-5521 (SK-NET FDDI-UP)
3088 - SK-5522 (SK-NET FDDI-UP DAS)
3089 - SK-5541 (SK-NET FDDI-FP)
3090 - SK-5543 (SK-NET FDDI-LP)
3091 - SK-5544 (SK-NET FDDI-LP DAS)
3092 - SK-5821 (SK-NET FDDI-UP64)
3093 - SK-5822 (SK-NET FDDI-UP64 DAS)
3094 - SK-5841 (SK-NET FDDI-FP64)
3095 - SK-5843 (SK-NET FDDI-LP64)
3096 - SK-5844 (SK-NET FDDI-LP64 DAS)
3097 - Netelligent 100 FDDI DAS Fibre SC
3098 - Netelligent 100 FDDI SAS Fibre SC
3099 - Netelligent 100 FDDI DAS UTP
3100 - Netelligent 100 FDDI SAS UTP
3101 - Netelligent 100 FDDI SAS Fibre MIC
3103 Read <file:Documentation/networking/skfp.txt> for information about
3106 Questions concerning this driver can be addressed to:
3107 <linux@syskonnect.de>
3109 To compile this driver as a module, choose M here: the module
3110 will be called skfp. This is recommended.
3113 bool "HIPPI driver support (EXPERIMENTAL)"
3114 depends on EXPERIMENTAL && INET && PCI
3116 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3117 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3118 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3119 single-mode). HIPPI networks are commonly used for clusters and to
3120 connect to super computers. If you are connected to a HIPPI network
3121 and have a HIPPI network card in your computer that you want to use
3122 under Linux, say Y here (you must also remember to enable the driver
3123 for your HIPPI card below). Most people will say N here.
3126 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3127 depends on HIPPI && PCI
3129 Say Y here if this is your PCI HIPPI network card.
3131 To compile this driver as a module, choose M here: the module
3132 will be called rrunner. If unsure, say N.
3134 config ROADRUNNER_LARGE_RINGS
3135 bool "Use large TX/RX rings (EXPERIMENTAL)"
3136 depends on ROADRUNNER
3138 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3139 of additional memory to allow for fastest operation, both for
3140 transmitting and receiving. This memory cannot be used by any other
3141 kernel code or by user space programs. Say Y here only if you have
3145 tristate "PLIP (parallel port) support"
3148 PLIP (Parallel Line Internet Protocol) is used to create a
3149 reasonably fast mini network consisting of two (or, rarely, more)
3150 local machines. A PLIP link from a Linux box is a popular means to
3151 install a Linux distribution on a machine which doesn't have a
3152 CD-ROM drive (a minimal system has to be transferred with floppies
3153 first). The kernels on both machines need to have this PLIP option
3154 enabled for this to work.
3156 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3157 ports (the connectors at the computers with 25 holes) are connected
3158 with "null printer" or "Turbo Laplink" cables which can transmit 4
3159 bits at a time (mode 0) or with special PLIP cables, to be used on
3160 bidirectional parallel ports only, which can transmit 8 bits at a
3161 time (mode 1); you can find the wiring of these cables in
3162 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3163 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3164 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3165 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3166 and winsock or NCSA's telnet.
3168 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3169 as the NET-3-HOWTO, both available from
3170 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3171 protocol has been changed and this PLIP driver won't work together
3172 with the PLIP support in Linux versions 1.0.x. This option enlarges
3173 your kernel by about 8 KB.
3175 To compile this driver as a module, choose M here. The module
3176 will be called plip. If unsure, say Y or M, in case you buy
3180 tristate "PPP (point-to-point protocol) support"
3183 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3184 the same purpose: sending Internet traffic over telephone (and other
3185 serial) lines. Ask your access provider if they support it, because
3186 otherwise you can't use it; most Internet access providers these
3187 days support PPP rather than SLIP.
3189 To use PPP, you need an additional program called pppd as described
3190 in the PPP-HOWTO, available at
3191 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3192 the version of pppd recommended in <file:Documentation/Changes>.
3193 The PPP option enlarges your kernel by about 16 KB.
3195 There are actually two versions of PPP: the traditional PPP for
3196 asynchronous lines, such as regular analog phone lines, and
3197 synchronous PPP which can be used over digital ISDN lines for
3198 example. If you want to use PPP over phone lines or other
3199 asynchronous serial lines, you need to say Y (or M) here and also to
3200 the next option, "PPP support for async serial ports". For PPP over
3201 synchronous lines, you should say Y (or M) here and to "Support
3202 synchronous PPP", below.
3204 If you said Y to "Version information on all symbols" above, then
3205 you cannot compile the PPP driver into the kernel; you can then only
3206 compile it as a module. To compile this driver as a module, choose M
3207 here. The module will be called ppp_generic.
3209 config PPP_MULTILINK
3210 bool "PPP multilink support (EXPERIMENTAL)"
3211 depends on PPP && EXPERIMENTAL
3213 PPP multilink is a protocol (defined in RFC 1990) which allows you
3214 to combine several (logical or physical) lines into one logical PPP
3215 connection, so that you can utilize your full bandwidth.
3217 This has to be supported at the other end as well and you need a
3218 version of the pppd daemon which understands the multilink protocol.
3223 bool "PPP filtering"
3226 Say Y here if you want to be able to filter the packets passing over
3227 PPP interfaces. This allows you to control which packets count as
3228 activity (i.e. which packets will reset the idle timer or bring up
3229 a demand-dialed link) and which packets are to be dropped entirely.
3230 You need to say Y here if you wish to use the pass-filter and
3231 active-filter options to pppd.
3236 tristate "PPP support for async serial ports"
3240 Say Y (or M) here if you want to be able to use PPP over standard
3241 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3242 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3245 To compile this driver as a module, choose M here.
3250 tristate "PPP support for sync tty ports"
3253 Say Y (or M) here if you want to be able to use PPP over synchronous
3254 (HDLC) tty devices, such as the SyncLink adapter. These devices
3255 are often used for high-speed leased lines like T1/E1.
3257 To compile this driver as a module, choose M here.
3260 tristate "PPP Deflate compression"
3265 Support for the Deflate compression method for PPP, which uses the
3266 Deflate algorithm (the same algorithm that gzip uses) to compress
3267 each PPP packet before it is sent over the wire. The machine at the
3268 other end of the PPP link (usually your ISP) has to support the
3269 Deflate compression method as well for this to be useful. Even if
3270 they don't support it, it is safe to say Y here.
3272 To compile this driver as a module, choose M here.
3275 tristate "PPP BSD-Compress compression"
3278 Support for the BSD-Compress compression method for PPP, which uses
3279 the LZW compression method to compress each PPP packet before it is
3280 sent over the wire. The machine at the other end of the PPP link
3281 (usually your ISP) has to support the BSD-Compress compression
3282 method as well for this to be useful. Even if they don't support it,
3283 it is safe to say Y here.
3285 The PPP Deflate compression method ("PPP Deflate compression",
3286 above) is preferable to BSD-Compress, because it compresses better
3289 Note that the BSD compression code will always be compiled as a
3290 module; it is called bsd_comp and will show up in the directory
3291 modules once you have said "make modules". If unsure, say N.
3294 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3295 depends on PPP && EXPERIMENTAL
3301 Support for the MPPE Encryption protocol, as employed by the
3302 Microsoft Point-to-Point Tunneling Protocol.
3304 See http://pptpclient.sourceforge.net/ for information on
3305 configuring PPTP clients and servers to utilize this method.
3308 tristate "PPP over Ethernet (EXPERIMENTAL)"
3309 depends on EXPERIMENTAL && PPP
3311 Support for PPP over Ethernet.
3313 This driver requires the latest version of pppd from the CVS
3314 repository at cvs.samba.org. Alternatively, see the
3315 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3316 which contains instruction on how to use this driver (under
3317 the heading "Kernel mode PPPoE").
3320 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3321 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3323 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3325 This driver requires pppd plugin to work in client mode or
3326 modified pptpd (poptop) to work in server mode.
3327 See http://accel-pptp.sourceforge.net/ for information how to
3328 utilize this module.
3331 tristate "PPP over ATM"
3332 depends on ATM && PPP
3334 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3335 This implementation does not yet comply with section 8 of RFC2364,
3336 which can lead to bad results if the ATM peer loses state and
3337 changes its encapsulation unilaterally.
3340 tristate "PPP over L2TP (EXPERIMENTAL)"
3341 depends on EXPERIMENTAL && L2TP && PPP
3343 Support for PPP-over-L2TP socket family. L2TP is a protocol
3344 used by ISPs and enterprises to tunnel PPP traffic over UDP
3345 tunnels. L2TP is replacing PPTP for VPN uses.
3348 tristate "PPP on L2TP Access Concentrator"
3349 depends on PPP && INET
3351 L2TP (RFC 2661) is a tunneling protocol widely used in virtual private
3352 networks. This driver handles L2TP data packets between a UDP socket
3353 and a PPP channel, but only permits one session per socket. Thus it is
3354 fairly simple and suited for clients.
3357 tristate "PPP on PPTP Network Server"
3358 depends on PPP && INET
3360 PPTP (RFC 2637) is a tunneling protocol widely used in virtual private
3361 networks. This driver handles PPTP data packets between a RAW socket
3362 and a PPP channel. It is fairly simple and easy to use.
3365 tristate "SLIP (serial line) support"
3367 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3368 connect to your Internet service provider or to connect to some
3369 other local Unix box or if you want to configure your Linux box as a
3370 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3371 Internet Protocol) is a protocol used to send Internet traffic over
3372 serial connections such as telephone lines or null modem cables;
3373 nowadays, the protocol PPP is more commonly used for this same
3376 Normally, your access provider has to support SLIP in order for you
3377 to be able to use it, but there is now a SLIP emulator called SLiRP
3378 around (available from
3379 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3380 allows you to use SLIP over a regular dial up shell connection. If
3381 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3382 NET-3-HOWTO, available from
3383 <http://www.tldp.org/docs.html#howto>, explains how to
3384 configure SLIP. Note that you don't need this option if you just
3385 want to run term (term is a program which gives you almost full
3386 Internet connectivity if you have a regular dial up shell account on
3387 some Internet connected Unix computer. Read
3388 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3389 support will enlarge your kernel by about 4 KB. If unsure, say N.
3391 To compile this driver as a module, choose M here. The module
3392 will be called slip.
3394 config SLIP_COMPRESSED
3395 bool "CSLIP compressed headers"
3399 This protocol is faster than SLIP because it uses compression on the
3400 TCP/IP headers (not on the data itself), but it has to be supported
3401 on both ends. Ask your access provider if you are not sure and
3402 answer Y, just in case. You will still be able to use plain SLIP. If
3403 you plan to use SLiRP, the SLIP emulator (available from
3404 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3405 allows you to use SLIP over a regular dial up shell connection, you
3406 definitely want to say Y here. The NET-3-HOWTO, available from
3407 <http://www.tldp.org/docs.html#howto>, explains how to configure
3408 CSLIP. This won't enlarge your kernel.
3413 This option enables Van Jacobsen serial line header compression
3417 bool "Keepalive and linefill"
3420 Adds additional capabilities to the SLIP driver to support the
3421 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3424 config SLIP_MODE_SLIP6
3425 bool "Six bit SLIP encapsulation"
3428 Just occasionally you may need to run IP over hostile serial
3429 networks that don't pass all control characters or are only seven
3430 bit. Saying Y here adds an extra mode you can use with SLIP:
3431 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3432 the serial device. Naturally, this has to be supported at the other
3433 end of the link as well. It's good enough, for example, to run IP
3434 over the async ports of a Camtec JNT Pad. If unsure, say N.
3437 bool "Fibre Channel driver support"
3438 depends on SCSI && PCI
3440 Fibre Channel is a high speed serial protocol mainly used to connect
3441 large storage devices to the computer; it is compatible with and
3442 intended to replace SCSI.
3444 If you intend to use Fibre Channel, you need to have a Fibre channel
3445 adaptor card in your computer; say Y here and to the driver for your
3446 adaptor below. You also should have said Y to "SCSI support" and
3447 "SCSI generic support".
3450 tristate "Network console logging support"
3452 If you want to log kernel messages over the network, enable this.
3453 See <file:Documentation/networking/netconsole.txt> for details.
3455 config NETCONSOLE_DYNAMIC
3456 bool "Dynamic reconfiguration of logging targets"
3457 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
3458 !(NETCONSOLE=y && CONFIGFS_FS=m)
3460 This option enables the ability to dynamically reconfigure target
3461 parameters (interface, IP addresses, port numbers, MAC addresses)
3462 at runtime through a userspace interface exported using configfs.
3463 See <file:Documentation/networking/netconsole.txt> for details.
3469 bool "Netpoll traffic trapping"
3473 config NET_POLL_CONTROLLER
3477 tristate "Virtio network driver (EXPERIMENTAL)"
3478 depends on EXPERIMENTAL && VIRTIO
3480 This is the virtual network driver for virtio. It can be used with
3481 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3484 tristate "VMware VMXNET3 ethernet driver"
3485 depends on PCI && INET
3487 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3488 To compile this driver as a module, choose M here: the
3489 module will be called vmxnet3.