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 "EQL (serial line load balancing) support"
96 If you have two serial connections to some other computer (this
97 usually requires two modems and two telephone lines) and you use
98 SLIP (the protocol for sending Internet traffic over telephone
99 lines) or PPP (a better SLIP) on them, you can make them behave like
100 one double speed connection using this driver. Naturally, this has
101 to be supported at the other end as well, either with a similar EQL
102 Linux driver or with a Livingston Portmaster 2e.
104 Say Y if you want this and read
105 <file:Documentation/networking/eql.txt>. You may also want to read
106 section 6.2 of the NET-3-HOWTO, available from
107 <http://www.tldp.org/docs.html#howto>.
109 To compile this driver as a module, choose M here: the module
110 will be called eql. If unsure, say N.
113 tristate "Universal TUN/TAP device driver support"
116 TUN/TAP provides packet reception and transmission for user space
117 programs. It can be viewed as a simple Point-to-Point or Ethernet
118 device, which instead of receiving packets from a physical media,
119 receives them from user space program and instead of sending packets
120 via physical media writes them to the user space program.
122 When a program opens /dev/net/tun, driver creates and registers
123 corresponding net device tunX or tapX. After a program closed above
124 devices, driver will automatically delete tunXX or tapXX device and
125 all routes corresponding to it.
127 Please read <file:Documentation/networking/tuntap.txt> for more
130 To compile this driver as a module, choose M here: the module
133 If you don't know what to use this for, you don't need it.
136 tristate "Virtual ethernet pair device"
138 This device is a local ethernet tunnel. Devices are created in pairs.
139 When one end receives the packet it appears on its pair and vice
143 tristate "General Instruments Surfboard 1000"
146 This is a driver for the General Instrument (also known as
147 NextLevel) SURFboard 1000 internal
148 cable modem. This is an ISA card which is used by a number of cable
149 TV companies to provide cable modem access. It's a one-way
150 downstream-only cable modem, meaning that your upstream net link is
151 provided by your regular phone modem.
153 At present this driver only compiles as a module, so say M here if
154 you have this card. The module will be called sb1000. Then read
155 <file:Documentation/networking/README.sb1000> for information on how
156 to use this module, as it needs special ppp scripts for establishing
157 a connection. Further documentation and the necessary scripts can be
160 <http://www.jacksonville.net/~fventuri/>
161 <http://home.adelphia.net/~siglercm/sb1000.html>
162 <http://linuxpower.cx/~cable/>
164 If you don't have this card, of course say N.
166 source "drivers/net/arcnet/Kconfig"
168 source "drivers/net/phy/Kconfig"
174 menuconfig NET_ETHERNET
175 bool "Ethernet (10 or 100Mbit)"
178 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
179 type of Local Area Network (LAN) in universities and companies.
181 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
182 coaxial cable, linking computers in a chain), 10BASE-T or twisted
183 pair (10 Mbps over twisted pair cable, linking computers to central
184 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
185 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
186 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
187 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
188 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
189 Ethernet (1 Gbps over optical fiber or short copper links).
191 If your Linux machine will be connected to an Ethernet and you have
192 an Ethernet network interface card (NIC) installed in your computer,
193 say Y here and read the Ethernet-HOWTO, available from
194 <http://www.tldp.org/docs.html#howto>. You will then also have
195 to say Y to the driver for your particular NIC.
197 Note that the answer to this question won't directly affect the
198 kernel: saying N will just cause the configurator to skip all
199 the questions about Ethernet network cards. If unsure, say N.
204 tristate "Generic Media Independent Interface device support"
206 Most ethernet controllers have MII transceiver either as an external
207 or internal device. It is safe to say Y or M here even if your
208 ethernet card lack MII.
211 tristate "Atmel MACB support"
212 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9
215 The Atmel MACB ethernet interface is found on many AT32 and AT91
216 parts. Say Y to include support for the MACB chip.
218 To compile this driver as a module, choose M here: the module
221 source "drivers/net/arm/Kconfig"
224 tristate "ASIX AX88796 NE2000 clone support"
225 depends on ARM || MIPS || SUPERH
229 AX88796 driver, using platform bus to provide
230 chip detection and resources
233 bool "ASIX AX88796 external 93CX6 eeprom support"
237 Select this if your platform comes with an external 93CX6 eeprom.
240 tristate "MACE (Power Mac ethernet) support"
241 depends on PPC_PMAC && PPC32
244 Power Macintoshes and clones with Ethernet built-in on the
245 motherboard will usually use a MACE (Medium Access Control for
246 Ethernet) interface. Say Y to include support for the MACE chip.
248 To compile this driver as a module, choose M here: the module
251 config MACE_AAUI_PORT
252 bool "Use AAUI port instead of TP by default"
255 Some Apple machines (notably the Apple Network Server) which use the
256 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
257 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
258 Y here if you have such a machine. If unsure, say N.
259 The driver will default to AAUI on ANS anyway, and if you use it as
260 a module, you can provide the port_aaui=0|1 to force the driver.
263 tristate "BMAC (G3 ethernet) support"
264 depends on PPC_PMAC && PPC32
267 Say Y for support of BMAC Ethernet interfaces. These are used on G3
270 To compile this driver as a module, choose M here: the module
274 tristate "Ariadne support"
277 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
280 To compile this driver as a module, choose M here: the module
281 will be called ariadne.
284 tristate "A2065 support"
288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
291 To compile this driver as a module, choose M here: the module
292 will be called a2065.
295 tristate "Hydra support"
299 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
301 To compile this driver as a module, choose M here: the module
302 will be called hydra.
305 tristate "Zorro NS8390-based Ethernet support"
309 This driver is for Zorro Ethernet cards using an NS8390-compatible
310 chipset, like the Village Tronic Ariadne II and the Individual
311 Computers X-Surf Ethernet cards. If you have such a card, say Y.
314 To compile this driver as a module, choose M here: the module
315 will be called zorro8390.
318 tristate "PCMCIA NE2000 support"
319 depends on AMIGA_PCMCIA
322 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
325 To compile this driver as a module, choose M here: the module
329 bool "Macintosh NS 8390 based ethernet cards"
333 If you want to include a driver to support Nubus or LC-PDS
334 Ethernet cards using an NS8390 chipset or its equivalent, say Y
335 and read the Ethernet-HOWTO, available from
336 <http://www.tldp.org/docs.html#howto>.
339 tristate "Macintosh CS89x0 based ethernet cards"
342 Support for CS89x0 chipset based Ethernet cards. If you have a
343 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
344 read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
347 To compile this driver as a module, choose M here. This module will
351 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
354 Support for NatSemi SONIC based Ethernet devices. This includes
355 the onboard Ethernet in many Quadras as well as some LC-PDS,
356 a few Nubus and all known Comm Slot Ethernet cards. If you have
357 one of these say Y and read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 To compile this driver as a module, choose M here. This module will
364 bool "Macintosh (AV) onboard MACE ethernet"
368 Support for the onboard AMD 79C940 MACE Ethernet controller used in
369 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
370 say Y and read the Ethernet-HOWTO, available from
371 <http://www.tldp.org/docs.html#howto>.
374 tristate "MVME147 (Lance) Ethernet support"
378 Support for the on-board Ethernet interface on the Motorola MVME147
379 single-board computer. Say Y here to include the
380 driver for this chip in your kernel.
381 To compile this driver as a module, choose M here.
384 tristate "MVME16x Ethernet support"
387 This is the driver for the Ethernet interface on the Motorola
388 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
389 driver for this chip in your kernel.
390 To compile this driver as a module, choose M here.
393 tristate "BVME6000 Ethernet support"
396 This is the driver for the Ethernet interface on BVME4000 and
397 BVME6000 VME boards. Say Y here to include the driver for this chip
399 To compile this driver as a module, choose M here.
402 tristate "Atari Lance support"
405 Say Y to include support for several Atari Ethernet adapters based
406 on the AMD Lance chipset: RieblCard (with or without battery), or
407 PAMCard VME (also the version by Rhotron, with different addresses).
410 tristate "Sun3/Sun3x on-board LANCE support"
411 depends on SUN3 || SUN3X
413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
415 here to compile in the Linux driver for this and enable Ethernet.
416 General Linux information on the Sun 3 and 3x series (now
418 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
420 If you're not building a kernel for a Sun 3, say N.
423 bool "Sun3 on-board Intel 82586 support"
426 This driver enables support for the on-board Intel 82586 based
427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
428 that this driver does not support 82586-based adapters on additional
432 bool "HP on-board LANCE support"
436 If you want to use the builtin "LANCE" Ethernet controller on an
437 HP300 machine, say Y here.
440 tristate "Lasi ethernet"
443 Say Y here to support the builtin Intel 82596 ethernet controller
444 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
447 tristate "SNI RM ethernet"
448 depends on NET_ETHERNET && SNI_RM
450 Say Y here to support the on-board Intel 82596 ethernet controller
451 built into SNI RM machines.
454 tristate "Korina (IDT RC32434) Ethernet support"
455 depends on NET_ETHERNET && MIKROTIK_RB532
457 If you have a Mikrotik RouterBoard 500 or IDT RC32434
458 based system say Y. Otherwise say N.
460 config MIPS_JAZZ_SONIC
461 tristate "MIPS JAZZ onboard SONIC Ethernet support"
464 This is the driver for the onboard card of MIPS Magnum 4000,
465 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
467 config XTENSA_XT2000_SONIC
468 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
469 depends on XTENSA_PLATFORM_XT2000
471 This is the driver for the onboard card of the Xtensa XT2000 board.
473 config MIPS_AU1X00_ENET
474 bool "MIPS AU1000 Ethernet support"
475 depends on SOC_AU1X00
479 If you have an Alchemy Semi AU1X00 based system
480 say Y. Otherwise, say N.
483 bool "SGI IOC3 Ethernet"
484 depends on PCI && SGI_IP27
488 If you have a network (Ethernet) card of this type, say Y and read
489 the Ethernet-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>.
493 tristate "MIPS simulator Network device"
496 The MIPSNET device is a simple Ethernet network device which is
497 emulated by the MIPS Simulator.
498 If you are not using a MIPSsim or are unsure, say N.
500 config SGI_O2MACE_ETH
501 tristate "SGI O2 MACE Fast Ethernet support"
502 depends on SGI_IP32=y
505 tristate "National DP83902AV support"
509 Support for cards based on the National Semiconductor DP83902AV
510 ST-NIC Serial Network Interface Controller for Twisted Pair. This
511 is a 10Mbit/sec Ethernet controller. Product overview and specs at
512 <http://www.national.com/pf/DP/DP83902A.html>.
517 tristate "Renesas SuperH Ethernet support"
518 depends on SUPERH && \
519 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
520 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
527 Renesas SuperH Ethernet device driver.
528 This driver support SH7710, SH7712, SH7763, SH7619, and SH7724.
531 tristate "Sun LANCE support"
535 This driver supports the "le" interface present on all 32-bit Sparc
536 systems, on some older Ultra systems and as an Sbus option. These
537 cards are based on the AMD Lance chipset, which is better known
538 via the NE2100 cards.
540 To compile this driver as a module, choose M here: the module
541 will be called sunlance.
544 tristate "Sun Happy Meal 10/100baseT support"
545 depends on SBUS || PCI
548 This driver supports the "hme" interface present on most Ultra
549 systems and as an option on older Sbus systems. This driver supports
550 both PCI and Sbus devices. This driver also supports the "qfe" quad
551 100baseT device available in both PCI and Sbus configurations.
553 To compile this driver as a module, choose M here: the module
554 will be called sunhme.
557 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
558 depends on SBUS && EXPERIMENTAL
561 This driver supports the "be" interface available as an Sbus option.
562 This is Sun's older 100baseT Ethernet device.
564 To compile this driver as a module, choose M here: the module
565 will be called sunbmac.
568 tristate "Sun QuadEthernet support"
572 This driver supports the "qe" 10baseT Ethernet device, available as
573 an Sbus option. Note that this is not the same as Quad FastEthernet
574 "qfe" which is supported by the Happy Meal driver instead.
576 To compile this driver as a module, choose M here: the module
577 will be called sunqe.
580 tristate "Sun GEM support"
584 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
585 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
588 tristate "Sun Cassini support"
592 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
593 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
596 tristate "Sun Virtual Network support"
599 Support for virtual network devices under Sun Logical Domains.
601 config NET_VENDOR_3COM
603 depends on ISA || EISA || MCA || PCI
605 If you have a network (Ethernet) card belonging to this class, say Y
606 and read the Ethernet-HOWTO, available from
607 <http://www.tldp.org/docs.html#howto>.
609 Note that the answer to this question doesn't directly affect the
610 kernel: saying N will just cause the configurator to skip all
611 the questions about 3COM cards. If you say Y, you will be asked for
612 your specific card in the following questions.
615 tristate "3c501 \"EtherLink\" support"
616 depends on NET_VENDOR_3COM && ISA
618 If you have a network (Ethernet) card of this type, say Y and read
619 the Ethernet-HOWTO, available from
620 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
621 new card, since the 3c501 is slow, broken, and obsolete: you will
622 have problems. Some people suggest to ping ("man ping") a nearby
623 machine every minute ("man cron") when using this card.
625 To compile this driver as a module, choose M here. The module
626 will be called 3c501.
629 tristate "3c503 \"EtherLink II\" support"
630 depends on NET_VENDOR_3COM && ISA
633 If you have a network (Ethernet) card of this type, say Y and read
634 the Ethernet-HOWTO, available from
635 <http://www.tldp.org/docs.html#howto>.
637 To compile this driver as a module, choose M here. The module
638 will be called 3c503.
641 tristate "3c505 \"EtherLink Plus\" support"
642 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
644 Information about this network (Ethernet) card can be found in
645 <file:Documentation/networking/3c505.txt>. If you have a card of
646 this type, say Y and read 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 3c505.
653 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
654 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
656 If you have a network (Ethernet) card of this type, say Y and read
657 the Ethernet-HOWTO, available from
658 <http://www.tldp.org/docs.html#howto>.
660 To compile this driver as a module, choose M here. The module
661 will be called 3c507.
664 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
665 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
667 If you have a network (Ethernet) card belonging to the 3Com
668 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
669 from <http://www.tldp.org/docs.html#howto>.
671 If your card is not working you may need to use the DOS
672 setup disk to disable Plug & Play mode, and to select the default
675 To compile this driver as a module, choose M here. The module
676 will be called 3c509.
679 tristate "3c515 ISA \"Fast EtherLink\""
680 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
682 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
683 network card, say Y and read the Ethernet-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>.
686 To compile this driver as a module, choose M here. The module
687 will be called 3c515.
690 tristate "3c523 \"EtherLink/MC\" support"
691 depends on NET_VENDOR_3COM && MCA_LEGACY
693 If you have a network (Ethernet) card of this type, say Y and read
694 the Ethernet-HOWTO, available from
695 <http://www.tldp.org/docs.html#howto>.
697 To compile this driver as a module, choose M here. The module
698 will be called 3c523.
701 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
702 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
704 If you have a network (Ethernet) card of this type, say Y and read
705 the Ethernet-HOWTO, available from
706 <http://www.tldp.org/docs.html#howto>.
708 To compile this driver as a module, choose M here. The module
709 will be called 3c527.
712 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
713 depends on NET_VENDOR_3COM && (PCI || EISA)
716 This option enables driver support for a large number of 10Mbps and
717 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
719 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
720 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
721 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
722 "Tornado" (3c905) PCI
723 "Hurricane" (3c555/3cSOHO) PCI
725 If you have such a card, say Y and read the Ethernet-HOWTO,
726 available from <http://www.tldp.org/docs.html#howto>. More
727 specific information is in
728 <file:Documentation/networking/vortex.txt> and in the comments at
729 the beginning of <file:drivers/net/3c59x.c>.
731 To compile this support as a module, choose M here.
734 tristate "3cr990 series \"Typhoon\" support"
735 depends on NET_VENDOR_3COM && PCI
738 This option enables driver support for the 3cr990 series of cards:
740 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
741 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
742 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
744 If you have a network (Ethernet) card of this type, say Y and read
745 the Ethernet-HOWTO, available from
746 <http://www.tldp.org/docs.html#howto>.
748 To compile this driver as a module, choose M here. The module
749 will be called typhoon.
752 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
753 depends on ISA && ISA_DMA_API
755 If you have a network (Ethernet) card of this type, say Y and read
756 the Ethernet-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
760 To compile this driver as a module, choose M here: the module
761 will be called lance. This is recommended.
763 config NET_VENDOR_SMC
764 bool "Western Digital/SMC cards"
765 depends on ISA || MCA || EISA || MAC
767 If you have a network (Ethernet) card belonging to this class, say Y
768 and read the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>.
771 Note that the answer to this question doesn't directly affect the
772 kernel: saying N will just cause the configurator to skip all
773 the questions about Western Digital cards. If you say Y, you will be
774 asked for your specific card in the following questions.
777 tristate "WD80*3 support"
778 depends on NET_VENDOR_SMC && ISA
781 If you have a network (Ethernet) card of this type, say Y and read
782 the Ethernet-HOWTO, available from
783 <http://www.tldp.org/docs.html#howto>.
785 To compile this driver as a module, choose M here. The module
789 tristate "SMC Ultra MCA support"
790 depends on NET_VENDOR_SMC && MCA
793 If you have a network (Ethernet) card of this type and are running
794 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
795 available from <http://www.tldp.org/docs.html#howto>.
797 To compile this driver as a module, choose M here. The module
798 will be called smc-mca.
801 tristate "SMC Ultra support"
802 depends on NET_VENDOR_SMC && ISA
805 If you have a network (Ethernet) card of this type, say Y and read
806 the Ethernet-HOWTO, available from
807 <http://www.tldp.org/docs.html#howto>.
809 Important: There have been many reports that, with some motherboards
810 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
811 such as some BusLogic models) causes corruption problems with many
812 operating systems. The Linux smc-ultra driver has a work-around for
813 this but keep it in mind if you have such a SCSI card and have
816 To compile this driver as a module, choose M here. The module
817 will be called smc-ultra.
820 tristate "SMC Ultra32 EISA support"
821 depends on NET_VENDOR_SMC && EISA
824 If you have a network (Ethernet) card of this type, say Y and read
825 the Ethernet-HOWTO, available from
826 <http://www.tldp.org/docs.html#howto>.
828 To compile this driver as a module, choose M here. The module
829 will be called smc-ultra32.
832 tristate "Blackfin on-chip MAC support"
833 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
837 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
839 This is the driver for Blackfin on-chip mac device. Say Y if you want it
840 compiled into the kernel. This driver is also available as a module
841 ( = code which can be inserted in and removed from the running kernel
842 whenever you want). The module will be called bfin_mac.
844 config BFIN_MAC_USE_L1
845 bool "Use L1 memory for rx/tx packets"
846 depends on BFIN_MAC && (BF527 || BF537)
849 To get maximum network performance, you should use L1 memory as rx/tx buffers.
850 Say N here if you want to reserve L1 memory for other uses.
852 config BFIN_TX_DESC_NUM
853 int "Number of transmit buffer packets"
855 range 6 10 if BFIN_MAC_USE_L1
859 Set the number of buffer packets used in driver.
861 config BFIN_RX_DESC_NUM
862 int "Number of receive buffer packets"
864 range 20 100 if BFIN_MAC_USE_L1
868 Set the number of buffer packets used in driver.
871 bool "RMII PHY Interface (EXPERIMENTAL)"
872 depends on BFIN_MAC && EXPERIMENTAL
873 default y if BFIN527_EZKIT
874 default n if BFIN537_STAMP
876 Use Reduced PHY MII Interface
879 tristate "SMC 9194 support"
880 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
883 This is support for the SMC9xxx based Ethernet cards. Choose this
884 option if you have a DELL laptop with the docking station, or
885 another SMC9192/9194 based chipset. Say Y if you want it compiled
886 into the kernel, and read the file
887 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
888 available from <http://www.tldp.org/docs.html#howto>.
890 To compile this driver as a module, choose M here. The module
891 will be called smc9194.
894 tristate "SMC 91C9x/91C1xxx support"
897 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
898 MIPS || BLACKFIN || MN10300
900 This is a driver for SMC's 91x series of Ethernet chipsets,
901 including the SMC91C94 and the SMC91C111. Say Y if you want it
902 compiled into the kernel, and read the file
903 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
904 available from <http://www.linuxdoc.org/docs.html#howto>.
906 This driver is also available as a module ( = code which can be
907 inserted in and removed from the running kernel whenever you want).
908 The module will be called smc91x. If you want to compile it as a
909 module, say M here and read <file:Documentation/kbuild/modules.txt>.
912 tristate "NetX Ethernet support"
916 This is support for the Hilscher netX builtin Ethernet ports
918 To compile this driver as a module, choose M here. The module
919 will be called netx-eth.
921 config TI_DAVINCI_EMAC
922 tristate "TI DaVinci EMAC Support"
923 depends on ARM && ARCH_DAVINCI
926 This driver supports TI's DaVinci Ethernet .
928 To compile this driver as a module, choose M here: the module
929 will be called davinci_emac_driver. This is recommended.
932 tristate "DM9000 support"
933 depends on ARM || BLACKFIN || MIPS
937 Support for DM9000 chipset.
939 To compile this driver as a module, choose M here. The module
940 will be called dm9000.
942 config DM9000_DEBUGLEVEL
943 int "DM9000 maximum debug level"
947 The maximum level of debugging code compiled into the DM9000
950 config DM9000_FORCE_SIMPLE_PHY_POLL
951 bool "Force simple NSR based PHY polling"
954 This configuration forces the DM9000 to use the NSR's LinkStatus
955 bit to determine if the link is up or down instead of the more
956 costly MII PHY reads. Note, this will not work if the chip is
957 operating with an external PHY.
960 tristate "ENC28J60 support"
961 depends on EXPERIMENTAL && SPI && NET_ETHERNET
964 Support for the Microchip EN28J60 ethernet chip.
966 To compile this driver as a module, choose M here. The module will be
969 config ENC28J60_WRITEVERIFY
970 bool "Enable write verify"
973 Enable the verify after the buffer write useful for debugging purpose.
977 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
978 depends on NET_ETHERNET && HAS_IOMEM
984 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
987 tristate "SMSC LAN911[5678] support"
990 depends on ARM || SUPERH
992 This is a driver for SMSC's LAN911x series of Ethernet chipsets
993 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
994 Say Y if you want it compiled into the kernel,
995 and read the Ethernet-HOWTO, available from
996 <http://www.linuxdoc.org/docs.html#howto>.
998 This driver is also available as a module. The module will be
999 called smc911x. If you want to compile it as a module, say M
1000 here and read <file:Documentation/kbuild/modules.txt>
1003 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1004 depends on ARM || SUPERH || BLACKFIN
1009 Say Y here if you want support for SMSC LAN911x and LAN921x families
1010 of ethernet controllers.
1012 To compile this driver as a module, choose M here and read
1013 <file:Documentation/networking/net-modules.txt>. The module
1014 will be called smsc911x.
1016 config NET_VENDOR_RACAL
1017 bool "Racal-Interlan (Micom) NI cards"
1020 If you have a network (Ethernet) card belonging to this class, such
1021 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1022 available from <http://www.tldp.org/docs.html#howto>.
1024 Note that the answer to this question doesn't directly affect the
1025 kernel: saying N will just cause the configurator to skip all
1026 the questions about NI cards. If you say Y, you will be asked for
1027 your specific card in the following questions.
1030 tristate "NI5010 support (EXPERIMENTAL)"
1031 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1033 If you have a network (Ethernet) card of this type, say Y and read
1034 the Ethernet-HOWTO, available from
1035 <http://www.tldp.org/docs.html#howto>. Note that this is still
1038 To compile this driver as a module, choose M here. The module
1039 will be called ni5010.
1042 tristate "NI5210 support"
1043 depends on NET_VENDOR_RACAL && ISA
1045 If you have a network (Ethernet) card of this type, say Y and read
1046 the Ethernet-HOWTO, available from
1047 <http://www.tldp.org/docs.html#howto>.
1049 To compile this driver as a module, choose M here. The module
1050 will be called ni52.
1053 tristate "NI6510 support"
1054 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1056 If you have a network (Ethernet) card of this type, say Y and read
1057 the Ethernet-HOWTO, available from
1058 <http://www.tldp.org/docs.html#howto>.
1060 To compile this driver as a module, choose M here. The module
1061 will be called ni65.
1064 tristate "Dave ethernet support (DNET)"
1065 depends on NET_ETHERNET && HAS_IOMEM
1068 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1069 Say Y to include support for the DNET chip.
1071 To compile this driver as a module, choose M here: the module
1072 will be called dnet.
1074 source "drivers/net/tulip/Kconfig"
1077 tristate "AT1700/1720 support (EXPERIMENTAL)"
1078 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1081 If you have a network (Ethernet) card of this type, say Y and read
1082 the Ethernet-HOWTO, available from
1083 <http://www.tldp.org/docs.html#howto>.
1085 To compile this driver as a module, choose M here. The module
1086 will be called at1700.
1089 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1090 depends on ISA || EISA || MCA
1093 If you have a network (Ethernet) card of this type, say Y and read
1094 the Ethernet-HOWTO, available from
1095 <http://www.tldp.org/docs.html#howto> as well as
1096 <file:drivers/net/depca.c>.
1098 To compile this driver as a module, choose M here. The module
1099 will be called depca.
1102 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1103 depends on ISA || EISA || PCI
1105 If you have a network (Ethernet) card of this type, say Y and read
1106 the Ethernet-HOWTO, available from
1107 <http://www.tldp.org/docs.html#howto>.
1109 To compile this driver as a module, choose M here. The module
1110 will be called hp100.
1113 bool "Other ISA cards"
1116 If your network (Ethernet) card hasn't been mentioned yet and its
1117 bus system (that's the way the cards talks to the other components
1118 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1119 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1120 available from <http://www.tldp.org/docs.html#howto>.
1124 Note that the answer to this question doesn't directly affect the
1125 kernel: saying N will just cause the configurator to skip all
1126 the remaining ISA network card questions. If you say Y, you will be
1127 asked for your specific card in the following questions.
1130 tristate "Cabletron E21xx support"
1134 If you have a network (Ethernet) card of this type, say Y and read
1135 the Ethernet-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1138 To compile this driver as a module, choose M here. The module
1139 will be called e2100.
1142 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1146 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1147 cards. If this is for you, say Y and read
1148 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1149 well as the Ethernet-HOWTO, available from
1150 <http://www.tldp.org/docs.html#howto>.
1152 To compile this driver as a module, choose M here. The module
1153 will be called ewrk3.
1156 tristate "EtherExpress 16 support"
1159 If you have an EtherExpress16 network (Ethernet) card, say Y and
1160 read the Ethernet-HOWTO, available from
1161 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1162 EtherExpress16 card used to be regarded as a very poor choice
1163 because the driver was very unreliable. We now have a new driver
1164 that should do better.
1166 To compile this driver as a module, choose M here. The module
1167 will be called eexpress.
1170 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1173 If you have a network (Ethernet) card of this type, say Y. This
1174 driver supports Intel i82595{FX,TX} based boards. Note however
1175 that the EtherExpress PRO/100 Ethernet card has its own separate
1176 driver. Please read the Ethernet-HOWTO, available from
1177 <http://www.tldp.org/docs.html#howto>.
1179 To compile this driver as a module, choose M here. The module
1180 will be called eepro.
1183 tristate "HP PCLAN+ (27247B and 27252A) support"
1187 If you have a network (Ethernet) card of this type, say Y and read
1188 the Ethernet-HOWTO, available from
1189 <http://www.tldp.org/docs.html#howto>.
1191 To compile this driver as a module, choose M here. The module
1192 will be called hp-plus.
1195 tristate "HP PCLAN (27245 and other 27xxx series) support"
1199 If you have a network (Ethernet) card of this type, say Y and read
1200 the Ethernet-HOWTO, available from
1201 <http://www.tldp.org/docs.html#howto>.
1203 To compile this driver as a module, choose M here. The module
1207 tristate "LP486E on board Ethernet"
1210 Say Y here to support the 82596-based on-board Ethernet controller
1211 for the Panther motherboard, which is one of the two shipped in the
1212 Intel Professional Workstation.
1215 tristate "ICL EtherTeam 16i/32 support"
1218 If you have a network (Ethernet) card of this type, say Y and read
1219 the Ethernet-HOWTO, available from
1220 <http://www.tldp.org/docs.html#howto>.
1222 To compile this driver as a module, choose M here. The module
1223 will be called eth16i.
1226 tristate "NE2000/NE1000 support"
1227 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1230 If you have a network (Ethernet) card of this type, say Y and read
1231 the Ethernet-HOWTO, available from
1232 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1233 without a specific driver are compatible with NE2000.
1235 If you have a PCI NE2000 card however, say N here and Y to "PCI
1236 NE2000 and clone support" under "EISA, VLB, PCI and on board
1237 controllers" below. If you have a NE2000 card and are running on
1238 an MCA system (a bus system used on some IBM PS/2 computers and
1239 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1242 To compile this driver as a module, choose M here. The module
1246 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1247 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1249 The Zenith Z-Note notebook computer has a built-in network
1250 (Ethernet) card, and this is the Linux driver for it. Note that the
1251 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1252 by this driver. Read the Ethernet-HOWTO, available from
1253 <http://www.tldp.org/docs.html#howto>.
1256 tristate "SEEQ8005 support (EXPERIMENTAL)"
1257 depends on NET_ISA && EXPERIMENTAL
1259 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1260 is for you, read the Ethernet-HOWTO, available from
1261 <http://www.tldp.org/docs.html#howto>.
1263 To compile this driver as a module, choose M here. The module
1264 will be called seeq8005.
1267 tristate "NE/2 (ne2000 MCA version) support"
1268 depends on MCA_LEGACY
1271 If you have a network (Ethernet) card of this type, say Y and read
1272 the Ethernet-HOWTO, available from
1273 <http://www.tldp.org/docs.html#howto>.
1275 To compile this driver as a module, choose M here. The module
1279 tristate "IBM LAN Adapter/A support"
1282 This is a Micro Channel Ethernet adapter. You need to set
1283 CONFIG_MCA to use this driver. It is both available as an in-kernel
1284 driver and as a module.
1286 To compile this driver as a module, choose M here. The only
1287 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1288 will both support 16K and 32K memory windows, however a 32K window
1289 gives a better security against packet losses. Usage of multiple
1290 boards with this driver should be possible, but has not been tested
1291 up to now due to lack of hardware.
1294 tristate "IBM LAN Virtual Ethernet support"
1295 depends on PPC_PSERIES
1297 This driver supports virtual ethernet adapters on newer IBM iSeries
1298 and pSeries systems.
1300 To compile this driver as a module, choose M here. The module will
1303 source "drivers/net/ibm_newemac/Kconfig"
1306 bool "EISA, VLB, PCI and on board controllers"
1307 depends on ISA || EISA || PCI
1309 This is another class of network cards which attach directly to the
1310 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1311 available from <http://www.tldp.org/docs.html#howto>.
1313 Note that the answer to this question doesn't directly affect the
1314 kernel: saying N will just cause the configurator to skip all
1315 the questions about this class of network cards. If you say Y, you
1316 will be asked for your specific card in the following questions. If
1317 you are unsure, say Y.
1320 tristate "AMD PCnet32 PCI support"
1321 depends on NET_PCI && PCI
1325 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1326 answer Y here and read the Ethernet-HOWTO, available from
1327 <http://www.tldp.org/docs.html#howto>.
1329 To compile this driver as a module, choose M here. The module
1330 will be called pcnet32.
1333 tristate "AMD 8111 (new PCI lance) support"
1334 depends on NET_PCI && PCI
1338 If you have an AMD 8111-based PCI lance ethernet card,
1339 answer Y here and read the Ethernet-HOWTO, available from
1340 <http://www.tldp.org/docs.html#howto>.
1342 To compile this driver as a module, choose M here. The module
1343 will be called amd8111e.
1345 config ADAPTEC_STARFIRE
1346 tristate "Adaptec Starfire/DuraLAN support"
1347 depends on NET_PCI && PCI
1351 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1352 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1353 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1356 To compile this driver as a module, choose M here: the module
1357 will be called starfire. This is recommended.
1360 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1361 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1364 If you have a network (Ethernet) card of this type, say Y and read
1365 the Ethernet-HOWTO, available from
1366 <http://www.tldp.org/docs.html#howto>.
1368 To compile this driver as a module, choose M here. The module
1369 will be called ac3200.
1372 tristate "Apricot Xen-II on board Ethernet"
1373 depends on NET_PCI && ISA
1375 If you have a network (Ethernet) controller of this type, say Y and
1376 read the Ethernet-HOWTO, available from
1377 <http://www.tldp.org/docs.html#howto>.
1379 To compile this driver as a module, choose M here. The module
1380 will be called apricot.
1383 tristate "Broadcom 440x/47xx ethernet support"
1384 depends on SSB_POSSIBLE && HAS_DMA
1388 If you have a network (Ethernet) controller of this type, say Y
1389 or M and read the Ethernet-HOWTO, available from
1390 <http://www.tldp.org/docs.html#howto>.
1392 To compile this driver as a module, choose M here. The module
1395 # Auto-select SSB PCI-HOST support, if possible
1396 config B44_PCI_AUTOSELECT
1398 depends on B44 && SSB_PCIHOST_POSSIBLE
1402 # Auto-select SSB PCICORE driver, if possible
1403 config B44_PCICORE_AUTOSELECT
1405 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1406 select SSB_DRIVER_PCICORE
1411 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1415 tristate "nForce Ethernet support"
1416 depends on NET_PCI && PCI
1418 If you have a network (Ethernet) controller of this type, say Y and
1419 read the Ethernet-HOWTO, available from
1420 <http://www.tldp.org/docs.html#howto>.
1422 To compile this driver as a module, choose M here. The module
1423 will be called forcedeth.
1425 config FORCEDETH_NAPI
1426 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1427 depends on FORCEDETH && EXPERIMENTAL
1429 NAPI is a new driver API designed to reduce CPU and interrupt load
1430 when the driver is receiving lots of packets from the card. It is
1431 still somewhat experimental and thus not yet enabled by default.
1433 If your estimated Rx load is 10kpps or more, or if the card will be
1434 deployed on potentially unfriendly networks (e.g. in a firewall),
1440 tristate "CS89x0 support"
1441 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1442 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1444 Support for CS89x0 chipset based Ethernet cards. If you have a
1445 network (Ethernet) card of this type, say Y and read the
1446 Ethernet-HOWTO, available from
1447 <http://www.tldp.org/docs.html#howto> as well as
1448 <file:Documentation/networking/cs89x0.txt>.
1450 To compile this driver as a module, choose M here. The module
1451 will be called cs89x0.
1453 config CS89x0_NONISA_IRQ
1455 depends on CS89x0 != n
1456 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1459 tristate "TOSHIBA TC35815 Ethernet support"
1460 depends on NET_PCI && PCI && MIPS
1464 tristate "Intel(R) PRO/100+ support"
1465 depends on NET_PCI && PCI
1468 This driver supports Intel(R) PRO/100 family of adapters.
1469 To verify that your adapter is supported, find the board ID number
1470 on the adapter. Look for a label that has a barcode and a number
1471 in the format 123456-001 (six digits hyphen three digits).
1473 Use the above information and the Adapter & Driver ID Guide at:
1475 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1477 to identify the adapter.
1479 For the latest Intel PRO/100 network driver for Linux, see:
1481 <http://appsr.intel.com/scripts-df/support_intel.asp>
1483 More specific information on configuring the driver is in
1484 <file:Documentation/networking/e100.txt>.
1486 To compile this driver as a module, choose M here. The module
1487 will be called e100.
1490 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1491 depends on NET_PCI && EISA && EXPERIMENTAL
1494 If you have a network (Ethernet) card of this type, say Y and read
1495 the Ethernet-HOWTO, available from
1496 <http://www.tldp.org/docs.html#howto>.
1498 To compile this driver as a module, choose M here. The module
1499 will be called lne390.
1502 tristate "Myson MTD-8xx PCI Ethernet support"
1503 depends on NET_PCI && PCI
1507 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1508 cards. Specifications and data at
1509 <http://www.myson.com.hk/mtd/datasheet/>.
1512 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1513 depends on NET_PCI && PCI
1516 This driver is for the National Semiconductor DP83810 series,
1517 which is used in cards from PureData, NetGear, Linksys
1518 and others, including the 83815 chip.
1519 More specific information and updates are available from
1520 <http://www.scyld.com/network/natsemi.html>.
1523 tristate "PCI NE2000 and clones support (see help)"
1524 depends on NET_PCI && PCI
1527 This driver is for NE2000 compatible PCI cards. It will not work
1528 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1529 support" below). If you have a PCI NE2000 network (Ethernet) card,
1530 say Y and read the Ethernet-HOWTO, available from
1531 <http://www.tldp.org/docs.html#howto>.
1533 This driver also works for the following NE2000 clone cards:
1534 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1535 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1536 Holtek HT80232 Holtek HT80229
1538 To compile this driver as a module, choose M here. The module
1539 will be called ne2k-pci.
1542 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1543 depends on NET_PCI && EISA && EXPERIMENTAL
1546 If you have a network (Ethernet) card of this type, say Y and read
1547 the Ethernet-HOWTO, available from
1548 <http://www.tldp.org/docs.html#howto>. Note that this driver
1549 will NOT WORK for NE3200 cards as they are completely different.
1551 To compile this driver as a module, choose M here. The module
1552 will be called ne3210.
1555 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1556 depends on NET_PCI && EISA && EXPERIMENTAL
1559 If you have a network (Ethernet) card of this type, say Y and read
1560 the Ethernet-HOWTO, available from
1561 <http://www.tldp.org/docs.html#howto>.
1563 To compile this driver as a module, choose M here. The module
1564 will be called es3210.
1567 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1568 depends on NET_PCI && PCI && EXPERIMENTAL
1572 This is a driver for the Fast Ethernet PCI network cards based on
1573 the RTL8139C+ chips. If you have one of those, say Y and read
1574 the Ethernet-HOWTO, available from
1575 <http://www.tldp.org/docs.html#howto>.
1577 To compile this driver as a module, choose M here: the module
1578 will be called 8139cp. This is recommended.
1581 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1582 depends on NET_PCI && PCI
1586 This is a driver for the Fast Ethernet PCI network cards based on
1587 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1588 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1590 To compile this driver as a module, choose M here: the module
1591 will be called 8139too. This is recommended.
1594 bool "Use PIO instead of MMIO"
1598 This instructs the driver to use programmed I/O ports (PIO) instead
1599 of PCI shared memory (MMIO). This can possibly solve some problems
1600 in case your mainboard has memory consistency issues. If unsure,
1603 config 8139TOO_TUNE_TWISTER
1604 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1607 This implements a function which might come in handy in case you
1608 are using low quality on long cabling. It is required for RealTek
1609 RTL-8139 revision K boards, and totally unused otherwise. It tries
1610 to match the transceiver to the cable characteristics. This is
1611 experimental since hardly documented by the manufacturer.
1615 bool "Support for older RTL-8129/8130 boards"
1618 This enables support for the older and uncommon RTL-8129 and
1619 RTL-8130 chips, which support MII via an external transceiver,
1620 instead of an internal one. Disabling this option will save some
1621 memory by making the code size smaller. If unsure, say Y.
1623 config 8139_OLD_RX_RESET
1624 bool "Use older RX-reset method"
1627 The 8139too driver was recently updated to contain a more rapid
1628 reset sequence, in the face of severe receive errors. This "new"
1629 RX-reset method should be adequate for all boards. But if you
1630 experience problems, you can enable this option to restore the
1631 old RX-reset behavior. If unsure, say N.
1634 tristate "RDC R6040 Fast Ethernet Adapter support"
1635 depends on NET_PCI && PCI
1639 This is a driver for the R6040 Fast Ethernet MACs found in the
1640 the RDC R-321x System-on-chips.
1642 To compile this driver as a module, choose M here: the module
1643 will be called r6040. This is recommended.
1646 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1647 depends on NET_PCI && PCI
1651 This is a driver for the Fast Ethernet PCI network cards based on
1652 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1653 SiS 630 and SiS 540 chipsets.
1655 This driver also supports AMD 79C901 HomePNA so that you can use
1656 your phone line as a network cable.
1658 To compile this driver as a module, choose M here: the module
1659 will be called sis900. This is recommended.
1662 tristate "SMC EtherPower II"
1663 depends on NET_PCI && PCI
1667 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1668 which is based on the SMC83c17x (EPIC/100).
1669 More specific information and updates are available from
1670 <http://www.scyld.com/network/epic100.html>.
1673 tristate "SMSC LAN9420 PCI ethernet adapter support"
1674 depends on NET_PCI && PCI
1679 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1680 Say Y if you want it compiled into the kernel,
1681 and read the Ethernet-HOWTO, available from
1682 <http://www.linuxdoc.org/docs.html#howto>.
1684 This driver is also available as a module. The module will be
1685 called smsc9420. If you want to compile it as a module, say M
1686 here and read <file:Documentation/kbuild/modules.txt>
1689 tristate "Sundance Alta support"
1690 depends on NET_PCI && PCI
1694 This driver is for the Sundance "Alta" chip.
1695 More specific information and updates are available from
1696 <http://www.scyld.com/network/sundance.html>.
1698 config SUNDANCE_MMIO
1699 bool "Use MMIO instead of PIO"
1702 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1703 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1704 is known to solve bugs on certain chips.
1709 tristate "TI ThunderLAN support"
1710 depends on NET_PCI && (PCI || EISA)
1712 If you have a PCI Ethernet network card based on the ThunderLAN chip
1713 which is supported by this driver, say Y and read the
1714 Ethernet-HOWTO, available from
1715 <http://www.tldp.org/docs.html#howto>.
1717 Devices currently supported by this driver are Compaq Netelligent,
1718 Compaq NetFlex and Olicom cards. Please read the file
1719 <file:Documentation/networking/tlan.txt> for more details.
1721 To compile this driver as a module, choose M here. The module
1722 will be called tlan.
1724 Please email feedback to <torben.mathiasen@compaq.com>.
1727 tristate "Micrel KSZ8842"
1728 depends on HAS_IOMEM
1730 This platform driver is for Micrel KSZ8842 / KS8842
1731 2-port ethernet switch chip (managed, VLAN, QoS).
1734 tristate "Micrel KS8851 SPI"
1739 SPI driver for Micrel KS8851 SPI attached network chip.
1742 tristate "Micrel KS8851 MLL"
1743 depends on HAS_IOMEM
1745 This platform driver is for Micrel KS8851 Address/data bus
1746 multiplexed network chip.
1749 tristate "VIA Rhine support"
1750 depends on NET_PCI && PCI
1754 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1755 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1756 Ethernet functions can also be found integrated on South Bridges
1759 To compile this driver as a module, choose M here. The module
1760 will be called via-rhine.
1762 config VIA_RHINE_MMIO
1763 bool "Use MMIO instead of PIO"
1764 depends on VIA_RHINE
1766 This instructs the driver to use PCI shared memory (MMIO) instead of
1767 programmed I/O ports (PIO). Enabling this gives an improvement in
1768 processing time in parts of the driver.
1773 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1774 depends on NET_PCI && PCI && EXPERIMENTAL
1777 This is a driver for the Fast Ethernet PCI network cards based on
1778 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1779 have one of these, say Y here.
1781 To compile this driver as a module, choose M here: the module
1782 will be called sc92031. This is recommended.
1785 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1786 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1789 TI AR7 CPMAC Ethernet support
1792 bool "Pocket and portable adapters"
1795 Cute little network (Ethernet) devices which attach to the parallel
1796 port ("pocket adapters"), commonly used with laptops. If you have
1797 one of those, say Y and read the Ethernet-HOWTO, available from
1798 <http://www.tldp.org/docs.html#howto>.
1800 If you want to plug a network (or some other) card into the PCMCIA
1801 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1802 credit card size extension cards used by all modern laptops), you
1803 need the pcmcia-cs package (location contained in the file
1804 <file:Documentation/Changes>) and you can say N here.
1806 Laptop users should read the Linux Laptop home page at
1807 <http://www.linux-on-laptops.com/> or
1808 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1810 Note that the answer to this question doesn't directly affect the
1811 kernel: saying N will just cause the configurator to skip all
1812 the questions about this class of network devices. If you say Y, you
1813 will be asked for your specific device in the following questions.
1816 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1817 depends on NET_POCKET && PARPORT && X86
1820 This is a network (Ethernet) device which attaches to your parallel
1821 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1822 available from <http://www.tldp.org/docs.html#howto>, if you
1823 want to use this. If you intend to use this driver, you should have
1824 said N to the "Parallel printer support", because the two drivers
1825 don't like each other.
1827 To compile this driver as a module, choose M here: the module
1831 tristate "D-Link DE600 pocket adapter support"
1832 depends on NET_POCKET && PARPORT
1834 This is a network (Ethernet) device which attaches to your parallel
1835 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1836 Ethernet-HOWTO, available from
1837 <http://www.tldp.org/docs.html#howto>, if you want to use
1838 this. It is possible to have several devices share a single parallel
1839 port and it is safe to compile the corresponding drivers into the
1842 To compile this driver as a module, choose M here: the module
1843 will be called de600.
1846 tristate "D-Link DE620 pocket adapter support"
1847 depends on NET_POCKET && PARPORT
1849 This is a network (Ethernet) device which attaches to your parallel
1850 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1851 Ethernet-HOWTO, available from
1852 <http://www.tldp.org/docs.html#howto>, if you want to use
1853 this. It is possible to have several devices share a single parallel
1854 port and it is safe to compile the corresponding drivers into the
1857 To compile this driver as a module, choose M here: the module
1858 will be called de620.
1861 tristate "SGI Seeq ethernet controller support"
1862 depends on SGI_HAS_SEEQ
1864 Say Y here if you have an Seeq based Ethernet network card. This is
1865 used in many Silicon Graphics machines.
1868 tristate "DEC LANCE ethernet controller support"
1869 depends on MACH_DECSTATION
1872 This driver is for the series of Ethernet controllers produced by
1873 DEC (now Compaq) based on the AMD Lance chipset, including the
1874 DEPCA series. (This chipset is better known via the NE2100 cards.)
1877 bool "Motorola 68360 ethernet controller"
1880 Say Y here if you want to use the built-in ethernet controller of
1881 the Motorola 68360 processor.
1884 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1885 depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27 || ARCH_MX35 || ARCH_MX25
1887 Say Y here if you want to use the built-in 10/100 Fast ethernet
1888 controller on some Motorola ColdFire and Freescale i.MX processors.
1891 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1894 Say Y here if you want to use the second built-in 10/100 Fast
1895 ethernet controller on some Motorola ColdFire processors.
1898 tristate "MPC52xx FEC driver"
1899 depends on PPC_MPC52xx && PPC_BESTCOMM
1902 select PPC_BESTCOMM_FEC
1904 This option enables support for the MPC5200's on-chip
1905 Fast Ethernet Controller
1906 If compiled as module, it will be called fec_mpc52xx.
1908 config FEC_MPC52xx_MDIO
1909 bool "MPC52xx FEC MDIO bus driver"
1910 depends on FEC_MPC52xx
1913 The MPC5200's FEC can connect to the Ethernet either with
1914 an external MII PHY chip or 10 Mbps 7-wire interface
1915 (Motorola? industry standard).
1916 If your board uses an external PHY connected to FEC, enable this.
1917 If not sure, enable.
1918 If compiled as module, it will be called fec_mpc52xx_phy.
1921 tristate "NE2000 compatible support for H8/300"
1924 Say Y here if you want to use the NE2000 compatible
1925 controller on the Renesas H8/300 processor.
1928 tristate "Atheros L2 Fast Ethernet support"
1933 This driver supports the Atheros L2 fast ethernet adapter.
1935 To compile this driver as a module, choose M here. The module
1936 will be called atl2.
1938 config XILINX_EMACLITE
1939 tristate "Xilinx 10/100 Ethernet Lite support"
1940 depends on PPC32 || MICROBLAZE
1942 This driver supports the 10/100 Ethernet Lite from Xilinx.
1945 tristate "Broadcom 63xx internal mac support"
1950 This driver supports the ethernet MACs in the Broadcom 63xx
1951 MIPS chipset family (BCM63XX).
1953 source "drivers/net/fs_enet/Kconfig"
1955 endif # NET_ETHERNET
1961 menuconfig NETDEV_1000
1962 bool "Ethernet (1000 Mbit)"
1966 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1967 type of Local Area Network (LAN) in universities and companies.
1969 Say Y here to get to see options for Gigabit Ethernet drivers.
1970 This option alone does not add any kernel code.
1971 Note that drivers supporting both 100 and 1000 MBit may be listed
1972 under "Ethernet (10 or 100MBit)" instead.
1974 If you say N, all options in this submenu will be skipped and disabled.
1979 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1982 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1983 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1984 adapter. The driver allows for using the Jumbo Frame option (9000
1985 bytes/frame) however it requires that your switches can handle this
1986 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1989 To compile this driver as a module, choose M here: the
1990 module will be called acenic.
1992 config ACENIC_OMIT_TIGON_I
1993 bool "Omit support for old Tigon I based AceNICs"
1996 Say Y here if you only have Tigon II based AceNICs and want to leave
1997 out support for the older Tigon I based cards which are no longer
1998 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1999 version)). This will reduce the size of the driver object by
2000 app. 100KB. If you are not sure whether your card is a Tigon I or a
2001 Tigon II, say N here.
2003 The safe and default value for this is N.
2006 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2010 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2012 D-Link DGE-550T Gigabit Ethernet Adapter.
2013 D-Link DL2000-based Gigabit Ethernet Adapter.
2014 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2016 To compile this driver as a module, choose M here: the
2017 module will be called dl2k.
2020 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2023 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2024 adapters. For more information on how to identify your adapter, go
2025 to the Adapter & Driver ID Guide at:
2027 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2029 For general information and support, go to the Intel support
2032 <http://support.intel.com>
2034 More specific information on configuring the driver is in
2035 <file:Documentation/networking/e1000.txt>.
2037 To compile this driver as a module, choose M here. The module
2038 will be called e1000.
2041 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2042 depends on PCI && (!SPARC32 || BROKEN)
2044 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2045 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2046 use the regular e1000 driver For more information on how to
2047 identify your adapter, go to the Adapter & Driver ID Guide at:
2049 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2051 For general information and support, go to the Intel support
2054 <http://support.intel.com>
2056 To compile this driver as a module, choose M here. The module
2057 will be called e1000e.
2060 tristate "IP1000 Gigabit Ethernet support"
2061 depends on PCI && EXPERIMENTAL
2064 This driver supports IP1000 gigabit Ethernet cards.
2066 To compile this driver as a module, choose M here: the module
2067 will be called ipg. This is recommended.
2070 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2073 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2074 adapters. For more information on how to identify your adapter, go
2075 to the Adapter & Driver ID Guide at:
2077 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2079 For general information and support, go to the Intel support
2082 <http://support.intel.com>
2084 More specific information on configuring the driver is in
2085 <file:Documentation/networking/e1000.txt>.
2087 To compile this driver as a module, choose M here. The module
2091 bool "Direct Cache Access (DCA) Support"
2093 depends on IGB && DCA && !(IGB=y && DCA=m)
2095 Say Y here if you want to use Direct Cache Access (DCA) in the
2096 driver. DCA is a method for warming the CPU cache before data
2097 is used, with the intent of lessening the impact of cache misses.
2100 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2103 This driver supports Intel(R) 82576 virtual functions. For more
2104 information on how to identify your adapter, go to the Adapter &
2107 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2109 For general information and support, go to the Intel support
2112 <http://support.intel.com>
2114 More specific information on configuring the driver is in
2115 <file:Documentation/networking/e1000.txt>.
2117 To compile this driver as a module, choose M here. The module
2118 will be called igbvf.
2120 source "drivers/net/ixp2000/Kconfig"
2123 tristate "MyriCOM Gigabit Ethernet support"
2126 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2128 To compile this driver as a module, choose M here: the module
2129 will be called myri_sbus. This is recommended.
2132 tristate "National Semiconductor DP83820 support"
2135 This is a driver for the National Semiconductor DP83820 series
2136 of gigabit ethernet MACs. Cards using this chipset include
2137 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2138 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2142 tristate "Packet Engines Hamachi GNIC-II support"
2146 If you have a Gigabit Ethernet card of this type, say Y and read
2147 the Ethernet-HOWTO, available from
2148 <http://www.tldp.org/docs.html#howto>.
2150 To compile this driver as a module, choose M here. The module will be
2154 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2155 depends on PCI && EXPERIMENTAL
2158 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2159 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2160 used by the Beowulf Linux cluster project. See
2161 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2162 information about this driver in particular and Beowulf in general.
2164 To compile this driver as a module, choose M here: the module
2165 will be called yellowfin. This is recommended.
2168 tristate "Realtek 8169 gigabit ethernet support"
2173 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2175 To compile this driver as a module, choose M here: the module
2176 will be called r8169. This is recommended.
2180 depends on R8169 && VLAN_8021Q
2182 Say Y here for the r8169 driver to support the functions required
2183 by the kernel 802.1Q code.
2188 tristate "SB1250 Gigabit Ethernet support"
2189 depends on SIBYTE_SB1xxx_SOC
2192 This driver supports Gigabit Ethernet interfaces based on the
2193 Broadcom SiByte family of System-On-a-Chip parts. They include
2194 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2197 To compile this driver as a module, choose M here: the module
2198 will be called sb1250-mac.
2201 tristate "SiS190/SiS191 gigabit ethernet support"
2206 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2207 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2208 appear in lan on motherboard designs which are based on SiS 965
2209 and SiS 966 south bridge.
2211 To compile this driver as a module, choose M here: the module
2212 will be called sis190. This is recommended.
2215 tristate "New SysKonnect GigaEthernet support"
2219 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2220 and related Gigabit Ethernet adapters. It is a new smaller driver
2221 with better performance and more complete ethtool support.
2223 It does not support the link failover and network management
2224 features that "portable" vendor supplied sk98lin driver does.
2226 This driver supports adapters based on the original Yukon chipset:
2227 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2228 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2230 It does not support the newer Yukon2 chipset: a separate driver,
2231 sky2, is provided for Yukon2-based adapters.
2233 To compile this driver as a module, choose M here: the module
2234 will be called skge. This is recommended.
2237 bool "Debugging interface"
2238 depends on SKGE && DEBUG_FS
2240 This option adds the ability to dump driver state for debugging.
2241 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2242 transmit and receive rings.
2247 tristate "SysKonnect Yukon2 support"
2251 This driver supports Gigabit Ethernet adapters based on the
2252 Marvell Yukon 2 chipset:
2253 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2254 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2256 There is companion driver for the older Marvell Yukon and
2257 Genesis based adapters: skge.
2259 To compile this driver as a module, choose M here: the module
2260 will be called sky2. This is recommended.
2263 bool "Debugging interface"
2264 depends on SKY2 && DEBUG_FS
2266 This option adds the ability to dump driver state for debugging.
2267 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2268 transmit and receive rings.
2273 tristate "VIA Velocity support"
2279 If you have a VIA "Velocity" based network card say Y here.
2281 To compile this driver as a module, choose M here. The module
2282 will be called via-velocity.
2285 tristate "Broadcom Tigon3 support"
2289 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2291 To compile this driver as a module, choose M here: the module
2292 will be called tg3. This is recommended.
2295 tristate "Broadcom NetXtremeII support"
2300 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2302 To compile this driver as a module, choose M here: the module
2303 will be called bnx2. This is recommended.
2306 tristate "Broadcom CNIC support"
2311 This driver supports offload features of Broadcom NetXtremeII
2312 gigabit Ethernet cards.
2314 To compile this driver as a module, choose M here: the module
2315 will be called cnic. This is recommended.
2318 tristate "Spider Gigabit Ethernet driver"
2319 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2322 This driver supports the Gigabit Ethernet chips present on the
2323 Cell Processor-Based Blades from IBM.
2326 tristate "Tundra TSI108 gigabit Ethernet support"
2327 depends on TSI108_BRIDGE
2329 This driver supports Tundra TSI108 gigabit Ethernet ports.
2330 To compile this driver as a module, choose M here: the module
2331 will be called tsi108_eth.
2334 tristate "PS3 Gigabit Ethernet driver"
2336 select PS3_SYS_MANAGER
2338 This driver supports the network device on the PS3 game
2339 console. This driver has built-in support for Ethernet.
2341 To compile this driver as a module, choose M here: the
2342 module will be called ps3_gelic.
2344 config GELIC_WIRELESS
2345 bool "PS3 Wireless support"
2346 depends on GELIC_NET
2349 This option adds the support for the wireless feature of PS3.
2350 If you have the wireless-less model of PS3 or have no plan to
2351 use wireless feature, disabling this option saves memory. As
2352 the driver automatically distinguishes the models, you can
2353 safely enable this option even if you have a wireless-less model.
2355 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2356 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2357 depends on GELIC_WIRELESS
2359 This option retains the obsolete private interface to pass
2360 the PSK from user space programs to the driver. The PSK
2361 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2362 (WPA-Personal) environment.
2363 If WPA[2]-PSK is used and you need to use old programs that
2364 support only this old interface, say Y. Otherwise N.
2369 tristate "Freescale PQ MDIO"
2373 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2376 tristate "Gianfar Ethernet"
2382 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2383 and MPC86xx family of chips, and the FEC on the 8540.
2386 tristate "Freescale QE Gigabit Ethernet"
2387 depends on QUICC_ENGINE
2391 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2392 which is available on some Freescale SOCs.
2394 config UGETH_TX_ON_DEMAND
2395 bool "Transmit on Demand support"
2399 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2400 depends on MV64X60 || PPC32 || PLAT_ORION
2404 This driver supports the gigabit ethernet MACs in the
2405 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2406 in the Marvell Orion ARM SoC family.
2408 Some boards that use the Discovery chipset are the Momenco
2409 Ocelot C and Jaguar ATX and Pegasos II.
2411 config XILINX_LL_TEMAC
2412 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2414 depends on PPC_DCR_NATIVE
2416 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2417 core used in Xilinx Spartan and Virtex FPGAs
2420 tristate "QLogic QLA3XXX Network Driver Support"
2423 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2425 To compile this driver as a module, choose M here: the module
2426 will be called qla3xxx.
2429 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2434 This driver supports the Atheros/Attansic L1 gigabit ethernet
2437 To compile this driver as a module, choose M here. The module
2438 will be called atl1.
2441 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2442 depends on PCI && EXPERIMENTAL
2446 This driver supports the Atheros L1E gigabit ethernet adapter.
2448 To compile this driver as a module, choose M here. The module
2449 will be called atl1e.
2452 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2453 depends on PCI && EXPERIMENTAL
2457 This driver supports the Atheros L1C gigabit ethernet adapter.
2459 To compile this driver as a module, choose M here. The module
2460 will be called atl1c.
2463 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2468 This driver supports the PCI-Express gigabit ethernet adapters
2469 based on JMicron JMC250 chipset.
2471 To compile this driver as a module, choose M here. The module
2475 tristate "S6105 GMAC ethernet support"
2476 depends on XTENSA_VARIANT_S6000
2479 This driver supports the on chip ethernet device on the
2480 S6105 xtensa processor.
2482 To compile this driver as a module, choose M here. The module
2483 will be called s6gmac.
2488 # 10 Gigabit Ethernet
2491 menuconfig NETDEV_10000
2492 bool "Ethernet (10000 Mbit)"
2496 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2497 This option alone does not add any kernel code.
2499 If you say N, all options in this submenu will be skipped and disabled.
2507 tristate "Chelsio 10Gb Ethernet support"
2512 This driver supports Chelsio gigabit and 10-gigabit
2513 Ethernet cards. More information about adapter features and
2514 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2516 For general information about Chelsio and our products, visit
2517 our website at <http://www.chelsio.com>.
2519 For customer support, please visit our customer support page at
2520 <http://www.chelsio.com/support.htm>.
2522 Please send feedback to <linux-bugs@chelsio.com>.
2524 To compile this driver as a module, choose M here: the module
2525 will be called cxgb.
2527 config CHELSIO_T1_1G
2528 bool "Chelsio gigabit Ethernet support"
2529 depends on CHELSIO_T1
2531 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2532 are using only 10G cards say 'N' here.
2534 config CHELSIO_T3_DEPENDS
2536 depends on PCI && INET
2540 tristate "Chelsio Communications T3 10Gb Ethernet support"
2541 depends on CHELSIO_T3_DEPENDS
2545 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2548 For general information about Chelsio and our products, visit
2549 our website at <http://www.chelsio.com>.
2551 For customer support, please visit our customer support page at
2552 <http://www.chelsio.com/support.htm>.
2554 Please send feedback to <linux-bugs@chelsio.com>.
2556 To compile this driver as a module, choose M here: the module
2557 will be called cxgb3.
2560 tristate "eHEA Ethernet support"
2561 depends on IBMEBUS && INET && SPARSEMEM
2564 This driver supports the IBM pSeries eHEA ethernet adapter.
2566 To compile the driver as a module, choose M here. The module
2567 will be called ehea.
2570 tristate "Cisco 10G Ethernet NIC support"
2571 depends on PCI && INET
2574 This enables the support for the Cisco 10G Ethernet card.
2577 tristate "Intel(R) 10GbE PCI Express adapters support"
2578 depends on PCI && INET
2581 This driver supports Intel(R) 10GbE PCI Express family of
2582 adapters. For more information on how to identify your adapter, go
2583 to the Adapter & Driver ID Guide at:
2585 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2587 For general information and support, go to the Intel support
2590 <http://support.intel.com>
2592 To compile this driver as a module, choose M here. The module
2593 will be called ixgbe.
2596 bool "Direct Cache Access (DCA) Support"
2598 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2600 Say Y here if you want to use Direct Cache Access (DCA) in the
2601 driver. DCA is a method for warming the CPU cache before data
2602 is used, with the intent of lessening the impact of cache misses.
2605 bool "Data Center Bridging (DCB) Support"
2607 depends on IXGBE && DCB
2609 Say Y here if you want to use Data Center Bridging (DCB) in the
2615 tristate "Intel(R) PRO/10GbE support"
2618 This driver supports Intel(R) PRO/10GbE family of adapters for
2619 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2620 instead. For more information on how to identify your adapter, go
2621 to the Adapter & Driver ID Guide at:
2623 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2625 For general information and support, go to the Intel support
2628 <http://support.intel.com>
2630 More specific information on configuring the driver is in
2631 <file:Documentation/networking/ixgb.txt>.
2633 To compile this driver as a module, choose M here. The module
2634 will be called ixgb.
2637 tristate "S2IO 10Gbe XFrame NIC"
2640 This driver supports the 10Gbe XFrame NIC of S2IO.
2641 More specific information on configuring the driver is in
2642 <file:Documentation/networking/s2io.txt>.
2645 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2646 depends on PCI && INET
2648 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2649 I/O Virtualized Server Adapter.
2650 More specific information on configuring the driver is in
2651 <file:Documentation/networking/vxge.txt>.
2653 config VXGE_DEBUG_TRACE_ALL
2654 bool "Enabling All Debug trace statments in driver"
2658 Say Y here if you want to enabling all the debug trace statements in
2659 driver. By default only few debug trace statements are enabled.
2662 tristate "Myricom Myri-10G Ethernet support"
2663 depends on PCI && INET
2668 This driver supports Myricom Myri-10G Dual Protocol interface in
2669 Ethernet mode. If the eeprom on your board is not recent enough,
2670 you will need a newer firmware image.
2671 You may get this image or more information, at:
2673 <http://www.myri.com/scs/download-Myri10GE.html>
2675 To compile this driver as a module, choose M here. The module
2676 will be called myri10ge.
2679 bool "Direct Cache Access (DCA) Support"
2681 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2683 Say Y here if you want to use Direct Cache Access (DCA) in the
2684 driver. DCA is a method for warming the CPU cache before data
2685 is used, with the intent of lessening the impact of cache misses.
2688 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2691 This enables the support for NetXen's Gigabit Ethernet card.
2694 tristate "Sun Neptune 10Gbit Ethernet support"
2697 This enables support for cards based upon Sun's
2701 tristate "PA Semi 1/10Gbit MAC"
2702 depends on PPC_PASEMI && PCI
2706 This driver supports the on-chip 1/10Gbit Ethernet controller on
2707 PA Semi's PWRficient line of chips.
2710 tristate "Mellanox Technologies 10Gbit Ethernet support"
2711 depends on PCI && INET
2715 This driver supports Mellanox Technologies ConnectX Ethernet
2724 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2725 depends on MLX4_CORE
2728 This option causes debugging code to be compiled into the
2729 mlx4_core driver. The output can be turned on via the
2730 debug_level module parameter (which can also be set after
2731 the driver is loaded through sysfs).
2734 tristate "Tehuti Networks 10G Ethernet"
2737 Tehuti Networks 10G Ethernet NIC
2740 tristate "Broadcom NetXtremeII 10Gb support"
2747 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2748 To compile this driver as a module, choose M here: the module
2749 will be called bnx2x. This is recommended.
2752 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2755 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2757 To compile this driver as a module, choose M here: the module
2758 will be called qlge.
2760 source "drivers/net/sfc/Kconfig"
2762 source "drivers/net/benet/Kconfig"
2764 endif # NETDEV_10000
2766 source "drivers/net/tokenring/Kconfig"
2768 source "drivers/net/wireless/Kconfig"
2770 source "drivers/net/wimax/Kconfig"
2772 source "drivers/net/usb/Kconfig"
2774 source "drivers/net/pcmcia/Kconfig"
2776 source "drivers/net/wan/Kconfig"
2778 source "drivers/atm/Kconfig"
2780 source "drivers/ieee802154/Kconfig"
2782 source "drivers/s390/net/Kconfig"
2784 config XEN_NETDEV_FRONTEND
2785 tristate "Xen network device frontend driver"
2789 The network device frontend driver allows the kernel to
2790 access network devices exported exported by a virtual
2791 machine containing a physical network device driver. The
2792 frontend driver is intended for unprivileged guest domains;
2793 if you are compiling a kernel for a Xen guest, you almost
2794 certainly want to enable this.
2797 tristate "iSeries Virtual Ethernet driver support"
2798 depends on PPC_ISERIES
2801 tristate "RapidIO Ethernet over messaging driver support"
2804 config RIONET_TX_SIZE
2805 int "Number of outbound queue entries"
2809 config RIONET_RX_SIZE
2810 int "Number of inbound queue entries"
2815 tristate "FDDI driver support"
2816 depends on (PCI || EISA || TC)
2818 Fiber Distributed Data Interface is a high speed local area network
2819 design; essentially a replacement for high speed Ethernet. FDDI can
2820 run over copper or fiber. If you are connected to such a network and
2821 want a driver for the FDDI card in your computer, say Y here (and
2822 then also Y to the driver for your FDDI card, below). Most people
2826 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2827 depends on FDDI && (PCI || EISA || TC)
2829 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2830 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2831 to a local FDDI network.
2833 To compile this driver as a module, choose M here: the module
2834 will be called defxx. If unsure, say N.
2838 prompt "Use MMIO instead of PIO" if PCI || EISA
2840 default n if PCI || EISA
2843 This instructs the driver to use EISA or PCI memory-mapped I/O
2844 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2845 Enabling this gives an improvement in processing time in parts
2846 of the driver, but it may cause problems with EISA (DEFEA)
2847 adapters. TURBOchannel does not have the concept of I/O ports,
2848 so MMIO is always used for these (DEFTA) adapters.
2853 tristate "SysKonnect FDDI PCI support"
2854 depends on FDDI && PCI
2857 Say Y here if you have a SysKonnect FDDI PCI adapter.
2858 The following adapters are supported by this driver:
2859 - SK-5521 (SK-NET FDDI-UP)
2860 - SK-5522 (SK-NET FDDI-UP DAS)
2861 - SK-5541 (SK-NET FDDI-FP)
2862 - SK-5543 (SK-NET FDDI-LP)
2863 - SK-5544 (SK-NET FDDI-LP DAS)
2864 - SK-5821 (SK-NET FDDI-UP64)
2865 - SK-5822 (SK-NET FDDI-UP64 DAS)
2866 - SK-5841 (SK-NET FDDI-FP64)
2867 - SK-5843 (SK-NET FDDI-LP64)
2868 - SK-5844 (SK-NET FDDI-LP64 DAS)
2869 - Netelligent 100 FDDI DAS Fibre SC
2870 - Netelligent 100 FDDI SAS Fibre SC
2871 - Netelligent 100 FDDI DAS UTP
2872 - Netelligent 100 FDDI SAS UTP
2873 - Netelligent 100 FDDI SAS Fibre MIC
2875 Read <file:Documentation/networking/skfp.txt> for information about
2878 Questions concerning this driver can be addressed to:
2879 <linux@syskonnect.de>
2881 To compile this driver as a module, choose M here: the module
2882 will be called skfp. This is recommended.
2885 bool "HIPPI driver support (EXPERIMENTAL)"
2886 depends on EXPERIMENTAL && INET && PCI
2888 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2889 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2890 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2891 single-mode). HIPPI networks are commonly used for clusters and to
2892 connect to super computers. If you are connected to a HIPPI network
2893 and have a HIPPI network card in your computer that you want to use
2894 under Linux, say Y here (you must also remember to enable the driver
2895 for your HIPPI card below). Most people will say N here.
2898 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2899 depends on HIPPI && PCI
2901 Say Y here if this is your PCI HIPPI network card.
2903 To compile this driver as a module, choose M here: the module
2904 will be called rrunner. If unsure, say N.
2906 config ROADRUNNER_LARGE_RINGS
2907 bool "Use large TX/RX rings (EXPERIMENTAL)"
2908 depends on ROADRUNNER
2910 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2911 of additional memory to allow for fastest operation, both for
2912 transmitting and receiving. This memory cannot be used by any other
2913 kernel code or by user space programs. Say Y here only if you have
2917 tristate "PLIP (parallel port) support"
2920 PLIP (Parallel Line Internet Protocol) is used to create a
2921 reasonably fast mini network consisting of two (or, rarely, more)
2922 local machines. A PLIP link from a Linux box is a popular means to
2923 install a Linux distribution on a machine which doesn't have a
2924 CD-ROM drive (a minimal system has to be transferred with floppies
2925 first). The kernels on both machines need to have this PLIP option
2926 enabled for this to work.
2928 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2929 ports (the connectors at the computers with 25 holes) are connected
2930 with "null printer" or "Turbo Laplink" cables which can transmit 4
2931 bits at a time (mode 0) or with special PLIP cables, to be used on
2932 bidirectional parallel ports only, which can transmit 8 bits at a
2933 time (mode 1); you can find the wiring of these cables in
2934 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2935 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2936 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2937 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2938 and winsock or NCSA's telnet.
2940 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2941 as the NET-3-HOWTO, both available from
2942 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2943 protocol has been changed and this PLIP driver won't work together
2944 with the PLIP support in Linux versions 1.0.x. This option enlarges
2945 your kernel by about 8 KB.
2947 To compile this driver as a module, choose M here. The module
2948 will be called plip. If unsure, say Y or M, in case you buy
2952 tristate "PPP (point-to-point protocol) support"
2955 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2956 the same purpose: sending Internet traffic over telephone (and other
2957 serial) lines. Ask your access provider if they support it, because
2958 otherwise you can't use it; most Internet access providers these
2959 days support PPP rather than SLIP.
2961 To use PPP, you need an additional program called pppd as described
2962 in the PPP-HOWTO, available at
2963 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2964 the version of pppd recommended in <file:Documentation/Changes>.
2965 The PPP option enlarges your kernel by about 16 KB.
2967 There are actually two versions of PPP: the traditional PPP for
2968 asynchronous lines, such as regular analog phone lines, and
2969 synchronous PPP which can be used over digital ISDN lines for
2970 example. If you want to use PPP over phone lines or other
2971 asynchronous serial lines, you need to say Y (or M) here and also to
2972 the next option, "PPP support for async serial ports". For PPP over
2973 synchronous lines, you should say Y (or M) here and to "Support
2974 synchronous PPP", below.
2976 If you said Y to "Version information on all symbols" above, then
2977 you cannot compile the PPP driver into the kernel; you can then only
2978 compile it as a module. To compile this driver as a module, choose M
2979 here. The module will be called ppp_generic.
2981 config PPP_MULTILINK
2982 bool "PPP multilink support (EXPERIMENTAL)"
2983 depends on PPP && EXPERIMENTAL
2985 PPP multilink is a protocol (defined in RFC 1990) which allows you
2986 to combine several (logical or physical) lines into one logical PPP
2987 connection, so that you can utilize your full bandwidth.
2989 This has to be supported at the other end as well and you need a
2990 version of the pppd daemon which understands the multilink protocol.
2995 bool "PPP filtering"
2998 Say Y here if you want to be able to filter the packets passing over
2999 PPP interfaces. This allows you to control which packets count as
3000 activity (i.e. which packets will reset the idle timer or bring up
3001 a demand-dialed link) and which packets are to be dropped entirely.
3002 You need to say Y here if you wish to use the pass-filter and
3003 active-filter options to pppd.
3008 tristate "PPP support for async serial ports"
3012 Say Y (or M) here if you want to be able to use PPP over standard
3013 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3014 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3017 To compile this driver as a module, choose M here.
3022 tristate "PPP support for sync tty ports"
3025 Say Y (or M) here if you want to be able to use PPP over synchronous
3026 (HDLC) tty devices, such as the SyncLink adapter. These devices
3027 are often used for high-speed leased lines like T1/E1.
3029 To compile this driver as a module, choose M here.
3032 tristate "PPP Deflate compression"
3037 Support for the Deflate compression method for PPP, which uses the
3038 Deflate algorithm (the same algorithm that gzip uses) to compress
3039 each PPP packet before it is sent over the wire. The machine at the
3040 other end of the PPP link (usually your ISP) has to support the
3041 Deflate compression method as well for this to be useful. Even if
3042 they don't support it, it is safe to say Y here.
3044 To compile this driver as a module, choose M here.
3047 tristate "PPP BSD-Compress compression"
3050 Support for the BSD-Compress compression method for PPP, which uses
3051 the LZW compression method to compress each PPP packet before it is
3052 sent over the wire. The machine at the other end of the PPP link
3053 (usually your ISP) has to support the BSD-Compress compression
3054 method as well for this to be useful. Even if they don't support it,
3055 it is safe to say Y here.
3057 The PPP Deflate compression method ("PPP Deflate compression",
3058 above) is preferable to BSD-Compress, because it compresses better
3061 Note that the BSD compression code will always be compiled as a
3062 module; it is called bsd_comp and will show up in the directory
3063 modules once you have said "make modules". If unsure, say N.
3066 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3067 depends on PPP && EXPERIMENTAL
3073 Support for the MPPE Encryption protocol, as employed by the
3074 Microsoft Point-to-Point Tunneling Protocol.
3076 See http://pptpclient.sourceforge.net/ for information on
3077 configuring PPTP clients and servers to utilize this method.
3080 tristate "PPP over Ethernet (EXPERIMENTAL)"
3081 depends on EXPERIMENTAL && PPP
3083 Support for PPP over Ethernet.
3085 This driver requires the latest version of pppd from the CVS
3086 repository at cvs.samba.org. Alternatively, see the
3087 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3088 which contains instruction on how to use this driver (under
3089 the heading "Kernel mode PPPoE").
3092 tristate "PPP over ATM"
3093 depends on ATM && PPP
3095 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3096 This implementation does not yet comply with section 8 of RFC2364,
3097 which can lead to bad results if the ATM peer loses state and
3098 changes its encapsulation unilaterally.
3101 tristate "PPP over L2TP (EXPERIMENTAL)"
3102 depends on EXPERIMENTAL && PPP && INET
3104 Support for PPP-over-L2TP socket family. L2TP is a protocol
3105 used by ISPs and enterprises to tunnel PPP traffic over UDP
3106 tunnels. L2TP is replacing PPTP for VPN uses.
3108 This kernel component handles only L2TP data packets: a
3109 userland daemon handles L2TP the control protocol (tunnel
3110 and session setup). One such daemon is OpenL2TP
3111 (http://openl2tp.sourceforge.net/).
3114 tristate "SLIP (serial line) support"
3116 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3117 connect to your Internet service provider or to connect to some
3118 other local Unix box or if you want to configure your Linux box as a
3119 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3120 Internet Protocol) is a protocol used to send Internet traffic over
3121 serial connections such as telephone lines or null modem cables;
3122 nowadays, the protocol PPP is more commonly used for this same
3125 Normally, your access provider has to support SLIP in order for you
3126 to be able to use it, but there is now a SLIP emulator called SLiRP
3127 around (available from
3128 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3129 allows you to use SLIP over a regular dial up shell connection. If
3130 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3131 NET-3-HOWTO, available from
3132 <http://www.tldp.org/docs.html#howto>, explains how to
3133 configure SLIP. Note that you don't need this option if you just
3134 want to run term (term is a program which gives you almost full
3135 Internet connectivity if you have a regular dial up shell account on
3136 some Internet connected Unix computer. Read
3137 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3138 support will enlarge your kernel by about 4 KB. If unsure, say N.
3140 To compile this driver as a module, choose M here. The module
3141 will be called slip.
3143 config SLIP_COMPRESSED
3144 bool "CSLIP compressed headers"
3148 This protocol is faster than SLIP because it uses compression on the
3149 TCP/IP headers (not on the data itself), but it has to be supported
3150 on both ends. Ask your access provider if you are not sure and
3151 answer Y, just in case. You will still be able to use plain SLIP. If
3152 you plan to use SLiRP, the SLIP emulator (available from
3153 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3154 allows you to use SLIP over a regular dial up shell connection, you
3155 definitely want to say Y here. The NET-3-HOWTO, available from
3156 <http://www.tldp.org/docs.html#howto>, explains how to configure
3157 CSLIP. This won't enlarge your kernel.
3162 This option enables Van Jacobsen serial line header compression
3166 bool "Keepalive and linefill"
3169 Adds additional capabilities to the SLIP driver to support the
3170 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3173 config SLIP_MODE_SLIP6
3174 bool "Six bit SLIP encapsulation"
3177 Just occasionally you may need to run IP over hostile serial
3178 networks that don't pass all control characters or are only seven
3179 bit. Saying Y here adds an extra mode you can use with SLIP:
3180 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3181 the serial device. Naturally, this has to be supported at the other
3182 end of the link as well. It's good enough, for example, to run IP
3183 over the async ports of a Camtec JNT Pad. If unsure, say N.
3186 bool "Fibre Channel driver support"
3187 depends on SCSI && PCI
3189 Fibre Channel is a high speed serial protocol mainly used to connect
3190 large storage devices to the computer; it is compatible with and
3191 intended to replace SCSI.
3193 If you intend to use Fibre Channel, you need to have a Fibre channel
3194 adaptor card in your computer; say Y here and to the driver for your
3195 adaptor below. You also should have said Y to "SCSI support" and
3196 "SCSI generic support".
3199 tristate "Network console logging support (EXPERIMENTAL)"
3200 depends on EXPERIMENTAL
3202 If you want to log kernel messages over the network, enable this.
3203 See <file:Documentation/networking/netconsole.txt> for details.
3205 config NETCONSOLE_DYNAMIC
3206 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3207 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3210 This option enables the ability to dynamically reconfigure target
3211 parameters (interface, IP addresses, port numbers, MAC addresses)
3212 at runtime through a userspace interface exported using configfs.
3213 See <file:Documentation/networking/netconsole.txt> for details.
3219 bool "Netpoll traffic trapping"
3223 config NET_POLL_CONTROLLER
3227 tristate "Virtio network driver (EXPERIMENTAL)"
3228 depends on EXPERIMENTAL && VIRTIO
3230 This is the virtual network driver for virtio. It can be used with
3231 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.