| blob | 072091ba79206d328c1564f279fc7c7fee825812 |
2 #
3 # Network device configuration
4 #
6 config NETDEVICES
7 depends on NET
8 bool "Network device support"
9 ---help---
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>.
22 If unsure, say Y.
24 config DUMMY
25 tristate "Dummy net driver support"
26 depends on NETDEVICES
27 ---help---
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',
42 'dummy1' etc.
44 config BONDING
45 tristate "Bonding driver support"
46 depends on NETDEVICES
47 ---help---
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.
64 config EQUALIZER
65 tristate "EQL (serial line load balancing) support"
66 depends on NETDEVICES
67 ---help---
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.
84 config TUN
85 tristate "Universal TUN/TAP device driver support"
86 depends on NETDEVICES
87 ---help---
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
100 information.
102 To compile this driver as a module, choose M here: the module
103 will be called tun.
105 If you don't know what to use this for, you don't need it.
107 config ETHERTAP
108 tristate "Ethertap network tap"
109 depends on NETDEVICES && EXPERIMENTAL && NETLINK_DEV
110 ---help---
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.
130 config NET_SB1000
131 tristate "General Instruments Surfboard 1000"
132 depends on NETDEVICES && PNP
133 ---help---
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
146 found at:
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.
154 if NETDEVICES
155 source "drivers/net/arcnet/Kconfig"
156 endif
158 #
159 # Ethernet
160 #
162 menu "Ethernet (10 or 100Mbit)"
163 depends on NETDEVICES
165 config NET_ETHERNET
166 bool "Ethernet (10 or 100Mbit)"
167 ---help---
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.
191 config MII
192 tristate "Generic Media Independent Interface device support"
193 depends on NET_ETHERNET
194 help
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"
201 config MOXACPU_MAC
202 tristate "Moxa CPU ethernet support"
203 depends on NET_ETHERNET && ARCH_MOXACPU
205 config MACE
206 tristate "MACE (Power Mac ethernet) support"
207 depends on NET_ETHERNET && PPC_PMAC && PPC32
208 select CRC32
209 help
210 Power Macintoshes and clones with Ethernet built-in on the
211 motherboard will usually use a MACE (Medium Access Control for
212 Ethernet) interface. Say Y to include support for the MACE chip.
214 To compile this driver as a module, choose M here: the module
215 will be called mace.
217 config MACE_AAUI_PORT
218 bool "Use AAUI port instead of TP by default"
219 depends on MACE
220 help
221 Some Apple machines (notably the Apple Network Server) which use the
222 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
223 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
224 Y here if you have such a machine. If unsure, say N.
225 The driver will default to AAUI on ANS anyway, and if you use it as
226 a module, you can provide the port_aaui=0|1 to force the driver.
228 config BMAC
229 tristate "BMAC (G3 ethernet) support"
230 depends on NET_ETHERNET && PPC_PMAC && PPC32
231 select CRC32
232 help
233 Say Y for support of BMAC Ethernet interfaces. These are used on G3
234 computers.
236 To compile this driver as a module, choose M here: the module
237 will be called bmac.
239 config OAKNET
240 tristate "National DP83902AV (Oak ethernet) support"
241 depends on NET_ETHERNET && PPC && BROKEN
242 select CRC32
243 help
244 Say Y if your machine has this type of Ethernet network card.
246 To compile this driver as a module, choose M here: the module
247 will be called oaknet.
249 config ARIADNE
250 tristate "Ariadne support"
251 depends on NET_ETHERNET && ZORRO
252 help
253 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
254 Otherwise, say N.
256 To compile this driver as a module, choose M here: the module
257 will be called ariadne.
259 config A2065
260 tristate "A2065 support"
261 depends on NET_ETHERNET && ZORRO
262 select CRC32
263 help
264 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
265 say N.
267 To compile this driver as a module, choose M here: the module
268 will be called a2065.
270 config HYDRA
271 tristate "Hydra support"
272 depends on NET_ETHERNET && ZORRO
273 select CRC32
274 help
275 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
277 To compile this driver as a module, choose M here: the module
278 will be called hydra.
280 config ZORRO8390
281 tristate "Zorro NS8390-based Ethernet support"
282 depends on NET_ETHERNET && ZORRO
283 select CRC32
284 help
285 This driver is for Zorro Ethernet cards using an NS8390-compatible
286 chipset, like the Village Tronic Ariadne II and the Individual
287 Computers X-Surf Ethernet cards. If you have such a card, say Y.
288 Otherwise, say N.
290 To compile this driver as a module, choose M here: the module
291 will be called zorro8390.
293 config APNE
294 tristate "PCMCIA NE2000 support"
295 depends on NETDEVICES && AMIGA_PCMCIA
296 select CRC32
297 help
298 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
299 say N.
301 To compile this driver as a module, choose M here: the module
302 will be called apne.
304 config APOLLO_ELPLUS
305 tristate "Apollo 3c505 support"
306 depends on NETDEVICES && APOLLO
307 help
308 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
309 If you don't have one made for Apollos, you can use one from a PC,
310 except that your Apollo won't be able to boot from it (because the
311 code in the ROM will be for a PC).
313 config MAC8390
314 bool "Macintosh NS 8390 based ethernet cards"
315 depends on NETDEVICES && MAC
316 select CRC32
317 help
318 If you want to include a driver to support Nubus or LC-PDS
319 Ethernet cards using an NS8390 chipset or its equivalent, say Y
320 and read the Ethernet-HOWTO, available from
321 <http://www.tldp.org/docs.html#howto>.
323 config MAC89x0
324 tristate "Macintosh CS89x0 based ethernet cards"
325 depends on NETDEVICES && MAC && BROKEN
326 ---help---
327 Support for CS89x0 chipset based Ethernet cards. If you have a
328 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
329 read the Ethernet-HOWTO, available from
330 <http://www.tldp.org/docs.html#howto>.
332 To compile this driver as a module, choose M here and read
333 <file:Documentation/networking/net-modules.txt>. This module will
334 be called mac89x0.
336 config MACSONIC
337 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
338 depends on NETDEVICES && MAC
339 ---help---
340 Support for NatSemi SONIC based Ethernet devices. This includes
341 the onboard Ethernet in many Quadras as well as some LC-PDS,
342 a few Nubus and all known Comm Slot Ethernet cards. If you have
343 one of these say Y and read the Ethernet-HOWTO, available from
344 <http://www.tldp.org/docs.html#howto>.
346 To compile this driver as a module, choose M here and read
347 <file:Documentation/networking/net-modules.txt>. This module will
348 be called macsonic.
350 config MACMACE
351 bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
352 depends on NETDEVICES && MAC && EXPERIMENTAL
353 select CRC32
354 help
355 Support for the onboard AMD 79C940 MACE Ethernet controller used in
356 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
357 say Y and read the Ethernet-HOWTO, available from
358 <http://www.tldp.org/docs.html#howto>.
360 config MVME147_NET
361 tristate "MVME147 (Lance) Ethernet support"
362 depends on NETDEVICES && MVME147
363 select CRC32
364 help
365 Support for the on-board Ethernet interface on the Motorola MVME147
366 single-board computer. Say Y here to include the
367 driver for this chip in your kernel.
368 To compile this driver as a module, choose M here.
370 config MVME16x_NET
371 tristate "MVME16x Ethernet support"
372 depends on NETDEVICES && MVME16x
373 help
374 This is the driver for the Ethernet interface on the Motorola
375 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
376 driver for this chip in your kernel.
377 To compile this driver as a module, choose M here.
379 config BVME6000_NET
380 tristate "BVME6000 Ethernet support"
381 depends on NETDEVICES && BVME6000
382 help
383 This is the driver for the Ethernet interface on BVME4000 and
384 BVME6000 VME boards. Say Y here to include the driver for this chip
385 in your kernel.
386 To compile this driver as a module, choose M here.
388 config ATARILANCE
389 tristate "Atari Lance support"
390 depends on NETDEVICES && ATARI
391 help
392 Say Y to include support for several Atari Ethernet adapters based
393 on the AMD Lance chipset: RieblCard (with or without battery), or
394 PAMCard VME (also the version by Rhotron, with different addresses).
396 config ATARI_BIONET
397 tristate "BioNet-100 support"
398 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
399 help
400 Say Y to include support for BioData's BioNet-100 Ethernet adapter
401 for the ACSI port. The driver works (has to work...) with a polled
402 I/O scheme, so it's rather slow :-(
404 config ATARI_PAMSNET
405 tristate "PAMsNet support"
406 depends on NETDEVICES && ATARI && ATARI_ACSI!=n && BROKEN
407 help
408 Say Y to include support for the PAMsNet Ethernet adapter for the
409 ACSI port ("ACSI node"). The driver works (has to work...) with a
410 polled I/O scheme, so it's rather slow :-(
412 config SUN3LANCE
413 tristate "Sun3/Sun3x on-board LANCE support"
414 depends on NETDEVICES && (SUN3 || SUN3X)
415 help
416 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
417 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
418 here to compile in the Linux driver for this and enable Ethernet.
419 General Linux information on the Sun 3 and 3x series (now
420 discontinued) is at
421 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
423 If you're not building a kernel for a Sun 3, say N.
425 config SUN3_82586
426 tristate "Sun3 on-board Intel 82586 support"
427 depends on NETDEVICES && SUN3
428 help
429 This driver enables support for the on-board Intel 82586 based
430 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
431 that this driver does not support 82586-based adapters on additional
432 VME boards.
434 config HPLANCE
435 bool "HP on-board LANCE support"
436 depends on NETDEVICES && HP300
437 select CRC32
438 help
439 If you want to use the builtin "LANCE" Ethernet controller on an
440 HP300 machine, say Y here.
442 config LASI_82596
443 tristate "Lasi ethernet"
444 depends on NET_ETHERNET && PARISC && GSC_LASI
445 help
446 Say Y here to support the on-board Intel 82596 ethernet controller
447 built into Hewlett-Packard PA-RISC machines.
449 config MIPS_JAZZ_SONIC
450 tristate "MIPS JAZZ onboard SONIC Ethernet support"
451 depends on NET_ETHERNET && MIPS_JAZZ
452 help
453 This is the driver for the onboard card of MIPS Magnum 4000,
454 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
456 config MIPS_GT96100ETH
457 bool "MIPS GT96100 Ethernet support"
458 depends on NET_ETHERNET && MIPS_GT96100
459 help
460 Say Y here to support the Ethernet subsystem on your GT96100 card.
462 config MIPS_AU1X00_ENET
463 bool "MIPS AU1000 Ethernet support"
464 depends on NET_ETHERNET && SOC_AU1X00
465 select CRC32
466 help
467 If you have an Alchemy Semi AU1X00 based system
468 say Y. Otherwise, say N.
470 config NET_SB1250_MAC
471 tristate "SB1250 Ethernet support"
472 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
474 config SGI_IOC3_ETH
475 bool "SGI IOC3 Ethernet"
476 depends on NET_ETHERNET && SGI_IP27
477 select CRC32
478 select MII
479 help
480 If you have a network (Ethernet) card of this type, say Y and read
481 the Ethernet-HOWTO, available from
482 <http://www.tldp.org/docs.html#howto>.
484 config SGI_IOC3_ETH_HW_RX_CSUM
485 bool "Receive hardware checksums"
486 depends on SGI_IOC3_ETH && INET
487 default y
488 help
489 The SGI IOC3 network adapter supports TCP and UDP checksums in
490 hardware to offload processing of these checksums from the CPU. At
491 the moment only acceleration of IPv4 is supported. This option
492 enables offloading for checksums on receive. If unsure, say Y.
494 config SGI_IOC3_ETH_HW_TX_CSUM
495 bool "Transmit hardware checksums"
496 depends on SGI_IOC3_ETH && INET
497 default y
498 help
499 The SGI IOC3 network adapter supports TCP and UDP checksums in
500 hardware to offload processing of these checksums from the CPU. At
501 the moment only acceleration of IPv4 is supported. This option
502 enables offloading for checksums on transmit. If unsure, say Y.
504 config SGI_O2MACE_ETH
505 tristate "SGI O2 MACE Fast Ethernet support"
506 depends on NET_ETHERNET && SGI_IP32=y
508 config STNIC
509 tristate "National DP83902AV support"
510 depends on NET_ETHERNET && SUPERH
511 select CRC32
512 help
513 Support for cards based on the National Semiconductor DP83902AV
514 ST-NIC Serial Network Interface Controller for Twisted Pair. This
515 is a 10Mbit/sec Ethernet controller. Product overview and specs at
516 <http://www.national.com/pf/DP/DP83902A.html>.
518 If unsure, say N.
520 config SUNLANCE
521 tristate "Sun LANCE support"
522 depends on NET_ETHERNET && SBUS
523 select CRC32
524 help
525 This driver supports the "le" interface present on all 32-bit Sparc
526 systems, on some older Ultra systems and as an Sbus option. These
527 cards are based on the AMD Lance chipset, which is better known
528 via the NE2100 cards.
530 To compile this driver as a module, choose M here: the module
531 will be called sunlance.
533 config HAPPYMEAL
534 tristate "Sun Happy Meal 10/100baseT support"
535 depends on NET_ETHERNET && (SBUS || PCI)
536 select CRC32
537 help
538 This driver supports the "hme" interface present on most Ultra
539 systems and as an option on older Sbus systems. This driver supports
540 both PCI and Sbus devices. This driver also supports the "qfe" quad
541 100baseT device available in both PCI and Sbus configurations.
543 To compile this driver as a module, choose M here: the module
544 will be called sunhme.
546 config SUNBMAC
547 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
548 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
549 select CRC32
550 help
551 This driver supports the "be" interface available as an Sbus option.
552 This is Sun's older 100baseT Ethernet device.
554 To compile this driver as a module, choose M here: the module
555 will be called sunbmac.
557 config SUNQE
558 tristate "Sun QuadEthernet support"
559 depends on NET_ETHERNET && SBUS
560 select CRC32
561 help
562 This driver supports the "qe" 10baseT Ethernet device, available as
563 an Sbus option. Note that this is not the same as Quad FastEthernet
564 "qfe" which is supported by the Happy Meal driver instead.
566 To compile this driver as a module, choose M here: the module
567 will be called sunqe.
569 config SUNGEM
570 tristate "Sun GEM support"
571 depends on NET_ETHERNET && PCI
572 select CRC32
573 help
574 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
575 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
577 config NET_VENDOR_3COM
578 bool "3COM cards"
579 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
580 help
581 If you have a network (Ethernet) card belonging to this class, say Y
582 and read the Ethernet-HOWTO, available from
583 <http://www.tldp.org/docs.html#howto>.
585 Note that the answer to this question doesn't directly affect the
586 kernel: saying N will just cause the configurator to skip all
587 the questions about 3COM cards. If you say Y, you will be asked for
588 your specific card in the following questions.
590 config EL1
591 tristate "3c501 \"EtherLink\" support"
592 depends on NET_VENDOR_3COM && ISA
593 ---help---
594 If you have a network (Ethernet) card of this type, say Y and read
595 the Ethernet-HOWTO, available from
596 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
597 new card, since the 3c501 is slow, broken, and obsolete: you will
598 have problems. Some people suggest to ping ("man ping") a nearby
599 machine every minute ("man cron") when using this card.
601 To compile this driver as a module, choose M here and read
602 <file:Documentation/networking/net-modules.txt>. The module
603 will be called 3c501.
605 config EL2
606 tristate "3c503 \"EtherLink II\" support"
607 depends on NET_VENDOR_3COM && ISA
608 select CRC32
609 help
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 3c503.
618 config ELPLUS
619 tristate "3c505 \"EtherLink Plus\" support"
620 depends on NET_VENDOR_3COM && ISA
621 ---help---
622 Information about this network (Ethernet) card can be found in
623 <file:Documentation/networking/3c505.txt>. If you have a card of
624 this type, say Y and read the Ethernet-HOWTO, available from
625 <http://www.tldp.org/docs.html#howto>.
627 To compile this driver as a module, choose M here and read
628 <file:Documentation/networking/net-modules.txt>. The module
629 will be called 3c505.
631 config EL16
632 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
633 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
634 help
635 If you have a network (Ethernet) card of this type, say Y and read
636 the Ethernet-HOWTO, available from
637 <http://www.tldp.org/docs.html#howto>.
639 To compile this driver as a module, choose M here and read
640 <file:Documentation/networking/net-modules.txt>. The module
641 will be called 3c507.
643 config EL3
644 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support"
645 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
646 ---help---
647 If you have a network (Ethernet) card belonging to the 3Com
648 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
649 from <http://www.tldp.org/docs.html#howto>.
651 If your card is not working you may need to use the DOS
652 setup disk to disable Plug & Play mode, and to select the default
653 media type.
655 To compile this driver as a module, choose M here and read
656 <file:Documentation/networking/net-modules.txt>. The module
657 will be called 3c509.
659 config 3C515
660 tristate "3c515 ISA \"Fast EtherLink\""
661 depends on NET_VENDOR_3COM && (ISA || EISA)
662 help
663 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
664 network card, say Y and read the Ethernet-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>.
667 To compile this driver as a module, choose M here and read
668 <file:Documentation/networking/net-modules.txt>. The module
669 will be called 3c515.
671 config ELMC
672 tristate "3c523 \"EtherLink/MC\" support"
673 depends on NET_VENDOR_3COM && MCA_LEGACY
674 help
675 If you have a network (Ethernet) card of this type, say Y and read
676 the Ethernet-HOWTO, available from
677 <http://www.tldp.org/docs.html#howto>.
679 To compile this driver as a module, choose M here and read
680 <file:Documentation/networking/net-modules.txt>. The module
681 will be called 3c523.
683 config ELMC_II
684 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
685 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
686 help
687 If you have a network (Ethernet) card of this type, say Y and read
688 the Ethernet-HOWTO, available from
689 <http://www.tldp.org/docs.html#howto>.
691 To compile this driver as a module, choose M here and read
692 <file:Documentation/networking/net-modules.txt>. The module
693 will be called 3c527.
695 config VORTEX
696 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
697 depends on NET_VENDOR_3COM && (PCI || EISA)
698 ---help---
699 This option enables driver support for a large number of 10mbps and
700 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
702 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
703 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
704 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
705 "Tornado" (3c905) PCI
706 "Hurricane" (3c555/3cSOHO) PCI
708 If you have such a card, say Y and read the Ethernet-HOWTO,
709 available from <http://www.tldp.org/docs.html#howto>. More
710 specific information is in
711 <file:Documentation/networking/vortex.txt> and in the comments at
712 the beginning of <file:drivers/net/3c59x.c>.
714 To compile this support as a module, choose M here and read
715 <file:Documentation/networking/net-modules.txt>.
717 config TYPHOON
718 tristate "3cr990 series \"Typhoon\" support"
719 depends on NET_VENDOR_3COM && PCI
720 select CRC32
721 ---help---
722 This option enables driver support for the 3cr990 series of cards:
724 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
725 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
726 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
728 If you have a network (Ethernet) card of this type, say Y and read
729 the Ethernet-HOWTO, available from
730 <http://www.tldp.org/docs.html#howto>.
732 To compile this driver as a module, choose M here and read
733 <file:Documentation/networking/net-modules.txt>. The module
734 will be called typhoon.
736 config LANCE
737 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
738 depends on NET_ETHERNET && ISA
739 help
740 If you have a network (Ethernet) card of this type, say Y and read
741 the Ethernet-HOWTO, available from
742 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
743 of this type.
745 To compile this driver as a module, choose M here: the module
746 will be called lance. This is recommended.
748 config NET_VENDOR_SMC
749 bool "Western Digital/SMC cards"
750 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC || EMBEDDED)
751 help
752 If you have a network (Ethernet) card belonging to this class, say Y
753 and read the Ethernet-HOWTO, available from
754 <http://www.tldp.org/docs.html#howto>.
756 Note that the answer to this question doesn't directly affect the
757 kernel: saying N will just cause the configurator to skip all
758 the questions about Western Digital cards. If you say Y, you will be
759 asked for your specific card in the following questions.
761 config WD80x3
762 tristate "WD80*3 support"
763 depends on NET_VENDOR_SMC && ISA
764 select CRC32
765 help
766 If you have a network (Ethernet) card of this type, say Y and read
767 the Ethernet-HOWTO, available from
768 <http://www.tldp.org/docs.html#howto>.
770 To compile this driver as a module, choose M here and read
771 <file:Documentation/networking/net-modules.txt>. The module
772 will be called wd.
774 config ULTRAMCA
775 tristate "SMC Ultra MCA support"
776 depends on NET_VENDOR_SMC && MCA
777 select CRC32
778 help
779 If you have a network (Ethernet) card of this type and are running
780 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
781 available from <http://www.tldp.org/docs.html#howto>.
783 To compile this driver as a module, choose M here and read
784 <file:Documentation/networking/net-modules.txt>. The module
785 will be called smc-mca.
787 config ULTRA
788 tristate "SMC Ultra support"
789 depends on NET_VENDOR_SMC && ISA
790 select CRC32
791 ---help---
792 If you have a network (Ethernet) card of this type, say Y and read
793 the Ethernet-HOWTO, available from
794 <http://www.tldp.org/docs.html#howto>.
796 Important: There have been many reports that, with some motherboards
797 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
798 such as some BusLogic models) causes corruption problems with many
799 operating systems. The Linux smc-ultra driver has a work-around for
800 this but keep it in mind if you have such a SCSI card and have
801 problems.
803 To compile this driver as a module, choose M here and read
804 <file:Documentation/networking/net-modules.txt>. The module
805 will be called smc-ultra.
807 config ULTRA32
808 tristate "SMC Ultra32 EISA support"
809 depends on NET_VENDOR_SMC && EISA
810 select CRC32
811 help
812 If you have a network (Ethernet) card of this type, say Y and read
813 the Ethernet-HOWTO, available from
814 <http://www.tldp.org/docs.html#howto>.
816 To compile this driver as a module, choose M here and read
817 <file:Documentation/networking/net-modules.txt>. The module
818 will be called smc-ultra32.
820 config SMC91X
821 tristate "SMC 91C9x/91C1xxx support"
822 select CRC32
823 select MII
824 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R)
825 help
826 This is a driver for SMC's 91x series of Ethernet chipsets,
827 including the SMC91C94 and the SMC91C111. Say Y if you want it
828 compiled into the kernel, and read the file
829 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
830 available from <http://www.linuxdoc.org/docs.html#howto>.
832 This driver is also available as a module ( = code which can be
833 inserted in and removed from the running kernel whenever you want).
834 The module will be called smc91x. If you want to compile it as a
835 module, say M here and read <file:Documentation/modules.txt> as well
836 as <file:Documentation/networking/net-modules.txt>.
838 config SMC9194
839 tristate "SMC 9194 support"
840 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN || EMBEDDED)
841 select CRC32
842 ---help---
843 This is support for the SMC9xxx based Ethernet cards. Choose this
844 option if you have a DELL laptop with the docking station, or
845 another SMC9192/9194 based chipset. Say Y if you want it compiled
846 into the kernel, and read the file
847 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
848 available from <http://www.tldp.org/docs.html#howto>.
850 To compile this driver as a module, choose M here and read
851 <file:Documentation/networking/net-modules.txt>. The module
852 will be called smc9194.
854 config NET_VENDOR_RACAL
855 bool "Racal-Interlan (Micom) NI cards"
856 depends on NET_ETHERNET && ISA
857 help
858 If you have a network (Ethernet) card belonging to this class, such
859 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
860 available from <http://www.tldp.org/docs.html#howto>.
862 Note that the answer to this question doesn't directly affect the
863 kernel: saying N will just cause the configurator to skip all
864 the questions about NI cards. If you say Y, you will be asked for
865 your specific card in the following questions.
867 config NI5010
868 tristate "NI5010 support (EXPERIMENTAL)"
869 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
870 ---help---
871 If you have a network (Ethernet) card of this type, say Y and read
872 the Ethernet-HOWTO, available from
873 <http://www.tldp.org/docs.html#howto>. Note that this is still
874 experimental code.
876 To compile this driver as a module, choose M here and read
877 <file:Documentation/networking/net-modules.txt>. The module
878 will be called ni5010.
880 config NI52
881 tristate "NI5210 support"
882 depends on NET_VENDOR_RACAL && ISA
883 help
884 If you have a network (Ethernet) card of this type, say Y and read
885 the Ethernet-HOWTO, available from
886 <http://www.tldp.org/docs.html#howto>.
888 To compile this driver as a module, choose M here and read
889 <file:Documentation/networking/net-modules.txt>. The module
890 will be called ni52.
892 config NI65
893 tristate "NI6510 support"
894 depends on NET_VENDOR_RACAL && ISA
895 help
896 If you have a network (Ethernet) card of this type, say Y and read
897 the Ethernet-HOWTO, available from
898 <http://www.tldp.org/docs.html#howto>.
900 To compile this driver as a module, choose M here and read
901 <file:Documentation/networking/net-modules.txt>. The module
902 will be called ni65.
904 source "drivers/net/tulip/Kconfig"
906 config AT1700
907 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)"
908 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
909 select CRC32
910 ---help---
911 If you have a network (Ethernet) card of this type, say Y and read
912 the Ethernet-HOWTO, available from
913 <http://www.tldp.org/docs.html#howto>.
915 To compile this driver as a module, choose M here and read
916 <file:Documentation/networking/net-modules.txt>. The module
917 will be called at1700.
919 config DEPCA
920 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
921 depends on NET_ETHERNET && (ISA || EISA || MCA)
922 select CRC32
923 ---help---
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> as well as
927 <file:drivers/net/depca.c>.
929 To compile this driver as a module, choose M here and read
930 <file:Documentation/networking/net-modules.txt>. The module
931 will be called depca.
933 config HP100
934 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
935 depends on NET_ETHERNET && (ISA || EISA || PCI)
936 help
937 If you have a network (Ethernet) card of this type, say Y and read
938 the Ethernet-HOWTO, available from
939 <http://www.tldp.org/docs.html#howto>.
941 To compile this driver as a module, choose M here and read
942 <file:Documentation/networking/net-modules.txt>. The module
943 will be called hp100.
945 config NET_ISA
946 bool "Other ISA cards"
947 depends on NET_ETHERNET && ISA
948 ---help---
949 If your network (Ethernet) card hasn't been mentioned yet and its
950 bus system (that's the way the cards talks to the other components
951 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
952 Make sure you know the name of your card. Read the Ethernet-HOWTO,
953 available from <http://www.tldp.org/docs.html#howto>.
955 If unsure, say Y.
957 Note that the answer to this question doesn't directly affect the
958 kernel: saying N will just cause the configurator to skip all
959 the remaining ISA network card questions. If you say Y, you will be
960 asked for your specific card in the following questions.
962 config E2100
963 tristate "Cabletron E21xx support"
964 depends on NET_ISA
965 select CRC32
966 help
967 If you have a network (Ethernet) card of this type, say Y and read
968 the Ethernet-HOWTO, available from
969 <http://www.tldp.org/docs.html#howto>.
971 To compile this driver as a module, choose M here and read
972 <file:Documentation/networking/net-modules.txt>. The module
973 will be called e2100.
975 config EWRK3
976 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
977 depends on NET_ISA
978 select CRC32
979 ---help---
980 This driver supports the DE203, DE204 and DE205 network (Ethernet)
981 cards. If this is for you, say Y and read
982 <file:Documentation/networking/ewrk3.txt> in the kernel source as
983 well as the Ethernet-HOWTO, available from
984 <http://www.tldp.org/docs.html#howto>.
986 To compile this driver as a module, choose M here and read
987 <file:Documentation/networking/net-modules.txt>. The module
988 will be called ewrk3.
990 config EEXPRESS
991 tristate "EtherExpress 16 support"
992 depends on NET_ISA
993 ---help---
994 If you have an EtherExpress16 network (Ethernet) card, say Y and
995 read the Ethernet-HOWTO, available from
996 <http://www.tldp.org/docs.html#howto>. Note that the Intel
997 EtherExpress16 card used to be regarded as a very poor choice
998 because the driver was very unreliable. We now have a new driver
999 that should do better.
1001 To compile this driver as a module, choose M here and read
1002 <file:Documentation/networking/net-modules.txt>. The module
1003 will be called eexpress.
1005 config EEXPRESS_PRO
1006 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1007 depends on NET_ISA
1008 ---help---
1009 If you have a network (Ethernet) card of this type, say Y. This
1010 driver supports intel i82595{FX,TX} based boards. Note however
1011 that the EtherExpress PRO/100 Ethernet card has its own separate
1012 driver. Please read the Ethernet-HOWTO, available from
1013 <http://www.tldp.org/docs.html#howto>.
1015 To compile this driver as a module, choose M here and read
1016 <file:Documentation/networking/net-modules.txt>. The module
1017 will be called eepro.
1019 config FMV18X
1020 tristate "FMV-181/182/183/184 support (OBSOLETE)"
1021 depends on NET_ISA && OBSOLETE
1022 ---help---
1023 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
1024 say Y and read the Ethernet-HOWTO, available from
1025 <http://www.tldp.org/docs.html#howto>.
1027 If you use an FMV-183 or FMV-184 and it is not working, you may need
1028 to disable Plug & Play mode of the card.
1030 To compile this driver as a module, choose M here and read
1031 <file:Documentation/networking/net-modules.txt>. The module
1032 will be called fmv18x.
1034 config HPLAN_PLUS
1035 tristate "HP PCLAN+ (27247B and 27252A) support"
1036 depends on NET_ISA
1037 select CRC32
1038 help
1039 If you have a network (Ethernet) card of this type, say Y and read
1040 the Ethernet-HOWTO, available from
1041 <http://www.tldp.org/docs.html#howto>.
1043 To compile this driver as a module, choose M here and read
1044 <file:Documentation/networking/net-modules.txt>. The module
1045 will be called hp-plus.
1047 config HPLAN
1048 tristate "HP PCLAN (27245 and other 27xxx series) support"
1049 depends on NET_ISA
1050 select CRC32
1051 help
1052 If you have a network (Ethernet) card of this type, say Y and read
1053 the Ethernet-HOWTO, available from
1054 <http://www.tldp.org/docs.html#howto>.
1056 To compile this driver as a module, choose M here and read
1057 <file:Documentation/networking/net-modules.txt>. The module
1058 will be called hp.
1060 config LP486E
1061 tristate "LP486E on board Ethernet"
1062 depends on NET_ISA
1063 help
1064 Say Y here to support the 82596-based on-board Ethernet controller
1065 for the Panther motherboard, which is one of the two shipped in the
1066 Intel Professional Workstation.
1068 config ETH16I
1069 tristate "ICL EtherTeam 16i/32 support"
1070 depends on NET_ISA
1071 help
1072 If you have a network (Ethernet) card of this type, say Y and read
1073 the Ethernet-HOWTO, available from
1074 <http://www.tldp.org/docs.html#howto>.
1076 To compile this driver as a module, choose M here and read
1077 <file:Documentation/networking/net-modules.txt>. The module
1078 will be called eth16i.
1080 config NE2000
1081 tristate "NE2000/NE1000 support"
1082 depends on NET_ISA || (Q40 && m) || M32R || EMBEDDED
1083 select CRC32
1084 ---help---
1085 If you have a network (Ethernet) card of this type, say Y and read
1086 the Ethernet-HOWTO, available from
1087 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1088 without a specific driver are compatible with NE2000.
1090 If you have a PCI NE2000 card however, say N here and Y to "PCI
1091 NE2000 support", above. If you have a NE2000 card and are running on
1092 an MCA system (a bus system used on some IBM PS/2 computers and
1093 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1094 below.
1096 To compile this driver as a module, choose M here and read
1097 <file:Documentation/networking/net-modules.txt>. The module
1098 will be called ne.
1100 config ZNET
1101 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1102 depends on NET_ISA && EXPERIMENTAL
1103 help
1104 The Zenith Z-Note notebook computer has a built-in network
1105 (Ethernet) card, and this is the Linux driver for it. Note that the
1106 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1107 by this driver. Read the Ethernet-HOWTO, available from
1108 <http://www.tldp.org/docs.html#howto>.
1110 config SEEQ8005
1111 tristate "SEEQ8005 support (EXPERIMENTAL)"
1112 depends on NET_ISA && EXPERIMENTAL
1113 help
1114 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1115 is for you, read the Ethernet-HOWTO, available from
1116 <http://www.tldp.org/docs.html#howto>.
1118 To compile this driver as a module, choose M here and read
1119 <file:Documentation/networking/net-modules.txt>. The module
1120 will be called seeq8005.
1122 config SK_G16
1123 tristate "SK_G16 support (OBSOLETE)"
1124 depends on NET_ISA && OBSOLETE
1125 help
1126 If you have a network (Ethernet) card of this type, say Y and read
1127 the Ethernet-HOWTO, available from
1128 <http://www.tldp.org/docs.html#howto>.
1130 config SKMC
1131 tristate "SKnet MCA support"
1132 depends on NET_ETHERNET && MCA && BROKEN
1133 ---help---
1134 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1135 support" in order to use this driver. Supported cards are the SKnet
1136 Junior MC2 and the SKnet MC2(+). The driver automatically
1137 distinguishes between the two cards. Note that using multiple boards
1138 of different type hasn't been tested with this driver. Say Y if you
1139 have one of these Ethernet adapters.
1141 To compile this driver as a module, choose M here and read
1142 <file:Documentation/networking/net-modules.txt>. The module
1143 will be called sk_mca.
1145 config NE2_MCA
1146 tristate "NE/2 (ne2000 MCA version) support"
1147 depends on NET_ETHERNET && MCA_LEGACY
1148 select CRC32
1149 help
1150 If you have a network (Ethernet) card of this type, say Y and read
1151 the Ethernet-HOWTO, available from
1152 <http://www.tldp.org/docs.html#howto>.
1154 To compile this driver as a module, choose M here and read
1155 <file:Documentation/networking/net-modules.txt>. The module
1156 will be called ne2.
1158 config IBMLANA
1159 tristate "IBM LAN Adapter/A support"
1160 depends on NET_ETHERNET && MCA && MCA_LEGACY
1161 ---help---
1162 This is a Micro Channel Ethernet adapter. You need to set
1163 CONFIG_MCA to use this driver. It is both available as an in-kernel
1164 driver and as a module.
1166 To compile this driver as a module, choose M here and read
1167 <file:Documentation/networking/net-modules.txt>. The only
1168 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1169 will both support 16K and 32K memory windows, however a 32K window
1170 gives a better security against packet losses. Usage of multiple
1171 boards with this driver should be possible, but has not been tested
1172 up to now due to lack of hardware.
1174 config IBMVETH
1175 tristate "IBM LAN Virtual Ethernet support"
1176 depends on NETDEVICES && NET_ETHERNET && PPC_PSERIES
1177 ---help---
1178 This driver supports virtual ethernet adapters on newer IBM iSeries
1179 and pSeries systems.
1181 To compile this driver as a module, choose M here and read
1182 <file:Documentation/networking/net-modules.txt>. The module will
1183 be called ibmveth.
1185 config IBM_EMAC
1186 tristate "IBM PPC4xx EMAC driver support"
1187 depends on 4xx
1188 ---help---
1189 This driver supports the IBM PPC4xx EMAC family of on-chip
1190 Ethernet controllers.
1192 config IBM_EMAC_ERRMSG
1193 bool "Verbose error messages"
1194 depends on IBM_EMAC
1196 config IBM_EMAC_RXB
1197 int "Number of receive buffers"
1198 depends on IBM_EMAC
1199 default "128" if IBM_EMAC4
1200 default "64"
1202 config IBM_EMAC_TXB
1203 int "Number of transmit buffers"
1204 depends on IBM_EMAC
1205 default "128" if IBM_EMAC4
1206 default "8"
1208 config IBM_EMAC_FGAP
1209 int "Frame gap"
1210 depends on IBM_EMAC
1211 default "8"
1213 config IBM_EMAC_SKBRES
1214 int "Skb reserve amount"
1215 depends on IBM_EMAC
1216 default "0"
1218 config NET_PCI
1219 bool "EISA, VLB, PCI and on board controllers"
1220 depends on NET_ETHERNET && (ISA || EISA || PCI)
1221 help
1222 This is another class of network cards which attach directly to the
1223 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1224 available from <http://www.tldp.org/docs.html#howto>.
1226 Note that the answer to this question doesn't directly affect the
1227 kernel: saying N will just cause the configurator to skip all
1228 the questions about this class of network cards. If you say Y, you
1229 will be asked for your specific card in the following questions. If
1230 you are unsure, say Y.
1232 config PCNET32
1233 tristate "AMD PCnet32 PCI support"
1234 depends on NET_PCI && PCI
1235 select CRC32
1236 select MII
1237 help
1238 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1239 answer Y here and read the Ethernet-HOWTO, available from
1240 <http://www.tldp.org/docs.html#howto>.
1242 To compile this driver as a module, choose M here and read
1243 <file:Documentation/networking/net-modules.txt>. The module
1244 will be called pcnet32.
1246 config AMD8111_ETH
1247 tristate "AMD 8111 (new PCI lance) support"
1248 depends on NET_PCI && PCI
1249 select CRC32
1250 select MII
1251 help
1252 If you have an AMD 8111-based PCI lance ethernet card,
1253 answer Y here and read the Ethernet-HOWTO, available from
1254 <http://www.tldp.org/docs.html#howto>.
1256 To compile this driver as a module, choose M here and read
1257 <file:Documentation/networking/net-modules.txt>. The module
1258 will be called amd8111e.
1259 config AMD8111E_NAPI
1260 bool "Enable NAPI support"
1261 depends on AMD8111_ETH
1262 help
1263 NAPI is a new driver API designed to reduce CPU and interrupt load
1264 when the driver is receiving lots of packets from the card. It is
1265 still somewhat experimental and thus not yet enabled by default.
1267 If your estimated Rx load is 10kpps or more, or if the card will be
1268 deployed on potentially unfriendly networks (e.g. in a firewall),
1269 then say Y here.
1271 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1272 information.
1274 If in doubt, say N.
1276 config ADAPTEC_STARFIRE
1277 tristate "Adaptec Starfire/DuraLAN support"
1278 depends on NET_PCI && PCI
1279 select CRC32
1280 select MII
1281 help
1282 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1283 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1284 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1285 driver.
1287 To compile this driver as a module, choose M here: the module
1288 will be called starfire. This is recommended.
1290 config ADAPTEC_STARFIRE_NAPI
1291 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1292 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1293 help
1294 NAPI is a new driver API designed to reduce CPU and interrupt load
1295 when the driver is receiving lots of packets from the card. It is
1296 still somewhat experimental and thus not yet enabled by default.
1298 If your estimated Rx load is 10kpps or more, or if the card will be
1299 deployed on potentially unfriendly networks (e.g. in a firewall),
1300 then say Y here.
1302 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1303 information.
1305 If in doubt, say N.
1307 config AC3200
1308 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1309 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1310 select CRC32
1311 help
1312 If you have a network (Ethernet) card of this type, say Y and read
1313 the Ethernet-HOWTO, available from
1314 <http://www.tldp.org/docs.html#howto>.
1316 To compile this driver as a module, choose M here and read
1317 <file:Documentation/networking/net-modules.txt>. The module
1318 will be called ac3200.
1320 config APRICOT
1321 tristate "Apricot Xen-II on board Ethernet"
1322 depends on NET_PCI && ISA
1323 help
1324 If you have a network (Ethernet) controller of this type, say Y and
1325 read the Ethernet-HOWTO, available from
1326 <http://www.tldp.org/docs.html#howto>.
1328 To compile this driver as a module, choose M here and read
1329 <file:Documentation/networking/net-modules.txt>. The module will be
1330 called apricot.
1332 config B44
1333 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1334 depends on NET_PCI && PCI && EXPERIMENTAL
1335 select MII
1336 help
1337 If you have a network (Ethernet) controller of this type, say Y and
1338 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 will be
1343 called b44.
1345 config FORCEDETH
1346 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1347 depends on NET_PCI && PCI && EXPERIMENTAL
1348 help
1349 If you have a network (Ethernet) controller of this type, say Y and
1350 read the Ethernet-HOWTO, available from
1351 <http://www.tldp.org/docs.html#howto>.
1353 To compile this driver as a module, choose M here and read
1354 <file:Documentation/networking/net-modules.txt>. The module will be
1355 called forcedeth.
1358 config CS89x0
1359 tristate "CS89x0 support"
1360 depends on NET_PCI && (ISA || ARCH_IXDP2X01 || M68328 || M68EZ328 || M68VZ328)
1361 ---help---
1362 Support for CS89x0 chipset based Ethernet cards. If you have a
1363 network (Ethernet) card of this type, say Y and read the
1364 Ethernet-HOWTO, available from
1365 <http://www.tldp.org/docs.html#howto> as well as
1366 <file:Documentation/networking/cs89x0.txt>.
1368 To compile this driver as a module, choose M here and read
1369 <file:Documentation/networking/net-modules.txt>. The module will be
1370 called cs89x.
1372 config CS89x0_SWAPPED
1373 bool "Hardware swapped CS89x0"
1374 depends on CS89x0 && !NET_PCI && !ISA
1375 ---help---
1376 Say Y if your CS89x0 data bus is swapped.
1377 This option is for single board computers using a CS89x0 chip. If you
1378 are using a regular Ethernet card, say N.
1380 config TC35815
1381 tristate "TOSHIBA TC35815 Ethernet support"
1382 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1384 config DGRS
1385 tristate "Digi Intl. RightSwitch SE-X support"
1386 depends on NET_PCI && (PCI || EISA)
1387 ---help---
1388 This is support for the Digi International RightSwitch series of
1389 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1390 models. If you have a network card of this type, say Y and read the
1391 Ethernet-HOWTO, available from
1392 <http://www.tldp.org/docs.html#howto>. More specific
1393 information is contained in <file:Documentation/networking/dgrs.txt>.
1395 To compile this driver as a module, choose M here and read
1396 <file:Documentation/networking/net-modules.txt>. The module
1397 will be called dgrs.
1399 config EEPRO100
1400 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1401 depends on NET_PCI && PCI
1402 select MII
1403 help
1404 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1405 card, say Y and read the Ethernet-HOWTO, available from
1406 <http://www.tldp.org/docs.html#howto>.
1408 To compile this driver as a module, choose M here and read
1409 <file:Documentation/networking/net-modules.txt>. The module
1410 will be called eepro100.
1413 config EEPRO100_PIO
1414 bool "Use PIO instead of MMIO" if !X86_VISWS
1415 depends on EEPRO100
1416 default y if X86_VISWS
1417 help
1418 This instructs the driver to use programmed I/O ports (PIO) instead
1419 of PCI shared memory (MMIO). This can possibly solve some problems
1420 in case your mainboard has memory consistency issues. If unsure,
1421 say N.
1423 config E100
1424 tristate "Intel(R) PRO/100+ support"
1425 depends on NET_PCI && PCI
1426 select MII
1427 ---help---
1428 This driver supports Intel(R) PRO/100 family of adapters, which
1429 includes:
1431 Controller Adapter Name Board IDs
1432 ---------- ------------ ---------
1434 82558 PRO/100+ PCI Adapter 668081-xxx,
1435 689661-xxx
1436 82558 PRO/100+ Management Adapter 691334-xxx,
1437 701738-xxx,
1438 721383-xxx
1439 82558 PRO/100+ Dual Port Server Adapter 714303-xxx,
1440 711269-xxx,
1441 A28276-xxx
1442 82558 PRO/100+ PCI Server Adapter 710550-xxx
1443 82550 PRO/100 S Server Adapter 752438-xxx
1444 82559 A56831-xxx,
1445 A10563-xxx,
1446 A12171-xxx,
1447 A12321-xxx,
1448 A12320-xxx,
1449 A12170-xxx
1450 748568-xxx
1451 748565-xxx
1452 82550 PRO/100 S Desktop Adapter 751767-xxx
1453 82559 748592-xxx,
1454 A12167-xxx,
1455 A12318-xxx,
1456 A12317-xxx,
1457 A12165-xxx,
1458 748569-xxx
1459 82559 PRO/100+ Server Adapter 729757-xxx
1460 82559 PRO/100 S Management Adapter 748566-xxx,
1461 748564-xxx
1462 82550 PRO/100 S Dual Port Server Adapter A56831-xxx
1463 82551 PRO/100 M Desktop Adapter A80897-xxx
1464 PRO/100 S Advanced Management Adapter
1465 747842-xxx,
1466 745171-xxx
1467 CNR PRO/100 VE Desktop Adapter A10386-xxx,
1468 A10725-xxx,
1469 A23801-xxx,
1470 A19716-xxx
1471 PRO/100 VM Desktop Adapter A14323-xxx,
1472 A19725-xxx,
1473 A23801-xxx,
1474 A22220-xxx,
1475 A23796-xxx
1478 To verify that your adapter is supported, find the board ID number
1479 on the adapter. Look for a label that has a barcode and a number
1480 in the format 123456-001 (six digits hyphen three digits). Match
1481 this to the list of numbers above.
1483 For more information on how to identify your adapter, go to the
1484 Adapter & Driver ID Guide at:
1486 http://support.intel.com/support/network/adapter/pro100/21397.htm
1488 For the latest Intel PRO/100 network driver for Linux, see:
1490 http://appsr.intel.com/scripts-df/support_intel.asp
1492 More specific information on configuring the driver is in
1493 <file:Documentation/networking/e100.txt>.
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 e100.
1499 config E100_NAPI
1500 bool "Use Rx Polling (NAPI)"
1501 depends on E100
1502 help
1503 NAPI is a new driver API designed to reduce CPU and interrupt load
1504 when the driver is receiving lots of packets from the card. It is
1505 still somewhat experimental and thus not yet enabled by default.
1507 If your estimated Rx load is 10kpps or more, or if the card will be
1508 deployed on potentially unfriendly networks (e.g. in a firewall),
1509 then say Y here.
1511 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1512 information.
1514 If in doubt, say N.
1516 config LNE390
1517 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1518 depends on NET_PCI && EISA && EXPERIMENTAL
1519 select CRC32
1520 help
1521 If you have a network (Ethernet) card of this type, say Y and read
1522 the Ethernet-HOWTO, available from
1523 <http://www.tldp.org/docs.html#howto>.
1525 To compile this driver as a module, choose M here and read
1526 <file:Documentation/networking/net-modules.txt>. The module
1527 will be called lne390.
1529 config FEALNX
1530 tristate "Myson MTD-8xx PCI Ethernet support"
1531 depends on NET_PCI && PCI
1532 select CRC32
1533 select MII
1534 help
1535 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1536 cards. Specifications and data at
1537 <http://www.myson.com.hk/mtd/datasheet/>.
1539 config NATSEMI
1540 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1541 depends on NET_PCI && PCI
1542 select CRC32
1543 help
1544 This driver is for the National Semiconductor DP83810 series,
1545 which is used in cards from PureData, NetGear, Linksys
1546 and others, including the 83815 chip.
1547 More specific information and updates are available from
1548 <http://www.scyld.com/network/natsemi.html>.
1550 config NE2K_PCI
1551 tristate "PCI NE2000 and clones support (see help)"
1552 depends on NET_PCI && PCI
1553 select CRC32
1554 ---help---
1555 This driver is for NE2000 compatible PCI cards. It will not work
1556 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1557 support" below). If you have a PCI NE2000 network (Ethernet) card,
1558 say Y and read the Ethernet-HOWTO, available from
1559 <http://www.tldp.org/docs.html#howto>.
1561 This driver also works for the following NE2000 clone cards:
1562 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1563 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1564 Holtek HT80232 Holtek HT80229
1566 To compile this driver as a module, choose M here and read
1567 <file:Documentation/networking/net-modules.txt>. The module
1568 will be called ne2k-pci.
1570 config NE3210
1571 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1572 depends on NET_PCI && EISA && EXPERIMENTAL
1573 select CRC32
1574 ---help---
1575 If you have a network (Ethernet) card of this type, say Y and read
1576 the Ethernet-HOWTO, available from
1577 <http://www.tldp.org/docs.html#howto>. Note that this driver
1578 will NOT WORK for NE3200 cards as they are completely different.
1580 To compile this driver as a module, choose M here and read
1581 <file:Documentation/networking/net-modules.txt>. The module
1582 will be called ne3210.
1584 config ES3210
1585 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1586 depends on NET_PCI && EISA && EXPERIMENTAL
1587 select CRC32
1588 help
1589 If you have a network (Ethernet) card of this type, say Y and read
1590 the Ethernet-HOWTO, available from
1591 <http://www.tldp.org/docs.html#howto>.
1593 To compile this driver as a module, choose M here and read
1594 <file:Documentation/networking/net-modules.txt>. The module
1595 will be called es3210.
1597 config 8139CP
1598 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1599 depends on NET_PCI && PCI && EXPERIMENTAL
1600 select CRC32
1601 select MII
1602 help
1603 This is a driver for the Fast Ethernet PCI network cards based on
1604 the RTL8139C+ chips. If you have one of those, say Y and read
1605 the Ethernet-HOWTO, available from
1606 <http://www.tldp.org/docs.html#howto>.
1608 To compile this driver as a module, choose M here: the module
1609 will be called 8139cp. This is recommended.
1611 config 8139TOO
1612 tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
1613 depends on NET_PCI && PCI
1614 select CRC32
1615 select MII
1616 ---help---
1617 This is a driver for the Fast Ethernet PCI network cards based on
1618 the RTL8139 chips. If you have one of those, say Y and read
1619 the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1621 To compile this driver as a module, choose M here: the module
1622 will be called 8139too. This is recommended.
1624 config 8139TOO_PIO
1625 bool "Use PIO instead of MMIO"
1626 default y
1627 depends on 8139TOO
1628 help
1629 This instructs the driver to use programmed I/O ports (PIO) instead
1630 of PCI shared memory (MMIO). This can possibly solve some problems
1631 in case your mainboard has memory consistency issues. If unsure,
1632 say N.
1634 config 8139TOO_TUNE_TWISTER
1635 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1636 depends on 8139TOO
1637 help
1638 This implements a function which might come in handy in case you
1639 are using low quality on long cabling. It is required for RealTek
1640 RTL-8139 revision K boards, and totally unused otherwise. It tries
1641 to match the transceiver to the cable characteristics. This is
1642 experimental since hardly documented by the manufacturer.
1643 If unsure, say Y.
1645 config 8139TOO_8129
1646 bool "Support for older RTL-8129/8130 boards"
1647 depends on 8139TOO
1648 help
1649 This enables support for the older and uncommon RTL-8129 and
1650 RTL-8130 chips, which support MII via an external transceiver,
1651 instead of an internal one. Disabling this option will save some
1652 memory by making the code size smaller. If unsure, say Y.
1654 config 8139_OLD_RX_RESET
1655 bool "Use older RX-reset method"
1656 depends on 8139TOO
1657 help
1658 The 8139too driver was recently updated to contain a more rapid
1659 reset sequence, in the face of severe receive errors. This "new"
1660 RX-reset method should be adequate for all boards. But if you
1661 experience problems, you can enable this option to restore the
1662 old RX-reset behavior. If unsure, say N.
1664 config SIS900
1665 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1666 depends on NET_PCI && PCI
1667 select CRC32
1668 ---help---
1669 This is a driver for the Fast Ethernet PCI network cards based on
1670 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1671 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1672 read the Ethernet-HOWTO, available at
1673 <http://www.tldp.org/docs.html#howto>. Please read
1674 <file:Documentation/networking/sis900.txt> and comments at the
1675 beginning of <file:drivers/net/sis900.c> for more information.
1677 This driver also supports AMD 79C901 HomePNA so that you can use
1678 your phone line as a network cable.
1680 To compile this driver as a module, choose M here: the module
1681 will be called sis900. This is recommended.
1683 config EPIC100
1684 tristate "SMC EtherPower II"
1685 depends on NET_PCI && PCI
1686 select CRC32
1687 select MII
1688 help
1689 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1690 which is based on the SMC83c17x (EPIC/100).
1691 More specific information and updates are available from
1692 <http://www.scyld.com/network/epic100.html>.
1694 config SUNDANCE
1695 tristate "Sundance Alta support"
1696 depends on NET_PCI && PCI
1697 select CRC32
1698 select MII
1699 help
1700 This driver is for the Sundance "Alta" chip.
1701 More specific information and updates are available from
1702 <http://www.scyld.com/network/sundance.html>.
1704 config SUNDANCE_MMIO
1705 bool "Use MMIO instead of PIO"
1706 depends on SUNDANCE
1707 help
1708 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1709 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1710 is known to solve bugs on certain chips.
1712 If unsure, say N.
1714 config TLAN
1715 tristate "TI ThunderLAN support"
1716 depends on NET_PCI && (PCI || EISA) && !64BIT
1717 ---help---
1718 If you have a PCI Ethernet network card based on the ThunderLAN chip
1719 which is supported by this driver, say Y and read the
1720 Ethernet-HOWTO, available from
1721 <http://www.tldp.org/docs.html#howto>.
1723 Devices currently supported by this driver are Compaq Netelligent,
1724 Compaq NetFlex and Olicom cards. Please read the file
1725 <file:Documentation/networking/tlan.txt> for more details.
1727 To compile this driver as a module, choose M here and read
1728 <file:Documentation/networking/net-modules.txt>. The module
1729 will be called tlan.
1731 Please email feedback to torben.mathiasen@compaq.com.
1733 config VIA_RHINE
1734 tristate "VIA Rhine support"
1735 depends on NET_PCI && PCI
1736 select CRC32
1737 select MII
1738 help
1739 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1740 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1741 Ethernet functions can also be found integrated on South Bridges
1742 (e.g. VT8235).
1744 To compile this driver as a module, choose M here. The module
1745 will be called via-rhine.
1747 config VIA_RHINE_MMIO
1748 bool "Use MMIO instead of PIO"
1749 depends on VIA_RHINE
1750 help
1751 This instructs the driver to use PCI shared memory (MMIO) instead of
1752 programmed I/O ports (PIO). Enabling this gives an improvement in
1753 processing time in parts of the driver.
1755 If unsure, say Y.
1757 config VIA_VELOCITY
1758 tristate "VIA Velocity support"
1759 depends on NET_PCI && PCI
1760 select CRC32
1761 select CRC_CCITT
1762 select MII
1763 help
1764 If you have a VIA "Velocity" based network card say Y here.
1766 To compile this driver as a module, choose M here. The module
1767 will be called via-velocity.
1769 config LAN_SAA9730
1770 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1771 depends on NET_PCI && EXPERIMENTAL && MIPS
1772 help
1773 The SAA9730 is a combined multimedia and peripheral controller used
1774 in thin clients, Internet access terminals, and diskless
1775 workstations.
1776 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1778 config NET_POCKET
1779 bool "Pocket and portable adapters"
1780 depends on NET_ETHERNET && ISA
1781 ---help---
1782 Cute little network (Ethernet) devices which attach to the parallel
1783 port ("pocket adapters"), commonly used with laptops. If you have
1784 one of those, say Y and read the Ethernet-HOWTO, available from
1785 <http://www.tldp.org/docs.html#howto>.
1787 If you want to plug a network (or some other) card into the PCMCIA
1788 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1789 credit card size extension cards used by all modern laptops), you
1790 need the pcmcia-cs package (location contained in the file
1791 <file:Documentation/Changes>) and you can say N here.
1793 Laptop users should read the Linux Laptop home page at
1794 <http://www.linux-on-laptops.com/> or
1795 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1797 Note that the answer to this question doesn't directly affect the
1798 kernel: saying N will just cause the configurator to skip all
1799 the questions about this class of network devices. If you say Y, you
1800 will be asked for your specific device in the following questions.
1802 config ATP
1803 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1804 depends on NET_POCKET && ISA && X86
1805 select CRC32
1806 ---help---
1807 This is a network (Ethernet) device which attaches to your parallel
1808 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1809 available from <http://www.tldp.org/docs.html#howto>, if you
1810 want to use this. If you intend to use this driver, you should have
1811 said N to the "Parallel printer support", because the two drivers
1812 don't like each other.
1814 To compile this driver as a module, choose M here: the module
1815 will be called atp.
1817 config DE600
1818 tristate "D-Link DE600 pocket adapter support"
1819 depends on NET_POCKET && ISA
1820 ---help---
1821 This is a network (Ethernet) device which attaches to your parallel
1822 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1823 Ethernet-HOWTO, available from
1824 <http://www.tldp.org/docs.html#howto>, if you want to use
1825 this. It is possible to have several devices share a single parallel
1826 port and it is safe to compile the corresponding drivers into the
1827 kernel.
1829 To compile this driver as a module, choose M here: the module
1830 will be called de600.
1832 config DE620
1833 tristate "D-Link DE620 pocket adapter support"
1834 depends on NET_POCKET && ISA
1835 ---help---
1836 This is a network (Ethernet) device which attaches to your parallel
1837 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1838 Ethernet-HOWTO, available from
1839 <http://www.tldp.org/docs.html#howto>, if you want to use
1840 this. It is possible to have several devices share a single parallel
1841 port and it is safe to compile the corresponding drivers into the
1842 kernel.
1844 To compile this driver as a module, choose M here: the module
1845 will be called de620.
1847 config SGISEEQ
1848 tristate "SGI Seeq ethernet controller support"
1849 depends on NET_ETHERNET && SGI_IP22
1850 help
1851 Say Y here if you have an Seeq based Ethernet network card. This is
1852 used in many Silicon Graphics machines.
1854 config DECLANCE
1855 tristate "DEC LANCE ethernet controller support"
1856 depends on NET_ETHERNET && MACH_DECSTATION
1857 select CRC32
1858 help
1859 This driver is for the series of Ethernet controllers produced by
1860 DEC (now Compaq) based on the AMD Lance chipset, including the
1861 DEPCA series. (This chipset is better known via the NE2100 cards.)
1863 config BAGETLANCE
1864 tristate "Baget AMD LANCE support"
1865 depends on NET_ETHERNET && BAGET_MIPS
1866 help
1867 Say Y to enable kernel support for AMD Lance Ethernet cards on the
1868 MIPS-32-based Baget embedded system. This chipset is better known
1869 via the NE2100 cards.
1871 config 68360_ENET
1872 bool "Motorola 68360 ethernet controller"
1873 depends on M68360
1874 help
1875 Say Y here if you want to use the built-in ethernet controller of
1876 the Motorola 68360 processor.
1878 config FEC
1879 bool "FEC ethernet controller (of ColdFire CPUs)"
1880 depends on M527x || M5272 || M528x
1881 help
1882 Say Y here if you want to use the built-in 10/100 Fast ethernet
1883 controller on some Motorola ColdFire processors.
1885 config FEC2
1886 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1887 depends on FEC
1888 help
1889 Say Y here if you want to use the second built-in 10/100 Fast
1890 ethernet controller on some Motorola ColdFire processors.
1892 config NE_H8300
1893 tristate "NE2000 compatible support for H8/300"
1894 depends on H8300 && NET_ETHERNET
1895 help
1896 Say Y here if you want to use the NE2000 compatible
1897 controller on the Renesas H8/300 processor.
1899 source "drivers/net/fec_8xx/Kconfig"
1901 endmenu
1903 #
1904 # Gigabit Ethernet
1905 #
1907 menu "Ethernet (1000 Mbit)"
1908 depends on NETDEVICES
1910 config ACENIC
1911 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1912 depends on PCI
1913 ---help---
1914 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1915 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1916 adapter. The driver allows for using the Jumbo Frame option (9000
1917 bytes/frame) however it requires that your switches can handle this
1918 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1919 line.
1921 To compile this driver as a module, choose M here: the
1922 module will be called acenic.
1924 config ACENIC_OMIT_TIGON_I
1925 bool "Omit support for old Tigon I based AceNICs"
1926 depends on ACENIC
1927 help
1928 Say Y here if you only have Tigon II based AceNICs and want to leave
1929 out support for the older Tigon I based cards which are no longer
1930 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1931 version)). This will reduce the size of the driver object by
1932 app. 100KB. If you are not sure whether your card is a Tigon I or a
1933 Tigon II, say N here.
1935 The safe and default value for this is N.
1937 config DL2K
1938 tristate "D-Link DL2000-based Gigabit Ethernet support"
1939 depends on PCI
1940 select CRC32
1941 help
1942 This driver supports D-Link 2000-based gigabit ethernet cards, which
1943 includes
1944 D-Link DGE-550T Gigabit Ethernet Adapter.
1945 D-Link DL2000-based Gigabit Ethernet Adapter.
1947 To compile this driver as a module, choose M here: the
1948 module will be called dl2k.
1950 config E1000
1951 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1952 depends on PCI
1953 ---help---
1954 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1955 adapters, which includes:
1957 Controller Adapter Name Board IDs
1958 ---------- ------------ ---------
1959 82542 PRO/1000 Gigabit Server Adapter 700262-xxx,
1960 717037-xxx
1961 82543 PRO/1000 F Server Adapter 738640-xxx,
1962 A38888-xxx
1963 82543 PRO/1000 T Server Adapter A19845-xxx,
1964 A33948-xxx
1965 82544 PRO/1000 XT Server Adapter A51580-xxx
1966 82544 PRO/1000 XF Server Adapter A50484-xxx
1967 82544 PRO/1000 T Desktop Adapter A62947-xxx
1968 82540 PRO/1000 MT Desktop Adapter A78408-xxx
1969 82541 PRO/1000 MT Desktop Adapter C91016-xxx
1970 82545 PRO/1000 MT Server Adapter A92165-xxx
1971 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx
1972 82545 PRO/1000 MF Server Adapter A91622-xxx
1973 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx
1974 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx
1976 For more information on how to identify your adapter, go to the
1977 Adapter & Driver ID Guide at:
1979 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1981 For general information and support, go to the Intel support
1982 website at:
1984 <http://support.intel.com>
1986 More specific information on configuring the driver is in
1987 <file:Documentation/networking/e1000.txt>.
1989 To compile this driver as a module, choose M here and read
1990 <file:Documentation/networking/net-modules.txt>. The module
1991 will be called e1000.
1993 config E1000_NAPI
1994 bool "Use Rx Polling (NAPI)"
1995 depends on E1000
1996 help
1997 NAPI is a new driver API designed to reduce CPU and interrupt load
1998 when the driver is receiving lots of packets from the card. It is
1999 still somewhat experimental and thus not yet enabled by default.
2001 If your estimated Rx load is 10kpps or more, or if the card will be
2002 deployed on potentially unfriendly networks (e.g. in a firewall),
2003 then say Y here.
2005 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2006 information.
2008 If in doubt, say N.
2010 config MYRI_SBUS
2011 tristate "MyriCOM Gigabit Ethernet support"
2012 depends on SBUS
2013 help
2014 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2016 To compile this driver as a module, choose M here: the module
2017 will be called myri_sbus. This is recommended.
2019 config NS83820
2020 tristate "National Semiconduct DP83820 support"
2021 depends on PCI
2022 help
2023 This is a driver for the National Semiconductor DP83820 series
2024 of gigabit ethernet MACs. Cards using this chipset include
2025 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2026 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2027 zero copy.
2029 config HAMACHI
2030 tristate "Packet Engines Hamachi GNIC-II support"
2031 depends on PCI
2032 select MII
2033 help
2034 If you have a Gigabit Ethernet card of this type, say Y and read
2035 the Ethernet-HOWTO, available from
2036 <http://www.tldp.org/docs.html#howto>.
2038 To compile this driver as a module, choose M here and read
2039 <file:Documentation/networking/net-modules.txt>. The module will be
2040 called hamachi.
2042 config YELLOWFIN
2043 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2044 depends on PCI && EXPERIMENTAL
2045 select CRC32
2046 ---help---
2047 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2048 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2049 used by the Beowulf Linux cluster project. See
2050 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2051 information about this driver in particular and Beowulf in general.
2053 To compile this driver as a module, choose M here: the module
2054 will be called yellowfin. This is recommended.
2056 config R8169
2057 tristate "Realtek 8169 gigabit ethernet support"
2058 depends on PCI
2059 select CRC32
2060 ---help---
2061 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2063 To compile this driver as a module, choose M here: the module
2064 will be called r8169. This is recommended.
2066 config R8169_NAPI
2067 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2068 depends on R8169 && EXPERIMENTAL
2069 help
2070 NAPI is a new driver API designed to reduce CPU and interrupt load
2071 when the driver is receiving lots of packets from the card. It is
2072 still somewhat experimental and thus not yet enabled by default.
2074 If your estimated Rx load is 10kpps or more, or if the card will be
2075 deployed on potentially unfriendly networks (e.g. in a firewall),
2076 then say Y here.
2078 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2079 information.
2081 If in doubt, say N.
2083 config SK98LIN
2084 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2085 depends on PCI
2086 ---help---
2087 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2088 compliant Gigabit Ethernet Adapter. The following adapters are supported
2089 by this driver:
2090 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2091 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2092 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2093 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2094 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2095 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2096 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2097 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2098 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2099 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2100 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2101 - DGE-530T Gigabit Ethernet Adapter
2102 - EG1032 v2 Instant Gigabit Network Adapter
2103 - EG1064 v2 Instant Gigabit Network Adapter
2104 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2105 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2106 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2107 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2108 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2109 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2110 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2111 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2112 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2113 - Marvell RDK-8001 Adapter
2114 - Marvell RDK-8002 Adapter
2115 - Marvell RDK-8003 Adapter
2116 - Marvell RDK-8004 Adapter
2117 - Marvell RDK-8006 Adapter
2118 - Marvell RDK-8007 Adapter
2119 - Marvell RDK-8008 Adapter
2120 - Marvell RDK-8009 Adapter
2121 - Marvell RDK-8010 Adapter
2122 - Marvell RDK-8011 Adapter
2123 - Marvell RDK-8012 Adapter
2124 - Marvell RDK-8052 Adapter
2125 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2126 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2127 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2128 - SK-9521 10/100/1000Base-T Adapter
2129 - SK-9521 V2.0 10/100/1000Base-T Adapter
2130 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2131 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2132 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2133 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2134 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2135 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2136 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2137 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2138 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2139 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2140 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2141 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2142 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2143 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2144 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2145 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2146 - SMC EZ Card 1000 (SMC9452TXV.2)
2148 The adapters support Jumbo Frames.
2149 The dual link adapters support link-failover and dual port features.
2150 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2151 the scatter-gather functionality with sendfile(). Please refer to
2152 Documentation/networking/sk98lin.txt for more information about
2153 optional driver parameters.
2154 Questions concerning this driver may be addressed to:
2155 linux@syskonnect.de
2157 If you want to compile this driver as a module ( = code which can be
2158 inserted in and removed from the running kernel whenever you want),
2159 say M here and read Documentation/kbuild/modules.txt. The module will
2160 be called sk98lin. This is recommended.
2162 config TIGON3
2163 tristate "Broadcom Tigon3 support"
2164 depends on PCI
2165 help
2166 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2168 To compile this driver as a module, choose M here: the module
2169 will be called tg3. This is recommended.
2171 config GIANFAR
2172 tristate "Gianfar Ethernet"
2173 depends on 85xx
2174 help
2175 This driver supports the Gigabit TSEC on the MPC85xx
2176 family of chips, and the FEC on the 8540
2178 config GFAR_NAPI
2179 bool "NAPI Support"
2180 depends on GIANFAR
2182 config MV643XX_ETH
2183 tristate "MV-643XX Ethernet support"
2184 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX
2185 help
2186 This driver supports the gigabit Ethernet on the Marvell MV643XX
2187 chipset which is used in the Momenco Ocelot C and Jaguar ATX.
2189 config MV643XX_ETH_0
2190 bool "MV-643XX Port 0"
2191 depends on MV643XX_ETH
2192 help
2193 This enables support for Port 0 of the Marvell MV643XX Gigabit
2194 Ethernet.
2196 config MV643XX_ETH_1
2197 bool "MV-643XX Port 1"
2198 depends on MV643XX_ETH
2199 help
2200 This enables support for Port 1 of the Marvell MV643XX Gigabit
2201 Ethernet.
2203 config MV643XX_ETH_2
2204 bool "MV-643XX Port 2"
2205 depends on MV643XX_ETH
2206 help
2207 This enables support for Port 2 of the Marvell MV643XX Gigabit
2208 Ethernet.
2210 endmenu
2212 #
2213 # 10 Gigabit Ethernet
2214 #
2216 menu "Ethernet (10000 Mbit)"
2217 depends on NETDEVICES
2219 config IXGB
2220 tristate "Intel(R) PRO/10GbE support"
2221 depends on PCI
2222 ---help---
2223 This driver supports Intel(R) PRO/10GbE family of
2224 adapters, which includes:
2226 Controller Adapter Name Board IDs
2227 ---------- ------------ ---------
2228 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx
2230 For more information on how to identify your adapter, go to the
2231 Adapter & Driver ID Guide at:
2233 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2235 For general information and support, go to the Intel support
2236 website at:
2238 <http://support.intel.com>
2240 More specific information on configuring the driver is in
2241 <file:Documentation/networking/ixgb.txt>.
2243 To compile this driver as a module, choose M here and read
2244 <file:Documentation/networking/net-modules.txt>. The module
2245 will be called ixgb.
2247 config IXGB_NAPI
2248 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2249 depends on IXGB && EXPERIMENTAL
2250 help
2251 NAPI is a new driver API designed to reduce CPU and interrupt load
2252 when the driver is receiving lots of packets from the card. It is
2253 still somewhat experimental and thus not yet enabled by default.
2255 If your estimated Rx load is 10kpps or more, or if the card will be
2256 deployed on potentially unfriendly networks (e.g. in a firewall),
2257 then say Y here.
2259 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2260 information.
2262 If in doubt, say N.
2264 config S2IO
2265 tristate "S2IO 10Gbe XFrame NIC"
2266 depends on PCI
2267 ---help---
2268 This driver supports the 10Gbe XFrame NIC of S2IO.
2269 For help regarding driver compilation, installation and
2270 tuning please look into ~/drivers/net/s2io/README.txt.
2272 config S2IO_NAPI
2273 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2274 depends on S2IO && EXPERIMENTAL
2275 help
2276 NAPI is a new driver API designed to reduce CPU and interrupt load
2277 when the driver is receiving lots of packets from the card. It is
2278 still somewhat experimental and thus not yet enabled by default.
2280 If your estimated Rx load is 10kpps or more, or if the card will be
2281 deployed on potentially unfriendly networks (e.g. in a firewall),
2282 then say Y here.
2284 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2285 information.
2287 If in doubt, say N.
2289 endmenu
2291 source "drivers/net/tokenring/Kconfig"
2293 source "drivers/net/wireless/Kconfig"
2295 source "drivers/net/pcmcia/Kconfig"
2297 source "drivers/net/wan/Kconfig"
2299 source "drivers/atm/Kconfig"
2301 source "drivers/s390/net/Kconfig"
2303 config ISERIES_VETH
2304 tristate "iSeries Virtual Ethernet driver support"
2305 depends on NETDEVICES && PPC_ISERIES
2307 config FDDI
2308 bool "FDDI driver support"
2309 depends on NETDEVICES && (PCI || EISA)
2310 help
2311 Fiber Distributed Data Interface is a high speed local area network
2312 design; essentially a replacement for high speed Ethernet. FDDI can
2313 run over copper or fiber. If you are connected to such a network and
2314 want a driver for the FDDI card in your computer, say Y here (and
2315 then also Y to the driver for your FDDI card, below). Most people
2316 will say N.
2318 config DEFXX
2319 tristate "Digital DEFEA and DEFPA adapter support"
2320 depends on FDDI && (PCI || EISA)
2321 help
2322 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2323 (DEFPA) controllers which can connect you to a local FDDI network.
2325 config SKFP
2326 tristate "SysKonnect FDDI PCI support"
2327 depends on FDDI && PCI
2328 ---help---
2329 Say Y here if you have a SysKonnect FDDI PCI adapter.
2330 The following adapters are supported by this driver:
2331 - SK-5521 (SK-NET FDDI-UP)
2332 - SK-5522 (SK-NET FDDI-UP DAS)
2333 - SK-5541 (SK-NET FDDI-FP)
2334 - SK-5543 (SK-NET FDDI-LP)
2335 - SK-5544 (SK-NET FDDI-LP DAS)
2336 - SK-5821 (SK-NET FDDI-UP64)
2337 - SK-5822 (SK-NET FDDI-UP64 DAS)
2338 - SK-5841 (SK-NET FDDI-FP64)
2339 - SK-5843 (SK-NET FDDI-LP64)
2340 - SK-5844 (SK-NET FDDI-LP64 DAS)
2341 - Netelligent 100 FDDI DAS Fibre SC
2342 - Netelligent 100 FDDI SAS Fibre SC
2343 - Netelligent 100 FDDI DAS UTP
2344 - Netelligent 100 FDDI SAS UTP
2345 - Netelligent 100 FDDI SAS Fibre MIC
2347 Read <file:Documentation/networking/skfp.txt> for information about
2348 the driver.
2350 Questions concerning this driver can be addressed to:
2351 linux@syskonnect.de
2353 To compile this driver as a module, choose M here: the module
2354 will be called skfp. This is recommended.
2356 config HIPPI
2357 bool "HIPPI driver support (EXPERIMENTAL)"
2358 depends on NETDEVICES && EXPERIMENTAL && INET && PCI
2359 help
2360 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2361 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2362 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2363 single-mode). HIPPI networks are commonly used for clusters and to
2364 connect to super computers. If you are connected to a HIPPI network
2365 and have a HIPPI network card in your computer that you want to use
2366 under Linux, say Y here (you must also remember to enable the driver
2367 for your HIPPI card below). Most people will say N here.
2369 config ROADRUNNER
2370 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2371 depends on HIPPI && PCI
2372 help
2373 Say Y here if this is your PCI HIPPI network card.
2375 To compile this driver as a module, choose M here: the module
2376 will be called rrunner. If unsure, say N.
2378 config ROADRUNNER_LARGE_RINGS
2379 bool "Use large TX/RX rings (EXPERIMENTAL)"
2380 depends on ROADRUNNER
2381 help
2382 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2383 of additional memory to allow for fastest operation, both for
2384 transmitting and receiving. This memory cannot be used by any other
2385 kernel code or by user space programs. Say Y here only if you have
2386 the memory.
2388 config PLIP
2389 tristate "PLIP (parallel port) support"
2390 depends on NETDEVICES && PARPORT
2391 ---help---
2392 PLIP (Parallel Line Internet Protocol) is used to create a
2393 reasonably fast mini network consisting of two (or, rarely, more)
2394 local machines. A PLIP link from a Linux box is a popular means to
2395 install a Linux distribution on a machine which doesn't have a
2396 CD-ROM drive (a minimal system has to be transferred with floppies
2397 first). The kernels on both machines need to have this PLIP option
2398 enabled for this to work.
2400 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2401 ports (the connectors at the computers with 25 holes) are connected
2402 with "null printer" or "Turbo Laplink" cables which can transmit 4
2403 bits at a time (mode 0) or with special PLIP cables, to be used on
2404 bidirectional parallel ports only, which can transmit 8 bits at a
2405 time (mode 1); you can find the wiring of these cables in
2406 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2407 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2408 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2409 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2410 and winsock or NCSA's telnet.
2412 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2413 as the NET-3-HOWTO, both available from
2414 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2415 protocol has been changed and this PLIP driver won't work together
2416 with the PLIP support in Linux versions 1.0.x. This option enlarges
2417 your kernel by about 8 KB.
2419 To compile this driver as a module, choose M here and read
2420 <file:Documentation/networking/net-modules.txt>. The module will be
2421 called plip. If unsure, say Y or M, in case you buy a laptop
2422 later.
2424 config PPP
2425 tristate "PPP (point-to-point protocol) support"
2426 depends on NETDEVICES
2427 ---help---
2428 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2429 the same purpose: sending Internet traffic over telephone (and other
2430 serial) lines. Ask your access provider if they support it, because
2431 otherwise you can't use it; most Internet access providers these
2432 days support PPP rather than SLIP.
2434 To use PPP, you need an additional program called pppd as described
2435 in the PPP-HOWTO, available at
2436 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2437 the version of pppd recommended in <file:Documentation/Changes>.
2438 The PPP option enlarges your kernel by about 16 KB.
2440 There are actually two versions of PPP: the traditional PPP for
2441 asynchronous lines, such as regular analog phone lines, and
2442 synchronous PPP which can be used over digital ISDN lines for
2443 example. If you want to use PPP over phone lines or other
2444 asynchronous serial lines, you need to say Y (or M) here and also to
2445 the next option, "PPP support for async serial ports". For PPP over
2446 synchronous lines, you should say Y (or M) here and to "Support
2447 synchronous PPP", below.
2449 If you said Y to "Version information on all symbols" above, then
2450 you cannot compile the PPP driver into the kernel; you can then only
2451 compile it as a module. To compile this driver as a module, choose M
2452 here and read <file:Documentation/networking/net-modules.txt>.
2453 The module will be called ppp_generic.
2455 config PPP_MULTILINK
2456 bool "PPP multilink support (EXPERIMENTAL)"
2457 depends on PPP && EXPERIMENTAL
2458 help
2459 PPP multilink is a protocol (defined in RFC 1990) which allows you
2460 to combine several (logical or physical) lines into one logical PPP
2461 connection, so that you can utilize your full bandwidth.
2463 This has to be supported at the other end as well and you need a
2464 version of the pppd daemon which understands the multilink protocol.
2466 If unsure, say N.
2468 config PPP_FILTER
2469 bool "PPP filtering"
2470 depends on PPP
2471 help
2472 Say Y here if you want to be able to filter the packets passing over
2473 PPP interfaces. This allows you to control which packets count as
2474 activity (i.e. which packets will reset the idle timer or bring up
2475 a demand-dialled link) and which packets are to be dropped entirely.
2476 You need to say Y here if you wish to use the pass-filter and
2477 active-filter options to pppd.
2479 If unsure, say N.
2481 config PPP_ASYNC
2482 tristate "PPP support for async serial ports"
2483 depends on PPP
2484 select CRC_CCITT
2485 ---help---
2486 Say Y (or M) here if you want to be able to use PPP over standard
2487 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2488 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2489 need this option.
2491 To compile this driver as a module, choose M here.
2493 If unsure, say Y.
2495 config PPP_SYNC_TTY
2496 tristate "PPP support for sync tty ports"
2497 depends on PPP
2498 help
2499 Say Y (or M) here if you want to be able to use PPP over synchronous
2500 (HDLC) tty devices, such as the SyncLink adapter. These devices
2501 are often used for high-speed leased lines like T1/E1.
2503 To compile this driver as a module, choose M here.
2505 config PPP_DEFLATE
2506 tristate "PPP Deflate compression"
2507 depends on PPP
2508 select ZLIB_INFLATE
2509 select ZLIB_DEFLATE
2510 ---help---
2511 Support for the Deflate compression method for PPP, which uses the
2512 Deflate algorithm (the same algorithm that gzip uses) to compress
2513 each PPP packet before it is sent over the wire. The machine at the
2514 other end of the PPP link (usually your ISP) has to support the
2515 Deflate compression method as well for this to be useful. Even if
2516 they don't support it, it is safe to say Y here.
2518 To compile this driver as a module, choose M here.
2520 config PPP_BSDCOMP
2521 tristate "PPP BSD-Compress compression"
2522 depends on PPP
2523 ---help---
2524 Support for the BSD-Compress compression method for PPP, which uses
2525 the LZW compression method to compress each PPP packet before it is
2526 sent over the wire. The machine at the other end of the PPP link
2527 (usually your ISP) has to support the BSD-Compress compression
2528 method as well for this to be useful. Even if they don't support it,
2529 it is safe to say Y here.
2531 The PPP Deflate compression method ("PPP Deflate compression",
2532 above) is preferable to BSD-Compress, because it compresses better
2533 and is patent-free.
2535 Note that the BSD compression code will always be compiled as a
2536 module; it is called bsd_comp and will show up in the directory
2537 modules once you have said "make modules". If unsure, say N.
2539 config PPPOE
2540 tristate "PPP over Ethernet (EXPERIMENTAL)"
2541 depends on EXPERIMENTAL && PPP
2542 help
2543 Support for PPP over Ethernet.
2545 This driver requires the latest version of pppd from the CVS
2546 repository at cvs.samba.org. Alternatively, see the
2547 RoaringPenguin package (http://www.roaringpenguin.com/pppoe)
2548 which contains instruction on how to use this driver (under
2549 the heading "Kernel mode PPPoE").
2551 config PPPOATM
2552 tristate "PPP over ATM"
2553 depends on ATM && PPP
2554 help
2555 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2556 This implementation does not yet comply with section 8 of RFC2364,
2557 which can lead to bad results if the ATM peer loses state and
2558 changes its encapsulation unilaterally.
2560 config SLIP
2561 tristate "SLIP (serial line) support"
2562 depends on NETDEVICES
2563 ---help---
2564 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2565 connect to your Internet service provider or to connect to some
2566 other local Unix box or if you want to configure your Linux box as a
2567 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2568 Internet Protocol) is a protocol used to send Internet traffic over
2569 serial connections such as telephone lines or null modem cables;
2570 nowadays, the protocol PPP is more commonly used for this same
2571 purpose.
2573 Normally, your access provider has to support SLIP in order for you
2574 to be able to use it, but there is now a SLIP emulator called SLiRP
2575 around (available from
2576 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2577 allows you to use SLIP over a regular dial up shell connection. If
2578 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2579 NET-3-HOWTO, available from
2580 <http://www.tldp.org/docs.html#howto>, explains how to
2581 configure SLIP. Note that you don't need this option if you just
2582 want to run term (term is a program which gives you almost full
2583 Internet connectivity if you have a regular dial up shell account on
2584 some Internet connected Unix computer. Read
2585 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2586 support will enlarge your kernel by about 4 KB. If unsure, say N.
2588 To compile this driver as a module, choose M here and read
2589 <file:Documentation/networking/net-modules.txt>. The module will be
2590 called slip.
2592 config SLIP_COMPRESSED
2593 bool "CSLIP compressed headers"
2594 depends on SLIP
2595 ---help---
2596 This protocol is faster than SLIP because it uses compression on the
2597 TCP/IP headers (not on the data itself), but it has to be supported
2598 on both ends. Ask your access provider if you are not sure and
2599 answer Y, just in case. You will still be able to use plain SLIP. If
2600 you plan to use SLiRP, the SLIP emulator (available from
2601 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2602 allows you to use SLIP over a regular dial up shell connection, you
2603 definitely want to say Y here. The NET-3-HOWTO, available from
2604 <http://www.tldp.org/docs.html#howto>, explains how to configure
2605 CSLIP. This won't enlarge your kernel.
2607 config SLIP_SMART
2608 bool "Keepalive and linefill"
2609 depends on SLIP
2610 help
2611 Adds additional capabilities to the SLIP driver to support the
2612 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2613 analogue lines.
2615 config SLIP_MODE_SLIP6
2616 bool "Six bit SLIP encapsulation"
2617 depends on SLIP
2618 help
2619 Just occasionally you may need to run IP over hostile serial
2620 networks that don't pass all control characters or are only seven
2621 bit. Saying Y here adds an extra mode you can use with SLIP:
2622 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2623 the serial device. Naturally, this has to be supported at the other
2624 end of the link as well. It's good enough, for example, to run IP
2625 over the async ports of a Camtec JNT Pad. If unsure, say N.
2627 config NET_FC
2628 bool "Fibre Channel driver support"
2629 depends on NETDEVICES && SCSI && PCI
2630 help
2631 Fibre Channel is a high speed serial protocol mainly used to connect
2632 large storage devices to the computer; it is compatible with and
2633 intended to replace SCSI.
2635 If you intend to use Fibre Channel, you need to have a Fibre channel
2636 adaptor card in your computer; say Y here and to the driver for your
2637 adaptor below. You also should have said Y to "SCSI support" and
2638 "SCSI generic support".
2640 config IPHASE5526
2641 tristate "Interphase 5526 Tachyon chipset based adapter support"
2642 depends on NET_FC && SCSI && PCI && BROKEN
2643 help
2644 Say Y here if you have a Fibre Channel adaptor of this kind.
2646 To compile this driver as a module, choose M here: the module
2647 will be called iph5526.
2649 config SHAPER
2650 tristate "Traffic Shaper (EXPERIMENTAL)"
2651 depends on NETDEVICES && EXPERIMENTAL
2652 ---help---
2653 The traffic shaper is a virtual network device that allows you to
2654 limit the rate of outgoing data flow over some other network device.
2655 The traffic that you want to slow down can then be routed through
2656 these virtual devices. See
2657 <file:Documentation/networking/shaper.txt> for more information.
2659 An alternative to this traffic shaper is the experimental
2660 Class-Based Queueing (CBQ) scheduling support which you get if you
2661 say Y to "QoS and/or fair queueing" above.
2663 To set up and configure shaper devices, you need the shapecfg
2664 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
2665 shaper package.
2667 To compile this driver as a module, choose M here: the module
2668 will be called shaper. If unsure, say N.
2670 config NETCONSOLE
2671 tristate "Network console logging support (EXPERIMENTAL)"
2672 depends on NETDEVICES && EXPERIMENTAL
2673 ---help---
2674 If you want to log kernel messages over the network, enable this.
2675 See Documentation/networking/netconsole.txt for details.