2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
97 This adds a specialized tap character device driver that is based
98 on the MAC-VLAN network interface, called macvtap. A macvtap device
99 can be added in the same way as a macvlan device, using 'type
100 macvlan', and then be accessed through the tap user space interface.
102 To compile this driver as a module, choose M here: the module
103 will be called macvtap.
106 tristate "EQL (serial line load balancing) support"
108 If you have two serial connections to some other computer (this
109 usually requires two modems and two telephone lines) and you use
110 SLIP (the protocol for sending Internet traffic over telephone
111 lines) or PPP (a better SLIP) on them, you can make them behave like
112 one double speed connection using this driver. Naturally, this has
113 to be supported at the other end as well, either with a similar EQL
114 Linux driver or with a Livingston Portmaster 2e.
116 Say Y if you want this and read
117 <file:Documentation/networking/eql.txt>. You may also want to read
118 section 6.2 of the NET-3-HOWTO, available from
119 <http://www.tldp.org/docs.html#howto>.
121 To compile this driver as a module, choose M here: the module
122 will be called eql. If unsure, say N.
125 tristate "Universal TUN/TAP device driver support"
128 TUN/TAP provides packet reception and transmission for user space
129 programs. It can be viewed as a simple Point-to-Point or Ethernet
130 device, which instead of receiving packets from a physical media,
131 receives them from user space program and instead of sending packets
132 via physical media writes them to the user space program.
134 When a program opens /dev/net/tun, driver creates and registers
135 corresponding net device tunX or tapX. After a program closed above
136 devices, driver will automatically delete tunXX or tapXX device and
137 all routes corresponding to it.
139 Please read <file:Documentation/networking/tuntap.txt> for more
142 To compile this driver as a module, choose M here: the module
145 If you don't know what to use this for, you don't need it.
148 tristate "Virtual ethernet pair device"
150 This device is a local ethernet tunnel. Devices are created in pairs.
151 When one end receives the packet it appears on its pair and vice
155 tristate "General Instruments Surfboard 1000"
158 This is a driver for the General Instrument (also known as
159 NextLevel) SURFboard 1000 internal
160 cable modem. This is an ISA card which is used by a number of cable
161 TV companies to provide cable modem access. It's a one-way
162 downstream-only cable modem, meaning that your upstream net link is
163 provided by your regular phone modem.
165 At present this driver only compiles as a module, so say M here if
166 you have this card. The module will be called sb1000. Then read
167 <file:Documentation/networking/README.sb1000> for information on how
168 to use this module, as it needs special ppp scripts for establishing
169 a connection. Further documentation and the necessary scripts can be
172 <http://www.jacksonville.net/~fventuri/>
173 <http://home.adelphia.net/~siglercm/sb1000.html>
174 <http://linuxpower.cx/~cable/>
176 If you don't have this card, of course say N.
178 source "drivers/net/arcnet/Kconfig"
180 source "drivers/net/phy/Kconfig"
186 menuconfig NET_ETHERNET
187 bool "Ethernet (10 or 100Mbit)"
190 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
191 type of Local Area Network (LAN) in universities and companies.
193 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
194 coaxial cable, linking computers in a chain), 10BASE-T or twisted
195 pair (10 Mbps over twisted pair cable, linking computers to central
196 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
197 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
198 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
199 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
200 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
201 Ethernet (1 Gbps over optical fiber or short copper links).
203 If your Linux machine will be connected to an Ethernet and you have
204 an Ethernet network interface card (NIC) installed in your computer,
205 say Y here and read the Ethernet-HOWTO, available from
206 <http://www.tldp.org/docs.html#howto>. You will then also have
207 to say Y to the driver for your particular NIC.
209 Note that the answer to this question won't directly affect the
210 kernel: saying N will just cause the configurator to skip all
211 the questions about Ethernet network cards. If unsure, say N.
216 tristate "Generic Media Independent Interface device support"
218 Most ethernet controllers have MII transceiver either as an external
219 or internal device. It is safe to say Y or M here even if your
220 ethernet card lack MII.
223 tristate "Atmel MACB support"
224 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9
227 The Atmel MACB ethernet interface is found on many AT32 and AT91
228 parts. Say Y to include support for the MACB chip.
230 To compile this driver as a module, choose M here: the module
233 source "drivers/net/arm/Kconfig"
236 tristate "ASIX AX88796 NE2000 clone support"
237 depends on ARM || MIPS || SUPERH
241 AX88796 driver, using platform bus to provide
242 chip detection and resources
245 bool "ASIX AX88796 external 93CX6 eeprom support"
249 Select this if your platform comes with an external 93CX6 eeprom.
252 tristate "MACE (Power Mac ethernet) support"
253 depends on PPC_PMAC && PPC32
256 Power Macintoshes and clones with Ethernet built-in on the
257 motherboard will usually use a MACE (Medium Access Control for
258 Ethernet) interface. Say Y to include support for the MACE chip.
260 To compile this driver as a module, choose M here: the module
263 config MACE_AAUI_PORT
264 bool "Use AAUI port instead of TP by default"
267 Some Apple machines (notably the Apple Network Server) which use the
268 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
269 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
270 Y here if you have such a machine. If unsure, say N.
271 The driver will default to AAUI on ANS anyway, and if you use it as
272 a module, you can provide the port_aaui=0|1 to force the driver.
275 tristate "BMAC (G3 ethernet) support"
276 depends on PPC_PMAC && PPC32
279 Say Y for support of BMAC Ethernet interfaces. These are used on G3
282 To compile this driver as a module, choose M here: the module
286 tristate "Ariadne support"
289 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
292 To compile this driver as a module, choose M here: the module
293 will be called ariadne.
296 tristate "A2065 support"
300 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
303 To compile this driver as a module, choose M here: the module
304 will be called a2065.
307 tristate "Hydra support"
311 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
313 To compile this driver as a module, choose M here: the module
314 will be called hydra.
317 tristate "Zorro NS8390-based Ethernet support"
321 This driver is for Zorro Ethernet cards using an NS8390-compatible
322 chipset, like the Village Tronic Ariadne II and the Individual
323 Computers X-Surf Ethernet cards. If you have such a card, say Y.
326 To compile this driver as a module, choose M here: the module
327 will be called zorro8390.
330 tristate "PCMCIA NE2000 support"
331 depends on AMIGA_PCMCIA
334 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
337 To compile this driver as a module, choose M here: the module
341 bool "Macintosh NS 8390 based ethernet cards"
345 If you want to include a driver to support Nubus or LC-PDS
346 Ethernet cards using an NS8390 chipset or its equivalent, say Y
347 and read the Ethernet-HOWTO, available from
348 <http://www.tldp.org/docs.html#howto>.
351 tristate "Macintosh CS89x0 based ethernet cards"
354 Support for CS89x0 chipset based Ethernet cards. If you have a
355 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
356 read the Ethernet-HOWTO, available from
357 <http://www.tldp.org/docs.html#howto>.
359 To compile this driver as a module, choose M here. This module will
363 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
366 Support for NatSemi SONIC based Ethernet devices. This includes
367 the onboard Ethernet in many Quadras as well as some LC-PDS,
368 a few Nubus and all known Comm Slot Ethernet cards. If you have
369 one of these say Y and read the Ethernet-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>.
372 To compile this driver as a module, choose M here. This module will
376 bool "Macintosh (AV) onboard MACE ethernet"
380 Support for the onboard AMD 79C940 MACE Ethernet controller used in
381 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
382 say Y and read the Ethernet-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>.
386 tristate "MVME147 (Lance) Ethernet support"
390 Support for the on-board Ethernet interface on the Motorola MVME147
391 single-board computer. Say Y here to include the
392 driver for this chip in your kernel.
393 To compile this driver as a module, choose M here.
396 tristate "MVME16x Ethernet support"
399 This is the driver for the Ethernet interface on the Motorola
400 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
401 driver for this chip in your kernel.
402 To compile this driver as a module, choose M here.
405 tristate "BVME6000 Ethernet support"
408 This is the driver for the Ethernet interface on BVME4000 and
409 BVME6000 VME boards. Say Y here to include the driver for this chip
411 To compile this driver as a module, choose M here.
414 tristate "Atari Lance support"
417 Say Y to include support for several Atari Ethernet adapters based
418 on the AMD Lance chipset: RieblCard (with or without battery), or
419 PAMCard VME (also the version by Rhotron, with different addresses).
422 tristate "Sun3/Sun3x on-board LANCE support"
423 depends on SUN3 || SUN3X
425 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
426 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
427 here to compile in the Linux driver for this and enable Ethernet.
428 General Linux information on the Sun 3 and 3x series (now
430 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
432 If you're not building a kernel for a Sun 3, say N.
435 bool "Sun3 on-board Intel 82586 support"
438 This driver enables support for the on-board Intel 82586 based
439 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
440 that this driver does not support 82586-based adapters on additional
444 bool "HP on-board LANCE support"
448 If you want to use the builtin "LANCE" Ethernet controller on an
449 HP300 machine, say Y here.
452 tristate "Lasi ethernet"
455 Say Y here to support the builtin Intel 82596 ethernet controller
456 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
459 tristate "SNI RM ethernet"
460 depends on NET_ETHERNET && SNI_RM
462 Say Y here to support the on-board Intel 82596 ethernet controller
463 built into SNI RM machines.
466 tristate "Korina (IDT RC32434) Ethernet support"
467 depends on NET_ETHERNET && MIKROTIK_RB532
469 If you have a Mikrotik RouterBoard 500 or IDT RC32434
470 based system say Y. Otherwise say N.
472 config MIPS_JAZZ_SONIC
473 tristate "MIPS JAZZ onboard SONIC Ethernet support"
476 This is the driver for the onboard card of MIPS Magnum 4000,
477 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
479 config XTENSA_XT2000_SONIC
480 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
481 depends on XTENSA_PLATFORM_XT2000
483 This is the driver for the onboard card of the Xtensa XT2000 board.
485 config MIPS_AU1X00_ENET
486 bool "MIPS AU1000 Ethernet support"
487 depends on SOC_AU1X00
491 If you have an Alchemy Semi AU1X00 based system
492 say Y. Otherwise, say N.
495 bool "SGI IOC3 Ethernet"
496 depends on PCI && SGI_IP27
500 If you have a network (Ethernet) card of this type, say Y and read
501 the Ethernet-HOWTO, available from
502 <http://www.tldp.org/docs.html#howto>.
505 tristate "MIPS simulator Network device"
508 The MIPSNET device is a simple Ethernet network device which is
509 emulated by the MIPS Simulator.
510 If you are not using a MIPSsim or are unsure, say N.
512 config SGI_O2MACE_ETH
513 tristate "SGI O2 MACE Fast Ethernet support"
514 depends on SGI_IP32=y
517 tristate "National DP83902AV support"
521 Support for cards based on the National Semiconductor DP83902AV
522 ST-NIC Serial Network Interface Controller for Twisted Pair. This
523 is a 10Mbit/sec Ethernet controller. Product overview and specs at
524 <http://www.national.com/pf/DP/DP83902A.html>.
529 tristate "Renesas SuperH Ethernet support"
530 depends on SUPERH && \
531 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
532 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
539 Renesas SuperH Ethernet device driver.
540 This driver support SH7710, SH7712, SH7763, SH7619, and SH7724.
543 tristate "Sun LANCE support"
547 This driver supports the "le" interface present on all 32-bit Sparc
548 systems, on some older Ultra systems and as an Sbus option. These
549 cards are based on the AMD Lance chipset, which is better known
550 via the NE2100 cards.
552 To compile this driver as a module, choose M here: the module
553 will be called sunlance.
556 tristate "Sun Happy Meal 10/100baseT support"
557 depends on SBUS || PCI
560 This driver supports the "hme" interface present on most Ultra
561 systems and as an option on older Sbus systems. This driver supports
562 both PCI and Sbus devices. This driver also supports the "qfe" quad
563 100baseT device available in both PCI and Sbus configurations.
565 To compile this driver as a module, choose M here: the module
566 will be called sunhme.
569 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
570 depends on SBUS && EXPERIMENTAL
573 This driver supports the "be" interface available as an Sbus option.
574 This is Sun's older 100baseT Ethernet device.
576 To compile this driver as a module, choose M here: the module
577 will be called sunbmac.
580 tristate "Sun QuadEthernet support"
584 This driver supports the "qe" 10baseT Ethernet device, available as
585 an Sbus option. Note that this is not the same as Quad FastEthernet
586 "qfe" which is supported by the Happy Meal driver instead.
588 To compile this driver as a module, choose M here: the module
589 will be called sunqe.
592 tristate "Sun GEM support"
596 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
597 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
600 tristate "Sun Cassini support"
604 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
605 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
608 tristate "Sun Virtual Network support"
611 Support for virtual network devices under Sun Logical Domains.
613 config NET_VENDOR_3COM
615 depends on ISA || EISA || MCA || PCI
617 If you have a network (Ethernet) card belonging to this class, say Y
618 and read the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 Note that the answer to this question doesn't directly affect the
622 kernel: saying N will just cause the configurator to skip all
623 the questions about 3COM cards. If you say Y, you will be asked for
624 your specific card in the following questions.
627 tristate "3c501 \"EtherLink\" support"
628 depends on NET_VENDOR_3COM && ISA
630 If you have a network (Ethernet) card of this type, say Y and read
631 the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
633 new card, since the 3c501 is slow, broken, and obsolete: you will
634 have problems. Some people suggest to ping ("man ping") a nearby
635 machine every minute ("man cron") when using this card.
637 To compile this driver as a module, choose M here. The module
638 will be called 3c501.
641 tristate "3c503 \"EtherLink II\" support"
642 depends on NET_VENDOR_3COM && ISA
645 If you have a network (Ethernet) card of this type, say Y and read
646 the Ethernet-HOWTO, available from
647 <http://www.tldp.org/docs.html#howto>.
649 To compile this driver as a module, choose M here. The module
650 will be called 3c503.
653 tristate "3c505 \"EtherLink Plus\" support"
654 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
656 Information about this network (Ethernet) card can be found in
657 <file:Documentation/networking/3c505.txt>. If you have a card of
658 this type, say Y and read the Ethernet-HOWTO, available from
659 <http://www.tldp.org/docs.html#howto>.
661 To compile this driver as a module, choose M here. The module
662 will be called 3c505.
665 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
666 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
668 If you have a network (Ethernet) card of this type, say Y and read
669 the Ethernet-HOWTO, available from
670 <http://www.tldp.org/docs.html#howto>.
672 To compile this driver as a module, choose M here. The module
673 will be called 3c507.
676 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
677 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
679 If you have a network (Ethernet) card belonging to the 3Com
680 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
681 from <http://www.tldp.org/docs.html#howto>.
683 If your card is not working you may need to use the DOS
684 setup disk to disable Plug & Play mode, and to select the default
687 To compile this driver as a module, choose M here. The module
688 will be called 3c509.
691 tristate "3c515 ISA \"Fast EtherLink\""
692 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
694 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
695 network card, say Y and read the Ethernet-HOWTO, available from
696 <http://www.tldp.org/docs.html#howto>.
698 To compile this driver as a module, choose M here. The module
699 will be called 3c515.
702 tristate "3c523 \"EtherLink/MC\" support"
703 depends on NET_VENDOR_3COM && MCA_LEGACY
705 If you have a network (Ethernet) card of this type, say Y and read
706 the Ethernet-HOWTO, available from
707 <http://www.tldp.org/docs.html#howto>.
709 To compile this driver as a module, choose M here. The module
710 will be called 3c523.
713 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
714 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
716 If you have a network (Ethernet) card of this type, say Y and read
717 the Ethernet-HOWTO, available from
718 <http://www.tldp.org/docs.html#howto>.
720 To compile this driver as a module, choose M here. The module
721 will be called 3c527.
724 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
725 depends on NET_VENDOR_3COM && (PCI || EISA)
728 This option enables driver support for a large number of 10Mbps and
729 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
731 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
732 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
733 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
734 "Tornado" (3c905) PCI
735 "Hurricane" (3c555/3cSOHO) PCI
737 If you have such a card, say Y and read the Ethernet-HOWTO,
738 available from <http://www.tldp.org/docs.html#howto>. More
739 specific information is in
740 <file:Documentation/networking/vortex.txt> and in the comments at
741 the beginning of <file:drivers/net/3c59x.c>.
743 To compile this support as a module, choose M here.
746 tristate "3cr990 series \"Typhoon\" support"
747 depends on NET_VENDOR_3COM && PCI
750 This option enables driver support for the 3cr990 series of cards:
752 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
753 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
754 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
756 If you have a network (Ethernet) card of this type, say Y and read
757 the Ethernet-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>.
760 To compile this driver as a module, choose M here. The module
761 will be called typhoon.
764 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
765 depends on ISA && ISA_DMA_API
767 If you have a network (Ethernet) card of this type, say Y and read
768 the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
772 To compile this driver as a module, choose M here: the module
773 will be called lance. This is recommended.
775 config NET_VENDOR_SMC
776 bool "Western Digital/SMC cards"
777 depends on ISA || MCA || EISA || MAC
779 If you have a network (Ethernet) card belonging to this class, say Y
780 and read the Ethernet-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 Note that the answer to this question doesn't directly affect the
784 kernel: saying N will just cause the configurator to skip all
785 the questions about Western Digital cards. If you say Y, you will be
786 asked for your specific card in the following questions.
789 tristate "WD80*3 support"
790 depends on NET_VENDOR_SMC && ISA
793 If you have a network (Ethernet) card of this type, say Y and read
794 the Ethernet-HOWTO, available from
795 <http://www.tldp.org/docs.html#howto>.
797 To compile this driver as a module, choose M here. The module
801 tristate "SMC Ultra MCA support"
802 depends on NET_VENDOR_SMC && MCA
805 If you have a network (Ethernet) card of this type and are running
806 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
807 available from <http://www.tldp.org/docs.html#howto>.
809 To compile this driver as a module, choose M here. The module
810 will be called smc-mca.
813 tristate "SMC Ultra support"
814 depends on NET_VENDOR_SMC && ISA
817 If you have a network (Ethernet) card of this type, say Y and read
818 the Ethernet-HOWTO, available from
819 <http://www.tldp.org/docs.html#howto>.
821 Important: There have been many reports that, with some motherboards
822 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
823 such as some BusLogic models) causes corruption problems with many
824 operating systems. The Linux smc-ultra driver has a work-around for
825 this but keep it in mind if you have such a SCSI card and have
828 To compile this driver as a module, choose M here. The module
829 will be called smc-ultra.
832 tristate "SMC Ultra32 EISA support"
833 depends on NET_VENDOR_SMC && EISA
836 If you have a network (Ethernet) card of this type, say Y and read
837 the Ethernet-HOWTO, available from
838 <http://www.tldp.org/docs.html#howto>.
840 To compile this driver as a module, choose M here. The module
841 will be called smc-ultra32.
844 tristate "Blackfin on-chip MAC support"
845 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
849 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
851 This is the driver for Blackfin on-chip mac device. Say Y if you want it
852 compiled into the kernel. This driver is also available as a module
853 ( = code which can be inserted in and removed from the running kernel
854 whenever you want). The module will be called bfin_mac.
856 config BFIN_MAC_USE_L1
857 bool "Use L1 memory for rx/tx packets"
858 depends on BFIN_MAC && (BF527 || BF537)
861 To get maximum network performance, you should use L1 memory as rx/tx buffers.
862 Say N here if you want to reserve L1 memory for other uses.
864 config BFIN_TX_DESC_NUM
865 int "Number of transmit buffer packets"
867 range 6 10 if BFIN_MAC_USE_L1
871 Set the number of buffer packets used in driver.
873 config BFIN_RX_DESC_NUM
874 int "Number of receive buffer packets"
876 range 20 100 if BFIN_MAC_USE_L1
880 Set the number of buffer packets used in driver.
883 bool "RMII PHY Interface"
885 default y if BFIN527_EZKIT
886 default n if BFIN537_STAMP
888 Use Reduced PHY MII Interface
891 tristate "SMC 9194 support"
892 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
895 This is support for the SMC9xxx based Ethernet cards. Choose this
896 option if you have a DELL laptop with the docking station, or
897 another SMC9192/9194 based chipset. Say Y if you want it compiled
898 into the kernel, and read the file
899 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
900 available from <http://www.tldp.org/docs.html#howto>.
902 To compile this driver as a module, choose M here. The module
903 will be called smc9194.
906 tristate "SMC 91C9x/91C1xxx support"
909 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
910 MIPS || BLACKFIN || MN10300 || COLDFIRE
912 This is a driver for SMC's 91x series of Ethernet chipsets,
913 including the SMC91C94 and the SMC91C111. Say Y if you want it
914 compiled into the kernel, and read the file
915 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
916 available from <http://www.linuxdoc.org/docs.html#howto>.
918 This driver is also available as a module ( = code which can be
919 inserted in and removed from the running kernel whenever you want).
920 The module will be called smc91x. If you want to compile it as a
921 module, say M here and read <file:Documentation/kbuild/modules.txt>.
924 tristate "NetX Ethernet support"
928 This is support for the Hilscher netX builtin Ethernet ports
930 To compile this driver as a module, choose M here. The module
931 will be called netx-eth.
933 config TI_DAVINCI_EMAC
934 tristate "TI DaVinci EMAC Support"
935 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
938 This driver supports TI's DaVinci Ethernet .
940 To compile this driver as a module, choose M here: the module
941 will be called davinci_emac_driver. This is recommended.
944 tristate "DM9000 support"
945 depends on ARM || BLACKFIN || MIPS
949 Support for DM9000 chipset.
951 To compile this driver as a module, choose M here. The module
952 will be called dm9000.
954 config DM9000_DEBUGLEVEL
955 int "DM9000 maximum debug level"
959 The maximum level of debugging code compiled into the DM9000
962 config DM9000_FORCE_SIMPLE_PHY_POLL
963 bool "Force simple NSR based PHY polling"
966 This configuration forces the DM9000 to use the NSR's LinkStatus
967 bit to determine if the link is up or down instead of the more
968 costly MII PHY reads. Note, this will not work if the chip is
969 operating with an external PHY.
972 tristate "ENC28J60 support"
973 depends on EXPERIMENTAL && SPI && NET_ETHERNET
976 Support for the Microchip EN28J60 ethernet chip.
978 To compile this driver as a module, choose M here. The module will be
981 config ENC28J60_WRITEVERIFY
982 bool "Enable write verify"
985 Enable the verify after the buffer write useful for debugging purpose.
989 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
990 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
996 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
999 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1004 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1007 tristate "SMSC LAN911[5678] support"
1010 depends on ARM || SUPERH
1012 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1013 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1014 Say Y if you want it compiled into the kernel,
1015 and read the Ethernet-HOWTO, available from
1016 <http://www.linuxdoc.org/docs.html#howto>.
1018 This driver is also available as a module. The module will be
1019 called smc911x. If you want to compile it as a module, say M
1020 here and read <file:Documentation/kbuild/modules.txt>
1023 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1024 depends on ARM || SUPERH || BLACKFIN || MIPS
1029 Say Y here if you want support for SMSC LAN911x and LAN921x families
1030 of ethernet controllers.
1032 To compile this driver as a module, choose M here and read
1033 <file:Documentation/networking/net-modules.txt>. The module
1034 will be called smsc911x.
1036 config NET_VENDOR_RACAL
1037 bool "Racal-Interlan (Micom) NI cards"
1040 If you have a network (Ethernet) card belonging to this class, such
1041 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1042 available from <http://www.tldp.org/docs.html#howto>.
1044 Note that the answer to this question doesn't directly affect the
1045 kernel: saying N will just cause the configurator to skip all
1046 the questions about NI cards. If you say Y, you will be asked for
1047 your specific card in the following questions.
1050 tristate "NI5010 support (EXPERIMENTAL)"
1051 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1053 If you have a network (Ethernet) card of this type, say Y and read
1054 the Ethernet-HOWTO, available from
1055 <http://www.tldp.org/docs.html#howto>. Note that this is still
1058 To compile this driver as a module, choose M here. The module
1059 will be called ni5010.
1062 tristate "NI5210 support"
1063 depends on NET_VENDOR_RACAL && ISA
1065 If you have a network (Ethernet) card of this type, say Y and read
1066 the Ethernet-HOWTO, available from
1067 <http://www.tldp.org/docs.html#howto>.
1069 To compile this driver as a module, choose M here. The module
1070 will be called ni52.
1073 tristate "NI6510 support"
1074 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1076 If you have a network (Ethernet) card of this type, say Y and read
1077 the Ethernet-HOWTO, available from
1078 <http://www.tldp.org/docs.html#howto>.
1080 To compile this driver as a module, choose M here. The module
1081 will be called ni65.
1084 tristate "Dave ethernet support (DNET)"
1085 depends on NET_ETHERNET && HAS_IOMEM
1088 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1089 Say Y to include support for the DNET chip.
1091 To compile this driver as a module, choose M here: the module
1092 will be called dnet.
1094 source "drivers/net/tulip/Kconfig"
1097 tristate "AT1700/1720 support (EXPERIMENTAL)"
1098 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1101 If you have a network (Ethernet) card of this type, say Y and read
1102 the Ethernet-HOWTO, available from
1103 <http://www.tldp.org/docs.html#howto>.
1105 To compile this driver as a module, choose M here. The module
1106 will be called at1700.
1109 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1110 depends on ISA || EISA || MCA
1113 If you have a network (Ethernet) card of this type, say Y and read
1114 the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto> as well as
1116 <file:drivers/net/depca.c>.
1118 To compile this driver as a module, choose M here. The module
1119 will be called depca.
1122 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1123 depends on ISA || EISA || PCI
1125 If you have a network (Ethernet) card of this type, say Y and read
1126 the Ethernet-HOWTO, available from
1127 <http://www.tldp.org/docs.html#howto>.
1129 To compile this driver as a module, choose M here. The module
1130 will be called hp100.
1133 bool "Other ISA cards"
1136 If your network (Ethernet) card hasn't been mentioned yet and its
1137 bus system (that's the way the cards talks to the other components
1138 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1139 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1140 available from <http://www.tldp.org/docs.html#howto>.
1144 Note that the answer to this question doesn't directly affect the
1145 kernel: saying N will just cause the configurator to skip all
1146 the remaining ISA network card questions. If you say Y, you will be
1147 asked for your specific card in the following questions.
1150 tristate "Cabletron E21xx support"
1154 If you have a network (Ethernet) card of this type, say Y and read
1155 the Ethernet-HOWTO, available from
1156 <http://www.tldp.org/docs.html#howto>.
1158 To compile this driver as a module, choose M here. The module
1159 will be called e2100.
1162 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1166 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1167 cards. If this is for you, say Y and read
1168 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1169 well as the Ethernet-HOWTO, available from
1170 <http://www.tldp.org/docs.html#howto>.
1172 To compile this driver as a module, choose M here. The module
1173 will be called ewrk3.
1176 tristate "EtherExpress 16 support"
1179 If you have an EtherExpress16 network (Ethernet) card, say Y and
1180 read the Ethernet-HOWTO, available from
1181 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1182 EtherExpress16 card used to be regarded as a very poor choice
1183 because the driver was very unreliable. We now have a new driver
1184 that should do better.
1186 To compile this driver as a module, choose M here. The module
1187 will be called eexpress.
1190 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1193 If you have a network (Ethernet) card of this type, say Y. This
1194 driver supports Intel i82595{FX,TX} based boards. Note however
1195 that the EtherExpress PRO/100 Ethernet card has its own separate
1196 driver. Please read the Ethernet-HOWTO, available from
1197 <http://www.tldp.org/docs.html#howto>.
1199 To compile this driver as a module, choose M here. The module
1200 will be called eepro.
1203 tristate "HP PCLAN+ (27247B and 27252A) support"
1207 If you have a network (Ethernet) card of this type, say Y and read
1208 the Ethernet-HOWTO, available from
1209 <http://www.tldp.org/docs.html#howto>.
1211 To compile this driver as a module, choose M here. The module
1212 will be called hp-plus.
1215 tristate "HP PCLAN (27245 and other 27xxx series) support"
1219 If you have a network (Ethernet) card of this type, say Y and read
1220 the Ethernet-HOWTO, available from
1221 <http://www.tldp.org/docs.html#howto>.
1223 To compile this driver as a module, choose M here. The module
1227 tristate "LP486E on board Ethernet"
1230 Say Y here to support the 82596-based on-board Ethernet controller
1231 for the Panther motherboard, which is one of the two shipped in the
1232 Intel Professional Workstation.
1235 tristate "ICL EtherTeam 16i/32 support"
1238 If you have a network (Ethernet) card of this type, say Y and read
1239 the Ethernet-HOWTO, available from
1240 <http://www.tldp.org/docs.html#howto>.
1242 To compile this driver as a module, choose M here. The module
1243 will be called eth16i.
1246 tristate "NE2000/NE1000 support"
1247 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1250 If you have a network (Ethernet) card of this type, say Y and read
1251 the Ethernet-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1253 without a specific driver are compatible with NE2000.
1255 If you have a PCI NE2000 card however, say N here and Y to "PCI
1256 NE2000 and clone support" under "EISA, VLB, PCI and on board
1257 controllers" below. If you have a NE2000 card and are running on
1258 an MCA system (a bus system used on some IBM PS/2 computers and
1259 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1262 To compile this driver as a module, choose M here. The module
1266 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1267 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1269 The Zenith Z-Note notebook computer has a built-in network
1270 (Ethernet) card, and this is the Linux driver for it. Note that the
1271 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1272 by this driver. Read the Ethernet-HOWTO, available from
1273 <http://www.tldp.org/docs.html#howto>.
1276 tristate "SEEQ8005 support (EXPERIMENTAL)"
1277 depends on NET_ISA && EXPERIMENTAL
1279 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1280 is for you, read the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1283 To compile this driver as a module, choose M here. The module
1284 will be called seeq8005.
1287 tristate "NE/2 (ne2000 MCA version) support"
1288 depends on MCA_LEGACY
1291 If you have a network (Ethernet) card of this type, say Y and read
1292 the Ethernet-HOWTO, available from
1293 <http://www.tldp.org/docs.html#howto>.
1295 To compile this driver as a module, choose M here. The module
1299 tristate "IBM LAN Adapter/A support"
1302 This is a Micro Channel Ethernet adapter. You need to set
1303 CONFIG_MCA to use this driver. It is both available as an in-kernel
1304 driver and as a module.
1306 To compile this driver as a module, choose M here. The only
1307 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1308 will both support 16K and 32K memory windows, however a 32K window
1309 gives a better security against packet losses. Usage of multiple
1310 boards with this driver should be possible, but has not been tested
1311 up to now due to lack of hardware.
1314 tristate "IBM LAN Virtual Ethernet support"
1315 depends on PPC_PSERIES
1317 This driver supports virtual ethernet adapters on newer IBM iSeries
1318 and pSeries systems.
1320 To compile this driver as a module, choose M here. The module will
1323 source "drivers/net/ibm_newemac/Kconfig"
1326 bool "EISA, VLB, PCI and on board controllers"
1327 depends on ISA || EISA || PCI
1329 This is another class of network cards which attach directly to the
1330 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1331 available from <http://www.tldp.org/docs.html#howto>.
1333 Note that the answer to this question doesn't directly affect the
1334 kernel: saying N will just cause the configurator to skip all
1335 the questions about this class of network cards. If you say Y, you
1336 will be asked for your specific card in the following questions. If
1337 you are unsure, say Y.
1340 tristate "AMD PCnet32 PCI support"
1341 depends on NET_PCI && PCI
1345 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1346 answer Y here and read the Ethernet-HOWTO, available from
1347 <http://www.tldp.org/docs.html#howto>.
1349 To compile this driver as a module, choose M here. The module
1350 will be called pcnet32.
1353 tristate "AMD 8111 (new PCI lance) support"
1354 depends on NET_PCI && PCI
1358 If you have an AMD 8111-based PCI lance ethernet card,
1359 answer Y here and read the Ethernet-HOWTO, available from
1360 <http://www.tldp.org/docs.html#howto>.
1362 To compile this driver as a module, choose M here. The module
1363 will be called amd8111e.
1365 config ADAPTEC_STARFIRE
1366 tristate "Adaptec Starfire/DuraLAN support"
1367 depends on NET_PCI && PCI
1371 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1372 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1373 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1376 To compile this driver as a module, choose M here: the module
1377 will be called starfire. This is recommended.
1380 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1381 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1384 If you have a network (Ethernet) card of this type, say Y and read
1385 the Ethernet-HOWTO, available from
1386 <http://www.tldp.org/docs.html#howto>.
1388 To compile this driver as a module, choose M here. The module
1389 will be called ac3200.
1392 tristate "Micrel KSZ8841/2 PCI"
1393 depends on NET_PCI && PCI
1397 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1399 To compile this driver as a module, choose M here. The module
1400 will be called ksz884x.
1403 tristate "Apricot Xen-II on board Ethernet"
1404 depends on NET_PCI && ISA
1406 If you have a network (Ethernet) controller of this type, say Y and
1407 read the Ethernet-HOWTO, available from
1408 <http://www.tldp.org/docs.html#howto>.
1410 To compile this driver as a module, choose M here. The module
1411 will be called apricot.
1414 tristate "Broadcom 440x/47xx ethernet support"
1415 depends on SSB_POSSIBLE && HAS_DMA
1419 If you have a network (Ethernet) controller of this type, say Y
1420 or M and read the Ethernet-HOWTO, available from
1421 <http://www.tldp.org/docs.html#howto>.
1423 To compile this driver as a module, choose M here. The module
1426 # Auto-select SSB PCI-HOST support, if possible
1427 config B44_PCI_AUTOSELECT
1429 depends on B44 && SSB_PCIHOST_POSSIBLE
1433 # Auto-select SSB PCICORE driver, if possible
1434 config B44_PCICORE_AUTOSELECT
1436 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1437 select SSB_DRIVER_PCICORE
1442 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1446 tristate "nForce Ethernet support"
1447 depends on NET_PCI && PCI
1449 If you have a network (Ethernet) controller of this type, say Y and
1450 read the Ethernet-HOWTO, available from
1451 <http://www.tldp.org/docs.html#howto>.
1453 To compile this driver as a module, choose M here. The module
1454 will be called forcedeth.
1456 config FORCEDETH_NAPI
1457 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1458 depends on FORCEDETH && EXPERIMENTAL
1460 NAPI is a new driver API designed to reduce CPU and interrupt load
1461 when the driver is receiving lots of packets from the card. It is
1462 still somewhat experimental and thus not yet enabled by default.
1464 If your estimated Rx load is 10kpps or more, or if the card will be
1465 deployed on potentially unfriendly networks (e.g. in a firewall),
1471 tristate "CS89x0 support"
1472 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1473 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1475 Support for CS89x0 chipset based Ethernet cards. If you have a
1476 network (Ethernet) card of this type, say Y and read the
1477 Ethernet-HOWTO, available from
1478 <http://www.tldp.org/docs.html#howto> as well as
1479 <file:Documentation/networking/cs89x0.txt>.
1481 To compile this driver as a module, choose M here. The module
1482 will be called cs89x0.
1484 config CS89x0_NONISA_IRQ
1486 depends on CS89x0 != n
1487 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1490 tristate "TOSHIBA TC35815 Ethernet support"
1491 depends on NET_PCI && PCI && MIPS
1495 tristate "Intel(R) PRO/100+ support"
1496 depends on NET_PCI && PCI
1499 This driver supports Intel(R) PRO/100 family of adapters.
1500 To verify that your adapter is supported, find the board ID number
1501 on the adapter. Look for a label that has a barcode and a number
1502 in the format 123456-001 (six digits hyphen three digits).
1504 Use the above information and the Adapter & Driver ID Guide at:
1506 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1508 to identify the adapter.
1510 For the latest Intel PRO/100 network driver for Linux, see:
1512 <http://appsr.intel.com/scripts-df/support_intel.asp>
1514 More specific information on configuring the driver is in
1515 <file:Documentation/networking/e100.txt>.
1517 To compile this driver as a module, choose M here. The module
1518 will be called e100.
1521 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1522 depends on NET_PCI && EISA && EXPERIMENTAL
1525 If you have a network (Ethernet) card of this type, say Y and read
1526 the Ethernet-HOWTO, available from
1527 <http://www.tldp.org/docs.html#howto>.
1529 To compile this driver as a module, choose M here. The module
1530 will be called lne390.
1533 tristate "Myson MTD-8xx PCI Ethernet support"
1534 depends on NET_PCI && PCI
1538 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1539 cards. Specifications and data at
1540 <http://www.myson.com.hk/mtd/datasheet/>.
1543 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1544 depends on NET_PCI && PCI
1547 This driver is for the National Semiconductor DP83810 series,
1548 which is used in cards from PureData, NetGear, Linksys
1549 and others, including the 83815 chip.
1550 More specific information and updates are available from
1551 <http://www.scyld.com/network/natsemi.html>.
1554 tristate "PCI NE2000 and clones support (see help)"
1555 depends on NET_PCI && PCI
1558 This driver is for NE2000 compatible PCI cards. It will not work
1559 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1560 support" below). If you have a PCI NE2000 network (Ethernet) card,
1561 say Y and read the Ethernet-HOWTO, available from
1562 <http://www.tldp.org/docs.html#howto>.
1564 This driver also works for the following NE2000 clone cards:
1565 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1566 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1567 Holtek HT80232 Holtek HT80229
1569 To compile this driver as a module, choose M here. The module
1570 will be called ne2k-pci.
1573 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1574 depends on NET_PCI && EISA && EXPERIMENTAL
1577 If you have a network (Ethernet) card of this type, say Y and read
1578 the Ethernet-HOWTO, available from
1579 <http://www.tldp.org/docs.html#howto>. Note that this driver
1580 will NOT WORK for NE3200 cards as they are completely different.
1582 To compile this driver as a module, choose M here. The module
1583 will be called ne3210.
1586 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1587 depends on NET_PCI && EISA && EXPERIMENTAL
1590 If you have a network (Ethernet) card of this type, say Y and read
1591 the Ethernet-HOWTO, available from
1592 <http://www.tldp.org/docs.html#howto>.
1594 To compile this driver as a module, choose M here. The module
1595 will be called es3210.
1598 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1599 depends on NET_PCI && PCI && EXPERIMENTAL
1603 This is a driver for the Fast Ethernet PCI network cards based on
1604 the RTL8139C+ chips. If you have one of those, say Y and read
1605 the Ethernet-HOWTO, available from
1606 <http://www.tldp.org/docs.html#howto>.
1608 To compile this driver as a module, choose M here: the module
1609 will be called 8139cp. This is recommended.
1612 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1613 depends on NET_PCI && PCI
1617 This is a driver for the Fast Ethernet PCI network cards based on
1618 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1619 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1621 To compile this driver as a module, choose M here: the module
1622 will be called 8139too. This is recommended.
1625 bool "Use PIO instead of MMIO"
1629 This instructs the driver to use programmed I/O ports (PIO) instead
1630 of PCI shared memory (MMIO). This can possibly solve some problems
1631 in case your mainboard has memory consistency issues. If unsure,
1634 config 8139TOO_TUNE_TWISTER
1635 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1638 This implements a function which might come in handy in case you
1639 are using low quality on long cabling. It is required for RealTek
1640 RTL-8139 revision K boards, and totally unused otherwise. It tries
1641 to match the transceiver to the cable characteristics. This is
1642 experimental since hardly documented by the manufacturer.
1646 bool "Support for older RTL-8129/8130 boards"
1649 This enables support for the older and uncommon RTL-8129 and
1650 RTL-8130 chips, which support MII via an external transceiver,
1651 instead of an internal one. Disabling this option will save some
1652 memory by making the code size smaller. If unsure, say Y.
1654 config 8139_OLD_RX_RESET
1655 bool "Use older RX-reset method"
1658 The 8139too driver was recently updated to contain a more rapid
1659 reset sequence, in the face of severe receive errors. This "new"
1660 RX-reset method should be adequate for all boards. But if you
1661 experience problems, you can enable this option to restore the
1662 old RX-reset behavior. If unsure, say N.
1665 tristate "RDC R6040 Fast Ethernet Adapter support"
1666 depends on NET_PCI && PCI
1670 This is a driver for the R6040 Fast Ethernet MACs found in the
1671 the RDC R-321x System-on-chips.
1673 To compile this driver as a module, choose M here: the module
1674 will be called r6040. This is recommended.
1677 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1678 depends on NET_PCI && PCI
1682 This is a driver for the Fast Ethernet PCI network cards based on
1683 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1684 SiS 630 and SiS 540 chipsets.
1686 This driver also supports AMD 79C901 HomePNA so that you can use
1687 your phone line as a network cable.
1689 To compile this driver as a module, choose M here: the module
1690 will be called sis900. This is recommended.
1693 tristate "SMC EtherPower II"
1694 depends on NET_PCI && PCI
1698 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1699 which is based on the SMC83c17x (EPIC/100).
1700 More specific information and updates are available from
1701 <http://www.scyld.com/network/epic100.html>.
1704 tristate "SMSC LAN9420 PCI ethernet adapter support"
1705 depends on NET_PCI && PCI
1710 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1711 Say Y if you want it compiled into the kernel,
1712 and read the Ethernet-HOWTO, available from
1713 <http://www.linuxdoc.org/docs.html#howto>.
1715 This driver is also available as a module. The module will be
1716 called smsc9420. If you want to compile it as a module, say M
1717 here and read <file:Documentation/kbuild/modules.txt>
1720 tristate "Sundance Alta support"
1721 depends on NET_PCI && PCI
1725 This driver is for the Sundance "Alta" chip.
1726 More specific information and updates are available from
1727 <http://www.scyld.com/network/sundance.html>.
1729 config SUNDANCE_MMIO
1730 bool "Use MMIO instead of PIO"
1733 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1734 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1735 is known to solve bugs on certain chips.
1740 tristate "TI ThunderLAN support"
1741 depends on NET_PCI && (PCI || EISA)
1743 If you have a PCI Ethernet network card based on the ThunderLAN chip
1744 which is supported by this driver, say Y and read the
1745 Ethernet-HOWTO, available from
1746 <http://www.tldp.org/docs.html#howto>.
1748 Devices currently supported by this driver are Compaq Netelligent,
1749 Compaq NetFlex and Olicom cards. Please read the file
1750 <file:Documentation/networking/tlan.txt> for more details.
1752 To compile this driver as a module, choose M here. The module
1753 will be called tlan.
1755 Please email feedback to <torben.mathiasen@compaq.com>.
1758 tristate "Micrel KSZ8842"
1759 depends on HAS_IOMEM
1761 This platform driver is for Micrel KSZ8842 / KS8842
1762 2-port ethernet switch chip (managed, VLAN, QoS).
1765 tristate "Micrel KS8851 SPI"
1770 SPI driver for Micrel KS8851 SPI attached network chip.
1773 tristate "Micrel KS8851 MLL"
1774 depends on HAS_IOMEM
1777 This platform driver is for Micrel KS8851 Address/data bus
1778 multiplexed network chip.
1781 tristate "VIA Rhine support"
1782 depends on NET_PCI && PCI
1786 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1787 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1788 Ethernet functions can also be found integrated on South Bridges
1791 To compile this driver as a module, choose M here. The module
1792 will be called via-rhine.
1794 config VIA_RHINE_MMIO
1795 bool "Use MMIO instead of PIO"
1796 depends on VIA_RHINE
1798 This instructs the driver to use PCI shared memory (MMIO) instead of
1799 programmed I/O ports (PIO). Enabling this gives an improvement in
1800 processing time in parts of the driver.
1805 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1806 depends on NET_PCI && PCI && EXPERIMENTAL
1809 This is a driver for the Fast Ethernet PCI network cards based on
1810 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1811 have one of these, say Y here.
1813 To compile this driver as a module, choose M here: the module
1814 will be called sc92031. This is recommended.
1817 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1818 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1821 TI AR7 CPMAC Ethernet support
1824 bool "Pocket and portable adapters"
1827 Cute little network (Ethernet) devices which attach to the parallel
1828 port ("pocket adapters"), commonly used with laptops. If you have
1829 one of those, say Y and read the Ethernet-HOWTO, available from
1830 <http://www.tldp.org/docs.html#howto>.
1832 If you want to plug a network (or some other) card into the PCMCIA
1833 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1834 credit card size extension cards used by all modern laptops), you
1835 need the pcmcia-cs package (location contained in the file
1836 <file:Documentation/Changes>) and you can say N here.
1838 Laptop users should read the Linux Laptop home page at
1839 <http://www.linux-on-laptops.com/> or
1840 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1842 Note that the answer to this question doesn't directly affect the
1843 kernel: saying N will just cause the configurator to skip all
1844 the questions about this class of network devices. If you say Y, you
1845 will be asked for your specific device in the following questions.
1848 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1849 depends on NET_POCKET && PARPORT && X86
1852 This is a network (Ethernet) device which attaches to your parallel
1853 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1854 available from <http://www.tldp.org/docs.html#howto>, if you
1855 want to use this. If you intend to use this driver, you should have
1856 said N to the "Parallel printer support", because the two drivers
1857 don't like each other.
1859 To compile this driver as a module, choose M here: the module
1863 tristate "D-Link DE600 pocket adapter support"
1864 depends on NET_POCKET && PARPORT
1866 This is a network (Ethernet) device which attaches to your parallel
1867 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1868 Ethernet-HOWTO, available from
1869 <http://www.tldp.org/docs.html#howto>, if you want to use
1870 this. It is possible to have several devices share a single parallel
1871 port and it is safe to compile the corresponding drivers into the
1874 To compile this driver as a module, choose M here: the module
1875 will be called de600.
1878 tristate "D-Link DE620 pocket adapter support"
1879 depends on NET_POCKET && PARPORT
1881 This is a network (Ethernet) device which attaches to your parallel
1882 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1883 Ethernet-HOWTO, available from
1884 <http://www.tldp.org/docs.html#howto>, if you want to use
1885 this. It is possible to have several devices share a single parallel
1886 port and it is safe to compile the corresponding drivers into the
1889 To compile this driver as a module, choose M here: the module
1890 will be called de620.
1893 tristate "SGI Seeq ethernet controller support"
1894 depends on SGI_HAS_SEEQ
1896 Say Y here if you have an Seeq based Ethernet network card. This is
1897 used in many Silicon Graphics machines.
1900 tristate "DEC LANCE ethernet controller support"
1901 depends on MACH_DECSTATION
1904 This driver is for the series of Ethernet controllers produced by
1905 DEC (now Compaq) based on the AMD Lance chipset, including the
1906 DEPCA series. (This chipset is better known via the NE2100 cards.)
1909 bool "Motorola 68360 ethernet controller"
1912 Say Y here if you want to use the built-in ethernet controller of
1913 the Motorola 68360 processor.
1916 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1917 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1918 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5
1920 Say Y here if you want to use the built-in 10/100 Fast ethernet
1921 controller on some Motorola ColdFire and Freescale i.MX processors.
1924 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1927 Say Y here if you want to use the second built-in 10/100 Fast
1928 ethernet controller on some Motorola ColdFire processors.
1931 tristate "MPC52xx FEC driver"
1932 depends on PPC_MPC52xx && PPC_BESTCOMM
1935 select PPC_BESTCOMM_FEC
1937 This option enables support for the MPC5200's on-chip
1938 Fast Ethernet Controller
1939 If compiled as module, it will be called fec_mpc52xx.
1941 config FEC_MPC52xx_MDIO
1942 bool "MPC52xx FEC MDIO bus driver"
1943 depends on FEC_MPC52xx
1946 The MPC5200's FEC can connect to the Ethernet either with
1947 an external MII PHY chip or 10 Mbps 7-wire interface
1948 (Motorola? industry standard).
1949 If your board uses an external PHY connected to FEC, enable this.
1950 If not sure, enable.
1951 If compiled as module, it will be called fec_mpc52xx_phy.
1954 tristate "NE2000 compatible support for H8/300"
1957 Say Y here if you want to use the NE2000 compatible
1958 controller on the Renesas H8/300 processor.
1961 tristate "Atheros L2 Fast Ethernet support"
1966 This driver supports the Atheros L2 fast ethernet adapter.
1968 To compile this driver as a module, choose M here. The module
1969 will be called atl2.
1971 config XILINX_EMACLITE
1972 tristate "Xilinx 10/100 Ethernet Lite support"
1973 depends on PPC32 || MICROBLAZE
1976 This driver supports the 10/100 Ethernet Lite from Xilinx.
1979 tristate "Broadcom 63xx internal mac support"
1984 This driver supports the ethernet MACs in the Broadcom 63xx
1985 MIPS chipset family (BCM63XX).
1987 source "drivers/net/fs_enet/Kconfig"
1989 source "drivers/net/octeon/Kconfig"
1991 endif # NET_ETHERNET
1997 menuconfig NETDEV_1000
1998 bool "Ethernet (1000 Mbit)"
2002 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2003 type of Local Area Network (LAN) in universities and companies.
2005 Say Y here to get to see options for Gigabit Ethernet drivers.
2006 This option alone does not add any kernel code.
2007 Note that drivers supporting both 100 and 1000 MBit may be listed
2008 under "Ethernet (10 or 100MBit)" instead.
2010 If you say N, all options in this submenu will be skipped and disabled.
2015 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2018 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2019 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2020 adapter. The driver allows for using the Jumbo Frame option (9000
2021 bytes/frame) however it requires that your switches can handle this
2022 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2025 To compile this driver as a module, choose M here: the
2026 module will be called acenic.
2028 config ACENIC_OMIT_TIGON_I
2029 bool "Omit support for old Tigon I based AceNICs"
2032 Say Y here if you only have Tigon II based AceNICs and want to leave
2033 out support for the older Tigon I based cards which are no longer
2034 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2035 version)). This will reduce the size of the driver object by
2036 app. 100KB. If you are not sure whether your card is a Tigon I or a
2037 Tigon II, say N here.
2039 The safe and default value for this is N.
2042 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2046 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2048 D-Link DGE-550T Gigabit Ethernet Adapter.
2049 D-Link DL2000-based Gigabit Ethernet Adapter.
2050 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2052 To compile this driver as a module, choose M here: the
2053 module will be called dl2k.
2056 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2059 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2060 adapters. For more information on how to identify your adapter, go
2061 to the Adapter & Driver ID Guide at:
2063 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2065 For general information and support, go to the Intel support
2068 <http://support.intel.com>
2070 More specific information on configuring the driver is in
2071 <file:Documentation/networking/e1000.txt>.
2073 To compile this driver as a module, choose M here. The module
2074 will be called e1000.
2077 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2078 depends on PCI && (!SPARC32 || BROKEN)
2080 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2081 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2082 use the regular e1000 driver For more information on how to
2083 identify your adapter, go to the Adapter & Driver ID Guide at:
2085 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2087 For general information and support, go to the Intel support
2090 <http://support.intel.com>
2092 To compile this driver as a module, choose M here. The module
2093 will be called e1000e.
2096 tristate "IP1000 Gigabit Ethernet support"
2097 depends on PCI && EXPERIMENTAL
2100 This driver supports IP1000 gigabit Ethernet cards.
2102 To compile this driver as a module, choose M here: the module
2103 will be called ipg. This is recommended.
2106 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2109 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2110 adapters. For more information on how to identify your adapter, go
2111 to the Adapter & Driver ID Guide at:
2113 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2115 For general information and support, go to the Intel support
2118 <http://support.intel.com>
2120 More specific information on configuring the driver is in
2121 <file:Documentation/networking/e1000.txt>.
2123 To compile this driver as a module, choose M here. The module
2127 bool "Direct Cache Access (DCA) Support"
2129 depends on IGB && DCA && !(IGB=y && DCA=m)
2131 Say Y here if you want to use Direct Cache Access (DCA) in the
2132 driver. DCA is a method for warming the CPU cache before data
2133 is used, with the intent of lessening the impact of cache misses.
2136 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2139 This driver supports Intel(R) 82576 virtual functions. For more
2140 information on how to identify your adapter, go to the Adapter &
2143 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2145 For general information and support, go to the Intel support
2148 <http://support.intel.com>
2150 More specific information on configuring the driver is in
2151 <file:Documentation/networking/e1000.txt>.
2153 To compile this driver as a module, choose M here. The module
2154 will be called igbvf.
2156 source "drivers/net/ixp2000/Kconfig"
2159 tristate "MyriCOM Gigabit Ethernet support"
2162 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2164 To compile this driver as a module, choose M here: the module
2165 will be called myri_sbus. This is recommended.
2168 tristate "National Semiconductor DP83820 support"
2171 This is a driver for the National Semiconductor DP83820 series
2172 of gigabit ethernet MACs. Cards using this chipset include
2173 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2174 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2178 tristate "Packet Engines Hamachi GNIC-II support"
2182 If you have a Gigabit Ethernet card of this type, say Y and read
2183 the Ethernet-HOWTO, available from
2184 <http://www.tldp.org/docs.html#howto>.
2186 To compile this driver as a module, choose M here. The module will be
2190 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2191 depends on PCI && EXPERIMENTAL
2194 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2195 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2196 used by the Beowulf Linux cluster project. See
2197 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2198 information about this driver in particular and Beowulf in general.
2200 To compile this driver as a module, choose M here: the module
2201 will be called yellowfin. This is recommended.
2204 tristate "Realtek 8169 gigabit ethernet support"
2209 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2211 To compile this driver as a module, choose M here: the module
2212 will be called r8169. This is recommended.
2216 depends on R8169 && VLAN_8021Q
2218 Say Y here for the r8169 driver to support the functions required
2219 by the kernel 802.1Q code.
2224 tristate "SB1250 Gigabit Ethernet support"
2225 depends on SIBYTE_SB1xxx_SOC
2228 This driver supports Gigabit Ethernet interfaces based on the
2229 Broadcom SiByte family of System-On-a-Chip parts. They include
2230 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2233 To compile this driver as a module, choose M here: the module
2234 will be called sb1250-mac.
2237 tristate "SiS190/SiS191 gigabit ethernet support"
2242 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2243 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2244 appear in lan on motherboard designs which are based on SiS 965
2245 and SiS 966 south bridge.
2247 To compile this driver as a module, choose M here: the module
2248 will be called sis190. This is recommended.
2251 tristate "New SysKonnect GigaEthernet support"
2255 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2256 and related Gigabit Ethernet adapters. It is a new smaller driver
2257 with better performance and more complete ethtool support.
2259 It does not support the link failover and network management
2260 features that "portable" vendor supplied sk98lin driver does.
2262 This driver supports adapters based on the original Yukon chipset:
2263 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2264 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2266 It does not support the newer Yukon2 chipset: a separate driver,
2267 sky2, is provided for Yukon2-based adapters.
2269 To compile this driver as a module, choose M here: the module
2270 will be called skge. This is recommended.
2273 bool "Debugging interface"
2274 depends on SKGE && DEBUG_FS
2276 This option adds the ability to dump driver state for debugging.
2277 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2278 transmit and receive rings.
2283 tristate "SysKonnect Yukon2 support"
2287 This driver supports Gigabit Ethernet adapters based on the
2288 Marvell Yukon 2 chipset:
2289 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2290 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2292 There is companion driver for the older Marvell Yukon and
2293 Genesis based adapters: skge.
2295 To compile this driver as a module, choose M here: the module
2296 will be called sky2. This is recommended.
2299 bool "Debugging interface"
2300 depends on SKY2 && DEBUG_FS
2302 This option adds the ability to dump driver state for debugging.
2303 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2304 transmit and receive rings.
2309 tristate "VIA Velocity support"
2315 If you have a VIA "Velocity" based network card say Y here.
2317 To compile this driver as a module, choose M here. The module
2318 will be called via-velocity.
2321 tristate "Broadcom Tigon3 support"
2325 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2327 To compile this driver as a module, choose M here: the module
2328 will be called tg3. This is recommended.
2331 tristate "Broadcom NetXtremeII support"
2336 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2338 To compile this driver as a module, choose M here: the module
2339 will be called bnx2. This is recommended.
2342 tristate "Broadcom CNIC support"
2347 This driver supports offload features of Broadcom NetXtremeII
2348 gigabit Ethernet cards.
2350 To compile this driver as a module, choose M here: the module
2351 will be called cnic. This is recommended.
2354 tristate "Spider Gigabit Ethernet driver"
2355 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2358 This driver supports the Gigabit Ethernet chips present on the
2359 Cell Processor-Based Blades from IBM.
2362 tristate "Tundra TSI108 gigabit Ethernet support"
2363 depends on TSI108_BRIDGE
2365 This driver supports Tundra TSI108 gigabit Ethernet ports.
2366 To compile this driver as a module, choose M here: the module
2367 will be called tsi108_eth.
2370 tristate "PS3 Gigabit Ethernet driver"
2372 select PS3_SYS_MANAGER
2374 This driver supports the network device on the PS3 game
2375 console. This driver has built-in support for Ethernet.
2377 To compile this driver as a module, choose M here: the
2378 module will be called ps3_gelic.
2380 config GELIC_WIRELESS
2381 bool "PS3 Wireless support"
2383 depends on GELIC_NET
2386 This option adds the support for the wireless feature of PS3.
2387 If you have the wireless-less model of PS3 or have no plan to
2388 use wireless feature, disabling this option saves memory. As
2389 the driver automatically distinguishes the models, you can
2390 safely enable this option even if you have a wireless-less model.
2393 tristate "Freescale PQ MDIO"
2397 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2400 tristate "Gianfar Ethernet"
2406 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2407 and MPC86xx family of chips, and the FEC on the 8540.
2410 tristate "Freescale QE Gigabit Ethernet"
2411 depends on QUICC_ENGINE
2415 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2416 which is available on some Freescale SOCs.
2418 config UGETH_TX_ON_DEMAND
2419 bool "Transmit on Demand support"
2423 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2424 depends on MV64X60 || PPC32 || PLAT_ORION
2428 This driver supports the gigabit ethernet MACs in the
2429 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2430 in the Marvell Orion ARM SoC family.
2432 Some boards that use the Discovery chipset are the Momenco
2433 Ocelot C and Jaguar ATX and Pegasos II.
2435 config XILINX_LL_TEMAC
2436 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2438 depends on PPC_DCR_NATIVE
2440 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2441 core used in Xilinx Spartan and Virtex FPGAs
2444 tristate "QLogic QLA3XXX Network Driver Support"
2447 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2449 To compile this driver as a module, choose M here: the module
2450 will be called qla3xxx.
2453 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2458 This driver supports the Atheros/Attansic L1 gigabit ethernet
2461 To compile this driver as a module, choose M here. The module
2462 will be called atl1.
2465 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2466 depends on PCI && EXPERIMENTAL
2470 This driver supports the Atheros L1E gigabit ethernet adapter.
2472 To compile this driver as a module, choose M here. The module
2473 will be called atl1e.
2476 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2477 depends on PCI && EXPERIMENTAL
2481 This driver supports the Atheros L1C gigabit ethernet adapter.
2483 To compile this driver as a module, choose M here. The module
2484 will be called atl1c.
2487 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2492 This driver supports the PCI-Express gigabit ethernet adapters
2493 based on JMicron JMC250 chipset.
2495 To compile this driver as a module, choose M here. The module
2499 tristate "S6105 GMAC ethernet support"
2500 depends on XTENSA_VARIANT_S6000
2503 This driver supports the on chip ethernet device on the
2504 S6105 xtensa processor.
2506 To compile this driver as a module, choose M here. The module
2507 will be called s6gmac.
2509 source "drivers/net/stmmac/Kconfig"
2514 # 10 Gigabit Ethernet
2517 menuconfig NETDEV_10000
2518 bool "Ethernet (10000 Mbit)"
2522 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2523 This option alone does not add any kernel code.
2525 If you say N, all options in this submenu will be skipped and disabled.
2533 tristate "Chelsio 10Gb Ethernet support"
2538 This driver supports Chelsio gigabit and 10-gigabit
2539 Ethernet cards. More information about adapter features and
2540 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2542 For general information about Chelsio and our products, visit
2543 our website at <http://www.chelsio.com>.
2545 For customer support, please visit our customer support page at
2546 <http://www.chelsio.com/support.htm>.
2548 Please send feedback to <linux-bugs@chelsio.com>.
2550 To compile this driver as a module, choose M here: the module
2551 will be called cxgb.
2553 config CHELSIO_T1_1G
2554 bool "Chelsio gigabit Ethernet support"
2555 depends on CHELSIO_T1
2557 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2558 are using only 10G cards say 'N' here.
2560 config CHELSIO_T3_DEPENDS
2562 depends on PCI && INET
2566 tristate "Chelsio Communications T3 10Gb Ethernet support"
2567 depends on CHELSIO_T3_DEPENDS
2571 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2574 For general information about Chelsio and our products, visit
2575 our website at <http://www.chelsio.com>.
2577 For customer support, please visit our customer support page at
2578 <http://www.chelsio.com/support.htm>.
2580 Please send feedback to <linux-bugs@chelsio.com>.
2582 To compile this driver as a module, choose M here: the module
2583 will be called cxgb3.
2585 config CHELSIO_T4_DEPENDS
2587 depends on PCI && INET
2591 tristate "Chelsio Communications T4 Ethernet support"
2592 depends on CHELSIO_T4_DEPENDS
2596 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2599 For general information about Chelsio and our products, visit
2600 our website at <http://www.chelsio.com>.
2602 For customer support, please visit our customer support page at
2603 <http://www.chelsio.com/support.htm>.
2605 Please send feedback to <linux-bugs@chelsio.com>.
2607 To compile this driver as a module choose M here; the module
2608 will be called cxgb4.
2611 tristate "eHEA Ethernet support"
2612 depends on IBMEBUS && INET && SPARSEMEM
2615 This driver supports the IBM pSeries eHEA ethernet adapter.
2617 To compile the driver as a module, choose M here. The module
2618 will be called ehea.
2621 tristate "Cisco 10G Ethernet NIC support"
2622 depends on PCI && INET
2625 This enables the support for the Cisco 10G Ethernet card.
2628 tristate "Intel(R) 10GbE PCI Express adapters support"
2629 depends on PCI && INET
2632 This driver supports Intel(R) 10GbE PCI Express family of
2633 adapters. For more information on how to identify your adapter, go
2634 to the Adapter & Driver ID Guide at:
2636 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2638 For general information and support, go to the Intel support
2641 <http://support.intel.com>
2643 To compile this driver as a module, choose M here. The module
2644 will be called ixgbe.
2647 bool "Direct Cache Access (DCA) Support"
2649 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2651 Say Y here if you want to use Direct Cache Access (DCA) in the
2652 driver. DCA is a method for warming the CPU cache before data
2653 is used, with the intent of lessening the impact of cache misses.
2656 bool "Data Center Bridging (DCB) Support"
2658 depends on IXGBE && DCB
2660 Say Y here if you want to use Data Center Bridging (DCB) in the
2666 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2669 This driver supports Intel(R) 82599 virtual functions. For more
2670 information on how to identify your adapter, go to the Adapter &
2673 <http://support.intel.com/support/network/sb/CS-008441.htm>
2675 For general information and support, go to the Intel support
2678 <http://support.intel.com>
2680 More specific information on configuring the driver is in
2681 <file:Documentation/networking/ixgbevf.txt>.
2683 To compile this driver as a module, choose M here. The module
2684 will be called ixgbevf. MSI-X interrupt support is required
2685 for this driver to work correctly.
2688 tristate "Intel(R) PRO/10GbE support"
2691 This driver supports Intel(R) PRO/10GbE family of adapters for
2692 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2693 instead. For more information on how to identify your adapter, go
2694 to the Adapter & Driver ID Guide at:
2696 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2698 For general information and support, go to the Intel support
2701 <http://support.intel.com>
2703 More specific information on configuring the driver is in
2704 <file:Documentation/networking/ixgb.txt>.
2706 To compile this driver as a module, choose M here. The module
2707 will be called ixgb.
2710 tristate "S2IO 10Gbe XFrame NIC"
2713 This driver supports the 10Gbe XFrame NIC of S2IO.
2714 More specific information on configuring the driver is in
2715 <file:Documentation/networking/s2io.txt>.
2718 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2719 depends on PCI && INET
2721 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2722 I/O Virtualized Server Adapter.
2723 More specific information on configuring the driver is in
2724 <file:Documentation/networking/vxge.txt>.
2726 config VXGE_DEBUG_TRACE_ALL
2727 bool "Enabling All Debug trace statments in driver"
2731 Say Y here if you want to enabling all the debug trace statements in
2732 driver. By default only few debug trace statements are enabled.
2735 tristate "Myricom Myri-10G Ethernet support"
2736 depends on PCI && INET
2741 This driver supports Myricom Myri-10G Dual Protocol interface in
2742 Ethernet mode. If the eeprom on your board is not recent enough,
2743 you will need a newer firmware image.
2744 You may get this image or more information, at:
2746 <http://www.myri.com/scs/download-Myri10GE.html>
2748 To compile this driver as a module, choose M here. The module
2749 will be called myri10ge.
2752 bool "Direct Cache Access (DCA) Support"
2754 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2756 Say Y here if you want to use Direct Cache Access (DCA) in the
2757 driver. DCA is a method for warming the CPU cache before data
2758 is used, with the intent of lessening the impact of cache misses.
2761 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2764 This enables the support for NetXen's Gigabit Ethernet card.
2767 tristate "Sun Neptune 10Gbit Ethernet support"
2771 This enables support for cards based upon Sun's
2775 tristate "PA Semi 1/10Gbit MAC"
2776 depends on PPC_PASEMI && PCI
2780 This driver supports the on-chip 1/10Gbit Ethernet controller on
2781 PA Semi's PWRficient line of chips.
2784 tristate "Mellanox Technologies 10Gbit Ethernet support"
2785 depends on PCI && INET
2789 This driver supports Mellanox Technologies ConnectX Ethernet
2798 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2799 depends on MLX4_CORE
2802 This option causes debugging code to be compiled into the
2803 mlx4_core driver. The output can be turned on via the
2804 debug_level module parameter (which can also be set after
2805 the driver is loaded through sysfs).
2808 tristate "Tehuti Networks 10G Ethernet"
2811 Tehuti Networks 10G Ethernet NIC
2814 tristate "Broadcom NetXtremeII 10Gb support"
2821 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2822 To compile this driver as a module, choose M here: the module
2823 will be called bnx2x. This is recommended.
2826 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2829 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2833 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2836 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2838 To compile this driver as a module, choose M here: the module
2839 will be called qlge.
2841 source "drivers/net/sfc/Kconfig"
2843 source "drivers/net/benet/Kconfig"
2845 endif # NETDEV_10000
2847 source "drivers/net/tokenring/Kconfig"
2849 source "drivers/net/wireless/Kconfig"
2851 source "drivers/net/wimax/Kconfig"
2853 source "drivers/net/usb/Kconfig"
2855 source "drivers/net/pcmcia/Kconfig"
2857 source "drivers/net/wan/Kconfig"
2859 source "drivers/atm/Kconfig"
2861 source "drivers/ieee802154/Kconfig"
2863 source "drivers/s390/net/Kconfig"
2865 config XEN_NETDEV_FRONTEND
2866 tristate "Xen network device frontend driver"
2870 The network device frontend driver allows the kernel to
2871 access network devices exported exported by a virtual
2872 machine containing a physical network device driver. The
2873 frontend driver is intended for unprivileged guest domains;
2874 if you are compiling a kernel for a Xen guest, you almost
2875 certainly want to enable this.
2878 tristate "iSeries Virtual Ethernet driver support"
2879 depends on PPC_ISERIES
2882 tristate "RapidIO Ethernet over messaging driver support"
2885 config RIONET_TX_SIZE
2886 int "Number of outbound queue entries"
2890 config RIONET_RX_SIZE
2891 int "Number of inbound queue entries"
2896 tristate "FDDI driver support"
2897 depends on (PCI || EISA || TC)
2899 Fiber Distributed Data Interface is a high speed local area network
2900 design; essentially a replacement for high speed Ethernet. FDDI can
2901 run over copper or fiber. If you are connected to such a network and
2902 want a driver for the FDDI card in your computer, say Y here (and
2903 then also Y to the driver for your FDDI card, below). Most people
2907 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2908 depends on FDDI && (PCI || EISA || TC)
2910 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2911 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2912 to a local FDDI network.
2914 To compile this driver as a module, choose M here: the module
2915 will be called defxx. If unsure, say N.
2919 prompt "Use MMIO instead of PIO" if PCI || EISA
2921 default n if PCI || EISA
2924 This instructs the driver to use EISA or PCI memory-mapped I/O
2925 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2926 Enabling this gives an improvement in processing time in parts
2927 of the driver, but it may cause problems with EISA (DEFEA)
2928 adapters. TURBOchannel does not have the concept of I/O ports,
2929 so MMIO is always used for these (DEFTA) adapters.
2934 tristate "SysKonnect FDDI PCI support"
2935 depends on FDDI && PCI
2938 Say Y here if you have a SysKonnect FDDI PCI adapter.
2939 The following adapters are supported by this driver:
2940 - SK-5521 (SK-NET FDDI-UP)
2941 - SK-5522 (SK-NET FDDI-UP DAS)
2942 - SK-5541 (SK-NET FDDI-FP)
2943 - SK-5543 (SK-NET FDDI-LP)
2944 - SK-5544 (SK-NET FDDI-LP DAS)
2945 - SK-5821 (SK-NET FDDI-UP64)
2946 - SK-5822 (SK-NET FDDI-UP64 DAS)
2947 - SK-5841 (SK-NET FDDI-FP64)
2948 - SK-5843 (SK-NET FDDI-LP64)
2949 - SK-5844 (SK-NET FDDI-LP64 DAS)
2950 - Netelligent 100 FDDI DAS Fibre SC
2951 - Netelligent 100 FDDI SAS Fibre SC
2952 - Netelligent 100 FDDI DAS UTP
2953 - Netelligent 100 FDDI SAS UTP
2954 - Netelligent 100 FDDI SAS Fibre MIC
2956 Read <file:Documentation/networking/skfp.txt> for information about
2959 Questions concerning this driver can be addressed to:
2960 <linux@syskonnect.de>
2962 To compile this driver as a module, choose M here: the module
2963 will be called skfp. This is recommended.
2966 bool "HIPPI driver support (EXPERIMENTAL)"
2967 depends on EXPERIMENTAL && INET && PCI
2969 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2970 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2971 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2972 single-mode). HIPPI networks are commonly used for clusters and to
2973 connect to super computers. If you are connected to a HIPPI network
2974 and have a HIPPI network card in your computer that you want to use
2975 under Linux, say Y here (you must also remember to enable the driver
2976 for your HIPPI card below). Most people will say N here.
2979 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2980 depends on HIPPI && PCI
2982 Say Y here if this is your PCI HIPPI network card.
2984 To compile this driver as a module, choose M here: the module
2985 will be called rrunner. If unsure, say N.
2987 config ROADRUNNER_LARGE_RINGS
2988 bool "Use large TX/RX rings (EXPERIMENTAL)"
2989 depends on ROADRUNNER
2991 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2992 of additional memory to allow for fastest operation, both for
2993 transmitting and receiving. This memory cannot be used by any other
2994 kernel code or by user space programs. Say Y here only if you have
2998 tristate "PLIP (parallel port) support"
3001 PLIP (Parallel Line Internet Protocol) is used to create a
3002 reasonably fast mini network consisting of two (or, rarely, more)
3003 local machines. A PLIP link from a Linux box is a popular means to
3004 install a Linux distribution on a machine which doesn't have a
3005 CD-ROM drive (a minimal system has to be transferred with floppies
3006 first). The kernels on both machines need to have this PLIP option
3007 enabled for this to work.
3009 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3010 ports (the connectors at the computers with 25 holes) are connected
3011 with "null printer" or "Turbo Laplink" cables which can transmit 4
3012 bits at a time (mode 0) or with special PLIP cables, to be used on
3013 bidirectional parallel ports only, which can transmit 8 bits at a
3014 time (mode 1); you can find the wiring of these cables in
3015 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3016 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3017 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3018 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3019 and winsock or NCSA's telnet.
3021 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3022 as the NET-3-HOWTO, both available from
3023 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3024 protocol has been changed and this PLIP driver won't work together
3025 with the PLIP support in Linux versions 1.0.x. This option enlarges
3026 your kernel by about 8 KB.
3028 To compile this driver as a module, choose M here. The module
3029 will be called plip. If unsure, say Y or M, in case you buy
3033 tristate "PPP (point-to-point protocol) support"
3036 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3037 the same purpose: sending Internet traffic over telephone (and other
3038 serial) lines. Ask your access provider if they support it, because
3039 otherwise you can't use it; most Internet access providers these
3040 days support PPP rather than SLIP.
3042 To use PPP, you need an additional program called pppd as described
3043 in the PPP-HOWTO, available at
3044 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3045 the version of pppd recommended in <file:Documentation/Changes>.
3046 The PPP option enlarges your kernel by about 16 KB.
3048 There are actually two versions of PPP: the traditional PPP for
3049 asynchronous lines, such as regular analog phone lines, and
3050 synchronous PPP which can be used over digital ISDN lines for
3051 example. If you want to use PPP over phone lines or other
3052 asynchronous serial lines, you need to say Y (or M) here and also to
3053 the next option, "PPP support for async serial ports". For PPP over
3054 synchronous lines, you should say Y (or M) here and to "Support
3055 synchronous PPP", below.
3057 If you said Y to "Version information on all symbols" above, then
3058 you cannot compile the PPP driver into the kernel; you can then only
3059 compile it as a module. To compile this driver as a module, choose M
3060 here. The module will be called ppp_generic.
3062 config PPP_MULTILINK
3063 bool "PPP multilink support (EXPERIMENTAL)"
3064 depends on PPP && EXPERIMENTAL
3066 PPP multilink is a protocol (defined in RFC 1990) which allows you
3067 to combine several (logical or physical) lines into one logical PPP
3068 connection, so that you can utilize your full bandwidth.
3070 This has to be supported at the other end as well and you need a
3071 version of the pppd daemon which understands the multilink protocol.
3076 bool "PPP filtering"
3079 Say Y here if you want to be able to filter the packets passing over
3080 PPP interfaces. This allows you to control which packets count as
3081 activity (i.e. which packets will reset the idle timer or bring up
3082 a demand-dialed link) and which packets are to be dropped entirely.
3083 You need to say Y here if you wish to use the pass-filter and
3084 active-filter options to pppd.
3089 tristate "PPP support for async serial ports"
3093 Say Y (or M) here if you want to be able to use PPP over standard
3094 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3095 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3098 To compile this driver as a module, choose M here.
3103 tristate "PPP support for sync tty ports"
3106 Say Y (or M) here if you want to be able to use PPP over synchronous
3107 (HDLC) tty devices, such as the SyncLink adapter. These devices
3108 are often used for high-speed leased lines like T1/E1.
3110 To compile this driver as a module, choose M here.
3113 tristate "PPP Deflate compression"
3118 Support for the Deflate compression method for PPP, which uses the
3119 Deflate algorithm (the same algorithm that gzip uses) to compress
3120 each PPP packet before it is sent over the wire. The machine at the
3121 other end of the PPP link (usually your ISP) has to support the
3122 Deflate compression method as well for this to be useful. Even if
3123 they don't support it, it is safe to say Y here.
3125 To compile this driver as a module, choose M here.
3128 tristate "PPP BSD-Compress compression"
3131 Support for the BSD-Compress compression method for PPP, which uses
3132 the LZW compression method to compress each PPP packet before it is
3133 sent over the wire. The machine at the other end of the PPP link
3134 (usually your ISP) has to support the BSD-Compress compression
3135 method as well for this to be useful. Even if they don't support it,
3136 it is safe to say Y here.
3138 The PPP Deflate compression method ("PPP Deflate compression",
3139 above) is preferable to BSD-Compress, because it compresses better
3142 Note that the BSD compression code will always be compiled as a
3143 module; it is called bsd_comp and will show up in the directory
3144 modules once you have said "make modules". If unsure, say N.
3147 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3148 depends on PPP && EXPERIMENTAL
3154 Support for the MPPE Encryption protocol, as employed by the
3155 Microsoft Point-to-Point Tunneling Protocol.
3157 See http://pptpclient.sourceforge.net/ for information on
3158 configuring PPTP clients and servers to utilize this method.
3161 tristate "PPP over Ethernet (EXPERIMENTAL)"
3162 depends on EXPERIMENTAL && PPP
3164 Support for PPP over Ethernet.
3166 This driver requires the latest version of pppd from the CVS
3167 repository at cvs.samba.org. Alternatively, see the
3168 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3169 which contains instruction on how to use this driver (under
3170 the heading "Kernel mode PPPoE").
3173 tristate "PPP over ATM"
3174 depends on ATM && PPP
3176 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3177 This implementation does not yet comply with section 8 of RFC2364,
3178 which can lead to bad results if the ATM peer loses state and
3179 changes its encapsulation unilaterally.
3182 tristate "PPP over L2TP (EXPERIMENTAL)"
3183 depends on EXPERIMENTAL && PPP && INET
3185 Support for PPP-over-L2TP socket family. L2TP is a protocol
3186 used by ISPs and enterprises to tunnel PPP traffic over UDP
3187 tunnels. L2TP is replacing PPTP for VPN uses.
3189 This kernel component handles only L2TP data packets: a
3190 userland daemon handles L2TP the control protocol (tunnel
3191 and session setup). One such daemon is OpenL2TP
3192 (http://openl2tp.sourceforge.net/).
3195 tristate "SLIP (serial line) support"
3197 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3198 connect to your Internet service provider or to connect to some
3199 other local Unix box or if you want to configure your Linux box as a
3200 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3201 Internet Protocol) is a protocol used to send Internet traffic over
3202 serial connections such as telephone lines or null modem cables;
3203 nowadays, the protocol PPP is more commonly used for this same
3206 Normally, your access provider has to support SLIP in order for you
3207 to be able to use it, but there is now a SLIP emulator called SLiRP
3208 around (available from
3209 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3210 allows you to use SLIP over a regular dial up shell connection. If
3211 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3212 NET-3-HOWTO, available from
3213 <http://www.tldp.org/docs.html#howto>, explains how to
3214 configure SLIP. Note that you don't need this option if you just
3215 want to run term (term is a program which gives you almost full
3216 Internet connectivity if you have a regular dial up shell account on
3217 some Internet connected Unix computer. Read
3218 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3219 support will enlarge your kernel by about 4 KB. If unsure, say N.
3221 To compile this driver as a module, choose M here. The module
3222 will be called slip.
3224 config SLIP_COMPRESSED
3225 bool "CSLIP compressed headers"
3229 This protocol is faster than SLIP because it uses compression on the
3230 TCP/IP headers (not on the data itself), but it has to be supported
3231 on both ends. Ask your access provider if you are not sure and
3232 answer Y, just in case. You will still be able to use plain SLIP. If
3233 you plan to use SLiRP, the SLIP emulator (available from
3234 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3235 allows you to use SLIP over a regular dial up shell connection, you
3236 definitely want to say Y here. The NET-3-HOWTO, available from
3237 <http://www.tldp.org/docs.html#howto>, explains how to configure
3238 CSLIP. This won't enlarge your kernel.
3243 This option enables Van Jacobsen serial line header compression
3247 bool "Keepalive and linefill"
3250 Adds additional capabilities to the SLIP driver to support the
3251 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3254 config SLIP_MODE_SLIP6
3255 bool "Six bit SLIP encapsulation"
3258 Just occasionally you may need to run IP over hostile serial
3259 networks that don't pass all control characters or are only seven
3260 bit. Saying Y here adds an extra mode you can use with SLIP:
3261 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3262 the serial device. Naturally, this has to be supported at the other
3263 end of the link as well. It's good enough, for example, to run IP
3264 over the async ports of a Camtec JNT Pad. If unsure, say N.
3267 bool "Fibre Channel driver support"
3268 depends on SCSI && PCI
3270 Fibre Channel is a high speed serial protocol mainly used to connect
3271 large storage devices to the computer; it is compatible with and
3272 intended to replace SCSI.
3274 If you intend to use Fibre Channel, you need to have a Fibre channel
3275 adaptor card in your computer; say Y here and to the driver for your
3276 adaptor below. You also should have said Y to "SCSI support" and
3277 "SCSI generic support".
3280 tristate "Network console logging support (EXPERIMENTAL)"
3281 depends on EXPERIMENTAL
3283 If you want to log kernel messages over the network, enable this.
3284 See <file:Documentation/networking/netconsole.txt> for details.
3286 config NETCONSOLE_DYNAMIC
3287 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3288 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3291 This option enables the ability to dynamically reconfigure target
3292 parameters (interface, IP addresses, port numbers, MAC addresses)
3293 at runtime through a userspace interface exported using configfs.
3294 See <file:Documentation/networking/netconsole.txt> for details.
3300 bool "Netpoll traffic trapping"
3304 config NET_POLL_CONTROLLER
3308 tristate "Virtio network driver (EXPERIMENTAL)"
3309 depends on EXPERIMENTAL && VIRTIO
3311 This is the virtual network driver for virtio. It can be used with
3312 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3315 tristate "VMware VMXNET3 ethernet driver"
3316 depends on PCI && INET
3318 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3319 To compile this driver as a module, choose M here: the
3320 module will be called vmxnet3.