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