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