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