3 # Network device configuration
6 menu "Network device support"
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
31 source "drivers/net/hnd/Kconfig"
34 tristate "Intermediate Functional Block support"
35 depends on NET_CLS_ACT
37 This is an intermediate driver that allows sharing of
39 To compile this driver as a module, choose M here: the module
40 will be called ifb. If you want to use more than one ifb
41 device at a time, you need to compile this driver as a module.
42 Instead of 'ifb', the devices will then be called 'ifb0',
44 Look at the iproute2 documentation directory for usage etc
47 tristate "Dummy net driver support"
49 This is essentially a bit-bucket device (i.e. traffic you send to
50 this device is consigned into oblivion) with a configurable IP
51 address. It is most commonly used in order to make your currently
52 inactive SLIP address seem like a real address for local programs.
53 If you use SLIP or PPP, you might want to say Y here. Since this
54 thing often comes in handy, the default is Y. It won't enlarge your
55 kernel either. What a deal. Read about it in the Network
56 Administrator's Guide, available from
57 <http://www.tldp.org/docs.html#guide>.
59 To compile this driver as a module, choose M here: the module
60 will be called dummy. If you want to use more than one dummy
61 device at a time, you need to compile this driver as a module.
62 Instead of 'dummy', the devices will then be called 'dummy0',
66 tristate "Bonding driver support"
69 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
70 Channels together. This is called 'Etherchannel' by Cisco,
71 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
73 The driver supports multiple bonding modes to allow for both high
74 performance and high availability operation.
76 Refer to <file:Documentation/networking/bonding.txt> for more
79 To compile this driver as a module, choose M here: the module
80 will be called bonding.
83 tristate "EQL (serial line load balancing) support"
85 If you have two serial connections to some other computer (this
86 usually requires two modems and two telephone lines) and you use
87 SLIP (the protocol for sending Internet traffic over telephone
88 lines) or PPP (a better SLIP) on them, you can make them behave like
89 one double speed connection using this driver. Naturally, this has
90 to be supported at the other end as well, either with a similar EQL
91 Linux driver or with a Livingston Portmaster 2e.
93 Say Y if you want this and read
94 <file:Documentation/networking/eql.txt>. You may also want to read
95 section 6.2 of the NET-3-HOWTO, available from
96 <http://www.tldp.org/docs.html#howto>.
98 To compile this driver as a module, choose M here: the module
99 will be called eql. If unsure, say N.
102 tristate "IMQ (intermediate queueing device) support"
103 depends on NETDEVICES && NETFILTER
105 The IMQ device(s) is used as placeholder for QoS queueing
106 disciplines. Every packet entering/leaving the IP stack can be
107 directed through the IMQ device where it's enqueued/dequeued to the
108 attached qdisc. This allows you to treat network devices as classes
109 and distribute bandwidth among them. Iptables is used to specify
110 through which IMQ device, if any, packets travel.
112 More information at: http://www.linuximq.net/
114 To compile this driver as a module, choose M here: the module
115 will be called imq. If unsure, say N.
118 prompt "IMQ behavior (PRE/POSTROUTING)"
120 default IMQ_BEHAVIOR_AB
123 This settings defines how IMQ behaves in respect to its
124 hooking in PREROUTING and POSTROUTING.
126 IMQ can work in any of the following ways:
128 PREROUTING | POSTROUTING
129 -----------------|-------------------
130 #1 After NAT | After NAT
131 #2 After NAT | Before NAT
132 #3 Before NAT | After NAT
133 #4 Before NAT | Before NAT
135 The default behavior is to hook before NAT on PREROUTING
136 and after NAT on POSTROUTING (#3).
138 You can change it later with the 'behaviour' module parameter
139 (if compiled as module) or 'imq.behaviour' kernel parameter.
141 This settings are specially usefull when trying to use IMQ
142 to shape NATed clients.
144 More information can be found at: www.linuximq.net
146 If not sure leave the default settings alone.
148 config IMQ_BEHAVIOR_AA
151 This settings defines how IMQ behaves in respect to its
152 hooking in PREROUTING and POSTROUTING.
154 Choosing this option will make IMQ hook like this:
156 PREROUTING: After NAT
157 POSTROUTING: After NAT
159 More information can be found at: www.linuximq.net
161 If not sure leave the default settings alone.
163 config IMQ_BEHAVIOR_AB
166 This settings defines how IMQ behaves in respect to its
167 hooking in PREROUTING and POSTROUTING.
169 Choosing this option will make IMQ hook like this:
171 PREROUTING: After NAT
172 POSTROUTING: Before NAT
174 More information can be found at: www.linuximq.net
176 If not sure leave the default settings alone.
178 config IMQ_BEHAVIOR_BA
181 This settings defines how IMQ behaves in respect to its
182 hooking in PREROUTING and POSTROUTING.
184 Choosing this option will make IMQ hook like this:
186 PREROUTING: Before NAT
187 POSTROUTING: After NAT
189 More information can be found at: www.linuximq.net
191 If not sure leave the default settings alone.
193 config IMQ_BEHAVIOR_BB
196 This settings defines how IMQ behaves in respect to its
197 hooking in PREROUTING and POSTROUTING.
199 Choosing this option will make IMQ hook like this:
201 PREROUTING: Before NAT
202 POSTROUTING: Before NAT
204 More information can be found at: www.linuximq.net
206 If not sure leave the default settings alone.
212 int "Number of IMQ devices"
218 This settings defines how many IMQ devices will be
221 The default value is 16.
223 More information can be found at: www.linuximq.net
225 If not sure leave the default settings alone.
228 tristate "Universal TUN/TAP device driver support"
231 TUN/TAP provides packet reception and transmission for user space
232 programs. It can be viewed as a simple Point-to-Point or Ethernet
233 device, which instead of receiving packets from a physical media,
234 receives them from user space program and instead of sending packets
235 via physical media writes them to the user space program.
237 When a program opens /dev/net/tun, driver creates and registers
238 corresponding net device tunX or tapX. After a program closed above
239 devices, driver will automatically delete tunXX or tapXX device and
240 all routes corresponding to it.
242 Please read <file:Documentation/networking/tuntap.txt> for more
245 To compile this driver as a module, choose M here: the module
248 If you don't know what to use this for, you don't need it.
251 tristate "General Instruments Surfboard 1000"
254 This is a driver for the General Instrument (also known as
255 NextLevel) SURFboard 1000 internal
256 cable modem. This is an ISA card which is used by a number of cable
257 TV companies to provide cable modem access. It's a one-way
258 downstream-only cable modem, meaning that your upstream net link is
259 provided by your regular phone modem.
261 At present this driver only compiles as a module, so say M here if
262 you have this card. The module will be called sb1000. Then read
263 <file:Documentation/networking/README.sb1000> for information on how
264 to use this module, as it needs special ppp scripts for establishing
265 a connection. Further documentation and the necessary scripts can be
268 <http://www.jacksonville.net/~fventuri/>
269 <http://home.adelphia.net/~siglercm/sb1000.html>
270 <http://linuxpower.cx/~cable/>
272 If you don't have this card, of course say N.
274 source "drivers/net/arcnet/Kconfig"
276 source "drivers/net/phy/Kconfig"
282 menu "Ethernet (10 or 100Mbit)"
286 bool "Ethernet (10 or 100Mbit)"
288 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
289 type of Local Area Network (LAN) in universities and companies.
291 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
292 coaxial cable, linking computers in a chain), 10BASE-T or twisted
293 pair (10 Mbps over twisted pair cable, linking computers to central
294 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
295 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
296 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
297 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
298 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
299 Ethernet (1 Gbps over optical fiber or short copper links).
301 If your Linux machine will be connected to an Ethernet and you have
302 an Ethernet network interface card (NIC) installed in your computer,
303 say Y here and read the Ethernet-HOWTO, available from
304 <http://www.tldp.org/docs.html#howto>. You will then also have
305 to say Y to the driver for your particular NIC.
307 Note that the answer to this question won't directly affect the
308 kernel: saying N will just cause the configurator to skip all
309 the questions about Ethernet network cards. If unsure, say N.
312 tristate "Generic Media Independent Interface device support"
313 depends on NET_ETHERNET
315 Most ethernet controllers have MII transceiver either as an external
316 or internal device. It is safe to say Y or M here even if your
317 ethernet card lack MII.
320 tristate "Atmel MACB support"
321 depends on NET_ETHERNET && (AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263)
324 The Atmel MACB ethernet interface is found on many AT32 and AT91
325 parts. Say Y to include support for the MACB chip.
327 To compile this driver as a module, choose M here: the module
330 source "drivers/net/arm/Kconfig"
333 tristate "MACE (Power Mac ethernet) support"
334 depends on NET_ETHERNET && PPC_PMAC && PPC32
337 Power Macintoshes and clones with Ethernet built-in on the
338 motherboard will usually use a MACE (Medium Access Control for
339 Ethernet) interface. Say Y to include support for the MACE chip.
341 To compile this driver as a module, choose M here: the module
344 config MACE_AAUI_PORT
345 bool "Use AAUI port instead of TP by default"
348 Some Apple machines (notably the Apple Network Server) which use the
349 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
350 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
351 Y here if you have such a machine. If unsure, say N.
352 The driver will default to AAUI on ANS anyway, and if you use it as
353 a module, you can provide the port_aaui=0|1 to force the driver.
356 tristate "BMAC (G3 ethernet) support"
357 depends on NET_ETHERNET && PPC_PMAC && PPC32
360 Say Y for support of BMAC Ethernet interfaces. These are used on G3
363 To compile this driver as a module, choose M here: the module
367 tristate "Ariadne support"
368 depends on NET_ETHERNET && ZORRO
370 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
373 To compile this driver as a module, choose M here: the module
374 will be called ariadne.
377 tristate "A2065 support"
378 depends on NET_ETHERNET && ZORRO
381 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
384 To compile this driver as a module, choose M here: the module
385 will be called a2065.
388 tristate "Hydra support"
389 depends on NET_ETHERNET && ZORRO
392 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
394 To compile this driver as a module, choose M here: the module
395 will be called hydra.
398 tristate "Zorro NS8390-based Ethernet support"
399 depends on NET_ETHERNET && ZORRO
402 This driver is for Zorro Ethernet cards using an NS8390-compatible
403 chipset, like the Village Tronic Ariadne II and the Individual
404 Computers X-Surf Ethernet cards. If you have such a card, say Y.
407 To compile this driver as a module, choose M here: the module
408 will be called zorro8390.
411 tristate "PCMCIA NE2000 support"
412 depends on NET_ETHERNET && AMIGA_PCMCIA
415 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
418 To compile this driver as a module, choose M here: the module
422 tristate "Apollo 3c505 support"
423 depends on NET_ETHERNET && APOLLO
425 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
426 If you don't have one made for Apollos, you can use one from a PC,
427 except that your Apollo won't be able to boot from it (because the
428 code in the ROM will be for a PC).
431 bool "Macintosh NS 8390 based ethernet cards"
432 depends on NET_ETHERNET && MAC
435 If you want to include a driver to support Nubus or LC-PDS
436 Ethernet cards using an NS8390 chipset or its equivalent, say Y
437 and read the Ethernet-HOWTO, available from
438 <http://www.tldp.org/docs.html#howto>.
441 tristate "Macintosh CS89x0 based ethernet cards"
442 depends on NET_ETHERNET && MAC
444 Support for CS89x0 chipset based Ethernet cards. If you have a
445 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
446 read the Ethernet-HOWTO, available from
447 <http://www.tldp.org/docs.html#howto>.
449 To compile this driver as a module, choose M here and read
450 <file:Documentation/networking/net-modules.txt>. This module will
454 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
455 depends on NET_ETHERNET && MAC
457 Support for NatSemi SONIC based Ethernet devices. This includes
458 the onboard Ethernet in many Quadras as well as some LC-PDS,
459 a few Nubus and all known Comm Slot Ethernet cards. If you have
460 one of these say Y and read the Ethernet-HOWTO, available from
461 <http://www.tldp.org/docs.html#howto>.
463 To compile this driver as a module, choose M here and read
464 <file:Documentation/networking/net-modules.txt>. This module will
468 bool "Macintosh (AV) onboard MACE ethernet"
469 depends on NET_ETHERNET && MAC
472 Support for the onboard AMD 79C940 MACE Ethernet controller used in
473 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
474 say Y and read the Ethernet-HOWTO, available from
475 <http://www.tldp.org/docs.html#howto>.
478 tristate "MVME147 (Lance) Ethernet support"
479 depends on NET_ETHERNET && MVME147
482 Support for the on-board Ethernet interface on the Motorola MVME147
483 single-board computer. Say Y here to include the
484 driver for this chip in your kernel.
485 To compile this driver as a module, choose M here.
488 tristate "MVME16x Ethernet support"
489 depends on NET_ETHERNET && MVME16x
491 This is the driver for the Ethernet interface on the Motorola
492 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
493 driver for this chip in your kernel.
494 To compile this driver as a module, choose M here.
497 tristate "BVME6000 Ethernet support"
498 depends on NET_ETHERNET && BVME6000
500 This is the driver for the Ethernet interface on BVME4000 and
501 BVME6000 VME boards. Say Y here to include the driver for this chip
503 To compile this driver as a module, choose M here.
506 tristate "Atari Lance support"
507 depends on NET_ETHERNET && ATARI
509 Say Y to include support for several Atari Ethernet adapters based
510 on the AMD Lance chipset: RieblCard (with or without battery), or
511 PAMCard VME (also the version by Rhotron, with different addresses).
514 tristate "BioNet-100 support"
515 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
517 Say Y to include support for BioData's BioNet-100 Ethernet adapter
518 for the ACSI port. The driver works (has to work...) with a polled
519 I/O scheme, so it's rather slow :-(
522 tristate "PAMsNet support"
523 depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
525 Say Y to include support for the PAMsNet Ethernet adapter for the
526 ACSI port ("ACSI node"). The driver works (has to work...) with a
527 polled I/O scheme, so it's rather slow :-(
530 tristate "Sun3/Sun3x on-board LANCE support"
531 depends on NET_ETHERNET && (SUN3 || SUN3X)
533 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
534 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
535 here to compile in the Linux driver for this and enable Ethernet.
536 General Linux information on the Sun 3 and 3x series (now
538 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
540 If you're not building a kernel for a Sun 3, say N.
543 bool "Sun3 on-board Intel 82586 support"
544 depends on NET_ETHERNET && SUN3
546 This driver enables support for the on-board Intel 82586 based
547 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
548 that this driver does not support 82586-based adapters on additional
552 bool "HP on-board LANCE support"
553 depends on NET_ETHERNET && DIO
556 If you want to use the builtin "LANCE" Ethernet controller on an
557 HP300 machine, say Y here.
560 tristate "Lasi ethernet"
561 depends on NET_ETHERNET && GSC
563 Say Y here to support the builtin Intel 82596 ethernet controller
564 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
566 config MIPS_JAZZ_SONIC
567 tristate "MIPS JAZZ onboard SONIC Ethernet support"
568 depends on NET_ETHERNET && MACH_JAZZ
570 This is the driver for the onboard card of MIPS Magnum 4000,
571 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
573 config GALILEO_64240_ETH
574 tristate "Galileo GT64240 Ethernet support"
575 depends on NET_ETHERNET && MOMENCO_OCELOT_G
578 This is the driver for the ethernet interfaces integrated into
579 the Galileo (now Marvell) GT64240 chipset.
581 config MIPS_AU1X00_ENET
582 bool "MIPS AU1000 Ethernet support"
583 depends on NET_ETHERNET && SOC_AU1X00
587 If you have an Alchemy Semi AU1X00 based system
588 say Y. Otherwise, say N.
591 bool "SGI IOC3 Ethernet"
592 depends on NET_ETHERNET && PCI && SGI_IP27
596 If you have a network (Ethernet) card of this type, say Y and read
597 the Ethernet-HOWTO, available from
598 <http://www.tldp.org/docs.html#howto>.
601 tristate "MIPS simulator Network device"
602 depends on NET_ETHERNET && MIPS_SIM
604 The MIPSNET device is a simple Ethernet network device which is
605 emulated by the MIPS Simulator.
606 If you are not using a MIPSsim or are unsure, say N.
608 config SGI_O2MACE_ETH
609 tristate "SGI O2 MACE Fast Ethernet support"
610 depends on NET_ETHERNET && SGI_IP32=y
613 tristate "National DP83902AV support"
614 depends on NET_ETHERNET && SUPERH
617 Support for cards based on the National Semiconductor DP83902AV
618 ST-NIC Serial Network Interface Controller for Twisted Pair. This
619 is a 10Mbit/sec Ethernet controller. Product overview and specs at
620 <http://www.national.com/pf/DP/DP83902A.html>.
625 tristate "Sun LANCE support"
626 depends on NET_ETHERNET && SBUS
629 This driver supports the "le" interface present on all 32-bit Sparc
630 systems, on some older Ultra systems and as an Sbus option. These
631 cards are based on the AMD Lance chipset, which is better known
632 via the NE2100 cards.
634 To compile this driver as a module, choose M here: the module
635 will be called sunlance.
638 tristate "Sun Happy Meal 10/100baseT support"
639 depends on NET_ETHERNET && (SBUS || PCI)
642 This driver supports the "hme" interface present on most Ultra
643 systems and as an option on older Sbus systems. This driver supports
644 both PCI and Sbus devices. This driver also supports the "qfe" quad
645 100baseT device available in both PCI and Sbus configurations.
647 To compile this driver as a module, choose M here: the module
648 will be called sunhme.
651 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
652 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
655 This driver supports the "be" interface available as an Sbus option.
656 This is Sun's older 100baseT Ethernet device.
658 To compile this driver as a module, choose M here: the module
659 will be called sunbmac.
662 tristate "Sun QuadEthernet support"
663 depends on NET_ETHERNET && SBUS
666 This driver supports the "qe" 10baseT Ethernet device, available as
667 an Sbus option. Note that this is not the same as Quad FastEthernet
668 "qfe" which is supported by the Happy Meal driver instead.
670 To compile this driver as a module, choose M here: the module
671 will be called sunqe.
674 tristate "Sun GEM support"
675 depends on NET_ETHERNET && PCI
678 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
679 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
682 tristate "Sun Cassini support"
683 depends on NET_ETHERNET && PCI
686 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
687 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
689 config NET_VENDOR_3COM
691 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
693 If you have a network (Ethernet) card belonging to this class, say Y
694 and read the Ethernet-HOWTO, available from
695 <http://www.tldp.org/docs.html#howto>.
697 Note that the answer to this question doesn't directly affect the
698 kernel: saying N will just cause the configurator to skip all
699 the questions about 3COM cards. If you say Y, you will be asked for
700 your specific card in the following questions.
703 tristate "3c501 \"EtherLink\" support"
704 depends on NET_VENDOR_3COM && ISA
706 If you have a network (Ethernet) card of this type, say Y and read
707 the Ethernet-HOWTO, available from
708 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
709 new card, since the 3c501 is slow, broken, and obsolete: you will
710 have problems. Some people suggest to ping ("man ping") a nearby
711 machine every minute ("man cron") when using this card.
713 To compile this driver as a module, choose M here and read
714 <file:Documentation/networking/net-modules.txt>. The module
715 will be called 3c501.
718 tristate "3c503 \"EtherLink II\" support"
719 depends on NET_VENDOR_3COM && ISA
722 If you have a network (Ethernet) card of this type, say Y and read
723 the Ethernet-HOWTO, available from
724 <http://www.tldp.org/docs.html#howto>.
726 To compile this driver as a module, choose M here and read
727 <file:Documentation/networking/net-modules.txt>. The module
728 will be called 3c503.
731 tristate "3c505 \"EtherLink Plus\" support"
732 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
734 Information about this network (Ethernet) card can be found in
735 <file:Documentation/networking/3c505.txt>. If you have a card of
736 this type, say Y and read the Ethernet-HOWTO, available from
737 <http://www.tldp.org/docs.html#howto>.
739 To compile this driver as a module, choose M here and read
740 <file:Documentation/networking/net-modules.txt>. The module
741 will be called 3c505.
744 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
745 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
747 If you have a network (Ethernet) card of this type, say Y and read
748 the Ethernet-HOWTO, available from
749 <http://www.tldp.org/docs.html#howto>.
751 To compile this driver as a module, choose M here and read
752 <file:Documentation/networking/net-modules.txt>. The module
753 will be called 3c507.
756 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
757 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
759 If you have a network (Ethernet) card belonging to the 3Com
760 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
761 from <http://www.tldp.org/docs.html#howto>.
763 If your card is not working you may need to use the DOS
764 setup disk to disable Plug & Play mode, and to select the default
767 To compile this driver as a module, choose M here and read
768 <file:Documentation/networking/net-modules.txt>. The module
769 will be called 3c509.
772 tristate "3c515 ISA \"Fast EtherLink\""
773 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
775 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
776 network card, say Y and read the Ethernet-HOWTO, available from
777 <http://www.tldp.org/docs.html#howto>.
779 To compile this driver as a module, choose M here and read
780 <file:Documentation/networking/net-modules.txt>. The module
781 will be called 3c515.
784 tristate "3c523 \"EtherLink/MC\" support"
785 depends on NET_VENDOR_3COM && MCA_LEGACY
787 If you have a network (Ethernet) card of this type, say Y and read
788 the Ethernet-HOWTO, available from
789 <http://www.tldp.org/docs.html#howto>.
791 To compile this driver as a module, choose M here and read
792 <file:Documentation/networking/net-modules.txt>. The module
793 will be called 3c523.
796 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
797 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
799 If you have a network (Ethernet) card of this type, say Y and read
800 the Ethernet-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>.
803 To compile this driver as a module, choose M here and read
804 <file:Documentation/networking/net-modules.txt>. The module
805 will be called 3c527.
808 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
809 depends on NET_VENDOR_3COM && (PCI || EISA)
812 This option enables driver support for a large number of 10Mbps and
813 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
815 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
816 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
817 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
818 "Tornado" (3c905) PCI
819 "Hurricane" (3c555/3cSOHO) PCI
821 If you have such a card, say Y and read the Ethernet-HOWTO,
822 available from <http://www.tldp.org/docs.html#howto>. More
823 specific information is in
824 <file:Documentation/networking/vortex.txt> and in the comments at
825 the beginning of <file:drivers/net/3c59x.c>.
827 To compile this support as a module, choose M here and read
828 <file:Documentation/networking/net-modules.txt>.
831 tristate "3cr990 series \"Typhoon\" support"
832 depends on NET_VENDOR_3COM && PCI
835 This option enables driver support for the 3cr990 series of cards:
837 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
838 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
839 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
841 If you have a network (Ethernet) card of this type, say Y and read
842 the Ethernet-HOWTO, available from
843 <http://www.tldp.org/docs.html#howto>.
845 To compile this driver as a module, choose M here and read
846 <file:Documentation/networking/net-modules.txt>. The module
847 will be called typhoon.
850 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
851 depends on NET_ETHERNET && ISA && ISA_DMA_API
853 If you have a network (Ethernet) card of this type, say Y and read
854 the Ethernet-HOWTO, available from
855 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
858 To compile this driver as a module, choose M here: the module
859 will be called lance. This is recommended.
861 config NET_VENDOR_SMC
862 bool "Western Digital/SMC cards"
863 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
865 If you have a network (Ethernet) card belonging to this class, say Y
866 and read the Ethernet-HOWTO, available from
867 <http://www.tldp.org/docs.html#howto>.
869 Note that the answer to this question doesn't directly affect the
870 kernel: saying N will just cause the configurator to skip all
871 the questions about Western Digital cards. If you say Y, you will be
872 asked for your specific card in the following questions.
875 tristate "WD80*3 support"
876 depends on NET_VENDOR_SMC && ISA
879 If you have a network (Ethernet) card of this type, say Y and read
880 the Ethernet-HOWTO, available from
881 <http://www.tldp.org/docs.html#howto>.
883 To compile this driver as a module, choose M here and read
884 <file:Documentation/networking/net-modules.txt>. The module
888 tristate "SMC Ultra MCA support"
889 depends on NET_VENDOR_SMC && MCA
892 If you have a network (Ethernet) card of this type and are running
893 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
894 available from <http://www.tldp.org/docs.html#howto>.
896 To compile this driver as a module, choose M here and read
897 <file:Documentation/networking/net-modules.txt>. The module
898 will be called smc-mca.
901 tristate "SMC Ultra support"
902 depends on NET_VENDOR_SMC && ISA
905 If you have a network (Ethernet) card of this type, say Y and read
906 the Ethernet-HOWTO, available from
907 <http://www.tldp.org/docs.html#howto>.
909 Important: There have been many reports that, with some motherboards
910 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
911 such as some BusLogic models) causes corruption problems with many
912 operating systems. The Linux smc-ultra driver has a work-around for
913 this but keep it in mind if you have such a SCSI card and have
916 To compile this driver as a module, choose M here and read
917 <file:Documentation/networking/net-modules.txt>. The module
918 will be called smc-ultra.
921 tristate "SMC Ultra32 EISA support"
922 depends on NET_VENDOR_SMC && EISA
925 If you have a network (Ethernet) card of this type, say Y and read
926 the Ethernet-HOWTO, available from
927 <http://www.tldp.org/docs.html#howto>.
929 To compile this driver as a module, choose M here and read
930 <file:Documentation/networking/net-modules.txt>. The module
931 will be called smc-ultra32.
934 tristate "SMC 91C9x/91C1xxx support"
937 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN)
939 This is a driver for SMC's 91x series of Ethernet chipsets,
940 including the SMC91C94 and the SMC91C111. Say Y if you want it
941 compiled into the kernel, and read the file
942 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
943 available from <http://www.linuxdoc.org/docs.html#howto>.
945 This driver is also available as a module ( = code which can be
946 inserted in and removed from the running kernel whenever you want).
947 The module will be called smc91x. If you want to compile it as a
948 module, say M here and read <file:Documentation/kbuild/modules.txt>
949 as well as <file:Documentation/networking/net-modules.txt>.
952 tristate "SMC 9194 support"
953 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
956 This is support for the SMC9xxx based Ethernet cards. Choose this
957 option if you have a DELL laptop with the docking station, or
958 another SMC9192/9194 based chipset. Say Y if you want it compiled
959 into the kernel, and read the file
960 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
961 available from <http://www.tldp.org/docs.html#howto>.
963 To compile this driver as a module, choose M here and read
964 <file:Documentation/networking/net-modules.txt>. The module
965 will be called smc9194.
968 tristate "NetX Ethernet support"
970 depends on NET_ETHERNET && ARCH_NETX
972 This is support for the Hilscher netX builtin Ethernet ports
974 To compile this driver as a module, choose M here and read
975 <file:Documentation/networking/net-modules.txt>. The module
976 will be called netx-eth.
979 tristate "DM9000 support"
980 depends on (ARM || MIPS) && NET_ETHERNET
984 Support for DM9000 chipset.
986 To compile this driver as a module, choose M here and read
987 <file:Documentation/networking/net-modules.txt>. The module will be
991 tristate "SMSC LAN911[5678] support"
994 depends on NET_ETHERNET && ARCH_PXA
996 This is a driver for SMSC's LAN911x series of Ethernet chipsets
997 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
998 Say Y if you want it compiled into the kernel,
999 and read the Ethernet-HOWTO, available from
1000 <http://www.linuxdoc.org/docs.html#howto>.
1002 This driver is also available as a module. The module will be
1003 called smc911x. If you want to compile it as a module, say M
1004 here and read <file:Documentation/kbuild/modules.txt>
1006 config NET_VENDOR_RACAL
1007 bool "Racal-Interlan (Micom) NI cards"
1008 depends on NET_ETHERNET && ISA
1010 If you have a network (Ethernet) card belonging to this class, such
1011 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1012 available from <http://www.tldp.org/docs.html#howto>.
1014 Note that the answer to this question doesn't directly affect the
1015 kernel: saying N will just cause the configurator to skip all
1016 the questions about NI cards. If you say Y, you will be asked for
1017 your specific card in the following questions.
1020 tristate "NI5010 support (EXPERIMENTAL)"
1021 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1023 If you have a network (Ethernet) card of this type, say Y and read
1024 the Ethernet-HOWTO, available from
1025 <http://www.tldp.org/docs.html#howto>. Note that this is still
1028 To compile this driver as a module, choose M here and read
1029 <file:Documentation/networking/net-modules.txt>. The module
1030 will be called ni5010.
1033 tristate "NI5210 support"
1034 depends on NET_VENDOR_RACAL && ISA
1036 If you have a network (Ethernet) card of this type, say Y and read
1037 the Ethernet-HOWTO, available from
1038 <http://www.tldp.org/docs.html#howto>.
1040 To compile this driver as a module, choose M here and read
1041 <file:Documentation/networking/net-modules.txt>. The module
1042 will be called ni52.
1045 tristate "NI6510 support"
1046 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1048 If you have a network (Ethernet) card of this type, say Y and read
1049 the Ethernet-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto>.
1052 To compile this driver as a module, choose M here and read
1053 <file:Documentation/networking/net-modules.txt>. The module
1054 will be called ni65.
1056 source "drivers/net/tulip/Kconfig"
1059 tristate "AT1700/1720 support (EXPERIMENTAL)"
1060 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
1063 If you have a network (Ethernet) card of this type, say Y and read
1064 the Ethernet-HOWTO, available from
1065 <http://www.tldp.org/docs.html#howto>.
1067 To compile this driver as a module, choose M here and read
1068 <file:Documentation/networking/net-modules.txt>. The module
1069 will be called at1700.
1072 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1073 depends on NET_ETHERNET && (ISA || EISA || MCA)
1076 If you have a network (Ethernet) card of this type, say Y and read
1077 the Ethernet-HOWTO, available from
1078 <http://www.tldp.org/docs.html#howto> as well as
1079 <file:drivers/net/depca.c>.
1081 To compile this driver as a module, choose M here and read
1082 <file:Documentation/networking/net-modules.txt>. The module
1083 will be called depca.
1086 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1087 depends on NET_ETHERNET && (ISA || EISA || PCI)
1089 If you have a network (Ethernet) card of this type, say Y and read
1090 the Ethernet-HOWTO, available from
1091 <http://www.tldp.org/docs.html#howto>.
1093 To compile this driver as a module, choose M here and read
1094 <file:Documentation/networking/net-modules.txt>. The module
1095 will be called hp100.
1098 bool "Other ISA cards"
1099 depends on NET_ETHERNET && ISA
1101 If your network (Ethernet) card hasn't been mentioned yet and its
1102 bus system (that's the way the cards talks to the other components
1103 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1104 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1105 available from <http://www.tldp.org/docs.html#howto>.
1109 Note that the answer to this question doesn't directly affect the
1110 kernel: saying N will just cause the configurator to skip all
1111 the remaining ISA network card questions. If you say Y, you will be
1112 asked for your specific card in the following questions.
1115 tristate "Cabletron E21xx support"
1119 If you have a network (Ethernet) card of this type, say Y and read
1120 the Ethernet-HOWTO, available from
1121 <http://www.tldp.org/docs.html#howto>.
1123 To compile this driver as a module, choose M here and read
1124 <file:Documentation/networking/net-modules.txt>. The module
1125 will be called e2100.
1128 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1132 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1133 cards. If this is for you, say Y and read
1134 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1135 well as the Ethernet-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1138 To compile this driver as a module, choose M here and read
1139 <file:Documentation/networking/net-modules.txt>. The module
1140 will be called ewrk3.
1143 tristate "EtherExpress 16 support"
1146 If you have an EtherExpress16 network (Ethernet) card, say Y and
1147 read the Ethernet-HOWTO, available from
1148 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1149 EtherExpress16 card used to be regarded as a very poor choice
1150 because the driver was very unreliable. We now have a new driver
1151 that should do better.
1153 To compile this driver as a module, choose M here and read
1154 <file:Documentation/networking/net-modules.txt>. The module
1155 will be called eexpress.
1158 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1161 If you have a network (Ethernet) card of this type, say Y. This
1162 driver supports Intel i82595{FX,TX} based boards. Note however
1163 that the EtherExpress PRO/100 Ethernet card has its own separate
1164 driver. Please read the Ethernet-HOWTO, available from
1165 <http://www.tldp.org/docs.html#howto>.
1167 To compile this driver as a module, choose M here and read
1168 <file:Documentation/networking/net-modules.txt>. The module
1169 will be called eepro.
1172 tristate "HP PCLAN+ (27247B and 27252A) support"
1176 If you have a network (Ethernet) card of this type, say Y and read
1177 the Ethernet-HOWTO, available from
1178 <http://www.tldp.org/docs.html#howto>.
1180 To compile this driver as a module, choose M here and read
1181 <file:Documentation/networking/net-modules.txt>. The module
1182 will be called hp-plus.
1185 tristate "HP PCLAN (27245 and other 27xxx series) support"
1189 If you have a network (Ethernet) card of this type, say Y and read
1190 the Ethernet-HOWTO, available from
1191 <http://www.tldp.org/docs.html#howto>.
1193 To compile this driver as a module, choose M here and read
1194 <file:Documentation/networking/net-modules.txt>. The module
1198 tristate "LP486E on board Ethernet"
1201 Say Y here to support the 82596-based on-board Ethernet controller
1202 for the Panther motherboard, which is one of the two shipped in the
1203 Intel Professional Workstation.
1206 tristate "ICL EtherTeam 16i/32 support"
1209 If you have a network (Ethernet) card of this type, say Y and read
1210 the Ethernet-HOWTO, available from
1211 <http://www.tldp.org/docs.html#howto>.
1213 To compile this driver as a module, choose M here and read
1214 <file:Documentation/networking/net-modules.txt>. The module
1215 will be called eth16i.
1218 tristate "NE2000/NE1000 support"
1219 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1222 If you have a network (Ethernet) card of this type, say Y and read
1223 the Ethernet-HOWTO, available from
1224 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1225 without a specific driver are compatible with NE2000.
1227 If you have a PCI NE2000 card however, say N here and Y to "PCI
1228 NE2000 and clone support" under "EISA, VLB, PCI and on board
1229 controllers" below. If you have a NE2000 card and are running on
1230 an MCA system (a bus system used on some IBM PS/2 computers and
1231 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1234 To compile this driver as a module, choose M here and read
1235 <file:Documentation/networking/net-modules.txt>. The module
1239 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1240 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1242 The Zenith Z-Note notebook computer has a built-in network
1243 (Ethernet) card, and this is the Linux driver for it. Note that the
1244 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1245 by this driver. Read the Ethernet-HOWTO, available from
1246 <http://www.tldp.org/docs.html#howto>.
1249 tristate "SEEQ8005 support (EXPERIMENTAL)"
1250 depends on NET_ISA && EXPERIMENTAL
1252 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1253 is for you, read the Ethernet-HOWTO, available from
1254 <http://www.tldp.org/docs.html#howto>.
1256 To compile this driver as a module, choose M here and read
1257 <file:Documentation/networking/net-modules.txt>. The module
1258 will be called seeq8005.
1261 tristate "NE/2 (ne2000 MCA version) support"
1262 depends on NET_ETHERNET && MCA_LEGACY
1265 If you have a network (Ethernet) card of this type, say Y and read
1266 the Ethernet-HOWTO, available from
1267 <http://www.tldp.org/docs.html#howto>.
1269 To compile this driver as a module, choose M here and read
1270 <file:Documentation/networking/net-modules.txt>. The module
1274 tristate "IBM LAN Adapter/A support"
1275 depends on NET_ETHERNET && MCA && MCA_LEGACY
1277 This is a Micro Channel Ethernet adapter. You need to set
1278 CONFIG_MCA to use this driver. It is both available as an in-kernel
1279 driver and as a module.
1281 To compile this driver as a module, choose M here and read
1282 <file:Documentation/networking/net-modules.txt>. The only
1283 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1284 will both support 16K and 32K memory windows, however a 32K window
1285 gives a better security against packet losses. Usage of multiple
1286 boards with this driver should be possible, but has not been tested
1287 up to now due to lack of hardware.
1290 tristate "IBM LAN Virtual Ethernet support"
1291 depends on NET_ETHERNET && PPC_PSERIES
1293 This driver supports virtual ethernet adapters on newer IBM iSeries
1294 and pSeries systems.
1296 To compile this driver as a module, choose M here and read
1297 <file:Documentation/networking/net-modules.txt>. The module will
1301 tristate "PowerPC 4xx on-chip Ethernet support"
1302 depends on 4xx && !PPC_MERGE
1304 This driver supports the PowerPC 4xx EMAC family of on-chip
1305 Ethernet controllers.
1308 int "Number of receive buffers"
1313 int "Number of transmit buffers"
1317 config IBM_EMAC_POLL_WEIGHT
1318 int "MAL NAPI polling weight"
1322 config IBM_EMAC_RX_COPY_THRESHOLD
1323 int "RX skb copy threshold (bytes)"
1327 config IBM_EMAC_RX_SKB_HEADROOM
1328 int "Additional RX skb headroom (bytes)"
1332 Additional receive skb headroom. Note, that driver
1333 will always reserve at least 2 bytes to make IP header
1334 aligned, so usually there is no need to add any additional
1337 If unsure, set to 0.
1339 config IBM_EMAC_PHY_RX_CLK_FIX
1340 bool "PHY Rx clock workaround"
1341 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1343 Enable this if EMAC attached to a PHY which doesn't generate
1344 RX clock if there is no link, if this is the case, you will
1345 see "TX disable timeout" or "RX disable timeout" in the system
1350 config IBM_EMAC_DEBUG
1355 config IBM_EMAC_ZMII
1357 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1360 config IBM_EMAC_RGMII
1362 depends on IBM_EMAC && 440GX
1367 depends on IBM_EMAC && 440GX
1371 bool "EISA, VLB, PCI and on board controllers"
1372 depends on NET_ETHERNET && (ISA || EISA || PCI)
1374 This is another class of network cards which attach directly to the
1375 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1376 available from <http://www.tldp.org/docs.html#howto>.
1378 Note that the answer to this question doesn't directly affect the
1379 kernel: saying N will just cause the configurator to skip all
1380 the questions about this class of network cards. If you say Y, you
1381 will be asked for your specific card in the following questions. If
1382 you are unsure, say Y.
1385 tristate "AMD PCnet32 PCI support"
1386 depends on NET_PCI && PCI
1390 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1391 answer Y here and read the Ethernet-HOWTO, available from
1392 <http://www.tldp.org/docs.html#howto>.
1394 To compile this driver as a module, choose M here and read
1395 <file:Documentation/networking/net-modules.txt>. The module
1396 will be called pcnet32.
1399 bool "Use RX polling (NAPI)"
1402 NAPI is a new driver API designed to reduce CPU and interrupt load
1403 when the driver is receiving lots of packets from the card. It is
1404 still somewhat experimental and thus not yet enabled by default.
1406 If your estimated Rx load is 10kpps or more, or if the card will be
1407 deployed on potentially unfriendly networks (e.g. in a firewall),
1410 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1416 tristate "AMD 8111 (new PCI lance) support"
1417 depends on NET_PCI && PCI
1421 If you have an AMD 8111-based PCI lance ethernet card,
1422 answer Y here and read the Ethernet-HOWTO, available from
1423 <http://www.tldp.org/docs.html#howto>.
1425 To compile this driver as a module, choose M here and read
1426 <file:Documentation/networking/net-modules.txt>. The module
1427 will be called amd8111e.
1428 config AMD8111E_NAPI
1429 bool "Enable NAPI support"
1430 depends on AMD8111_ETH
1432 NAPI is a new driver API designed to reduce CPU and interrupt load
1433 when the driver is receiving lots of packets from the card. It is
1434 still somewhat experimental and thus not yet enabled by default.
1436 If your estimated Rx load is 10kpps or more, or if the card will be
1437 deployed on potentially unfriendly networks (e.g. in a firewall),
1440 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1445 config ADAPTEC_STARFIRE
1446 tristate "Adaptec Starfire/DuraLAN support"
1447 depends on NET_PCI && PCI
1451 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1452 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1453 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1456 To compile this driver as a module, choose M here: the module
1457 will be called starfire. This is recommended.
1459 config ADAPTEC_STARFIRE_NAPI
1460 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1461 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1463 NAPI is a new driver API designed to reduce CPU and interrupt load
1464 when the driver is receiving lots of packets from the card. It is
1465 still somewhat experimental and thus not yet enabled by default.
1467 If your estimated Rx load is 10kpps or more, or if the card will be
1468 deployed on potentially unfriendly networks (e.g. in a firewall),
1471 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1477 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1478 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1481 If you have a network (Ethernet) card of this type, say Y and read
1482 the Ethernet-HOWTO, available from
1483 <http://www.tldp.org/docs.html#howto>.
1485 To compile this driver as a module, choose M here and read
1486 <file:Documentation/networking/net-modules.txt>. The module
1487 will be called ac3200.
1490 tristate "Apricot Xen-II on board Ethernet"
1491 depends on NET_PCI && ISA
1493 If you have a network (Ethernet) controller of this type, say Y and
1494 read the Ethernet-HOWTO, available from
1495 <http://www.tldp.org/docs.html#howto>.
1497 To compile this driver as a module, choose M here and read
1498 <file:Documentation/networking/net-modules.txt>. The module will be
1502 tristate "Broadcom 4400 ethernet support"
1503 depends on NET_PCI && PCI
1506 If you have a network (Ethernet) controller of this type, say Y and
1507 read the Ethernet-HOWTO, available from
1508 <http://www.tldp.org/docs.html#howto>.
1510 To compile this driver as a module, choose M here and read
1511 <file:Documentation/networking/net-modules.txt>. The module will be
1515 tristate "nForce Ethernet support"
1516 depends on NET_PCI && PCI
1518 If you have a network (Ethernet) controller of this type, say Y and
1519 read the Ethernet-HOWTO, available from
1520 <http://www.tldp.org/docs.html#howto>.
1522 To compile this driver as a module, choose M here and read
1523 <file:Documentation/networking/net-modules.txt>. The module will be
1526 config FORCEDETH_NAPI
1527 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1528 depends on FORCEDETH && EXPERIMENTAL
1530 NAPI is a new driver API designed to reduce CPU and interrupt load
1531 when the driver is receiving lots of packets from the card. It is
1532 still somewhat experimental and thus not yet enabled by default.
1534 If your estimated Rx load is 10kpps or more, or if the card will be
1535 deployed on potentially unfriendly networks (e.g. in a firewall),
1538 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1544 tristate "CS89x0 support"
1545 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1547 Support for CS89x0 chipset based Ethernet cards. If you have a
1548 network (Ethernet) card of this type, say Y and read the
1549 Ethernet-HOWTO, available from
1550 <http://www.tldp.org/docs.html#howto> as well as
1551 <file:Documentation/networking/cs89x0.txt>.
1553 To compile this driver as a module, choose M here and read
1554 <file:Documentation/networking/net-modules.txt>. The module will be
1558 tristate "TOSHIBA TC35815 Ethernet support"
1559 depends on NET_PCI && PCI && MIPS
1563 tristate "Digi Intl. RightSwitch SE-X support"
1564 depends on NET_PCI && (PCI || EISA)
1566 This is support for the Digi International RightSwitch series of
1567 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1568 models. If you have a network card of this type, say Y and read the
1569 Ethernet-HOWTO, available from
1570 <http://www.tldp.org/docs.html#howto>. More specific
1571 information is contained in <file:Documentation/networking/dgrs.txt>.
1573 To compile this driver as a module, choose M here and read
1574 <file:Documentation/networking/net-modules.txt>. The module
1575 will be called dgrs.
1578 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1579 depends on NET_PCI && PCI
1582 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1583 card, say Y and read the Ethernet-HOWTO, available from
1584 <http://www.tldp.org/docs.html#howto>.
1586 To compile this driver as a module, choose M here and read
1587 <file:Documentation/networking/net-modules.txt>. The module
1588 will be called eepro100.
1592 tristate "Intel(R) PRO/100+ support"
1593 depends on NET_PCI && PCI
1596 This driver supports Intel(R) PRO/100 family of adapters.
1597 To verify that your adapter is supported, find the board ID number
1598 on the adapter. Look for a label that has a barcode and a number
1599 in the format 123456-001 (six digits hyphen three digits).
1601 Use the above information and the Adapter & Driver ID Guide at:
1603 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1605 to identify the adapter.
1607 For the latest Intel PRO/100 network driver for Linux, see:
1609 <http://appsr.intel.com/scripts-df/support_intel.asp>
1611 More specific information on configuring the driver is in
1612 <file:Documentation/networking/e100.txt>.
1614 To compile this driver as a module, choose M here and read
1615 <file:Documentation/networking/net-modules.txt>. The module
1616 will be called e100.
1619 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1620 depends on NET_PCI && EISA && EXPERIMENTAL
1623 If you have a network (Ethernet) card of this type, say Y and read
1624 the Ethernet-HOWTO, available from
1625 <http://www.tldp.org/docs.html#howto>.
1627 To compile this driver as a module, choose M here and read
1628 <file:Documentation/networking/net-modules.txt>. The module
1629 will be called lne390.
1632 tristate "Myson MTD-8xx PCI Ethernet support"
1633 depends on NET_PCI && PCI
1637 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1638 cards. Specifications and data at
1639 <http://www.myson.com.hk/mtd/datasheet/>.
1642 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1643 depends on NET_PCI && PCI
1646 This driver is for the National Semiconductor DP83810 series,
1647 which is used in cards from PureData, NetGear, Linksys
1648 and others, including the 83815 chip.
1649 More specific information and updates are available from
1650 <http://www.scyld.com/network/natsemi.html>.
1653 tristate "PCI NE2000 and clones support (see help)"
1654 depends on NET_PCI && PCI
1657 This driver is for NE2000 compatible PCI cards. It will not work
1658 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1659 support" below). If you have a PCI NE2000 network (Ethernet) card,
1660 say Y and read the Ethernet-HOWTO, available from
1661 <http://www.tldp.org/docs.html#howto>.
1663 This driver also works for the following NE2000 clone cards:
1664 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1665 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1666 Holtek HT80232 Holtek HT80229
1668 To compile this driver as a module, choose M here and read
1669 <file:Documentation/networking/net-modules.txt>. The module
1670 will be called ne2k-pci.
1673 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1674 depends on NET_PCI && EISA && EXPERIMENTAL
1677 If you have a network (Ethernet) card of this type, say Y and read
1678 the Ethernet-HOWTO, available from
1679 <http://www.tldp.org/docs.html#howto>. Note that this driver
1680 will NOT WORK for NE3200 cards as they are completely different.
1682 To compile this driver as a module, choose M here and read
1683 <file:Documentation/networking/net-modules.txt>. The module
1684 will be called ne3210.
1687 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1688 depends on NET_PCI && EISA && EXPERIMENTAL
1691 If you have a network (Ethernet) card of this type, say Y and read
1692 the Ethernet-HOWTO, available from
1693 <http://www.tldp.org/docs.html#howto>.
1695 To compile this driver as a module, choose M here and read
1696 <file:Documentation/networking/net-modules.txt>. The module
1697 will be called es3210.
1700 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1701 depends on NET_PCI && PCI && EXPERIMENTAL
1705 This is a driver for the Fast Ethernet PCI network cards based on
1706 the RTL8139C+ chips. If you have one of those, say Y and read
1707 the Ethernet-HOWTO, available from
1708 <http://www.tldp.org/docs.html#howto>.
1710 To compile this driver as a module, choose M here: the module
1711 will be called 8139cp. This is recommended.
1714 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1715 depends on NET_PCI && PCI
1719 This is a driver for the Fast Ethernet PCI network cards based on
1720 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1721 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1723 To compile this driver as a module, choose M here: the module
1724 will be called 8139too. This is recommended.
1727 bool "Use PIO instead of MMIO"
1731 This instructs the driver to use programmed I/O ports (PIO) instead
1732 of PCI shared memory (MMIO). This can possibly solve some problems
1733 in case your mainboard has memory consistency issues. If unsure,
1736 config 8139TOO_TUNE_TWISTER
1737 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1740 This implements a function which might come in handy in case you
1741 are using low quality on long cabling. It is required for RealTek
1742 RTL-8139 revision K boards, and totally unused otherwise. It tries
1743 to match the transceiver to the cable characteristics. This is
1744 experimental since hardly documented by the manufacturer.
1748 bool "Support for older RTL-8129/8130 boards"
1751 This enables support for the older and uncommon RTL-8129 and
1752 RTL-8130 chips, which support MII via an external transceiver,
1753 instead of an internal one. Disabling this option will save some
1754 memory by making the code size smaller. If unsure, say Y.
1756 config 8139_OLD_RX_RESET
1757 bool "Use older RX-reset method"
1760 The 8139too driver was recently updated to contain a more rapid
1761 reset sequence, in the face of severe receive errors. This "new"
1762 RX-reset method should be adequate for all boards. But if you
1763 experience problems, you can enable this option to restore the
1764 old RX-reset behavior. If unsure, say N.
1767 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1768 depends on NET_PCI && PCI
1772 This is a driver for the Fast Ethernet PCI network cards based on
1773 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1774 SiS 630 and SiS 540 chipsets.
1776 This driver also supports AMD 79C901 HomePNA so that you can use
1777 your phone line as a network cable.
1779 To compile this driver as a module, choose M here: the module
1780 will be called sis900. This is recommended.
1783 tristate "SMC EtherPower II"
1784 depends on NET_PCI && PCI
1788 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1789 which is based on the SMC83c17x (EPIC/100).
1790 More specific information and updates are available from
1791 <http://www.scyld.com/network/epic100.html>.
1794 tristate "Sundance Alta support"
1795 depends on NET_PCI && PCI
1799 This driver is for the Sundance "Alta" chip.
1800 More specific information and updates are available from
1801 <http://www.scyld.com/network/sundance.html>.
1803 config SUNDANCE_MMIO
1804 bool "Use MMIO instead of PIO"
1807 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1808 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1809 is known to solve bugs on certain chips.
1814 tristate "TI ThunderLAN support"
1815 depends on NET_PCI && (PCI || EISA) && !64BIT
1817 If you have a PCI Ethernet network card based on the ThunderLAN chip
1818 which is supported by this driver, say Y and read the
1819 Ethernet-HOWTO, available from
1820 <http://www.tldp.org/docs.html#howto>.
1822 Devices currently supported by this driver are Compaq Netelligent,
1823 Compaq NetFlex and Olicom cards. Please read the file
1824 <file:Documentation/networking/tlan.txt> for more details.
1826 To compile this driver as a module, choose M here and read
1827 <file:Documentation/networking/net-modules.txt>. The module
1828 will be called tlan.
1830 Please email feedback to <torben.mathiasen@compaq.com>.
1833 tristate "VIA Rhine support"
1834 depends on NET_PCI && PCI
1838 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1839 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1840 Ethernet functions can also be found integrated on South Bridges
1843 To compile this driver as a module, choose M here. The module
1844 will be called via-rhine.
1846 config VIA_RHINE_MMIO
1847 bool "Use MMIO instead of PIO"
1848 depends on VIA_RHINE
1850 This instructs the driver to use PCI shared memory (MMIO) instead of
1851 programmed I/O ports (PIO). Enabling this gives an improvement in
1852 processing time in parts of the driver.
1856 config VIA_RHINE_NAPI
1857 bool "Use Rx Polling (NAPI)"
1858 depends on VIA_RHINE
1860 NAPI is a new driver API designed to reduce CPU and interrupt load
1861 when the driver is receiving lots of packets from the card.
1863 If your estimated Rx load is 10kpps or more, or if the card will be
1864 deployed on potentially unfriendly networks (e.g. in a firewall),
1867 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1871 bool "Philips SAA9730 Ethernet support"
1872 depends on NET_PCI && PCI && MIPS_ATLAS
1874 The SAA9730 is a combined multimedia and peripheral controller used
1875 in thin clients, Internet access terminals, and diskless
1877 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1880 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1881 depends on NET_PCI && PCI && EXPERIMENTAL
1884 This is a driver for the Fast Ethernet PCI network cards based on
1885 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1886 have one of these, say Y here.
1888 To compile this driver as a module, choose M here: the module
1889 will be called sc92031. This is recommended.
1892 bool "Pocket and portable adapters"
1893 depends on NET_ETHERNET && PARPORT
1895 Cute little network (Ethernet) devices which attach to the parallel
1896 port ("pocket adapters"), commonly used with laptops. If you have
1897 one of those, say Y and read the Ethernet-HOWTO, available from
1898 <http://www.tldp.org/docs.html#howto>.
1900 If you want to plug a network (or some other) card into the PCMCIA
1901 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1902 credit card size extension cards used by all modern laptops), you
1903 need the pcmcia-cs package (location contained in the file
1904 <file:Documentation/Changes>) and you can say N here.
1906 Laptop users should read the Linux Laptop home page at
1907 <http://www.linux-on-laptops.com/> or
1908 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1910 Note that the answer to this question doesn't directly affect the
1911 kernel: saying N will just cause the configurator to skip all
1912 the questions about this class of network devices. If you say Y, you
1913 will be asked for your specific device in the following questions.
1916 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1917 depends on NET_POCKET && PARPORT && X86
1920 This is a network (Ethernet) device which attaches to your parallel
1921 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1922 available from <http://www.tldp.org/docs.html#howto>, if you
1923 want to use this. If you intend to use this driver, you should have
1924 said N to the "Parallel printer support", because the two drivers
1925 don't like each other.
1927 To compile this driver as a module, choose M here: the module
1931 tristate "D-Link DE600 pocket adapter support"
1932 depends on NET_POCKET && PARPORT
1934 This is a network (Ethernet) device which attaches to your parallel
1935 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1936 Ethernet-HOWTO, available from
1937 <http://www.tldp.org/docs.html#howto>, if you want to use
1938 this. It is possible to have several devices share a single parallel
1939 port and it is safe to compile the corresponding drivers into the
1942 To compile this driver as a module, choose M here: the module
1943 will be called de600.
1946 tristate "D-Link DE620 pocket adapter support"
1947 depends on NET_POCKET && PARPORT
1949 This is a network (Ethernet) device which attaches to your parallel
1950 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1951 Ethernet-HOWTO, available from
1952 <http://www.tldp.org/docs.html#howto>, if you want to use
1953 this. It is possible to have several devices share a single parallel
1954 port and it is safe to compile the corresponding drivers into the
1957 To compile this driver as a module, choose M here: the module
1958 will be called de620.
1961 tristate "SGI Seeq ethernet controller support"
1962 depends on NET_ETHERNET && SGI_IP22
1964 Say Y here if you have an Seeq based Ethernet network card. This is
1965 used in many Silicon Graphics machines.
1968 tristate "DEC LANCE ethernet controller support"
1969 depends on NET_ETHERNET && MACH_DECSTATION
1972 This driver is for the series of Ethernet controllers produced by
1973 DEC (now Compaq) based on the AMD Lance chipset, including the
1974 DEPCA series. (This chipset is better known via the NE2100 cards.)
1977 bool "Motorola 68360 ethernet controller"
1980 Say Y here if you want to use the built-in ethernet controller of
1981 the Motorola 68360 processor.
1984 bool "FEC ethernet controller (of ColdFire CPUs)"
1985 depends on M523x || M527x || M5272 || M528x || M520x
1987 Say Y here if you want to use the built-in 10/100 Fast ethernet
1988 controller on some Motorola ColdFire processors.
1991 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1994 Say Y here if you want to use the second built-in 10/100 Fast
1995 ethernet controller on some Motorola ColdFire processors.
1998 tristate "NE2000 compatible support for H8/300"
1999 depends on H8300 && NET_ETHERNET
2001 Say Y here if you want to use the NE2000 compatible
2002 controller on the Renesas H8/300 processor.
2004 source "drivers/net/fec_8xx/Kconfig"
2005 source "drivers/net/fs_enet/Kconfig"
2013 menuconfig NETDEV_1000
2014 bool "Ethernet (1000 Mbit)"
2021 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2024 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2025 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2026 adapter. The driver allows for using the Jumbo Frame option (9000
2027 bytes/frame) however it requires that your switches can handle this
2028 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2031 To compile this driver as a module, choose M here: the
2032 module will be called acenic.
2034 config ACENIC_OMIT_TIGON_I
2035 bool "Omit support for old Tigon I based AceNICs"
2038 Say Y here if you only have Tigon II based AceNICs and want to leave
2039 out support for the older Tigon I based cards which are no longer
2040 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2041 version)). This will reduce the size of the driver object by
2042 app. 100KB. If you are not sure whether your card is a Tigon I or a
2043 Tigon II, say N here.
2045 The safe and default value for this is N.
2048 tristate "D-Link DL2000-based Gigabit Ethernet support"
2052 This driver supports D-Link 2000-based gigabit ethernet cards, which
2054 D-Link DGE-550T Gigabit Ethernet Adapter.
2055 D-Link DL2000-based Gigabit Ethernet Adapter.
2057 To compile this driver as a module, choose M here: the
2058 module will be called dl2k.
2061 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2064 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2065 adapters. For more information on how to identify your adapter, go
2066 to the Adapter & Driver ID Guide at:
2068 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2070 For general information and support, go to the Intel support
2073 <http://support.intel.com>
2075 More specific information on configuring the driver is in
2076 <file:Documentation/networking/e1000.txt>.
2078 To compile this driver as a module, choose M here and read
2079 <file:Documentation/networking/net-modules.txt>. The module
2080 will be called e1000.
2083 bool "Use Rx Polling (NAPI)"
2086 NAPI is a new driver API designed to reduce CPU and interrupt load
2087 when the driver is receiving lots of packets from the card. It is
2088 still somewhat experimental and thus not yet enabled by default.
2090 If your estimated Rx load is 10kpps or more, or if the card will be
2091 deployed on potentially unfriendly networks (e.g. in a firewall),
2094 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2099 config E1000_DISABLE_PACKET_SPLIT
2100 bool "Disable Packet Split for PCI express adapters"
2103 Say Y here if you want to use the legacy receive path for PCI express
2108 source "drivers/net/ixp2000/Kconfig"
2111 tristate "MyriCOM Gigabit Ethernet support"
2114 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2116 To compile this driver as a module, choose M here: the module
2117 will be called myri_sbus. This is recommended.
2120 tristate "National Semiconductor DP83820 support"
2123 This is a driver for the National Semiconductor DP83820 series
2124 of gigabit ethernet MACs. Cards using this chipset include
2125 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2126 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2130 tristate "Packet Engines Hamachi GNIC-II support"
2134 If you have a Gigabit Ethernet card of this type, say Y and read
2135 the Ethernet-HOWTO, available from
2136 <http://www.tldp.org/docs.html#howto>.
2138 To compile this driver as a module, choose M here and read
2139 <file:Documentation/networking/net-modules.txt>. The module will be
2143 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2144 depends on PCI && EXPERIMENTAL
2147 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2148 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2149 used by the Beowulf Linux cluster project. See
2150 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2151 information about this driver in particular and Beowulf in general.
2153 To compile this driver as a module, choose M here: the module
2154 will be called yellowfin. This is recommended.
2157 tristate "Realtek 8169 gigabit ethernet support"
2161 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2163 To compile this driver as a module, choose M here: the module
2164 will be called r8169. This is recommended.
2167 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2168 depends on R8169 && EXPERIMENTAL
2170 NAPI is a new driver API designed to reduce CPU and interrupt load
2171 when the driver is receiving lots of packets from the card. It is
2172 still somewhat experimental and thus not yet enabled by default.
2174 If your estimated Rx load is 10kpps or more, or if the card will be
2175 deployed on potentially unfriendly networks (e.g. in a firewall),
2178 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2183 config NET_SB1250_MAC
2184 tristate "SB1250 Ethernet support"
2185 depends on SIBYTE_SB1xxx_SOC
2189 depends on R8169 && VLAN_8021Q
2191 Say Y here for the r8169 driver to support the functions required
2192 by the kernel 802.1Q code.
2197 tristate "SiS190/SiS191 gigabit ethernet support"
2202 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2203 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2204 appear in lan on motherboard designs which are based on SiS 965
2205 and SiS 966 south bridge.
2207 To compile this driver as a module, choose M here: the module
2208 will be called sis190. This is recommended.
2211 tristate "New SysKonnect GigaEthernet support"
2215 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2216 and related Gigabit Ethernet adapters. It is a new smaller driver
2217 with better performance and more complete ethtool support.
2219 It does not support the link failover and network management
2220 features that "portable" vendor supplied sk98lin driver does.
2222 This driver supports adapters based on the original Yukon chipset:
2223 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2224 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2226 It does not support the newer Yukon2 chipset: a separate driver,
2227 sky2, is provided for Yukon2-based adapters.
2229 To compile this driver as a module, choose M here: the module
2230 will be called skge. This is recommended.
2233 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2237 This driver supports Gigabit Ethernet adapters based on the
2238 Marvell Yukon 2 chipset:
2239 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2240 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2242 There is companion driver for the older Marvell Yukon and
2243 Genesis based adapters: skge.
2245 To compile this driver as a module, choose M here: the module
2246 will be called sky2. This is recommended.
2249 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2252 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2253 compliant Gigabit Ethernet Adapter.
2255 This driver supports the original Yukon chipset. This driver is
2256 deprecated and will be removed from the kernel in the near future,
2257 it has been replaced by the skge driver. skge is cleaner and
2258 seems to work better.
2260 This driver does not support the newer Yukon2 chipset. A separate
2261 driver, sky2, is provided to support Yukon2-based adapters.
2263 The following adapters are supported by this driver:
2264 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2265 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2266 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2267 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2268 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2269 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2270 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2271 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2272 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2273 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2274 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2275 - EG1032 v2 Instant Gigabit Network Adapter
2276 - EG1064 v2 Instant Gigabit Network Adapter
2277 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2278 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2279 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2280 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2281 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2282 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2283 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2284 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2285 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2286 - Marvell RDK-8001 Adapter
2287 - Marvell RDK-8002 Adapter
2288 - Marvell RDK-8003 Adapter
2289 - Marvell RDK-8004 Adapter
2290 - Marvell RDK-8006 Adapter
2291 - Marvell RDK-8007 Adapter
2292 - Marvell RDK-8008 Adapter
2293 - Marvell RDK-8009 Adapter
2294 - Marvell RDK-8010 Adapter
2295 - Marvell RDK-8011 Adapter
2296 - Marvell RDK-8012 Adapter
2297 - Marvell RDK-8052 Adapter
2298 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2299 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2300 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2301 - SK-9521 10/100/1000Base-T Adapter
2302 - SK-9521 V2.0 10/100/1000Base-T Adapter
2303 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2304 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2305 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2306 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2307 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2308 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2309 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2310 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2311 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2312 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2313 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2314 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2315 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2316 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2317 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2318 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2319 - SMC EZ Card 1000 (SMC9452TXV.2)
2321 The adapters support Jumbo Frames.
2322 The dual link adapters support link-failover and dual port features.
2323 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2324 the scatter-gather functionality with sendfile(). Please refer to
2325 <file:Documentation/networking/sk98lin.txt> for more information about
2326 optional driver parameters.
2327 Questions concerning this driver may be addressed to:
2328 <linux@syskonnect.de>
2330 If you want to compile this driver as a module ( = code which can be
2331 inserted in and removed from the running kernel whenever you want),
2332 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2333 be called sk98lin. This is recommended.
2336 tristate "VIA Velocity support"
2342 If you have a VIA "Velocity" based network card say Y here.
2344 To compile this driver as a module, choose M here. The module
2345 will be called via-velocity.
2348 tristate "Broadcom Tigon3 support"
2351 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2353 To compile this driver as a module, choose M here: the module
2354 will be called tg3. This is recommended.
2357 tristate "Broadcom NetXtremeII support"
2362 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2364 To compile this driver as a module, choose M here: the module
2365 will be called bnx2. This is recommended.
2368 tristate "Spider Gigabit Ethernet driver"
2369 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2372 This driver supports the Gigabit Ethernet chips present on the
2373 Cell Processor-Based Blades from IBM.
2376 tristate "Tundra TSI108 gigabit Ethernet support"
2377 depends on TSI108_BRIDGE
2379 This driver supports Tundra TSI108 gigabit Ethernet ports.
2380 To compile this driver as a module, choose M here: the module
2381 will be called tsi108_eth.
2384 tristate "Gianfar Ethernet"
2385 depends on 85xx || 83xx || PPC_86xx
2389 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2390 and MPC86xx family of chips, and the FEC on the 8540.
2397 tristate "Freescale QE Gigabit Ethernet"
2398 depends on QUICC_ENGINE
2401 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2402 which is available on some Freescale SOCs.
2408 config UGETH_MAGIC_PACKET
2409 bool "Magic Packet detection support"
2412 config UGETH_FILTERING
2413 bool "Mac address filtering support"
2416 config UGETH_TX_ON_DEMAND
2417 bool "Transmit on Demand support"
2421 tristate "MV-643XX Ethernet support"
2422 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MV64X60 || MOMENCO_OCELOT_3 || (PPC_MULTIPLATFORM && PPC32)
2425 This driver supports the gigabit Ethernet on the Marvell MV643XX
2426 chipset which is used in the Momenco Ocelot C Ocelot, Jaguar ATX
2427 and Pegasos II, amongst other PPC and MIPS boards.
2430 bool "PMC-Sierra TITAN Fast Ethernet Support"
2431 depends on NET_ETHERNET && PMC_BIG_SUR
2433 This enables support for the the integrated ethernet of
2434 PMC-Sierra's Big Sur SoC.
2437 bool "PMC-Sierra TITAN Gigabit Ethernet Support"
2438 depends on PMC_YOSEMITE
2440 This enables support for the the integrated ethernet of
2441 PMC-Sierra's Titan SoC.
2444 tristate "QLogic QLA3XXX Network Driver Support"
2447 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2449 To compile this driver as a module, choose M here: the module
2450 will be called qla3xxx.
2453 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2454 depends on PCI && EXPERIMENTAL
2458 This driver supports the Attansic L1 gigabit ethernet adapter.
2460 To compile this driver as a module, choose M here. The module
2461 will be called atl1.
2466 # 10 Gigabit Ethernet
2469 menuconfig NETDEV_10000
2470 bool "Ethernet (10000 Mbit)"
2477 tristate "Chelsio 10Gb Ethernet support"
2481 This driver supports Chelsio gigabit and 10-gigabit
2482 Ethernet cards. More information about adapter features and
2483 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2485 For general information about Chelsio and our products, visit
2486 our website at <http://www.chelsio.com>.
2488 For customer support, please visit our customer support page at
2489 <http://www.chelsio.com/support.htm>.
2491 Please send feedback to <linux-bugs@chelsio.com>.
2493 To compile this driver as a module, choose M here: the module
2494 will be called cxgb.
2496 config CHELSIO_T1_1G
2497 bool "Chelsio gigabit Ethernet support"
2498 depends on CHELSIO_T1
2500 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2501 are using only 10G cards say 'N' here.
2503 config CHELSIO_T1_NAPI
2504 bool "Use Rx Polling (NAPI)"
2505 depends on CHELSIO_T1
2508 NAPI is a driver API designed to reduce CPU and interrupt load
2509 when the driver is receiving lots of packets from the card.
2512 tristate "Chelsio Communications T3 10Gb Ethernet support"
2516 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2519 For general information about Chelsio and our products, visit
2520 our website at <http://www.chelsio.com>.
2522 For customer support, please visit our customer support page at
2523 <http://www.chelsio.com/support.htm>.
2525 Please send feedback to <linux-bugs@chelsio.com>.
2527 To compile this driver as a module, choose M here: the module
2528 will be called cxgb3.
2531 tristate "eHEA Ethernet support"
2534 This driver supports the IBM pSeries eHEA ethernet adapter.
2536 To compile the driver as a module, choose M here. The module
2537 will be called ehea.
2540 tristate "Intel(R) PRO/10GbE support"
2543 This driver supports Intel(R) PRO/10GbE family of
2544 adapters. For more information on how to identify your adapter, go
2545 to the Adapter & Driver ID Guide at:
2547 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2549 For general information and support, go to the Intel support
2552 <http://support.intel.com>
2554 More specific information on configuring the driver is in
2555 <file:Documentation/networking/ixgb.txt>.
2557 To compile this driver as a module, choose M here and read
2558 <file:Documentation/networking/net-modules.txt>. The module
2559 will be called ixgb.
2562 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2563 depends on IXGB && EXPERIMENTAL
2565 NAPI is a new driver API designed to reduce CPU and interrupt load
2566 when the driver is receiving lots of packets from the card. It is
2567 still somewhat experimental and thus not yet enabled by default.
2569 If your estimated Rx load is 10kpps or more, or if the card will be
2570 deployed on potentially unfriendly networks (e.g. in a firewall),
2573 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2579 tristate "S2IO 10Gbe XFrame NIC"
2582 This driver supports the 10Gbe XFrame NIC of S2IO.
2583 More specific information on configuring the driver is in
2584 <file:Documentation/networking/s2io.txt>.
2587 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2588 depends on S2IO && EXPERIMENTAL
2590 NAPI is a new driver API designed to reduce CPU and interrupt load
2591 when the driver is receiving lots of packets from the card. It is
2592 still somewhat experimental and thus not yet enabled by default.
2594 If your estimated Rx load is 10kpps or more, or if the card will be
2595 deployed on potentially unfriendly networks (e.g. in a firewall),
2598 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2604 tristate "Myricom Myri-10G Ethernet support"
2609 This driver supports Myricom Myri-10G Dual Protocol interface in
2610 Ethernet mode. If the eeprom on your board is not recent enough,
2611 you will need a newer firmware image.
2612 You may get this image or more information, at:
2614 <http://www.myri.com/scs/download-Myri10GE.html>
2616 To compile this driver as a module, choose M here and read
2617 <file:Documentation/networking/net-modules.txt>. The module
2618 will be called myri10ge.
2621 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2624 This enables the support for NetXen's Gigabit Ethernet card.
2627 tristate "PA Semi 1/10Gbit MAC"
2628 depends on PPC64 && PCI
2631 This driver supports the on-chip 1/10Gbit Ethernet controller on
2632 PA Semi's PWRficient line of chips.
2640 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2641 depends on MLX4_CORE
2644 This option causes debugging code to be compiled into the
2645 mlx4_core driver. The output can be turned on via the
2646 debug_level module parameter (which can also be set after
2647 the driver is loaded through sysfs).
2649 endif # NETDEV_10000
2651 source "drivers/net/tokenring/Kconfig"
2653 source "drivers/net/wireless/Kconfig"
2655 source "drivers/net/usb/Kconfig"
2657 source "drivers/net/pcmcia/Kconfig"
2659 source "drivers/net/wan/Kconfig"
2661 source "drivers/atm/Kconfig"
2663 source "drivers/s390/net/Kconfig"
2666 tristate "iSeries Virtual Ethernet driver support"
2667 depends on PPC_ISERIES
2670 tristate "RapidIO Ethernet over messaging driver support"
2673 config RIONET_TX_SIZE
2674 int "Number of outbound queue entries"
2678 config RIONET_RX_SIZE
2679 int "Number of inbound queue entries"
2684 bool "FDDI driver support"
2685 depends on (PCI || EISA || TC)
2687 Fiber Distributed Data Interface is a high speed local area network
2688 design; essentially a replacement for high speed Ethernet. FDDI can
2689 run over copper or fiber. If you are connected to such a network and
2690 want a driver for the FDDI card in your computer, say Y here (and
2691 then also Y to the driver for your FDDI card, below). Most people
2695 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2696 depends on FDDI && (PCI || EISA || TC)
2698 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2699 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2700 to a local FDDI network.
2702 To compile this driver as a module, choose M here: the module
2703 will be called defxx. If unsure, say N.
2707 prompt "Use MMIO instead of PIO" if PCI || EISA
2709 default n if PCI || EISA
2712 This instructs the driver to use EISA or PCI memory-mapped I/O
2713 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2714 Enabling this gives an improvement in processing time in parts
2715 of the driver, but it may cause problems with EISA (DEFEA)
2716 adapters. TURBOchannel does not have the concept of I/O ports,
2717 so MMIO is always used for these (DEFTA) adapters.
2722 tristate "SysKonnect FDDI PCI support"
2723 depends on FDDI && PCI
2726 Say Y here if you have a SysKonnect FDDI PCI adapter.
2727 The following adapters are supported by this driver:
2728 - SK-5521 (SK-NET FDDI-UP)
2729 - SK-5522 (SK-NET FDDI-UP DAS)
2730 - SK-5541 (SK-NET FDDI-FP)
2731 - SK-5543 (SK-NET FDDI-LP)
2732 - SK-5544 (SK-NET FDDI-LP DAS)
2733 - SK-5821 (SK-NET FDDI-UP64)
2734 - SK-5822 (SK-NET FDDI-UP64 DAS)
2735 - SK-5841 (SK-NET FDDI-FP64)
2736 - SK-5843 (SK-NET FDDI-LP64)
2737 - SK-5844 (SK-NET FDDI-LP64 DAS)
2738 - Netelligent 100 FDDI DAS Fibre SC
2739 - Netelligent 100 FDDI SAS Fibre SC
2740 - Netelligent 100 FDDI DAS UTP
2741 - Netelligent 100 FDDI SAS UTP
2742 - Netelligent 100 FDDI SAS Fibre MIC
2744 Read <file:Documentation/networking/skfp.txt> for information about
2747 Questions concerning this driver can be addressed to:
2748 <linux@syskonnect.de>
2750 To compile this driver as a module, choose M here: the module
2751 will be called skfp. This is recommended.
2754 bool "HIPPI driver support (EXPERIMENTAL)"
2755 depends on EXPERIMENTAL && INET && PCI
2757 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2758 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2759 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2760 single-mode). HIPPI networks are commonly used for clusters and to
2761 connect to super computers. If you are connected to a HIPPI network
2762 and have a HIPPI network card in your computer that you want to use
2763 under Linux, say Y here (you must also remember to enable the driver
2764 for your HIPPI card below). Most people will say N here.
2767 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2768 depends on HIPPI && PCI
2770 Say Y here if this is your PCI HIPPI network card.
2772 To compile this driver as a module, choose M here: the module
2773 will be called rrunner. If unsure, say N.
2775 config ROADRUNNER_LARGE_RINGS
2776 bool "Use large TX/RX rings (EXPERIMENTAL)"
2777 depends on ROADRUNNER
2779 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2780 of additional memory to allow for fastest operation, both for
2781 transmitting and receiving. This memory cannot be used by any other
2782 kernel code or by user space programs. Say Y here only if you have
2786 tristate "PLIP (parallel port) support"
2789 PLIP (Parallel Line Internet Protocol) is used to create a
2790 reasonably fast mini network consisting of two (or, rarely, more)
2791 local machines. A PLIP link from a Linux box is a popular means to
2792 install a Linux distribution on a machine which doesn't have a
2793 CD-ROM drive (a minimal system has to be transferred with floppies
2794 first). The kernels on both machines need to have this PLIP option
2795 enabled for this to work.
2797 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2798 ports (the connectors at the computers with 25 holes) are connected
2799 with "null printer" or "Turbo Laplink" cables which can transmit 4
2800 bits at a time (mode 0) or with special PLIP cables, to be used on
2801 bidirectional parallel ports only, which can transmit 8 bits at a
2802 time (mode 1); you can find the wiring of these cables in
2803 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2804 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2805 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2806 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2807 and winsock or NCSA's telnet.
2809 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2810 as the NET-3-HOWTO, both available from
2811 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2812 protocol has been changed and this PLIP driver won't work together
2813 with the PLIP support in Linux versions 1.0.x. This option enlarges
2814 your kernel by about 8 KB.
2816 To compile this driver as a module, choose M here and read
2817 <file:Documentation/networking/net-modules.txt>. The module will be
2818 called plip. If unsure, say Y or M, in case you buy a laptop
2822 tristate "PPP (point-to-point protocol) support"
2825 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2826 the same purpose: sending Internet traffic over telephone (and other
2827 serial) lines. Ask your access provider if they support it, because
2828 otherwise you can't use it; most Internet access providers these
2829 days support PPP rather than SLIP.
2831 To use PPP, you need an additional program called pppd as described
2832 in the PPP-HOWTO, available at
2833 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2834 the version of pppd recommended in <file:Documentation/Changes>.
2835 The PPP option enlarges your kernel by about 16 KB.
2837 There are actually two versions of PPP: the traditional PPP for
2838 asynchronous lines, such as regular analog phone lines, and
2839 synchronous PPP which can be used over digital ISDN lines for
2840 example. If you want to use PPP over phone lines or other
2841 asynchronous serial lines, you need to say Y (or M) here and also to
2842 the next option, "PPP support for async serial ports". For PPP over
2843 synchronous lines, you should say Y (or M) here and to "Support
2844 synchronous PPP", below.
2846 If you said Y to "Version information on all symbols" above, then
2847 you cannot compile the PPP driver into the kernel; you can then only
2848 compile it as a module. To compile this driver as a module, choose M
2849 here and read <file:Documentation/networking/net-modules.txt>.
2850 The module will be called ppp_generic.
2852 config PPP_MULTILINK
2853 bool "PPP multilink support (EXPERIMENTAL)"
2854 depends on PPP && EXPERIMENTAL
2856 PPP multilink is a protocol (defined in RFC 1990) which allows you
2857 to combine several (logical or physical) lines into one logical PPP
2858 connection, so that you can utilize your full bandwidth.
2860 This has to be supported at the other end as well and you need a
2861 version of the pppd daemon which understands the multilink protocol.
2866 bool "PPP filtering"
2869 Say Y here if you want to be able to filter the packets passing over
2870 PPP interfaces. This allows you to control which packets count as
2871 activity (i.e. which packets will reset the idle timer or bring up
2872 a demand-dialed link) and which packets are to be dropped entirely.
2873 You need to say Y here if you wish to use the pass-filter and
2874 active-filter options to pppd.
2879 tristate "PPP support for async serial ports"
2883 Say Y (or M) here if you want to be able to use PPP over standard
2884 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2885 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2888 To compile this driver as a module, choose M here.
2893 tristate "PPP support for sync tty ports"
2896 Say Y (or M) here if you want to be able to use PPP over synchronous
2897 (HDLC) tty devices, such as the SyncLink adapter. These devices
2898 are often used for high-speed leased lines like T1/E1.
2900 To compile this driver as a module, choose M here.
2903 tristate "PPP Deflate compression"
2908 Support for the Deflate compression method for PPP, which uses the
2909 Deflate algorithm (the same algorithm that gzip uses) to compress
2910 each PPP packet before it is sent over the wire. The machine at the
2911 other end of the PPP link (usually your ISP) has to support the
2912 Deflate compression method as well for this to be useful. Even if
2913 they don't support it, it is safe to say Y here.
2915 To compile this driver as a module, choose M here.
2918 tristate "PPP BSD-Compress compression"
2921 Support for the BSD-Compress compression method for PPP, which uses
2922 the LZW compression method to compress each PPP packet before it is
2923 sent over the wire. The machine at the other end of the PPP link
2924 (usually your ISP) has to support the BSD-Compress compression
2925 method as well for this to be useful. Even if they don't support it,
2926 it is safe to say Y here.
2928 The PPP Deflate compression method ("PPP Deflate compression",
2929 above) is preferable to BSD-Compress, because it compresses better
2932 Note that the BSD compression code will always be compiled as a
2933 module; it is called bsd_comp and will show up in the directory
2934 modules once you have said "make modules". If unsure, say N.
2936 config PPP_MPPE_MPPC
2937 tristate "Microsoft PPP compression/encryption (MPPC/MPPE)"
2942 Support for the Microsoft Point-To-Point Compression (RFC2118) and
2943 Microsoft Point-To-Point Encryption (RFC3078). These protocols are
2944 supported by Microsoft Windows and wide range of "hardware" access
2945 servers. MPPE is common protocol in Virtual Private Networks. According
2946 to RFC3078, MPPE supports 40, 56 and 128-bit key lengths. Depending on
2947 PPP daemon configuration on both ends of the link, following scenarios
2949 - only compression (MPPC) is used,
2950 - only encryption (MPPE) is used,
2951 - compression and encryption (MPPC+MPPE) are used.
2953 Please note that Hi/Fn (http://www.hifn.com) holds patent on MPPC so
2954 you should check if this patent is valid in your country in order to
2955 avoid legal problems.
2957 For more information please visit http://mppe-mppc.alphacron.de
2959 To compile this driver as a module, choose M here. The module will
2960 be called ppp_mppe_mppc.ko.
2963 tristate "PPP over Ethernet (EXPERIMENTAL)"
2964 depends on EXPERIMENTAL && PPP
2966 Support for PPP over Ethernet.
2968 This driver requires the latest version of pppd from the CVS
2969 repository at cvs.samba.org. Alternatively, see the
2970 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2971 which contains instruction on how to use this driver (under
2972 the heading "Kernel mode PPPoE").
2975 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
2976 depends on EXPERIMENTAL && PPP
2978 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
2980 This driver requires pppd plugin to work in client mode or
2981 modified pptpd (poptop) to work in server mode.
2982 See http://accel-pptp.sourceforge.net/ for information how to
2983 utilize this module.
2986 tristate "PPP over ATM"
2987 depends on ATM && PPP
2989 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2990 This implementation does not yet comply with section 8 of RFC2364,
2991 which can lead to bad results if the ATM peer loses state and
2992 changes its encapsulation unilaterally.
2995 tristate "PPP over L2TP (EXPERIMENTAL)"
2996 depends on EXPERIMENTAL && PPP
2998 Support for PPP-over-L2TP socket family. L2TP is a protocol
2999 used by ISPs and enterprises to tunnel PPP traffic over UDP
3000 tunnels. L2TP is replacing PPTP for VPN uses.
3002 This kernel component handles only L2TP data packets: a
3003 userland daemon handles L2TP the control protocol (tunnel
3004 and session setup). One such daemon is OpenL2TP
3005 (http://openl2tp.sourceforge.net/).
3008 tristate "SLIP (serial line) support"
3010 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3011 connect to your Internet service provider or to connect to some
3012 other local Unix box or if you want to configure your Linux box as a
3013 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3014 Internet Protocol) is a protocol used to send Internet traffic over
3015 serial connections such as telephone lines or null modem cables;
3016 nowadays, the protocol PPP is more commonly used for this same
3019 Normally, your access provider has to support SLIP in order for you
3020 to be able to use it, but there is now a SLIP emulator called SLiRP
3021 around (available from
3022 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3023 allows you to use SLIP over a regular dial up shell connection. If
3024 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3025 NET-3-HOWTO, available from
3026 <http://www.tldp.org/docs.html#howto>, explains how to
3027 configure SLIP. Note that you don't need this option if you just
3028 want to run term (term is a program which gives you almost full
3029 Internet connectivity if you have a regular dial up shell account on
3030 some Internet connected Unix computer. Read
3031 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3032 support will enlarge your kernel by about 4 KB. If unsure, say N.
3034 To compile this driver as a module, choose M here and read
3035 <file:Documentation/networking/net-modules.txt>. The module will be
3038 config SLIP_COMPRESSED
3039 bool "CSLIP compressed headers"
3043 This protocol is faster than SLIP because it uses compression on the
3044 TCP/IP headers (not on the data itself), but it has to be supported
3045 on both ends. Ask your access provider if you are not sure and
3046 answer Y, just in case. You will still be able to use plain SLIP. If
3047 you plan to use SLiRP, the SLIP emulator (available from
3048 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3049 allows you to use SLIP over a regular dial up shell connection, you
3050 definitely want to say Y here. The NET-3-HOWTO, available from
3051 <http://www.tldp.org/docs.html#howto>, explains how to configure
3052 CSLIP. This won't enlarge your kernel.
3057 This option enables Van Jacobsen serial line header compression
3061 bool "Keepalive and linefill"
3064 Adds additional capabilities to the SLIP driver to support the
3065 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3068 config SLIP_MODE_SLIP6
3069 bool "Six bit SLIP encapsulation"
3072 Just occasionally you may need to run IP over hostile serial
3073 networks that don't pass all control characters or are only seven
3074 bit. Saying Y here adds an extra mode you can use with SLIP:
3075 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3076 the serial device. Naturally, this has to be supported at the other
3077 end of the link as well. It's good enough, for example, to run IP
3078 over the async ports of a Camtec JNT Pad. If unsure, say N.
3081 bool "Fibre Channel driver support"
3082 depends on SCSI && PCI
3084 Fibre Channel is a high speed serial protocol mainly used to connect
3085 large storage devices to the computer; it is compatible with and
3086 intended to replace SCSI.
3088 If you intend to use Fibre Channel, you need to have a Fibre channel
3089 adaptor card in your computer; say Y here and to the driver for your
3090 adaptor below. You also should have said Y to "SCSI support" and
3091 "SCSI generic support".
3094 tristate "Traffic Shaper (OBSOLETE)"
3095 depends on EXPERIMENTAL
3097 The traffic shaper is a virtual network device that allows you to
3098 limit the rate of outgoing data flow over some other network device.
3099 The traffic that you want to slow down can then be routed through
3100 these virtual devices. See
3101 <file:Documentation/networking/shaper.txt> for more information.
3103 An alternative to this traffic shaper are traffic schedulers which
3104 you'll get if you say Y to "QoS and/or fair queuing" in
3105 "Networking options".
3107 To compile this driver as a module, choose M here: the module
3108 will be called shaper. If unsure, say N.
3111 tristate "Network console logging support (EXPERIMENTAL)"
3112 depends on EXPERIMENTAL
3114 If you want to log kernel messages over the network, enable this.
3115 See <file:Documentation/networking/netconsole.txt> for details.
3123 bool "Netpoll traffic trapping"
3127 config NET_POLL_CONTROLLER