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 bool "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 (EXPERIMENTAL)"
884 depends on BFIN_MAC && EXPERIMENTAL
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
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
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 "SMSC LAN911[5678] support"
1002 depends on ARM || SUPERH
1004 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1005 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1006 Say Y if you want it compiled into the kernel,
1007 and read the Ethernet-HOWTO, available from
1008 <http://www.linuxdoc.org/docs.html#howto>.
1010 This driver is also available as a module. The module will be
1011 called smc911x. If you want to compile it as a module, say M
1012 here and read <file:Documentation/kbuild/modules.txt>
1015 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1016 depends on ARM || SUPERH || BLACKFIN || MIPS
1021 Say Y here if you want support for SMSC LAN911x and LAN921x families
1022 of ethernet controllers.
1024 To compile this driver as a module, choose M here and read
1025 <file:Documentation/networking/net-modules.txt>. The module
1026 will be called smsc911x.
1028 config NET_VENDOR_RACAL
1029 bool "Racal-Interlan (Micom) NI cards"
1032 If you have a network (Ethernet) card belonging to this class, such
1033 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1034 available from <http://www.tldp.org/docs.html#howto>.
1036 Note that the answer to this question doesn't directly affect the
1037 kernel: saying N will just cause the configurator to skip all
1038 the questions about NI cards. If you say Y, you will be asked for
1039 your specific card in the following questions.
1042 tristate "NI5010 support (EXPERIMENTAL)"
1043 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1045 If you have a network (Ethernet) card of this type, say Y and read
1046 the Ethernet-HOWTO, available from
1047 <http://www.tldp.org/docs.html#howto>. Note that this is still
1050 To compile this driver as a module, choose M here. The module
1051 will be called ni5010.
1054 tristate "NI5210 support"
1055 depends on NET_VENDOR_RACAL && ISA
1057 If you have a network (Ethernet) card of this type, say Y and read
1058 the Ethernet-HOWTO, available from
1059 <http://www.tldp.org/docs.html#howto>.
1061 To compile this driver as a module, choose M here. The module
1062 will be called ni52.
1065 tristate "NI6510 support"
1066 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1068 If you have a network (Ethernet) card of this type, say Y and read
1069 the Ethernet-HOWTO, available from
1070 <http://www.tldp.org/docs.html#howto>.
1072 To compile this driver as a module, choose M here. The module
1073 will be called ni65.
1076 tristate "Dave ethernet support (DNET)"
1077 depends on NET_ETHERNET && HAS_IOMEM
1080 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1081 Say Y to include support for the DNET chip.
1083 To compile this driver as a module, choose M here: the module
1084 will be called dnet.
1086 source "drivers/net/tulip/Kconfig"
1089 tristate "AT1700/1720 support (EXPERIMENTAL)"
1090 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1093 If you have a network (Ethernet) card of this type, say Y and read
1094 the Ethernet-HOWTO, available from
1095 <http://www.tldp.org/docs.html#howto>.
1097 To compile this driver as a module, choose M here. The module
1098 will be called at1700.
1101 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1102 depends on ISA || EISA || MCA
1105 If you have a network (Ethernet) card of this type, say Y and read
1106 the Ethernet-HOWTO, available from
1107 <http://www.tldp.org/docs.html#howto> as well as
1108 <file:drivers/net/depca.c>.
1110 To compile this driver as a module, choose M here. The module
1111 will be called depca.
1114 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1115 depends on ISA || EISA || PCI
1117 If you have a network (Ethernet) card of this type, say Y and read
1118 the Ethernet-HOWTO, available from
1119 <http://www.tldp.org/docs.html#howto>.
1121 To compile this driver as a module, choose M here. The module
1122 will be called hp100.
1125 bool "Other ISA cards"
1128 If your network (Ethernet) card hasn't been mentioned yet and its
1129 bus system (that's the way the cards talks to the other components
1130 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1131 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1132 available from <http://www.tldp.org/docs.html#howto>.
1136 Note that the answer to this question doesn't directly affect the
1137 kernel: saying N will just cause the configurator to skip all
1138 the remaining ISA network card questions. If you say Y, you will be
1139 asked for your specific card in the following questions.
1142 tristate "Cabletron E21xx support"
1146 If you have a network (Ethernet) card of this type, say Y and read
1147 the Ethernet-HOWTO, available from
1148 <http://www.tldp.org/docs.html#howto>.
1150 To compile this driver as a module, choose M here. The module
1151 will be called e2100.
1154 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1158 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1159 cards. If this is for you, say Y and read
1160 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1161 well as the Ethernet-HOWTO, available from
1162 <http://www.tldp.org/docs.html#howto>.
1164 To compile this driver as a module, choose M here. The module
1165 will be called ewrk3.
1168 tristate "EtherExpress 16 support"
1171 If you have an EtherExpress16 network (Ethernet) card, say Y and
1172 read the Ethernet-HOWTO, available from
1173 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1174 EtherExpress16 card used to be regarded as a very poor choice
1175 because the driver was very unreliable. We now have a new driver
1176 that should do better.
1178 To compile this driver as a module, choose M here. The module
1179 will be called eexpress.
1182 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1185 If you have a network (Ethernet) card of this type, say Y. This
1186 driver supports Intel i82595{FX,TX} based boards. Note however
1187 that the EtherExpress PRO/100 Ethernet card has its own separate
1188 driver. Please read the Ethernet-HOWTO, available from
1189 <http://www.tldp.org/docs.html#howto>.
1191 To compile this driver as a module, choose M here. The module
1192 will be called eepro.
1195 tristate "HP PCLAN+ (27247B and 27252A) support"
1199 If you have a network (Ethernet) card of this type, say Y and read
1200 the Ethernet-HOWTO, available from
1201 <http://www.tldp.org/docs.html#howto>.
1203 To compile this driver as a module, choose M here. The module
1204 will be called hp-plus.
1207 tristate "HP PCLAN (27245 and other 27xxx series) support"
1211 If you have a network (Ethernet) card of this type, say Y and read
1212 the Ethernet-HOWTO, available from
1213 <http://www.tldp.org/docs.html#howto>.
1215 To compile this driver as a module, choose M here. The module
1219 tristate "LP486E on board Ethernet"
1222 Say Y here to support the 82596-based on-board Ethernet controller
1223 for the Panther motherboard, which is one of the two shipped in the
1224 Intel Professional Workstation.
1227 tristate "ICL EtherTeam 16i/32 support"
1230 If you have a network (Ethernet) card of this type, say Y and read
1231 the Ethernet-HOWTO, available from
1232 <http://www.tldp.org/docs.html#howto>.
1234 To compile this driver as a module, choose M here. The module
1235 will be called eth16i.
1238 tristate "NE2000/NE1000 support"
1239 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1242 If you have a network (Ethernet) card of this type, say Y and read
1243 the Ethernet-HOWTO, available from
1244 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1245 without a specific driver are compatible with NE2000.
1247 If you have a PCI NE2000 card however, say N here and Y to "PCI
1248 NE2000 and clone support" under "EISA, VLB, PCI and on board
1249 controllers" below. If you have a NE2000 card and are running on
1250 an MCA system (a bus system used on some IBM PS/2 computers and
1251 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1254 To compile this driver as a module, choose M here. The module
1258 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1259 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1261 The Zenith Z-Note notebook computer has a built-in network
1262 (Ethernet) card, and this is the Linux driver for it. Note that the
1263 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1264 by this driver. Read the Ethernet-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>.
1268 tristate "SEEQ8005 support (EXPERIMENTAL)"
1269 depends on NET_ISA && EXPERIMENTAL
1271 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1272 is for you, read the Ethernet-HOWTO, available from
1273 <http://www.tldp.org/docs.html#howto>.
1275 To compile this driver as a module, choose M here. The module
1276 will be called seeq8005.
1279 tristate "NE/2 (ne2000 MCA version) support"
1280 depends on MCA_LEGACY
1283 If you have a network (Ethernet) card of this type, say Y and read
1284 the Ethernet-HOWTO, available from
1285 <http://www.tldp.org/docs.html#howto>.
1287 To compile this driver as a module, choose M here. The module
1291 tristate "IBM LAN Adapter/A support"
1294 This is a Micro Channel Ethernet adapter. You need to set
1295 CONFIG_MCA to use this driver. It is both available as an in-kernel
1296 driver and as a module.
1298 To compile this driver as a module, choose M here. The only
1299 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1300 will both support 16K and 32K memory windows, however a 32K window
1301 gives a better security against packet losses. Usage of multiple
1302 boards with this driver should be possible, but has not been tested
1303 up to now due to lack of hardware.
1306 tristate "IBM LAN Virtual Ethernet support"
1307 depends on PPC_PSERIES
1309 This driver supports virtual ethernet adapters on newer IBM iSeries
1310 and pSeries systems.
1312 To compile this driver as a module, choose M here. The module will
1315 source "drivers/net/ibm_newemac/Kconfig"
1318 bool "EISA, VLB, PCI and on board controllers"
1319 depends on ISA || EISA || PCI
1321 This is another class of network cards which attach directly to the
1322 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1323 available from <http://www.tldp.org/docs.html#howto>.
1325 Note that the answer to this question doesn't directly affect the
1326 kernel: saying N will just cause the configurator to skip all
1327 the questions about this class of network cards. If you say Y, you
1328 will be asked for your specific card in the following questions. If
1329 you are unsure, say Y.
1332 tristate "AMD PCnet32 PCI support"
1333 depends on NET_PCI && PCI
1337 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1338 answer Y here and read the Ethernet-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here. The module
1342 will be called pcnet32.
1345 tristate "AMD 8111 (new PCI lance) support"
1346 depends on NET_PCI && PCI
1350 If you have an AMD 8111-based PCI lance ethernet card,
1351 answer Y here and read the Ethernet-HOWTO, available from
1352 <http://www.tldp.org/docs.html#howto>.
1354 To compile this driver as a module, choose M here. The module
1355 will be called amd8111e.
1357 config ADAPTEC_STARFIRE
1358 tristate "Adaptec Starfire/DuraLAN support"
1359 depends on NET_PCI && PCI
1363 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1364 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1365 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1368 To compile this driver as a module, choose M here: the module
1369 will be called starfire. This is recommended.
1372 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1373 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1376 If you have a network (Ethernet) card of this type, say Y and read
1377 the Ethernet-HOWTO, available from
1378 <http://www.tldp.org/docs.html#howto>.
1380 To compile this driver as a module, choose M here. The module
1381 will be called ac3200.
1384 tristate "Apricot Xen-II on board Ethernet"
1385 depends on NET_PCI && ISA
1387 If you have a network (Ethernet) controller of this type, say Y and
1388 read the Ethernet-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>.
1391 To compile this driver as a module, choose M here. The module
1392 will be called apricot.
1395 tristate "Broadcom 440x/47xx ethernet support"
1396 depends on SSB_POSSIBLE && HAS_DMA
1400 If you have a network (Ethernet) controller of this type, say Y
1401 or M and read the Ethernet-HOWTO, available from
1402 <http://www.tldp.org/docs.html#howto>.
1404 To compile this driver as a module, choose M here. The module
1407 # Auto-select SSB PCI-HOST support, if possible
1408 config B44_PCI_AUTOSELECT
1410 depends on B44 && SSB_PCIHOST_POSSIBLE
1414 # Auto-select SSB PCICORE driver, if possible
1415 config B44_PCICORE_AUTOSELECT
1417 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1418 select SSB_DRIVER_PCICORE
1423 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1427 tristate "nForce Ethernet support"
1428 depends on NET_PCI && PCI
1430 If you have a network (Ethernet) controller of this type, say Y and
1431 read the Ethernet-HOWTO, available from
1432 <http://www.tldp.org/docs.html#howto>.
1434 To compile this driver as a module, choose M here. The module
1435 will be called forcedeth.
1437 config FORCEDETH_NAPI
1438 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1439 depends on FORCEDETH && EXPERIMENTAL
1441 NAPI is a new driver API designed to reduce CPU and interrupt load
1442 when the driver is receiving lots of packets from the card. It is
1443 still somewhat experimental and thus not yet enabled by default.
1445 If your estimated Rx load is 10kpps or more, or if the card will be
1446 deployed on potentially unfriendly networks (e.g. in a firewall),
1452 tristate "CS89x0 support"
1453 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1454 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1456 Support for CS89x0 chipset based Ethernet cards. If you have a
1457 network (Ethernet) card of this type, say Y and read the
1458 Ethernet-HOWTO, available from
1459 <http://www.tldp.org/docs.html#howto> as well as
1460 <file:Documentation/networking/cs89x0.txt>.
1462 To compile this driver as a module, choose M here. The module
1463 will be called cs89x0.
1465 config CS89x0_NONISA_IRQ
1467 depends on CS89x0 != n
1468 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1471 tristate "TOSHIBA TC35815 Ethernet support"
1472 depends on NET_PCI && PCI && MIPS
1476 tristate "Intel(R) PRO/100+ support"
1477 depends on NET_PCI && PCI
1480 This driver supports Intel(R) PRO/100 family of adapters.
1481 To verify that your adapter is supported, find the board ID number
1482 on the adapter. Look for a label that has a barcode and a number
1483 in the format 123456-001 (six digits hyphen three digits).
1485 Use the above information and the Adapter & Driver ID Guide at:
1487 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1489 to identify the adapter.
1491 For the latest Intel PRO/100 network driver for Linux, see:
1493 <http://appsr.intel.com/scripts-df/support_intel.asp>
1495 More specific information on configuring the driver is in
1496 <file:Documentation/networking/e100.txt>.
1498 To compile this driver as a module, choose M here. The module
1499 will be called e100.
1502 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1503 depends on NET_PCI && EISA && EXPERIMENTAL
1506 If you have a network (Ethernet) card of this type, say Y and read
1507 the Ethernet-HOWTO, available from
1508 <http://www.tldp.org/docs.html#howto>.
1510 To compile this driver as a module, choose M here. The module
1511 will be called lne390.
1514 tristate "Myson MTD-8xx PCI Ethernet support"
1515 depends on NET_PCI && PCI
1519 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1520 cards. Specifications and data at
1521 <http://www.myson.com.hk/mtd/datasheet/>.
1524 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1525 depends on NET_PCI && PCI
1528 This driver is for the National Semiconductor DP83810 series,
1529 which is used in cards from PureData, NetGear, Linksys
1530 and others, including the 83815 chip.
1531 More specific information and updates are available from
1532 <http://www.scyld.com/network/natsemi.html>.
1535 tristate "PCI NE2000 and clones support (see help)"
1536 depends on NET_PCI && PCI
1539 This driver is for NE2000 compatible PCI cards. It will not work
1540 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1541 support" below). If you have a PCI NE2000 network (Ethernet) card,
1542 say Y and read the Ethernet-HOWTO, available from
1543 <http://www.tldp.org/docs.html#howto>.
1545 This driver also works for the following NE2000 clone cards:
1546 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1547 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1548 Holtek HT80232 Holtek HT80229
1550 To compile this driver as a module, choose M here. The module
1551 will be called ne2k-pci.
1554 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1555 depends on NET_PCI && EISA && EXPERIMENTAL
1558 If you have a network (Ethernet) card of this type, say Y and read
1559 the Ethernet-HOWTO, available from
1560 <http://www.tldp.org/docs.html#howto>. Note that this driver
1561 will NOT WORK for NE3200 cards as they are completely different.
1563 To compile this driver as a module, choose M here. The module
1564 will be called ne3210.
1567 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1568 depends on NET_PCI && EISA && EXPERIMENTAL
1571 If you have a network (Ethernet) card of this type, say Y and read
1572 the Ethernet-HOWTO, available from
1573 <http://www.tldp.org/docs.html#howto>.
1575 To compile this driver as a module, choose M here. The module
1576 will be called es3210.
1579 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1580 depends on NET_PCI && PCI && EXPERIMENTAL
1584 This is a driver for the Fast Ethernet PCI network cards based on
1585 the RTL8139C+ chips. If you have one of those, say Y and read
1586 the Ethernet-HOWTO, available from
1587 <http://www.tldp.org/docs.html#howto>.
1589 To compile this driver as a module, choose M here: the module
1590 will be called 8139cp. This is recommended.
1593 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1594 depends on NET_PCI && PCI
1598 This is a driver for the Fast Ethernet PCI network cards based on
1599 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1600 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1602 To compile this driver as a module, choose M here: the module
1603 will be called 8139too. This is recommended.
1606 bool "Use PIO instead of MMIO"
1610 This instructs the driver to use programmed I/O ports (PIO) instead
1611 of PCI shared memory (MMIO). This can possibly solve some problems
1612 in case your mainboard has memory consistency issues. If unsure,
1615 config 8139TOO_TUNE_TWISTER
1616 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1619 This implements a function which might come in handy in case you
1620 are using low quality on long cabling. It is required for RealTek
1621 RTL-8139 revision K boards, and totally unused otherwise. It tries
1622 to match the transceiver to the cable characteristics. This is
1623 experimental since hardly documented by the manufacturer.
1627 bool "Support for older RTL-8129/8130 boards"
1630 This enables support for the older and uncommon RTL-8129 and
1631 RTL-8130 chips, which support MII via an external transceiver,
1632 instead of an internal one. Disabling this option will save some
1633 memory by making the code size smaller. If unsure, say Y.
1635 config 8139_OLD_RX_RESET
1636 bool "Use older RX-reset method"
1639 The 8139too driver was recently updated to contain a more rapid
1640 reset sequence, in the face of severe receive errors. This "new"
1641 RX-reset method should be adequate for all boards. But if you
1642 experience problems, you can enable this option to restore the
1643 old RX-reset behavior. If unsure, say N.
1646 tristate "RDC R6040 Fast Ethernet Adapter support"
1647 depends on NET_PCI && PCI
1651 This is a driver for the R6040 Fast Ethernet MACs found in the
1652 the RDC R-321x System-on-chips.
1654 To compile this driver as a module, choose M here: the module
1655 will be called r6040. This is recommended.
1658 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1659 depends on NET_PCI && PCI
1663 This is a driver for the Fast Ethernet PCI network cards based on
1664 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1665 SiS 630 and SiS 540 chipsets.
1667 This driver also supports AMD 79C901 HomePNA so that you can use
1668 your phone line as a network cable.
1670 To compile this driver as a module, choose M here: the module
1671 will be called sis900. This is recommended.
1674 tristate "SMC EtherPower II"
1675 depends on NET_PCI && PCI
1679 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1680 which is based on the SMC83c17x (EPIC/100).
1681 More specific information and updates are available from
1682 <http://www.scyld.com/network/epic100.html>.
1685 tristate "SMSC LAN9420 PCI ethernet adapter support"
1686 depends on NET_PCI && PCI
1691 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1692 Say Y if you want it compiled into the kernel,
1693 and read the Ethernet-HOWTO, available from
1694 <http://www.linuxdoc.org/docs.html#howto>.
1696 This driver is also available as a module. The module will be
1697 called smsc9420. If you want to compile it as a module, say M
1698 here and read <file:Documentation/kbuild/modules.txt>
1701 tristate "Sundance Alta support"
1702 depends on NET_PCI && PCI
1706 This driver is for the Sundance "Alta" chip.
1707 More specific information and updates are available from
1708 <http://www.scyld.com/network/sundance.html>.
1710 config SUNDANCE_MMIO
1711 bool "Use MMIO instead of PIO"
1714 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1715 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1716 is known to solve bugs on certain chips.
1721 tristate "TI ThunderLAN support"
1722 depends on NET_PCI && (PCI || EISA)
1724 If you have a PCI Ethernet network card based on the ThunderLAN chip
1725 which is supported by this driver, say Y and read the
1726 Ethernet-HOWTO, available from
1727 <http://www.tldp.org/docs.html#howto>.
1729 Devices currently supported by this driver are Compaq Netelligent,
1730 Compaq NetFlex and Olicom cards. Please read the file
1731 <file:Documentation/networking/tlan.txt> for more details.
1733 To compile this driver as a module, choose M here. The module
1734 will be called tlan.
1736 Please email feedback to <torben.mathiasen@compaq.com>.
1739 tristate "Micrel KSZ8842"
1740 depends on HAS_IOMEM
1742 This platform driver is for Micrel KSZ8842 / KS8842
1743 2-port ethernet switch chip (managed, VLAN, QoS).
1746 tristate "Micrel KS8851 SPI"
1751 SPI driver for Micrel KS8851 SPI attached network chip.
1754 tristate "Micrel KS8851 MLL"
1755 depends on HAS_IOMEM
1758 This platform driver is for Micrel KS8851 Address/data bus
1759 multiplexed network chip.
1762 tristate "VIA Rhine support"
1763 depends on NET_PCI && PCI
1767 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1768 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1769 Ethernet functions can also be found integrated on South Bridges
1772 To compile this driver as a module, choose M here. The module
1773 will be called via-rhine.
1775 config VIA_RHINE_MMIO
1776 bool "Use MMIO instead of PIO"
1777 depends on VIA_RHINE
1779 This instructs the driver to use PCI shared memory (MMIO) instead of
1780 programmed I/O ports (PIO). Enabling this gives an improvement in
1781 processing time in parts of the driver.
1786 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1787 depends on NET_PCI && PCI && EXPERIMENTAL
1790 This is a driver for the Fast Ethernet PCI network cards based on
1791 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1792 have one of these, say Y here.
1794 To compile this driver as a module, choose M here: the module
1795 will be called sc92031. This is recommended.
1798 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1799 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1802 TI AR7 CPMAC Ethernet support
1805 bool "Pocket and portable adapters"
1808 Cute little network (Ethernet) devices which attach to the parallel
1809 port ("pocket adapters"), commonly used with laptops. If you have
1810 one of those, say Y and read the Ethernet-HOWTO, available from
1811 <http://www.tldp.org/docs.html#howto>.
1813 If you want to plug a network (or some other) card into the PCMCIA
1814 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1815 credit card size extension cards used by all modern laptops), you
1816 need the pcmcia-cs package (location contained in the file
1817 <file:Documentation/Changes>) and you can say N here.
1819 Laptop users should read the Linux Laptop home page at
1820 <http://www.linux-on-laptops.com/> or
1821 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1823 Note that the answer to this question doesn't directly affect the
1824 kernel: saying N will just cause the configurator to skip all
1825 the questions about this class of network devices. If you say Y, you
1826 will be asked for your specific device in the following questions.
1829 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1830 depends on NET_POCKET && PARPORT && X86
1833 This is a network (Ethernet) device which attaches to your parallel
1834 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1835 available from <http://www.tldp.org/docs.html#howto>, if you
1836 want to use this. If you intend to use this driver, you should have
1837 said N to the "Parallel printer support", because the two drivers
1838 don't like each other.
1840 To compile this driver as a module, choose M here: the module
1844 tristate "D-Link DE600 pocket adapter support"
1845 depends on NET_POCKET && PARPORT
1847 This is a network (Ethernet) device which attaches to your parallel
1848 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1849 Ethernet-HOWTO, available from
1850 <http://www.tldp.org/docs.html#howto>, if you want to use
1851 this. It is possible to have several devices share a single parallel
1852 port and it is safe to compile the corresponding drivers into the
1855 To compile this driver as a module, choose M here: the module
1856 will be called de600.
1859 tristate "D-Link DE620 pocket adapter support"
1860 depends on NET_POCKET && PARPORT
1862 This is a network (Ethernet) device which attaches to your parallel
1863 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1864 Ethernet-HOWTO, available from
1865 <http://www.tldp.org/docs.html#howto>, if you want to use
1866 this. It is possible to have several devices share a single parallel
1867 port and it is safe to compile the corresponding drivers into the
1870 To compile this driver as a module, choose M here: the module
1871 will be called de620.
1874 tristate "SGI Seeq ethernet controller support"
1875 depends on SGI_HAS_SEEQ
1877 Say Y here if you have an Seeq based Ethernet network card. This is
1878 used in many Silicon Graphics machines.
1881 tristate "DEC LANCE ethernet controller support"
1882 depends on MACH_DECSTATION
1885 This driver is for the series of Ethernet controllers produced by
1886 DEC (now Compaq) based on the AMD Lance chipset, including the
1887 DEPCA series. (This chipset is better known via the NE2100 cards.)
1890 bool "Motorola 68360 ethernet controller"
1893 Say Y here if you want to use the built-in ethernet controller of
1894 the Motorola 68360 processor.
1897 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1898 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1899 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1901 Say Y here if you want to use the built-in 10/100 Fast ethernet
1902 controller on some Motorola ColdFire and Freescale i.MX processors.
1905 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1908 Say Y here if you want to use the second built-in 10/100 Fast
1909 ethernet controller on some Motorola ColdFire processors.
1912 tristate "MPC52xx FEC driver"
1913 depends on PPC_MPC52xx && PPC_BESTCOMM
1916 select PPC_BESTCOMM_FEC
1918 This option enables support for the MPC5200's on-chip
1919 Fast Ethernet Controller
1920 If compiled as module, it will be called fec_mpc52xx.
1922 config FEC_MPC52xx_MDIO
1923 bool "MPC52xx FEC MDIO bus driver"
1924 depends on FEC_MPC52xx
1927 The MPC5200's FEC can connect to the Ethernet either with
1928 an external MII PHY chip or 10 Mbps 7-wire interface
1929 (Motorola? industry standard).
1930 If your board uses an external PHY connected to FEC, enable this.
1931 If not sure, enable.
1932 If compiled as module, it will be called fec_mpc52xx_phy.
1935 tristate "NE2000 compatible support for H8/300"
1938 Say Y here if you want to use the NE2000 compatible
1939 controller on the Renesas H8/300 processor.
1942 tristate "Atheros L2 Fast Ethernet support"
1947 This driver supports the Atheros L2 fast ethernet adapter.
1949 To compile this driver as a module, choose M here. The module
1950 will be called atl2.
1952 config XILINX_EMACLITE
1953 tristate "Xilinx 10/100 Ethernet Lite support"
1954 depends on PPC32 || MICROBLAZE
1956 This driver supports the 10/100 Ethernet Lite from Xilinx.
1959 tristate "Broadcom 63xx internal mac support"
1964 This driver supports the ethernet MACs in the Broadcom 63xx
1965 MIPS chipset family (BCM63XX).
1967 source "drivers/net/fs_enet/Kconfig"
1969 source "drivers/net/octeon/Kconfig"
1971 endif # NET_ETHERNET
1977 menuconfig NETDEV_1000
1978 bool "Ethernet (1000 Mbit)"
1982 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1983 type of Local Area Network (LAN) in universities and companies.
1985 Say Y here to get to see options for Gigabit Ethernet drivers.
1986 This option alone does not add any kernel code.
1987 Note that drivers supporting both 100 and 1000 MBit may be listed
1988 under "Ethernet (10 or 100MBit)" instead.
1990 If you say N, all options in this submenu will be skipped and disabled.
1995 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1998 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1999 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2000 adapter. The driver allows for using the Jumbo Frame option (9000
2001 bytes/frame) however it requires that your switches can handle this
2002 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2005 To compile this driver as a module, choose M here: the
2006 module will be called acenic.
2008 config ACENIC_OMIT_TIGON_I
2009 bool "Omit support for old Tigon I based AceNICs"
2012 Say Y here if you only have Tigon II based AceNICs and want to leave
2013 out support for the older Tigon I based cards which are no longer
2014 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2015 version)). This will reduce the size of the driver object by
2016 app. 100KB. If you are not sure whether your card is a Tigon I or a
2017 Tigon II, say N here.
2019 The safe and default value for this is N.
2022 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2026 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2028 D-Link DGE-550T Gigabit Ethernet Adapter.
2029 D-Link DL2000-based Gigabit Ethernet Adapter.
2030 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2032 To compile this driver as a module, choose M here: the
2033 module will be called dl2k.
2036 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2039 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2040 adapters. For more information on how to identify your adapter, go
2041 to the Adapter & Driver ID Guide at:
2043 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2045 For general information and support, go to the Intel support
2048 <http://support.intel.com>
2050 More specific information on configuring the driver is in
2051 <file:Documentation/networking/e1000.txt>.
2053 To compile this driver as a module, choose M here. The module
2054 will be called e1000.
2057 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2058 depends on PCI && (!SPARC32 || BROKEN)
2060 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2061 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2062 use the regular e1000 driver For more information on how to
2063 identify your adapter, go to the Adapter & Driver ID Guide at:
2065 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2067 For general information and support, go to the Intel support
2070 <http://support.intel.com>
2072 To compile this driver as a module, choose M here. The module
2073 will be called e1000e.
2076 tristate "IP1000 Gigabit Ethernet support"
2077 depends on PCI && EXPERIMENTAL
2080 This driver supports IP1000 gigabit Ethernet cards.
2082 To compile this driver as a module, choose M here: the module
2083 will be called ipg. This is recommended.
2086 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2089 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2090 adapters. For more information on how to identify your adapter, go
2091 to the Adapter & Driver ID Guide at:
2093 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2095 For general information and support, go to the Intel support
2098 <http://support.intel.com>
2100 More specific information on configuring the driver is in
2101 <file:Documentation/networking/e1000.txt>.
2103 To compile this driver as a module, choose M here. The module
2107 bool "Direct Cache Access (DCA) Support"
2109 depends on IGB && DCA && !(IGB=y && DCA=m)
2111 Say Y here if you want to use Direct Cache Access (DCA) in the
2112 driver. DCA is a method for warming the CPU cache before data
2113 is used, with the intent of lessening the impact of cache misses.
2116 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2119 This driver supports Intel(R) 82576 virtual functions. For more
2120 information on how to identify your adapter, go to the Adapter &
2123 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2125 For general information and support, go to the Intel support
2128 <http://support.intel.com>
2130 More specific information on configuring the driver is in
2131 <file:Documentation/networking/e1000.txt>.
2133 To compile this driver as a module, choose M here. The module
2134 will be called igbvf.
2136 source "drivers/net/ixp2000/Kconfig"
2139 tristate "MyriCOM Gigabit Ethernet support"
2142 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2144 To compile this driver as a module, choose M here: the module
2145 will be called myri_sbus. This is recommended.
2148 tristate "National Semiconductor DP83820 support"
2151 This is a driver for the National Semiconductor DP83820 series
2152 of gigabit ethernet MACs. Cards using this chipset include
2153 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2154 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2158 tristate "Packet Engines Hamachi GNIC-II support"
2162 If you have a Gigabit Ethernet card of this type, say Y and read
2163 the Ethernet-HOWTO, available from
2164 <http://www.tldp.org/docs.html#howto>.
2166 To compile this driver as a module, choose M here. The module will be
2170 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2171 depends on PCI && EXPERIMENTAL
2174 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2175 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2176 used by the Beowulf Linux cluster project. See
2177 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2178 information about this driver in particular and Beowulf in general.
2180 To compile this driver as a module, choose M here: the module
2181 will be called yellowfin. This is recommended.
2184 tristate "Realtek 8169 gigabit ethernet support"
2189 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2191 To compile this driver as a module, choose M here: the module
2192 will be called r8169. This is recommended.
2196 depends on R8169 && VLAN_8021Q
2198 Say Y here for the r8169 driver to support the functions required
2199 by the kernel 802.1Q code.
2204 tristate "SB1250 Gigabit Ethernet support"
2205 depends on SIBYTE_SB1xxx_SOC
2208 This driver supports Gigabit Ethernet interfaces based on the
2209 Broadcom SiByte family of System-On-a-Chip parts. They include
2210 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2213 To compile this driver as a module, choose M here: the module
2214 will be called sb1250-mac.
2217 tristate "SiS190/SiS191 gigabit ethernet support"
2222 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2223 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2224 appear in lan on motherboard designs which are based on SiS 965
2225 and SiS 966 south bridge.
2227 To compile this driver as a module, choose M here: the module
2228 will be called sis190. This is recommended.
2231 tristate "New SysKonnect GigaEthernet support"
2235 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2236 and related Gigabit Ethernet adapters. It is a new smaller driver
2237 with better performance and more complete ethtool support.
2239 It does not support the link failover and network management
2240 features that "portable" vendor supplied sk98lin driver does.
2242 This driver supports adapters based on the original Yukon chipset:
2243 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2244 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2246 It does not support the newer Yukon2 chipset: a separate driver,
2247 sky2, is provided for Yukon2-based adapters.
2249 To compile this driver as a module, choose M here: the module
2250 will be called skge. This is recommended.
2253 bool "Debugging interface"
2254 depends on SKGE && DEBUG_FS
2256 This option adds the ability to dump driver state for debugging.
2257 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2258 transmit and receive rings.
2263 tristate "SysKonnect Yukon2 support"
2267 This driver supports Gigabit Ethernet adapters based on the
2268 Marvell Yukon 2 chipset:
2269 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2270 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2272 There is companion driver for the older Marvell Yukon and
2273 Genesis based adapters: skge.
2275 To compile this driver as a module, choose M here: the module
2276 will be called sky2. This is recommended.
2279 bool "Debugging interface"
2280 depends on SKY2 && DEBUG_FS
2282 This option adds the ability to dump driver state for debugging.
2283 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2284 transmit and receive rings.
2289 tristate "VIA Velocity support"
2295 If you have a VIA "Velocity" based network card say Y here.
2297 To compile this driver as a module, choose M here. The module
2298 will be called via-velocity.
2301 tristate "Broadcom Tigon3 support"
2305 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2307 To compile this driver as a module, choose M here: the module
2308 will be called tg3. This is recommended.
2311 tristate "Broadcom NetXtremeII support"
2316 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2318 To compile this driver as a module, choose M here: the module
2319 will be called bnx2. This is recommended.
2322 tristate "Broadcom CNIC support"
2327 This driver supports offload features of Broadcom NetXtremeII
2328 gigabit Ethernet cards.
2330 To compile this driver as a module, choose M here: the module
2331 will be called cnic. This is recommended.
2334 tristate "Spider Gigabit Ethernet driver"
2335 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2338 This driver supports the Gigabit Ethernet chips present on the
2339 Cell Processor-Based Blades from IBM.
2342 tristate "Tundra TSI108 gigabit Ethernet support"
2343 depends on TSI108_BRIDGE
2345 This driver supports Tundra TSI108 gigabit Ethernet ports.
2346 To compile this driver as a module, choose M here: the module
2347 will be called tsi108_eth.
2350 tristate "PS3 Gigabit Ethernet driver"
2352 select PS3_SYS_MANAGER
2354 This driver supports the network device on the PS3 game
2355 console. This driver has built-in support for Ethernet.
2357 To compile this driver as a module, choose M here: the
2358 module will be called ps3_gelic.
2360 config GELIC_WIRELESS
2361 bool "PS3 Wireless support"
2363 depends on GELIC_NET
2366 This option adds the support for the wireless feature of PS3.
2367 If you have the wireless-less model of PS3 or have no plan to
2368 use wireless feature, disabling this option saves memory. As
2369 the driver automatically distinguishes the models, you can
2370 safely enable this option even if you have a wireless-less model.
2373 tristate "Freescale PQ MDIO"
2377 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2380 tristate "Gianfar Ethernet"
2386 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2387 and MPC86xx family of chips, and the FEC on the 8540.
2390 tristate "Freescale QE Gigabit Ethernet"
2391 depends on QUICC_ENGINE
2395 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2396 which is available on some Freescale SOCs.
2398 config UGETH_TX_ON_DEMAND
2399 bool "Transmit on Demand support"
2403 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2404 depends on MV64X60 || PPC32 || PLAT_ORION
2408 This driver supports the gigabit ethernet MACs in the
2409 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2410 in the Marvell Orion ARM SoC family.
2412 Some boards that use the Discovery chipset are the Momenco
2413 Ocelot C and Jaguar ATX and Pegasos II.
2415 config XILINX_LL_TEMAC
2416 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2418 depends on PPC_DCR_NATIVE
2420 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2421 core used in Xilinx Spartan and Virtex FPGAs
2424 tristate "QLogic QLA3XXX Network Driver Support"
2427 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2429 To compile this driver as a module, choose M here: the module
2430 will be called qla3xxx.
2433 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2438 This driver supports the Atheros/Attansic L1 gigabit ethernet
2441 To compile this driver as a module, choose M here. The module
2442 will be called atl1.
2445 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2446 depends on PCI && EXPERIMENTAL
2450 This driver supports the Atheros L1E gigabit ethernet adapter.
2452 To compile this driver as a module, choose M here. The module
2453 will be called atl1e.
2456 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2457 depends on PCI && EXPERIMENTAL
2461 This driver supports the Atheros L1C gigabit ethernet adapter.
2463 To compile this driver as a module, choose M here. The module
2464 will be called atl1c.
2467 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2472 This driver supports the PCI-Express gigabit ethernet adapters
2473 based on JMicron JMC250 chipset.
2475 To compile this driver as a module, choose M here. The module
2479 tristate "S6105 GMAC ethernet support"
2480 depends on XTENSA_VARIANT_S6000
2483 This driver supports the on chip ethernet device on the
2484 S6105 xtensa processor.
2486 To compile this driver as a module, choose M here. The module
2487 will be called s6gmac.
2489 source "drivers/net/stmmac/Kconfig"
2494 # 10 Gigabit Ethernet
2497 menuconfig NETDEV_10000
2498 bool "Ethernet (10000 Mbit)"
2502 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2503 This option alone does not add any kernel code.
2505 If you say N, all options in this submenu will be skipped and disabled.
2513 tristate "Chelsio 10Gb Ethernet support"
2518 This driver supports Chelsio gigabit and 10-gigabit
2519 Ethernet cards. More information about adapter features and
2520 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2522 For general information about Chelsio and our products, visit
2523 our website at <http://www.chelsio.com>.
2525 For customer support, please visit our customer support page at
2526 <http://www.chelsio.com/support.htm>.
2528 Please send feedback to <linux-bugs@chelsio.com>.
2530 To compile this driver as a module, choose M here: the module
2531 will be called cxgb.
2533 config CHELSIO_T1_1G
2534 bool "Chelsio gigabit Ethernet support"
2535 depends on CHELSIO_T1
2537 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2538 are using only 10G cards say 'N' here.
2540 config CHELSIO_T3_DEPENDS
2542 depends on PCI && INET
2546 tristate "Chelsio Communications T3 10Gb Ethernet support"
2547 depends on CHELSIO_T3_DEPENDS
2551 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2554 For general information about Chelsio and our products, visit
2555 our website at <http://www.chelsio.com>.
2557 For customer support, please visit our customer support page at
2558 <http://www.chelsio.com/support.htm>.
2560 Please send feedback to <linux-bugs@chelsio.com>.
2562 To compile this driver as a module, choose M here: the module
2563 will be called cxgb3.
2566 tristate "eHEA Ethernet support"
2567 depends on IBMEBUS && INET && SPARSEMEM
2570 This driver supports the IBM pSeries eHEA ethernet adapter.
2572 To compile the driver as a module, choose M here. The module
2573 will be called ehea.
2576 tristate "Cisco 10G Ethernet NIC support"
2577 depends on PCI && INET
2580 This enables the support for the Cisco 10G Ethernet card.
2583 tristate "Intel(R) 10GbE PCI Express adapters support"
2584 depends on PCI && INET
2587 This driver supports Intel(R) 10GbE PCI Express family of
2588 adapters. For more information on how to identify your adapter, go
2589 to the Adapter & Driver ID Guide at:
2591 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2593 For general information and support, go to the Intel support
2596 <http://support.intel.com>
2598 To compile this driver as a module, choose M here. The module
2599 will be called ixgbe.
2602 bool "Direct Cache Access (DCA) Support"
2604 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2606 Say Y here if you want to use Direct Cache Access (DCA) in the
2607 driver. DCA is a method for warming the CPU cache before data
2608 is used, with the intent of lessening the impact of cache misses.
2611 bool "Data Center Bridging (DCB) Support"
2613 depends on IXGBE && DCB
2615 Say Y here if you want to use Data Center Bridging (DCB) in the
2621 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2624 This driver supports Intel(R) 82599 virtual functions. For more
2625 information on how to identify your adapter, go to the Adapter &
2628 <http://support.intel.com/support/network/sb/CS-008441.htm>
2630 For general information and support, go to the Intel support
2633 <http://support.intel.com>
2635 More specific information on configuring the driver is in
2636 <file:Documentation/networking/ixgbevf.txt>.
2638 To compile this driver as a module, choose M here. The module
2639 will be called ixgbevf. MSI-X interrupt support is required
2640 for this driver to work correctly.
2643 tristate "Intel(R) PRO/10GbE support"
2646 This driver supports Intel(R) PRO/10GbE family of adapters for
2647 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2648 instead. For more information on how to identify your adapter, go
2649 to the Adapter & Driver ID Guide at:
2651 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2653 For general information and support, go to the Intel support
2656 <http://support.intel.com>
2658 More specific information on configuring the driver is in
2659 <file:Documentation/networking/ixgb.txt>.
2661 To compile this driver as a module, choose M here. The module
2662 will be called ixgb.
2665 tristate "S2IO 10Gbe XFrame NIC"
2668 This driver supports the 10Gbe XFrame NIC of S2IO.
2669 More specific information on configuring the driver is in
2670 <file:Documentation/networking/s2io.txt>.
2673 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2674 depends on PCI && INET
2676 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2677 I/O Virtualized Server Adapter.
2678 More specific information on configuring the driver is in
2679 <file:Documentation/networking/vxge.txt>.
2681 config VXGE_DEBUG_TRACE_ALL
2682 bool "Enabling All Debug trace statments in driver"
2686 Say Y here if you want to enabling all the debug trace statements in
2687 driver. By default only few debug trace statements are enabled.
2690 tristate "Myricom Myri-10G Ethernet support"
2691 depends on PCI && INET
2696 This driver supports Myricom Myri-10G Dual Protocol interface in
2697 Ethernet mode. If the eeprom on your board is not recent enough,
2698 you will need a newer firmware image.
2699 You may get this image or more information, at:
2701 <http://www.myri.com/scs/download-Myri10GE.html>
2703 To compile this driver as a module, choose M here. The module
2704 will be called myri10ge.
2707 bool "Direct Cache Access (DCA) Support"
2709 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2711 Say Y here if you want to use Direct Cache Access (DCA) in the
2712 driver. DCA is a method for warming the CPU cache before data
2713 is used, with the intent of lessening the impact of cache misses.
2716 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2719 This enables the support for NetXen's Gigabit Ethernet card.
2722 tristate "Sun Neptune 10Gbit Ethernet support"
2726 This enables support for cards based upon Sun's
2730 tristate "PA Semi 1/10Gbit MAC"
2731 depends on PPC_PASEMI && PCI
2735 This driver supports the on-chip 1/10Gbit Ethernet controller on
2736 PA Semi's PWRficient line of chips.
2739 tristate "Mellanox Technologies 10Gbit Ethernet support"
2740 depends on PCI && INET
2744 This driver supports Mellanox Technologies ConnectX Ethernet
2753 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2754 depends on MLX4_CORE
2757 This option causes debugging code to be compiled into the
2758 mlx4_core driver. The output can be turned on via the
2759 debug_level module parameter (which can also be set after
2760 the driver is loaded through sysfs).
2763 tristate "Tehuti Networks 10G Ethernet"
2766 Tehuti Networks 10G Ethernet NIC
2769 tristate "Broadcom NetXtremeII 10Gb support"
2776 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2777 To compile this driver as a module, choose M here: the module
2778 will be called bnx2x. This is recommended.
2781 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2784 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2788 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2791 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2793 To compile this driver as a module, choose M here: the module
2794 will be called qlge.
2796 source "drivers/net/sfc/Kconfig"
2798 source "drivers/net/benet/Kconfig"
2800 endif # NETDEV_10000
2802 source "drivers/net/tokenring/Kconfig"
2804 source "drivers/net/wireless/Kconfig"
2806 source "drivers/net/wimax/Kconfig"
2808 source "drivers/net/usb/Kconfig"
2810 source "drivers/net/pcmcia/Kconfig"
2812 source "drivers/net/wan/Kconfig"
2814 source "drivers/atm/Kconfig"
2816 source "drivers/ieee802154/Kconfig"
2818 source "drivers/s390/net/Kconfig"
2820 config XEN_NETDEV_FRONTEND
2821 tristate "Xen network device frontend driver"
2825 The network device frontend driver allows the kernel to
2826 access network devices exported exported by a virtual
2827 machine containing a physical network device driver. The
2828 frontend driver is intended for unprivileged guest domains;
2829 if you are compiling a kernel for a Xen guest, you almost
2830 certainly want to enable this.
2833 tristate "iSeries Virtual Ethernet driver support"
2834 depends on PPC_ISERIES
2837 tristate "RapidIO Ethernet over messaging driver support"
2840 config RIONET_TX_SIZE
2841 int "Number of outbound queue entries"
2845 config RIONET_RX_SIZE
2846 int "Number of inbound queue entries"
2851 tristate "FDDI driver support"
2852 depends on (PCI || EISA || TC)
2854 Fiber Distributed Data Interface is a high speed local area network
2855 design; essentially a replacement for high speed Ethernet. FDDI can
2856 run over copper or fiber. If you are connected to such a network and
2857 want a driver for the FDDI card in your computer, say Y here (and
2858 then also Y to the driver for your FDDI card, below). Most people
2862 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2863 depends on FDDI && (PCI || EISA || TC)
2865 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2866 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2867 to a local FDDI network.
2869 To compile this driver as a module, choose M here: the module
2870 will be called defxx. If unsure, say N.
2874 prompt "Use MMIO instead of PIO" if PCI || EISA
2876 default n if PCI || EISA
2879 This instructs the driver to use EISA or PCI memory-mapped I/O
2880 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2881 Enabling this gives an improvement in processing time in parts
2882 of the driver, but it may cause problems with EISA (DEFEA)
2883 adapters. TURBOchannel does not have the concept of I/O ports,
2884 so MMIO is always used for these (DEFTA) adapters.
2889 tristate "SysKonnect FDDI PCI support"
2890 depends on FDDI && PCI
2893 Say Y here if you have a SysKonnect FDDI PCI adapter.
2894 The following adapters are supported by this driver:
2895 - SK-5521 (SK-NET FDDI-UP)
2896 - SK-5522 (SK-NET FDDI-UP DAS)
2897 - SK-5541 (SK-NET FDDI-FP)
2898 - SK-5543 (SK-NET FDDI-LP)
2899 - SK-5544 (SK-NET FDDI-LP DAS)
2900 - SK-5821 (SK-NET FDDI-UP64)
2901 - SK-5822 (SK-NET FDDI-UP64 DAS)
2902 - SK-5841 (SK-NET FDDI-FP64)
2903 - SK-5843 (SK-NET FDDI-LP64)
2904 - SK-5844 (SK-NET FDDI-LP64 DAS)
2905 - Netelligent 100 FDDI DAS Fibre SC
2906 - Netelligent 100 FDDI SAS Fibre SC
2907 - Netelligent 100 FDDI DAS UTP
2908 - Netelligent 100 FDDI SAS UTP
2909 - Netelligent 100 FDDI SAS Fibre MIC
2911 Read <file:Documentation/networking/skfp.txt> for information about
2914 Questions concerning this driver can be addressed to:
2915 <linux@syskonnect.de>
2917 To compile this driver as a module, choose M here: the module
2918 will be called skfp. This is recommended.
2921 bool "HIPPI driver support (EXPERIMENTAL)"
2922 depends on EXPERIMENTAL && INET && PCI
2924 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2925 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2926 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2927 single-mode). HIPPI networks are commonly used for clusters and to
2928 connect to super computers. If you are connected to a HIPPI network
2929 and have a HIPPI network card in your computer that you want to use
2930 under Linux, say Y here (you must also remember to enable the driver
2931 for your HIPPI card below). Most people will say N here.
2934 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2935 depends on HIPPI && PCI
2937 Say Y here if this is your PCI HIPPI network card.
2939 To compile this driver as a module, choose M here: the module
2940 will be called rrunner. If unsure, say N.
2942 config ROADRUNNER_LARGE_RINGS
2943 bool "Use large TX/RX rings (EXPERIMENTAL)"
2944 depends on ROADRUNNER
2946 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2947 of additional memory to allow for fastest operation, both for
2948 transmitting and receiving. This memory cannot be used by any other
2949 kernel code or by user space programs. Say Y here only if you have
2953 tristate "PLIP (parallel port) support"
2956 PLIP (Parallel Line Internet Protocol) is used to create a
2957 reasonably fast mini network consisting of two (or, rarely, more)
2958 local machines. A PLIP link from a Linux box is a popular means to
2959 install a Linux distribution on a machine which doesn't have a
2960 CD-ROM drive (a minimal system has to be transferred with floppies
2961 first). The kernels on both machines need to have this PLIP option
2962 enabled for this to work.
2964 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2965 ports (the connectors at the computers with 25 holes) are connected
2966 with "null printer" or "Turbo Laplink" cables which can transmit 4
2967 bits at a time (mode 0) or with special PLIP cables, to be used on
2968 bidirectional parallel ports only, which can transmit 8 bits at a
2969 time (mode 1); you can find the wiring of these cables in
2970 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2971 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2972 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2973 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2974 and winsock or NCSA's telnet.
2976 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2977 as the NET-3-HOWTO, both available from
2978 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2979 protocol has been changed and this PLIP driver won't work together
2980 with the PLIP support in Linux versions 1.0.x. This option enlarges
2981 your kernel by about 8 KB.
2983 To compile this driver as a module, choose M here. The module
2984 will be called plip. If unsure, say Y or M, in case you buy
2988 tristate "PPP (point-to-point protocol) support"
2991 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2992 the same purpose: sending Internet traffic over telephone (and other
2993 serial) lines. Ask your access provider if they support it, because
2994 otherwise you can't use it; most Internet access providers these
2995 days support PPP rather than SLIP.
2997 To use PPP, you need an additional program called pppd as described
2998 in the PPP-HOWTO, available at
2999 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3000 the version of pppd recommended in <file:Documentation/Changes>.
3001 The PPP option enlarges your kernel by about 16 KB.
3003 There are actually two versions of PPP: the traditional PPP for
3004 asynchronous lines, such as regular analog phone lines, and
3005 synchronous PPP which can be used over digital ISDN lines for
3006 example. If you want to use PPP over phone lines or other
3007 asynchronous serial lines, you need to say Y (or M) here and also to
3008 the next option, "PPP support for async serial ports". For PPP over
3009 synchronous lines, you should say Y (or M) here and to "Support
3010 synchronous PPP", below.
3012 If you said Y to "Version information on all symbols" above, then
3013 you cannot compile the PPP driver into the kernel; you can then only
3014 compile it as a module. To compile this driver as a module, choose M
3015 here. The module will be called ppp_generic.
3017 config PPP_MULTILINK
3018 bool "PPP multilink support (EXPERIMENTAL)"
3019 depends on PPP && EXPERIMENTAL
3021 PPP multilink is a protocol (defined in RFC 1990) which allows you
3022 to combine several (logical or physical) lines into one logical PPP
3023 connection, so that you can utilize your full bandwidth.
3025 This has to be supported at the other end as well and you need a
3026 version of the pppd daemon which understands the multilink protocol.
3031 bool "PPP filtering"
3034 Say Y here if you want to be able to filter the packets passing over
3035 PPP interfaces. This allows you to control which packets count as
3036 activity (i.e. which packets will reset the idle timer or bring up
3037 a demand-dialed link) and which packets are to be dropped entirely.
3038 You need to say Y here if you wish to use the pass-filter and
3039 active-filter options to pppd.
3044 tristate "PPP support for async serial ports"
3048 Say Y (or M) here if you want to be able to use PPP over standard
3049 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3050 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3053 To compile this driver as a module, choose M here.
3058 tristate "PPP support for sync tty ports"
3061 Say Y (or M) here if you want to be able to use PPP over synchronous
3062 (HDLC) tty devices, such as the SyncLink adapter. These devices
3063 are often used for high-speed leased lines like T1/E1.
3065 To compile this driver as a module, choose M here.
3068 tristate "PPP Deflate compression"
3073 Support for the Deflate compression method for PPP, which uses the
3074 Deflate algorithm (the same algorithm that gzip uses) to compress
3075 each PPP packet before it is sent over the wire. The machine at the
3076 other end of the PPP link (usually your ISP) has to support the
3077 Deflate compression method as well for this to be useful. Even if
3078 they don't support it, it is safe to say Y here.
3080 To compile this driver as a module, choose M here.
3083 tristate "PPP BSD-Compress compression"
3086 Support for the BSD-Compress compression method for PPP, which uses
3087 the LZW compression method to compress each PPP packet before it is
3088 sent over the wire. The machine at the other end of the PPP link
3089 (usually your ISP) has to support the BSD-Compress compression
3090 method as well for this to be useful. Even if they don't support it,
3091 it is safe to say Y here.
3093 The PPP Deflate compression method ("PPP Deflate compression",
3094 above) is preferable to BSD-Compress, because it compresses better
3097 Note that the BSD compression code will always be compiled as a
3098 module; it is called bsd_comp and will show up in the directory
3099 modules once you have said "make modules". If unsure, say N.
3102 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3103 depends on PPP && EXPERIMENTAL
3109 Support for the MPPE Encryption protocol, as employed by the
3110 Microsoft Point-to-Point Tunneling Protocol.
3112 See http://pptpclient.sourceforge.net/ for information on
3113 configuring PPTP clients and servers to utilize this method.
3116 tristate "PPP over Ethernet (EXPERIMENTAL)"
3117 depends on EXPERIMENTAL && PPP
3119 Support for PPP over Ethernet.
3121 This driver requires the latest version of pppd from the CVS
3122 repository at cvs.samba.org. Alternatively, see the
3123 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3124 which contains instruction on how to use this driver (under
3125 the heading "Kernel mode PPPoE").
3128 tristate "PPP over ATM"
3129 depends on ATM && PPP
3131 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3132 This implementation does not yet comply with section 8 of RFC2364,
3133 which can lead to bad results if the ATM peer loses state and
3134 changes its encapsulation unilaterally.
3137 tristate "PPP over L2TP (EXPERIMENTAL)"
3138 depends on EXPERIMENTAL && PPP && INET
3140 Support for PPP-over-L2TP socket family. L2TP is a protocol
3141 used by ISPs and enterprises to tunnel PPP traffic over UDP
3142 tunnels. L2TP is replacing PPTP for VPN uses.
3144 This kernel component handles only L2TP data packets: a
3145 userland daemon handles L2TP the control protocol (tunnel
3146 and session setup). One such daemon is OpenL2TP
3147 (http://openl2tp.sourceforge.net/).
3150 tristate "SLIP (serial line) support"
3152 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3153 connect to your Internet service provider or to connect to some
3154 other local Unix box or if you want to configure your Linux box as a
3155 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3156 Internet Protocol) is a protocol used to send Internet traffic over
3157 serial connections such as telephone lines or null modem cables;
3158 nowadays, the protocol PPP is more commonly used for this same
3161 Normally, your access provider has to support SLIP in order for you
3162 to be able to use it, but there is now a SLIP emulator called SLiRP
3163 around (available from
3164 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3165 allows you to use SLIP over a regular dial up shell connection. If
3166 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3167 NET-3-HOWTO, available from
3168 <http://www.tldp.org/docs.html#howto>, explains how to
3169 configure SLIP. Note that you don't need this option if you just
3170 want to run term (term is a program which gives you almost full
3171 Internet connectivity if you have a regular dial up shell account on
3172 some Internet connected Unix computer. Read
3173 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3174 support will enlarge your kernel by about 4 KB. If unsure, say N.
3176 To compile this driver as a module, choose M here. The module
3177 will be called slip.
3179 config SLIP_COMPRESSED
3180 bool "CSLIP compressed headers"
3184 This protocol is faster than SLIP because it uses compression on the
3185 TCP/IP headers (not on the data itself), but it has to be supported
3186 on both ends. Ask your access provider if you are not sure and
3187 answer Y, just in case. You will still be able to use plain SLIP. If
3188 you plan to use SLiRP, the SLIP emulator (available from
3189 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3190 allows you to use SLIP over a regular dial up shell connection, you
3191 definitely want to say Y here. The NET-3-HOWTO, available from
3192 <http://www.tldp.org/docs.html#howto>, explains how to configure
3193 CSLIP. This won't enlarge your kernel.
3198 This option enables Van Jacobsen serial line header compression
3202 bool "Keepalive and linefill"
3205 Adds additional capabilities to the SLIP driver to support the
3206 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3209 config SLIP_MODE_SLIP6
3210 bool "Six bit SLIP encapsulation"
3213 Just occasionally you may need to run IP over hostile serial
3214 networks that don't pass all control characters or are only seven
3215 bit. Saying Y here adds an extra mode you can use with SLIP:
3216 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3217 the serial device. Naturally, this has to be supported at the other
3218 end of the link as well. It's good enough, for example, to run IP
3219 over the async ports of a Camtec JNT Pad. If unsure, say N.
3222 bool "Fibre Channel driver support"
3223 depends on SCSI && PCI
3225 Fibre Channel is a high speed serial protocol mainly used to connect
3226 large storage devices to the computer; it is compatible with and
3227 intended to replace SCSI.
3229 If you intend to use Fibre Channel, you need to have a Fibre channel
3230 adaptor card in your computer; say Y here and to the driver for your
3231 adaptor below. You also should have said Y to "SCSI support" and
3232 "SCSI generic support".
3235 tristate "Network console logging support (EXPERIMENTAL)"
3236 depends on EXPERIMENTAL
3238 If you want to log kernel messages over the network, enable this.
3239 See <file:Documentation/networking/netconsole.txt> for details.
3241 config NETCONSOLE_DYNAMIC
3242 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3243 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3246 This option enables the ability to dynamically reconfigure target
3247 parameters (interface, IP addresses, port numbers, MAC addresses)
3248 at runtime through a userspace interface exported using configfs.
3249 See <file:Documentation/networking/netconsole.txt> for details.
3255 bool "Netpoll traffic trapping"
3259 config NET_POLL_CONTROLLER
3263 tristate "Virtio network driver (EXPERIMENTAL)"
3264 depends on EXPERIMENTAL && VIRTIO
3266 This is the virtual network driver for virtio. It can be used with
3267 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3270 tristate "VMware VMXNET3 ethernet driver"
3271 depends on PCI && INET
3273 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3274 To compile this driver as a module, choose M here: the
3275 module will be called vmxnet3.