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