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