2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
97 This adds a specialized tap character device driver that is based
98 on the MAC-VLAN network interface, called macvtap. A macvtap device
99 can be added in the same way as a macvlan device, using 'type
100 macvlan', and then be accessed through the tap user space interface.
102 To compile this driver as a module, choose M here: the module
103 will be called macvtap.
106 tristate "EQL (serial line load balancing) support"
108 If you have two serial connections to some other computer (this
109 usually requires two modems and two telephone lines) and you use
110 SLIP (the protocol for sending Internet traffic over telephone
111 lines) or PPP (a better SLIP) on them, you can make them behave like
112 one double speed connection using this driver. Naturally, this has
113 to be supported at the other end as well, either with a similar EQL
114 Linux driver or with a Livingston Portmaster 2e.
116 Say Y if you want this and read
117 <file:Documentation/networking/eql.txt>. You may also want to read
118 section 6.2 of the NET-3-HOWTO, available from
119 <http://www.tldp.org/docs.html#howto>.
121 To compile this driver as a module, choose M here: the module
122 will be called eql. If unsure, say N.
125 tristate "Universal TUN/TAP device driver support"
128 TUN/TAP provides packet reception and transmission for user space
129 programs. It can be viewed as a simple Point-to-Point or Ethernet
130 device, which instead of receiving packets from a physical media,
131 receives them from user space program and instead of sending packets
132 via physical media writes them to the user space program.
134 When a program opens /dev/net/tun, driver creates and registers
135 corresponding net device tunX or tapX. After a program closed above
136 devices, driver will automatically delete tunXX or tapXX device and
137 all routes corresponding to it.
139 Please read <file:Documentation/networking/tuntap.txt> for more
142 To compile this driver as a module, choose M here: the module
145 If you don't know what to use this for, you don't need it.
148 tristate "Virtual ethernet pair device"
150 This device is a local ethernet tunnel. Devices are created in pairs.
151 When one end receives the packet it appears on its pair and vice
155 tristate "General Instruments Surfboard 1000"
158 This is a driver for the General Instrument (also known as
159 NextLevel) SURFboard 1000 internal
160 cable modem. This is an ISA card which is used by a number of cable
161 TV companies to provide cable modem access. It's a one-way
162 downstream-only cable modem, meaning that your upstream net link is
163 provided by your regular phone modem.
165 At present this driver only compiles as a module, so say M here if
166 you have this card. The module will be called sb1000. Then read
167 <file:Documentation/networking/README.sb1000> for information on how
168 to use this module, as it needs special ppp scripts for establishing
169 a connection. Further documentation and the necessary scripts can be
172 <http://www.jacksonville.net/~fventuri/>
173 <http://home.adelphia.net/~siglercm/sb1000.html>
174 <http://linuxpower.cx/~cable/>
176 If you don't have this card, of course say N.
178 source "drivers/net/arcnet/Kconfig"
180 source "drivers/net/phy/Kconfig"
186 menuconfig NET_ETHERNET
187 bool "Ethernet (10 or 100Mbit)"
190 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
191 type of Local Area Network (LAN) in universities and companies.
193 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
194 coaxial cable, linking computers in a chain), 10BASE-T or twisted
195 pair (10 Mbps over twisted pair cable, linking computers to central
196 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
197 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
198 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
199 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
200 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
201 Ethernet (1 Gbps over optical fiber or short copper links).
203 If your Linux machine will be connected to an Ethernet and you have
204 an Ethernet network interface card (NIC) installed in your computer,
205 say Y here and read the Ethernet-HOWTO, available from
206 <http://www.tldp.org/docs.html#howto>. You will then also have
207 to say Y to the driver for your particular NIC.
209 Note that the answer to this question won't directly affect the
210 kernel: saying N will just cause the configurator to skip all
211 the questions about Ethernet network cards. If unsure, say N.
216 tristate "Generic Media Independent Interface device support"
218 Most ethernet controllers have MII transceiver either as an external
219 or internal device. It is safe to say Y or M here even if your
220 ethernet card lack MII.
223 tristate "Atmel MACB support"
224 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9
227 The Atmel MACB ethernet interface is found on many AT32 and AT91
228 parts. Say Y to include support for the MACB chip.
230 To compile this driver as a module, choose M here: the module
233 source "drivers/net/arm/Kconfig"
236 tristate "ASIX AX88796 NE2000 clone support"
237 depends on ARM || MIPS || SUPERH
241 AX88796 driver, using platform bus to provide
242 chip detection and resources
245 bool "ASIX AX88796 external 93CX6 eeprom support"
249 Select this if your platform comes with an external 93CX6 eeprom.
252 tristate "MACE (Power Mac ethernet) support"
253 depends on PPC_PMAC && PPC32
256 Power Macintoshes and clones with Ethernet built-in on the
257 motherboard will usually use a MACE (Medium Access Control for
258 Ethernet) interface. Say Y to include support for the MACE chip.
260 To compile this driver as a module, choose M here: the module
263 config MACE_AAUI_PORT
264 bool "Use AAUI port instead of TP by default"
267 Some Apple machines (notably the Apple Network Server) which use the
268 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
269 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
270 Y here if you have such a machine. If unsure, say N.
271 The driver will default to AAUI on ANS anyway, and if you use it as
272 a module, you can provide the port_aaui=0|1 to force the driver.
275 tristate "BMAC (G3 ethernet) support"
276 depends on PPC_PMAC && PPC32
279 Say Y for support of BMAC Ethernet interfaces. These are used on G3
282 To compile this driver as a module, choose M here: the module
286 tristate "Ariadne support"
289 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
292 To compile this driver as a module, choose M here: the module
293 will be called ariadne.
296 tristate "A2065 support"
300 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
303 To compile this driver as a module, choose M here: the module
304 will be called a2065.
307 tristate "Hydra support"
311 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
313 To compile this driver as a module, choose M here: the module
314 will be called hydra.
317 tristate "Zorro NS8390-based Ethernet support"
321 This driver is for Zorro Ethernet cards using an NS8390-compatible
322 chipset, like the Village Tronic Ariadne II and the Individual
323 Computers X-Surf Ethernet cards. If you have such a card, say Y.
326 To compile this driver as a module, choose M here: the module
327 will be called zorro8390.
330 tristate "PCMCIA NE2000 support"
331 depends on AMIGA_PCMCIA
334 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
337 To compile this driver as a module, choose M here: the module
341 bool "Macintosh NS 8390 based ethernet cards"
345 If you want to include a driver to support Nubus or LC-PDS
346 Ethernet cards using an NS8390 chipset or its equivalent, say Y
347 and read the Ethernet-HOWTO, available from
348 <http://www.tldp.org/docs.html#howto>.
351 tristate "Macintosh CS89x0 based ethernet cards"
354 Support for CS89x0 chipset based Ethernet cards. If you have a
355 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
356 read the Ethernet-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>.
359 To compile this driver as a module, choose M here. This module will
363 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
366 Support for NatSemi SONIC based Ethernet devices. This includes
367 the onboard Ethernet in many Quadras as well as some LC-PDS,
368 a few Nubus and all known Comm Slot Ethernet cards. If you have
369 one of these say Y and read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
372 To compile this driver as a module, choose M here. This module will
376 bool "Macintosh (AV) onboard MACE ethernet"
380 Support for the onboard AMD 79C940 MACE Ethernet controller used in
381 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
382 say Y and read the Ethernet-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>.
386 tristate "MVME147 (Lance) Ethernet support"
390 Support for the on-board Ethernet interface on the Motorola MVME147
391 single-board computer. Say Y here to include the
392 driver for this chip in your kernel.
393 To compile this driver as a module, choose M here.
396 tristate "MVME16x Ethernet support"
399 This is the driver for the Ethernet interface on the Motorola
400 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
401 driver for this chip in your kernel.
402 To compile this driver as a module, choose M here.
405 tristate "BVME6000 Ethernet support"
408 This is the driver for the Ethernet interface on BVME4000 and
409 BVME6000 VME boards. Say Y here to include the driver for this chip
411 To compile this driver as a module, choose M here.
414 tristate "Atari Lance support"
417 Say Y to include support for several Atari Ethernet adapters based
418 on the AMD Lance chipset: RieblCard (with or without battery), or
419 PAMCard VME (also the version by Rhotron, with different addresses).
422 tristate "Sun3/Sun3x on-board LANCE support"
423 depends on SUN3 || SUN3X
425 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
426 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
427 here to compile in the Linux driver for this and enable Ethernet.
428 General Linux information on the Sun 3 and 3x series (now
430 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
432 If you're not building a kernel for a Sun 3, say N.
435 bool "Sun3 on-board Intel 82586 support"
438 This driver enables support for the on-board Intel 82586 based
439 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
440 that this driver does not support 82586-based adapters on additional
444 bool "HP on-board LANCE support"
448 If you want to use the builtin "LANCE" Ethernet controller on an
449 HP300 machine, say Y here.
452 tristate "Lasi ethernet"
455 Say Y here to support the builtin Intel 82596 ethernet controller
456 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
459 tristate "SNI RM ethernet"
460 depends on NET_ETHERNET && SNI_RM
462 Say Y here to support the on-board Intel 82596 ethernet controller
463 built into SNI RM machines.
466 tristate "Korina (IDT RC32434) Ethernet support"
467 depends on NET_ETHERNET && MIKROTIK_RB532
469 If you have a Mikrotik RouterBoard 500 or IDT RC32434
470 based system say Y. Otherwise say N.
472 config MIPS_JAZZ_SONIC
473 tristate "MIPS JAZZ onboard SONIC Ethernet support"
476 This is the driver for the onboard card of MIPS Magnum 4000,
477 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
479 config XTENSA_XT2000_SONIC
480 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
481 depends on XTENSA_PLATFORM_XT2000
483 This is the driver for the onboard card of the Xtensa XT2000 board.
485 config MIPS_AU1X00_ENET
486 tristate "MIPS AU1000 Ethernet support"
487 depends on MIPS_ALCHEMY
491 If you have an Alchemy Semi AU1X00 based system
492 say Y. Otherwise, say N.
495 bool "SGI IOC3 Ethernet"
496 depends on PCI && SGI_IP27
500 If you have a network (Ethernet) card of this type, say Y and read
501 the Ethernet-HOWTO, available from
502 <http://www.tldp.org/docs.html#howto>.
505 tristate "MIPS simulator Network device"
508 The MIPSNET device is a simple Ethernet network device which is
509 emulated by the MIPS Simulator.
510 If you are not using a MIPSsim or are unsure, say N.
512 config SGI_O2MACE_ETH
513 tristate "SGI O2 MACE Fast Ethernet support"
514 depends on SGI_IP32=y
517 tristate "National DP83902AV support"
521 Support for cards based on the National Semiconductor DP83902AV
522 ST-NIC Serial Network Interface Controller for Twisted Pair. This
523 is a 10Mbit/sec Ethernet controller. Product overview and specs at
524 <http://www.national.com/pf/DP/DP83902A.html>.
529 tristate "Renesas SuperH Ethernet support"
530 depends on SUPERH && \
531 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
532 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
533 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
539 Renesas SuperH Ethernet device driver.
540 This driver supporting CPUs are:
541 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
544 tristate "Sun LANCE support"
548 This driver supports the "le" interface present on all 32-bit Sparc
549 systems, on some older Ultra systems and as an Sbus option. These
550 cards are based on the AMD Lance chipset, which is better known
551 via the NE2100 cards.
553 To compile this driver as a module, choose M here: the module
554 will be called sunlance.
557 tristate "Sun Happy Meal 10/100baseT support"
558 depends on SBUS || PCI
561 This driver supports the "hme" interface present on most Ultra
562 systems and as an option on older Sbus systems. This driver supports
563 both PCI and Sbus devices. This driver also supports the "qfe" quad
564 100baseT device available in both PCI and Sbus configurations.
566 To compile this driver as a module, choose M here: the module
567 will be called sunhme.
570 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
571 depends on SBUS && EXPERIMENTAL
574 This driver supports the "be" interface available as an Sbus option.
575 This is Sun's older 100baseT Ethernet device.
577 To compile this driver as a module, choose M here: the module
578 will be called sunbmac.
581 tristate "Sun QuadEthernet support"
585 This driver supports the "qe" 10baseT Ethernet device, available as
586 an Sbus option. Note that this is not the same as Quad FastEthernet
587 "qfe" which is supported by the Happy Meal driver instead.
589 To compile this driver as a module, choose M here: the module
590 will be called sunqe.
593 tristate "Sun GEM support"
597 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
598 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
601 tristate "Sun Cassini support"
605 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
606 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
609 tristate "Sun Virtual Network support"
612 Support for virtual network devices under Sun Logical Domains.
614 config NET_VENDOR_3COM
616 depends on ISA || EISA || MCA || PCI
618 If you have a network (Ethernet) card belonging to this class, say Y
619 and read the Ethernet-HOWTO, available from
620 <http://www.tldp.org/docs.html#howto>.
622 Note that the answer to this question doesn't directly affect the
623 kernel: saying N will just cause the configurator to skip all
624 the questions about 3COM cards. If you say Y, you will be asked for
625 your specific card in the following questions.
628 tristate "3c501 \"EtherLink\" support"
629 depends on NET_VENDOR_3COM && ISA
631 If you have a network (Ethernet) card of this type, say Y and read
632 the Ethernet-HOWTO, available from
633 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
634 new card, since the 3c501 is slow, broken, and obsolete: you will
635 have problems. Some people suggest to ping ("man ping") a nearby
636 machine every minute ("man cron") when using this card.
638 To compile this driver as a module, choose M here. The module
639 will be called 3c501.
642 tristate "3c503 \"EtherLink II\" support"
643 depends on NET_VENDOR_3COM && ISA
646 If you have a network (Ethernet) card of this type, say Y and read
647 the Ethernet-HOWTO, available from
648 <http://www.tldp.org/docs.html#howto>.
650 To compile this driver as a module, choose M here. The module
651 will be called 3c503.
654 tristate "3c505 \"EtherLink Plus\" support"
655 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
657 Information about this network (Ethernet) card can be found in
658 <file:Documentation/networking/3c505.txt>. If you have a card of
659 this type, say Y and read the Ethernet-HOWTO, available from
660 <http://www.tldp.org/docs.html#howto>.
662 To compile this driver as a module, choose M here. The module
663 will be called 3c505.
666 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
667 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
669 If you have a network (Ethernet) card of this type, say Y and read
670 the Ethernet-HOWTO, available from
671 <http://www.tldp.org/docs.html#howto>.
673 To compile this driver as a module, choose M here. The module
674 will be called 3c507.
677 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
678 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
680 If you have a network (Ethernet) card belonging to the 3Com
681 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
682 from <http://www.tldp.org/docs.html#howto>.
684 If your card is not working you may need to use the DOS
685 setup disk to disable Plug & Play mode, and to select the default
688 To compile this driver as a module, choose M here. The module
689 will be called 3c509.
692 tristate "3c515 ISA \"Fast EtherLink\""
693 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
695 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
696 network card, say Y and read the Ethernet-HOWTO, available from
697 <http://www.tldp.org/docs.html#howto>.
699 To compile this driver as a module, choose M here. The module
700 will be called 3c515.
703 tristate "3c523 \"EtherLink/MC\" support"
704 depends on NET_VENDOR_3COM && MCA_LEGACY
706 If you have a network (Ethernet) card of this type, say Y and read
707 the Ethernet-HOWTO, available from
708 <http://www.tldp.org/docs.html#howto>.
710 To compile this driver as a module, choose M here. The module
711 will be called 3c523.
714 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
715 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
717 If you have a network (Ethernet) card of this type, say Y and read
718 the Ethernet-HOWTO, available from
719 <http://www.tldp.org/docs.html#howto>.
721 To compile this driver as a module, choose M here. The module
722 will be called 3c527.
725 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
726 depends on NET_VENDOR_3COM && (PCI || EISA)
729 This option enables driver support for a large number of 10Mbps and
730 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
732 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
733 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
734 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
735 "Tornado" (3c905) PCI
736 "Hurricane" (3c555/3cSOHO) PCI
738 If you have such a card, say Y and read the Ethernet-HOWTO,
739 available from <http://www.tldp.org/docs.html#howto>. More
740 specific information is in
741 <file:Documentation/networking/vortex.txt> and in the comments at
742 the beginning of <file:drivers/net/3c59x.c>.
744 To compile this support as a module, choose M here.
747 tristate "3cr990 series \"Typhoon\" support"
748 depends on NET_VENDOR_3COM && PCI
751 This option enables driver support for the 3cr990 series of cards:
753 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
754 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
755 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
757 If you have a network (Ethernet) card of this type, say Y and read
758 the Ethernet-HOWTO, available from
759 <http://www.tldp.org/docs.html#howto>.
761 To compile this driver as a module, choose M here. The module
762 will be called typhoon.
765 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
766 depends on ISA && ISA_DMA_API
768 If you have a network (Ethernet) card of this type, say Y and read
769 the Ethernet-HOWTO, available from
770 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
773 To compile this driver as a module, choose M here: the module
774 will be called lance. This is recommended.
776 config NET_VENDOR_SMC
777 bool "Western Digital/SMC cards"
778 depends on ISA || MCA || EISA || MAC
780 If you have a network (Ethernet) card belonging to this class, say Y
781 and read the Ethernet-HOWTO, available from
782 <http://www.tldp.org/docs.html#howto>.
784 Note that the answer to this question doesn't directly affect the
785 kernel: saying N will just cause the configurator to skip all
786 the questions about Western Digital cards. If you say Y, you will be
787 asked for your specific card in the following questions.
790 tristate "WD80*3 support"
791 depends on NET_VENDOR_SMC && ISA
794 If you have a network (Ethernet) card of this type, say Y and read
795 the Ethernet-HOWTO, available from
796 <http://www.tldp.org/docs.html#howto>.
798 To compile this driver as a module, choose M here. The module
802 tristate "SMC Ultra MCA support"
803 depends on NET_VENDOR_SMC && MCA
806 If you have a network (Ethernet) card of this type and are running
807 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
808 available from <http://www.tldp.org/docs.html#howto>.
810 To compile this driver as a module, choose M here. The module
811 will be called smc-mca.
814 tristate "SMC Ultra support"
815 depends on NET_VENDOR_SMC && ISA
818 If you have a network (Ethernet) card of this type, say Y and read
819 the Ethernet-HOWTO, available from
820 <http://www.tldp.org/docs.html#howto>.
822 Important: There have been many reports that, with some motherboards
823 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
824 such as some BusLogic models) causes corruption problems with many
825 operating systems. The Linux smc-ultra driver has a work-around for
826 this but keep it in mind if you have such a SCSI card and have
829 To compile this driver as a module, choose M here. The module
830 will be called smc-ultra.
833 tristate "SMC Ultra32 EISA support"
834 depends on NET_VENDOR_SMC && EISA
837 If you have a network (Ethernet) card of this type, say Y and read
838 the Ethernet-HOWTO, available from
839 <http://www.tldp.org/docs.html#howto>.
841 To compile this driver as a module, choose M here. The module
842 will be called smc-ultra32.
845 tristate "Blackfin on-chip MAC support"
846 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
850 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
852 This is the driver for Blackfin on-chip mac device. Say Y if you want it
853 compiled into the kernel. This driver is also available as a module
854 ( = code which can be inserted in and removed from the running kernel
855 whenever you want). The module will be called bfin_mac.
857 config BFIN_MAC_USE_L1
858 bool "Use L1 memory for rx/tx packets"
859 depends on BFIN_MAC && (BF527 || BF537)
862 To get maximum network performance, you should use L1 memory as rx/tx buffers.
863 Say N here if you want to reserve L1 memory for other uses.
865 config BFIN_TX_DESC_NUM
866 int "Number of transmit buffer packets"
868 range 6 10 if BFIN_MAC_USE_L1
872 Set the number of buffer packets used in driver.
874 config BFIN_RX_DESC_NUM
875 int "Number of receive buffer packets"
877 range 20 100 if BFIN_MAC_USE_L1
881 Set the number of buffer packets used in driver.
884 bool "RMII PHY Interface"
886 default y if BFIN527_EZKIT
887 default n if BFIN537_STAMP
889 Use Reduced PHY MII Interface
891 config BFIN_MAC_USE_HWSTAMP
892 bool "Use IEEE 1588 hwstamp"
893 depends on BFIN_MAC && BF518
896 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
899 tristate "SMC 9194 support"
900 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
903 This is support for the SMC9xxx based Ethernet cards. Choose this
904 option if you have a DELL laptop with the docking station, or
905 another SMC9192/9194 based chipset. Say Y if you want it compiled
906 into the kernel, and read the file
907 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
908 available from <http://www.tldp.org/docs.html#howto>.
910 To compile this driver as a module, choose M here. The module
911 will be called smc9194.
914 tristate "SMC 91C9x/91C1xxx support"
917 depends on ARM || M32R || SUPERH || \
918 MIPS || BLACKFIN || MN10300 || COLDFIRE
920 This is a driver for SMC's 91x series of Ethernet chipsets,
921 including the SMC91C94 and the SMC91C111. Say Y if you want it
922 compiled into the kernel, and read the file
923 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
924 available from <http://www.linuxdoc.org/docs.html#howto>.
926 This driver is also available as a module ( = code which can be
927 inserted in and removed from the running kernel whenever you want).
928 The module will be called smc91x. If you want to compile it as a
929 module, say M here and read <file:Documentation/kbuild/modules.txt>.
932 tristate "NetX Ethernet support"
936 This is support for the Hilscher netX builtin Ethernet ports
938 To compile this driver as a module, choose M here. The module
939 will be called netx-eth.
941 config TI_DAVINCI_EMAC
942 tristate "TI DaVinci EMAC Support"
943 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
946 This driver supports TI's DaVinci Ethernet .
948 To compile this driver as a module, choose M here: the module
949 will be called davinci_emac_driver. This is recommended.
952 tristate "DM9000 support"
953 depends on ARM || BLACKFIN || MIPS
957 Support for DM9000 chipset.
959 To compile this driver as a module, choose M here. The module
960 will be called dm9000.
962 config DM9000_DEBUGLEVEL
963 int "DM9000 maximum debug level"
967 The maximum level of debugging code compiled into the DM9000
970 config DM9000_FORCE_SIMPLE_PHY_POLL
971 bool "Force simple NSR based PHY polling"
974 This configuration forces the DM9000 to use the NSR's LinkStatus
975 bit to determine if the link is up or down instead of the more
976 costly MII PHY reads. Note, this will not work if the chip is
977 operating with an external PHY.
980 tristate "ENC28J60 support"
981 depends on EXPERIMENTAL && SPI && NET_ETHERNET
984 Support for the Microchip EN28J60 ethernet chip.
986 To compile this driver as a module, choose M here. The module will be
989 config ENC28J60_WRITEVERIFY
990 bool "Enable write verify"
993 Enable the verify after the buffer write useful for debugging purpose.
997 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
998 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1004 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1007 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1012 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1015 tristate "SMSC LAN911[5678] support"
1018 depends on ARM || SUPERH
1020 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1021 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1022 Say Y if you want it compiled into the kernel,
1023 and read the Ethernet-HOWTO, available from
1024 <http://www.linuxdoc.org/docs.html#howto>.
1026 This driver is also available as a module. The module will be
1027 called smc911x. If you want to compile it as a module, say M
1028 here and read <file:Documentation/kbuild/modules.txt>
1031 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1032 depends on ARM || SUPERH || BLACKFIN || MIPS
1037 Say Y here if you want support for SMSC LAN911x and LAN921x families
1038 of ethernet controllers.
1040 To compile this driver as a module, choose M here and read
1041 <file:Documentation/networking/net-modules.txt>. The module
1042 will be called smsc911x.
1044 config NET_VENDOR_RACAL
1045 bool "Racal-Interlan (Micom) NI cards"
1048 If you have a network (Ethernet) card belonging to this class, such
1049 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1050 available from <http://www.tldp.org/docs.html#howto>.
1052 Note that the answer to this question doesn't directly affect the
1053 kernel: saying N will just cause the configurator to skip all
1054 the questions about NI cards. If you say Y, you will be asked for
1055 your specific card in the following questions.
1058 tristate "NI5010 support (EXPERIMENTAL)"
1059 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1061 If you have a network (Ethernet) card of this type, say Y and read
1062 the Ethernet-HOWTO, available from
1063 <http://www.tldp.org/docs.html#howto>. Note that this is still
1066 To compile this driver as a module, choose M here. The module
1067 will be called ni5010.
1070 tristate "NI5210 support"
1071 depends on NET_VENDOR_RACAL && ISA
1073 If you have a network (Ethernet) card of this type, say Y and read
1074 the Ethernet-HOWTO, available from
1075 <http://www.tldp.org/docs.html#howto>.
1077 To compile this driver as a module, choose M here. The module
1078 will be called ni52.
1081 tristate "NI6510 support"
1082 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1084 If you have a network (Ethernet) card of this type, say Y and read
1085 the Ethernet-HOWTO, available from
1086 <http://www.tldp.org/docs.html#howto>.
1088 To compile this driver as a module, choose M here. The module
1089 will be called ni65.
1092 tristate "Dave ethernet support (DNET)"
1093 depends on NET_ETHERNET && HAS_IOMEM
1096 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1097 Say Y to include support for the DNET chip.
1099 To compile this driver as a module, choose M here: the module
1100 will be called dnet.
1102 source "drivers/net/tulip/Kconfig"
1105 tristate "AT1700/1720 support (EXPERIMENTAL)"
1106 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
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 at1700.
1117 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1118 depends on ISA || EISA || MCA
1121 If you have a network (Ethernet) card of this type, say Y and read
1122 the Ethernet-HOWTO, available from
1123 <http://www.tldp.org/docs.html#howto> as well as
1124 <file:drivers/net/depca.c>.
1126 To compile this driver as a module, choose M here. The module
1127 will be called depca.
1130 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1131 depends on ISA || EISA || PCI
1133 If you have a network (Ethernet) card of this type, say Y and read
1134 the Ethernet-HOWTO, available from
1135 <http://www.tldp.org/docs.html#howto>.
1137 To compile this driver as a module, choose M here. The module
1138 will be called hp100.
1141 bool "Other ISA cards"
1144 If your network (Ethernet) card hasn't been mentioned yet and its
1145 bus system (that's the way the cards talks to the other components
1146 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1147 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1148 available from <http://www.tldp.org/docs.html#howto>.
1152 Note that the answer to this question doesn't directly affect the
1153 kernel: saying N will just cause the configurator to skip all
1154 the remaining ISA network card questions. If you say Y, you will be
1155 asked for your specific card in the following questions.
1158 tristate "Cabletron E21xx support"
1162 If you have a network (Ethernet) card of this type, say Y and read
1163 the Ethernet-HOWTO, available from
1164 <http://www.tldp.org/docs.html#howto>.
1166 To compile this driver as a module, choose M here. The module
1167 will be called e2100.
1170 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1174 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1175 cards. If this is for you, say Y and read
1176 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1177 well as the Ethernet-HOWTO, available from
1178 <http://www.tldp.org/docs.html#howto>.
1180 To compile this driver as a module, choose M here. The module
1181 will be called ewrk3.
1184 tristate "EtherExpress 16 support"
1187 If you have an EtherExpress16 network (Ethernet) card, say Y and
1188 read the Ethernet-HOWTO, available from
1189 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1190 EtherExpress16 card used to be regarded as a very poor choice
1191 because the driver was very unreliable. We now have a new driver
1192 that should do better.
1194 To compile this driver as a module, choose M here. The module
1195 will be called eexpress.
1198 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1201 If you have a network (Ethernet) card of this type, say Y. This
1202 driver supports Intel i82595{FX,TX} based boards. Note however
1203 that the EtherExpress PRO/100 Ethernet card has its own separate
1204 driver. Please read the Ethernet-HOWTO, available from
1205 <http://www.tldp.org/docs.html#howto>.
1207 To compile this driver as a module, choose M here. The module
1208 will be called eepro.
1211 tristate "HP PCLAN+ (27247B and 27252A) support"
1215 If you have a network (Ethernet) card of this type, say Y and read
1216 the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here. The module
1220 will be called hp-plus.
1223 tristate "HP PCLAN (27245 and other 27xxx series) support"
1227 If you have a network (Ethernet) card of this type, say Y and read
1228 the Ethernet-HOWTO, available from
1229 <http://www.tldp.org/docs.html#howto>.
1231 To compile this driver as a module, choose M here. The module
1235 tristate "LP486E on board Ethernet"
1238 Say Y here to support the 82596-based on-board Ethernet controller
1239 for the Panther motherboard, which is one of the two shipped in the
1240 Intel Professional Workstation.
1243 tristate "ICL EtherTeam 16i/32 support"
1246 If you have a network (Ethernet) card of this type, say Y and read
1247 the Ethernet-HOWTO, available from
1248 <http://www.tldp.org/docs.html#howto>.
1250 To compile this driver as a module, choose M here. The module
1251 will be called eth16i.
1254 tristate "NE2000/NE1000 support"
1255 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1258 If you have a network (Ethernet) card of this type, say Y and read
1259 the Ethernet-HOWTO, available from
1260 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1261 without a specific driver are compatible with NE2000.
1263 If you have a PCI NE2000 card however, say N here and Y to "PCI
1264 NE2000 and clone support" under "EISA, VLB, PCI and on board
1265 controllers" below. If you have a NE2000 card and are running on
1266 an MCA system (a bus system used on some IBM PS/2 computers and
1267 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1270 To compile this driver as a module, choose M here. The module
1274 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1275 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1277 The Zenith Z-Note notebook computer has a built-in network
1278 (Ethernet) card, and this is the Linux driver for it. Note that the
1279 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1280 by this driver. Read the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1284 tristate "SEEQ8005 support (EXPERIMENTAL)"
1285 depends on NET_ISA && EXPERIMENTAL
1287 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1288 is for you, read the Ethernet-HOWTO, available from
1289 <http://www.tldp.org/docs.html#howto>.
1291 To compile this driver as a module, choose M here. The module
1292 will be called seeq8005.
1295 tristate "NE/2 (ne2000 MCA version) support"
1296 depends on MCA_LEGACY
1299 If you have a network (Ethernet) card of this type, say Y and read
1300 the Ethernet-HOWTO, available from
1301 <http://www.tldp.org/docs.html#howto>.
1303 To compile this driver as a module, choose M here. The module
1307 tristate "IBM LAN Adapter/A support"
1310 This is a Micro Channel Ethernet adapter. You need to set
1311 CONFIG_MCA to use this driver. It is both available as an in-kernel
1312 driver and as a module.
1314 To compile this driver as a module, choose M here. The only
1315 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1316 will both support 16K and 32K memory windows, however a 32K window
1317 gives a better security against packet losses. Usage of multiple
1318 boards with this driver should be possible, but has not been tested
1319 up to now due to lack of hardware.
1322 tristate "IBM LAN Virtual Ethernet support"
1323 depends on PPC_PSERIES
1325 This driver supports virtual ethernet adapters on newer IBM iSeries
1326 and pSeries systems.
1328 To compile this driver as a module, choose M here. The module will
1331 source "drivers/net/ibm_newemac/Kconfig"
1334 bool "EISA, VLB, PCI and on board controllers"
1335 depends on ISA || EISA || PCI
1337 This is another class of network cards which attach directly to the
1338 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1339 available from <http://www.tldp.org/docs.html#howto>.
1341 Note that the answer to this question doesn't directly affect the
1342 kernel: saying N will just cause the configurator to skip all
1343 the questions about this class of network cards. If you say Y, you
1344 will be asked for your specific card in the following questions. If
1345 you are unsure, say Y.
1348 tristate "AMD PCnet32 PCI support"
1349 depends on NET_PCI && PCI
1353 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1354 answer Y here and read the Ethernet-HOWTO, available from
1355 <http://www.tldp.org/docs.html#howto>.
1357 To compile this driver as a module, choose M here. The module
1358 will be called pcnet32.
1361 tristate "AMD 8111 (new PCI lance) support"
1362 depends on NET_PCI && PCI
1366 If you have an AMD 8111-based PCI lance ethernet card,
1367 answer Y here and read the Ethernet-HOWTO, available from
1368 <http://www.tldp.org/docs.html#howto>.
1370 To compile this driver as a module, choose M here. The module
1371 will be called amd8111e.
1373 config ADAPTEC_STARFIRE
1374 tristate "Adaptec Starfire/DuraLAN support"
1375 depends on NET_PCI && PCI
1379 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1380 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1381 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1384 To compile this driver as a module, choose M here: the module
1385 will be called starfire. This is recommended.
1388 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1389 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1392 If you have a network (Ethernet) card of this type, say Y and read
1393 the Ethernet-HOWTO, available from
1394 <http://www.tldp.org/docs.html#howto>.
1396 To compile this driver as a module, choose M here. The module
1397 will be called ac3200.
1400 tristate "Micrel KSZ8841/2 PCI"
1401 depends on NET_PCI && PCI
1405 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1407 To compile this driver as a module, choose M here. The module
1408 will be called ksz884x.
1411 tristate "Apricot Xen-II on board Ethernet"
1412 depends on NET_PCI && ISA
1414 If you have a network (Ethernet) controller of this type, say Y and
1415 read the Ethernet-HOWTO, available from
1416 <http://www.tldp.org/docs.html#howto>.
1418 To compile this driver as a module, choose M here. The module
1419 will be called apricot.
1422 tristate "Broadcom 440x/47xx ethernet support"
1423 depends on SSB_POSSIBLE && HAS_DMA
1427 If you have a network (Ethernet) controller of this type, say Y
1428 or M and read the Ethernet-HOWTO, available from
1429 <http://www.tldp.org/docs.html#howto>.
1431 To compile this driver as a module, choose M here. The module
1434 # Auto-select SSB PCI-HOST support, if possible
1435 config B44_PCI_AUTOSELECT
1437 depends on B44 && SSB_PCIHOST_POSSIBLE
1441 # Auto-select SSB PCICORE driver, if possible
1442 config B44_PCICORE_AUTOSELECT
1444 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1445 select SSB_DRIVER_PCICORE
1450 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1454 tristate "nForce Ethernet support"
1455 depends on NET_PCI && PCI
1457 If you have a network (Ethernet) controller of this type, say Y and
1458 read the Ethernet-HOWTO, available from
1459 <http://www.tldp.org/docs.html#howto>.
1461 To compile this driver as a module, choose M here. The module
1462 will be called forcedeth.
1465 tristate "CS89x0 support"
1466 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1467 || ARCH_IXDP2X01 || MACH_MX31ADS)
1469 Support for CS89x0 chipset based Ethernet cards. If you have a
1470 network (Ethernet) card of this type, say Y and read the
1471 Ethernet-HOWTO, available from
1472 <http://www.tldp.org/docs.html#howto> as well as
1473 <file:Documentation/networking/cs89x0.txt>.
1475 To compile this driver as a module, choose M here. The module
1476 will be called cs89x0.
1478 config CS89x0_NONISA_IRQ
1480 depends on CS89x0 != n
1481 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS
1484 tristate "TOSHIBA TC35815 Ethernet support"
1485 depends on NET_PCI && PCI && MIPS
1489 tristate "Intel(R) PRO/100+ support"
1490 depends on NET_PCI && PCI
1493 This driver supports Intel(R) PRO/100 family of adapters.
1494 To verify that your adapter is supported, find the board ID number
1495 on the adapter. Look for a label that has a barcode and a number
1496 in the format 123456-001 (six digits hyphen three digits).
1498 Use the above information and the Adapter & Driver ID Guide at:
1500 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1502 to identify the adapter.
1504 For the latest Intel PRO/100 network driver for Linux, see:
1506 <http://appsr.intel.com/scripts-df/support_intel.asp>
1508 More specific information on configuring the driver is in
1509 <file:Documentation/networking/e100.txt>.
1511 To compile this driver as a module, choose M here. The module
1512 will be called e100.
1515 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1516 depends on NET_PCI && EISA && EXPERIMENTAL
1519 If you have a network (Ethernet) card of this type, say Y and read
1520 the Ethernet-HOWTO, available from
1521 <http://www.tldp.org/docs.html#howto>.
1523 To compile this driver as a module, choose M here. The module
1524 will be called lne390.
1527 tristate "Myson MTD-8xx PCI Ethernet support"
1528 depends on NET_PCI && PCI
1532 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1533 cards. Specifications and data at
1534 <http://www.myson.com.hk/mtd/datasheet/>.
1537 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1538 depends on NET_PCI && PCI
1541 This driver is for the National Semiconductor DP83810 series,
1542 which is used in cards from PureData, NetGear, Linksys
1543 and others, including the 83815 chip.
1544 More specific information and updates are available from
1545 <http://www.scyld.com/network/natsemi.html>.
1548 tristate "PCI NE2000 and clones support (see help)"
1549 depends on NET_PCI && PCI
1552 This driver is for NE2000 compatible PCI cards. It will not work
1553 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1554 support" below). If you have a PCI NE2000 network (Ethernet) card,
1555 say Y and read the Ethernet-HOWTO, available from
1556 <http://www.tldp.org/docs.html#howto>.
1558 This driver also works for the following NE2000 clone cards:
1559 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1560 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1561 Holtek HT80232 Holtek HT80229
1563 To compile this driver as a module, choose M here. The module
1564 will be called ne2k-pci.
1567 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1568 depends on NET_PCI && EISA && EXPERIMENTAL
1571 If you have a network (Ethernet) card of this type, say Y and read
1572 the Ethernet-HOWTO, available from
1573 <http://www.tldp.org/docs.html#howto>. Note that this driver
1574 will NOT WORK for NE3200 cards as they are completely different.
1576 To compile this driver as a module, choose M here. The module
1577 will be called ne3210.
1580 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1581 depends on NET_PCI && EISA && EXPERIMENTAL
1584 If you have a network (Ethernet) card of this type, say Y and read
1585 the Ethernet-HOWTO, available from
1586 <http://www.tldp.org/docs.html#howto>.
1588 To compile this driver as a module, choose M here. The module
1589 will be called es3210.
1592 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1593 depends on NET_PCI && PCI && EXPERIMENTAL
1597 This is a driver for the Fast Ethernet PCI network cards based on
1598 the RTL8139C+ chips. If you have one of those, say Y and read
1599 the Ethernet-HOWTO, available from
1600 <http://www.tldp.org/docs.html#howto>.
1602 To compile this driver as a module, choose M here: the module
1603 will be called 8139cp. This is recommended.
1606 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1607 depends on NET_PCI && PCI
1611 This is a driver for the Fast Ethernet PCI network cards based on
1612 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1613 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1615 To compile this driver as a module, choose M here: the module
1616 will be called 8139too. This is recommended.
1619 bool "Use PIO instead of MMIO"
1623 This instructs the driver to use programmed I/O ports (PIO) instead
1624 of PCI shared memory (MMIO). This can possibly solve some problems
1625 in case your mainboard has memory consistency issues. If unsure,
1628 config 8139TOO_TUNE_TWISTER
1629 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1632 This implements a function which might come in handy in case you
1633 are using low quality on long cabling. It is required for RealTek
1634 RTL-8139 revision K boards, and totally unused otherwise. It tries
1635 to match the transceiver to the cable characteristics. This is
1636 experimental since hardly documented by the manufacturer.
1640 bool "Support for older RTL-8129/8130 boards"
1643 This enables support for the older and uncommon RTL-8129 and
1644 RTL-8130 chips, which support MII via an external transceiver,
1645 instead of an internal one. Disabling this option will save some
1646 memory by making the code size smaller. If unsure, say Y.
1648 config 8139_OLD_RX_RESET
1649 bool "Use older RX-reset method"
1652 The 8139too driver was recently updated to contain a more rapid
1653 reset sequence, in the face of severe receive errors. This "new"
1654 RX-reset method should be adequate for all boards. But if you
1655 experience problems, you can enable this option to restore the
1656 old RX-reset behavior. If unsure, say N.
1659 tristate "RDC R6040 Fast Ethernet Adapter support"
1660 depends on NET_PCI && PCI
1665 This is a driver for the R6040 Fast Ethernet MACs found in the
1666 the RDC R-321x System-on-chips.
1668 To compile this driver as a module, choose M here: the module
1669 will be called r6040. This is recommended.
1672 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1673 depends on NET_PCI && PCI
1677 This is a driver for the Fast Ethernet PCI network cards based on
1678 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1679 SiS 630 and SiS 540 chipsets.
1681 This driver also supports AMD 79C901 HomePNA so that you can use
1682 your phone line as a network cable.
1684 To compile this driver as a module, choose M here: the module
1685 will be called sis900. This is recommended.
1688 tristate "SMC EtherPower II"
1689 depends on NET_PCI && PCI
1693 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1694 which is based on the SMC83c17x (EPIC/100).
1695 More specific information and updates are available from
1696 <http://www.scyld.com/network/epic100.html>.
1699 tristate "SMSC LAN9420 PCI ethernet adapter support"
1700 depends on NET_PCI && PCI
1705 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1706 Say Y if you want it compiled into the kernel,
1707 and read the Ethernet-HOWTO, available from
1708 <http://www.linuxdoc.org/docs.html#howto>.
1710 This driver is also available as a module. The module will be
1711 called smsc9420. If you want to compile it as a module, say M
1712 here and read <file:Documentation/kbuild/modules.txt>
1715 tristate "Sundance Alta support"
1716 depends on NET_PCI && PCI
1720 This driver is for the Sundance "Alta" chip.
1721 More specific information and updates are available from
1722 <http://www.scyld.com/network/sundance.html>.
1724 config SUNDANCE_MMIO
1725 bool "Use MMIO instead of PIO"
1728 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1729 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1730 is known to solve bugs on certain chips.
1735 tristate "TI ThunderLAN support"
1736 depends on NET_PCI && (PCI || EISA)
1738 If you have a PCI Ethernet network card based on the ThunderLAN chip
1739 which is supported by this driver, say Y and read the
1740 Ethernet-HOWTO, available from
1741 <http://www.tldp.org/docs.html#howto>.
1743 Devices currently supported by this driver are Compaq Netelligent,
1744 Compaq NetFlex and Olicom cards. Please read the file
1745 <file:Documentation/networking/tlan.txt> for more details.
1747 To compile this driver as a module, choose M here. The module
1748 will be called tlan.
1750 Please email feedback to <torben.mathiasen@compaq.com>.
1753 tristate "Micrel KSZ8841/42 with generic bus interface"
1754 depends on HAS_IOMEM && DMA_ENGINE
1756 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1757 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1761 tristate "Micrel KS8851 SPI"
1766 SPI driver for Micrel KS8851 SPI attached network chip.
1769 tristate "Micrel KS8851 MLL"
1770 depends on HAS_IOMEM
1773 This platform driver is for Micrel KS8851 Address/data bus
1774 multiplexed network chip.
1777 tristate "VIA Rhine support"
1778 depends on NET_PCI && PCI
1782 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1783 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1784 Ethernet functions can also be found integrated on South Bridges
1787 To compile this driver as a module, choose M here. The module
1788 will be called via-rhine.
1790 config VIA_RHINE_MMIO
1791 bool "Use MMIO instead of PIO"
1792 depends on VIA_RHINE
1794 This instructs the driver to use PCI shared memory (MMIO) instead of
1795 programmed I/O ports (PIO). Enabling this gives an improvement in
1796 processing time in parts of the driver.
1801 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1802 depends on NET_PCI && PCI && EXPERIMENTAL
1805 This is a driver for the Fast Ethernet PCI network cards based on
1806 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1807 have one of these, say Y here.
1809 To compile this driver as a module, choose M here: the module
1810 will be called sc92031. This is recommended.
1813 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1814 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1817 TI AR7 CPMAC Ethernet support
1820 bool "Pocket and portable adapters"
1823 Cute little network (Ethernet) devices which attach to the parallel
1824 port ("pocket adapters"), commonly used with laptops. If you have
1825 one of those, say Y and read the Ethernet-HOWTO, available from
1826 <http://www.tldp.org/docs.html#howto>.
1828 If you want to plug a network (or some other) card into the PCMCIA
1829 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1830 credit card size extension cards used by all modern laptops), you
1831 need the pcmcia-cs package (location contained in the file
1832 <file:Documentation/Changes>) and you can say N here.
1834 Laptop users should read the Linux Laptop home page at
1835 <http://www.linux-on-laptops.com/> or
1836 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1838 Note that the answer to this question doesn't directly affect the
1839 kernel: saying N will just cause the configurator to skip all
1840 the questions about this class of network devices. If you say Y, you
1841 will be asked for your specific device in the following questions.
1844 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1845 depends on NET_POCKET && PARPORT && X86
1848 This is a network (Ethernet) device which attaches to your parallel
1849 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1850 available from <http://www.tldp.org/docs.html#howto>, if you
1851 want to use this. If you intend to use this driver, you should have
1852 said N to the "Parallel printer support", because the two drivers
1853 don't like each other.
1855 To compile this driver as a module, choose M here: the module
1859 tristate "D-Link DE600 pocket adapter support"
1860 depends on NET_POCKET && PARPORT
1862 This is a network (Ethernet) device which attaches to your parallel
1863 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1864 Ethernet-HOWTO, available from
1865 <http://www.tldp.org/docs.html#howto>, if you want to use
1866 this. It is possible to have several devices share a single parallel
1867 port and it is safe to compile the corresponding drivers into the
1870 To compile this driver as a module, choose M here: the module
1871 will be called de600.
1874 tristate "D-Link DE620 pocket adapter support"
1875 depends on NET_POCKET && PARPORT
1877 This is a network (Ethernet) device which attaches to your parallel
1878 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1879 Ethernet-HOWTO, available from
1880 <http://www.tldp.org/docs.html#howto>, if you want to use
1881 this. It is possible to have several devices share a single parallel
1882 port and it is safe to compile the corresponding drivers into the
1885 To compile this driver as a module, choose M here: the module
1886 will be called de620.
1889 tristate "SGI Seeq ethernet controller support"
1890 depends on SGI_HAS_SEEQ
1892 Say Y here if you have an Seeq based Ethernet network card. This is
1893 used in many Silicon Graphics machines.
1896 tristate "DEC LANCE ethernet controller support"
1897 depends on MACH_DECSTATION
1900 This driver is for the series of Ethernet controllers produced by
1901 DEC (now Compaq) based on the AMD Lance chipset, including the
1902 DEPCA series. (This chipset is better known via the NE2100 cards.)
1905 bool "Motorola 68360 ethernet controller"
1908 Say Y here if you want to use the built-in ethernet controller of
1909 the Motorola 68360 processor.
1912 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1913 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1914 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1917 Say Y here if you want to use the built-in 10/100 Fast ethernet
1918 controller on some Motorola ColdFire and Freescale i.MX processors.
1921 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1924 Say Y here if you want to use the second built-in 10/100 Fast
1925 ethernet controller on some Motorola ColdFire processors.
1928 tristate "MPC52xx FEC driver"
1929 depends on PPC_MPC52xx && PPC_BESTCOMM
1932 select PPC_BESTCOMM_FEC
1934 This option enables support for the MPC5200's on-chip
1935 Fast Ethernet Controller
1936 If compiled as module, it will be called fec_mpc52xx.
1938 config FEC_MPC52xx_MDIO
1939 bool "MPC52xx FEC MDIO bus driver"
1940 depends on FEC_MPC52xx
1943 The MPC5200's FEC can connect to the Ethernet either with
1944 an external MII PHY chip or 10 Mbps 7-wire interface
1945 (Motorola? industry standard).
1946 If your board uses an external PHY connected to FEC, enable this.
1947 If not sure, enable.
1948 If compiled as module, it will be called fec_mpc52xx_phy.
1951 tristate "NE2000 compatible support for H8/300"
1954 Say Y here if you want to use the NE2000 compatible
1955 controller on the Renesas H8/300 processor.
1958 tristate "Atheros L2 Fast Ethernet support"
1963 This driver supports the Atheros L2 fast ethernet adapter.
1965 To compile this driver as a module, choose M here. The module
1966 will be called atl2.
1968 config XILINX_EMACLITE
1969 tristate "Xilinx 10/100 Ethernet Lite support"
1970 depends on PPC32 || MICROBLAZE
1973 This driver supports the 10/100 Ethernet Lite from Xilinx.
1976 tristate "Broadcom 63xx internal mac support"
1981 This driver supports the ethernet MACs in the Broadcom 63xx
1982 MIPS chipset family (BCM63XX).
1984 source "drivers/net/fs_enet/Kconfig"
1986 source "drivers/net/octeon/Kconfig"
1988 endif # NET_ETHERNET
1994 menuconfig NETDEV_1000
1995 bool "Ethernet (1000 Mbit)"
1999 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2000 type of Local Area Network (LAN) in universities and companies.
2002 Say Y here to get to see options for Gigabit Ethernet drivers.
2003 This option alone does not add any kernel code.
2004 Note that drivers supporting both 100 and 1000 MBit may be listed
2005 under "Ethernet (10 or 100MBit)" instead.
2007 If you say N, all options in this submenu will be skipped and disabled.
2012 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2015 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2016 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2017 adapter. The driver allows for using the Jumbo Frame option (9000
2018 bytes/frame) however it requires that your switches can handle this
2019 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2022 To compile this driver as a module, choose M here: the
2023 module will be called acenic.
2025 config ACENIC_OMIT_TIGON_I
2026 bool "Omit support for old Tigon I based AceNICs"
2029 Say Y here if you only have Tigon II based AceNICs and want to leave
2030 out support for the older Tigon I based cards which are no longer
2031 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2032 version)). This will reduce the size of the driver object by
2033 app. 100KB. If you are not sure whether your card is a Tigon I or a
2034 Tigon II, say N here.
2036 The safe and default value for this is N.
2039 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2043 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2045 D-Link DGE-550T Gigabit Ethernet Adapter.
2046 D-Link DL2000-based Gigabit Ethernet Adapter.
2047 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2049 To compile this driver as a module, choose M here: the
2050 module will be called dl2k.
2053 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2056 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2057 adapters. For more information on how to identify your adapter, go
2058 to the Adapter & Driver ID Guide at:
2060 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2062 For general information and support, go to the Intel support
2065 <http://support.intel.com>
2067 More specific information on configuring the driver is in
2068 <file:Documentation/networking/e1000.txt>.
2070 To compile this driver as a module, choose M here. The module
2071 will be called e1000.
2074 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2075 depends on PCI && (!SPARC32 || BROKEN)
2077 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2078 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2079 use the regular e1000 driver For more information on how to
2080 identify your adapter, go to the Adapter & Driver ID Guide at:
2082 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2084 For general information and support, go to the Intel support
2087 <http://support.intel.com>
2089 To compile this driver as a module, choose M here. The module
2090 will be called e1000e.
2093 tristate "IP1000 Gigabit Ethernet support"
2094 depends on PCI && EXPERIMENTAL
2097 This driver supports IP1000 gigabit Ethernet cards.
2099 To compile this driver as a module, choose M here: the module
2100 will be called ipg. This is recommended.
2103 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2106 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2107 adapters. For more information on how to identify your adapter, go
2108 to the Adapter & Driver ID Guide at:
2110 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2112 For general information and support, go to the Intel support
2115 <http://support.intel.com>
2117 More specific information on configuring the driver is in
2118 <file:Documentation/networking/e1000.txt>.
2120 To compile this driver as a module, choose M here. The module
2124 bool "Direct Cache Access (DCA) Support"
2126 depends on IGB && DCA && !(IGB=y && DCA=m)
2128 Say Y here if you want to use Direct Cache Access (DCA) in the
2129 driver. DCA is a method for warming the CPU cache before data
2130 is used, with the intent of lessening the impact of cache misses.
2133 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2136 This driver supports Intel(R) 82576 virtual functions. For more
2137 information on how to identify your adapter, go to the Adapter &
2140 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2142 For general information and support, go to the Intel support
2145 <http://support.intel.com>
2147 More specific information on configuring the driver is in
2148 <file:Documentation/networking/e1000.txt>.
2150 To compile this driver as a module, choose M here. The module
2151 will be called igbvf.
2153 source "drivers/net/ixp2000/Kconfig"
2156 tristate "MyriCOM Gigabit Ethernet support"
2159 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2161 To compile this driver as a module, choose M here: the module
2162 will be called myri_sbus. This is recommended.
2165 tristate "National Semiconductor DP83820 support"
2168 This is a driver for the National Semiconductor DP83820 series
2169 of gigabit ethernet MACs. Cards using this chipset include
2170 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2171 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2175 tristate "Packet Engines Hamachi GNIC-II support"
2179 If you have a Gigabit Ethernet card of this type, say Y and read
2180 the Ethernet-HOWTO, available from
2181 <http://www.tldp.org/docs.html#howto>.
2183 To compile this driver as a module, choose M here. The module will be
2187 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2188 depends on PCI && EXPERIMENTAL
2191 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2192 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2193 used by the Beowulf Linux cluster project. See
2194 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2195 information about this driver in particular and Beowulf in general.
2197 To compile this driver as a module, choose M here: the module
2198 will be called yellowfin. This is recommended.
2201 tristate "Realtek 8169 gigabit ethernet support"
2206 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2208 To compile this driver as a module, choose M here: the module
2209 will be called r8169. This is recommended.
2213 depends on R8169 && VLAN_8021Q
2215 Say Y here for the r8169 driver to support the functions required
2216 by the kernel 802.1Q code.
2221 tristate "SB1250 Gigabit Ethernet support"
2222 depends on SIBYTE_SB1xxx_SOC
2225 This driver supports Gigabit Ethernet interfaces based on the
2226 Broadcom SiByte family of System-On-a-Chip parts. They include
2227 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2230 To compile this driver as a module, choose M here: the module
2231 will be called sb1250-mac.
2234 tristate "SiS190/SiS191 gigabit ethernet support"
2239 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2240 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2241 appear in lan on motherboard designs which are based on SiS 965
2242 and SiS 966 south bridge.
2244 To compile this driver as a module, choose M here: the module
2245 will be called sis190. This is recommended.
2248 tristate "New SysKonnect GigaEthernet support"
2252 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2253 and related Gigabit Ethernet adapters. It is a new smaller driver
2254 with better performance and more complete ethtool support.
2256 It does not support the link failover and network management
2257 features that "portable" vendor supplied sk98lin driver does.
2259 This driver supports adapters based on the original Yukon chipset:
2260 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2261 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2263 It does not support the newer Yukon2 chipset: a separate driver,
2264 sky2, is provided for Yukon2-based adapters.
2266 To compile this driver as a module, choose M here: the module
2267 will be called skge. This is recommended.
2270 bool "Debugging interface"
2271 depends on SKGE && DEBUG_FS
2273 This option adds the ability to dump driver state for debugging.
2274 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2275 transmit and receive rings.
2280 tristate "SysKonnect Yukon2 support"
2284 This driver supports Gigabit Ethernet adapters based on the
2285 Marvell Yukon 2 chipset:
2286 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2287 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2289 There is companion driver for the older Marvell Yukon and
2290 Genesis based adapters: skge.
2292 To compile this driver as a module, choose M here: the module
2293 will be called sky2. This is recommended.
2296 bool "Debugging interface"
2297 depends on SKY2 && DEBUG_FS
2299 This option adds the ability to dump driver state for debugging.
2300 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2301 transmit and receive rings.
2306 tristate "VIA Velocity support"
2312 If you have a VIA "Velocity" based network card say Y here.
2314 To compile this driver as a module, choose M here. The module
2315 will be called via-velocity.
2318 tristate "Broadcom Tigon3 support"
2322 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2324 To compile this driver as a module, choose M here: the module
2325 will be called tg3. This is recommended.
2328 tristate "Broadcom NetXtremeII support"
2333 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2335 To compile this driver as a module, choose M here: the module
2336 will be called bnx2. This is recommended.
2339 tristate "Broadcom CNIC support"
2344 This driver supports offload features of Broadcom NetXtremeII
2345 gigabit Ethernet cards.
2347 To compile this driver as a module, choose M here: the module
2348 will be called cnic. This is recommended.
2351 tristate "Spider Gigabit Ethernet driver"
2352 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2355 This driver supports the Gigabit Ethernet chips present on the
2356 Cell Processor-Based Blades from IBM.
2359 tristate "Tundra TSI108 gigabit Ethernet support"
2360 depends on TSI108_BRIDGE
2362 This driver supports Tundra TSI108 gigabit Ethernet ports.
2363 To compile this driver as a module, choose M here: the module
2364 will be called tsi108_eth.
2367 tristate "PS3 Gigabit Ethernet driver"
2369 select PS3_SYS_MANAGER
2371 This driver supports the network device on the PS3 game
2372 console. This driver has built-in support for Ethernet.
2374 To compile this driver as a module, choose M here: the
2375 module will be called ps3_gelic.
2377 config GELIC_WIRELESS
2378 bool "PS3 Wireless support"
2380 depends on GELIC_NET
2383 This option adds the support for the wireless feature of PS3.
2384 If you have the wireless-less model of PS3 or have no plan to
2385 use wireless feature, disabling this option saves memory. As
2386 the driver automatically distinguishes the models, you can
2387 safely enable this option even if you have a wireless-less model.
2390 tristate "Freescale PQ MDIO"
2394 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2397 tristate "Gianfar Ethernet"
2403 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2404 and MPC86xx family of chips, and the FEC on the 8540.
2407 tristate "Freescale QE Gigabit Ethernet"
2408 depends on QUICC_ENGINE
2412 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2413 which is available on some Freescale SOCs.
2415 config UGETH_TX_ON_DEMAND
2416 bool "Transmit on Demand support"
2420 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2421 depends on MV64X60 || PPC32 || PLAT_ORION
2425 This driver supports the gigabit ethernet MACs in the
2426 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2427 in the Marvell Orion ARM SoC family.
2429 Some boards that use the Discovery chipset are the Momenco
2430 Ocelot C and Jaguar ATX and Pegasos II.
2432 config XILINX_LL_TEMAC
2433 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2434 depends on PPC || MICROBLAZE
2437 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2438 core used in Xilinx Spartan and Virtex FPGAs
2441 tristate "QLogic QLA3XXX Network Driver Support"
2444 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2446 To compile this driver as a module, choose M here: the module
2447 will be called qla3xxx.
2450 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2455 This driver supports the Atheros/Attansic L1 gigabit ethernet
2458 To compile this driver as a module, choose M here. The module
2459 will be called atl1.
2462 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2463 depends on PCI && EXPERIMENTAL
2467 This driver supports the Atheros L1E gigabit ethernet adapter.
2469 To compile this driver as a module, choose M here. The module
2470 will be called atl1e.
2473 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2474 depends on PCI && EXPERIMENTAL
2478 This driver supports the Atheros L1C gigabit ethernet adapter.
2480 To compile this driver as a module, choose M here. The module
2481 will be called atl1c.
2484 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2489 This driver supports the PCI-Express gigabit ethernet adapters
2490 based on JMicron JMC250 chipset.
2492 To compile this driver as a module, choose M here. The module
2496 tristate "S6105 GMAC ethernet support"
2497 depends on XTENSA_VARIANT_S6000
2500 This driver supports the on chip ethernet device on the
2501 S6105 xtensa processor.
2503 To compile this driver as a module, choose M here. The module
2504 will be called s6gmac.
2506 source "drivers/net/stmmac/Kconfig"
2511 # 10 Gigabit Ethernet
2514 menuconfig NETDEV_10000
2515 bool "Ethernet (10000 Mbit)"
2519 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2520 This option alone does not add any kernel code.
2522 If you say N, all options in this submenu will be skipped and disabled.
2530 tristate "Chelsio 10Gb Ethernet support"
2535 This driver supports Chelsio gigabit and 10-gigabit
2536 Ethernet cards. More information about adapter features and
2537 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2539 For general information about Chelsio and our products, visit
2540 our website at <http://www.chelsio.com>.
2542 For customer support, please visit our customer support page at
2543 <http://www.chelsio.com/support.htm>.
2545 Please send feedback to <linux-bugs@chelsio.com>.
2547 To compile this driver as a module, choose M here: the module
2548 will be called cxgb.
2550 config CHELSIO_T1_1G
2551 bool "Chelsio gigabit Ethernet support"
2552 depends on CHELSIO_T1
2554 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2555 are using only 10G cards say 'N' here.
2557 config CHELSIO_T3_DEPENDS
2559 depends on PCI && INET
2563 tristate "Chelsio Communications T3 10Gb Ethernet support"
2564 depends on CHELSIO_T3_DEPENDS
2568 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2571 For general information about Chelsio and our products, visit
2572 our website at <http://www.chelsio.com>.
2574 For customer support, please visit our customer support page at
2575 <http://www.chelsio.com/support.htm>.
2577 Please send feedback to <linux-bugs@chelsio.com>.
2579 To compile this driver as a module, choose M here: the module
2580 will be called cxgb3.
2582 config CHELSIO_T4_DEPENDS
2584 depends on PCI && INET
2588 tristate "Chelsio Communications T4 Ethernet support"
2589 depends on CHELSIO_T4_DEPENDS
2593 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2596 For general information about Chelsio and our products, visit
2597 our website at <http://www.chelsio.com>.
2599 For customer support, please visit our customer support page at
2600 <http://www.chelsio.com/support.htm>.
2602 Please send feedback to <linux-bugs@chelsio.com>.
2604 To compile this driver as a module choose M here; the module
2605 will be called cxgb4.
2607 config CHELSIO_T4VF_DEPENDS
2609 depends on PCI && INET
2613 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2614 depends on CHELSIO_T4VF_DEPENDS
2616 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2617 adapters with PCI-E SR-IOV Virtual Functions.
2619 For general information about Chelsio and our products, visit
2620 our website at <http://www.chelsio.com>.
2622 For customer support, please visit our customer support page at
2623 <http://www.chelsio.com/support.htm>.
2625 Please send feedback to <linux-bugs@chelsio.com>.
2627 To compile this driver as a module choose M here; the module
2628 will be called cxgb4vf.
2631 tristate "eHEA Ethernet support"
2632 depends on IBMEBUS && INET && SPARSEMEM
2635 This driver supports the IBM pSeries eHEA ethernet adapter.
2637 To compile the driver as a module, choose M here. The module
2638 will be called ehea.
2641 tristate "Cisco VIC Ethernet NIC Support"
2642 depends on PCI && INET
2644 This enables the support for the Cisco VIC Ethernet card.
2647 tristate "Intel(R) 10GbE PCI Express adapters support"
2648 depends on PCI && INET
2651 This driver supports Intel(R) 10GbE PCI Express family of
2652 adapters. For more information on how to identify your adapter, go
2653 to the Adapter & Driver ID Guide at:
2655 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2657 For general information and support, go to the Intel support
2660 <http://support.intel.com>
2662 To compile this driver as a module, choose M here. The module
2663 will be called ixgbe.
2666 bool "Direct Cache Access (DCA) Support"
2668 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2670 Say Y here if you want to use Direct Cache Access (DCA) in the
2671 driver. DCA is a method for warming the CPU cache before data
2672 is used, with the intent of lessening the impact of cache misses.
2675 bool "Data Center Bridging (DCB) Support"
2677 depends on IXGBE && DCB
2679 Say Y here if you want to use Data Center Bridging (DCB) in the
2685 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2688 This driver supports Intel(R) 82599 virtual functions. For more
2689 information on how to identify your adapter, go to the Adapter &
2692 <http://support.intel.com/support/network/sb/CS-008441.htm>
2694 For general information and support, go to the Intel support
2697 <http://support.intel.com>
2699 More specific information on configuring the driver is in
2700 <file:Documentation/networking/ixgbevf.txt>.
2702 To compile this driver as a module, choose M here. The module
2703 will be called ixgbevf. MSI-X interrupt support is required
2704 for this driver to work correctly.
2707 tristate "Intel(R) PRO/10GbE support"
2710 This driver supports Intel(R) PRO/10GbE family of adapters for
2711 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2712 instead. For more information on how to identify your adapter, go
2713 to the Adapter & Driver ID Guide at:
2715 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2717 For general information and support, go to the Intel support
2720 <http://support.intel.com>
2722 More specific information on configuring the driver is in
2723 <file:Documentation/networking/ixgb.txt>.
2725 To compile this driver as a module, choose M here. The module
2726 will be called ixgb.
2729 tristate "S2IO 10Gbe XFrame NIC"
2732 This driver supports the 10Gbe XFrame NIC of S2IO.
2733 More specific information on configuring the driver is in
2734 <file:Documentation/networking/s2io.txt>.
2737 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2738 depends on PCI && INET
2740 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2741 I/O Virtualized Server Adapter.
2742 More specific information on configuring the driver is in
2743 <file:Documentation/networking/vxge.txt>.
2745 config VXGE_DEBUG_TRACE_ALL
2746 bool "Enabling All Debug trace statments in driver"
2750 Say Y here if you want to enabling all the debug trace statements in
2751 driver. By default only few debug trace statements are enabled.
2754 tristate "Myricom Myri-10G Ethernet support"
2755 depends on PCI && INET
2760 This driver supports Myricom Myri-10G Dual Protocol interface in
2761 Ethernet mode. If the eeprom on your board is not recent enough,
2762 you will need a newer firmware image.
2763 You may get this image or more information, at:
2765 <http://www.myri.com/scs/download-Myri10GE.html>
2767 To compile this driver as a module, choose M here. The module
2768 will be called myri10ge.
2771 bool "Direct Cache Access (DCA) Support"
2773 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2775 Say Y here if you want to use Direct Cache Access (DCA) in the
2776 driver. DCA is a method for warming the CPU cache before data
2777 is used, with the intent of lessening the impact of cache misses.
2780 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2784 This enables the support for NetXen's Gigabit Ethernet card.
2787 tristate "Sun Neptune 10Gbit Ethernet support"
2791 This enables support for cards based upon Sun's
2795 tristate "PA Semi 1/10Gbit MAC"
2796 depends on PPC_PASEMI && PCI
2800 This driver supports the on-chip 1/10Gbit Ethernet controller on
2801 PA Semi's PWRficient line of chips.
2804 tristate "Mellanox Technologies 10Gbit Ethernet support"
2805 depends on PCI && INET
2809 This driver supports Mellanox Technologies ConnectX Ethernet
2818 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2819 depends on MLX4_CORE
2822 This option causes debugging code to be compiled into the
2823 mlx4_core driver. The output can be turned on via the
2824 debug_level module parameter (which can also be set after
2825 the driver is loaded through sysfs).
2828 tristate "Tehuti Networks 10G Ethernet"
2831 Tehuti Networks 10G Ethernet NIC
2834 tristate "Broadcom NetXtremeII 10Gb support"
2841 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2842 To compile this driver as a module, choose M here: the module
2843 will be called bnx2x. This is recommended.
2846 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2850 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2854 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2857 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2859 To compile this driver as a module, choose M here: the module
2860 will be called qlge.
2862 source "drivers/net/sfc/Kconfig"
2864 source "drivers/net/benet/Kconfig"
2866 endif # NETDEV_10000
2868 source "drivers/net/tokenring/Kconfig"
2870 source "drivers/net/wireless/Kconfig"
2872 source "drivers/net/wimax/Kconfig"
2874 source "drivers/net/usb/Kconfig"
2876 source "drivers/net/pcmcia/Kconfig"
2878 source "drivers/net/wan/Kconfig"
2880 source "drivers/atm/Kconfig"
2882 source "drivers/ieee802154/Kconfig"
2884 source "drivers/s390/net/Kconfig"
2886 source "drivers/net/caif/Kconfig"
2888 config XEN_NETDEV_FRONTEND
2889 tristate "Xen network device frontend driver"
2893 The network device frontend driver allows the kernel to
2894 access network devices exported exported by a virtual
2895 machine containing a physical network device driver. The
2896 frontend driver is intended for unprivileged guest domains;
2897 if you are compiling a kernel for a Xen guest, you almost
2898 certainly want to enable this.
2901 tristate "iSeries Virtual Ethernet driver support"
2902 depends on PPC_ISERIES
2905 tristate "RapidIO Ethernet over messaging driver support"
2908 config RIONET_TX_SIZE
2909 int "Number of outbound queue entries"
2913 config RIONET_RX_SIZE
2914 int "Number of inbound queue entries"
2919 tristate "FDDI driver support"
2920 depends on (PCI || EISA || TC)
2922 Fiber Distributed Data Interface is a high speed local area network
2923 design; essentially a replacement for high speed Ethernet. FDDI can
2924 run over copper or fiber. If you are connected to such a network and
2925 want a driver for the FDDI card in your computer, say Y here (and
2926 then also Y to the driver for your FDDI card, below). Most people
2930 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2931 depends on FDDI && (PCI || EISA || TC)
2933 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2934 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2935 to a local FDDI network.
2937 To compile this driver as a module, choose M here: the module
2938 will be called defxx. If unsure, say N.
2942 prompt "Use MMIO instead of PIO" if PCI || EISA
2944 default n if PCI || EISA
2947 This instructs the driver to use EISA or PCI memory-mapped I/O
2948 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2949 Enabling this gives an improvement in processing time in parts
2950 of the driver, but it may cause problems with EISA (DEFEA)
2951 adapters. TURBOchannel does not have the concept of I/O ports,
2952 so MMIO is always used for these (DEFTA) adapters.
2957 tristate "SysKonnect FDDI PCI support"
2958 depends on FDDI && PCI
2961 Say Y here if you have a SysKonnect FDDI PCI adapter.
2962 The following adapters are supported by this driver:
2963 - SK-5521 (SK-NET FDDI-UP)
2964 - SK-5522 (SK-NET FDDI-UP DAS)
2965 - SK-5541 (SK-NET FDDI-FP)
2966 - SK-5543 (SK-NET FDDI-LP)
2967 - SK-5544 (SK-NET FDDI-LP DAS)
2968 - SK-5821 (SK-NET FDDI-UP64)
2969 - SK-5822 (SK-NET FDDI-UP64 DAS)
2970 - SK-5841 (SK-NET FDDI-FP64)
2971 - SK-5843 (SK-NET FDDI-LP64)
2972 - SK-5844 (SK-NET FDDI-LP64 DAS)
2973 - Netelligent 100 FDDI DAS Fibre SC
2974 - Netelligent 100 FDDI SAS Fibre SC
2975 - Netelligent 100 FDDI DAS UTP
2976 - Netelligent 100 FDDI SAS UTP
2977 - Netelligent 100 FDDI SAS Fibre MIC
2979 Read <file:Documentation/networking/skfp.txt> for information about
2982 Questions concerning this driver can be addressed to:
2983 <linux@syskonnect.de>
2985 To compile this driver as a module, choose M here: the module
2986 will be called skfp. This is recommended.
2989 bool "HIPPI driver support (EXPERIMENTAL)"
2990 depends on EXPERIMENTAL && INET && PCI
2992 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2993 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2994 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2995 single-mode). HIPPI networks are commonly used for clusters and to
2996 connect to super computers. If you are connected to a HIPPI network
2997 and have a HIPPI network card in your computer that you want to use
2998 under Linux, say Y here (you must also remember to enable the driver
2999 for your HIPPI card below). Most people will say N here.
3002 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3003 depends on HIPPI && PCI
3005 Say Y here if this is your PCI HIPPI network card.
3007 To compile this driver as a module, choose M here: the module
3008 will be called rrunner. If unsure, say N.
3010 config ROADRUNNER_LARGE_RINGS
3011 bool "Use large TX/RX rings (EXPERIMENTAL)"
3012 depends on ROADRUNNER
3014 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3015 of additional memory to allow for fastest operation, both for
3016 transmitting and receiving. This memory cannot be used by any other
3017 kernel code or by user space programs. Say Y here only if you have
3021 tristate "PLIP (parallel port) support"
3024 PLIP (Parallel Line Internet Protocol) is used to create a
3025 reasonably fast mini network consisting of two (or, rarely, more)
3026 local machines. A PLIP link from a Linux box is a popular means to
3027 install a Linux distribution on a machine which doesn't have a
3028 CD-ROM drive (a minimal system has to be transferred with floppies
3029 first). The kernels on both machines need to have this PLIP option
3030 enabled for this to work.
3032 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3033 ports (the connectors at the computers with 25 holes) are connected
3034 with "null printer" or "Turbo Laplink" cables which can transmit 4
3035 bits at a time (mode 0) or with special PLIP cables, to be used on
3036 bidirectional parallel ports only, which can transmit 8 bits at a
3037 time (mode 1); you can find the wiring of these cables in
3038 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3039 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3040 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3041 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3042 and winsock or NCSA's telnet.
3044 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3045 as the NET-3-HOWTO, both available from
3046 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3047 protocol has been changed and this PLIP driver won't work together
3048 with the PLIP support in Linux versions 1.0.x. This option enlarges
3049 your kernel by about 8 KB.
3051 To compile this driver as a module, choose M here. The module
3052 will be called plip. If unsure, say Y or M, in case you buy
3056 tristate "PPP (point-to-point protocol) support"
3059 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3060 the same purpose: sending Internet traffic over telephone (and other
3061 serial) lines. Ask your access provider if they support it, because
3062 otherwise you can't use it; most Internet access providers these
3063 days support PPP rather than SLIP.
3065 To use PPP, you need an additional program called pppd as described
3066 in the PPP-HOWTO, available at
3067 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3068 the version of pppd recommended in <file:Documentation/Changes>.
3069 The PPP option enlarges your kernel by about 16 KB.
3071 There are actually two versions of PPP: the traditional PPP for
3072 asynchronous lines, such as regular analog phone lines, and
3073 synchronous PPP which can be used over digital ISDN lines for
3074 example. If you want to use PPP over phone lines or other
3075 asynchronous serial lines, you need to say Y (or M) here and also to
3076 the next option, "PPP support for async serial ports". For PPP over
3077 synchronous lines, you should say Y (or M) here and to "Support
3078 synchronous PPP", below.
3080 If you said Y to "Version information on all symbols" above, then
3081 you cannot compile the PPP driver into the kernel; you can then only
3082 compile it as a module. To compile this driver as a module, choose M
3083 here. The module will be called ppp_generic.
3085 config PPP_MULTILINK
3086 bool "PPP multilink support (EXPERIMENTAL)"
3087 depends on PPP && EXPERIMENTAL
3089 PPP multilink is a protocol (defined in RFC 1990) which allows you
3090 to combine several (logical or physical) lines into one logical PPP
3091 connection, so that you can utilize your full bandwidth.
3093 This has to be supported at the other end as well and you need a
3094 version of the pppd daemon which understands the multilink protocol.
3099 bool "PPP filtering"
3102 Say Y here if you want to be able to filter the packets passing over
3103 PPP interfaces. This allows you to control which packets count as
3104 activity (i.e. which packets will reset the idle timer or bring up
3105 a demand-dialed link) and which packets are to be dropped entirely.
3106 You need to say Y here if you wish to use the pass-filter and
3107 active-filter options to pppd.
3112 tristate "PPP support for async serial ports"
3116 Say Y (or M) here if you want to be able to use PPP over standard
3117 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3118 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3121 To compile this driver as a module, choose M here.
3126 tristate "PPP support for sync tty ports"
3129 Say Y (or M) here if you want to be able to use PPP over synchronous
3130 (HDLC) tty devices, such as the SyncLink adapter. These devices
3131 are often used for high-speed leased lines like T1/E1.
3133 To compile this driver as a module, choose M here.
3136 tristate "PPP Deflate compression"
3141 Support for the Deflate compression method for PPP, which uses the
3142 Deflate algorithm (the same algorithm that gzip uses) to compress
3143 each PPP packet before it is sent over the wire. The machine at the
3144 other end of the PPP link (usually your ISP) has to support the
3145 Deflate compression method as well for this to be useful. Even if
3146 they don't support it, it is safe to say Y here.
3148 To compile this driver as a module, choose M here.
3151 tristate "PPP BSD-Compress compression"
3154 Support for the BSD-Compress compression method for PPP, which uses
3155 the LZW compression method to compress each PPP packet before it is
3156 sent over the wire. The machine at the other end of the PPP link
3157 (usually your ISP) has to support the BSD-Compress compression
3158 method as well for this to be useful. Even if they don't support it,
3159 it is safe to say Y here.
3161 The PPP Deflate compression method ("PPP Deflate compression",
3162 above) is preferable to BSD-Compress, because it compresses better
3165 Note that the BSD compression code will always be compiled as a
3166 module; it is called bsd_comp and will show up in the directory
3167 modules once you have said "make modules". If unsure, say N.
3170 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3171 depends on PPP && EXPERIMENTAL
3177 Support for the MPPE Encryption protocol, as employed by the
3178 Microsoft Point-to-Point Tunneling Protocol.
3180 See http://pptpclient.sourceforge.net/ for information on
3181 configuring PPTP clients and servers to utilize this method.
3184 tristate "PPP over Ethernet (EXPERIMENTAL)"
3185 depends on EXPERIMENTAL && PPP
3187 Support for PPP over Ethernet.
3189 This driver requires the latest version of pppd from the CVS
3190 repository at cvs.samba.org. Alternatively, see the
3191 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3192 which contains instruction on how to use this driver (under
3193 the heading "Kernel mode PPPoE").
3196 tristate "PPP over ATM"
3197 depends on ATM && PPP
3199 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3200 This implementation does not yet comply with section 8 of RFC2364,
3201 which can lead to bad results if the ATM peer loses state and
3202 changes its encapsulation unilaterally.
3205 tristate "PPP over L2TP (EXPERIMENTAL)"
3206 depends on EXPERIMENTAL && L2TP && PPP
3208 Support for PPP-over-L2TP socket family. L2TP is a protocol
3209 used by ISPs and enterprises to tunnel PPP traffic over UDP
3210 tunnels. L2TP is replacing PPTP for VPN uses.
3213 tristate "SLIP (serial line) support"
3215 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3216 connect to your Internet service provider or to connect to some
3217 other local Unix box or if you want to configure your Linux box as a
3218 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3219 Internet Protocol) is a protocol used to send Internet traffic over
3220 serial connections such as telephone lines or null modem cables;
3221 nowadays, the protocol PPP is more commonly used for this same
3224 Normally, your access provider has to support SLIP in order for you
3225 to be able to use it, but there is now a SLIP emulator called SLiRP
3226 around (available from
3227 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3228 allows you to use SLIP over a regular dial up shell connection. If
3229 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3230 NET-3-HOWTO, available from
3231 <http://www.tldp.org/docs.html#howto>, explains how to
3232 configure SLIP. Note that you don't need this option if you just
3233 want to run term (term is a program which gives you almost full
3234 Internet connectivity if you have a regular dial up shell account on
3235 some Internet connected Unix computer. Read
3236 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3237 support will enlarge your kernel by about 4 KB. If unsure, say N.
3239 To compile this driver as a module, choose M here. The module
3240 will be called slip.
3242 config SLIP_COMPRESSED
3243 bool "CSLIP compressed headers"
3247 This protocol is faster than SLIP because it uses compression on the
3248 TCP/IP headers (not on the data itself), but it has to be supported
3249 on both ends. Ask your access provider if you are not sure and
3250 answer Y, just in case. You will still be able to use plain SLIP. If
3251 you plan to use SLiRP, the SLIP emulator (available from
3252 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3253 allows you to use SLIP over a regular dial up shell connection, you
3254 definitely want to say Y here. The NET-3-HOWTO, available from
3255 <http://www.tldp.org/docs.html#howto>, explains how to configure
3256 CSLIP. This won't enlarge your kernel.
3261 This option enables Van Jacobsen serial line header compression
3265 bool "Keepalive and linefill"
3268 Adds additional capabilities to the SLIP driver to support the
3269 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3272 config SLIP_MODE_SLIP6
3273 bool "Six bit SLIP encapsulation"
3276 Just occasionally you may need to run IP over hostile serial
3277 networks that don't pass all control characters or are only seven
3278 bit. Saying Y here adds an extra mode you can use with SLIP:
3279 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3280 the serial device. Naturally, this has to be supported at the other
3281 end of the link as well. It's good enough, for example, to run IP
3282 over the async ports of a Camtec JNT Pad. If unsure, say N.
3285 bool "Fibre Channel driver support"
3286 depends on SCSI && PCI
3288 Fibre Channel is a high speed serial protocol mainly used to connect
3289 large storage devices to the computer; it is compatible with and
3290 intended to replace SCSI.
3292 If you intend to use Fibre Channel, you need to have a Fibre channel
3293 adaptor card in your computer; say Y here and to the driver for your
3294 adaptor below. You also should have said Y to "SCSI support" and
3295 "SCSI generic support".
3298 tristate "Network console logging support"
3300 If you want to log kernel messages over the network, enable this.
3301 See <file:Documentation/networking/netconsole.txt> for details.
3303 config NETCONSOLE_DYNAMIC
3304 bool "Dynamic reconfiguration of logging targets"
3305 depends on NETCONSOLE && SYSFS
3308 This option enables the ability to dynamically reconfigure target
3309 parameters (interface, IP addresses, port numbers, MAC addresses)
3310 at runtime through a userspace interface exported using configfs.
3311 See <file:Documentation/networking/netconsole.txt> for details.
3317 bool "Netpoll traffic trapping"
3321 config NET_POLL_CONTROLLER
3325 tristate "Virtio network driver (EXPERIMENTAL)"
3326 depends on EXPERIMENTAL && VIRTIO
3328 This is the virtual network driver for virtio. It can be used with
3329 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3332 tristate "VMware VMXNET3 ethernet driver"
3333 depends on PCI && INET
3335 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3336 To compile this driver as a module, choose M here: the
3337 module will be called vmxnet3.