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 tristate "Dummy net driver support"
28 This is essentially a bit-bucket device (i.e. traffic you send to
29 this device is consigned into oblivion) with a configurable IP
30 address. It is most commonly used in order to make your currently
31 inactive SLIP address seem like a real address for local programs.
32 If you use SLIP or PPP, you might want to say Y here. Since this
33 thing often comes in handy, the default is Y. It won't enlarge your
34 kernel either. What a deal. Read about it in the Network
35 Administrator's Guide, available from
36 <http://www.tldp.org/docs.html#guide>.
38 To compile this driver as a module, choose M here: the module
39 will be called dummy. If you want to use more than one dummy
40 device at a time, you need to compile this driver as a module.
41 Instead of 'dummy', the devices will then be called 'dummy0',
45 tristate "Bonding driver support"
48 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
49 Channels together. This is called 'Etherchannel' by Cisco,
50 'Trunking' by Sun, and 'Bonding' in Linux.
52 If you have two Ethernet connections to some other computer, you can
53 make them behave like one double speed connection using this driver.
54 Naturally, this has to be supported at the other end as well, either
55 with a similar Bonding Linux driver, a Cisco 5500 switch or a
56 SunTrunking SunSoft driver.
58 This is similar to the EQL driver, but it merges Ethernet segments
59 instead of serial lines.
61 To compile this driver as a module, choose M here: the module
62 will be called bonding.
65 tristate "EQL (serial line load balancing) support"
68 If you have two serial connections to some other computer (this
69 usually requires two modems and two telephone lines) and you use
70 SLIP (the protocol for sending Internet traffic over telephone
71 lines) or PPP (a better SLIP) on them, you can make them behave like
72 one double speed connection using this driver. Naturally, this has
73 to be supported at the other end as well, either with a similar EQL
74 Linux driver or with a Livingston Portmaster 2e.
76 Say Y if you want this and read
77 <file:Documentation/networking/eql.txt>. You may also want to read
78 section 6.2 of the NET-3-HOWTO, available from
79 <http://www.tldp.org/docs.html#howto>.
81 To compile this driver as a module, choose M here: the module
82 will be called eql. If unsure, say N.
85 tristate "Universal TUN/TAP device driver support"
88 TUN/TAP provides packet reception and transmission for user space
89 programs. It can be viewed as a simple Point-to-Point or Ethernet
90 device, which instead of receiving packets from a physical media,
91 receives them from user space program and instead of sending packets
92 via physical media writes them to the user space program.
94 When a program opens /dev/net/tun, driver creates and registers
95 corresponding net device tunX or tapX. After a program closed above
96 devices, driver will automatically delete tunXX or tapXX device and
97 all routes corresponding to it.
99 Please read <file:Documentation/networking/tuntap.txt> for more
102 To compile this driver as a module, choose M here: the module
105 If you don't know what to use this for, you don't need it.
108 tristate "Ethertap network tap"
109 depends on NETDEVICES && EXPERIMENTAL && NETLINK_DEV
111 If you say Y here (and have said Y to "Kernel/User network link
112 driver", above) and create a character special file /dev/tap0 with
113 major number 36 and minor number 16 using mknod ("man mknod"), you
114 will be able to have a user space program read and write raw
115 Ethernet frames from/to that special file. tap0 can be configured
116 with ifconfig and route like any other Ethernet device but it is not
117 connected to any physical LAN; everything written by the user to
118 /dev/tap0 is treated by the kernel as if it had come in from a LAN
119 to the device tap0; everything the kernel wants to send out over the
120 device tap0 can instead be read by the user from /dev/tap0: the user
121 mode program replaces the LAN that would be attached to an ordinary
122 Ethernet device. Please read the file
123 <file:Documentation/networking/ethertap.txt> for more information.
125 To compile this driver as a module, choose M here: the module
126 will be called ethertap.
128 If you don't know what to use this for, you don't need it.
131 tristate "General Instruments Surfboard 1000"
132 depends on NETDEVICES && PNP
134 This is a driver for the General Instrument (also known as
135 NextLevel) SURFboard 1000 internal
136 cable modem. This is an ISA card which is used by a number of cable
137 TV companies to provide cable modem access. It's a one-way
138 downstream-only cable modem, meaning that your upstream net link is
139 provided by your regular phone modem.
141 At present this driver only compiles as a module, so say M here if
142 you have this card. The module will be called sb1000. Then read
143 <file:Documentation/networking/README.sb1000> for information on how
144 to use this module, as it needs special ppp scripts for establishing
145 a connection. Further documentation and the necessary scripts can be
148 <http://www.jacksonville.net/~fventuri/>
149 <http://home.adelphia.net/~siglercm/sb1000.html>
150 <http://linuxpower.cx/~cable/>
152 If you don't have this card, of course say N.
155 source "drivers/net/arcnet/Kconfig"
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
476 If you have a network (Ethernet) card of this type, say Y and read
477 the Ethernet-HOWTO, available from
478 <http://www.tldp.org/docs.html#howto>.
480 config SGI_IOC3_ETH_HW_RX_CSUM
481 bool "Receive hardware checksums"
482 depends on SGI_IOC3_ETH && INET
485 The SGI IOC3 network adapter supports TCP and UDP checksums in
486 hardware to offload processing of these checksums from the CPU. At
487 the moment only acceleration of IPv4 is supported. This option
488 enables offloading for checksums on receive. If unsure, say Y.
490 config SGI_IOC3_ETH_HW_TX_CSUM
491 bool "Transmit hardware checksums"
492 depends on SGI_IOC3_ETH && INET
495 The SGI IOC3 network adapter supports TCP and UDP checksums in
496 hardware to offload processing of these checksums from the CPU. At
497 the moment only acceleration of IPv4 is supported. This option
498 enables offloading for checksums on transmit. If unsure, say Y.
500 config SGI_O2MACE_ETH
501 tristate "SGI O2 MACE Fast Ethernet support"
502 depends on NET_ETHERNET && SGI_IP32=y
505 tristate "National DP83902AV support"
506 depends on NET_ETHERNET && SUPERH
509 Support for cards based on the National Semiconductor DP83902AV
510 ST-NIC Serial Network Interface Controller for Twisted Pair. This
511 is a 10Mbit/sec Ethernet controller. Product overview and specs at
512 <http://www.national.com/pf/DP/DP83902A.html>.
517 tristate "Sun LANCE support"
518 depends on NET_ETHERNET && SBUS
521 This driver supports the "le" interface present on all 32-bit Sparc
522 systems, on some older Ultra systems and as an Sbus option. These
523 cards are based on the AMD Lance chipset, which is better known
524 via the NE2100 cards.
526 To compile this driver as a module, choose M here: the module
527 will be called sunlance.
530 tristate "Sun Happy Meal 10/100baseT support"
531 depends on NET_ETHERNET && (SBUS || PCI)
534 This driver supports the "hme" interface present on most Ultra
535 systems and as an option on older Sbus systems. This driver supports
536 both PCI and Sbus devices. This driver also supports the "qfe" quad
537 100baseT device available in both PCI and Sbus configurations.
539 To compile this driver as a module, choose M here: the module
540 will be called sunhme.
543 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
544 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
547 This driver supports the "be" interface available as an Sbus option.
548 This is Sun's older 100baseT Ethernet device.
550 To compile this driver as a module, choose M here: the module
551 will be called sunbmac.
554 tristate "Sun QuadEthernet support"
555 depends on NET_ETHERNET && SBUS
558 This driver supports the "qe" 10baseT Ethernet device, available as
559 an Sbus option. Note that this is not the same as Quad FastEthernet
560 "qfe" which is supported by the Happy Meal driver instead.
562 To compile this driver as a module, choose M here: the module
563 will be called sunqe.
566 tristate "Sun GEM support"
567 depends on NET_ETHERNET && PCI
570 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
571 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
573 config NET_VENDOR_3COM
575 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
577 If you have a network (Ethernet) card belonging to this class, say Y
578 and read the Ethernet-HOWTO, available from
579 <http://www.tldp.org/docs.html#howto>.
581 Note that the answer to this question doesn't directly affect the
582 kernel: saying N will just cause the configurator to skip all
583 the questions about 3COM cards. If you say Y, you will be asked for
584 your specific card in the following questions.
587 tristate "3c501 \"EtherLink\" support"
588 depends on NET_VENDOR_3COM && ISA
590 If you have a network (Ethernet) card of this type, say Y and read
591 the Ethernet-HOWTO, available from
592 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
593 new card, since the 3c501 is slow, broken, and obsolete: you will
594 have problems. Some people suggest to ping ("man ping") a nearby
595 machine every minute ("man cron") when using this card.
597 To compile this driver as a module, choose M here and read
598 <file:Documentation/networking/net-modules.txt>. The module
599 will be called 3c501.
602 tristate "3c503 \"EtherLink II\" support"
603 depends on NET_VENDOR_3COM && ISA
606 If you have a network (Ethernet) card of this type, say Y and read
607 the Ethernet-HOWTO, available from
608 <http://www.tldp.org/docs.html#howto>.
610 To compile this driver as a module, choose M here and read
611 <file:Documentation/networking/net-modules.txt>. The module
612 will be called 3c503.
615 tristate "3c505 \"EtherLink Plus\" support"
616 depends on NET_VENDOR_3COM && ISA
618 Information about this network (Ethernet) card can be found in
619 <file:Documentation/networking/3c505.txt>. If you have a card of
620 this type, say Y and read the Ethernet-HOWTO, available from
621 <http://www.tldp.org/docs.html#howto>.
623 To compile this driver as a module, choose M here and read
624 <file:Documentation/networking/net-modules.txt>. The module
625 will be called 3c505.
628 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
629 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
631 If you have a network (Ethernet) card of this type, say Y and read
632 the Ethernet-HOWTO, available from
633 <http://www.tldp.org/docs.html#howto>.
635 To compile this driver as a module, choose M here and read
636 <file:Documentation/networking/net-modules.txt>. The module
637 will be called 3c507.
640 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support"
641 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
643 If you have a network (Ethernet) card belonging to the 3Com
644 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
645 from <http://www.tldp.org/docs.html#howto>.
647 If your card is not working you may need to use the DOS
648 setup disk to disable Plug & Play mode, and to select the default
651 To compile this driver as a module, choose M here and read
652 <file:Documentation/networking/net-modules.txt>. The module
653 will be called 3c509.
656 tristate "3c515 ISA \"Fast EtherLink\""
657 depends on NET_VENDOR_3COM && (ISA || EISA)
659 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
660 network card, say Y and read the Ethernet-HOWTO, available from
661 <http://www.tldp.org/docs.html#howto>.
663 To compile this driver as a module, choose M here and read
664 <file:Documentation/networking/net-modules.txt>. The module
665 will be called 3c515.
668 tristate "3c523 \"EtherLink/MC\" support"
669 depends on NET_VENDOR_3COM && MCA
671 If you have a network (Ethernet) card of this type, say Y and read
672 the Ethernet-HOWTO, available from
673 <http://www.tldp.org/docs.html#howto>.
675 To compile this driver as a module, choose M here and read
676 <file:Documentation/networking/net-modules.txt>. The module
677 will be called 3c523.
680 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
681 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
683 If you have a network (Ethernet) card of this type, say Y and read
684 the Ethernet-HOWTO, available from
685 <http://www.tldp.org/docs.html#howto>.
687 To compile this driver as a module, choose M here and read
688 <file:Documentation/networking/net-modules.txt>. The module
689 will be called 3c527.
692 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
693 depends on NET_VENDOR_3COM && (PCI || EISA)
695 This option enables driver support for a large number of 10mbps and
696 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
698 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
699 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
700 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
701 "Tornado" (3c905) PCI
702 "Hurricane" (3c555/3cSOHO) PCI
704 If you have such a card, say Y and read the Ethernet-HOWTO,
705 available from <http://www.tldp.org/docs.html#howto>. More
706 specific information is in
707 <file:Documentation/networking/vortex.txt> and in the comments at
708 the beginning of <file:drivers/net/3c59x.c>.
710 To compile this support as a module, choose M here and read
711 <file:Documentation/networking/net-modules.txt>.
714 tristate "3cr990 series \"Typhoon\" support"
715 depends on NET_VENDOR_3COM && PCI
718 This option enables driver support for the 3cr990 series of cards:
720 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
721 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
722 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
724 If you have a network (Ethernet) card of this type, say Y and read
725 the Ethernet-HOWTO, available from
726 <http://www.tldp.org/docs.html#howto>.
728 To compile this driver as a module, choose M here and read
729 <file:Documentation/networking/net-modules.txt>. The module
730 will be called typhoon.
733 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
734 depends on NET_ETHERNET && ISA
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>. Some LinkSys cards are
741 To compile this driver as a module, choose M here: the module
742 will be called lance. This is recommended.
744 config NET_VENDOR_SMC
745 bool "Western Digital/SMC cards"
746 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
748 If you have a network (Ethernet) card belonging to this class, say Y
749 and read the Ethernet-HOWTO, available from
750 <http://www.tldp.org/docs.html#howto>.
752 Note that the answer to this question doesn't directly affect the
753 kernel: saying N will just cause the configurator to skip all
754 the questions about Western Digital cards. If you say Y, you will be
755 asked for your specific card in the following questions.
758 tristate "WD80*3 support"
759 depends on NET_VENDOR_SMC && ISA
762 If you have a network (Ethernet) card of this type, say Y and read
763 the Ethernet-HOWTO, available from
764 <http://www.tldp.org/docs.html#howto>.
766 To compile this driver as a module, choose M here and read
767 <file:Documentation/networking/net-modules.txt>. The module
771 tristate "SMC Ultra MCA support"
772 depends on NET_VENDOR_SMC && MCA
775 If you have a network (Ethernet) card of this type and are running
776 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
777 available from <http://www.tldp.org/docs.html#howto>.
779 To compile this driver as a module, choose M here and read
780 <file:Documentation/networking/net-modules.txt>. The module
781 will be called smc-mca.
784 tristate "SMC Ultra support"
785 depends on NET_VENDOR_SMC && ISA
788 If you have a network (Ethernet) card of this type, say Y and read
789 the Ethernet-HOWTO, available from
790 <http://www.tldp.org/docs.html#howto>.
792 Important: There have been many reports that, with some motherboards
793 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
794 such as some BusLogic models) causes corruption problems with many
795 operating systems. The Linux smc-ultra driver has a work-around for
796 this but keep it in mind if you have such a SCSI card and have
799 To compile this driver as a module, choose M here and read
800 <file:Documentation/networking/net-modules.txt>. The module
801 will be called smc-ultra.
804 tristate "SMC Ultra32 EISA support"
805 depends on NET_VENDOR_SMC && EISA
808 If you have a network (Ethernet) card of this type, say Y and read
809 the Ethernet-HOWTO, available from
810 <http://www.tldp.org/docs.html#howto>.
812 To compile this driver as a module, choose M here and read
813 <file:Documentation/networking/net-modules.txt>. The module
814 will be called smc-ultra32.
817 tristate "SMC 9194 support"
818 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
821 This is support for the SMC9xxx based Ethernet cards. Choose this
822 option if you have a DELL laptop with the docking station, or
823 another SMC9192/9194 based chipset. Say Y if you want it compiled
824 into the kernel, and read the file
825 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
826 available from <http://www.tldp.org/docs.html#howto>.
828 To compile this driver as a module, choose M here and read
829 <file:Documentation/networking/net-modules.txt>. The module
830 will be called smc9194.
832 config NET_VENDOR_RACAL
833 bool "Racal-Interlan (Micom) NI cards"
834 depends on NET_ETHERNET && ISA
836 If you have a network (Ethernet) card belonging to this class, such
837 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
838 available from <http://www.tldp.org/docs.html#howto>.
840 Note that the answer to this question doesn't directly affect the
841 kernel: saying N will just cause the configurator to skip all
842 the questions about NI cards. If you say Y, you will be asked for
843 your specific card in the following questions.
846 tristate "NI5010 support (EXPERIMENTAL)"
847 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
849 If you have a network (Ethernet) card of this type, say Y and read
850 the Ethernet-HOWTO, available from
851 <http://www.tldp.org/docs.html#howto>. Note that this is still
854 To compile this driver as a module, choose M here and read
855 <file:Documentation/networking/net-modules.txt>. The module
856 will be called ni5010.
859 tristate "NI5210 support"
860 depends on NET_VENDOR_RACAL && ISA
862 If you have a network (Ethernet) card of this type, say Y and read
863 the Ethernet-HOWTO, available from
864 <http://www.tldp.org/docs.html#howto>.
866 To compile this driver as a module, choose M here and read
867 <file:Documentation/networking/net-modules.txt>. The module
871 tristate "NI6510 support"
872 depends on NET_VENDOR_RACAL && ISA
874 If you have a network (Ethernet) card of this type, say Y and read
875 the Ethernet-HOWTO, available from
876 <http://www.tldp.org/docs.html#howto>.
878 To compile this driver as a module, choose M here and read
879 <file:Documentation/networking/net-modules.txt>. The module
882 source "drivers/net/tulip/Kconfig"
885 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)"
886 depends on NET_ETHERNET && (ISA || MCA) && EXPERIMENTAL
889 If you have a network (Ethernet) card of this type, say Y and read
890 the Ethernet-HOWTO, available from
891 <http://www.tldp.org/docs.html#howto>.
893 To compile this driver as a module, choose M here and read
894 <file:Documentation/networking/net-modules.txt>. The module
895 will be called at1700.
898 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
899 depends on NET_ETHERNET && (ISA || EISA || MCA)
902 If you have a network (Ethernet) card of this type, say Y and read
903 the Ethernet-HOWTO, available from
904 <http://www.tldp.org/docs.html#howto> as well as
905 <file:drivers/net/depca.c>.
907 To compile this driver as a module, choose M here and read
908 <file:Documentation/networking/net-modules.txt>. The module
909 will be called depca.
912 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
913 depends on NET_ETHERNET && (ISA || EISA || PCI)
915 If you have a network (Ethernet) card of this type, say Y and read
916 the Ethernet-HOWTO, available from
917 <http://www.tldp.org/docs.html#howto>.
919 To compile this driver as a module, choose M here and read
920 <file:Documentation/networking/net-modules.txt>. The module
921 will be called hp100.
924 bool "Other ISA cards"
925 depends on NET_ETHERNET && ISA && !X86_PC9800
927 If your network (Ethernet) card hasn't been mentioned yet and its
928 bus system (that's the way the cards talks to the other components
929 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
930 Make sure you know the name of your card. Read the Ethernet-HOWTO,
931 available from <http://www.tldp.org/docs.html#howto>.
935 Note that the answer to this question doesn't directly affect the
936 kernel: saying N will just cause the configurator to skip all
937 the remaining ISA network card questions. If you say Y, you will be
938 asked for your specific card in the following questions.
941 tristate "Cabletron E21xx support"
945 If you have a network (Ethernet) card of this type, say Y and read
946 the Ethernet-HOWTO, available from
947 <http://www.tldp.org/docs.html#howto>.
949 To compile this driver as a module, choose M here and read
950 <file:Documentation/networking/net-modules.txt>. The module
951 will be called e2100.
954 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
958 This driver supports the DE203, DE204 and DE205 network (Ethernet)
959 cards. If this is for you, say Y and read
960 <file:Documentation/networking/ewrk3.txt> in the kernel source as
961 well as the Ethernet-HOWTO, available from
962 <http://www.tldp.org/docs.html#howto>.
964 To compile this driver as a module, choose M here and read
965 <file:Documentation/networking/net-modules.txt>. The module
966 will be called ewrk3.
969 tristate "EtherExpress 16 support"
972 If you have an EtherExpress16 network (Ethernet) card, say Y and
973 read the Ethernet-HOWTO, available from
974 <http://www.tldp.org/docs.html#howto>. Note that the Intel
975 EtherExpress16 card used to be regarded as a very poor choice
976 because the driver was very unreliable. We now have a new driver
977 that should do better.
979 To compile this driver as a module, choose M here and read
980 <file:Documentation/networking/net-modules.txt>. The module
981 will be called eexpress.
984 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
987 If you have a network (Ethernet) card of this type, say Y. This
988 driver supports intel i82595{FX,TX} based boards. Note however
989 that the EtherExpress PRO/100 Ethernet card has its own separate
990 driver. Please read the Ethernet-HOWTO, available from
991 <http://www.tldp.org/docs.html#howto>.
993 To compile this driver as a module, choose M here and read
994 <file:Documentation/networking/net-modules.txt>. The module
995 will be called eepro.
998 tristate "FMV-181/182/183/184 support (OBSOLETE)"
999 depends on NET_ISA && OBSOLETE
1001 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
1002 say Y and read the Ethernet-HOWTO, available from
1003 <http://www.tldp.org/docs.html#howto>.
1005 If you use an FMV-183 or FMV-184 and it is not working, you may need
1006 to disable Plug & Play mode of the card.
1008 To compile this driver as a module, choose M here and read
1009 <file:Documentation/networking/net-modules.txt>. The module
1010 will be called fmv18x.
1013 tristate "HP PCLAN+ (27247B and 27252A) support"
1017 If you have a network (Ethernet) card of this type, say Y and read
1018 the Ethernet-HOWTO, available from
1019 <http://www.tldp.org/docs.html#howto>.
1021 To compile this driver as a module, choose M here and read
1022 <file:Documentation/networking/net-modules.txt>. The module
1023 will be called hp-plus.
1026 tristate "HP PCLAN (27245 and other 27xxx series) support"
1030 If you have a network (Ethernet) card of this type, say Y and read
1031 the Ethernet-HOWTO, available from
1032 <http://www.tldp.org/docs.html#howto>.
1034 To compile this driver as a module, choose M here and read
1035 <file:Documentation/networking/net-modules.txt>. The module
1039 tristate "LP486E on board Ethernet"
1042 Say Y here to support the 82596-based on-board Ethernet controller
1043 for the Panther motherboard, which is one of the two shipped in the
1044 Intel Professional Workstation.
1047 tristate "ICL EtherTeam 16i/32 support"
1050 If you have a network (Ethernet) card of this type, say Y and read
1051 the Ethernet-HOWTO, available from
1052 <http://www.tldp.org/docs.html#howto>.
1054 To compile this driver as a module, choose M here and read
1055 <file:Documentation/networking/net-modules.txt>. The module
1056 will be called eth16i.
1059 tristate "NE2000/NE1000 support"
1062 If you have a network (Ethernet) card of this type, say Y and read
1063 the Ethernet-HOWTO, available from
1064 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1065 without a specific driver are compatible with NE2000.
1067 If you have a PCI NE2000 card however, say N here and Y to "PCI
1068 NE2000 support", above. If you have a NE2000 card and are running on
1069 an MCA system (a bus system used on some IBM PS/2 computers and
1070 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1073 To compile this driver as a module, choose M here and read
1074 <file:Documentation/networking/net-modules.txt>. The module
1078 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1079 depends on NET_ISA && EXPERIMENTAL
1081 The Zenith Z-Note notebook computer has a built-in network
1082 (Ethernet) card, and this is the Linux driver for it. Note that the
1083 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1084 by this driver. Read the Ethernet-HOWTO, available from
1085 <http://www.tldp.org/docs.html#howto>.
1088 tristate "SEEQ8005 support (EXPERIMENTAL)"
1089 depends on NET_ISA && EXPERIMENTAL
1091 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1092 is for you, read the Ethernet-HOWTO, available from
1093 <http://www.tldp.org/docs.html#howto>.
1095 To compile this driver as a module, choose M here and read
1096 <file:Documentation/networking/net-modules.txt>. The module
1097 will be called seeq8005.
1100 tristate "SK_G16 support (OBSOLETE)"
1101 depends on NET_ISA && OBSOLETE
1103 If you have a network (Ethernet) card of this type, say Y and read
1104 the Ethernet-HOWTO, available from
1105 <http://www.tldp.org/docs.html#howto>.
1108 bool "NEC PC-9800 C-bus cards"
1109 depends on NET_ETHERNET && ISA && X86_PC9800
1111 If your network (Ethernet) card hasn't been mentioned yet and its
1112 bus system (that's the way the cards talks to the other components
1113 of your computer) is NEC PC-9800 C-Bus, say Y.
1116 tristate "Most NE2000-based Ethernet support"
1120 config NE2K_CBUS_EGY98
1121 bool "Melco EGY-98 support"
1122 depends on NE2K_CBUS
1124 config NE2K_CBUS_LGY98
1125 bool "Melco LGY-98 support"
1126 depends on NE2K_CBUS
1128 config NE2K_CBUS_ICM
1129 bool "ICM IF-27xxET support"
1130 depends on NE2K_CBUS
1132 config NE2K_CBUS_IOLA98
1133 bool "I-O DATA LA-98 support"
1134 depends on NE2K_CBUS
1136 config NE2K_CBUS_CNET98EL
1137 bool "Contec C-NET(98)E/L support"
1138 depends on NE2K_CBUS
1140 config NE2K_CBUS_CNET98EL_IO_BASE
1141 hex "C-NET(98)E/L I/O base address (0xaaed or 0x55ed)"
1142 depends on NE2K_CBUS_CNET98EL
1145 config NE2K_CBUS_ATLA98
1146 bool "Allied Telesis LA-98 Support"
1147 depends on NE2K_CBUS
1149 config NE2K_CBUS_BDN
1150 bool "ELECOM Laneed LD-BDN[123]A Support"
1151 depends on NE2K_CBUS
1153 config NE2K_CBUS_NEC108
1154 bool "NEC PC-9801-108 Support"
1155 depends on NE2K_CBUS
1158 tristate "SKnet MCA support"
1159 depends on NET_ETHERNET && MCA && BROKEN
1161 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1162 support" in order to use this driver. Supported cards are the SKnet
1163 Junior MC2 and the SKnet MC2(+). The driver automatically
1164 distinguishes between the two cards. Note that using multiple boards
1165 of different type hasn't been tested with this driver. Say Y if you
1166 have one of these Ethernet adapters.
1168 To compile this driver as a module, choose M here and read
1169 <file:Documentation/networking/net-modules.txt>. The module
1170 will be called sk_mca.
1173 tristate "NE/2 (ne2000 MCA version) support"
1174 depends on NET_ETHERNET && MCA
1177 If you have a network (Ethernet) card of this type, say Y and read
1178 the Ethernet-HOWTO, available from
1179 <http://www.tldp.org/docs.html#howto>.
1181 To compile this driver as a module, choose M here and read
1182 <file:Documentation/networking/net-modules.txt>. The module
1186 tristate "IBM LAN Adapter/A support"
1187 depends on NET_ETHERNET && MCA && MCA_LEGACY
1189 This is a Micro Channel Ethernet adapter. You need to set
1190 CONFIG_MCA to use this driver. It is both available as an in-kernel
1191 driver and as a module.
1193 To compile this driver as a module, choose M here and read
1194 <file:Documentation/networking/net-modules.txt>. The only
1195 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1196 will both support 16K and 32K memory windows, however a 32K window
1197 gives a better security against packet losses. Usage of multiple
1198 boards with this driver should be possible, but has not been tested
1199 up to now due to lack of hardware.
1202 tristate "IBM LAN Virtual Ethernet support"
1203 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1205 This driver supports virtual ethernet adapters on newer IBM iSeries
1206 and pSeries systems.
1208 To compile this driver as a module, choose M here and read
1209 <file:Documentation/networking/net-modules.txt>. The module will
1213 tristate "IBM PPC4xx EMAC driver support"
1216 This driver supports the IBM PPC4xx EMAC family of on-chip
1217 Ethernet controllers.
1219 config IBM_EMAC_ERRMSG
1220 bool "Verbose error messages"
1224 int "Number of receive buffers"
1226 default "128" if IBM_EMAC4
1230 int "Number of transmit buffers"
1232 default "128" if IBM_EMAC4
1235 config IBM_EMAC_FGAP
1240 config IBM_EMAC_SKBRES
1241 int "Skb reserve amount"
1246 bool "EISA, VLB, PCI and on board controllers"
1247 depends on NET_ETHERNET && (ISA || EISA || PCI)
1249 This is another class of network cards which attach directly to the
1250 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1251 available from <http://www.tldp.org/docs.html#howto>.
1253 Note that the answer to this question doesn't directly affect the
1254 kernel: saying N will just cause the configurator to skip all
1255 the questions about this class of network cards. If you say Y, you
1256 will be asked for your specific card in the following questions. If
1257 you are unsure, say Y.
1260 tristate "AMD PCnet32 PCI support"
1261 depends on NET_PCI && PCI
1265 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1266 answer Y here and read the Ethernet-HOWTO, available from
1267 <http://www.tldp.org/docs.html#howto>.
1269 To compile this driver as a module, choose M here and read
1270 <file:Documentation/networking/net-modules.txt>. The module
1271 will be called pcnet32.
1274 tristate "AMD 8111 (new PCI lance) support"
1275 depends on NET_PCI && PCI
1279 If you have an AMD 8111-based PCI lance ethernet card,
1280 answer Y here and read the Ethernet-HOWTO, available from
1281 <http://www.tldp.org/docs.html#howto>.
1283 To compile this driver as a module, choose M here and read
1284 <file:Documentation/networking/net-modules.txt>. The module
1285 will be called amd8111e.
1286 config AMD8111E_NAPI
1287 bool "Enable NAPI support"
1288 depends on AMD8111_ETH
1290 config ADAPTEC_STARFIRE
1291 tristate "Adaptec Starfire/DuraLAN support"
1292 depends on NET_PCI && PCI
1296 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1297 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1298 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1301 To compile this driver as a module, choose M here: the module
1302 will be called starfire. This is recommended.
1304 config ADAPTEC_STARFIRE_NAPI
1305 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1306 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1308 NAPI is a new driver API designed to reduce CPU and interrupt load
1309 when the driver is receiving lots of packets from the card. It is
1310 still somewhat experimental and thus not yet enabled by default.
1312 If your estimated Rx load is 10kpps or more, or if the card will be
1313 deployed on potentially unfriendly networks (e.g. in a firewall),
1317 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1318 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1321 If you have a network (Ethernet) card of this type, say Y and read
1322 the Ethernet-HOWTO, available from
1323 <http://www.tldp.org/docs.html#howto>.
1325 To compile this driver as a module, choose M here and read
1326 <file:Documentation/networking/net-modules.txt>. The module
1327 will be called ac3200.
1330 tristate "Apricot Xen-II on board Ethernet"
1331 depends on NET_PCI && ISA
1333 If you have a network (Ethernet) controller of this type, say Y and
1334 read the Ethernet-HOWTO, available from
1335 <http://www.tldp.org/docs.html#howto>.
1337 To compile this driver as a module, choose M here and read
1338 <file:Documentation/networking/net-modules.txt>. The module will be
1342 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1343 depends on NET_PCI && PCI && EXPERIMENTAL
1346 If you have a network (Ethernet) controller of this type, say Y and
1347 read the Ethernet-HOWTO, available from
1348 <http://www.tldp.org/docs.html#howto>.
1350 To compile this driver as a module, choose M here and read
1351 <file:Documentation/networking/net-modules.txt>. The module will be
1355 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1356 depends on NET_PCI && PCI && EXPERIMENTAL
1358 If you have a network (Ethernet) controller of this type, say Y and
1359 read the Ethernet-HOWTO, available from
1360 <http://www.tldp.org/docs.html#howto>.
1362 To compile this driver as a module, choose M here and read
1363 <file:Documentation/networking/net-modules.txt>. The module will be
1368 tristate "CS89x0 support"
1369 depends on NET_PCI && ISA
1371 Support for CS89x0 chipset based Ethernet cards. If you have a
1372 network (Ethernet) card of this type, say Y and read the
1373 Ethernet-HOWTO, available from
1374 <http://www.tldp.org/docs.html#howto> as well as
1375 <file:Documentation/networking/cs89x0.txt>.
1377 To compile this driver as a module, choose M here and read
1378 <file:Documentation/networking/net-modules.txt>. The module will be
1382 tristate "TOSHIBA TC35815 Ethernet support"
1383 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1386 tristate "Digi Intl. RightSwitch SE-X support"
1387 depends on NET_PCI && (PCI || EISA)
1389 This is support for the Digi International RightSwitch series of
1390 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1391 models. If you have a network card of this type, say Y and read the
1392 Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto>. More specific
1394 information is contained in <file:Documentation/networking/dgrs.txt>.
1396 To compile this driver as a module, choose M here and read
1397 <file:Documentation/networking/net-modules.txt>. The module
1398 will be called dgrs.
1401 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1402 depends on NET_PCI && PCI
1405 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1406 card, say Y and read the Ethernet-HOWTO, available from
1407 <http://www.tldp.org/docs.html#howto>.
1409 To compile this driver as a module, choose M here and read
1410 <file:Documentation/networking/net-modules.txt>. The module
1411 will be called eepro100.
1415 bool "Use PIO instead of MMIO" if !X86_VISWS
1417 default y if X86_VISWS
1419 This instructs the driver to use programmed I/O ports (PIO) instead
1420 of PCI shared memory (MMIO). This can possibly solve some problems
1421 in case your mainboard has memory consistency issues. If unsure,
1425 tristate "Intel(R) PRO/100+ support"
1426 depends on NET_PCI && PCI
1429 This driver supports Intel(R) PRO/100 family of adapters, which
1432 Controller Adapter Name Board IDs
1433 ---------- ------------ ---------
1435 82558 PRO/100+ PCI Adapter 668081-xxx,
1437 82558 PRO/100+ Management Adapter 691334-xxx,
1440 82558 PRO/100+ Dual Port Server Adapter 714303-xxx,
1443 82558 PRO/100+ PCI Server Adapter 710550-xxx
1444 82550 PRO/100 S Server Adapter 752438-xxx
1453 82550 PRO/100 S Desktop Adapter 751767-xxx
1460 82559 PRO/100+ Server Adapter 729757-xxx
1461 82559 PRO/100 S Management Adapter 748566-xxx,
1463 82550 PRO/100 S Dual Port Server Adapter A56831-xxx
1464 82551 PRO/100 M Desktop Adapter A80897-xxx
1465 PRO/100 S Advanced Management Adapter
1468 CNR PRO/100 VE Desktop Adapter A10386-xxx,
1472 PRO/100 VM Desktop Adapter A14323-xxx,
1479 To verify that your adapter is supported, find the board ID number
1480 on the adapter. Look for a label that has a barcode and a number
1481 in the format 123456-001 (six digits hyphen three digits). Match
1482 this to the list of numbers above.
1484 For more information on how to identify your adapter, go to the
1485 Adapter & Driver ID Guide at:
1487 http://support.intel.com/support/network/adapter/pro100/21397.htm
1489 For the latest Intel PRO/100 network driver for Linux, see:
1491 http://appsr.intel.com/scripts-df/support_intel.asp
1493 More specific information on configuring the driver is in
1494 <file:Documentation/networking/e100.txt>.
1496 To compile this driver as a module, choose M here and read
1497 <file:Documentation/networking/net-modules.txt>. The module
1498 will be called e100.
1501 bool "Use Rx Polling (NAPI)"
1505 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1506 depends on NET_PCI && EISA && EXPERIMENTAL
1509 If you have a network (Ethernet) card of this type, say Y and read
1510 the Ethernet-HOWTO, available from
1511 <http://www.tldp.org/docs.html#howto>.
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 lne390.
1518 tristate "Myson MTD-8xx PCI Ethernet support"
1519 depends on NET_PCI && PCI
1523 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1524 cards. Specifications and data at
1525 <http://www.myson.com.hk/mtd/datasheet/>.
1528 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1529 depends on NET_PCI && PCI
1532 This driver is for the National Semiconductor DP83810 series,
1533 which is used in cards from PureData, NetGear, Linksys
1534 and others, including the 83815 chip.
1535 More specific information and updates are available from
1536 <http://www.scyld.com/network/natsemi.html>.
1539 tristate "PCI NE2000 and clones support (see help)"
1540 depends on NET_PCI && PCI
1543 This driver is for NE2000 compatible PCI cards. It will not work
1544 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1545 support" below). If you have a PCI NE2000 network (Ethernet) card,
1546 say Y and read the Ethernet-HOWTO, available from
1547 <http://www.tldp.org/docs.html#howto>.
1549 This driver also works for the following NE2000 clone cards:
1550 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1551 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1552 Holtek HT80232 Holtek HT80229
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 ne2k-pci.
1559 tristate "Novell/Eagle/Microdyne NE3210 EISA 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>. Note that this driver
1566 will NOT WORK for NE3200 cards as they are completely different.
1568 To compile this driver as a module, choose M here and read
1569 <file:Documentation/networking/net-modules.txt>. The module
1570 will be called ne3210.
1573 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1574 depends on NET_PCI && EISA && EXPERIMENTAL
1577 If you have a network (Ethernet) card of this type, say Y and read
1578 the Ethernet-HOWTO, available from
1579 <http://www.tldp.org/docs.html#howto>.
1581 To compile this driver as a module, choose M here and read
1582 <file:Documentation/networking/net-modules.txt>. The module
1583 will be called es3210.
1586 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1587 depends on NET_PCI && PCI && EXPERIMENTAL
1591 This is a driver for the Fast Ethernet PCI network cards based on
1592 the RTL8139C+ chips. If you have one of those, say Y and read
1593 the Ethernet-HOWTO, available from
1594 <http://www.tldp.org/docs.html#howto>.
1596 To compile this driver as a module, choose M here: the module
1597 will be called 8139cp. This is recommended.
1600 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1601 depends on NET_PCI && PCI
1605 This is a driver for the Fast Ethernet PCI network cards based on
1606 the RTL8139 chips. If you have one of those, say Y and read
1607 <file:Documentation/networking/8139too.txt> as well as the
1608 Ethernet-HOWTO, available from
1609 <http://www.tldp.org/docs.html#howto>.
1611 To compile this driver as a module, choose M here: the module
1612 will be called 8139too. This is recommended.
1615 bool "Use PIO instead of MMIO"
1619 This instructs the driver to use programmed I/O ports (PIO) instead
1620 of PCI shared memory (MMIO). This can possibly solve some problems
1621 in case your mainboard has memory consistency issues. If unsure,
1624 config 8139TOO_TUNE_TWISTER
1625 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1628 This implements a function which might come in handy in case you
1629 are using low quality on long cabling. It is required for RealTek
1630 RTL-8139 revision K boards, and totally unused otherwise. It tries
1631 to match the transceiver to the cable characteristics. This is
1632 experimental since hardly documented by the manufacturer.
1636 bool "Support for older RTL-8129/8130 boards"
1639 This enables support for the older and uncommon RTL-8129 and
1640 RTL-8130 chips, which support MII via an external transceiver,
1641 instead of an internal one. Disabling this option will save some
1642 memory by making the code size smaller. If unsure, say Y.
1644 config 8139_OLD_RX_RESET
1645 bool "Use older RX-reset method"
1648 The 8139too driver was recently updated to contain a more rapid
1649 reset sequence, in the face of severe receive errors. This "new"
1650 RX-reset method should be adequate for all boards. But if you
1651 experience problems, you can enable this option to restore the
1652 old RX-reset behavior. If unsure, say N.
1655 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1656 depends on NET_PCI && PCI
1659 This is a driver for the Fast Ethernet PCI network cards based on
1660 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1661 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1662 read the Ethernet-HOWTO, available at
1663 <http://www.tldp.org/docs.html#howto>. Please read
1664 <file:Documentation/networking/sis900.txt> and comments at the
1665 beginning of <file:drivers/net/sis900.c> for more information.
1667 This driver also supports AMD 79C901 HomePNA so that you can use
1668 your phone line as a network cable.
1670 To compile this driver as a module, choose M here: the module
1671 will be called sis900. This is recommended.
1674 tristate "SMC EtherPower II"
1675 depends on NET_PCI && PCI
1679 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1680 which is based on the SMC83c17x (EPIC/100).
1681 More specific information and updates are available from
1682 <http://www.scyld.com/network/epic100.html>.
1685 tristate "Sundance Alta support"
1686 depends on NET_PCI && PCI
1690 This driver is for the Sundance "Alta" chip.
1691 More specific information and updates are available from
1692 <http://www.scyld.com/network/sundance.html>.
1694 config SUNDANCE_MMIO
1695 bool "Use MMIO instead of PIO"
1698 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1699 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1700 is known to solve bugs on certain chips.
1705 tristate "TI ThunderLAN support"
1706 depends on NET_PCI && (PCI || EISA) && !64BIT
1708 If you have a PCI Ethernet network card based on the ThunderLAN chip
1709 which is supported by this driver, say Y and read the
1710 Ethernet-HOWTO, available from
1711 <http://www.tldp.org/docs.html#howto>.
1713 Devices currently supported by this driver are Compaq Netelligent,
1714 Compaq NetFlex and Olicom cards. Please read the file
1715 <file:Documentation/networking/tlan.txt> for more details.
1717 To compile this driver as a module, choose M here and read
1718 <file:Documentation/networking/net-modules.txt>. The module
1719 will be called tlan.
1721 Please email feedback to torben.mathiasen@compaq.com.
1724 tristate "VIA Rhine support"
1725 depends on NET_PCI && PCI
1729 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1730 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1731 Ethernet functions can also be found integrated on South Bridges
1734 To compile this driver as a module, choose M here. The module
1735 will be called via-rhine.
1737 config VIA_RHINE_MMIO
1738 bool "Use MMIO instead of PIO"
1739 depends on VIA_RHINE
1741 This instructs the driver to use PCI shared memory (MMIO) instead of
1742 programmed I/O ports (PIO). Enabling this gives an improvement in
1743 processing time in parts of the driver.
1748 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1749 depends on NET_PCI && EXPERIMENTAL && MIPS
1751 The SAA9730 is a combined multimedia and peripheral controller used
1752 in thin clients, Internet access terminals, and diskless
1754 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1757 bool "Pocket and portable adapters"
1758 depends on NET_ETHERNET && ISA
1760 Cute little network (Ethernet) devices which attach to the parallel
1761 port ("pocket adapters"), commonly used with laptops. If you have
1762 one of those, say Y and read the Ethernet-HOWTO, available from
1763 <http://www.tldp.org/docs.html#howto>.
1765 If you want to plug a network (or some other) card into the PCMCIA
1766 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1767 credit card size extension cards used by all modern laptops), you
1768 need the pcmcia-cs package (location contained in the file
1769 <file:Documentation/Changes>) and you can say N here.
1771 Laptop users should read the Linux Laptop home page at
1772 <http://www.linux-on-laptops.com/> or
1773 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1775 Note that the answer to this question doesn't directly affect the
1776 kernel: saying N will just cause the configurator to skip all
1777 the questions about this class of network devices. If you say Y, you
1778 will be asked for your specific device in the following questions.
1781 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1782 depends on NET_POCKET && ISA && X86
1785 This is a network (Ethernet) device which attaches to your parallel
1786 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1787 available from <http://www.tldp.org/docs.html#howto>, if you
1788 want to use this. If you intend to use this driver, you should have
1789 said N to the "Parallel printer support", because the two drivers
1790 don't like each other.
1792 To compile this driver as a module, choose M here: the module
1796 tristate "D-Link DE600 pocket adapter support"
1797 depends on NET_POCKET && ISA
1799 This is a network (Ethernet) device which attaches to your parallel
1800 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1801 Ethernet-HOWTO, available from
1802 <http://www.tldp.org/docs.html#howto>, if you want to use
1803 this. It is possible to have several devices share a single parallel
1804 port and it is safe to compile the corresponding drivers into the
1807 To compile this driver as a module, choose M here: the module
1808 will be called de600.
1811 tristate "D-Link DE620 pocket adapter support"
1812 depends on NET_POCKET && ISA
1814 This is a network (Ethernet) device which attaches to your parallel
1815 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1816 Ethernet-HOWTO, available from
1817 <http://www.tldp.org/docs.html#howto>, if you want to use
1818 this. It is possible to have several devices share a single parallel
1819 port and it is safe to compile the corresponding drivers into the
1822 To compile this driver as a module, choose M here: the module
1823 will be called de620.
1826 tristate "SGI Seeq ethernet controller support"
1827 depends on NET_ETHERNET && SGI_IP22
1829 Say Y here if you have an Seeq based Ethernet network card. This is
1830 used in many Silicon Graphics machines.
1833 tristate "DEC LANCE ethernet controller support"
1834 depends on NET_ETHERNET && MACH_DECSTATION
1837 This driver is for the series of Ethernet controllers produced by
1838 DEC (now Compaq) based on the AMD Lance chipset, including the
1839 DEPCA series. (This chipset is better known via the NE2100 cards.)
1842 tristate "Baget AMD LANCE support"
1843 depends on NET_ETHERNET && BAGET_MIPS
1845 Say Y to enable kernel support for AMD Lance Ethernet cards on the
1846 MIPS-32-based Baget embedded system. This chipset is better known
1847 via the NE2100 cards.
1850 bool "Motorola 68360 ethernet controller"
1853 Say Y here if you want to use the built-in ethernet controller of
1854 the Motorola 68360 processor.
1857 bool "FEC ethernet controller (of ColdFire 5272)"
1858 depends on M5272 || M5282
1860 Say Y here if you want to use the built-in 10/100 Fast ethernet
1861 controller on the Motorola ColdFire 5272 processor.
1864 tristate "NE2000 compatible support for H8/300"
1865 depends on H8300 && NET_ETHERNET
1867 Say Y here if you want to use the NE2000 compatible
1868 controller on the Renesas H8/300 processor.
1876 menu "Gigabit Ethernet (1000/10000 Mbit)"
1877 depends on NETDEVICES
1880 bool "Gigabit Ethernet (1000/10000 Mbit) controller support"
1881 depends on NETDEVICES && NET_ETHERNET && (PCI || SBUS)
1883 Gigabit ethernet. It's yummy and fast, fast, fast.
1885 Note that the answer to this question doesn't directly affect the
1886 kernel: saying N will just cause the configurator to skip all
1887 the questions about this class of network cards. If you say Y, you
1888 will be asked for your specific card in the following questions.
1890 If you are unsure, say Y.
1893 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1894 depends on PCI && NET_GIGE
1896 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1897 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1898 adapter. The driver allows for using the Jumbo Frame option (9000
1899 bytes/frame) however it requires that your switches can handle this
1900 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1903 To compile this driver as a module, choose M here: the
1904 module will be called acenic.
1906 config ACENIC_OMIT_TIGON_I
1907 bool "Omit support for old Tigon I based AceNICs"
1910 Say Y here if you only have Tigon II based AceNICs and want to leave
1911 out support for the older Tigon I based cards which are no longer
1912 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1913 version)). This will reduce the size of the driver object by
1914 app. 100KB. If you are not sure whether your card is a Tigon I or a
1915 Tigon II, say N here.
1917 The safe and default value for this is N.
1920 tristate "D-Link DL2000-based Gigabit Ethernet support"
1921 depends on PCI && NET_GIGE
1924 This driver supports D-Link 2000-based gigabit ethernet cards, which
1926 D-Link DGE-550T Gigabit Ethernet Adapter.
1927 D-Link DL2000-based Gigabit Ethernet Adapter.
1929 To compile this driver as a module, choose M here: the
1930 module will be called dl2k.
1933 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1934 depends on PCI && NET_GIGE
1936 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1937 adapters, which includes:
1939 Controller Adapter Name Board IDs
1940 ---------- ------------ ---------
1941 82542 PRO/1000 Gigabit Server Adapter 700262-xxx,
1943 82543 PRO/1000 F Server Adapter 738640-xxx,
1945 82543 PRO/1000 T Server Adapter A19845-xxx,
1947 82544 PRO/1000 XT Server Adapter A51580-xxx
1948 82544 PRO/1000 XF Server Adapter A50484-xxx
1949 82544 PRO/1000 T Desktop Adapter A62947-xxx
1950 82540 PRO/1000 MT Desktop Adapter A78408-xxx
1951 82541 PRO/1000 MT Desktop Adapter C91016-xxx
1952 82545 PRO/1000 MT Server Adapter A92165-xxx
1953 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx
1954 82545 PRO/1000 MF Server Adapter A91622-xxx
1955 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx
1956 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx
1958 For more information on how to identify your adapter, go to the
1959 Adapter & Driver ID Guide at:
1961 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1963 For general information and support, go to the Intel support
1966 <http://support.intel.com>
1968 More specific information on configuring the driver is in
1969 <file:Documentation/networking/e1000.txt>.
1971 To compile this driver as a module, choose M here and read
1972 <file:Documentation/networking/net-modules.txt>. The module
1973 will be called e1000.
1976 bool "Use Rx Polling (NAPI)"
1980 tristate "MyriCOM Gigabit Ethernet support"
1981 depends on SBUS && NET_GIGE
1983 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1985 To compile this driver as a module, choose M here: the module
1986 will be called myri_sbus. This is recommended.
1989 tristate "National Semiconduct DP83820 support"
1990 depends on PCI && NET_GIGE
1992 This is a driver for the National Semiconductor DP83820 series
1993 of gigabit ethernet MACs. Cards using this chipset include
1994 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1995 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1999 tristate "Packet Engines Hamachi GNIC-II support"
2000 depends on PCI && NET_GIGE
2003 If you have a Gigabit Ethernet card of this type, say Y and read
2004 the Ethernet-HOWTO, available from
2005 <http://www.tldp.org/docs.html#howto>.
2007 To compile this driver as a module, choose M here and read
2008 <file:Documentation/networking/net-modules.txt>. The module will be
2012 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2013 depends on PCI && EXPERIMENTAL && NET_GIGE
2016 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2017 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2018 used by the Beowulf Linux cluster project. See
2019 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2020 information about this driver in particular and Beowulf in general.
2022 To compile this driver as a module, choose M here: the module
2023 will be called yellowfin. This is recommended.
2026 tristate "Realtek 8169 gigabit ethernet support"
2027 depends on PCI && NET_GIGE
2030 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2032 To compile this driver as a module, choose M here: the module
2033 will be called r8169. This is recommended.
2036 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2037 depends on PCI && NET_GIGE
2039 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2040 compliant Gigabit Ethernet Adapter. The following adapters are supported
2042 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2043 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2044 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2045 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2046 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2047 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2048 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2049 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2050 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2051 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2052 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2053 - DGE-530T Gigabit Ethernet Adapter
2054 - EG1032 v2 Instant Gigabit Network Adapter
2055 - EG1064 v2 Instant Gigabit Network Adapter
2056 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2057 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2058 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2059 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2060 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2061 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2062 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2063 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2064 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2065 - Marvell RDK-8001 Adapter
2066 - Marvell RDK-8002 Adapter
2067 - Marvell RDK-8003 Adapter
2068 - Marvell RDK-8004 Adapter
2069 - Marvell RDK-8006 Adapter
2070 - Marvell RDK-8007 Adapter
2071 - Marvell RDK-8008 Adapter
2072 - Marvell RDK-8009 Adapter
2073 - Marvell RDK-8010 Adapter
2074 - Marvell RDK-8011 Adapter
2075 - Marvell RDK-8012 Adapter
2076 - Marvell RDK-8052 Adapter
2077 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2078 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2079 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2080 - SK-9521 10/100/1000Base-T Adapter
2081 - SK-9521 V2.0 10/100/1000Base-T Adapter
2082 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2083 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2084 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2085 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2086 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2087 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2088 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2089 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2090 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2091 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2092 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2093 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2094 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2095 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2096 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2097 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2098 - SMC EZ Card 1000 (SMC9452TXV.2)
2100 The adapters support Jumbo Frames.
2101 The dual link adapters support link-failover and dual port features.
2102 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2103 the scatter-gather functionality with sendfile(). Please refer to
2104 Documentation/networking/sk98lin.txt for more information about
2105 optional driver parameters.
2106 Questions concerning this driver may be addressed to:
2109 If you want to compile this driver as a module ( = code which can be
2110 inserted in and removed from the running kernel whenever you want),
2111 say M here and read Documentation/kbuild/modules.txt. The module will
2112 be called sk98lin. This is recommended.
2115 tristate "Broadcom Tigon3 support"
2116 depends on PCI && NET_GIGE
2118 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2120 To compile this driver as a module, choose M here: the module
2121 will be called tg3. This is recommended.
2124 tristate "Intel(R) PRO/10GbE support"
2125 depends on PCI && NET_GIGE
2127 This driver supports Intel(R) PRO/10GbE family of
2128 adapters, which includes:
2130 Controller Adapter Name Board IDs
2131 ---------- ------------ ---------
2132 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx
2134 For more information on how to identify your adapter, go to the
2135 Adapter & Driver ID Guide at:
2137 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2139 For general information and support, go to the Intel support
2142 <http://support.intel.com>
2144 More specific information on configuring the driver is in
2145 <file:Documentation/networking/ixgb.txt>.
2147 To compile this driver as a module, choose M here and read
2148 <file:Documentation/networking/net-modules.txt>. The module
2149 will be called ixgb.
2152 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2153 depends on IXGB && EXPERIMENTAL
2156 tristate "S2IO 10Gbe XFrame NIC"
2157 depends on PCI && NET_GIGE
2159 This driver supports the 10Gbe XFrame NIC of S2IO.
2160 For help regarding driver compilation, installation and
2161 tuning please look into ~/drivers/net/s2io/README.txt.
2164 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2165 depends on S2IO && EXPERIMENTAL
2169 source "drivers/net/tokenring/Kconfig"
2171 source "drivers/net/wireless/Kconfig"
2173 source "drivers/net/pcmcia/Kconfig"
2175 source "drivers/net/wan/Kconfig"
2177 source "drivers/atm/Kconfig"
2179 source "drivers/s390/net/Kconfig"
2182 tristate "iSeries Virtual Ethernet driver support"
2183 depends on NETDEVICES && PPC_ISERIES
2186 bool "FDDI driver support"
2187 depends on NETDEVICES && (PCI || EISA)
2189 Fiber Distributed Data Interface is a high speed local area network
2190 design; essentially a replacement for high speed Ethernet. FDDI can
2191 run over copper or fiber. If you are connected to such a network and
2192 want a driver for the FDDI card in your computer, say Y here (and
2193 then also Y to the driver for your FDDI card, below). Most people
2197 tristate "Digital DEFEA and DEFPA adapter support"
2198 depends on FDDI && (PCI || EISA)
2200 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2201 (DEFPA) controllers which can connect you to a local FDDI network.
2204 tristate "SysKonnect FDDI PCI support"
2205 depends on FDDI && PCI
2207 Say Y here if you have a SysKonnect FDDI PCI adapter.
2208 The following adapters are supported by this driver:
2209 - SK-5521 (SK-NET FDDI-UP)
2210 - SK-5522 (SK-NET FDDI-UP DAS)
2211 - SK-5541 (SK-NET FDDI-FP)
2212 - SK-5543 (SK-NET FDDI-LP)
2213 - SK-5544 (SK-NET FDDI-LP DAS)
2214 - SK-5821 (SK-NET FDDI-UP64)
2215 - SK-5822 (SK-NET FDDI-UP64 DAS)
2216 - SK-5841 (SK-NET FDDI-FP64)
2217 - SK-5843 (SK-NET FDDI-LP64)
2218 - SK-5844 (SK-NET FDDI-LP64 DAS)
2219 - Netelligent 100 FDDI DAS Fibre SC
2220 - Netelligent 100 FDDI SAS Fibre SC
2221 - Netelligent 100 FDDI DAS UTP
2222 - Netelligent 100 FDDI SAS UTP
2223 - Netelligent 100 FDDI SAS Fibre MIC
2225 Read <file:Documentation/networking/skfp.txt> for information about
2228 Questions concerning this driver can be addressed to:
2231 To compile this driver as a module, choose M here: the module
2232 will be called skfp. This is recommended.
2235 bool "HIPPI driver support (EXPERIMENTAL)"
2236 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2238 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2239 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2240 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2241 single-mode). HIPPI networks are commonly used for clusters and to
2242 connect to super computers. If you are connected to a HIPPI network
2243 and have a HIPPI network card in your computer that you want to use
2244 under Linux, say Y here (you must also remember to enable the driver
2245 for your HIPPI card below). Most people will say N here.
2248 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2249 depends on HIPPI && PCI
2251 Say Y here if this is your PCI HIPPI network card.
2253 To compile this driver as a module, choose M here: the module
2254 will be called rrunner. If unsure, say N.
2256 config ROADRUNNER_LARGE_RINGS
2257 bool "Use large TX/RX rings (EXPERIMENTAL)"
2258 depends on ROADRUNNER
2260 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2261 of additional memory to allow for fastest operation, both for
2262 transmitting and receiving. This memory cannot be used by any other
2263 kernel code or by user space programs. Say Y here only if you have
2267 tristate "PLIP (parallel port) support"
2268 depends on NETDEVICES && PARPORT
2270 PLIP (Parallel Line Internet Protocol) is used to create a
2271 reasonably fast mini network consisting of two (or, rarely, more)
2272 local machines. A PLIP link from a Linux box is a popular means to
2273 install a Linux distribution on a machine which doesn't have a
2274 CD-ROM drive (a minimal system has to be transferred with floppies
2275 first). The kernels on both machines need to have this PLIP option
2276 enabled for this to work.
2278 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2279 ports (the connectors at the computers with 25 holes) are connected
2280 with "null printer" or "Turbo Laplink" cables which can transmit 4
2281 bits at a time (mode 0) or with special PLIP cables, to be used on
2282 bidirectional parallel ports only, which can transmit 8 bits at a
2283 time (mode 1); you can find the wiring of these cables in
2284 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2285 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2286 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2287 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2288 and winsock or NCSA's telnet.
2290 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2291 as the NET-3-HOWTO, both available from
2292 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2293 protocol has been changed and this PLIP driver won't work together
2294 with the PLIP support in Linux versions 1.0.x. This option enlarges
2295 your kernel by about 8 KB.
2297 To compile this driver as a module, choose M here and read
2298 <file:Documentation/networking/net-modules.txt>. The module will be
2299 called plip. If unsure, say Y or M, in case you buy a laptop
2303 tristate "PPP (point-to-point protocol) support"
2304 depends on NETDEVICES
2306 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2307 the same purpose: sending Internet traffic over telephone (and other
2308 serial) lines. Ask your access provider if they support it, because
2309 otherwise you can't use it; most Internet access providers these
2310 days support PPP rather than SLIP.
2312 To use PPP, you need an additional program called pppd as described
2313 in the PPP-HOWTO, available at
2314 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2315 the version of pppd recommended in <file:Documentation/Changes>.
2316 The PPP option enlarges your kernel by about 16 KB.
2318 There are actually two versions of PPP: the traditional PPP for
2319 asynchronous lines, such as regular analog phone lines, and
2320 synchronous PPP which can be used over digital ISDN lines for
2321 example. If you want to use PPP over phone lines or other
2322 asynchronous serial lines, you need to say Y (or M) here and also to
2323 the next option, "PPP support for async serial ports". For PPP over
2324 synchronous lines, you should say Y (or M) here and to "Support
2325 synchronous PPP", below.
2327 If you said Y to "Version information on all symbols" above, then
2328 you cannot compile the PPP driver into the kernel; you can then only
2329 compile it as a module. To compile this driver as a module, choose M
2330 here and read <file:Documentation/networking/net-modules.txt>.
2331 The module will be called ppp_generic.
2333 config PPP_MULTILINK
2334 bool "PPP multilink support (EXPERIMENTAL)"
2335 depends on PPP && EXPERIMENTAL
2337 PPP multilink is a protocol (defined in RFC 1990) which allows you
2338 to combine several (logical or physical) lines into one logical PPP
2339 connection, so that you can utilize your full bandwidth.
2341 This has to be supported at the other end as well and you need a
2342 version of the pppd daemon which understands the multilink protocol.
2347 bool "PPP filtering"
2350 Say Y here if you want to be able to filter the packets passing over
2351 PPP interfaces. This allows you to control which packets count as
2352 activity (i.e. which packets will reset the idle timer or bring up
2353 a demand-dialled link) and which packets are to be dropped entirely.
2354 You need to say Y here if you wish to use the pass-filter and
2355 active-filter options to pppd.
2360 tristate "PPP support for async serial ports"
2363 Say Y (or M) here if you want to be able to use PPP over standard
2364 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2365 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2368 To compile this driver as a module, choose M here.
2373 tristate "PPP support for sync tty ports"
2376 Say Y (or M) here if you want to be able to use PPP over synchronous
2377 (HDLC) tty devices, such as the SyncLink adapter. These devices
2378 are often used for high-speed leased lines like T1/E1.
2380 To compile this driver as a module, choose M here.
2383 tristate "PPP Deflate compression"
2388 Support for the Deflate compression method for PPP, which uses the
2389 Deflate algorithm (the same algorithm that gzip uses) to compress
2390 each PPP packet before it is sent over the wire. The machine at the
2391 other end of the PPP link (usually your ISP) has to support the
2392 Deflate compression method as well for this to be useful. Even if
2393 they don't support it, it is safe to say Y here.
2395 To compile this driver as a module, choose M here.
2398 tristate "PPP BSD-Compress compression"
2401 Support for the BSD-Compress compression method for PPP, which uses
2402 the LZW compression method to compress each PPP packet before it is
2403 sent over the wire. The machine at the other end of the PPP link
2404 (usually your ISP) has to support the BSD-Compress compression
2405 method as well for this to be useful. Even if they don't support it,
2406 it is safe to say Y here.
2408 The PPP Deflate compression method ("PPP Deflate compression",
2409 above) is preferable to BSD-Compress, because it compresses better
2412 Note that the BSD compression code will always be compiled as a
2413 module; it is called bsd_comp and will show up in the directory
2414 modules once you have said "make modules". If unsure, say N.
2417 tristate "PPP over Ethernet (EXPERIMENTAL)"
2418 depends on EXPERIMENTAL && PPP
2420 Support for PPP over Ethernet.
2422 This driver requires the latest version of pppd from the CVS
2423 repository at cvs.samba.org. Alternatively, see the
2424 RoaringPenguin package (http://www.roaringpenguin.com/pppoe)
2425 which contains instruction on how to use this driver (under
2426 the heading "Kernel mode PPPoE").
2429 tristate "PPP over ATM"
2430 depends on ATM && PPP
2432 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2433 This implementation does not yet comply with section 8 of RFC2364,
2434 which can lead to bad results if the ATM peer loses state and
2435 changes its encapsulation unilaterally.
2438 tristate "SLIP (serial line) support"
2439 depends on NETDEVICES
2441 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2442 connect to your Internet service provider or to connect to some
2443 other local Unix box or if you want to configure your Linux box as a
2444 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2445 Internet Protocol) is a protocol used to send Internet traffic over
2446 serial connections such as telephone lines or null modem cables;
2447 nowadays, the protocol PPP is more commonly used for this same
2450 Normally, your access provider has to support SLIP in order for you
2451 to be able to use it, but there is now a SLIP emulator called SLiRP
2452 around (available from
2453 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2454 allows you to use SLIP over a regular dial up shell connection. If
2455 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2456 NET-3-HOWTO, available from
2457 <http://www.tldp.org/docs.html#howto>, explains how to
2458 configure SLIP. Note that you don't need this option if you just
2459 want to run term (term is a program which gives you almost full
2460 Internet connectivity if you have a regular dial up shell account on
2461 some Internet connected Unix computer. Read
2462 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2463 support will enlarge your kernel by about 4 KB. If unsure, say N.
2465 To compile this driver as a module, choose M here and read
2466 <file:Documentation/networking/net-modules.txt>. The module will be
2469 config SLIP_COMPRESSED
2470 bool "CSLIP compressed headers"
2473 This protocol is faster than SLIP because it uses compression on the
2474 TCP/IP headers (not on the data itself), but it has to be supported
2475 on both ends. Ask your access provider if you are not sure and
2476 answer Y, just in case. You will still be able to use plain SLIP. If
2477 you plan to use SLiRP, the SLIP emulator (available from
2478 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2479 allows you to use SLIP over a regular dial up shell connection, you
2480 definitely want to say Y here. The NET-3-HOWTO, available from
2481 <http://www.tldp.org/docs.html#howto>, explains how to configure
2482 CSLIP. This won't enlarge your kernel.
2485 bool "Keepalive and linefill"
2488 Adds additional capabilities to the SLIP driver to support the
2489 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2492 config SLIP_MODE_SLIP6
2493 bool "Six bit SLIP encapsulation"
2496 Just occasionally you may need to run IP over hostile serial
2497 networks that don't pass all control characters or are only seven
2498 bit. Saying Y here adds an extra mode you can use with SLIP:
2499 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2500 the serial device. Naturally, this has to be supported at the other
2501 end of the link as well. It's good enough, for example, to run IP
2502 over the async ports of a Camtec JNT Pad. If unsure, say N.
2505 bool "Fibre Channel driver support"
2506 depends on NETDEVICES && SCSI && PCI
2508 Fibre Channel is a high speed serial protocol mainly used to connect
2509 large storage devices to the computer; it is compatible with and
2510 intended to replace SCSI.
2512 If you intend to use Fibre Channel, you need to have a Fibre channel
2513 adaptor card in your computer; say Y here and to the driver for your
2514 adaptor below. You also should have said Y to "SCSI support" and
2515 "SCSI generic support".
2518 tristate "Interphase 5526 Tachyon chipset based adapter support"
2519 depends on NET_FC && SCSI && PCI && BROKEN
2521 Say Y here if you have a Fibre Channel adaptor of this kind.
2523 To compile this driver as a module, choose M here: the module
2524 will be called iph5526.
2527 tristate "Traffic Shaper (EXPERIMENTAL)"
2528 depends on NETDEVICES && EXPERIMENTAL
2530 The traffic shaper is a virtual network device that allows you to
2531 limit the rate of outgoing data flow over some other network device.
2532 The traffic that you want to slow down can then be routed through
2533 these virtual devices. See
2534 <file:Documentation/networking/shaper.txt> for more information.
2536 An alternative to this traffic shaper is the experimental
2537 Class-Based Queueing (CBQ) scheduling support which you get if you
2538 say Y to "QoS and/or fair queueing" above.
2540 To set up and configure shaper devices, you need the shapecfg
2541 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2544 To compile this driver as a module, choose M here: the module
2545 will be called shaper. If unsure, say N.
2548 tristate "Network console logging support (EXPERIMENTAL)"
2549 depends on NETDEVICES && EXPERIMENTAL
2551 If you want to log kernel messages over the network, enable this.
2552 See Documentation/networking/netconsole.txt for details.