2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
97 This adds a specialized tap character device driver that is based
98 on the MAC-VLAN network interface, called macvtap. A macvtap device
99 can be added in the same way as a macvlan device, using 'type
100 macvlan', and then be accessed through the tap user space interface.
102 To compile this driver as a module, choose M here: the module
103 will be called macvtap.
106 tristate "EQL (serial line load balancing) support"
108 If you have two serial connections to some other computer (this
109 usually requires two modems and two telephone lines) and you use
110 SLIP (the protocol for sending Internet traffic over telephone
111 lines) or PPP (a better SLIP) on them, you can make them behave like
112 one double speed connection using this driver. Naturally, this has
113 to be supported at the other end as well, either with a similar EQL
114 Linux driver or with a Livingston Portmaster 2e.
116 Say Y if you want this and read
117 <file:Documentation/networking/eql.txt>. You may also want to read
118 section 6.2 of the NET-3-HOWTO, available from
119 <http://www.tldp.org/docs.html#howto>.
121 To compile this driver as a module, choose M here: the module
122 will be called eql. If unsure, say N.
125 tristate "Universal TUN/TAP device driver support"
128 TUN/TAP provides packet reception and transmission for user space
129 programs. It can be viewed as a simple Point-to-Point or Ethernet
130 device, which instead of receiving packets from a physical media,
131 receives them from user space program and instead of sending packets
132 via physical media writes them to the user space program.
134 When a program opens /dev/net/tun, driver creates and registers
135 corresponding net device tunX or tapX. After a program closed above
136 devices, driver will automatically delete tunXX or tapXX device and
137 all routes corresponding to it.
139 Please read <file:Documentation/networking/tuntap.txt> for more
142 To compile this driver as a module, choose M here: the module
145 If you don't know what to use this for, you don't need it.
148 tristate "Virtual ethernet pair device"
150 This device is a local ethernet tunnel. Devices are created in pairs.
151 When one end receives the packet it appears on its pair and vice
155 tristate "General Instruments Surfboard 1000"
158 This is a driver for the General Instrument (also known as
159 NextLevel) SURFboard 1000 internal
160 cable modem. This is an ISA card which is used by a number of cable
161 TV companies to provide cable modem access. It's a one-way
162 downstream-only cable modem, meaning that your upstream net link is
163 provided by your regular phone modem.
165 At present this driver only compiles as a module, so say M here if
166 you have this card. The module will be called sb1000. Then read
167 <file:Documentation/networking/README.sb1000> for information on how
168 to use this module, as it needs special ppp scripts for establishing
169 a connection. Further documentation and the necessary scripts can be
172 <http://www.jacksonville.net/~fventuri/>
173 <http://home.adelphia.net/~siglercm/sb1000.html>
174 <http://linuxpower.cx/~cable/>
176 If you don't have this card, of course say N.
178 source "drivers/net/arcnet/Kconfig"
180 source "drivers/net/phy/Kconfig"
186 menuconfig NET_ETHERNET
187 bool "Ethernet (10 or 100Mbit)"
190 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
191 type of Local Area Network (LAN) in universities and companies.
193 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
194 coaxial cable, linking computers in a chain), 10BASE-T or twisted
195 pair (10 Mbps over twisted pair cable, linking computers to central
196 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
197 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
198 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
199 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
200 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
201 Ethernet (1 Gbps over optical fiber or short copper links).
203 If your Linux machine will be connected to an Ethernet and you have
204 an Ethernet network interface card (NIC) installed in your computer,
205 say Y here and read the Ethernet-HOWTO, available from
206 <http://www.tldp.org/docs.html#howto>. You will then also have
207 to say Y to the driver for your particular NIC.
209 Note that the answer to this question won't directly affect the
210 kernel: saying N will just cause the configurator to skip all
211 the questions about Ethernet network cards. If unsure, say N.
216 tristate "Generic Media Independent Interface device support"
218 Most ethernet controllers have MII transceiver either as an external
219 or internal device. It is safe to say Y or M here even if your
220 ethernet card lack MII.
223 tristate "Atmel MACB support"
224 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9
227 The Atmel MACB ethernet interface is found on many AT32 and AT91
228 parts. Say Y to include support for the MACB chip.
230 To compile this driver as a module, choose M here: the module
233 source "drivers/net/arm/Kconfig"
236 tristate "ASIX AX88796 NE2000 clone support"
237 depends on ARM || MIPS || SUPERH
241 AX88796 driver, using platform bus to provide
242 chip detection and resources
245 bool "ASIX AX88796 external 93CX6 eeprom support"
249 Select this if your platform comes with an external 93CX6 eeprom.
252 tristate "MACE (Power Mac ethernet) support"
253 depends on PPC_PMAC && PPC32
256 Power Macintoshes and clones with Ethernet built-in on the
257 motherboard will usually use a MACE (Medium Access Control for
258 Ethernet) interface. Say Y to include support for the MACE chip.
260 To compile this driver as a module, choose M here: the module
263 config MACE_AAUI_PORT
264 bool "Use AAUI port instead of TP by default"
267 Some Apple machines (notably the Apple Network Server) which use the
268 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
269 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
270 Y here if you have such a machine. If unsure, say N.
271 The driver will default to AAUI on ANS anyway, and if you use it as
272 a module, you can provide the port_aaui=0|1 to force the driver.
275 tristate "BMAC (G3 ethernet) support"
276 depends on PPC_PMAC && PPC32
279 Say Y for support of BMAC Ethernet interfaces. These are used on G3
282 To compile this driver as a module, choose M here: the module
286 tristate "Ariadne support"
289 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
292 To compile this driver as a module, choose M here: the module
293 will be called ariadne.
296 tristate "A2065 support"
300 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
303 To compile this driver as a module, choose M here: the module
304 will be called a2065.
307 tristate "Hydra support"
311 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
313 To compile this driver as a module, choose M here: the module
314 will be called hydra.
317 tristate "Zorro NS8390-based Ethernet support"
321 This driver is for Zorro Ethernet cards using an NS8390-compatible
322 chipset, like the Village Tronic Ariadne II and the Individual
323 Computers X-Surf Ethernet cards. If you have such a card, say Y.
326 To compile this driver as a module, choose M here: the module
327 will be called zorro8390.
330 tristate "PCMCIA NE2000 support"
331 depends on AMIGA_PCMCIA
334 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
337 To compile this driver as a module, choose M here: the module
341 bool "Macintosh NS 8390 based ethernet cards"
345 If you want to include a driver to support Nubus or LC-PDS
346 Ethernet cards using an NS8390 chipset or its equivalent, say Y
347 and read the Ethernet-HOWTO, available from
348 <http://www.tldp.org/docs.html#howto>.
351 tristate "Macintosh CS89x0 based ethernet cards"
354 Support for CS89x0 chipset based Ethernet cards. If you have a
355 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
356 read the Ethernet-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>.
359 To compile this driver as a module, choose M here. This module will
363 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
366 Support for NatSemi SONIC based Ethernet devices. This includes
367 the onboard Ethernet in many Quadras as well as some LC-PDS,
368 a few Nubus and all known Comm Slot Ethernet cards. If you have
369 one of these say Y and read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
372 To compile this driver as a module, choose M here. This module will
376 bool "Macintosh (AV) onboard MACE ethernet"
380 Support for the onboard AMD 79C940 MACE Ethernet controller used in
381 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
382 say Y and read the Ethernet-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>.
386 tristate "MVME147 (Lance) Ethernet support"
390 Support for the on-board Ethernet interface on the Motorola MVME147
391 single-board computer. Say Y here to include the
392 driver for this chip in your kernel.
393 To compile this driver as a module, choose M here.
396 tristate "MVME16x Ethernet support"
399 This is the driver for the Ethernet interface on the Motorola
400 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
401 driver for this chip in your kernel.
402 To compile this driver as a module, choose M here.
405 tristate "BVME6000 Ethernet support"
408 This is the driver for the Ethernet interface on BVME4000 and
409 BVME6000 VME boards. Say Y here to include the driver for this chip
411 To compile this driver as a module, choose M here.
414 tristate "Atari Lance support"
417 Say Y to include support for several Atari Ethernet adapters based
418 on the AMD Lance chipset: RieblCard (with or without battery), or
419 PAMCard VME (also the version by Rhotron, with different addresses).
422 tristate "Sun3/Sun3x on-board LANCE support"
423 depends on SUN3 || SUN3X
425 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
426 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
427 here to compile in the Linux driver for this and enable Ethernet.
428 General Linux information on the Sun 3 and 3x series (now
430 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
432 If you're not building a kernel for a Sun 3, say N.
435 bool "Sun3 on-board Intel 82586 support"
438 This driver enables support for the on-board Intel 82586 based
439 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
440 that this driver does not support 82586-based adapters on additional
444 bool "HP on-board LANCE support"
448 If you want to use the builtin "LANCE" Ethernet controller on an
449 HP300 machine, say Y here.
452 tristate "Lasi ethernet"
455 Say Y here to support the builtin Intel 82596 ethernet controller
456 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
459 tristate "SNI RM ethernet"
460 depends on NET_ETHERNET && SNI_RM
462 Say Y here to support the on-board Intel 82596 ethernet controller
463 built into SNI RM machines.
466 tristate "Korina (IDT RC32434) Ethernet support"
467 depends on NET_ETHERNET && MIKROTIK_RB532
469 If you have a Mikrotik RouterBoard 500 or IDT RC32434
470 based system say Y. Otherwise say N.
472 config MIPS_JAZZ_SONIC
473 tristate "MIPS JAZZ onboard SONIC Ethernet support"
476 This is the driver for the onboard card of MIPS Magnum 4000,
477 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
479 config XTENSA_XT2000_SONIC
480 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
481 depends on XTENSA_PLATFORM_XT2000
483 This is the driver for the onboard card of the Xtensa XT2000 board.
485 config MIPS_AU1X00_ENET
486 tristate "MIPS AU1000 Ethernet support"
487 depends on SOC_AU1X00
491 If you have an Alchemy Semi AU1X00 based system
492 say Y. Otherwise, say N.
495 bool "SGI IOC3 Ethernet"
496 depends on PCI && SGI_IP27
500 If you have a network (Ethernet) card of this type, say Y and read
501 the Ethernet-HOWTO, available from
502 <http://www.tldp.org/docs.html#howto>.
505 tristate "MIPS simulator Network device"
508 The MIPSNET device is a simple Ethernet network device which is
509 emulated by the MIPS Simulator.
510 If you are not using a MIPSsim or are unsure, say N.
512 config SGI_O2MACE_ETH
513 tristate "SGI O2 MACE Fast Ethernet support"
514 depends on SGI_IP32=y
517 tristate "National DP83902AV support"
521 Support for cards based on the National Semiconductor DP83902AV
522 ST-NIC Serial Network Interface Controller for Twisted Pair. This
523 is a 10Mbit/sec Ethernet controller. Product overview and specs at
524 <http://www.national.com/pf/DP/DP83902A.html>.
529 tristate "Renesas SuperH Ethernet support"
530 depends on SUPERH && \
531 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
532 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
539 Renesas SuperH Ethernet device driver.
540 This driver support SH7710, SH7712, SH7763, SH7619, and SH7724.
543 tristate "Sun LANCE support"
547 This driver supports the "le" interface present on all 32-bit Sparc
548 systems, on some older Ultra systems and as an Sbus option. These
549 cards are based on the AMD Lance chipset, which is better known
550 via the NE2100 cards.
552 To compile this driver as a module, choose M here: the module
553 will be called sunlance.
556 tristate "Sun Happy Meal 10/100baseT support"
557 depends on SBUS || PCI
560 This driver supports the "hme" interface present on most Ultra
561 systems and as an option on older Sbus systems. This driver supports
562 both PCI and Sbus devices. This driver also supports the "qfe" quad
563 100baseT device available in both PCI and Sbus configurations.
565 To compile this driver as a module, choose M here: the module
566 will be called sunhme.
569 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
570 depends on SBUS && EXPERIMENTAL
573 This driver supports the "be" interface available as an Sbus option.
574 This is Sun's older 100baseT Ethernet device.
576 To compile this driver as a module, choose M here: the module
577 will be called sunbmac.
580 tristate "Sun QuadEthernet support"
584 This driver supports the "qe" 10baseT Ethernet device, available as
585 an Sbus option. Note that this is not the same as Quad FastEthernet
586 "qfe" which is supported by the Happy Meal driver instead.
588 To compile this driver as a module, choose M here: the module
589 will be called sunqe.
592 tristate "Sun GEM support"
596 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
597 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
600 tristate "Sun Cassini support"
604 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
605 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
608 tristate "Sun Virtual Network support"
611 Support for virtual network devices under Sun Logical Domains.
613 config NET_VENDOR_3COM
615 depends on ISA || EISA || MCA || PCI
617 If you have a network (Ethernet) card belonging to this class, say Y
618 and read the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 Note that the answer to this question doesn't directly affect the
622 kernel: saying N will just cause the configurator to skip all
623 the questions about 3COM cards. If you say Y, you will be asked for
624 your specific card in the following questions.
627 tristate "3c501 \"EtherLink\" support"
628 depends on NET_VENDOR_3COM && ISA
630 If you have a network (Ethernet) card of this type, say Y and read
631 the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
633 new card, since the 3c501 is slow, broken, and obsolete: you will
634 have problems. Some people suggest to ping ("man ping") a nearby
635 machine every minute ("man cron") when using this card.
637 To compile this driver as a module, choose M here. The module
638 will be called 3c501.
641 tristate "3c503 \"EtherLink II\" support"
642 depends on NET_VENDOR_3COM && ISA
645 If you have a network (Ethernet) card of this type, say Y and read
646 the Ethernet-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here. The module
650 will be called 3c503.
653 tristate "3c505 \"EtherLink Plus\" support"
654 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
656 Information about this network (Ethernet) card can be found in
657 <file:Documentation/networking/3c505.txt>. If you have a card of
658 this type, say Y and read the Ethernet-HOWTO, available from
659 <http://www.tldp.org/docs.html#howto>.
661 To compile this driver as a module, choose M here. The module
662 will be called 3c505.
665 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
666 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
668 If you have a network (Ethernet) card of this type, say Y and read
669 the Ethernet-HOWTO, available from
670 <http://www.tldp.org/docs.html#howto>.
672 To compile this driver as a module, choose M here. The module
673 will be called 3c507.
676 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
677 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
679 If you have a network (Ethernet) card belonging to the 3Com
680 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
681 from <http://www.tldp.org/docs.html#howto>.
683 If your card is not working you may need to use the DOS
684 setup disk to disable Plug & Play mode, and to select the default
687 To compile this driver as a module, choose M here. The module
688 will be called 3c509.
691 tristate "3c515 ISA \"Fast EtherLink\""
692 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
694 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
695 network card, say Y and read the Ethernet-HOWTO, available from
696 <http://www.tldp.org/docs.html#howto>.
698 To compile this driver as a module, choose M here. The module
699 will be called 3c515.
702 tristate "3c523 \"EtherLink/MC\" support"
703 depends on NET_VENDOR_3COM && MCA_LEGACY
705 If you have a network (Ethernet) card of this type, say Y and read
706 the Ethernet-HOWTO, available from
707 <http://www.tldp.org/docs.html#howto>.
709 To compile this driver as a module, choose M here. The module
710 will be called 3c523.
713 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
714 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
716 If you have a network (Ethernet) card of this type, say Y and read
717 the Ethernet-HOWTO, available from
718 <http://www.tldp.org/docs.html#howto>.
720 To compile this driver as a module, choose M here. The module
721 will be called 3c527.
724 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
725 depends on NET_VENDOR_3COM && (PCI || EISA)
728 This option enables driver support for a large number of 10Mbps and
729 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
731 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
732 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
733 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
734 "Tornado" (3c905) PCI
735 "Hurricane" (3c555/3cSOHO) PCI
737 If you have such a card, say Y and read the Ethernet-HOWTO,
738 available from <http://www.tldp.org/docs.html#howto>. More
739 specific information is in
740 <file:Documentation/networking/vortex.txt> and in the comments at
741 the beginning of <file:drivers/net/3c59x.c>.
743 To compile this support as a module, choose M here.
746 tristate "3cr990 series \"Typhoon\" support"
747 depends on NET_VENDOR_3COM && PCI
750 This option enables driver support for the 3cr990 series of cards:
752 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
753 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
754 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
756 If you have a network (Ethernet) card of this type, say Y and read
757 the Ethernet-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>.
760 To compile this driver as a module, choose M here. The module
761 will be called typhoon.
764 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
765 depends on ISA && ISA_DMA_API
767 If you have a network (Ethernet) card of this type, say Y and read
768 the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
772 To compile this driver as a module, choose M here: the module
773 will be called lance. This is recommended.
775 config NET_VENDOR_SMC
776 bool "Western Digital/SMC cards"
777 depends on ISA || MCA || EISA || MAC
779 If you have a network (Ethernet) card belonging to this class, say Y
780 and read the Ethernet-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 Note that the answer to this question doesn't directly affect the
784 kernel: saying N will just cause the configurator to skip all
785 the questions about Western Digital cards. If you say Y, you will be
786 asked for your specific card in the following questions.
789 tristate "WD80*3 support"
790 depends on NET_VENDOR_SMC && ISA
793 If you have a network (Ethernet) card of this type, say Y and read
794 the Ethernet-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 To compile this driver as a module, choose M here. The module
801 tristate "SMC Ultra MCA support"
802 depends on NET_VENDOR_SMC && MCA
805 If you have a network (Ethernet) card of this type and are running
806 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
807 available from <http://www.tldp.org/docs.html#howto>.
809 To compile this driver as a module, choose M here. The module
810 will be called smc-mca.
813 tristate "SMC Ultra support"
814 depends on NET_VENDOR_SMC && ISA
817 If you have a network (Ethernet) card of this type, say Y and read
818 the Ethernet-HOWTO, available from
819 <http://www.tldp.org/docs.html#howto>.
821 Important: There have been many reports that, with some motherboards
822 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
823 such as some BusLogic models) causes corruption problems with many
824 operating systems. The Linux smc-ultra driver has a work-around for
825 this but keep it in mind if you have such a SCSI card and have
828 To compile this driver as a module, choose M here. The module
829 will be called smc-ultra.
832 tristate "SMC Ultra32 EISA support"
833 depends on NET_VENDOR_SMC && EISA
836 If you have a network (Ethernet) card of this type, say Y and read
837 the Ethernet-HOWTO, available from
838 <http://www.tldp.org/docs.html#howto>.
840 To compile this driver as a module, choose M here. The module
841 will be called smc-ultra32.
844 tristate "Blackfin on-chip MAC support"
845 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
849 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
851 This is the driver for Blackfin on-chip mac device. Say Y if you want it
852 compiled into the kernel. This driver is also available as a module
853 ( = code which can be inserted in and removed from the running kernel
854 whenever you want). The module will be called bfin_mac.
856 config BFIN_MAC_USE_L1
857 bool "Use L1 memory for rx/tx packets"
858 depends on BFIN_MAC && (BF527 || BF537)
861 To get maximum network performance, you should use L1 memory as rx/tx buffers.
862 Say N here if you want to reserve L1 memory for other uses.
864 config BFIN_TX_DESC_NUM
865 int "Number of transmit buffer packets"
867 range 6 10 if BFIN_MAC_USE_L1
871 Set the number of buffer packets used in driver.
873 config BFIN_RX_DESC_NUM
874 int "Number of receive buffer packets"
876 range 20 100 if BFIN_MAC_USE_L1
880 Set the number of buffer packets used in driver.
883 bool "RMII PHY Interface"
885 default y if BFIN527_EZKIT
886 default n if BFIN537_STAMP
888 Use Reduced PHY MII Interface
891 tristate "SMC 9194 support"
892 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
895 This is support for the SMC9xxx based Ethernet cards. Choose this
896 option if you have a DELL laptop with the docking station, or
897 another SMC9192/9194 based chipset. Say Y if you want it compiled
898 into the kernel, and read the file
899 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
900 available from <http://www.tldp.org/docs.html#howto>.
902 To compile this driver as a module, choose M here. The module
903 will be called smc9194.
906 tristate "SMC 91C9x/91C1xxx support"
909 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
910 MIPS || BLACKFIN || MN10300 || COLDFIRE
912 This is a driver for SMC's 91x series of Ethernet chipsets,
913 including the SMC91C94 and the SMC91C111. Say Y if you want it
914 compiled into the kernel, and read the file
915 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
916 available from <http://www.linuxdoc.org/docs.html#howto>.
918 This driver is also available as a module ( = code which can be
919 inserted in and removed from the running kernel whenever you want).
920 The module will be called smc91x. If you want to compile it as a
921 module, say M here and read <file:Documentation/kbuild/modules.txt>.
924 tristate "NetX Ethernet support"
928 This is support for the Hilscher netX builtin Ethernet ports
930 To compile this driver as a module, choose M here. The module
931 will be called netx-eth.
933 config TI_DAVINCI_EMAC
934 tristate "TI DaVinci EMAC Support"
935 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
938 This driver supports TI's DaVinci Ethernet .
940 To compile this driver as a module, choose M here: the module
941 will be called davinci_emac_driver. This is recommended.
944 tristate "DM9000 support"
945 depends on ARM || BLACKFIN || MIPS
949 Support for DM9000 chipset.
951 To compile this driver as a module, choose M here. The module
952 will be called dm9000.
954 config DM9000_DEBUGLEVEL
955 int "DM9000 maximum debug level"
959 The maximum level of debugging code compiled into the DM9000
962 config DM9000_FORCE_SIMPLE_PHY_POLL
963 bool "Force simple NSR based PHY polling"
966 This configuration forces the DM9000 to use the NSR's LinkStatus
967 bit to determine if the link is up or down instead of the more
968 costly MII PHY reads. Note, this will not work if the chip is
969 operating with an external PHY.
972 tristate "ENC28J60 support"
973 depends on EXPERIMENTAL && SPI && NET_ETHERNET
976 Support for the Microchip EN28J60 ethernet chip.
978 To compile this driver as a module, choose M here. The module will be
981 config ENC28J60_WRITEVERIFY
982 bool "Enable write verify"
985 Enable the verify after the buffer write useful for debugging purpose.
989 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
990 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
996 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
999 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1004 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1007 tristate "SMSC LAN911[5678] support"
1010 depends on ARM || SUPERH
1012 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1013 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1014 Say Y if you want it compiled into the kernel,
1015 and read the Ethernet-HOWTO, available from
1016 <http://www.linuxdoc.org/docs.html#howto>.
1018 This driver is also available as a module. The module will be
1019 called smc911x. If you want to compile it as a module, say M
1020 here and read <file:Documentation/kbuild/modules.txt>
1023 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1024 depends on ARM || SUPERH || BLACKFIN || MIPS
1029 Say Y here if you want support for SMSC LAN911x and LAN921x families
1030 of ethernet controllers.
1032 To compile this driver as a module, choose M here and read
1033 <file:Documentation/networking/net-modules.txt>. The module
1034 will be called smsc911x.
1036 config NET_VENDOR_RACAL
1037 bool "Racal-Interlan (Micom) NI cards"
1040 If you have a network (Ethernet) card belonging to this class, such
1041 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1042 available from <http://www.tldp.org/docs.html#howto>.
1044 Note that the answer to this question doesn't directly affect the
1045 kernel: saying N will just cause the configurator to skip all
1046 the questions about NI cards. If you say Y, you will be asked for
1047 your specific card in the following questions.
1050 tristate "NI5010 support (EXPERIMENTAL)"
1051 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1053 If you have a network (Ethernet) card of this type, say Y and read
1054 the Ethernet-HOWTO, available from
1055 <http://www.tldp.org/docs.html#howto>. Note that this is still
1058 To compile this driver as a module, choose M here. The module
1059 will be called ni5010.
1062 tristate "NI5210 support"
1063 depends on NET_VENDOR_RACAL && ISA
1065 If you have a network (Ethernet) card of this type, say Y and read
1066 the Ethernet-HOWTO, available from
1067 <http://www.tldp.org/docs.html#howto>.
1069 To compile this driver as a module, choose M here. The module
1070 will be called ni52.
1073 tristate "NI6510 support"
1074 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1076 If you have a network (Ethernet) card of this type, say Y and read
1077 the Ethernet-HOWTO, available from
1078 <http://www.tldp.org/docs.html#howto>.
1080 To compile this driver as a module, choose M here. The module
1081 will be called ni65.
1084 tristate "Dave ethernet support (DNET)"
1085 depends on NET_ETHERNET && HAS_IOMEM
1088 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1089 Say Y to include support for the DNET chip.
1091 To compile this driver as a module, choose M here: the module
1092 will be called dnet.
1094 source "drivers/net/tulip/Kconfig"
1097 tristate "AT1700/1720 support (EXPERIMENTAL)"
1098 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1101 If you have a network (Ethernet) card of this type, say Y and read
1102 the Ethernet-HOWTO, available from
1103 <http://www.tldp.org/docs.html#howto>.
1105 To compile this driver as a module, choose M here. The module
1106 will be called at1700.
1109 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1110 depends on ISA || EISA || MCA
1113 If you have a network (Ethernet) card of this type, say Y and read
1114 the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto> as well as
1116 <file:drivers/net/depca.c>.
1118 To compile this driver as a module, choose M here. The module
1119 will be called depca.
1122 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1123 depends on ISA || EISA || PCI
1125 If you have a network (Ethernet) card of this type, say Y and read
1126 the Ethernet-HOWTO, available from
1127 <http://www.tldp.org/docs.html#howto>.
1129 To compile this driver as a module, choose M here. The module
1130 will be called hp100.
1133 bool "Other ISA cards"
1136 If your network (Ethernet) card hasn't been mentioned yet and its
1137 bus system (that's the way the cards talks to the other components
1138 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1139 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1140 available from <http://www.tldp.org/docs.html#howto>.
1144 Note that the answer to this question doesn't directly affect the
1145 kernel: saying N will just cause the configurator to skip all
1146 the remaining ISA network card questions. If you say Y, you will be
1147 asked for your specific card in the following questions.
1150 tristate "Cabletron E21xx support"
1154 If you have a network (Ethernet) card of this type, say Y and read
1155 the Ethernet-HOWTO, available from
1156 <http://www.tldp.org/docs.html#howto>.
1158 To compile this driver as a module, choose M here. The module
1159 will be called e2100.
1162 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1166 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1167 cards. If this is for you, say Y and read
1168 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1169 well as the Ethernet-HOWTO, available from
1170 <http://www.tldp.org/docs.html#howto>.
1172 To compile this driver as a module, choose M here. The module
1173 will be called ewrk3.
1176 tristate "EtherExpress 16 support"
1179 If you have an EtherExpress16 network (Ethernet) card, say Y and
1180 read the Ethernet-HOWTO, available from
1181 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1182 EtherExpress16 card used to be regarded as a very poor choice
1183 because the driver was very unreliable. We now have a new driver
1184 that should do better.
1186 To compile this driver as a module, choose M here. The module
1187 will be called eexpress.
1190 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1193 If you have a network (Ethernet) card of this type, say Y. This
1194 driver supports Intel i82595{FX,TX} based boards. Note however
1195 that the EtherExpress PRO/100 Ethernet card has its own separate
1196 driver. Please read the Ethernet-HOWTO, available from
1197 <http://www.tldp.org/docs.html#howto>.
1199 To compile this driver as a module, choose M here. The module
1200 will be called eepro.
1203 tristate "HP PCLAN+ (27247B and 27252A) support"
1207 If you have a network (Ethernet) card of this type, say Y and read
1208 the Ethernet-HOWTO, available from
1209 <http://www.tldp.org/docs.html#howto>.
1211 To compile this driver as a module, choose M here. The module
1212 will be called hp-plus.
1215 tristate "HP PCLAN (27245 and other 27xxx series) support"
1219 If you have a network (Ethernet) card of this type, say Y and read
1220 the Ethernet-HOWTO, available from
1221 <http://www.tldp.org/docs.html#howto>.
1223 To compile this driver as a module, choose M here. The module
1227 tristate "LP486E on board Ethernet"
1230 Say Y here to support the 82596-based on-board Ethernet controller
1231 for the Panther motherboard, which is one of the two shipped in the
1232 Intel Professional Workstation.
1235 tristate "ICL EtherTeam 16i/32 support"
1238 If you have a network (Ethernet) card of this type, say Y and read
1239 the Ethernet-HOWTO, available from
1240 <http://www.tldp.org/docs.html#howto>.
1242 To compile this driver as a module, choose M here. The module
1243 will be called eth16i.
1246 tristate "NE2000/NE1000 support"
1247 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1250 If you have a network (Ethernet) card of this type, say Y and read
1251 the Ethernet-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1253 without a specific driver are compatible with NE2000.
1255 If you have a PCI NE2000 card however, say N here and Y to "PCI
1256 NE2000 and clone support" under "EISA, VLB, PCI and on board
1257 controllers" below. If you have a NE2000 card and are running on
1258 an MCA system (a bus system used on some IBM PS/2 computers and
1259 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1262 To compile this driver as a module, choose M here. The module
1266 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1267 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1269 The Zenith Z-Note notebook computer has a built-in network
1270 (Ethernet) card, and this is the Linux driver for it. Note that the
1271 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1272 by this driver. Read the Ethernet-HOWTO, available from
1273 <http://www.tldp.org/docs.html#howto>.
1276 tristate "SEEQ8005 support (EXPERIMENTAL)"
1277 depends on NET_ISA && EXPERIMENTAL
1279 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1280 is for you, read the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1283 To compile this driver as a module, choose M here. The module
1284 will be called seeq8005.
1287 tristate "NE/2 (ne2000 MCA version) support"
1288 depends on MCA_LEGACY
1291 If you have a network (Ethernet) card of this type, say Y and read
1292 the Ethernet-HOWTO, available from
1293 <http://www.tldp.org/docs.html#howto>.
1295 To compile this driver as a module, choose M here. The module
1299 tristate "IBM LAN Adapter/A support"
1302 This is a Micro Channel Ethernet adapter. You need to set
1303 CONFIG_MCA to use this driver. It is both available as an in-kernel
1304 driver and as a module.
1306 To compile this driver as a module, choose M here. The only
1307 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1308 will both support 16K and 32K memory windows, however a 32K window
1309 gives a better security against packet losses. Usage of multiple
1310 boards with this driver should be possible, but has not been tested
1311 up to now due to lack of hardware.
1314 tristate "IBM LAN Virtual Ethernet support"
1315 depends on PPC_PSERIES
1317 This driver supports virtual ethernet adapters on newer IBM iSeries
1318 and pSeries systems.
1320 To compile this driver as a module, choose M here. The module will
1323 source "drivers/net/ibm_newemac/Kconfig"
1326 bool "EISA, VLB, PCI and on board controllers"
1327 depends on ISA || EISA || PCI
1329 This is another class of network cards which attach directly to the
1330 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1331 available from <http://www.tldp.org/docs.html#howto>.
1333 Note that the answer to this question doesn't directly affect the
1334 kernel: saying N will just cause the configurator to skip all
1335 the questions about this class of network cards. If you say Y, you
1336 will be asked for your specific card in the following questions. If
1337 you are unsure, say Y.
1340 tristate "AMD PCnet32 PCI support"
1341 depends on NET_PCI && PCI
1345 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1346 answer Y here and read the Ethernet-HOWTO, available from
1347 <http://www.tldp.org/docs.html#howto>.
1349 To compile this driver as a module, choose M here. The module
1350 will be called pcnet32.
1353 tristate "AMD 8111 (new PCI lance) support"
1354 depends on NET_PCI && PCI
1358 If you have an AMD 8111-based PCI lance 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 amd8111e.
1365 config ADAPTEC_STARFIRE
1366 tristate "Adaptec Starfire/DuraLAN support"
1367 depends on NET_PCI && PCI
1371 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1372 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1373 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1376 To compile this driver as a module, choose M here: the module
1377 will be called starfire. This is recommended.
1380 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1381 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1384 If you have a network (Ethernet) card of this type, say Y and read
1385 the Ethernet-HOWTO, available from
1386 <http://www.tldp.org/docs.html#howto>.
1388 To compile this driver as a module, choose M here. The module
1389 will be called ac3200.
1392 tristate "Micrel KSZ8841/2 PCI"
1393 depends on NET_PCI && PCI
1397 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1399 To compile this driver as a module, choose M here. The module
1400 will be called ksz884x.
1403 tristate "Apricot Xen-II on board Ethernet"
1404 depends on NET_PCI && ISA
1406 If you have a network (Ethernet) controller of this type, say Y and
1407 read the Ethernet-HOWTO, available from
1408 <http://www.tldp.org/docs.html#howto>.
1410 To compile this driver as a module, choose M here. The module
1411 will be called apricot.
1414 tristate "Broadcom 440x/47xx ethernet support"
1415 depends on SSB_POSSIBLE && HAS_DMA
1419 If you have a network (Ethernet) controller of this type, say Y
1420 or M and 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
1426 # Auto-select SSB PCI-HOST support, if possible
1427 config B44_PCI_AUTOSELECT
1429 depends on B44 && SSB_PCIHOST_POSSIBLE
1433 # Auto-select SSB PCICORE driver, if possible
1434 config B44_PCICORE_AUTOSELECT
1436 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1437 select SSB_DRIVER_PCICORE
1442 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1446 tristate "nForce Ethernet support"
1447 depends on NET_PCI && PCI
1449 If you have a network (Ethernet) controller of this type, say Y and
1450 read the Ethernet-HOWTO, available from
1451 <http://www.tldp.org/docs.html#howto>.
1453 To compile this driver as a module, choose M here. The module
1454 will be called forcedeth.
1457 tristate "CS89x0 support"
1458 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1459 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1461 Support for CS89x0 chipset based Ethernet cards. If you have a
1462 network (Ethernet) card of this type, say Y and read the
1463 Ethernet-HOWTO, available from
1464 <http://www.tldp.org/docs.html#howto> as well as
1465 <file:Documentation/networking/cs89x0.txt>.
1467 To compile this driver as a module, choose M here. The module
1468 will be called cs89x0.
1470 config CS89x0_NONISA_IRQ
1472 depends on CS89x0 != n
1473 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1476 tristate "TOSHIBA TC35815 Ethernet support"
1477 depends on NET_PCI && PCI && MIPS
1481 tristate "Intel(R) PRO/100+ support"
1482 depends on NET_PCI && PCI
1485 This driver supports Intel(R) PRO/100 family of adapters.
1486 To verify that your adapter is supported, find the board ID number
1487 on the adapter. Look for a label that has a barcode and a number
1488 in the format 123456-001 (six digits hyphen three digits).
1490 Use the above information and the Adapter & Driver ID Guide at:
1492 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1494 to identify the adapter.
1496 For the latest Intel PRO/100 network driver for Linux, see:
1498 <http://appsr.intel.com/scripts-df/support_intel.asp>
1500 More specific information on configuring the driver is in
1501 <file:Documentation/networking/e100.txt>.
1503 To compile this driver as a module, choose M here. The module
1504 will be called e100.
1507 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1508 depends on NET_PCI && EISA && EXPERIMENTAL
1511 If you have a network (Ethernet) card of this type, say Y and read
1512 the Ethernet-HOWTO, available from
1513 <http://www.tldp.org/docs.html#howto>.
1515 To compile this driver as a module, choose M here. The module
1516 will be called lne390.
1519 tristate "Myson MTD-8xx PCI Ethernet support"
1520 depends on NET_PCI && PCI
1524 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1525 cards. Specifications and data at
1526 <http://www.myson.com.hk/mtd/datasheet/>.
1529 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1530 depends on NET_PCI && PCI
1533 This driver is for the National Semiconductor DP83810 series,
1534 which is used in cards from PureData, NetGear, Linksys
1535 and others, including the 83815 chip.
1536 More specific information and updates are available from
1537 <http://www.scyld.com/network/natsemi.html>.
1540 tristate "PCI NE2000 and clones support (see help)"
1541 depends on NET_PCI && PCI
1544 This driver is for NE2000 compatible PCI cards. It will not work
1545 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1546 support" below). If you have a PCI NE2000 network (Ethernet) card,
1547 say Y and read the Ethernet-HOWTO, available from
1548 <http://www.tldp.org/docs.html#howto>.
1550 This driver also works for the following NE2000 clone cards:
1551 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1552 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1553 Holtek HT80232 Holtek HT80229
1555 To compile this driver as a module, choose M here. The module
1556 will be called ne2k-pci.
1559 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1560 depends on NET_PCI && EISA && EXPERIMENTAL
1563 If you have a network (Ethernet) card of this type, say Y and read
1564 the Ethernet-HOWTO, available from
1565 <http://www.tldp.org/docs.html#howto>. Note that this driver
1566 will NOT WORK for NE3200 cards as they are completely different.
1568 To compile this driver as a module, choose M here. The module
1569 will be called ne3210.
1572 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1573 depends on NET_PCI && EISA && EXPERIMENTAL
1576 If you have a network (Ethernet) card of this type, say Y and read
1577 the Ethernet-HOWTO, available from
1578 <http://www.tldp.org/docs.html#howto>.
1580 To compile this driver as a module, choose M here. The module
1581 will be called es3210.
1584 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1585 depends on NET_PCI && PCI && EXPERIMENTAL
1589 This is a driver for the Fast Ethernet PCI network cards based on
1590 the RTL8139C+ chips. If you have one of those, say Y and read
1591 the Ethernet-HOWTO, available from
1592 <http://www.tldp.org/docs.html#howto>.
1594 To compile this driver as a module, choose M here: the module
1595 will be called 8139cp. This is recommended.
1598 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1599 depends on NET_PCI && PCI
1603 This is a driver for the Fast Ethernet PCI network cards based on
1604 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1605 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1607 To compile this driver as a module, choose M here: the module
1608 will be called 8139too. This is recommended.
1611 bool "Use PIO instead of MMIO"
1615 This instructs the driver to use programmed I/O ports (PIO) instead
1616 of PCI shared memory (MMIO). This can possibly solve some problems
1617 in case your mainboard has memory consistency issues. If unsure,
1620 config 8139TOO_TUNE_TWISTER
1621 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1624 This implements a function which might come in handy in case you
1625 are using low quality on long cabling. It is required for RealTek
1626 RTL-8139 revision K boards, and totally unused otherwise. It tries
1627 to match the transceiver to the cable characteristics. This is
1628 experimental since hardly documented by the manufacturer.
1632 bool "Support for older RTL-8129/8130 boards"
1635 This enables support for the older and uncommon RTL-8129 and
1636 RTL-8130 chips, which support MII via an external transceiver,
1637 instead of an internal one. Disabling this option will save some
1638 memory by making the code size smaller. If unsure, say Y.
1640 config 8139_OLD_RX_RESET
1641 bool "Use older RX-reset method"
1644 The 8139too driver was recently updated to contain a more rapid
1645 reset sequence, in the face of severe receive errors. This "new"
1646 RX-reset method should be adequate for all boards. But if you
1647 experience problems, you can enable this option to restore the
1648 old RX-reset behavior. If unsure, say N.
1651 tristate "RDC R6040 Fast Ethernet Adapter support"
1652 depends on NET_PCI && PCI
1656 This is a driver for the R6040 Fast Ethernet MACs found in the
1657 the RDC R-321x System-on-chips.
1659 To compile this driver as a module, choose M here: the module
1660 will be called r6040. This is recommended.
1663 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1664 depends on NET_PCI && PCI
1668 This is a driver for the Fast Ethernet PCI network cards based on
1669 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1670 SiS 630 and SiS 540 chipsets.
1672 This driver also supports AMD 79C901 HomePNA so that you can use
1673 your phone line as a network cable.
1675 To compile this driver as a module, choose M here: the module
1676 will be called sis900. This is recommended.
1679 tristate "SMC EtherPower II"
1680 depends on NET_PCI && PCI
1684 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1685 which is based on the SMC83c17x (EPIC/100).
1686 More specific information and updates are available from
1687 <http://www.scyld.com/network/epic100.html>.
1690 tristate "SMSC LAN9420 PCI ethernet adapter support"
1691 depends on NET_PCI && PCI
1696 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1697 Say Y if you want it compiled into the kernel,
1698 and read the Ethernet-HOWTO, available from
1699 <http://www.linuxdoc.org/docs.html#howto>.
1701 This driver is also available as a module. The module will be
1702 called smsc9420. If you want to compile it as a module, say M
1703 here and read <file:Documentation/kbuild/modules.txt>
1706 tristate "Sundance Alta support"
1707 depends on NET_PCI && PCI
1711 This driver is for the Sundance "Alta" chip.
1712 More specific information and updates are available from
1713 <http://www.scyld.com/network/sundance.html>.
1715 config SUNDANCE_MMIO
1716 bool "Use MMIO instead of PIO"
1719 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1720 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1721 is known to solve bugs on certain chips.
1726 tristate "TI ThunderLAN support"
1727 depends on NET_PCI && (PCI || EISA)
1729 If you have a PCI Ethernet network card based on the ThunderLAN chip
1730 which is supported by this driver, say Y and read the
1731 Ethernet-HOWTO, available from
1732 <http://www.tldp.org/docs.html#howto>.
1734 Devices currently supported by this driver are Compaq Netelligent,
1735 Compaq NetFlex and Olicom cards. Please read the file
1736 <file:Documentation/networking/tlan.txt> for more details.
1738 To compile this driver as a module, choose M here. The module
1739 will be called tlan.
1741 Please email feedback to <torben.mathiasen@compaq.com>.
1744 tristate "Micrel KSZ8842"
1745 depends on HAS_IOMEM
1747 This platform driver is for Micrel KSZ8842 / KS8842
1748 2-port ethernet switch chip (managed, VLAN, QoS).
1751 tristate "Micrel KS8851 SPI"
1756 SPI driver for Micrel KS8851 SPI attached network chip.
1759 tristate "Micrel KS8851 MLL"
1760 depends on HAS_IOMEM
1763 This platform driver is for Micrel KS8851 Address/data bus
1764 multiplexed network chip.
1767 tristate "VIA Rhine support"
1768 depends on NET_PCI && PCI
1772 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1773 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1774 Ethernet functions can also be found integrated on South Bridges
1777 To compile this driver as a module, choose M here. The module
1778 will be called via-rhine.
1780 config VIA_RHINE_MMIO
1781 bool "Use MMIO instead of PIO"
1782 depends on VIA_RHINE
1784 This instructs the driver to use PCI shared memory (MMIO) instead of
1785 programmed I/O ports (PIO). Enabling this gives an improvement in
1786 processing time in parts of the driver.
1791 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1792 depends on NET_PCI && PCI && EXPERIMENTAL
1795 This is a driver for the Fast Ethernet PCI network cards based on
1796 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1797 have one of these, say Y here.
1799 To compile this driver as a module, choose M here: the module
1800 will be called sc92031. This is recommended.
1803 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1804 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1807 TI AR7 CPMAC Ethernet support
1810 bool "Pocket and portable adapters"
1813 Cute little network (Ethernet) devices which attach to the parallel
1814 port ("pocket adapters"), commonly used with laptops. If you have
1815 one of those, say Y and read the Ethernet-HOWTO, available from
1816 <http://www.tldp.org/docs.html#howto>.
1818 If you want to plug a network (or some other) card into the PCMCIA
1819 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1820 credit card size extension cards used by all modern laptops), you
1821 need the pcmcia-cs package (location contained in the file
1822 <file:Documentation/Changes>) and you can say N here.
1824 Laptop users should read the Linux Laptop home page at
1825 <http://www.linux-on-laptops.com/> or
1826 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1828 Note that the answer to this question doesn't directly affect the
1829 kernel: saying N will just cause the configurator to skip all
1830 the questions about this class of network devices. If you say Y, you
1831 will be asked for your specific device in the following questions.
1834 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1835 depends on NET_POCKET && PARPORT && X86
1838 This is a network (Ethernet) device which attaches to your parallel
1839 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1840 available from <http://www.tldp.org/docs.html#howto>, if you
1841 want to use this. If you intend to use this driver, you should have
1842 said N to the "Parallel printer support", because the two drivers
1843 don't like each other.
1845 To compile this driver as a module, choose M here: the module
1849 tristate "D-Link DE600 pocket adapter support"
1850 depends on NET_POCKET && PARPORT
1852 This is a network (Ethernet) device which attaches to your parallel
1853 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1854 Ethernet-HOWTO, available from
1855 <http://www.tldp.org/docs.html#howto>, if you want to use
1856 this. It is possible to have several devices share a single parallel
1857 port and it is safe to compile the corresponding drivers into the
1860 To compile this driver as a module, choose M here: the module
1861 will be called de600.
1864 tristate "D-Link DE620 pocket adapter support"
1865 depends on NET_POCKET && PARPORT
1867 This is a network (Ethernet) device which attaches to your parallel
1868 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1869 Ethernet-HOWTO, available from
1870 <http://www.tldp.org/docs.html#howto>, if you want to use
1871 this. It is possible to have several devices share a single parallel
1872 port and it is safe to compile the corresponding drivers into the
1875 To compile this driver as a module, choose M here: the module
1876 will be called de620.
1879 tristate "SGI Seeq ethernet controller support"
1880 depends on SGI_HAS_SEEQ
1882 Say Y here if you have an Seeq based Ethernet network card. This is
1883 used in many Silicon Graphics machines.
1886 tristate "DEC LANCE ethernet controller support"
1887 depends on MACH_DECSTATION
1890 This driver is for the series of Ethernet controllers produced by
1891 DEC (now Compaq) based on the AMD Lance chipset, including the
1892 DEPCA series. (This chipset is better known via the NE2100 cards.)
1895 bool "Motorola 68360 ethernet controller"
1898 Say Y here if you want to use the built-in ethernet controller of
1899 the Motorola 68360 processor.
1902 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1903 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1904 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1907 Say Y here if you want to use the built-in 10/100 Fast ethernet
1908 controller on some Motorola ColdFire and Freescale i.MX processors.
1911 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1914 Say Y here if you want to use the second built-in 10/100 Fast
1915 ethernet controller on some Motorola ColdFire processors.
1918 tristate "MPC52xx FEC driver"
1919 depends on PPC_MPC52xx && PPC_BESTCOMM
1922 select PPC_BESTCOMM_FEC
1924 This option enables support for the MPC5200's on-chip
1925 Fast Ethernet Controller
1926 If compiled as module, it will be called fec_mpc52xx.
1928 config FEC_MPC52xx_MDIO
1929 bool "MPC52xx FEC MDIO bus driver"
1930 depends on FEC_MPC52xx
1933 The MPC5200's FEC can connect to the Ethernet either with
1934 an external MII PHY chip or 10 Mbps 7-wire interface
1935 (Motorola? industry standard).
1936 If your board uses an external PHY connected to FEC, enable this.
1937 If not sure, enable.
1938 If compiled as module, it will be called fec_mpc52xx_phy.
1941 tristate "NE2000 compatible support for H8/300"
1944 Say Y here if you want to use the NE2000 compatible
1945 controller on the Renesas H8/300 processor.
1948 tristate "Atheros L2 Fast Ethernet support"
1953 This driver supports the Atheros L2 fast ethernet adapter.
1955 To compile this driver as a module, choose M here. The module
1956 will be called atl2.
1958 config XILINX_EMACLITE
1959 tristate "Xilinx 10/100 Ethernet Lite support"
1960 depends on PPC32 || MICROBLAZE
1963 This driver supports the 10/100 Ethernet Lite from Xilinx.
1966 tristate "Broadcom 63xx internal mac support"
1971 This driver supports the ethernet MACs in the Broadcom 63xx
1972 MIPS chipset family (BCM63XX).
1974 source "drivers/net/fs_enet/Kconfig"
1976 source "drivers/net/octeon/Kconfig"
1978 endif # NET_ETHERNET
1984 menuconfig NETDEV_1000
1985 bool "Ethernet (1000 Mbit)"
1989 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1990 type of Local Area Network (LAN) in universities and companies.
1992 Say Y here to get to see options for Gigabit Ethernet drivers.
1993 This option alone does not add any kernel code.
1994 Note that drivers supporting both 100 and 1000 MBit may be listed
1995 under "Ethernet (10 or 100MBit)" instead.
1997 If you say N, all options in this submenu will be skipped and disabled.
2002 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2005 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2006 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2007 adapter. The driver allows for using the Jumbo Frame option (9000
2008 bytes/frame) however it requires that your switches can handle this
2009 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2012 To compile this driver as a module, choose M here: the
2013 module will be called acenic.
2015 config ACENIC_OMIT_TIGON_I
2016 bool "Omit support for old Tigon I based AceNICs"
2019 Say Y here if you only have Tigon II based AceNICs and want to leave
2020 out support for the older Tigon I based cards which are no longer
2021 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2022 version)). This will reduce the size of the driver object by
2023 app. 100KB. If you are not sure whether your card is a Tigon I or a
2024 Tigon II, say N here.
2026 The safe and default value for this is N.
2029 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2033 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2035 D-Link DGE-550T Gigabit Ethernet Adapter.
2036 D-Link DL2000-based Gigabit Ethernet Adapter.
2037 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2039 To compile this driver as a module, choose M here: the
2040 module will be called dl2k.
2043 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2046 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2047 adapters. For more information on how to identify your adapter, go
2048 to the Adapter & Driver ID Guide at:
2050 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2052 For general information and support, go to the Intel support
2055 <http://support.intel.com>
2057 More specific information on configuring the driver is in
2058 <file:Documentation/networking/e1000.txt>.
2060 To compile this driver as a module, choose M here. The module
2061 will be called e1000.
2064 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2065 depends on PCI && (!SPARC32 || BROKEN)
2067 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2068 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2069 use the regular e1000 driver For more information on how to
2070 identify your adapter, go to the Adapter & Driver ID Guide at:
2072 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2074 For general information and support, go to the Intel support
2077 <http://support.intel.com>
2079 To compile this driver as a module, choose M here. The module
2080 will be called e1000e.
2083 tristate "IP1000 Gigabit Ethernet support"
2084 depends on PCI && EXPERIMENTAL
2087 This driver supports IP1000 gigabit Ethernet cards.
2089 To compile this driver as a module, choose M here: the module
2090 will be called ipg. This is recommended.
2093 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2096 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2097 adapters. For more information on how to identify your adapter, go
2098 to the Adapter & Driver ID Guide at:
2100 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2102 For general information and support, go to the Intel support
2105 <http://support.intel.com>
2107 More specific information on configuring the driver is in
2108 <file:Documentation/networking/e1000.txt>.
2110 To compile this driver as a module, choose M here. The module
2114 bool "Direct Cache Access (DCA) Support"
2116 depends on IGB && DCA && !(IGB=y && DCA=m)
2118 Say Y here if you want to use Direct Cache Access (DCA) in the
2119 driver. DCA is a method for warming the CPU cache before data
2120 is used, with the intent of lessening the impact of cache misses.
2123 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2126 This driver supports Intel(R) 82576 virtual functions. For more
2127 information on how to identify your adapter, go to the Adapter &
2130 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2132 For general information and support, go to the Intel support
2135 <http://support.intel.com>
2137 More specific information on configuring the driver is in
2138 <file:Documentation/networking/e1000.txt>.
2140 To compile this driver as a module, choose M here. The module
2141 will be called igbvf.
2143 source "drivers/net/ixp2000/Kconfig"
2146 tristate "MyriCOM Gigabit Ethernet support"
2149 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2151 To compile this driver as a module, choose M here: the module
2152 will be called myri_sbus. This is recommended.
2155 tristate "National Semiconductor DP83820 support"
2158 This is a driver for the National Semiconductor DP83820 series
2159 of gigabit ethernet MACs. Cards using this chipset include
2160 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2161 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2165 tristate "Packet Engines Hamachi GNIC-II support"
2169 If you have a Gigabit Ethernet card of this type, say Y and read
2170 the Ethernet-HOWTO, available from
2171 <http://www.tldp.org/docs.html#howto>.
2173 To compile this driver as a module, choose M here. The module will be
2177 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2178 depends on PCI && EXPERIMENTAL
2181 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2182 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2183 used by the Beowulf Linux cluster project. See
2184 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2185 information about this driver in particular and Beowulf in general.
2187 To compile this driver as a module, choose M here: the module
2188 will be called yellowfin. This is recommended.
2191 tristate "Realtek 8169 gigabit ethernet support"
2196 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2198 To compile this driver as a module, choose M here: the module
2199 will be called r8169. This is recommended.
2203 depends on R8169 && VLAN_8021Q
2205 Say Y here for the r8169 driver to support the functions required
2206 by the kernel 802.1Q code.
2211 tristate "SB1250 Gigabit Ethernet support"
2212 depends on SIBYTE_SB1xxx_SOC
2215 This driver supports Gigabit Ethernet interfaces based on the
2216 Broadcom SiByte family of System-On-a-Chip parts. They include
2217 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2220 To compile this driver as a module, choose M here: the module
2221 will be called sb1250-mac.
2224 tristate "SiS190/SiS191 gigabit ethernet support"
2229 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2230 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2231 appear in lan on motherboard designs which are based on SiS 965
2232 and SiS 966 south bridge.
2234 To compile this driver as a module, choose M here: the module
2235 will be called sis190. This is recommended.
2238 tristate "New SysKonnect GigaEthernet support"
2242 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2243 and related Gigabit Ethernet adapters. It is a new smaller driver
2244 with better performance and more complete ethtool support.
2246 It does not support the link failover and network management
2247 features that "portable" vendor supplied sk98lin driver does.
2249 This driver supports adapters based on the original Yukon chipset:
2250 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2251 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2253 It does not support the newer Yukon2 chipset: a separate driver,
2254 sky2, is provided for Yukon2-based adapters.
2256 To compile this driver as a module, choose M here: the module
2257 will be called skge. This is recommended.
2260 bool "Debugging interface"
2261 depends on SKGE && DEBUG_FS
2263 This option adds the ability to dump driver state for debugging.
2264 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2265 transmit and receive rings.
2270 tristate "SysKonnect Yukon2 support"
2274 This driver supports Gigabit Ethernet adapters based on the
2275 Marvell Yukon 2 chipset:
2276 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2277 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2279 There is companion driver for the older Marvell Yukon and
2280 Genesis based adapters: skge.
2282 To compile this driver as a module, choose M here: the module
2283 will be called sky2. This is recommended.
2286 bool "Debugging interface"
2287 depends on SKY2 && DEBUG_FS
2289 This option adds the ability to dump driver state for debugging.
2290 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2291 transmit and receive rings.
2296 tristate "VIA Velocity support"
2302 If you have a VIA "Velocity" based network card say Y here.
2304 To compile this driver as a module, choose M here. The module
2305 will be called via-velocity.
2308 tristate "Broadcom Tigon3 support"
2312 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2314 To compile this driver as a module, choose M here: the module
2315 will be called tg3. This is recommended.
2318 tristate "Broadcom NetXtremeII support"
2323 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2325 To compile this driver as a module, choose M here: the module
2326 will be called bnx2. This is recommended.
2329 tristate "Broadcom CNIC support"
2334 This driver supports offload features of Broadcom NetXtremeII
2335 gigabit Ethernet cards.
2337 To compile this driver as a module, choose M here: the module
2338 will be called cnic. This is recommended.
2341 tristate "Spider Gigabit Ethernet driver"
2342 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2345 This driver supports the Gigabit Ethernet chips present on the
2346 Cell Processor-Based Blades from IBM.
2349 tristate "Tundra TSI108 gigabit Ethernet support"
2350 depends on TSI108_BRIDGE
2352 This driver supports Tundra TSI108 gigabit Ethernet ports.
2353 To compile this driver as a module, choose M here: the module
2354 will be called tsi108_eth.
2357 tristate "PS3 Gigabit Ethernet driver"
2359 select PS3_SYS_MANAGER
2361 This driver supports the network device on the PS3 game
2362 console. This driver has built-in support for Ethernet.
2364 To compile this driver as a module, choose M here: the
2365 module will be called ps3_gelic.
2367 config GELIC_WIRELESS
2368 bool "PS3 Wireless support"
2370 depends on GELIC_NET
2373 This option adds the support for the wireless feature of PS3.
2374 If you have the wireless-less model of PS3 or have no plan to
2375 use wireless feature, disabling this option saves memory. As
2376 the driver automatically distinguishes the models, you can
2377 safely enable this option even if you have a wireless-less model.
2380 tristate "Freescale PQ MDIO"
2384 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2387 tristate "Gianfar Ethernet"
2393 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2394 and MPC86xx family of chips, and the FEC on the 8540.
2397 tristate "Freescale QE Gigabit Ethernet"
2398 depends on QUICC_ENGINE
2402 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2403 which is available on some Freescale SOCs.
2405 config UGETH_TX_ON_DEMAND
2406 bool "Transmit on Demand support"
2410 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2411 depends on MV64X60 || PPC32 || PLAT_ORION
2415 This driver supports the gigabit ethernet MACs in the
2416 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2417 in the Marvell Orion ARM SoC family.
2419 Some boards that use the Discovery chipset are the Momenco
2420 Ocelot C and Jaguar ATX and Pegasos II.
2422 config XILINX_LL_TEMAC
2423 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2424 depends on PPC || MICROBLAZE
2427 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2428 core used in Xilinx Spartan and Virtex FPGAs
2431 tristate "QLogic QLA3XXX Network Driver Support"
2434 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2436 To compile this driver as a module, choose M here: the module
2437 will be called qla3xxx.
2440 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2445 This driver supports the Atheros/Attansic L1 gigabit ethernet
2448 To compile this driver as a module, choose M here. The module
2449 will be called atl1.
2452 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2453 depends on PCI && EXPERIMENTAL
2457 This driver supports the Atheros L1E gigabit ethernet adapter.
2459 To compile this driver as a module, choose M here. The module
2460 will be called atl1e.
2463 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2464 depends on PCI && EXPERIMENTAL
2468 This driver supports the Atheros L1C gigabit ethernet adapter.
2470 To compile this driver as a module, choose M here. The module
2471 will be called atl1c.
2474 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2479 This driver supports the PCI-Express gigabit ethernet adapters
2480 based on JMicron JMC250 chipset.
2482 To compile this driver as a module, choose M here. The module
2486 tristate "S6105 GMAC ethernet support"
2487 depends on XTENSA_VARIANT_S6000
2490 This driver supports the on chip ethernet device on the
2491 S6105 xtensa processor.
2493 To compile this driver as a module, choose M here. The module
2494 will be called s6gmac.
2496 source "drivers/net/stmmac/Kconfig"
2501 # 10 Gigabit Ethernet
2504 menuconfig NETDEV_10000
2505 bool "Ethernet (10000 Mbit)"
2509 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2510 This option alone does not add any kernel code.
2512 If you say N, all options in this submenu will be skipped and disabled.
2520 tristate "Chelsio 10Gb Ethernet support"
2525 This driver supports Chelsio gigabit and 10-gigabit
2526 Ethernet cards. More information about adapter features and
2527 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2529 For general information about Chelsio and our products, visit
2530 our website at <http://www.chelsio.com>.
2532 For customer support, please visit our customer support page at
2533 <http://www.chelsio.com/support.htm>.
2535 Please send feedback to <linux-bugs@chelsio.com>.
2537 To compile this driver as a module, choose M here: the module
2538 will be called cxgb.
2540 config CHELSIO_T1_1G
2541 bool "Chelsio gigabit Ethernet support"
2542 depends on CHELSIO_T1
2544 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2545 are using only 10G cards say 'N' here.
2547 config CHELSIO_T3_DEPENDS
2549 depends on PCI && INET
2553 tristate "Chelsio Communications T3 10Gb Ethernet support"
2554 depends on CHELSIO_T3_DEPENDS
2558 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2561 For general information about Chelsio and our products, visit
2562 our website at <http://www.chelsio.com>.
2564 For customer support, please visit our customer support page at
2565 <http://www.chelsio.com/support.htm>.
2567 Please send feedback to <linux-bugs@chelsio.com>.
2569 To compile this driver as a module, choose M here: the module
2570 will be called cxgb3.
2572 config CHELSIO_T4_DEPENDS
2574 depends on PCI && INET
2578 tristate "Chelsio Communications T4 Ethernet support"
2579 depends on CHELSIO_T4_DEPENDS
2583 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2586 For general information about Chelsio and our products, visit
2587 our website at <http://www.chelsio.com>.
2589 For customer support, please visit our customer support page at
2590 <http://www.chelsio.com/support.htm>.
2592 Please send feedback to <linux-bugs@chelsio.com>.
2594 To compile this driver as a module choose M here; the module
2595 will be called cxgb4.
2598 tristate "eHEA Ethernet support"
2599 depends on IBMEBUS && INET && SPARSEMEM
2602 This driver supports the IBM pSeries eHEA ethernet adapter.
2604 To compile the driver as a module, choose M here. The module
2605 will be called ehea.
2608 tristate "Cisco VIC Ethernet NIC Support"
2609 depends on PCI && INET
2612 This enables the support for the Cisco VIC Ethernet card.
2615 tristate "Intel(R) 10GbE PCI Express adapters support"
2616 depends on PCI && INET
2619 This driver supports Intel(R) 10GbE PCI Express family of
2620 adapters. For more information on how to identify your adapter, go
2621 to the Adapter & Driver ID Guide at:
2623 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2625 For general information and support, go to the Intel support
2628 <http://support.intel.com>
2630 To compile this driver as a module, choose M here. The module
2631 will be called ixgbe.
2634 bool "Direct Cache Access (DCA) Support"
2636 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2638 Say Y here if you want to use Direct Cache Access (DCA) in the
2639 driver. DCA is a method for warming the CPU cache before data
2640 is used, with the intent of lessening the impact of cache misses.
2643 bool "Data Center Bridging (DCB) Support"
2645 depends on IXGBE && DCB
2647 Say Y here if you want to use Data Center Bridging (DCB) in the
2653 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2656 This driver supports Intel(R) 82599 virtual functions. For more
2657 information on how to identify your adapter, go to the Adapter &
2660 <http://support.intel.com/support/network/sb/CS-008441.htm>
2662 For general information and support, go to the Intel support
2665 <http://support.intel.com>
2667 More specific information on configuring the driver is in
2668 <file:Documentation/networking/ixgbevf.txt>.
2670 To compile this driver as a module, choose M here. The module
2671 will be called ixgbevf. MSI-X interrupt support is required
2672 for this driver to work correctly.
2675 tristate "Intel(R) PRO/10GbE support"
2678 This driver supports Intel(R) PRO/10GbE family of adapters for
2679 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2680 instead. For more information on how to identify your adapter, go
2681 to the Adapter & Driver ID Guide at:
2683 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2685 For general information and support, go to the Intel support
2688 <http://support.intel.com>
2690 More specific information on configuring the driver is in
2691 <file:Documentation/networking/ixgb.txt>.
2693 To compile this driver as a module, choose M here. The module
2694 will be called ixgb.
2697 tristate "S2IO 10Gbe XFrame NIC"
2700 This driver supports the 10Gbe XFrame NIC of S2IO.
2701 More specific information on configuring the driver is in
2702 <file:Documentation/networking/s2io.txt>.
2705 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2706 depends on PCI && INET
2708 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2709 I/O Virtualized Server Adapter.
2710 More specific information on configuring the driver is in
2711 <file:Documentation/networking/vxge.txt>.
2713 config VXGE_DEBUG_TRACE_ALL
2714 bool "Enabling All Debug trace statments in driver"
2718 Say Y here if you want to enabling all the debug trace statements in
2719 driver. By default only few debug trace statements are enabled.
2722 tristate "Myricom Myri-10G Ethernet support"
2723 depends on PCI && INET
2728 This driver supports Myricom Myri-10G Dual Protocol interface in
2729 Ethernet mode. If the eeprom on your board is not recent enough,
2730 you will need a newer firmware image.
2731 You may get this image or more information, at:
2733 <http://www.myri.com/scs/download-Myri10GE.html>
2735 To compile this driver as a module, choose M here. The module
2736 will be called myri10ge.
2739 bool "Direct Cache Access (DCA) Support"
2741 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2743 Say Y here if you want to use Direct Cache Access (DCA) in the
2744 driver. DCA is a method for warming the CPU cache before data
2745 is used, with the intent of lessening the impact of cache misses.
2748 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2751 This enables the support for NetXen's Gigabit Ethernet card.
2754 tristate "Sun Neptune 10Gbit Ethernet support"
2758 This enables support for cards based upon Sun's
2762 tristate "PA Semi 1/10Gbit MAC"
2763 depends on PPC_PASEMI && PCI
2767 This driver supports the on-chip 1/10Gbit Ethernet controller on
2768 PA Semi's PWRficient line of chips.
2771 tristate "Mellanox Technologies 10Gbit Ethernet support"
2772 depends on PCI && INET
2776 This driver supports Mellanox Technologies ConnectX Ethernet
2785 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2786 depends on MLX4_CORE
2789 This option causes debugging code to be compiled into the
2790 mlx4_core driver. The output can be turned on via the
2791 debug_level module parameter (which can also be set after
2792 the driver is loaded through sysfs).
2795 tristate "Tehuti Networks 10G Ethernet"
2798 Tehuti Networks 10G Ethernet NIC
2801 tristate "Broadcom NetXtremeII 10Gb support"
2808 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2809 To compile this driver as a module, choose M here: the module
2810 will be called bnx2x. This is recommended.
2813 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2816 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2820 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2823 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2825 To compile this driver as a module, choose M here: the module
2826 will be called qlge.
2828 source "drivers/net/sfc/Kconfig"
2830 source "drivers/net/benet/Kconfig"
2832 endif # NETDEV_10000
2834 source "drivers/net/tokenring/Kconfig"
2836 source "drivers/net/wireless/Kconfig"
2838 source "drivers/net/wimax/Kconfig"
2840 source "drivers/net/usb/Kconfig"
2842 source "drivers/net/pcmcia/Kconfig"
2844 source "drivers/net/wan/Kconfig"
2846 source "drivers/atm/Kconfig"
2848 source "drivers/ieee802154/Kconfig"
2850 source "drivers/s390/net/Kconfig"
2852 source "drivers/net/caif/Kconfig"
2854 config XEN_NETDEV_FRONTEND
2855 tristate "Xen network device frontend driver"
2859 The network device frontend driver allows the kernel to
2860 access network devices exported exported by a virtual
2861 machine containing a physical network device driver. The
2862 frontend driver is intended for unprivileged guest domains;
2863 if you are compiling a kernel for a Xen guest, you almost
2864 certainly want to enable this.
2867 tristate "iSeries Virtual Ethernet driver support"
2868 depends on PPC_ISERIES
2871 tristate "RapidIO Ethernet over messaging driver support"
2874 config RIONET_TX_SIZE
2875 int "Number of outbound queue entries"
2879 config RIONET_RX_SIZE
2880 int "Number of inbound queue entries"
2885 tristate "FDDI driver support"
2886 depends on (PCI || EISA || TC)
2888 Fiber Distributed Data Interface is a high speed local area network
2889 design; essentially a replacement for high speed Ethernet. FDDI can
2890 run over copper or fiber. If you are connected to such a network and
2891 want a driver for the FDDI card in your computer, say Y here (and
2892 then also Y to the driver for your FDDI card, below). Most people
2896 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2897 depends on FDDI && (PCI || EISA || TC)
2899 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2900 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2901 to a local FDDI network.
2903 To compile this driver as a module, choose M here: the module
2904 will be called defxx. If unsure, say N.
2908 prompt "Use MMIO instead of PIO" if PCI || EISA
2910 default n if PCI || EISA
2913 This instructs the driver to use EISA or PCI memory-mapped I/O
2914 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2915 Enabling this gives an improvement in processing time in parts
2916 of the driver, but it may cause problems with EISA (DEFEA)
2917 adapters. TURBOchannel does not have the concept of I/O ports,
2918 so MMIO is always used for these (DEFTA) adapters.
2923 tristate "SysKonnect FDDI PCI support"
2924 depends on FDDI && PCI
2927 Say Y here if you have a SysKonnect FDDI PCI adapter.
2928 The following adapters are supported by this driver:
2929 - SK-5521 (SK-NET FDDI-UP)
2930 - SK-5522 (SK-NET FDDI-UP DAS)
2931 - SK-5541 (SK-NET FDDI-FP)
2932 - SK-5543 (SK-NET FDDI-LP)
2933 - SK-5544 (SK-NET FDDI-LP DAS)
2934 - SK-5821 (SK-NET FDDI-UP64)
2935 - SK-5822 (SK-NET FDDI-UP64 DAS)
2936 - SK-5841 (SK-NET FDDI-FP64)
2937 - SK-5843 (SK-NET FDDI-LP64)
2938 - SK-5844 (SK-NET FDDI-LP64 DAS)
2939 - Netelligent 100 FDDI DAS Fibre SC
2940 - Netelligent 100 FDDI SAS Fibre SC
2941 - Netelligent 100 FDDI DAS UTP
2942 - Netelligent 100 FDDI SAS UTP
2943 - Netelligent 100 FDDI SAS Fibre MIC
2945 Read <file:Documentation/networking/skfp.txt> for information about
2948 Questions concerning this driver can be addressed to:
2949 <linux@syskonnect.de>
2951 To compile this driver as a module, choose M here: the module
2952 will be called skfp. This is recommended.
2955 bool "HIPPI driver support (EXPERIMENTAL)"
2956 depends on EXPERIMENTAL && INET && PCI
2958 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2959 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2960 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2961 single-mode). HIPPI networks are commonly used for clusters and to
2962 connect to super computers. If you are connected to a HIPPI network
2963 and have a HIPPI network card in your computer that you want to use
2964 under Linux, say Y here (you must also remember to enable the driver
2965 for your HIPPI card below). Most people will say N here.
2968 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2969 depends on HIPPI && PCI
2971 Say Y here if this is your PCI HIPPI network card.
2973 To compile this driver as a module, choose M here: the module
2974 will be called rrunner. If unsure, say N.
2976 config ROADRUNNER_LARGE_RINGS
2977 bool "Use large TX/RX rings (EXPERIMENTAL)"
2978 depends on ROADRUNNER
2980 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2981 of additional memory to allow for fastest operation, both for
2982 transmitting and receiving. This memory cannot be used by any other
2983 kernel code or by user space programs. Say Y here only if you have
2987 tristate "PLIP (parallel port) support"
2990 PLIP (Parallel Line Internet Protocol) is used to create a
2991 reasonably fast mini network consisting of two (or, rarely, more)
2992 local machines. A PLIP link from a Linux box is a popular means to
2993 install a Linux distribution on a machine which doesn't have a
2994 CD-ROM drive (a minimal system has to be transferred with floppies
2995 first). The kernels on both machines need to have this PLIP option
2996 enabled for this to work.
2998 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2999 ports (the connectors at the computers with 25 holes) are connected
3000 with "null printer" or "Turbo Laplink" cables which can transmit 4
3001 bits at a time (mode 0) or with special PLIP cables, to be used on
3002 bidirectional parallel ports only, which can transmit 8 bits at a
3003 time (mode 1); you can find the wiring of these cables in
3004 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3005 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3006 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3007 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3008 and winsock or NCSA's telnet.
3010 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3011 as the NET-3-HOWTO, both available from
3012 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3013 protocol has been changed and this PLIP driver won't work together
3014 with the PLIP support in Linux versions 1.0.x. This option enlarges
3015 your kernel by about 8 KB.
3017 To compile this driver as a module, choose M here. The module
3018 will be called plip. If unsure, say Y or M, in case you buy
3022 tristate "PPP (point-to-point protocol) support"
3025 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3026 the same purpose: sending Internet traffic over telephone (and other
3027 serial) lines. Ask your access provider if they support it, because
3028 otherwise you can't use it; most Internet access providers these
3029 days support PPP rather than SLIP.
3031 To use PPP, you need an additional program called pppd as described
3032 in the PPP-HOWTO, available at
3033 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3034 the version of pppd recommended in <file:Documentation/Changes>.
3035 The PPP option enlarges your kernel by about 16 KB.
3037 There are actually two versions of PPP: the traditional PPP for
3038 asynchronous lines, such as regular analog phone lines, and
3039 synchronous PPP which can be used over digital ISDN lines for
3040 example. If you want to use PPP over phone lines or other
3041 asynchronous serial lines, you need to say Y (or M) here and also to
3042 the next option, "PPP support for async serial ports". For PPP over
3043 synchronous lines, you should say Y (or M) here and to "Support
3044 synchronous PPP", below.
3046 If you said Y to "Version information on all symbols" above, then
3047 you cannot compile the PPP driver into the kernel; you can then only
3048 compile it as a module. To compile this driver as a module, choose M
3049 here. The module will be called ppp_generic.
3051 config PPP_MULTILINK
3052 bool "PPP multilink support (EXPERIMENTAL)"
3053 depends on PPP && EXPERIMENTAL
3055 PPP multilink is a protocol (defined in RFC 1990) which allows you
3056 to combine several (logical or physical) lines into one logical PPP
3057 connection, so that you can utilize your full bandwidth.
3059 This has to be supported at the other end as well and you need a
3060 version of the pppd daemon which understands the multilink protocol.
3065 bool "PPP filtering"
3068 Say Y here if you want to be able to filter the packets passing over
3069 PPP interfaces. This allows you to control which packets count as
3070 activity (i.e. which packets will reset the idle timer or bring up
3071 a demand-dialed link) and which packets are to be dropped entirely.
3072 You need to say Y here if you wish to use the pass-filter and
3073 active-filter options to pppd.
3078 tristate "PPP support for async serial ports"
3082 Say Y (or M) here if you want to be able to use PPP over standard
3083 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3084 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3087 To compile this driver as a module, choose M here.
3092 tristate "PPP support for sync tty ports"
3095 Say Y (or M) here if you want to be able to use PPP over synchronous
3096 (HDLC) tty devices, such as the SyncLink adapter. These devices
3097 are often used for high-speed leased lines like T1/E1.
3099 To compile this driver as a module, choose M here.
3102 tristate "PPP Deflate compression"
3107 Support for the Deflate compression method for PPP, which uses the
3108 Deflate algorithm (the same algorithm that gzip uses) to compress
3109 each PPP packet before it is sent over the wire. The machine at the
3110 other end of the PPP link (usually your ISP) has to support the
3111 Deflate compression method as well for this to be useful. Even if
3112 they don't support it, it is safe to say Y here.
3114 To compile this driver as a module, choose M here.
3117 tristate "PPP BSD-Compress compression"
3120 Support for the BSD-Compress compression method for PPP, which uses
3121 the LZW compression method to compress each PPP packet before it is
3122 sent over the wire. The machine at the other end of the PPP link
3123 (usually your ISP) has to support the BSD-Compress compression
3124 method as well for this to be useful. Even if they don't support it,
3125 it is safe to say Y here.
3127 The PPP Deflate compression method ("PPP Deflate compression",
3128 above) is preferable to BSD-Compress, because it compresses better
3131 Note that the BSD compression code will always be compiled as a
3132 module; it is called bsd_comp and will show up in the directory
3133 modules once you have said "make modules". If unsure, say N.
3136 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3137 depends on PPP && EXPERIMENTAL
3143 Support for the MPPE Encryption protocol, as employed by the
3144 Microsoft Point-to-Point Tunneling Protocol.
3146 See http://pptpclient.sourceforge.net/ for information on
3147 configuring PPTP clients and servers to utilize this method.
3150 tristate "PPP over Ethernet (EXPERIMENTAL)"
3151 depends on EXPERIMENTAL && PPP
3153 Support for PPP over Ethernet.
3155 This driver requires the latest version of pppd from the CVS
3156 repository at cvs.samba.org. Alternatively, see the
3157 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3158 which contains instruction on how to use this driver (under
3159 the heading "Kernel mode PPPoE").
3162 tristate "PPP over ATM"
3163 depends on ATM && PPP
3165 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3166 This implementation does not yet comply with section 8 of RFC2364,
3167 which can lead to bad results if the ATM peer loses state and
3168 changes its encapsulation unilaterally.
3171 tristate "PPP over L2TP (EXPERIMENTAL)"
3172 depends on EXPERIMENTAL && L2TP && PPP
3174 Support for PPP-over-L2TP socket family. L2TP is a protocol
3175 used by ISPs and enterprises to tunnel PPP traffic over UDP
3176 tunnels. L2TP is replacing PPTP for VPN uses.
3179 tristate "SLIP (serial line) support"
3181 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3182 connect to your Internet service provider or to connect to some
3183 other local Unix box or if you want to configure your Linux box as a
3184 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3185 Internet Protocol) is a protocol used to send Internet traffic over
3186 serial connections such as telephone lines or null modem cables;
3187 nowadays, the protocol PPP is more commonly used for this same
3190 Normally, your access provider has to support SLIP in order for you
3191 to be able to use it, but there is now a SLIP emulator called SLiRP
3192 around (available from
3193 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3194 allows you to use SLIP over a regular dial up shell connection. If
3195 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3196 NET-3-HOWTO, available from
3197 <http://www.tldp.org/docs.html#howto>, explains how to
3198 configure SLIP. Note that you don't need this option if you just
3199 want to run term (term is a program which gives you almost full
3200 Internet connectivity if you have a regular dial up shell account on
3201 some Internet connected Unix computer. Read
3202 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3203 support will enlarge your kernel by about 4 KB. If unsure, say N.
3205 To compile this driver as a module, choose M here. The module
3206 will be called slip.
3208 config SLIP_COMPRESSED
3209 bool "CSLIP compressed headers"
3213 This protocol is faster than SLIP because it uses compression on the
3214 TCP/IP headers (not on the data itself), but it has to be supported
3215 on both ends. Ask your access provider if you are not sure and
3216 answer Y, just in case. You will still be able to use plain SLIP. If
3217 you plan to use SLiRP, the SLIP emulator (available from
3218 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3219 allows you to use SLIP over a regular dial up shell connection, you
3220 definitely want to say Y here. The NET-3-HOWTO, available from
3221 <http://www.tldp.org/docs.html#howto>, explains how to configure
3222 CSLIP. This won't enlarge your kernel.
3227 This option enables Van Jacobsen serial line header compression
3231 bool "Keepalive and linefill"
3234 Adds additional capabilities to the SLIP driver to support the
3235 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3238 config SLIP_MODE_SLIP6
3239 bool "Six bit SLIP encapsulation"
3242 Just occasionally you may need to run IP over hostile serial
3243 networks that don't pass all control characters or are only seven
3244 bit. Saying Y here adds an extra mode you can use with SLIP:
3245 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3246 the serial device. Naturally, this has to be supported at the other
3247 end of the link as well. It's good enough, for example, to run IP
3248 over the async ports of a Camtec JNT Pad. If unsure, say N.
3251 bool "Fibre Channel driver support"
3252 depends on SCSI && PCI
3254 Fibre Channel is a high speed serial protocol mainly used to connect
3255 large storage devices to the computer; it is compatible with and
3256 intended to replace SCSI.
3258 If you intend to use Fibre Channel, you need to have a Fibre channel
3259 adaptor card in your computer; say Y here and to the driver for your
3260 adaptor below. You also should have said Y to "SCSI support" and
3261 "SCSI generic support".
3264 tristate "Network console logging support"
3266 If you want to log kernel messages over the network, enable this.
3267 See <file:Documentation/networking/netconsole.txt> for details.
3269 config NETCONSOLE_DYNAMIC
3270 bool "Dynamic reconfiguration of logging targets"
3271 depends on NETCONSOLE && SYSFS
3274 This option enables the ability to dynamically reconfigure target
3275 parameters (interface, IP addresses, port numbers, MAC addresses)
3276 at runtime through a userspace interface exported using configfs.
3277 See <file:Documentation/networking/netconsole.txt> for details.
3283 bool "Netpoll traffic trapping"
3287 config NET_POLL_CONTROLLER
3291 tristate "Virtio network driver (EXPERIMENTAL)"
3292 depends on EXPERIMENTAL && VIRTIO
3294 This is the virtual network driver for virtio. It can be used with
3295 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3298 tristate "VMware VMXNET3 ethernet driver"
3299 depends on PCI && INET
3301 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3302 To compile this driver as a module, choose M here: the
3303 module will be called vmxnet3.