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