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)
843 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
845 This is the driver for blackfin on-chip mac device. Say Y if you want it
846 compiled into the kernel. This driver is also available as a module
847 ( = code which can be inserted in and removed from the running kernel
848 whenever you want). The module will be called bfin_mac.
850 config BFIN_MAC_USE_L1
851 bool "Use L1 memory for rx/tx packets"
852 depends on BFIN_MAC && BF537
855 To get maximum network performace, you should use L1 memory as rx/tx buffers.
856 Say N here if you want to reserve L1 memory for other uses.
858 config BFIN_TX_DESC_NUM
859 int "Number of transmit buffer packets"
861 range 6 10 if BFIN_MAC_USE_L1
865 Set the number of buffer packets used in driver.
867 config BFIN_RX_DESC_NUM
868 int "Number of receive buffer packets"
870 range 20 100 if BFIN_MAC_USE_L1
874 Set the number of buffer packets used in driver.
877 bool "RMII PHY Interface (EXPERIMENTAL)"
878 depends on BFIN_MAC && EXPERIMENTAL
881 Use Reduced PHY MII Interface
884 tristate "SMC 9194 support"
885 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
888 This is support for the SMC9xxx based Ethernet cards. Choose this
889 option if you have a DELL laptop with the docking station, or
890 another SMC9192/9194 based chipset. Say Y if you want it compiled
891 into the kernel, and read the file
892 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
893 available from <http://www.tldp.org/docs.html#howto>.
895 To compile this driver as a module, choose M here and read
896 <file:Documentation/networking/net-modules.txt>. The module
897 will be called smc9194.
900 tristate "SMC 91C9x/91C1xxx support"
903 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
905 This is a driver for SMC's 91x series of Ethernet chipsets,
906 including the SMC91C94 and the SMC91C111. Say Y if you want it
907 compiled into the kernel, and read the file
908 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
909 available from <http://www.linuxdoc.org/docs.html#howto>.
911 This driver is also available as a module ( = code which can be
912 inserted in and removed from the running kernel whenever you want).
913 The module will be called smc91x. If you want to compile it as a
914 module, say M here and read <file:Documentation/kbuild/modules.txt>
915 as well as <file:Documentation/networking/net-modules.txt>.
918 tristate "NetX Ethernet support"
922 This is support for the Hilscher netX builtin Ethernet ports
924 To compile this driver as a module, choose M here and read
925 <file:Documentation/networking/net-modules.txt>. The module
926 will be called netx-eth.
929 tristate "DM9000 support"
930 depends on ARM || BLACKFIN || MIPS
934 Support for DM9000 chipset.
936 To compile this driver as a module, choose M here and read
937 <file:Documentation/networking/net-modules.txt>. The module will be
941 tristate "SMSC LAN911[5678] support"
946 This is a driver for SMSC's LAN911x series of Ethernet chipsets
947 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
948 Say Y if you want it compiled into the kernel,
949 and read the Ethernet-HOWTO, available from
950 <http://www.linuxdoc.org/docs.html#howto>.
952 This driver is also available as a module. The module will be
953 called smc911x. If you want to compile it as a module, say M
954 here and read <file:Documentation/kbuild/modules.txt>
956 config NET_VENDOR_RACAL
957 bool "Racal-Interlan (Micom) NI cards"
960 If you have a network (Ethernet) card belonging to this class, such
961 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
962 available from <http://www.tldp.org/docs.html#howto>.
964 Note that the answer to this question doesn't directly affect the
965 kernel: saying N will just cause the configurator to skip all
966 the questions about NI cards. If you say Y, you will be asked for
967 your specific card in the following questions.
970 tristate "NI5010 support (EXPERIMENTAL)"
971 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
973 If you have a network (Ethernet) card of this type, say Y and read
974 the Ethernet-HOWTO, available from
975 <http://www.tldp.org/docs.html#howto>. Note that this is still
978 To compile this driver as a module, choose M here and read
979 <file:Documentation/networking/net-modules.txt>. The module
980 will be called ni5010.
983 tristate "NI5210 support"
984 depends on NET_VENDOR_RACAL && ISA
986 If you have a network (Ethernet) card of this type, say Y and read
987 the Ethernet-HOWTO, available from
988 <http://www.tldp.org/docs.html#howto>.
990 To compile this driver as a module, choose M here and read
991 <file:Documentation/networking/net-modules.txt>. The module
995 tristate "NI6510 support"
996 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
998 If you have a network (Ethernet) card of this type, say Y and read
999 the Ethernet-HOWTO, available from
1000 <http://www.tldp.org/docs.html#howto>.
1002 To compile this driver as a module, choose M here and read
1003 <file:Documentation/networking/net-modules.txt>. The module
1004 will be called ni65.
1006 source "drivers/net/tulip/Kconfig"
1009 tristate "AT1700/1720 support (EXPERIMENTAL)"
1010 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1013 If you have a network (Ethernet) card of this type, say Y and read
1014 the Ethernet-HOWTO, available from
1015 <http://www.tldp.org/docs.html#howto>.
1017 To compile this driver as a module, choose M here and read
1018 <file:Documentation/networking/net-modules.txt>. The module
1019 will be called at1700.
1022 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1023 depends on ISA || EISA || MCA
1026 If you have a network (Ethernet) card of this type, say Y and read
1027 the Ethernet-HOWTO, available from
1028 <http://www.tldp.org/docs.html#howto> as well as
1029 <file:drivers/net/depca.c>.
1031 To compile this driver as a module, choose M here and read
1032 <file:Documentation/networking/net-modules.txt>. The module
1033 will be called depca.
1036 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1037 depends on ISA || EISA || PCI
1039 If you have a network (Ethernet) card of this type, say Y and read
1040 the Ethernet-HOWTO, available from
1041 <http://www.tldp.org/docs.html#howto>.
1043 To compile this driver as a module, choose M here and read
1044 <file:Documentation/networking/net-modules.txt>. The module
1045 will be called hp100.
1048 bool "Other ISA cards"
1051 If your network (Ethernet) card hasn't been mentioned yet and its
1052 bus system (that's the way the cards talks to the other components
1053 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1054 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1055 available from <http://www.tldp.org/docs.html#howto>.
1059 Note that the answer to this question doesn't directly affect the
1060 kernel: saying N will just cause the configurator to skip all
1061 the remaining ISA network card questions. If you say Y, you will be
1062 asked for your specific card in the following questions.
1065 tristate "Cabletron E21xx support"
1069 If you have a network (Ethernet) card of this type, say Y and read
1070 the Ethernet-HOWTO, available from
1071 <http://www.tldp.org/docs.html#howto>.
1073 To compile this driver as a module, choose M here and read
1074 <file:Documentation/networking/net-modules.txt>. The module
1075 will be called e2100.
1078 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1082 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1083 cards. If this is for you, say Y and read
1084 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1085 well as the Ethernet-HOWTO, available from
1086 <http://www.tldp.org/docs.html#howto>.
1088 To compile this driver as a module, choose M here and read
1089 <file:Documentation/networking/net-modules.txt>. The module
1090 will be called ewrk3.
1093 tristate "EtherExpress 16 support"
1096 If you have an EtherExpress16 network (Ethernet) card, say Y and
1097 read the Ethernet-HOWTO, available from
1098 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1099 EtherExpress16 card used to be regarded as a very poor choice
1100 because the driver was very unreliable. We now have a new driver
1101 that should do better.
1103 To compile this driver as a module, choose M here and read
1104 <file:Documentation/networking/net-modules.txt>. The module
1105 will be called eexpress.
1108 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1111 If you have a network (Ethernet) card of this type, say Y. This
1112 driver supports Intel i82595{FX,TX} based boards. Note however
1113 that the EtherExpress PRO/100 Ethernet card has its own separate
1114 driver. Please read the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>.
1117 To compile this driver as a module, choose M here and read
1118 <file:Documentation/networking/net-modules.txt>. The module
1119 will be called eepro.
1122 tristate "HP PCLAN+ (27247B and 27252A) support"
1126 If you have a network (Ethernet) card of this type, say Y and read
1127 the Ethernet-HOWTO, available from
1128 <http://www.tldp.org/docs.html#howto>.
1130 To compile this driver as a module, choose M here and read
1131 <file:Documentation/networking/net-modules.txt>. The module
1132 will be called hp-plus.
1135 tristate "HP PCLAN (27245 and other 27xxx series) support"
1139 If you have a network (Ethernet) card of this type, say Y and read
1140 the Ethernet-HOWTO, available from
1141 <http://www.tldp.org/docs.html#howto>.
1143 To compile this driver as a module, choose M here and read
1144 <file:Documentation/networking/net-modules.txt>. The module
1148 tristate "LP486E on board Ethernet"
1151 Say Y here to support the 82596-based on-board Ethernet controller
1152 for the Panther motherboard, which is one of the two shipped in the
1153 Intel Professional Workstation.
1156 tristate "ICL EtherTeam 16i/32 support"
1159 If you have a network (Ethernet) card of this type, say Y and read
1160 the Ethernet-HOWTO, available from
1161 <http://www.tldp.org/docs.html#howto>.
1163 To compile this driver as a module, choose M here and read
1164 <file:Documentation/networking/net-modules.txt>. The module
1165 will be called eth16i.
1168 tristate "NE2000/NE1000 support"
1169 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1172 If you have a network (Ethernet) card of this type, say Y and read
1173 the Ethernet-HOWTO, available from
1174 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1175 without a specific driver are compatible with NE2000.
1177 If you have a PCI NE2000 card however, say N here and Y to "PCI
1178 NE2000 and clone support" under "EISA, VLB, PCI and on board
1179 controllers" below. If you have a NE2000 card and are running on
1180 an MCA system (a bus system used on some IBM PS/2 computers and
1181 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1184 To compile this driver as a module, choose M here and read
1185 <file:Documentation/networking/net-modules.txt>. The module
1189 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1190 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1192 The Zenith Z-Note notebook computer has a built-in network
1193 (Ethernet) card, and this is the Linux driver for it. Note that the
1194 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1195 by this driver. Read the Ethernet-HOWTO, available from
1196 <http://www.tldp.org/docs.html#howto>.
1199 tristate "SEEQ8005 support (EXPERIMENTAL)"
1200 depends on NET_ISA && EXPERIMENTAL
1202 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1203 is for you, read the Ethernet-HOWTO, available from
1204 <http://www.tldp.org/docs.html#howto>.
1206 To compile this driver as a module, choose M here and read
1207 <file:Documentation/networking/net-modules.txt>. The module
1208 will be called seeq8005.
1211 tristate "NE/2 (ne2000 MCA version) support"
1212 depends on MCA_LEGACY
1215 If you have a network (Ethernet) card of this type, say Y and read
1216 the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here and read
1220 <file:Documentation/networking/net-modules.txt>. The module
1224 tristate "IBM LAN Adapter/A support"
1225 depends on MCA && MCA_LEGACY
1227 This is a Micro Channel Ethernet adapter. You need to set
1228 CONFIG_MCA to use this driver. It is both available as an in-kernel
1229 driver and as a module.
1231 To compile this driver as a module, choose M here and read
1232 <file:Documentation/networking/net-modules.txt>. The only
1233 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1234 will both support 16K and 32K memory windows, however a 32K window
1235 gives a better security against packet losses. Usage of multiple
1236 boards with this driver should be possible, but has not been tested
1237 up to now due to lack of hardware.
1240 tristate "IBM LAN Virtual Ethernet support"
1241 depends on PPC_PSERIES
1243 This driver supports virtual ethernet adapters on newer IBM iSeries
1244 and pSeries systems.
1246 To compile this driver as a module, choose M here and read
1247 <file:Documentation/networking/net-modules.txt>. The module will
1251 tristate "PowerPC 4xx on-chip Ethernet support"
1252 depends on 4xx && !PPC_MERGE
1254 This driver supports the PowerPC 4xx EMAC family of on-chip
1255 Ethernet controllers.
1258 int "Number of receive buffers"
1263 int "Number of transmit buffers"
1267 config IBM_EMAC_POLL_WEIGHT
1268 int "MAL NAPI polling weight"
1272 config IBM_EMAC_RX_COPY_THRESHOLD
1273 int "RX skb copy threshold (bytes)"
1277 config IBM_EMAC_RX_SKB_HEADROOM
1278 int "Additional RX skb headroom (bytes)"
1282 Additional receive skb headroom. Note, that driver
1283 will always reserve at least 2 bytes to make IP header
1284 aligned, so usually there is no need to add any additional
1287 If unsure, set to 0.
1289 config IBM_EMAC_PHY_RX_CLK_FIX
1290 bool "PHY Rx clock workaround"
1291 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1293 Enable this if EMAC attached to a PHY which doesn't generate
1294 RX clock if there is no link, if this is the case, you will
1295 see "TX disable timeout" or "RX disable timeout" in the system
1300 config IBM_EMAC_DEBUG
1305 config IBM_EMAC_ZMII
1307 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1310 config IBM_EMAC_RGMII
1312 depends on IBM_EMAC && 440GX
1317 depends on IBM_EMAC && 440GX
1321 bool "EISA, VLB, PCI and on board controllers"
1322 depends on ISA || EISA || PCI
1324 This is another class of network cards which attach directly to the
1325 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1326 available from <http://www.tldp.org/docs.html#howto>.
1328 Note that the answer to this question doesn't directly affect the
1329 kernel: saying N will just cause the configurator to skip all
1330 the questions about this class of network cards. If you say Y, you
1331 will be asked for your specific card in the following questions. If
1332 you are unsure, say Y.
1335 tristate "AMD PCnet32 PCI support"
1336 depends on NET_PCI && PCI
1340 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1341 answer Y here and read the Ethernet-HOWTO, available from
1342 <http://www.tldp.org/docs.html#howto>.
1344 To compile this driver as a module, choose M here and read
1345 <file:Documentation/networking/net-modules.txt>. The module
1346 will be called pcnet32.
1349 bool "Use RX polling (NAPI)"
1352 NAPI is a new driver API designed to reduce CPU and interrupt load
1353 when the driver is receiving lots of packets from the card. It is
1354 still somewhat experimental and thus not yet enabled by default.
1356 If your estimated Rx load is 10kpps or more, or if the card will be
1357 deployed on potentially unfriendly networks (e.g. in a firewall),
1360 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1366 tristate "AMD 8111 (new PCI lance) support"
1367 depends on NET_PCI && PCI
1371 If you have an AMD 8111-based PCI lance ethernet card,
1372 answer Y here and read the Ethernet-HOWTO, available from
1373 <http://www.tldp.org/docs.html#howto>.
1375 To compile this driver as a module, choose M here and read
1376 <file:Documentation/networking/net-modules.txt>. The module
1377 will be called amd8111e.
1379 config AMD8111E_NAPI
1380 bool "Enable NAPI support"
1381 depends on AMD8111_ETH
1383 NAPI is a new driver API designed to reduce CPU and interrupt load
1384 when the driver is receiving lots of packets from the card. It is
1385 still somewhat experimental and thus not yet enabled by default.
1387 If your estimated Rx load is 10kpps or more, or if the card will be
1388 deployed on potentially unfriendly networks (e.g. in a firewall),
1391 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1396 config ADAPTEC_STARFIRE
1397 tristate "Adaptec Starfire/DuraLAN support"
1398 depends on NET_PCI && PCI
1402 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1403 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1404 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1407 To compile this driver as a module, choose M here: the module
1408 will be called starfire. This is recommended.
1410 config ADAPTEC_STARFIRE_NAPI
1411 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1412 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1414 NAPI is a new driver API designed to reduce CPU and interrupt load
1415 when the driver is receiving lots of packets from the card. It is
1416 still somewhat experimental and thus not yet enabled by default.
1418 If your estimated Rx load is 10kpps or more, or if the card will be
1419 deployed on potentially unfriendly networks (e.g. in a firewall),
1422 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1428 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1429 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1432 If you have a network (Ethernet) card of this type, say Y and read
1433 the Ethernet-HOWTO, available from
1434 <http://www.tldp.org/docs.html#howto>.
1436 To compile this driver as a module, choose M here and read
1437 <file:Documentation/networking/net-modules.txt>. The module
1438 will be called ac3200.
1441 tristate "Apricot Xen-II on board Ethernet"
1442 depends on NET_PCI && ISA
1444 If you have a network (Ethernet) controller of this type, say Y and
1445 read the Ethernet-HOWTO, available from
1446 <http://www.tldp.org/docs.html#howto>.
1448 To compile this driver as a module, choose M here and read
1449 <file:Documentation/networking/net-modules.txt>. The module will be
1453 tristate "Broadcom 440x/47xx ethernet support"
1454 depends on SSB_POSSIBLE
1458 If you have a network (Ethernet) controller of this type, say Y
1459 or M and read the Ethernet-HOWTO, available from
1460 <http://www.tldp.org/docs.html#howto>.
1462 To compile this driver as a module, choose M here and read
1463 <file:Documentation/networking/net-modules.txt>. The module will be
1466 # Auto-select SSB PCI-HOST support, if possible
1467 config B44_PCI_AUTOSELECT
1469 depends on B44 && SSB_PCIHOST_POSSIBLE
1473 # Auto-select SSB PCICORE driver, if possible
1474 config B44_PCICORE_AUTOSELECT
1476 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1477 select SSB_DRIVER_PCICORE
1482 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1486 tristate "nForce Ethernet support"
1487 depends on NET_PCI && PCI
1489 If you have a network (Ethernet) controller of this type, say Y and
1490 read the Ethernet-HOWTO, available from
1491 <http://www.tldp.org/docs.html#howto>.
1493 To compile this driver as a module, choose M here and read
1494 <file:Documentation/networking/net-modules.txt>. The module will be
1497 config FORCEDETH_NAPI
1498 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1499 depends on FORCEDETH && EXPERIMENTAL
1501 NAPI is a new driver API designed to reduce CPU and interrupt load
1502 when the driver is receiving lots of packets from the card. It is
1503 still somewhat experimental and thus not yet enabled by default.
1505 If your estimated Rx load is 10kpps or more, or if the card will be
1506 deployed on potentially unfriendly networks (e.g. in a firewall),
1509 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1515 tristate "CS89x0 support"
1516 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1518 Support for CS89x0 chipset based Ethernet cards. If you have a
1519 network (Ethernet) card of this type, say Y and read the
1520 Ethernet-HOWTO, available from
1521 <http://www.tldp.org/docs.html#howto> as well as
1522 <file:Documentation/networking/cs89x0.txt>.
1524 To compile this driver as a module, choose M here and read
1525 <file:Documentation/networking/net-modules.txt>. The module will be
1529 tristate "TOSHIBA TC35815 Ethernet support"
1530 depends on NET_PCI && PCI && MIPS
1534 tristate "Digi Intl. RightSwitch SE-X support"
1535 depends on NET_PCI && (PCI || EISA)
1537 This is support for the Digi International RightSwitch series of
1538 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1539 models. If you have a network card of this type, say Y and read the
1540 Ethernet-HOWTO, available from
1541 <http://www.tldp.org/docs.html#howto>. More specific
1542 information is contained in <file:Documentation/networking/dgrs.txt>.
1544 To compile this driver as a module, choose M here and read
1545 <file:Documentation/networking/net-modules.txt>. The module
1546 will be called dgrs.
1549 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1550 depends on NET_PCI && PCI
1553 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1554 card, say Y and read the Ethernet-HOWTO, available from
1555 <http://www.tldp.org/docs.html#howto>.
1557 To compile this driver as a module, choose M here and read
1558 <file:Documentation/networking/net-modules.txt>. The module
1559 will be called eepro100.
1563 tristate "Intel(R) PRO/100+ support"
1564 depends on NET_PCI && PCI
1567 This driver supports Intel(R) PRO/100 family of adapters.
1568 To verify that your adapter is supported, find the board ID number
1569 on the adapter. Look for a label that has a barcode and a number
1570 in the format 123456-001 (six digits hyphen three digits).
1572 Use the above information and the Adapter & Driver ID Guide at:
1574 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1576 to identify the adapter.
1578 For the latest Intel PRO/100 network driver for Linux, see:
1580 <http://appsr.intel.com/scripts-df/support_intel.asp>
1582 More specific information on configuring the driver is in
1583 <file:Documentation/networking/e100.txt>.
1585 To compile this driver as a module, choose M here and read
1586 <file:Documentation/networking/net-modules.txt>. The module
1587 will be called e100.
1590 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1591 depends on NET_PCI && EISA && EXPERIMENTAL
1594 If you have a network (Ethernet) card of this type, say Y and read
1595 the Ethernet-HOWTO, available from
1596 <http://www.tldp.org/docs.html#howto>.
1598 To compile this driver as a module, choose M here and read
1599 <file:Documentation/networking/net-modules.txt>. The module
1600 will be called lne390.
1603 tristate "Myson MTD-8xx PCI Ethernet support"
1604 depends on NET_PCI && PCI
1608 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1609 cards. Specifications and data at
1610 <http://www.myson.com.hk/mtd/datasheet/>.
1613 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1614 depends on NET_PCI && PCI
1617 This driver is for the National Semiconductor DP83810 series,
1618 which is used in cards from PureData, NetGear, Linksys
1619 and others, including the 83815 chip.
1620 More specific information and updates are available from
1621 <http://www.scyld.com/network/natsemi.html>.
1624 tristate "PCI NE2000 and clones support (see help)"
1625 depends on NET_PCI && PCI
1628 This driver is for NE2000 compatible PCI cards. It will not work
1629 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1630 support" below). If you have a PCI NE2000 network (Ethernet) card,
1631 say Y and read the Ethernet-HOWTO, available from
1632 <http://www.tldp.org/docs.html#howto>.
1634 This driver also works for the following NE2000 clone cards:
1635 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1636 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1637 Holtek HT80232 Holtek HT80229
1639 To compile this driver as a module, choose M here and read
1640 <file:Documentation/networking/net-modules.txt>. The module
1641 will be called ne2k-pci.
1644 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1645 depends on NET_PCI && EISA && EXPERIMENTAL
1648 If you have a network (Ethernet) card of this type, say Y and read
1649 the Ethernet-HOWTO, available from
1650 <http://www.tldp.org/docs.html#howto>. Note that this driver
1651 will NOT WORK for NE3200 cards as they are completely different.
1653 To compile this driver as a module, choose M here and read
1654 <file:Documentation/networking/net-modules.txt>. The module
1655 will be called ne3210.
1658 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1659 depends on NET_PCI && EISA && EXPERIMENTAL
1662 If you have a network (Ethernet) card of this type, say Y and read
1663 the Ethernet-HOWTO, available from
1664 <http://www.tldp.org/docs.html#howto>.
1666 To compile this driver as a module, choose M here and read
1667 <file:Documentation/networking/net-modules.txt>. The module
1668 will be called es3210.
1671 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1672 depends on NET_PCI && PCI && EXPERIMENTAL
1676 This is a driver for the Fast Ethernet PCI network cards based on
1677 the RTL8139C+ chips. If you have one of those, say Y and read
1678 the Ethernet-HOWTO, available from
1679 <http://www.tldp.org/docs.html#howto>.
1681 To compile this driver as a module, choose M here: the module
1682 will be called 8139cp. This is recommended.
1685 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1686 depends on NET_PCI && PCI
1690 This is a driver for the Fast Ethernet PCI network cards based on
1691 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1692 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1694 To compile this driver as a module, choose M here: the module
1695 will be called 8139too. This is recommended.
1698 bool "Use PIO instead of MMIO"
1702 This instructs the driver to use programmed I/O ports (PIO) instead
1703 of PCI shared memory (MMIO). This can possibly solve some problems
1704 in case your mainboard has memory consistency issues. If unsure,
1707 config 8139TOO_TUNE_TWISTER
1708 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1711 This implements a function which might come in handy in case you
1712 are using low quality on long cabling. It is required for RealTek
1713 RTL-8139 revision K boards, and totally unused otherwise. It tries
1714 to match the transceiver to the cable characteristics. This is
1715 experimental since hardly documented by the manufacturer.
1719 bool "Support for older RTL-8129/8130 boards"
1722 This enables support for the older and uncommon RTL-8129 and
1723 RTL-8130 chips, which support MII via an external transceiver,
1724 instead of an internal one. Disabling this option will save some
1725 memory by making the code size smaller. If unsure, say Y.
1727 config 8139_OLD_RX_RESET
1728 bool "Use older RX-reset method"
1731 The 8139too driver was recently updated to contain a more rapid
1732 reset sequence, in the face of severe receive errors. This "new"
1733 RX-reset method should be adequate for all boards. But if you
1734 experience problems, you can enable this option to restore the
1735 old RX-reset behavior. If unsure, say N.
1738 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1739 depends on NET_PCI && PCI
1743 This is a driver for the Fast Ethernet PCI network cards based on
1744 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1745 SiS 630 and SiS 540 chipsets.
1747 This driver also supports AMD 79C901 HomePNA so that you can use
1748 your phone line as a network cable.
1750 To compile this driver as a module, choose M here: the module
1751 will be called sis900. This is recommended.
1754 tristate "SMC EtherPower II"
1755 depends on NET_PCI && PCI
1759 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1760 which is based on the SMC83c17x (EPIC/100).
1761 More specific information and updates are available from
1762 <http://www.scyld.com/network/epic100.html>.
1765 tristate "Sundance Alta support"
1766 depends on NET_PCI && PCI
1770 This driver is for the Sundance "Alta" chip.
1771 More specific information and updates are available from
1772 <http://www.scyld.com/network/sundance.html>.
1774 config SUNDANCE_MMIO
1775 bool "Use MMIO instead of PIO"
1778 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1779 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1780 is known to solve bugs on certain chips.
1785 tristate "TI ThunderLAN support"
1786 depends on NET_PCI && (PCI || EISA) && !64BIT
1788 If you have a PCI Ethernet network card based on the ThunderLAN chip
1789 which is supported by this driver, say Y and read the
1790 Ethernet-HOWTO, available from
1791 <http://www.tldp.org/docs.html#howto>.
1793 Devices currently supported by this driver are Compaq Netelligent,
1794 Compaq NetFlex and Olicom cards. Please read the file
1795 <file:Documentation/networking/tlan.txt> for more details.
1797 To compile this driver as a module, choose M here and read
1798 <file:Documentation/networking/net-modules.txt>. The module
1799 will be called tlan.
1801 Please email feedback to <torben.mathiasen@compaq.com>.
1804 tristate "VIA Rhine support"
1805 depends on NET_PCI && PCI
1809 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1810 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1811 Ethernet functions can also be found integrated on South Bridges
1814 To compile this driver as a module, choose M here. The module
1815 will be called via-rhine.
1817 config VIA_RHINE_MMIO
1818 bool "Use MMIO instead of PIO"
1819 depends on VIA_RHINE
1821 This instructs the driver to use PCI shared memory (MMIO) instead of
1822 programmed I/O ports (PIO). Enabling this gives an improvement in
1823 processing time in parts of the driver.
1827 config VIA_RHINE_NAPI
1828 bool "Use Rx Polling (NAPI)"
1829 depends on VIA_RHINE
1831 NAPI is a new driver API designed to reduce CPU and interrupt load
1832 when the driver is receiving lots of packets from the card.
1834 If your estimated Rx load is 10kpps or more, or if the card will be
1835 deployed on potentially unfriendly networks (e.g. in a firewall),
1838 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1842 bool "Philips SAA9730 Ethernet support"
1843 depends on NET_PCI && PCI && MIPS_ATLAS
1845 The SAA9730 is a combined multimedia and peripheral controller used
1846 in thin clients, Internet access terminals, and diskless
1848 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1851 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1852 depends on NET_PCI && PCI && EXPERIMENTAL
1855 This is a driver for the Fast Ethernet PCI network cards based on
1856 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1857 have one of these, say Y here.
1859 To compile this driver as a module, choose M here: the module
1860 will be called sc92031. This is recommended.
1863 bool "Pocket and portable adapters"
1866 Cute little network (Ethernet) devices which attach to the parallel
1867 port ("pocket adapters"), commonly used with laptops. If you have
1868 one of those, say Y and read the Ethernet-HOWTO, available from
1869 <http://www.tldp.org/docs.html#howto>.
1871 If you want to plug a network (or some other) card into the PCMCIA
1872 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1873 credit card size extension cards used by all modern laptops), you
1874 need the pcmcia-cs package (location contained in the file
1875 <file:Documentation/Changes>) and you can say N here.
1877 Laptop users should read the Linux Laptop home page at
1878 <http://www.linux-on-laptops.com/> or
1879 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1881 Note that the answer to this question doesn't directly affect the
1882 kernel: saying N will just cause the configurator to skip all
1883 the questions about this class of network devices. If you say Y, you
1884 will be asked for your specific device in the following questions.
1887 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1888 depends on NET_POCKET && PARPORT && X86
1891 This is a network (Ethernet) device which attaches to your parallel
1892 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1893 available from <http://www.tldp.org/docs.html#howto>, if you
1894 want to use this. If you intend to use this driver, you should have
1895 said N to the "Parallel printer support", because the two drivers
1896 don't like each other.
1898 To compile this driver as a module, choose M here: the module
1902 tristate "D-Link DE600 pocket adapter support"
1903 depends on NET_POCKET && PARPORT
1905 This is a network (Ethernet) device which attaches to your parallel
1906 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1907 Ethernet-HOWTO, available from
1908 <http://www.tldp.org/docs.html#howto>, if you want to use
1909 this. It is possible to have several devices share a single parallel
1910 port and it is safe to compile the corresponding drivers into the
1913 To compile this driver as a module, choose M here: the module
1914 will be called de600.
1917 tristate "D-Link DE620 pocket adapter support"
1918 depends on NET_POCKET && PARPORT
1920 This is a network (Ethernet) device which attaches to your parallel
1921 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1922 Ethernet-HOWTO, available from
1923 <http://www.tldp.org/docs.html#howto>, if you want to use
1924 this. It is possible to have several devices share a single parallel
1925 port and it is safe to compile the corresponding drivers into the
1928 To compile this driver as a module, choose M here: the module
1929 will be called de620.
1932 tristate "SGI Seeq ethernet controller support"
1935 Say Y here if you have an Seeq based Ethernet network card. This is
1936 used in many Silicon Graphics machines.
1939 tristate "DEC LANCE ethernet controller support"
1940 depends on MACH_DECSTATION
1943 This driver is for the series of Ethernet controllers produced by
1944 DEC (now Compaq) based on the AMD Lance chipset, including the
1945 DEPCA series. (This chipset is better known via the NE2100 cards.)
1948 bool "Motorola 68360 ethernet controller"
1951 Say Y here if you want to use the built-in ethernet controller of
1952 the Motorola 68360 processor.
1955 bool "FEC ethernet controller (of ColdFire CPUs)"
1956 depends on M523x || M527x || M5272 || M528x || M520x
1958 Say Y here if you want to use the built-in 10/100 Fast ethernet
1959 controller on some Motorola ColdFire processors.
1962 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1965 Say Y here if you want to use the second built-in 10/100 Fast
1966 ethernet controller on some Motorola ColdFire processors.
1969 tristate "NE2000 compatible support for H8/300"
1972 Say Y here if you want to use the NE2000 compatible
1973 controller on the Renesas H8/300 processor.
1975 source "drivers/net/fec_8xx/Kconfig"
1976 source "drivers/net/fs_enet/Kconfig"
1978 endif # NET_ETHERNET
1984 menuconfig NETDEV_1000
1985 bool "Ethernet (1000 Mbit)"
1989 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1990 type of Local Area Network (LAN) in universities and companies.
1992 Say Y here to get to see options for Gigabit Ethernet drivers.
1993 This option alone does not add any kernel code.
1994 Note that drivers supporting both 100 and 1000 MBit may be listed
1995 under "Ethernet (10 or 100MBit)" instead.
1997 If you say N, all options in this submenu will be skipped and disabled.
2002 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2005 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2006 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2007 adapter. The driver allows for using the Jumbo Frame option (9000
2008 bytes/frame) however it requires that your switches can handle this
2009 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2012 To compile this driver as a module, choose M here: the
2013 module will be called acenic.
2015 config ACENIC_OMIT_TIGON_I
2016 bool "Omit support for old Tigon I based AceNICs"
2019 Say Y here if you only have Tigon II based AceNICs and want to leave
2020 out support for the older Tigon I based cards which are no longer
2021 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2022 version)). This will reduce the size of the driver object by
2023 app. 100KB. If you are not sure whether your card is a Tigon I or a
2024 Tigon II, say N here.
2026 The safe and default value for this is N.
2029 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2033 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2035 D-Link DGE-550T Gigabit Ethernet Adapter.
2036 D-Link DL2000-based Gigabit Ethernet Adapter.
2037 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2039 To compile this driver as a module, choose M here: the
2040 module will be called dl2k.
2043 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2046 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2047 adapters. For more information on how to identify your adapter, go
2048 to the Adapter & Driver ID Guide at:
2050 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2052 For general information and support, go to the Intel support
2055 <http://support.intel.com>
2057 More specific information on configuring the driver is in
2058 <file:Documentation/networking/e1000.txt>.
2060 To compile this driver as a module, choose M here and read
2061 <file:Documentation/networking/net-modules.txt>. The module
2062 will be called e1000.
2065 bool "Use Rx Polling (NAPI)"
2068 NAPI is a new driver API designed to reduce CPU and interrupt load
2069 when the driver is receiving lots of packets from the card. It is
2070 still somewhat experimental and thus not yet enabled by default.
2072 If your estimated Rx load is 10kpps or more, or if the card will be
2073 deployed on potentially unfriendly networks (e.g. in a firewall),
2076 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2081 config E1000_DISABLE_PACKET_SPLIT
2082 bool "Disable Packet Split for PCI express adapters"
2085 Say Y here if you want to use the legacy receive path for PCI express
2091 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2094 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2095 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2096 use the regular e1000 driver For more information on how to
2097 identify your adapter, go to the Adapter & Driver ID Guide at:
2099 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2101 For general information and support, go to the Intel support
2104 <http://support.intel.com>
2106 More specific information on configuring the driver is in
2107 <file:Documentation/networking/e1000e.txt>.
2109 To compile this driver as a module, choose M here and read
2110 <file:Documentation/networking/net-modules.txt>. The module
2111 will be called e1000e.
2113 source "drivers/net/ixp2000/Kconfig"
2116 tristate "MyriCOM Gigabit Ethernet support"
2119 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2121 To compile this driver as a module, choose M here: the module
2122 will be called myri_sbus. This is recommended.
2125 tristate "National Semiconductor DP83820 support"
2128 This is a driver for the National Semiconductor DP83820 series
2129 of gigabit ethernet MACs. Cards using this chipset include
2130 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2131 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2135 tristate "Packet Engines Hamachi GNIC-II support"
2139 If you have a Gigabit Ethernet card of this type, say Y and read
2140 the Ethernet-HOWTO, available from
2141 <http://www.tldp.org/docs.html#howto>.
2143 To compile this driver as a module, choose M here and read
2144 <file:Documentation/networking/net-modules.txt>. The module will be
2148 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2149 depends on PCI && EXPERIMENTAL
2152 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2153 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2154 used by the Beowulf Linux cluster project. See
2155 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2156 information about this driver in particular and Beowulf in general.
2158 To compile this driver as a module, choose M here: the module
2159 will be called yellowfin. This is recommended.
2162 tristate "Realtek 8169 gigabit ethernet support"
2166 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2168 To compile this driver as a module, choose M here: the module
2169 will be called r8169. This is recommended.
2172 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2173 depends on R8169 && EXPERIMENTAL
2175 NAPI is a new driver API designed to reduce CPU and interrupt load
2176 when the driver is receiving lots of packets from the card. It is
2177 still somewhat experimental and thus not yet enabled by default.
2179 If your estimated Rx load is 10kpps or more, or if the card will be
2180 deployed on potentially unfriendly networks (e.g. in a firewall),
2183 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2190 depends on R8169 && VLAN_8021Q
2192 Say Y here for the r8169 driver to support the functions required
2193 by the kernel 802.1Q code.
2198 tristate "SiS190/SiS191 gigabit ethernet support"
2203 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2204 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2205 appear in lan on motherboard designs which are based on SiS 965
2206 and SiS 966 south bridge.
2208 To compile this driver as a module, choose M here: the module
2209 will be called sis190. This is recommended.
2212 tristate "New SysKonnect GigaEthernet support"
2216 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2217 and related Gigabit Ethernet adapters. It is a new smaller driver
2218 with better performance and more complete ethtool support.
2220 It does not support the link failover and network management
2221 features that "portable" vendor supplied sk98lin driver does.
2223 This driver supports adapters based on the original Yukon chipset:
2224 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2225 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2227 It does not support the newer Yukon2 chipset: a separate driver,
2228 sky2, is provided for Yukon2-based adapters.
2230 To compile this driver as a module, choose M here: the module
2231 will be called skge. This is recommended.
2234 tristate "SysKonnect Yukon2 support"
2238 This driver supports Gigabit Ethernet adapters based on the
2239 Marvell Yukon 2 chipset:
2240 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2241 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2243 There is companion driver for the older Marvell Yukon and
2244 Genesis based adapters: skge.
2246 To compile this driver as a module, choose M here: the module
2247 will be called sky2. This is recommended.
2250 bool "Debugging interface"
2251 depends on SKY2 && DEBUG_FS
2253 This option adds the ability to dump driver state for debugging.
2254 The file debugfs/sky2/ethX displays the state of the internal
2255 transmit and receive rings.
2260 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2263 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2264 compliant Gigabit Ethernet Adapter.
2266 This driver supports the original Yukon chipset. This driver is
2267 deprecated and will be removed from the kernel in the near future,
2268 it has been replaced by the skge driver. skge is cleaner and
2269 seems to work better.
2271 This driver does not support the newer Yukon2 chipset. A separate
2272 driver, sky2, is provided to support Yukon2-based adapters.
2274 The following adapters are supported by this driver:
2275 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2276 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2277 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2278 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2279 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2280 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2281 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2282 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2283 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2284 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2285 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2286 - EG1032 v2 Instant Gigabit Network Adapter
2287 - EG1064 v2 Instant Gigabit Network Adapter
2288 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2289 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2290 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2291 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2292 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2293 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2294 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2295 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2296 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2297 - Marvell RDK-8001 Adapter
2298 - Marvell RDK-8002 Adapter
2299 - Marvell RDK-8003 Adapter
2300 - Marvell RDK-8004 Adapter
2301 - Marvell RDK-8006 Adapter
2302 - Marvell RDK-8007 Adapter
2303 - Marvell RDK-8008 Adapter
2304 - Marvell RDK-8009 Adapter
2305 - Marvell RDK-8010 Adapter
2306 - Marvell RDK-8011 Adapter
2307 - Marvell RDK-8012 Adapter
2308 - Marvell RDK-8052 Adapter
2309 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2310 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2311 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2312 - SK-9521 10/100/1000Base-T Adapter
2313 - SK-9521 V2.0 10/100/1000Base-T Adapter
2314 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2315 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2316 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2317 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2318 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2319 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2320 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2321 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2322 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2323 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2324 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2325 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2326 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2327 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2328 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2329 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2330 - SMC EZ Card 1000 (SMC9452TXV.2)
2332 The adapters support Jumbo Frames.
2333 The dual link adapters support link-failover and dual port features.
2334 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2335 the scatter-gather functionality with sendfile(). Please refer to
2336 <file:Documentation/networking/sk98lin.txt> for more information about
2337 optional driver parameters.
2338 Questions concerning this driver may be addressed to:
2339 <linux@syskonnect.de>
2341 If you want to compile this driver as a module ( = code which can be
2342 inserted in and removed from the running kernel whenever you want),
2343 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2344 be called sk98lin. This is recommended.
2347 tristate "VIA Velocity support"
2353 If you have a VIA "Velocity" based network card say Y here.
2355 To compile this driver as a module, choose M here. The module
2356 will be called via-velocity.
2359 tristate "Broadcom Tigon3 support"
2362 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2364 To compile this driver as a module, choose M here: the module
2365 will be called tg3. This is recommended.
2368 tristate "Broadcom NetXtremeII support"
2373 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2375 To compile this driver as a module, choose M here: the module
2376 will be called bnx2. This is recommended.
2379 tristate "Spider Gigabit Ethernet driver"
2380 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2383 This driver supports the Gigabit Ethernet chips present on the
2384 Cell Processor-Based Blades from IBM.
2387 tristate "Tundra TSI108 gigabit Ethernet support"
2388 depends on TSI108_BRIDGE
2390 This driver supports Tundra TSI108 gigabit Ethernet ports.
2391 To compile this driver as a module, choose M here: the module
2392 will be called tsi108_eth.
2395 tristate "PS3 Gigabit Ethernet driver"
2398 This driver supports the network device on the PS3 game
2399 console. This driver has built-in support for Ethernet.
2401 To compile this driver as a module, choose M here: the
2402 module will be called ps3_gelic.
2405 tristate "Gianfar Ethernet"
2406 depends on 85xx || 83xx || PPC_86xx
2410 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2411 and MPC86xx family of chips, and the FEC on the 8540.
2418 tristate "Freescale QE Gigabit Ethernet"
2419 depends on QUICC_ENGINE
2422 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2423 which is available on some Freescale SOCs.
2429 config UGETH_MAGIC_PACKET
2430 bool "Magic Packet detection support"
2433 config UGETH_FILTERING
2434 bool "Mac address filtering support"
2437 config UGETH_TX_ON_DEMAND
2438 bool "Transmit on Demand support"
2442 tristate "MV-643XX Ethernet support"
2443 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32)
2446 This driver supports the gigabit Ethernet on the Marvell MV643XX
2447 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2448 Pegasos II, amongst other PPC and MIPS boards.
2451 tristate "QLogic QLA3XXX Network Driver Support"
2454 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2456 To compile this driver as a module, choose M here: the module
2457 will be called qla3xxx.
2460 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2461 depends on PCI && EXPERIMENTAL
2465 This driver supports the Attansic L1 gigabit ethernet adapter.
2467 To compile this driver as a module, choose M here. The module
2468 will be called atl1.
2473 # 10 Gigabit Ethernet
2476 menuconfig NETDEV_10000
2477 bool "Ethernet (10000 Mbit)"
2481 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2482 This option alone does not add any kernel code.
2484 If you say N, all options in this submenu will be skipped and disabled.
2489 tristate "Chelsio 10Gb Ethernet support"
2493 This driver supports Chelsio gigabit and 10-gigabit
2494 Ethernet cards. More information about adapter features and
2495 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2497 For general information about Chelsio and our products, visit
2498 our website at <http://www.chelsio.com>.
2500 For customer support, please visit our customer support page at
2501 <http://www.chelsio.com/support.htm>.
2503 Please send feedback to <linux-bugs@chelsio.com>.
2505 To compile this driver as a module, choose M here: the module
2506 will be called cxgb.
2508 config CHELSIO_T1_1G
2509 bool "Chelsio gigabit Ethernet support"
2510 depends on CHELSIO_T1
2512 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2513 are using only 10G cards say 'N' here.
2515 config CHELSIO_T1_NAPI
2516 bool "Use Rx Polling (NAPI)"
2517 depends on CHELSIO_T1
2520 NAPI is a driver API designed to reduce CPU and interrupt load
2521 when the driver is receiving lots of packets from the card.
2524 tristate "Chelsio Communications T3 10Gb Ethernet support"
2528 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2531 For general information about Chelsio and our products, visit
2532 our website at <http://www.chelsio.com>.
2534 For customer support, please visit our customer support page at
2535 <http://www.chelsio.com/support.htm>.
2537 Please send feedback to <linux-bugs@chelsio.com>.
2539 To compile this driver as a module, choose M here: the module
2540 will be called cxgb3.
2543 tristate "eHEA Ethernet support"
2547 This driver supports the IBM pSeries eHEA ethernet adapter.
2549 To compile the driver as a module, choose M here. The module
2550 will be called ehea.
2553 tristate "Intel(R) 10GbE PCI Express adapters support"
2556 This driver supports Intel(R) 10GbE PCI Express family of
2557 adapters. For more information on how to identify your adapter, go
2558 to the Adapter & Driver ID Guide at:
2560 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2562 For general information and support, go to the Intel support
2565 <http://support.intel.com>
2567 More specific information on configuring the driver is in
2568 <file:Documentation/networking/ixgbe.txt>.
2570 To compile this driver as a module, choose M here and read
2571 <file:Documentation/networking/net-modules.txt>. The module
2572 will be called ixgbe.
2575 tristate "Intel(R) PRO/10GbE support"
2578 This driver supports Intel(R) PRO/10GbE family of adapters for
2579 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2580 instead. For more information on how to identify your adapter, go
2581 to the Adapter & Driver ID Guide at:
2583 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2585 For general information and support, go to the Intel support
2588 <http://support.intel.com>
2590 More specific information on configuring the driver is in
2591 <file:Documentation/networking/ixgb.txt>.
2593 To compile this driver as a module, choose M here and read
2594 <file:Documentation/networking/net-modules.txt>. The module
2595 will be called ixgb.
2598 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2599 depends on IXGB && EXPERIMENTAL
2601 NAPI is a new driver API designed to reduce CPU and interrupt load
2602 when the driver is receiving lots of packets from the card. It is
2603 still somewhat experimental and thus not yet enabled by default.
2605 If your estimated Rx load is 10kpps or more, or if the card will be
2606 deployed on potentially unfriendly networks (e.g. in a firewall),
2609 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2615 tristate "S2IO 10Gbe XFrame NIC"
2618 This driver supports the 10Gbe XFrame NIC of S2IO.
2619 More specific information on configuring the driver is in
2620 <file:Documentation/networking/s2io.txt>.
2623 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2624 depends on S2IO && EXPERIMENTAL
2626 NAPI is a new driver API designed to reduce CPU and interrupt load
2627 when the driver is receiving lots of packets from the card. It is
2628 still somewhat experimental and thus not yet enabled by default.
2630 If your estimated Rx load is 10kpps or more, or if the card will be
2631 deployed on potentially unfriendly networks (e.g. in a firewall),
2634 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2640 tristate "Myricom Myri-10G Ethernet support"
2646 This driver supports Myricom Myri-10G Dual Protocol interface in
2647 Ethernet mode. If the eeprom on your board is not recent enough,
2648 you will need a newer firmware image.
2649 You may get this image or more information, at:
2651 <http://www.myri.com/scs/download-Myri10GE.html>
2653 To compile this driver as a module, choose M here and read
2654 <file:Documentation/networking/net-modules.txt>. The module
2655 will be called myri10ge.
2658 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2661 This enables the support for NetXen's Gigabit Ethernet card.
2664 tristate "PA Semi 1/10Gbit MAC"
2665 depends on PPC64 && PCI
2668 This driver supports the on-chip 1/10Gbit Ethernet controller on
2669 PA Semi's PWRficient line of chips.
2677 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2678 depends on MLX4_CORE
2681 This option causes debugging code to be compiled into the
2682 mlx4_core driver. The output can be turned on via the
2683 debug_level module parameter (which can also be set after
2684 the driver is loaded through sysfs).
2687 tristate "Tehuti Networks 10G Ethernet"
2690 Tehuti Networks 10G Ethernet NIC
2692 endif # NETDEV_10000
2694 source "drivers/net/tokenring/Kconfig"
2696 source "drivers/net/wireless/Kconfig"
2698 source "drivers/net/usb/Kconfig"
2700 source "drivers/net/pcmcia/Kconfig"
2702 source "drivers/net/wan/Kconfig"
2704 source "drivers/atm/Kconfig"
2706 source "drivers/s390/net/Kconfig"
2708 config XEN_NETDEV_FRONTEND
2709 tristate "Xen network device frontend driver"
2713 The network device frontend driver allows the kernel to
2714 access network devices exported exported by a virtual
2715 machine containing a physical network device driver. The
2716 frontend driver is intended for unprivileged guest domains;
2717 if you are compiling a kernel for a Xen guest, you almost
2718 certainly want to enable this.
2721 tristate "iSeries Virtual Ethernet driver support"
2722 depends on PPC_ISERIES
2725 tristate "RapidIO Ethernet over messaging driver support"
2728 config RIONET_TX_SIZE
2729 int "Number of outbound queue entries"
2733 config RIONET_RX_SIZE
2734 int "Number of inbound queue entries"
2739 bool "FDDI driver support"
2740 depends on (PCI || EISA || TC)
2742 Fiber Distributed Data Interface is a high speed local area network
2743 design; essentially a replacement for high speed Ethernet. FDDI can
2744 run over copper or fiber. If you are connected to such a network and
2745 want a driver for the FDDI card in your computer, say Y here (and
2746 then also Y to the driver for your FDDI card, below). Most people
2750 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2751 depends on FDDI && (PCI || EISA || TC)
2753 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2754 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2755 to a local FDDI network.
2757 To compile this driver as a module, choose M here: the module
2758 will be called defxx. If unsure, say N.
2762 prompt "Use MMIO instead of PIO" if PCI || EISA
2764 default n if PCI || EISA
2767 This instructs the driver to use EISA or PCI memory-mapped I/O
2768 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2769 Enabling this gives an improvement in processing time in parts
2770 of the driver, but it may cause problems with EISA (DEFEA)
2771 adapters. TURBOchannel does not have the concept of I/O ports,
2772 so MMIO is always used for these (DEFTA) adapters.
2777 tristate "SysKonnect FDDI PCI support"
2778 depends on FDDI && PCI
2781 Say Y here if you have a SysKonnect FDDI PCI adapter.
2782 The following adapters are supported by this driver:
2783 - SK-5521 (SK-NET FDDI-UP)
2784 - SK-5522 (SK-NET FDDI-UP DAS)
2785 - SK-5541 (SK-NET FDDI-FP)
2786 - SK-5543 (SK-NET FDDI-LP)
2787 - SK-5544 (SK-NET FDDI-LP DAS)
2788 - SK-5821 (SK-NET FDDI-UP64)
2789 - SK-5822 (SK-NET FDDI-UP64 DAS)
2790 - SK-5841 (SK-NET FDDI-FP64)
2791 - SK-5843 (SK-NET FDDI-LP64)
2792 - SK-5844 (SK-NET FDDI-LP64 DAS)
2793 - Netelligent 100 FDDI DAS Fibre SC
2794 - Netelligent 100 FDDI SAS Fibre SC
2795 - Netelligent 100 FDDI DAS UTP
2796 - Netelligent 100 FDDI SAS UTP
2797 - Netelligent 100 FDDI SAS Fibre MIC
2799 Read <file:Documentation/networking/skfp.txt> for information about
2802 Questions concerning this driver can be addressed to:
2803 <linux@syskonnect.de>
2805 To compile this driver as a module, choose M here: the module
2806 will be called skfp. This is recommended.
2809 bool "HIPPI driver support (EXPERIMENTAL)"
2810 depends on EXPERIMENTAL && INET && PCI
2812 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2813 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2814 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2815 single-mode). HIPPI networks are commonly used for clusters and to
2816 connect to super computers. If you are connected to a HIPPI network
2817 and have a HIPPI network card in your computer that you want to use
2818 under Linux, say Y here (you must also remember to enable the driver
2819 for your HIPPI card below). Most people will say N here.
2822 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2823 depends on HIPPI && PCI
2825 Say Y here if this is your PCI HIPPI network card.
2827 To compile this driver as a module, choose M here: the module
2828 will be called rrunner. If unsure, say N.
2830 config ROADRUNNER_LARGE_RINGS
2831 bool "Use large TX/RX rings (EXPERIMENTAL)"
2832 depends on ROADRUNNER
2834 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2835 of additional memory to allow for fastest operation, both for
2836 transmitting and receiving. This memory cannot be used by any other
2837 kernel code or by user space programs. Say Y here only if you have
2841 tristate "PLIP (parallel port) support"
2844 PLIP (Parallel Line Internet Protocol) is used to create a
2845 reasonably fast mini network consisting of two (or, rarely, more)
2846 local machines. A PLIP link from a Linux box is a popular means to
2847 install a Linux distribution on a machine which doesn't have a
2848 CD-ROM drive (a minimal system has to be transferred with floppies
2849 first). The kernels on both machines need to have this PLIP option
2850 enabled for this to work.
2852 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2853 ports (the connectors at the computers with 25 holes) are connected
2854 with "null printer" or "Turbo Laplink" cables which can transmit 4
2855 bits at a time (mode 0) or with special PLIP cables, to be used on
2856 bidirectional parallel ports only, which can transmit 8 bits at a
2857 time (mode 1); you can find the wiring of these cables in
2858 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2859 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2860 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2861 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2862 and winsock or NCSA's telnet.
2864 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2865 as the NET-3-HOWTO, both available from
2866 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2867 protocol has been changed and this PLIP driver won't work together
2868 with the PLIP support in Linux versions 1.0.x. This option enlarges
2869 your kernel by about 8 KB.
2871 To compile this driver as a module, choose M here and read
2872 <file:Documentation/networking/net-modules.txt>. The module will be
2873 called plip. If unsure, say Y or M, in case you buy a laptop
2877 tristate "PPP (point-to-point protocol) support"
2880 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2881 the same purpose: sending Internet traffic over telephone (and other
2882 serial) lines. Ask your access provider if they support it, because
2883 otherwise you can't use it; most Internet access providers these
2884 days support PPP rather than SLIP.
2886 To use PPP, you need an additional program called pppd as described
2887 in the PPP-HOWTO, available at
2888 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2889 the version of pppd recommended in <file:Documentation/Changes>.
2890 The PPP option enlarges your kernel by about 16 KB.
2892 There are actually two versions of PPP: the traditional PPP for
2893 asynchronous lines, such as regular analog phone lines, and
2894 synchronous PPP which can be used over digital ISDN lines for
2895 example. If you want to use PPP over phone lines or other
2896 asynchronous serial lines, you need to say Y (or M) here and also to
2897 the next option, "PPP support for async serial ports". For PPP over
2898 synchronous lines, you should say Y (or M) here and to "Support
2899 synchronous PPP", below.
2901 If you said Y to "Version information on all symbols" above, then
2902 you cannot compile the PPP driver into the kernel; you can then only
2903 compile it as a module. To compile this driver as a module, choose M
2904 here and read <file:Documentation/networking/net-modules.txt>.
2905 The module will be called ppp_generic.
2907 config PPP_MULTILINK
2908 bool "PPP multilink support (EXPERIMENTAL)"
2909 depends on PPP && EXPERIMENTAL
2911 PPP multilink is a protocol (defined in RFC 1990) which allows you
2912 to combine several (logical or physical) lines into one logical PPP
2913 connection, so that you can utilize your full bandwidth.
2915 This has to be supported at the other end as well and you need a
2916 version of the pppd daemon which understands the multilink protocol.
2921 bool "PPP filtering"
2924 Say Y here if you want to be able to filter the packets passing over
2925 PPP interfaces. This allows you to control which packets count as
2926 activity (i.e. which packets will reset the idle timer or bring up
2927 a demand-dialed link) and which packets are to be dropped entirely.
2928 You need to say Y here if you wish to use the pass-filter and
2929 active-filter options to pppd.
2934 tristate "PPP support for async serial ports"
2938 Say Y (or M) here if you want to be able to use PPP over standard
2939 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2940 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2943 To compile this driver as a module, choose M here.
2948 tristate "PPP support for sync tty ports"
2951 Say Y (or M) here if you want to be able to use PPP over synchronous
2952 (HDLC) tty devices, such as the SyncLink adapter. These devices
2953 are often used for high-speed leased lines like T1/E1.
2955 To compile this driver as a module, choose M here.
2958 tristate "PPP Deflate compression"
2963 Support for the Deflate compression method for PPP, which uses the
2964 Deflate algorithm (the same algorithm that gzip uses) to compress
2965 each PPP packet before it is sent over the wire. The machine at the
2966 other end of the PPP link (usually your ISP) has to support the
2967 Deflate compression method as well for this to be useful. Even if
2968 they don't support it, it is safe to say Y here.
2970 To compile this driver as a module, choose M here.
2973 tristate "PPP BSD-Compress compression"
2976 Support for the BSD-Compress compression method for PPP, which uses
2977 the LZW compression method to compress each PPP packet before it is
2978 sent over the wire. The machine at the other end of the PPP link
2979 (usually your ISP) has to support the BSD-Compress compression
2980 method as well for this to be useful. Even if they don't support it,
2981 it is safe to say Y here.
2983 The PPP Deflate compression method ("PPP Deflate compression",
2984 above) is preferable to BSD-Compress, because it compresses better
2987 Note that the BSD compression code will always be compiled as a
2988 module; it is called bsd_comp and will show up in the directory
2989 modules once you have said "make modules". If unsure, say N.
2992 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2993 depends on PPP && EXPERIMENTAL
2999 Support for the MPPE Encryption protocol, as employed by the
3000 Microsoft Point-to-Point Tunneling Protocol.
3002 See http://pptpclient.sourceforge.net/ for information on
3003 configuring PPTP clients and servers to utilize this method.
3006 tristate "PPP over Ethernet (EXPERIMENTAL)"
3007 depends on EXPERIMENTAL && PPP
3009 Support for PPP over Ethernet.
3011 This driver requires the latest version of pppd from the CVS
3012 repository at cvs.samba.org. Alternatively, see the
3013 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3014 which contains instruction on how to use this driver (under
3015 the heading "Kernel mode PPPoE").
3018 tristate "PPP over ATM"
3019 depends on ATM && PPP
3021 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3022 This implementation does not yet comply with section 8 of RFC2364,
3023 which can lead to bad results if the ATM peer loses state and
3024 changes its encapsulation unilaterally.
3027 tristate "PPP over L2TP (EXPERIMENTAL)"
3028 depends on EXPERIMENTAL && PPP && INET
3030 Support for PPP-over-L2TP socket family. L2TP is a protocol
3031 used by ISPs and enterprises to tunnel PPP traffic over UDP
3032 tunnels. L2TP is replacing PPTP for VPN uses.
3034 This kernel component handles only L2TP data packets: a
3035 userland daemon handles L2TP the control protocol (tunnel
3036 and session setup). One such daemon is OpenL2TP
3037 (http://openl2tp.sourceforge.net/).
3040 tristate "SLIP (serial line) support"
3042 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3043 connect to your Internet service provider or to connect to some
3044 other local Unix box or if you want to configure your Linux box as a
3045 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3046 Internet Protocol) is a protocol used to send Internet traffic over
3047 serial connections such as telephone lines or null modem cables;
3048 nowadays, the protocol PPP is more commonly used for this same
3051 Normally, your access provider has to support SLIP in order for you
3052 to be able to use it, but there is now a SLIP emulator called SLiRP
3053 around (available from
3054 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3055 allows you to use SLIP over a regular dial up shell connection. If
3056 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3057 NET-3-HOWTO, available from
3058 <http://www.tldp.org/docs.html#howto>, explains how to
3059 configure SLIP. Note that you don't need this option if you just
3060 want to run term (term is a program which gives you almost full
3061 Internet connectivity if you have a regular dial up shell account on
3062 some Internet connected Unix computer. Read
3063 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3064 support will enlarge your kernel by about 4 KB. If unsure, say N.
3066 To compile this driver as a module, choose M here and read
3067 <file:Documentation/networking/net-modules.txt>. The module will be
3070 config SLIP_COMPRESSED
3071 bool "CSLIP compressed headers"
3075 This protocol is faster than SLIP because it uses compression on the
3076 TCP/IP headers (not on the data itself), but it has to be supported
3077 on both ends. Ask your access provider if you are not sure and
3078 answer Y, just in case. You will still be able to use plain SLIP. If
3079 you plan to use SLiRP, the SLIP emulator (available from
3080 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3081 allows you to use SLIP over a regular dial up shell connection, you
3082 definitely want to say Y here. The NET-3-HOWTO, available from
3083 <http://www.tldp.org/docs.html#howto>, explains how to configure
3084 CSLIP. This won't enlarge your kernel.
3089 This option enables Van Jacobsen serial line header compression
3093 bool "Keepalive and linefill"
3096 Adds additional capabilities to the SLIP driver to support the
3097 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3100 config SLIP_MODE_SLIP6
3101 bool "Six bit SLIP encapsulation"
3104 Just occasionally you may need to run IP over hostile serial
3105 networks that don't pass all control characters or are only seven
3106 bit. Saying Y here adds an extra mode you can use with SLIP:
3107 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3108 the serial device. Naturally, this has to be supported at the other
3109 end of the link as well. It's good enough, for example, to run IP
3110 over the async ports of a Camtec JNT Pad. If unsure, say N.
3113 bool "Fibre Channel driver support"
3114 depends on SCSI && PCI
3116 Fibre Channel is a high speed serial protocol mainly used to connect
3117 large storage devices to the computer; it is compatible with and
3118 intended to replace SCSI.
3120 If you intend to use Fibre Channel, you need to have a Fibre channel
3121 adaptor card in your computer; say Y here and to the driver for your
3122 adaptor below. You also should have said Y to "SCSI support" and
3123 "SCSI generic support".
3126 tristate "Traffic Shaper (OBSOLETE)"
3127 depends on EXPERIMENTAL
3129 The traffic shaper is a virtual network device that allows you to
3130 limit the rate of outgoing data flow over some other network device.
3131 The traffic that you want to slow down can then be routed through
3132 these virtual devices. See
3133 <file:Documentation/networking/shaper.txt> for more information.
3135 An alternative to this traffic shaper are traffic schedulers which
3136 you'll get if you say Y to "QoS and/or fair queuing" in
3137 "Networking options".
3139 To compile this driver as a module, choose M here: the module
3140 will be called shaper. If unsure, say N.
3143 tristate "Network console logging support (EXPERIMENTAL)"
3144 depends on EXPERIMENTAL
3146 If you want to log kernel messages over the network, enable this.
3147 See <file:Documentation/networking/netconsole.txt> for details.
3149 config NETCONSOLE_DYNAMIC
3150 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3151 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3154 This option enables the ability to dynamically reconfigure target
3155 parameters (interface, IP addresses, port numbers, MAC addresses)
3156 at runtime through a userspace interface exported using configfs.
3157 See <file:Documentation/networking/netconsole.txt> for details.
3163 bool "Netpoll traffic trapping"
3167 config NET_POLL_CONTROLLER