3 # Network device configuration
9 bool "Network device support"
11 You can say N here if you don't intend to connect your Linux box to
12 any other computer at all.
14 You'll have to say Y if your computer contains a network card that
15 you want to use under Linux. If you are going to run SLIP or PPP over
16 telephone line or null modem cable you need say Y here. Connecting
17 two machines with parallel ports using PLIP needs this, as well as
18 AX.25/KISS for sending Internet traffic over amateur radio links.
20 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 # All the following symbols are dependent on NETDEVICES - do not repeat
26 # that for each of the symbols.
29 config NETDEVICES_MULTIQUEUE
30 bool "Netdevice multiple hardware queue support"
32 Say Y here if you want to allow the network stack to use multiple
33 hardware TX queues on an ethernet device.
35 Most people will say N here.
38 tristate "Intermediate Functional Block support"
39 depends on NET_CLS_ACT
41 This is an intermediate driver that allows sharing of
43 To compile this driver as a module, choose M here: the module
44 will be called ifb. If you want to use more than one ifb
45 device at a time, you need to compile this driver as a module.
46 Instead of 'ifb', the devices will then be called 'ifb0',
48 Look at the iproute2 documentation directory for usage etc
51 tristate "Dummy net driver support"
53 This is essentially a bit-bucket device (i.e. traffic you send to
54 this device is consigned into oblivion) with a configurable IP
55 address. It is most commonly used in order to make your currently
56 inactive SLIP address seem like a real address for local programs.
57 If you use SLIP or PPP, you might want to say Y here. Since this
58 thing often comes in handy, the default is Y. It won't enlarge your
59 kernel either. What a deal. Read about it in the Network
60 Administrator's Guide, available from
61 <http://www.tldp.org/docs.html#guide>.
63 To compile this driver as a module, choose M here: the module
64 will be called dummy. If you want to use more than one dummy
65 device at a time, you need to compile this driver as a module.
66 Instead of 'dummy', the devices will then be called 'dummy0',
70 tristate "Bonding driver support"
73 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
74 Channels together. This is called 'Etherchannel' by Cisco,
75 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
77 The driver supports multiple bonding modes to allow for both high
78 performance and high availability operation.
80 Refer to <file:Documentation/networking/bonding.txt> for more
83 To compile this driver as a module, choose M here: the module
84 will be called bonding.
87 tristate "MAC-VLAN support (EXPERIMENTAL)"
88 depends on EXPERIMENTAL
90 This allows one to create virtual interfaces that map packets to
91 or from specific MAC addresses to a particular interface.
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "EQL (serial line load balancing) support"
99 If you have two serial connections to some other computer (this
100 usually requires two modems and two telephone lines) and you use
101 SLIP (the protocol for sending Internet traffic over telephone
102 lines) or PPP (a better SLIP) on them, you can make them behave like
103 one double speed connection using this driver. Naturally, this has
104 to be supported at the other end as well, either with a similar EQL
105 Linux driver or with a Livingston Portmaster 2e.
107 Say Y if you want this and read
108 <file:Documentation/networking/eql.txt>. You may also want to read
109 section 6.2 of the NET-3-HOWTO, available from
110 <http://www.tldp.org/docs.html#howto>.
112 To compile this driver as a module, choose M here: the module
113 will be called eql. If unsure, say N.
116 tristate "Universal TUN/TAP device driver support"
119 TUN/TAP provides packet reception and transmission for user space
120 programs. It can be viewed as a simple Point-to-Point or Ethernet
121 device, which instead of receiving packets from a physical media,
122 receives them from user space program and instead of sending packets
123 via physical media writes them to the user space program.
125 When a program opens /dev/net/tun, driver creates and registers
126 corresponding net device tunX or tapX. After a program closed above
127 devices, driver will automatically delete tunXX or tapXX device and
128 all routes corresponding to it.
130 Please read <file:Documentation/networking/tuntap.txt> for more
133 To compile this driver as a module, choose M here: the module
136 If you don't know what to use this for, you don't need it.
139 tristate "Virtual ethernet device"
141 The device is an ethernet tunnel. Devices are created in pairs. When
142 one end receives the packet it appears on its pair and vice versa.
145 tristate "General Instruments Surfboard 1000"
148 This is a driver for the General Instrument (also known as
149 NextLevel) SURFboard 1000 internal
150 cable modem. This is an ISA card which is used by a number of cable
151 TV companies to provide cable modem access. It's a one-way
152 downstream-only cable modem, meaning that your upstream net link is
153 provided by your regular phone modem.
155 At present this driver only compiles as a module, so say M here if
156 you have this card. The module will be called sb1000. Then read
157 <file:Documentation/networking/README.sb1000> for information on how
158 to use this module, as it needs special ppp scripts for establishing
159 a connection. Further documentation and the necessary scripts can be
162 <http://www.jacksonville.net/~fventuri/>
163 <http://home.adelphia.net/~siglercm/sb1000.html>
164 <http://linuxpower.cx/~cable/>
166 If you don't have this card, of course say N.
169 tristate "IP1000 Gigabit Ethernet support"
170 depends on PCI && EXPERIMENTAL
172 This driver supports IP1000 gigabit Ethernet cards.
174 To compile this driver as a module, choose M here: the module
175 will be called ipg. This is recommended.
177 source "drivers/net/arcnet/Kconfig"
179 source "drivers/net/phy/Kconfig"
185 menuconfig NET_ETHERNET
186 bool "Ethernet (10 or 100Mbit)"
189 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
190 type of Local Area Network (LAN) in universities and companies.
192 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
193 coaxial cable, linking computers in a chain), 10BASE-T or twisted
194 pair (10 Mbps over twisted pair cable, linking computers to central
195 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
196 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
197 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
198 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
199 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
200 Ethernet (1 Gbps over optical fiber or short copper links).
202 If your Linux machine will be connected to an Ethernet and you have
203 an Ethernet network interface card (NIC) installed in your computer,
204 say Y here and read the Ethernet-HOWTO, available from
205 <http://www.tldp.org/docs.html#howto>. You will then also have
206 to say Y to the driver for your particular NIC.
208 Note that the answer to this question won't directly affect the
209 kernel: saying N will just cause the configurator to skip all
210 the questions about Ethernet network cards. If unsure, say N.
215 tristate "Generic Media Independent Interface device support"
217 Most ethernet controllers have MII transceiver either as an external
218 or internal device. It is safe to say Y or M here even if your
219 ethernet card lack MII.
222 tristate "Atmel MACB support"
223 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263
226 The Atmel MACB ethernet interface is found on many AT32 and AT91
227 parts. Say Y to include support for the MACB chip.
229 To compile this driver as a module, choose M here: the module
232 source "drivers/net/arm/Kconfig"
235 tristate "ASIX AX88796 NE2000 clone support"
236 depends on ARM || MIPS
240 AX88796 driver, using platform bus to provide
241 chip detection and resources
244 tristate "MACE (Power Mac ethernet) support"
245 depends on PPC_PMAC && PPC32
248 Power Macintoshes and clones with Ethernet built-in on the
249 motherboard will usually use a MACE (Medium Access Control for
250 Ethernet) interface. Say Y to include support for the MACE chip.
252 To compile this driver as a module, choose M here: the module
255 config MACE_AAUI_PORT
256 bool "Use AAUI port instead of TP by default"
259 Some Apple machines (notably the Apple Network Server) which use the
260 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
261 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
262 Y here if you have such a machine. If unsure, say N.
263 The driver will default to AAUI on ANS anyway, and if you use it as
264 a module, you can provide the port_aaui=0|1 to force the driver.
267 tristate "BMAC (G3 ethernet) support"
268 depends on PPC_PMAC && PPC32
271 Say Y for support of BMAC Ethernet interfaces. These are used on G3
274 To compile this driver as a module, choose M here: the module
278 tristate "Ariadne support"
281 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
284 To compile this driver as a module, choose M here: the module
285 will be called ariadne.
288 tristate "A2065 support"
292 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
295 To compile this driver as a module, choose M here: the module
296 will be called a2065.
299 tristate "Hydra support"
303 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
305 To compile this driver as a module, choose M here: the module
306 will be called hydra.
309 tristate "Zorro NS8390-based Ethernet support"
313 This driver is for Zorro Ethernet cards using an NS8390-compatible
314 chipset, like the Village Tronic Ariadne II and the Individual
315 Computers X-Surf Ethernet cards. If you have such a card, say Y.
318 To compile this driver as a module, choose M here: the module
319 will be called zorro8390.
322 tristate "PCMCIA NE2000 support"
323 depends on AMIGA_PCMCIA
326 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
329 To compile this driver as a module, choose M here: the module
333 tristate "Apollo 3c505 support"
336 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
337 If you don't have one made for Apollos, you can use one from a PC,
338 except that your Apollo won't be able to boot from it (because the
339 code in the ROM will be for a PC).
342 bool "Macintosh NS 8390 based ethernet cards"
346 If you want to include a driver to support Nubus or LC-PDS
347 Ethernet cards using an NS8390 chipset or its equivalent, say Y
348 and read the Ethernet-HOWTO, available from
349 <http://www.tldp.org/docs.html#howto>.
352 tristate "Macintosh CS89x0 based ethernet cards"
355 Support for CS89x0 chipset based Ethernet cards. If you have a
356 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
357 read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 To compile this driver as a module, choose M here and read
361 <file:Documentation/networking/net-modules.txt>. This module will
365 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
368 Support for NatSemi SONIC based Ethernet devices. This includes
369 the onboard Ethernet in many Quadras as well as some LC-PDS,
370 a few Nubus and all known Comm Slot Ethernet cards. If you have
371 one of these say Y and read the Ethernet-HOWTO, available from
372 <http://www.tldp.org/docs.html#howto>.
374 To compile this driver as a module, choose M here and read
375 <file:Documentation/networking/net-modules.txt>. This module will
379 bool "Macintosh (AV) onboard MACE ethernet"
383 Support for the onboard AMD 79C940 MACE Ethernet controller used in
384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
385 say Y and read the Ethernet-HOWTO, available from
386 <http://www.tldp.org/docs.html#howto>.
389 tristate "MVME147 (Lance) Ethernet support"
393 Support for the on-board Ethernet interface on the Motorola MVME147
394 single-board computer. Say Y here to include the
395 driver for this chip in your kernel.
396 To compile this driver as a module, choose M here.
399 tristate "MVME16x Ethernet support"
402 This is the driver for the Ethernet interface on the Motorola
403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
404 driver for this chip in your kernel.
405 To compile this driver as a module, choose M here.
408 tristate "BVME6000 Ethernet support"
411 This is the driver for the Ethernet interface on BVME4000 and
412 BVME6000 VME boards. Say Y here to include the driver for this chip
414 To compile this driver as a module, choose M here.
417 tristate "Atari Lance support"
420 Say Y to include support for several Atari Ethernet adapters based
421 on the AMD Lance chipset: RieblCard (with or without battery), or
422 PAMCard VME (also the version by Rhotron, with different addresses).
425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
435 If you're not building a kernel for a Sun 3, say N.
438 bool "Sun3 on-board Intel 82586 support"
441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional
447 bool "HP on-board LANCE support"
451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here.
455 tristate "Lasi ethernet"
458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM
465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines.
468 config MIPS_JAZZ_SONIC
469 tristate "MIPS JAZZ onboard SONIC Ethernet support"
472 This is the driver for the onboard card of MIPS Magnum 4000,
473 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
475 config MIPS_AU1X00_ENET
476 bool "MIPS AU1000 Ethernet support"
477 depends on SOC_AU1X00
481 If you have an Alchemy Semi AU1X00 based system
482 say Y. Otherwise, say N.
485 bool "SGI IOC3 Ethernet"
486 depends on PCI && SGI_IP27
490 If you have a network (Ethernet) card of this type, say Y and read
491 the Ethernet-HOWTO, available from
492 <http://www.tldp.org/docs.html#howto>.
495 tristate "MIPS simulator Network device"
498 The MIPSNET device is a simple Ethernet network device which is
499 emulated by the MIPS Simulator.
500 If you are not using a MIPSsim or are unsure, say N.
502 config SGI_O2MACE_ETH
503 tristate "SGI O2 MACE Fast Ethernet support"
504 depends on SGI_IP32=y
507 tristate "National DP83902AV support"
511 Support for cards based on the National Semiconductor DP83902AV
512 ST-NIC Serial Network Interface Controller for Twisted Pair. This
513 is a 10Mbit/sec Ethernet controller. Product overview and specs at
514 <http://www.national.com/pf/DP/DP83902A.html>.
519 tristate "Sun LANCE support"
523 This driver supports the "le" interface present on all 32-bit Sparc
524 systems, on some older Ultra systems and as an Sbus option. These
525 cards are based on the AMD Lance chipset, which is better known
526 via the NE2100 cards.
528 To compile this driver as a module, choose M here: the module
529 will be called sunlance.
532 tristate "Sun Happy Meal 10/100baseT support"
533 depends on SBUS || PCI
536 This driver supports the "hme" interface present on most Ultra
537 systems and as an option on older Sbus systems. This driver supports
538 both PCI and Sbus devices. This driver also supports the "qfe" quad
539 100baseT device available in both PCI and Sbus configurations.
541 To compile this driver as a module, choose M here: the module
542 will be called sunhme.
545 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
546 depends on SBUS && EXPERIMENTAL
549 This driver supports the "be" interface available as an Sbus option.
550 This is Sun's older 100baseT Ethernet device.
552 To compile this driver as a module, choose M here: the module
553 will be called sunbmac.
556 tristate "Sun QuadEthernet support"
560 This driver supports the "qe" 10baseT Ethernet device, available as
561 an Sbus option. Note that this is not the same as Quad FastEthernet
562 "qfe" which is supported by the Happy Meal driver instead.
564 To compile this driver as a module, choose M here: the module
565 will be called sunqe.
568 tristate "Sun GEM support"
572 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
573 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
576 tristate "Sun Cassini support"
580 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
581 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
584 tristate "Sun Virtual Network support"
587 Support for virtual network devices under Sun Logical Domains.
589 config NET_VENDOR_3COM
591 depends on ISA || EISA || MCA || PCI
593 If you have a network (Ethernet) card belonging to this class, say Y
594 and read the Ethernet-HOWTO, available from
595 <http://www.tldp.org/docs.html#howto>.
597 Note that the answer to this question doesn't directly affect the
598 kernel: saying N will just cause the configurator to skip all
599 the questions about 3COM cards. If you say Y, you will be asked for
600 your specific card in the following questions.
603 tristate "3c501 \"EtherLink\" support"
604 depends on NET_VENDOR_3COM && ISA
606 If you have a network (Ethernet) card of this type, say Y and read
607 the Ethernet-HOWTO, available from
608 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
609 new card, since the 3c501 is slow, broken, and obsolete: you will
610 have problems. Some people suggest to ping ("man ping") a nearby
611 machine every minute ("man cron") when using this card.
613 To compile this driver as a module, choose M here and read
614 <file:Documentation/networking/net-modules.txt>. The module
615 will be called 3c501.
618 tristate "3c503 \"EtherLink II\" support"
619 depends on NET_VENDOR_3COM && ISA
622 If you have a network (Ethernet) card of this type, say Y and read
623 the Ethernet-HOWTO, available from
624 <http://www.tldp.org/docs.html#howto>.
626 To compile this driver as a module, choose M here and read
627 <file:Documentation/networking/net-modules.txt>. The module
628 will be called 3c503.
631 tristate "3c505 \"EtherLink Plus\" support"
632 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
634 Information about this network (Ethernet) card can be found in
635 <file:Documentation/networking/3c505.txt>. If you have a card of
636 this type, say Y and read the Ethernet-HOWTO, available from
637 <http://www.tldp.org/docs.html#howto>.
639 To compile this driver as a module, choose M here and read
640 <file:Documentation/networking/net-modules.txt>. The module
641 will be called 3c505.
644 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
645 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
647 If you have a network (Ethernet) card of this type, say Y and read
648 the Ethernet-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>.
651 To compile this driver as a module, choose M here and read
652 <file:Documentation/networking/net-modules.txt>. The module
653 will be called 3c507.
656 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
657 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
659 If you have a network (Ethernet) card belonging to the 3Com
660 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
661 from <http://www.tldp.org/docs.html#howto>.
663 If your card is not working you may need to use the DOS
664 setup disk to disable Plug & Play mode, and to select the default
667 To compile this driver as a module, choose M here and read
668 <file:Documentation/networking/net-modules.txt>. The module
669 will be called 3c509.
672 tristate "3c515 ISA \"Fast EtherLink\""
673 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
675 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
676 network card, say Y and read the Ethernet-HOWTO, available from
677 <http://www.tldp.org/docs.html#howto>.
679 To compile this driver as a module, choose M here and read
680 <file:Documentation/networking/net-modules.txt>. The module
681 will be called 3c515.
684 tristate "3c523 \"EtherLink/MC\" support"
685 depends on NET_VENDOR_3COM && MCA_LEGACY
687 If you have a network (Ethernet) card of this type, say Y and read
688 the Ethernet-HOWTO, available from
689 <http://www.tldp.org/docs.html#howto>.
691 To compile this driver as a module, choose M here and read
692 <file:Documentation/networking/net-modules.txt>. The module
693 will be called 3c523.
696 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
697 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
699 If you have a network (Ethernet) card of this type, say Y and read
700 the Ethernet-HOWTO, available from
701 <http://www.tldp.org/docs.html#howto>.
703 To compile this driver as a module, choose M here and read
704 <file:Documentation/networking/net-modules.txt>. The module
705 will be called 3c527.
708 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
709 depends on NET_VENDOR_3COM && (PCI || EISA)
712 This option enables driver support for a large number of 10Mbps and
713 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
715 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
716 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
717 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
718 "Tornado" (3c905) PCI
719 "Hurricane" (3c555/3cSOHO) PCI
721 If you have such a card, say Y and read the Ethernet-HOWTO,
722 available from <http://www.tldp.org/docs.html#howto>. More
723 specific information is in
724 <file:Documentation/networking/vortex.txt> and in the comments at
725 the beginning of <file:drivers/net/3c59x.c>.
727 To compile this support as a module, choose M here and read
728 <file:Documentation/networking/net-modules.txt>.
731 tristate "3cr990 series \"Typhoon\" support"
732 depends on NET_VENDOR_3COM && PCI
735 This option enables driver support for the 3cr990 series of cards:
737 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
738 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
739 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
741 If you have a network (Ethernet) card of this type, say Y and read
742 the Ethernet-HOWTO, available from
743 <http://www.tldp.org/docs.html#howto>.
745 To compile this driver as a module, choose M here and read
746 <file:Documentation/networking/net-modules.txt>. The module
747 will be called typhoon.
750 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
751 depends on ISA && ISA_DMA_API
753 If you have a network (Ethernet) card of this type, say Y and read
754 the Ethernet-HOWTO, available from
755 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
758 To compile this driver as a module, choose M here: the module
759 will be called lance. This is recommended.
761 config NET_VENDOR_SMC
762 bool "Western Digital/SMC cards"
763 depends on ISA || MCA || EISA || MAC
765 If you have a network (Ethernet) card belonging to this class, say Y
766 and read the Ethernet-HOWTO, available from
767 <http://www.tldp.org/docs.html#howto>.
769 Note that the answer to this question doesn't directly affect the
770 kernel: saying N will just cause the configurator to skip all
771 the questions about Western Digital cards. If you say Y, you will be
772 asked for your specific card in the following questions.
775 tristate "WD80*3 support"
776 depends on NET_VENDOR_SMC && ISA
779 If you have a network (Ethernet) card of this type, say Y and read
780 the Ethernet-HOWTO, available from
781 <http://www.tldp.org/docs.html#howto>.
783 To compile this driver as a module, choose M here and read
784 <file:Documentation/networking/net-modules.txt>. The module
788 tristate "SMC Ultra MCA support"
789 depends on NET_VENDOR_SMC && MCA
792 If you have a network (Ethernet) card of this type and are running
793 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
794 available from <http://www.tldp.org/docs.html#howto>.
796 To compile this driver as a module, choose M here and read
797 <file:Documentation/networking/net-modules.txt>. The module
798 will be called smc-mca.
801 tristate "SMC Ultra support"
802 depends on NET_VENDOR_SMC && ISA
805 If you have a network (Ethernet) card of this type, say Y and read
806 the Ethernet-HOWTO, available from
807 <http://www.tldp.org/docs.html#howto>.
809 Important: There have been many reports that, with some motherboards
810 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
811 such as some BusLogic models) causes corruption problems with many
812 operating systems. The Linux smc-ultra driver has a work-around for
813 this but keep it in mind if you have such a SCSI card and have
816 To compile this driver as a module, choose M here and read
817 <file:Documentation/networking/net-modules.txt>. The module
818 will be called smc-ultra.
821 tristate "SMC Ultra32 EISA support"
822 depends on NET_VENDOR_SMC && EISA
825 If you have a network (Ethernet) card of this type, say Y and read
826 the Ethernet-HOWTO, available from
827 <http://www.tldp.org/docs.html#howto>.
829 To compile this driver as a module, choose M here and read
830 <file:Documentation/networking/net-modules.txt>. The module
831 will be called smc-ultra32.
834 tristate "Blackfin 536/537 on-chip mac support"
835 depends on NET_ETHERNET && (BF537 || BF536) && (!BF537_PORT_H)
839 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
841 This is the driver for blackfin on-chip mac device. Say Y if you want it
842 compiled into the kernel. This driver is also available as a module
843 ( = code which can be inserted in and removed from the running kernel
844 whenever you want). The module will be called bfin_mac.
846 config BFIN_MAC_USE_L1
847 bool "Use L1 memory for rx/tx packets"
848 depends on BFIN_MAC && BF537
851 To get maximum network performace, you should use L1 memory as rx/tx buffers.
852 Say N here if you want to reserve L1 memory for other uses.
854 config BFIN_TX_DESC_NUM
855 int "Number of transmit buffer packets"
857 range 6 10 if BFIN_MAC_USE_L1
861 Set the number of buffer packets used in driver.
863 config BFIN_RX_DESC_NUM
864 int "Number of receive buffer packets"
866 range 20 100 if BFIN_MAC_USE_L1
870 Set the number of buffer packets used in driver.
873 bool "RMII PHY Interface (EXPERIMENTAL)"
874 depends on BFIN_MAC && EXPERIMENTAL
877 Use Reduced PHY MII Interface
880 tristate "SMC 9194 support"
881 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
884 This is support for the SMC9xxx based Ethernet cards. Choose this
885 option if you have a DELL laptop with the docking station, or
886 another SMC9192/9194 based chipset. Say Y if you want it compiled
887 into the kernel, and read the file
888 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
889 available from <http://www.tldp.org/docs.html#howto>.
891 To compile this driver as a module, choose M here and read
892 <file:Documentation/networking/net-modules.txt>. The module
893 will be called smc9194.
896 tristate "SMC 91C9x/91C1xxx support"
899 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
901 This is a driver for SMC's 91x series of Ethernet chipsets,
902 including the SMC91C94 and the SMC91C111. Say Y if you want it
903 compiled into the kernel, and read the file
904 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
905 available from <http://www.linuxdoc.org/docs.html#howto>.
907 This driver is also available as a module ( = code which can be
908 inserted in and removed from the running kernel whenever you want).
909 The module will be called smc91x. If you want to compile it as a
910 module, say M here and read <file:Documentation/kbuild/modules.txt>
911 as well as <file:Documentation/networking/net-modules.txt>.
914 tristate "NetX Ethernet support"
918 This is support for the Hilscher netX builtin Ethernet ports
920 To compile this driver as a module, choose M here and read
921 <file:Documentation/networking/net-modules.txt>. The module
922 will be called netx-eth.
925 tristate "DM9000 support"
926 depends on ARM || BLACKFIN || MIPS
930 Support for DM9000 chipset.
932 To compile this driver as a module, choose M here and read
933 <file:Documentation/networking/net-modules.txt>. The module will be
937 tristate "SMSC LAN911[5678] support"
942 This is a driver for SMSC's LAN911x series of Ethernet chipsets
943 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
944 Say Y if you want it compiled into the kernel,
945 and read the Ethernet-HOWTO, available from
946 <http://www.linuxdoc.org/docs.html#howto>.
948 This driver is also available as a module. The module will be
949 called smc911x. If you want to compile it as a module, say M
950 here and read <file:Documentation/kbuild/modules.txt>
952 config NET_VENDOR_RACAL
953 bool "Racal-Interlan (Micom) NI cards"
956 If you have a network (Ethernet) card belonging to this class, such
957 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
958 available from <http://www.tldp.org/docs.html#howto>.
960 Note that the answer to this question doesn't directly affect the
961 kernel: saying N will just cause the configurator to skip all
962 the questions about NI cards. If you say Y, you will be asked for
963 your specific card in the following questions.
966 tristate "NI5010 support (EXPERIMENTAL)"
967 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
969 If you have a network (Ethernet) card of this type, say Y and read
970 the Ethernet-HOWTO, available from
971 <http://www.tldp.org/docs.html#howto>. Note that this is still
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 ni5010.
979 tristate "NI5210 support"
980 depends on NET_VENDOR_RACAL && ISA
982 If you have a network (Ethernet) card of this type, say Y and read
983 the Ethernet-HOWTO, available from
984 <http://www.tldp.org/docs.html#howto>.
986 To compile this driver as a module, choose M here and read
987 <file:Documentation/networking/net-modules.txt>. The module
991 tristate "NI6510 support"
992 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
994 If you have a network (Ethernet) card of this type, say Y and read
995 the Ethernet-HOWTO, available from
996 <http://www.tldp.org/docs.html#howto>.
998 To compile this driver as a module, choose M here and read
999 <file:Documentation/networking/net-modules.txt>. The module
1000 will be called ni65.
1002 source "drivers/net/tulip/Kconfig"
1005 tristate "AT1700/1720 support (EXPERIMENTAL)"
1006 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1009 If you have a network (Ethernet) card of this type, say Y and read
1010 the Ethernet-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1013 To compile this driver as a module, choose M here and read
1014 <file:Documentation/networking/net-modules.txt>. The module
1015 will be called at1700.
1018 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1019 depends on ISA || EISA || MCA
1022 If you have a network (Ethernet) card of this type, say Y and read
1023 the Ethernet-HOWTO, available from
1024 <http://www.tldp.org/docs.html#howto> as well as
1025 <file:drivers/net/depca.c>.
1027 To compile this driver as a module, choose M here and read
1028 <file:Documentation/networking/net-modules.txt>. The module
1029 will be called depca.
1032 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1033 depends on ISA || EISA || PCI
1035 If you have a network (Ethernet) card of this type, say Y and read
1036 the Ethernet-HOWTO, available from
1037 <http://www.tldp.org/docs.html#howto>.
1039 To compile this driver as a module, choose M here and read
1040 <file:Documentation/networking/net-modules.txt>. The module
1041 will be called hp100.
1044 bool "Other ISA cards"
1047 If your network (Ethernet) card hasn't been mentioned yet and its
1048 bus system (that's the way the cards talks to the other components
1049 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1050 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1051 available from <http://www.tldp.org/docs.html#howto>.
1055 Note that the answer to this question doesn't directly affect the
1056 kernel: saying N will just cause the configurator to skip all
1057 the remaining ISA network card questions. If you say Y, you will be
1058 asked for your specific card in the following questions.
1061 tristate "Cabletron E21xx support"
1065 If you have a network (Ethernet) card of this type, say Y and read
1066 the Ethernet-HOWTO, available from
1067 <http://www.tldp.org/docs.html#howto>.
1069 To compile this driver as a module, choose M here and read
1070 <file:Documentation/networking/net-modules.txt>. The module
1071 will be called e2100.
1074 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1078 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1079 cards. If this is for you, say Y and read
1080 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1081 well as the Ethernet-HOWTO, available from
1082 <http://www.tldp.org/docs.html#howto>.
1084 To compile this driver as a module, choose M here and read
1085 <file:Documentation/networking/net-modules.txt>. The module
1086 will be called ewrk3.
1089 tristate "EtherExpress 16 support"
1092 If you have an EtherExpress16 network (Ethernet) card, say Y and
1093 read the Ethernet-HOWTO, available from
1094 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1095 EtherExpress16 card used to be regarded as a very poor choice
1096 because the driver was very unreliable. We now have a new driver
1097 that should do better.
1099 To compile this driver as a module, choose M here and read
1100 <file:Documentation/networking/net-modules.txt>. The module
1101 will be called eexpress.
1104 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1107 If you have a network (Ethernet) card of this type, say Y. This
1108 driver supports Intel i82595{FX,TX} based boards. Note however
1109 that the EtherExpress PRO/100 Ethernet card has its own separate
1110 driver. Please read the Ethernet-HOWTO, available from
1111 <http://www.tldp.org/docs.html#howto>.
1113 To compile this driver as a module, choose M here and read
1114 <file:Documentation/networking/net-modules.txt>. The module
1115 will be called eepro.
1118 tristate "HP PCLAN+ (27247B and 27252A) support"
1122 If you have a network (Ethernet) card of this type, say Y and read
1123 the Ethernet-HOWTO, available from
1124 <http://www.tldp.org/docs.html#howto>.
1126 To compile this driver as a module, choose M here and read
1127 <file:Documentation/networking/net-modules.txt>. The module
1128 will be called hp-plus.
1131 tristate "HP PCLAN (27245 and other 27xxx series) support"
1135 If you have a network (Ethernet) card of this type, say Y and read
1136 the Ethernet-HOWTO, available from
1137 <http://www.tldp.org/docs.html#howto>.
1139 To compile this driver as a module, choose M here and read
1140 <file:Documentation/networking/net-modules.txt>. The module
1144 tristate "LP486E on board Ethernet"
1147 Say Y here to support the 82596-based on-board Ethernet controller
1148 for the Panther motherboard, which is one of the two shipped in the
1149 Intel Professional Workstation.
1152 tristate "ICL EtherTeam 16i/32 support"
1155 If you have a network (Ethernet) card of this type, say Y and read
1156 the Ethernet-HOWTO, available from
1157 <http://www.tldp.org/docs.html#howto>.
1159 To compile this driver as a module, choose M here and read
1160 <file:Documentation/networking/net-modules.txt>. The module
1161 will be called eth16i.
1164 tristate "NE2000/NE1000 support"
1165 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1168 If you have a network (Ethernet) card of this type, say Y and read
1169 the Ethernet-HOWTO, available from
1170 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1171 without a specific driver are compatible with NE2000.
1173 If you have a PCI NE2000 card however, say N here and Y to "PCI
1174 NE2000 and clone support" under "EISA, VLB, PCI and on board
1175 controllers" below. If you have a NE2000 card and are running on
1176 an MCA system (a bus system used on some IBM PS/2 computers and
1177 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1180 To compile this driver as a module, choose M here and read
1181 <file:Documentation/networking/net-modules.txt>. The module
1185 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1186 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1188 The Zenith Z-Note notebook computer has a built-in network
1189 (Ethernet) card, and this is the Linux driver for it. Note that the
1190 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1191 by this driver. Read the Ethernet-HOWTO, available from
1192 <http://www.tldp.org/docs.html#howto>.
1195 tristate "SEEQ8005 support (EXPERIMENTAL)"
1196 depends on NET_ISA && EXPERIMENTAL
1198 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1199 is for you, read the Ethernet-HOWTO, available from
1200 <http://www.tldp.org/docs.html#howto>.
1202 To compile this driver as a module, choose M here and read
1203 <file:Documentation/networking/net-modules.txt>. The module
1204 will be called seeq8005.
1207 tristate "NE/2 (ne2000 MCA version) support"
1208 depends on MCA_LEGACY
1211 If you have a network (Ethernet) card of this type, say Y and read
1212 the Ethernet-HOWTO, available from
1213 <http://www.tldp.org/docs.html#howto>.
1215 To compile this driver as a module, choose M here and read
1216 <file:Documentation/networking/net-modules.txt>. The module
1220 tristate "IBM LAN Adapter/A support"
1221 depends on MCA && MCA_LEGACY
1223 This is a Micro Channel Ethernet adapter. You need to set
1224 CONFIG_MCA to use this driver. It is both available as an in-kernel
1225 driver and as a module.
1227 To compile this driver as a module, choose M here and read
1228 <file:Documentation/networking/net-modules.txt>. The only
1229 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1230 will both support 16K and 32K memory windows, however a 32K window
1231 gives a better security against packet losses. Usage of multiple
1232 boards with this driver should be possible, but has not been tested
1233 up to now due to lack of hardware.
1236 tristate "IBM LAN Virtual Ethernet support"
1237 depends on PPC_PSERIES
1239 This driver supports virtual ethernet adapters on newer IBM iSeries
1240 and pSeries systems.
1242 To compile this driver as a module, choose M here and read
1243 <file:Documentation/networking/net-modules.txt>. The module will
1246 source "drivers/net/ibm_emac/Kconfig"
1247 source "drivers/net/ibm_newemac/Kconfig"
1250 bool "EISA, VLB, PCI and on board controllers"
1251 depends on ISA || EISA || PCI
1253 This is another class of network cards which attach directly to the
1254 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1255 available from <http://www.tldp.org/docs.html#howto>.
1257 Note that the answer to this question doesn't directly affect the
1258 kernel: saying N will just cause the configurator to skip all
1259 the questions about this class of network cards. If you say Y, you
1260 will be asked for your specific card in the following questions. If
1261 you are unsure, say Y.
1264 tristate "AMD PCnet32 PCI support"
1265 depends on NET_PCI && PCI
1269 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1270 answer Y here and read the Ethernet-HOWTO, available from
1271 <http://www.tldp.org/docs.html#howto>.
1273 To compile this driver as a module, choose M here and read
1274 <file:Documentation/networking/net-modules.txt>. The module
1275 will be called pcnet32.
1278 bool "Use RX polling (NAPI)"
1281 NAPI is a new driver API designed to reduce CPU and interrupt load
1282 when the driver is receiving lots of packets from the card. It is
1283 still somewhat experimental and thus not yet enabled by default.
1285 If your estimated Rx load is 10kpps or more, or if the card will be
1286 deployed on potentially unfriendly networks (e.g. in a firewall),
1289 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1295 tristate "AMD 8111 (new PCI lance) support"
1296 depends on NET_PCI && PCI
1300 If you have an AMD 8111-based PCI lance ethernet card,
1301 answer Y here and read the Ethernet-HOWTO, available from
1302 <http://www.tldp.org/docs.html#howto>.
1304 To compile this driver as a module, choose M here and read
1305 <file:Documentation/networking/net-modules.txt>. The module
1306 will be called amd8111e.
1308 config AMD8111E_NAPI
1309 bool "Enable NAPI support"
1310 depends on AMD8111_ETH
1312 NAPI is a new driver API designed to reduce CPU and interrupt load
1313 when the driver is receiving lots of packets from the card. It is
1314 still somewhat experimental and thus not yet enabled by default.
1316 If your estimated Rx load is 10kpps or more, or if the card will be
1317 deployed on potentially unfriendly networks (e.g. in a firewall),
1320 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1325 config ADAPTEC_STARFIRE
1326 tristate "Adaptec Starfire/DuraLAN support"
1327 depends on NET_PCI && PCI
1331 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1332 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1333 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1336 To compile this driver as a module, choose M here: the module
1337 will be called starfire. This is recommended.
1339 config ADAPTEC_STARFIRE_NAPI
1340 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1341 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1343 NAPI is a new driver API designed to reduce CPU and interrupt load
1344 when the driver is receiving lots of packets from the card. It is
1345 still somewhat experimental and thus not yet enabled by default.
1347 If your estimated Rx load is 10kpps or more, or if the card will be
1348 deployed on potentially unfriendly networks (e.g. in a firewall),
1351 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1357 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1358 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1361 If you have a network (Ethernet) card of this type, say Y and read
1362 the Ethernet-HOWTO, available from
1363 <http://www.tldp.org/docs.html#howto>.
1365 To compile this driver as a module, choose M here and read
1366 <file:Documentation/networking/net-modules.txt>. The module
1367 will be called ac3200.
1370 tristate "Apricot Xen-II on board Ethernet"
1371 depends on NET_PCI && ISA
1373 If you have a network (Ethernet) controller of this type, say Y and
1374 read the Ethernet-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>.
1377 To compile this driver as a module, choose M here and read
1378 <file:Documentation/networking/net-modules.txt>. The module will be
1382 tristate "Broadcom 440x/47xx ethernet support"
1383 depends on SSB_POSSIBLE
1387 If you have a network (Ethernet) controller of this type, say Y
1388 or M and read the Ethernet-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>.
1391 To compile this driver as a module, choose M here and read
1392 <file:Documentation/networking/net-modules.txt>. The module will be
1395 # Auto-select SSB PCI-HOST support, if possible
1396 config B44_PCI_AUTOSELECT
1398 depends on B44 && SSB_PCIHOST_POSSIBLE
1402 # Auto-select SSB PCICORE driver, if possible
1403 config B44_PCICORE_AUTOSELECT
1405 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1406 select SSB_DRIVER_PCICORE
1411 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1415 tristate "nForce Ethernet support"
1416 depends on NET_PCI && PCI
1418 If you have a network (Ethernet) controller of this type, say Y and
1419 read the Ethernet-HOWTO, available from
1420 <http://www.tldp.org/docs.html#howto>.
1422 To compile this driver as a module, choose M here and read
1423 <file:Documentation/networking/net-modules.txt>. The module will be
1426 config FORCEDETH_NAPI
1427 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1428 depends on FORCEDETH && EXPERIMENTAL
1430 NAPI is a new driver API designed to reduce CPU and interrupt load
1431 when the driver is receiving lots of packets from the card. It is
1432 still somewhat experimental and thus not yet enabled by default.
1434 If your estimated Rx load is 10kpps or more, or if the card will be
1435 deployed on potentially unfriendly networks (e.g. in a firewall),
1438 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1444 tristate "CS89x0 support"
1445 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1447 Support for CS89x0 chipset based Ethernet cards. If you have a
1448 network (Ethernet) card of this type, say Y and read the
1449 Ethernet-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto> as well as
1451 <file:Documentation/networking/cs89x0.txt>.
1453 To compile this driver as a module, choose M here and read
1454 <file:Documentation/networking/net-modules.txt>. The module will be
1458 tristate "TOSHIBA TC35815 Ethernet support"
1459 depends on NET_PCI && PCI && MIPS
1463 tristate "Digi Intl. RightSwitch SE-X support"
1464 depends on NET_PCI && (PCI || EISA)
1466 This is support for the Digi International RightSwitch series of
1467 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1468 models. If you have a network card of this type, say Y and read the
1469 Ethernet-HOWTO, available from
1470 <http://www.tldp.org/docs.html#howto>. More specific
1471 information is contained in <file:Documentation/networking/dgrs.txt>.
1473 To compile this driver as a module, choose M here and read
1474 <file:Documentation/networking/net-modules.txt>. The module
1475 will be called dgrs.
1478 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1479 depends on NET_PCI && PCI
1482 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1483 card, say Y and read the Ethernet-HOWTO, available from
1484 <http://www.tldp.org/docs.html#howto>.
1486 To compile this driver as a module, choose M here and read
1487 <file:Documentation/networking/net-modules.txt>. The module
1488 will be called eepro100.
1492 tristate "Intel(R) PRO/100+ support"
1493 depends on NET_PCI && PCI
1496 This driver supports Intel(R) PRO/100 family of adapters.
1497 To verify that your adapter is supported, find the board ID number
1498 on the adapter. Look for a label that has a barcode and a number
1499 in the format 123456-001 (six digits hyphen three digits).
1501 Use the above information and the Adapter & Driver ID Guide at:
1503 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1505 to identify the adapter.
1507 For the latest Intel PRO/100 network driver for Linux, see:
1509 <http://appsr.intel.com/scripts-df/support_intel.asp>
1511 More specific information on configuring the driver is in
1512 <file:Documentation/networking/e100.txt>.
1514 To compile this driver as a module, choose M here and read
1515 <file:Documentation/networking/net-modules.txt>. The module
1516 will be called e100.
1519 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1520 depends on NET_PCI && EISA && EXPERIMENTAL
1523 If you have a network (Ethernet) card of this type, say Y and read
1524 the Ethernet-HOWTO, available from
1525 <http://www.tldp.org/docs.html#howto>.
1527 To compile this driver as a module, choose M here and read
1528 <file:Documentation/networking/net-modules.txt>. The module
1529 will be called lne390.
1532 tristate "Myson MTD-8xx PCI Ethernet support"
1533 depends on NET_PCI && PCI
1537 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1538 cards. Specifications and data at
1539 <http://www.myson.com.hk/mtd/datasheet/>.
1542 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1543 depends on NET_PCI && PCI
1546 This driver is for the National Semiconductor DP83810 series,
1547 which is used in cards from PureData, NetGear, Linksys
1548 and others, including the 83815 chip.
1549 More specific information and updates are available from
1550 <http://www.scyld.com/network/natsemi.html>.
1553 tristate "PCI NE2000 and clones support (see help)"
1554 depends on NET_PCI && PCI
1557 This driver is for NE2000 compatible PCI cards. It will not work
1558 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1559 support" below). If you have a PCI NE2000 network (Ethernet) card,
1560 say Y and read the Ethernet-HOWTO, available from
1561 <http://www.tldp.org/docs.html#howto>.
1563 This driver also works for the following NE2000 clone cards:
1564 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1565 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1566 Holtek HT80232 Holtek HT80229
1568 To compile this driver as a module, choose M here and read
1569 <file:Documentation/networking/net-modules.txt>. The module
1570 will be called ne2k-pci.
1573 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1574 depends on NET_PCI && EISA && EXPERIMENTAL
1577 If you have a network (Ethernet) card of this type, say Y and read
1578 the Ethernet-HOWTO, available from
1579 <http://www.tldp.org/docs.html#howto>. Note that this driver
1580 will NOT WORK for NE3200 cards as they are completely different.
1582 To compile this driver as a module, choose M here and read
1583 <file:Documentation/networking/net-modules.txt>. The module
1584 will be called ne3210.
1587 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1588 depends on NET_PCI && EISA && EXPERIMENTAL
1591 If you have a network (Ethernet) card of this type, say Y and read
1592 the Ethernet-HOWTO, available from
1593 <http://www.tldp.org/docs.html#howto>.
1595 To compile this driver as a module, choose M here and read
1596 <file:Documentation/networking/net-modules.txt>. The module
1597 will be called es3210.
1600 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1601 depends on NET_PCI && PCI && EXPERIMENTAL
1605 This is a driver for the Fast Ethernet PCI network cards based on
1606 the RTL8139C+ chips. If you have one of those, say Y and read
1607 the Ethernet-HOWTO, available from
1608 <http://www.tldp.org/docs.html#howto>.
1610 To compile this driver as a module, choose M here: the module
1611 will be called 8139cp. This is recommended.
1614 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1615 depends on NET_PCI && PCI
1619 This is a driver for the Fast Ethernet PCI network cards based on
1620 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1621 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1623 To compile this driver as a module, choose M here: the module
1624 will be called 8139too. This is recommended.
1627 bool "Use PIO instead of MMIO"
1631 This instructs the driver to use programmed I/O ports (PIO) instead
1632 of PCI shared memory (MMIO). This can possibly solve some problems
1633 in case your mainboard has memory consistency issues. If unsure,
1636 config 8139TOO_TUNE_TWISTER
1637 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1640 This implements a function which might come in handy in case you
1641 are using low quality on long cabling. It is required for RealTek
1642 RTL-8139 revision K boards, and totally unused otherwise. It tries
1643 to match the transceiver to the cable characteristics. This is
1644 experimental since hardly documented by the manufacturer.
1648 bool "Support for older RTL-8129/8130 boards"
1651 This enables support for the older and uncommon RTL-8129 and
1652 RTL-8130 chips, which support MII via an external transceiver,
1653 instead of an internal one. Disabling this option will save some
1654 memory by making the code size smaller. If unsure, say Y.
1656 config 8139_OLD_RX_RESET
1657 bool "Use older RX-reset method"
1660 The 8139too driver was recently updated to contain a more rapid
1661 reset sequence, in the face of severe receive errors. This "new"
1662 RX-reset method should be adequate for all boards. But if you
1663 experience problems, you can enable this option to restore the
1664 old RX-reset behavior. If unsure, say N.
1667 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1668 depends on NET_PCI && PCI
1672 This is a driver for the Fast Ethernet PCI network cards based on
1673 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1674 SiS 630 and SiS 540 chipsets.
1676 This driver also supports AMD 79C901 HomePNA so that you can use
1677 your phone line as a network cable.
1679 To compile this driver as a module, choose M here: the module
1680 will be called sis900. This is recommended.
1683 tristate "SMC EtherPower II"
1684 depends on NET_PCI && PCI
1688 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1689 which is based on the SMC83c17x (EPIC/100).
1690 More specific information and updates are available from
1691 <http://www.scyld.com/network/epic100.html>.
1694 tristate "Sundance Alta support"
1695 depends on NET_PCI && PCI
1699 This driver is for the Sundance "Alta" chip.
1700 More specific information and updates are available from
1701 <http://www.scyld.com/network/sundance.html>.
1703 config SUNDANCE_MMIO
1704 bool "Use MMIO instead of PIO"
1707 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1708 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1709 is known to solve bugs on certain chips.
1714 tristate "TI ThunderLAN support"
1715 depends on NET_PCI && (PCI || EISA) && !64BIT
1717 If you have a PCI Ethernet network card based on the ThunderLAN chip
1718 which is supported by this driver, say Y and read the
1719 Ethernet-HOWTO, available from
1720 <http://www.tldp.org/docs.html#howto>.
1722 Devices currently supported by this driver are Compaq Netelligent,
1723 Compaq NetFlex and Olicom cards. Please read the file
1724 <file:Documentation/networking/tlan.txt> for more details.
1726 To compile this driver as a module, choose M here and read
1727 <file:Documentation/networking/net-modules.txt>. The module
1728 will be called tlan.
1730 Please email feedback to <torben.mathiasen@compaq.com>.
1733 tristate "VIA Rhine support"
1734 depends on NET_PCI && PCI
1738 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1739 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1740 Ethernet functions can also be found integrated on South Bridges
1743 To compile this driver as a module, choose M here. The module
1744 will be called via-rhine.
1746 config VIA_RHINE_MMIO
1747 bool "Use MMIO instead of PIO"
1748 depends on VIA_RHINE
1750 This instructs the driver to use PCI shared memory (MMIO) instead of
1751 programmed I/O ports (PIO). Enabling this gives an improvement in
1752 processing time in parts of the driver.
1756 config VIA_RHINE_NAPI
1757 bool "Use Rx Polling (NAPI)"
1758 depends on VIA_RHINE
1760 NAPI is a new driver API designed to reduce CPU and interrupt load
1761 when the driver is receiving lots of packets from the card.
1763 If your estimated Rx load is 10kpps or more, or if the card will be
1764 deployed on potentially unfriendly networks (e.g. in a firewall),
1767 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1771 bool "Philips SAA9730 Ethernet support"
1772 depends on NET_PCI && PCI && MIPS_ATLAS
1774 The SAA9730 is a combined multimedia and peripheral controller used
1775 in thin clients, Internet access terminals, and diskless
1777 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1780 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1781 depends on NET_PCI && PCI && EXPERIMENTAL
1784 This is a driver for the Fast Ethernet PCI network cards based on
1785 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1786 have one of these, say Y here.
1788 To compile this driver as a module, choose M here: the module
1789 will be called sc92031. This is recommended.
1792 bool "Pocket and portable adapters"
1795 Cute little network (Ethernet) devices which attach to the parallel
1796 port ("pocket adapters"), commonly used with laptops. If you have
1797 one of those, say Y and read the Ethernet-HOWTO, available from
1798 <http://www.tldp.org/docs.html#howto>.
1800 If you want to plug a network (or some other) card into the PCMCIA
1801 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1802 credit card size extension cards used by all modern laptops), you
1803 need the pcmcia-cs package (location contained in the file
1804 <file:Documentation/Changes>) and you can say N here.
1806 Laptop users should read the Linux Laptop home page at
1807 <http://www.linux-on-laptops.com/> or
1808 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1810 Note that the answer to this question doesn't directly affect the
1811 kernel: saying N will just cause the configurator to skip all
1812 the questions about this class of network devices. If you say Y, you
1813 will be asked for your specific device in the following questions.
1816 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1817 depends on NET_POCKET && PARPORT && X86
1820 This is a network (Ethernet) device which attaches to your parallel
1821 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1822 available from <http://www.tldp.org/docs.html#howto>, if you
1823 want to use this. If you intend to use this driver, you should have
1824 said N to the "Parallel printer support", because the two drivers
1825 don't like each other.
1827 To compile this driver as a module, choose M here: the module
1831 tristate "D-Link DE600 pocket adapter support"
1832 depends on NET_POCKET && PARPORT
1834 This is a network (Ethernet) device which attaches to your parallel
1835 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1836 Ethernet-HOWTO, available from
1837 <http://www.tldp.org/docs.html#howto>, if you want to use
1838 this. It is possible to have several devices share a single parallel
1839 port and it is safe to compile the corresponding drivers into the
1842 To compile this driver as a module, choose M here: the module
1843 will be called de600.
1846 tristate "D-Link DE620 pocket adapter support"
1847 depends on NET_POCKET && PARPORT
1849 This is a network (Ethernet) device which attaches to your parallel
1850 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1851 Ethernet-HOWTO, available from
1852 <http://www.tldp.org/docs.html#howto>, if you want to use
1853 this. It is possible to have several devices share a single parallel
1854 port and it is safe to compile the corresponding drivers into the
1857 To compile this driver as a module, choose M here: the module
1858 will be called de620.
1861 tristate "SGI Seeq ethernet controller support"
1864 Say Y here if you have an Seeq based Ethernet network card. This is
1865 used in many Silicon Graphics machines.
1868 tristate "DEC LANCE ethernet controller support"
1869 depends on MACH_DECSTATION
1872 This driver is for the series of Ethernet controllers produced by
1873 DEC (now Compaq) based on the AMD Lance chipset, including the
1874 DEPCA series. (This chipset is better known via the NE2100 cards.)
1877 bool "Motorola 68360 ethernet controller"
1880 Say Y here if you want to use the built-in ethernet controller of
1881 the Motorola 68360 processor.
1884 bool "FEC ethernet controller (of ColdFire CPUs)"
1885 depends on M523x || M527x || M5272 || M528x || M520x
1887 Say Y here if you want to use the built-in 10/100 Fast ethernet
1888 controller on some Motorola ColdFire processors.
1891 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1894 Say Y here if you want to use the second built-in 10/100 Fast
1895 ethernet controller on some Motorola ColdFire processors.
1898 tristate "NE2000 compatible support for H8/300"
1901 Say Y here if you want to use the NE2000 compatible
1902 controller on the Renesas H8/300 processor.
1904 source "drivers/net/fec_8xx/Kconfig"
1905 source "drivers/net/fs_enet/Kconfig"
1907 endif # NET_ETHERNET
1913 menuconfig NETDEV_1000
1914 bool "Ethernet (1000 Mbit)"
1918 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1919 type of Local Area Network (LAN) in universities and companies.
1921 Say Y here to get to see options for Gigabit Ethernet drivers.
1922 This option alone does not add any kernel code.
1923 Note that drivers supporting both 100 and 1000 MBit may be listed
1924 under "Ethernet (10 or 100MBit)" instead.
1926 If you say N, all options in this submenu will be skipped and disabled.
1931 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1934 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1935 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1936 adapter. The driver allows for using the Jumbo Frame option (9000
1937 bytes/frame) however it requires that your switches can handle this
1938 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1941 To compile this driver as a module, choose M here: the
1942 module will be called acenic.
1944 config ACENIC_OMIT_TIGON_I
1945 bool "Omit support for old Tigon I based AceNICs"
1948 Say Y here if you only have Tigon II based AceNICs and want to leave
1949 out support for the older Tigon I based cards which are no longer
1950 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1951 version)). This will reduce the size of the driver object by
1952 app. 100KB. If you are not sure whether your card is a Tigon I or a
1953 Tigon II, say N here.
1955 The safe and default value for this is N.
1958 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1962 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1964 D-Link DGE-550T Gigabit Ethernet Adapter.
1965 D-Link DL2000-based Gigabit Ethernet Adapter.
1966 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1968 To compile this driver as a module, choose M here: the
1969 module will be called dl2k.
1972 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1975 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1976 adapters. For more information on how to identify your adapter, go
1977 to the Adapter & Driver ID Guide at:
1979 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1981 For general information and support, go to the Intel support
1984 <http://support.intel.com>
1986 More specific information on configuring the driver is in
1987 <file:Documentation/networking/e1000.txt>.
1989 To compile this driver as a module, choose M here and read
1990 <file:Documentation/networking/net-modules.txt>. The module
1991 will be called e1000.
1994 bool "Use Rx Polling (NAPI)"
1997 NAPI is a new driver API designed to reduce CPU and interrupt load
1998 when the driver is receiving lots of packets from the card. It is
1999 still somewhat experimental and thus not yet enabled by default.
2001 If your estimated Rx load is 10kpps or more, or if the card will be
2002 deployed on potentially unfriendly networks (e.g. in a firewall),
2005 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2010 config E1000_DISABLE_PACKET_SPLIT
2011 bool "Disable Packet Split for PCI express adapters"
2014 Say Y here if you want to use the legacy receive path for PCI express
2020 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2023 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2024 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2025 use the regular e1000 driver For more information on how to
2026 identify your adapter, go to the Adapter & Driver ID Guide at:
2028 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2030 For general information and support, go to the Intel support
2033 <http://support.intel.com>
2035 More specific information on configuring the driver is in
2036 <file:Documentation/networking/e1000e.txt>.
2038 To compile this driver as a module, choose M here and read
2039 <file:Documentation/networking/net-modules.txt>. The module
2040 will be called e1000e.
2042 source "drivers/net/ixp2000/Kconfig"
2045 tristate "MyriCOM Gigabit Ethernet support"
2048 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2050 To compile this driver as a module, choose M here: the module
2051 will be called myri_sbus. This is recommended.
2054 tristate "National Semiconductor DP83820 support"
2057 This is a driver for the National Semiconductor DP83820 series
2058 of gigabit ethernet MACs. Cards using this chipset include
2059 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2060 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2064 tristate "Packet Engines Hamachi GNIC-II support"
2068 If you have a Gigabit Ethernet card of this type, say Y and read
2069 the Ethernet-HOWTO, available from
2070 <http://www.tldp.org/docs.html#howto>.
2072 To compile this driver as a module, choose M here and read
2073 <file:Documentation/networking/net-modules.txt>. The module will be
2077 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2078 depends on PCI && EXPERIMENTAL
2081 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2082 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2083 used by the Beowulf Linux cluster project. See
2084 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2085 information about this driver in particular and Beowulf in general.
2087 To compile this driver as a module, choose M here: the module
2088 will be called yellowfin. This is recommended.
2091 tristate "Realtek 8169 gigabit ethernet support"
2095 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2097 To compile this driver as a module, choose M here: the module
2098 will be called r8169. This is recommended.
2101 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2102 depends on R8169 && EXPERIMENTAL
2104 NAPI is a new driver API designed to reduce CPU and interrupt load
2105 when the driver is receiving lots of packets from the card. It is
2106 still somewhat experimental and thus not yet enabled by default.
2108 If your estimated Rx load is 10kpps or more, or if the card will be
2109 deployed on potentially unfriendly networks (e.g. in a firewall),
2112 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2119 depends on R8169 && VLAN_8021Q
2121 Say Y here for the r8169 driver to support the functions required
2122 by the kernel 802.1Q code.
2127 tristate "SB1250 Gigabit Ethernet support"
2128 depends on SIBYTE_SB1xxx_SOC
2130 This driver supports Gigabit Ethernet interfaces based on the
2131 Broadcom SiByte family of System-On-a-Chip parts. They include
2132 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2135 To compile this driver as a module, choose M here: the module
2136 will be called sb1250-mac.
2139 tristate "SiS190/SiS191 gigabit ethernet support"
2144 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2145 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2146 appear in lan on motherboard designs which are based on SiS 965
2147 and SiS 966 south bridge.
2149 To compile this driver as a module, choose M here: the module
2150 will be called sis190. This is recommended.
2153 tristate "New SysKonnect GigaEthernet support"
2157 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2158 and related Gigabit Ethernet adapters. It is a new smaller driver
2159 with better performance and more complete ethtool support.
2161 It does not support the link failover and network management
2162 features that "portable" vendor supplied sk98lin driver does.
2164 This driver supports adapters based on the original Yukon chipset:
2165 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2166 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2168 It does not support the newer Yukon2 chipset: a separate driver,
2169 sky2, is provided for Yukon2-based adapters.
2171 To compile this driver as a module, choose M here: the module
2172 will be called skge. This is recommended.
2175 tristate "SysKonnect Yukon2 support"
2179 This driver supports Gigabit Ethernet adapters based on the
2180 Marvell Yukon 2 chipset:
2181 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2182 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2184 There is companion driver for the older Marvell Yukon and
2185 Genesis based adapters: skge.
2187 To compile this driver as a module, choose M here: the module
2188 will be called sky2. This is recommended.
2191 bool "Debugging interface"
2192 depends on SKY2 && DEBUG_FS
2194 This option adds the ability to dump driver state for debugging.
2195 The file debugfs/sky2/ethX displays the state of the internal
2196 transmit and receive rings.
2201 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2204 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2205 compliant Gigabit Ethernet Adapter.
2207 This driver supports the original Yukon chipset. This driver is
2208 deprecated and will be removed from the kernel in the near future,
2209 it has been replaced by the skge driver. skge is cleaner and
2210 seems to work better.
2212 This driver does not support the newer Yukon2 chipset. A separate
2213 driver, sky2, is provided to support Yukon2-based adapters.
2215 The following adapters are supported by this driver:
2216 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2217 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2218 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2219 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2220 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2221 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2222 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2223 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2224 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2225 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2226 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2227 - EG1032 v2 Instant Gigabit Network Adapter
2228 - EG1064 v2 Instant Gigabit Network Adapter
2229 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2230 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2231 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2232 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2233 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2234 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2235 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2236 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2237 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2238 - Marvell RDK-8001 Adapter
2239 - Marvell RDK-8002 Adapter
2240 - Marvell RDK-8003 Adapter
2241 - Marvell RDK-8004 Adapter
2242 - Marvell RDK-8006 Adapter
2243 - Marvell RDK-8007 Adapter
2244 - Marvell RDK-8008 Adapter
2245 - Marvell RDK-8009 Adapter
2246 - Marvell RDK-8010 Adapter
2247 - Marvell RDK-8011 Adapter
2248 - Marvell RDK-8012 Adapter
2249 - Marvell RDK-8052 Adapter
2250 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2251 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2252 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2253 - SK-9521 10/100/1000Base-T Adapter
2254 - SK-9521 V2.0 10/100/1000Base-T Adapter
2255 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2256 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2257 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2258 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2259 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2260 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2261 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2262 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2263 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2264 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2265 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2266 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2267 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2268 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2269 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2270 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2271 - SMC EZ Card 1000 (SMC9452TXV.2)
2273 The adapters support Jumbo Frames.
2274 The dual link adapters support link-failover and dual port features.
2275 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2276 the scatter-gather functionality with sendfile(). Please refer to
2277 <file:Documentation/networking/sk98lin.txt> for more information about
2278 optional driver parameters.
2279 Questions concerning this driver may be addressed to:
2280 <linux@syskonnect.de>
2282 If you want to compile this driver as a module ( = code which can be
2283 inserted in and removed from the running kernel whenever you want),
2284 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2285 be called sk98lin. This is recommended.
2288 tristate "VIA Velocity support"
2294 If you have a VIA "Velocity" based network card say Y here.
2296 To compile this driver as a module, choose M here. The module
2297 will be called via-velocity.
2300 tristate "Broadcom Tigon3 support"
2303 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2305 To compile this driver as a module, choose M here: the module
2306 will be called tg3. This is recommended.
2309 tristate "Broadcom NetXtremeII support"
2314 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2316 To compile this driver as a module, choose M here: the module
2317 will be called bnx2. This is recommended.
2320 tristate "Spider Gigabit Ethernet driver"
2321 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2324 This driver supports the Gigabit Ethernet chips present on the
2325 Cell Processor-Based Blades from IBM.
2328 tristate "Tundra TSI108 gigabit Ethernet support"
2329 depends on TSI108_BRIDGE
2331 This driver supports Tundra TSI108 gigabit Ethernet ports.
2332 To compile this driver as a module, choose M here: the module
2333 will be called tsi108_eth.
2336 tristate "PS3 Gigabit Ethernet driver"
2339 This driver supports the network device on the PS3 game
2340 console. This driver has built-in support for Ethernet.
2342 To compile this driver as a module, choose M here: the
2343 module will be called ps3_gelic.
2346 tristate "Gianfar Ethernet"
2347 depends on 85xx || 83xx || PPC_86xx
2351 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2352 and MPC86xx family of chips, and the FEC on the 8540.
2359 tristate "Freescale QE Gigabit Ethernet"
2360 depends on QUICC_ENGINE
2363 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2364 which is available on some Freescale SOCs.
2370 config UGETH_MAGIC_PACKET
2371 bool "Magic Packet detection support"
2374 config UGETH_FILTERING
2375 bool "Mac address filtering support"
2378 config UGETH_TX_ON_DEMAND
2379 bool "Transmit on Demand support"
2383 tristate "MV-643XX Ethernet support"
2384 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32)
2387 This driver supports the gigabit Ethernet on the Marvell MV643XX
2388 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2389 Pegasos II, amongst other PPC and MIPS boards.
2392 tristate "QLogic QLA3XXX Network Driver Support"
2395 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2397 To compile this driver as a module, choose M here: the module
2398 will be called qla3xxx.
2401 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2402 depends on PCI && EXPERIMENTAL
2406 This driver supports the Attansic L1 gigabit ethernet adapter.
2408 To compile this driver as a module, choose M here. The module
2409 will be called atl1.
2414 # 10 Gigabit Ethernet
2417 menuconfig NETDEV_10000
2418 bool "Ethernet (10000 Mbit)"
2422 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2423 This option alone does not add any kernel code.
2425 If you say N, all options in this submenu will be skipped and disabled.
2430 tristate "Chelsio 10Gb Ethernet support"
2434 This driver supports Chelsio gigabit and 10-gigabit
2435 Ethernet cards. More information about adapter features and
2436 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2438 For general information about Chelsio and our products, visit
2439 our website at <http://www.chelsio.com>.
2441 For customer support, please visit our customer support page at
2442 <http://www.chelsio.com/support.htm>.
2444 Please send feedback to <linux-bugs@chelsio.com>.
2446 To compile this driver as a module, choose M here: the module
2447 will be called cxgb.
2449 config CHELSIO_T1_1G
2450 bool "Chelsio gigabit Ethernet support"
2451 depends on CHELSIO_T1
2453 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2454 are using only 10G cards say 'N' here.
2456 config CHELSIO_T1_NAPI
2457 bool "Use Rx Polling (NAPI)"
2458 depends on CHELSIO_T1
2461 NAPI is a driver API designed to reduce CPU and interrupt load
2462 when the driver is receiving lots of packets from the card.
2465 tristate "Chelsio Communications T3 10Gb Ethernet support"
2469 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2472 For general information about Chelsio and our products, visit
2473 our website at <http://www.chelsio.com>.
2475 For customer support, please visit our customer support page at
2476 <http://www.chelsio.com/support.htm>.
2478 Please send feedback to <linux-bugs@chelsio.com>.
2480 To compile this driver as a module, choose M here: the module
2481 will be called cxgb3.
2484 tristate "eHEA Ethernet support"
2488 This driver supports the IBM pSeries eHEA ethernet adapter.
2490 To compile the driver as a module, choose M here. The module
2491 will be called ehea.
2494 tristate "Intel(R) 10GbE PCI Express adapters support"
2497 This driver supports Intel(R) 10GbE PCI Express family of
2498 adapters. For more information on how to identify your adapter, go
2499 to the Adapter & Driver ID Guide at:
2501 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2503 For general information and support, go to the Intel support
2506 <http://support.intel.com>
2508 More specific information on configuring the driver is in
2509 <file:Documentation/networking/ixgbe.txt>.
2511 To compile this driver as a module, choose M here and read
2512 <file:Documentation/networking/net-modules.txt>. The module
2513 will be called ixgbe.
2516 tristate "Intel(R) PRO/10GbE support"
2519 This driver supports Intel(R) PRO/10GbE family of adapters for
2520 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2521 instead. For more information on how to identify your adapter, go
2522 to the Adapter & Driver ID Guide at:
2524 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2526 For general information and support, go to the Intel support
2529 <http://support.intel.com>
2531 More specific information on configuring the driver is in
2532 <file:Documentation/networking/ixgb.txt>.
2534 To compile this driver as a module, choose M here and read
2535 <file:Documentation/networking/net-modules.txt>. The module
2536 will be called ixgb.
2539 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2540 depends on IXGB && EXPERIMENTAL
2542 NAPI is a new driver API designed to reduce CPU and interrupt load
2543 when the driver is receiving lots of packets from the card. It is
2544 still somewhat experimental and thus not yet enabled by default.
2546 If your estimated Rx load is 10kpps or more, or if the card will be
2547 deployed on potentially unfriendly networks (e.g. in a firewall),
2550 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2556 tristate "S2IO 10Gbe XFrame NIC"
2559 This driver supports the 10Gbe XFrame NIC of S2IO.
2560 More specific information on configuring the driver is in
2561 <file:Documentation/networking/s2io.txt>.
2564 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2565 depends on S2IO && EXPERIMENTAL
2567 NAPI is a new driver API designed to reduce CPU and interrupt load
2568 when the driver is receiving lots of packets from the card. It is
2569 still somewhat experimental and thus not yet enabled by default.
2571 If your estimated Rx load is 10kpps or more, or if the card will be
2572 deployed on potentially unfriendly networks (e.g. in a firewall),
2575 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2581 tristate "Myricom Myri-10G Ethernet support"
2587 This driver supports Myricom Myri-10G Dual Protocol interface in
2588 Ethernet mode. If the eeprom on your board is not recent enough,
2589 you will need a newer firmware image.
2590 You may get this image or more information, at:
2592 <http://www.myri.com/scs/download-Myri10GE.html>
2594 To compile this driver as a module, choose M here and read
2595 <file:Documentation/networking/net-modules.txt>. The module
2596 will be called myri10ge.
2599 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2602 This enables the support for NetXen's Gigabit Ethernet card.
2605 tristate "PA Semi 1/10Gbit MAC"
2606 depends on PPC64 && PCI
2609 This driver supports the on-chip 1/10Gbit Ethernet controller on
2610 PA Semi's PWRficient line of chips.
2618 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2619 depends on MLX4_CORE
2622 This option causes debugging code to be compiled into the
2623 mlx4_core driver. The output can be turned on via the
2624 debug_level module parameter (which can also be set after
2625 the driver is loaded through sysfs).
2628 tristate "Tehuti Networks 10G Ethernet"
2631 Tehuti Networks 10G Ethernet NIC
2633 endif # NETDEV_10000
2635 source "drivers/net/tokenring/Kconfig"
2637 source "drivers/net/wireless/Kconfig"
2639 source "drivers/net/usb/Kconfig"
2641 source "drivers/net/pcmcia/Kconfig"
2643 source "drivers/net/wan/Kconfig"
2645 source "drivers/atm/Kconfig"
2647 source "drivers/s390/net/Kconfig"
2649 config XEN_NETDEV_FRONTEND
2650 tristate "Xen network device frontend driver"
2654 The network device frontend driver allows the kernel to
2655 access network devices exported exported by a virtual
2656 machine containing a physical network device driver. The
2657 frontend driver is intended for unprivileged guest domains;
2658 if you are compiling a kernel for a Xen guest, you almost
2659 certainly want to enable this.
2662 tristate "iSeries Virtual Ethernet driver support"
2663 depends on PPC_ISERIES
2666 tristate "RapidIO Ethernet over messaging driver support"
2669 config RIONET_TX_SIZE
2670 int "Number of outbound queue entries"
2674 config RIONET_RX_SIZE
2675 int "Number of inbound queue entries"
2680 bool "FDDI driver support"
2681 depends on (PCI || EISA || TC)
2683 Fiber Distributed Data Interface is a high speed local area network
2684 design; essentially a replacement for high speed Ethernet. FDDI can
2685 run over copper or fiber. If you are connected to such a network and
2686 want a driver for the FDDI card in your computer, say Y here (and
2687 then also Y to the driver for your FDDI card, below). Most people
2691 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2692 depends on FDDI && (PCI || EISA || TC)
2694 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2695 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2696 to a local FDDI network.
2698 To compile this driver as a module, choose M here: the module
2699 will be called defxx. If unsure, say N.
2703 prompt "Use MMIO instead of PIO" if PCI || EISA
2705 default n if PCI || EISA
2708 This instructs the driver to use EISA or PCI memory-mapped I/O
2709 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2710 Enabling this gives an improvement in processing time in parts
2711 of the driver, but it may cause problems with EISA (DEFEA)
2712 adapters. TURBOchannel does not have the concept of I/O ports,
2713 so MMIO is always used for these (DEFTA) adapters.
2718 tristate "SysKonnect FDDI PCI support"
2719 depends on FDDI && PCI
2722 Say Y here if you have a SysKonnect FDDI PCI adapter.
2723 The following adapters are supported by this driver:
2724 - SK-5521 (SK-NET FDDI-UP)
2725 - SK-5522 (SK-NET FDDI-UP DAS)
2726 - SK-5541 (SK-NET FDDI-FP)
2727 - SK-5543 (SK-NET FDDI-LP)
2728 - SK-5544 (SK-NET FDDI-LP DAS)
2729 - SK-5821 (SK-NET FDDI-UP64)
2730 - SK-5822 (SK-NET FDDI-UP64 DAS)
2731 - SK-5841 (SK-NET FDDI-FP64)
2732 - SK-5843 (SK-NET FDDI-LP64)
2733 - SK-5844 (SK-NET FDDI-LP64 DAS)
2734 - Netelligent 100 FDDI DAS Fibre SC
2735 - Netelligent 100 FDDI SAS Fibre SC
2736 - Netelligent 100 FDDI DAS UTP
2737 - Netelligent 100 FDDI SAS UTP
2738 - Netelligent 100 FDDI SAS Fibre MIC
2740 Read <file:Documentation/networking/skfp.txt> for information about
2743 Questions concerning this driver can be addressed to:
2744 <linux@syskonnect.de>
2746 To compile this driver as a module, choose M here: the module
2747 will be called skfp. This is recommended.
2750 bool "HIPPI driver support (EXPERIMENTAL)"
2751 depends on EXPERIMENTAL && INET && PCI
2753 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2754 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2755 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2756 single-mode). HIPPI networks are commonly used for clusters and to
2757 connect to super computers. If you are connected to a HIPPI network
2758 and have a HIPPI network card in your computer that you want to use
2759 under Linux, say Y here (you must also remember to enable the driver
2760 for your HIPPI card below). Most people will say N here.
2763 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2764 depends on HIPPI && PCI
2766 Say Y here if this is your PCI HIPPI network card.
2768 To compile this driver as a module, choose M here: the module
2769 will be called rrunner. If unsure, say N.
2771 config ROADRUNNER_LARGE_RINGS
2772 bool "Use large TX/RX rings (EXPERIMENTAL)"
2773 depends on ROADRUNNER
2775 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2776 of additional memory to allow for fastest operation, both for
2777 transmitting and receiving. This memory cannot be used by any other
2778 kernel code or by user space programs. Say Y here only if you have
2782 tristate "PLIP (parallel port) support"
2785 PLIP (Parallel Line Internet Protocol) is used to create a
2786 reasonably fast mini network consisting of two (or, rarely, more)
2787 local machines. A PLIP link from a Linux box is a popular means to
2788 install a Linux distribution on a machine which doesn't have a
2789 CD-ROM drive (a minimal system has to be transferred with floppies
2790 first). The kernels on both machines need to have this PLIP option
2791 enabled for this to work.
2793 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2794 ports (the connectors at the computers with 25 holes) are connected
2795 with "null printer" or "Turbo Laplink" cables which can transmit 4
2796 bits at a time (mode 0) or with special PLIP cables, to be used on
2797 bidirectional parallel ports only, which can transmit 8 bits at a
2798 time (mode 1); you can find the wiring of these cables in
2799 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2800 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2801 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2802 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2803 and winsock or NCSA's telnet.
2805 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2806 as the NET-3-HOWTO, both available from
2807 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2808 protocol has been changed and this PLIP driver won't work together
2809 with the PLIP support in Linux versions 1.0.x. This option enlarges
2810 your kernel by about 8 KB.
2812 To compile this driver as a module, choose M here and read
2813 <file:Documentation/networking/net-modules.txt>. The module will be
2814 called plip. If unsure, say Y or M, in case you buy a laptop
2818 tristate "PPP (point-to-point protocol) support"
2821 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2822 the same purpose: sending Internet traffic over telephone (and other
2823 serial) lines. Ask your access provider if they support it, because
2824 otherwise you can't use it; most Internet access providers these
2825 days support PPP rather than SLIP.
2827 To use PPP, you need an additional program called pppd as described
2828 in the PPP-HOWTO, available at
2829 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2830 the version of pppd recommended in <file:Documentation/Changes>.
2831 The PPP option enlarges your kernel by about 16 KB.
2833 There are actually two versions of PPP: the traditional PPP for
2834 asynchronous lines, such as regular analog phone lines, and
2835 synchronous PPP which can be used over digital ISDN lines for
2836 example. If you want to use PPP over phone lines or other
2837 asynchronous serial lines, you need to say Y (or M) here and also to
2838 the next option, "PPP support for async serial ports". For PPP over
2839 synchronous lines, you should say Y (or M) here and to "Support
2840 synchronous PPP", below.
2842 If you said Y to "Version information on all symbols" above, then
2843 you cannot compile the PPP driver into the kernel; you can then only
2844 compile it as a module. To compile this driver as a module, choose M
2845 here and read <file:Documentation/networking/net-modules.txt>.
2846 The module will be called ppp_generic.
2848 config PPP_MULTILINK
2849 bool "PPP multilink support (EXPERIMENTAL)"
2850 depends on PPP && EXPERIMENTAL
2852 PPP multilink is a protocol (defined in RFC 1990) which allows you
2853 to combine several (logical or physical) lines into one logical PPP
2854 connection, so that you can utilize your full bandwidth.
2856 This has to be supported at the other end as well and you need a
2857 version of the pppd daemon which understands the multilink protocol.
2862 bool "PPP filtering"
2865 Say Y here if you want to be able to filter the packets passing over
2866 PPP interfaces. This allows you to control which packets count as
2867 activity (i.e. which packets will reset the idle timer or bring up
2868 a demand-dialed link) and which packets are to be dropped entirely.
2869 You need to say Y here if you wish to use the pass-filter and
2870 active-filter options to pppd.
2875 tristate "PPP support for async serial ports"
2879 Say Y (or M) here if you want to be able to use PPP over standard
2880 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2881 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2884 To compile this driver as a module, choose M here.
2889 tristate "PPP support for sync tty ports"
2892 Say Y (or M) here if you want to be able to use PPP over synchronous
2893 (HDLC) tty devices, such as the SyncLink adapter. These devices
2894 are often used for high-speed leased lines like T1/E1.
2896 To compile this driver as a module, choose M here.
2899 tristate "PPP Deflate compression"
2904 Support for the Deflate compression method for PPP, which uses the
2905 Deflate algorithm (the same algorithm that gzip uses) to compress
2906 each PPP packet before it is sent over the wire. The machine at the
2907 other end of the PPP link (usually your ISP) has to support the
2908 Deflate compression method as well for this to be useful. Even if
2909 they don't support it, it is safe to say Y here.
2911 To compile this driver as a module, choose M here.
2914 tristate "PPP BSD-Compress compression"
2917 Support for the BSD-Compress compression method for PPP, which uses
2918 the LZW compression method to compress each PPP packet before it is
2919 sent over the wire. The machine at the other end of the PPP link
2920 (usually your ISP) has to support the BSD-Compress compression
2921 method as well for this to be useful. Even if they don't support it,
2922 it is safe to say Y here.
2924 The PPP Deflate compression method ("PPP Deflate compression",
2925 above) is preferable to BSD-Compress, because it compresses better
2928 Note that the BSD compression code will always be compiled as a
2929 module; it is called bsd_comp and will show up in the directory
2930 modules once you have said "make modules". If unsure, say N.
2933 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2934 depends on PPP && EXPERIMENTAL
2940 Support for the MPPE Encryption protocol, as employed by the
2941 Microsoft Point-to-Point Tunneling Protocol.
2943 See http://pptpclient.sourceforge.net/ for information on
2944 configuring PPTP clients and servers to utilize this method.
2947 tristate "PPP over Ethernet (EXPERIMENTAL)"
2948 depends on EXPERIMENTAL && PPP
2950 Support for PPP over Ethernet.
2952 This driver requires the latest version of pppd from the CVS
2953 repository at cvs.samba.org. Alternatively, see the
2954 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2955 which contains instruction on how to use this driver (under
2956 the heading "Kernel mode PPPoE").
2959 tristate "PPP over ATM"
2960 depends on ATM && PPP
2962 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2963 This implementation does not yet comply with section 8 of RFC2364,
2964 which can lead to bad results if the ATM peer loses state and
2965 changes its encapsulation unilaterally.
2968 tristate "PPP over L2TP (EXPERIMENTAL)"
2969 depends on EXPERIMENTAL && PPP && INET
2971 Support for PPP-over-L2TP socket family. L2TP is a protocol
2972 used by ISPs and enterprises to tunnel PPP traffic over UDP
2973 tunnels. L2TP is replacing PPTP for VPN uses.
2975 This kernel component handles only L2TP data packets: a
2976 userland daemon handles L2TP the control protocol (tunnel
2977 and session setup). One such daemon is OpenL2TP
2978 (http://openl2tp.sourceforge.net/).
2981 tristate "SLIP (serial line) support"
2983 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2984 connect to your Internet service provider or to connect to some
2985 other local Unix box or if you want to configure your Linux box as a
2986 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2987 Internet Protocol) is a protocol used to send Internet traffic over
2988 serial connections such as telephone lines or null modem cables;
2989 nowadays, the protocol PPP is more commonly used for this same
2992 Normally, your access provider has to support SLIP in order for you
2993 to be able to use it, but there is now a SLIP emulator called SLiRP
2994 around (available from
2995 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2996 allows you to use SLIP over a regular dial up shell connection. If
2997 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2998 NET-3-HOWTO, available from
2999 <http://www.tldp.org/docs.html#howto>, explains how to
3000 configure SLIP. Note that you don't need this option if you just
3001 want to run term (term is a program which gives you almost full
3002 Internet connectivity if you have a regular dial up shell account on
3003 some Internet connected Unix computer. Read
3004 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3005 support will enlarge your kernel by about 4 KB. If unsure, say N.
3007 To compile this driver as a module, choose M here and read
3008 <file:Documentation/networking/net-modules.txt>. The module will be
3011 config SLIP_COMPRESSED
3012 bool "CSLIP compressed headers"
3016 This protocol is faster than SLIP because it uses compression on the
3017 TCP/IP headers (not on the data itself), but it has to be supported
3018 on both ends. Ask your access provider if you are not sure and
3019 answer Y, just in case. You will still be able to use plain SLIP. If
3020 you plan to use SLiRP, the SLIP emulator (available from
3021 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3022 allows you to use SLIP over a regular dial up shell connection, you
3023 definitely want to say Y here. The NET-3-HOWTO, available from
3024 <http://www.tldp.org/docs.html#howto>, explains how to configure
3025 CSLIP. This won't enlarge your kernel.
3030 This option enables Van Jacobsen serial line header compression
3034 bool "Keepalive and linefill"
3037 Adds additional capabilities to the SLIP driver to support the
3038 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3041 config SLIP_MODE_SLIP6
3042 bool "Six bit SLIP encapsulation"
3045 Just occasionally you may need to run IP over hostile serial
3046 networks that don't pass all control characters or are only seven
3047 bit. Saying Y here adds an extra mode you can use with SLIP:
3048 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3049 the serial device. Naturally, this has to be supported at the other
3050 end of the link as well. It's good enough, for example, to run IP
3051 over the async ports of a Camtec JNT Pad. If unsure, say N.
3054 bool "Fibre Channel driver support"
3055 depends on SCSI && PCI
3057 Fibre Channel is a high speed serial protocol mainly used to connect
3058 large storage devices to the computer; it is compatible with and
3059 intended to replace SCSI.
3061 If you intend to use Fibre Channel, you need to have a Fibre channel
3062 adaptor card in your computer; say Y here and to the driver for your
3063 adaptor below. You also should have said Y to "SCSI support" and
3064 "SCSI generic support".
3067 tristate "Traffic Shaper (OBSOLETE)"
3068 depends on EXPERIMENTAL
3070 The traffic shaper is a virtual network device that allows you to
3071 limit the rate of outgoing data flow over some other network device.
3072 The traffic that you want to slow down can then be routed through
3073 these virtual devices. See
3074 <file:Documentation/networking/shaper.txt> for more information.
3076 An alternative to this traffic shaper are traffic schedulers which
3077 you'll get if you say Y to "QoS and/or fair queuing" in
3078 "Networking options".
3080 To compile this driver as a module, choose M here: the module
3081 will be called shaper. If unsure, say N.
3084 tristate "Network console logging support (EXPERIMENTAL)"
3085 depends on EXPERIMENTAL
3087 If you want to log kernel messages over the network, enable this.
3088 See <file:Documentation/networking/netconsole.txt> for details.
3090 config NETCONSOLE_DYNAMIC
3091 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3092 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3095 This option enables the ability to dynamically reconfigure target
3096 parameters (interface, IP addresses, port numbers, MAC addresses)
3097 at runtime through a userspace interface exported using configfs.
3098 See <file:Documentation/networking/netconsole.txt> for details.
3104 bool "Netpoll traffic trapping"
3108 config NET_POLL_CONTROLLER