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 "MACE (Power Mac ethernet) support"
256 depends on PPC_PMAC && PPC32
259 Power Macintoshes and clones with Ethernet built-in on the
260 motherboard will usually use a MACE (Medium Access Control for
261 Ethernet) interface. Say Y to include support for the MACE chip.
263 To compile this driver as a module, choose M here: the module
266 config MACE_AAUI_PORT
267 bool "Use AAUI port instead of TP by default"
270 Some Apple machines (notably the Apple Network Server) which use the
271 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
272 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
273 Y here if you have such a machine. If unsure, say N.
274 The driver will default to AAUI on ANS anyway, and if you use it as
275 a module, you can provide the port_aaui=0|1 to force the driver.
278 tristate "BMAC (G3 ethernet) support"
279 depends on PPC_PMAC && PPC32
282 Say Y for support of BMAC Ethernet interfaces. These are used on G3
285 To compile this driver as a module, choose M here: the module
289 tristate "Ariadne support"
292 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
295 To compile this driver as a module, choose M here: the module
296 will be called ariadne.
299 tristate "A2065 support"
303 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
306 To compile this driver as a module, choose M here: the module
307 will be called a2065.
310 tristate "Hydra support"
314 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
316 To compile this driver as a module, choose M here: the module
317 will be called hydra.
320 tristate "Zorro NS8390-based Ethernet support"
324 This driver is for Zorro Ethernet cards using an NS8390-compatible
325 chipset, like the Village Tronic Ariadne II and the Individual
326 Computers X-Surf Ethernet cards. If you have such a card, say Y.
329 To compile this driver as a module, choose M here: the module
330 will be called zorro8390.
333 tristate "PCMCIA NE2000 support"
334 depends on AMIGA_PCMCIA
337 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
340 To compile this driver as a module, choose M here: the module
344 bool "Macintosh NS 8390 based ethernet cards"
348 If you want to include a driver to support Nubus or LC-PDS
349 Ethernet cards using an NS8390 chipset or its equivalent, say Y
350 and read the Ethernet-HOWTO, available from
351 <http://www.tldp.org/docs.html#howto>.
354 tristate "Macintosh CS89x0 based ethernet cards"
357 Support for CS89x0 chipset based Ethernet cards. If you have a
358 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
359 read the Ethernet-HOWTO, available from
360 <http://www.tldp.org/docs.html#howto>.
362 To compile this driver as a module, choose M here. This module will
366 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
369 Support for NatSemi SONIC based Ethernet devices. This includes
370 the onboard Ethernet in many Quadras as well as some LC-PDS,
371 a few Nubus and all known Comm Slot Ethernet cards. If you have
372 one of these say Y and read the Ethernet-HOWTO, available from
373 <http://www.tldp.org/docs.html#howto>.
375 To compile this driver as a module, choose M here. This module will
379 bool "Macintosh (AV) onboard MACE ethernet"
383 Support for the onboard AMD 79C940 MACE Ethernet controller used in
384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
385 say Y and read the Ethernet-HOWTO, available from
386 <http://www.tldp.org/docs.html#howto>.
389 tristate "MVME147 (Lance) Ethernet support"
393 Support for the on-board Ethernet interface on the Motorola MVME147
394 single-board computer. Say Y here to include the
395 driver for this chip in your kernel.
396 To compile this driver as a module, choose M here.
399 tristate "MVME16x Ethernet support"
402 This is the driver for the Ethernet interface on the Motorola
403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
404 driver for this chip in your kernel.
405 To compile this driver as a module, choose M here.
408 tristate "BVME6000 Ethernet support"
411 This is the driver for the Ethernet interface on BVME4000 and
412 BVME6000 VME boards. Say Y here to include the driver for this chip
414 To compile this driver as a module, choose M here.
417 tristate "Atari Lance support"
420 Say Y to include support for several Atari Ethernet adapters based
421 on the AMD Lance chipset: RieblCard (with or without battery), or
422 PAMCard VME (also the version by Rhotron, with different addresses).
425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
435 If you're not building a kernel for a Sun 3, say N.
438 bool "Sun3 on-board Intel 82586 support"
441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional
447 bool "HP on-board LANCE support"
451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here.
455 tristate "Lasi ethernet"
458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM
465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines.
469 tristate "Korina (IDT RC32434) Ethernet support"
470 depends on NET_ETHERNET && MIKROTIK_RB532
472 If you have a Mikrotik RouterBoard 500 or IDT RC32434
473 based system say Y. Otherwise say N.
475 config MIPS_JAZZ_SONIC
476 tristate "MIPS JAZZ onboard SONIC Ethernet support"
479 This is the driver for the onboard card of MIPS Magnum 4000,
480 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
482 config XTENSA_XT2000_SONIC
483 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
484 depends on XTENSA_PLATFORM_XT2000
486 This is the driver for the onboard card of the Xtensa XT2000 board.
488 config MIPS_AU1X00_ENET
489 tristate "MIPS AU1000 Ethernet support"
490 depends on MIPS_ALCHEMY
494 If you have an Alchemy Semi AU1X00 based system
495 say Y. Otherwise, say N.
498 bool "SGI IOC3 Ethernet"
499 depends on PCI && SGI_IP27
503 If you have a network (Ethernet) card of this type, say Y and read
504 the Ethernet-HOWTO, available from
505 <http://www.tldp.org/docs.html#howto>.
508 tristate "MIPS simulator Network device"
511 The MIPSNET device is a simple Ethernet network device which is
512 emulated by the MIPS Simulator.
513 If you are not using a MIPSsim or are unsure, say N.
515 config SGI_O2MACE_ETH
516 tristate "SGI O2 MACE Fast Ethernet support"
517 depends on SGI_IP32=y
520 tristate "National DP83902AV support"
524 Support for cards based on the National Semiconductor DP83902AV
525 ST-NIC Serial Network Interface Controller for Twisted Pair. This
526 is a 10Mbit/sec Ethernet controller. Product overview and specs at
527 <http://www.national.com/pf/DP/DP83902A.html>.
532 tristate "Renesas SuperH Ethernet support"
533 depends on SUPERH && \
534 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
535 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
536 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
542 Renesas SuperH Ethernet device driver.
543 This driver supporting CPUs are:
544 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
547 tristate "Sun LANCE support"
551 This driver supports the "le" interface present on all 32-bit Sparc
552 systems, on some older Ultra systems and as an Sbus option. These
553 cards are based on the AMD Lance chipset, which is better known
554 via the NE2100 cards.
556 To compile this driver as a module, choose M here: the module
557 will be called sunlance.
560 tristate "Sun Happy Meal 10/100baseT support"
561 depends on SBUS || PCI
564 This driver supports the "hme" interface present on most Ultra
565 systems and as an option on older Sbus systems. This driver supports
566 both PCI and Sbus devices. This driver also supports the "qfe" quad
567 100baseT device available in both PCI and Sbus configurations.
569 To compile this driver as a module, choose M here: the module
570 will be called sunhme.
573 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
574 depends on SBUS && EXPERIMENTAL
577 This driver supports the "be" interface available as an Sbus option.
578 This is Sun's older 100baseT Ethernet device.
580 To compile this driver as a module, choose M here: the module
581 will be called sunbmac.
584 tristate "Sun QuadEthernet support"
588 This driver supports the "qe" 10baseT Ethernet device, available as
589 an Sbus option. Note that this is not the same as Quad FastEthernet
590 "qfe" which is supported by the Happy Meal driver instead.
592 To compile this driver as a module, choose M here: the module
593 will be called sunqe.
596 tristate "Sun GEM support"
600 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
601 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
604 tristate "Sun Cassini support"
608 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
609 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
612 tristate "Sun Virtual Network support"
615 Support for virtual network devices under Sun Logical Domains.
617 config NET_VENDOR_3COM
619 depends on ISA || EISA || MCA || PCI
621 If you have a network (Ethernet) card belonging to this class, say Y
622 and read the Ethernet-HOWTO, available from
623 <http://www.tldp.org/docs.html#howto>.
625 Note that the answer to this question doesn't directly affect the
626 kernel: saying N will just cause the configurator to skip all
627 the questions about 3COM cards. If you say Y, you will be asked for
628 your specific card in the following questions.
631 tristate "3c501 \"EtherLink\" support"
632 depends on NET_VENDOR_3COM && ISA
634 If you have a network (Ethernet) card of this type, say Y and read
635 the Ethernet-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
637 new card, since the 3c501 is slow, broken, and obsolete: you will
638 have problems. Some people suggest to ping ("man ping") a nearby
639 machine every minute ("man cron") when using this card.
641 To compile this driver as a module, choose M here. The module
642 will be called 3c501.
645 tristate "3c503 \"EtherLink II\" support"
646 depends on NET_VENDOR_3COM && ISA
649 If you have a network (Ethernet) card of this type, say Y and read
650 the Ethernet-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>.
653 To compile this driver as a module, choose M here. The module
654 will be called 3c503.
657 tristate "3c505 \"EtherLink Plus\" support"
658 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
660 Information about this network (Ethernet) card can be found in
661 <file:Documentation/networking/3c505.txt>. If you have a card of
662 this type, say Y and read the Ethernet-HOWTO, available from
663 <http://www.tldp.org/docs.html#howto>.
665 To compile this driver as a module, choose M here. The module
666 will be called 3c505.
669 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
670 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
672 If you have a network (Ethernet) card of this type, say Y and read
673 the Ethernet-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>.
676 To compile this driver as a module, choose M here. The module
677 will be called 3c507.
680 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
681 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
683 If you have a network (Ethernet) card belonging to the 3Com
684 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
685 from <http://www.tldp.org/docs.html#howto>.
687 If your card is not working you may need to use the DOS
688 setup disk to disable Plug & Play mode, and to select the default
691 To compile this driver as a module, choose M here. The module
692 will be called 3c509.
695 tristate "3c515 ISA \"Fast EtherLink\""
696 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
698 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
699 network card, say Y and read the Ethernet-HOWTO, available from
700 <http://www.tldp.org/docs.html#howto>.
702 To compile this driver as a module, choose M here. The module
703 will be called 3c515.
706 tristate "3c523 \"EtherLink/MC\" support"
707 depends on NET_VENDOR_3COM && MCA_LEGACY
709 If you have a network (Ethernet) card of this type, say Y and read
710 the Ethernet-HOWTO, available from
711 <http://www.tldp.org/docs.html#howto>.
713 To compile this driver as a module, choose M here. The module
714 will be called 3c523.
717 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
718 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
720 If you have a network (Ethernet) card of this type, say Y and read
721 the Ethernet-HOWTO, available from
722 <http://www.tldp.org/docs.html#howto>.
724 To compile this driver as a module, choose M here. The module
725 will be called 3c527.
728 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
729 depends on NET_VENDOR_3COM && (PCI || EISA)
732 This option enables driver support for a large number of 10Mbps and
733 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
735 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
736 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
737 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
738 "Tornado" (3c905) PCI
739 "Hurricane" (3c555/3cSOHO) PCI
741 If you have such a card, say Y and read the Ethernet-HOWTO,
742 available from <http://www.tldp.org/docs.html#howto>. More
743 specific information is in
744 <file:Documentation/networking/vortex.txt> and in the comments at
745 the beginning of <file:drivers/net/3c59x.c>.
747 To compile this support as a module, choose M here.
750 tristate "3cr990 series \"Typhoon\" support"
751 depends on NET_VENDOR_3COM && PCI
754 This option enables driver support for the 3cr990 series of cards:
756 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
757 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
758 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
760 If you have a network (Ethernet) card of this type, say Y and read
761 the Ethernet-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>.
764 To compile this driver as a module, choose M here. The module
765 will be called typhoon.
768 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
769 depends on ISA && ISA_DMA_API
771 If you have a network (Ethernet) card of this type, say Y and read
772 the Ethernet-HOWTO, available from
773 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
776 To compile this driver as a module, choose M here: the module
777 will be called lance. This is recommended.
779 config NET_VENDOR_SMC
780 bool "Western Digital/SMC cards"
781 depends on ISA || MCA || EISA || MAC
783 If you have a network (Ethernet) card belonging to this class, say Y
784 and read the Ethernet-HOWTO, available from
785 <http://www.tldp.org/docs.html#howto>.
787 Note that the answer to this question doesn't directly affect the
788 kernel: saying N will just cause the configurator to skip all
789 the questions about Western Digital cards. If you say Y, you will be
790 asked for your specific card in the following questions.
793 tristate "WD80*3 support"
794 depends on NET_VENDOR_SMC && ISA
799 If you have a network (Ethernet) card of this type, say Y and read
800 the Ethernet-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>.
803 To compile this driver as a module, choose M here. The module
807 tristate "SMC Ultra MCA support"
808 depends on NET_VENDOR_SMC && MCA
811 If you have a network (Ethernet) card of this type and are running
812 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
813 available from <http://www.tldp.org/docs.html#howto>.
815 To compile this driver as a module, choose M here. The module
816 will be called smc-mca.
819 tristate "SMC Ultra support"
820 depends on NET_VENDOR_SMC && ISA
823 If you have a network (Ethernet) card of this type, say Y and read
824 the Ethernet-HOWTO, available from
825 <http://www.tldp.org/docs.html#howto>.
827 Important: There have been many reports that, with some motherboards
828 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
829 such as some BusLogic models) causes corruption problems with many
830 operating systems. The Linux smc-ultra driver has a work-around for
831 this but keep it in mind if you have such a SCSI card and have
834 To compile this driver as a module, choose M here. The module
835 will be called smc-ultra.
838 tristate "SMC Ultra32 EISA support"
839 depends on NET_VENDOR_SMC && EISA
842 If you have a network (Ethernet) card of this type, say Y and read
843 the Ethernet-HOWTO, available from
844 <http://www.tldp.org/docs.html#howto>.
846 To compile this driver as a module, choose M here. The module
847 will be called smc-ultra32.
850 tristate "Blackfin on-chip MAC support"
851 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
855 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
857 This is the driver for Blackfin on-chip mac device. Say Y if you want it
858 compiled into the kernel. This driver is also available as a module
859 ( = code which can be inserted in and removed from the running kernel
860 whenever you want). The module will be called bfin_mac.
862 config BFIN_MAC_USE_L1
863 bool "Use L1 memory for rx/tx packets"
864 depends on BFIN_MAC && (BF527 || BF537)
867 To get maximum network performance, you should use L1 memory as rx/tx buffers.
868 Say N here if you want to reserve L1 memory for other uses.
870 config BFIN_TX_DESC_NUM
871 int "Number of transmit buffer packets"
873 range 6 10 if BFIN_MAC_USE_L1
877 Set the number of buffer packets used in driver.
879 config BFIN_RX_DESC_NUM
880 int "Number of receive buffer packets"
882 range 20 100 if BFIN_MAC_USE_L1
886 Set the number of buffer packets used in driver.
888 config BFIN_MAC_USE_HWSTAMP
889 bool "Use IEEE 1588 hwstamp"
890 depends on BFIN_MAC && BF518
893 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
896 tristate "SMC 9194 support"
897 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
900 This is support for the SMC9xxx based Ethernet cards. Choose this
901 option if you have a DELL laptop with the docking station, or
902 another SMC9192/9194 based chipset. Say Y if you want it compiled
903 into the kernel, and read the file
904 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
905 available from <http://www.tldp.org/docs.html#howto>.
907 To compile this driver as a module, choose M here. The module
908 will be called smc9194.
911 tristate "SMC 91C9x/91C1xxx support"
914 depends on ARM || M32R || SUPERH || \
915 MIPS || BLACKFIN || MN10300 || COLDFIRE
917 This is a driver for SMC's 91x series of Ethernet chipsets,
918 including the SMC91C94 and the SMC91C111. Say Y if you want it
919 compiled into the kernel, and read the file
920 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
921 available from <http://www.tldp.org/docs.html#howto>.
923 This driver is also available as a module ( = code which can be
924 inserted in and removed from the running kernel whenever you want).
925 The module will be called smc91x. If you want to compile it as a
926 module, say M here and read <file:Documentation/kbuild/modules.txt>.
929 tristate "Marvell pxa168 ethernet support"
930 depends on CPU_PXA168
933 This driver supports the pxa168 Ethernet ports.
935 To compile this driver as a module, choose M here. The module
936 will be called pxa168_eth.
939 tristate "NetX Ethernet support"
943 This is support for the Hilscher netX builtin Ethernet ports
945 To compile this driver as a module, choose M here. The module
946 will be called netx-eth.
948 config TI_DAVINCI_EMAC
949 tristate "TI DaVinci EMAC Support"
950 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
951 select TI_DAVINCI_MDIO
952 select TI_DAVINCI_CPDMA
955 This driver supports TI's DaVinci Ethernet .
957 To compile this driver as a module, choose M here: the module
958 will be called davinci_emac_driver. This is recommended.
960 config TI_DAVINCI_MDIO
961 tristate "TI DaVinci MDIO Support"
962 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
965 This driver supports TI's DaVinci MDIO module.
967 To compile this driver as a module, choose M here: the module
968 will be called davinci_mdio. This is recommended.
970 config TI_DAVINCI_CPDMA
971 tristate "TI DaVinci CPDMA Support"
972 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
974 This driver supports TI's DaVinci CPDMA dma engine.
976 To compile this driver as a module, choose M here: the module
977 will be called davinci_cpdma. This is recommended.
980 tristate "DM9000 support"
981 depends on ARM || BLACKFIN || MIPS
985 Support for DM9000 chipset.
987 To compile this driver as a module, choose M here. The module
988 will be called dm9000.
990 config DM9000_DEBUGLEVEL
991 int "DM9000 maximum debug level"
995 The maximum level of debugging code compiled into the DM9000
998 config DM9000_FORCE_SIMPLE_PHY_POLL
999 bool "Force simple NSR based PHY polling"
1002 This configuration forces the DM9000 to use the NSR's LinkStatus
1003 bit to determine if the link is up or down instead of the more
1004 costly MII PHY reads. Note, this will not work if the chip is
1005 operating with an external PHY.
1008 tristate "ENC28J60 support"
1009 depends on EXPERIMENTAL && SPI && NET_ETHERNET
1012 Support for the Microchip EN28J60 ethernet chip.
1014 To compile this driver as a module, choose M here. The module will be
1017 config ENC28J60_WRITEVERIFY
1018 bool "Enable write verify"
1021 Enable the verify after the buffer write useful for debugging purpose.
1025 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
1026 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1032 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1035 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1040 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1043 tristate "SMSC LAN911[5678] support"
1046 depends on ARM || SUPERH || MN10300
1048 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1049 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1050 Say Y if you want it compiled into the kernel,
1051 and read the Ethernet-HOWTO, available from
1052 <http://www.tldp.org/docs.html#howto>.
1054 This driver is also available as a module. The module will be
1055 called smc911x. If you want to compile it as a module, say M
1056 here and read <file:Documentation/kbuild/modules.txt>
1059 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1060 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
1065 Say Y here if you want support for SMSC LAN911x and LAN921x families
1066 of ethernet controllers.
1068 To compile this driver as a module, choose M here and read
1069 <file:Documentation/networking/net-modules.txt>. The module
1070 will be called smsc911x.
1072 config SMSC911X_ARCH_HOOKS
1076 If the arch enables this, it allows the arch to implement various
1077 hooks for more comprehensive interrupt control and also to override
1078 the source of the MAC address.
1080 config NET_VENDOR_RACAL
1081 bool "Racal-Interlan (Micom) NI cards"
1084 If you have a network (Ethernet) card belonging to this class, such
1085 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1086 available from <http://www.tldp.org/docs.html#howto>.
1088 Note that the answer to this question doesn't directly affect the
1089 kernel: saying N will just cause the configurator to skip all
1090 the questions about NI cards. If you say Y, you will be asked for
1091 your specific card in the following questions.
1094 tristate "NI5010 support (EXPERIMENTAL)"
1095 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1097 If you have a network (Ethernet) card of this type, say Y and read
1098 the Ethernet-HOWTO, available from
1099 <http://www.tldp.org/docs.html#howto>. Note that this is still
1102 To compile this driver as a module, choose M here. The module
1103 will be called ni5010.
1106 tristate "NI5210 support"
1107 depends on NET_VENDOR_RACAL && ISA
1109 If you have a network (Ethernet) card of this type, say Y and read
1110 the Ethernet-HOWTO, available from
1111 <http://www.tldp.org/docs.html#howto>.
1113 To compile this driver as a module, choose M here. The module
1114 will be called ni52.
1117 tristate "NI6510 support"
1118 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1120 If you have a network (Ethernet) card of this type, say Y and read
1121 the Ethernet-HOWTO, available from
1122 <http://www.tldp.org/docs.html#howto>.
1124 To compile this driver as a module, choose M here. The module
1125 will be called ni65.
1128 tristate "Dave ethernet support (DNET)"
1129 depends on NET_ETHERNET && HAS_IOMEM
1132 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1133 Say Y to include support for the DNET chip.
1135 To compile this driver as a module, choose M here: the module
1136 will be called dnet.
1138 source "drivers/net/tulip/Kconfig"
1141 tristate "AT1700/1720 support (EXPERIMENTAL)"
1142 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1145 If you have a network (Ethernet) card of this type, say Y and read
1146 the Ethernet-HOWTO, available from
1147 <http://www.tldp.org/docs.html#howto>.
1149 To compile this driver as a module, choose M here. The module
1150 will be called at1700.
1153 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1154 depends on ISA || EISA || MCA
1157 If you have a network (Ethernet) card of this type, say Y and read
1158 the Ethernet-HOWTO, available from
1159 <http://www.tldp.org/docs.html#howto> as well as
1160 <file:drivers/net/depca.c>.
1162 To compile this driver as a module, choose M here. The module
1163 will be called depca.
1166 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1167 depends on ISA || EISA || PCI
1169 If you have a network (Ethernet) card of this type, say Y and read
1170 the Ethernet-HOWTO, available from
1171 <http://www.tldp.org/docs.html#howto>.
1173 To compile this driver as a module, choose M here. The module
1174 will be called hp100.
1177 bool "Other ISA cards"
1180 If your network (Ethernet) card hasn't been mentioned yet and its
1181 bus system (that's the way the cards talks to the other components
1182 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1183 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1184 available from <http://www.tldp.org/docs.html#howto>.
1188 Note that the answer to this question doesn't directly affect the
1189 kernel: saying N will just cause the configurator to skip all
1190 the remaining ISA network card questions. If you say Y, you will be
1191 asked for your specific card in the following questions.
1194 tristate "Cabletron E21xx support"
1198 If you have a network (Ethernet) card of this type, say Y and read
1199 the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here. The module
1203 will be called e2100.
1206 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1210 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1211 cards. If this is for you, say Y and read
1212 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1213 well as the Ethernet-HOWTO, available from
1214 <http://www.tldp.org/docs.html#howto>.
1216 To compile this driver as a module, choose M here. The module
1217 will be called ewrk3.
1220 tristate "EtherExpress 16 support"
1223 If you have an EtherExpress16 network (Ethernet) card, say Y and
1224 read the Ethernet-HOWTO, available from
1225 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1226 EtherExpress16 card used to be regarded as a very poor choice
1227 because the driver was very unreliable. We now have a new driver
1228 that should do better.
1230 To compile this driver as a module, choose M here. The module
1231 will be called eexpress.
1234 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1237 If you have a network (Ethernet) card of this type, say Y. This
1238 driver supports Intel i82595{FX,TX} based boards. Note however
1239 that the EtherExpress PRO/100 Ethernet card has its own separate
1240 driver. Please read the Ethernet-HOWTO, available from
1241 <http://www.tldp.org/docs.html#howto>.
1243 To compile this driver as a module, choose M here. The module
1244 will be called eepro.
1247 tristate "HP PCLAN+ (27247B and 27252A) support"
1249 # broken build with config-Mon_Jul_21_20_21_08_CEST_2008.bad
1253 If you have a network (Ethernet) card of this type, say Y and read
1254 the Ethernet-HOWTO, available from
1255 <http://www.tldp.org/docs.html#howto>.
1257 To compile this driver as a module, choose M here. The module
1258 will be called hp-plus.
1261 tristate "HP PCLAN (27245 and other 27xxx series) support"
1265 If you have a network (Ethernet) card of this type, say Y and read
1266 the Ethernet-HOWTO, available from
1267 <http://www.tldp.org/docs.html#howto>.
1269 To compile this driver as a module, choose M here. The module
1273 tristate "LP486E on board Ethernet"
1276 Say Y here to support the 82596-based on-board Ethernet controller
1277 for the Panther motherboard, which is one of the two shipped in the
1278 Intel Professional Workstation.
1281 tristate "ICL EtherTeam 16i/32 support"
1284 If you have a network (Ethernet) card of this type, say Y and read
1285 the Ethernet-HOWTO, available from
1286 <http://www.tldp.org/docs.html#howto>.
1288 To compile this driver as a module, choose M here. The module
1289 will be called eth16i.
1292 tristate "NE2000/NE1000 support"
1293 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1296 If you have a network (Ethernet) card of this type, say Y and read
1297 the Ethernet-HOWTO, available from
1298 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1299 without a specific driver are compatible with NE2000.
1301 If you have a PCI NE2000 card however, say N here and Y to "PCI
1302 NE2000 and clone support" under "EISA, VLB, PCI and on board
1303 controllers" below. If you have a NE2000 card and are running on
1304 an MCA system (a bus system used on some IBM PS/2 computers and
1305 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1308 To compile this driver as a module, choose M here. The module
1312 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1313 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1315 The Zenith Z-Note notebook computer has a built-in network
1316 (Ethernet) card, and this is the Linux driver for it. Note that the
1317 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1318 by this driver. Read the Ethernet-HOWTO, available from
1319 <http://www.tldp.org/docs.html#howto>.
1322 tristate "SEEQ8005 support (EXPERIMENTAL)"
1323 depends on NET_ISA && EXPERIMENTAL
1325 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1326 is for you, read the Ethernet-HOWTO, available from
1327 <http://www.tldp.org/docs.html#howto>.
1329 To compile this driver as a module, choose M here. The module
1330 will be called seeq8005.
1333 tristate "NE/2 (ne2000 MCA version) support"
1334 depends on MCA_LEGACY
1337 If you have a network (Ethernet) card of this type, say Y and read
1338 the Ethernet-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here. The module
1345 tristate "IBM LAN Adapter/A support"
1348 This is a Micro Channel Ethernet adapter. You need to set
1349 CONFIG_MCA to use this driver. It is both available as an in-kernel
1350 driver and as a module.
1352 To compile this driver as a module, choose M here. The only
1353 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1354 will both support 16K and 32K memory windows, however a 32K window
1355 gives a better security against packet losses. Usage of multiple
1356 boards with this driver should be possible, but has not been tested
1357 up to now due to lack of hardware.
1360 tristate "IBM LAN Virtual Ethernet support"
1361 depends on PPC_PSERIES
1363 This driver supports virtual ethernet adapters on newer IBM iSeries
1364 and pSeries systems.
1366 To compile this driver as a module, choose M here. The module will
1369 source "drivers/net/ibm_newemac/Kconfig"
1372 bool "EISA, VLB, PCI and on board controllers"
1373 depends on ISA || EISA || PCI
1375 This is another class of network cards which attach directly to the
1376 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1377 available from <http://www.tldp.org/docs.html#howto>.
1379 Note that the answer to this question doesn't directly affect the
1380 kernel: saying N will just cause the configurator to skip all
1381 the questions about this class of network cards. If you say Y, you
1382 will be asked for your specific card in the following questions. If
1383 you are unsure, say Y.
1386 tristate "AMD PCnet32 PCI support"
1387 depends on NET_PCI && PCI
1391 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1392 answer Y here and read the Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto>.
1395 To compile this driver as a module, choose M here. The module
1396 will be called pcnet32.
1399 tristate "AMD 8111 (new PCI lance) support"
1400 depends on NET_PCI && PCI
1404 If you have an AMD 8111-based PCI lance ethernet card,
1405 answer Y here and read the Ethernet-HOWTO, available from
1406 <http://www.tldp.org/docs.html#howto>.
1408 To compile this driver as a module, choose M here. The module
1409 will be called amd8111e.
1411 config ADAPTEC_STARFIRE
1412 tristate "Adaptec Starfire/DuraLAN support"
1413 depends on NET_PCI && PCI
1417 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1418 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1419 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1422 To compile this driver as a module, choose M here: the module
1423 will be called starfire. This is recommended.
1426 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1427 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1430 If you have a network (Ethernet) card of this type, say Y and read
1431 the Ethernet-HOWTO, available from
1432 <http://www.tldp.org/docs.html#howto>.
1434 To compile this driver as a module, choose M here. The module
1435 will be called ac3200.
1438 tristate "Micrel KSZ8841/2 PCI"
1439 depends on NET_PCI && PCI
1443 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1445 To compile this driver as a module, choose M here. The module
1446 will be called ksz884x.
1449 tristate "Apricot Xen-II on board Ethernet"
1450 depends on NET_PCI && ISA
1452 If you have a network (Ethernet) controller of this type, say Y and
1453 read the Ethernet-HOWTO, available from
1454 <http://www.tldp.org/docs.html#howto>.
1456 To compile this driver as a module, choose M here. The module
1457 will be called apricot.
1460 tristate "Broadcom 440x/47xx ethernet support"
1461 depends on SSB_POSSIBLE && HAS_DMA
1465 If you have a network (Ethernet) controller of this type, say Y
1466 or M and read the Ethernet-HOWTO, available from
1467 <http://www.tldp.org/docs.html#howto>.
1469 To compile this driver as a module, choose M here. The module
1472 # Auto-select SSB PCI-HOST support, if possible
1473 config B44_PCI_AUTOSELECT
1475 depends on B44 && SSB_PCIHOST_POSSIBLE
1479 # Auto-select SSB PCICORE driver, if possible
1480 config B44_PCICORE_AUTOSELECT
1482 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1483 select SSB_DRIVER_PCICORE
1488 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1492 tristate "nForce Ethernet support"
1493 depends on NET_PCI && PCI
1495 If you have a network (Ethernet) controller of this type, say Y and
1496 read the Ethernet-HOWTO, available from
1497 <http://www.tldp.org/docs.html#howto>.
1499 To compile this driver as a module, choose M here. The module
1500 will be called forcedeth.
1503 tristate "CS89x0 support"
1504 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1505 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1507 Support for CS89x0 chipset based Ethernet cards. If you have a
1508 network (Ethernet) card of this type, say Y and read the
1509 Ethernet-HOWTO, available from
1510 <http://www.tldp.org/docs.html#howto> as well as
1511 <file:Documentation/networking/cs89x0.txt>.
1513 To compile this driver as a module, choose M here. The module
1514 will be called cs89x0.
1516 config CS89x0_NONISA_IRQ
1518 depends on CS89x0 != n
1519 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1522 tristate "TOSHIBA TC35815 Ethernet support"
1523 depends on NET_PCI && PCI && MIPS
1527 tristate "Intel(R) PRO/100+ support"
1528 depends on NET_PCI && PCI
1531 This driver supports Intel(R) PRO/100 family of adapters.
1532 To verify that your adapter is supported, find the board ID number
1533 on the adapter. Look for a label that has a barcode and a number
1534 in the format 123456-001 (six digits hyphen three digits).
1536 Use the above information and the Adapter & Driver ID Guide at:
1538 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1540 to identify the adapter.
1542 For the latest Intel PRO/100 network driver for Linux, see:
1544 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1546 More specific information on configuring the driver is in
1547 <file:Documentation/networking/e100.txt>.
1549 To compile this driver as a module, choose M here. The module
1550 will be called e100.
1553 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1554 depends on NET_PCI && EISA && EXPERIMENTAL
1557 If you have a network (Ethernet) card of this type, say Y and read
1558 the Ethernet-HOWTO, available from
1559 <http://www.tldp.org/docs.html#howto>.
1561 To compile this driver as a module, choose M here. The module
1562 will be called lne390.
1565 tristate "Myson MTD-8xx PCI Ethernet support"
1566 depends on NET_PCI && PCI
1570 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1571 cards. <http://www.myson.com.tw/>
1574 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1575 depends on NET_PCI && PCI
1578 This driver is for the National Semiconductor DP83810 series,
1579 which is used in cards from PureData, NetGear, Linksys
1580 and others, including the 83815 chip.
1581 More specific information and updates are available from
1582 <http://www.scyld.com/network/natsemi.html>.
1585 tristate "PCI NE2000 and clones support (see help)"
1586 depends on NET_PCI && PCI
1589 This driver is for NE2000 compatible PCI cards. It will not work
1590 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1591 support" below). If you have a PCI NE2000 network (Ethernet) card,
1592 say Y and read the Ethernet-HOWTO, available from
1593 <http://www.tldp.org/docs.html#howto>.
1595 This driver also works for the following NE2000 clone cards:
1596 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1597 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1598 Holtek HT80232 Holtek HT80229
1600 To compile this driver as a module, choose M here. The module
1601 will be called ne2k-pci.
1604 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1605 depends on NET_PCI && EISA && EXPERIMENTAL
1608 If you have a network (Ethernet) card of this type, say Y and read
1609 the Ethernet-HOWTO, available from
1610 <http://www.tldp.org/docs.html#howto>. Note that this driver
1611 will NOT WORK for NE3200 cards as they are completely different.
1613 To compile this driver as a module, choose M here. The module
1614 will be called ne3210.
1617 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1618 depends on NET_PCI && EISA && EXPERIMENTAL
1621 If you have a network (Ethernet) card of this type, say Y and read
1622 the Ethernet-HOWTO, available from
1623 <http://www.tldp.org/docs.html#howto>.
1625 To compile this driver as a module, choose M here. The module
1626 will be called es3210.
1629 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1630 depends on NET_PCI && PCI && EXPERIMENTAL
1634 This is a driver for the Fast Ethernet PCI network cards based on
1635 the RTL8139C+ chips. If you have one of those, say Y and read
1636 the Ethernet-HOWTO, available from
1637 <http://www.tldp.org/docs.html#howto>.
1639 To compile this driver as a module, choose M here: the module
1640 will be called 8139cp. This is recommended.
1643 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1644 depends on NET_PCI && PCI
1648 This is a driver for the Fast Ethernet PCI network cards based on
1649 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1650 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1652 To compile this driver as a module, choose M here: the module
1653 will be called 8139too. This is recommended.
1656 bool "Use PIO instead of MMIO"
1660 This instructs the driver to use programmed I/O ports (PIO) instead
1661 of PCI shared memory (MMIO). This can possibly solve some problems
1662 in case your mainboard has memory consistency issues. If unsure,
1665 config 8139TOO_TUNE_TWISTER
1666 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1669 This implements a function which might come in handy in case you
1670 are using low quality on long cabling. It is required for RealTek
1671 RTL-8139 revision K boards, and totally unused otherwise. It tries
1672 to match the transceiver to the cable characteristics. This is
1673 experimental since hardly documented by the manufacturer.
1677 bool "Support for older RTL-8129/8130 boards"
1680 This enables support for the older and uncommon RTL-8129 and
1681 RTL-8130 chips, which support MII via an external transceiver,
1682 instead of an internal one. Disabling this option will save some
1683 memory by making the code size smaller. If unsure, say Y.
1685 config 8139_OLD_RX_RESET
1686 bool "Use older RX-reset method"
1689 The 8139too driver was recently updated to contain a more rapid
1690 reset sequence, in the face of severe receive errors. This "new"
1691 RX-reset method should be adequate for all boards. But if you
1692 experience problems, you can enable this option to restore the
1693 old RX-reset behavior. If unsure, say N.
1696 tristate "RDC R6040 Fast Ethernet Adapter support"
1697 depends on NET_PCI && PCI
1702 This is a driver for the R6040 Fast Ethernet MACs found in the
1703 the RDC R-321x System-on-chips.
1705 To compile this driver as a module, choose M here: the module
1706 will be called r6040. This is recommended.
1709 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1710 depends on NET_PCI && PCI
1714 This is a driver for the Fast Ethernet PCI network cards based on
1715 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1716 SiS 630 and SiS 540 chipsets.
1718 This driver also supports AMD 79C901 HomePNA so that you can use
1719 your phone line as a network cable.
1721 To compile this driver as a module, choose M here: the module
1722 will be called sis900. This is recommended.
1725 tristate "SMC EtherPower II"
1726 depends on NET_PCI && PCI
1730 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1731 which is based on the SMC83c17x (EPIC/100).
1732 More specific information and updates are available from
1733 <http://www.scyld.com/network/epic100.html>.
1736 tristate "SMSC LAN9420 PCI ethernet adapter support"
1737 depends on NET_PCI && PCI
1742 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1743 Say Y if you want it compiled into the kernel,
1744 and read the Ethernet-HOWTO, available from
1745 <http://www.tldp.org/docs.html#howto>.
1747 This driver is also available as a module. The module will be
1748 called smsc9420. If you want to compile it as a module, say M
1749 here and read <file:Documentation/kbuild/modules.txt>
1752 tristate "Sundance Alta support"
1753 depends on NET_PCI && PCI
1757 This driver is for the Sundance "Alta" chip.
1758 More specific information and updates are available from
1759 <http://www.scyld.com/network/sundance.html>.
1761 config SUNDANCE_MMIO
1762 bool "Use MMIO instead of PIO"
1765 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1766 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1767 is known to solve bugs on certain chips.
1772 tristate "TI ThunderLAN support"
1773 depends on NET_PCI && (PCI || EISA)
1775 If you have a PCI Ethernet network card based on the ThunderLAN chip
1776 which is supported by this driver, say Y and read the
1777 Ethernet-HOWTO, available from
1778 <http://www.tldp.org/docs.html#howto>.
1780 Devices currently supported by this driver are Compaq Netelligent,
1781 Compaq NetFlex and Olicom cards. Please read the file
1782 <file:Documentation/networking/tlan.txt> for more details.
1784 To compile this driver as a module, choose M here. The module
1785 will be called tlan.
1787 Please email feedback to <torben.mathiasen@compaq.com>.
1790 tristate "Micrel KSZ8841/42 with generic bus interface"
1791 depends on HAS_IOMEM && DMA_ENGINE
1793 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1794 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1798 tristate "Micrel KS8851 SPI"
1803 SPI driver for Micrel KS8851 SPI attached network chip.
1806 tristate "Micrel KS8851 MLL"
1807 depends on HAS_IOMEM
1810 This platform driver is for Micrel KS8851 Address/data bus
1811 multiplexed network chip.
1814 tristate "VIA Rhine support"
1815 depends on NET_PCI && PCI
1819 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1820 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1821 Ethernet functions can also be found integrated on South Bridges
1824 To compile this driver as a module, choose M here. The module
1825 will be called via-rhine.
1827 config VIA_RHINE_MMIO
1828 bool "Use MMIO instead of PIO"
1829 depends on VIA_RHINE
1831 This instructs the driver to use PCI shared memory (MMIO) instead of
1832 programmed I/O ports (PIO). Enabling this gives an improvement in
1833 processing time in parts of the driver.
1838 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1839 depends on NET_PCI && PCI && EXPERIMENTAL
1842 This is a driver for the Fast Ethernet PCI network cards based on
1843 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1844 have one of these, say Y here.
1846 To compile this driver as a module, choose M here: the module
1847 will be called sc92031. This is recommended.
1850 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1851 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1854 TI AR7 CPMAC Ethernet support
1857 bool "Pocket and portable adapters"
1860 Cute little network (Ethernet) devices which attach to the parallel
1861 port ("pocket adapters"), commonly used with laptops. If you have
1862 one of those, say Y and read the Ethernet-HOWTO, available from
1863 <http://www.tldp.org/docs.html#howto>.
1865 If you want to plug a network (or some other) card into the PCMCIA
1866 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1867 credit card size extension cards used by all modern laptops), you
1868 need the pcmcia-cs package (location contained in the file
1869 <file:Documentation/Changes>) and you can say N here.
1871 Laptop users should read the Linux Laptop home page at
1872 <http://www.linux-on-laptops.com/> or
1873 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1875 Note that the answer to this question doesn't directly affect the
1876 kernel: saying N will just cause the configurator to skip all
1877 the questions about this class of network devices. If you say Y, you
1878 will be asked for your specific device in the following questions.
1881 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1882 depends on NET_POCKET && PARPORT && X86
1885 This is a network (Ethernet) device which attaches to your parallel
1886 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1887 available from <http://www.tldp.org/docs.html#howto>, if you
1888 want to use this. If you intend to use this driver, you should have
1889 said N to the "Parallel printer support", because the two drivers
1890 don't like each other.
1892 To compile this driver as a module, choose M here: the module
1896 tristate "D-Link DE600 pocket adapter support"
1897 depends on NET_POCKET && PARPORT
1899 This is a network (Ethernet) device which attaches to your parallel
1900 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1901 Ethernet-HOWTO, available from
1902 <http://www.tldp.org/docs.html#howto>, if you want to use
1903 this. It is possible to have several devices share a single parallel
1904 port and it is safe to compile the corresponding drivers into the
1907 To compile this driver as a module, choose M here: the module
1908 will be called de600.
1911 tristate "D-Link DE620 pocket adapter support"
1912 depends on NET_POCKET && PARPORT
1914 This is a network (Ethernet) device which attaches to your parallel
1915 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1916 Ethernet-HOWTO, available from
1917 <http://www.tldp.org/docs.html#howto>, if you want to use
1918 this. It is possible to have several devices share a single parallel
1919 port and it is safe to compile the corresponding drivers into the
1922 To compile this driver as a module, choose M here: the module
1923 will be called de620.
1926 tristate "SGI Seeq ethernet controller support"
1927 depends on SGI_HAS_SEEQ
1929 Say Y here if you have an Seeq based Ethernet network card. This is
1930 used in many Silicon Graphics machines.
1933 tristate "DEC LANCE ethernet controller support"
1934 depends on MACH_DECSTATION
1937 This driver is for the series of Ethernet controllers produced by
1938 DEC (now Compaq) based on the AMD Lance chipset, including the
1939 DEPCA series. (This chipset is better known via the NE2100 cards.)
1942 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1943 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1944 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1945 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1948 Say Y here if you want to use the built-in 10/100 Fast ethernet
1949 controller on some Motorola ColdFire and Freescale i.MX processors.
1952 tristate "MPC52xx FEC driver"
1953 depends on PPC_MPC52xx && PPC_BESTCOMM
1956 select PPC_BESTCOMM_FEC
1958 This option enables support for the MPC5200's on-chip
1959 Fast Ethernet Controller
1960 If compiled as module, it will be called fec_mpc52xx.
1962 config FEC_MPC52xx_MDIO
1963 bool "MPC52xx FEC MDIO bus driver"
1964 depends on FEC_MPC52xx
1967 The MPC5200's FEC can connect to the Ethernet either with
1968 an external MII PHY chip or 10 Mbps 7-wire interface
1969 (Motorola? industry standard).
1970 If your board uses an external PHY connected to FEC, enable this.
1971 If not sure, enable.
1972 If compiled as module, it will be called fec_mpc52xx_phy.
1975 tristate "NE2000 compatible support for H8/300"
1978 Say Y here if you want to use the NE2000 compatible
1979 controller on the Renesas H8/300 processor.
1982 tristate "Atheros L2 Fast Ethernet support"
1987 This driver supports the Atheros L2 fast ethernet adapter.
1989 To compile this driver as a module, choose M here. The module
1990 will be called atl2.
1992 config XILINX_EMACLITE
1993 tristate "Xilinx 10/100 Ethernet Lite support"
1994 depends on PPC32 || MICROBLAZE
1997 This driver supports the 10/100 Ethernet Lite from Xilinx.
2000 tristate "Broadcom 63xx internal mac support"
2005 This driver supports the ethernet MACs in the Broadcom 63xx
2006 MIPS chipset family (BCM63XX).
2009 tristate "Faraday FTMAC100 10/100 Ethernet support"
2013 This driver supports the FTMAC100 10/100 Ethernet controller
2014 from Faraday. It is used on Faraday A320, Andes AG101 and some
2015 other ARM/NDS32 SoC's.
2018 tristate "Lantiq SoC ETOP driver"
2019 depends on SOC_TYPE_XWAY
2021 Support for the MII0 inside the Lantiq SoC
2024 source "drivers/net/fs_enet/Kconfig"
2026 source "drivers/net/octeon/Kconfig"
2028 endif # NET_ETHERNET
2034 menuconfig NETDEV_1000
2035 bool "Ethernet (1000 Mbit)"
2039 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2040 type of Local Area Network (LAN) in universities and companies.
2042 Say Y here to get to see options for Gigabit Ethernet drivers.
2043 This option alone does not add any kernel code.
2044 Note that drivers supporting both 100 and 1000 MBit may be listed
2045 under "Ethernet (10 or 100MBit)" instead.
2047 If you say N, all options in this submenu will be skipped and disabled.
2052 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2055 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2056 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2057 adapter. The driver allows for using the Jumbo Frame option (9000
2058 bytes/frame) however it requires that your switches can handle this
2059 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2062 To compile this driver as a module, choose M here: the
2063 module will be called acenic.
2065 config ACENIC_OMIT_TIGON_I
2066 bool "Omit support for old Tigon I based AceNICs"
2069 Say Y here if you only have Tigon II based AceNICs and want to leave
2070 out support for the older Tigon I based cards which are no longer
2071 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2072 version)). This will reduce the size of the driver object by
2073 app. 100KB. If you are not sure whether your card is a Tigon I or a
2074 Tigon II, say N here.
2076 The safe and default value for this is N.
2079 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2083 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2085 D-Link DGE-550T Gigabit Ethernet Adapter.
2086 D-Link DL2000-based Gigabit Ethernet Adapter.
2087 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2089 To compile this driver as a module, choose M here: the
2090 module will be called dl2k.
2093 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2096 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2097 adapters. For more information on how to identify your adapter, go
2098 to the Adapter & Driver ID Guide at:
2100 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2102 For general information and support, go to the Intel support
2105 <http://support.intel.com>
2107 More specific information on configuring the driver is in
2108 <file:Documentation/networking/e1000.txt>.
2110 To compile this driver as a module, choose M here. The module
2111 will be called e1000.
2114 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2115 depends on PCI && (!SPARC32 || BROKEN)
2118 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2119 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2120 use the regular e1000 driver For more information on how to
2121 identify your adapter, go to the Adapter & Driver ID Guide at:
2123 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2125 For general information and support, go to the Intel support
2128 <http://support.intel.com>
2130 To compile this driver as a module, choose M here. The module
2131 will be called e1000e.
2134 tristate "IP1000 Gigabit Ethernet support"
2135 depends on PCI && EXPERIMENTAL
2138 This driver supports IP1000 gigabit Ethernet cards.
2140 To compile this driver as a module, choose M here: the module
2141 will be called ipg. This is recommended.
2144 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2147 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2148 adapters. For more information on how to identify your adapter, go
2149 to the Adapter & Driver ID Guide at:
2151 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2153 For general information and support, go to the Intel support
2156 <http://support.intel.com>
2158 More specific information on configuring the driver is in
2159 <file:Documentation/networking/e1000.txt>.
2161 To compile this driver as a module, choose M here. The module
2165 bool "Direct Cache Access (DCA) Support"
2167 depends on IGB && DCA && !(IGB=y && DCA=m)
2169 Say Y here if you want to use Direct Cache Access (DCA) in the
2170 driver. DCA is a method for warming the CPU cache before data
2171 is used, with the intent of lessening the impact of cache misses.
2174 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2177 This driver supports Intel(R) 82576 virtual functions. For more
2178 information on how to identify your adapter, go to the Adapter &
2181 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2183 For general information and support, go to the Intel support
2186 <http://support.intel.com>
2188 More specific information on configuring the driver is in
2189 <file:Documentation/networking/e1000.txt>.
2191 To compile this driver as a module, choose M here. The module
2192 will be called igbvf.
2194 source "drivers/net/ixp2000/Kconfig"
2197 tristate "National Semiconductor DP83820 support"
2200 This is a driver for the National Semiconductor DP83820 series
2201 of gigabit ethernet MACs. Cards using this chipset include
2202 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2203 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2207 tristate "Packet Engines Hamachi GNIC-II support"
2211 If you have a Gigabit Ethernet card of this type, say Y and read
2212 the Ethernet-HOWTO, available from
2213 <http://www.tldp.org/docs.html#howto>.
2215 To compile this driver as a module, choose M here. The module will be
2219 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2220 depends on PCI && EXPERIMENTAL
2223 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2224 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2225 used by the Beowulf Linux cluster project. See
2226 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2227 information about this driver in particular and Beowulf in general.
2229 To compile this driver as a module, choose M here: the module
2230 will be called yellowfin. This is recommended.
2233 tristate "Realtek 8169 gigabit ethernet support"
2239 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2241 To compile this driver as a module, choose M here: the module
2242 will be called r8169. This is recommended.
2245 tristate "SB1250 Gigabit Ethernet support"
2246 depends on SIBYTE_SB1xxx_SOC
2249 This driver supports Gigabit Ethernet interfaces based on the
2250 Broadcom SiByte family of System-On-a-Chip parts. They include
2251 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2254 To compile this driver as a module, choose M here: the module
2255 will be called sb1250-mac.
2258 tristate "SiS190/SiS191 gigabit ethernet support"
2263 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2264 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2265 appear in lan on motherboard designs which are based on SiS 965
2266 and SiS 966 south bridge.
2268 To compile this driver as a module, choose M here: the module
2269 will be called sis190. This is recommended.
2272 tristate "Marvell Yukon Gigabit Ethernet support"
2276 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2277 and related Gigabit Ethernet adapters. It is a new smaller driver
2278 with better performance and more complete ethtool support.
2280 It does not support the link failover and network management
2281 features that "portable" vendor supplied sk98lin driver does.
2283 This driver supports adapters based on the original Yukon chipset:
2284 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2285 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2287 It does not support the newer Yukon2 chipset: a separate driver,
2288 sky2, is provided for these adapters.
2290 To compile this driver as a module, choose M here: the module
2291 will be called skge. This is recommended.
2294 bool "Debugging interface"
2295 depends on SKGE && DEBUG_FS
2297 This option adds the ability to dump driver state for debugging.
2298 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2299 transmit and receive rings.
2304 bool "Support for older SysKonnect Genesis boards"
2307 This enables support for the older and uncommon SysKonnect Genesis
2308 chips, which support MII via an external transceiver, instead of
2309 an internal one. Disabling this option will save some memory
2310 by making code smaller. If unsure say Y.
2313 tristate "Marvell Yukon 2 support"
2317 This driver supports Gigabit Ethernet adapters based on the
2318 Marvell Yukon 2 chipset:
2319 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2320 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2322 There is companion driver for the older Marvell Yukon and
2323 SysKonnect Genesis based adapters: skge.
2325 To compile this driver as a module, choose M here: the module
2326 will be called sky2. This is recommended.
2329 bool "Debugging interface"
2330 depends on SKY2 && DEBUG_FS
2332 This option adds the ability to dump driver state for debugging.
2333 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2334 transmit and receive rings.
2339 tristate "VIA Velocity support"
2345 If you have a VIA "Velocity" based network card say Y here.
2347 To compile this driver as a module, choose M here. The module
2348 will be called via-velocity.
2351 tristate "Broadcom Tigon3 support"
2355 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2357 To compile this driver as a module, choose M here: the module
2358 will be called tg3. This is recommended.
2361 tristate "Broadcom NetXtremeII support"
2366 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2368 To compile this driver as a module, choose M here: the module
2369 will be called bnx2. This is recommended.
2372 tristate "Broadcom CNIC support"
2377 This driver supports offload features of Broadcom NetXtremeII
2378 gigabit Ethernet cards.
2380 To compile this driver as a module, choose M here: the module
2381 will be called cnic. This is recommended.
2384 tristate "Spider Gigabit Ethernet driver"
2385 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2388 This driver supports the Gigabit Ethernet chips present on the
2389 Cell Processor-Based Blades from IBM.
2392 tristate "Tundra TSI108 gigabit Ethernet support"
2393 depends on TSI108_BRIDGE
2395 This driver supports Tundra TSI108 gigabit Ethernet ports.
2396 To compile this driver as a module, choose M here: the module
2397 will be called tsi108_eth.
2400 tristate "PS3 Gigabit Ethernet driver"
2402 select PS3_SYS_MANAGER
2404 This driver supports the network device on the PS3 game
2405 console. This driver has built-in support for Ethernet.
2407 To compile this driver as a module, choose M here: the
2408 module will be called ps3_gelic.
2410 config GELIC_WIRELESS
2411 bool "PS3 Wireless support"
2413 depends on GELIC_NET
2416 This option adds the support for the wireless feature of PS3.
2417 If you have the wireless-less model of PS3 or have no plan to
2418 use wireless feature, disabling this option saves memory. As
2419 the driver automatically distinguishes the models, you can
2420 safely enable this option even if you have a wireless-less model.
2423 tristate "Freescale PQ MDIO"
2427 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2430 tristate "Gianfar Ethernet"
2436 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2437 and MPC86xx family of chips, and the FEC on the 8540.
2440 tristate "Freescale QE Gigabit Ethernet"
2441 depends on QUICC_ENGINE
2445 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2446 which is available on some Freescale SOCs.
2448 config UGETH_TX_ON_DEMAND
2449 bool "Transmit on Demand support"
2453 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2454 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2458 This driver supports the gigabit ethernet MACs in the
2459 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2460 in the Marvell Orion ARM SoC family.
2462 Some boards that use the Discovery chipset are the Momenco
2463 Ocelot C and Jaguar ATX and Pegasos II.
2465 config XILINX_LL_TEMAC
2466 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2467 depends on PPC || MICROBLAZE
2470 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2471 core used in Xilinx Spartan and Virtex FPGAs
2474 tristate "QLogic QLA3XXX Network Driver Support"
2477 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2479 To compile this driver as a module, choose M here: the module
2480 will be called qla3xxx.
2483 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2488 This driver supports the Atheros/Attansic L1 gigabit ethernet
2491 To compile this driver as a module, choose M here. The module
2492 will be called atl1.
2495 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2496 depends on PCI && EXPERIMENTAL
2500 This driver supports the Atheros L1E gigabit ethernet adapter.
2502 To compile this driver as a module, choose M here. The module
2503 will be called atl1e.
2506 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2507 depends on PCI && EXPERIMENTAL
2511 This driver supports the Atheros L1C gigabit ethernet adapter.
2513 To compile this driver as a module, choose M here. The module
2514 will be called atl1c.
2517 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2522 This driver supports the PCI-Express gigabit ethernet adapters
2523 based on JMicron JMC250 chipset.
2525 To compile this driver as a module, choose M here. The module
2529 tristate "S6105 GMAC ethernet support"
2530 depends on XTENSA_VARIANT_S6000
2533 This driver supports the on chip ethernet device on the
2534 S6105 xtensa processor.
2536 To compile this driver as a module, choose M here. The module
2537 will be called s6gmac.
2539 source "drivers/net/stmmac/Kconfig"
2542 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
2546 This is a gigabit ethernet driver for EG20T PCH.
2547 EG20T PCH is the platform controller hub that is used in Intel's
2548 general embedded platform.
2549 EG20T PCH has Gigabit Ethernet interface.
2550 Using this interface, it is able to access system devices connected
2551 to Gigabit Ethernet.
2552 This driver enables Gigabit Ethernet function.
2554 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
2555 Output Hub), ML7223.
2556 ML7223 IOH is for MP(Media Phone) use.
2557 ML7223 is companion chip for Intel Atom E6xx series.
2558 ML7223 is completely compatible for Intel EG20T PCH.
2561 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
2565 This driver supports the FTGMAC100 Gigabit Ethernet controller
2566 from Faraday. It is used on Faraday A369, Andes AG102 and some
2567 other ARM/NDS32 SoC's.
2572 # 10 Gigabit Ethernet
2575 menuconfig NETDEV_10000
2576 bool "Ethernet (10000 Mbit)"
2580 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2581 This option alone does not add any kernel code.
2583 If you say N, all options in this submenu will be skipped and disabled.
2591 tristate "Chelsio 10Gb Ethernet support"
2596 This driver supports Chelsio gigabit and 10-gigabit
2597 Ethernet cards. More information about adapter features and
2598 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2600 For general information about Chelsio and our products, visit
2601 our website at <http://www.chelsio.com>.
2603 For customer support, please visit our customer support page at
2604 <http://www.chelsio.com/support.html>.
2606 Please send feedback to <linux-bugs@chelsio.com>.
2608 To compile this driver as a module, choose M here: the module
2609 will be called cxgb.
2611 config CHELSIO_T1_1G
2612 bool "Chelsio gigabit Ethernet support"
2613 depends on CHELSIO_T1
2615 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2616 are using only 10G cards say 'N' here.
2619 tristate "Chelsio Communications T3 10Gb Ethernet support"
2620 depends on PCI && INET
2624 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2627 For general information about Chelsio and our products, visit
2628 our website at <http://www.chelsio.com>.
2630 For customer support, please visit our customer support page at
2631 <http://www.chelsio.com/support.html>.
2633 Please send feedback to <linux-bugs@chelsio.com>.
2635 To compile this driver as a module, choose M here: the module
2636 will be called cxgb3.
2639 tristate "Chelsio Communications T4 Ethernet support"
2644 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2647 For general information about Chelsio and our products, visit
2648 our website at <http://www.chelsio.com>.
2650 For customer support, please visit our customer support page at
2651 <http://www.chelsio.com/support.html>.
2653 Please send feedback to <linux-bugs@chelsio.com>.
2655 To compile this driver as a module choose M here; the module
2656 will be called cxgb4.
2659 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2662 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2663 adapters with PCI-E SR-IOV Virtual Functions.
2665 For general information about Chelsio and our products, visit
2666 our website at <http://www.chelsio.com>.
2668 For customer support, please visit our customer support page at
2669 <http://www.chelsio.com/support.html>.
2671 Please send feedback to <linux-bugs@chelsio.com>.
2673 To compile this driver as a module choose M here; the module
2674 will be called cxgb4vf.
2677 tristate "eHEA Ethernet support"
2678 depends on IBMEBUS && INET && SPARSEMEM
2681 This driver supports the IBM pSeries eHEA ethernet adapter.
2683 To compile the driver as a module, choose M here. The module
2684 will be called ehea.
2687 tristate "Cisco VIC Ethernet NIC Support"
2688 depends on PCI && INET
2690 This enables the support for the Cisco VIC Ethernet card.
2693 tristate "Intel(R) 10GbE PCI Express adapters support"
2694 depends on PCI && INET
2697 This driver supports Intel(R) 10GbE PCI Express family of
2698 adapters. For more information on how to identify your adapter, go
2699 to the Adapter & Driver ID Guide at:
2701 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2703 For general information and support, go to the Intel support
2706 <http://support.intel.com>
2708 To compile this driver as a module, choose M here. The module
2709 will be called ixgbe.
2712 bool "Direct Cache Access (DCA) Support"
2714 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2716 Say Y here if you want to use Direct Cache Access (DCA) in the
2717 driver. DCA is a method for warming the CPU cache before data
2718 is used, with the intent of lessening the impact of cache misses.
2721 bool "Data Center Bridging (DCB) Support"
2723 depends on IXGBE && DCB
2725 Say Y here if you want to use Data Center Bridging (DCB) in the
2731 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2734 This driver supports Intel(R) 82599 virtual functions. For more
2735 information on how to identify your adapter, go to the Adapter &
2738 <http://support.intel.com/support/network/sb/CS-008441.htm>
2740 For general information and support, go to the Intel support
2743 <http://support.intel.com>
2745 More specific information on configuring the driver is in
2746 <file:Documentation/networking/ixgbevf.txt>.
2748 To compile this driver as a module, choose M here. The module
2749 will be called ixgbevf. MSI-X interrupt support is required
2750 for this driver to work correctly.
2753 tristate "Intel(R) PRO/10GbE support"
2756 This driver supports Intel(R) PRO/10GbE family of adapters for
2757 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2758 instead. For more information on how to identify your adapter, go
2759 to the Adapter & Driver ID Guide at:
2761 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2763 For general information and support, go to the Intel support
2766 <http://support.intel.com>
2768 More specific information on configuring the driver is in
2769 <file:Documentation/networking/ixgb.txt>.
2771 To compile this driver as a module, choose M here. The module
2772 will be called ixgb.
2775 tristate "Exar Xframe 10Gb Ethernet Adapter"
2778 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2780 More specific information on configuring the driver is in
2781 <file:Documentation/networking/s2io.txt>.
2783 To compile this driver as a module, choose M here. The module
2784 will be called s2io.
2787 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2788 depends on PCI && INET
2792 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2793 I/O Virtualized Server Adapter.
2795 More specific information on configuring the driver is in
2796 <file:Documentation/networking/vxge.txt>.
2798 To compile this driver as a module, choose M here. The module
2799 will be called vxge.
2801 config VXGE_DEBUG_TRACE_ALL
2802 bool "Enabling All Debug trace statments in driver"
2806 Say Y here if you want to enabling all the debug trace statements in
2807 the vxge driver. By default only few debug trace statements are
2811 tristate "Myricom Myri-10G Ethernet support"
2812 depends on PCI && INET
2817 This driver supports Myricom Myri-10G Dual Protocol interface in
2818 Ethernet mode. If the eeprom on your board is not recent enough,
2819 you will need a newer firmware image.
2820 You may get this image or more information, at:
2822 <http://www.myri.com/scs/download-Myri10GE.html>
2824 To compile this driver as a module, choose M here. The module
2825 will be called myri10ge.
2828 bool "Direct Cache Access (DCA) Support"
2830 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2832 Say Y here if you want to use Direct Cache Access (DCA) in the
2833 driver. DCA is a method for warming the CPU cache before data
2834 is used, with the intent of lessening the impact of cache misses.
2837 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2843 This enables the support for NetXen's Gigabit Ethernet card.
2846 tristate "Sun Neptune 10Gbit Ethernet support"
2850 This enables support for cards based upon Sun's
2854 tristate "PA Semi 1/10Gbit MAC"
2855 depends on PPC_PASEMI && PCI && INET
2859 This driver supports the on-chip 1/10Gbit Ethernet controller on
2860 PA Semi's PWRficient line of chips.
2863 tristate "Mellanox Technologies 10Gbit Ethernet support"
2864 depends on PCI && INET
2868 This driver supports Mellanox Technologies ConnectX Ethernet
2877 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2878 depends on MLX4_CORE
2881 This option causes debugging code to be compiled into the
2882 mlx4_core driver. The output can be turned on via the
2883 debug_level module parameter (which can also be set after
2884 the driver is loaded through sysfs).
2887 tristate "Tehuti Networks 10G Ethernet"
2890 Tehuti Networks 10G Ethernet NIC
2893 tristate "Broadcom NetXtremeII 10Gb support"
2900 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2901 To compile this driver as a module, choose M here: the module
2902 will be called bnx2x. This is recommended.
2905 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2909 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2913 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2916 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2918 To compile this driver as a module, choose M here: the module
2919 will be called qlge.
2922 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2925 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2927 To compile this driver as a module, choose M here: the module
2930 For general information and support, go to the Brocade support
2933 <http://support.brocade.com>
2935 source "drivers/net/sfc/Kconfig"
2937 source "drivers/net/benet/Kconfig"
2939 endif # NETDEV_10000
2941 source "drivers/net/tokenring/Kconfig"
2943 source "drivers/net/wireless/Kconfig"
2945 source "drivers/net/wimax/Kconfig"
2947 source "drivers/net/usb/Kconfig"
2949 source "drivers/net/pcmcia/Kconfig"
2951 source "drivers/net/wan/Kconfig"
2953 source "drivers/atm/Kconfig"
2955 source "drivers/ieee802154/Kconfig"
2957 source "drivers/s390/net/Kconfig"
2959 source "drivers/net/caif/Kconfig"
2962 tristate "Tilera GBE/XGBE network driver support"
2967 This is a standard Linux network device driver for the
2968 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2970 To compile this driver as a module, choose M here: the module
2971 will be called tile_net.
2973 config XEN_NETDEV_FRONTEND
2974 tristate "Xen network device frontend driver"
2976 select XEN_XENBUS_FRONTEND
2979 This driver provides support for Xen paravirtual network
2980 devices exported by a Xen network driver domain (often
2983 The corresponding Linux backend driver is enabled by the
2984 CONFIG_XEN_NETDEV_BACKEND option.
2986 If you are compiling a kernel for use as Xen guest, you
2987 should say Y here. To compile this driver as a module, chose
2988 M here: the module will be called xen-netfront.
2990 config XEN_NETDEV_BACKEND
2991 tristate "Xen backend network device"
2992 depends on XEN_BACKEND
2994 This driver allows the kernel to act as a Xen network driver
2995 domain which exports paravirtual network devices to other
2996 Xen domains. These devices can be accessed by any operating
2997 system that implements a compatible front end.
2999 The corresponding Linux frontend driver is enabled by the
3000 CONFIG_XEN_NETDEV_FRONTEND configuration option.
3002 The backend driver presents a standard network device
3003 endpoint for each paravirtual network device to the driver
3004 domain network stack. These can then be bridged or routed
3005 etc in order to provide full network connectivity.
3007 If you are compiling a kernel to run in a Xen network driver
3008 domain (often this is domain 0) you should say Y here. To
3009 compile this driver as a module, chose M here: the module
3010 will be called xen-netback.
3013 tristate "iSeries Virtual Ethernet driver support"
3014 depends on PPC_ISERIES
3017 tristate "RapidIO Ethernet over messaging driver support"
3020 config RIONET_TX_SIZE
3021 int "Number of outbound queue entries"
3025 config RIONET_RX_SIZE
3026 int "Number of inbound queue entries"
3031 tristate "FDDI driver support"
3032 depends on (PCI || EISA || TC)
3034 Fiber Distributed Data Interface is a high speed local area network
3035 design; essentially a replacement for high speed Ethernet. FDDI can
3036 run over copper or fiber. If you are connected to such a network and
3037 want a driver for the FDDI card in your computer, say Y here (and
3038 then also Y to the driver for your FDDI card, below). Most people
3042 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
3043 depends on FDDI && (PCI || EISA || TC)
3045 This is support for the DIGITAL series of TURBOchannel (DEFTA),
3046 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
3047 to a local FDDI network.
3049 To compile this driver as a module, choose M here: the module
3050 will be called defxx. If unsure, say N.
3054 prompt "Use MMIO instead of PIO" if PCI || EISA
3056 default n if PCI || EISA
3059 This instructs the driver to use EISA or PCI memory-mapped I/O
3060 (MMIO) as appropriate instead of programmed I/O ports (PIO).
3061 Enabling this gives an improvement in processing time in parts
3062 of the driver, but it may cause problems with EISA (DEFEA)
3063 adapters. TURBOchannel does not have the concept of I/O ports,
3064 so MMIO is always used for these (DEFTA) adapters.
3069 tristate "SysKonnect FDDI PCI support"
3070 depends on FDDI && PCI
3073 Say Y here if you have a SysKonnect FDDI PCI adapter.
3074 The following adapters are supported by this driver:
3075 - SK-5521 (SK-NET FDDI-UP)
3076 - SK-5522 (SK-NET FDDI-UP DAS)
3077 - SK-5541 (SK-NET FDDI-FP)
3078 - SK-5543 (SK-NET FDDI-LP)
3079 - SK-5544 (SK-NET FDDI-LP DAS)
3080 - SK-5821 (SK-NET FDDI-UP64)
3081 - SK-5822 (SK-NET FDDI-UP64 DAS)
3082 - SK-5841 (SK-NET FDDI-FP64)
3083 - SK-5843 (SK-NET FDDI-LP64)
3084 - SK-5844 (SK-NET FDDI-LP64 DAS)
3085 - Netelligent 100 FDDI DAS Fibre SC
3086 - Netelligent 100 FDDI SAS Fibre SC
3087 - Netelligent 100 FDDI DAS UTP
3088 - Netelligent 100 FDDI SAS UTP
3089 - Netelligent 100 FDDI SAS Fibre MIC
3091 Read <file:Documentation/networking/skfp.txt> for information about
3094 Questions concerning this driver can be addressed to:
3095 <linux@syskonnect.de>
3097 To compile this driver as a module, choose M here: the module
3098 will be called skfp. This is recommended.
3101 bool "HIPPI driver support (EXPERIMENTAL)"
3102 depends on EXPERIMENTAL && INET && PCI
3104 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3105 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3106 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3107 single-mode). HIPPI networks are commonly used for clusters and to
3108 connect to super computers. If you are connected to a HIPPI network
3109 and have a HIPPI network card in your computer that you want to use
3110 under Linux, say Y here (you must also remember to enable the driver
3111 for your HIPPI card below). Most people will say N here.
3114 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3115 depends on HIPPI && PCI
3117 Say Y here if this is your PCI HIPPI network card.
3119 To compile this driver as a module, choose M here: the module
3120 will be called rrunner. If unsure, say N.
3122 config ROADRUNNER_LARGE_RINGS
3123 bool "Use large TX/RX rings (EXPERIMENTAL)"
3124 depends on ROADRUNNER
3126 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3127 of additional memory to allow for fastest operation, both for
3128 transmitting and receiving. This memory cannot be used by any other
3129 kernel code or by user space programs. Say Y here only if you have
3133 tristate "PLIP (parallel port) support"
3136 PLIP (Parallel Line Internet Protocol) is used to create a
3137 reasonably fast mini network consisting of two (or, rarely, more)
3138 local machines. A PLIP link from a Linux box is a popular means to
3139 install a Linux distribution on a machine which doesn't have a
3140 CD-ROM drive (a minimal system has to be transferred with floppies
3141 first). The kernels on both machines need to have this PLIP option
3142 enabled for this to work.
3144 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3145 ports (the connectors at the computers with 25 holes) are connected
3146 with "null printer" or "Turbo Laplink" cables which can transmit 4
3147 bits at a time (mode 0) or with special PLIP cables, to be used on
3148 bidirectional parallel ports only, which can transmit 8 bits at a
3149 time (mode 1); you can find the wiring of these cables in
3150 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3151 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3152 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3153 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3154 and winsock or NCSA's telnet.
3156 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3157 as the NET-3-HOWTO, both available from
3158 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3159 protocol has been changed and this PLIP driver won't work together
3160 with the PLIP support in Linux versions 1.0.x. This option enlarges
3161 your kernel by about 8 KB.
3163 To compile this driver as a module, choose M here. The module
3164 will be called plip. If unsure, say Y or M, in case you buy
3168 tristate "PPP (point-to-point protocol) support"
3171 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3172 the same purpose: sending Internet traffic over telephone (and other
3173 serial) lines. Ask your access provider if they support it, because
3174 otherwise you can't use it; most Internet access providers these
3175 days support PPP rather than SLIP.
3177 To use PPP, you need an additional program called pppd as described
3178 in the PPP-HOWTO, available at
3179 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3180 the version of pppd recommended in <file:Documentation/Changes>.
3181 The PPP option enlarges your kernel by about 16 KB.
3183 There are actually two versions of PPP: the traditional PPP for
3184 asynchronous lines, such as regular analog phone lines, and
3185 synchronous PPP which can be used over digital ISDN lines for
3186 example. If you want to use PPP over phone lines or other
3187 asynchronous serial lines, you need to say Y (or M) here and also to
3188 the next option, "PPP support for async serial ports". For PPP over
3189 synchronous lines, you should say Y (or M) here and to "Support
3190 synchronous PPP", below.
3192 If you said Y to "Version information on all symbols" above, then
3193 you cannot compile the PPP driver into the kernel; you can then only
3194 compile it as a module. To compile this driver as a module, choose M
3195 here. The module will be called ppp_generic.
3197 config PPP_MULTILINK
3198 bool "PPP multilink support (EXPERIMENTAL)"
3199 depends on PPP && EXPERIMENTAL
3201 PPP multilink is a protocol (defined in RFC 1990) which allows you
3202 to combine several (logical or physical) lines into one logical PPP
3203 connection, so that you can utilize your full bandwidth.
3205 This has to be supported at the other end as well and you need a
3206 version of the pppd daemon which understands the multilink protocol.
3211 bool "PPP filtering"
3214 Say Y here if you want to be able to filter the packets passing over
3215 PPP interfaces. This allows you to control which packets count as
3216 activity (i.e. which packets will reset the idle timer or bring up
3217 a demand-dialed link) and which packets are to be dropped entirely.
3218 You need to say Y here if you wish to use the pass-filter and
3219 active-filter options to pppd.
3224 tristate "PPP support for async serial ports"
3228 Say Y (or M) here if you want to be able to use PPP over standard
3229 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3230 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3233 To compile this driver as a module, choose M here.
3238 tristate "PPP support for sync tty ports"
3241 Say Y (or M) here if you want to be able to use PPP over synchronous
3242 (HDLC) tty devices, such as the SyncLink adapter. These devices
3243 are often used for high-speed leased lines like T1/E1.
3245 To compile this driver as a module, choose M here.
3248 tristate "PPP Deflate compression"
3253 Support for the Deflate compression method for PPP, which uses the
3254 Deflate algorithm (the same algorithm that gzip uses) to compress
3255 each PPP packet before it is sent over the wire. The machine at the
3256 other end of the PPP link (usually your ISP) has to support the
3257 Deflate compression method as well for this to be useful. Even if
3258 they don't support it, it is safe to say Y here.
3260 To compile this driver as a module, choose M here.
3263 tristate "PPP BSD-Compress compression"
3266 Support for the BSD-Compress compression method for PPP, which uses
3267 the LZW compression method to compress each PPP packet before it is
3268 sent over the wire. The machine at the other end of the PPP link
3269 (usually your ISP) has to support the BSD-Compress compression
3270 method as well for this to be useful. Even if they don't support it,
3271 it is safe to say Y here.
3273 The PPP Deflate compression method ("PPP Deflate compression",
3274 above) is preferable to BSD-Compress, because it compresses better
3277 Note that the BSD compression code will always be compiled as a
3278 module; it is called bsd_comp and will show up in the directory
3279 modules once you have said "make modules". If unsure, say N.
3282 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3283 depends on PPP && EXPERIMENTAL
3289 Support for the MPPE Encryption protocol, as employed by the
3290 Microsoft Point-to-Point Tunneling Protocol.
3292 See http://pptpclient.sourceforge.net/ for information on
3293 configuring PPTP clients and servers to utilize this method.
3296 tristate "PPP over Ethernet (EXPERIMENTAL)"
3297 depends on EXPERIMENTAL && PPP
3299 Support for PPP over Ethernet.
3301 This driver requires the latest version of pppd from the CVS
3302 repository at cvs.samba.org. Alternatively, see the
3303 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3304 which contains instruction on how to use this driver (under
3305 the heading "Kernel mode PPPoE").
3308 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3309 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3311 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3313 This driver requires pppd plugin to work in client mode or
3314 modified pptpd (poptop) to work in server mode.
3315 See http://accel-pptp.sourceforge.net/ for information how to
3316 utilize this module.
3319 tristate "PPP over ATM"
3320 depends on ATM && PPP
3322 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3323 This implementation does not yet comply with section 8 of RFC2364,
3324 which can lead to bad results if the ATM peer loses state and
3325 changes its encapsulation unilaterally.
3328 tristate "PPP over L2TP (EXPERIMENTAL)"
3329 depends on EXPERIMENTAL && L2TP && PPP
3331 Support for PPP-over-L2TP socket family. L2TP is a protocol
3332 used by ISPs and enterprises to tunnel PPP traffic over UDP
3333 tunnels. L2TP is replacing PPTP for VPN uses.
3336 tristate "SLIP (serial line) support"
3338 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3339 connect to your Internet service provider or to connect to some
3340 other local Unix box or if you want to configure your Linux box as a
3341 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3342 Internet Protocol) is a protocol used to send Internet traffic over
3343 serial connections such as telephone lines or null modem cables;
3344 nowadays, the protocol PPP is more commonly used for this same
3347 Normally, your access provider has to support SLIP in order for you
3348 to be able to use it, but there is now a SLIP emulator called SLiRP
3349 around (available from
3350 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3351 allows you to use SLIP over a regular dial up shell connection. If
3352 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3353 NET-3-HOWTO, available from
3354 <http://www.tldp.org/docs.html#howto>, explains how to
3355 configure SLIP. Note that you don't need this option if you just
3356 want to run term (term is a program which gives you almost full
3357 Internet connectivity if you have a regular dial up shell account on
3358 some Internet connected Unix computer. Read
3359 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3360 support will enlarge your kernel by about 4 KB. If unsure, say N.
3362 To compile this driver as a module, choose M here. The module
3363 will be called slip.
3365 config SLIP_COMPRESSED
3366 bool "CSLIP compressed headers"
3370 This protocol is faster than SLIP because it uses compression on the
3371 TCP/IP headers (not on the data itself), but it has to be supported
3372 on both ends. Ask your access provider if you are not sure and
3373 answer Y, just in case. You will still be able to use plain SLIP. If
3374 you plan to use SLiRP, the SLIP emulator (available from
3375 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3376 allows you to use SLIP over a regular dial up shell connection, you
3377 definitely want to say Y here. The NET-3-HOWTO, available from
3378 <http://www.tldp.org/docs.html#howto>, explains how to configure
3379 CSLIP. This won't enlarge your kernel.
3384 This option enables Van Jacobsen serial line header compression
3388 bool "Keepalive and linefill"
3391 Adds additional capabilities to the SLIP driver to support the
3392 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3395 config SLIP_MODE_SLIP6
3396 bool "Six bit SLIP encapsulation"
3399 Just occasionally you may need to run IP over hostile serial
3400 networks that don't pass all control characters or are only seven
3401 bit. Saying Y here adds an extra mode you can use with SLIP:
3402 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3403 the serial device. Naturally, this has to be supported at the other
3404 end of the link as well. It's good enough, for example, to run IP
3405 over the async ports of a Camtec JNT Pad. If unsure, say N.
3408 bool "Fibre Channel driver support"
3409 depends on SCSI && PCI
3411 Fibre Channel is a high speed serial protocol mainly used to connect
3412 large storage devices to the computer; it is compatible with and
3413 intended to replace SCSI.
3415 If you intend to use Fibre Channel, you need to have a Fibre channel
3416 adaptor card in your computer; say Y here and to the driver for your
3417 adaptor below. You also should have said Y to "SCSI support" and
3418 "SCSI generic support".
3421 tristate "Network console logging support"
3423 If you want to log kernel messages over the network, enable this.
3424 See <file:Documentation/networking/netconsole.txt> for details.
3426 config NETCONSOLE_DYNAMIC
3427 bool "Dynamic reconfiguration of logging targets"
3428 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
3429 !(NETCONSOLE=y && CONFIGFS_FS=m)
3431 This option enables the ability to dynamically reconfigure target
3432 parameters (interface, IP addresses, port numbers, MAC addresses)
3433 at runtime through a userspace interface exported using configfs.
3434 See <file:Documentation/networking/netconsole.txt> for details.
3440 bool "Netpoll traffic trapping"
3444 config NET_POLL_CONTROLLER
3448 tristate "Virtio network driver (EXPERIMENTAL)"
3449 depends on EXPERIMENTAL && VIRTIO
3451 This is the virtual network driver for virtio. It can be used with
3452 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3455 tristate "VMware VMXNET3 ethernet driver"
3456 depends on PCI && INET
3458 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3459 To compile this driver as a module, choose M here: the
3460 module will be called vmxnet3.