3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
29 config NETDEVICES_MULTIQUEUE
30 bool "Netdevice multiple hardware queue support"
32 Say Y here if you want to allow the network stack to use multiple
33 hardware TX queues on an ethernet device.
35 Most people will say N here.
38 tristate "Intermediate Functional Block support"
39 depends on NET_CLS_ACT
41 This is an intermediate driver that allows sharing of
43 To compile this driver as a module, choose M here: the module
44 will be called ifb. If you want to use more than one ifb
45 device at a time, you need to compile this driver as a module.
46 Instead of 'ifb', the devices will then be called 'ifb0',
48 Look at the iproute2 documentation directory for usage etc
51 tristate "Dummy net driver support"
53 This is essentially a bit-bucket device (i.e. traffic you send to
54 this device is consigned into oblivion) with a configurable IP
55 address. It is most commonly used in order to make your currently
56 inactive SLIP address seem like a real address for local programs.
57 If you use SLIP or PPP, you might want to say Y here. Since this
58 thing often comes in handy, the default is Y. It won't enlarge your
59 kernel either. What a deal. Read about it in the Network
60 Administrator's Guide, available from
61 <http://www.tldp.org/docs.html#guide>.
63 To compile this driver as a module, choose M here: the module
64 will be called dummy. If you want to use more than one dummy
65 device at a time, you need to compile this driver as a module.
66 Instead of 'dummy', the devices will then be called 'dummy0',
70 tristate "Bonding driver support"
73 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
74 Channels together. This is called 'Etherchannel' by Cisco,
75 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
77 The driver supports multiple bonding modes to allow for both high
78 performance and high availability operation.
80 Refer to <file:Documentation/networking/bonding.txt> for more
83 To compile this driver as a module, choose M here: the module
84 will be called bonding.
87 tristate "MAC-VLAN support (EXPERIMENTAL)"
88 depends on EXPERIMENTAL
90 This allows one to create virtual interfaces that map packets to
91 or from specific MAC addresses to a particular interface.
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "EQL (serial line load balancing) support"
99 If you have two serial connections to some other computer (this
100 usually requires two modems and two telephone lines) and you use
101 SLIP (the protocol for sending Internet traffic over telephone
102 lines) or PPP (a better SLIP) on them, you can make them behave like
103 one double speed connection using this driver. Naturally, this has
104 to be supported at the other end as well, either with a similar EQL
105 Linux driver or with a Livingston Portmaster 2e.
107 Say Y if you want this and read
108 <file:Documentation/networking/eql.txt>. You may also want to read
109 section 6.2 of the NET-3-HOWTO, available from
110 <http://www.tldp.org/docs.html#howto>.
112 To compile this driver as a module, choose M here: the module
113 will be called eql. If unsure, say N.
116 tristate "Universal TUN/TAP device driver support"
119 TUN/TAP provides packet reception and transmission for user space
120 programs. It can be viewed as a simple Point-to-Point or Ethernet
121 device, which instead of receiving packets from a physical media,
122 receives them from user space program and instead of sending packets
123 via physical media writes them to the user space program.
125 When a program opens /dev/net/tun, driver creates and registers
126 corresponding net device tunX or tapX. After a program closed above
127 devices, driver will automatically delete tunXX or tapXX device and
128 all routes corresponding to it.
130 Please read <file:Documentation/networking/tuntap.txt> for more
133 To compile this driver as a module, choose M here: the module
136 If you don't know what to use this for, you don't need it.
139 tristate "Virtual ethernet device"
141 The device is an ethernet tunnel. Devices are created in pairs. When
142 one end receives the packet it appears on its pair and vice versa.
145 tristate "General Instruments Surfboard 1000"
148 This is a driver for the General Instrument (also known as
149 NextLevel) SURFboard 1000 internal
150 cable modem. This is an ISA card which is used by a number of cable
151 TV companies to provide cable modem access. It's a one-way
152 downstream-only cable modem, meaning that your upstream net link is
153 provided by your regular phone modem.
155 At present this driver only compiles as a module, so say M here if
156 you have this card. The module will be called sb1000. Then read
157 <file:Documentation/networking/README.sb1000> for information on how
158 to use this module, as it needs special ppp scripts for establishing
159 a connection. Further documentation and the necessary scripts can be
162 <http://www.jacksonville.net/~fventuri/>
163 <http://home.adelphia.net/~siglercm/sb1000.html>
164 <http://linuxpower.cx/~cable/>
166 If you don't have this card, of course say N.
169 tristate "IP1000 Gigabit Ethernet support"
170 depends on PCI && EXPERIMENTAL
172 This driver supports IP1000 gigabit Ethernet cards.
174 To compile this driver as a module, choose M here: the module
175 will be called ipg. This is recommended.
177 source "drivers/net/arcnet/Kconfig"
179 source "drivers/net/phy/Kconfig"
185 menuconfig NET_ETHERNET
186 bool "Ethernet (10 or 100Mbit)"
189 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
190 type of Local Area Network (LAN) in universities and companies.
192 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
193 coaxial cable, linking computers in a chain), 10BASE-T or twisted
194 pair (10 Mbps over twisted pair cable, linking computers to central
195 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
196 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
197 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
198 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
199 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
200 Ethernet (1 Gbps over optical fiber or short copper links).
202 If your Linux machine will be connected to an Ethernet and you have
203 an Ethernet network interface card (NIC) installed in your computer,
204 say Y here and read the Ethernet-HOWTO, available from
205 <http://www.tldp.org/docs.html#howto>. You will then also have
206 to say Y to the driver for your particular NIC.
208 Note that the answer to this question won't directly affect the
209 kernel: saying N will just cause the configurator to skip all
210 the questions about Ethernet network cards. If unsure, say N.
215 tristate "Generic Media Independent Interface device support"
217 Most ethernet controllers have MII transceiver either as an external
218 or internal device. It is safe to say Y or M here even if your
219 ethernet card lack MII.
222 tristate "Atmel MACB support"
223 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263
226 The Atmel MACB ethernet interface is found on many AT32 and AT91
227 parts. Say Y to include support for the MACB chip.
229 To compile this driver as a module, choose M here: the module
232 source "drivers/net/arm/Kconfig"
235 tristate "ASIX AX88796 NE2000 clone support"
236 depends on ARM || MIPS
240 AX88796 driver, using platform bus to provide
241 chip detection and resources
244 tristate "MACE (Power Mac ethernet) support"
245 depends on PPC_PMAC && PPC32
248 Power Macintoshes and clones with Ethernet built-in on the
249 motherboard will usually use a MACE (Medium Access Control for
250 Ethernet) interface. Say Y to include support for the MACE chip.
252 To compile this driver as a module, choose M here: the module
255 config MACE_AAUI_PORT
256 bool "Use AAUI port instead of TP by default"
259 Some Apple machines (notably the Apple Network Server) which use the
260 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
261 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
262 Y here if you have such a machine. If unsure, say N.
263 The driver will default to AAUI on ANS anyway, and if you use it as
264 a module, you can provide the port_aaui=0|1 to force the driver.
267 tristate "BMAC (G3 ethernet) support"
268 depends on PPC_PMAC && PPC32
271 Say Y for support of BMAC Ethernet interfaces. These are used on G3
274 To compile this driver as a module, choose M here: the module
278 tristate "Ariadne support"
281 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
284 To compile this driver as a module, choose M here: the module
285 will be called ariadne.
288 tristate "A2065 support"
292 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
295 To compile this driver as a module, choose M here: the module
296 will be called a2065.
299 tristate "Hydra support"
303 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
305 To compile this driver as a module, choose M here: the module
306 will be called hydra.
309 tristate "Zorro NS8390-based Ethernet support"
313 This driver is for Zorro Ethernet cards using an NS8390-compatible
314 chipset, like the Village Tronic Ariadne II and the Individual
315 Computers X-Surf Ethernet cards. If you have such a card, say Y.
318 To compile this driver as a module, choose M here: the module
319 will be called zorro8390.
322 tristate "PCMCIA NE2000 support"
323 depends on AMIGA_PCMCIA
326 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
329 To compile this driver as a module, choose M here: the module
333 tristate "Apollo 3c505 support"
336 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
337 If you don't have one made for Apollos, you can use one from a PC,
338 except that your Apollo won't be able to boot from it (because the
339 code in the ROM will be for a PC).
342 bool "Macintosh NS 8390 based ethernet cards"
346 If you want to include a driver to support Nubus or LC-PDS
347 Ethernet cards using an NS8390 chipset or its equivalent, say Y
348 and read the Ethernet-HOWTO, available from
349 <http://www.tldp.org/docs.html#howto>.
352 tristate "Macintosh CS89x0 based ethernet cards"
355 Support for CS89x0 chipset based Ethernet cards. If you have a
356 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
357 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 and read
361 <file:Documentation/networking/net-modules.txt>. This module will
365 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
368 Support for NatSemi SONIC based Ethernet devices. This includes
369 the onboard Ethernet in many Quadras as well as some LC-PDS,
370 a few Nubus and all known Comm Slot Ethernet cards. If you have
371 one of these say Y and read the Ethernet-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>.
374 To compile this driver as a module, choose M here and read
375 <file:Documentation/networking/net-modules.txt>. This module will
379 bool "Macintosh (AV) onboard MACE ethernet"
383 Support for the onboard AMD 79C940 MACE Ethernet controller used in
384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
385 say Y and read the Ethernet-HOWTO, available from
386 <http://www.tldp.org/docs.html#howto>.
389 tristate "MVME147 (Lance) Ethernet support"
393 Support for the on-board Ethernet interface on the Motorola MVME147
394 single-board computer. Say Y here to include the
395 driver for this chip in your kernel.
396 To compile this driver as a module, choose M here.
399 tristate "MVME16x Ethernet support"
402 This is the driver for the Ethernet interface on the Motorola
403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
404 driver for this chip in your kernel.
405 To compile this driver as a module, choose M here.
408 tristate "BVME6000 Ethernet support"
411 This is the driver for the Ethernet interface on BVME4000 and
412 BVME6000 VME boards. Say Y here to include the driver for this chip
414 To compile this driver as a module, choose M here.
417 tristate "Atari Lance support"
420 Say Y to include support for several Atari Ethernet adapters based
421 on the AMD Lance chipset: RieblCard (with or without battery), or
422 PAMCard VME (also the version by Rhotron, with different addresses).
425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
435 If you're not building a kernel for a Sun 3, say N.
438 bool "Sun3 on-board Intel 82586 support"
441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional
447 bool "HP on-board LANCE support"
451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here.
455 tristate "Lasi ethernet"
458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM
465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines.
468 config MIPS_JAZZ_SONIC
469 tristate "MIPS JAZZ onboard SONIC Ethernet support"
472 This is the driver for the onboard card of MIPS Magnum 4000,
473 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
475 config MIPS_AU1X00_ENET
476 bool "MIPS AU1000 Ethernet support"
477 depends on SOC_AU1X00
481 If you have an Alchemy Semi AU1X00 based system
482 say Y. Otherwise, say N.
484 config NET_SB1250_MAC
485 tristate "SB1250 Ethernet support"
486 depends on SIBYTE_SB1xxx_SOC
489 bool "SGI IOC3 Ethernet"
490 depends on PCI && SGI_IP27
494 If you have a network (Ethernet) card of this type, say Y and read
495 the Ethernet-HOWTO, available from
496 <http://www.tldp.org/docs.html#howto>.
499 tristate "MIPS simulator Network device"
502 The MIPSNET device is a simple Ethernet network device which is
503 emulated by the MIPS Simulator.
504 If you are not using a MIPSsim or are unsure, say N.
506 config SGI_O2MACE_ETH
507 tristate "SGI O2 MACE Fast Ethernet support"
508 depends on SGI_IP32=y
511 tristate "National DP83902AV support"
515 Support for cards based on the National Semiconductor DP83902AV
516 ST-NIC Serial Network Interface Controller for Twisted Pair. This
517 is a 10Mbit/sec Ethernet controller. Product overview and specs at
518 <http://www.national.com/pf/DP/DP83902A.html>.
523 tristate "Sun LANCE support"
527 This driver supports the "le" interface present on all 32-bit Sparc
528 systems, on some older Ultra systems and as an Sbus option. These
529 cards are based on the AMD Lance chipset, which is better known
530 via the NE2100 cards.
532 To compile this driver as a module, choose M here: the module
533 will be called sunlance.
536 tristate "Sun Happy Meal 10/100baseT support"
537 depends on SBUS || PCI
540 This driver supports the "hme" interface present on most Ultra
541 systems and as an option on older Sbus systems. This driver supports
542 both PCI and Sbus devices. This driver also supports the "qfe" quad
543 100baseT device available in both PCI and Sbus configurations.
545 To compile this driver as a module, choose M here: the module
546 will be called sunhme.
549 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
550 depends on SBUS && EXPERIMENTAL
553 This driver supports the "be" interface available as an Sbus option.
554 This is Sun's older 100baseT Ethernet device.
556 To compile this driver as a module, choose M here: the module
557 will be called sunbmac.
560 tristate "Sun QuadEthernet support"
564 This driver supports the "qe" 10baseT Ethernet device, available as
565 an Sbus option. Note that this is not the same as Quad FastEthernet
566 "qfe" which is supported by the Happy Meal driver instead.
568 To compile this driver as a module, choose M here: the module
569 will be called sunqe.
572 tristate "Sun GEM support"
576 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
577 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
580 tristate "Sun Cassini support"
584 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
585 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
588 tristate "Sun Virtual Network support"
591 Support for virtual network devices under Sun Logical Domains.
593 config NET_VENDOR_3COM
595 depends on ISA || EISA || MCA || PCI
597 If you have a network (Ethernet) card belonging to this class, say Y
598 and read the Ethernet-HOWTO, available from
599 <http://www.tldp.org/docs.html#howto>.
601 Note that the answer to this question doesn't directly affect the
602 kernel: saying N will just cause the configurator to skip all
603 the questions about 3COM cards. If you say Y, you will be asked for
604 your specific card in the following questions.
607 tristate "3c501 \"EtherLink\" support"
608 depends on NET_VENDOR_3COM && ISA
610 If you have a network (Ethernet) card of this type, say Y and read
611 the Ethernet-HOWTO, available from
612 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
613 new card, since the 3c501 is slow, broken, and obsolete: you will
614 have problems. Some people suggest to ping ("man ping") a nearby
615 machine every minute ("man cron") when using this card.
617 To compile this driver as a module, choose M here and read
618 <file:Documentation/networking/net-modules.txt>. The module
619 will be called 3c501.
622 tristate "3c503 \"EtherLink II\" support"
623 depends on NET_VENDOR_3COM && ISA
626 If you have a network (Ethernet) card of this type, say Y and read
627 the Ethernet-HOWTO, available from
628 <http://www.tldp.org/docs.html#howto>.
630 To compile this driver as a module, choose M here and read
631 <file:Documentation/networking/net-modules.txt>. The module
632 will be called 3c503.
635 tristate "3c505 \"EtherLink Plus\" support"
636 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
638 Information about this network (Ethernet) card can be found in
639 <file:Documentation/networking/3c505.txt>. If you have a card of
640 this type, say Y and read the Ethernet-HOWTO, available from
641 <http://www.tldp.org/docs.html#howto>.
643 To compile this driver as a module, choose M here and read
644 <file:Documentation/networking/net-modules.txt>. The module
645 will be called 3c505.
648 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
649 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
651 If you have a network (Ethernet) card of this type, say Y and read
652 the Ethernet-HOWTO, available from
653 <http://www.tldp.org/docs.html#howto>.
655 To compile this driver as a module, choose M here and read
656 <file:Documentation/networking/net-modules.txt>. The module
657 will be called 3c507.
660 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
661 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
663 If you have a network (Ethernet) card belonging to the 3Com
664 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
665 from <http://www.tldp.org/docs.html#howto>.
667 If your card is not working you may need to use the DOS
668 setup disk to disable Plug & Play mode, and to select the default
671 To compile this driver as a module, choose M here and read
672 <file:Documentation/networking/net-modules.txt>. The module
673 will be called 3c509.
676 tristate "3c515 ISA \"Fast EtherLink\""
677 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
679 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
680 network card, say Y and read the Ethernet-HOWTO, available from
681 <http://www.tldp.org/docs.html#howto>.
683 To compile this driver as a module, choose M here and read
684 <file:Documentation/networking/net-modules.txt>. The module
685 will be called 3c515.
688 tristate "3c523 \"EtherLink/MC\" support"
689 depends on NET_VENDOR_3COM && MCA_LEGACY
691 If you have a network (Ethernet) card of this type, say Y and read
692 the Ethernet-HOWTO, available from
693 <http://www.tldp.org/docs.html#howto>.
695 To compile this driver as a module, choose M here and read
696 <file:Documentation/networking/net-modules.txt>. 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 and read
708 <file:Documentation/networking/net-modules.txt>. The module
709 will be called 3c527.
712 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
713 depends on NET_VENDOR_3COM && (PCI || EISA)
716 This option enables driver support for a large number of 10Mbps and
717 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
719 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
720 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
721 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
722 "Tornado" (3c905) PCI
723 "Hurricane" (3c555/3cSOHO) PCI
725 If you have such a card, say Y and read the Ethernet-HOWTO,
726 available from <http://www.tldp.org/docs.html#howto>. More
727 specific information is in
728 <file:Documentation/networking/vortex.txt> and in the comments at
729 the beginning of <file:drivers/net/3c59x.c>.
731 To compile this support as a module, choose M here and read
732 <file:Documentation/networking/net-modules.txt>.
735 tristate "3cr990 series \"Typhoon\" support"
736 depends on NET_VENDOR_3COM && PCI
739 This option enables driver support for the 3cr990 series of cards:
741 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
742 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
743 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
745 If you have a network (Ethernet) card of this type, say Y and read
746 the Ethernet-HOWTO, available from
747 <http://www.tldp.org/docs.html#howto>.
749 To compile this driver as a module, choose M here and read
750 <file:Documentation/networking/net-modules.txt>. The module
751 will be called typhoon.
754 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
755 depends on ISA && ISA_DMA_API
757 If you have a network (Ethernet) card of this type, say Y and read
758 the Ethernet-HOWTO, available from
759 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
762 To compile this driver as a module, choose M here: the module
763 will be called lance. This is recommended.
765 config NET_VENDOR_SMC
766 bool "Western Digital/SMC cards"
767 depends on ISA || MCA || EISA || MAC
769 If you have a network (Ethernet) card belonging to this class, say Y
770 and read the Ethernet-HOWTO, available from
771 <http://www.tldp.org/docs.html#howto>.
773 Note that the answer to this question doesn't directly affect the
774 kernel: saying N will just cause the configurator to skip all
775 the questions about Western Digital cards. If you say Y, you will be
776 asked for your specific card in the following questions.
779 tristate "WD80*3 support"
780 depends on NET_VENDOR_SMC && ISA
783 If you have a network (Ethernet) card of this type, say Y and read
784 the Ethernet-HOWTO, available from
785 <http://www.tldp.org/docs.html#howto>.
787 To compile this driver as a module, choose M here and read
788 <file:Documentation/networking/net-modules.txt>. The module
792 tristate "SMC Ultra MCA support"
793 depends on NET_VENDOR_SMC && MCA
796 If you have a network (Ethernet) card of this type and are running
797 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
798 available from <http://www.tldp.org/docs.html#howto>.
800 To compile this driver as a module, choose M here and read
801 <file:Documentation/networking/net-modules.txt>. The module
802 will be called smc-mca.
805 tristate "SMC Ultra support"
806 depends on NET_VENDOR_SMC && ISA
809 If you have a network (Ethernet) card of this type, say Y and read
810 the Ethernet-HOWTO, available from
811 <http://www.tldp.org/docs.html#howto>.
813 Important: There have been many reports that, with some motherboards
814 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
815 such as some BusLogic models) causes corruption problems with many
816 operating systems. The Linux smc-ultra driver has a work-around for
817 this but keep it in mind if you have such a SCSI card and have
820 To compile this driver as a module, choose M here and read
821 <file:Documentation/networking/net-modules.txt>. The module
822 will be called smc-ultra.
825 tristate "SMC Ultra32 EISA support"
826 depends on NET_VENDOR_SMC && EISA
829 If you have a network (Ethernet) card of this type, say Y and read
830 the Ethernet-HOWTO, available from
831 <http://www.tldp.org/docs.html#howto>.
833 To compile this driver as a module, choose M here and read
834 <file:Documentation/networking/net-modules.txt>. The module
835 will be called smc-ultra32.
838 tristate "Blackfin 536/537 on-chip mac support"
839 depends on NET_ETHERNET && (BF537 || BF536) && (!BF537_PORT_H)
841 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
843 This is the driver for blackfin on-chip mac device. Say Y if you want it
844 compiled into the kernel. This driver is also available as a module
845 ( = code which can be inserted in and removed from the running kernel
846 whenever you want). The module will be called bfin_mac.
848 config BFIN_MAC_USE_L1
849 bool "Use L1 memory for rx/tx packets"
850 depends on BFIN_MAC && BF537
853 To get maximum network performace, you should use L1 memory as rx/tx buffers.
854 Say N here if you want to reserve L1 memory for other uses.
856 config BFIN_TX_DESC_NUM
857 int "Number of transmit buffer packets"
859 range 6 10 if BFIN_MAC_USE_L1
863 Set the number of buffer packets used in driver.
865 config BFIN_RX_DESC_NUM
866 int "Number of receive buffer packets"
868 range 20 100 if BFIN_MAC_USE_L1
872 Set the number of buffer packets used in driver.
875 bool "RMII PHY Interface (EXPERIMENTAL)"
876 depends on BFIN_MAC && EXPERIMENTAL
879 Use Reduced PHY MII Interface
882 tristate "SMC 9194 support"
883 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
886 This is support for the SMC9xxx based Ethernet cards. Choose this
887 option if you have a DELL laptop with the docking station, or
888 another SMC9192/9194 based chipset. Say Y if you want it compiled
889 into the kernel, and read the file
890 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
891 available from <http://www.tldp.org/docs.html#howto>.
893 To compile this driver as a module, choose M here and read
894 <file:Documentation/networking/net-modules.txt>. The module
895 will be called smc9194.
898 tristate "SMC 91C9x/91C1xxx support"
901 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
903 This is a driver for SMC's 91x series of Ethernet chipsets,
904 including the SMC91C94 and the SMC91C111. Say Y if you want it
905 compiled into the kernel, and read the file
906 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
907 available from <http://www.linuxdoc.org/docs.html#howto>.
909 This driver is also available as a module ( = code which can be
910 inserted in and removed from the running kernel whenever you want).
911 The module will be called smc91x. If you want to compile it as a
912 module, say M here and read <file:Documentation/kbuild/modules.txt>
913 as well as <file:Documentation/networking/net-modules.txt>.
916 tristate "NetX Ethernet support"
920 This is support for the Hilscher netX builtin Ethernet ports
922 To compile this driver as a module, choose M here and read
923 <file:Documentation/networking/net-modules.txt>. The module
924 will be called netx-eth.
927 tristate "DM9000 support"
928 depends on ARM || BLACKFIN || MIPS
932 Support for DM9000 chipset.
934 To compile this driver as a module, choose M here and read
935 <file:Documentation/networking/net-modules.txt>. The module will be
939 tristate "SMSC LAN911[5678] support"
944 This is a driver for SMSC's LAN911x series of Ethernet chipsets
945 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
946 Say Y if you want it compiled into the kernel,
947 and read the Ethernet-HOWTO, available from
948 <http://www.linuxdoc.org/docs.html#howto>.
950 This driver is also available as a module. The module will be
951 called smc911x. If you want to compile it as a module, say M
952 here and read <file:Documentation/kbuild/modules.txt>
954 config NET_VENDOR_RACAL
955 bool "Racal-Interlan (Micom) NI cards"
958 If you have a network (Ethernet) card belonging to this class, such
959 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
960 available from <http://www.tldp.org/docs.html#howto>.
962 Note that the answer to this question doesn't directly affect the
963 kernel: saying N will just cause the configurator to skip all
964 the questions about NI cards. If you say Y, you will be asked for
965 your specific card in the following questions.
968 tristate "NI5010 support (EXPERIMENTAL)"
969 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
971 If you have a network (Ethernet) card of this type, say Y and read
972 the Ethernet-HOWTO, available from
973 <http://www.tldp.org/docs.html#howto>. Note that this is still
976 To compile this driver as a module, choose M here and read
977 <file:Documentation/networking/net-modules.txt>. The module
978 will be called ni5010.
981 tristate "NI5210 support"
982 depends on NET_VENDOR_RACAL && ISA
984 If you have a network (Ethernet) card of this type, say Y and read
985 the Ethernet-HOWTO, available from
986 <http://www.tldp.org/docs.html#howto>.
988 To compile this driver as a module, choose M here and read
989 <file:Documentation/networking/net-modules.txt>. The module
993 tristate "NI6510 support"
994 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
996 If you have a network (Ethernet) card of this type, say Y and read
997 the Ethernet-HOWTO, available from
998 <http://www.tldp.org/docs.html#howto>.
1000 To compile this driver as a module, choose M here and read
1001 <file:Documentation/networking/net-modules.txt>. The module
1002 will be called ni65.
1004 source "drivers/net/tulip/Kconfig"
1007 tristate "AT1700/1720 support (EXPERIMENTAL)"
1008 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1011 If you have a network (Ethernet) card of this type, say Y and read
1012 the Ethernet-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
1015 To compile this driver as a module, choose M here and read
1016 <file:Documentation/networking/net-modules.txt>. The module
1017 will be called at1700.
1020 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1021 depends on ISA || EISA || MCA
1024 If you have a network (Ethernet) card of this type, say Y and read
1025 the Ethernet-HOWTO, available from
1026 <http://www.tldp.org/docs.html#howto> as well as
1027 <file:drivers/net/depca.c>.
1029 To compile this driver as a module, choose M here and read
1030 <file:Documentation/networking/net-modules.txt>. The module
1031 will be called depca.
1034 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1035 depends on ISA || EISA || PCI
1037 If you have a network (Ethernet) card of this type, say Y and read
1038 the Ethernet-HOWTO, available from
1039 <http://www.tldp.org/docs.html#howto>.
1041 To compile this driver as a module, choose M here and read
1042 <file:Documentation/networking/net-modules.txt>. The module
1043 will be called hp100.
1046 bool "Other ISA cards"
1049 If your network (Ethernet) card hasn't been mentioned yet and its
1050 bus system (that's the way the cards talks to the other components
1051 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1052 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1053 available from <http://www.tldp.org/docs.html#howto>.
1057 Note that the answer to this question doesn't directly affect the
1058 kernel: saying N will just cause the configurator to skip all
1059 the remaining ISA network card questions. If you say Y, you will be
1060 asked for your specific card in the following questions.
1063 tristate "Cabletron E21xx support"
1067 If you have a network (Ethernet) card of this type, say Y and read
1068 the Ethernet-HOWTO, available from
1069 <http://www.tldp.org/docs.html#howto>.
1071 To compile this driver as a module, choose M here and read
1072 <file:Documentation/networking/net-modules.txt>. The module
1073 will be called e2100.
1076 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1080 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1081 cards. If this is for you, say Y and read
1082 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1083 well as the Ethernet-HOWTO, available from
1084 <http://www.tldp.org/docs.html#howto>.
1086 To compile this driver as a module, choose M here and read
1087 <file:Documentation/networking/net-modules.txt>. The module
1088 will be called ewrk3.
1091 tristate "EtherExpress 16 support"
1094 If you have an EtherExpress16 network (Ethernet) card, say Y and
1095 read the Ethernet-HOWTO, available from
1096 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1097 EtherExpress16 card used to be regarded as a very poor choice
1098 because the driver was very unreliable. We now have a new driver
1099 that should do better.
1101 To compile this driver as a module, choose M here and read
1102 <file:Documentation/networking/net-modules.txt>. The module
1103 will be called eexpress.
1106 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1109 If you have a network (Ethernet) card of this type, say Y. This
1110 driver supports Intel i82595{FX,TX} based boards. Note however
1111 that the EtherExpress PRO/100 Ethernet card has its own separate
1112 driver. Please read the Ethernet-HOWTO, available from
1113 <http://www.tldp.org/docs.html#howto>.
1115 To compile this driver as a module, choose M here and read
1116 <file:Documentation/networking/net-modules.txt>. The module
1117 will be called eepro.
1120 tristate "HP PCLAN+ (27247B and 27252A) support"
1124 If you have a network (Ethernet) card of this type, say Y and read
1125 the Ethernet-HOWTO, available from
1126 <http://www.tldp.org/docs.html#howto>.
1128 To compile this driver as a module, choose M here and read
1129 <file:Documentation/networking/net-modules.txt>. The module
1130 will be called hp-plus.
1133 tristate "HP PCLAN (27245 and other 27xxx series) support"
1137 If you have a network (Ethernet) card of this type, say Y and read
1138 the Ethernet-HOWTO, available from
1139 <http://www.tldp.org/docs.html#howto>.
1141 To compile this driver as a module, choose M here and read
1142 <file:Documentation/networking/net-modules.txt>. The module
1146 tristate "LP486E on board Ethernet"
1149 Say Y here to support the 82596-based on-board Ethernet controller
1150 for the Panther motherboard, which is one of the two shipped in the
1151 Intel Professional Workstation.
1154 tristate "ICL EtherTeam 16i/32 support"
1157 If you have a network (Ethernet) card of this type, say Y and read
1158 the Ethernet-HOWTO, available from
1159 <http://www.tldp.org/docs.html#howto>.
1161 To compile this driver as a module, choose M here and read
1162 <file:Documentation/networking/net-modules.txt>. The module
1163 will be called eth16i.
1166 tristate "NE2000/NE1000 support"
1167 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1170 If you have a network (Ethernet) card of this type, say Y and read
1171 the Ethernet-HOWTO, available from
1172 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1173 without a specific driver are compatible with NE2000.
1175 If you have a PCI NE2000 card however, say N here and Y to "PCI
1176 NE2000 and clone support" under "EISA, VLB, PCI and on board
1177 controllers" below. If you have a NE2000 card and are running on
1178 an MCA system (a bus system used on some IBM PS/2 computers and
1179 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1182 To compile this driver as a module, choose M here and read
1183 <file:Documentation/networking/net-modules.txt>. The module
1187 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1188 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1190 The Zenith Z-Note notebook computer has a built-in network
1191 (Ethernet) card, and this is the Linux driver for it. Note that the
1192 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1193 by this driver. Read the Ethernet-HOWTO, available from
1194 <http://www.tldp.org/docs.html#howto>.
1197 tristate "SEEQ8005 support (EXPERIMENTAL)"
1198 depends on NET_ISA && EXPERIMENTAL
1200 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1201 is for you, read the Ethernet-HOWTO, available from
1202 <http://www.tldp.org/docs.html#howto>.
1204 To compile this driver as a module, choose M here and read
1205 <file:Documentation/networking/net-modules.txt>. The module
1206 will be called seeq8005.
1209 tristate "NE/2 (ne2000 MCA version) support"
1210 depends on MCA_LEGACY
1213 If you have a network (Ethernet) card of this type, say Y and read
1214 the Ethernet-HOWTO, available from
1215 <http://www.tldp.org/docs.html#howto>.
1217 To compile this driver as a module, choose M here and read
1218 <file:Documentation/networking/net-modules.txt>. The module
1222 tristate "IBM LAN Adapter/A support"
1223 depends on MCA && MCA_LEGACY
1225 This is a Micro Channel Ethernet adapter. You need to set
1226 CONFIG_MCA to use this driver. It is both available as an in-kernel
1227 driver and as a module.
1229 To compile this driver as a module, choose M here and read
1230 <file:Documentation/networking/net-modules.txt>. The only
1231 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1232 will both support 16K and 32K memory windows, however a 32K window
1233 gives a better security against packet losses. Usage of multiple
1234 boards with this driver should be possible, but has not been tested
1235 up to now due to lack of hardware.
1238 tristate "IBM LAN Virtual Ethernet support"
1239 depends on PPC_PSERIES
1241 This driver supports virtual ethernet adapters on newer IBM iSeries
1242 and pSeries systems.
1244 To compile this driver as a module, choose M here and read
1245 <file:Documentation/networking/net-modules.txt>. The module will
1249 tristate "PowerPC 4xx on-chip Ethernet support"
1250 depends on 4xx && !PPC_MERGE
1252 This driver supports the PowerPC 4xx EMAC family of on-chip
1253 Ethernet controllers.
1256 int "Number of receive buffers"
1261 int "Number of transmit buffers"
1265 config IBM_EMAC_POLL_WEIGHT
1266 int "MAL NAPI polling weight"
1270 config IBM_EMAC_RX_COPY_THRESHOLD
1271 int "RX skb copy threshold (bytes)"
1275 config IBM_EMAC_RX_SKB_HEADROOM
1276 int "Additional RX skb headroom (bytes)"
1280 Additional receive skb headroom. Note, that driver
1281 will always reserve at least 2 bytes to make IP header
1282 aligned, so usually there is no need to add any additional
1285 If unsure, set to 0.
1287 config IBM_EMAC_PHY_RX_CLK_FIX
1288 bool "PHY Rx clock workaround"
1289 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1291 Enable this if EMAC attached to a PHY which doesn't generate
1292 RX clock if there is no link, if this is the case, you will
1293 see "TX disable timeout" or "RX disable timeout" in the system
1298 config IBM_EMAC_DEBUG
1303 config IBM_EMAC_ZMII
1305 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1308 config IBM_EMAC_RGMII
1310 depends on IBM_EMAC && 440GX
1315 depends on IBM_EMAC && 440GX
1319 bool "EISA, VLB, PCI and on board controllers"
1320 depends on ISA || EISA || PCI
1322 This is another class of network cards which attach directly to the
1323 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1324 available from <http://www.tldp.org/docs.html#howto>.
1326 Note that the answer to this question doesn't directly affect the
1327 kernel: saying N will just cause the configurator to skip all
1328 the questions about this class of network cards. If you say Y, you
1329 will be asked for your specific card in the following questions. If
1330 you are unsure, say Y.
1333 tristate "AMD PCnet32 PCI support"
1334 depends on NET_PCI && PCI
1338 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1339 answer Y here and read the Ethernet-HOWTO, available from
1340 <http://www.tldp.org/docs.html#howto>.
1342 To compile this driver as a module, choose M here and read
1343 <file:Documentation/networking/net-modules.txt>. The module
1344 will be called pcnet32.
1347 bool "Use RX polling (NAPI)"
1350 NAPI is a new driver API designed to reduce CPU and interrupt load
1351 when the driver is receiving lots of packets from the card. It is
1352 still somewhat experimental and thus not yet enabled by default.
1354 If your estimated Rx load is 10kpps or more, or if the card will be
1355 deployed on potentially unfriendly networks (e.g. in a firewall),
1358 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1364 tristate "AMD 8111 (new PCI lance) support"
1365 depends on NET_PCI && PCI
1369 If you have an AMD 8111-based PCI lance ethernet card,
1370 answer Y here and read the Ethernet-HOWTO, available from
1371 <http://www.tldp.org/docs.html#howto>.
1373 To compile this driver as a module, choose M here and read
1374 <file:Documentation/networking/net-modules.txt>. The module
1375 will be called amd8111e.
1377 config AMD8111E_NAPI
1378 bool "Enable NAPI support"
1379 depends on AMD8111_ETH
1381 NAPI is a new driver API designed to reduce CPU and interrupt load
1382 when the driver is receiving lots of packets from the card. It is
1383 still somewhat experimental and thus not yet enabled by default.
1385 If your estimated Rx load is 10kpps or more, or if the card will be
1386 deployed on potentially unfriendly networks (e.g. in a firewall),
1389 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1394 config ADAPTEC_STARFIRE
1395 tristate "Adaptec Starfire/DuraLAN support"
1396 depends on NET_PCI && PCI
1400 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1401 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1402 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1405 To compile this driver as a module, choose M here: the module
1406 will be called starfire. This is recommended.
1408 config ADAPTEC_STARFIRE_NAPI
1409 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1410 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1412 NAPI is a new driver API designed to reduce CPU and interrupt load
1413 when the driver is receiving lots of packets from the card. It is
1414 still somewhat experimental and thus not yet enabled by default.
1416 If your estimated Rx load is 10kpps or more, or if the card will be
1417 deployed on potentially unfriendly networks (e.g. in a firewall),
1420 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1426 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1427 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1430 If you have a network (Ethernet) card of this type, say Y and read
1431 the Ethernet-HOWTO, available from
1432 <http://www.tldp.org/docs.html#howto>.
1434 To compile this driver as a module, choose M here and read
1435 <file:Documentation/networking/net-modules.txt>. The module
1436 will be called ac3200.
1439 tristate "Apricot Xen-II on board Ethernet"
1440 depends on NET_PCI && ISA
1442 If you have a network (Ethernet) controller of this type, say Y and
1443 read the Ethernet-HOWTO, available from
1444 <http://www.tldp.org/docs.html#howto>.
1446 To compile this driver as a module, choose M here and read
1447 <file:Documentation/networking/net-modules.txt>. The module will be
1451 tristate "Broadcom 440x/47xx ethernet support"
1452 depends on SSB_POSSIBLE
1456 If you have a network (Ethernet) controller of this type, say Y
1457 or M and read the Ethernet-HOWTO, available from
1458 <http://www.tldp.org/docs.html#howto>.
1460 To compile this driver as a module, choose M here and read
1461 <file:Documentation/networking/net-modules.txt>. The module will be
1464 # Auto-select SSB PCI-HOST support, if possible
1465 config B44_PCI_AUTOSELECT
1467 depends on B44 && SSB_PCIHOST_POSSIBLE
1471 # Auto-select SSB PCICORE driver, if possible
1472 config B44_PCICORE_AUTOSELECT
1474 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1475 select SSB_DRIVER_PCICORE
1480 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1484 tristate "nForce Ethernet support"
1485 depends on NET_PCI && PCI
1487 If you have a network (Ethernet) controller of this type, say Y and
1488 read the Ethernet-HOWTO, available from
1489 <http://www.tldp.org/docs.html#howto>.
1491 To compile this driver as a module, choose M here and read
1492 <file:Documentation/networking/net-modules.txt>. The module will be
1495 config FORCEDETH_NAPI
1496 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1497 depends on FORCEDETH && EXPERIMENTAL
1499 NAPI is a new driver API designed to reduce CPU and interrupt load
1500 when the driver is receiving lots of packets from the card. It is
1501 still somewhat experimental and thus not yet enabled by default.
1503 If your estimated Rx load is 10kpps or more, or if the card will be
1504 deployed on potentially unfriendly networks (e.g. in a firewall),
1507 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1513 tristate "CS89x0 support"
1514 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1516 Support for CS89x0 chipset based Ethernet cards. If you have a
1517 network (Ethernet) card of this type, say Y and read the
1518 Ethernet-HOWTO, available from
1519 <http://www.tldp.org/docs.html#howto> as well as
1520 <file:Documentation/networking/cs89x0.txt>.
1522 To compile this driver as a module, choose M here and read
1523 <file:Documentation/networking/net-modules.txt>. The module will be
1527 tristate "TOSHIBA TC35815 Ethernet support"
1528 depends on NET_PCI && PCI && MIPS
1532 tristate "Digi Intl. RightSwitch SE-X support"
1533 depends on NET_PCI && (PCI || EISA)
1535 This is support for the Digi International RightSwitch series of
1536 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1537 models. If you have a network card of this type, say Y and read the
1538 Ethernet-HOWTO, available from
1539 <http://www.tldp.org/docs.html#howto>. More specific
1540 information is contained in <file:Documentation/networking/dgrs.txt>.
1542 To compile this driver as a module, choose M here and read
1543 <file:Documentation/networking/net-modules.txt>. The module
1544 will be called dgrs.
1547 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1548 depends on NET_PCI && PCI
1551 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1552 card, say Y and read the Ethernet-HOWTO, available from
1553 <http://www.tldp.org/docs.html#howto>.
1555 To compile this driver as a module, choose M here and read
1556 <file:Documentation/networking/net-modules.txt>. The module
1557 will be called eepro100.
1561 tristate "Intel(R) PRO/100+ support"
1562 depends on NET_PCI && PCI
1565 This driver supports Intel(R) PRO/100 family of adapters.
1566 To verify that your adapter is supported, find the board ID number
1567 on the adapter. Look for a label that has a barcode and a number
1568 in the format 123456-001 (six digits hyphen three digits).
1570 Use the above information and the Adapter & Driver ID Guide at:
1572 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1574 to identify the adapter.
1576 For the latest Intel PRO/100 network driver for Linux, see:
1578 <http://appsr.intel.com/scripts-df/support_intel.asp>
1580 More specific information on configuring the driver is in
1581 <file:Documentation/networking/e100.txt>.
1583 To compile this driver as a module, choose M here and read
1584 <file:Documentation/networking/net-modules.txt>. The module
1585 will be called e100.
1588 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1589 depends on NET_PCI && EISA && EXPERIMENTAL
1592 If you have a network (Ethernet) card of this type, say Y and read
1593 the Ethernet-HOWTO, available from
1594 <http://www.tldp.org/docs.html#howto>.
1596 To compile this driver as a module, choose M here and read
1597 <file:Documentation/networking/net-modules.txt>. The module
1598 will be called lne390.
1601 tristate "Myson MTD-8xx PCI Ethernet support"
1602 depends on NET_PCI && PCI
1606 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1607 cards. Specifications and data at
1608 <http://www.myson.com.hk/mtd/datasheet/>.
1611 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1612 depends on NET_PCI && PCI
1615 This driver is for the National Semiconductor DP83810 series,
1616 which is used in cards from PureData, NetGear, Linksys
1617 and others, including the 83815 chip.
1618 More specific information and updates are available from
1619 <http://www.scyld.com/network/natsemi.html>.
1622 tristate "PCI NE2000 and clones support (see help)"
1623 depends on NET_PCI && PCI
1626 This driver is for NE2000 compatible PCI cards. It will not work
1627 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1628 support" below). If you have a PCI NE2000 network (Ethernet) card,
1629 say Y and read the Ethernet-HOWTO, available from
1630 <http://www.tldp.org/docs.html#howto>.
1632 This driver also works for the following NE2000 clone cards:
1633 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1634 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1635 Holtek HT80232 Holtek HT80229
1637 To compile this driver as a module, choose M here and read
1638 <file:Documentation/networking/net-modules.txt>. The module
1639 will be called ne2k-pci.
1642 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1643 depends on NET_PCI && EISA && EXPERIMENTAL
1646 If you have a network (Ethernet) card of this type, say Y and read
1647 the Ethernet-HOWTO, available from
1648 <http://www.tldp.org/docs.html#howto>. Note that this driver
1649 will NOT WORK for NE3200 cards as they are completely different.
1651 To compile this driver as a module, choose M here and read
1652 <file:Documentation/networking/net-modules.txt>. The module
1653 will be called ne3210.
1656 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1657 depends on NET_PCI && EISA && EXPERIMENTAL
1660 If you have a network (Ethernet) card of this type, say Y and read
1661 the Ethernet-HOWTO, available from
1662 <http://www.tldp.org/docs.html#howto>.
1664 To compile this driver as a module, choose M here and read
1665 <file:Documentation/networking/net-modules.txt>. The module
1666 will be called es3210.
1669 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1670 depends on NET_PCI && PCI && EXPERIMENTAL
1674 This is a driver for the Fast Ethernet PCI network cards based on
1675 the RTL8139C+ chips. If you have one of those, say Y and read
1676 the Ethernet-HOWTO, available from
1677 <http://www.tldp.org/docs.html#howto>.
1679 To compile this driver as a module, choose M here: the module
1680 will be called 8139cp. This is recommended.
1683 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1684 depends on NET_PCI && PCI
1688 This is a driver for the Fast Ethernet PCI network cards based on
1689 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1690 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1692 To compile this driver as a module, choose M here: the module
1693 will be called 8139too. This is recommended.
1696 bool "Use PIO instead of MMIO"
1700 This instructs the driver to use programmed I/O ports (PIO) instead
1701 of PCI shared memory (MMIO). This can possibly solve some problems
1702 in case your mainboard has memory consistency issues. If unsure,
1705 config 8139TOO_TUNE_TWISTER
1706 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1709 This implements a function which might come in handy in case you
1710 are using low quality on long cabling. It is required for RealTek
1711 RTL-8139 revision K boards, and totally unused otherwise. It tries
1712 to match the transceiver to the cable characteristics. This is
1713 experimental since hardly documented by the manufacturer.
1717 bool "Support for older RTL-8129/8130 boards"
1720 This enables support for the older and uncommon RTL-8129 and
1721 RTL-8130 chips, which support MII via an external transceiver,
1722 instead of an internal one. Disabling this option will save some
1723 memory by making the code size smaller. If unsure, say Y.
1725 config 8139_OLD_RX_RESET
1726 bool "Use older RX-reset method"
1729 The 8139too driver was recently updated to contain a more rapid
1730 reset sequence, in the face of severe receive errors. This "new"
1731 RX-reset method should be adequate for all boards. But if you
1732 experience problems, you can enable this option to restore the
1733 old RX-reset behavior. If unsure, say N.
1736 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1737 depends on NET_PCI && PCI
1741 This is a driver for the Fast Ethernet PCI network cards based on
1742 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1743 SiS 630 and SiS 540 chipsets.
1745 This driver also supports AMD 79C901 HomePNA so that you can use
1746 your phone line as a network cable.
1748 To compile this driver as a module, choose M here: the module
1749 will be called sis900. This is recommended.
1752 tristate "SMC EtherPower II"
1753 depends on NET_PCI && PCI
1757 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1758 which is based on the SMC83c17x (EPIC/100).
1759 More specific information and updates are available from
1760 <http://www.scyld.com/network/epic100.html>.
1763 tristate "Sundance Alta support"
1764 depends on NET_PCI && PCI
1768 This driver is for the Sundance "Alta" chip.
1769 More specific information and updates are available from
1770 <http://www.scyld.com/network/sundance.html>.
1772 config SUNDANCE_MMIO
1773 bool "Use MMIO instead of PIO"
1776 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1777 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1778 is known to solve bugs on certain chips.
1783 tristate "TI ThunderLAN support"
1784 depends on NET_PCI && (PCI || EISA) && !64BIT
1786 If you have a PCI Ethernet network card based on the ThunderLAN chip
1787 which is supported by this driver, say Y and read the
1788 Ethernet-HOWTO, available from
1789 <http://www.tldp.org/docs.html#howto>.
1791 Devices currently supported by this driver are Compaq Netelligent,
1792 Compaq NetFlex and Olicom cards. Please read the file
1793 <file:Documentation/networking/tlan.txt> for more details.
1795 To compile this driver as a module, choose M here and read
1796 <file:Documentation/networking/net-modules.txt>. The module
1797 will be called tlan.
1799 Please email feedback to <torben.mathiasen@compaq.com>.
1802 tristate "VIA Rhine support"
1803 depends on NET_PCI && PCI
1807 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1808 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1809 Ethernet functions can also be found integrated on South Bridges
1812 To compile this driver as a module, choose M here. The module
1813 will be called via-rhine.
1815 config VIA_RHINE_MMIO
1816 bool "Use MMIO instead of PIO"
1817 depends on VIA_RHINE
1819 This instructs the driver to use PCI shared memory (MMIO) instead of
1820 programmed I/O ports (PIO). Enabling this gives an improvement in
1821 processing time in parts of the driver.
1825 config VIA_RHINE_NAPI
1826 bool "Use Rx Polling (NAPI)"
1827 depends on VIA_RHINE
1829 NAPI is a new driver API designed to reduce CPU and interrupt load
1830 when the driver is receiving lots of packets from the card.
1832 If your estimated Rx load is 10kpps or more, or if the card will be
1833 deployed on potentially unfriendly networks (e.g. in a firewall),
1836 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1840 bool "Philips SAA9730 Ethernet support"
1841 depends on NET_PCI && PCI && MIPS_ATLAS
1843 The SAA9730 is a combined multimedia and peripheral controller used
1844 in thin clients, Internet access terminals, and diskless
1846 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1849 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1850 depends on NET_PCI && PCI && EXPERIMENTAL
1853 This is a driver for the Fast Ethernet PCI network cards based on
1854 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1855 have one of these, say Y here.
1857 To compile this driver as a module, choose M here: the module
1858 will be called sc92031. This is recommended.
1861 bool "Pocket and portable adapters"
1864 Cute little network (Ethernet) devices which attach to the parallel
1865 port ("pocket adapters"), commonly used with laptops. If you have
1866 one of those, say Y and read the Ethernet-HOWTO, available from
1867 <http://www.tldp.org/docs.html#howto>.
1869 If you want to plug a network (or some other) card into the PCMCIA
1870 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1871 credit card size extension cards used by all modern laptops), you
1872 need the pcmcia-cs package (location contained in the file
1873 <file:Documentation/Changes>) and you can say N here.
1875 Laptop users should read the Linux Laptop home page at
1876 <http://www.linux-on-laptops.com/> or
1877 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1879 Note that the answer to this question doesn't directly affect the
1880 kernel: saying N will just cause the configurator to skip all
1881 the questions about this class of network devices. If you say Y, you
1882 will be asked for your specific device in the following questions.
1885 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1886 depends on NET_POCKET && PARPORT && X86
1889 This is a network (Ethernet) device which attaches to your parallel
1890 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1891 available from <http://www.tldp.org/docs.html#howto>, if you
1892 want to use this. If you intend to use this driver, you should have
1893 said N to the "Parallel printer support", because the two drivers
1894 don't like each other.
1896 To compile this driver as a module, choose M here: the module
1900 tristate "D-Link DE600 pocket adapter support"
1901 depends on NET_POCKET && PARPORT
1903 This is a network (Ethernet) device which attaches to your parallel
1904 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1905 Ethernet-HOWTO, available from
1906 <http://www.tldp.org/docs.html#howto>, if you want to use
1907 this. It is possible to have several devices share a single parallel
1908 port and it is safe to compile the corresponding drivers into the
1911 To compile this driver as a module, choose M here: the module
1912 will be called de600.
1915 tristate "D-Link DE620 pocket adapter support"
1916 depends on NET_POCKET && PARPORT
1918 This is a network (Ethernet) device which attaches to your parallel
1919 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1920 Ethernet-HOWTO, available from
1921 <http://www.tldp.org/docs.html#howto>, if you want to use
1922 this. It is possible to have several devices share a single parallel
1923 port and it is safe to compile the corresponding drivers into the
1926 To compile this driver as a module, choose M here: the module
1927 will be called de620.
1930 tristate "SGI Seeq ethernet controller support"
1933 Say Y here if you have an Seeq based Ethernet network card. This is
1934 used in many Silicon Graphics machines.
1937 tristate "DEC LANCE ethernet controller support"
1938 depends on MACH_DECSTATION
1941 This driver is for the series of Ethernet controllers produced by
1942 DEC (now Compaq) based on the AMD Lance chipset, including the
1943 DEPCA series. (This chipset is better known via the NE2100 cards.)
1946 bool "Motorola 68360 ethernet controller"
1949 Say Y here if you want to use the built-in ethernet controller of
1950 the Motorola 68360 processor.
1953 bool "FEC ethernet controller (of ColdFire CPUs)"
1954 depends on M523x || M527x || M5272 || M528x || M520x
1956 Say Y here if you want to use the built-in 10/100 Fast ethernet
1957 controller on some Motorola ColdFire processors.
1960 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1963 Say Y here if you want to use the second built-in 10/100 Fast
1964 ethernet controller on some Motorola ColdFire processors.
1967 tristate "NE2000 compatible support for H8/300"
1970 Say Y here if you want to use the NE2000 compatible
1971 controller on the Renesas H8/300 processor.
1973 source "drivers/net/fec_8xx/Kconfig"
1974 source "drivers/net/fs_enet/Kconfig"
1976 endif # NET_ETHERNET
1982 menuconfig NETDEV_1000
1983 bool "Ethernet (1000 Mbit)"
1987 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1988 type of Local Area Network (LAN) in universities and companies.
1990 Say Y here to get to see options for Gigabit Ethernet drivers.
1991 This option alone does not add any kernel code.
1992 Note that drivers supporting both 100 and 1000 MBit may be listed
1993 under "Ethernet (10 or 100MBit)" instead.
1995 If you say N, all options in this submenu will be skipped and disabled.
2000 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2003 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2004 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2005 adapter. The driver allows for using the Jumbo Frame option (9000
2006 bytes/frame) however it requires that your switches can handle this
2007 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2010 To compile this driver as a module, choose M here: the
2011 module will be called acenic.
2013 config ACENIC_OMIT_TIGON_I
2014 bool "Omit support for old Tigon I based AceNICs"
2017 Say Y here if you only have Tigon II based AceNICs and want to leave
2018 out support for the older Tigon I based cards which are no longer
2019 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2020 version)). This will reduce the size of the driver object by
2021 app. 100KB. If you are not sure whether your card is a Tigon I or a
2022 Tigon II, say N here.
2024 The safe and default value for this is N.
2027 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2031 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2033 D-Link DGE-550T Gigabit Ethernet Adapter.
2034 D-Link DL2000-based Gigabit Ethernet Adapter.
2035 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2037 To compile this driver as a module, choose M here: the
2038 module will be called dl2k.
2041 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2044 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2045 adapters. For more information on how to identify your adapter, go
2046 to the Adapter & Driver ID Guide at:
2048 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2050 For general information and support, go to the Intel support
2053 <http://support.intel.com>
2055 More specific information on configuring the driver is in
2056 <file:Documentation/networking/e1000.txt>.
2058 To compile this driver as a module, choose M here and read
2059 <file:Documentation/networking/net-modules.txt>. The module
2060 will be called e1000.
2063 bool "Use Rx Polling (NAPI)"
2066 NAPI is a new driver API designed to reduce CPU and interrupt load
2067 when the driver is receiving lots of packets from the card. It is
2068 still somewhat experimental and thus not yet enabled by default.
2070 If your estimated Rx load is 10kpps or more, or if the card will be
2071 deployed on potentially unfriendly networks (e.g. in a firewall),
2074 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2079 config E1000_DISABLE_PACKET_SPLIT
2080 bool "Disable Packet Split for PCI express adapters"
2083 Say Y here if you want to use the legacy receive path for PCI express
2089 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2092 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2093 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2094 use the regular e1000 driver For more information on how to
2095 identify your adapter, go to the Adapter & Driver ID Guide at:
2097 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2099 For general information and support, go to the Intel support
2102 <http://support.intel.com>
2104 More specific information on configuring the driver is in
2105 <file:Documentation/networking/e1000e.txt>.
2107 To compile this driver as a module, choose M here and read
2108 <file:Documentation/networking/net-modules.txt>. The module
2109 will be called e1000e.
2111 source "drivers/net/ixp2000/Kconfig"
2114 tristate "MyriCOM Gigabit Ethernet support"
2117 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2119 To compile this driver as a module, choose M here: the module
2120 will be called myri_sbus. This is recommended.
2123 tristate "National Semiconductor DP83820 support"
2126 This is a driver for the National Semiconductor DP83820 series
2127 of gigabit ethernet MACs. Cards using this chipset include
2128 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2129 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2133 tristate "Packet Engines Hamachi GNIC-II support"
2137 If you have a Gigabit Ethernet card of this type, say Y and read
2138 the Ethernet-HOWTO, available from
2139 <http://www.tldp.org/docs.html#howto>.
2141 To compile this driver as a module, choose M here and read
2142 <file:Documentation/networking/net-modules.txt>. The module will be
2146 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2147 depends on PCI && EXPERIMENTAL
2150 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2151 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2152 used by the Beowulf Linux cluster project. See
2153 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2154 information about this driver in particular and Beowulf in general.
2156 To compile this driver as a module, choose M here: the module
2157 will be called yellowfin. This is recommended.
2160 tristate "Realtek 8169 gigabit ethernet support"
2164 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2166 To compile this driver as a module, choose M here: the module
2167 will be called r8169. This is recommended.
2170 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2171 depends on R8169 && EXPERIMENTAL
2173 NAPI is a new driver API designed to reduce CPU and interrupt load
2174 when the driver is receiving lots of packets from the card. It is
2175 still somewhat experimental and thus not yet enabled by default.
2177 If your estimated Rx load is 10kpps or more, or if the card will be
2178 deployed on potentially unfriendly networks (e.g. in a firewall),
2181 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2188 depends on R8169 && VLAN_8021Q
2190 Say Y here for the r8169 driver to support the functions required
2191 by the kernel 802.1Q code.
2196 tristate "SiS190/SiS191 gigabit ethernet support"
2201 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2202 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2203 appear in lan on motherboard designs which are based on SiS 965
2204 and SiS 966 south bridge.
2206 To compile this driver as a module, choose M here: the module
2207 will be called sis190. This is recommended.
2210 tristate "New SysKonnect GigaEthernet support"
2214 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2215 and related Gigabit Ethernet adapters. It is a new smaller driver
2216 with better performance and more complete ethtool support.
2218 It does not support the link failover and network management
2219 features that "portable" vendor supplied sk98lin driver does.
2221 This driver supports adapters based on the original Yukon chipset:
2222 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2223 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2225 It does not support the newer Yukon2 chipset: a separate driver,
2226 sky2, is provided for Yukon2-based adapters.
2228 To compile this driver as a module, choose M here: the module
2229 will be called skge. This is recommended.
2232 tristate "SysKonnect Yukon2 support"
2236 This driver supports Gigabit Ethernet adapters based on the
2237 Marvell Yukon 2 chipset:
2238 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2239 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2241 There is companion driver for the older Marvell Yukon and
2242 Genesis based adapters: skge.
2244 To compile this driver as a module, choose M here: the module
2245 will be called sky2. This is recommended.
2248 bool "Debugging interface"
2249 depends on SKY2 && DEBUG_FS
2251 This option adds the ability to dump driver state for debugging.
2252 The file debugfs/sky2/ethX displays the state of the internal
2253 transmit and receive rings.
2258 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2261 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2262 compliant Gigabit Ethernet Adapter.
2264 This driver supports the original Yukon chipset. This driver is
2265 deprecated and will be removed from the kernel in the near future,
2266 it has been replaced by the skge driver. skge is cleaner and
2267 seems to work better.
2269 This driver does not support the newer Yukon2 chipset. A separate
2270 driver, sky2, is provided to support Yukon2-based adapters.
2272 The following adapters are supported by this driver:
2273 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2274 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2275 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2276 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2277 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2278 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2279 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2280 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2281 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2282 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2283 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2284 - EG1032 v2 Instant Gigabit Network Adapter
2285 - EG1064 v2 Instant Gigabit Network Adapter
2286 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2287 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2288 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2289 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2290 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2291 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2292 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2293 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2294 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2295 - Marvell RDK-8001 Adapter
2296 - Marvell RDK-8002 Adapter
2297 - Marvell RDK-8003 Adapter
2298 - Marvell RDK-8004 Adapter
2299 - Marvell RDK-8006 Adapter
2300 - Marvell RDK-8007 Adapter
2301 - Marvell RDK-8008 Adapter
2302 - Marvell RDK-8009 Adapter
2303 - Marvell RDK-8010 Adapter
2304 - Marvell RDK-8011 Adapter
2305 - Marvell RDK-8012 Adapter
2306 - Marvell RDK-8052 Adapter
2307 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2308 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2309 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2310 - SK-9521 10/100/1000Base-T Adapter
2311 - SK-9521 V2.0 10/100/1000Base-T Adapter
2312 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2313 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2314 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2315 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2316 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2317 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2318 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2319 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2320 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2321 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2322 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2323 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2324 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2325 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2326 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2327 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2328 - SMC EZ Card 1000 (SMC9452TXV.2)
2330 The adapters support Jumbo Frames.
2331 The dual link adapters support link-failover and dual port features.
2332 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2333 the scatter-gather functionality with sendfile(). Please refer to
2334 <file:Documentation/networking/sk98lin.txt> for more information about
2335 optional driver parameters.
2336 Questions concerning this driver may be addressed to:
2337 <linux@syskonnect.de>
2339 If you want to compile this driver as a module ( = code which can be
2340 inserted in and removed from the running kernel whenever you want),
2341 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2342 be called sk98lin. This is recommended.
2345 tristate "VIA Velocity support"
2351 If you have a VIA "Velocity" based network card say Y here.
2353 To compile this driver as a module, choose M here. The module
2354 will be called via-velocity.
2357 tristate "Broadcom Tigon3 support"
2360 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2362 To compile this driver as a module, choose M here: the module
2363 will be called tg3. This is recommended.
2366 tristate "Broadcom NetXtremeII support"
2371 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2373 To compile this driver as a module, choose M here: the module
2374 will be called bnx2. This is recommended.
2377 tristate "Spider Gigabit Ethernet driver"
2378 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2381 This driver supports the Gigabit Ethernet chips present on the
2382 Cell Processor-Based Blades from IBM.
2385 tristate "Tundra TSI108 gigabit Ethernet support"
2386 depends on TSI108_BRIDGE
2388 This driver supports Tundra TSI108 gigabit Ethernet ports.
2389 To compile this driver as a module, choose M here: the module
2390 will be called tsi108_eth.
2393 tristate "PS3 Gigabit Ethernet driver"
2396 This driver supports the network device on the PS3 game
2397 console. This driver has built-in support for Ethernet.
2399 To compile this driver as a module, choose M here: the
2400 module will be called ps3_gelic.
2403 tristate "Gianfar Ethernet"
2404 depends on 85xx || 83xx || PPC_86xx
2408 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2409 and MPC86xx family of chips, and the FEC on the 8540.
2416 tristate "Freescale QE Gigabit Ethernet"
2417 depends on QUICC_ENGINE
2420 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2421 which is available on some Freescale SOCs.
2427 config UGETH_MAGIC_PACKET
2428 bool "Magic Packet detection support"
2431 config UGETH_FILTERING
2432 bool "Mac address filtering support"
2435 config UGETH_TX_ON_DEMAND
2436 bool "Transmit on Demand support"
2440 tristate "MV-643XX Ethernet support"
2441 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32)
2444 This driver supports the gigabit Ethernet on the Marvell MV643XX
2445 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2446 Pegasos II, amongst other PPC and MIPS boards.
2449 tristate "QLogic QLA3XXX Network Driver Support"
2452 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2454 To compile this driver as a module, choose M here: the module
2455 will be called qla3xxx.
2458 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2459 depends on PCI && EXPERIMENTAL
2463 This driver supports the Attansic L1 gigabit ethernet adapter.
2465 To compile this driver as a module, choose M here. The module
2466 will be called atl1.
2471 # 10 Gigabit Ethernet
2474 menuconfig NETDEV_10000
2475 bool "Ethernet (10000 Mbit)"
2479 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2480 This option alone does not add any kernel code.
2482 If you say N, all options in this submenu will be skipped and disabled.
2487 tristate "Chelsio 10Gb Ethernet support"
2491 This driver supports Chelsio gigabit and 10-gigabit
2492 Ethernet cards. More information about adapter features and
2493 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2495 For general information about Chelsio and our products, visit
2496 our website at <http://www.chelsio.com>.
2498 For customer support, please visit our customer support page at
2499 <http://www.chelsio.com/support.htm>.
2501 Please send feedback to <linux-bugs@chelsio.com>.
2503 To compile this driver as a module, choose M here: the module
2504 will be called cxgb.
2506 config CHELSIO_T1_1G
2507 bool "Chelsio gigabit Ethernet support"
2508 depends on CHELSIO_T1
2510 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2511 are using only 10G cards say 'N' here.
2513 config CHELSIO_T1_NAPI
2514 bool "Use Rx Polling (NAPI)"
2515 depends on CHELSIO_T1
2518 NAPI is a driver API designed to reduce CPU and interrupt load
2519 when the driver is receiving lots of packets from the card.
2522 tristate "Chelsio Communications T3 10Gb Ethernet support"
2526 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2529 For general information about Chelsio and our products, visit
2530 our website at <http://www.chelsio.com>.
2532 For customer support, please visit our customer support page at
2533 <http://www.chelsio.com/support.htm>.
2535 Please send feedback to <linux-bugs@chelsio.com>.
2537 To compile this driver as a module, choose M here: the module
2538 will be called cxgb3.
2541 tristate "eHEA Ethernet support"
2545 This driver supports the IBM pSeries eHEA ethernet adapter.
2547 To compile the driver as a module, choose M here. The module
2548 will be called ehea.
2551 tristate "Intel(R) 10GbE PCI Express adapters support"
2554 This driver supports Intel(R) 10GbE PCI Express family of
2555 adapters. For more information on how to identify your adapter, go
2556 to the Adapter & Driver ID Guide at:
2558 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2560 For general information and support, go to the Intel support
2563 <http://support.intel.com>
2565 More specific information on configuring the driver is in
2566 <file:Documentation/networking/ixgbe.txt>.
2568 To compile this driver as a module, choose M here and read
2569 <file:Documentation/networking/net-modules.txt>. The module
2570 will be called ixgbe.
2573 tristate "Intel(R) PRO/10GbE support"
2576 This driver supports Intel(R) PRO/10GbE family of adapters for
2577 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2578 instead. For more information on how to identify your adapter, go
2579 to the Adapter & Driver ID Guide at:
2581 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2583 For general information and support, go to the Intel support
2586 <http://support.intel.com>
2588 More specific information on configuring the driver is in
2589 <file:Documentation/networking/ixgb.txt>.
2591 To compile this driver as a module, choose M here and read
2592 <file:Documentation/networking/net-modules.txt>. The module
2593 will be called ixgb.
2596 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2597 depends on IXGB && EXPERIMENTAL
2599 NAPI is a new driver API designed to reduce CPU and interrupt load
2600 when the driver is receiving lots of packets from the card. It is
2601 still somewhat experimental and thus not yet enabled by default.
2603 If your estimated Rx load is 10kpps or more, or if the card will be
2604 deployed on potentially unfriendly networks (e.g. in a firewall),
2607 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2613 tristate "S2IO 10Gbe XFrame NIC"
2616 This driver supports the 10Gbe XFrame NIC of S2IO.
2617 More specific information on configuring the driver is in
2618 <file:Documentation/networking/s2io.txt>.
2621 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2622 depends on S2IO && EXPERIMENTAL
2624 NAPI is a new driver API designed to reduce CPU and interrupt load
2625 when the driver is receiving lots of packets from the card. It is
2626 still somewhat experimental and thus not yet enabled by default.
2628 If your estimated Rx load is 10kpps or more, or if the card will be
2629 deployed on potentially unfriendly networks (e.g. in a firewall),
2632 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2638 tristate "Myricom Myri-10G Ethernet support"
2644 This driver supports Myricom Myri-10G Dual Protocol interface in
2645 Ethernet mode. If the eeprom on your board is not recent enough,
2646 you will need a newer firmware image.
2647 You may get this image or more information, at:
2649 <http://www.myri.com/scs/download-Myri10GE.html>
2651 To compile this driver as a module, choose M here and read
2652 <file:Documentation/networking/net-modules.txt>. The module
2653 will be called myri10ge.
2656 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2659 This enables the support for NetXen's Gigabit Ethernet card.
2662 tristate "PA Semi 1/10Gbit MAC"
2663 depends on PPC64 && PCI
2666 This driver supports the on-chip 1/10Gbit Ethernet controller on
2667 PA Semi's PWRficient line of chips.
2675 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2676 depends on MLX4_CORE
2679 This option causes debugging code to be compiled into the
2680 mlx4_core driver. The output can be turned on via the
2681 debug_level module parameter (which can also be set after
2682 the driver is loaded through sysfs).
2685 tristate "Tehuti Networks 10G Ethernet"
2688 Tehuti Networks 10G Ethernet NIC
2690 endif # NETDEV_10000
2692 source "drivers/net/tokenring/Kconfig"
2694 source "drivers/net/wireless/Kconfig"
2696 source "drivers/net/usb/Kconfig"
2698 source "drivers/net/pcmcia/Kconfig"
2700 source "drivers/net/wan/Kconfig"
2702 source "drivers/atm/Kconfig"
2704 source "drivers/s390/net/Kconfig"
2706 config XEN_NETDEV_FRONTEND
2707 tristate "Xen network device frontend driver"
2711 The network device frontend driver allows the kernel to
2712 access network devices exported exported by a virtual
2713 machine containing a physical network device driver. The
2714 frontend driver is intended for unprivileged guest domains;
2715 if you are compiling a kernel for a Xen guest, you almost
2716 certainly want to enable this.
2719 tristate "iSeries Virtual Ethernet driver support"
2720 depends on PPC_ISERIES
2723 tristate "RapidIO Ethernet over messaging driver support"
2726 config RIONET_TX_SIZE
2727 int "Number of outbound queue entries"
2731 config RIONET_RX_SIZE
2732 int "Number of inbound queue entries"
2737 bool "FDDI driver support"
2738 depends on (PCI || EISA || TC)
2740 Fiber Distributed Data Interface is a high speed local area network
2741 design; essentially a replacement for high speed Ethernet. FDDI can
2742 run over copper or fiber. If you are connected to such a network and
2743 want a driver for the FDDI card in your computer, say Y here (and
2744 then also Y to the driver for your FDDI card, below). Most people
2748 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2749 depends on FDDI && (PCI || EISA || TC)
2751 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2752 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2753 to a local FDDI network.
2755 To compile this driver as a module, choose M here: the module
2756 will be called defxx. If unsure, say N.
2760 prompt "Use MMIO instead of PIO" if PCI || EISA
2762 default n if PCI || EISA
2765 This instructs the driver to use EISA or PCI memory-mapped I/O
2766 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2767 Enabling this gives an improvement in processing time in parts
2768 of the driver, but it may cause problems with EISA (DEFEA)
2769 adapters. TURBOchannel does not have the concept of I/O ports,
2770 so MMIO is always used for these (DEFTA) adapters.
2775 tristate "SysKonnect FDDI PCI support"
2776 depends on FDDI && PCI
2779 Say Y here if you have a SysKonnect FDDI PCI adapter.
2780 The following adapters are supported by this driver:
2781 - SK-5521 (SK-NET FDDI-UP)
2782 - SK-5522 (SK-NET FDDI-UP DAS)
2783 - SK-5541 (SK-NET FDDI-FP)
2784 - SK-5543 (SK-NET FDDI-LP)
2785 - SK-5544 (SK-NET FDDI-LP DAS)
2786 - SK-5821 (SK-NET FDDI-UP64)
2787 - SK-5822 (SK-NET FDDI-UP64 DAS)
2788 - SK-5841 (SK-NET FDDI-FP64)
2789 - SK-5843 (SK-NET FDDI-LP64)
2790 - SK-5844 (SK-NET FDDI-LP64 DAS)
2791 - Netelligent 100 FDDI DAS Fibre SC
2792 - Netelligent 100 FDDI SAS Fibre SC
2793 - Netelligent 100 FDDI DAS UTP
2794 - Netelligent 100 FDDI SAS UTP
2795 - Netelligent 100 FDDI SAS Fibre MIC
2797 Read <file:Documentation/networking/skfp.txt> for information about
2800 Questions concerning this driver can be addressed to:
2801 <linux@syskonnect.de>
2803 To compile this driver as a module, choose M here: the module
2804 will be called skfp. This is recommended.
2807 bool "HIPPI driver support (EXPERIMENTAL)"
2808 depends on EXPERIMENTAL && INET && PCI
2810 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2811 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2812 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2813 single-mode). HIPPI networks are commonly used for clusters and to
2814 connect to super computers. If you are connected to a HIPPI network
2815 and have a HIPPI network card in your computer that you want to use
2816 under Linux, say Y here (you must also remember to enable the driver
2817 for your HIPPI card below). Most people will say N here.
2820 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2821 depends on HIPPI && PCI
2823 Say Y here if this is your PCI HIPPI network card.
2825 To compile this driver as a module, choose M here: the module
2826 will be called rrunner. If unsure, say N.
2828 config ROADRUNNER_LARGE_RINGS
2829 bool "Use large TX/RX rings (EXPERIMENTAL)"
2830 depends on ROADRUNNER
2832 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2833 of additional memory to allow for fastest operation, both for
2834 transmitting and receiving. This memory cannot be used by any other
2835 kernel code or by user space programs. Say Y here only if you have
2839 tristate "PLIP (parallel port) support"
2842 PLIP (Parallel Line Internet Protocol) is used to create a
2843 reasonably fast mini network consisting of two (or, rarely, more)
2844 local machines. A PLIP link from a Linux box is a popular means to
2845 install a Linux distribution on a machine which doesn't have a
2846 CD-ROM drive (a minimal system has to be transferred with floppies
2847 first). The kernels on both machines need to have this PLIP option
2848 enabled for this to work.
2850 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2851 ports (the connectors at the computers with 25 holes) are connected
2852 with "null printer" or "Turbo Laplink" cables which can transmit 4
2853 bits at a time (mode 0) or with special PLIP cables, to be used on
2854 bidirectional parallel ports only, which can transmit 8 bits at a
2855 time (mode 1); you can find the wiring of these cables in
2856 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2857 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2858 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2859 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2860 and winsock or NCSA's telnet.
2862 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2863 as the NET-3-HOWTO, both available from
2864 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2865 protocol has been changed and this PLIP driver won't work together
2866 with the PLIP support in Linux versions 1.0.x. This option enlarges
2867 your kernel by about 8 KB.
2869 To compile this driver as a module, choose M here and read
2870 <file:Documentation/networking/net-modules.txt>. The module will be
2871 called plip. If unsure, say Y or M, in case you buy a laptop
2875 tristate "PPP (point-to-point protocol) support"
2878 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2879 the same purpose: sending Internet traffic over telephone (and other
2880 serial) lines. Ask your access provider if they support it, because
2881 otherwise you can't use it; most Internet access providers these
2882 days support PPP rather than SLIP.
2884 To use PPP, you need an additional program called pppd as described
2885 in the PPP-HOWTO, available at
2886 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2887 the version of pppd recommended in <file:Documentation/Changes>.
2888 The PPP option enlarges your kernel by about 16 KB.
2890 There are actually two versions of PPP: the traditional PPP for
2891 asynchronous lines, such as regular analog phone lines, and
2892 synchronous PPP which can be used over digital ISDN lines for
2893 example. If you want to use PPP over phone lines or other
2894 asynchronous serial lines, you need to say Y (or M) here and also to
2895 the next option, "PPP support for async serial ports". For PPP over
2896 synchronous lines, you should say Y (or M) here and to "Support
2897 synchronous PPP", below.
2899 If you said Y to "Version information on all symbols" above, then
2900 you cannot compile the PPP driver into the kernel; you can then only
2901 compile it as a module. To compile this driver as a module, choose M
2902 here and read <file:Documentation/networking/net-modules.txt>.
2903 The module will be called ppp_generic.
2905 config PPP_MULTILINK
2906 bool "PPP multilink support (EXPERIMENTAL)"
2907 depends on PPP && EXPERIMENTAL
2909 PPP multilink is a protocol (defined in RFC 1990) which allows you
2910 to combine several (logical or physical) lines into one logical PPP
2911 connection, so that you can utilize your full bandwidth.
2913 This has to be supported at the other end as well and you need a
2914 version of the pppd daemon which understands the multilink protocol.
2919 bool "PPP filtering"
2922 Say Y here if you want to be able to filter the packets passing over
2923 PPP interfaces. This allows you to control which packets count as
2924 activity (i.e. which packets will reset the idle timer or bring up
2925 a demand-dialed link) and which packets are to be dropped entirely.
2926 You need to say Y here if you wish to use the pass-filter and
2927 active-filter options to pppd.
2932 tristate "PPP support for async serial ports"
2936 Say Y (or M) here if you want to be able to use PPP over standard
2937 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2938 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2941 To compile this driver as a module, choose M here.
2946 tristate "PPP support for sync tty ports"
2949 Say Y (or M) here if you want to be able to use PPP over synchronous
2950 (HDLC) tty devices, such as the SyncLink adapter. These devices
2951 are often used for high-speed leased lines like T1/E1.
2953 To compile this driver as a module, choose M here.
2956 tristate "PPP Deflate compression"
2961 Support for the Deflate compression method for PPP, which uses the
2962 Deflate algorithm (the same algorithm that gzip uses) to compress
2963 each PPP packet before it is sent over the wire. The machine at the
2964 other end of the PPP link (usually your ISP) has to support the
2965 Deflate compression method as well for this to be useful. Even if
2966 they don't support it, it is safe to say Y here.
2968 To compile this driver as a module, choose M here.
2971 tristate "PPP BSD-Compress compression"
2974 Support for the BSD-Compress compression method for PPP, which uses
2975 the LZW compression method to compress each PPP packet before it is
2976 sent over the wire. The machine at the other end of the PPP link
2977 (usually your ISP) has to support the BSD-Compress compression
2978 method as well for this to be useful. Even if they don't support it,
2979 it is safe to say Y here.
2981 The PPP Deflate compression method ("PPP Deflate compression",
2982 above) is preferable to BSD-Compress, because it compresses better
2985 Note that the BSD compression code will always be compiled as a
2986 module; it is called bsd_comp and will show up in the directory
2987 modules once you have said "make modules". If unsure, say N.
2990 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2991 depends on PPP && EXPERIMENTAL
2997 Support for the MPPE Encryption protocol, as employed by the
2998 Microsoft Point-to-Point Tunneling Protocol.
3000 See http://pptpclient.sourceforge.net/ for information on
3001 configuring PPTP clients and servers to utilize this method.
3004 tristate "PPP over Ethernet (EXPERIMENTAL)"
3005 depends on EXPERIMENTAL && PPP
3007 Support for PPP over Ethernet.
3009 This driver requires the latest version of pppd from the CVS
3010 repository at cvs.samba.org. Alternatively, see the
3011 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3012 which contains instruction on how to use this driver (under
3013 the heading "Kernel mode PPPoE").
3016 tristate "PPP over ATM"
3017 depends on ATM && PPP
3019 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3020 This implementation does not yet comply with section 8 of RFC2364,
3021 which can lead to bad results if the ATM peer loses state and
3022 changes its encapsulation unilaterally.
3025 tristate "PPP over L2TP (EXPERIMENTAL)"
3026 depends on EXPERIMENTAL && PPP && INET
3028 Support for PPP-over-L2TP socket family. L2TP is a protocol
3029 used by ISPs and enterprises to tunnel PPP traffic over UDP
3030 tunnels. L2TP is replacing PPTP for VPN uses.
3032 This kernel component handles only L2TP data packets: a
3033 userland daemon handles L2TP the control protocol (tunnel
3034 and session setup). One such daemon is OpenL2TP
3035 (http://openl2tp.sourceforge.net/).
3038 tristate "SLIP (serial line) support"
3040 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3041 connect to your Internet service provider or to connect to some
3042 other local Unix box or if you want to configure your Linux box as a
3043 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3044 Internet Protocol) is a protocol used to send Internet traffic over
3045 serial connections such as telephone lines or null modem cables;
3046 nowadays, the protocol PPP is more commonly used for this same
3049 Normally, your access provider has to support SLIP in order for you
3050 to be able to use it, but there is now a SLIP emulator called SLiRP
3051 around (available from
3052 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3053 allows you to use SLIP over a regular dial up shell connection. If
3054 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3055 NET-3-HOWTO, available from
3056 <http://www.tldp.org/docs.html#howto>, explains how to
3057 configure SLIP. Note that you don't need this option if you just
3058 want to run term (term is a program which gives you almost full
3059 Internet connectivity if you have a regular dial up shell account on
3060 some Internet connected Unix computer. Read
3061 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3062 support will enlarge your kernel by about 4 KB. If unsure, say N.
3064 To compile this driver as a module, choose M here and read
3065 <file:Documentation/networking/net-modules.txt>. The module will be
3068 config SLIP_COMPRESSED
3069 bool "CSLIP compressed headers"
3073 This protocol is faster than SLIP because it uses compression on the
3074 TCP/IP headers (not on the data itself), but it has to be supported
3075 on both ends. Ask your access provider if you are not sure and
3076 answer Y, just in case. You will still be able to use plain SLIP. If
3077 you plan to use SLiRP, the SLIP emulator (available from
3078 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3079 allows you to use SLIP over a regular dial up shell connection, you
3080 definitely want to say Y here. The NET-3-HOWTO, available from
3081 <http://www.tldp.org/docs.html#howto>, explains how to configure
3082 CSLIP. This won't enlarge your kernel.
3087 This option enables Van Jacobsen serial line header compression
3091 bool "Keepalive and linefill"
3094 Adds additional capabilities to the SLIP driver to support the
3095 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3098 config SLIP_MODE_SLIP6
3099 bool "Six bit SLIP encapsulation"
3102 Just occasionally you may need to run IP over hostile serial
3103 networks that don't pass all control characters or are only seven
3104 bit. Saying Y here adds an extra mode you can use with SLIP:
3105 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3106 the serial device. Naturally, this has to be supported at the other
3107 end of the link as well. It's good enough, for example, to run IP
3108 over the async ports of a Camtec JNT Pad. If unsure, say N.
3111 bool "Fibre Channel driver support"
3112 depends on SCSI && PCI
3114 Fibre Channel is a high speed serial protocol mainly used to connect
3115 large storage devices to the computer; it is compatible with and
3116 intended to replace SCSI.
3118 If you intend to use Fibre Channel, you need to have a Fibre channel
3119 adaptor card in your computer; say Y here and to the driver for your
3120 adaptor below. You also should have said Y to "SCSI support" and
3121 "SCSI generic support".
3124 tristate "Traffic Shaper (OBSOLETE)"
3125 depends on EXPERIMENTAL
3127 The traffic shaper is a virtual network device that allows you to
3128 limit the rate of outgoing data flow over some other network device.
3129 The traffic that you want to slow down can then be routed through
3130 these virtual devices. See
3131 <file:Documentation/networking/shaper.txt> for more information.
3133 An alternative to this traffic shaper are traffic schedulers which
3134 you'll get if you say Y to "QoS and/or fair queuing" in
3135 "Networking options".
3137 To compile this driver as a module, choose M here: the module
3138 will be called shaper. If unsure, say N.
3141 tristate "Network console logging support (EXPERIMENTAL)"
3142 depends on EXPERIMENTAL
3144 If you want to log kernel messages over the network, enable this.
3145 See <file:Documentation/networking/netconsole.txt> for details.
3147 config NETCONSOLE_DYNAMIC
3148 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3149 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3152 This option enables the ability to dynamically reconfigure target
3153 parameters (interface, IP addresses, port numbers, MAC addresses)
3154 at runtime through a userspace interface exported using configfs.
3155 See <file:Documentation/networking/netconsole.txt> for details.
3161 bool "Netpoll traffic trapping"
3165 config NET_POLL_CONTROLLER