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