2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 menuconfig NET_ETHERNET
197 bool "Ethernet (10 or 100Mbit)"
200 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
201 type of Local Area Network (LAN) in universities and companies.
203 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
204 coaxial cable, linking computers in a chain), 10BASE-T or twisted
205 pair (10 Mbps over twisted pair cable, linking computers to central
206 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
207 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
208 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
209 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
210 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
211 Ethernet (1 Gbps over optical fiber or short copper links).
213 If your Linux machine will be connected to an Ethernet and you have
214 an Ethernet network interface card (NIC) installed in your computer,
215 say Y here and read the Ethernet-HOWTO, available from
216 <http://www.tldp.org/docs.html#howto>. You will then also have
217 to say Y to the driver for your particular NIC.
219 Note that the answer to this question won't directly affect the
220 kernel: saying N will just cause the configurator to skip all
221 the questions about Ethernet network cards. If unsure, say N.
226 tristate "Atmel MACB support"
227 depends on HAVE_NET_MACB
230 The Atmel MACB ethernet interface is found on many AT32 and AT91
231 parts. Say Y to include support for the MACB chip.
233 To compile this driver as a module, choose M here: the module
236 source "drivers/net/arm/Kconfig"
239 tristate "ASIX AX88796 NE2000 clone support"
240 depends on ARM || MIPS || SUPERH
244 AX88796 driver, using platform bus to provide
245 chip detection and resources
248 bool "ASIX AX88796 external 93CX6 eeprom support"
252 Select this if your platform comes with an external 93CX6 eeprom.
255 tristate "MACE (Power Mac ethernet) support"
256 depends on PPC_PMAC && PPC32
259 Power Macintoshes and clones with Ethernet built-in on the
260 motherboard will usually use a MACE (Medium Access Control for
261 Ethernet) interface. Say Y to include support for the MACE chip.
263 To compile this driver as a module, choose M here: the module
266 config MACE_AAUI_PORT
267 bool "Use AAUI port instead of TP by default"
270 Some Apple machines (notably the Apple Network Server) which use the
271 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
272 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
273 Y here if you have such a machine. If unsure, say N.
274 The driver will default to AAUI on ANS anyway, and if you use it as
275 a module, you can provide the port_aaui=0|1 to force the driver.
278 tristate "BMAC (G3 ethernet) support"
279 depends on PPC_PMAC && PPC32
282 Say Y for support of BMAC Ethernet interfaces. These are used on G3
285 To compile this driver as a module, choose M here: the module
289 tristate "Ariadne support"
292 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
295 To compile this driver as a module, choose M here: the module
296 will be called ariadne.
299 tristate "A2065 support"
303 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
306 To compile this driver as a module, choose M here: the module
307 will be called a2065.
310 tristate "Hydra support"
314 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
316 To compile this driver as a module, choose M here: the module
317 will be called hydra.
320 tristate "Zorro NS8390-based Ethernet support"
324 This driver is for Zorro Ethernet cards using an NS8390-compatible
325 chipset, like the Village Tronic Ariadne II and the Individual
326 Computers X-Surf Ethernet cards. If you have such a card, say Y.
329 To compile this driver as a module, choose M here: the module
330 will be called zorro8390.
333 tristate "PCMCIA NE2000 support"
334 depends on AMIGA_PCMCIA
337 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
340 To compile this driver as a module, choose M here: the module
344 bool "Macintosh NS 8390 based ethernet cards"
348 If you want to include a driver to support Nubus or LC-PDS
349 Ethernet cards using an NS8390 chipset or its equivalent, say Y
350 and read the Ethernet-HOWTO, available from
351 <http://www.tldp.org/docs.html#howto>.
354 tristate "Macintosh CS89x0 based ethernet cards"
357 Support for CS89x0 chipset based Ethernet cards. If you have a
358 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
359 read the Ethernet-HOWTO, available from
360 <http://www.tldp.org/docs.html#howto>.
362 To compile this driver as a module, choose M here. This module will
366 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
369 Support for NatSemi SONIC based Ethernet devices. This includes
370 the onboard Ethernet in many Quadras as well as some LC-PDS,
371 a few Nubus and all known Comm Slot Ethernet cards. If you have
372 one of these say Y and read the Ethernet-HOWTO, available from
373 <http://www.tldp.org/docs.html#howto>.
375 To compile this driver as a module, choose M here. This module will
379 bool "Macintosh (AV) onboard MACE ethernet"
383 Support for the onboard AMD 79C940 MACE Ethernet controller used in
384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
385 say Y and read the Ethernet-HOWTO, available from
386 <http://www.tldp.org/docs.html#howto>.
389 tristate "MVME147 (Lance) Ethernet support"
393 Support for the on-board Ethernet interface on the Motorola MVME147
394 single-board computer. Say Y here to include the
395 driver for this chip in your kernel.
396 To compile this driver as a module, choose M here.
399 tristate "MVME16x Ethernet support"
402 This is the driver for the Ethernet interface on the Motorola
403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
404 driver for this chip in your kernel.
405 To compile this driver as a module, choose M here.
408 tristate "BVME6000 Ethernet support"
411 This is the driver for the Ethernet interface on BVME4000 and
412 BVME6000 VME boards. Say Y here to include the driver for this chip
414 To compile this driver as a module, choose M here.
417 tristate "Atari Lance support"
420 Say Y to include support for several Atari Ethernet adapters based
421 on the AMD Lance chipset: RieblCard (with or without battery), or
422 PAMCard VME (also the version by Rhotron, with different addresses).
425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
435 If you're not building a kernel for a Sun 3, say N.
438 bool "Sun3 on-board Intel 82586 support"
441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional
447 bool "HP on-board LANCE support"
451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here.
455 tristate "Lasi ethernet"
458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM
465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines.
469 tristate "Korina (IDT RC32434) Ethernet support"
470 depends on NET_ETHERNET && MIKROTIK_RB532
472 If you have a Mikrotik RouterBoard 500 or IDT RC32434
473 based system say Y. Otherwise say N.
475 config MIPS_JAZZ_SONIC
476 tristate "MIPS JAZZ onboard SONIC Ethernet support"
479 This is the driver for the onboard card of MIPS Magnum 4000,
480 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
482 config XTENSA_XT2000_SONIC
483 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
484 depends on XTENSA_PLATFORM_XT2000
486 This is the driver for the onboard card of the Xtensa XT2000 board.
488 config MIPS_AU1X00_ENET
489 tristate "MIPS AU1000 Ethernet support"
490 depends on MIPS_ALCHEMY
494 If you have an Alchemy Semi AU1X00 based system
495 say Y. Otherwise, say N.
498 bool "SGI IOC3 Ethernet"
499 depends on PCI && SGI_IP27
503 If you have a network (Ethernet) card of this type, say Y and read
504 the Ethernet-HOWTO, available from
505 <http://www.tldp.org/docs.html#howto>.
508 tristate "MIPS simulator Network device"
511 The MIPSNET device is a simple Ethernet network device which is
512 emulated by the MIPS Simulator.
513 If you are not using a MIPSsim or are unsure, say N.
515 config SGI_O2MACE_ETH
516 tristate "SGI O2 MACE Fast Ethernet support"
517 depends on SGI_IP32=y
520 tristate "National DP83902AV support"
524 Support for cards based on the National Semiconductor DP83902AV
525 ST-NIC Serial Network Interface Controller for Twisted Pair. This
526 is a 10Mbit/sec Ethernet controller. Product overview and specs at
527 <http://www.national.com/pf/DP/DP83902A.html>.
532 tristate "Renesas SuperH Ethernet support"
533 depends on SUPERH && \
534 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
535 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
536 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
542 Renesas SuperH Ethernet device driver.
543 This driver supporting CPUs are:
544 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
547 tristate "Sun LANCE support"
551 This driver supports the "le" interface present on all 32-bit Sparc
552 systems, on some older Ultra systems and as an Sbus option. These
553 cards are based on the AMD Lance chipset, which is better known
554 via the NE2100 cards.
556 To compile this driver as a module, choose M here: the module
557 will be called sunlance.
560 tristate "Sun Happy Meal 10/100baseT support"
561 depends on SBUS || PCI
564 This driver supports the "hme" interface present on most Ultra
565 systems and as an option on older Sbus systems. This driver supports
566 both PCI and Sbus devices. This driver also supports the "qfe" quad
567 100baseT device available in both PCI and Sbus configurations.
569 To compile this driver as a module, choose M here: the module
570 will be called sunhme.
573 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
574 depends on SBUS && EXPERIMENTAL
577 This driver supports the "be" interface available as an Sbus option.
578 This is Sun's older 100baseT Ethernet device.
580 To compile this driver as a module, choose M here: the module
581 will be called sunbmac.
584 tristate "Sun QuadEthernet support"
588 This driver supports the "qe" 10baseT Ethernet device, available as
589 an Sbus option. Note that this is not the same as Quad FastEthernet
590 "qfe" which is supported by the Happy Meal driver instead.
592 To compile this driver as a module, choose M here: the module
593 will be called sunqe.
596 tristate "Sun GEM support"
600 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
601 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
604 tristate "Sun Cassini support"
608 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
609 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
612 tristate "Sun Virtual Network support"
615 Support for virtual network devices under Sun Logical Domains.
617 config NET_VENDOR_3COM
619 depends on ISA || EISA || MCA || PCI
621 If you have a network (Ethernet) card belonging to this class, say Y
622 and read the Ethernet-HOWTO, available from
623 <http://www.tldp.org/docs.html#howto>.
625 Note that the answer to this question doesn't directly affect the
626 kernel: saying N will just cause the configurator to skip all
627 the questions about 3COM cards. If you say Y, you will be asked for
628 your specific card in the following questions.
631 tristate "3c501 \"EtherLink\" support"
632 depends on NET_VENDOR_3COM && ISA
634 If you have a network (Ethernet) card of this type, say Y and read
635 the Ethernet-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
637 new card, since the 3c501 is slow, broken, and obsolete: you will
638 have problems. Some people suggest to ping ("man ping") a nearby
639 machine every minute ("man cron") when using this card.
641 To compile this driver as a module, choose M here. The module
642 will be called 3c501.
645 tristate "3c503 \"EtherLink II\" support"
646 depends on NET_VENDOR_3COM && ISA
649 If you have a network (Ethernet) card of this type, say Y and read
650 the Ethernet-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>.
653 To compile this driver as a module, choose M here. The module
654 will be called 3c503.
657 tristate "3c505 \"EtherLink Plus\" support"
658 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
660 Information about this network (Ethernet) card can be found in
661 <file:Documentation/networking/3c505.txt>. If you have a card of
662 this type, say Y and read the Ethernet-HOWTO, available from
663 <http://www.tldp.org/docs.html#howto>.
665 To compile this driver as a module, choose M here. The module
666 will be called 3c505.
669 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
670 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
672 If you have a network (Ethernet) card of this type, say Y and read
673 the Ethernet-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>.
676 To compile this driver as a module, choose M here. The module
677 will be called 3c507.
680 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
681 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
683 If you have a network (Ethernet) card belonging to the 3Com
684 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
685 from <http://www.tldp.org/docs.html#howto>.
687 If your card is not working you may need to use the DOS
688 setup disk to disable Plug & Play mode, and to select the default
691 To compile this driver as a module, choose M here. The module
692 will be called 3c509.
695 tristate "3c515 ISA \"Fast EtherLink\""
696 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
698 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
699 network card, say Y and read the Ethernet-HOWTO, available from
700 <http://www.tldp.org/docs.html#howto>.
702 To compile this driver as a module, choose M here. The module
703 will be called 3c515.
706 tristate "3c523 \"EtherLink/MC\" support"
707 depends on NET_VENDOR_3COM && MCA_LEGACY
709 If you have a network (Ethernet) card of this type, say Y and read
710 the Ethernet-HOWTO, available from
711 <http://www.tldp.org/docs.html#howto>.
713 To compile this driver as a module, choose M here. The module
714 will be called 3c523.
717 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
718 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
720 If you have a network (Ethernet) card of this type, say Y and read
721 the Ethernet-HOWTO, available from
722 <http://www.tldp.org/docs.html#howto>.
724 To compile this driver as a module, choose M here. The module
725 will be called 3c527.
728 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
729 depends on NET_VENDOR_3COM && (PCI || EISA)
732 This option enables driver support for a large number of 10Mbps and
733 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
735 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
736 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
737 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
738 "Tornado" (3c905) PCI
739 "Hurricane" (3c555/3cSOHO) PCI
741 If you have such a card, say Y and read the Ethernet-HOWTO,
742 available from <http://www.tldp.org/docs.html#howto>. More
743 specific information is in
744 <file:Documentation/networking/vortex.txt> and in the comments at
745 the beginning of <file:drivers/net/3c59x.c>.
747 To compile this support as a module, choose M here.
750 tristate "3cr990 series \"Typhoon\" support"
751 depends on NET_VENDOR_3COM && PCI
754 This option enables driver support for the 3cr990 series of cards:
756 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
757 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
758 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
760 If you have a network (Ethernet) card of this type, say Y and read
761 the Ethernet-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>.
764 To compile this driver as a module, choose M here. The module
765 will be called typhoon.
768 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
769 depends on ISA && ISA_DMA_API
771 If you have a network (Ethernet) card of this type, say Y and read
772 the Ethernet-HOWTO, available from
773 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
776 To compile this driver as a module, choose M here: the module
777 will be called lance. This is recommended.
779 config NET_VENDOR_SMC
780 bool "Western Digital/SMC cards"
781 depends on ISA || MCA || EISA || MAC
783 If you have a network (Ethernet) card belonging to this class, say Y
784 and read the Ethernet-HOWTO, available from
785 <http://www.tldp.org/docs.html#howto>.
787 Note that the answer to this question doesn't directly affect the
788 kernel: saying N will just cause the configurator to skip all
789 the questions about Western Digital cards. If you say Y, you will be
790 asked for your specific card in the following questions.
793 tristate "WD80*3 support"
794 depends on NET_VENDOR_SMC && ISA
797 If you have a network (Ethernet) card of this type, say Y and read
798 the Ethernet-HOWTO, available from
799 <http://www.tldp.org/docs.html#howto>.
801 To compile this driver as a module, choose M here. The module
805 tristate "SMC Ultra MCA support"
806 depends on NET_VENDOR_SMC && MCA
809 If you have a network (Ethernet) card of this type and are running
810 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
811 available from <http://www.tldp.org/docs.html#howto>.
813 To compile this driver as a module, choose M here. The module
814 will be called smc-mca.
817 tristate "SMC Ultra support"
818 depends on NET_VENDOR_SMC && ISA
821 If you have a network (Ethernet) card of this type, say Y and read
822 the Ethernet-HOWTO, available from
823 <http://www.tldp.org/docs.html#howto>.
825 Important: There have been many reports that, with some motherboards
826 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
827 such as some BusLogic models) causes corruption problems with many
828 operating systems. The Linux smc-ultra driver has a work-around for
829 this but keep it in mind if you have such a SCSI card and have
832 To compile this driver as a module, choose M here. The module
833 will be called smc-ultra.
836 tristate "SMC Ultra32 EISA support"
837 depends on NET_VENDOR_SMC && EISA
840 If you have a network (Ethernet) card of this type, say Y and read
841 the Ethernet-HOWTO, available from
842 <http://www.tldp.org/docs.html#howto>.
844 To compile this driver as a module, choose M here. The module
845 will be called smc-ultra32.
848 tristate "Blackfin on-chip MAC support"
849 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
853 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
855 This is the driver for Blackfin on-chip mac device. Say Y if you want it
856 compiled into the kernel. This driver is also available as a module
857 ( = code which can be inserted in and removed from the running kernel
858 whenever you want). The module will be called bfin_mac.
860 config BFIN_MAC_USE_L1
861 bool "Use L1 memory for rx/tx packets"
862 depends on BFIN_MAC && (BF527 || BF537)
865 To get maximum network performance, you should use L1 memory as rx/tx buffers.
866 Say N here if you want to reserve L1 memory for other uses.
868 config BFIN_TX_DESC_NUM
869 int "Number of transmit buffer packets"
871 range 6 10 if BFIN_MAC_USE_L1
875 Set the number of buffer packets used in driver.
877 config BFIN_RX_DESC_NUM
878 int "Number of receive buffer packets"
880 range 20 100 if BFIN_MAC_USE_L1
884 Set the number of buffer packets used in driver.
886 config BFIN_MAC_USE_HWSTAMP
887 bool "Use IEEE 1588 hwstamp"
888 depends on BFIN_MAC && BF518
891 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
894 tristate "SMC 9194 support"
895 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
898 This is support for the SMC9xxx based Ethernet cards. Choose this
899 option if you have a DELL laptop with the docking station, or
900 another SMC9192/9194 based chipset. Say Y if you want it compiled
901 into the kernel, and read the file
902 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
903 available from <http://www.tldp.org/docs.html#howto>.
905 To compile this driver as a module, choose M here. The module
906 will be called smc9194.
909 tristate "SMC 91C9x/91C1xxx support"
912 depends on ARM || M32R || SUPERH || \
913 MIPS || BLACKFIN || MN10300 || COLDFIRE
915 This is a driver for SMC's 91x series of Ethernet chipsets,
916 including the SMC91C94 and the SMC91C111. Say Y if you want it
917 compiled into the kernel, and read the file
918 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
919 available from <http://www.tldp.org/docs.html#howto>.
921 This driver is also available as a module ( = code which can be
922 inserted in and removed from the running kernel whenever you want).
923 The module will be called smc91x. If you want to compile it as a
924 module, say M here and read <file:Documentation/kbuild/modules.txt>.
927 tristate "Marvell pxa168 ethernet support"
928 depends on CPU_PXA168
931 This driver supports the pxa168 Ethernet ports.
933 To compile this driver as a module, choose M here. The module
934 will be called pxa168_eth.
937 tristate "NetX Ethernet support"
941 This is support for the Hilscher netX builtin Ethernet ports
943 To compile this driver as a module, choose M here. The module
944 will be called netx-eth.
946 config TI_DAVINCI_EMAC
947 tristate "TI DaVinci EMAC Support"
948 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
951 This driver supports TI's DaVinci Ethernet .
953 To compile this driver as a module, choose M here: the module
954 will be called davinci_emac_driver. This is recommended.
957 tristate "DM9000 support"
958 depends on ARM || BLACKFIN || MIPS
962 Support for DM9000 chipset.
964 To compile this driver as a module, choose M here. The module
965 will be called dm9000.
967 config DM9000_DEBUGLEVEL
968 int "DM9000 maximum debug level"
972 The maximum level of debugging code compiled into the DM9000
975 config DM9000_FORCE_SIMPLE_PHY_POLL
976 bool "Force simple NSR based PHY polling"
979 This configuration forces the DM9000 to use the NSR's LinkStatus
980 bit to determine if the link is up or down instead of the more
981 costly MII PHY reads. Note, this will not work if the chip is
982 operating with an external PHY.
985 tristate "ENC28J60 support"
986 depends on EXPERIMENTAL && SPI && NET_ETHERNET
989 Support for the Microchip EN28J60 ethernet chip.
991 To compile this driver as a module, choose M here. The module will be
994 config ENC28J60_WRITEVERIFY
995 bool "Enable write verify"
998 Enable the verify after the buffer write useful for debugging purpose.
1002 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
1003 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1009 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1012 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1017 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1020 tristate "SMSC LAN911[5678] support"
1023 depends on ARM || SUPERH
1025 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1026 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1027 Say Y if you want it compiled into the kernel,
1028 and read the Ethernet-HOWTO, available from
1029 <http://www.tldp.org/docs.html#howto>.
1031 This driver is also available as a module. The module will be
1032 called smc911x. If you want to compile it as a module, say M
1033 here and read <file:Documentation/kbuild/modules.txt>
1036 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1037 depends on ARM || SUPERH || BLACKFIN || MIPS
1042 Say Y here if you want support for SMSC LAN911x and LAN921x families
1043 of ethernet controllers.
1045 To compile this driver as a module, choose M here and read
1046 <file:Documentation/networking/net-modules.txt>. The module
1047 will be called smsc911x.
1049 config NET_VENDOR_RACAL
1050 bool "Racal-Interlan (Micom) NI cards"
1053 If you have a network (Ethernet) card belonging to this class, such
1054 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1055 available from <http://www.tldp.org/docs.html#howto>.
1057 Note that the answer to this question doesn't directly affect the
1058 kernel: saying N will just cause the configurator to skip all
1059 the questions about NI cards. If you say Y, you will be asked for
1060 your specific card in the following questions.
1063 tristate "NI5010 support (EXPERIMENTAL)"
1064 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1066 If you have a network (Ethernet) card of this type, say Y and read
1067 the Ethernet-HOWTO, available from
1068 <http://www.tldp.org/docs.html#howto>. Note that this is still
1071 To compile this driver as a module, choose M here. The module
1072 will be called ni5010.
1075 tristate "NI5210 support"
1076 depends on NET_VENDOR_RACAL && ISA
1078 If you have a network (Ethernet) card of this type, say Y and read
1079 the Ethernet-HOWTO, available from
1080 <http://www.tldp.org/docs.html#howto>.
1082 To compile this driver as a module, choose M here. The module
1083 will be called ni52.
1086 tristate "NI6510 support"
1087 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1089 If you have a network (Ethernet) card of this type, say Y and read
1090 the Ethernet-HOWTO, available from
1091 <http://www.tldp.org/docs.html#howto>.
1093 To compile this driver as a module, choose M here. The module
1094 will be called ni65.
1097 tristate "Dave ethernet support (DNET)"
1098 depends on NET_ETHERNET && HAS_IOMEM
1101 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1102 Say Y to include support for the DNET chip.
1104 To compile this driver as a module, choose M here: the module
1105 will be called dnet.
1107 source "drivers/net/tulip/Kconfig"
1110 tristate "AT1700/1720 support (EXPERIMENTAL)"
1111 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1114 If you have a network (Ethernet) card of this type, say Y and read
1115 the Ethernet-HOWTO, available from
1116 <http://www.tldp.org/docs.html#howto>.
1118 To compile this driver as a module, choose M here. The module
1119 will be called at1700.
1122 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1123 depends on ISA || EISA || MCA
1126 If you have a network (Ethernet) card of this type, say Y and read
1127 the Ethernet-HOWTO, available from
1128 <http://www.tldp.org/docs.html#howto> as well as
1129 <file:drivers/net/depca.c>.
1131 To compile this driver as a module, choose M here. The module
1132 will be called depca.
1135 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1136 depends on ISA || EISA || PCI
1138 If you have a network (Ethernet) card of this type, say Y and read
1139 the Ethernet-HOWTO, available from
1140 <http://www.tldp.org/docs.html#howto>.
1142 To compile this driver as a module, choose M here. The module
1143 will be called hp100.
1146 bool "Other ISA cards"
1149 If your network (Ethernet) card hasn't been mentioned yet and its
1150 bus system (that's the way the cards talks to the other components
1151 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1152 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1153 available from <http://www.tldp.org/docs.html#howto>.
1157 Note that the answer to this question doesn't directly affect the
1158 kernel: saying N will just cause the configurator to skip all
1159 the remaining ISA network card questions. If you say Y, you will be
1160 asked for your specific card in the following questions.
1163 tristate "Cabletron E21xx support"
1167 If you have a network (Ethernet) card of this type, say Y and read
1168 the Ethernet-HOWTO, available from
1169 <http://www.tldp.org/docs.html#howto>.
1171 To compile this driver as a module, choose M here. The module
1172 will be called e2100.
1175 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1179 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1180 cards. If this is for you, say Y and read
1181 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1182 well as the Ethernet-HOWTO, available from
1183 <http://www.tldp.org/docs.html#howto>.
1185 To compile this driver as a module, choose M here. The module
1186 will be called ewrk3.
1189 tristate "EtherExpress 16 support"
1192 If you have an EtherExpress16 network (Ethernet) card, say Y and
1193 read the Ethernet-HOWTO, available from
1194 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1195 EtherExpress16 card used to be regarded as a very poor choice
1196 because the driver was very unreliable. We now have a new driver
1197 that should do better.
1199 To compile this driver as a module, choose M here. The module
1200 will be called eexpress.
1203 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1206 If you have a network (Ethernet) card of this type, say Y. This
1207 driver supports Intel i82595{FX,TX} based boards. Note however
1208 that the EtherExpress PRO/100 Ethernet card has its own separate
1209 driver. Please read the Ethernet-HOWTO, available from
1210 <http://www.tldp.org/docs.html#howto>.
1212 To compile this driver as a module, choose M here. The module
1213 will be called eepro.
1216 tristate "HP PCLAN+ (27247B and 27252A) support"
1220 If you have a network (Ethernet) card of this type, say Y and read
1221 the Ethernet-HOWTO, available from
1222 <http://www.tldp.org/docs.html#howto>.
1224 To compile this driver as a module, choose M here. The module
1225 will be called hp-plus.
1228 tristate "HP PCLAN (27245 and other 27xxx series) support"
1232 If you have a network (Ethernet) card of this type, say Y and read
1233 the Ethernet-HOWTO, available from
1234 <http://www.tldp.org/docs.html#howto>.
1236 To compile this driver as a module, choose M here. The module
1240 tristate "LP486E on board Ethernet"
1243 Say Y here to support the 82596-based on-board Ethernet controller
1244 for the Panther motherboard, which is one of the two shipped in the
1245 Intel Professional Workstation.
1248 tristate "ICL EtherTeam 16i/32 support"
1251 If you have a network (Ethernet) card of this type, say Y and read
1252 the Ethernet-HOWTO, available from
1253 <http://www.tldp.org/docs.html#howto>.
1255 To compile this driver as a module, choose M here. The module
1256 will be called eth16i.
1259 tristate "NE2000/NE1000 support"
1260 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1263 If you have a network (Ethernet) card of this type, say Y and read
1264 the Ethernet-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1266 without a specific driver are compatible with NE2000.
1268 If you have a PCI NE2000 card however, say N here and Y to "PCI
1269 NE2000 and clone support" under "EISA, VLB, PCI and on board
1270 controllers" below. If you have a NE2000 card and are running on
1271 an MCA system (a bus system used on some IBM PS/2 computers and
1272 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1275 To compile this driver as a module, choose M here. The module
1279 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1280 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1282 The Zenith Z-Note notebook computer has a built-in network
1283 (Ethernet) card, and this is the Linux driver for it. Note that the
1284 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1285 by this driver. Read the Ethernet-HOWTO, available from
1286 <http://www.tldp.org/docs.html#howto>.
1289 tristate "SEEQ8005 support (EXPERIMENTAL)"
1290 depends on NET_ISA && EXPERIMENTAL
1292 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1293 is for you, read the Ethernet-HOWTO, available from
1294 <http://www.tldp.org/docs.html#howto>.
1296 To compile this driver as a module, choose M here. The module
1297 will be called seeq8005.
1300 tristate "NE/2 (ne2000 MCA version) support"
1301 depends on MCA_LEGACY
1304 If you have a network (Ethernet) card of this type, say Y and read
1305 the Ethernet-HOWTO, available from
1306 <http://www.tldp.org/docs.html#howto>.
1308 To compile this driver as a module, choose M here. The module
1312 tristate "IBM LAN Adapter/A support"
1315 This is a Micro Channel Ethernet adapter. You need to set
1316 CONFIG_MCA to use this driver. It is both available as an in-kernel
1317 driver and as a module.
1319 To compile this driver as a module, choose M here. The only
1320 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1321 will both support 16K and 32K memory windows, however a 32K window
1322 gives a better security against packet losses. Usage of multiple
1323 boards with this driver should be possible, but has not been tested
1324 up to now due to lack of hardware.
1327 tristate "IBM LAN Virtual Ethernet support"
1328 depends on PPC_PSERIES
1330 This driver supports virtual ethernet adapters on newer IBM iSeries
1331 and pSeries systems.
1333 To compile this driver as a module, choose M here. The module will
1336 source "drivers/net/ibm_newemac/Kconfig"
1339 bool "EISA, VLB, PCI and on board controllers"
1340 depends on ISA || EISA || PCI
1342 This is another class of network cards which attach directly to the
1343 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1344 available from <http://www.tldp.org/docs.html#howto>.
1346 Note that the answer to this question doesn't directly affect the
1347 kernel: saying N will just cause the configurator to skip all
1348 the questions about this class of network cards. If you say Y, you
1349 will be asked for your specific card in the following questions. If
1350 you are unsure, say Y.
1353 tristate "AMD PCnet32 PCI support"
1354 depends on NET_PCI && PCI
1358 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1359 answer Y here and read the Ethernet-HOWTO, available from
1360 <http://www.tldp.org/docs.html#howto>.
1362 To compile this driver as a module, choose M here. The module
1363 will be called pcnet32.
1366 tristate "AMD 8111 (new PCI lance) support"
1367 depends on NET_PCI && PCI
1371 If you have an AMD 8111-based PCI lance ethernet card,
1372 answer Y here and read the Ethernet-HOWTO, available from
1373 <http://www.tldp.org/docs.html#howto>.
1375 To compile this driver as a module, choose M here. The module
1376 will be called amd8111e.
1378 config ADAPTEC_STARFIRE
1379 tristate "Adaptec Starfire/DuraLAN support"
1380 depends on NET_PCI && PCI
1384 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1385 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1386 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1389 To compile this driver as a module, choose M here: the module
1390 will be called starfire. This is recommended.
1393 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1394 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1397 If you have a network (Ethernet) card of this type, say Y and read
1398 the Ethernet-HOWTO, available from
1399 <http://www.tldp.org/docs.html#howto>.
1401 To compile this driver as a module, choose M here. The module
1402 will be called ac3200.
1405 tristate "Micrel KSZ8841/2 PCI"
1406 depends on NET_PCI && PCI
1410 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1412 To compile this driver as a module, choose M here. The module
1413 will be called ksz884x.
1416 tristate "Apricot Xen-II on board Ethernet"
1417 depends on NET_PCI && ISA
1419 If you have a network (Ethernet) controller of this type, say Y and
1420 read the Ethernet-HOWTO, available from
1421 <http://www.tldp.org/docs.html#howto>.
1423 To compile this driver as a module, choose M here. The module
1424 will be called apricot.
1427 tristate "Broadcom 440x/47xx ethernet support"
1428 depends on SSB_POSSIBLE && HAS_DMA
1432 If you have a network (Ethernet) controller of this type, say Y
1433 or M and read the Ethernet-HOWTO, available from
1434 <http://www.tldp.org/docs.html#howto>.
1436 To compile this driver as a module, choose M here. The module
1439 # Auto-select SSB PCI-HOST support, if possible
1440 config B44_PCI_AUTOSELECT
1442 depends on B44 && SSB_PCIHOST_POSSIBLE
1446 # Auto-select SSB PCICORE driver, if possible
1447 config B44_PCICORE_AUTOSELECT
1449 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1450 select SSB_DRIVER_PCICORE
1455 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1459 tristate "nForce Ethernet support"
1460 depends on NET_PCI && PCI
1462 If you have a network (Ethernet) controller of this type, say Y and
1463 read the Ethernet-HOWTO, available from
1464 <http://www.tldp.org/docs.html#howto>.
1466 To compile this driver as a module, choose M here. The module
1467 will be called forcedeth.
1470 tristate "CS89x0 support"
1471 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1472 || ARCH_IXDP2X01 || MACH_MX31ADS)
1474 Support for CS89x0 chipset based Ethernet cards. If you have a
1475 network (Ethernet) card of this type, say Y and read the
1476 Ethernet-HOWTO, available from
1477 <http://www.tldp.org/docs.html#howto> as well as
1478 <file:Documentation/networking/cs89x0.txt>.
1480 To compile this driver as a module, choose M here. The module
1481 will be called cs89x0.
1483 config CS89x0_NONISA_IRQ
1485 depends on CS89x0 != n
1486 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS
1489 tristate "TOSHIBA TC35815 Ethernet support"
1490 depends on NET_PCI && PCI && MIPS
1494 tristate "Intel(R) PRO/100+ support"
1495 depends on NET_PCI && PCI
1498 This driver supports Intel(R) PRO/100 family of adapters.
1499 To verify that your adapter is supported, find the board ID number
1500 on the adapter. Look for a label that has a barcode and a number
1501 in the format 123456-001 (six digits hyphen three digits).
1503 Use the above information and the Adapter & Driver ID Guide at:
1505 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1507 to identify the adapter.
1509 For the latest Intel PRO/100 network driver for Linux, see:
1511 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1513 More specific information on configuring the driver is in
1514 <file:Documentation/networking/e100.txt>.
1516 To compile this driver as a module, choose M here. The module
1517 will be called e100.
1520 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1521 depends on NET_PCI && EISA && EXPERIMENTAL
1524 If you have a network (Ethernet) card of this type, say Y and read
1525 the Ethernet-HOWTO, available from
1526 <http://www.tldp.org/docs.html#howto>.
1528 To compile this driver as a module, choose M here. The module
1529 will be called lne390.
1532 tristate "Myson MTD-8xx PCI Ethernet support"
1533 depends on NET_PCI && PCI
1537 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1538 cards. <http://www.myson.com.tw/>
1541 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1542 depends on NET_PCI && PCI
1545 This driver is for the National Semiconductor DP83810 series,
1546 which is used in cards from PureData, NetGear, Linksys
1547 and others, including the 83815 chip.
1548 More specific information and updates are available from
1549 <http://www.scyld.com/network/natsemi.html>.
1552 tristate "PCI NE2000 and clones support (see help)"
1553 depends on NET_PCI && PCI
1556 This driver is for NE2000 compatible PCI cards. It will not work
1557 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1558 support" below). If you have a PCI NE2000 network (Ethernet) card,
1559 say Y and read the Ethernet-HOWTO, available from
1560 <http://www.tldp.org/docs.html#howto>.
1562 This driver also works for the following NE2000 clone cards:
1563 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1564 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1565 Holtek HT80232 Holtek HT80229
1567 To compile this driver as a module, choose M here. The module
1568 will be called ne2k-pci.
1571 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1572 depends on NET_PCI && EISA && EXPERIMENTAL
1575 If you have a network (Ethernet) card of this type, say Y and read
1576 the Ethernet-HOWTO, available from
1577 <http://www.tldp.org/docs.html#howto>. Note that this driver
1578 will NOT WORK for NE3200 cards as they are completely different.
1580 To compile this driver as a module, choose M here. The module
1581 will be called ne3210.
1584 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1585 depends on NET_PCI && EISA && EXPERIMENTAL
1588 If you have a network (Ethernet) card of this type, say Y and read
1589 the Ethernet-HOWTO, available from
1590 <http://www.tldp.org/docs.html#howto>.
1592 To compile this driver as a module, choose M here. The module
1593 will be called es3210.
1596 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1597 depends on NET_PCI && PCI && EXPERIMENTAL
1601 This is a driver for the Fast Ethernet PCI network cards based on
1602 the RTL8139C+ chips. If you have one of those, say Y and read
1603 the Ethernet-HOWTO, available from
1604 <http://www.tldp.org/docs.html#howto>.
1606 To compile this driver as a module, choose M here: the module
1607 will be called 8139cp. This is recommended.
1610 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1611 depends on NET_PCI && PCI
1615 This is a driver for the Fast Ethernet PCI network cards based on
1616 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1617 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1619 To compile this driver as a module, choose M here: the module
1620 will be called 8139too. This is recommended.
1623 bool "Use PIO instead of MMIO"
1627 This instructs the driver to use programmed I/O ports (PIO) instead
1628 of PCI shared memory (MMIO). This can possibly solve some problems
1629 in case your mainboard has memory consistency issues. If unsure,
1632 config 8139TOO_TUNE_TWISTER
1633 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1636 This implements a function which might come in handy in case you
1637 are using low quality on long cabling. It is required for RealTek
1638 RTL-8139 revision K boards, and totally unused otherwise. It tries
1639 to match the transceiver to the cable characteristics. This is
1640 experimental since hardly documented by the manufacturer.
1644 bool "Support for older RTL-8129/8130 boards"
1647 This enables support for the older and uncommon RTL-8129 and
1648 RTL-8130 chips, which support MII via an external transceiver,
1649 instead of an internal one. Disabling this option will save some
1650 memory by making the code size smaller. If unsure, say Y.
1652 config 8139_OLD_RX_RESET
1653 bool "Use older RX-reset method"
1656 The 8139too driver was recently updated to contain a more rapid
1657 reset sequence, in the face of severe receive errors. This "new"
1658 RX-reset method should be adequate for all boards. But if you
1659 experience problems, you can enable this option to restore the
1660 old RX-reset behavior. If unsure, say N.
1663 tristate "RDC R6040 Fast Ethernet Adapter support"
1664 depends on NET_PCI && PCI
1669 This is a driver for the R6040 Fast Ethernet MACs found in the
1670 the RDC R-321x System-on-chips.
1672 To compile this driver as a module, choose M here: the module
1673 will be called r6040. This is recommended.
1676 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1677 depends on NET_PCI && PCI
1681 This is a driver for the Fast Ethernet PCI network cards based on
1682 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1683 SiS 630 and SiS 540 chipsets.
1685 This driver also supports AMD 79C901 HomePNA so that you can use
1686 your phone line as a network cable.
1688 To compile this driver as a module, choose M here: the module
1689 will be called sis900. This is recommended.
1692 tristate "SMC EtherPower II"
1693 depends on NET_PCI && PCI
1697 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1698 which is based on the SMC83c17x (EPIC/100).
1699 More specific information and updates are available from
1700 <http://www.scyld.com/network/epic100.html>.
1703 tristate "SMSC LAN9420 PCI ethernet adapter support"
1704 depends on NET_PCI && PCI
1709 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1710 Say Y if you want it compiled into the kernel,
1711 and read the Ethernet-HOWTO, available from
1712 <http://www.tldp.org/docs.html#howto>.
1714 This driver is also available as a module. The module will be
1715 called smsc9420. If you want to compile it as a module, say M
1716 here and read <file:Documentation/kbuild/modules.txt>
1719 tristate "Sundance Alta support"
1720 depends on NET_PCI && PCI
1724 This driver is for the Sundance "Alta" chip.
1725 More specific information and updates are available from
1726 <http://www.scyld.com/network/sundance.html>.
1728 config SUNDANCE_MMIO
1729 bool "Use MMIO instead of PIO"
1732 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1733 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1734 is known to solve bugs on certain chips.
1739 tristate "TI ThunderLAN support"
1740 depends on NET_PCI && (PCI || EISA)
1742 If you have a PCI Ethernet network card based on the ThunderLAN chip
1743 which is supported by this driver, say Y and read the
1744 Ethernet-HOWTO, available from
1745 <http://www.tldp.org/docs.html#howto>.
1747 Devices currently supported by this driver are Compaq Netelligent,
1748 Compaq NetFlex and Olicom cards. Please read the file
1749 <file:Documentation/networking/tlan.txt> for more details.
1751 To compile this driver as a module, choose M here. The module
1752 will be called tlan.
1754 Please email feedback to <torben.mathiasen@compaq.com>.
1757 tristate "Micrel KSZ8841/42 with generic bus interface"
1758 depends on HAS_IOMEM && DMA_ENGINE
1760 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1761 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1765 tristate "Micrel KS8851 SPI"
1770 SPI driver for Micrel KS8851 SPI attached network chip.
1773 tristate "Micrel KS8851 MLL"
1774 depends on HAS_IOMEM
1777 This platform driver is for Micrel KS8851 Address/data bus
1778 multiplexed network chip.
1781 tristate "VIA Rhine support"
1782 depends on NET_PCI && PCI
1786 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1787 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1788 Ethernet functions can also be found integrated on South Bridges
1791 To compile this driver as a module, choose M here. The module
1792 will be called via-rhine.
1794 config VIA_RHINE_MMIO
1795 bool "Use MMIO instead of PIO"
1796 depends on VIA_RHINE
1798 This instructs the driver to use PCI shared memory (MMIO) instead of
1799 programmed I/O ports (PIO). Enabling this gives an improvement in
1800 processing time in parts of the driver.
1805 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1806 depends on NET_PCI && PCI && EXPERIMENTAL
1809 This is a driver for the Fast Ethernet PCI network cards based on
1810 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1811 have one of these, say Y here.
1813 To compile this driver as a module, choose M here: the module
1814 will be called sc92031. This is recommended.
1817 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1818 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1821 TI AR7 CPMAC Ethernet support
1824 bool "Pocket and portable adapters"
1827 Cute little network (Ethernet) devices which attach to the parallel
1828 port ("pocket adapters"), commonly used with laptops. If you have
1829 one of those, say Y and read the Ethernet-HOWTO, available from
1830 <http://www.tldp.org/docs.html#howto>.
1832 If you want to plug a network (or some other) card into the PCMCIA
1833 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1834 credit card size extension cards used by all modern laptops), you
1835 need the pcmcia-cs package (location contained in the file
1836 <file:Documentation/Changes>) and you can say N here.
1838 Laptop users should read the Linux Laptop home page at
1839 <http://www.linux-on-laptops.com/> or
1840 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1842 Note that the answer to this question doesn't directly affect the
1843 kernel: saying N will just cause the configurator to skip all
1844 the questions about this class of network devices. If you say Y, you
1845 will be asked for your specific device in the following questions.
1848 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1849 depends on NET_POCKET && PARPORT && X86
1852 This is a network (Ethernet) device which attaches to your parallel
1853 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1854 available from <http://www.tldp.org/docs.html#howto>, if you
1855 want to use this. If you intend to use this driver, you should have
1856 said N to the "Parallel printer support", because the two drivers
1857 don't like each other.
1859 To compile this driver as a module, choose M here: the module
1863 tristate "D-Link DE600 pocket adapter support"
1864 depends on NET_POCKET && PARPORT
1866 This is a network (Ethernet) device which attaches to your parallel
1867 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1868 Ethernet-HOWTO, available from
1869 <http://www.tldp.org/docs.html#howto>, if you want to use
1870 this. It is possible to have several devices share a single parallel
1871 port and it is safe to compile the corresponding drivers into the
1874 To compile this driver as a module, choose M here: the module
1875 will be called de600.
1878 tristate "D-Link DE620 pocket adapter support"
1879 depends on NET_POCKET && PARPORT
1881 This is a network (Ethernet) device which attaches to your parallel
1882 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1883 Ethernet-HOWTO, available from
1884 <http://www.tldp.org/docs.html#howto>, if you want to use
1885 this. It is possible to have several devices share a single parallel
1886 port and it is safe to compile the corresponding drivers into the
1889 To compile this driver as a module, choose M here: the module
1890 will be called de620.
1893 tristate "SGI Seeq ethernet controller support"
1894 depends on SGI_HAS_SEEQ
1896 Say Y here if you have an Seeq based Ethernet network card. This is
1897 used in many Silicon Graphics machines.
1900 tristate "DEC LANCE ethernet controller support"
1901 depends on MACH_DECSTATION
1904 This driver is for the series of Ethernet controllers produced by
1905 DEC (now Compaq) based on the AMD Lance chipset, including the
1906 DEPCA series. (This chipset is better known via the NE2100 cards.)
1909 bool "Motorola 68360 ethernet controller"
1912 Say Y here if you want to use the built-in ethernet controller of
1913 the Motorola 68360 processor.
1916 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1917 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1918 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1921 Say Y here if you want to use the built-in 10/100 Fast ethernet
1922 controller on some Motorola ColdFire and Freescale i.MX processors.
1925 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1928 Say Y here if you want to use the second built-in 10/100 Fast
1929 ethernet controller on some Motorola ColdFire processors.
1932 tristate "MPC52xx FEC driver"
1933 depends on PPC_MPC52xx && PPC_BESTCOMM
1936 select PPC_BESTCOMM_FEC
1938 This option enables support for the MPC5200's on-chip
1939 Fast Ethernet Controller
1940 If compiled as module, it will be called fec_mpc52xx.
1942 config FEC_MPC52xx_MDIO
1943 bool "MPC52xx FEC MDIO bus driver"
1944 depends on FEC_MPC52xx
1947 The MPC5200's FEC can connect to the Ethernet either with
1948 an external MII PHY chip or 10 Mbps 7-wire interface
1949 (Motorola? industry standard).
1950 If your board uses an external PHY connected to FEC, enable this.
1951 If not sure, enable.
1952 If compiled as module, it will be called fec_mpc52xx_phy.
1955 tristate "NE2000 compatible support for H8/300"
1958 Say Y here if you want to use the NE2000 compatible
1959 controller on the Renesas H8/300 processor.
1962 tristate "Atheros L2 Fast Ethernet support"
1967 This driver supports the Atheros L2 fast ethernet adapter.
1969 To compile this driver as a module, choose M here. The module
1970 will be called atl2.
1972 config XILINX_EMACLITE
1973 tristate "Xilinx 10/100 Ethernet Lite support"
1974 depends on PPC32 || MICROBLAZE
1977 This driver supports the 10/100 Ethernet Lite from Xilinx.
1980 tristate "Broadcom 63xx internal mac support"
1985 This driver supports the ethernet MACs in the Broadcom 63xx
1986 MIPS chipset family (BCM63XX).
1988 source "drivers/net/fs_enet/Kconfig"
1990 source "drivers/net/octeon/Kconfig"
1992 endif # NET_ETHERNET
1998 menuconfig NETDEV_1000
1999 bool "Ethernet (1000 Mbit)"
2003 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2004 type of Local Area Network (LAN) in universities and companies.
2006 Say Y here to get to see options for Gigabit Ethernet drivers.
2007 This option alone does not add any kernel code.
2008 Note that drivers supporting both 100 and 1000 MBit may be listed
2009 under "Ethernet (10 or 100MBit)" instead.
2011 If you say N, all options in this submenu will be skipped and disabled.
2016 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2019 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2020 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2021 adapter. The driver allows for using the Jumbo Frame option (9000
2022 bytes/frame) however it requires that your switches can handle this
2023 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2026 To compile this driver as a module, choose M here: the
2027 module will be called acenic.
2029 config ACENIC_OMIT_TIGON_I
2030 bool "Omit support for old Tigon I based AceNICs"
2033 Say Y here if you only have Tigon II based AceNICs and want to leave
2034 out support for the older Tigon I based cards which are no longer
2035 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2036 version)). This will reduce the size of the driver object by
2037 app. 100KB. If you are not sure whether your card is a Tigon I or a
2038 Tigon II, say N here.
2040 The safe and default value for this is N.
2043 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2047 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2049 D-Link DGE-550T Gigabit Ethernet Adapter.
2050 D-Link DL2000-based Gigabit Ethernet Adapter.
2051 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2053 To compile this driver as a module, choose M here: the
2054 module will be called dl2k.
2057 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2060 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2061 adapters. For more information on how to identify your adapter, go
2062 to the Adapter & Driver ID Guide at:
2064 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2066 For general information and support, go to the Intel support
2069 <http://support.intel.com>
2071 More specific information on configuring the driver is in
2072 <file:Documentation/networking/e1000.txt>.
2074 To compile this driver as a module, choose M here. The module
2075 will be called e1000.
2078 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2079 depends on PCI && (!SPARC32 || BROKEN)
2081 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2082 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2083 use the regular e1000 driver For more information on how to
2084 identify your adapter, go to the Adapter & Driver ID Guide at:
2086 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2088 For general information and support, go to the Intel support
2091 <http://support.intel.com>
2093 To compile this driver as a module, choose M here. The module
2094 will be called e1000e.
2097 tristate "IP1000 Gigabit Ethernet support"
2098 depends on PCI && EXPERIMENTAL
2101 This driver supports IP1000 gigabit Ethernet cards.
2103 To compile this driver as a module, choose M here: the module
2104 will be called ipg. This is recommended.
2107 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2110 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2111 adapters. For more information on how to identify your adapter, go
2112 to the Adapter & Driver ID Guide at:
2114 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2116 For general information and support, go to the Intel support
2119 <http://support.intel.com>
2121 More specific information on configuring the driver is in
2122 <file:Documentation/networking/e1000.txt>.
2124 To compile this driver as a module, choose M here. The module
2128 bool "Direct Cache Access (DCA) Support"
2130 depends on IGB && DCA && !(IGB=y && DCA=m)
2132 Say Y here if you want to use Direct Cache Access (DCA) in the
2133 driver. DCA is a method for warming the CPU cache before data
2134 is used, with the intent of lessening the impact of cache misses.
2137 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2140 This driver supports Intel(R) 82576 virtual functions. For more
2141 information on how to identify your adapter, go to the Adapter &
2144 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2146 For general information and support, go to the Intel support
2149 <http://support.intel.com>
2151 More specific information on configuring the driver is in
2152 <file:Documentation/networking/e1000.txt>.
2154 To compile this driver as a module, choose M here. The module
2155 will be called igbvf.
2157 source "drivers/net/ixp2000/Kconfig"
2160 tristate "MyriCOM Gigabit Ethernet support"
2163 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2165 To compile this driver as a module, choose M here: the module
2166 will be called myri_sbus. This is recommended.
2169 tristate "National Semiconductor DP83820 support"
2172 This is a driver for the National Semiconductor DP83820 series
2173 of gigabit ethernet MACs. Cards using this chipset include
2174 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2175 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2179 tristate "Packet Engines Hamachi GNIC-II support"
2183 If you have a Gigabit Ethernet card of this type, say Y and read
2184 the Ethernet-HOWTO, available from
2185 <http://www.tldp.org/docs.html#howto>.
2187 To compile this driver as a module, choose M here. The module will be
2191 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2192 depends on PCI && EXPERIMENTAL
2195 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2196 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2197 used by the Beowulf Linux cluster project. See
2198 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2199 information about this driver in particular and Beowulf in general.
2201 To compile this driver as a module, choose M here: the module
2202 will be called yellowfin. This is recommended.
2205 tristate "Realtek 8169 gigabit ethernet support"
2210 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2212 To compile this driver as a module, choose M here: the module
2213 will be called r8169. This is recommended.
2217 depends on R8169 && VLAN_8021Q
2219 Say Y here for the r8169 driver to support the functions required
2220 by the kernel 802.1Q code.
2225 tristate "SB1250 Gigabit Ethernet support"
2226 depends on SIBYTE_SB1xxx_SOC
2229 This driver supports Gigabit Ethernet interfaces based on the
2230 Broadcom SiByte family of System-On-a-Chip parts. They include
2231 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2234 To compile this driver as a module, choose M here: the module
2235 will be called sb1250-mac.
2238 tristate "SiS190/SiS191 gigabit ethernet support"
2243 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2244 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2245 appear in lan on motherboard designs which are based on SiS 965
2246 and SiS 966 south bridge.
2248 To compile this driver as a module, choose M here: the module
2249 will be called sis190. This is recommended.
2252 tristate "New SysKonnect GigaEthernet support"
2256 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2257 and related Gigabit Ethernet adapters. It is a new smaller driver
2258 with better performance and more complete ethtool support.
2260 It does not support the link failover and network management
2261 features that "portable" vendor supplied sk98lin driver does.
2263 This driver supports adapters based on the original Yukon chipset:
2264 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2265 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2267 It does not support the newer Yukon2 chipset: a separate driver,
2268 sky2, is provided for Yukon2-based adapters.
2270 To compile this driver as a module, choose M here: the module
2271 will be called skge. This is recommended.
2274 bool "Debugging interface"
2275 depends on SKGE && DEBUG_FS
2277 This option adds the ability to dump driver state for debugging.
2278 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2279 transmit and receive rings.
2284 tristate "SysKonnect Yukon2 support"
2288 This driver supports Gigabit Ethernet adapters based on the
2289 Marvell Yukon 2 chipset:
2290 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2291 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2293 There is companion driver for the older Marvell Yukon and
2294 Genesis based adapters: skge.
2296 To compile this driver as a module, choose M here: the module
2297 will be called sky2. This is recommended.
2300 bool "Debugging interface"
2301 depends on SKY2 && DEBUG_FS
2303 This option adds the ability to dump driver state for debugging.
2304 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2305 transmit and receive rings.
2310 tristate "VIA Velocity support"
2316 If you have a VIA "Velocity" based network card say Y here.
2318 To compile this driver as a module, choose M here. The module
2319 will be called via-velocity.
2322 tristate "Broadcom Tigon3 support"
2326 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2328 To compile this driver as a module, choose M here: the module
2329 will be called tg3. This is recommended.
2332 tristate "Broadcom NetXtremeII support"
2337 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2339 To compile this driver as a module, choose M here: the module
2340 will be called bnx2. This is recommended.
2343 tristate "Broadcom CNIC support"
2348 This driver supports offload features of Broadcom NetXtremeII
2349 gigabit Ethernet cards.
2351 To compile this driver as a module, choose M here: the module
2352 will be called cnic. This is recommended.
2355 tristate "Spider Gigabit Ethernet driver"
2356 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2359 This driver supports the Gigabit Ethernet chips present on the
2360 Cell Processor-Based Blades from IBM.
2363 tristate "Tundra TSI108 gigabit Ethernet support"
2364 depends on TSI108_BRIDGE
2366 This driver supports Tundra TSI108 gigabit Ethernet ports.
2367 To compile this driver as a module, choose M here: the module
2368 will be called tsi108_eth.
2371 tristate "PS3 Gigabit Ethernet driver"
2373 select PS3_SYS_MANAGER
2375 This driver supports the network device on the PS3 game
2376 console. This driver has built-in support for Ethernet.
2378 To compile this driver as a module, choose M here: the
2379 module will be called ps3_gelic.
2381 config GELIC_WIRELESS
2382 bool "PS3 Wireless support"
2384 depends on GELIC_NET
2387 This option adds the support for the wireless feature of PS3.
2388 If you have the wireless-less model of PS3 or have no plan to
2389 use wireless feature, disabling this option saves memory. As
2390 the driver automatically distinguishes the models, you can
2391 safely enable this option even if you have a wireless-less model.
2394 tristate "Freescale PQ MDIO"
2398 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2401 tristate "Gianfar Ethernet"
2407 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2408 and MPC86xx family of chips, and the FEC on the 8540.
2411 tristate "Freescale QE Gigabit Ethernet"
2412 depends on QUICC_ENGINE
2416 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2417 which is available on some Freescale SOCs.
2419 config UGETH_TX_ON_DEMAND
2420 bool "Transmit on Demand support"
2424 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2425 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2429 This driver supports the gigabit ethernet MACs in the
2430 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2431 in the Marvell Orion ARM SoC family.
2433 Some boards that use the Discovery chipset are the Momenco
2434 Ocelot C and Jaguar ATX and Pegasos II.
2436 config XILINX_LL_TEMAC
2437 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2438 depends on PPC || MICROBLAZE
2441 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2442 core used in Xilinx Spartan and Virtex FPGAs
2445 tristate "QLogic QLA3XXX Network Driver Support"
2448 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2450 To compile this driver as a module, choose M here: the module
2451 will be called qla3xxx.
2454 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2459 This driver supports the Atheros/Attansic L1 gigabit ethernet
2462 To compile this driver as a module, choose M here. The module
2463 will be called atl1.
2466 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2467 depends on PCI && EXPERIMENTAL
2471 This driver supports the Atheros L1E gigabit ethernet adapter.
2473 To compile this driver as a module, choose M here. The module
2474 will be called atl1e.
2477 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2478 depends on PCI && EXPERIMENTAL
2482 This driver supports the Atheros L1C gigabit ethernet adapter.
2484 To compile this driver as a module, choose M here. The module
2485 will be called atl1c.
2488 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2493 This driver supports the PCI-Express gigabit ethernet adapters
2494 based on JMicron JMC250 chipset.
2496 To compile this driver as a module, choose M here. The module
2500 tristate "S6105 GMAC ethernet support"
2501 depends on XTENSA_VARIANT_S6000
2504 This driver supports the on chip ethernet device on the
2505 S6105 xtensa processor.
2507 To compile this driver as a module, choose M here. The module
2508 will be called s6gmac.
2510 source "drivers/net/stmmac/Kconfig"
2513 tristate "PCH Gigabit Ethernet"
2516 This is a gigabit ethernet driver for Topcliff PCH.
2517 Topcliff PCH is the platform controller hub that is used in Intel's
2518 general embedded platform.
2519 Topcliff PCH has Gigabit Ethernet interface.
2520 Using this interface, it is able to access system devices connected
2521 to Gigabit Ethernet.
2522 This driver enables Gigabit Ethernet function.
2527 # 10 Gigabit Ethernet
2530 menuconfig NETDEV_10000
2531 bool "Ethernet (10000 Mbit)"
2535 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2536 This option alone does not add any kernel code.
2538 If you say N, all options in this submenu will be skipped and disabled.
2546 tristate "Chelsio 10Gb Ethernet support"
2551 This driver supports Chelsio gigabit and 10-gigabit
2552 Ethernet cards. More information about adapter features and
2553 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2555 For general information about Chelsio and our products, visit
2556 our website at <http://www.chelsio.com>.
2558 For customer support, please visit our customer support page at
2559 <http://www.chelsio.com/support.html>.
2561 Please send feedback to <linux-bugs@chelsio.com>.
2563 To compile this driver as a module, choose M here: the module
2564 will be called cxgb.
2566 config CHELSIO_T1_1G
2567 bool "Chelsio gigabit Ethernet support"
2568 depends on CHELSIO_T1
2570 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2571 are using only 10G cards say 'N' here.
2573 config CHELSIO_T3_DEPENDS
2575 depends on PCI && INET
2579 tristate "Chelsio Communications T3 10Gb Ethernet support"
2580 depends on CHELSIO_T3_DEPENDS
2584 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2587 For general information about Chelsio and our products, visit
2588 our website at <http://www.chelsio.com>.
2590 For customer support, please visit our customer support page at
2591 <http://www.chelsio.com/support.html>.
2593 Please send feedback to <linux-bugs@chelsio.com>.
2595 To compile this driver as a module, choose M here: the module
2596 will be called cxgb3.
2598 config CHELSIO_T4_DEPENDS
2600 depends on PCI && INET
2604 tristate "Chelsio Communications T4 Ethernet support"
2605 depends on CHELSIO_T4_DEPENDS
2609 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2612 For general information about Chelsio and our products, visit
2613 our website at <http://www.chelsio.com>.
2615 For customer support, please visit our customer support page at
2616 <http://www.chelsio.com/support.html>.
2618 Please send feedback to <linux-bugs@chelsio.com>.
2620 To compile this driver as a module choose M here; the module
2621 will be called cxgb4.
2623 config CHELSIO_T4VF_DEPENDS
2625 depends on PCI && INET
2629 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2630 depends on CHELSIO_T4VF_DEPENDS
2632 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2633 adapters with PCI-E SR-IOV Virtual Functions.
2635 For general information about Chelsio and our products, visit
2636 our website at <http://www.chelsio.com>.
2638 For customer support, please visit our customer support page at
2639 <http://www.chelsio.com/support.html>.
2641 Please send feedback to <linux-bugs@chelsio.com>.
2643 To compile this driver as a module choose M here; the module
2644 will be called cxgb4vf.
2647 tristate "eHEA Ethernet support"
2648 depends on IBMEBUS && INET && SPARSEMEM
2651 This driver supports the IBM pSeries eHEA ethernet adapter.
2653 To compile the driver as a module, choose M here. The module
2654 will be called ehea.
2657 tristate "Cisco VIC Ethernet NIC Support"
2658 depends on PCI && INET
2660 This enables the support for the Cisco VIC Ethernet card.
2663 tristate "Intel(R) 10GbE PCI Express adapters support"
2664 depends on PCI && INET
2667 This driver supports Intel(R) 10GbE PCI Express family of
2668 adapters. For more information on how to identify your adapter, go
2669 to the Adapter & Driver ID Guide at:
2671 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2673 For general information and support, go to the Intel support
2676 <http://support.intel.com>
2678 To compile this driver as a module, choose M here. The module
2679 will be called ixgbe.
2682 bool "Direct Cache Access (DCA) Support"
2684 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2686 Say Y here if you want to use Direct Cache Access (DCA) in the
2687 driver. DCA is a method for warming the CPU cache before data
2688 is used, with the intent of lessening the impact of cache misses.
2691 bool "Data Center Bridging (DCB) Support"
2693 depends on IXGBE && DCB
2695 Say Y here if you want to use Data Center Bridging (DCB) in the
2701 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2704 This driver supports Intel(R) 82599 virtual functions. For more
2705 information on how to identify your adapter, go to the Adapter &
2708 <http://support.intel.com/support/network/sb/CS-008441.htm>
2710 For general information and support, go to the Intel support
2713 <http://support.intel.com>
2715 More specific information on configuring the driver is in
2716 <file:Documentation/networking/ixgbevf.txt>.
2718 To compile this driver as a module, choose M here. The module
2719 will be called ixgbevf. MSI-X interrupt support is required
2720 for this driver to work correctly.
2723 tristate "Intel(R) PRO/10GbE support"
2726 This driver supports Intel(R) PRO/10GbE family of adapters for
2727 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2728 instead. For more information on how to identify your adapter, go
2729 to the Adapter & Driver ID Guide at:
2731 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2733 For general information and support, go to the Intel support
2736 <http://support.intel.com>
2738 More specific information on configuring the driver is in
2739 <file:Documentation/networking/ixgb.txt>.
2741 To compile this driver as a module, choose M here. The module
2742 will be called ixgb.
2745 tristate "S2IO 10Gbe XFrame NIC"
2748 This driver supports the 10Gbe XFrame NIC of S2IO.
2749 More specific information on configuring the driver is in
2750 <file:Documentation/networking/s2io.txt>.
2753 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2754 depends on PCI && INET
2756 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2757 I/O Virtualized Server Adapter.
2758 More specific information on configuring the driver is in
2759 <file:Documentation/networking/vxge.txt>.
2761 config VXGE_DEBUG_TRACE_ALL
2762 bool "Enabling All Debug trace statments in driver"
2766 Say Y here if you want to enabling all the debug trace statements in
2767 driver. By default only few debug trace statements are enabled.
2770 tristate "Myricom Myri-10G Ethernet support"
2771 depends on PCI && INET
2776 This driver supports Myricom Myri-10G Dual Protocol interface in
2777 Ethernet mode. If the eeprom on your board is not recent enough,
2778 you will need a newer firmware image.
2779 You may get this image or more information, at:
2781 <http://www.myri.com/scs/download-Myri10GE.html>
2783 To compile this driver as a module, choose M here. The module
2784 will be called myri10ge.
2787 bool "Direct Cache Access (DCA) Support"
2789 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2791 Say Y here if you want to use Direct Cache Access (DCA) in the
2792 driver. DCA is a method for warming the CPU cache before data
2793 is used, with the intent of lessening the impact of cache misses.
2796 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2800 This enables the support for NetXen's Gigabit Ethernet card.
2803 tristate "Sun Neptune 10Gbit Ethernet support"
2807 This enables support for cards based upon Sun's
2811 tristate "PA Semi 1/10Gbit MAC"
2812 depends on PPC_PASEMI && PCI && INET
2816 This driver supports the on-chip 1/10Gbit Ethernet controller on
2817 PA Semi's PWRficient line of chips.
2820 tristate "Mellanox Technologies 10Gbit Ethernet support"
2821 depends on PCI && INET
2825 This driver supports Mellanox Technologies ConnectX Ethernet
2834 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2835 depends on MLX4_CORE
2838 This option causes debugging code to be compiled into the
2839 mlx4_core driver. The output can be turned on via the
2840 debug_level module parameter (which can also be set after
2841 the driver is loaded through sysfs).
2844 tristate "Tehuti Networks 10G Ethernet"
2847 Tehuti Networks 10G Ethernet NIC
2850 tristate "Broadcom NetXtremeII 10Gb support"
2857 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2858 To compile this driver as a module, choose M here: the module
2859 will be called bnx2x. This is recommended.
2862 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2866 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2870 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2873 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2875 To compile this driver as a module, choose M here: the module
2876 will be called qlge.
2879 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2882 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2884 To compile this driver as a module, choose M here: the module
2887 For general information and support, go to the Brocade support
2890 <http://support.brocade.com>
2892 source "drivers/net/sfc/Kconfig"
2894 source "drivers/net/benet/Kconfig"
2896 endif # NETDEV_10000
2898 source "drivers/net/tokenring/Kconfig"
2900 source "drivers/net/wireless/Kconfig"
2902 source "drivers/net/wimax/Kconfig"
2904 source "drivers/net/usb/Kconfig"
2906 source "drivers/net/pcmcia/Kconfig"
2908 source "drivers/net/wan/Kconfig"
2910 source "drivers/atm/Kconfig"
2912 source "drivers/ieee802154/Kconfig"
2914 source "drivers/s390/net/Kconfig"
2916 source "drivers/net/caif/Kconfig"
2918 config XEN_NETDEV_FRONTEND
2919 tristate "Xen network device frontend driver"
2923 The network device frontend driver allows the kernel to
2924 access network devices exported exported by a virtual
2925 machine containing a physical network device driver. The
2926 frontend driver is intended for unprivileged guest domains;
2927 if you are compiling a kernel for a Xen guest, you almost
2928 certainly want to enable this.
2931 tristate "iSeries Virtual Ethernet driver support"
2932 depends on PPC_ISERIES
2935 tristate "RapidIO Ethernet over messaging driver support"
2938 config RIONET_TX_SIZE
2939 int "Number of outbound queue entries"
2943 config RIONET_RX_SIZE
2944 int "Number of inbound queue entries"
2949 tristate "FDDI driver support"
2950 depends on (PCI || EISA || TC)
2952 Fiber Distributed Data Interface is a high speed local area network
2953 design; essentially a replacement for high speed Ethernet. FDDI can
2954 run over copper or fiber. If you are connected to such a network and
2955 want a driver for the FDDI card in your computer, say Y here (and
2956 then also Y to the driver for your FDDI card, below). Most people
2960 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2961 depends on FDDI && (PCI || EISA || TC)
2963 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2964 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2965 to a local FDDI network.
2967 To compile this driver as a module, choose M here: the module
2968 will be called defxx. If unsure, say N.
2972 prompt "Use MMIO instead of PIO" if PCI || EISA
2974 default n if PCI || EISA
2977 This instructs the driver to use EISA or PCI memory-mapped I/O
2978 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2979 Enabling this gives an improvement in processing time in parts
2980 of the driver, but it may cause problems with EISA (DEFEA)
2981 adapters. TURBOchannel does not have the concept of I/O ports,
2982 so MMIO is always used for these (DEFTA) adapters.
2987 tristate "SysKonnect FDDI PCI support"
2988 depends on FDDI && PCI
2991 Say Y here if you have a SysKonnect FDDI PCI adapter.
2992 The following adapters are supported by this driver:
2993 - SK-5521 (SK-NET FDDI-UP)
2994 - SK-5522 (SK-NET FDDI-UP DAS)
2995 - SK-5541 (SK-NET FDDI-FP)
2996 - SK-5543 (SK-NET FDDI-LP)
2997 - SK-5544 (SK-NET FDDI-LP DAS)
2998 - SK-5821 (SK-NET FDDI-UP64)
2999 - SK-5822 (SK-NET FDDI-UP64 DAS)
3000 - SK-5841 (SK-NET FDDI-FP64)
3001 - SK-5843 (SK-NET FDDI-LP64)
3002 - SK-5844 (SK-NET FDDI-LP64 DAS)
3003 - Netelligent 100 FDDI DAS Fibre SC
3004 - Netelligent 100 FDDI SAS Fibre SC
3005 - Netelligent 100 FDDI DAS UTP
3006 - Netelligent 100 FDDI SAS UTP
3007 - Netelligent 100 FDDI SAS Fibre MIC
3009 Read <file:Documentation/networking/skfp.txt> for information about
3012 Questions concerning this driver can be addressed to:
3013 <linux@syskonnect.de>
3015 To compile this driver as a module, choose M here: the module
3016 will be called skfp. This is recommended.
3019 bool "HIPPI driver support (EXPERIMENTAL)"
3020 depends on EXPERIMENTAL && INET && PCI
3022 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3023 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3024 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3025 single-mode). HIPPI networks are commonly used for clusters and to
3026 connect to super computers. If you are connected to a HIPPI network
3027 and have a HIPPI network card in your computer that you want to use
3028 under Linux, say Y here (you must also remember to enable the driver
3029 for your HIPPI card below). Most people will say N here.
3032 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3033 depends on HIPPI && PCI
3035 Say Y here if this is your PCI HIPPI network card.
3037 To compile this driver as a module, choose M here: the module
3038 will be called rrunner. If unsure, say N.
3040 config ROADRUNNER_LARGE_RINGS
3041 bool "Use large TX/RX rings (EXPERIMENTAL)"
3042 depends on ROADRUNNER
3044 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3045 of additional memory to allow for fastest operation, both for
3046 transmitting and receiving. This memory cannot be used by any other
3047 kernel code or by user space programs. Say Y here only if you have
3051 tristate "PLIP (parallel port) support"
3054 PLIP (Parallel Line Internet Protocol) is used to create a
3055 reasonably fast mini network consisting of two (or, rarely, more)
3056 local machines. A PLIP link from a Linux box is a popular means to
3057 install a Linux distribution on a machine which doesn't have a
3058 CD-ROM drive (a minimal system has to be transferred with floppies
3059 first). The kernels on both machines need to have this PLIP option
3060 enabled for this to work.
3062 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3063 ports (the connectors at the computers with 25 holes) are connected
3064 with "null printer" or "Turbo Laplink" cables which can transmit 4
3065 bits at a time (mode 0) or with special PLIP cables, to be used on
3066 bidirectional parallel ports only, which can transmit 8 bits at a
3067 time (mode 1); you can find the wiring of these cables in
3068 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3069 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3070 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3071 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3072 and winsock or NCSA's telnet.
3074 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3075 as the NET-3-HOWTO, both available from
3076 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3077 protocol has been changed and this PLIP driver won't work together
3078 with the PLIP support in Linux versions 1.0.x. This option enlarges
3079 your kernel by about 8 KB.
3081 To compile this driver as a module, choose M here. The module
3082 will be called plip. If unsure, say Y or M, in case you buy
3086 tristate "PPP (point-to-point protocol) support"
3089 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3090 the same purpose: sending Internet traffic over telephone (and other
3091 serial) lines. Ask your access provider if they support it, because
3092 otherwise you can't use it; most Internet access providers these
3093 days support PPP rather than SLIP.
3095 To use PPP, you need an additional program called pppd as described
3096 in the PPP-HOWTO, available at
3097 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3098 the version of pppd recommended in <file:Documentation/Changes>.
3099 The PPP option enlarges your kernel by about 16 KB.
3101 There are actually two versions of PPP: the traditional PPP for
3102 asynchronous lines, such as regular analog phone lines, and
3103 synchronous PPP which can be used over digital ISDN lines for
3104 example. If you want to use PPP over phone lines or other
3105 asynchronous serial lines, you need to say Y (or M) here and also to
3106 the next option, "PPP support for async serial ports". For PPP over
3107 synchronous lines, you should say Y (or M) here and to "Support
3108 synchronous PPP", below.
3110 If you said Y to "Version information on all symbols" above, then
3111 you cannot compile the PPP driver into the kernel; you can then only
3112 compile it as a module. To compile this driver as a module, choose M
3113 here. The module will be called ppp_generic.
3115 config PPP_MULTILINK
3116 bool "PPP multilink support (EXPERIMENTAL)"
3117 depends on PPP && EXPERIMENTAL
3119 PPP multilink is a protocol (defined in RFC 1990) which allows you
3120 to combine several (logical or physical) lines into one logical PPP
3121 connection, so that you can utilize your full bandwidth.
3123 This has to be supported at the other end as well and you need a
3124 version of the pppd daemon which understands the multilink protocol.
3129 bool "PPP filtering"
3132 Say Y here if you want to be able to filter the packets passing over
3133 PPP interfaces. This allows you to control which packets count as
3134 activity (i.e. which packets will reset the idle timer or bring up
3135 a demand-dialed link) and which packets are to be dropped entirely.
3136 You need to say Y here if you wish to use the pass-filter and
3137 active-filter options to pppd.
3142 tristate "PPP support for async serial ports"
3146 Say Y (or M) here if you want to be able to use PPP over standard
3147 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3148 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3151 To compile this driver as a module, choose M here.
3156 tristate "PPP support for sync tty ports"
3159 Say Y (or M) here if you want to be able to use PPP over synchronous
3160 (HDLC) tty devices, such as the SyncLink adapter. These devices
3161 are often used for high-speed leased lines like T1/E1.
3163 To compile this driver as a module, choose M here.
3166 tristate "PPP Deflate compression"
3171 Support for the Deflate compression method for PPP, which uses the
3172 Deflate algorithm (the same algorithm that gzip uses) to compress
3173 each PPP packet before it is sent over the wire. The machine at the
3174 other end of the PPP link (usually your ISP) has to support the
3175 Deflate compression method as well for this to be useful. Even if
3176 they don't support it, it is safe to say Y here.
3178 To compile this driver as a module, choose M here.
3181 tristate "PPP BSD-Compress compression"
3184 Support for the BSD-Compress compression method for PPP, which uses
3185 the LZW compression method to compress each PPP packet before it is
3186 sent over the wire. The machine at the other end of the PPP link
3187 (usually your ISP) has to support the BSD-Compress compression
3188 method as well for this to be useful. Even if they don't support it,
3189 it is safe to say Y here.
3191 The PPP Deflate compression method ("PPP Deflate compression",
3192 above) is preferable to BSD-Compress, because it compresses better
3195 Note that the BSD compression code will always be compiled as a
3196 module; it is called bsd_comp and will show up in the directory
3197 modules once you have said "make modules". If unsure, say N.
3200 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3201 depends on PPP && EXPERIMENTAL
3207 Support for the MPPE Encryption protocol, as employed by the
3208 Microsoft Point-to-Point Tunneling Protocol.
3210 See http://pptpclient.sourceforge.net/ for information on
3211 configuring PPTP clients and servers to utilize this method.
3214 tristate "PPP over Ethernet (EXPERIMENTAL)"
3215 depends on EXPERIMENTAL && PPP
3217 Support for PPP over Ethernet.
3219 This driver requires the latest version of pppd from the CVS
3220 repository at cvs.samba.org. Alternatively, see the
3221 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3222 which contains instruction on how to use this driver (under
3223 the heading "Kernel mode PPPoE").
3226 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3227 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3229 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3231 This driver requires pppd plugin to work in client mode or
3232 modified pptpd (poptop) to work in server mode.
3233 See http://accel-pptp.sourceforge.net/ for information how to
3234 utilize this module.
3237 tristate "PPP over ATM"
3238 depends on ATM && PPP
3240 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3241 This implementation does not yet comply with section 8 of RFC2364,
3242 which can lead to bad results if the ATM peer loses state and
3243 changes its encapsulation unilaterally.
3246 tristate "PPP over L2TP (EXPERIMENTAL)"
3247 depends on EXPERIMENTAL && L2TP && PPP
3249 Support for PPP-over-L2TP socket family. L2TP is a protocol
3250 used by ISPs and enterprises to tunnel PPP traffic over UDP
3251 tunnels. L2TP is replacing PPTP for VPN uses.
3254 tristate "SLIP (serial line) support"
3256 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3257 connect to your Internet service provider or to connect to some
3258 other local Unix box or if you want to configure your Linux box as a
3259 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3260 Internet Protocol) is a protocol used to send Internet traffic over
3261 serial connections such as telephone lines or null modem cables;
3262 nowadays, the protocol PPP is more commonly used for this same
3265 Normally, your access provider has to support SLIP in order for you
3266 to be able to use it, but there is now a SLIP emulator called SLiRP
3267 around (available from
3268 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3269 allows you to use SLIP over a regular dial up shell connection. If
3270 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3271 NET-3-HOWTO, available from
3272 <http://www.tldp.org/docs.html#howto>, explains how to
3273 configure SLIP. Note that you don't need this option if you just
3274 want to run term (term is a program which gives you almost full
3275 Internet connectivity if you have a regular dial up shell account on
3276 some Internet connected Unix computer. Read
3277 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3278 support will enlarge your kernel by about 4 KB. If unsure, say N.
3280 To compile this driver as a module, choose M here. The module
3281 will be called slip.
3283 config SLIP_COMPRESSED
3284 bool "CSLIP compressed headers"
3288 This protocol is faster than SLIP because it uses compression on the
3289 TCP/IP headers (not on the data itself), but it has to be supported
3290 on both ends. Ask your access provider if you are not sure and
3291 answer Y, just in case. You will still be able to use plain SLIP. If
3292 you plan to use SLiRP, the SLIP emulator (available from
3293 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3294 allows you to use SLIP over a regular dial up shell connection, you
3295 definitely want to say Y here. The NET-3-HOWTO, available from
3296 <http://www.tldp.org/docs.html#howto>, explains how to configure
3297 CSLIP. This won't enlarge your kernel.
3302 This option enables Van Jacobsen serial line header compression
3306 bool "Keepalive and linefill"
3309 Adds additional capabilities to the SLIP driver to support the
3310 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3313 config SLIP_MODE_SLIP6
3314 bool "Six bit SLIP encapsulation"
3317 Just occasionally you may need to run IP over hostile serial
3318 networks that don't pass all control characters or are only seven
3319 bit. Saying Y here adds an extra mode you can use with SLIP:
3320 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3321 the serial device. Naturally, this has to be supported at the other
3322 end of the link as well. It's good enough, for example, to run IP
3323 over the async ports of a Camtec JNT Pad. If unsure, say N.
3326 bool "Fibre Channel driver support"
3327 depends on SCSI && PCI
3329 Fibre Channel is a high speed serial protocol mainly used to connect
3330 large storage devices to the computer; it is compatible with and
3331 intended to replace SCSI.
3333 If you intend to use Fibre Channel, you need to have a Fibre channel
3334 adaptor card in your computer; say Y here and to the driver for your
3335 adaptor below. You also should have said Y to "SCSI support" and
3336 "SCSI generic support".
3339 tristate "Network console logging support"
3341 If you want to log kernel messages over the network, enable this.
3342 See <file:Documentation/networking/netconsole.txt> for details.
3344 config NETCONSOLE_DYNAMIC
3345 bool "Dynamic reconfiguration of logging targets"
3346 depends on NETCONSOLE && SYSFS
3349 This option enables the ability to dynamically reconfigure target
3350 parameters (interface, IP addresses, port numbers, MAC addresses)
3351 at runtime through a userspace interface exported using configfs.
3352 See <file:Documentation/networking/netconsole.txt> for details.
3358 bool "Netpoll traffic trapping"
3362 config NET_POLL_CONTROLLER
3366 tristate "Virtio network driver (EXPERIMENTAL)"
3367 depends on EXPERIMENTAL && VIRTIO
3369 This is the virtual network driver for virtio. It can be used with
3370 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3373 tristate "VMware VMXNET3 ethernet driver"
3374 depends on PCI && INET
3376 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3377 To compile this driver as a module, choose M here: the
3378 module will be called vmxnet3.