3 # Network device configuration
8 bool "Network device support"
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
25 source "drivers/net/arcnet/Kconfig"
29 tristate "Dummy net driver support"
32 This is essentially a bit-bucket device (i.e. traffic you send to
33 this device is consigned into oblivion) with a configurable IP
34 address. It is most commonly used in order to make your currently
35 inactive SLIP address seem like a real address for local programs.
36 If you use SLIP or PPP, you might want to say Y here. Since this
37 thing often comes in handy, the default is Y. It won't enlarge your
38 kernel either. What a deal. Read about it in the Network
39 Administrator's Guide, available from
40 <http://www.tldp.org/docs.html#guide>.
42 To compile this driver as a module, choose M here: the module
43 will be called dummy. If you want to use more than one dummy
44 device at a time, you need to compile this driver as a module.
45 Instead of 'dummy', the devices will then be called 'dummy0',
49 tristate "Bonding driver support"
52 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
53 Channels together. This is called 'Etherchannel' by Cisco,
54 'Trunking' by Sun, and 'Bonding' in Linux.
56 If you have two Ethernet connections to some other computer, you can
57 make them behave like one double speed connection using this driver.
58 Naturally, this has to be supported at the other end as well, either
59 with a similar Bonding Linux driver, a Cisco 5500 switch or a
60 SunTrunking SunSoft driver.
62 This is similar to the EQL driver, but it merges Ethernet segments
63 instead of serial lines.
65 To compile this driver as a module, choose M here: the module
66 will be called bonding.
69 tristate "EQL (serial line load balancing) support"
72 If you have two serial connections to some other computer (this
73 usually requires two modems and two telephone lines) and you use
74 SLIP (the protocol for sending Internet traffic over telephone
75 lines) or PPP (a better SLIP) on them, you can make them behave like
76 one double speed connection using this driver. Naturally, this has
77 to be supported at the other end as well, either with a similar EQL
78 Linux driver or with a Livingston Portmaster 2e.
80 Say Y if you want this and read
81 <file:Documentation/networking/eql.txt>. You may also want to read
82 section 6.2 of the NET-3-HOWTO, available from
83 <http://www.tldp.org/docs.html#howto>.
85 To compile this driver as a module, choose M here: the module
86 will be called eql. If unsure, say N.
89 tristate "Universal TUN/TAP device driver support"
92 TUN/TAP provides packet reception and transmission for user space
93 programs. It can be viewed as a simple Point-to-Point or Ethernet
94 device, which instead of receiving packets from a physical media,
95 receives them from user space program and instead of sending packets
96 via physical media writes them to the user space program.
98 When a program opens /dev/net/tun, driver creates and registers
99 corresponding net device tunX or tapX. After a program closed above
100 devices, driver will automatically delete tunXX or tapXX device and
101 all routes corresponding to it.
103 Please read <file:Documentation/networking/tuntap.txt> for more
106 To compile this driver as a module, choose M here: the module
109 If you don't know what to use this for, you don't need it.
112 tristate "Ethertap network tap"
113 depends on NETDEVICES && EXPERIMENTAL && NETLINK_DEV
115 If you say Y here (and have said Y to "Kernel/User network link
116 driver", above) and create a character special file /dev/tap0 with
117 major number 36 and minor number 16 using mknod ("man mknod"), you
118 will be able to have a user space program read and write raw
119 Ethernet frames from/to that special file. tap0 can be configured
120 with ifconfig and route like any other Ethernet device but it is not
121 connected to any physical LAN; everything written by the user to
122 /dev/tap0 is treated by the kernel as if it had come in from a LAN
123 to the device tap0; everything the kernel wants to send out over the
124 device tap0 can instead be read by the user from /dev/tap0: the user
125 mode program replaces the LAN that would be attached to an ordinary
126 Ethernet device. Please read the file
127 <file:Documentation/networking/ethertap.txt> for more information.
129 To compile this driver as a module, choose M here: the module
130 will be called ethertap.
132 If you don't know what to use this for, you don't need it.
135 tristate "General Instruments Surfboard 1000"
136 depends on NETDEVICES && PNP
138 This is a driver for the General Instrument (also known as
139 NextLevel) SURFboard 1000 internal
140 cable modem. This is an ISA card which is used by a number of cable
141 TV companies to provide cable modem access. It's a one-way
142 downstream-only cable modem, meaning that your upstream net link is
143 provided by your regular phone modem.
145 At present this driver only compiles as a module, so say M here if
146 you have this card. The module will be called sb1000. Then read
147 <file:Documentation/networking/README.sb1000> for information on how
148 to use this module, as it needs special ppp scripts for establishing
149 a connection. Further documentation and the necessary scripts can be
152 <http://www.jacksonville.net/~fventuri/>
153 <http://home.adelphia.net/~siglercm/sb1000.html>
154 <http://linuxpower.cx/~cable/>
156 If you don't have this card, of course say N.
162 menu "Ethernet (10 or 100Mbit)"
163 depends on NETDEVICES
166 bool "Ethernet (10 or 100Mbit)"
168 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
169 type of Local Area Network (LAN) in universities and companies.
171 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
172 coaxial cable, linking computers in a chain), 10BASE-T or twisted
173 pair (10 Mbps over twisted pair cable, linking computers to central
174 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
175 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
176 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
177 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
178 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
179 Ethernet (1 Gbps over optical fiber or short copper links).
181 If your Linux machine will be connected to an Ethernet and you have
182 an Ethernet network interface card (NIC) installed in your computer,
183 say Y here and read the Ethernet-HOWTO, available from
184 <http://www.tldp.org/docs.html#howto>. You will then also have
185 to say Y to the driver for your particular NIC.
187 Note that the answer to this question won't directly affect the
188 kernel: saying N will just cause the configurator to skip all
189 the questions about Ethernet network cards. If unsure, say N.
192 tristate "Generic Media Independent Interface device support"
193 depends on NET_ETHERNET
195 Most ethernet controllers have MII transceiver either as an external
196 or internal device. It is safe to say Y or M here even if your
197 ethernet card lack MII.
199 source "drivers/net/arm/Kconfig"
202 tristate "MACE (Power Mac ethernet) support"
203 depends on NET_ETHERNET && PPC_PMAC
206 Power Macintoshes and clones with Ethernet built-in on the
207 motherboard will usually use a MACE (Medium Access Control for
208 Ethernet) interface. Say Y to include support for the MACE chip.
210 To compile this driver as a module, choose M here: the module
213 config MACE_AAUI_PORT
214 bool "Use AAUI port instead of TP by default"
217 Some Apple machines (notably the Apple Network Server) which use the
218 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
219 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
220 Y here if you have such a machine. If unsure, say N.
221 The driver will default to AAUI on ANS anyway, and if you use it as
222 a module, you can provide the port_aaui=0|1 to force the driver.
225 tristate "BMAC (G3 ethernet) support"
226 depends on NET_ETHERNET && PPC_PMAC
229 Say Y for support of BMAC Ethernet interfaces. These are used on G3
232 To compile this driver as a module, choose M here: the module
236 tristate "National DP83902AV (Oak ethernet) support"
237 depends on NET_ETHERNET && PPC
240 Say Y if your machine has this type of Ethernet network card.
242 To compile this driver as a module, choose M here: the module
243 will be called oaknet.
246 tristate "Ariadne support"
247 depends on NET_ETHERNET && ZORRO
249 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
252 To compile this driver as a module, choose M here: the module
253 will be called ariadne.
256 tristate "A2065 support"
257 depends on NET_ETHERNET && ZORRO
260 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
263 To compile this driver as a module, choose M here: the module
264 will be called a2065.
267 tristate "Hydra support"
268 depends on NET_ETHERNET && ZORRO
271 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
273 To compile this driver as a module, choose M here: the module
274 will be called hydra.
277 tristate "Zorro NS8390-based Ethernet support"
278 depends on NET_ETHERNET && ZORRO
281 This driver is for Zorro Ethernet cards using an NS8390-compatible
282 chipset, like the Village Tronic Ariadne II and the Individual
283 Computers X-Surf Ethernet cards. If you have such a card, say Y.
286 To compile this driver as a module, choose M here: the module
287 will be called zorro8390.
290 tristate "PCMCIA NE2000 support"
291 depends on NETDEVICES && AMIGA_PCMCIA
294 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
297 To compile this driver as a module, choose M here: the module
301 tristate "Apollo 3c505 support"
302 depends on NETDEVICES && APOLLO
304 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
305 If you don't have one made for Apollos, you can use one from a PC,
306 except that your Apollo won't be able to boot from it (because the
307 code in the ROM will be for a PC).
310 bool "Macintosh NS 8390 based ethernet cards"
311 depends on NETDEVICES && MAC
314 If you want to include a driver to support Nubus or LC-PDS
315 Ethernet cards using an NS8390 chipset or its equivalent, say Y
316 and read the Ethernet-HOWTO, available from
317 <http://www.tldp.org/docs.html#howto>.
320 tristate "Macintosh CS89x0 based ethernet cards"
321 depends on NETDEVICES && MAC && BROKEN
323 Support for CS89x0 chipset based Ethernet cards. If you have a
324 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
325 read the Ethernet-HOWTO, available from
326 <http://www.tldp.org/docs.html#howto>.
328 To compile this driver as a module, choose M here and read
329 <file:Documentation/networking/net-modules.txt>. This module will
333 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
334 depends on NETDEVICES && MAC
336 Support for NatSemi SONIC based Ethernet devices. This includes
337 the onboard Ethernet in many Quadras as well as some LC-PDS,
338 a few Nubus and all known Comm Slot Ethernet cards. If you have
339 one of these say Y and read the Ethernet-HOWTO, available from
340 <http://www.tldp.org/docs.html#howto>.
342 To compile this driver as a module, choose M here and read
343 <file:Documentation/networking/net-modules.txt>. This module will
347 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
348 depends on NETDEVICES && MAC && EXPERIMENTAL
351 Support for the onboard AMD 79C940 MACE Ethernet controller used in
352 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
353 say Y and read the Ethernet-HOWTO, available from
354 <http://www.tldp.org/docs.html#howto>.
357 tristate "MVME147 (Lance) Ethernet support"
358 depends on NETDEVICES && MVME147
361 Support for the on-board Ethernet interface on the Motorola MVME147
362 single-board computer. Say Y here to include the
363 driver for this chip in your kernel.
364 To compile this driver as a module, choose M here.
367 tristate "MVME16x Ethernet support"
368 depends on NETDEVICES && MVME16x
370 This is the driver for the Ethernet interface on the Motorola
371 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
372 driver for this chip in your kernel.
373 To compile this driver as a module, choose M here.
376 tristate "BVME6000 Ethernet support"
377 depends on NETDEVICES && BVME6000
379 This is the driver for the Ethernet interface on BVME4000 and
380 BVME6000 VME boards. Say Y here to include the driver for this chip
382 To compile this driver as a module, choose M here.
385 tristate "Atari Lance support"
386 depends on NETDEVICES && ATARI
388 Say Y to include support for several Atari Ethernet adapters based
389 on the AMD Lance chipset: RieblCard (with or without battery), or
390 PAMCard VME (also the version by Rhotron, with different addresses).
393 tristate "BioNet-100 support"
394 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
396 Say Y to include support for BioData's BioNet-100 Ethernet adapter
397 for the ACSI port. The driver works (has to work...) with a polled
398 I/O scheme, so it's rather slow :-(
401 tristate "PAMsNet support"
402 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
404 Say Y to include support for the PAMsNet Ethernet adapter for the
405 ACSI port ("ACSI node"). The driver works (has to work...) with a
406 polled I/O scheme, so it's rather slow :-(
409 tristate "Sun3/Sun3x on-board LANCE support"
410 depends on NETDEVICES && (SUN3 || SUN3X)
412 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
413 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
414 here to compile in the Linux driver for this and enable Ethernet.
415 General Linux information on the Sun 3 and 3x series (now
417 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
419 If you're not building a kernel for a Sun 3, say N.
422 tristate "Sun3 on-board Intel 82586 support"
423 depends on NETDEVICES && SUN3
425 This driver enables support for the on-board Intel 82586 based
426 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
427 that this driver does not support 82586-based adapters on additional
431 bool "HP on-board LANCE support"
432 depends on NETDEVICES && HP300
435 If you want to use the builtin "LANCE" Ethernet controller on an
436 HP300 machine, say Y here.
439 tristate "Lasi ethernet"
440 depends on NET_ETHERNET && PARISC && GSC_LASI
442 Say Y here to support the on-board Intel 82596 ethernet controller
443 built into Hewlett-Packard PA-RISC machines.
445 config MIPS_JAZZ_SONIC
446 tristate "MIPS JAZZ onboard SONIC Ethernet support"
447 depends on NET_ETHERNET && MIPS_JAZZ
449 This is the driver for the onboard card of MIPS Magnum 4000,
450 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
452 config MIPS_GT96100ETH
453 bool "MIPS GT96100 Ethernet support"
454 depends on NET_ETHERNET && MIPS_GT96100
456 Say Y here to support the Ethernet subsystem on your GT96100 card.
458 config MIPS_AU1X00_ENET
459 bool "MIPS AU1000 Ethernet support"
460 depends on NET_ETHERNET && SOC_AU1X00
463 If you have an Alchemy Semi AU1X00 based system
464 say Y. Otherwise, say N.
466 config NET_SB1250_MAC
467 tristate "SB1250 Ethernet support"
468 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
471 bool "SGI IOC3 Ethernet"
472 depends on NET_ETHERNET && SGI_IP27
475 If you have a network (Ethernet) card of this type, say Y and read
476 the Ethernet-HOWTO, available from
477 <http://www.tldp.org/docs.html#howto>.
479 config SGI_O2MACE_ETH
480 tristate "SGI O2 MACE Fast Ethernet support"
481 depends on NET_ETHERNET && SGI_IP32=y
484 tristate "National DP83902AV support"
485 depends on NET_ETHERNET && SUPERH
488 Support for cards based on the National Semiconductor DP83902AV
489 ST-NIC Serial Network Interface Controller for Twisted Pair. This
490 is a 10Mbit/sec Ethernet controller. Product overview and specs at
491 <http://www.national.com/pf/DP/DP83902A.html>.
496 tristate "Sun LANCE support"
497 depends on NET_ETHERNET && SBUS
500 This driver supports the "le" interface present on all 32-bit Sparc
501 systems, on some older Ultra systems and as an Sbus option. These
502 cards are based on the AMD Lance chipset, which is better known
503 via the NE2100 cards.
505 To compile this driver as a module, choose M here: the module
506 will be called sunlance.
509 tristate "Sun Happy Meal 10/100baseT support"
510 depends on NET_ETHERNET && (SBUS || PCI)
513 This driver supports the "hme" interface present on most Ultra
514 systems and as an option on older Sbus systems. This driver supports
515 both PCI and Sbus devices. This driver also supports the "qfe" quad
516 100baseT device available in both PCI and Sbus configurations.
518 To compile this driver as a module, choose M here: the module
519 will be called sunhme.
522 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
523 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
526 This driver supports the "be" interface available as an Sbus option.
527 This is Sun's older 100baseT Ethernet device.
529 To compile this driver as a module, choose M here: the module
530 will be called sunbmac.
533 tristate "Sun QuadEthernet support"
534 depends on NET_ETHERNET && SBUS
537 This driver supports the "qe" 10baseT Ethernet device, available as
538 an Sbus option. Note that this is not the same as Quad FastEthernet
539 "qfe" which is supported by the Happy Meal driver instead.
541 To compile this driver as a module, choose M here: the module
542 will be called sunqe.
545 tristate "Sun GEM support"
546 depends on NET_ETHERNET && PCI
549 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
550 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
552 config NET_VENDOR_3COM
554 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
556 If you have a network (Ethernet) card belonging to this class, say Y
557 and read the Ethernet-HOWTO, available from
558 <http://www.tldp.org/docs.html#howto>.
560 Note that the answer to this question doesn't directly affect the
561 kernel: saying N will just cause the configurator to skip all
562 the questions about 3COM cards. If you say Y, you will be asked for
563 your specific card in the following questions.
566 tristate "3c501 \"EtherLink\" support"
567 depends on NET_VENDOR_3COM && ISA
569 If you have a network (Ethernet) card of this type, say Y and read
570 the Ethernet-HOWTO, available from
571 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
572 new card, since the 3c501 is slow, broken, and obsolete: you will
573 have problems. Some people suggest to ping ("man ping") a nearby
574 machine every minute ("man cron") when using this card.
576 To compile this driver as a module, choose M here and read
577 <file:Documentation/networking/net-modules.txt>. The module
578 will be called 3c501.
581 tristate "3c503 \"EtherLink II\" support"
582 depends on NET_VENDOR_3COM && ISA
585 If you have a network (Ethernet) card of this type, say Y and read
586 the Ethernet-HOWTO, available from
587 <http://www.tldp.org/docs.html#howto>.
589 To compile this driver as a module, choose M here and read
590 <file:Documentation/networking/net-modules.txt>. The module
591 will be called 3c503.
594 tristate "3c505 \"EtherLink Plus\" support"
595 depends on NET_VENDOR_3COM && ISA
597 Information about this network (Ethernet) card can be found in
598 <file:Documentation/networking/3c505.txt>. If you have a card of
599 this type, say Y and read the Ethernet-HOWTO, available from
600 <http://www.tldp.org/docs.html#howto>.
602 To compile this driver as a module, choose M here and read
603 <file:Documentation/networking/net-modules.txt>. The module
604 will be called 3c505.
607 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
608 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
610 If you have a network (Ethernet) card of this type, say Y and read
611 the Ethernet-HOWTO, available from
612 <http://www.tldp.org/docs.html#howto>.
614 To compile this driver as a module, choose M here and read
615 <file:Documentation/networking/net-modules.txt>. The module
616 will be called 3c507.
619 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support"
620 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
622 If you have a network (Ethernet) card belonging to the 3Com
623 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
624 from <http://www.tldp.org/docs.html#howto>.
626 If your card is not working you may need to use the DOS
627 setup disk to disable Plug & Play mode, and to select the default
630 To compile this driver as a module, choose M here and read
631 <file:Documentation/networking/net-modules.txt>. The module
632 will be called 3c509.
635 tristate "3c515 ISA \"Fast EtherLink\""
636 depends on NET_VENDOR_3COM && (ISA || EISA)
638 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
639 network card, say Y and read the Ethernet-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>.
642 To compile this driver as a module, choose M here and read
643 <file:Documentation/networking/net-modules.txt>. The module
644 will be called 3c515.
647 tristate "3c523 \"EtherLink/MC\" support"
648 depends on NET_VENDOR_3COM && MCA
650 If you have a network (Ethernet) card of this type, say Y and read
651 the Ethernet-HOWTO, available from
652 <http://www.tldp.org/docs.html#howto>.
654 To compile this driver as a module, choose M here and read
655 <file:Documentation/networking/net-modules.txt>. The module
656 will be called 3c523.
659 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
660 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
662 If you have a network (Ethernet) card of this type, say Y and read
663 the Ethernet-HOWTO, available from
664 <http://www.tldp.org/docs.html#howto>.
666 To compile this driver as a module, choose M here and read
667 <file:Documentation/networking/net-modules.txt>. The module
668 will be called 3c527.
671 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
672 depends on NET_VENDOR_3COM && (PCI || EISA)
674 This option enables driver support for a large number of 10mbps and
675 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
677 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
678 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
679 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
680 "Tornado" (3c905) PCI
681 "Hurricane" (3c555/3cSOHO) PCI
683 If you have such a card, say Y and read the Ethernet-HOWTO,
684 available from <http://www.tldp.org/docs.html#howto>. More
685 specific information is in
686 <file:Documentation/networking/vortex.txt> and in the comments at
687 the beginning of <file:drivers/net/3c59x.c>.
689 To compile this support as a module, choose M here and read
690 <file:Documentation/networking/net-modules.txt>.
693 tristate "3cr990 series \"Typhoon\" support"
694 depends on NET_VENDOR_3COM && PCI
697 This option enables driver support for the 3cr990 series of cards:
699 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
700 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
701 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
703 If you have a network (Ethernet) card of this type, say Y and read
704 the Ethernet-HOWTO, available from
705 <http://www.tldp.org/docs.html#howto>.
707 To compile this driver as a module, choose M here and read
708 <file:Documentation/networking/net-modules.txt>. The module
709 will be called typhoon.
712 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
713 depends on NET_ETHERNET && ISA
715 If you have a network (Ethernet) card of this type, say Y and read
716 the Ethernet-HOWTO, available from
717 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
720 To compile this driver as a module, choose M here: the module
721 will be called lance. This is recommended.
723 config NET_VENDOR_SMC
724 bool "Western Digital/SMC cards"
725 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
727 If you have a network (Ethernet) card belonging to this class, say Y
728 and read the Ethernet-HOWTO, available from
729 <http://www.tldp.org/docs.html#howto>.
731 Note that the answer to this question doesn't directly affect the
732 kernel: saying N will just cause the configurator to skip all
733 the questions about Western Digital cards. If you say Y, you will be
734 asked for your specific card in the following questions.
737 tristate "WD80*3 support"
738 depends on NET_VENDOR_SMC && ISA
741 If you have a network (Ethernet) card of this type, say Y and read
742 the Ethernet-HOWTO, available from
743 <http://www.tldp.org/docs.html#howto>.
745 To compile this driver as a module, choose M here and read
746 <file:Documentation/networking/net-modules.txt>. The module
750 tristate "SMC Ultra MCA support"
751 depends on NET_VENDOR_SMC && MCA
754 If you have a network (Ethernet) card of this type and are running
755 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
756 available from <http://www.tldp.org/docs.html#howto>.
758 To compile this driver as a module, choose M here and read
759 <file:Documentation/networking/net-modules.txt>. The module
760 will be called smc-mca.
763 tristate "SMC Ultra support"
764 depends on NET_VENDOR_SMC && ISA
767 If you have a network (Ethernet) card of this type, say Y and read
768 the Ethernet-HOWTO, available from
769 <http://www.tldp.org/docs.html#howto>.
771 Important: There have been many reports that, with some motherboards
772 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
773 such as some BusLogic models) causes corruption problems with many
774 operating systems. The Linux smc-ultra driver has a work-around for
775 this but keep it in mind if you have such a SCSI card and have
778 To compile this driver as a module, choose M here and read
779 <file:Documentation/networking/net-modules.txt>. The module
780 will be called smc-ultra.
783 tristate "SMC Ultra32 EISA support"
784 depends on NET_VENDOR_SMC && EISA
787 If you have a network (Ethernet) card of this type, say Y and read
788 the Ethernet-HOWTO, available from
789 <http://www.tldp.org/docs.html#howto>.
791 To compile this driver as a module, choose M here and read
792 <file:Documentation/networking/net-modules.txt>. The module
793 will be called smc-ultra32.
796 tristate "SMC 9194 support"
797 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
800 This is support for the SMC9xxx based Ethernet cards. Choose this
801 option if you have a DELL laptop with the docking station, or
802 another SMC9192/9194 based chipset. Say Y if you want it compiled
803 into the kernel, and read the file
804 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
805 available from <http://www.tldp.org/docs.html#howto>.
807 To compile this driver as a module, choose M here and read
808 <file:Documentation/networking/net-modules.txt>. The module
809 will be called smc9194.
811 config NET_VENDOR_RACAL
812 bool "Racal-Interlan (Micom) NI cards"
813 depends on NET_ETHERNET && ISA
815 If you have a network (Ethernet) card belonging to this class, such
816 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
817 available from <http://www.tldp.org/docs.html#howto>.
819 Note that the answer to this question doesn't directly affect the
820 kernel: saying N will just cause the configurator to skip all
821 the questions about NI cards. If you say Y, you will be asked for
822 your specific card in the following questions.
825 tristate "NI5010 support (EXPERIMENTAL)"
826 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
828 If you have a network (Ethernet) card of this type, say Y and read
829 the Ethernet-HOWTO, available from
830 <http://www.tldp.org/docs.html#howto>. Note that this is still
833 To compile this driver as a module, choose M here and read
834 <file:Documentation/networking/net-modules.txt>. The module
835 will be called ni5010.
838 tristate "NI5210 support"
839 depends on NET_VENDOR_RACAL && ISA
841 If you have a network (Ethernet) card of this type, say Y and read
842 the Ethernet-HOWTO, available from
843 <http://www.tldp.org/docs.html#howto>.
845 To compile this driver as a module, choose M here and read
846 <file:Documentation/networking/net-modules.txt>. The module
850 tristate "NI6510 support"
851 depends on NET_VENDOR_RACAL && ISA
853 If you have a network (Ethernet) card of this type, say Y and read
854 the Ethernet-HOWTO, available from
855 <http://www.tldp.org/docs.html#howto>.
857 To compile this driver as a module, choose M here and read
858 <file:Documentation/networking/net-modules.txt>. The module
861 source "drivers/net/tulip/Kconfig"
864 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)"
865 depends on NET_ETHERNET && (ISA || MCA) && EXPERIMENTAL
868 If you have a network (Ethernet) card of this type, say Y and read
869 the Ethernet-HOWTO, available from
870 <http://www.tldp.org/docs.html#howto>.
872 To compile this driver as a module, choose M here and read
873 <file:Documentation/networking/net-modules.txt>. The module
874 will be called at1700.
877 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
878 depends on NET_ETHERNET && (ISA || EISA || MCA)
881 If you have a network (Ethernet) card of this type, say Y and read
882 the Ethernet-HOWTO, available from
883 <http://www.tldp.org/docs.html#howto> as well as
884 <file:drivers/net/depca.c>.
886 To compile this driver as a module, choose M here and read
887 <file:Documentation/networking/net-modules.txt>. The module
888 will be called depca.
891 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
892 depends on NET_ETHERNET && (ISA || EISA || PCI)
894 If you have a network (Ethernet) card of this type, say Y and read
895 the Ethernet-HOWTO, available from
896 <http://www.tldp.org/docs.html#howto>.
898 To compile this driver as a module, choose M here and read
899 <file:Documentation/networking/net-modules.txt>. The module
900 will be called hp100.
903 bool "Other ISA cards"
904 depends on NET_ETHERNET && ISA && !X86_PC9800
906 If your network (Ethernet) card hasn't been mentioned yet and its
907 bus system (that's the way the cards talks to the other components
908 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
909 Make sure you know the name of your card. Read the Ethernet-HOWTO,
910 available from <http://www.tldp.org/docs.html#howto>.
914 Note that the answer to this question doesn't directly affect the
915 kernel: saying N will just cause the configurator to skip all
916 the remaining ISA network card questions. If you say Y, you will be
917 asked for your specific card in the following questions.
920 tristate "Cabletron E21xx support"
924 If you have a network (Ethernet) card of this type, say Y and read
925 the Ethernet-HOWTO, available from
926 <http://www.tldp.org/docs.html#howto>.
928 To compile this driver as a module, choose M here and read
929 <file:Documentation/networking/net-modules.txt>. The module
930 will be called e2100.
933 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
937 This driver supports the DE203, DE204 and DE205 network (Ethernet)
938 cards. If this is for you, say Y and read
939 <file:Documentation/networking/ewrk3.txt> in the kernel source as
940 well as the Ethernet-HOWTO, available from
941 <http://www.tldp.org/docs.html#howto>.
943 To compile this driver as a module, choose M here and read
944 <file:Documentation/networking/net-modules.txt>. The module
945 will be called ewrk3.
948 tristate "EtherExpress 16 support"
951 If you have an EtherExpress16 network (Ethernet) card, say Y and
952 read the Ethernet-HOWTO, available from
953 <http://www.tldp.org/docs.html#howto>. Note that the Intel
954 EtherExpress16 card used to be regarded as a very poor choice
955 because the driver was very unreliable. We now have a new driver
956 that should do better.
958 To compile this driver as a module, choose M here and read
959 <file:Documentation/networking/net-modules.txt>. The module
960 will be called eexpress.
963 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
966 If you have a network (Ethernet) card of this type, say Y. This
967 driver supports intel i82595{FX,TX} based boards. Note however
968 that the EtherExpress PRO/100 Ethernet card has its own separate
969 driver. Please read the Ethernet-HOWTO, available from
970 <http://www.tldp.org/docs.html#howto>.
972 To compile this driver as a module, choose M here and read
973 <file:Documentation/networking/net-modules.txt>. The module
974 will be called eepro.
977 tristate "FMV-181/182/183/184 support (OBSOLETE)"
978 depends on NET_ISA && OBSOLETE
980 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
981 say Y and read the Ethernet-HOWTO, available from
982 <http://www.tldp.org/docs.html#howto>.
984 If you use an FMV-183 or FMV-184 and it is not working, you may need
985 to disable Plug & Play mode of the card.
987 To compile this driver as a module, choose M here and read
988 <file:Documentation/networking/net-modules.txt>. The module
989 will be called fmv18x.
992 tristate "HP PCLAN+ (27247B and 27252A) support"
996 If you have a network (Ethernet) card of this type, say Y and read
997 the Ethernet-HOWTO, available from
998 <http://www.tldp.org/docs.html#howto>.
1000 To compile this driver as a module, choose M here and read
1001 <file:Documentation/networking/net-modules.txt>. The module
1002 will be called hp-plus.
1005 tristate "HP PCLAN (27245 and other 27xxx series) support"
1009 If you have a network (Ethernet) card of this type, say Y and read
1010 the Ethernet-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1013 To compile this driver as a module, choose M here and read
1014 <file:Documentation/networking/net-modules.txt>. The module
1018 tristate "LP486E on board Ethernet"
1021 Say Y here to support the 82596-based on-board Ethernet controller
1022 for the Panther motherboard, which is one of the two shipped in the
1023 Intel Professional Workstation.
1026 tristate "ICL EtherTeam 16i/32 support"
1029 If you have a network (Ethernet) card of this type, say Y and read
1030 the Ethernet-HOWTO, available from
1031 <http://www.tldp.org/docs.html#howto>.
1033 To compile this driver as a module, choose M here and read
1034 <file:Documentation/networking/net-modules.txt>. The module
1035 will be called eth16i.
1038 tristate "NE2000/NE1000 support"
1039 depends on NET_ISA || (Q40 && m)
1042 If you have a network (Ethernet) card of this type, say Y and read
1043 the Ethernet-HOWTO, available from
1044 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1045 without a specific driver are compatible with NE2000.
1047 If you have a PCI NE2000 card however, say N here and Y to "PCI
1048 NE2000 support", above. If you have a NE2000 card and are running on
1049 an MCA system (a bus system used on some IBM PS/2 computers and
1050 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1053 To compile this driver as a module, choose M here and read
1054 <file:Documentation/networking/net-modules.txt>. The module
1058 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1059 depends on NET_ISA && EXPERIMENTAL
1061 The Zenith Z-Note notebook computer has a built-in network
1062 (Ethernet) card, and this is the Linux driver for it. Note that the
1063 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1064 by this driver. Read the Ethernet-HOWTO, available from
1065 <http://www.tldp.org/docs.html#howto>.
1068 tristate "SEEQ8005 support (EXPERIMENTAL)"
1069 depends on NET_ISA && EXPERIMENTAL
1071 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1072 is for you, read the Ethernet-HOWTO, available from
1073 <http://www.tldp.org/docs.html#howto>.
1075 To compile this driver as a module, choose M here and read
1076 <file:Documentation/networking/net-modules.txt>. The module
1077 will be called seeq8005.
1080 tristate "SK_G16 support (OBSOLETE)"
1081 depends on NET_ISA && OBSOLETE
1083 If you have a network (Ethernet) card of this type, say Y and read
1084 the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1088 bool "NEC PC-9800 C-bus cards"
1089 depends on NET_ETHERNET && ISA && X86_PC9800
1091 If your network (Ethernet) card hasn't been mentioned yet and its
1092 bus system (that's the way the cards talks to the other components
1093 of your computer) is NEC PC-9800 C-Bus, say Y.
1096 tristate "Most NE2000-based Ethernet support"
1100 config NE2K_CBUS_EGY98
1101 bool "Melco EGY-98 support"
1102 depends on NE2K_CBUS
1104 config NE2K_CBUS_LGY98
1105 bool "Melco LGY-98 support"
1106 depends on NE2K_CBUS
1108 config NE2K_CBUS_ICM
1109 bool "ICM IF-27xxET support"
1110 depends on NE2K_CBUS
1112 config NE2K_CBUS_IOLA98
1113 bool "I-O DATA LA-98 support"
1114 depends on NE2K_CBUS
1116 config NE2K_CBUS_CNET98EL
1117 bool "Contec C-NET(98)E/L support"
1118 depends on NE2K_CBUS
1120 config NE2K_CBUS_CNET98EL_IO_BASE
1121 hex "C-NET(98)E/L I/O base address (0xaaed or 0x55ed)"
1122 depends on NE2K_CBUS_CNET98EL
1125 config NE2K_CBUS_ATLA98
1126 bool "Allied Telesis LA-98 Support"
1127 depends on NE2K_CBUS
1129 config NE2K_CBUS_BDN
1130 bool "ELECOM Laneed LD-BDN[123]A Support"
1131 depends on NE2K_CBUS
1133 config NE2K_CBUS_NEC108
1134 bool "NEC PC-9801-108 Support"
1135 depends on NE2K_CBUS
1138 tristate "SKnet MCA support"
1139 depends on NET_ETHERNET && MCA && BROKEN
1141 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1142 support" in order to use this driver. Supported cards are the SKnet
1143 Junior MC2 and the SKnet MC2(+). The driver automatically
1144 distinguishes between the two cards. Note that using multiple boards
1145 of different type hasn't been tested with this driver. Say Y if you
1146 have one of these Ethernet adapters.
1148 To compile this driver as a module, choose M here and read
1149 <file:Documentation/networking/net-modules.txt>. The module
1150 will be called sk_mca.
1153 tristate "NE/2 (ne2000 MCA version) support"
1154 depends on NET_ETHERNET && MCA
1157 If you have a network (Ethernet) card of this type, say Y and read
1158 the Ethernet-HOWTO, available from
1159 <http://www.tldp.org/docs.html#howto>.
1161 To compile this driver as a module, choose M here and read
1162 <file:Documentation/networking/net-modules.txt>. The module
1166 tristate "IBM LAN Adapter/A support"
1167 depends on NET_ETHERNET && MCA
1169 This is a Micro Channel Ethernet adapter. You need to set
1170 CONFIG_MCA to use this driver. It is both available as an in-kernel
1171 driver and as a module.
1173 To compile this driver as a module, choose M here and read
1174 <file:Documentation/networking/net-modules.txt>. The only
1175 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1176 will both support 16K and 32K memory windows, however a 32K window
1177 gives a better security against packet losses. Usage of multiple
1178 boards with this driver should be possible, but has not been tested
1179 up to now due to lack of hardware.
1182 bool "EISA, VLB, PCI and on board controllers"
1183 depends on NET_ETHERNET && (ISA || EISA || PCI)
1185 This is another class of network cards which attach directly to the
1186 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1187 available from <http://www.tldp.org/docs.html#howto>.
1189 Note that the answer to this question doesn't directly affect the
1190 kernel: saying N will just cause the configurator to skip all
1191 the questions about this class of network cards. If you say Y, you
1192 will be asked for your specific card in the following questions. If
1193 you are unsure, say Y.
1196 tristate "AMD PCnet32 PCI support"
1197 depends on NET_PCI && PCI
1201 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1202 answer Y here and read the Ethernet-HOWTO, available from
1203 <http://www.tldp.org/docs.html#howto>.
1205 To compile this driver as a module, choose M here and read
1206 <file:Documentation/networking/net-modules.txt>. The module
1207 will be called pcnet32.
1210 tristate "AMD 8111 (new PCI lance) support"
1211 depends on NET_PCI && PCI
1215 If you have an AMD 8111-based PCI lance ethernet card,
1216 answer Y here and read the Ethernet-HOWTO, available from
1217 <http://www.tldp.org/docs.html#howto>.
1219 To compile this driver as a module, choose M here and read
1220 <file:Documentation/networking/net-modules.txt>. The module
1221 will be called amd8111e.
1223 config ADAPTEC_STARFIRE
1224 tristate "Adaptec Starfire/DuraLAN support"
1225 depends on NET_PCI && PCI
1229 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1230 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1231 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1234 To compile this driver as a module, choose M here: the module
1235 will be called starfire. This is recommended.
1237 config ADAPTEC_STARFIRE_NAPI
1238 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1239 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1241 NAPI is a new driver API designed to reduce CPU and interrupt load
1242 when the driver is receiving lots of packets from the card. It is
1243 still somewhat experimental and thus not yet enabled by default.
1245 If your estimated Rx load is 10kpps or more, or if the card will be
1246 deployed on potentially unfriendly networks (e.g. in a firewall),
1250 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1251 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1254 If you have a network (Ethernet) card of this type, say Y and read
1255 the Ethernet-HOWTO, available from
1256 <http://www.tldp.org/docs.html#howto>.
1258 To compile this driver as a module, choose M here and read
1259 <file:Documentation/networking/net-modules.txt>. The module
1260 will be called ac3200.
1263 tristate "Apricot Xen-II on board Ethernet"
1264 depends on NET_PCI && ISA
1266 If you have a network (Ethernet) controller of this type, say Y and
1267 read the Ethernet-HOWTO, available from
1268 <http://www.tldp.org/docs.html#howto>.
1270 To compile this driver as a module, choose M here and read
1271 <file:Documentation/networking/net-modules.txt>. The module will be
1275 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1276 depends on NET_PCI && PCI && EXPERIMENTAL
1278 If you have a network (Ethernet) controller of this type, say Y and
1279 read the Ethernet-HOWTO, available from
1280 <http://www.tldp.org/docs.html#howto>.
1282 To compile this driver as a module, choose M here and read
1283 <file:Documentation/networking/net-modules.txt>. The module will be
1287 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1288 depends on NET_PCI && PCI && EXPERIMENTAL
1290 If you have a network (Ethernet) controller of this type, say Y and
1291 read the Ethernet-HOWTO, available from
1292 <http://www.tldp.org/docs.html#howto>.
1294 To compile this driver as a module, choose M here and read
1295 <file:Documentation/networking/net-modules.txt>. The module will be
1300 tristate "CS89x0 support"
1301 depends on NET_PCI && ISA
1303 Support for CS89x0 chipset based Ethernet cards. If you have a
1304 network (Ethernet) card of this type, say Y and read the
1305 Ethernet-HOWTO, available from
1306 <http://www.tldp.org/docs.html#howto> as well as
1307 <file:Documentation/networking/cs89x0.txt>.
1309 To compile this driver as a module, choose M here and read
1310 <file:Documentation/networking/net-modules.txt>. The module will be
1314 tristate "TOSHIBA TC35815 Ethernet support"
1315 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1318 tristate "Digi Intl. RightSwitch SE-X support"
1319 depends on NET_PCI && (PCI || EISA)
1321 This is support for the Digi International RightSwitch series of
1322 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1323 models. If you have a network card of this type, say Y and read the
1324 Ethernet-HOWTO, available from
1325 <http://www.tldp.org/docs.html#howto>. More specific
1326 information is contained in <file:Documentation/networking/dgrs.txt>.
1328 To compile this driver as a module, choose M here and read
1329 <file:Documentation/networking/net-modules.txt>. The module
1330 will be called dgrs.
1333 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1334 depends on NET_PCI && PCI
1337 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1338 card, say Y and read the Ethernet-HOWTO, available from
1339 <http://www.tldp.org/docs.html#howto>.
1341 To compile this driver as a module, choose M here and read
1342 <file:Documentation/networking/net-modules.txt>. The module
1343 will be called eepro100.
1347 bool "Use PIO instead of MMIO" if !X86_VISWS
1349 default y if X86_VISWS
1351 This instructs the driver to use programmed I/O ports (PIO) instead
1352 of PCI shared memory (MMIO). This can possibly solve some problems
1353 in case your mainboard has memory consistency issues. If unsure,
1357 tristate "EtherExpressPro/100 support (e100, Alternate Intel driver)"
1358 depends on NET_PCI && PCI
1360 This driver supports Intel(R) PRO/100 family of adapters, which
1363 Controller Adapter Name Board IDs
1364 ---------- ------------ ---------
1366 82558 PRO/100+ PCI Adapter 668081-xxx,
1368 82558 PRO/100+ Management Adapter 691334-xxx,
1371 82558 PRO/100+ Dual Port Server Adapter 714303-xxx,
1374 82558 PRO/100+ PCI Server Adapter 710550-xxx
1375 82550 PRO/100 S Server Adapter 752438-xxx
1384 82550 PRO/100 S Desktop Adapter 751767-xxx
1391 82559 PRO/100+ Server Adapter 729757-xxx
1392 82559 PRO/100 S Management Adapter 748566-xxx,
1394 82550 PRO/100 S Dual Port Server Adapter A56831-xxx
1395 82551 PRO/100 M Desktop Adapter A80897-xxx
1396 PRO/100 S Advanced Management Adapter
1399 CNR PRO/100 VE Desktop Adapter A10386-xxx,
1403 PRO/100 VM Desktop Adapter A14323-xxx,
1410 To verify that your adapter is supported, find the board ID number
1411 on the adapter. Look for a label that has a barcode and a number
1412 in the format 123456-001 (six digits hyphen three digits). Match
1413 this to the list of numbers above.
1415 For more information on how to identify your adapter, go to the
1416 Adapter & Driver ID Guide at:
1418 http://support.intel.com/support/network/adapter/pro100/21397.htm
1420 For the latest Intel PRO/100 network driver for Linux, see:
1422 http://appsr.intel.com/scripts-df/support_intel.asp
1424 More specific information on configuring the driver is in
1425 <file:Documentation/networking/e100.txt>.
1427 To compile this driver as a module, choose M here and read
1428 <file:Documentation/networking/net-modules.txt>. The module
1429 will be called e100.
1432 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1433 depends on NET_PCI && EISA && EXPERIMENTAL
1436 If you have a network (Ethernet) card of this type, say Y and read
1437 the Ethernet-HOWTO, available from
1438 <http://www.tldp.org/docs.html#howto>.
1440 To compile this driver as a module, choose M here and read
1441 <file:Documentation/networking/net-modules.txt>. The module
1442 will be called lne390.
1445 tristate "Myson MTD-8xx PCI Ethernet support"
1446 depends on NET_PCI && PCI
1450 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1451 cards. Specifications and data at
1452 <http://www.myson.com.hk/mtd/datasheet/>.
1455 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1456 depends on NET_PCI && PCI
1459 This driver is for the National Semiconductor DP83810 series,
1460 which is used in cards from PureData, NetGear, Linksys
1461 and others, including the 83815 chip.
1462 More specific information and updates are available from
1463 <http://www.scyld.com/network/natsemi.html>.
1466 tristate "PCI NE2000 and clones support (see help)"
1467 depends on NET_PCI && PCI
1470 This driver is for NE2000 compatible PCI cards. It will not work
1471 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1472 support" below). If you have a PCI NE2000 network (Ethernet) card,
1473 say Y and read the Ethernet-HOWTO, available from
1474 <http://www.tldp.org/docs.html#howto>.
1476 This driver also works for the following NE2000 clone cards:
1477 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1478 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1479 Holtek HT80232 Holtek HT80229
1481 To compile this driver as a module, choose M here and read
1482 <file:Documentation/networking/net-modules.txt>. The module
1483 will be called ne2k-pci.
1486 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1487 depends on NET_PCI && EISA && EXPERIMENTAL
1490 If you have a network (Ethernet) card of this type, say Y and read
1491 the Ethernet-HOWTO, available from
1492 <http://www.tldp.org/docs.html#howto>. Note that this driver
1493 will NOT WORK for NE3200 cards as they are completely different.
1495 To compile this driver as a module, choose M here and read
1496 <file:Documentation/networking/net-modules.txt>. The module
1497 will be called ne3210.
1500 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1501 depends on NET_PCI && EISA && EXPERIMENTAL
1504 If you have a network (Ethernet) card of this type, say Y and read
1505 the Ethernet-HOWTO, available from
1506 <http://www.tldp.org/docs.html#howto>.
1508 To compile this driver as a module, choose M here and read
1509 <file:Documentation/networking/net-modules.txt>. The module
1510 will be called es3210.
1513 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1514 depends on NET_PCI && PCI && EXPERIMENTAL
1518 This is a driver for the Fast Ethernet PCI network cards based on
1519 the RTL8139C+ chips. If you have one of those, say Y and read
1520 the Ethernet-HOWTO, available from
1521 <http://www.tldp.org/docs.html#howto>.
1523 To compile this driver as a module, choose M here: the module
1524 will be called 8139cp. This is recommended.
1527 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1528 depends on NET_PCI && PCI
1532 This is a driver for the Fast Ethernet PCI network cards based on
1533 the RTL8139 chips. If you have one of those, say Y and read
1534 <file:Documentation/networking/8139too.txt> as well as the
1535 Ethernet-HOWTO, available from
1536 <http://www.tldp.org/docs.html#howto>.
1538 To compile this driver as a module, choose M here: the module
1539 will be called 8139too. This is recommended.
1542 bool "Use PIO instead of MMIO"
1545 This instructs the driver to use programmed I/O ports (PIO) instead
1546 of PCI shared memory (MMIO). This can possibly solve some problems
1547 in case your mainboard has memory consistency issues. If unsure,
1550 config 8139TOO_TUNE_TWISTER
1551 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1554 This implements a function which might come in handy in case you
1555 are using low quality on long cabling. It is required for RealTek
1556 RTL-8139 revision K boards, and totally unused otherwise. It tries
1557 to match the transceiver to the cable characteristics. This is
1558 experimental since hardly documented by the manufacturer.
1562 bool "Support for older RTL-8129/8130 boards"
1565 This enables support for the older and uncommon RTL-8129 and
1566 RTL-8130 chips, which support MII via an external transceiver,
1567 instead of an internal one. Disabling this option will save some
1568 memory by making the code size smaller. If unsure, say Y.
1570 config 8139_OLD_RX_RESET
1571 bool "Use older RX-reset method"
1574 The 8139too driver was recently updated to contain a more rapid
1575 reset sequence, in the face of severe receive errors. This "new"
1576 RX-reset method should be adequate for all boards. But if you
1577 experience problems, you can enable this option to restore the
1578 old RX-reset behavior. If unsure, say N.
1580 config 8139_RXBUF_IDX
1581 int "Receive ring size (0 => 8K, 1 => 16K, 2 => 32K, 3 => 64K)"
1584 default 1 if EMBEDDED || SH_DREAMCAST
1587 The 8139too driver has a fixed area of memory for receiving data.
1588 The default value is adequate for most systems. The 64KB
1589 ring size has hardware issues that may cause problems.
1592 1 => 16 KB embedded systems
1593 2 => 32 KB default for most systems
1595 If unsure, use the default 2.
1599 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1600 depends on NET_PCI && PCI
1603 This is a driver for the Fast Ethernet PCI network cards based on
1604 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1605 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1606 read the Ethernet-HOWTO, available at
1607 <http://www.tldp.org/docs.html#howto>. Please read
1608 <file:Documentation/networking/sis900.txt> and comments at the
1609 beginning of <file:drivers/net/sis900.c> for more information.
1611 This driver also supports AMD 79C901 HomePNA so that you can use
1612 your phone line as a network cable.
1614 To compile this driver as a module, choose M here: the module
1615 will be called sis900. This is recommended.
1618 tristate "SMC EtherPower II"
1619 depends on NET_PCI && PCI
1623 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1624 which is based on the SMC83c17x (EPIC/100).
1625 More specific information and updates are available from
1626 <http://www.scyld.com/network/epic100.html>.
1629 tristate "Sundance Alta support"
1630 depends on NET_PCI && PCI
1634 This driver is for the Sundance "Alta" chip.
1635 More specific information and updates are available from
1636 <http://www.scyld.com/network/sundance.html>.
1638 config SUNDANCE_MMIO
1639 bool "Use MMIO instead of PIO"
1642 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1643 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1644 is known to solve bugs on certain chips.
1649 tristate "TI ThunderLAN support"
1650 depends on NET_PCI && (PCI || EISA) && !64BIT
1652 If you have a PCI Ethernet network card based on the ThunderLAN chip
1653 which is supported by this driver, say Y and read the
1654 Ethernet-HOWTO, available from
1655 <http://www.tldp.org/docs.html#howto>.
1657 Devices currently supported by this driver are Compaq Netelligent,
1658 Compaq NetFlex and Olicom cards. Please read the file
1659 <file:Documentation/networking/tlan.txt> for more details.
1661 To compile this driver as a module, choose M here and read
1662 <file:Documentation/networking/net-modules.txt>. The module
1663 will be called tlan.
1665 Please email feedback to torben.mathiasen@compaq.com.
1668 tristate "VIA Rhine support"
1669 depends on NET_PCI && PCI
1673 If you have a VIA "rhine" based network card (Rhine-I (3043) or
1674 Rhine-2 (VT86c100A)), say Y here.
1676 To compile this driver as a module, choose M here and read
1677 <file:Documentation/networking/net-modules.txt>. The module
1678 will be called via-rhine.
1680 config VIA_RHINE_MMIO
1681 bool "Use MMIO instead of PIO (EXPERIMENTAL)"
1682 depends on VIA_RHINE && EXPERIMENTAL
1684 This instructs the driver to use PCI shared memory (MMIO) instead of
1685 programmed I/O ports (PIO). Enabling this gives an improvement in
1686 processing time in parts of the driver.
1688 It is not known if this works reliably on all "rhine" based cards,
1689 but it has been tested successfully on some DFE-530TX adapters.
1694 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1695 depends on NET_PCI && EXPERIMENTAL && MIPS
1697 The SAA9730 is a combined multimedia and peripheral controller used
1698 in thin clients, Internet access terminals, and diskless
1700 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1703 bool "Pocket and portable adapters"
1704 depends on NET_ETHERNET && ISA
1706 Cute little network (Ethernet) devices which attach to the parallel
1707 port ("pocket adapters"), commonly used with laptops. If you have
1708 one of those, say Y and read the Ethernet-HOWTO, available from
1709 <http://www.tldp.org/docs.html#howto>.
1711 If you want to plug a network (or some other) card into the PCMCIA
1712 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1713 credit card size extension cards used by all modern laptops), you
1714 need the pcmcia-cs package (location contained in the file
1715 <file:Documentation/Changes>) and you can say N here.
1717 Laptop users should read the Linux Laptop home page at
1718 <http://www.linux-on-laptops.com/>.
1720 Note that the answer to this question doesn't directly affect the
1721 kernel: saying N will just cause the configurator to skip all
1722 the questions about this class of network devices. If you say Y, you
1723 will be asked for your specific device in the following questions.
1726 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1727 depends on NET_POCKET && ISA && X86
1730 This is a network (Ethernet) device which attaches to your parallel
1731 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1732 available from <http://www.tldp.org/docs.html#howto>, if you
1733 want to use this. If you intend to use this driver, you should have
1734 said N to the "Parallel printer support", because the two drivers
1735 don't like each other.
1737 To compile this driver as a module, choose M here: the module
1741 tristate "D-Link DE600 pocket adapter support"
1742 depends on NET_POCKET && ISA
1744 This is a network (Ethernet) device which attaches to your parallel
1745 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1746 Ethernet-HOWTO, available from
1747 <http://www.tldp.org/docs.html#howto>, if you want to use
1748 this. It is possible to have several devices share a single parallel
1749 port and it is safe to compile the corresponding drivers into the
1752 To compile this driver as a module, choose M here: the module
1753 will be called de600.
1756 tristate "D-Link DE620 pocket adapter support"
1757 depends on NET_POCKET && ISA
1759 This is a network (Ethernet) device which attaches to your parallel
1760 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1761 Ethernet-HOWTO, available from
1762 <http://www.tldp.org/docs.html#howto>, if you want to use
1763 this. It is possible to have several devices share a single parallel
1764 port and it is safe to compile the corresponding drivers into the
1767 To compile this driver as a module, choose M here: the module
1768 will be called de620.
1771 tristate "SGI Seeq ethernet controller support"
1772 depends on NET_ETHERNET && SGI_IP22
1774 Say Y here if you have an Seeq based Ethernet network card. This is
1775 used in many Silicon Graphics machines.
1778 tristate "DEC LANCE ethernet controller support"
1779 depends on NET_ETHERNET && DECSTATION
1782 This driver is for the series of Ethernet controllers produced by
1783 DEC (now Compaq) based on the AMD Lance chipset, including the
1784 DEPCA series. (This chipset is better known via the NE2100 cards.)
1787 tristate "Baget AMD LANCE support"
1788 depends on NET_ETHERNET && BAGET_MIPS
1790 Say Y to enable kernel support for AMD Lance Ethernet cards on the
1791 MIPS-32-based Baget embedded system. This chipset is better known
1792 via the NE2100 cards.
1795 bool "Motorola 68360 ethernet controller"
1798 Say Y here if you want to use the built-in ethernet controller of
1799 the Motorola 68360 processor.
1802 bool "FEC ethernet controller (of ColdFire 5272)"
1803 depends on M5272 || M5282
1805 Say Y here if you want to use the built-in 10/100 Fast ethernet
1806 controller on the Motorola ColdFire 5272 processor.
1814 menu "Ethernet (1000 Mbit)"
1815 depends on NETDEVICES
1818 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1821 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1822 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1823 adapter. The driver allows for using the Jumbo Frame option (9000
1824 bytes/frame) however it requires that your switches can handle this
1825 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1828 To compile this driver as a module, choose M here: the
1829 module will be called acenic.
1831 config ACENIC_OMIT_TIGON_I
1832 bool "Omit support for old Tigon I based AceNICs"
1835 Say Y here if you only have Tigon II based AceNICs and want to leave
1836 out support for the older Tigon I based cards which are no longer
1837 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1838 version)). This will reduce the size of the driver object by
1839 app. 100KB. If you are not sure whether your card is a Tigon I or a
1840 Tigon II, say N here.
1842 The safe and default value for this is N.
1845 tristate "D-Link DL2000-based Gigabit Ethernet support"
1849 This driver supports D-Link 2000-based gigabit ethernet cards, which
1851 D-Link DGE-550T Gigabit Ethernet Adapter.
1852 D-Link DL2000-based Gigabit Ethernet Adapter.
1854 To compile this driver as a module, choose M here: the
1855 module will be called dl2k.
1858 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1861 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1862 adapters, which includes:
1864 Controller Adapter Name Board IDs
1865 ---------- ------------ ---------
1866 82542 PRO/1000 Gigabit Server Adapter 700262-xxx,
1868 82543 PRO/1000 F Server Adapter 738640-xxx,
1870 82543 PRO/1000 T Server Adapter A19845-xxx,
1872 82544 PRO/1000 XT Server Adapter A51580-xxx
1873 82544 PRO/1000 XF Server Adapter A50484-xxx
1874 82544 PRO/1000 T Desktop Adapter A62947-xxx
1875 82540 PRO/1000 MT Desktop Adapter A78408-xxx
1876 82541 PRO/1000 MT Desktop Adapter C91016-xxx
1877 82545 PRO/1000 MT Server Adapter A92165-xxx
1878 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx
1879 82545 PRO/1000 MF Server Adapter A91622-xxx
1880 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx
1881 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx
1883 For more information on how to identify your adapter, go to the
1884 Adapter & Driver ID Guide at:
1886 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1888 For general information and support, go to the Intel support
1891 <http://support.intel.com>
1893 More specific information on configuring the driver is in
1894 <file:Documentation/networking/e1000.txt>.
1896 To compile this driver as a module, choose M here and read
1897 <file:Documentation/networking/net-modules.txt>. The module
1898 will be called e1000.
1901 bool "Use Rx Polling (NAPI)"
1905 tristate "MyriCOM Gigabit Ethernet support"
1908 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1910 To compile this driver as a module, choose M here: the module
1911 will be called myri_sbus. This is recommended.
1914 tristate "National Semiconduct DP83820 support"
1917 This is a driver for the National Semiconductor DP83820 series
1918 of gigabit ethernet MACs. Cards using this chipset include
1919 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1920 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1924 tristate "Packet Engines Hamachi GNIC-II support"
1928 If you have a Gigabit Ethernet card of this type, say Y and read
1929 the Ethernet-HOWTO, available from
1930 <http://www.tldp.org/docs.html#howto>.
1932 To compile this driver as a module, choose M here and read
1933 <file:Documentation/networking/net-modules.txt>. The module will be
1937 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1938 depends on PCI && EXPERIMENTAL
1941 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1942 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1943 used by the Beowulf Linux cluster project. See
1944 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1945 information about this driver in particular and Beowulf in general.
1947 To compile this driver as a module, choose M here: the module
1948 will be called yellowfin. This is recommended.
1951 tristate "Realtek 8169 gigabit ethernet support"
1955 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1957 To compile this driver as a module, choose M here: the module
1958 will be called r8169. This is recommended.
1961 tristate "SiS190 gigabit ethernet support (EXPERIMENTAL)"
1962 depends on PCI && EXPERIMENTAL
1965 Say Y here if you have a SiS 190 PCI Gigabit Ethernet adapter.
1967 To compile this driver as a module, choose M here: the module
1968 will be called sis190. This is recommended.
1971 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
1974 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1975 compliant Gigabit Ethernet Adapter. The following adapters are supported
1977 - 3Com 3C940 Gigabit LOM Ethernet Adapter
1978 - 3Com 3C941 Gigabit LOM Ethernet Adapter
1979 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
1980 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
1981 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
1982 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
1983 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
1984 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
1985 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
1986 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
1987 - DGE-530T Gigabit Ethernet Adapter
1988 - EG1032 v2 Instant Gigabit Network Adapter
1989 - EG1064 v2 Instant Gigabit Network Adapter
1990 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
1991 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
1992 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
1993 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
1994 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
1995 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
1996 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
1997 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
1998 - Marvell RDK-8001 Adapter
1999 - Marvell RDK-8002 Adapter
2000 - Marvell RDK-8003 Adapter
2001 - Marvell RDK-8004 Adapter
2002 - Marvell RDK-8006 Adapter
2003 - Marvell RDK-8007 Adapter
2004 - Marvell RDK-8008 Adapter
2005 - Marvell RDK-8009 Adapter
2006 - Marvell RDK-8010 Adapter
2007 - Marvell RDK-8011 Adapter
2008 - Marvell RDK-8012 Adapter
2009 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2010 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2011 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2012 - SK-9521 10/100/1000Base-T Adapter
2013 - SK-9521 V2.0 10/100/1000Base-T Adapter
2014 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2015 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2016 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2017 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2018 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2019 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2020 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2021 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2022 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2023 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2024 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2025 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2026 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2027 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2028 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2029 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2030 - SMC EZ Card 1000 (SMC9452TXV.2)
2032 The adapters support Jumbo Frames.
2033 The dual link adapters support link-failover and dual port features.
2034 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2035 the scatter-gather functionality with sendfile(). Please refer to
2036 Documentation/networking/sk98lin.txt for more information about
2037 optional driver parameters.
2038 Questions concerning this driver may be addressed to:
2041 If you want to compile this driver as a module ( = code which can be
2042 inserted in and removed from the running kernel whenever you want),
2043 say M here and read Documentation/modules.txt. This is recommended.
2044 The module will be called sk98lin. This is recommended.
2047 tristate "Broadcom Tigon3 support"
2050 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2052 To compile this driver as a module, choose M here: the module
2053 will be called tg3. This is recommended.
2058 # 10 Gigabit Ethernet
2061 menu "Ethernet (10000 Mbit)"
2062 depends on NETDEVICES
2065 tristate "Intel(R) PRO/10GbE support"
2068 This driver supports Intel(R) PRO/10GbE family of
2069 adapters, which includes:
2071 Controller Adapter Name Board IDs
2072 ---------- ------------ ---------
2073 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx
2075 For more information on how to identify your adapter, go to the
2076 Adapter & Driver ID Guide at:
2078 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2080 For general information and support, go to the Intel support
2083 <http://support.intel.com>
2085 More specific information on configuring the driver is in
2086 <file:Documentation/networking/ixgb.txt>.
2088 To compile this driver as a module, choose M here and read
2089 <file:Documentation/networking/net-modules.txt>. The module
2090 will be called ixgb.
2093 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2094 depends on IXGB && EXPERIMENTAL
2100 tristate "iSeries Virtual Ethernet driver support"
2101 depends on NETDEVICES && PPC_ISERIES
2104 tristate "IBM LAN Virtual Ethernet support"
2105 depends on NET_ETHERNET && PPC_PSERIES
2107 This is the Virtual Ethernet adapter driver.
2109 To compile this driver as a module, choose M here and read
2110 <file:Documentation/networking/net-modules.txt>.
2113 bool "FDDI driver support"
2114 depends on NETDEVICES && (PCI || EISA)
2116 Fiber Distributed Data Interface is a high speed local area network
2117 design; essentially a replacement for high speed Ethernet. FDDI can
2118 run over copper or fiber. If you are connected to such a network and
2119 want a driver for the FDDI card in your computer, say Y here (and
2120 then also Y to the driver for your FDDI card, below). Most people
2124 tristate "Digital DEFEA and DEFPA adapter support"
2125 depends on FDDI && (PCI || EISA)
2127 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2128 (DEFPA) controllers which can connect you to a local FDDI network.
2131 tristate "SysKonnect FDDI PCI support"
2132 depends on FDDI && PCI
2134 Say Y here if you have a SysKonnect FDDI PCI adapter.
2135 The following adapters are supported by this driver:
2136 - SK-5521 (SK-NET FDDI-UP)
2137 - SK-5522 (SK-NET FDDI-UP DAS)
2138 - SK-5541 (SK-NET FDDI-FP)
2139 - SK-5543 (SK-NET FDDI-LP)
2140 - SK-5544 (SK-NET FDDI-LP DAS)
2141 - SK-5821 (SK-NET FDDI-UP64)
2142 - SK-5822 (SK-NET FDDI-UP64 DAS)
2143 - SK-5841 (SK-NET FDDI-FP64)
2144 - SK-5843 (SK-NET FDDI-LP64)
2145 - SK-5844 (SK-NET FDDI-LP64 DAS)
2146 - Netelligent 100 FDDI DAS Fibre SC
2147 - Netelligent 100 FDDI SAS Fibre SC
2148 - Netelligent 100 FDDI DAS UTP
2149 - Netelligent 100 FDDI SAS UTP
2150 - Netelligent 100 FDDI SAS Fibre MIC
2152 Read <file:Documentation/networking/skfp.txt> for information about
2155 Questions concerning this driver can be addressed to:
2158 To compile this driver as a module, choose M here: the module
2159 will be called skfp. This is recommended.
2162 bool "HIPPI driver support (EXPERIMENTAL)"
2163 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2165 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2166 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2167 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2168 single-mode). HIPPI networks are commonly used for clusters and to
2169 connect to super computers. If you are connected to a HIPPI network
2170 and have a HIPPI network card in your computer that you want to use
2171 under Linux, say Y here (you must also remember to enable the driver
2172 for your HIPPI card below). Most people will say N here.
2175 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2176 depends on HIPPI && PCI
2178 Say Y here if this is your PCI HIPPI network card.
2180 To compile this driver as a module, choose M here: the module
2181 will be called rrunner. If unsure, say N.
2183 config ROADRUNNER_LARGE_RINGS
2184 bool "Use large TX/RX rings (EXPERIMENTAL)"
2185 depends on ROADRUNNER
2187 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2188 of additional memory to allow for fastest operation, both for
2189 transmitting and receiving. This memory cannot be used by any other
2190 kernel code or by user space programs. Say Y here only if you have
2194 tristate "PLIP (parallel port) support"
2195 depends on NETDEVICES && PARPORT
2197 PLIP (Parallel Line Internet Protocol) is used to create a
2198 reasonably fast mini network consisting of two (or, rarely, more)
2199 local machines. A PLIP link from a Linux box is a popular means to
2200 install a Linux distribution on a machine which doesn't have a
2201 CD-ROM drive (a minimal system has to be transferred with floppies
2202 first). The kernels on both machines need to have this PLIP option
2203 enabled for this to work.
2205 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2206 ports (the connectors at the computers with 25 holes) are connected
2207 with "null printer" or "Turbo Laplink" cables which can transmit 4
2208 bits at a time (mode 0) or with special PLIP cables, to be used on
2209 bidirectional parallel ports only, which can transmit 8 bits at a
2210 time (mode 1); you can find the wiring of these cables in
2211 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2212 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2213 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2214 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2215 and winsock or NCSA's telnet.
2217 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2218 as the NET-3-HOWTO, both available from
2219 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2220 protocol has been changed and this PLIP driver won't work together
2221 with the PLIP support in Linux versions 1.0.x. This option enlarges
2222 your kernel by about 8 KB.
2224 To compile this driver as a module, choose M here and read
2225 <file:Documentation/networking/net-modules.txt>. The module will be
2226 called plip. If unsure, say Y or M, in case you buy a laptop
2230 tristate "PPP (point-to-point protocol) support"
2231 depends on NETDEVICES
2233 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2234 the same purpose: sending Internet traffic over telephone (and other
2235 serial) lines. Ask your access provider if they support it, because
2236 otherwise you can't use it; most Internet access providers these
2237 days support PPP rather than SLIP.
2239 To use PPP, you need an additional program called pppd as described
2240 in the PPP-HOWTO, available at
2241 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2242 the version of pppd recommended in <file:Documentation/Changes>.
2243 The PPP option enlarges your kernel by about 16 KB.
2245 There are actually two versions of PPP: the traditional PPP for
2246 asynchronous lines, such as regular analog phone lines, and
2247 synchronous PPP which can be used over digital ISDN lines for
2248 example. If you want to use PPP over phone lines or other
2249 asynchronous serial lines, you need to say Y (or M) here and also to
2250 the next option, "PPP support for async serial ports". For PPP over
2251 synchronous lines, you should say Y (or M) here and to "Support
2252 synchronous PPP", below.
2254 If you said Y to "Version information on all symbols" above, then
2255 you cannot compile the PPP driver into the kernel; you can then only
2256 compile it as a module. To compile this driver as a module, choose M
2257 here and read <file:Documentation/networking/net-modules.txt>.
2258 The module will be called ppp_generic.
2260 config PPP_MULTILINK
2261 bool "PPP multilink support (EXPERIMENTAL)"
2262 depends on PPP && EXPERIMENTAL
2264 PPP multilink is a protocol (defined in RFC 1990) which allows you
2265 to combine several (logical or physical) lines into one logical PPP
2266 connection, so that you can utilize your full bandwidth.
2268 This has to be supported at the other end as well and you need a
2269 version of the pppd daemon which understands the multilink protocol.
2274 bool "PPP filtering"
2277 Say Y here if you want to be able to filter the packets passing over
2278 PPP interfaces. This allows you to control which packets count as
2279 activity (i.e. which packets will reset the idle timer or bring up
2280 a demand-dialled link) and which packets are to be dropped entirely.
2281 You need to say Y here if you wish to use the pass-filter and
2282 active-filter options to pppd.
2287 tristate "PPP support for async serial ports"
2290 Say Y (or M) here if you want to be able to use PPP over standard
2291 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2292 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2295 To compile this driver as a module, choose M here.
2300 tristate "PPP support for sync tty ports"
2303 Say Y (or M) here if you want to be able to use PPP over synchronous
2304 (HDLC) tty devices, such as the SyncLink adapter. These devices
2305 are often used for high-speed leased lines like T1/E1.
2307 To compile this driver as a module, choose M here.
2310 tristate "PPP Deflate compression"
2315 Support for the Deflate compression method for PPP, which uses the
2316 Deflate algorithm (the same algorithm that gzip uses) to compress
2317 each PPP packet before it is sent over the wire. The machine at the
2318 other end of the PPP link (usually your ISP) has to support the
2319 Deflate compression method as well for this to be useful. Even if
2320 they don't support it, it is safe to say Y here.
2322 To compile this driver as a module, choose M here.
2325 tristate "PPP BSD-Compress compression"
2328 Support for the BSD-Compress compression method for PPP, which uses
2329 the LZW compression method to compress each PPP packet before it is
2330 sent over the wire. The machine at the other end of the PPP link
2331 (usually your ISP) has to support the BSD-Compress compression
2332 method as well for this to be useful. Even if they don't support it,
2333 it is safe to say Y here.
2335 The PPP Deflate compression method ("PPP Deflate compression",
2336 above) is preferable to BSD-Compress, because it compresses better
2339 Note that the BSD compression code will always be compiled as a
2340 module; it is called bsd_comp and will show up in the directory
2341 modules once you have said "make modules". If unsure, say N.
2344 tristate "PPP over Ethernet (EXPERIMENTAL)"
2345 depends on EXPERIMENTAL && PPP
2347 Support for PPP over Ethernet.
2349 This driver requires the latest version of pppd from the CVS
2350 repository at cvs.samba.org. Alternatively, see the
2351 RoaringPenguin package (http://www.roaringpenguin.com/pppoe)
2352 which contains instruction on how to use this driver (under
2353 the heading "Kernel mode PPPoE").
2356 tristate "PPP over ATM"
2357 depends on ATM && PPP
2359 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2360 This implementation does not yet comply with section 8 of RFC2364,
2361 which can lead to bad results if the ATM peer loses state and
2362 changes its encapsulation unilaterally.
2365 tristate "SLIP (serial line) support"
2366 depends on NETDEVICES
2368 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2369 connect to your Internet service provider or to connect to some
2370 other local Unix box or if you want to configure your Linux box as a
2371 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2372 Internet Protocol) is a protocol used to send Internet traffic over
2373 serial connections such as telephone lines or null modem cables;
2374 nowadays, the protocol PPP is more commonly used for this same
2377 Normally, your access provider has to support SLIP in order for you
2378 to be able to use it, but there is now a SLIP emulator called SLiRP
2379 around (available from
2380 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2381 allows you to use SLIP over a regular dial up shell connection. If
2382 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2383 NET-3-HOWTO, available from
2384 <http://www.tldp.org/docs.html#howto>, explains how to
2385 configure SLIP. Note that you don't need this option if you just
2386 want to run term (term is a program which gives you almost full
2387 Internet connectivity if you have a regular dial up shell account on
2388 some Internet connected Unix computer. Read
2389 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2390 support will enlarge your kernel by about 4 KB. If unsure, say N.
2392 To compile this driver as a module, choose M here and read
2393 <file:Documentation/networking/net-modules.txt>. The module will be
2396 config SLIP_COMPRESSED
2397 bool "CSLIP compressed headers"
2400 This protocol is faster than SLIP because it uses compression on the
2401 TCP/IP headers (not on the data itself), but it has to be supported
2402 on both ends. Ask your access provider if you are not sure and
2403 answer Y, just in case. You will still be able to use plain SLIP. If
2404 you plan to use SLiRP, the SLIP emulator (available from
2405 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2406 allows you to use SLIP over a regular dial up shell connection, you
2407 definitely want to say Y here. The NET-3-HOWTO, available from
2408 <http://www.tldp.org/docs.html#howto>, explains how to configure
2409 CSLIP. This won't enlarge your kernel.
2412 bool "Keepalive and linefill"
2415 Adds additional capabilities to the SLIP driver to support the
2416 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2419 config SLIP_MODE_SLIP6
2420 bool "Six bit SLIP encapsulation"
2423 Just occasionally you may need to run IP over hostile serial
2424 networks that don't pass all control characters or are only seven
2425 bit. Saying Y here adds an extra mode you can use with SLIP:
2426 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2427 the serial device. Naturally, this has to be supported at the other
2428 end of the link as well. It's good enough, for example, to run IP
2429 over the async ports of a Camtec JNT Pad. If unsure, say N.
2431 source "drivers/net/wireless/Kconfig"
2433 source "drivers/net/tokenring/Kconfig"
2436 bool "Fibre Channel driver support"
2437 depends on NETDEVICES && SCSI && PCI
2439 Fibre Channel is a high speed serial protocol mainly used to connect
2440 large storage devices to the computer; it is compatible with and
2441 intended to replace SCSI.
2443 If you intend to use Fibre Channel, you need to have a Fibre channel
2444 adaptor card in your computer; say Y here and to the driver for your
2445 adaptor below. You also should have said Y to "SCSI support" and
2446 "SCSI generic support".
2449 tristate "Interphase 5526 Tachyon chipset based adapter support"
2450 depends on NET_FC && SCSI && PCI && BROKEN
2452 Say Y here if you have a Fibre Channel adaptor of this kind.
2454 To compile this driver as a module, choose M here: the module
2455 will be called iph5526.
2458 tristate "Red Creek Hardware VPN (EXPERIMENTAL)"
2459 depends on NETDEVICES && EXPERIMENTAL && PCI && !64BIT
2461 This is a driver for hardware which provides a Virtual Private
2462 Network (VPN). Say Y if you have it.
2464 To compile this driver as a module, choose M here: the module
2465 will be called rcpci.
2468 tristate "Traffic Shaper (EXPERIMENTAL)"
2469 depends on NETDEVICES && EXPERIMENTAL
2471 The traffic shaper is a virtual network device that allows you to
2472 limit the rate of outgoing data flow over some other network device.
2473 The traffic that you want to slow down can then be routed through
2474 these virtual devices. See
2475 <file:Documentation/networking/shaper.txt> for more information.
2477 An alternative to this traffic shaper is the experimental
2478 Class-Based Queueing (CBQ) scheduling support which you get if you
2479 say Y to "QoS and/or fair queueing" above.
2481 To set up and configure shaper devices, you need the shapecfg
2482 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2485 To compile this driver as a module, choose M here: the module
2486 will be called shaper. If unsure, say N.
2488 source "drivers/net/wan/Kconfig"
2490 source "drivers/net/pcmcia/Kconfig"
2492 source "drivers/atm/Kconfig"
2494 source "drivers/s390/net/Kconfig"