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.
168 source "drivers/net/arcnet/Kconfig"
170 source "drivers/net/phy/Kconfig"
176 menuconfig NET_ETHERNET
177 bool "Ethernet (10 or 100Mbit)"
180 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
181 type of Local Area Network (LAN) in universities and companies.
183 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
184 coaxial cable, linking computers in a chain), 10BASE-T or twisted
185 pair (10 Mbps over twisted pair cable, linking computers to central
186 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
187 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
188 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
189 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
190 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
191 Ethernet (1 Gbps over optical fiber or short copper links).
193 If your Linux machine will be connected to an Ethernet and you have
194 an Ethernet network interface card (NIC) installed in your computer,
195 say Y here and read the Ethernet-HOWTO, available from
196 <http://www.tldp.org/docs.html#howto>. You will then also have
197 to say Y to the driver for your particular NIC.
199 Note that the answer to this question won't directly affect the
200 kernel: saying N will just cause the configurator to skip all
201 the questions about Ethernet network cards. If unsure, say N.
206 tristate "Generic Media Independent Interface device support"
208 Most ethernet controllers have MII transceiver either as an external
209 or internal device. It is safe to say Y or M here even if your
210 ethernet card lack MII.
213 tristate "Atmel MACB support"
214 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263
217 The Atmel MACB ethernet interface is found on many AT32 and AT91
218 parts. Say Y to include support for the MACB chip.
220 To compile this driver as a module, choose M here: the module
223 source "drivers/net/arm/Kconfig"
226 tristate "ASIX AX88796 NE2000 clone support"
227 depends on ARM || MIPS
231 AX88796 driver, using platform bus to provide
232 chip detection and resources
235 tristate "MACE (Power Mac ethernet) support"
236 depends on PPC_PMAC && PPC32
239 Power Macintoshes and clones with Ethernet built-in on the
240 motherboard will usually use a MACE (Medium Access Control for
241 Ethernet) interface. Say Y to include support for the MACE chip.
243 To compile this driver as a module, choose M here: the module
246 config MACE_AAUI_PORT
247 bool "Use AAUI port instead of TP by default"
250 Some Apple machines (notably the Apple Network Server) which use the
251 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
252 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
253 Y here if you have such a machine. If unsure, say N.
254 The driver will default to AAUI on ANS anyway, and if you use it as
255 a module, you can provide the port_aaui=0|1 to force the driver.
258 tristate "BMAC (G3 ethernet) support"
259 depends on PPC_PMAC && PPC32
262 Say Y for support of BMAC Ethernet interfaces. These are used on G3
265 To compile this driver as a module, choose M here: the module
269 tristate "Ariadne support"
272 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
275 To compile this driver as a module, choose M here: the module
276 will be called ariadne.
279 tristate "A2065 support"
283 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
286 To compile this driver as a module, choose M here: the module
287 will be called a2065.
290 tristate "Hydra support"
294 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
296 To compile this driver as a module, choose M here: the module
297 will be called hydra.
300 tristate "Zorro NS8390-based Ethernet support"
304 This driver is for Zorro Ethernet cards using an NS8390-compatible
305 chipset, like the Village Tronic Ariadne II and the Individual
306 Computers X-Surf Ethernet cards. If you have such a card, say Y.
309 To compile this driver as a module, choose M here: the module
310 will be called zorro8390.
313 tristate "PCMCIA NE2000 support"
314 depends on AMIGA_PCMCIA
317 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
320 To compile this driver as a module, choose M here: the module
324 tristate "Apollo 3c505 support"
327 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
328 If you don't have one made for Apollos, you can use one from a PC,
329 except that your Apollo won't be able to boot from it (because the
330 code in the ROM will be for a PC).
333 bool "Macintosh NS 8390 based ethernet cards"
337 If you want to include a driver to support Nubus or LC-PDS
338 Ethernet cards using an NS8390 chipset or its equivalent, say Y
339 and read the Ethernet-HOWTO, available from
340 <http://www.tldp.org/docs.html#howto>.
343 tristate "Macintosh CS89x0 based ethernet cards"
346 Support for CS89x0 chipset based Ethernet cards. If you have a
347 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
348 read the Ethernet-HOWTO, available from
349 <http://www.tldp.org/docs.html#howto>.
351 To compile this driver as a module, choose M here and read
352 <file:Documentation/networking/net-modules.txt>. This module will
356 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
359 Support for NatSemi SONIC based Ethernet devices. This includes
360 the onboard Ethernet in many Quadras as well as some LC-PDS,
361 a few Nubus and all known Comm Slot Ethernet cards. If you have
362 one of these say Y and read the Ethernet-HOWTO, available from
363 <http://www.tldp.org/docs.html#howto>.
365 To compile this driver as a module, choose M here and read
366 <file:Documentation/networking/net-modules.txt>. This module will
370 bool "Macintosh (AV) onboard MACE ethernet"
374 Support for the onboard AMD 79C940 MACE Ethernet controller used in
375 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
376 say Y and read the Ethernet-HOWTO, available from
377 <http://www.tldp.org/docs.html#howto>.
380 tristate "MVME147 (Lance) Ethernet support"
384 Support for the on-board Ethernet interface on the Motorola MVME147
385 single-board computer. Say Y here to include the
386 driver for this chip in your kernel.
387 To compile this driver as a module, choose M here.
390 tristate "MVME16x Ethernet support"
393 This is the driver for the Ethernet interface on the Motorola
394 MVME162, 166, 167, 172 and 177 boards. 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 "BVME6000 Ethernet support"
402 This is the driver for the Ethernet interface on BVME4000 and
403 BVME6000 VME boards. Say Y here to include the driver for this chip
405 To compile this driver as a module, choose M here.
408 tristate "Atari Lance support"
411 Say Y to include support for several Atari Ethernet adapters based
412 on the AMD Lance chipset: RieblCard (with or without battery), or
413 PAMCard VME (also the version by Rhotron, with different addresses).
416 tristate "Sun3/Sun3x on-board LANCE support"
417 depends on SUN3 || SUN3X
419 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
420 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
421 here to compile in the Linux driver for this and enable Ethernet.
422 General Linux information on the Sun 3 and 3x series (now
424 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
426 If you're not building a kernel for a Sun 3, say N.
429 bool "Sun3 on-board Intel 82586 support"
432 This driver enables support for the on-board Intel 82586 based
433 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
434 that this driver does not support 82586-based adapters on additional
438 bool "HP on-board LANCE support"
442 If you want to use the builtin "LANCE" Ethernet controller on an
443 HP300 machine, say Y here.
446 tristate "Lasi ethernet"
449 Say Y here to support the builtin Intel 82596 ethernet controller
450 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
453 tristate "SNI RM ethernet"
454 depends on NET_ETHERNET && SNI_RM
456 Say Y here to support the on-board Intel 82596 ethernet controller
457 built into SNI RM machines.
459 config MIPS_JAZZ_SONIC
460 tristate "MIPS JAZZ onboard SONIC Ethernet support"
463 This is the driver for the onboard card of MIPS Magnum 4000,
464 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
466 config MIPS_AU1X00_ENET
467 bool "MIPS AU1000 Ethernet support"
468 depends on SOC_AU1X00
472 If you have an Alchemy Semi AU1X00 based system
473 say Y. Otherwise, say N.
475 config NET_SB1250_MAC
476 tristate "SB1250 Ethernet support"
477 depends on SIBYTE_SB1xxx_SOC
480 bool "SGI IOC3 Ethernet"
481 depends on PCI && SGI_IP27
485 If you have a network (Ethernet) card of this type, say Y and read
486 the Ethernet-HOWTO, available from
487 <http://www.tldp.org/docs.html#howto>.
490 tristate "MIPS simulator Network device"
493 The MIPSNET device is a simple Ethernet network device which is
494 emulated by the MIPS Simulator.
495 If you are not using a MIPSsim or are unsure, say N.
497 config SGI_O2MACE_ETH
498 tristate "SGI O2 MACE Fast Ethernet support"
499 depends on SGI_IP32=y
502 tristate "National DP83902AV support"
506 Support for cards based on the National Semiconductor DP83902AV
507 ST-NIC Serial Network Interface Controller for Twisted Pair. This
508 is a 10Mbit/sec Ethernet controller. Product overview and specs at
509 <http://www.national.com/pf/DP/DP83902A.html>.
514 tristate "Sun LANCE support"
518 This driver supports the "le" interface present on all 32-bit Sparc
519 systems, on some older Ultra systems and as an Sbus option. These
520 cards are based on the AMD Lance chipset, which is better known
521 via the NE2100 cards.
523 To compile this driver as a module, choose M here: the module
524 will be called sunlance.
527 tristate "Sun Happy Meal 10/100baseT support"
528 depends on SBUS || PCI
531 This driver supports the "hme" interface present on most Ultra
532 systems and as an option on older Sbus systems. This driver supports
533 both PCI and Sbus devices. This driver also supports the "qfe" quad
534 100baseT device available in both PCI and Sbus configurations.
536 To compile this driver as a module, choose M here: the module
537 will be called sunhme.
540 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
541 depends on SBUS && EXPERIMENTAL
544 This driver supports the "be" interface available as an Sbus option.
545 This is Sun's older 100baseT Ethernet device.
547 To compile this driver as a module, choose M here: the module
548 will be called sunbmac.
551 tristate "Sun QuadEthernet support"
555 This driver supports the "qe" 10baseT Ethernet device, available as
556 an Sbus option. Note that this is not the same as Quad FastEthernet
557 "qfe" which is supported by the Happy Meal driver instead.
559 To compile this driver as a module, choose M here: the module
560 will be called sunqe.
563 tristate "Sun GEM support"
567 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
568 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
571 tristate "Sun Cassini support"
575 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
576 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
579 tristate "Sun Virtual Network support"
582 Support for virtual network devices under Sun Logical Domains.
584 config NET_VENDOR_3COM
586 depends on ISA || EISA || MCA || PCI
588 If you have a network (Ethernet) card belonging to this class, say Y
589 and read the Ethernet-HOWTO, available from
590 <http://www.tldp.org/docs.html#howto>.
592 Note that the answer to this question doesn't directly affect the
593 kernel: saying N will just cause the configurator to skip all
594 the questions about 3COM cards. If you say Y, you will be asked for
595 your specific card in the following questions.
598 tristate "3c501 \"EtherLink\" support"
599 depends on NET_VENDOR_3COM && ISA
601 If you have a network (Ethernet) card of this type, say Y and read
602 the Ethernet-HOWTO, available from
603 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
604 new card, since the 3c501 is slow, broken, and obsolete: you will
605 have problems. Some people suggest to ping ("man ping") a nearby
606 machine every minute ("man cron") when using this card.
608 To compile this driver as a module, choose M here and read
609 <file:Documentation/networking/net-modules.txt>. The module
610 will be called 3c501.
613 tristate "3c503 \"EtherLink II\" support"
614 depends on NET_VENDOR_3COM && ISA
617 If you have a network (Ethernet) card of this type, say Y and read
618 the Ethernet-HOWTO, available from
619 <http://www.tldp.org/docs.html#howto>.
621 To compile this driver as a module, choose M here and read
622 <file:Documentation/networking/net-modules.txt>. The module
623 will be called 3c503.
626 tristate "3c505 \"EtherLink Plus\" support"
627 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
629 Information about this network (Ethernet) card can be found in
630 <file:Documentation/networking/3c505.txt>. If you have a card of
631 this type, say Y and read the Ethernet-HOWTO, available from
632 <http://www.tldp.org/docs.html#howto>.
634 To compile this driver as a module, choose M here and read
635 <file:Documentation/networking/net-modules.txt>. The module
636 will be called 3c505.
639 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
640 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
642 If you have a network (Ethernet) card of this type, say Y and read
643 the Ethernet-HOWTO, available from
644 <http://www.tldp.org/docs.html#howto>.
646 To compile this driver as a module, choose M here and read
647 <file:Documentation/networking/net-modules.txt>. The module
648 will be called 3c507.
651 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
652 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
654 If you have a network (Ethernet) card belonging to the 3Com
655 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
656 from <http://www.tldp.org/docs.html#howto>.
658 If your card is not working you may need to use the DOS
659 setup disk to disable Plug & Play mode, and to select the default
662 To compile this driver as a module, choose M here and read
663 <file:Documentation/networking/net-modules.txt>. The module
664 will be called 3c509.
667 tristate "3c515 ISA \"Fast EtherLink\""
668 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
670 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
671 network card, say Y and read the Ethernet-HOWTO, available from
672 <http://www.tldp.org/docs.html#howto>.
674 To compile this driver as a module, choose M here and read
675 <file:Documentation/networking/net-modules.txt>. The module
676 will be called 3c515.
679 tristate "3c523 \"EtherLink/MC\" support"
680 depends on NET_VENDOR_3COM && MCA_LEGACY
682 If you have a network (Ethernet) card of this type, say Y and read
683 the Ethernet-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>.
686 To compile this driver as a module, choose M here and read
687 <file:Documentation/networking/net-modules.txt>. The module
688 will be called 3c523.
691 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
692 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
694 If you have a network (Ethernet) card of this type, say Y and read
695 the Ethernet-HOWTO, available from
696 <http://www.tldp.org/docs.html#howto>.
698 To compile this driver as a module, choose M here and read
699 <file:Documentation/networking/net-modules.txt>. The module
700 will be called 3c527.
703 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
704 depends on NET_VENDOR_3COM && (PCI || EISA)
707 This option enables driver support for a large number of 10Mbps and
708 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
710 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
711 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
712 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
713 "Tornado" (3c905) PCI
714 "Hurricane" (3c555/3cSOHO) PCI
716 If you have such a card, say Y and read the Ethernet-HOWTO,
717 available from <http://www.tldp.org/docs.html#howto>. More
718 specific information is in
719 <file:Documentation/networking/vortex.txt> and in the comments at
720 the beginning of <file:drivers/net/3c59x.c>.
722 To compile this support as a module, choose M here and read
723 <file:Documentation/networking/net-modules.txt>.
726 tristate "3cr990 series \"Typhoon\" support"
727 depends on NET_VENDOR_3COM && PCI
730 This option enables driver support for the 3cr990 series of cards:
732 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
733 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
734 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
736 If you have a network (Ethernet) card of this type, say Y and read
737 the Ethernet-HOWTO, available from
738 <http://www.tldp.org/docs.html#howto>.
740 To compile this driver as a module, choose M here and read
741 <file:Documentation/networking/net-modules.txt>. The module
742 will be called typhoon.
745 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
746 depends on ISA && ISA_DMA_API
748 If you have a network (Ethernet) card of this type, say Y and read
749 the Ethernet-HOWTO, available from
750 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
753 To compile this driver as a module, choose M here: the module
754 will be called lance. This is recommended.
756 config NET_VENDOR_SMC
757 bool "Western Digital/SMC cards"
758 depends on ISA || MCA || EISA || MAC
760 If you have a network (Ethernet) card belonging to this class, say Y
761 and read the Ethernet-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>.
764 Note that the answer to this question doesn't directly affect the
765 kernel: saying N will just cause the configurator to skip all
766 the questions about Western Digital cards. If you say Y, you will be
767 asked for your specific card in the following questions.
770 tristate "WD80*3 support"
771 depends on NET_VENDOR_SMC && ISA
774 If you have a network (Ethernet) card of this type, say Y and read
775 the Ethernet-HOWTO, available from
776 <http://www.tldp.org/docs.html#howto>.
778 To compile this driver as a module, choose M here and read
779 <file:Documentation/networking/net-modules.txt>. The module
783 tristate "SMC Ultra MCA support"
784 depends on NET_VENDOR_SMC && MCA
787 If you have a network (Ethernet) card of this type and are running
788 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
789 available from <http://www.tldp.org/docs.html#howto>.
791 To compile this driver as a module, choose M here and read
792 <file:Documentation/networking/net-modules.txt>. The module
793 will be called smc-mca.
796 tristate "SMC Ultra support"
797 depends on NET_VENDOR_SMC && ISA
800 If you have a network (Ethernet) card of this type, say Y and read
801 the Ethernet-HOWTO, available from
802 <http://www.tldp.org/docs.html#howto>.
804 Important: There have been many reports that, with some motherboards
805 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
806 such as some BusLogic models) causes corruption problems with many
807 operating systems. The Linux smc-ultra driver has a work-around for
808 this but keep it in mind if you have such a SCSI card and have
811 To compile this driver as a module, choose M here and read
812 <file:Documentation/networking/net-modules.txt>. The module
813 will be called smc-ultra.
816 tristate "SMC Ultra32 EISA support"
817 depends on NET_VENDOR_SMC && EISA
820 If you have a network (Ethernet) card of this type, say Y and read
821 the Ethernet-HOWTO, available from
822 <http://www.tldp.org/docs.html#howto>.
824 To compile this driver as a module, choose M here and read
825 <file:Documentation/networking/net-modules.txt>. The module
826 will be called smc-ultra32.
829 tristate "Blackfin 536/537 on-chip mac support"
830 depends on NET_ETHERNET && (BF537 || BF536) && (!BF537_PORT_H)
832 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
834 This is the driver for blackfin on-chip mac device. Say Y if you want it
835 compiled into the kernel. This driver is also available as a module
836 ( = code which can be inserted in and removed from the running kernel
837 whenever you want). The module will be called bfin_mac.
839 config BFIN_MAC_USE_L1
840 bool "Use L1 memory for rx/tx packets"
841 depends on BFIN_MAC && BF537
844 To get maximum network performace, you should use L1 memory as rx/tx buffers.
845 Say N here if you want to reserve L1 memory for other uses.
847 config BFIN_TX_DESC_NUM
848 int "Number of transmit buffer packets"
850 range 6 10 if BFIN_MAC_USE_L1
854 Set the number of buffer packets used in driver.
856 config BFIN_RX_DESC_NUM
857 int "Number of receive buffer packets"
859 range 20 100 if BFIN_MAC_USE_L1
863 Set the number of buffer packets used in driver.
866 bool "RMII PHY Interface (EXPERIMENTAL)"
867 depends on BFIN_MAC && EXPERIMENTAL
870 Use Reduced PHY MII Interface
873 tristate "SMC 9194 support"
874 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
877 This is support for the SMC9xxx based Ethernet cards. Choose this
878 option if you have a DELL laptop with the docking station, or
879 another SMC9192/9194 based chipset. Say Y if you want it compiled
880 into the kernel, and read the file
881 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
882 available from <http://www.tldp.org/docs.html#howto>.
884 To compile this driver as a module, choose M here and read
885 <file:Documentation/networking/net-modules.txt>. The module
886 will be called smc9194.
889 tristate "SMC 91C9x/91C1xxx support"
892 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BFIN
894 This is a driver for SMC's 91x series of Ethernet chipsets,
895 including the SMC91C94 and the SMC91C111. Say Y if you want it
896 compiled into the kernel, and read the file
897 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
898 available from <http://www.linuxdoc.org/docs.html#howto>.
900 This driver is also available as a module ( = code which can be
901 inserted in and removed from the running kernel whenever you want).
902 The module will be called smc91x. If you want to compile it as a
903 module, say M here and read <file:Documentation/kbuild/modules.txt>
904 as well as <file:Documentation/networking/net-modules.txt>.
907 tristate "NetX Ethernet support"
911 This is support for the Hilscher netX builtin Ethernet ports
913 To compile this driver as a module, choose M here and read
914 <file:Documentation/networking/net-modules.txt>. The module
915 will be called netx-eth.
918 tristate "DM9000 support"
919 depends on ARM || BLACKFIN || MIPS
923 Support for DM9000 chipset.
925 To compile this driver as a module, choose M here and read
926 <file:Documentation/networking/net-modules.txt>. The module will be
930 tristate "SMSC LAN911[5678] support"
935 This is a driver for SMSC's LAN911x series of Ethernet chipsets
936 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
937 Say Y if you want it compiled into the kernel,
938 and read the Ethernet-HOWTO, available from
939 <http://www.linuxdoc.org/docs.html#howto>.
941 This driver is also available as a module. The module will be
942 called smc911x. If you want to compile it as a module, say M
943 here and read <file:Documentation/kbuild/modules.txt>
945 config NET_VENDOR_RACAL
946 bool "Racal-Interlan (Micom) NI cards"
949 If you have a network (Ethernet) card belonging to this class, such
950 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
951 available from <http://www.tldp.org/docs.html#howto>.
953 Note that the answer to this question doesn't directly affect the
954 kernel: saying N will just cause the configurator to skip all
955 the questions about NI cards. If you say Y, you will be asked for
956 your specific card in the following questions.
959 tristate "NI5010 support (EXPERIMENTAL)"
960 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
962 If you have a network (Ethernet) card of this type, say Y and read
963 the Ethernet-HOWTO, available from
964 <http://www.tldp.org/docs.html#howto>. Note that this is still
967 To compile this driver as a module, choose M here and read
968 <file:Documentation/networking/net-modules.txt>. The module
969 will be called ni5010.
972 tristate "NI5210 support"
973 depends on NET_VENDOR_RACAL && ISA
975 If you have a network (Ethernet) card of this type, say Y and read
976 the Ethernet-HOWTO, available from
977 <http://www.tldp.org/docs.html#howto>.
979 To compile this driver as a module, choose M here and read
980 <file:Documentation/networking/net-modules.txt>. The module
984 tristate "NI6510 support"
985 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
987 If you have a network (Ethernet) card of this type, say Y and read
988 the Ethernet-HOWTO, available from
989 <http://www.tldp.org/docs.html#howto>.
991 To compile this driver as a module, choose M here and read
992 <file:Documentation/networking/net-modules.txt>. The module
995 source "drivers/net/tulip/Kconfig"
998 tristate "AT1700/1720 support (EXPERIMENTAL)"
999 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1002 If you have a network (Ethernet) card of this type, say Y and read
1003 the Ethernet-HOWTO, available from
1004 <http://www.tldp.org/docs.html#howto>.
1006 To compile this driver as a module, choose M here and read
1007 <file:Documentation/networking/net-modules.txt>. The module
1008 will be called at1700.
1011 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1012 depends on ISA || EISA || MCA
1015 If you have a network (Ethernet) card of this type, say Y and read
1016 the Ethernet-HOWTO, available from
1017 <http://www.tldp.org/docs.html#howto> as well as
1018 <file:drivers/net/depca.c>.
1020 To compile this driver as a module, choose M here and read
1021 <file:Documentation/networking/net-modules.txt>. The module
1022 will be called depca.
1025 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1026 depends on ISA || EISA || PCI
1028 If you have a network (Ethernet) card of this type, say Y and read
1029 the Ethernet-HOWTO, available from
1030 <http://www.tldp.org/docs.html#howto>.
1032 To compile this driver as a module, choose M here and read
1033 <file:Documentation/networking/net-modules.txt>. The module
1034 will be called hp100.
1037 bool "Other ISA cards"
1040 If your network (Ethernet) card hasn't been mentioned yet and its
1041 bus system (that's the way the cards talks to the other components
1042 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1043 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1044 available from <http://www.tldp.org/docs.html#howto>.
1048 Note that the answer to this question doesn't directly affect the
1049 kernel: saying N will just cause the configurator to skip all
1050 the remaining ISA network card questions. If you say Y, you will be
1051 asked for your specific card in the following questions.
1054 tristate "Cabletron E21xx support"
1058 If you have a network (Ethernet) card of this type, say Y and read
1059 the Ethernet-HOWTO, available from
1060 <http://www.tldp.org/docs.html#howto>.
1062 To compile this driver as a module, choose M here and read
1063 <file:Documentation/networking/net-modules.txt>. The module
1064 will be called e2100.
1067 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1071 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1072 cards. If this is for you, say Y and read
1073 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1074 well as the Ethernet-HOWTO, available from
1075 <http://www.tldp.org/docs.html#howto>.
1077 To compile this driver as a module, choose M here and read
1078 <file:Documentation/networking/net-modules.txt>. The module
1079 will be called ewrk3.
1082 tristate "EtherExpress 16 support"
1085 If you have an EtherExpress16 network (Ethernet) card, say Y and
1086 read the Ethernet-HOWTO, available from
1087 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1088 EtherExpress16 card used to be regarded as a very poor choice
1089 because the driver was very unreliable. We now have a new driver
1090 that should do better.
1092 To compile this driver as a module, choose M here and read
1093 <file:Documentation/networking/net-modules.txt>. The module
1094 will be called eexpress.
1097 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1100 If you have a network (Ethernet) card of this type, say Y. This
1101 driver supports Intel i82595{FX,TX} based boards. Note however
1102 that the EtherExpress PRO/100 Ethernet card has its own separate
1103 driver. Please read the Ethernet-HOWTO, available from
1104 <http://www.tldp.org/docs.html#howto>.
1106 To compile this driver as a module, choose M here and read
1107 <file:Documentation/networking/net-modules.txt>. The module
1108 will be called eepro.
1111 tristate "HP PCLAN+ (27247B and 27252A) support"
1115 If you have a network (Ethernet) card of this type, say Y and read
1116 the Ethernet-HOWTO, available from
1117 <http://www.tldp.org/docs.html#howto>.
1119 To compile this driver as a module, choose M here and read
1120 <file:Documentation/networking/net-modules.txt>. The module
1121 will be called hp-plus.
1124 tristate "HP PCLAN (27245 and other 27xxx series) support"
1128 If you have a network (Ethernet) card of this type, say Y and read
1129 the Ethernet-HOWTO, available from
1130 <http://www.tldp.org/docs.html#howto>.
1132 To compile this driver as a module, choose M here and read
1133 <file:Documentation/networking/net-modules.txt>. The module
1137 tristate "LP486E on board Ethernet"
1140 Say Y here to support the 82596-based on-board Ethernet controller
1141 for the Panther motherboard, which is one of the two shipped in the
1142 Intel Professional Workstation.
1145 tristate "ICL EtherTeam 16i/32 support"
1148 If you have a network (Ethernet) card of this type, say Y and read
1149 the Ethernet-HOWTO, available from
1150 <http://www.tldp.org/docs.html#howto>.
1152 To compile this driver as a module, choose M here and read
1153 <file:Documentation/networking/net-modules.txt>. The module
1154 will be called eth16i.
1157 tristate "NE2000/NE1000 support"
1158 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
1161 If you have a network (Ethernet) card of this type, say Y and read
1162 the Ethernet-HOWTO, available from
1163 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1164 without a specific driver are compatible with NE2000.
1166 If you have a PCI NE2000 card however, say N here and Y to "PCI
1167 NE2000 and clone support" under "EISA, VLB, PCI and on board
1168 controllers" below. If you have a NE2000 card and are running on
1169 an MCA system (a bus system used on some IBM PS/2 computers and
1170 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1173 To compile this driver as a module, choose M here and read
1174 <file:Documentation/networking/net-modules.txt>. The module
1178 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1179 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1181 The Zenith Z-Note notebook computer has a built-in network
1182 (Ethernet) card, and this is the Linux driver for it. Note that the
1183 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1184 by this driver. Read the Ethernet-HOWTO, available from
1185 <http://www.tldp.org/docs.html#howto>.
1188 tristate "SEEQ8005 support (EXPERIMENTAL)"
1189 depends on NET_ISA && EXPERIMENTAL
1191 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1192 is for you, read the Ethernet-HOWTO, available from
1193 <http://www.tldp.org/docs.html#howto>.
1195 To compile this driver as a module, choose M here and read
1196 <file:Documentation/networking/net-modules.txt>. The module
1197 will be called seeq8005.
1200 tristate "NE/2 (ne2000 MCA version) support"
1201 depends on MCA_LEGACY
1204 If you have a network (Ethernet) card of this type, say Y and read
1205 the Ethernet-HOWTO, available from
1206 <http://www.tldp.org/docs.html#howto>.
1208 To compile this driver as a module, choose M here and read
1209 <file:Documentation/networking/net-modules.txt>. The module
1213 tristate "IBM LAN Adapter/A support"
1214 depends on MCA && MCA_LEGACY
1216 This is a Micro Channel Ethernet adapter. You need to set
1217 CONFIG_MCA to use this driver. It is both available as an in-kernel
1218 driver and as a module.
1220 To compile this driver as a module, choose M here and read
1221 <file:Documentation/networking/net-modules.txt>. The only
1222 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1223 will both support 16K and 32K memory windows, however a 32K window
1224 gives a better security against packet losses. Usage of multiple
1225 boards with this driver should be possible, but has not been tested
1226 up to now due to lack of hardware.
1229 tristate "IBM LAN Virtual Ethernet support"
1230 depends on PPC_PSERIES
1232 This driver supports virtual ethernet adapters on newer IBM iSeries
1233 and pSeries systems.
1235 To compile this driver as a module, choose M here and read
1236 <file:Documentation/networking/net-modules.txt>. The module will
1240 tristate "PowerPC 4xx on-chip Ethernet support"
1241 depends on 4xx && !PPC_MERGE
1243 This driver supports the PowerPC 4xx EMAC family of on-chip
1244 Ethernet controllers.
1247 int "Number of receive buffers"
1252 int "Number of transmit buffers"
1256 config IBM_EMAC_POLL_WEIGHT
1257 int "MAL NAPI polling weight"
1261 config IBM_EMAC_RX_COPY_THRESHOLD
1262 int "RX skb copy threshold (bytes)"
1266 config IBM_EMAC_RX_SKB_HEADROOM
1267 int "Additional RX skb headroom (bytes)"
1271 Additional receive skb headroom. Note, that driver
1272 will always reserve at least 2 bytes to make IP header
1273 aligned, so usually there is no need to add any additional
1276 If unsure, set to 0.
1278 config IBM_EMAC_PHY_RX_CLK_FIX
1279 bool "PHY Rx clock workaround"
1280 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
1282 Enable this if EMAC attached to a PHY which doesn't generate
1283 RX clock if there is no link, if this is the case, you will
1284 see "TX disable timeout" or "RX disable timeout" in the system
1289 config IBM_EMAC_DEBUG
1294 config IBM_EMAC_ZMII
1296 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1299 config IBM_EMAC_RGMII
1301 depends on IBM_EMAC && 440GX
1306 depends on IBM_EMAC && 440GX
1310 bool "EISA, VLB, PCI and on board controllers"
1311 depends on ISA || EISA || PCI
1313 This is another class of network cards which attach directly to the
1314 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1315 available from <http://www.tldp.org/docs.html#howto>.
1317 Note that the answer to this question doesn't directly affect the
1318 kernel: saying N will just cause the configurator to skip all
1319 the questions about this class of network cards. If you say Y, you
1320 will be asked for your specific card in the following questions. If
1321 you are unsure, say Y.
1324 tristate "AMD PCnet32 PCI support"
1325 depends on NET_PCI && PCI
1329 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1330 answer Y here and read the Ethernet-HOWTO, available from
1331 <http://www.tldp.org/docs.html#howto>.
1333 To compile this driver as a module, choose M here and read
1334 <file:Documentation/networking/net-modules.txt>. The module
1335 will be called pcnet32.
1338 bool "Use RX polling (NAPI)"
1341 NAPI is a new driver API designed to reduce CPU and interrupt load
1342 when the driver is receiving lots of packets from the card. It is
1343 still somewhat experimental and thus not yet enabled by default.
1345 If your estimated Rx load is 10kpps or more, or if the card will be
1346 deployed on potentially unfriendly networks (e.g. in a firewall),
1349 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1355 tristate "AMD 8111 (new PCI lance) support"
1356 depends on NET_PCI && PCI
1360 If you have an AMD 8111-based PCI lance ethernet card,
1361 answer Y here and read the Ethernet-HOWTO, available from
1362 <http://www.tldp.org/docs.html#howto>.
1364 To compile this driver as a module, choose M here and read
1365 <file:Documentation/networking/net-modules.txt>. The module
1366 will be called amd8111e.
1368 config AMD8111E_NAPI
1369 bool "Enable NAPI support"
1370 depends on AMD8111_ETH
1372 NAPI is a new driver API designed to reduce CPU and interrupt load
1373 when the driver is receiving lots of packets from the card. It is
1374 still somewhat experimental and thus not yet enabled by default.
1376 If your estimated Rx load is 10kpps or more, or if the card will be
1377 deployed on potentially unfriendly networks (e.g. in a firewall),
1380 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1385 config ADAPTEC_STARFIRE
1386 tristate "Adaptec Starfire/DuraLAN support"
1387 depends on NET_PCI && PCI
1391 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1392 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1393 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1396 To compile this driver as a module, choose M here: the module
1397 will be called starfire. This is recommended.
1399 config ADAPTEC_STARFIRE_NAPI
1400 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1401 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1403 NAPI is a new driver API designed to reduce CPU and interrupt load
1404 when the driver is receiving lots of packets from the card. It is
1405 still somewhat experimental and thus not yet enabled by default.
1407 If your estimated Rx load is 10kpps or more, or if the card will be
1408 deployed on potentially unfriendly networks (e.g. in a firewall),
1411 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1417 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1418 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1421 If you have a network (Ethernet) card of this type, say Y and read
1422 the Ethernet-HOWTO, available from
1423 <http://www.tldp.org/docs.html#howto>.
1425 To compile this driver as a module, choose M here and read
1426 <file:Documentation/networking/net-modules.txt>. The module
1427 will be called ac3200.
1430 tristate "Apricot Xen-II on board Ethernet"
1431 depends on NET_PCI && ISA
1433 If you have a network (Ethernet) controller of this type, say Y and
1434 read the Ethernet-HOWTO, available from
1435 <http://www.tldp.org/docs.html#howto>.
1437 To compile this driver as a module, choose M here and read
1438 <file:Documentation/networking/net-modules.txt>. The module will be
1442 tristate "Broadcom 4400 ethernet support"
1443 depends on NET_PCI && PCI
1446 If you have a network (Ethernet) controller of this type, say Y and
1447 read the Ethernet-HOWTO, available from
1448 <http://www.tldp.org/docs.html#howto>.
1450 To compile this driver as a module, choose M here and read
1451 <file:Documentation/networking/net-modules.txt>. The module will be
1455 tristate "nForce Ethernet support"
1456 depends on NET_PCI && PCI
1458 If you have a network (Ethernet) controller of this type, say Y and
1459 read the Ethernet-HOWTO, available from
1460 <http://www.tldp.org/docs.html#howto>.
1462 To compile this driver as a module, choose M here and read
1463 <file:Documentation/networking/net-modules.txt>. The module will be
1466 config FORCEDETH_NAPI
1467 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1468 depends on FORCEDETH && EXPERIMENTAL
1470 NAPI is a new driver API designed to reduce CPU and interrupt load
1471 when the driver is receiving lots of packets from the card. It is
1472 still somewhat experimental and thus not yet enabled by default.
1474 If your estimated Rx load is 10kpps or more, or if the card will be
1475 deployed on potentially unfriendly networks (e.g. in a firewall),
1478 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1484 tristate "CS89x0 support"
1485 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
1487 Support for CS89x0 chipset based Ethernet cards. If you have a
1488 network (Ethernet) card of this type, say Y and read the
1489 Ethernet-HOWTO, available from
1490 <http://www.tldp.org/docs.html#howto> as well as
1491 <file:Documentation/networking/cs89x0.txt>.
1493 To compile this driver as a module, choose M here and read
1494 <file:Documentation/networking/net-modules.txt>. The module will be
1498 tristate "TOSHIBA TC35815 Ethernet support"
1499 depends on NET_PCI && PCI && MIPS
1503 tristate "Digi Intl. RightSwitch SE-X support"
1504 depends on NET_PCI && (PCI || EISA)
1506 This is support for the Digi International RightSwitch series of
1507 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1508 models. If you have a network card of this type, say Y and read the
1509 Ethernet-HOWTO, available from
1510 <http://www.tldp.org/docs.html#howto>. More specific
1511 information is contained in <file:Documentation/networking/dgrs.txt>.
1513 To compile this driver as a module, choose M here and read
1514 <file:Documentation/networking/net-modules.txt>. The module
1515 will be called dgrs.
1518 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1519 depends on NET_PCI && PCI
1522 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1523 card, say Y and read the Ethernet-HOWTO, available from
1524 <http://www.tldp.org/docs.html#howto>.
1526 To compile this driver as a module, choose M here and read
1527 <file:Documentation/networking/net-modules.txt>. The module
1528 will be called eepro100.
1532 tristate "Intel(R) PRO/100+ support"
1533 depends on NET_PCI && PCI
1536 This driver supports Intel(R) PRO/100 family of adapters.
1537 To verify that your adapter is supported, find the board ID number
1538 on the adapter. Look for a label that has a barcode and a number
1539 in the format 123456-001 (six digits hyphen three digits).
1541 Use the above information and the Adapter & Driver ID Guide at:
1543 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1545 to identify the adapter.
1547 For the latest Intel PRO/100 network driver for Linux, see:
1549 <http://appsr.intel.com/scripts-df/support_intel.asp>
1551 More specific information on configuring the driver is in
1552 <file:Documentation/networking/e100.txt>.
1554 To compile this driver as a module, choose M here and read
1555 <file:Documentation/networking/net-modules.txt>. The module
1556 will be called e100.
1559 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1560 depends on NET_PCI && EISA && EXPERIMENTAL
1563 If you have a network (Ethernet) card of this type, say Y and read
1564 the Ethernet-HOWTO, available from
1565 <http://www.tldp.org/docs.html#howto>.
1567 To compile this driver as a module, choose M here and read
1568 <file:Documentation/networking/net-modules.txt>. The module
1569 will be called lne390.
1572 tristate "Myson MTD-8xx PCI Ethernet support"
1573 depends on NET_PCI && PCI
1577 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1578 cards. Specifications and data at
1579 <http://www.myson.com.hk/mtd/datasheet/>.
1582 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1583 depends on NET_PCI && PCI
1586 This driver is for the National Semiconductor DP83810 series,
1587 which is used in cards from PureData, NetGear, Linksys
1588 and others, including the 83815 chip.
1589 More specific information and updates are available from
1590 <http://www.scyld.com/network/natsemi.html>.
1593 tristate "PCI NE2000 and clones support (see help)"
1594 depends on NET_PCI && PCI
1597 This driver is for NE2000 compatible PCI cards. It will not work
1598 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1599 support" below). If you have a PCI NE2000 network (Ethernet) card,
1600 say Y and read the Ethernet-HOWTO, available from
1601 <http://www.tldp.org/docs.html#howto>.
1603 This driver also works for the following NE2000 clone cards:
1604 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1605 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1606 Holtek HT80232 Holtek HT80229
1608 To compile this driver as a module, choose M here and read
1609 <file:Documentation/networking/net-modules.txt>. The module
1610 will be called ne2k-pci.
1613 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1614 depends on NET_PCI && EISA && EXPERIMENTAL
1617 If you have a network (Ethernet) card of this type, say Y and read
1618 the Ethernet-HOWTO, available from
1619 <http://www.tldp.org/docs.html#howto>. Note that this driver
1620 will NOT WORK for NE3200 cards as they are completely different.
1622 To compile this driver as a module, choose M here and read
1623 <file:Documentation/networking/net-modules.txt>. The module
1624 will be called ne3210.
1627 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1628 depends on NET_PCI && EISA && EXPERIMENTAL
1631 If you have a network (Ethernet) card of this type, say Y and read
1632 the Ethernet-HOWTO, available from
1633 <http://www.tldp.org/docs.html#howto>.
1635 To compile this driver as a module, choose M here and read
1636 <file:Documentation/networking/net-modules.txt>. The module
1637 will be called es3210.
1640 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1641 depends on NET_PCI && PCI && EXPERIMENTAL
1645 This is a driver for the Fast Ethernet PCI network cards based on
1646 the RTL8139C+ chips. If you have one of those, say Y and read
1647 the Ethernet-HOWTO, available from
1648 <http://www.tldp.org/docs.html#howto>.
1650 To compile this driver as a module, choose M here: the module
1651 will be called 8139cp. This is recommended.
1654 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1655 depends on NET_PCI && PCI
1659 This is a driver for the Fast Ethernet PCI network cards based on
1660 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1661 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1663 To compile this driver as a module, choose M here: the module
1664 will be called 8139too. This is recommended.
1667 bool "Use PIO instead of MMIO"
1671 This instructs the driver to use programmed I/O ports (PIO) instead
1672 of PCI shared memory (MMIO). This can possibly solve some problems
1673 in case your mainboard has memory consistency issues. If unsure,
1676 config 8139TOO_TUNE_TWISTER
1677 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1680 This implements a function which might come in handy in case you
1681 are using low quality on long cabling. It is required for RealTek
1682 RTL-8139 revision K boards, and totally unused otherwise. It tries
1683 to match the transceiver to the cable characteristics. This is
1684 experimental since hardly documented by the manufacturer.
1688 bool "Support for older RTL-8129/8130 boards"
1691 This enables support for the older and uncommon RTL-8129 and
1692 RTL-8130 chips, which support MII via an external transceiver,
1693 instead of an internal one. Disabling this option will save some
1694 memory by making the code size smaller. If unsure, say Y.
1696 config 8139_OLD_RX_RESET
1697 bool "Use older RX-reset method"
1700 The 8139too driver was recently updated to contain a more rapid
1701 reset sequence, in the face of severe receive errors. This "new"
1702 RX-reset method should be adequate for all boards. But if you
1703 experience problems, you can enable this option to restore the
1704 old RX-reset behavior. If unsure, say N.
1707 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1708 depends on NET_PCI && PCI
1712 This is a driver for the Fast Ethernet PCI network cards based on
1713 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1714 SiS 630 and SiS 540 chipsets.
1716 This driver also supports AMD 79C901 HomePNA so that you can use
1717 your phone line as a network cable.
1719 To compile this driver as a module, choose M here: the module
1720 will be called sis900. This is recommended.
1723 tristate "SMC EtherPower II"
1724 depends on NET_PCI && PCI
1728 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1729 which is based on the SMC83c17x (EPIC/100).
1730 More specific information and updates are available from
1731 <http://www.scyld.com/network/epic100.html>.
1734 tristate "Sundance Alta support"
1735 depends on NET_PCI && PCI
1739 This driver is for the Sundance "Alta" chip.
1740 More specific information and updates are available from
1741 <http://www.scyld.com/network/sundance.html>.
1743 config SUNDANCE_MMIO
1744 bool "Use MMIO instead of PIO"
1747 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1748 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1749 is known to solve bugs on certain chips.
1754 tristate "TI ThunderLAN support"
1755 depends on NET_PCI && (PCI || EISA) && !64BIT
1757 If you have a PCI Ethernet network card based on the ThunderLAN chip
1758 which is supported by this driver, say Y and read the
1759 Ethernet-HOWTO, available from
1760 <http://www.tldp.org/docs.html#howto>.
1762 Devices currently supported by this driver are Compaq Netelligent,
1763 Compaq NetFlex and Olicom cards. Please read the file
1764 <file:Documentation/networking/tlan.txt> for more details.
1766 To compile this driver as a module, choose M here and read
1767 <file:Documentation/networking/net-modules.txt>. The module
1768 will be called tlan.
1770 Please email feedback to <torben.mathiasen@compaq.com>.
1773 tristate "VIA Rhine support"
1774 depends on NET_PCI && PCI
1778 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1779 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1780 Ethernet functions can also be found integrated on South Bridges
1783 To compile this driver as a module, choose M here. The module
1784 will be called via-rhine.
1786 config VIA_RHINE_MMIO
1787 bool "Use MMIO instead of PIO"
1788 depends on VIA_RHINE
1790 This instructs the driver to use PCI shared memory (MMIO) instead of
1791 programmed I/O ports (PIO). Enabling this gives an improvement in
1792 processing time in parts of the driver.
1796 config VIA_RHINE_NAPI
1797 bool "Use Rx Polling (NAPI)"
1798 depends on VIA_RHINE
1800 NAPI is a new driver API designed to reduce CPU and interrupt load
1801 when the driver is receiving lots of packets from the card.
1803 If your estimated Rx load is 10kpps or more, or if the card will be
1804 deployed on potentially unfriendly networks (e.g. in a firewall),
1807 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1811 bool "Philips SAA9730 Ethernet support"
1812 depends on NET_PCI && PCI && MIPS_ATLAS
1814 The SAA9730 is a combined multimedia and peripheral controller used
1815 in thin clients, Internet access terminals, and diskless
1817 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1820 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1821 depends on NET_PCI && PCI && EXPERIMENTAL
1824 This is a driver for the Fast Ethernet PCI network cards based on
1825 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1826 have one of these, say Y here.
1828 To compile this driver as a module, choose M here: the module
1829 will be called sc92031. This is recommended.
1832 bool "Pocket and portable adapters"
1835 Cute little network (Ethernet) devices which attach to the parallel
1836 port ("pocket adapters"), commonly used with laptops. If you have
1837 one of those, say Y and read the Ethernet-HOWTO, available from
1838 <http://www.tldp.org/docs.html#howto>.
1840 If you want to plug a network (or some other) card into the PCMCIA
1841 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1842 credit card size extension cards used by all modern laptops), you
1843 need the pcmcia-cs package (location contained in the file
1844 <file:Documentation/Changes>) and you can say N here.
1846 Laptop users should read the Linux Laptop home page at
1847 <http://www.linux-on-laptops.com/> or
1848 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1850 Note that the answer to this question doesn't directly affect the
1851 kernel: saying N will just cause the configurator to skip all
1852 the questions about this class of network devices. If you say Y, you
1853 will be asked for your specific device in the following questions.
1856 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1857 depends on NET_POCKET && PARPORT && X86
1860 This is a network (Ethernet) device which attaches to your parallel
1861 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1862 available from <http://www.tldp.org/docs.html#howto>, if you
1863 want to use this. If you intend to use this driver, you should have
1864 said N to the "Parallel printer support", because the two drivers
1865 don't like each other.
1867 To compile this driver as a module, choose M here: the module
1871 tristate "D-Link DE600 pocket adapter support"
1872 depends on NET_POCKET && PARPORT
1874 This is a network (Ethernet) device which attaches to your parallel
1875 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1876 Ethernet-HOWTO, available from
1877 <http://www.tldp.org/docs.html#howto>, if you want to use
1878 this. It is possible to have several devices share a single parallel
1879 port and it is safe to compile the corresponding drivers into the
1882 To compile this driver as a module, choose M here: the module
1883 will be called de600.
1886 tristate "D-Link DE620 pocket adapter support"
1887 depends on NET_POCKET && PARPORT
1889 This is a network (Ethernet) device which attaches to your parallel
1890 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1891 Ethernet-HOWTO, available from
1892 <http://www.tldp.org/docs.html#howto>, if you want to use
1893 this. It is possible to have several devices share a single parallel
1894 port and it is safe to compile the corresponding drivers into the
1897 To compile this driver as a module, choose M here: the module
1898 will be called de620.
1901 tristate "SGI Seeq ethernet controller support"
1904 Say Y here if you have an Seeq based Ethernet network card. This is
1905 used in many Silicon Graphics machines.
1908 tristate "DEC LANCE ethernet controller support"
1909 depends on MACH_DECSTATION
1912 This driver is for the series of Ethernet controllers produced by
1913 DEC (now Compaq) based on the AMD Lance chipset, including the
1914 DEPCA series. (This chipset is better known via the NE2100 cards.)
1917 bool "Motorola 68360 ethernet controller"
1920 Say Y here if you want to use the built-in ethernet controller of
1921 the Motorola 68360 processor.
1924 bool "FEC ethernet controller (of ColdFire CPUs)"
1925 depends on M523x || M527x || M5272 || M528x || M520x
1927 Say Y here if you want to use the built-in 10/100 Fast ethernet
1928 controller on some Motorola ColdFire processors.
1931 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1934 Say Y here if you want to use the second built-in 10/100 Fast
1935 ethernet controller on some Motorola ColdFire processors.
1938 tristate "NE2000 compatible support for H8/300"
1941 Say Y here if you want to use the NE2000 compatible
1942 controller on the Renesas H8/300 processor.
1944 source "drivers/net/fec_8xx/Kconfig"
1945 source "drivers/net/fs_enet/Kconfig"
1947 endif # NET_ETHERNET
1953 menuconfig NETDEV_1000
1954 bool "Ethernet (1000 Mbit)"
1958 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1959 type of Local Area Network (LAN) in universities and companies.
1961 Say Y here to get to see options for Gigabit Ethernet drivers.
1962 This option alone does not add any kernel code.
1963 Note that drivers supporting both 100 and 1000 MBit may be listed
1964 under "Ethernet (10 or 100MBit)" instead.
1966 If you say N, all options in this submenu will be skipped and disabled.
1971 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1974 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1975 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1976 adapter. The driver allows for using the Jumbo Frame option (9000
1977 bytes/frame) however it requires that your switches can handle this
1978 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1981 To compile this driver as a module, choose M here: the
1982 module will be called acenic.
1984 config ACENIC_OMIT_TIGON_I
1985 bool "Omit support for old Tigon I based AceNICs"
1988 Say Y here if you only have Tigon II based AceNICs and want to leave
1989 out support for the older Tigon I based cards which are no longer
1990 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1991 version)). This will reduce the size of the driver object by
1992 app. 100KB. If you are not sure whether your card is a Tigon I or a
1993 Tigon II, say N here.
1995 The safe and default value for this is N.
1998 tristate "D-Link DL2000-based Gigabit Ethernet support"
2002 This driver supports D-Link 2000-based gigabit ethernet cards, which
2004 D-Link DGE-550T Gigabit Ethernet Adapter.
2005 D-Link DL2000-based Gigabit Ethernet Adapter.
2007 To compile this driver as a module, choose M here: the
2008 module will be called dl2k.
2011 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2014 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2015 adapters. For more information on how to identify your adapter, go
2016 to the Adapter & Driver ID Guide at:
2018 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2020 For general information and support, go to the Intel support
2023 <http://support.intel.com>
2025 More specific information on configuring the driver is in
2026 <file:Documentation/networking/e1000.txt>.
2028 To compile this driver as a module, choose M here and read
2029 <file:Documentation/networking/net-modules.txt>. The module
2030 will be called e1000.
2033 bool "Use Rx Polling (NAPI)"
2036 NAPI is a new driver API designed to reduce CPU and interrupt load
2037 when the driver is receiving lots of packets from the card. It is
2038 still somewhat experimental and thus not yet enabled by default.
2040 If your estimated Rx load is 10kpps or more, or if the card will be
2041 deployed on potentially unfriendly networks (e.g. in a firewall),
2044 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2049 config E1000_DISABLE_PACKET_SPLIT
2050 bool "Disable Packet Split for PCI express adapters"
2053 Say Y here if you want to use the legacy receive path for PCI express
2058 source "drivers/net/ixp2000/Kconfig"
2061 tristate "MyriCOM Gigabit Ethernet support"
2064 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2066 To compile this driver as a module, choose M here: the module
2067 will be called myri_sbus. This is recommended.
2070 tristate "National Semiconductor DP83820 support"
2073 This is a driver for the National Semiconductor DP83820 series
2074 of gigabit ethernet MACs. Cards using this chipset include
2075 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2076 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2080 tristate "Packet Engines Hamachi GNIC-II support"
2084 If you have a Gigabit Ethernet card of this type, say Y and read
2085 the Ethernet-HOWTO, available from
2086 <http://www.tldp.org/docs.html#howto>.
2088 To compile this driver as a module, choose M here and read
2089 <file:Documentation/networking/net-modules.txt>. The module will be
2093 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2094 depends on PCI && EXPERIMENTAL
2097 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2098 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2099 used by the Beowulf Linux cluster project. See
2100 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2101 information about this driver in particular and Beowulf in general.
2103 To compile this driver as a module, choose M here: the module
2104 will be called yellowfin. This is recommended.
2107 tristate "Realtek 8169 gigabit ethernet support"
2111 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2113 To compile this driver as a module, choose M here: the module
2114 will be called r8169. This is recommended.
2117 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2118 depends on R8169 && EXPERIMENTAL
2120 NAPI is a new driver API designed to reduce CPU and interrupt load
2121 when the driver is receiving lots of packets from the card. It is
2122 still somewhat experimental and thus not yet enabled by default.
2124 If your estimated Rx load is 10kpps or more, or if the card will be
2125 deployed on potentially unfriendly networks (e.g. in a firewall),
2128 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2135 depends on R8169 && VLAN_8021Q
2137 Say Y here for the r8169 driver to support the functions required
2138 by the kernel 802.1Q code.
2143 tristate "SiS190/SiS191 gigabit ethernet support"
2148 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2149 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2150 appear in lan on motherboard designs which are based on SiS 965
2151 and SiS 966 south bridge.
2153 To compile this driver as a module, choose M here: the module
2154 will be called sis190. This is recommended.
2157 tristate "New SysKonnect GigaEthernet support"
2161 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2162 and related Gigabit Ethernet adapters. It is a new smaller driver
2163 with better performance and more complete ethtool support.
2165 It does not support the link failover and network management
2166 features that "portable" vendor supplied sk98lin driver does.
2168 This driver supports adapters based on the original Yukon chipset:
2169 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2170 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2172 It does not support the newer Yukon2 chipset: a separate driver,
2173 sky2, is provided for Yukon2-based adapters.
2175 To compile this driver as a module, choose M here: the module
2176 will be called skge. This is recommended.
2179 tristate "SysKonnect Yukon2 support"
2183 This driver supports Gigabit Ethernet adapters based on the
2184 Marvell Yukon 2 chipset:
2185 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2186 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2188 There is companion driver for the older Marvell Yukon and
2189 Genesis based adapters: skge.
2191 To compile this driver as a module, choose M here: the module
2192 will be called sky2. This is recommended.
2195 bool "Debugging interface"
2196 depends on SKY2 && DEBUG_FS
2198 This option adds the ability to dump driver state for debugging.
2199 The file debugfs/sky2/ethX displays the state of the internal
2200 transmit and receive rings.
2205 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)"
2208 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2209 compliant Gigabit Ethernet Adapter.
2211 This driver supports the original Yukon chipset. This driver is
2212 deprecated and will be removed from the kernel in the near future,
2213 it has been replaced by the skge driver. skge is cleaner and
2214 seems to work better.
2216 This driver does not support the newer Yukon2 chipset. A separate
2217 driver, sky2, is provided to support Yukon2-based adapters.
2219 The following adapters are supported by this driver:
2220 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2221 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2222 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2223 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2224 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2225 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2226 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2227 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2228 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2229 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2230 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2231 - EG1032 v2 Instant Gigabit Network Adapter
2232 - EG1064 v2 Instant Gigabit Network Adapter
2233 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2234 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2235 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2236 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2237 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2238 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2239 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2240 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2241 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2242 - Marvell RDK-8001 Adapter
2243 - Marvell RDK-8002 Adapter
2244 - Marvell RDK-8003 Adapter
2245 - Marvell RDK-8004 Adapter
2246 - Marvell RDK-8006 Adapter
2247 - Marvell RDK-8007 Adapter
2248 - Marvell RDK-8008 Adapter
2249 - Marvell RDK-8009 Adapter
2250 - Marvell RDK-8010 Adapter
2251 - Marvell RDK-8011 Adapter
2252 - Marvell RDK-8012 Adapter
2253 - Marvell RDK-8052 Adapter
2254 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2255 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2256 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2257 - SK-9521 10/100/1000Base-T Adapter
2258 - SK-9521 V2.0 10/100/1000Base-T Adapter
2259 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2260 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2261 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2262 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2263 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2264 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2265 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2266 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2267 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2268 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2269 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2270 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2271 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2272 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2273 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2274 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2275 - SMC EZ Card 1000 (SMC9452TXV.2)
2277 The adapters support Jumbo Frames.
2278 The dual link adapters support link-failover and dual port features.
2279 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2280 the scatter-gather functionality with sendfile(). Please refer to
2281 <file:Documentation/networking/sk98lin.txt> for more information about
2282 optional driver parameters.
2283 Questions concerning this driver may be addressed to:
2284 <linux@syskonnect.de>
2286 If you want to compile this driver as a module ( = code which can be
2287 inserted in and removed from the running kernel whenever you want),
2288 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2289 be called sk98lin. This is recommended.
2292 tristate "VIA Velocity support"
2298 If you have a VIA "Velocity" based network card say Y here.
2300 To compile this driver as a module, choose M here. The module
2301 will be called via-velocity.
2304 tristate "Broadcom Tigon3 support"
2307 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2309 To compile this driver as a module, choose M here: the module
2310 will be called tg3. This is recommended.
2313 tristate "Broadcom NetXtremeII support"
2318 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2320 To compile this driver as a module, choose M here: the module
2321 will be called bnx2. This is recommended.
2324 tristate "Spider Gigabit Ethernet driver"
2325 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2328 This driver supports the Gigabit Ethernet chips present on the
2329 Cell Processor-Based Blades from IBM.
2332 tristate "Tundra TSI108 gigabit Ethernet support"
2333 depends on TSI108_BRIDGE
2335 This driver supports Tundra TSI108 gigabit Ethernet ports.
2336 To compile this driver as a module, choose M here: the module
2337 will be called tsi108_eth.
2340 tristate "PS3 Gigabit Ethernet driver"
2343 This driver supports the network device on the PS3 game
2344 console. This driver has built-in support for Ethernet.
2346 To compile this driver as a module, choose M here: the
2347 module will be called ps3_gelic.
2350 tristate "Gianfar Ethernet"
2351 depends on 85xx || 83xx || PPC_86xx
2355 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2356 and MPC86xx family of chips, and the FEC on the 8540.
2363 tristate "Freescale QE Gigabit Ethernet"
2364 depends on QUICC_ENGINE
2367 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2368 which is available on some Freescale SOCs.
2374 config UGETH_MAGIC_PACKET
2375 bool "Magic Packet detection support"
2378 config UGETH_FILTERING
2379 bool "Mac address filtering support"
2382 config UGETH_TX_ON_DEMAND
2383 bool "Transmit on Demand support"
2387 tristate "MV-643XX Ethernet support"
2388 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32)
2391 This driver supports the gigabit Ethernet on the Marvell MV643XX
2392 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2393 Pegasos II, amongst other PPC and MIPS boards.
2396 tristate "QLogic QLA3XXX Network Driver Support"
2399 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2401 To compile this driver as a module, choose M here: the module
2402 will be called qla3xxx.
2405 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
2406 depends on PCI && EXPERIMENTAL
2410 This driver supports the Attansic L1 gigabit ethernet adapter.
2412 To compile this driver as a module, choose M here. The module
2413 will be called atl1.
2418 # 10 Gigabit Ethernet
2421 menuconfig NETDEV_10000
2422 bool "Ethernet (10000 Mbit)"
2426 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2427 This option alone does not add any kernel code.
2429 If you say N, all options in this submenu will be skipped and disabled.
2434 tristate "Chelsio 10Gb Ethernet support"
2438 This driver supports Chelsio gigabit and 10-gigabit
2439 Ethernet cards. More information about adapter features and
2440 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2442 For general information about Chelsio and our products, visit
2443 our website at <http://www.chelsio.com>.
2445 For customer support, please visit our customer support page at
2446 <http://www.chelsio.com/support.htm>.
2448 Please send feedback to <linux-bugs@chelsio.com>.
2450 To compile this driver as a module, choose M here: the module
2451 will be called cxgb.
2453 config CHELSIO_T1_1G
2454 bool "Chelsio gigabit Ethernet support"
2455 depends on CHELSIO_T1
2457 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2458 are using only 10G cards say 'N' here.
2460 config CHELSIO_T1_NAPI
2461 bool "Use Rx Polling (NAPI)"
2462 depends on CHELSIO_T1
2465 NAPI is a driver API designed to reduce CPU and interrupt load
2466 when the driver is receiving lots of packets from the card.
2469 tristate "Chelsio Communications T3 10Gb Ethernet support"
2473 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2476 For general information about Chelsio and our products, visit
2477 our website at <http://www.chelsio.com>.
2479 For customer support, please visit our customer support page at
2480 <http://www.chelsio.com/support.htm>.
2482 Please send feedback to <linux-bugs@chelsio.com>.
2484 To compile this driver as a module, choose M here: the module
2485 will be called cxgb3.
2488 tristate "eHEA Ethernet support"
2492 This driver supports the IBM pSeries eHEA ethernet adapter.
2494 To compile the driver as a module, choose M here. The module
2495 will be called ehea.
2498 tristate "Intel(R) PRO/10GbE support"
2501 This driver supports Intel(R) PRO/10GbE family of
2502 adapters. For more information on how to identify your adapter, go
2503 to the Adapter & Driver ID Guide at:
2505 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2507 For general information and support, go to the Intel support
2510 <http://support.intel.com>
2512 More specific information on configuring the driver is in
2513 <file:Documentation/networking/ixgb.txt>.
2515 To compile this driver as a module, choose M here and read
2516 <file:Documentation/networking/net-modules.txt>. The module
2517 will be called ixgb.
2520 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2521 depends on IXGB && EXPERIMENTAL
2523 NAPI is a new driver API designed to reduce CPU and interrupt load
2524 when the driver is receiving lots of packets from the card. It is
2525 still somewhat experimental and thus not yet enabled by default.
2527 If your estimated Rx load is 10kpps or more, or if the card will be
2528 deployed on potentially unfriendly networks (e.g. in a firewall),
2531 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2537 tristate "S2IO 10Gbe XFrame NIC"
2540 This driver supports the 10Gbe XFrame NIC of S2IO.
2541 More specific information on configuring the driver is in
2542 <file:Documentation/networking/s2io.txt>.
2545 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2546 depends on S2IO && EXPERIMENTAL
2548 NAPI is a new driver API designed to reduce CPU and interrupt load
2549 when the driver is receiving lots of packets from the card. It is
2550 still somewhat experimental and thus not yet enabled by default.
2552 If your estimated Rx load is 10kpps or more, or if the card will be
2553 deployed on potentially unfriendly networks (e.g. in a firewall),
2556 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2562 tristate "Myricom Myri-10G Ethernet support"
2568 This driver supports Myricom Myri-10G Dual Protocol interface in
2569 Ethernet mode. If the eeprom on your board is not recent enough,
2570 you will need a newer firmware image.
2571 You may get this image or more information, at:
2573 <http://www.myri.com/scs/download-Myri10GE.html>
2575 To compile this driver as a module, choose M here and read
2576 <file:Documentation/networking/net-modules.txt>. The module
2577 will be called myri10ge.
2580 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2583 This enables the support for NetXen's Gigabit Ethernet card.
2586 tristate "PA Semi 1/10Gbit MAC"
2587 depends on PPC64 && PCI
2590 This driver supports the on-chip 1/10Gbit Ethernet controller on
2591 PA Semi's PWRficient line of chips.
2599 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2600 depends on MLX4_CORE
2603 This option causes debugging code to be compiled into the
2604 mlx4_core driver. The output can be turned on via the
2605 debug_level module parameter (which can also be set after
2606 the driver is loaded through sysfs).
2608 endif # NETDEV_10000
2610 source "drivers/net/tokenring/Kconfig"
2612 source "drivers/net/wireless/Kconfig"
2614 source "drivers/net/usb/Kconfig"
2616 source "drivers/net/pcmcia/Kconfig"
2618 source "drivers/net/wan/Kconfig"
2620 source "drivers/atm/Kconfig"
2622 source "drivers/s390/net/Kconfig"
2624 config XEN_NETDEV_FRONTEND
2625 tristate "Xen network device frontend driver"
2629 The network device frontend driver allows the kernel to
2630 access network devices exported exported by a virtual
2631 machine containing a physical network device driver. The
2632 frontend driver is intended for unprivileged guest domains;
2633 if you are compiling a kernel for a Xen guest, you almost
2634 certainly want to enable this.
2637 tristate "iSeries Virtual Ethernet driver support"
2638 depends on PPC_ISERIES
2641 tristate "RapidIO Ethernet over messaging driver support"
2644 config RIONET_TX_SIZE
2645 int "Number of outbound queue entries"
2649 config RIONET_RX_SIZE
2650 int "Number of inbound queue entries"
2655 bool "FDDI driver support"
2656 depends on (PCI || EISA || TC)
2658 Fiber Distributed Data Interface is a high speed local area network
2659 design; essentially a replacement for high speed Ethernet. FDDI can
2660 run over copper or fiber. If you are connected to such a network and
2661 want a driver for the FDDI card in your computer, say Y here (and
2662 then also Y to the driver for your FDDI card, below). Most people
2666 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2667 depends on FDDI && (PCI || EISA || TC)
2669 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2670 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2671 to a local FDDI network.
2673 To compile this driver as a module, choose M here: the module
2674 will be called defxx. If unsure, say N.
2678 prompt "Use MMIO instead of PIO" if PCI || EISA
2680 default n if PCI || EISA
2683 This instructs the driver to use EISA or PCI memory-mapped I/O
2684 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2685 Enabling this gives an improvement in processing time in parts
2686 of the driver, but it may cause problems with EISA (DEFEA)
2687 adapters. TURBOchannel does not have the concept of I/O ports,
2688 so MMIO is always used for these (DEFTA) adapters.
2693 tristate "SysKonnect FDDI PCI support"
2694 depends on FDDI && PCI
2697 Say Y here if you have a SysKonnect FDDI PCI adapter.
2698 The following adapters are supported by this driver:
2699 - SK-5521 (SK-NET FDDI-UP)
2700 - SK-5522 (SK-NET FDDI-UP DAS)
2701 - SK-5541 (SK-NET FDDI-FP)
2702 - SK-5543 (SK-NET FDDI-LP)
2703 - SK-5544 (SK-NET FDDI-LP DAS)
2704 - SK-5821 (SK-NET FDDI-UP64)
2705 - SK-5822 (SK-NET FDDI-UP64 DAS)
2706 - SK-5841 (SK-NET FDDI-FP64)
2707 - SK-5843 (SK-NET FDDI-LP64)
2708 - SK-5844 (SK-NET FDDI-LP64 DAS)
2709 - Netelligent 100 FDDI DAS Fibre SC
2710 - Netelligent 100 FDDI SAS Fibre SC
2711 - Netelligent 100 FDDI DAS UTP
2712 - Netelligent 100 FDDI SAS UTP
2713 - Netelligent 100 FDDI SAS Fibre MIC
2715 Read <file:Documentation/networking/skfp.txt> for information about
2718 Questions concerning this driver can be addressed to:
2719 <linux@syskonnect.de>
2721 To compile this driver as a module, choose M here: the module
2722 will be called skfp. This is recommended.
2725 bool "HIPPI driver support (EXPERIMENTAL)"
2726 depends on EXPERIMENTAL && INET && PCI
2728 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2729 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2730 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2731 single-mode). HIPPI networks are commonly used for clusters and to
2732 connect to super computers. If you are connected to a HIPPI network
2733 and have a HIPPI network card in your computer that you want to use
2734 under Linux, say Y here (you must also remember to enable the driver
2735 for your HIPPI card below). Most people will say N here.
2738 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2739 depends on HIPPI && PCI
2741 Say Y here if this is your PCI HIPPI network card.
2743 To compile this driver as a module, choose M here: the module
2744 will be called rrunner. If unsure, say N.
2746 config ROADRUNNER_LARGE_RINGS
2747 bool "Use large TX/RX rings (EXPERIMENTAL)"
2748 depends on ROADRUNNER
2750 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2751 of additional memory to allow for fastest operation, both for
2752 transmitting and receiving. This memory cannot be used by any other
2753 kernel code or by user space programs. Say Y here only if you have
2757 tristate "PLIP (parallel port) support"
2760 PLIP (Parallel Line Internet Protocol) is used to create a
2761 reasonably fast mini network consisting of two (or, rarely, more)
2762 local machines. A PLIP link from a Linux box is a popular means to
2763 install a Linux distribution on a machine which doesn't have a
2764 CD-ROM drive (a minimal system has to be transferred with floppies
2765 first). The kernels on both machines need to have this PLIP option
2766 enabled for this to work.
2768 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2769 ports (the connectors at the computers with 25 holes) are connected
2770 with "null printer" or "Turbo Laplink" cables which can transmit 4
2771 bits at a time (mode 0) or with special PLIP cables, to be used on
2772 bidirectional parallel ports only, which can transmit 8 bits at a
2773 time (mode 1); you can find the wiring of these cables in
2774 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2775 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2776 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2777 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2778 and winsock or NCSA's telnet.
2780 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2781 as the NET-3-HOWTO, both available from
2782 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2783 protocol has been changed and this PLIP driver won't work together
2784 with the PLIP support in Linux versions 1.0.x. This option enlarges
2785 your kernel by about 8 KB.
2787 To compile this driver as a module, choose M here and read
2788 <file:Documentation/networking/net-modules.txt>. The module will be
2789 called plip. If unsure, say Y or M, in case you buy a laptop
2793 tristate "PPP (point-to-point protocol) support"
2796 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2797 the same purpose: sending Internet traffic over telephone (and other
2798 serial) lines. Ask your access provider if they support it, because
2799 otherwise you can't use it; most Internet access providers these
2800 days support PPP rather than SLIP.
2802 To use PPP, you need an additional program called pppd as described
2803 in the PPP-HOWTO, available at
2804 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2805 the version of pppd recommended in <file:Documentation/Changes>.
2806 The PPP option enlarges your kernel by about 16 KB.
2808 There are actually two versions of PPP: the traditional PPP for
2809 asynchronous lines, such as regular analog phone lines, and
2810 synchronous PPP which can be used over digital ISDN lines for
2811 example. If you want to use PPP over phone lines or other
2812 asynchronous serial lines, you need to say Y (or M) here and also to
2813 the next option, "PPP support for async serial ports". For PPP over
2814 synchronous lines, you should say Y (or M) here and to "Support
2815 synchronous PPP", below.
2817 If you said Y to "Version information on all symbols" above, then
2818 you cannot compile the PPP driver into the kernel; you can then only
2819 compile it as a module. To compile this driver as a module, choose M
2820 here and read <file:Documentation/networking/net-modules.txt>.
2821 The module will be called ppp_generic.
2823 config PPP_MULTILINK
2824 bool "PPP multilink support (EXPERIMENTAL)"
2825 depends on PPP && EXPERIMENTAL
2827 PPP multilink is a protocol (defined in RFC 1990) which allows you
2828 to combine several (logical or physical) lines into one logical PPP
2829 connection, so that you can utilize your full bandwidth.
2831 This has to be supported at the other end as well and you need a
2832 version of the pppd daemon which understands the multilink protocol.
2837 bool "PPP filtering"
2840 Say Y here if you want to be able to filter the packets passing over
2841 PPP interfaces. This allows you to control which packets count as
2842 activity (i.e. which packets will reset the idle timer or bring up
2843 a demand-dialed link) and which packets are to be dropped entirely.
2844 You need to say Y here if you wish to use the pass-filter and
2845 active-filter options to pppd.
2850 tristate "PPP support for async serial ports"
2854 Say Y (or M) here if you want to be able to use PPP over standard
2855 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2856 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2859 To compile this driver as a module, choose M here.
2864 tristate "PPP support for sync tty ports"
2867 Say Y (or M) here if you want to be able to use PPP over synchronous
2868 (HDLC) tty devices, such as the SyncLink adapter. These devices
2869 are often used for high-speed leased lines like T1/E1.
2871 To compile this driver as a module, choose M here.
2874 tristate "PPP Deflate compression"
2879 Support for the Deflate compression method for PPP, which uses the
2880 Deflate algorithm (the same algorithm that gzip uses) to compress
2881 each PPP packet before it is sent over the wire. The machine at the
2882 other end of the PPP link (usually your ISP) has to support the
2883 Deflate compression method as well for this to be useful. Even if
2884 they don't support it, it is safe to say Y here.
2886 To compile this driver as a module, choose M here.
2889 tristate "PPP BSD-Compress compression"
2892 Support for the BSD-Compress compression method for PPP, which uses
2893 the LZW compression method to compress each PPP packet before it is
2894 sent over the wire. The machine at the other end of the PPP link
2895 (usually your ISP) has to support the BSD-Compress compression
2896 method as well for this to be useful. Even if they don't support it,
2897 it is safe to say Y here.
2899 The PPP Deflate compression method ("PPP Deflate compression",
2900 above) is preferable to BSD-Compress, because it compresses better
2903 Note that the BSD compression code will always be compiled as a
2904 module; it is called bsd_comp and will show up in the directory
2905 modules once you have said "make modules". If unsure, say N.
2908 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2909 depends on PPP && EXPERIMENTAL
2915 Support for the MPPE Encryption protocol, as employed by the
2916 Microsoft Point-to-Point Tunneling Protocol.
2918 See http://pptpclient.sourceforge.net/ for information on
2919 configuring PPTP clients and servers to utilize this method.
2922 tristate "PPP over Ethernet (EXPERIMENTAL)"
2923 depends on EXPERIMENTAL && PPP
2925 Support for PPP over Ethernet.
2927 This driver requires the latest version of pppd from the CVS
2928 repository at cvs.samba.org. Alternatively, see the
2929 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2930 which contains instruction on how to use this driver (under
2931 the heading "Kernel mode PPPoE").
2934 tristate "PPP over ATM"
2935 depends on ATM && PPP
2937 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2938 This implementation does not yet comply with section 8 of RFC2364,
2939 which can lead to bad results if the ATM peer loses state and
2940 changes its encapsulation unilaterally.
2943 tristate "PPP over L2TP (EXPERIMENTAL)"
2944 depends on EXPERIMENTAL && PPP && INET
2946 Support for PPP-over-L2TP socket family. L2TP is a protocol
2947 used by ISPs and enterprises to tunnel PPP traffic over UDP
2948 tunnels. L2TP is replacing PPTP for VPN uses.
2950 This kernel component handles only L2TP data packets: a
2951 userland daemon handles L2TP the control protocol (tunnel
2952 and session setup). One such daemon is OpenL2TP
2953 (http://openl2tp.sourceforge.net/).
2956 tristate "SLIP (serial line) support"
2958 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2959 connect to your Internet service provider or to connect to some
2960 other local Unix box or if you want to configure your Linux box as a
2961 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2962 Internet Protocol) is a protocol used to send Internet traffic over
2963 serial connections such as telephone lines or null modem cables;
2964 nowadays, the protocol PPP is more commonly used for this same
2967 Normally, your access provider has to support SLIP in order for you
2968 to be able to use it, but there is now a SLIP emulator called SLiRP
2969 around (available from
2970 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2971 allows you to use SLIP over a regular dial up shell connection. If
2972 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2973 NET-3-HOWTO, available from
2974 <http://www.tldp.org/docs.html#howto>, explains how to
2975 configure SLIP. Note that you don't need this option if you just
2976 want to run term (term is a program which gives you almost full
2977 Internet connectivity if you have a regular dial up shell account on
2978 some Internet connected Unix computer. Read
2979 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2980 support will enlarge your kernel by about 4 KB. If unsure, say N.
2982 To compile this driver as a module, choose M here and read
2983 <file:Documentation/networking/net-modules.txt>. The module will be
2986 config SLIP_COMPRESSED
2987 bool "CSLIP compressed headers"
2991 This protocol is faster than SLIP because it uses compression on the
2992 TCP/IP headers (not on the data itself), but it has to be supported
2993 on both ends. Ask your access provider if you are not sure and
2994 answer Y, just in case. You will still be able to use plain SLIP. If
2995 you plan to use SLiRP, the SLIP emulator (available from
2996 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2997 allows you to use SLIP over a regular dial up shell connection, you
2998 definitely want to say Y here. The NET-3-HOWTO, available from
2999 <http://www.tldp.org/docs.html#howto>, explains how to configure
3000 CSLIP. This won't enlarge your kernel.
3005 This option enables Van Jacobsen serial line header compression
3009 bool "Keepalive and linefill"
3012 Adds additional capabilities to the SLIP driver to support the
3013 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3016 config SLIP_MODE_SLIP6
3017 bool "Six bit SLIP encapsulation"
3020 Just occasionally you may need to run IP over hostile serial
3021 networks that don't pass all control characters or are only seven
3022 bit. Saying Y here adds an extra mode you can use with SLIP:
3023 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3024 the serial device. Naturally, this has to be supported at the other
3025 end of the link as well. It's good enough, for example, to run IP
3026 over the async ports of a Camtec JNT Pad. If unsure, say N.
3029 bool "Fibre Channel driver support"
3030 depends on SCSI && PCI
3032 Fibre Channel is a high speed serial protocol mainly used to connect
3033 large storage devices to the computer; it is compatible with and
3034 intended to replace SCSI.
3036 If you intend to use Fibre Channel, you need to have a Fibre channel
3037 adaptor card in your computer; say Y here and to the driver for your
3038 adaptor below. You also should have said Y to "SCSI support" and
3039 "SCSI generic support".
3042 tristate "Traffic Shaper (OBSOLETE)"
3043 depends on EXPERIMENTAL
3045 The traffic shaper is a virtual network device that allows you to
3046 limit the rate of outgoing data flow over some other network device.
3047 The traffic that you want to slow down can then be routed through
3048 these virtual devices. See
3049 <file:Documentation/networking/shaper.txt> for more information.
3051 An alternative to this traffic shaper are traffic schedulers which
3052 you'll get if you say Y to "QoS and/or fair queuing" in
3053 "Networking options".
3055 To compile this driver as a module, choose M here: the module
3056 will be called shaper. If unsure, say N.
3059 tristate "Network console logging support (EXPERIMENTAL)"
3060 depends on EXPERIMENTAL
3062 If you want to log kernel messages over the network, enable this.
3063 See <file:Documentation/networking/netconsole.txt> for details.
3065 config NETCONSOLE_DYNAMIC
3066 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3067 depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3070 This option enables the ability to dynamically reconfigure target
3071 parameters (interface, IP addresses, port numbers, MAC addresses)
3072 at runtime through a userspace interface exported using configfs.
3073 See <file:Documentation/networking/netconsole.txt> for details.
3079 bool "Netpoll traffic trapping"
3083 config NET_POLL_CONTROLLER