2 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 # All the following symbols are dependent on NETDEVICES - do not repeat
25 # that for each of the symbols.
29 tristate "Intermediate Functional Block support"
30 depends on NET_CLS_ACT
32 This is an intermediate driver that allows sharing of
34 To compile this driver as a module, choose M here: the module
35 will be called ifb. If you want to use more than one ifb
36 device at a time, you need to compile this driver as a module.
37 Instead of 'ifb', the devices will then be called 'ifb0',
39 Look at the iproute2 documentation directory for usage etc
42 tristate "Dummy net driver support"
44 This is essentially a bit-bucket device (i.e. traffic you send to
45 this device is consigned into oblivion) with a configurable IP
46 address. It is most commonly used in order to make your currently
47 inactive SLIP address seem like a real address for local programs.
48 If you use SLIP or PPP, you might want to say Y here. Since this
49 thing often comes in handy, the default is Y. It won't enlarge your
50 kernel either. What a deal. Read about it in the Network
51 Administrator's Guide, available from
52 <http://www.tldp.org/docs.html#guide>.
54 To compile this driver as a module, choose M here: the module
55 will be called dummy. If you want to use more than one dummy
56 device at a time, you need to compile this driver as a module.
57 Instead of 'dummy', the devices will then be called 'dummy0',
61 tristate "Bonding driver support"
63 depends on IPV6 || IPV6=n
65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
66 Channels together. This is called 'Etherchannel' by Cisco,
67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
69 The driver supports multiple bonding modes to allow for both high
70 performance and high availability operation.
72 Refer to <file:Documentation/networking/bonding.txt> for more
75 To compile this driver as a module, choose M here: the module
76 will be called bonding.
79 tristate "MAC-VLAN support (EXPERIMENTAL)"
80 depends on EXPERIMENTAL
82 This allows one to create virtual interfaces that map packets to
83 or from specific MAC addresses to a particular interface.
85 Macvlan devices can be added using the "ip" command from the
86 iproute2 package starting with the iproute2-2.6.23 release:
88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
90 To compile this driver as a module, choose M here: the module
91 will be called macvlan.
94 tristate "EQL (serial line load balancing) support"
96 If you have two serial connections to some other computer (this
97 usually requires two modems and two telephone lines) and you use
98 SLIP (the protocol for sending Internet traffic over telephone
99 lines) or PPP (a better SLIP) on them, you can make them behave like
100 one double speed connection using this driver. Naturally, this has
101 to be supported at the other end as well, either with a similar EQL
102 Linux driver or with a Livingston Portmaster 2e.
104 Say Y if you want this and read
105 <file:Documentation/networking/eql.txt>. You may also want to read
106 section 6.2 of the NET-3-HOWTO, available from
107 <http://www.tldp.org/docs.html#howto>.
109 To compile this driver as a module, choose M here: the module
110 will be called eql. If unsure, say N.
113 tristate "Universal TUN/TAP device driver support"
116 TUN/TAP provides packet reception and transmission for user space
117 programs. It can be viewed as a simple Point-to-Point or Ethernet
118 device, which instead of receiving packets from a physical media,
119 receives them from user space program and instead of sending packets
120 via physical media writes them to the user space program.
122 When a program opens /dev/net/tun, driver creates and registers
123 corresponding net device tunX or tapX. After a program closed above
124 devices, driver will automatically delete tunXX or tapXX device and
125 all routes corresponding to it.
127 Please read <file:Documentation/networking/tuntap.txt> for more
130 To compile this driver as a module, choose M here: the module
133 If you don't know what to use this for, you don't need it.
136 tristate "Virtual ethernet pair device"
138 This device is a local ethernet tunnel. Devices are created in pairs.
139 When one end receives the packet it appears on its pair and vice
143 tristate "General Instruments Surfboard 1000"
146 This is a driver for the General Instrument (also known as
147 NextLevel) SURFboard 1000 internal
148 cable modem. This is an ISA card which is used by a number of cable
149 TV companies to provide cable modem access. It's a one-way
150 downstream-only cable modem, meaning that your upstream net link is
151 provided by your regular phone modem.
153 At present this driver only compiles as a module, so say M here if
154 you have this card. The module will be called sb1000. Then read
155 <file:Documentation/networking/README.sb1000> for information on how
156 to use this module, as it needs special ppp scripts for establishing
157 a connection. Further documentation and the necessary scripts can be
160 <http://www.jacksonville.net/~fventuri/>
161 <http://home.adelphia.net/~siglercm/sb1000.html>
162 <http://linuxpower.cx/~cable/>
164 If you don't have this card, of course say N.
166 source "drivers/net/arcnet/Kconfig"
168 source "drivers/net/phy/Kconfig"
174 menuconfig NET_ETHERNET
175 bool "Ethernet (10 or 100Mbit)"
178 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
179 type of Local Area Network (LAN) in universities and companies.
181 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
182 coaxial cable, linking computers in a chain), 10BASE-T or twisted
183 pair (10 Mbps over twisted pair cable, linking computers to central
184 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
185 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
186 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
187 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
188 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
189 Ethernet (1 Gbps over optical fiber or short copper links).
191 If your Linux machine will be connected to an Ethernet and you have
192 an Ethernet network interface card (NIC) installed in your computer,
193 say Y here and read the Ethernet-HOWTO, available from
194 <http://www.tldp.org/docs.html#howto>. You will then also have
195 to say Y to the driver for your particular NIC.
197 Note that the answer to this question won't directly affect the
198 kernel: saying N will just cause the configurator to skip all
199 the questions about Ethernet network cards. If unsure, say N.
204 tristate "Generic Media Independent Interface device support"
206 Most ethernet controllers have MII transceiver either as an external
207 or internal device. It is safe to say Y or M here even if your
208 ethernet card lack MII.
211 tristate "Atmel MACB support"
212 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
215 The Atmel MACB ethernet interface is found on many AT32 and AT91
216 parts. Say Y to include support for the MACB chip.
218 To compile this driver as a module, choose M here: the module
221 source "drivers/net/arm/Kconfig"
224 tristate "ASIX AX88796 NE2000 clone support"
225 depends on ARM || MIPS || SUPERH
229 AX88796 driver, using platform bus to provide
230 chip detection and resources
233 bool "ASIX AX88796 external 93CX6 eeprom support"
237 Select this if your platform comes with an external 93CX6 eeprom.
240 tristate "MACE (Power Mac ethernet) support"
241 depends on PPC_PMAC && PPC32
244 Power Macintoshes and clones with Ethernet built-in on the
245 motherboard will usually use a MACE (Medium Access Control for
246 Ethernet) interface. Say Y to include support for the MACE chip.
248 To compile this driver as a module, choose M here: the module
251 config MACE_AAUI_PORT
252 bool "Use AAUI port instead of TP by default"
255 Some Apple machines (notably the Apple Network Server) which use the
256 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
257 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
258 Y here if you have such a machine. If unsure, say N.
259 The driver will default to AAUI on ANS anyway, and if you use it as
260 a module, you can provide the port_aaui=0|1 to force the driver.
263 tristate "BMAC (G3 ethernet) support"
264 depends on PPC_PMAC && PPC32
267 Say Y for support of BMAC Ethernet interfaces. These are used on G3
270 To compile this driver as a module, choose M here: the module
274 tristate "Ariadne support"
277 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
280 To compile this driver as a module, choose M here: the module
281 will be called ariadne.
284 tristate "A2065 support"
288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
291 To compile this driver as a module, choose M here: the module
292 will be called a2065.
295 tristate "Hydra support"
299 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
301 To compile this driver as a module, choose M here: the module
302 will be called hydra.
305 tristate "Zorro NS8390-based Ethernet support"
309 This driver is for Zorro Ethernet cards using an NS8390-compatible
310 chipset, like the Village Tronic Ariadne II and the Individual
311 Computers X-Surf Ethernet cards. If you have such a card, say Y.
314 To compile this driver as a module, choose M here: the module
315 will be called zorro8390.
318 tristate "PCMCIA NE2000 support"
319 depends on AMIGA_PCMCIA
322 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
325 To compile this driver as a module, choose M here: the module
329 bool "Macintosh NS 8390 based ethernet cards"
333 If you want to include a driver to support Nubus or LC-PDS
334 Ethernet cards using an NS8390 chipset or its equivalent, say Y
335 and read the Ethernet-HOWTO, available from
336 <http://www.tldp.org/docs.html#howto>.
339 tristate "Macintosh CS89x0 based ethernet cards"
342 Support for CS89x0 chipset based Ethernet cards. If you have a
343 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
344 read the Ethernet-HOWTO, available from
345 <http://www.tldp.org/docs.html#howto>.
347 To compile this driver as a module, choose M here. This module will
351 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
354 Support for NatSemi SONIC based Ethernet devices. This includes
355 the onboard Ethernet in many Quadras as well as some LC-PDS,
356 a few Nubus and all known Comm Slot Ethernet cards. If you have
357 one of these say Y and read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 To compile this driver as a module, choose M here. This module will
364 bool "Macintosh (AV) onboard MACE ethernet"
368 Support for the onboard AMD 79C940 MACE Ethernet controller used in
369 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
370 say Y and read the Ethernet-HOWTO, available from
371 <http://www.tldp.org/docs.html#howto>.
374 tristate "MVME147 (Lance) Ethernet support"
378 Support for the on-board Ethernet interface on the Motorola MVME147
379 single-board computer. Say Y here to include the
380 driver for this chip in your kernel.
381 To compile this driver as a module, choose M here.
384 tristate "MVME16x Ethernet support"
387 This is the driver for the Ethernet interface on the Motorola
388 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
389 driver for this chip in your kernel.
390 To compile this driver as a module, choose M here.
393 tristate "BVME6000 Ethernet support"
396 This is the driver for the Ethernet interface on BVME4000 and
397 BVME6000 VME boards. Say Y here to include the driver for this chip
399 To compile this driver as a module, choose M here.
402 tristate "Atari Lance support"
405 Say Y to include support for several Atari Ethernet adapters based
406 on the AMD Lance chipset: RieblCard (with or without battery), or
407 PAMCard VME (also the version by Rhotron, with different addresses).
410 tristate "Sun3/Sun3x on-board LANCE support"
411 depends on SUN3 || SUN3X
413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
415 here to compile in the Linux driver for this and enable Ethernet.
416 General Linux information on the Sun 3 and 3x series (now
418 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
420 If you're not building a kernel for a Sun 3, say N.
423 bool "Sun3 on-board Intel 82586 support"
426 This driver enables support for the on-board Intel 82586 based
427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
428 that this driver does not support 82586-based adapters on additional
432 bool "HP on-board LANCE support"
436 If you want to use the builtin "LANCE" Ethernet controller on an
437 HP300 machine, say Y here.
440 tristate "Lasi ethernet"
443 Say Y here to support the builtin Intel 82596 ethernet controller
444 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
447 tristate "SNI RM ethernet"
448 depends on NET_ETHERNET && SNI_RM
450 Say Y here to support the on-board Intel 82596 ethernet controller
451 built into SNI RM machines.
454 tristate "Korina (IDT RC32434) Ethernet support"
455 depends on NET_ETHERNET && MIKROTIK_RB532
457 If you have a Mikrotik RouterBoard 500 or IDT RC32434
458 based system say Y. Otherwise say N.
460 config MIPS_JAZZ_SONIC
461 tristate "MIPS JAZZ onboard SONIC Ethernet support"
464 This is the driver for the onboard card of MIPS Magnum 4000,
465 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
467 config XTENSA_XT2000_SONIC
468 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
469 depends on XTENSA_PLATFORM_XT2000
471 This is the driver for the onboard card of the Xtensa XT2000 board.
473 config MIPS_AU1X00_ENET
474 bool "MIPS AU1000 Ethernet support"
475 depends on SOC_AU1X00
479 If you have an Alchemy Semi AU1X00 based system
480 say Y. Otherwise, say N.
483 bool "SGI IOC3 Ethernet"
484 depends on PCI && SGI_IP27
488 If you have a network (Ethernet) card of this type, say Y and read
489 the Ethernet-HOWTO, available from
490 <http://www.tldp.org/docs.html#howto>.
493 tristate "MIPS simulator Network device"
496 The MIPSNET device is a simple Ethernet network device which is
497 emulated by the MIPS Simulator.
498 If you are not using a MIPSsim or are unsure, say N.
500 config SGI_O2MACE_ETH
501 tristate "SGI O2 MACE Fast Ethernet support"
502 depends on SGI_IP32=y
505 tristate "National DP83902AV support"
509 Support for cards based on the National Semiconductor DP83902AV
510 ST-NIC Serial Network Interface Controller for Twisted Pair. This
511 is a 10Mbit/sec Ethernet controller. Product overview and specs at
512 <http://www.national.com/pf/DP/DP83902A.html>.
517 tristate "Renesas SuperH Ethernet support"
518 depends on SUPERH && \
519 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
526 Renesas SuperH Ethernet device driver.
527 This driver support SH7710, SH7712, SH7763 and SH7619.
530 tristate "Sun LANCE support"
534 This driver supports the "le" interface present on all 32-bit Sparc
535 systems, on some older Ultra systems and as an Sbus option. These
536 cards are based on the AMD Lance chipset, which is better known
537 via the NE2100 cards.
539 To compile this driver as a module, choose M here: the module
540 will be called sunlance.
543 tristate "Sun Happy Meal 10/100baseT support"
544 depends on SBUS || PCI
547 This driver supports the "hme" interface present on most Ultra
548 systems and as an option on older Sbus systems. This driver supports
549 both PCI and Sbus devices. This driver also supports the "qfe" quad
550 100baseT device available in both PCI and Sbus configurations.
552 To compile this driver as a module, choose M here: the module
553 will be called sunhme.
556 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
557 depends on SBUS && EXPERIMENTAL
560 This driver supports the "be" interface available as an Sbus option.
561 This is Sun's older 100baseT Ethernet device.
563 To compile this driver as a module, choose M here: the module
564 will be called sunbmac.
567 tristate "Sun QuadEthernet support"
571 This driver supports the "qe" 10baseT Ethernet device, available as
572 an Sbus option. Note that this is not the same as Quad FastEthernet
573 "qfe" which is supported by the Happy Meal driver instead.
575 To compile this driver as a module, choose M here: the module
576 will be called sunqe.
579 tristate "Sun GEM support"
583 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
584 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
587 tristate "Sun Cassini support"
591 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
592 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
595 tristate "Sun Virtual Network support"
598 Support for virtual network devices under Sun Logical Domains.
600 config NET_VENDOR_3COM
602 depends on ISA || EISA || MCA || PCI
604 If you have a network (Ethernet) card belonging to this class, say Y
605 and read the Ethernet-HOWTO, available from
606 <http://www.tldp.org/docs.html#howto>.
608 Note that the answer to this question doesn't directly affect the
609 kernel: saying N will just cause the configurator to skip all
610 the questions about 3COM cards. If you say Y, you will be asked for
611 your specific card in the following questions.
614 tristate "3c501 \"EtherLink\" support"
615 depends on NET_VENDOR_3COM && ISA
617 If you have a network (Ethernet) card of this type, say Y and read
618 the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
620 new card, since the 3c501 is slow, broken, and obsolete: you will
621 have problems. Some people suggest to ping ("man ping") a nearby
622 machine every minute ("man cron") when using this card.
624 To compile this driver as a module, choose M here. The module
625 will be called 3c501.
628 tristate "3c503 \"EtherLink II\" support"
629 depends on NET_VENDOR_3COM && ISA
632 If you have a network (Ethernet) card of this type, say Y and read
633 the Ethernet-HOWTO, available from
634 <http://www.tldp.org/docs.html#howto>.
636 To compile this driver as a module, choose M here. The module
637 will be called 3c503.
640 tristate "3c505 \"EtherLink Plus\" support"
641 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
643 Information about this network (Ethernet) card can be found in
644 <file:Documentation/networking/3c505.txt>. If you have a card of
645 this type, say Y and read the Ethernet-HOWTO, available from
646 <http://www.tldp.org/docs.html#howto>.
648 To compile this driver as a module, choose M here. The module
649 will be called 3c505.
652 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
653 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
655 If you have a network (Ethernet) card of this type, say Y and read
656 the Ethernet-HOWTO, available from
657 <http://www.tldp.org/docs.html#howto>.
659 To compile this driver as a module, choose M here. The module
660 will be called 3c507.
663 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
664 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
666 If you have a network (Ethernet) card belonging to the 3Com
667 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
668 from <http://www.tldp.org/docs.html#howto>.
670 If your card is not working you may need to use the DOS
671 setup disk to disable Plug & Play mode, and to select the default
674 To compile this driver as a module, choose M here. The module
675 will be called 3c509.
678 tristate "3c515 ISA \"Fast EtherLink\""
679 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
681 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
682 network card, say Y and read the Ethernet-HOWTO, available from
683 <http://www.tldp.org/docs.html#howto>.
685 To compile this driver as a module, choose M here. The module
686 will be called 3c515.
689 tristate "3c523 \"EtherLink/MC\" support"
690 depends on NET_VENDOR_3COM && MCA_LEGACY
692 If you have a network (Ethernet) card of this type, say Y and read
693 the Ethernet-HOWTO, available from
694 <http://www.tldp.org/docs.html#howto>.
696 To compile this driver as a module, choose M here. The module
697 will be called 3c523.
700 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
701 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
703 If you have a network (Ethernet) card of this type, say Y and read
704 the Ethernet-HOWTO, available from
705 <http://www.tldp.org/docs.html#howto>.
707 To compile this driver as a module, choose M here. The module
708 will be called 3c527.
711 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
712 depends on NET_VENDOR_3COM && (PCI || EISA)
715 This option enables driver support for a large number of 10Mbps and
716 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
718 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
719 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
720 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
721 "Tornado" (3c905) PCI
722 "Hurricane" (3c555/3cSOHO) PCI
724 If you have such a card, say Y and read the Ethernet-HOWTO,
725 available from <http://www.tldp.org/docs.html#howto>. More
726 specific information is in
727 <file:Documentation/networking/vortex.txt> and in the comments at
728 the beginning of <file:drivers/net/3c59x.c>.
730 To compile this support as a module, choose M here.
733 tristate "3cr990 series \"Typhoon\" support"
734 depends on NET_VENDOR_3COM && PCI
737 This option enables driver support for the 3cr990 series of cards:
739 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
740 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
741 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
743 If you have a network (Ethernet) card of this type, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>.
747 To compile this driver as a module, choose M here. The module
748 will be called typhoon.
751 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
752 depends on ISA && ISA_DMA_API
754 If you have a network (Ethernet) card of this type, say Y and read
755 the Ethernet-HOWTO, available from
756 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
759 To compile this driver as a module, choose M here: the module
760 will be called lance. This is recommended.
762 config NET_VENDOR_SMC
763 bool "Western Digital/SMC cards"
764 depends on ISA || MCA || EISA || MAC
766 If you have a network (Ethernet) card belonging to this class, say Y
767 and read the Ethernet-HOWTO, available from
768 <http://www.tldp.org/docs.html#howto>.
770 Note that the answer to this question doesn't directly affect the
771 kernel: saying N will just cause the configurator to skip all
772 the questions about Western Digital cards. If you say Y, you will be
773 asked for your specific card in the following questions.
776 tristate "WD80*3 support"
777 depends on NET_VENDOR_SMC && ISA
780 If you have a network (Ethernet) card of this type, say Y and read
781 the Ethernet-HOWTO, available from
782 <http://www.tldp.org/docs.html#howto>.
784 To compile this driver as a module, choose M here. The module
788 tristate "SMC Ultra MCA support"
789 depends on NET_VENDOR_SMC && MCA
792 If you have a network (Ethernet) card of this type and are running
793 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
794 available from <http://www.tldp.org/docs.html#howto>.
796 To compile this driver as a module, choose M here. The module
797 will be called smc-mca.
800 tristate "SMC Ultra support"
801 depends on NET_VENDOR_SMC && ISA
804 If you have a network (Ethernet) card of this type, say Y and read
805 the Ethernet-HOWTO, available from
806 <http://www.tldp.org/docs.html#howto>.
808 Important: There have been many reports that, with some motherboards
809 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
810 such as some BusLogic models) causes corruption problems with many
811 operating systems. The Linux smc-ultra driver has a work-around for
812 this but keep it in mind if you have such a SCSI card and have
815 To compile this driver as a module, choose M here. The module
816 will be called smc-ultra.
819 tristate "SMC Ultra32 EISA support"
820 depends on NET_VENDOR_SMC && EISA
823 If you have a network (Ethernet) card of this type, say Y and read
824 the Ethernet-HOWTO, available from
825 <http://www.tldp.org/docs.html#howto>.
827 To compile this driver as a module, choose M here. The module
828 will be called smc-ultra32.
831 tristate "Blackfin on-chip MAC support"
832 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
836 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
838 This is the driver for Blackfin on-chip mac device. Say Y if you want it
839 compiled into the kernel. This driver is also available as a module
840 ( = code which can be inserted in and removed from the running kernel
841 whenever you want). The module will be called bfin_mac.
843 config BFIN_MAC_USE_L1
844 bool "Use L1 memory for rx/tx packets"
845 depends on BFIN_MAC && (BF527 || BF537)
848 To get maximum network performance, you should use L1 memory as rx/tx buffers.
849 Say N here if you want to reserve L1 memory for other uses.
851 config BFIN_TX_DESC_NUM
852 int "Number of transmit buffer packets"
854 range 6 10 if BFIN_MAC_USE_L1
858 Set the number of buffer packets used in driver.
860 config BFIN_RX_DESC_NUM
861 int "Number of receive buffer packets"
863 range 20 100 if BFIN_MAC_USE_L1
867 Set the number of buffer packets used in driver.
870 bool "RMII PHY Interface (EXPERIMENTAL)"
871 depends on BFIN_MAC && EXPERIMENTAL
872 default y if BFIN527_EZKIT
873 default n if BFIN537_STAMP
875 Use Reduced PHY MII Interface
878 tristate "SMC 9194 support"
879 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
882 This is support for the SMC9xxx based Ethernet cards. Choose this
883 option if you have a DELL laptop with the docking station, or
884 another SMC9192/9194 based chipset. Say Y if you want it compiled
885 into the kernel, and read the file
886 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
887 available from <http://www.tldp.org/docs.html#howto>.
889 To compile this driver as a module, choose M here. The module
890 will be called smc9194.
893 tristate "SMC 91C9x/91C1xxx support"
896 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
897 MIPS || BLACKFIN || MN10300
899 This is a driver for SMC's 91x series of Ethernet chipsets,
900 including the SMC91C94 and the SMC91C111. Say Y if you want it
901 compiled into the kernel, and read the file
902 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
903 available from <http://www.linuxdoc.org/docs.html#howto>.
905 This driver is also available as a module ( = code which can be
906 inserted in and removed from the running kernel whenever you want).
907 The module will be called smc91x. If you want to compile it as a
908 module, say M here and read <file:Documentation/kbuild/modules.txt>.
911 tristate "NetX Ethernet support"
915 This is support for the Hilscher netX builtin Ethernet ports
917 To compile this driver as a module, choose M here. The module
918 will be called netx-eth.
920 config TI_DAVINCI_EMAC
921 tristate "TI DaVinci EMAC Support"
922 depends on ARM && ARCH_DAVINCI
925 This driver supports TI's DaVinci Ethernet .
927 To compile this driver as a module, choose M here: the module
928 will be called davinci_emac_driver. This is recommended.
931 tristate "DM9000 support"
932 depends on ARM || BLACKFIN || MIPS
936 Support for DM9000 chipset.
938 To compile this driver as a module, choose M here. The module
939 will be called dm9000.
941 config DM9000_DEBUGLEVEL
942 int "DM9000 maximum debug level"
946 The maximum level of debugging code compiled into the DM9000
949 config DM9000_FORCE_SIMPLE_PHY_POLL
950 bool "Force simple NSR based PHY polling"
953 This configuration forces the DM9000 to use the NSR's LinkStatus
954 bit to determine if the link is up or down instead of the more
955 costly MII PHY reads. Note, this will not work if the chip is
956 operating with an external PHY.
959 tristate "ENC28J60 support"
960 depends on EXPERIMENTAL && SPI && NET_ETHERNET
963 Support for the Microchip EN28J60 ethernet chip.
965 To compile this driver as a module, choose M here. The module will be
968 config ENC28J60_WRITEVERIFY
969 bool "Enable write verify"
972 Enable the verify after the buffer write useful for debugging purpose.
976 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
977 depends on NET_ETHERNET && HAS_IOMEM
983 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
986 tristate "SMSC LAN911[5678] support"
989 depends on ARM || SUPERH
991 This is a driver for SMSC's LAN911x series of Ethernet chipsets
992 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
993 Say Y if you want it compiled into the kernel,
994 and read the Ethernet-HOWTO, available from
995 <http://www.linuxdoc.org/docs.html#howto>.
997 This driver is also available as a module. The module will be
998 called smc911x. If you want to compile it as a module, say M
999 here and read <file:Documentation/kbuild/modules.txt>
1002 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1003 depends on ARM || SUPERH
1008 Say Y here if you want support for SMSC LAN911x and LAN921x families
1009 of ethernet controllers.
1011 To compile this driver as a module, choose M here and read
1012 <file:Documentation/networking/net-modules.txt>. The module
1013 will be called smsc911x.
1015 config NET_VENDOR_RACAL
1016 bool "Racal-Interlan (Micom) NI cards"
1019 If you have a network (Ethernet) card belonging to this class, such
1020 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1021 available from <http://www.tldp.org/docs.html#howto>.
1023 Note that the answer to this question doesn't directly affect the
1024 kernel: saying N will just cause the configurator to skip all
1025 the questions about NI cards. If you say Y, you will be asked for
1026 your specific card in the following questions.
1029 tristate "NI5010 support (EXPERIMENTAL)"
1030 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1032 If you have a network (Ethernet) card of this type, say Y and read
1033 the Ethernet-HOWTO, available from
1034 <http://www.tldp.org/docs.html#howto>. Note that this is still
1037 To compile this driver as a module, choose M here. The module
1038 will be called ni5010.
1041 tristate "NI5210 support"
1042 depends on NET_VENDOR_RACAL && ISA
1044 If you have a network (Ethernet) card of this type, say Y and read
1045 the Ethernet-HOWTO, available from
1046 <http://www.tldp.org/docs.html#howto>.
1048 To compile this driver as a module, choose M here. The module
1049 will be called ni52.
1052 tristate "NI6510 support"
1053 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1055 If you have a network (Ethernet) card of this type, say Y and read
1056 the Ethernet-HOWTO, available from
1057 <http://www.tldp.org/docs.html#howto>.
1059 To compile this driver as a module, choose M here. The module
1060 will be called ni65.
1063 tristate "Dave ethernet support (DNET)"
1064 depends on NET_ETHERNET && HAS_IOMEM
1067 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1068 Say Y to include support for the DNET chip.
1070 To compile this driver as a module, choose M here: the module
1071 will be called dnet.
1073 source "drivers/net/tulip/Kconfig"
1076 tristate "AT1700/1720 support (EXPERIMENTAL)"
1077 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1080 If you have a network (Ethernet) card of this type, say Y and read
1081 the Ethernet-HOWTO, available from
1082 <http://www.tldp.org/docs.html#howto>.
1084 To compile this driver as a module, choose M here. The module
1085 will be called at1700.
1088 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1089 depends on ISA || EISA || MCA
1092 If you have a network (Ethernet) card of this type, say Y and read
1093 the Ethernet-HOWTO, available from
1094 <http://www.tldp.org/docs.html#howto> as well as
1095 <file:drivers/net/depca.c>.
1097 To compile this driver as a module, choose M here. The module
1098 will be called depca.
1101 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1102 depends on ISA || EISA || PCI
1104 If you have a network (Ethernet) card of this type, say Y and read
1105 the Ethernet-HOWTO, available from
1106 <http://www.tldp.org/docs.html#howto>.
1108 To compile this driver as a module, choose M here. The module
1109 will be called hp100.
1112 bool "Other ISA cards"
1115 If your network (Ethernet) card hasn't been mentioned yet and its
1116 bus system (that's the way the cards talks to the other components
1117 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1118 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1119 available from <http://www.tldp.org/docs.html#howto>.
1123 Note that the answer to this question doesn't directly affect the
1124 kernel: saying N will just cause the configurator to skip all
1125 the remaining ISA network card questions. If you say Y, you will be
1126 asked for your specific card in the following questions.
1129 tristate "Cabletron E21xx support"
1133 If you have a network (Ethernet) card of this type, say Y and read
1134 the Ethernet-HOWTO, available from
1135 <http://www.tldp.org/docs.html#howto>.
1137 To compile this driver as a module, choose M here. The module
1138 will be called e2100.
1141 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1145 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1146 cards. If this is for you, say Y and read
1147 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1148 well as the Ethernet-HOWTO, available from
1149 <http://www.tldp.org/docs.html#howto>.
1151 To compile this driver as a module, choose M here. The module
1152 will be called ewrk3.
1155 tristate "EtherExpress 16 support"
1158 If you have an EtherExpress16 network (Ethernet) card, say Y and
1159 read the Ethernet-HOWTO, available from
1160 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1161 EtherExpress16 card used to be regarded as a very poor choice
1162 because the driver was very unreliable. We now have a new driver
1163 that should do better.
1165 To compile this driver as a module, choose M here. The module
1166 will be called eexpress.
1169 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1172 If you have a network (Ethernet) card of this type, say Y. This
1173 driver supports Intel i82595{FX,TX} based boards. Note however
1174 that the EtherExpress PRO/100 Ethernet card has its own separate
1175 driver. Please read the Ethernet-HOWTO, available from
1176 <http://www.tldp.org/docs.html#howto>.
1178 To compile this driver as a module, choose M here. The module
1179 will be called eepro.
1182 tristate "HP PCLAN+ (27247B and 27252A) support"
1186 If you have a network (Ethernet) card of this type, say Y and read
1187 the Ethernet-HOWTO, available from
1188 <http://www.tldp.org/docs.html#howto>.
1190 To compile this driver as a module, choose M here. The module
1191 will be called hp-plus.
1194 tristate "HP PCLAN (27245 and other 27xxx series) support"
1198 If you have a network (Ethernet) card of this type, say Y and read
1199 the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here. The module
1206 tristate "LP486E on board Ethernet"
1209 Say Y here to support the 82596-based on-board Ethernet controller
1210 for the Panther motherboard, which is one of the two shipped in the
1211 Intel Professional Workstation.
1214 tristate "ICL EtherTeam 16i/32 support"
1217 If you have a network (Ethernet) card of this type, say Y and read
1218 the Ethernet-HOWTO, available from
1219 <http://www.tldp.org/docs.html#howto>.
1221 To compile this driver as a module, choose M here. The module
1222 will be called eth16i.
1225 tristate "NE2000/NE1000 support"
1226 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1229 If you have a network (Ethernet) card of this type, say Y and read
1230 the Ethernet-HOWTO, available from
1231 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1232 without a specific driver are compatible with NE2000.
1234 If you have a PCI NE2000 card however, say N here and Y to "PCI
1235 NE2000 and clone support" under "EISA, VLB, PCI and on board
1236 controllers" below. If you have a NE2000 card and are running on
1237 an MCA system (a bus system used on some IBM PS/2 computers and
1238 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1241 To compile this driver as a module, choose M here. The module
1245 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1246 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1248 The Zenith Z-Note notebook computer has a built-in network
1249 (Ethernet) card, and this is the Linux driver for it. Note that the
1250 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1251 by this driver. Read the Ethernet-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>.
1255 tristate "SEEQ8005 support (EXPERIMENTAL)"
1256 depends on NET_ISA && EXPERIMENTAL
1258 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1259 is for you, read the Ethernet-HOWTO, available from
1260 <http://www.tldp.org/docs.html#howto>.
1262 To compile this driver as a module, choose M here. The module
1263 will be called seeq8005.
1266 tristate "NE/2 (ne2000 MCA version) support"
1267 depends on MCA_LEGACY
1270 If you have a network (Ethernet) card of this type, say Y and read
1271 the Ethernet-HOWTO, available from
1272 <http://www.tldp.org/docs.html#howto>.
1274 To compile this driver as a module, choose M here. The module
1278 tristate "IBM LAN Adapter/A support"
1281 This is a Micro Channel Ethernet adapter. You need to set
1282 CONFIG_MCA to use this driver. It is both available as an in-kernel
1283 driver and as a module.
1285 To compile this driver as a module, choose M here. The only
1286 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1287 will both support 16K and 32K memory windows, however a 32K window
1288 gives a better security against packet losses. Usage of multiple
1289 boards with this driver should be possible, but has not been tested
1290 up to now due to lack of hardware.
1293 tristate "IBM LAN Virtual Ethernet support"
1294 depends on PPC_PSERIES
1296 This driver supports virtual ethernet adapters on newer IBM iSeries
1297 and pSeries systems.
1299 To compile this driver as a module, choose M here. The module will
1302 source "drivers/net/ibm_newemac/Kconfig"
1305 bool "EISA, VLB, PCI and on board controllers"
1306 depends on ISA || EISA || PCI
1308 This is another class of network cards which attach directly to the
1309 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1310 available from <http://www.tldp.org/docs.html#howto>.
1312 Note that the answer to this question doesn't directly affect the
1313 kernel: saying N will just cause the configurator to skip all
1314 the questions about this class of network cards. If you say Y, you
1315 will be asked for your specific card in the following questions. If
1316 you are unsure, say Y.
1319 tristate "AMD PCnet32 PCI support"
1320 depends on NET_PCI && PCI
1324 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1325 answer Y here and read the Ethernet-HOWTO, available from
1326 <http://www.tldp.org/docs.html#howto>.
1328 To compile this driver as a module, choose M here. The module
1329 will be called pcnet32.
1332 tristate "AMD 8111 (new PCI lance) support"
1333 depends on NET_PCI && PCI
1337 If you have an AMD 8111-based PCI lance ethernet card,
1338 answer Y here and read the Ethernet-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here. The module
1342 will be called amd8111e.
1344 config ADAPTEC_STARFIRE
1345 tristate "Adaptec Starfire/DuraLAN support"
1346 depends on NET_PCI && PCI
1350 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1351 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1352 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1355 To compile this driver as a module, choose M here: the module
1356 will be called starfire. This is recommended.
1359 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1360 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1363 If you have a network (Ethernet) card of this type, say Y and read
1364 the Ethernet-HOWTO, available from
1365 <http://www.tldp.org/docs.html#howto>.
1367 To compile this driver as a module, choose M here. The module
1368 will be called ac3200.
1371 tristate "Apricot Xen-II on board Ethernet"
1372 depends on NET_PCI && ISA
1374 If you have a network (Ethernet) controller of this type, say Y and
1375 read the Ethernet-HOWTO, available from
1376 <http://www.tldp.org/docs.html#howto>.
1378 To compile this driver as a module, choose M here. The module
1379 will be called apricot.
1382 tristate "Broadcom 440x/47xx ethernet support"
1383 depends on SSB_POSSIBLE && HAS_DMA
1387 If you have a network (Ethernet) controller of this type, say Y
1388 or M and read the Ethernet-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>.
1391 To compile this driver as a module, choose M here. The module
1394 # Auto-select SSB PCI-HOST support, if possible
1395 config B44_PCI_AUTOSELECT
1397 depends on B44 && SSB_PCIHOST_POSSIBLE
1401 # Auto-select SSB PCICORE driver, if possible
1402 config B44_PCICORE_AUTOSELECT
1404 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1405 select SSB_DRIVER_PCICORE
1410 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1414 tristate "nForce Ethernet support"
1415 depends on NET_PCI && PCI
1417 If you have a network (Ethernet) controller of this type, say Y and
1418 read the Ethernet-HOWTO, available from
1419 <http://www.tldp.org/docs.html#howto>.
1421 To compile this driver as a module, choose M here. The module
1422 will be called forcedeth.
1424 config FORCEDETH_NAPI
1425 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1426 depends on FORCEDETH && EXPERIMENTAL
1428 NAPI is a new driver API designed to reduce CPU and interrupt load
1429 when the driver is receiving lots of packets from the card. It is
1430 still somewhat experimental and thus not yet enabled by default.
1432 If your estimated Rx load is 10kpps or more, or if the card will be
1433 deployed on potentially unfriendly networks (e.g. in a firewall),
1439 tristate "CS89x0 support"
1440 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1441 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1443 Support for CS89x0 chipset based Ethernet cards. If you have a
1444 network (Ethernet) card of this type, say Y and read the
1445 Ethernet-HOWTO, available from
1446 <http://www.tldp.org/docs.html#howto> as well as
1447 <file:Documentation/networking/cs89x0.txt>.
1449 To compile this driver as a module, choose M here. The module
1450 will be called cs89x0.
1452 config CS89x0_NONISA_IRQ
1454 depends on CS89x0 != n
1455 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1458 tristate "TOSHIBA TC35815 Ethernet support"
1459 depends on NET_PCI && PCI && MIPS
1463 tristate "Intel(R) PRO/100+ support"
1464 depends on NET_PCI && PCI
1467 This driver supports Intel(R) PRO/100 family of adapters.
1468 To verify that your adapter is supported, find the board ID number
1469 on the adapter. Look for a label that has a barcode and a number
1470 in the format 123456-001 (six digits hyphen three digits).
1472 Use the above information and the Adapter & Driver ID Guide at:
1474 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1476 to identify the adapter.
1478 For the latest Intel PRO/100 network driver for Linux, see:
1480 <http://appsr.intel.com/scripts-df/support_intel.asp>
1482 More specific information on configuring the driver is in
1483 <file:Documentation/networking/e100.txt>.
1485 To compile this driver as a module, choose M here. The module
1486 will be called e100.
1489 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1490 depends on NET_PCI && EISA && EXPERIMENTAL
1493 If you have a network (Ethernet) card of this type, say Y and read
1494 the Ethernet-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>.
1497 To compile this driver as a module, choose M here. The module
1498 will be called lne390.
1501 tristate "Myson MTD-8xx PCI Ethernet support"
1502 depends on NET_PCI && PCI
1506 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1507 cards. Specifications and data at
1508 <http://www.myson.com.hk/mtd/datasheet/>.
1511 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1512 depends on NET_PCI && PCI
1515 This driver is for the National Semiconductor DP83810 series,
1516 which is used in cards from PureData, NetGear, Linksys
1517 and others, including the 83815 chip.
1518 More specific information and updates are available from
1519 <http://www.scyld.com/network/natsemi.html>.
1522 tristate "PCI NE2000 and clones support (see help)"
1523 depends on NET_PCI && PCI
1526 This driver is for NE2000 compatible PCI cards. It will not work
1527 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1528 support" below). If you have a PCI NE2000 network (Ethernet) card,
1529 say Y and read the Ethernet-HOWTO, available from
1530 <http://www.tldp.org/docs.html#howto>.
1532 This driver also works for the following NE2000 clone cards:
1533 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1534 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1535 Holtek HT80232 Holtek HT80229
1537 To compile this driver as a module, choose M here. The module
1538 will be called ne2k-pci.
1541 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1542 depends on NET_PCI && EISA && EXPERIMENTAL
1545 If you have a network (Ethernet) card of this type, say Y and read
1546 the Ethernet-HOWTO, available from
1547 <http://www.tldp.org/docs.html#howto>. Note that this driver
1548 will NOT WORK for NE3200 cards as they are completely different.
1550 To compile this driver as a module, choose M here. The module
1551 will be called ne3210.
1554 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1555 depends on NET_PCI && EISA && EXPERIMENTAL
1558 If you have a network (Ethernet) card of this type, say Y and read
1559 the Ethernet-HOWTO, available from
1560 <http://www.tldp.org/docs.html#howto>.
1562 To compile this driver as a module, choose M here. The module
1563 will be called es3210.
1566 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1567 depends on NET_PCI && PCI && EXPERIMENTAL
1571 This is a driver for the Fast Ethernet PCI network cards based on
1572 the RTL8139C+ chips. If you have one of those, say Y and read
1573 the Ethernet-HOWTO, available from
1574 <http://www.tldp.org/docs.html#howto>.
1576 To compile this driver as a module, choose M here: the module
1577 will be called 8139cp. This is recommended.
1580 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1581 depends on NET_PCI && PCI
1585 This is a driver for the Fast Ethernet PCI network cards based on
1586 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1587 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1589 To compile this driver as a module, choose M here: the module
1590 will be called 8139too. This is recommended.
1593 bool "Use PIO instead of MMIO"
1597 This instructs the driver to use programmed I/O ports (PIO) instead
1598 of PCI shared memory (MMIO). This can possibly solve some problems
1599 in case your mainboard has memory consistency issues. If unsure,
1602 config 8139TOO_TUNE_TWISTER
1603 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1606 This implements a function which might come in handy in case you
1607 are using low quality on long cabling. It is required for RealTek
1608 RTL-8139 revision K boards, and totally unused otherwise. It tries
1609 to match the transceiver to the cable characteristics. This is
1610 experimental since hardly documented by the manufacturer.
1614 bool "Support for older RTL-8129/8130 boards"
1617 This enables support for the older and uncommon RTL-8129 and
1618 RTL-8130 chips, which support MII via an external transceiver,
1619 instead of an internal one. Disabling this option will save some
1620 memory by making the code size smaller. If unsure, say Y.
1622 config 8139_OLD_RX_RESET
1623 bool "Use older RX-reset method"
1626 The 8139too driver was recently updated to contain a more rapid
1627 reset sequence, in the face of severe receive errors. This "new"
1628 RX-reset method should be adequate for all boards. But if you
1629 experience problems, you can enable this option to restore the
1630 old RX-reset behavior. If unsure, say N.
1633 tristate "RDC R6040 Fast Ethernet Adapter support"
1634 depends on NET_PCI && PCI
1638 This is a driver for the R6040 Fast Ethernet MACs found in the
1639 the RDC R-321x System-on-chips.
1641 To compile this driver as a module, choose M here: the module
1642 will be called r6040. This is recommended.
1645 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1646 depends on NET_PCI && PCI
1650 This is a driver for the Fast Ethernet PCI network cards based on
1651 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1652 SiS 630 and SiS 540 chipsets.
1654 This driver also supports AMD 79C901 HomePNA so that you can use
1655 your phone line as a network cable.
1657 To compile this driver as a module, choose M here: the module
1658 will be called sis900. This is recommended.
1661 tristate "SMC EtherPower II"
1662 depends on NET_PCI && PCI
1666 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1667 which is based on the SMC83c17x (EPIC/100).
1668 More specific information and updates are available from
1669 <http://www.scyld.com/network/epic100.html>.
1672 tristate "SMSC LAN9420 PCI ethernet adapter support"
1673 depends on NET_PCI && PCI
1678 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1679 Say Y if you want it compiled into the kernel,
1680 and read the Ethernet-HOWTO, available from
1681 <http://www.linuxdoc.org/docs.html#howto>.
1683 This driver is also available as a module. The module will be
1684 called smsc9420. If you want to compile it as a module, say M
1685 here and read <file:Documentation/kbuild/modules.txt>
1688 tristate "Sundance Alta support"
1689 depends on NET_PCI && PCI
1693 This driver is for the Sundance "Alta" chip.
1694 More specific information and updates are available from
1695 <http://www.scyld.com/network/sundance.html>.
1697 config SUNDANCE_MMIO
1698 bool "Use MMIO instead of PIO"
1701 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1702 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1703 is known to solve bugs on certain chips.
1708 tristate "TI ThunderLAN support"
1709 depends on NET_PCI && (PCI || EISA)
1711 If you have a PCI Ethernet network card based on the ThunderLAN chip
1712 which is supported by this driver, say Y and read the
1713 Ethernet-HOWTO, available from
1714 <http://www.tldp.org/docs.html#howto>.
1716 Devices currently supported by this driver are Compaq Netelligent,
1717 Compaq NetFlex and Olicom cards. Please read the file
1718 <file:Documentation/networking/tlan.txt> for more details.
1720 To compile this driver as a module, choose M here. The module
1721 will be called tlan.
1723 Please email feedback to <torben.mathiasen@compaq.com>.
1726 tristate "VIA Rhine support"
1727 depends on NET_PCI && PCI
1731 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1732 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1733 Ethernet functions can also be found integrated on South Bridges
1736 To compile this driver as a module, choose M here. The module
1737 will be called via-rhine.
1739 config VIA_RHINE_MMIO
1740 bool "Use MMIO instead of PIO"
1741 depends on VIA_RHINE
1743 This instructs the driver to use PCI shared memory (MMIO) instead of
1744 programmed I/O ports (PIO). Enabling this gives an improvement in
1745 processing time in parts of the driver.
1750 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1751 depends on NET_PCI && PCI && EXPERIMENTAL
1754 This is a driver for the Fast Ethernet PCI network cards based on
1755 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1756 have one of these, say Y here.
1758 To compile this driver as a module, choose M here: the module
1759 will be called sc92031. This is recommended.
1762 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1763 depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1766 TI AR7 CPMAC Ethernet support
1769 bool "Pocket and portable adapters"
1772 Cute little network (Ethernet) devices which attach to the parallel
1773 port ("pocket adapters"), commonly used with laptops. If you have
1774 one of those, say Y and read the Ethernet-HOWTO, available from
1775 <http://www.tldp.org/docs.html#howto>.
1777 If you want to plug a network (or some other) card into the PCMCIA
1778 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1779 credit card size extension cards used by all modern laptops), you
1780 need the pcmcia-cs package (location contained in the file
1781 <file:Documentation/Changes>) and you can say N here.
1783 Laptop users should read the Linux Laptop home page at
1784 <http://www.linux-on-laptops.com/> or
1785 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1787 Note that the answer to this question doesn't directly affect the
1788 kernel: saying N will just cause the configurator to skip all
1789 the questions about this class of network devices. If you say Y, you
1790 will be asked for your specific device in the following questions.
1793 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1794 depends on NET_POCKET && PARPORT && X86
1797 This is a network (Ethernet) device which attaches to your parallel
1798 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1799 available from <http://www.tldp.org/docs.html#howto>, if you
1800 want to use this. If you intend to use this driver, you should have
1801 said N to the "Parallel printer support", because the two drivers
1802 don't like each other.
1804 To compile this driver as a module, choose M here: the module
1808 tristate "D-Link DE600 pocket adapter support"
1809 depends on NET_POCKET && PARPORT
1811 This is a network (Ethernet) device which attaches to your parallel
1812 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1813 Ethernet-HOWTO, available from
1814 <http://www.tldp.org/docs.html#howto>, if you want to use
1815 this. It is possible to have several devices share a single parallel
1816 port and it is safe to compile the corresponding drivers into the
1819 To compile this driver as a module, choose M here: the module
1820 will be called de600.
1823 tristate "D-Link DE620 pocket adapter support"
1824 depends on NET_POCKET && PARPORT
1826 This is a network (Ethernet) device which attaches to your parallel
1827 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1828 Ethernet-HOWTO, available from
1829 <http://www.tldp.org/docs.html#howto>, if you want to use
1830 this. It is possible to have several devices share a single parallel
1831 port and it is safe to compile the corresponding drivers into the
1834 To compile this driver as a module, choose M here: the module
1835 will be called de620.
1838 tristate "SGI Seeq ethernet controller support"
1839 depends on SGI_HAS_SEEQ
1841 Say Y here if you have an Seeq based Ethernet network card. This is
1842 used in many Silicon Graphics machines.
1845 tristate "DEC LANCE ethernet controller support"
1846 depends on MACH_DECSTATION
1849 This driver is for the series of Ethernet controllers produced by
1850 DEC (now Compaq) based on the AMD Lance chipset, including the
1851 DEPCA series. (This chipset is better known via the NE2100 cards.)
1854 bool "Motorola 68360 ethernet controller"
1857 Say Y here if you want to use the built-in ethernet controller of
1858 the Motorola 68360 processor.
1861 bool "FEC ethernet controller (of ColdFire CPUs)"
1862 depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27
1864 Say Y here if you want to use the built-in 10/100 Fast ethernet
1865 controller on some Motorola ColdFire and Freescale i.MX processors.
1868 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1871 Say Y here if you want to use the second built-in 10/100 Fast
1872 ethernet controller on some Motorola ColdFire processors.
1875 tristate "MPC52xx FEC driver"
1876 depends on PPC_MPC52xx && PPC_BESTCOMM
1879 select PPC_BESTCOMM_FEC
1881 This option enables support for the MPC5200's on-chip
1882 Fast Ethernet Controller
1883 If compiled as module, it will be called 'fec_mpc52xx.ko'.
1885 config FEC_MPC52xx_MDIO
1886 bool "MPC52xx FEC MDIO bus driver"
1887 depends on FEC_MPC52xx
1890 The MPC5200's FEC can connect to the Ethernet either with
1891 an external MII PHY chip or 10 Mbps 7-wire interface
1892 (Motorola? industry standard).
1893 If your board uses an external PHY connected to FEC, enable this.
1894 If not sure, enable.
1895 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1898 tristate "NE2000 compatible support for H8/300"
1901 Say Y here if you want to use the NE2000 compatible
1902 controller on the Renesas H8/300 processor.
1905 tristate "Atheros L2 Fast Ethernet support"
1910 This driver supports the Atheros L2 fast ethernet adapter.
1912 To compile this driver as a module, choose M here. The module
1913 will be called atl2.
1915 source "drivers/net/fs_enet/Kconfig"
1917 endif # NET_ETHERNET
1923 menuconfig NETDEV_1000
1924 bool "Ethernet (1000 Mbit)"
1928 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1929 type of Local Area Network (LAN) in universities and companies.
1931 Say Y here to get to see options for Gigabit Ethernet drivers.
1932 This option alone does not add any kernel code.
1933 Note that drivers supporting both 100 and 1000 MBit may be listed
1934 under "Ethernet (10 or 100MBit)" instead.
1936 If you say N, all options in this submenu will be skipped and disabled.
1941 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1944 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1945 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1946 adapter. The driver allows for using the Jumbo Frame option (9000
1947 bytes/frame) however it requires that your switches can handle this
1948 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1951 To compile this driver as a module, choose M here: the
1952 module will be called acenic.
1954 config ACENIC_OMIT_TIGON_I
1955 bool "Omit support for old Tigon I based AceNICs"
1958 Say Y here if you only have Tigon II based AceNICs and want to leave
1959 out support for the older Tigon I based cards which are no longer
1960 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1961 version)). This will reduce the size of the driver object by
1962 app. 100KB. If you are not sure whether your card is a Tigon I or a
1963 Tigon II, say N here.
1965 The safe and default value for this is N.
1968 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1972 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1974 D-Link DGE-550T Gigabit Ethernet Adapter.
1975 D-Link DL2000-based Gigabit Ethernet Adapter.
1976 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1978 To compile this driver as a module, choose M here: the
1979 module will be called dl2k.
1982 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1985 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1986 adapters. For more information on how to identify your adapter, go
1987 to the Adapter & Driver ID Guide at:
1989 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1991 For general information and support, go to the Intel support
1994 <http://support.intel.com>
1996 More specific information on configuring the driver is in
1997 <file:Documentation/networking/e1000.txt>.
1999 To compile this driver as a module, choose M here. The module
2000 will be called e1000.
2003 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2004 depends on PCI && (!SPARC32 || BROKEN)
2006 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2007 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2008 use the regular e1000 driver For more information on how to
2009 identify your adapter, go to the Adapter & Driver ID Guide at:
2011 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2013 For general information and support, go to the Intel support
2016 <http://support.intel.com>
2018 To compile this driver as a module, choose M here. The module
2019 will be called e1000e.
2022 tristate "IP1000 Gigabit Ethernet support"
2023 depends on PCI && EXPERIMENTAL
2026 This driver supports IP1000 gigabit Ethernet cards.
2028 To compile this driver as a module, choose M here: the module
2029 will be called ipg. This is recommended.
2032 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2035 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2036 adapters. For more information on how to identify your adapter, go
2037 to the Adapter & Driver ID Guide at:
2039 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2041 For general information and support, go to the Intel support
2044 <http://support.intel.com>
2046 More specific information on configuring the driver is in
2047 <file:Documentation/networking/e1000.txt>.
2049 To compile this driver as a module, choose M here. The module
2053 bool "Direct Cache Access (DCA) Support"
2055 depends on IGB && DCA && !(IGB=y && DCA=m)
2057 Say Y here if you want to use Direct Cache Access (DCA) in the
2058 driver. DCA is a method for warming the CPU cache before data
2059 is used, with the intent of lessening the impact of cache misses.
2062 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2065 This driver supports Intel(R) 82576 virtual functions. For more
2066 information on how to identify your adapter, go to the Adapter &
2069 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2071 For general information and support, go to the Intel support
2074 <http://support.intel.com>
2076 More specific information on configuring the driver is in
2077 <file:Documentation/networking/e1000.txt>.
2079 To compile this driver as a module, choose M here. The module
2080 will be called igbvf.
2082 source "drivers/net/ixp2000/Kconfig"
2085 tristate "MyriCOM Gigabit Ethernet support"
2088 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2090 To compile this driver as a module, choose M here: the module
2091 will be called myri_sbus. This is recommended.
2094 tristate "National Semiconductor DP83820 support"
2097 This is a driver for the National Semiconductor DP83820 series
2098 of gigabit ethernet MACs. Cards using this chipset include
2099 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2100 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2104 tristate "Packet Engines Hamachi GNIC-II support"
2108 If you have a Gigabit Ethernet card of this type, say Y and read
2109 the Ethernet-HOWTO, available from
2110 <http://www.tldp.org/docs.html#howto>.
2112 To compile this driver as a module, choose M here. The module will be
2116 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2117 depends on PCI && EXPERIMENTAL
2120 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2121 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2122 used by the Beowulf Linux cluster project. See
2123 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2124 information about this driver in particular and Beowulf in general.
2126 To compile this driver as a module, choose M here: the module
2127 will be called yellowfin. This is recommended.
2130 tristate "Realtek 8169 gigabit ethernet support"
2135 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2137 To compile this driver as a module, choose M here: the module
2138 will be called r8169. This is recommended.
2142 depends on R8169 && VLAN_8021Q
2144 Say Y here for the r8169 driver to support the functions required
2145 by the kernel 802.1Q code.
2150 tristate "SB1250 Gigabit Ethernet support"
2151 depends on SIBYTE_SB1xxx_SOC
2154 This driver supports Gigabit Ethernet interfaces based on the
2155 Broadcom SiByte family of System-On-a-Chip parts. They include
2156 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2159 To compile this driver as a module, choose M here: the module
2160 will be called sb1250-mac.
2163 tristate "SiS190/SiS191 gigabit ethernet support"
2168 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2169 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2170 appear in lan on motherboard designs which are based on SiS 965
2171 and SiS 966 south bridge.
2173 To compile this driver as a module, choose M here: the module
2174 will be called sis190. This is recommended.
2177 tristate "New SysKonnect GigaEthernet support"
2181 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2182 and related Gigabit Ethernet adapters. It is a new smaller driver
2183 with better performance and more complete ethtool support.
2185 It does not support the link failover and network management
2186 features that "portable" vendor supplied sk98lin driver does.
2188 This driver supports adapters based on the original Yukon chipset:
2189 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2190 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2192 It does not support the newer Yukon2 chipset: a separate driver,
2193 sky2, is provided for Yukon2-based adapters.
2195 To compile this driver as a module, choose M here: the module
2196 will be called skge. This is recommended.
2199 bool "Debugging interface"
2200 depends on SKGE && DEBUG_FS
2202 This option adds the ability to dump driver state for debugging.
2203 The file debugfs/skge/ethX displays the state of the internal
2204 transmit and receive rings.
2209 tristate "SysKonnect Yukon2 support"
2213 This driver supports Gigabit Ethernet adapters based on the
2214 Marvell Yukon 2 chipset:
2215 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2216 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2218 There is companion driver for the older Marvell Yukon and
2219 Genesis based adapters: skge.
2221 To compile this driver as a module, choose M here: the module
2222 will be called sky2. This is recommended.
2225 bool "Debugging interface"
2226 depends on SKY2 && DEBUG_FS
2228 This option adds the ability to dump driver state for debugging.
2229 The file debugfs/sky2/ethX displays the state of the internal
2230 transmit and receive rings.
2235 tristate "VIA Velocity support"
2241 If you have a VIA "Velocity" based network card say Y here.
2243 To compile this driver as a module, choose M here. The module
2244 will be called via-velocity.
2247 tristate "Broadcom Tigon3 support"
2251 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2253 To compile this driver as a module, choose M here: the module
2254 will be called tg3. This is recommended.
2257 tristate "Broadcom NetXtremeII support"
2262 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2264 To compile this driver as a module, choose M here: the module
2265 will be called bnx2. This is recommended.
2268 tristate "Spider Gigabit Ethernet driver"
2269 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2272 This driver supports the Gigabit Ethernet chips present on the
2273 Cell Processor-Based Blades from IBM.
2276 tristate "Tundra TSI108 gigabit Ethernet support"
2277 depends on TSI108_BRIDGE
2279 This driver supports Tundra TSI108 gigabit Ethernet ports.
2280 To compile this driver as a module, choose M here: the module
2281 will be called tsi108_eth.
2284 tristate "PS3 Gigabit Ethernet driver"
2286 select PS3_SYS_MANAGER
2288 This driver supports the network device on the PS3 game
2289 console. This driver has built-in support for Ethernet.
2291 To compile this driver as a module, choose M here: the
2292 module will be called ps3_gelic.
2294 config GELIC_WIRELESS
2295 bool "PS3 Wireless support"
2296 depends on GELIC_NET
2299 This option adds the support for the wireless feature of PS3.
2300 If you have the wireless-less model of PS3 or have no plan to
2301 use wireless feature, disabling this option saves memory. As
2302 the driver automatically distinguishes the models, you can
2303 safely enable this option even if you have a wireless-less model.
2305 config GELIC_WIRELESS_OLD_PSK_INTERFACE
2306 bool "PS3 Wireless private PSK interface (OBSOLETE)"
2307 depends on GELIC_WIRELESS
2309 This option retains the obsolete private interface to pass
2310 the PSK from user space programs to the driver. The PSK
2311 stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2312 (WPA-Personal) environment.
2313 If WPA[2]-PSK is used and you need to use old programs that
2314 support only this old interface, say Y. Otherwise N.
2319 tristate "Freescale PQ MDIO"
2323 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2326 tristate "Gianfar Ethernet"
2332 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2333 and MPC86xx family of chips, and the FEC on the 8540.
2336 tristate "Freescale QE Gigabit Ethernet"
2337 depends on QUICC_ENGINE
2341 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2342 which is available on some Freescale SOCs.
2344 config UGETH_MAGIC_PACKET
2345 bool "Magic Packet detection support"
2348 config UGETH_TX_ON_DEMAND
2349 bool "Transmit on Demand support"
2353 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2354 depends on MV64360 || MV64X60 || PPC32 || PLAT_ORION
2358 This driver supports the gigabit ethernet MACs in the
2359 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2360 in the Marvell Orion ARM SoC family.
2362 Some boards that use the Discovery chipset are the Momenco
2363 Ocelot C and Jaguar ATX and Pegasos II.
2365 config XILINX_LL_TEMAC
2366 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2368 depends on PPC_DCR_NATIVE
2370 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2371 core used in Xilinx Spartan and Virtex FPGAs
2374 tristate "QLogic QLA3XXX Network Driver Support"
2377 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2379 To compile this driver as a module, choose M here: the module
2380 will be called qla3xxx.
2383 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2388 This driver supports the Atheros/Attansic L1 gigabit ethernet
2391 To compile this driver as a module, choose M here. The module
2392 will be called atl1.
2395 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2396 depends on PCI && EXPERIMENTAL
2400 This driver supports the Atheros L1E gigabit ethernet adapter.
2402 To compile this driver as a module, choose M here. The module
2403 will be called atl1e.
2406 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2407 depends on PCI && EXPERIMENTAL
2411 This driver supports the Atheros L1C gigabit ethernet adapter.
2413 To compile this driver as a module, choose M here. The module
2414 will be called atl1c.
2417 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2422 This driver supports the PCI-Express gigabit ethernet adapters
2423 based on JMicron JMC250 chipset.
2425 To compile this driver as a module, choose M here. The module
2431 # 10 Gigabit Ethernet
2434 menuconfig NETDEV_10000
2435 bool "Ethernet (10000 Mbit)"
2439 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2440 This option alone does not add any kernel code.
2442 If you say N, all options in this submenu will be skipped and disabled.
2450 tristate "Chelsio 10Gb Ethernet support"
2455 This driver supports Chelsio gigabit and 10-gigabit
2456 Ethernet cards. More information about adapter features and
2457 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2459 For general information about Chelsio and our products, visit
2460 our website at <http://www.chelsio.com>.
2462 For customer support, please visit our customer support page at
2463 <http://www.chelsio.com/support.htm>.
2465 Please send feedback to <linux-bugs@chelsio.com>.
2467 To compile this driver as a module, choose M here: the module
2468 will be called cxgb.
2470 config CHELSIO_T1_1G
2471 bool "Chelsio gigabit Ethernet support"
2472 depends on CHELSIO_T1
2474 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2475 are using only 10G cards say 'N' here.
2477 config CHELSIO_T3_DEPENDS
2479 depends on PCI && INET
2483 tristate "Chelsio Communications T3 10Gb Ethernet support"
2484 depends on CHELSIO_T3_DEPENDS
2488 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2491 For general information about Chelsio and our products, visit
2492 our website at <http://www.chelsio.com>.
2494 For customer support, please visit our customer support page at
2495 <http://www.chelsio.com/support.htm>.
2497 Please send feedback to <linux-bugs@chelsio.com>.
2499 To compile this driver as a module, choose M here: the module
2500 will be called cxgb3.
2503 tristate "eHEA Ethernet support"
2504 depends on IBMEBUS && INET && SPARSEMEM
2507 This driver supports the IBM pSeries eHEA ethernet adapter.
2509 To compile the driver as a module, choose M here. The module
2510 will be called ehea.
2513 tristate "Cisco 10G Ethernet NIC support"
2514 depends on PCI && INET
2517 This enables the support for the Cisco 10G Ethernet card.
2520 tristate "Intel(R) 10GbE PCI Express adapters support"
2521 depends on PCI && INET
2524 This driver supports Intel(R) 10GbE PCI Express family of
2525 adapters. For more information on how to identify your adapter, go
2526 to the Adapter & Driver ID Guide at:
2528 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2530 For general information and support, go to the Intel support
2533 <http://support.intel.com>
2535 To compile this driver as a module, choose M here. The module
2536 will be called ixgbe.
2539 bool "Direct Cache Access (DCA) Support"
2541 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2543 Say Y here if you want to use Direct Cache Access (DCA) in the
2544 driver. DCA is a method for warming the CPU cache before data
2545 is used, with the intent of lessening the impact of cache misses.
2548 bool "Data Center Bridging (DCB) Support"
2550 depends on IXGBE && DCB
2552 Say Y here if you want to use Data Center Bridging (DCB) in the
2558 tristate "Intel(R) PRO/10GbE support"
2561 This driver supports Intel(R) PRO/10GbE family of adapters for
2562 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2563 instead. For more information on how to identify your adapter, go
2564 to the Adapter & Driver ID Guide at:
2566 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2568 For general information and support, go to the Intel support
2571 <http://support.intel.com>
2573 More specific information on configuring the driver is in
2574 <file:Documentation/networking/ixgb.txt>.
2576 To compile this driver as a module, choose M here. The module
2577 will be called ixgb.
2580 tristate "S2IO 10Gbe XFrame NIC"
2583 This driver supports the 10Gbe XFrame NIC of S2IO.
2584 More specific information on configuring the driver is in
2585 <file:Documentation/networking/s2io.txt>.
2588 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2589 depends on PCI && INET
2591 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2592 I/O Virtualized Server Adapter.
2593 More specific information on configuring the driver is in
2594 <file:Documentation/networking/vxge.txt>.
2596 config VXGE_DEBUG_TRACE_ALL
2597 bool "Enabling All Debug trace statments in driver"
2601 Say Y here if you want to enabling all the debug trace statements in
2602 driver. By default only few debug trace statements are enabled.
2605 tristate "Myricom Myri-10G Ethernet support"
2606 depends on PCI && INET
2611 This driver supports Myricom Myri-10G Dual Protocol interface in
2612 Ethernet mode. If the eeprom on your board is not recent enough,
2613 you will need a newer firmware image.
2614 You may get this image or more information, at:
2616 <http://www.myri.com/scs/download-Myri10GE.html>
2618 To compile this driver as a module, choose M here. The module
2619 will be called myri10ge.
2622 bool "Direct Cache Access (DCA) Support"
2624 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2626 Say Y here if you want to use Direct Cache Access (DCA) in the
2627 driver. DCA is a method for warming the CPU cache before data
2628 is used, with the intent of lessening the impact of cache misses.
2631 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2634 This enables the support for NetXen's Gigabit Ethernet card.
2637 tristate "Sun Neptune 10Gbit Ethernet support"
2640 This enables support for cards based upon Sun's
2644 tristate "PA Semi 1/10Gbit MAC"
2645 depends on PPC_PASEMI && PCI
2649 This driver supports the on-chip 1/10Gbit Ethernet controller on
2650 PA Semi's PWRficient line of chips.
2653 tristate "Mellanox Technologies 10Gbit Ethernet support"
2654 depends on PCI && INET
2658 This driver supports Mellanox Technologies ConnectX Ethernet
2667 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2668 depends on MLX4_CORE
2671 This option causes debugging code to be compiled into the
2672 mlx4_core driver. The output can be turned on via the
2673 debug_level module parameter (which can also be set after
2674 the driver is loaded through sysfs).
2677 tristate "Tehuti Networks 10G Ethernet"
2680 Tehuti Networks 10G Ethernet NIC
2683 tristate "Broadcom NetXtremeII 10Gb support"
2689 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2690 To compile this driver as a module, choose M here: the module
2691 will be called bnx2x. This is recommended.
2694 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2697 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2699 To compile this driver as a module, choose M here: the module
2700 will be called qlge.
2702 source "drivers/net/sfc/Kconfig"
2704 source "drivers/net/benet/Kconfig"
2706 endif # NETDEV_10000
2708 source "drivers/net/tokenring/Kconfig"
2710 source "drivers/net/wireless/Kconfig"
2712 source "drivers/net/wimax/Kconfig"
2714 source "drivers/net/usb/Kconfig"
2716 source "drivers/net/pcmcia/Kconfig"
2718 source "drivers/net/wan/Kconfig"
2720 source "drivers/atm/Kconfig"
2722 source "drivers/s390/net/Kconfig"
2724 config XEN_NETDEV_FRONTEND
2725 tristate "Xen network device frontend driver"
2729 The network device frontend driver allows the kernel to
2730 access network devices exported exported by a virtual
2731 machine containing a physical network device driver. The
2732 frontend driver is intended for unprivileged guest domains;
2733 if you are compiling a kernel for a Xen guest, you almost
2734 certainly want to enable this.
2737 tristate "iSeries Virtual Ethernet driver support"
2738 depends on PPC_ISERIES
2741 tristate "RapidIO Ethernet over messaging driver support"
2744 config RIONET_TX_SIZE
2745 int "Number of outbound queue entries"
2749 config RIONET_RX_SIZE
2750 int "Number of inbound queue entries"
2755 tristate "FDDI driver support"
2756 depends on (PCI || EISA || TC)
2758 Fiber Distributed Data Interface is a high speed local area network
2759 design; essentially a replacement for high speed Ethernet. FDDI can
2760 run over copper or fiber. If you are connected to such a network and
2761 want a driver for the FDDI card in your computer, say Y here (and
2762 then also Y to the driver for your FDDI card, below). Most people
2766 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2767 depends on FDDI && (PCI || EISA || TC)
2769 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2770 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2771 to a local FDDI network.
2773 To compile this driver as a module, choose M here: the module
2774 will be called defxx. If unsure, say N.
2778 prompt "Use MMIO instead of PIO" if PCI || EISA
2780 default n if PCI || EISA
2783 This instructs the driver to use EISA or PCI memory-mapped I/O
2784 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2785 Enabling this gives an improvement in processing time in parts
2786 of the driver, but it may cause problems with EISA (DEFEA)
2787 adapters. TURBOchannel does not have the concept of I/O ports,
2788 so MMIO is always used for these (DEFTA) adapters.
2793 tristate "SysKonnect FDDI PCI support"
2794 depends on FDDI && PCI
2797 Say Y here if you have a SysKonnect FDDI PCI adapter.
2798 The following adapters are supported by this driver:
2799 - SK-5521 (SK-NET FDDI-UP)
2800 - SK-5522 (SK-NET FDDI-UP DAS)
2801 - SK-5541 (SK-NET FDDI-FP)
2802 - SK-5543 (SK-NET FDDI-LP)
2803 - SK-5544 (SK-NET FDDI-LP DAS)
2804 - SK-5821 (SK-NET FDDI-UP64)
2805 - SK-5822 (SK-NET FDDI-UP64 DAS)
2806 - SK-5841 (SK-NET FDDI-FP64)
2807 - SK-5843 (SK-NET FDDI-LP64)
2808 - SK-5844 (SK-NET FDDI-LP64 DAS)
2809 - Netelligent 100 FDDI DAS Fibre SC
2810 - Netelligent 100 FDDI SAS Fibre SC
2811 - Netelligent 100 FDDI DAS UTP
2812 - Netelligent 100 FDDI SAS UTP
2813 - Netelligent 100 FDDI SAS Fibre MIC
2815 Read <file:Documentation/networking/skfp.txt> for information about
2818 Questions concerning this driver can be addressed to:
2819 <linux@syskonnect.de>
2821 To compile this driver as a module, choose M here: the module
2822 will be called skfp. This is recommended.
2825 bool "HIPPI driver support (EXPERIMENTAL)"
2826 depends on EXPERIMENTAL && INET && PCI
2828 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2829 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2830 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2831 single-mode). HIPPI networks are commonly used for clusters and to
2832 connect to super computers. If you are connected to a HIPPI network
2833 and have a HIPPI network card in your computer that you want to use
2834 under Linux, say Y here (you must also remember to enable the driver
2835 for your HIPPI card below). Most people will say N here.
2838 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2839 depends on HIPPI && PCI
2841 Say Y here if this is your PCI HIPPI network card.
2843 To compile this driver as a module, choose M here: the module
2844 will be called rrunner. If unsure, say N.
2846 config ROADRUNNER_LARGE_RINGS
2847 bool "Use large TX/RX rings (EXPERIMENTAL)"
2848 depends on ROADRUNNER
2850 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2851 of additional memory to allow for fastest operation, both for
2852 transmitting and receiving. This memory cannot be used by any other
2853 kernel code or by user space programs. Say Y here only if you have
2857 tristate "PLIP (parallel port) support"
2860 PLIP (Parallel Line Internet Protocol) is used to create a
2861 reasonably fast mini network consisting of two (or, rarely, more)
2862 local machines. A PLIP link from a Linux box is a popular means to
2863 install a Linux distribution on a machine which doesn't have a
2864 CD-ROM drive (a minimal system has to be transferred with floppies
2865 first). The kernels on both machines need to have this PLIP option
2866 enabled for this to work.
2868 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2869 ports (the connectors at the computers with 25 holes) are connected
2870 with "null printer" or "Turbo Laplink" cables which can transmit 4
2871 bits at a time (mode 0) or with special PLIP cables, to be used on
2872 bidirectional parallel ports only, which can transmit 8 bits at a
2873 time (mode 1); you can find the wiring of these cables in
2874 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2875 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2876 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2877 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2878 and winsock or NCSA's telnet.
2880 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2881 as the NET-3-HOWTO, both available from
2882 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2883 protocol has been changed and this PLIP driver won't work together
2884 with the PLIP support in Linux versions 1.0.x. This option enlarges
2885 your kernel by about 8 KB.
2887 To compile this driver as a module, choose M here. The module
2888 will be called plip. If unsure, say Y or M, in case you buy
2892 tristate "PPP (point-to-point protocol) support"
2895 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2896 the same purpose: sending Internet traffic over telephone (and other
2897 serial) lines. Ask your access provider if they support it, because
2898 otherwise you can't use it; most Internet access providers these
2899 days support PPP rather than SLIP.
2901 To use PPP, you need an additional program called pppd as described
2902 in the PPP-HOWTO, available at
2903 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2904 the version of pppd recommended in <file:Documentation/Changes>.
2905 The PPP option enlarges your kernel by about 16 KB.
2907 There are actually two versions of PPP: the traditional PPP for
2908 asynchronous lines, such as regular analog phone lines, and
2909 synchronous PPP which can be used over digital ISDN lines for
2910 example. If you want to use PPP over phone lines or other
2911 asynchronous serial lines, you need to say Y (or M) here and also to
2912 the next option, "PPP support for async serial ports". For PPP over
2913 synchronous lines, you should say Y (or M) here and to "Support
2914 synchronous PPP", below.
2916 If you said Y to "Version information on all symbols" above, then
2917 you cannot compile the PPP driver into the kernel; you can then only
2918 compile it as a module. To compile this driver as a module, choose M
2919 here. The module will be called ppp_generic.
2921 config PPP_MULTILINK
2922 bool "PPP multilink support (EXPERIMENTAL)"
2923 depends on PPP && EXPERIMENTAL
2925 PPP multilink is a protocol (defined in RFC 1990) which allows you
2926 to combine several (logical or physical) lines into one logical PPP
2927 connection, so that you can utilize your full bandwidth.
2929 This has to be supported at the other end as well and you need a
2930 version of the pppd daemon which understands the multilink protocol.
2935 bool "PPP filtering"
2938 Say Y here if you want to be able to filter the packets passing over
2939 PPP interfaces. This allows you to control which packets count as
2940 activity (i.e. which packets will reset the idle timer or bring up
2941 a demand-dialed link) and which packets are to be dropped entirely.
2942 You need to say Y here if you wish to use the pass-filter and
2943 active-filter options to pppd.
2948 tristate "PPP support for async serial ports"
2952 Say Y (or M) here if you want to be able to use PPP over standard
2953 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2954 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2957 To compile this driver as a module, choose M here.
2962 tristate "PPP support for sync tty ports"
2965 Say Y (or M) here if you want to be able to use PPP over synchronous
2966 (HDLC) tty devices, such as the SyncLink adapter. These devices
2967 are often used for high-speed leased lines like T1/E1.
2969 To compile this driver as a module, choose M here.
2972 tristate "PPP Deflate compression"
2977 Support for the Deflate compression method for PPP, which uses the
2978 Deflate algorithm (the same algorithm that gzip uses) to compress
2979 each PPP packet before it is sent over the wire. The machine at the
2980 other end of the PPP link (usually your ISP) has to support the
2981 Deflate compression method as well for this to be useful. Even if
2982 they don't support it, it is safe to say Y here.
2984 To compile this driver as a module, choose M here.
2987 tristate "PPP BSD-Compress compression"
2990 Support for the BSD-Compress compression method for PPP, which uses
2991 the LZW compression method to compress each PPP packet before it is
2992 sent over the wire. The machine at the other end of the PPP link
2993 (usually your ISP) has to support the BSD-Compress compression
2994 method as well for this to be useful. Even if they don't support it,
2995 it is safe to say Y here.
2997 The PPP Deflate compression method ("PPP Deflate compression",
2998 above) is preferable to BSD-Compress, because it compresses better
3001 Note that the BSD compression code will always be compiled as a
3002 module; it is called bsd_comp and will show up in the directory
3003 modules once you have said "make modules". If unsure, say N.
3006 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3007 depends on PPP && EXPERIMENTAL
3013 Support for the MPPE Encryption protocol, as employed by the
3014 Microsoft Point-to-Point Tunneling Protocol.
3016 See http://pptpclient.sourceforge.net/ for information on
3017 configuring PPTP clients and servers to utilize this method.
3020 tristate "PPP over Ethernet (EXPERIMENTAL)"
3021 depends on EXPERIMENTAL && PPP
3023 Support for PPP over Ethernet.
3025 This driver requires the latest version of pppd from the CVS
3026 repository at cvs.samba.org. Alternatively, see the
3027 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3028 which contains instruction on how to use this driver (under
3029 the heading "Kernel mode PPPoE").
3032 tristate "PPP over ATM"
3033 depends on ATM && PPP
3035 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3036 This implementation does not yet comply with section 8 of RFC2364,
3037 which can lead to bad results if the ATM peer loses state and
3038 changes its encapsulation unilaterally.
3041 tristate "PPP over L2TP (EXPERIMENTAL)"
3042 depends on EXPERIMENTAL && PPP && INET
3044 Support for PPP-over-L2TP socket family. L2TP is a protocol
3045 used by ISPs and enterprises to tunnel PPP traffic over UDP
3046 tunnels. L2TP is replacing PPTP for VPN uses.
3048 This kernel component handles only L2TP data packets: a
3049 userland daemon handles L2TP the control protocol (tunnel
3050 and session setup). One such daemon is OpenL2TP
3051 (http://openl2tp.sourceforge.net/).
3054 tristate "SLIP (serial line) support"
3056 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3057 connect to your Internet service provider or to connect to some
3058 other local Unix box or if you want to configure your Linux box as a
3059 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3060 Internet Protocol) is a protocol used to send Internet traffic over
3061 serial connections such as telephone lines or null modem cables;
3062 nowadays, the protocol PPP is more commonly used for this same
3065 Normally, your access provider has to support SLIP in order for you
3066 to be able to use it, but there is now a SLIP emulator called SLiRP
3067 around (available from
3068 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3069 allows you to use SLIP over a regular dial up shell connection. If
3070 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3071 NET-3-HOWTO, available from
3072 <http://www.tldp.org/docs.html#howto>, explains how to
3073 configure SLIP. Note that you don't need this option if you just
3074 want to run term (term is a program which gives you almost full
3075 Internet connectivity if you have a regular dial up shell account on
3076 some Internet connected Unix computer. Read
3077 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3078 support will enlarge your kernel by about 4 KB. If unsure, say N.
3080 To compile this driver as a module, choose M here. The module
3081 will be called slip.
3083 config SLIP_COMPRESSED
3084 bool "CSLIP compressed headers"
3088 This protocol is faster than SLIP because it uses compression on the
3089 TCP/IP headers (not on the data itself), but it has to be supported
3090 on both ends. Ask your access provider if you are not sure and
3091 answer Y, just in case. You will still be able to use plain SLIP. If
3092 you plan to use SLiRP, the SLIP emulator (available from
3093 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3094 allows you to use SLIP over a regular dial up shell connection, you
3095 definitely want to say Y here. The NET-3-HOWTO, available from
3096 <http://www.tldp.org/docs.html#howto>, explains how to configure
3097 CSLIP. This won't enlarge your kernel.
3102 This option enables Van Jacobsen serial line header compression
3106 bool "Keepalive and linefill"
3109 Adds additional capabilities to the SLIP driver to support the
3110 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3113 config SLIP_MODE_SLIP6
3114 bool "Six bit SLIP encapsulation"
3117 Just occasionally you may need to run IP over hostile serial
3118 networks that don't pass all control characters or are only seven
3119 bit. Saying Y here adds an extra mode you can use with SLIP:
3120 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3121 the serial device. Naturally, this has to be supported at the other
3122 end of the link as well. It's good enough, for example, to run IP
3123 over the async ports of a Camtec JNT Pad. If unsure, say N.
3126 bool "Fibre Channel driver support"
3127 depends on SCSI && PCI
3129 Fibre Channel is a high speed serial protocol mainly used to connect
3130 large storage devices to the computer; it is compatible with and
3131 intended to replace SCSI.
3133 If you intend to use Fibre Channel, you need to have a Fibre channel
3134 adaptor card in your computer; say Y here and to the driver for your
3135 adaptor below. You also should have said Y to "SCSI support" and
3136 "SCSI generic support".
3139 tristate "Network console logging support (EXPERIMENTAL)"
3140 depends on EXPERIMENTAL
3142 If you want to log kernel messages over the network, enable this.
3143 See <file:Documentation/networking/netconsole.txt> for details.
3145 config NETCONSOLE_DYNAMIC
3146 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3147 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3150 This option enables the ability to dynamically reconfigure target
3151 parameters (interface, IP addresses, port numbers, MAC addresses)
3152 at runtime through a userspace interface exported using configfs.
3153 See <file:Documentation/networking/netconsole.txt> for details.
3159 bool "Netpoll traffic trapping"
3163 config NET_POLL_CONTROLLER
3167 tristate "Virtio network driver (EXPERIMENTAL)"
3168 depends on EXPERIMENTAL && VIRTIO
3170 This is the virtual network driver for virtio. It can be used with
3171 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.