2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
97 This adds a specialized tap character device driver that is based
98 on the MAC-VLAN network interface, called macvtap. A macvtap device
99 can be added in the same way as a macvlan device, using 'type
100 macvlan', and then be accessed through the tap user space interface.
102 To compile this driver as a module, choose M here: the module
103 will be called macvtap.
106 tristate "EQL (serial line load balancing) support"
108 If you have two serial connections to some other computer (this
109 usually requires two modems and two telephone lines) and you use
110 SLIP (the protocol for sending Internet traffic over telephone
111 lines) or PPP (a better SLIP) on them, you can make them behave like
112 one double speed connection using this driver. Naturally, this has
113 to be supported at the other end as well, either with a similar EQL
114 Linux driver or with a Livingston Portmaster 2e.
116 Say Y if you want this and read
117 <file:Documentation/networking/eql.txt>. You may also want to read
118 section 6.2 of the NET-3-HOWTO, available from
119 <http://www.tldp.org/docs.html#howto>.
121 To compile this driver as a module, choose M here: the module
122 will be called eql. If unsure, say N.
125 tristate "Universal TUN/TAP device driver support"
128 TUN/TAP provides packet reception and transmission for user space
129 programs. It can be viewed as a simple Point-to-Point or Ethernet
130 device, which instead of receiving packets from a physical media,
131 receives them from user space program and instead of sending packets
132 via physical media writes them to the user space program.
134 When a program opens /dev/net/tun, driver creates and registers
135 corresponding net device tunX or tapX. After a program closed above
136 devices, driver will automatically delete tunXX or tapXX device and
137 all routes corresponding to it.
139 Please read <file:Documentation/networking/tuntap.txt> for more
142 To compile this driver as a module, choose M here: the module
145 If you don't know what to use this for, you don't need it.
148 tristate "Virtual ethernet pair device"
150 This device is a local ethernet tunnel. Devices are created in pairs.
151 When one end receives the packet it appears on its pair and vice
155 tristate "General Instruments Surfboard 1000"
158 This is a driver for the General Instrument (also known as
159 NextLevel) SURFboard 1000 internal
160 cable modem. This is an ISA card which is used by a number of cable
161 TV companies to provide cable modem access. It's a one-way
162 downstream-only cable modem, meaning that your upstream net link is
163 provided by your regular phone modem.
165 At present this driver only compiles as a module, so say M here if
166 you have this card. The module will be called sb1000. Then read
167 <file:Documentation/networking/README.sb1000> for information on how
168 to use this module, as it needs special ppp scripts for establishing
169 a connection. Further documentation and the necessary scripts can be
172 <http://www.jacksonville.net/~fventuri/>
173 <http://home.adelphia.net/~siglercm/sb1000.html>
174 <http://linuxpower.cx/~cable/>
176 If you don't have this card, of course say N.
178 source "drivers/net/arcnet/Kconfig"
180 source "drivers/net/phy/Kconfig"
186 menuconfig NET_ETHERNET
187 bool "Ethernet (10 or 100Mbit)"
190 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
191 type of Local Area Network (LAN) in universities and companies.
193 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
194 coaxial cable, linking computers in a chain), 10BASE-T or twisted
195 pair (10 Mbps over twisted pair cable, linking computers to central
196 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
197 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
198 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
199 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
200 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
201 Ethernet (1 Gbps over optical fiber or short copper links).
203 If your Linux machine will be connected to an Ethernet and you have
204 an Ethernet network interface card (NIC) installed in your computer,
205 say Y here and read the Ethernet-HOWTO, available from
206 <http://www.tldp.org/docs.html#howto>. You will then also have
207 to say Y to the driver for your particular NIC.
209 Note that the answer to this question won't directly affect the
210 kernel: saying N will just cause the configurator to skip all
211 the questions about Ethernet network cards. If unsure, say N.
216 tristate "Generic Media Independent Interface device support"
218 Most ethernet controllers have MII transceiver either as an external
219 or internal device. It is safe to say Y or M here even if your
220 ethernet card lack MII.
223 tristate "Atmel MACB support"
224 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9
227 The Atmel MACB ethernet interface is found on many AT32 and AT91
228 parts. Say Y to include support for the MACB chip.
230 To compile this driver as a module, choose M here: the module
233 source "drivers/net/arm/Kconfig"
236 tristate "ASIX AX88796 NE2000 clone support"
237 depends on ARM || MIPS || SUPERH
241 AX88796 driver, using platform bus to provide
242 chip detection and resources
245 bool "ASIX AX88796 external 93CX6 eeprom support"
249 Select this if your platform comes with an external 93CX6 eeprom.
252 tristate "MACE (Power Mac ethernet) support"
253 depends on PPC_PMAC && PPC32
256 Power Macintoshes and clones with Ethernet built-in on the
257 motherboard will usually use a MACE (Medium Access Control for
258 Ethernet) interface. Say Y to include support for the MACE chip.
260 To compile this driver as a module, choose M here: the module
263 config MACE_AAUI_PORT
264 bool "Use AAUI port instead of TP by default"
267 Some Apple machines (notably the Apple Network Server) which use the
268 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
269 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
270 Y here if you have such a machine. If unsure, say N.
271 The driver will default to AAUI on ANS anyway, and if you use it as
272 a module, you can provide the port_aaui=0|1 to force the driver.
275 tristate "BMAC (G3 ethernet) support"
276 depends on PPC_PMAC && PPC32
279 Say Y for support of BMAC Ethernet interfaces. These are used on G3
282 To compile this driver as a module, choose M here: the module
286 tristate "Ariadne support"
289 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
292 To compile this driver as a module, choose M here: the module
293 will be called ariadne.
296 tristate "A2065 support"
300 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
303 To compile this driver as a module, choose M here: the module
304 will be called a2065.
307 tristate "Hydra support"
311 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
313 To compile this driver as a module, choose M here: the module
314 will be called hydra.
317 tristate "Zorro NS8390-based Ethernet support"
321 This driver is for Zorro Ethernet cards using an NS8390-compatible
322 chipset, like the Village Tronic Ariadne II and the Individual
323 Computers X-Surf Ethernet cards. If you have such a card, say Y.
326 To compile this driver as a module, choose M here: the module
327 will be called zorro8390.
330 tristate "PCMCIA NE2000 support"
331 depends on AMIGA_PCMCIA
334 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
337 To compile this driver as a module, choose M here: the module
341 bool "Macintosh NS 8390 based ethernet cards"
345 If you want to include a driver to support Nubus or LC-PDS
346 Ethernet cards using an NS8390 chipset or its equivalent, say Y
347 and read the Ethernet-HOWTO, available from
348 <http://www.tldp.org/docs.html#howto>.
351 tristate "Macintosh CS89x0 based ethernet cards"
354 Support for CS89x0 chipset based Ethernet cards. If you have a
355 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
356 read the Ethernet-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>.
359 To compile this driver as a module, choose M here. This module will
363 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
366 Support for NatSemi SONIC based Ethernet devices. This includes
367 the onboard Ethernet in many Quadras as well as some LC-PDS,
368 a few Nubus and all known Comm Slot Ethernet cards. If you have
369 one of these say Y and read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
372 To compile this driver as a module, choose M here. This module will
376 bool "Macintosh (AV) onboard MACE ethernet"
380 Support for the onboard AMD 79C940 MACE Ethernet controller used in
381 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
382 say Y and read the Ethernet-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>.
386 tristate "MVME147 (Lance) Ethernet support"
390 Support for the on-board Ethernet interface on the Motorola MVME147
391 single-board computer. Say Y here to include the
392 driver for this chip in your kernel.
393 To compile this driver as a module, choose M here.
396 tristate "MVME16x Ethernet support"
399 This is the driver for the Ethernet interface on the Motorola
400 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
401 driver for this chip in your kernel.
402 To compile this driver as a module, choose M here.
405 tristate "BVME6000 Ethernet support"
408 This is the driver for the Ethernet interface on BVME4000 and
409 BVME6000 VME boards. Say Y here to include the driver for this chip
411 To compile this driver as a module, choose M here.
414 tristate "Atari Lance support"
417 Say Y to include support for several Atari Ethernet adapters based
418 on the AMD Lance chipset: RieblCard (with or without battery), or
419 PAMCard VME (also the version by Rhotron, with different addresses).
422 tristate "Sun3/Sun3x on-board LANCE support"
423 depends on SUN3 || SUN3X
425 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
426 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
427 here to compile in the Linux driver for this and enable Ethernet.
428 General Linux information on the Sun 3 and 3x series (now
430 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
432 If you're not building a kernel for a Sun 3, say N.
435 bool "Sun3 on-board Intel 82586 support"
438 This driver enables support for the on-board Intel 82586 based
439 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
440 that this driver does not support 82586-based adapters on additional
444 bool "HP on-board LANCE support"
448 If you want to use the builtin "LANCE" Ethernet controller on an
449 HP300 machine, say Y here.
452 tristate "Lasi ethernet"
455 Say Y here to support the builtin Intel 82596 ethernet controller
456 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
459 tristate "SNI RM ethernet"
460 depends on NET_ETHERNET && SNI_RM
462 Say Y here to support the on-board Intel 82596 ethernet controller
463 built into SNI RM machines.
466 tristate "Korina (IDT RC32434) Ethernet support"
467 depends on NET_ETHERNET && MIKROTIK_RB532
469 If you have a Mikrotik RouterBoard 500 or IDT RC32434
470 based system say Y. Otherwise say N.
472 config MIPS_JAZZ_SONIC
473 tristate "MIPS JAZZ onboard SONIC Ethernet support"
476 This is the driver for the onboard card of MIPS Magnum 4000,
477 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
479 config XTENSA_XT2000_SONIC
480 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
481 depends on XTENSA_PLATFORM_XT2000
483 This is the driver for the onboard card of the Xtensa XT2000 board.
485 config MIPS_AU1X00_ENET
486 tristate "MIPS AU1000 Ethernet support"
487 depends on SOC_AU1X00
491 If you have an Alchemy Semi AU1X00 based system
492 say Y. Otherwise, say N.
495 bool "SGI IOC3 Ethernet"
496 depends on PCI && SGI_IP27
500 If you have a network (Ethernet) card of this type, say Y and read
501 the Ethernet-HOWTO, available from
502 <http://www.tldp.org/docs.html#howto>.
505 tristate "MIPS simulator Network device"
508 The MIPSNET device is a simple Ethernet network device which is
509 emulated by the MIPS Simulator.
510 If you are not using a MIPSsim or are unsure, say N.
512 config SGI_O2MACE_ETH
513 tristate "SGI O2 MACE Fast Ethernet support"
514 depends on SGI_IP32=y
517 tristate "National DP83902AV support"
521 Support for cards based on the National Semiconductor DP83902AV
522 ST-NIC Serial Network Interface Controller for Twisted Pair. This
523 is a 10Mbit/sec Ethernet controller. Product overview and specs at
524 <http://www.national.com/pf/DP/DP83902A.html>.
529 tristate "Renesas SuperH Ethernet support"
530 depends on SUPERH && \
531 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
532 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
539 Renesas SuperH Ethernet device driver.
540 This driver support SH7710, SH7712, SH7763, SH7619, and SH7724.
543 tristate "Sun LANCE support"
547 This driver supports the "le" interface present on all 32-bit Sparc
548 systems, on some older Ultra systems and as an Sbus option. These
549 cards are based on the AMD Lance chipset, which is better known
550 via the NE2100 cards.
552 To compile this driver as a module, choose M here: the module
553 will be called sunlance.
556 tristate "Sun Happy Meal 10/100baseT support"
557 depends on SBUS || PCI
560 This driver supports the "hme" interface present on most Ultra
561 systems and as an option on older Sbus systems. This driver supports
562 both PCI and Sbus devices. This driver also supports the "qfe" quad
563 100baseT device available in both PCI and Sbus configurations.
565 To compile this driver as a module, choose M here: the module
566 will be called sunhme.
569 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
570 depends on SBUS && EXPERIMENTAL
573 This driver supports the "be" interface available as an Sbus option.
574 This is Sun's older 100baseT Ethernet device.
576 To compile this driver as a module, choose M here: the module
577 will be called sunbmac.
580 tristate "Sun QuadEthernet support"
584 This driver supports the "qe" 10baseT Ethernet device, available as
585 an Sbus option. Note that this is not the same as Quad FastEthernet
586 "qfe" which is supported by the Happy Meal driver instead.
588 To compile this driver as a module, choose M here: the module
589 will be called sunqe.
592 tristate "Sun GEM support"
596 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
597 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
600 tristate "Sun Cassini support"
604 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
605 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
608 tristate "Sun Virtual Network support"
611 Support for virtual network devices under Sun Logical Domains.
613 config NET_VENDOR_3COM
615 depends on ISA || EISA || MCA || PCI
617 If you have a network (Ethernet) card belonging to this class, say Y
618 and read the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 Note that the answer to this question doesn't directly affect the
622 kernel: saying N will just cause the configurator to skip all
623 the questions about 3COM cards. If you say Y, you will be asked for
624 your specific card in the following questions.
627 tristate "3c501 \"EtherLink\" support"
628 depends on NET_VENDOR_3COM && ISA
630 If you have a network (Ethernet) card of this type, say Y and read
631 the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
633 new card, since the 3c501 is slow, broken, and obsolete: you will
634 have problems. Some people suggest to ping ("man ping") a nearby
635 machine every minute ("man cron") when using this card.
637 To compile this driver as a module, choose M here. The module
638 will be called 3c501.
641 tristate "3c503 \"EtherLink II\" support"
642 depends on NET_VENDOR_3COM && ISA
645 If you have a network (Ethernet) card of this type, say Y and read
646 the Ethernet-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here. The module
650 will be called 3c503.
653 tristate "3c505 \"EtherLink Plus\" support"
654 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
656 Information about this network (Ethernet) card can be found in
657 <file:Documentation/networking/3c505.txt>. If you have a card of
658 this type, say Y and read the Ethernet-HOWTO, available from
659 <http://www.tldp.org/docs.html#howto>.
661 To compile this driver as a module, choose M here. The module
662 will be called 3c505.
665 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
666 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
668 If you have a network (Ethernet) card of this type, say Y and read
669 the Ethernet-HOWTO, available from
670 <http://www.tldp.org/docs.html#howto>.
672 To compile this driver as a module, choose M here. The module
673 will be called 3c507.
676 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
677 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
679 If you have a network (Ethernet) card belonging to the 3Com
680 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
681 from <http://www.tldp.org/docs.html#howto>.
683 If your card is not working you may need to use the DOS
684 setup disk to disable Plug & Play mode, and to select the default
687 To compile this driver as a module, choose M here. The module
688 will be called 3c509.
691 tristate "3c515 ISA \"Fast EtherLink\""
692 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
694 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
695 network card, say Y and read the Ethernet-HOWTO, available from
696 <http://www.tldp.org/docs.html#howto>.
698 To compile this driver as a module, choose M here. The module
699 will be called 3c515.
702 tristate "3c523 \"EtherLink/MC\" support"
703 depends on NET_VENDOR_3COM && MCA_LEGACY
705 If you have a network (Ethernet) card of this type, say Y and read
706 the Ethernet-HOWTO, available from
707 <http://www.tldp.org/docs.html#howto>.
709 To compile this driver as a module, choose M here. The module
710 will be called 3c523.
713 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
714 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
716 If you have a network (Ethernet) card of this type, say Y and read
717 the Ethernet-HOWTO, available from
718 <http://www.tldp.org/docs.html#howto>.
720 To compile this driver as a module, choose M here. The module
721 will be called 3c527.
724 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
725 depends on NET_VENDOR_3COM && (PCI || EISA)
728 This option enables driver support for a large number of 10Mbps and
729 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
731 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
732 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
733 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
734 "Tornado" (3c905) PCI
735 "Hurricane" (3c555/3cSOHO) PCI
737 If you have such a card, say Y and read the Ethernet-HOWTO,
738 available from <http://www.tldp.org/docs.html#howto>. More
739 specific information is in
740 <file:Documentation/networking/vortex.txt> and in the comments at
741 the beginning of <file:drivers/net/3c59x.c>.
743 To compile this support as a module, choose M here.
746 tristate "3cr990 series \"Typhoon\" support"
747 depends on NET_VENDOR_3COM && PCI
750 This option enables driver support for the 3cr990 series of cards:
752 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
753 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
754 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
756 If you have a network (Ethernet) card of this type, say Y and read
757 the Ethernet-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>.
760 To compile this driver as a module, choose M here. The module
761 will be called typhoon.
764 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
765 depends on ISA && ISA_DMA_API
767 If you have a network (Ethernet) card of this type, say Y and read
768 the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
772 To compile this driver as a module, choose M here: the module
773 will be called lance. This is recommended.
775 config NET_VENDOR_SMC
776 bool "Western Digital/SMC cards"
777 depends on ISA || MCA || EISA || MAC
779 If you have a network (Ethernet) card belonging to this class, say Y
780 and read the Ethernet-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 Note that the answer to this question doesn't directly affect the
784 kernel: saying N will just cause the configurator to skip all
785 the questions about Western Digital cards. If you say Y, you will be
786 asked for your specific card in the following questions.
789 tristate "WD80*3 support"
790 depends on NET_VENDOR_SMC && ISA
793 If you have a network (Ethernet) card of this type, say Y and read
794 the Ethernet-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 To compile this driver as a module, choose M here. The module
801 tristate "SMC Ultra MCA support"
802 depends on NET_VENDOR_SMC && MCA
805 If you have a network (Ethernet) card of this type and are running
806 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
807 available from <http://www.tldp.org/docs.html#howto>.
809 To compile this driver as a module, choose M here. The module
810 will be called smc-mca.
813 tristate "SMC Ultra support"
814 depends on NET_VENDOR_SMC && ISA
817 If you have a network (Ethernet) card of this type, say Y and read
818 the Ethernet-HOWTO, available from
819 <http://www.tldp.org/docs.html#howto>.
821 Important: There have been many reports that, with some motherboards
822 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
823 such as some BusLogic models) causes corruption problems with many
824 operating systems. The Linux smc-ultra driver has a work-around for
825 this but keep it in mind if you have such a SCSI card and have
828 To compile this driver as a module, choose M here. The module
829 will be called smc-ultra.
832 tristate "SMC Ultra32 EISA support"
833 depends on NET_VENDOR_SMC && EISA
836 If you have a network (Ethernet) card of this type, say Y and read
837 the Ethernet-HOWTO, available from
838 <http://www.tldp.org/docs.html#howto>.
840 To compile this driver as a module, choose M here. The module
841 will be called smc-ultra32.
844 tristate "Blackfin on-chip MAC support"
845 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
849 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
851 This is the driver for Blackfin on-chip mac device. Say Y if you want it
852 compiled into the kernel. This driver is also available as a module
853 ( = code which can be inserted in and removed from the running kernel
854 whenever you want). The module will be called bfin_mac.
856 config BFIN_MAC_USE_L1
857 bool "Use L1 memory for rx/tx packets"
858 depends on BFIN_MAC && (BF527 || BF537)
861 To get maximum network performance, you should use L1 memory as rx/tx buffers.
862 Say N here if you want to reserve L1 memory for other uses.
864 config BFIN_TX_DESC_NUM
865 int "Number of transmit buffer packets"
867 range 6 10 if BFIN_MAC_USE_L1
871 Set the number of buffer packets used in driver.
873 config BFIN_RX_DESC_NUM
874 int "Number of receive buffer packets"
876 range 20 100 if BFIN_MAC_USE_L1
880 Set the number of buffer packets used in driver.
883 bool "RMII PHY Interface"
885 default y if BFIN527_EZKIT
886 default n if BFIN537_STAMP
888 Use Reduced PHY MII Interface
890 config BFIN_MAC_USE_HWSTAMP
891 bool "Use IEEE 1588 hwstamp"
892 depends on BFIN_MAC && BF518
895 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
898 tristate "SMC 9194 support"
899 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
902 This is support for the SMC9xxx based Ethernet cards. Choose this
903 option if you have a DELL laptop with the docking station, or
904 another SMC9192/9194 based chipset. Say Y if you want it compiled
905 into the kernel, and read the file
906 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
907 available from <http://www.tldp.org/docs.html#howto>.
909 To compile this driver as a module, choose M here. The module
910 will be called smc9194.
913 tristate "SMC 91C9x/91C1xxx support"
916 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
917 MIPS || BLACKFIN || MN10300 || COLDFIRE
919 This is a driver for SMC's 91x series of Ethernet chipsets,
920 including the SMC91C94 and the SMC91C111. Say Y if you want it
921 compiled into the kernel, and read the file
922 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
923 available from <http://www.linuxdoc.org/docs.html#howto>.
925 This driver is also available as a module ( = code which can be
926 inserted in and removed from the running kernel whenever you want).
927 The module will be called smc91x. If you want to compile it as a
928 module, say M here and read <file:Documentation/kbuild/modules.txt>.
931 tristate "NetX Ethernet support"
935 This is support for the Hilscher netX builtin Ethernet ports
937 To compile this driver as a module, choose M here. The module
938 will be called netx-eth.
940 config TI_DAVINCI_EMAC
941 tristate "TI DaVinci EMAC Support"
942 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
945 This driver supports TI's DaVinci Ethernet .
947 To compile this driver as a module, choose M here: the module
948 will be called davinci_emac_driver. This is recommended.
951 tristate "DM9000 support"
952 depends on ARM || BLACKFIN || MIPS
956 Support for DM9000 chipset.
958 To compile this driver as a module, choose M here. The module
959 will be called dm9000.
961 config DM9000_DEBUGLEVEL
962 int "DM9000 maximum debug level"
966 The maximum level of debugging code compiled into the DM9000
969 config DM9000_FORCE_SIMPLE_PHY_POLL
970 bool "Force simple NSR based PHY polling"
973 This configuration forces the DM9000 to use the NSR's LinkStatus
974 bit to determine if the link is up or down instead of the more
975 costly MII PHY reads. Note, this will not work if the chip is
976 operating with an external PHY.
979 tristate "ENC28J60 support"
980 depends on EXPERIMENTAL && SPI && NET_ETHERNET
983 Support for the Microchip EN28J60 ethernet chip.
985 To compile this driver as a module, choose M here. The module will be
988 config ENC28J60_WRITEVERIFY
989 bool "Enable write verify"
992 Enable the verify after the buffer write useful for debugging purpose.
996 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
997 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1003 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1006 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1011 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1014 tristate "SMSC LAN911[5678] support"
1017 depends on ARM || SUPERH
1019 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1020 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1021 Say Y if you want it compiled into the kernel,
1022 and read the Ethernet-HOWTO, available from
1023 <http://www.linuxdoc.org/docs.html#howto>.
1025 This driver is also available as a module. The module will be
1026 called smc911x. If you want to compile it as a module, say M
1027 here and read <file:Documentation/kbuild/modules.txt>
1030 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1031 depends on ARM || SUPERH || BLACKFIN || MIPS
1036 Say Y here if you want support for SMSC LAN911x and LAN921x families
1037 of ethernet controllers.
1039 To compile this driver as a module, choose M here and read
1040 <file:Documentation/networking/net-modules.txt>. The module
1041 will be called smsc911x.
1043 config NET_VENDOR_RACAL
1044 bool "Racal-Interlan (Micom) NI cards"
1047 If you have a network (Ethernet) card belonging to this class, such
1048 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1049 available from <http://www.tldp.org/docs.html#howto>.
1051 Note that the answer to this question doesn't directly affect the
1052 kernel: saying N will just cause the configurator to skip all
1053 the questions about NI cards. If you say Y, you will be asked for
1054 your specific card in the following questions.
1057 tristate "NI5010 support (EXPERIMENTAL)"
1058 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1060 If you have a network (Ethernet) card of this type, say Y and read
1061 the Ethernet-HOWTO, available from
1062 <http://www.tldp.org/docs.html#howto>. Note that this is still
1065 To compile this driver as a module, choose M here. The module
1066 will be called ni5010.
1069 tristate "NI5210 support"
1070 depends on NET_VENDOR_RACAL && ISA
1072 If you have a network (Ethernet) card of this type, say Y and read
1073 the Ethernet-HOWTO, available from
1074 <http://www.tldp.org/docs.html#howto>.
1076 To compile this driver as a module, choose M here. The module
1077 will be called ni52.
1080 tristate "NI6510 support"
1081 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1083 If you have a network (Ethernet) card of this type, say Y and read
1084 the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1087 To compile this driver as a module, choose M here. The module
1088 will be called ni65.
1091 tristate "Dave ethernet support (DNET)"
1092 depends on NET_ETHERNET && HAS_IOMEM
1095 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1096 Say Y to include support for the DNET chip.
1098 To compile this driver as a module, choose M here: the module
1099 will be called dnet.
1101 source "drivers/net/tulip/Kconfig"
1104 tristate "AT1700/1720 support (EXPERIMENTAL)"
1105 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1108 If you have a network (Ethernet) card of this type, say Y and read
1109 the Ethernet-HOWTO, available from
1110 <http://www.tldp.org/docs.html#howto>.
1112 To compile this driver as a module, choose M here. The module
1113 will be called at1700.
1116 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1117 depends on ISA || EISA || MCA
1120 If you have a network (Ethernet) card of this type, say Y and read
1121 the Ethernet-HOWTO, available from
1122 <http://www.tldp.org/docs.html#howto> as well as
1123 <file:drivers/net/depca.c>.
1125 To compile this driver as a module, choose M here. The module
1126 will be called depca.
1129 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1130 depends on ISA || EISA || PCI
1132 If you have a network (Ethernet) card of this type, say Y and read
1133 the Ethernet-HOWTO, available from
1134 <http://www.tldp.org/docs.html#howto>.
1136 To compile this driver as a module, choose M here. The module
1137 will be called hp100.
1140 bool "Other ISA cards"
1143 If your network (Ethernet) card hasn't been mentioned yet and its
1144 bus system (that's the way the cards talks to the other components
1145 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1146 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1147 available from <http://www.tldp.org/docs.html#howto>.
1151 Note that the answer to this question doesn't directly affect the
1152 kernel: saying N will just cause the configurator to skip all
1153 the remaining ISA network card questions. If you say Y, you will be
1154 asked for your specific card in the following questions.
1157 tristate "Cabletron E21xx support"
1161 If you have a network (Ethernet) card of this type, say Y and read
1162 the Ethernet-HOWTO, available from
1163 <http://www.tldp.org/docs.html#howto>.
1165 To compile this driver as a module, choose M here. The module
1166 will be called e2100.
1169 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1173 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1174 cards. If this is for you, say Y and read
1175 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1176 well as the Ethernet-HOWTO, available from
1177 <http://www.tldp.org/docs.html#howto>.
1179 To compile this driver as a module, choose M here. The module
1180 will be called ewrk3.
1183 tristate "EtherExpress 16 support"
1186 If you have an EtherExpress16 network (Ethernet) card, say Y and
1187 read the Ethernet-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1189 EtherExpress16 card used to be regarded as a very poor choice
1190 because the driver was very unreliable. We now have a new driver
1191 that should do better.
1193 To compile this driver as a module, choose M here. The module
1194 will be called eexpress.
1197 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1200 If you have a network (Ethernet) card of this type, say Y. This
1201 driver supports Intel i82595{FX,TX} based boards. Note however
1202 that the EtherExpress PRO/100 Ethernet card has its own separate
1203 driver. Please read the Ethernet-HOWTO, available from
1204 <http://www.tldp.org/docs.html#howto>.
1206 To compile this driver as a module, choose M here. The module
1207 will be called eepro.
1210 tristate "HP PCLAN+ (27247B and 27252A) support"
1214 If you have a network (Ethernet) card of this type, say Y and read
1215 the Ethernet-HOWTO, available from
1216 <http://www.tldp.org/docs.html#howto>.
1218 To compile this driver as a module, choose M here. The module
1219 will be called hp-plus.
1222 tristate "HP PCLAN (27245 and other 27xxx series) support"
1226 If you have a network (Ethernet) card of this type, say Y and read
1227 the Ethernet-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here. The module
1234 tristate "LP486E on board Ethernet"
1237 Say Y here to support the 82596-based on-board Ethernet controller
1238 for the Panther motherboard, which is one of the two shipped in the
1239 Intel Professional Workstation.
1242 tristate "ICL EtherTeam 16i/32 support"
1245 If you have a network (Ethernet) card of this type, say Y and read
1246 the Ethernet-HOWTO, available from
1247 <http://www.tldp.org/docs.html#howto>.
1249 To compile this driver as a module, choose M here. The module
1250 will be called eth16i.
1253 tristate "NE2000/NE1000 support"
1254 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1257 If you have a network (Ethernet) card of this type, say Y and read
1258 the Ethernet-HOWTO, available from
1259 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1260 without a specific driver are compatible with NE2000.
1262 If you have a PCI NE2000 card however, say N here and Y to "PCI
1263 NE2000 and clone support" under "EISA, VLB, PCI and on board
1264 controllers" below. If you have a NE2000 card and are running on
1265 an MCA system (a bus system used on some IBM PS/2 computers and
1266 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1269 To compile this driver as a module, choose M here. The module
1273 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1274 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1276 The Zenith Z-Note notebook computer has a built-in network
1277 (Ethernet) card, and this is the Linux driver for it. Note that the
1278 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1279 by this driver. Read the Ethernet-HOWTO, available from
1280 <http://www.tldp.org/docs.html#howto>.
1283 tristate "SEEQ8005 support (EXPERIMENTAL)"
1284 depends on NET_ISA && EXPERIMENTAL
1286 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1287 is for you, read the Ethernet-HOWTO, available from
1288 <http://www.tldp.org/docs.html#howto>.
1290 To compile this driver as a module, choose M here. The module
1291 will be called seeq8005.
1294 tristate "NE/2 (ne2000 MCA version) support"
1295 depends on MCA_LEGACY
1298 If you have a network (Ethernet) card of this type, say Y and read
1299 the Ethernet-HOWTO, available from
1300 <http://www.tldp.org/docs.html#howto>.
1302 To compile this driver as a module, choose M here. The module
1306 tristate "IBM LAN Adapter/A support"
1309 This is a Micro Channel Ethernet adapter. You need to set
1310 CONFIG_MCA to use this driver. It is both available as an in-kernel
1311 driver and as a module.
1313 To compile this driver as a module, choose M here. The only
1314 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1315 will both support 16K and 32K memory windows, however a 32K window
1316 gives a better security against packet losses. Usage of multiple
1317 boards with this driver should be possible, but has not been tested
1318 up to now due to lack of hardware.
1321 tristate "IBM LAN Virtual Ethernet support"
1322 depends on PPC_PSERIES
1324 This driver supports virtual ethernet adapters on newer IBM iSeries
1325 and pSeries systems.
1327 To compile this driver as a module, choose M here. The module will
1330 source "drivers/net/ibm_newemac/Kconfig"
1333 bool "EISA, VLB, PCI and on board controllers"
1334 depends on ISA || EISA || PCI
1336 This is another class of network cards which attach directly to the
1337 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1338 available from <http://www.tldp.org/docs.html#howto>.
1340 Note that the answer to this question doesn't directly affect the
1341 kernel: saying N will just cause the configurator to skip all
1342 the questions about this class of network cards. If you say Y, you
1343 will be asked for your specific card in the following questions. If
1344 you are unsure, say Y.
1347 tristate "AMD PCnet32 PCI support"
1348 depends on NET_PCI && PCI
1352 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1353 answer Y here and read the Ethernet-HOWTO, available from
1354 <http://www.tldp.org/docs.html#howto>.
1356 To compile this driver as a module, choose M here. The module
1357 will be called pcnet32.
1360 tristate "AMD 8111 (new PCI lance) support"
1361 depends on NET_PCI && PCI
1365 If you have an AMD 8111-based PCI lance ethernet card,
1366 answer Y here and read the Ethernet-HOWTO, available from
1367 <http://www.tldp.org/docs.html#howto>.
1369 To compile this driver as a module, choose M here. The module
1370 will be called amd8111e.
1372 config ADAPTEC_STARFIRE
1373 tristate "Adaptec Starfire/DuraLAN support"
1374 depends on NET_PCI && PCI
1378 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1379 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1380 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1383 To compile this driver as a module, choose M here: the module
1384 will be called starfire. This is recommended.
1387 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1388 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1391 If you have a network (Ethernet) card of this type, say Y and read
1392 the Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto>.
1395 To compile this driver as a module, choose M here. The module
1396 will be called ac3200.
1399 tristate "Micrel KSZ8841/2 PCI"
1400 depends on NET_PCI && PCI
1404 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1406 To compile this driver as a module, choose M here. The module
1407 will be called ksz884x.
1410 tristate "Apricot Xen-II on board Ethernet"
1411 depends on NET_PCI && ISA
1413 If you have a network (Ethernet) controller of this type, say Y and
1414 read the Ethernet-HOWTO, available from
1415 <http://www.tldp.org/docs.html#howto>.
1417 To compile this driver as a module, choose M here. The module
1418 will be called apricot.
1421 tristate "Broadcom 440x/47xx ethernet support"
1422 depends on SSB_POSSIBLE && HAS_DMA
1426 If you have a network (Ethernet) controller of this type, say Y
1427 or M and read the Ethernet-HOWTO, available from
1428 <http://www.tldp.org/docs.html#howto>.
1430 To compile this driver as a module, choose M here. The module
1433 # Auto-select SSB PCI-HOST support, if possible
1434 config B44_PCI_AUTOSELECT
1436 depends on B44 && SSB_PCIHOST_POSSIBLE
1440 # Auto-select SSB PCICORE driver, if possible
1441 config B44_PCICORE_AUTOSELECT
1443 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1444 select SSB_DRIVER_PCICORE
1449 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1453 tristate "nForce Ethernet support"
1454 depends on NET_PCI && PCI
1456 If you have a network (Ethernet) controller of this type, say Y and
1457 read the Ethernet-HOWTO, available from
1458 <http://www.tldp.org/docs.html#howto>.
1460 To compile this driver as a module, choose M here. The module
1461 will be called forcedeth.
1464 tristate "CS89x0 support"
1465 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1466 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1468 Support for CS89x0 chipset based Ethernet cards. If you have a
1469 network (Ethernet) card of this type, say Y and read the
1470 Ethernet-HOWTO, available from
1471 <http://www.tldp.org/docs.html#howto> as well as
1472 <file:Documentation/networking/cs89x0.txt>.
1474 To compile this driver as a module, choose M here. The module
1475 will be called cs89x0.
1477 config CS89x0_NONISA_IRQ
1479 depends on CS89x0 != n
1480 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1483 tristate "TOSHIBA TC35815 Ethernet support"
1484 depends on NET_PCI && PCI && MIPS
1488 tristate "Intel(R) PRO/100+ support"
1489 depends on NET_PCI && PCI
1492 This driver supports Intel(R) PRO/100 family of adapters.
1493 To verify that your adapter is supported, find the board ID number
1494 on the adapter. Look for a label that has a barcode and a number
1495 in the format 123456-001 (six digits hyphen three digits).
1497 Use the above information and the Adapter & Driver ID Guide at:
1499 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1501 to identify the adapter.
1503 For the latest Intel PRO/100 network driver for Linux, see:
1505 <http://appsr.intel.com/scripts-df/support_intel.asp>
1507 More specific information on configuring the driver is in
1508 <file:Documentation/networking/e100.txt>.
1510 To compile this driver as a module, choose M here. The module
1511 will be called e100.
1514 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1515 depends on NET_PCI && EISA && EXPERIMENTAL
1518 If you have a network (Ethernet) card of this type, say Y and read
1519 the Ethernet-HOWTO, available from
1520 <http://www.tldp.org/docs.html#howto>.
1522 To compile this driver as a module, choose M here. The module
1523 will be called lne390.
1526 tristate "Myson MTD-8xx PCI Ethernet support"
1527 depends on NET_PCI && PCI
1531 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1532 cards. Specifications and data at
1533 <http://www.myson.com.hk/mtd/datasheet/>.
1536 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1537 depends on NET_PCI && PCI
1540 This driver is for the National Semiconductor DP83810 series,
1541 which is used in cards from PureData, NetGear, Linksys
1542 and others, including the 83815 chip.
1543 More specific information and updates are available from
1544 <http://www.scyld.com/network/natsemi.html>.
1547 tristate "PCI NE2000 and clones support (see help)"
1548 depends on NET_PCI && PCI
1551 This driver is for NE2000 compatible PCI cards. It will not work
1552 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1553 support" below). If you have a PCI NE2000 network (Ethernet) card,
1554 say Y and read the Ethernet-HOWTO, available from
1555 <http://www.tldp.org/docs.html#howto>.
1557 This driver also works for the following NE2000 clone cards:
1558 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1559 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1560 Holtek HT80232 Holtek HT80229
1562 To compile this driver as a module, choose M here. The module
1563 will be called ne2k-pci.
1566 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1567 depends on NET_PCI && EISA && EXPERIMENTAL
1570 If you have a network (Ethernet) card of this type, say Y and read
1571 the Ethernet-HOWTO, available from
1572 <http://www.tldp.org/docs.html#howto>. Note that this driver
1573 will NOT WORK for NE3200 cards as they are completely different.
1575 To compile this driver as a module, choose M here. The module
1576 will be called ne3210.
1579 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1580 depends on NET_PCI && EISA && EXPERIMENTAL
1583 If you have a network (Ethernet) card of this type, say Y and read
1584 the Ethernet-HOWTO, available from
1585 <http://www.tldp.org/docs.html#howto>.
1587 To compile this driver as a module, choose M here. The module
1588 will be called es3210.
1591 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1592 depends on NET_PCI && PCI && EXPERIMENTAL
1596 This is a driver for the Fast Ethernet PCI network cards based on
1597 the RTL8139C+ chips. If you have one of those, say Y and read
1598 the Ethernet-HOWTO, available from
1599 <http://www.tldp.org/docs.html#howto>.
1601 To compile this driver as a module, choose M here: the module
1602 will be called 8139cp. This is recommended.
1605 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1606 depends on NET_PCI && PCI
1610 This is a driver for the Fast Ethernet PCI network cards based on
1611 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1612 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1614 To compile this driver as a module, choose M here: the module
1615 will be called 8139too. This is recommended.
1618 bool "Use PIO instead of MMIO"
1622 This instructs the driver to use programmed I/O ports (PIO) instead
1623 of PCI shared memory (MMIO). This can possibly solve some problems
1624 in case your mainboard has memory consistency issues. If unsure,
1627 config 8139TOO_TUNE_TWISTER
1628 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1631 This implements a function which might come in handy in case you
1632 are using low quality on long cabling. It is required for RealTek
1633 RTL-8139 revision K boards, and totally unused otherwise. It tries
1634 to match the transceiver to the cable characteristics. This is
1635 experimental since hardly documented by the manufacturer.
1639 bool "Support for older RTL-8129/8130 boards"
1642 This enables support for the older and uncommon RTL-8129 and
1643 RTL-8130 chips, which support MII via an external transceiver,
1644 instead of an internal one. Disabling this option will save some
1645 memory by making the code size smaller. If unsure, say Y.
1647 config 8139_OLD_RX_RESET
1648 bool "Use older RX-reset method"
1651 The 8139too driver was recently updated to contain a more rapid
1652 reset sequence, in the face of severe receive errors. This "new"
1653 RX-reset method should be adequate for all boards. But if you
1654 experience problems, you can enable this option to restore the
1655 old RX-reset behavior. If unsure, say N.
1658 tristate "RDC R6040 Fast Ethernet Adapter support"
1659 depends on NET_PCI && PCI
1663 This is a driver for the R6040 Fast Ethernet MACs found in the
1664 the RDC R-321x System-on-chips.
1666 To compile this driver as a module, choose M here: the module
1667 will be called r6040. This is recommended.
1670 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1671 depends on NET_PCI && PCI
1675 This is a driver for the Fast Ethernet PCI network cards based on
1676 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1677 SiS 630 and SiS 540 chipsets.
1679 This driver also supports AMD 79C901 HomePNA so that you can use
1680 your phone line as a network cable.
1682 To compile this driver as a module, choose M here: the module
1683 will be called sis900. This is recommended.
1686 tristate "SMC EtherPower II"
1687 depends on NET_PCI && PCI
1691 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1692 which is based on the SMC83c17x (EPIC/100).
1693 More specific information and updates are available from
1694 <http://www.scyld.com/network/epic100.html>.
1697 tristate "SMSC LAN9420 PCI ethernet adapter support"
1698 depends on NET_PCI && PCI
1703 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1704 Say Y if you want it compiled into the kernel,
1705 and read the Ethernet-HOWTO, available from
1706 <http://www.linuxdoc.org/docs.html#howto>.
1708 This driver is also available as a module. The module will be
1709 called smsc9420. If you want to compile it as a module, say M
1710 here and read <file:Documentation/kbuild/modules.txt>
1713 tristate "Sundance Alta support"
1714 depends on NET_PCI && PCI
1718 This driver is for the Sundance "Alta" chip.
1719 More specific information and updates are available from
1720 <http://www.scyld.com/network/sundance.html>.
1722 config SUNDANCE_MMIO
1723 bool "Use MMIO instead of PIO"
1726 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1727 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1728 is known to solve bugs on certain chips.
1733 tristate "TI ThunderLAN support"
1734 depends on NET_PCI && (PCI || EISA)
1736 If you have a PCI Ethernet network card based on the ThunderLAN chip
1737 which is supported by this driver, say Y and read the
1738 Ethernet-HOWTO, available from
1739 <http://www.tldp.org/docs.html#howto>.
1741 Devices currently supported by this driver are Compaq Netelligent,
1742 Compaq NetFlex and Olicom cards. Please read the file
1743 <file:Documentation/networking/tlan.txt> for more details.
1745 To compile this driver as a module, choose M here. The module
1746 will be called tlan.
1748 Please email feedback to <torben.mathiasen@compaq.com>.
1751 tristate "Micrel KSZ8842"
1752 depends on HAS_IOMEM
1754 This platform driver is for Micrel KSZ8842 / KS8842
1755 2-port ethernet switch chip (managed, VLAN, QoS).
1758 tristate "Micrel KS8851 SPI"
1763 SPI driver for Micrel KS8851 SPI attached network chip.
1766 tristate "Micrel KS8851 MLL"
1767 depends on HAS_IOMEM
1770 This platform driver is for Micrel KS8851 Address/data bus
1771 multiplexed network chip.
1774 tristate "VIA Rhine support"
1775 depends on NET_PCI && PCI
1779 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1780 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1781 Ethernet functions can also be found integrated on South Bridges
1784 To compile this driver as a module, choose M here. The module
1785 will be called via-rhine.
1787 config VIA_RHINE_MMIO
1788 bool "Use MMIO instead of PIO"
1789 depends on VIA_RHINE
1791 This instructs the driver to use PCI shared memory (MMIO) instead of
1792 programmed I/O ports (PIO). Enabling this gives an improvement in
1793 processing time in parts of the driver.
1798 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1799 depends on NET_PCI && PCI && EXPERIMENTAL
1802 This is a driver for the Fast Ethernet PCI network cards based on
1803 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1804 have one of these, say Y here.
1806 To compile this driver as a module, choose M here: the module
1807 will be called sc92031. This is recommended.
1810 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1811 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1814 TI AR7 CPMAC Ethernet support
1817 bool "Pocket and portable adapters"
1820 Cute little network (Ethernet) devices which attach to the parallel
1821 port ("pocket adapters"), commonly used with laptops. If you have
1822 one of those, say Y and read the Ethernet-HOWTO, available from
1823 <http://www.tldp.org/docs.html#howto>.
1825 If you want to plug a network (or some other) card into the PCMCIA
1826 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1827 credit card size extension cards used by all modern laptops), you
1828 need the pcmcia-cs package (location contained in the file
1829 <file:Documentation/Changes>) and you can say N here.
1831 Laptop users should read the Linux Laptop home page at
1832 <http://www.linux-on-laptops.com/> or
1833 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1835 Note that the answer to this question doesn't directly affect the
1836 kernel: saying N will just cause the configurator to skip all
1837 the questions about this class of network devices. If you say Y, you
1838 will be asked for your specific device in the following questions.
1841 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1842 depends on NET_POCKET && PARPORT && X86
1845 This is a network (Ethernet) device which attaches to your parallel
1846 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1847 available from <http://www.tldp.org/docs.html#howto>, if you
1848 want to use this. If you intend to use this driver, you should have
1849 said N to the "Parallel printer support", because the two drivers
1850 don't like each other.
1852 To compile this driver as a module, choose M here: the module
1856 tristate "D-Link DE600 pocket adapter support"
1857 depends on NET_POCKET && PARPORT
1859 This is a network (Ethernet) device which attaches to your parallel
1860 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1861 Ethernet-HOWTO, available from
1862 <http://www.tldp.org/docs.html#howto>, if you want to use
1863 this. It is possible to have several devices share a single parallel
1864 port and it is safe to compile the corresponding drivers into the
1867 To compile this driver as a module, choose M here: the module
1868 will be called de600.
1871 tristate "D-Link DE620 pocket adapter support"
1872 depends on NET_POCKET && PARPORT
1874 This is a network (Ethernet) device which attaches to your parallel
1875 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1876 Ethernet-HOWTO, available from
1877 <http://www.tldp.org/docs.html#howto>, if you want to use
1878 this. It is possible to have several devices share a single parallel
1879 port and it is safe to compile the corresponding drivers into the
1882 To compile this driver as a module, choose M here: the module
1883 will be called de620.
1886 tristate "SGI Seeq ethernet controller support"
1887 depends on SGI_HAS_SEEQ
1889 Say Y here if you have an Seeq based Ethernet network card. This is
1890 used in many Silicon Graphics machines.
1893 tristate "DEC LANCE ethernet controller support"
1894 depends on MACH_DECSTATION
1897 This driver is for the series of Ethernet controllers produced by
1898 DEC (now Compaq) based on the AMD Lance chipset, including the
1899 DEPCA series. (This chipset is better known via the NE2100 cards.)
1902 bool "Motorola 68360 ethernet controller"
1905 Say Y here if you want to use the built-in ethernet controller of
1906 the Motorola 68360 processor.
1909 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1910 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1911 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1914 Say Y here if you want to use the built-in 10/100 Fast ethernet
1915 controller on some Motorola ColdFire and Freescale i.MX processors.
1918 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1921 Say Y here if you want to use the second built-in 10/100 Fast
1922 ethernet controller on some Motorola ColdFire processors.
1925 tristate "MPC52xx FEC driver"
1926 depends on PPC_MPC52xx && PPC_BESTCOMM
1929 select PPC_BESTCOMM_FEC
1931 This option enables support for the MPC5200's on-chip
1932 Fast Ethernet Controller
1933 If compiled as module, it will be called fec_mpc52xx.
1935 config FEC_MPC52xx_MDIO
1936 bool "MPC52xx FEC MDIO bus driver"
1937 depends on FEC_MPC52xx
1940 The MPC5200's FEC can connect to the Ethernet either with
1941 an external MII PHY chip or 10 Mbps 7-wire interface
1942 (Motorola? industry standard).
1943 If your board uses an external PHY connected to FEC, enable this.
1944 If not sure, enable.
1945 If compiled as module, it will be called fec_mpc52xx_phy.
1948 tristate "NE2000 compatible support for H8/300"
1951 Say Y here if you want to use the NE2000 compatible
1952 controller on the Renesas H8/300 processor.
1955 tristate "Atheros L2 Fast Ethernet support"
1960 This driver supports the Atheros L2 fast ethernet adapter.
1962 To compile this driver as a module, choose M here. The module
1963 will be called atl2.
1965 config XILINX_EMACLITE
1966 tristate "Xilinx 10/100 Ethernet Lite support"
1967 depends on PPC32 || MICROBLAZE
1970 This driver supports the 10/100 Ethernet Lite from Xilinx.
1973 tristate "Broadcom 63xx internal mac support"
1978 This driver supports the ethernet MACs in the Broadcom 63xx
1979 MIPS chipset family (BCM63XX).
1981 source "drivers/net/fs_enet/Kconfig"
1983 source "drivers/net/octeon/Kconfig"
1985 endif # NET_ETHERNET
1991 menuconfig NETDEV_1000
1992 bool "Ethernet (1000 Mbit)"
1996 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1997 type of Local Area Network (LAN) in universities and companies.
1999 Say Y here to get to see options for Gigabit Ethernet drivers.
2000 This option alone does not add any kernel code.
2001 Note that drivers supporting both 100 and 1000 MBit may be listed
2002 under "Ethernet (10 or 100MBit)" instead.
2004 If you say N, all options in this submenu will be skipped and disabled.
2009 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2012 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2013 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2014 adapter. The driver allows for using the Jumbo Frame option (9000
2015 bytes/frame) however it requires that your switches can handle this
2016 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2019 To compile this driver as a module, choose M here: the
2020 module will be called acenic.
2022 config ACENIC_OMIT_TIGON_I
2023 bool "Omit support for old Tigon I based AceNICs"
2026 Say Y here if you only have Tigon II based AceNICs and want to leave
2027 out support for the older Tigon I based cards which are no longer
2028 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2029 version)). This will reduce the size of the driver object by
2030 app. 100KB. If you are not sure whether your card is a Tigon I or a
2031 Tigon II, say N here.
2033 The safe and default value for this is N.
2036 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2040 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2042 D-Link DGE-550T Gigabit Ethernet Adapter.
2043 D-Link DL2000-based Gigabit Ethernet Adapter.
2044 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2046 To compile this driver as a module, choose M here: the
2047 module will be called dl2k.
2050 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2053 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2054 adapters. For more information on how to identify your adapter, go
2055 to the Adapter & Driver ID Guide at:
2057 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2059 For general information and support, go to the Intel support
2062 <http://support.intel.com>
2064 More specific information on configuring the driver is in
2065 <file:Documentation/networking/e1000.txt>.
2067 To compile this driver as a module, choose M here. The module
2068 will be called e1000.
2071 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2072 depends on PCI && (!SPARC32 || BROKEN)
2074 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2075 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2076 use the regular e1000 driver For more information on how to
2077 identify your adapter, go to the Adapter & Driver ID Guide at:
2079 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2081 For general information and support, go to the Intel support
2084 <http://support.intel.com>
2086 To compile this driver as a module, choose M here. The module
2087 will be called e1000e.
2090 tristate "IP1000 Gigabit Ethernet support"
2091 depends on PCI && EXPERIMENTAL
2094 This driver supports IP1000 gigabit Ethernet cards.
2096 To compile this driver as a module, choose M here: the module
2097 will be called ipg. This is recommended.
2100 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2103 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2104 adapters. For more information on how to identify your adapter, go
2105 to the Adapter & Driver ID Guide at:
2107 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2109 For general information and support, go to the Intel support
2112 <http://support.intel.com>
2114 More specific information on configuring the driver is in
2115 <file:Documentation/networking/e1000.txt>.
2117 To compile this driver as a module, choose M here. The module
2121 bool "Direct Cache Access (DCA) Support"
2123 depends on IGB && DCA && !(IGB=y && DCA=m)
2125 Say Y here if you want to use Direct Cache Access (DCA) in the
2126 driver. DCA is a method for warming the CPU cache before data
2127 is used, with the intent of lessening the impact of cache misses.
2130 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2133 This driver supports Intel(R) 82576 virtual functions. For more
2134 information on how to identify your adapter, go to the Adapter &
2137 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2139 For general information and support, go to the Intel support
2142 <http://support.intel.com>
2144 More specific information on configuring the driver is in
2145 <file:Documentation/networking/e1000.txt>.
2147 To compile this driver as a module, choose M here. The module
2148 will be called igbvf.
2150 source "drivers/net/ixp2000/Kconfig"
2153 tristate "MyriCOM Gigabit Ethernet support"
2156 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2158 To compile this driver as a module, choose M here: the module
2159 will be called myri_sbus. This is recommended.
2162 tristate "National Semiconductor DP83820 support"
2165 This is a driver for the National Semiconductor DP83820 series
2166 of gigabit ethernet MACs. Cards using this chipset include
2167 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2168 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2172 tristate "Packet Engines Hamachi GNIC-II support"
2176 If you have a Gigabit Ethernet card of this type, say Y and read
2177 the Ethernet-HOWTO, available from
2178 <http://www.tldp.org/docs.html#howto>.
2180 To compile this driver as a module, choose M here. The module will be
2184 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2185 depends on PCI && EXPERIMENTAL
2188 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2189 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2190 used by the Beowulf Linux cluster project. See
2191 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2192 information about this driver in particular and Beowulf in general.
2194 To compile this driver as a module, choose M here: the module
2195 will be called yellowfin. This is recommended.
2198 tristate "Realtek 8169 gigabit ethernet support"
2203 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2205 To compile this driver as a module, choose M here: the module
2206 will be called r8169. This is recommended.
2210 depends on R8169 && VLAN_8021Q
2212 Say Y here for the r8169 driver to support the functions required
2213 by the kernel 802.1Q code.
2218 tristate "SB1250 Gigabit Ethernet support"
2219 depends on SIBYTE_SB1xxx_SOC
2222 This driver supports Gigabit Ethernet interfaces based on the
2223 Broadcom SiByte family of System-On-a-Chip parts. They include
2224 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2227 To compile this driver as a module, choose M here: the module
2228 will be called sb1250-mac.
2231 tristate "SiS190/SiS191 gigabit ethernet support"
2236 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2237 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2238 appear in lan on motherboard designs which are based on SiS 965
2239 and SiS 966 south bridge.
2241 To compile this driver as a module, choose M here: the module
2242 will be called sis190. This is recommended.
2245 tristate "New SysKonnect GigaEthernet support"
2249 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2250 and related Gigabit Ethernet adapters. It is a new smaller driver
2251 with better performance and more complete ethtool support.
2253 It does not support the link failover and network management
2254 features that "portable" vendor supplied sk98lin driver does.
2256 This driver supports adapters based on the original Yukon chipset:
2257 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2258 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2260 It does not support the newer Yukon2 chipset: a separate driver,
2261 sky2, is provided for Yukon2-based adapters.
2263 To compile this driver as a module, choose M here: the module
2264 will be called skge. This is recommended.
2267 bool "Debugging interface"
2268 depends on SKGE && DEBUG_FS
2270 This option adds the ability to dump driver state for debugging.
2271 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2272 transmit and receive rings.
2277 tristate "SysKonnect Yukon2 support"
2281 This driver supports Gigabit Ethernet adapters based on the
2282 Marvell Yukon 2 chipset:
2283 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2284 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2286 There is companion driver for the older Marvell Yukon and
2287 Genesis based adapters: skge.
2289 To compile this driver as a module, choose M here: the module
2290 will be called sky2. This is recommended.
2293 bool "Debugging interface"
2294 depends on SKY2 && DEBUG_FS
2296 This option adds the ability to dump driver state for debugging.
2297 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2298 transmit and receive rings.
2303 tristate "VIA Velocity support"
2309 If you have a VIA "Velocity" based network card say Y here.
2311 To compile this driver as a module, choose M here. The module
2312 will be called via-velocity.
2315 tristate "Broadcom Tigon3 support"
2319 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2321 To compile this driver as a module, choose M here: the module
2322 will be called tg3. This is recommended.
2325 tristate "Broadcom NetXtremeII support"
2330 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2332 To compile this driver as a module, choose M here: the module
2333 will be called bnx2. This is recommended.
2336 tristate "Broadcom CNIC support"
2341 This driver supports offload features of Broadcom NetXtremeII
2342 gigabit Ethernet cards.
2344 To compile this driver as a module, choose M here: the module
2345 will be called cnic. This is recommended.
2348 tristate "Spider Gigabit Ethernet driver"
2349 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2352 This driver supports the Gigabit Ethernet chips present on the
2353 Cell Processor-Based Blades from IBM.
2356 tristate "Tundra TSI108 gigabit Ethernet support"
2357 depends on TSI108_BRIDGE
2359 This driver supports Tundra TSI108 gigabit Ethernet ports.
2360 To compile this driver as a module, choose M here: the module
2361 will be called tsi108_eth.
2364 tristate "PS3 Gigabit Ethernet driver"
2366 select PS3_SYS_MANAGER
2368 This driver supports the network device on the PS3 game
2369 console. This driver has built-in support for Ethernet.
2371 To compile this driver as a module, choose M here: the
2372 module will be called ps3_gelic.
2374 config GELIC_WIRELESS
2375 bool "PS3 Wireless support"
2377 depends on GELIC_NET
2380 This option adds the support for the wireless feature of PS3.
2381 If you have the wireless-less model of PS3 or have no plan to
2382 use wireless feature, disabling this option saves memory. As
2383 the driver automatically distinguishes the models, you can
2384 safely enable this option even if you have a wireless-less model.
2387 tristate "Freescale PQ MDIO"
2391 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2394 tristate "Gianfar Ethernet"
2400 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2401 and MPC86xx family of chips, and the FEC on the 8540.
2404 tristate "Freescale QE Gigabit Ethernet"
2405 depends on QUICC_ENGINE
2409 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2410 which is available on some Freescale SOCs.
2412 config UGETH_TX_ON_DEMAND
2413 bool "Transmit on Demand support"
2417 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2418 depends on MV64X60 || PPC32 || PLAT_ORION
2422 This driver supports the gigabit ethernet MACs in the
2423 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2424 in the Marvell Orion ARM SoC family.
2426 Some boards that use the Discovery chipset are the Momenco
2427 Ocelot C and Jaguar ATX and Pegasos II.
2429 config XILINX_LL_TEMAC
2430 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2431 depends on PPC || MICROBLAZE
2434 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2435 core used in Xilinx Spartan and Virtex FPGAs
2438 tristate "QLogic QLA3XXX Network Driver Support"
2441 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2443 To compile this driver as a module, choose M here: the module
2444 will be called qla3xxx.
2447 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2452 This driver supports the Atheros/Attansic L1 gigabit ethernet
2455 To compile this driver as a module, choose M here. The module
2456 will be called atl1.
2459 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2460 depends on PCI && EXPERIMENTAL
2464 This driver supports the Atheros L1E gigabit ethernet adapter.
2466 To compile this driver as a module, choose M here. The module
2467 will be called atl1e.
2470 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2471 depends on PCI && EXPERIMENTAL
2475 This driver supports the Atheros L1C gigabit ethernet adapter.
2477 To compile this driver as a module, choose M here. The module
2478 will be called atl1c.
2481 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2486 This driver supports the PCI-Express gigabit ethernet adapters
2487 based on JMicron JMC250 chipset.
2489 To compile this driver as a module, choose M here. The module
2493 tristate "S6105 GMAC ethernet support"
2494 depends on XTENSA_VARIANT_S6000
2497 This driver supports the on chip ethernet device on the
2498 S6105 xtensa processor.
2500 To compile this driver as a module, choose M here. The module
2501 will be called s6gmac.
2503 source "drivers/net/stmmac/Kconfig"
2508 # 10 Gigabit Ethernet
2511 menuconfig NETDEV_10000
2512 bool "Ethernet (10000 Mbit)"
2516 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2517 This option alone does not add any kernel code.
2519 If you say N, all options in this submenu will be skipped and disabled.
2527 tristate "Chelsio 10Gb Ethernet support"
2532 This driver supports Chelsio gigabit and 10-gigabit
2533 Ethernet cards. More information about adapter features and
2534 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2536 For general information about Chelsio and our products, visit
2537 our website at <http://www.chelsio.com>.
2539 For customer support, please visit our customer support page at
2540 <http://www.chelsio.com/support.htm>.
2542 Please send feedback to <linux-bugs@chelsio.com>.
2544 To compile this driver as a module, choose M here: the module
2545 will be called cxgb.
2547 config CHELSIO_T1_1G
2548 bool "Chelsio gigabit Ethernet support"
2549 depends on CHELSIO_T1
2551 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2552 are using only 10G cards say 'N' here.
2554 config CHELSIO_T3_DEPENDS
2556 depends on PCI && INET
2560 tristate "Chelsio Communications T3 10Gb Ethernet support"
2561 depends on CHELSIO_T3_DEPENDS
2565 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2568 For general information about Chelsio and our products, visit
2569 our website at <http://www.chelsio.com>.
2571 For customer support, please visit our customer support page at
2572 <http://www.chelsio.com/support.htm>.
2574 Please send feedback to <linux-bugs@chelsio.com>.
2576 To compile this driver as a module, choose M here: the module
2577 will be called cxgb3.
2579 config CHELSIO_T4_DEPENDS
2581 depends on PCI && INET
2585 tristate "Chelsio Communications T4 Ethernet support"
2586 depends on CHELSIO_T4_DEPENDS
2590 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2593 For general information about Chelsio and our products, visit
2594 our website at <http://www.chelsio.com>.
2596 For customer support, please visit our customer support page at
2597 <http://www.chelsio.com/support.htm>.
2599 Please send feedback to <linux-bugs@chelsio.com>.
2601 To compile this driver as a module choose M here; the module
2602 will be called cxgb4.
2605 tristate "eHEA Ethernet support"
2606 depends on IBMEBUS && INET && SPARSEMEM
2609 This driver supports the IBM pSeries eHEA ethernet adapter.
2611 To compile the driver as a module, choose M here. The module
2612 will be called ehea.
2615 tristate "Cisco VIC Ethernet NIC Support"
2616 depends on PCI && INET
2619 This enables the support for the Cisco VIC Ethernet card.
2622 tristate "Intel(R) 10GbE PCI Express adapters support"
2623 depends on PCI && INET
2626 This driver supports Intel(R) 10GbE PCI Express family of
2627 adapters. For more information on how to identify your adapter, go
2628 to the Adapter & Driver ID Guide at:
2630 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2632 For general information and support, go to the Intel support
2635 <http://support.intel.com>
2637 To compile this driver as a module, choose M here. The module
2638 will be called ixgbe.
2641 bool "Direct Cache Access (DCA) Support"
2643 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2645 Say Y here if you want to use Direct Cache Access (DCA) in the
2646 driver. DCA is a method for warming the CPU cache before data
2647 is used, with the intent of lessening the impact of cache misses.
2650 bool "Data Center Bridging (DCB) Support"
2652 depends on IXGBE && DCB
2654 Say Y here if you want to use Data Center Bridging (DCB) in the
2660 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2663 This driver supports Intel(R) 82599 virtual functions. For more
2664 information on how to identify your adapter, go to the Adapter &
2667 <http://support.intel.com/support/network/sb/CS-008441.htm>
2669 For general information and support, go to the Intel support
2672 <http://support.intel.com>
2674 More specific information on configuring the driver is in
2675 <file:Documentation/networking/ixgbevf.txt>.
2677 To compile this driver as a module, choose M here. The module
2678 will be called ixgbevf. MSI-X interrupt support is required
2679 for this driver to work correctly.
2682 tristate "Intel(R) PRO/10GbE support"
2685 This driver supports Intel(R) PRO/10GbE family of adapters for
2686 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2687 instead. For more information on how to identify your adapter, go
2688 to the Adapter & Driver ID Guide at:
2690 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2692 For general information and support, go to the Intel support
2695 <http://support.intel.com>
2697 More specific information on configuring the driver is in
2698 <file:Documentation/networking/ixgb.txt>.
2700 To compile this driver as a module, choose M here. The module
2701 will be called ixgb.
2704 tristate "S2IO 10Gbe XFrame NIC"
2707 This driver supports the 10Gbe XFrame NIC of S2IO.
2708 More specific information on configuring the driver is in
2709 <file:Documentation/networking/s2io.txt>.
2712 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2713 depends on PCI && INET
2715 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2716 I/O Virtualized Server Adapter.
2717 More specific information on configuring the driver is in
2718 <file:Documentation/networking/vxge.txt>.
2720 config VXGE_DEBUG_TRACE_ALL
2721 bool "Enabling All Debug trace statments in driver"
2725 Say Y here if you want to enabling all the debug trace statements in
2726 driver. By default only few debug trace statements are enabled.
2729 tristate "Myricom Myri-10G Ethernet support"
2730 depends on PCI && INET
2735 This driver supports Myricom Myri-10G Dual Protocol interface in
2736 Ethernet mode. If the eeprom on your board is not recent enough,
2737 you will need a newer firmware image.
2738 You may get this image or more information, at:
2740 <http://www.myri.com/scs/download-Myri10GE.html>
2742 To compile this driver as a module, choose M here. The module
2743 will be called myri10ge.
2746 bool "Direct Cache Access (DCA) Support"
2748 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2750 Say Y here if you want to use Direct Cache Access (DCA) in the
2751 driver. DCA is a method for warming the CPU cache before data
2752 is used, with the intent of lessening the impact of cache misses.
2755 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2758 This enables the support for NetXen's Gigabit Ethernet card.
2761 tristate "Sun Neptune 10Gbit Ethernet support"
2765 This enables support for cards based upon Sun's
2769 tristate "PA Semi 1/10Gbit MAC"
2770 depends on PPC_PASEMI && PCI
2774 This driver supports the on-chip 1/10Gbit Ethernet controller on
2775 PA Semi's PWRficient line of chips.
2778 tristate "Mellanox Technologies 10Gbit Ethernet support"
2779 depends on PCI && INET
2783 This driver supports Mellanox Technologies ConnectX Ethernet
2792 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2793 depends on MLX4_CORE
2796 This option causes debugging code to be compiled into the
2797 mlx4_core driver. The output can be turned on via the
2798 debug_level module parameter (which can also be set after
2799 the driver is loaded through sysfs).
2802 tristate "Tehuti Networks 10G Ethernet"
2805 Tehuti Networks 10G Ethernet NIC
2808 tristate "Broadcom NetXtremeII 10Gb support"
2815 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2816 To compile this driver as a module, choose M here: the module
2817 will be called bnx2x. This is recommended.
2820 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2823 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2827 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2830 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2832 To compile this driver as a module, choose M here: the module
2833 will be called qlge.
2835 source "drivers/net/sfc/Kconfig"
2837 source "drivers/net/benet/Kconfig"
2839 endif # NETDEV_10000
2841 source "drivers/net/tokenring/Kconfig"
2843 source "drivers/net/wireless/Kconfig"
2845 source "drivers/net/wimax/Kconfig"
2847 source "drivers/net/usb/Kconfig"
2849 source "drivers/net/pcmcia/Kconfig"
2851 source "drivers/net/wan/Kconfig"
2853 source "drivers/atm/Kconfig"
2855 source "drivers/ieee802154/Kconfig"
2857 source "drivers/s390/net/Kconfig"
2859 source "drivers/net/caif/Kconfig"
2861 config XEN_NETDEV_FRONTEND
2862 tristate "Xen network device frontend driver"
2866 The network device frontend driver allows the kernel to
2867 access network devices exported exported by a virtual
2868 machine containing a physical network device driver. The
2869 frontend driver is intended for unprivileged guest domains;
2870 if you are compiling a kernel for a Xen guest, you almost
2871 certainly want to enable this.
2874 tristate "iSeries Virtual Ethernet driver support"
2875 depends on PPC_ISERIES
2878 tristate "RapidIO Ethernet over messaging driver support"
2881 config RIONET_TX_SIZE
2882 int "Number of outbound queue entries"
2886 config RIONET_RX_SIZE
2887 int "Number of inbound queue entries"
2892 tristate "FDDI driver support"
2893 depends on (PCI || EISA || TC)
2895 Fiber Distributed Data Interface is a high speed local area network
2896 design; essentially a replacement for high speed Ethernet. FDDI can
2897 run over copper or fiber. If you are connected to such a network and
2898 want a driver for the FDDI card in your computer, say Y here (and
2899 then also Y to the driver for your FDDI card, below). Most people
2903 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2904 depends on FDDI && (PCI || EISA || TC)
2906 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2907 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2908 to a local FDDI network.
2910 To compile this driver as a module, choose M here: the module
2911 will be called defxx. If unsure, say N.
2915 prompt "Use MMIO instead of PIO" if PCI || EISA
2917 default n if PCI || EISA
2920 This instructs the driver to use EISA or PCI memory-mapped I/O
2921 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2922 Enabling this gives an improvement in processing time in parts
2923 of the driver, but it may cause problems with EISA (DEFEA)
2924 adapters. TURBOchannel does not have the concept of I/O ports,
2925 so MMIO is always used for these (DEFTA) adapters.
2930 tristate "SysKonnect FDDI PCI support"
2931 depends on FDDI && PCI
2934 Say Y here if you have a SysKonnect FDDI PCI adapter.
2935 The following adapters are supported by this driver:
2936 - SK-5521 (SK-NET FDDI-UP)
2937 - SK-5522 (SK-NET FDDI-UP DAS)
2938 - SK-5541 (SK-NET FDDI-FP)
2939 - SK-5543 (SK-NET FDDI-LP)
2940 - SK-5544 (SK-NET FDDI-LP DAS)
2941 - SK-5821 (SK-NET FDDI-UP64)
2942 - SK-5822 (SK-NET FDDI-UP64 DAS)
2943 - SK-5841 (SK-NET FDDI-FP64)
2944 - SK-5843 (SK-NET FDDI-LP64)
2945 - SK-5844 (SK-NET FDDI-LP64 DAS)
2946 - Netelligent 100 FDDI DAS Fibre SC
2947 - Netelligent 100 FDDI SAS Fibre SC
2948 - Netelligent 100 FDDI DAS UTP
2949 - Netelligent 100 FDDI SAS UTP
2950 - Netelligent 100 FDDI SAS Fibre MIC
2952 Read <file:Documentation/networking/skfp.txt> for information about
2955 Questions concerning this driver can be addressed to:
2956 <linux@syskonnect.de>
2958 To compile this driver as a module, choose M here: the module
2959 will be called skfp. This is recommended.
2962 bool "HIPPI driver support (EXPERIMENTAL)"
2963 depends on EXPERIMENTAL && INET && PCI
2965 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2966 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2967 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2968 single-mode). HIPPI networks are commonly used for clusters and to
2969 connect to super computers. If you are connected to a HIPPI network
2970 and have a HIPPI network card in your computer that you want to use
2971 under Linux, say Y here (you must also remember to enable the driver
2972 for your HIPPI card below). Most people will say N here.
2975 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2976 depends on HIPPI && PCI
2978 Say Y here if this is your PCI HIPPI network card.
2980 To compile this driver as a module, choose M here: the module
2981 will be called rrunner. If unsure, say N.
2983 config ROADRUNNER_LARGE_RINGS
2984 bool "Use large TX/RX rings (EXPERIMENTAL)"
2985 depends on ROADRUNNER
2987 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2988 of additional memory to allow for fastest operation, both for
2989 transmitting and receiving. This memory cannot be used by any other
2990 kernel code or by user space programs. Say Y here only if you have
2994 tristate "PLIP (parallel port) support"
2997 PLIP (Parallel Line Internet Protocol) is used to create a
2998 reasonably fast mini network consisting of two (or, rarely, more)
2999 local machines. A PLIP link from a Linux box is a popular means to
3000 install a Linux distribution on a machine which doesn't have a
3001 CD-ROM drive (a minimal system has to be transferred with floppies
3002 first). The kernels on both machines need to have this PLIP option
3003 enabled for this to work.
3005 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3006 ports (the connectors at the computers with 25 holes) are connected
3007 with "null printer" or "Turbo Laplink" cables which can transmit 4
3008 bits at a time (mode 0) or with special PLIP cables, to be used on
3009 bidirectional parallel ports only, which can transmit 8 bits at a
3010 time (mode 1); you can find the wiring of these cables in
3011 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3012 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3013 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3014 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3015 and winsock or NCSA's telnet.
3017 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3018 as the NET-3-HOWTO, both available from
3019 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3020 protocol has been changed and this PLIP driver won't work together
3021 with the PLIP support in Linux versions 1.0.x. This option enlarges
3022 your kernel by about 8 KB.
3024 To compile this driver as a module, choose M here. The module
3025 will be called plip. If unsure, say Y or M, in case you buy
3029 tristate "PPP (point-to-point protocol) support"
3032 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3033 the same purpose: sending Internet traffic over telephone (and other
3034 serial) lines. Ask your access provider if they support it, because
3035 otherwise you can't use it; most Internet access providers these
3036 days support PPP rather than SLIP.
3038 To use PPP, you need an additional program called pppd as described
3039 in the PPP-HOWTO, available at
3040 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3041 the version of pppd recommended in <file:Documentation/Changes>.
3042 The PPP option enlarges your kernel by about 16 KB.
3044 There are actually two versions of PPP: the traditional PPP for
3045 asynchronous lines, such as regular analog phone lines, and
3046 synchronous PPP which can be used over digital ISDN lines for
3047 example. If you want to use PPP over phone lines or other
3048 asynchronous serial lines, you need to say Y (or M) here and also to
3049 the next option, "PPP support for async serial ports". For PPP over
3050 synchronous lines, you should say Y (or M) here and to "Support
3051 synchronous PPP", below.
3053 If you said Y to "Version information on all symbols" above, then
3054 you cannot compile the PPP driver into the kernel; you can then only
3055 compile it as a module. To compile this driver as a module, choose M
3056 here. The module will be called ppp_generic.
3058 config PPP_MULTILINK
3059 bool "PPP multilink support (EXPERIMENTAL)"
3060 depends on PPP && EXPERIMENTAL
3062 PPP multilink is a protocol (defined in RFC 1990) which allows you
3063 to combine several (logical or physical) lines into one logical PPP
3064 connection, so that you can utilize your full bandwidth.
3066 This has to be supported at the other end as well and you need a
3067 version of the pppd daemon which understands the multilink protocol.
3072 bool "PPP filtering"
3075 Say Y here if you want to be able to filter the packets passing over
3076 PPP interfaces. This allows you to control which packets count as
3077 activity (i.e. which packets will reset the idle timer or bring up
3078 a demand-dialed link) and which packets are to be dropped entirely.
3079 You need to say Y here if you wish to use the pass-filter and
3080 active-filter options to pppd.
3085 tristate "PPP support for async serial ports"
3089 Say Y (or M) here if you want to be able to use PPP over standard
3090 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3091 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3094 To compile this driver as a module, choose M here.
3099 tristate "PPP support for sync tty ports"
3102 Say Y (or M) here if you want to be able to use PPP over synchronous
3103 (HDLC) tty devices, such as the SyncLink adapter. These devices
3104 are often used for high-speed leased lines like T1/E1.
3106 To compile this driver as a module, choose M here.
3109 tristate "PPP Deflate compression"
3114 Support for the Deflate compression method for PPP, which uses the
3115 Deflate algorithm (the same algorithm that gzip uses) to compress
3116 each PPP packet before it is sent over the wire. The machine at the
3117 other end of the PPP link (usually your ISP) has to support the
3118 Deflate compression method as well for this to be useful. Even if
3119 they don't support it, it is safe to say Y here.
3121 To compile this driver as a module, choose M here.
3124 tristate "PPP BSD-Compress compression"
3127 Support for the BSD-Compress compression method for PPP, which uses
3128 the LZW compression method to compress each PPP packet before it is
3129 sent over the wire. The machine at the other end of the PPP link
3130 (usually your ISP) has to support the BSD-Compress compression
3131 method as well for this to be useful. Even if they don't support it,
3132 it is safe to say Y here.
3134 The PPP Deflate compression method ("PPP Deflate compression",
3135 above) is preferable to BSD-Compress, because it compresses better
3138 Note that the BSD compression code will always be compiled as a
3139 module; it is called bsd_comp and will show up in the directory
3140 modules once you have said "make modules". If unsure, say N.
3143 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3144 depends on PPP && EXPERIMENTAL
3150 Support for the MPPE Encryption protocol, as employed by the
3151 Microsoft Point-to-Point Tunneling Protocol.
3153 See http://pptpclient.sourceforge.net/ for information on
3154 configuring PPTP clients and servers to utilize this method.
3157 tristate "PPP over Ethernet (EXPERIMENTAL)"
3158 depends on EXPERIMENTAL && PPP
3160 Support for PPP over Ethernet.
3162 This driver requires the latest version of pppd from the CVS
3163 repository at cvs.samba.org. Alternatively, see the
3164 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3165 which contains instruction on how to use this driver (under
3166 the heading "Kernel mode PPPoE").
3169 tristate "PPP over ATM"
3170 depends on ATM && PPP
3172 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3173 This implementation does not yet comply with section 8 of RFC2364,
3174 which can lead to bad results if the ATM peer loses state and
3175 changes its encapsulation unilaterally.
3178 tristate "PPP over L2TP (EXPERIMENTAL)"
3179 depends on EXPERIMENTAL && L2TP && PPP
3181 Support for PPP-over-L2TP socket family. L2TP is a protocol
3182 used by ISPs and enterprises to tunnel PPP traffic over UDP
3183 tunnels. L2TP is replacing PPTP for VPN uses.
3186 tristate "SLIP (serial line) support"
3188 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3189 connect to your Internet service provider or to connect to some
3190 other local Unix box or if you want to configure your Linux box as a
3191 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3192 Internet Protocol) is a protocol used to send Internet traffic over
3193 serial connections such as telephone lines or null modem cables;
3194 nowadays, the protocol PPP is more commonly used for this same
3197 Normally, your access provider has to support SLIP in order for you
3198 to be able to use it, but there is now a SLIP emulator called SLiRP
3199 around (available from
3200 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3201 allows you to use SLIP over a regular dial up shell connection. If
3202 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3203 NET-3-HOWTO, available from
3204 <http://www.tldp.org/docs.html#howto>, explains how to
3205 configure SLIP. Note that you don't need this option if you just
3206 want to run term (term is a program which gives you almost full
3207 Internet connectivity if you have a regular dial up shell account on
3208 some Internet connected Unix computer. Read
3209 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3210 support will enlarge your kernel by about 4 KB. If unsure, say N.
3212 To compile this driver as a module, choose M here. The module
3213 will be called slip.
3215 config SLIP_COMPRESSED
3216 bool "CSLIP compressed headers"
3220 This protocol is faster than SLIP because it uses compression on the
3221 TCP/IP headers (not on the data itself), but it has to be supported
3222 on both ends. Ask your access provider if you are not sure and
3223 answer Y, just in case. You will still be able to use plain SLIP. If
3224 you plan to use SLiRP, the SLIP emulator (available from
3225 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3226 allows you to use SLIP over a regular dial up shell connection, you
3227 definitely want to say Y here. The NET-3-HOWTO, available from
3228 <http://www.tldp.org/docs.html#howto>, explains how to configure
3229 CSLIP. This won't enlarge your kernel.
3234 This option enables Van Jacobsen serial line header compression
3238 bool "Keepalive and linefill"
3241 Adds additional capabilities to the SLIP driver to support the
3242 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3245 config SLIP_MODE_SLIP6
3246 bool "Six bit SLIP encapsulation"
3249 Just occasionally you may need to run IP over hostile serial
3250 networks that don't pass all control characters or are only seven
3251 bit. Saying Y here adds an extra mode you can use with SLIP:
3252 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3253 the serial device. Naturally, this has to be supported at the other
3254 end of the link as well. It's good enough, for example, to run IP
3255 over the async ports of a Camtec JNT Pad. If unsure, say N.
3258 bool "Fibre Channel driver support"
3259 depends on SCSI && PCI
3261 Fibre Channel is a high speed serial protocol mainly used to connect
3262 large storage devices to the computer; it is compatible with and
3263 intended to replace SCSI.
3265 If you intend to use Fibre Channel, you need to have a Fibre channel
3266 adaptor card in your computer; say Y here and to the driver for your
3267 adaptor below. You also should have said Y to "SCSI support" and
3268 "SCSI generic support".
3271 tristate "Network console logging support"
3273 If you want to log kernel messages over the network, enable this.
3274 See <file:Documentation/networking/netconsole.txt> for details.
3276 config NETCONSOLE_DYNAMIC
3277 bool "Dynamic reconfiguration of logging targets"
3278 depends on NETCONSOLE && SYSFS
3281 This option enables the ability to dynamically reconfigure target
3282 parameters (interface, IP addresses, port numbers, MAC addresses)
3283 at runtime through a userspace interface exported using configfs.
3284 See <file:Documentation/networking/netconsole.txt> for details.
3290 bool "Netpoll traffic trapping"
3294 config NET_POLL_CONTROLLER
3298 tristate "Virtio network driver (EXPERIMENTAL)"
3299 depends on EXPERIMENTAL && VIRTIO
3301 This is the virtual network driver for virtio. It can be used with
3302 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3305 tristate "VMware VMXNET3 ethernet driver"
3306 depends on PCI && INET
3308 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3309 To compile this driver as a module, choose M here: the
3310 module will be called vmxnet3.