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.
28 config COMPAT_NET_DEV_OPS
30 bool "Enable older network device API compatibility"
32 This option enables kernel compatibility with older network devices
33 that do not use net_device_ops interface.
38 tristate "Intermediate Functional Block support"
39 depends on NET_CLS_ACT
41 This is an intermediate driver that allows sharing of
43 To compile this driver as a module, choose M here: the module
44 will be called ifb. If you want to use more than one ifb
45 device at a time, you need to compile this driver as a module.
46 Instead of 'ifb', the devices will then be called 'ifb0',
48 Look at the iproute2 documentation directory for usage etc
51 tristate "Dummy net driver support"
53 This is essentially a bit-bucket device (i.e. traffic you send to
54 this device is consigned into oblivion) with a configurable IP
55 address. It is most commonly used in order to make your currently
56 inactive SLIP address seem like a real address for local programs.
57 If you use SLIP or PPP, you might want to say Y here. Since this
58 thing often comes in handy, the default is Y. It won't enlarge your
59 kernel either. What a deal. Read about it in the Network
60 Administrator's Guide, available from
61 <http://www.tldp.org/docs.html#guide>.
63 To compile this driver as a module, choose M here: the module
64 will be called dummy. If you want to use more than one dummy
65 device at a time, you need to compile this driver as a module.
66 Instead of 'dummy', the devices will then be called 'dummy0',
70 tristate "Bonding driver support"
72 depends on IPV6 || IPV6=n
74 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
75 Channels together. This is called 'Etherchannel' by Cisco,
76 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
78 The driver supports multiple bonding modes to allow for both high
79 performance and high availability operation.
81 Refer to <file:Documentation/networking/bonding.txt> for more
84 To compile this driver as a module, choose M here: the module
85 will be called bonding.
88 tristate "MAC-VLAN support (EXPERIMENTAL)"
89 depends on EXPERIMENTAL
91 This allows one to create virtual interfaces that map packets to
92 or from specific MAC addresses to a particular interface.
94 Macvlan devices can be added using the "ip" command from the
95 iproute2 package starting with the iproute2-2.6.23 release:
97 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
99 To compile this driver as a module, choose M here: the module
100 will be called macvlan.
103 tristate "EQL (serial line load balancing) support"
105 If you have two serial connections to some other computer (this
106 usually requires two modems and two telephone lines) and you use
107 SLIP (the protocol for sending Internet traffic over telephone
108 lines) or PPP (a better SLIP) on them, you can make them behave like
109 one double speed connection using this driver. Naturally, this has
110 to be supported at the other end as well, either with a similar EQL
111 Linux driver or with a Livingston Portmaster 2e.
113 Say Y if you want this and read
114 <file:Documentation/networking/eql.txt>. You may also want to read
115 section 6.2 of the NET-3-HOWTO, available from
116 <http://www.tldp.org/docs.html#howto>.
118 To compile this driver as a module, choose M here: the module
119 will be called eql. If unsure, say N.
122 tristate "Universal TUN/TAP device driver support"
125 TUN/TAP provides packet reception and transmission for user space
126 programs. It can be viewed as a simple Point-to-Point or Ethernet
127 device, which instead of receiving packets from a physical media,
128 receives them from user space program and instead of sending packets
129 via physical media writes them to the user space program.
131 When a program opens /dev/net/tun, driver creates and registers
132 corresponding net device tunX or tapX. After a program closed above
133 devices, driver will automatically delete tunXX or tapXX device and
134 all routes corresponding to it.
136 Please read <file:Documentation/networking/tuntap.txt> for more
139 To compile this driver as a module, choose M here: the module
142 If you don't know what to use this for, you don't need it.
145 tristate "Virtual ethernet pair device"
147 This device is a local ethernet tunnel. Devices are created in pairs.
148 When one end receives the packet it appears on its pair and vice
152 tristate "General Instruments Surfboard 1000"
155 This is a driver for the General Instrument (also known as
156 NextLevel) SURFboard 1000 internal
157 cable modem. This is an ISA card which is used by a number of cable
158 TV companies to provide cable modem access. It's a one-way
159 downstream-only cable modem, meaning that your upstream net link is
160 provided by your regular phone modem.
162 At present this driver only compiles as a module, so say M here if
163 you have this card. The module will be called sb1000. Then read
164 <file:Documentation/networking/README.sb1000> for information on how
165 to use this module, as it needs special ppp scripts for establishing
166 a connection. Further documentation and the necessary scripts can be
169 <http://www.jacksonville.net/~fventuri/>
170 <http://home.adelphia.net/~siglercm/sb1000.html>
171 <http://linuxpower.cx/~cable/>
173 If you don't have this card, of course say N.
175 source "drivers/net/arcnet/Kconfig"
177 source "drivers/net/phy/Kconfig"
183 menuconfig NET_ETHERNET
184 bool "Ethernet (10 or 100Mbit)"
187 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
188 type of Local Area Network (LAN) in universities and companies.
190 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
191 coaxial cable, linking computers in a chain), 10BASE-T or twisted
192 pair (10 Mbps over twisted pair cable, linking computers to central
193 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
194 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
195 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
196 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
197 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
198 Ethernet (1 Gbps over optical fiber or short copper links).
200 If your Linux machine will be connected to an Ethernet and you have
201 an Ethernet network interface card (NIC) installed in your computer,
202 say Y here and read the Ethernet-HOWTO, available from
203 <http://www.tldp.org/docs.html#howto>. You will then also have
204 to say Y to the driver for your particular NIC.
206 Note that the answer to this question won't directly affect the
207 kernel: saying N will just cause the configurator to skip all
208 the questions about Ethernet network cards. If unsure, say N.
213 tristate "Generic Media Independent Interface device support"
215 Most ethernet controllers have MII transceiver either as an external
216 or internal device. It is safe to say Y or M here even if your
217 ethernet card lack MII.
220 tristate "Atmel MACB support"
221 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
224 The Atmel MACB ethernet interface is found on many AT32 and AT91
225 parts. Say Y to include support for the MACB chip.
227 To compile this driver as a module, choose M here: the module
230 source "drivers/net/arm/Kconfig"
233 tristate "ASIX AX88796 NE2000 clone support"
234 depends on ARM || MIPS || SUPERH
238 AX88796 driver, using platform bus to provide
239 chip detection and resources
242 bool "ASIX AX88796 external 93CX6 eeprom support"
246 Select this if your platform comes with an external 93CX6 eeprom.
249 tristate "MACE (Power Mac ethernet) support"
250 depends on PPC_PMAC && PPC32
253 Power Macintoshes and clones with Ethernet built-in on the
254 motherboard will usually use a MACE (Medium Access Control for
255 Ethernet) interface. Say Y to include support for the MACE chip.
257 To compile this driver as a module, choose M here: the module
260 config MACE_AAUI_PORT
261 bool "Use AAUI port instead of TP by default"
264 Some Apple machines (notably the Apple Network Server) which use the
265 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
266 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
267 Y here if you have such a machine. If unsure, say N.
268 The driver will default to AAUI on ANS anyway, and if you use it as
269 a module, you can provide the port_aaui=0|1 to force the driver.
272 tristate "BMAC (G3 ethernet) support"
273 depends on PPC_PMAC && PPC32
276 Say Y for support of BMAC Ethernet interfaces. These are used on G3
279 To compile this driver as a module, choose M here: the module
283 tristate "Ariadne support"
286 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
289 To compile this driver as a module, choose M here: the module
290 will be called ariadne.
293 tristate "A2065 support"
297 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
300 To compile this driver as a module, choose M here: the module
301 will be called a2065.
304 tristate "Hydra support"
308 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
310 To compile this driver as a module, choose M here: the module
311 will be called hydra.
314 tristate "Zorro NS8390-based Ethernet support"
318 This driver is for Zorro Ethernet cards using an NS8390-compatible
319 chipset, like the Village Tronic Ariadne II and the Individual
320 Computers X-Surf Ethernet cards. If you have such a card, say Y.
323 To compile this driver as a module, choose M here: the module
324 will be called zorro8390.
327 tristate "PCMCIA NE2000 support"
328 depends on AMIGA_PCMCIA
331 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
334 To compile this driver as a module, choose M here: the module
338 bool "Macintosh NS 8390 based ethernet cards"
342 If you want to include a driver to support Nubus or LC-PDS
343 Ethernet cards using an NS8390 chipset or its equivalent, say Y
344 and read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
348 tristate "Macintosh CS89x0 based ethernet cards"
351 Support for CS89x0 chipset based Ethernet cards. If you have a
352 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
353 read the Ethernet-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>.
356 To compile this driver as a module, choose M here. This module will
360 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
363 Support for NatSemi SONIC based Ethernet devices. This includes
364 the onboard Ethernet in many Quadras as well as some LC-PDS,
365 a few Nubus and all known Comm Slot Ethernet cards. If you have
366 one of these say Y and read the Ethernet-HOWTO, available from
367 <http://www.tldp.org/docs.html#howto>.
369 To compile this driver as a module, choose M here. This module will
373 bool "Macintosh (AV) onboard MACE ethernet"
377 Support for the onboard AMD 79C940 MACE Ethernet controller used in
378 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
379 say Y and read the Ethernet-HOWTO, available from
380 <http://www.tldp.org/docs.html#howto>.
383 tristate "MVME147 (Lance) Ethernet support"
387 Support for the on-board Ethernet interface on the Motorola MVME147
388 single-board computer. 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 "MVME16x Ethernet support"
396 This is the driver for the Ethernet interface on the Motorola
397 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
398 driver for this chip in your kernel.
399 To compile this driver as a module, choose M here.
402 tristate "BVME6000 Ethernet support"
405 This is the driver for the Ethernet interface on BVME4000 and
406 BVME6000 VME boards. Say Y here to include the driver for this chip
408 To compile this driver as a module, choose M here.
411 tristate "Atari Lance support"
414 Say Y to include support for several Atari Ethernet adapters based
415 on the AMD Lance chipset: RieblCard (with or without battery), or
416 PAMCard VME (also the version by Rhotron, with different addresses).
419 tristate "Sun3/Sun3x on-board LANCE support"
420 depends on SUN3 || SUN3X
422 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
423 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
424 here to compile in the Linux driver for this and enable Ethernet.
425 General Linux information on the Sun 3 and 3x series (now
427 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
429 If you're not building a kernel for a Sun 3, say N.
432 bool "Sun3 on-board Intel 82586 support"
435 This driver enables support for the on-board Intel 82586 based
436 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
437 that this driver does not support 82586-based adapters on additional
441 bool "HP on-board LANCE support"
445 If you want to use the builtin "LANCE" Ethernet controller on an
446 HP300 machine, say Y here.
449 tristate "Lasi ethernet"
452 Say Y here to support the builtin Intel 82596 ethernet controller
453 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
456 tristate "SNI RM ethernet"
457 depends on NET_ETHERNET && SNI_RM
459 Say Y here to support the on-board Intel 82596 ethernet controller
460 built into SNI RM machines.
463 tristate "Korina (IDT RC32434) Ethernet support"
464 depends on NET_ETHERNET && MIKROTIK_RB532
466 If you have a Mikrotik RouterBoard 500 or IDT RC32434
467 based system say Y. Otherwise say N.
469 config MIPS_JAZZ_SONIC
470 tristate "MIPS JAZZ onboard SONIC Ethernet support"
473 This is the driver for the onboard card of MIPS Magnum 4000,
474 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
476 config XTENSA_XT2000_SONIC
477 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
478 depends on XTENSA_PLATFORM_XT2000
480 This is the driver for the onboard card of the Xtensa XT2000 board.
482 config MIPS_AU1X00_ENET
483 bool "MIPS AU1000 Ethernet support"
484 depends on SOC_AU1X00
488 If you have an Alchemy Semi AU1X00 based system
489 say Y. Otherwise, say N.
492 bool "SGI IOC3 Ethernet"
493 depends on PCI && SGI_IP27
497 If you have a network (Ethernet) card of this type, say Y and read
498 the Ethernet-HOWTO, available from
499 <http://www.tldp.org/docs.html#howto>.
502 tristate "MIPS simulator Network device"
505 The MIPSNET device is a simple Ethernet network device which is
506 emulated by the MIPS Simulator.
507 If you are not using a MIPSsim or are unsure, say N.
509 config SGI_O2MACE_ETH
510 tristate "SGI O2 MACE Fast Ethernet support"
511 depends on SGI_IP32=y
514 tristate "National DP83902AV support"
518 Support for cards based on the National Semiconductor DP83902AV
519 ST-NIC Serial Network Interface Controller for Twisted Pair. This
520 is a 10Mbit/sec Ethernet controller. Product overview and specs at
521 <http://www.national.com/pf/DP/DP83902A.html>.
526 tristate "Renesas SuperH Ethernet support"
527 depends on SUPERH && \
528 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
535 Renesas SuperH Ethernet device driver.
536 This driver support SH7710, SH7712, SH7763 and SH7619.
539 tristate "Sun LANCE support"
543 This driver supports the "le" interface present on all 32-bit Sparc
544 systems, on some older Ultra systems and as an Sbus option. These
545 cards are based on the AMD Lance chipset, which is better known
546 via the NE2100 cards.
548 To compile this driver as a module, choose M here: the module
549 will be called sunlance.
552 tristate "Sun Happy Meal 10/100baseT support"
553 depends on SBUS || PCI
556 This driver supports the "hme" interface present on most Ultra
557 systems and as an option on older Sbus systems. This driver supports
558 both PCI and Sbus devices. This driver also supports the "qfe" quad
559 100baseT device available in both PCI and Sbus configurations.
561 To compile this driver as a module, choose M here: the module
562 will be called sunhme.
565 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
566 depends on SBUS && EXPERIMENTAL
569 This driver supports the "be" interface available as an Sbus option.
570 This is Sun's older 100baseT Ethernet device.
572 To compile this driver as a module, choose M here: the module
573 will be called sunbmac.
576 tristate "Sun QuadEthernet support"
580 This driver supports the "qe" 10baseT Ethernet device, available as
581 an Sbus option. Note that this is not the same as Quad FastEthernet
582 "qfe" which is supported by the Happy Meal driver instead.
584 To compile this driver as a module, choose M here: the module
585 will be called sunqe.
588 tristate "Sun GEM support"
592 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
593 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
596 tristate "Sun Cassini support"
600 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
601 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
604 tristate "Sun Virtual Network support"
607 Support for virtual network devices under Sun Logical Domains.
609 config NET_VENDOR_3COM
611 depends on ISA || EISA || MCA || PCI
613 If you have a network (Ethernet) card belonging to this class, say Y
614 and read the Ethernet-HOWTO, available from
615 <http://www.tldp.org/docs.html#howto>.
617 Note that the answer to this question doesn't directly affect the
618 kernel: saying N will just cause the configurator to skip all
619 the questions about 3COM cards. If you say Y, you will be asked for
620 your specific card in the following questions.
623 tristate "3c501 \"EtherLink\" support"
624 depends on NET_VENDOR_3COM && ISA
626 If you have a network (Ethernet) card of this type, say Y and read
627 the Ethernet-HOWTO, available from
628 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
629 new card, since the 3c501 is slow, broken, and obsolete: you will
630 have problems. Some people suggest to ping ("man ping") a nearby
631 machine every minute ("man cron") when using this card.
633 To compile this driver as a module, choose M here. The module
634 will be called 3c501.
637 tristate "3c503 \"EtherLink II\" support"
638 depends on NET_VENDOR_3COM && ISA
641 If you have a network (Ethernet) card of this type, say Y and read
642 the Ethernet-HOWTO, available from
643 <http://www.tldp.org/docs.html#howto>.
645 To compile this driver as a module, choose M here. The module
646 will be called 3c503.
649 tristate "3c505 \"EtherLink Plus\" support"
650 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
652 Information about this network (Ethernet) card can be found in
653 <file:Documentation/networking/3c505.txt>. If you have a card of
654 this type, say Y and read the Ethernet-HOWTO, available from
655 <http://www.tldp.org/docs.html#howto>.
657 To compile this driver as a module, choose M here. The module
658 will be called 3c505.
661 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
662 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
664 If you have a network (Ethernet) card of this type, say Y and read
665 the Ethernet-HOWTO, available from
666 <http://www.tldp.org/docs.html#howto>.
668 To compile this driver as a module, choose M here. The module
669 will be called 3c507.
672 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
673 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
675 If you have a network (Ethernet) card belonging to the 3Com
676 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
677 from <http://www.tldp.org/docs.html#howto>.
679 If your card is not working you may need to use the DOS
680 setup disk to disable Plug & Play mode, and to select the default
683 To compile this driver as a module, choose M here. The module
684 will be called 3c509.
687 tristate "3c515 ISA \"Fast EtherLink\""
688 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
690 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
691 network card, say Y and read the Ethernet-HOWTO, available from
692 <http://www.tldp.org/docs.html#howto>.
694 To compile this driver as a module, choose M here. The module
695 will be called 3c515.
698 tristate "3c523 \"EtherLink/MC\" support"
699 depends on NET_VENDOR_3COM && MCA_LEGACY
701 If you have a network (Ethernet) card of this type, say Y and read
702 the Ethernet-HOWTO, available from
703 <http://www.tldp.org/docs.html#howto>.
705 To compile this driver as a module, choose M here. The module
706 will be called 3c523.
709 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
710 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
712 If you have a network (Ethernet) card of this type, say Y and read
713 the Ethernet-HOWTO, available from
714 <http://www.tldp.org/docs.html#howto>.
716 To compile this driver as a module, choose M here. The module
717 will be called 3c527.
720 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
721 depends on NET_VENDOR_3COM && (PCI || EISA)
724 This option enables driver support for a large number of 10Mbps and
725 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
727 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
728 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
729 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
730 "Tornado" (3c905) PCI
731 "Hurricane" (3c555/3cSOHO) PCI
733 If you have such a card, say Y and read the Ethernet-HOWTO,
734 available from <http://www.tldp.org/docs.html#howto>. More
735 specific information is in
736 <file:Documentation/networking/vortex.txt> and in the comments at
737 the beginning of <file:drivers/net/3c59x.c>.
739 To compile this support as a module, choose M here.
742 tristate "3cr990 series \"Typhoon\" support"
743 depends on NET_VENDOR_3COM && PCI
746 This option enables driver support for the 3cr990 series of cards:
748 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
749 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
750 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
752 If you have a network (Ethernet) card of this type, say Y and read
753 the Ethernet-HOWTO, available from
754 <http://www.tldp.org/docs.html#howto>.
756 To compile this driver as a module, choose M here. The module
757 will be called typhoon.
760 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
761 depends on ISA && ISA_DMA_API
763 If you have a network (Ethernet) card of this type, say Y and read
764 the Ethernet-HOWTO, available from
765 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
768 To compile this driver as a module, choose M here: the module
769 will be called lance. This is recommended.
771 config NET_VENDOR_SMC
772 bool "Western Digital/SMC cards"
773 depends on ISA || MCA || EISA || MAC
775 If you have a network (Ethernet) card belonging to this class, say Y
776 and read the Ethernet-HOWTO, available from
777 <http://www.tldp.org/docs.html#howto>.
779 Note that the answer to this question doesn't directly affect the
780 kernel: saying N will just cause the configurator to skip all
781 the questions about Western Digital cards. If you say Y, you will be
782 asked for your specific card in the following questions.
785 tristate "WD80*3 support"
786 depends on NET_VENDOR_SMC && ISA
789 If you have a network (Ethernet) card of this type, say Y and read
790 the Ethernet-HOWTO, available from
791 <http://www.tldp.org/docs.html#howto>.
793 To compile this driver as a module, choose M here. The module
797 tristate "SMC Ultra MCA support"
798 depends on NET_VENDOR_SMC && MCA
801 If you have a network (Ethernet) card of this type and are running
802 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
803 available from <http://www.tldp.org/docs.html#howto>.
805 To compile this driver as a module, choose M here. The module
806 will be called smc-mca.
809 tristate "SMC Ultra support"
810 depends on NET_VENDOR_SMC && ISA
813 If you have a network (Ethernet) card of this type, say Y and read
814 the Ethernet-HOWTO, available from
815 <http://www.tldp.org/docs.html#howto>.
817 Important: There have been many reports that, with some motherboards
818 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
819 such as some BusLogic models) causes corruption problems with many
820 operating systems. The Linux smc-ultra driver has a work-around for
821 this but keep it in mind if you have such a SCSI card and have
824 To compile this driver as a module, choose M here. The module
825 will be called smc-ultra.
828 tristate "SMC Ultra32 EISA support"
829 depends on NET_VENDOR_SMC && EISA
832 If you have a network (Ethernet) card of this type, say Y and read
833 the Ethernet-HOWTO, available from
834 <http://www.tldp.org/docs.html#howto>.
836 To compile this driver as a module, choose M here. The module
837 will be called smc-ultra32.
840 tristate "Blackfin on-chip MAC support"
841 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
845 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
847 This is the driver for Blackfin on-chip mac device. Say Y if you want it
848 compiled into the kernel. This driver is also available as a module
849 ( = code which can be inserted in and removed from the running kernel
850 whenever you want). The module will be called bfin_mac.
852 config BFIN_MAC_USE_L1
853 bool "Use L1 memory for rx/tx packets"
854 depends on BFIN_MAC && (BF527 || BF537)
857 To get maximum network performance, you should use L1 memory as rx/tx buffers.
858 Say N here if you want to reserve L1 memory for other uses.
860 config BFIN_TX_DESC_NUM
861 int "Number of transmit buffer packets"
863 range 6 10 if BFIN_MAC_USE_L1
867 Set the number of buffer packets used in driver.
869 config BFIN_RX_DESC_NUM
870 int "Number of receive buffer packets"
872 range 20 100 if BFIN_MAC_USE_L1
876 Set the number of buffer packets used in driver.
879 bool "RMII PHY Interface (EXPERIMENTAL)"
880 depends on BFIN_MAC && EXPERIMENTAL
881 default y if BFIN527_EZKIT
882 default n if BFIN537_STAMP
884 Use Reduced PHY MII Interface
887 tristate "SMC 9194 support"
888 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
891 This is support for the SMC9xxx based Ethernet cards. Choose this
892 option if you have a DELL laptop with the docking station, or
893 another SMC9192/9194 based chipset. Say Y if you want it compiled
894 into the kernel, and read the file
895 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
896 available from <http://www.tldp.org/docs.html#howto>.
898 To compile this driver as a module, choose M here. The module
899 will be called smc9194.
902 tristate "SMC 91C9x/91C1xxx support"
905 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
906 MIPS || BLACKFIN || MN10300
908 This is a driver for SMC's 91x series of Ethernet chipsets,
909 including the SMC91C94 and the SMC91C111. Say Y if you want it
910 compiled into the kernel, and read the file
911 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
912 available from <http://www.linuxdoc.org/docs.html#howto>.
914 This driver is also available as a module ( = code which can be
915 inserted in and removed from the running kernel whenever you want).
916 The module will be called smc91x. If you want to compile it as a
917 module, say M here and read <file:Documentation/kbuild/modules.txt>.
920 tristate "NetX Ethernet support"
924 This is support for the Hilscher netX builtin Ethernet ports
926 To compile this driver as a module, choose M here. The module
927 will be called netx-eth.
929 config TI_DAVINCI_EMAC
930 tristate "TI DaVinci EMAC Support"
931 depends on ARM && ARCH_DAVINCI
934 This driver supports TI's DaVinci Ethernet .
936 To compile this driver as a module, choose M here: the module
937 will be called davinci_emac_driver. This is recommended.
940 tristate "DM9000 support"
941 depends on ARM || BLACKFIN || MIPS
945 Support for DM9000 chipset.
947 To compile this driver as a module, choose M here. The module
948 will be called dm9000.
950 config DM9000_DEBUGLEVEL
951 int "DM9000 maximum debug level"
955 The maximum level of debugging code compiled into the DM9000
958 config DM9000_FORCE_SIMPLE_PHY_POLL
959 bool "Force simple NSR based PHY polling"
962 This configuration forces the DM9000 to use the NSR's LinkStatus
963 bit to determine if the link is up or down instead of the more
964 costly MII PHY reads. Note, this will not work if the chip is
965 operating with an external PHY.
968 tristate "ENC28J60 support"
969 depends on EXPERIMENTAL && SPI && NET_ETHERNET
972 Support for the Microchip EN28J60 ethernet chip.
974 To compile this driver as a module, choose M here. The module will be
977 config ENC28J60_WRITEVERIFY
978 bool "Enable write verify"
981 Enable the verify after the buffer write useful for debugging purpose.
985 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
986 depends on NET_ETHERNET && HAS_IOMEM
992 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
995 tristate "SMSC LAN911[5678] support"
998 depends on ARM || SUPERH
1000 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1001 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1002 Say Y if you want it compiled into the kernel,
1003 and read the Ethernet-HOWTO, available from
1004 <http://www.linuxdoc.org/docs.html#howto>.
1006 This driver is also available as a module. The module will be
1007 called smc911x. If you want to compile it as a module, say M
1008 here and read <file:Documentation/kbuild/modules.txt>
1011 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1012 depends on ARM || SUPERH
1017 Say Y here if you want support for SMSC LAN911x and LAN921x families
1018 of ethernet controllers.
1020 To compile this driver as a module, choose M here and read
1021 <file:Documentation/networking/net-modules.txt>. The module
1022 will be called smsc911x.
1024 config NET_VENDOR_RACAL
1025 bool "Racal-Interlan (Micom) NI cards"
1028 If you have a network (Ethernet) card belonging to this class, such
1029 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1030 available from <http://www.tldp.org/docs.html#howto>.
1032 Note that the answer to this question doesn't directly affect the
1033 kernel: saying N will just cause the configurator to skip all
1034 the questions about NI cards. If you say Y, you will be asked for
1035 your specific card in the following questions.
1038 tristate "NI5010 support (EXPERIMENTAL)"
1039 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1041 If you have a network (Ethernet) card of this type, say Y and read
1042 the Ethernet-HOWTO, available from
1043 <http://www.tldp.org/docs.html#howto>. Note that this is still
1046 To compile this driver as a module, choose M here. The module
1047 will be called ni5010.
1050 tristate "NI5210 support"
1051 depends on NET_VENDOR_RACAL && ISA
1053 If you have a network (Ethernet) card of this type, say Y and read
1054 the Ethernet-HOWTO, available from
1055 <http://www.tldp.org/docs.html#howto>.
1057 To compile this driver as a module, choose M here. The module
1058 will be called ni52.
1061 tristate "NI6510 support"
1062 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1064 If you have a network (Ethernet) card of this type, say Y and read
1065 the Ethernet-HOWTO, available from
1066 <http://www.tldp.org/docs.html#howto>.
1068 To compile this driver as a module, choose M here. The module
1069 will be called ni65.
1072 tristate "Dave ethernet support (DNET)"
1073 depends on NET_ETHERNET && HAS_IOMEM
1076 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1077 Say Y to include support for the DNET chip.
1079 To compile this driver as a module, choose M here: the module
1080 will be called dnet.
1082 source "drivers/net/tulip/Kconfig"
1085 tristate "AT1700/1720 support (EXPERIMENTAL)"
1086 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1089 If you have a network (Ethernet) card of this type, say Y and read
1090 the Ethernet-HOWTO, available from
1091 <http://www.tldp.org/docs.html#howto>.
1093 To compile this driver as a module, choose M here. The module
1094 will be called at1700.
1097 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1098 depends on ISA || EISA || MCA
1101 If you have a network (Ethernet) card of this type, say Y and read
1102 the Ethernet-HOWTO, available from
1103 <http://www.tldp.org/docs.html#howto> as well as
1104 <file:drivers/net/depca.c>.
1106 To compile this driver as a module, choose M here. The module
1107 will be called depca.
1110 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1111 depends on ISA || EISA || PCI
1113 If you have a network (Ethernet) card of this type, say Y and read
1114 the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>.
1117 To compile this driver as a module, choose M here. The module
1118 will be called hp100.
1121 bool "Other ISA cards"
1124 If your network (Ethernet) card hasn't been mentioned yet and its
1125 bus system (that's the way the cards talks to the other components
1126 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1127 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1128 available from <http://www.tldp.org/docs.html#howto>.
1132 Note that the answer to this question doesn't directly affect the
1133 kernel: saying N will just cause the configurator to skip all
1134 the remaining ISA network card questions. If you say Y, you will be
1135 asked for your specific card in the following questions.
1138 tristate "Cabletron E21xx support"
1142 If you have a network (Ethernet) card of this type, say Y and read
1143 the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1146 To compile this driver as a module, choose M here. The module
1147 will be called e2100.
1150 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1154 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1155 cards. If this is for you, say Y and read
1156 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1157 well as the Ethernet-HOWTO, available from
1158 <http://www.tldp.org/docs.html#howto>.
1160 To compile this driver as a module, choose M here. The module
1161 will be called ewrk3.
1164 tristate "EtherExpress 16 support"
1167 If you have an EtherExpress16 network (Ethernet) card, say Y and
1168 read the Ethernet-HOWTO, available from
1169 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1170 EtherExpress16 card used to be regarded as a very poor choice
1171 because the driver was very unreliable. We now have a new driver
1172 that should do better.
1174 To compile this driver as a module, choose M here. The module
1175 will be called eexpress.
1178 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1181 If you have a network (Ethernet) card of this type, say Y. This
1182 driver supports Intel i82595{FX,TX} based boards. Note however
1183 that the EtherExpress PRO/100 Ethernet card has its own separate
1184 driver. Please read the Ethernet-HOWTO, available from
1185 <http://www.tldp.org/docs.html#howto>.
1187 To compile this driver as a module, choose M here. The module
1188 will be called eepro.
1191 tristate "HP PCLAN+ (27247B and 27252A) support"
1195 If you have a network (Ethernet) card of this type, say Y and read
1196 the Ethernet-HOWTO, available from
1197 <http://www.tldp.org/docs.html#howto>.
1199 To compile this driver as a module, choose M here. The module
1200 will be called hp-plus.
1203 tristate "HP PCLAN (27245 and other 27xxx series) support"
1207 If you have a network (Ethernet) card of this type, say Y and read
1208 the Ethernet-HOWTO, available from
1209 <http://www.tldp.org/docs.html#howto>.
1211 To compile this driver as a module, choose M here. The module
1215 tristate "LP486E on board Ethernet"
1218 Say Y here to support the 82596-based on-board Ethernet controller
1219 for the Panther motherboard, which is one of the two shipped in the
1220 Intel Professional Workstation.
1223 tristate "ICL EtherTeam 16i/32 support"
1226 If you have a network (Ethernet) card of this type, say Y and read
1227 the Ethernet-HOWTO, available from
1228 <http://www.tldp.org/docs.html#howto>.
1230 To compile this driver as a module, choose M here. The module
1231 will be called eth16i.
1234 tristate "NE2000/NE1000 support"
1235 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1238 If you have a network (Ethernet) card of this type, say Y and read
1239 the Ethernet-HOWTO, available from
1240 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1241 without a specific driver are compatible with NE2000.
1243 If you have a PCI NE2000 card however, say N here and Y to "PCI
1244 NE2000 and clone support" under "EISA, VLB, PCI and on board
1245 controllers" below. If you have a NE2000 card and are running on
1246 an MCA system (a bus system used on some IBM PS/2 computers and
1247 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1250 To compile this driver as a module, choose M here. The module
1254 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1255 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1257 The Zenith Z-Note notebook computer has a built-in network
1258 (Ethernet) card, and this is the Linux driver for it. Note that the
1259 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1260 by this driver. Read the Ethernet-HOWTO, available from
1261 <http://www.tldp.org/docs.html#howto>.
1264 tristate "SEEQ8005 support (EXPERIMENTAL)"
1265 depends on NET_ISA && EXPERIMENTAL
1267 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1268 is for you, read the Ethernet-HOWTO, available from
1269 <http://www.tldp.org/docs.html#howto>.
1271 To compile this driver as a module, choose M here. The module
1272 will be called seeq8005.
1275 tristate "NE/2 (ne2000 MCA version) support"
1276 depends on MCA_LEGACY
1279 If you have a network (Ethernet) card of this type, say Y and read
1280 the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1283 To compile this driver as a module, choose M here. The module
1287 tristate "IBM LAN Adapter/A support"
1290 This is a Micro Channel Ethernet adapter. You need to set
1291 CONFIG_MCA to use this driver. It is both available as an in-kernel
1292 driver and as a module.
1294 To compile this driver as a module, choose M here. The only
1295 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1296 will both support 16K and 32K memory windows, however a 32K window
1297 gives a better security against packet losses. Usage of multiple
1298 boards with this driver should be possible, but has not been tested
1299 up to now due to lack of hardware.
1302 tristate "IBM LAN Virtual Ethernet support"
1303 depends on PPC_PSERIES
1305 This driver supports virtual ethernet adapters on newer IBM iSeries
1306 and pSeries systems.
1308 To compile this driver as a module, choose M here. The module will
1311 source "drivers/net/ibm_newemac/Kconfig"
1314 bool "EISA, VLB, PCI and on board controllers"
1315 depends on ISA || EISA || PCI
1317 This is another class of network cards which attach directly to the
1318 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1319 available from <http://www.tldp.org/docs.html#howto>.
1321 Note that the answer to this question doesn't directly affect the
1322 kernel: saying N will just cause the configurator to skip all
1323 the questions about this class of network cards. If you say Y, you
1324 will be asked for your specific card in the following questions. If
1325 you are unsure, say Y.
1328 tristate "AMD PCnet32 PCI support"
1329 depends on NET_PCI && PCI
1333 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1334 answer Y here and read the Ethernet-HOWTO, available from
1335 <http://www.tldp.org/docs.html#howto>.
1337 To compile this driver as a module, choose M here. The module
1338 will be called pcnet32.
1341 tristate "AMD 8111 (new PCI lance) support"
1342 depends on NET_PCI && PCI
1346 If you have an AMD 8111-based PCI lance ethernet card,
1347 answer Y here and read the Ethernet-HOWTO, available from
1348 <http://www.tldp.org/docs.html#howto>.
1350 To compile this driver as a module, choose M here. The module
1351 will be called amd8111e.
1353 config ADAPTEC_STARFIRE
1354 tristate "Adaptec Starfire/DuraLAN support"
1355 depends on NET_PCI && PCI
1359 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1360 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1361 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1364 To compile this driver as a module, choose M here: the module
1365 will be called starfire. This is recommended.
1368 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1369 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1372 If you have a network (Ethernet) card of this type, say Y and read
1373 the Ethernet-HOWTO, available from
1374 <http://www.tldp.org/docs.html#howto>.
1376 To compile this driver as a module, choose M here. The module
1377 will be called ac3200.
1380 tristate "Apricot Xen-II on board Ethernet"
1381 depends on NET_PCI && ISA
1383 If you have a network (Ethernet) controller of this type, say Y and
1384 read the Ethernet-HOWTO, available from
1385 <http://www.tldp.org/docs.html#howto>.
1387 To compile this driver as a module, choose M here. The module
1388 will be called apricot.
1391 tristate "Broadcom 440x/47xx ethernet support"
1392 depends on SSB_POSSIBLE && HAS_DMA
1396 If you have a network (Ethernet) controller of this type, say Y
1397 or M and read the Ethernet-HOWTO, available from
1398 <http://www.tldp.org/docs.html#howto>.
1400 To compile this driver as a module, choose M here. The module
1403 # Auto-select SSB PCI-HOST support, if possible
1404 config B44_PCI_AUTOSELECT
1406 depends on B44 && SSB_PCIHOST_POSSIBLE
1410 # Auto-select SSB PCICORE driver, if possible
1411 config B44_PCICORE_AUTOSELECT
1413 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1414 select SSB_DRIVER_PCICORE
1419 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1423 tristate "nForce Ethernet support"
1424 depends on NET_PCI && PCI
1426 If you have a network (Ethernet) controller of this type, say Y and
1427 read the Ethernet-HOWTO, available from
1428 <http://www.tldp.org/docs.html#howto>.
1430 To compile this driver as a module, choose M here. The module
1431 will be called forcedeth.
1433 config FORCEDETH_NAPI
1434 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1435 depends on FORCEDETH && EXPERIMENTAL
1437 NAPI is a new driver API designed to reduce CPU and interrupt load
1438 when the driver is receiving lots of packets from the card. It is
1439 still somewhat experimental and thus not yet enabled by default.
1441 If your estimated Rx load is 10kpps or more, or if the card will be
1442 deployed on potentially unfriendly networks (e.g. in a firewall),
1448 tristate "CS89x0 support"
1449 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1450 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1452 Support for CS89x0 chipset based Ethernet cards. If you have a
1453 network (Ethernet) card of this type, say Y and read the
1454 Ethernet-HOWTO, available from
1455 <http://www.tldp.org/docs.html#howto> as well as
1456 <file:Documentation/networking/cs89x0.txt>.
1458 To compile this driver as a module, choose M here. The module
1459 will be called cs89x0.
1461 config CS89x0_NONISA_IRQ
1463 depends on CS89x0 != n
1464 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1467 tristate "TOSHIBA TC35815 Ethernet support"
1468 depends on NET_PCI && PCI && MIPS
1472 tristate "Intel(R) PRO/100+ support"
1473 depends on NET_PCI && PCI
1476 This driver supports Intel(R) PRO/100 family of adapters.
1477 To verify that your adapter is supported, find the board ID number
1478 on the adapter. Look for a label that has a barcode and a number
1479 in the format 123456-001 (six digits hyphen three digits).
1481 Use the above information and the Adapter & Driver ID Guide at:
1483 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1485 to identify the adapter.
1487 For the latest Intel PRO/100 network driver for Linux, see:
1489 <http://appsr.intel.com/scripts-df/support_intel.asp>
1491 More specific information on configuring the driver is in
1492 <file:Documentation/networking/e100.txt>.
1494 To compile this driver as a module, choose M here. The module
1495 will be called e100.
1498 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1499 depends on NET_PCI && EISA && EXPERIMENTAL
1502 If you have a network (Ethernet) card of this type, say Y and read
1503 the Ethernet-HOWTO, available from
1504 <http://www.tldp.org/docs.html#howto>.
1506 To compile this driver as a module, choose M here. The module
1507 will be called lne390.
1510 tristate "Myson MTD-8xx PCI Ethernet support"
1511 depends on NET_PCI && PCI
1515 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1516 cards. Specifications and data at
1517 <http://www.myson.com.hk/mtd/datasheet/>.
1520 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1521 depends on NET_PCI && PCI
1524 This driver is for the National Semiconductor DP83810 series,
1525 which is used in cards from PureData, NetGear, Linksys
1526 and others, including the 83815 chip.
1527 More specific information and updates are available from
1528 <http://www.scyld.com/network/natsemi.html>.
1531 tristate "PCI NE2000 and clones support (see help)"
1532 depends on NET_PCI && PCI
1535 This driver is for NE2000 compatible PCI cards. It will not work
1536 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1537 support" below). If you have a PCI NE2000 network (Ethernet) card,
1538 say Y and read the Ethernet-HOWTO, available from
1539 <http://www.tldp.org/docs.html#howto>.
1541 This driver also works for the following NE2000 clone cards:
1542 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1543 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1544 Holtek HT80232 Holtek HT80229
1546 To compile this driver as a module, choose M here. The module
1547 will be called ne2k-pci.
1550 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1551 depends on NET_PCI && EISA && EXPERIMENTAL
1554 If you have a network (Ethernet) card of this type, say Y and read
1555 the Ethernet-HOWTO, available from
1556 <http://www.tldp.org/docs.html#howto>. Note that this driver
1557 will NOT WORK for NE3200 cards as they are completely different.
1559 To compile this driver as a module, choose M here. The module
1560 will be called ne3210.
1563 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1564 depends on NET_PCI && EISA && EXPERIMENTAL
1567 If you have a network (Ethernet) card of this type, say Y and read
1568 the Ethernet-HOWTO, available from
1569 <http://www.tldp.org/docs.html#howto>.
1571 To compile this driver as a module, choose M here. The module
1572 will be called es3210.
1575 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1576 depends on NET_PCI && PCI && EXPERIMENTAL
1580 This is a driver for the Fast Ethernet PCI network cards based on
1581 the RTL8139C+ chips. If you have one of those, say Y and read
1582 the Ethernet-HOWTO, available from
1583 <http://www.tldp.org/docs.html#howto>.
1585 To compile this driver as a module, choose M here: the module
1586 will be called 8139cp. This is recommended.
1589 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1590 depends on NET_PCI && PCI
1594 This is a driver for the Fast Ethernet PCI network cards based on
1595 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1596 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1598 To compile this driver as a module, choose M here: the module
1599 will be called 8139too. This is recommended.
1602 bool "Use PIO instead of MMIO"
1606 This instructs the driver to use programmed I/O ports (PIO) instead
1607 of PCI shared memory (MMIO). This can possibly solve some problems
1608 in case your mainboard has memory consistency issues. If unsure,
1611 config 8139TOO_TUNE_TWISTER
1612 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1615 This implements a function which might come in handy in case you
1616 are using low quality on long cabling. It is required for RealTek
1617 RTL-8139 revision K boards, and totally unused otherwise. It tries
1618 to match the transceiver to the cable characteristics. This is
1619 experimental since hardly documented by the manufacturer.
1623 bool "Support for older RTL-8129/8130 boards"
1626 This enables support for the older and uncommon RTL-8129 and
1627 RTL-8130 chips, which support MII via an external transceiver,
1628 instead of an internal one. Disabling this option will save some
1629 memory by making the code size smaller. If unsure, say Y.
1631 config 8139_OLD_RX_RESET
1632 bool "Use older RX-reset method"
1635 The 8139too driver was recently updated to contain a more rapid
1636 reset sequence, in the face of severe receive errors. This "new"
1637 RX-reset method should be adequate for all boards. But if you
1638 experience problems, you can enable this option to restore the
1639 old RX-reset behavior. If unsure, say N.
1642 tristate "RDC R6040 Fast Ethernet Adapter support"
1643 depends on NET_PCI && PCI
1647 This is a driver for the R6040 Fast Ethernet MACs found in the
1648 the RDC R-321x System-on-chips.
1650 To compile this driver as a module, choose M here: the module
1651 will be called r6040. This is recommended.
1654 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1655 depends on NET_PCI && PCI
1659 This is a driver for the Fast Ethernet PCI network cards based on
1660 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1661 SiS 630 and SiS 540 chipsets.
1663 This driver also supports AMD 79C901 HomePNA so that you can use
1664 your phone line as a network cable.
1666 To compile this driver as a module, choose M here: the module
1667 will be called sis900. This is recommended.
1670 tristate "SMC EtherPower II"
1671 depends on NET_PCI && PCI
1675 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1676 which is based on the SMC83c17x (EPIC/100).
1677 More specific information and updates are available from
1678 <http://www.scyld.com/network/epic100.html>.
1681 tristate "SMSC LAN9420 PCI ethernet adapter support"
1682 depends on NET_PCI && PCI
1687 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1688 Say Y if you want it compiled into the kernel,
1689 and read the Ethernet-HOWTO, available from
1690 <http://www.linuxdoc.org/docs.html#howto>.
1692 This driver is also available as a module. The module will be
1693 called smsc9420. If you want to compile it as a module, say M
1694 here and read <file:Documentation/kbuild/modules.txt>
1697 tristate "Sundance Alta support"
1698 depends on NET_PCI && PCI
1702 This driver is for the Sundance "Alta" chip.
1703 More specific information and updates are available from
1704 <http://www.scyld.com/network/sundance.html>.
1706 config SUNDANCE_MMIO
1707 bool "Use MMIO instead of PIO"
1710 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1711 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1712 is known to solve bugs on certain chips.
1717 tristate "TI ThunderLAN support"
1718 depends on NET_PCI && (PCI || EISA)
1720 If you have a PCI Ethernet network card based on the ThunderLAN chip
1721 which is supported by this driver, say Y and read the
1722 Ethernet-HOWTO, available from
1723 <http://www.tldp.org/docs.html#howto>.
1725 Devices currently supported by this driver are Compaq Netelligent,
1726 Compaq NetFlex and Olicom cards. Please read the file
1727 <file:Documentation/networking/tlan.txt> for more details.
1729 To compile this driver as a module, choose M here. The module
1730 will be called tlan.
1732 Please email feedback to <torben.mathiasen@compaq.com>.
1735 tristate "VIA Rhine support"
1736 depends on NET_PCI && PCI
1740 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1741 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1742 Ethernet functions can also be found integrated on South Bridges
1745 To compile this driver as a module, choose M here. The module
1746 will be called via-rhine.
1748 config VIA_RHINE_MMIO
1749 bool "Use MMIO instead of PIO"
1750 depends on VIA_RHINE
1752 This instructs the driver to use PCI shared memory (MMIO) instead of
1753 programmed I/O ports (PIO). Enabling this gives an improvement in
1754 processing time in parts of the driver.
1759 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1760 depends on NET_PCI && PCI && EXPERIMENTAL
1763 This is a driver for the Fast Ethernet PCI network cards based on
1764 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1765 have one of these, say Y here.
1767 To compile this driver as a module, choose M here: the module
1768 will be called sc92031. This is recommended.
1771 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1772 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1775 TI AR7 CPMAC Ethernet support
1778 bool "Pocket and portable adapters"
1781 Cute little network (Ethernet) devices which attach to the parallel
1782 port ("pocket adapters"), commonly used with laptops. If you have
1783 one of those, say Y and read the Ethernet-HOWTO, available from
1784 <http://www.tldp.org/docs.html#howto>.
1786 If you want to plug a network (or some other) card into the PCMCIA
1787 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1788 credit card size extension cards used by all modern laptops), you
1789 need the pcmcia-cs package (location contained in the file
1790 <file:Documentation/Changes>) and you can say N here.
1792 Laptop users should read the Linux Laptop home page at
1793 <http://www.linux-on-laptops.com/> or
1794 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1796 Note that the answer to this question doesn't directly affect the
1797 kernel: saying N will just cause the configurator to skip all
1798 the questions about this class of network devices. If you say Y, you
1799 will be asked for your specific device in the following questions.
1802 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1803 depends on NET_POCKET && PARPORT && X86
1806 This is a network (Ethernet) device which attaches to your parallel
1807 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1808 available from <http://www.tldp.org/docs.html#howto>, if you
1809 want to use this. If you intend to use this driver, you should have
1810 said N to the "Parallel printer support", because the two drivers
1811 don't like each other.
1813 To compile this driver as a module, choose M here: the module
1817 tristate "D-Link DE600 pocket adapter support"
1818 depends on NET_POCKET && PARPORT
1820 This is a network (Ethernet) device which attaches to your parallel
1821 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1822 Ethernet-HOWTO, available from
1823 <http://www.tldp.org/docs.html#howto>, if you want to use
1824 this. It is possible to have several devices share a single parallel
1825 port and it is safe to compile the corresponding drivers into the
1828 To compile this driver as a module, choose M here: the module
1829 will be called de600.
1832 tristate "D-Link DE620 pocket adapter support"
1833 depends on NET_POCKET && PARPORT
1835 This is a network (Ethernet) device which attaches to your parallel
1836 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1837 Ethernet-HOWTO, available from
1838 <http://www.tldp.org/docs.html#howto>, if you want to use
1839 this. It is possible to have several devices share a single parallel
1840 port and it is safe to compile the corresponding drivers into the
1843 To compile this driver as a module, choose M here: the module
1844 will be called de620.
1847 tristate "SGI Seeq ethernet controller support"
1848 depends on SGI_HAS_SEEQ
1850 Say Y here if you have an Seeq based Ethernet network card. This is
1851 used in many Silicon Graphics machines.
1854 tristate "DEC LANCE ethernet controller support"
1855 depends on MACH_DECSTATION
1858 This driver is for the series of Ethernet controllers produced by
1859 DEC (now Compaq) based on the AMD Lance chipset, including the
1860 DEPCA series. (This chipset is better known via the NE2100 cards.)
1863 bool "Motorola 68360 ethernet controller"
1866 Say Y here if you want to use the built-in ethernet controller of
1867 the Motorola 68360 processor.
1870 bool "FEC ethernet controller (of ColdFire CPUs)"
1871 depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27
1873 Say Y here if you want to use the built-in 10/100 Fast ethernet
1874 controller on some Motorola ColdFire and Freescale i.MX processors.
1877 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1880 Say Y here if you want to use the second built-in 10/100 Fast
1881 ethernet controller on some Motorola ColdFire processors.
1884 tristate "MPC52xx FEC driver"
1885 depends on PPC_MPC52xx && PPC_BESTCOMM
1888 select PPC_BESTCOMM_FEC
1890 This option enables support for the MPC5200's on-chip
1891 Fast Ethernet Controller
1892 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1894 config FEC_MPC52xx_MDIO
1895 bool "MPC52xx FEC MDIO bus driver"
1896 depends on FEC_MPC52xx
1899 The MPC5200's FEC can connect to the Ethernet either with
1900 an external MII PHY chip or 10 Mbps 7-wire interface
1901 (Motorola? industry standard).
1902 If your board uses an external PHY connected to FEC, enable this.
1903 If not sure, enable.
1904 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1907 tristate "NE2000 compatible support for H8/300"
1910 Say Y here if you want to use the NE2000 compatible
1911 controller on the Renesas H8/300 processor.
1914 tristate "Atheros L2 Fast Ethernet support"
1919 This driver supports the Atheros L2 fast ethernet adapter.
1921 To compile this driver as a module, choose M here. The module
1922 will be called atl2.
1924 source "drivers/net/fs_enet/Kconfig"
1926 endif # NET_ETHERNET
1932 menuconfig NETDEV_1000
1933 bool "Ethernet (1000 Mbit)"
1937 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1938 type of Local Area Network (LAN) in universities and companies.
1940 Say Y here to get to see options for Gigabit Ethernet drivers.
1941 This option alone does not add any kernel code.
1942 Note that drivers supporting both 100 and 1000 MBit may be listed
1943 under "Ethernet (10 or 100MBit)" instead.
1945 If you say N, all options in this submenu will be skipped and disabled.
1950 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1953 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1954 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1955 adapter. The driver allows for using the Jumbo Frame option (9000
1956 bytes/frame) however it requires that your switches can handle this
1957 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1960 To compile this driver as a module, choose M here: the
1961 module will be called acenic.
1963 config ACENIC_OMIT_TIGON_I
1964 bool "Omit support for old Tigon I based AceNICs"
1967 Say Y here if you only have Tigon II based AceNICs and want to leave
1968 out support for the older Tigon I based cards which are no longer
1969 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1970 version)). This will reduce the size of the driver object by
1971 app. 100KB. If you are not sure whether your card is a Tigon I or a
1972 Tigon II, say N here.
1974 The safe and default value for this is N.
1977 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1981 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1983 D-Link DGE-550T Gigabit Ethernet Adapter.
1984 D-Link DL2000-based Gigabit Ethernet Adapter.
1985 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1987 To compile this driver as a module, choose M here: the
1988 module will be called dl2k.
1991 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1994 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1995 adapters. For more information on how to identify your adapter, go
1996 to the Adapter & Driver ID Guide at:
1998 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2000 For general information and support, go to the Intel support
2003 <http://support.intel.com>
2005 More specific information on configuring the driver is in
2006 <file:Documentation/networking/e1000.txt>.
2008 To compile this driver as a module, choose M here. The module
2009 will be called e1000.
2012 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2013 depends on PCI && (!SPARC32 || BROKEN)
2015 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2016 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2017 use the regular e1000 driver For more information on how to
2018 identify your adapter, go to the Adapter & Driver ID Guide at:
2020 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2022 For general information and support, go to the Intel support
2025 <http://support.intel.com>
2027 To compile this driver as a module, choose M here. The module
2028 will be called e1000e.
2031 tristate "IP1000 Gigabit Ethernet support"
2032 depends on PCI && EXPERIMENTAL
2035 This driver supports IP1000 gigabit Ethernet cards.
2037 To compile this driver as a module, choose M here: the module
2038 will be called ipg. This is recommended.
2041 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2044 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2045 adapters. For more information on how to identify your adapter, go
2046 to the Adapter & Driver ID Guide at:
2048 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2050 For general information and support, go to the Intel support
2053 <http://support.intel.com>
2055 More specific information on configuring the driver is in
2056 <file:Documentation/networking/e1000.txt>.
2058 To compile this driver as a module, choose M here. The module
2062 bool "Direct Cache Access (DCA) Support"
2064 depends on IGB && DCA && !(IGB=y && DCA=m)
2066 Say Y here if you want to use Direct Cache Access (DCA) in the
2067 driver. DCA is a method for warming the CPU cache before data
2068 is used, with the intent of lessening the impact of cache misses.
2071 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2074 This driver supports Intel(R) 82576 virtual functions. For more
2075 information on how to identify your adapter, go to the Adapter &
2078 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2080 For general information and support, go to the Intel support
2083 <http://support.intel.com>
2085 More specific information on configuring the driver is in
2086 <file:Documentation/networking/e1000.txt>.
2088 To compile this driver as a module, choose M here. The module
2089 will be called igbvf.
2091 source "drivers/net/ixp2000/Kconfig"
2094 tristate "MyriCOM Gigabit Ethernet support"
2097 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2099 To compile this driver as a module, choose M here: the module
2100 will be called myri_sbus. This is recommended.
2103 tristate "National Semiconductor DP83820 support"
2106 This is a driver for the National Semiconductor DP83820 series
2107 of gigabit ethernet MACs. Cards using this chipset include
2108 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2109 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2113 tristate "Packet Engines Hamachi GNIC-II support"
2117 If you have a Gigabit Ethernet card of this type, say Y and read
2118 the Ethernet-HOWTO, available from
2119 <http://www.tldp.org/docs.html#howto>.
2121 To compile this driver as a module, choose M here. The module will be
2125 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2126 depends on PCI && EXPERIMENTAL
2129 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2130 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2131 used by the Beowulf Linux cluster project. See
2132 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2133 information about this driver in particular and Beowulf in general.
2135 To compile this driver as a module, choose M here: the module
2136 will be called yellowfin. This is recommended.
2139 tristate "Realtek 8169 gigabit ethernet support"
2144 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2146 To compile this driver as a module, choose M here: the module
2147 will be called r8169. This is recommended.
2151 depends on R8169 && VLAN_8021Q
2153 Say Y here for the r8169 driver to support the functions required
2154 by the kernel 802.1Q code.
2159 tristate "SB1250 Gigabit Ethernet support"
2160 depends on SIBYTE_SB1xxx_SOC
2163 This driver supports Gigabit Ethernet interfaces based on the
2164 Broadcom SiByte family of System-On-a-Chip parts. They include
2165 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2168 To compile this driver as a module, choose M here: the module
2169 will be called sb1250-mac.
2172 tristate "SiS190/SiS191 gigabit ethernet support"
2177 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2178 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2179 appear in lan on motherboard designs which are based on SiS 965
2180 and SiS 966 south bridge.
2182 To compile this driver as a module, choose M here: the module
2183 will be called sis190. This is recommended.
2186 tristate "New SysKonnect GigaEthernet support"
2190 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2191 and related Gigabit Ethernet adapters. It is a new smaller driver
2192 with better performance and more complete ethtool support.
2194 It does not support the link failover and network management
2195 features that "portable" vendor supplied sk98lin driver does.
2197 This driver supports adapters based on the original Yukon chipset:
2198 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2199 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2201 It does not support the newer Yukon2 chipset: a separate driver,
2202 sky2, is provided for Yukon2-based adapters.
2204 To compile this driver as a module, choose M here: the module
2205 will be called skge. This is recommended.
2208 bool "Debugging interface"
2209 depends on SKGE && DEBUG_FS
2211 This option adds the ability to dump driver state for debugging.
2212 The file debugfs/skge/ethX displays the state of the internal
2213 transmit and receive rings.
2218 tristate "SysKonnect Yukon2 support"
2222 This driver supports Gigabit Ethernet adapters based on the
2223 Marvell Yukon 2 chipset:
2224 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2225 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2227 There is companion driver for the older Marvell Yukon and
2228 Genesis based adapters: skge.
2230 To compile this driver as a module, choose M here: the module
2231 will be called sky2. This is recommended.
2234 bool "Debugging interface"
2235 depends on SKY2 && DEBUG_FS
2237 This option adds the ability to dump driver state for debugging.
2238 The file debugfs/sky2/ethX displays the state of the internal
2239 transmit and receive rings.
2244 tristate "VIA Velocity support"
2250 If you have a VIA "Velocity" based network card say Y here.
2252 To compile this driver as a module, choose M here. The module
2253 will be called via-velocity.
2256 tristate "Broadcom Tigon3 support"
2260 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2262 To compile this driver as a module, choose M here: the module
2263 will be called tg3. This is recommended.
2266 tristate "Broadcom NetXtremeII support"
2271 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2273 To compile this driver as a module, choose M here: the module
2274 will be called bnx2. This is recommended.
2277 tristate "Spider Gigabit Ethernet driver"
2278 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2281 This driver supports the Gigabit Ethernet chips present on the
2282 Cell Processor-Based Blades from IBM.
2285 tristate "Tundra TSI108 gigabit Ethernet support"
2286 depends on TSI108_BRIDGE
2288 This driver supports Tundra TSI108 gigabit Ethernet ports.
2289 To compile this driver as a module, choose M here: the module
2290 will be called tsi108_eth.
2293 tristate "PS3 Gigabit Ethernet driver"
2295 select PS3_SYS_MANAGER
2297 This driver supports the network device on the PS3 game
2298 console. This driver has built-in support for Ethernet.
2300 To compile this driver as a module, choose M here: the
2301 module will be called ps3_gelic.
2303 config GELIC_WIRELESS
2304 bool "PS3 Wireless support"
2305 depends on GELIC_NET
2308 This option adds the support for the wireless feature of PS3.
2309 If you have the wireless-less model of PS3 or have no plan to
2310 use wireless feature, disabling this option saves memory. As
2311 the driver automatically distinguishes the models, you can
2312 safely enable this option even if you have a wireless-less model.
2314 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2315 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2316 depends on GELIC_WIRELESS
2318 This option retains the obsolete private interface to pass
2319 the PSK from user space programs to the driver. The PSK
2320 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2321 (WPA-Personal) environment.
2322 If WPA[2]-PSK is used and you need to use old programs that
2323 support only this old interface, say Y. Otherwise N.
2328 tristate "Freescale PQ MDIO"
2332 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2335 tristate "Gianfar Ethernet"
2341 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2342 and MPC86xx family of chips, and the FEC on the 8540.
2345 tristate "Freescale QE Gigabit Ethernet"
2346 depends on QUICC_ENGINE
2350 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2351 which is available on some Freescale SOCs.
2353 config UGETH_MAGIC_PACKET
2354 bool "Magic Packet detection support"
2357 config UGETH_TX_ON_DEMAND
2358 bool "Transmit on Demand support"
2362 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2363 depends on MV64360 || MV64X60 || PPC32 || PLAT_ORION
2367 This driver supports the gigabit ethernet MACs in the
2368 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2369 in the Marvell Orion ARM SoC family.
2371 Some boards that use the Discovery chipset are the Momenco
2372 Ocelot C and Jaguar ATX and Pegasos II.
2374 config XILINX_LL_TEMAC
2375 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2377 depends on PPC_DCR_NATIVE
2379 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2380 core used in Xilinx Spartan and Virtex FPGAs
2383 tristate "QLogic QLA3XXX Network Driver Support"
2386 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2388 To compile this driver as a module, choose M here: the module
2389 will be called qla3xxx.
2392 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2397 This driver supports the Atheros/Attansic L1 gigabit ethernet
2400 To compile this driver as a module, choose M here. The module
2401 will be called atl1.
2404 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2405 depends on PCI && EXPERIMENTAL
2409 This driver supports the Atheros L1E gigabit ethernet adapter.
2411 To compile this driver as a module, choose M here. The module
2412 will be called atl1e.
2415 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2416 depends on PCI && EXPERIMENTAL
2420 This driver supports the Atheros L1C gigabit ethernet adapter.
2422 To compile this driver as a module, choose M here. The module
2423 will be called atl1c.
2426 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2431 This driver supports the PCI-Express gigabit ethernet adapters
2432 based on JMicron JMC250 chipset.
2434 To compile this driver as a module, choose M here. The module
2440 # 10 Gigabit Ethernet
2443 menuconfig NETDEV_10000
2444 bool "Ethernet (10000 Mbit)"
2448 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2449 This option alone does not add any kernel code.
2451 If you say N, all options in this submenu will be skipped and disabled.
2459 tristate "Chelsio 10Gb Ethernet support"
2464 This driver supports Chelsio gigabit and 10-gigabit
2465 Ethernet cards. More information about adapter features and
2466 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2468 For general information about Chelsio and our products, visit
2469 our website at <http://www.chelsio.com>.
2471 For customer support, please visit our customer support page at
2472 <http://www.chelsio.com/support.htm>.
2474 Please send feedback to <linux-bugs@chelsio.com>.
2476 To compile this driver as a module, choose M here: the module
2477 will be called cxgb.
2479 config CHELSIO_T1_1G
2480 bool "Chelsio gigabit Ethernet support"
2481 depends on CHELSIO_T1
2483 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2484 are using only 10G cards say 'N' here.
2486 config CHELSIO_T3_DEPENDS
2488 depends on PCI && INET
2492 tristate "Chelsio Communications T3 10Gb Ethernet support"
2493 depends on CHELSIO_T3_DEPENDS
2497 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2500 For general information about Chelsio and our products, visit
2501 our website at <http://www.chelsio.com>.
2503 For customer support, please visit our customer support page at
2504 <http://www.chelsio.com/support.htm>.
2506 Please send feedback to <linux-bugs@chelsio.com>.
2508 To compile this driver as a module, choose M here: the module
2509 will be called cxgb3.
2512 tristate "eHEA Ethernet support"
2513 depends on IBMEBUS && INET && SPARSEMEM
2516 This driver supports the IBM pSeries eHEA ethernet adapter.
2518 To compile the driver as a module, choose M here. The module
2519 will be called ehea.
2522 tristate "Cisco 10G Ethernet NIC support"
2523 depends on PCI && INET
2526 This enables the support for the Cisco 10G Ethernet card.
2529 tristate "Intel(R) 10GbE PCI Express adapters support"
2530 depends on PCI && INET
2533 This driver supports Intel(R) 10GbE PCI Express family of
2534 adapters. For more information on how to identify your adapter, go
2535 to the Adapter & Driver ID Guide at:
2537 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2539 For general information and support, go to the Intel support
2542 <http://support.intel.com>
2544 To compile this driver as a module, choose M here. The module
2545 will be called ixgbe.
2548 bool "Direct Cache Access (DCA) Support"
2550 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2552 Say Y here if you want to use Direct Cache Access (DCA) in the
2553 driver. DCA is a method for warming the CPU cache before data
2554 is used, with the intent of lessening the impact of cache misses.
2557 bool "Data Center Bridging (DCB) Support"
2559 depends on IXGBE && DCB
2561 Say Y here if you want to use Data Center Bridging (DCB) in the
2567 tristate "Intel(R) PRO/10GbE support"
2570 This driver supports Intel(R) PRO/10GbE family of adapters for
2571 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2572 instead. For more information on how to identify your adapter, go
2573 to the Adapter & Driver ID Guide at:
2575 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2577 For general information and support, go to the Intel support
2580 <http://support.intel.com>
2582 More specific information on configuring the driver is in
2583 <file:Documentation/networking/ixgb.txt>.
2585 To compile this driver as a module, choose M here. The module
2586 will be called ixgb.
2589 tristate "S2IO 10Gbe XFrame NIC"
2592 This driver supports the 10Gbe XFrame NIC of S2IO.
2593 More specific information on configuring the driver is in
2594 <file:Documentation/networking/s2io.txt>.
2597 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2598 depends on PCI && INET
2600 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2601 I/O Virtualized Server Adapter.
2602 More specific information on configuring the driver is in
2603 <file:Documentation/networking/vxge.txt>.
2605 config VXGE_DEBUG_TRACE_ALL
2606 bool "Enabling All Debug trace statments in driver"
2610 Say Y here if you want to enabling all the debug trace statements in
2611 driver. By default only few debug trace statements are enabled.
2614 tristate "Myricom Myri-10G Ethernet support"
2615 depends on PCI && INET
2620 This driver supports Myricom Myri-10G Dual Protocol interface in
2621 Ethernet mode. If the eeprom on your board is not recent enough,
2622 you will need a newer firmware image.
2623 You may get this image or more information, at:
2625 <http://www.myri.com/scs/download-Myri10GE.html>
2627 To compile this driver as a module, choose M here. The module
2628 will be called myri10ge.
2631 bool "Direct Cache Access (DCA) Support"
2633 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2635 Say Y here if you want to use Direct Cache Access (DCA) in the
2636 driver. DCA is a method for warming the CPU cache before data
2637 is used, with the intent of lessening the impact of cache misses.
2640 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2643 This enables the support for NetXen's Gigabit Ethernet card.
2646 tristate "Sun Neptune 10Gbit Ethernet support"
2649 This enables support for cards based upon Sun's
2653 tristate "PA Semi 1/10Gbit MAC"
2654 depends on PPC_PASEMI && PCI
2658 This driver supports the on-chip 1/10Gbit Ethernet controller on
2659 PA Semi's PWRficient line of chips.
2662 tristate "Mellanox Technologies 10Gbit Ethernet support"
2663 depends on PCI && INET
2667 This driver supports Mellanox Technologies ConnectX Ethernet
2676 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2677 depends on MLX4_CORE
2680 This option causes debugging code to be compiled into the
2681 mlx4_core driver. The output can be turned on via the
2682 debug_level module parameter (which can also be set after
2683 the driver is loaded through sysfs).
2686 tristate "Tehuti Networks 10G Ethernet"
2689 Tehuti Networks 10G Ethernet NIC
2692 tristate "Broadcom NetXtremeII 10Gb support"
2698 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2699 To compile this driver as a module, choose M here: the module
2700 will be called bnx2x. This is recommended.
2703 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2706 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2708 To compile this driver as a module, choose M here: the module
2709 will be called qlge.
2711 source "drivers/net/sfc/Kconfig"
2713 source "drivers/net/benet/Kconfig"
2715 endif # NETDEV_10000
2717 source "drivers/net/tokenring/Kconfig"
2719 source "drivers/net/wireless/Kconfig"
2721 source "drivers/net/wimax/Kconfig"
2723 source "drivers/net/usb/Kconfig"
2725 source "drivers/net/pcmcia/Kconfig"
2727 source "drivers/net/wan/Kconfig"
2729 source "drivers/atm/Kconfig"
2731 source "drivers/s390/net/Kconfig"
2733 config XEN_NETDEV_FRONTEND
2734 tristate "Xen network device frontend driver"
2738 The network device frontend driver allows the kernel to
2739 access network devices exported exported by a virtual
2740 machine containing a physical network device driver. The
2741 frontend driver is intended for unprivileged guest domains;
2742 if you are compiling a kernel for a Xen guest, you almost
2743 certainly want to enable this.
2746 tristate "iSeries Virtual Ethernet driver support"
2747 depends on PPC_ISERIES
2750 tristate "RapidIO Ethernet over messaging driver support"
2753 config RIONET_TX_SIZE
2754 int "Number of outbound queue entries"
2758 config RIONET_RX_SIZE
2759 int "Number of inbound queue entries"
2764 tristate "FDDI driver support"
2765 depends on (PCI || EISA || TC)
2767 Fiber Distributed Data Interface is a high speed local area network
2768 design; essentially a replacement for high speed Ethernet. FDDI can
2769 run over copper or fiber. If you are connected to such a network and
2770 want a driver for the FDDI card in your computer, say Y here (and
2771 then also Y to the driver for your FDDI card, below). Most people
2775 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2776 depends on FDDI && (PCI || EISA || TC)
2778 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2779 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2780 to a local FDDI network.
2782 To compile this driver as a module, choose M here: the module
2783 will be called defxx. If unsure, say N.
2787 prompt "Use MMIO instead of PIO" if PCI || EISA
2789 default n if PCI || EISA
2792 This instructs the driver to use EISA or PCI memory-mapped I/O
2793 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2794 Enabling this gives an improvement in processing time in parts
2795 of the driver, but it may cause problems with EISA (DEFEA)
2796 adapters. TURBOchannel does not have the concept of I/O ports,
2797 so MMIO is always used for these (DEFTA) adapters.
2802 tristate "SysKonnect FDDI PCI support"
2803 depends on FDDI && PCI
2806 Say Y here if you have a SysKonnect FDDI PCI adapter.
2807 The following adapters are supported by this driver:
2808 - SK-5521 (SK-NET FDDI-UP)
2809 - SK-5522 (SK-NET FDDI-UP DAS)
2810 - SK-5541 (SK-NET FDDI-FP)
2811 - SK-5543 (SK-NET FDDI-LP)
2812 - SK-5544 (SK-NET FDDI-LP DAS)
2813 - SK-5821 (SK-NET FDDI-UP64)
2814 - SK-5822 (SK-NET FDDI-UP64 DAS)
2815 - SK-5841 (SK-NET FDDI-FP64)
2816 - SK-5843 (SK-NET FDDI-LP64)
2817 - SK-5844 (SK-NET FDDI-LP64 DAS)
2818 - Netelligent 100 FDDI DAS Fibre SC
2819 - Netelligent 100 FDDI SAS Fibre SC
2820 - Netelligent 100 FDDI DAS UTP
2821 - Netelligent 100 FDDI SAS UTP
2822 - Netelligent 100 FDDI SAS Fibre MIC
2824 Read <file:Documentation/networking/skfp.txt> for information about
2827 Questions concerning this driver can be addressed to:
2828 <linux@syskonnect.de>
2830 To compile this driver as a module, choose M here: the module
2831 will be called skfp. This is recommended.
2834 bool "HIPPI driver support (EXPERIMENTAL)"
2835 depends on EXPERIMENTAL && INET && PCI
2837 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2838 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2839 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2840 single-mode). HIPPI networks are commonly used for clusters and to
2841 connect to super computers. If you are connected to a HIPPI network
2842 and have a HIPPI network card in your computer that you want to use
2843 under Linux, say Y here (you must also remember to enable the driver
2844 for your HIPPI card below). Most people will say N here.
2847 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2848 depends on HIPPI && PCI
2850 Say Y here if this is your PCI HIPPI network card.
2852 To compile this driver as a module, choose M here: the module
2853 will be called rrunner. If unsure, say N.
2855 config ROADRUNNER_LARGE_RINGS
2856 bool "Use large TX/RX rings (EXPERIMENTAL)"
2857 depends on ROADRUNNER
2859 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2860 of additional memory to allow for fastest operation, both for
2861 transmitting and receiving. This memory cannot be used by any other
2862 kernel code or by user space programs. Say Y here only if you have
2866 tristate "PLIP (parallel port) support"
2869 PLIP (Parallel Line Internet Protocol) is used to create a
2870 reasonably fast mini network consisting of two (or, rarely, more)
2871 local machines. A PLIP link from a Linux box is a popular means to
2872 install a Linux distribution on a machine which doesn't have a
2873 CD-ROM drive (a minimal system has to be transferred with floppies
2874 first). The kernels on both machines need to have this PLIP option
2875 enabled for this to work.
2877 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2878 ports (the connectors at the computers with 25 holes) are connected
2879 with "null printer" or "Turbo Laplink" cables which can transmit 4
2880 bits at a time (mode 0) or with special PLIP cables, to be used on
2881 bidirectional parallel ports only, which can transmit 8 bits at a
2882 time (mode 1); you can find the wiring of these cables in
2883 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2884 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2885 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2886 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2887 and winsock or NCSA's telnet.
2889 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2890 as the NET-3-HOWTO, both available from
2891 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2892 protocol has been changed and this PLIP driver won't work together
2893 with the PLIP support in Linux versions 1.0.x. This option enlarges
2894 your kernel by about 8 KB.
2896 To compile this driver as a module, choose M here. The module
2897 will be called plip. If unsure, say Y or M, in case you buy
2901 tristate "PPP (point-to-point protocol) support"
2904 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2905 the same purpose: sending Internet traffic over telephone (and other
2906 serial) lines. Ask your access provider if they support it, because
2907 otherwise you can't use it; most Internet access providers these
2908 days support PPP rather than SLIP.
2910 To use PPP, you need an additional program called pppd as described
2911 in the PPP-HOWTO, available at
2912 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2913 the version of pppd recommended in <file:Documentation/Changes>.
2914 The PPP option enlarges your kernel by about 16 KB.
2916 There are actually two versions of PPP: the traditional PPP for
2917 asynchronous lines, such as regular analog phone lines, and
2918 synchronous PPP which can be used over digital ISDN lines for
2919 example. If you want to use PPP over phone lines or other
2920 asynchronous serial lines, you need to say Y (or M) here and also to
2921 the next option, "PPP support for async serial ports". For PPP over
2922 synchronous lines, you should say Y (or M) here and to "Support
2923 synchronous PPP", below.
2925 If you said Y to "Version information on all symbols" above, then
2926 you cannot compile the PPP driver into the kernel; you can then only
2927 compile it as a module. To compile this driver as a module, choose M
2928 here. The module will be called ppp_generic.
2930 config PPP_MULTILINK
2931 bool "PPP multilink support (EXPERIMENTAL)"
2932 depends on PPP && EXPERIMENTAL
2934 PPP multilink is a protocol (defined in RFC 1990) which allows you
2935 to combine several (logical or physical) lines into one logical PPP
2936 connection, so that you can utilize your full bandwidth.
2938 This has to be supported at the other end as well and you need a
2939 version of the pppd daemon which understands the multilink protocol.
2944 bool "PPP filtering"
2947 Say Y here if you want to be able to filter the packets passing over
2948 PPP interfaces. This allows you to control which packets count as
2949 activity (i.e. which packets will reset the idle timer or bring up
2950 a demand-dialed link) and which packets are to be dropped entirely.
2951 You need to say Y here if you wish to use the pass-filter and
2952 active-filter options to pppd.
2957 tristate "PPP support for async serial ports"
2961 Say Y (or M) here if you want to be able to use PPP over standard
2962 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2963 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2966 To compile this driver as a module, choose M here.
2971 tristate "PPP support for sync tty ports"
2974 Say Y (or M) here if you want to be able to use PPP over synchronous
2975 (HDLC) tty devices, such as the SyncLink adapter. These devices
2976 are often used for high-speed leased lines like T1/E1.
2978 To compile this driver as a module, choose M here.
2981 tristate "PPP Deflate compression"
2986 Support for the Deflate compression method for PPP, which uses the
2987 Deflate algorithm (the same algorithm that gzip uses) to compress
2988 each PPP packet before it is sent over the wire. The machine at the
2989 other end of the PPP link (usually your ISP) has to support the
2990 Deflate compression method as well for this to be useful. Even if
2991 they don't support it, it is safe to say Y here.
2993 To compile this driver as a module, choose M here.
2996 tristate "PPP BSD-Compress compression"
2999 Support for the BSD-Compress compression method for PPP, which uses
3000 the LZW compression method to compress each PPP packet before it is
3001 sent over the wire. The machine at the other end of the PPP link
3002 (usually your ISP) has to support the BSD-Compress compression
3003 method as well for this to be useful. Even if they don't support it,
3004 it is safe to say Y here.
3006 The PPP Deflate compression method ("PPP Deflate compression",
3007 above) is preferable to BSD-Compress, because it compresses better
3010 Note that the BSD compression code will always be compiled as a
3011 module; it is called bsd_comp and will show up in the directory
3012 modules once you have said "make modules". If unsure, say N.
3015 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3016 depends on PPP && EXPERIMENTAL
3022 Support for the MPPE Encryption protocol, as employed by the
3023 Microsoft Point-to-Point Tunneling Protocol.
3025 See http://pptpclient.sourceforge.net/ for information on
3026 configuring PPTP clients and servers to utilize this method.
3029 tristate "PPP over Ethernet (EXPERIMENTAL)"
3030 depends on EXPERIMENTAL && PPP
3032 Support for PPP over Ethernet.
3034 This driver requires the latest version of pppd from the CVS
3035 repository at cvs.samba.org. Alternatively, see the
3036 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3037 which contains instruction on how to use this driver (under
3038 the heading "Kernel mode PPPoE").
3041 tristate "PPP over ATM"
3042 depends on ATM && PPP
3044 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3045 This implementation does not yet comply with section 8 of RFC2364,
3046 which can lead to bad results if the ATM peer loses state and
3047 changes its encapsulation unilaterally.
3050 tristate "PPP over L2TP (EXPERIMENTAL)"
3051 depends on EXPERIMENTAL && PPP && INET
3053 Support for PPP-over-L2TP socket family. L2TP is a protocol
3054 used by ISPs and enterprises to tunnel PPP traffic over UDP
3055 tunnels. L2TP is replacing PPTP for VPN uses.
3057 This kernel component handles only L2TP data packets: a
3058 userland daemon handles L2TP the control protocol (tunnel
3059 and session setup). One such daemon is OpenL2TP
3060 (http://openl2tp.sourceforge.net/).
3063 tristate "SLIP (serial line) support"
3065 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3066 connect to your Internet service provider or to connect to some
3067 other local Unix box or if you want to configure your Linux box as a
3068 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3069 Internet Protocol) is a protocol used to send Internet traffic over
3070 serial connections such as telephone lines or null modem cables;
3071 nowadays, the protocol PPP is more commonly used for this same
3074 Normally, your access provider has to support SLIP in order for you
3075 to be able to use it, but there is now a SLIP emulator called SLiRP
3076 around (available from
3077 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3078 allows you to use SLIP over a regular dial up shell connection. If
3079 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3080 NET-3-HOWTO, available from
3081 <http://www.tldp.org/docs.html#howto>, explains how to
3082 configure SLIP. Note that you don't need this option if you just
3083 want to run term (term is a program which gives you almost full
3084 Internet connectivity if you have a regular dial up shell account on
3085 some Internet connected Unix computer. Read
3086 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3087 support will enlarge your kernel by about 4 KB. If unsure, say N.
3089 To compile this driver as a module, choose M here. The module
3090 will be called slip.
3092 config SLIP_COMPRESSED
3093 bool "CSLIP compressed headers"
3097 This protocol is faster than SLIP because it uses compression on the
3098 TCP/IP headers (not on the data itself), but it has to be supported
3099 on both ends. Ask your access provider if you are not sure and
3100 answer Y, just in case. You will still be able to use plain SLIP. If
3101 you plan to use SLiRP, the SLIP emulator (available from
3102 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3103 allows you to use SLIP over a regular dial up shell connection, you
3104 definitely want to say Y here. The NET-3-HOWTO, available from
3105 <http://www.tldp.org/docs.html#howto>, explains how to configure
3106 CSLIP. This won't enlarge your kernel.
3111 This option enables Van Jacobsen serial line header compression
3115 bool "Keepalive and linefill"
3118 Adds additional capabilities to the SLIP driver to support the
3119 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3122 config SLIP_MODE_SLIP6
3123 bool "Six bit SLIP encapsulation"
3126 Just occasionally you may need to run IP over hostile serial
3127 networks that don't pass all control characters or are only seven
3128 bit. Saying Y here adds an extra mode you can use with SLIP:
3129 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3130 the serial device. Naturally, this has to be supported at the other
3131 end of the link as well. It's good enough, for example, to run IP
3132 over the async ports of a Camtec JNT Pad. If unsure, say N.
3135 bool "Fibre Channel driver support"
3136 depends on SCSI && PCI
3138 Fibre Channel is a high speed serial protocol mainly used to connect
3139 large storage devices to the computer; it is compatible with and
3140 intended to replace SCSI.
3142 If you intend to use Fibre Channel, you need to have a Fibre channel
3143 adaptor card in your computer; say Y here and to the driver for your
3144 adaptor below. You also should have said Y to "SCSI support" and
3145 "SCSI generic support".
3148 tristate "Network console logging support (EXPERIMENTAL)"
3149 depends on EXPERIMENTAL
3151 If you want to log kernel messages over the network, enable this.
3152 See <file:Documentation/networking/netconsole.txt> for details.
3154 config NETCONSOLE_DYNAMIC
3155 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3156 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3159 This option enables the ability to dynamically reconfigure target
3160 parameters (interface, IP addresses, port numbers, MAC addresses)
3161 at runtime through a userspace interface exported using configfs.
3162 See <file:Documentation/networking/netconsole.txt> for details.
3168 bool "Netpoll traffic trapping"
3172 config NET_POLL_CONTROLLER
3176 tristate "Virtio network driver (EXPERIMENTAL)"
3177 depends on EXPERIMENTAL && VIRTIO
3179 This is the virtual network driver for virtio. It can be used with
3180 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.