blob: 2610cedd55c7dd79921bc7da5898d6ce624ea329 [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
1090 NE2000 support", above. If you have a NE2000 card and are running on
1091 an MCA system (a bus system used on some IBM PS/2 computers and
1092 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1093 below.
1094
1095 To compile this driver as a module, choose M here and read
1096 <file:Documentation/networking/net-modules.txt>. The module
1097 will be called ne.
1098
1099config ZNET
1100 tristate "Zenith Z-Note support (EXPERIMENTAL)"
Al Viroa5532602005-05-04 05:39:42 +01001101 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -07001102 help
1103 The Zenith Z-Note notebook computer has a built-in network
1104 (Ethernet) card, and this is the Linux driver for it. Note that the
1105 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1106 by this driver. Read the Ethernet-HOWTO, available from
1107 <http://www.tldp.org/docs.html#howto>.
1108
1109config SEEQ8005
1110 tristate "SEEQ8005 support (EXPERIMENTAL)"
1111 depends on NET_ISA && EXPERIMENTAL
1112 help
1113 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1114 is for you, read the Ethernet-HOWTO, available from
1115 <http://www.tldp.org/docs.html#howto>.
1116
1117 To compile this driver as a module, choose M here and read
1118 <file:Documentation/networking/net-modules.txt>. The module
1119 will be called seeq8005.
1120
Linus Torvalds1da177e2005-04-16 15:20:36 -07001121config SKMC
1122 tristate "SKnet MCA support"
1123 depends on NET_ETHERNET && MCA && BROKEN
1124 ---help---
1125 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1126 support" in order to use this driver. Supported cards are the SKnet
1127 Junior MC2 and the SKnet MC2(+). The driver automatically
1128 distinguishes between the two cards. Note that using multiple boards
1129 of different type hasn't been tested with this driver. Say Y if you
1130 have one of these Ethernet adapters.
1131
1132 To compile this driver as a module, choose M here and read
1133 <file:Documentation/networking/net-modules.txt>. The module
1134 will be called sk_mca.
1135
1136config NE2_MCA
1137 tristate "NE/2 (ne2000 MCA version) support"
1138 depends on NET_ETHERNET && MCA_LEGACY
1139 select CRC32
1140 help
1141 If you have a network (Ethernet) card of this type, say Y and read
1142 the Ethernet-HOWTO, available from
1143 <http://www.tldp.org/docs.html#howto>.
1144
1145 To compile this driver as a module, choose M here and read
1146 <file:Documentation/networking/net-modules.txt>. The module
1147 will be called ne2.
1148
1149config IBMLANA
1150 tristate "IBM LAN Adapter/A support"
1151 depends on NET_ETHERNET && MCA && MCA_LEGACY
1152 ---help---
1153 This is a Micro Channel Ethernet adapter. You need to set
1154 CONFIG_MCA to use this driver. It is both available as an in-kernel
1155 driver and as a module.
1156
1157 To compile this driver as a module, choose M here and read
1158 <file:Documentation/networking/net-modules.txt>. The only
1159 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1160 will both support 16K and 32K memory windows, however a 32K window
1161 gives a better security against packet losses. Usage of multiple
1162 boards with this driver should be possible, but has not been tested
1163 up to now due to lack of hardware.
1164
1165config IBMVETH
1166 tristate "IBM LAN Virtual Ethernet support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07001167 depends on NET_ETHERNET && PPC_PSERIES
Linus Torvalds1da177e2005-04-16 15:20:36 -07001168 ---help---
1169 This driver supports virtual ethernet adapters on newer IBM iSeries
1170 and pSeries systems.
1171
1172 To compile this driver as a module, choose M here and read
1173 <file:Documentation/networking/net-modules.txt>. The module will
1174 be called ibmveth.
1175
1176config IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001177 tristate "PowerPC 4xx on-chip Ethernet support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001178 depends on 4xx
Eugene Surovegin37448f72005-10-10 16:58:14 -07001179 help
1180 This driver supports the PowerPC 4xx EMAC family of on-chip
1181 Ethernet controllers.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001182
1183config IBM_EMAC_RXB
1184 int "Number of receive buffers"
1185 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001186 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001187
1188config IBM_EMAC_TXB
1189 int "Number of transmit buffers"
1190 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001191 default "64"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001192
Eugene Surovegin37448f72005-10-10 16:58:14 -07001193config IBM_EMAC_POLL_WEIGHT
1194 int "MAL NAPI polling weight"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001195 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001196 default "32"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001197
Eugene Surovegin37448f72005-10-10 16:58:14 -07001198config IBM_EMAC_RX_COPY_THRESHOLD
1199 int "RX skb copy threshold (bytes)"
1200 depends on IBM_EMAC
1201 default "256"
1202
1203config IBM_EMAC_RX_SKB_HEADROOM
1204 int "Additional RX skb headroom (bytes)"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001205 depends on IBM_EMAC
1206 default "0"
Eugene Surovegin37448f72005-10-10 16:58:14 -07001207 help
1208 Additional receive skb headroom. Note, that driver
1209 will always reserve at least 2 bytes to make IP header
Jon Mason47c51432006-02-12 11:53:04 -06001210 aligned, so usually there is no need to add any additional
Eugene Surovegin37448f72005-10-10 16:58:14 -07001211 headroom.
1212
1213 If unsure, set to 0.
1214
1215config IBM_EMAC_PHY_RX_CLK_FIX
1216 bool "PHY Rx clock workaround"
Eugene Surovegin1b195912005-10-29 12:45:31 -07001217 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
Eugene Surovegin37448f72005-10-10 16:58:14 -07001218 help
1219 Enable this if EMAC attached to a PHY which doesn't generate
1220 RX clock if there is no link, if this is the case, you will
1221 see "TX disable timeout" or "RX disable timeout" in the system
1222 log.
1223
1224 If unsure, say N.
1225
1226config IBM_EMAC_DEBUG
1227 bool "Debugging"
1228 depends on IBM_EMAC
1229 default n
1230
1231config IBM_EMAC_ZMII
1232 bool
1233 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1234 default y
1235
1236config IBM_EMAC_RGMII
1237 bool
1238 depends on IBM_EMAC && 440GX
1239 default y
1240
1241config IBM_EMAC_TAH
1242 bool
1243 depends on IBM_EMAC && 440GX
1244 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001245
1246config NET_PCI
1247 bool "EISA, VLB, PCI and on board controllers"
1248 depends on NET_ETHERNET && (ISA || EISA || PCI)
1249 help
1250 This is another class of network cards which attach directly to the
1251 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1252 available from <http://www.tldp.org/docs.html#howto>.
1253
1254 Note that the answer to this question doesn't directly affect the
1255 kernel: saying N will just cause the configurator to skip all
1256 the questions about this class of network cards. If you say Y, you
1257 will be asked for your specific card in the following questions. If
1258 you are unsure, say Y.
1259
1260config PCNET32
1261 tristate "AMD PCnet32 PCI support"
1262 depends on NET_PCI && PCI
1263 select CRC32
1264 select MII
1265 help
1266 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1267 answer Y here and read the Ethernet-HOWTO, available from
1268 <http://www.tldp.org/docs.html#howto>.
1269
1270 To compile this driver as a module, choose M here and read
1271 <file:Documentation/networking/net-modules.txt>. The module
1272 will be called pcnet32.
1273
1274config AMD8111_ETH
1275 tristate "AMD 8111 (new PCI lance) support"
1276 depends on NET_PCI && PCI
1277 select CRC32
1278 select MII
1279 help
1280 If you have an AMD 8111-based PCI lance ethernet card,
1281 answer Y here and read the Ethernet-HOWTO, available from
1282 <http://www.tldp.org/docs.html#howto>.
1283
1284 To compile this driver as a module, choose M here and read
1285 <file:Documentation/networking/net-modules.txt>. The module
1286 will be called amd8111e.
1287config AMD8111E_NAPI
1288 bool "Enable NAPI support"
1289 depends on AMD8111_ETH
1290 help
1291 NAPI is a new driver API designed to reduce CPU and interrupt load
1292 when the driver is receiving lots of packets from the card. It is
1293 still somewhat experimental and thus not yet enabled by default.
1294
1295 If your estimated Rx load is 10kpps or more, or if the card will be
1296 deployed on potentially unfriendly networks (e.g. in a firewall),
1297 then say Y here.
1298
1299 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1300 information.
1301
1302 If in doubt, say N.
1303
1304config ADAPTEC_STARFIRE
1305 tristate "Adaptec Starfire/DuraLAN support"
1306 depends on NET_PCI && PCI
1307 select CRC32
1308 select MII
1309 help
1310 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1311 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1312 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1313 driver.
1314
1315 To compile this driver as a module, choose M here: the module
1316 will be called starfire. This is recommended.
1317
1318config ADAPTEC_STARFIRE_NAPI
1319 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1320 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1321 help
1322 NAPI is a new driver API designed to reduce CPU and interrupt load
1323 when the driver is receiving lots of packets from the card. It is
1324 still somewhat experimental and thus not yet enabled by default.
1325
1326 If your estimated Rx load is 10kpps or more, or if the card will be
1327 deployed on potentially unfriendly networks (e.g. in a firewall),
1328 then say Y here.
1329
1330 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1331 information.
1332
1333 If in doubt, say N.
1334
1335config AC3200
1336 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1337 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1338 select CRC32
1339 help
1340 If you have a network (Ethernet) card of this type, say Y and read
1341 the Ethernet-HOWTO, available from
1342 <http://www.tldp.org/docs.html#howto>.
1343
1344 To compile this driver as a module, choose M here and read
1345 <file:Documentation/networking/net-modules.txt>. The module
1346 will be called ac3200.
1347
1348config APRICOT
1349 tristate "Apricot Xen-II on board Ethernet"
1350 depends on NET_PCI && ISA
1351 help
1352 If you have a network (Ethernet) controller of this type, say Y and
1353 read the Ethernet-HOWTO, available from
1354 <http://www.tldp.org/docs.html#howto>.
1355
1356 To compile this driver as a module, choose M here and read
1357 <file:Documentation/networking/net-modules.txt>. The module will be
1358 called apricot.
1359
1360config B44
1361 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)"
1362 depends on NET_PCI && PCI && EXPERIMENTAL
1363 select MII
1364 help
1365 If you have a network (Ethernet) controller of this type, say Y and
1366 read the Ethernet-HOWTO, available from
1367 <http://www.tldp.org/docs.html#howto>.
1368
1369 To compile this driver as a module, choose M here and read
1370 <file:Documentation/networking/net-modules.txt>. The module will be
1371 called b44.
1372
1373config FORCEDETH
1374 tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
1375 depends on NET_PCI && PCI && EXPERIMENTAL
1376 help
1377 If you have a network (Ethernet) controller of this type, say Y and
1378 read the Ethernet-HOWTO, available from
1379 <http://www.tldp.org/docs.html#howto>.
1380
1381 To compile this driver as a module, choose M here and read
1382 <file:Documentation/networking/net-modules.txt>. The module will be
1383 called forcedeth.
1384
1385
1386config CS89x0
1387 tristate "CS89x0 support"
Deepak Saxena9c878962006-01-14 13:21:18 -08001388 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001389 ---help---
1390 Support for CS89x0 chipset based Ethernet cards. If you have a
1391 network (Ethernet) card of this type, say Y and read the
1392 Ethernet-HOWTO, available from
1393 <http://www.tldp.org/docs.html#howto> as well as
1394 <file:Documentation/networking/cs89x0.txt>.
1395
1396 To compile this driver as a module, choose M here and read
1397 <file:Documentation/networking/net-modules.txt>. The module will be
Jean Delvarefd85d762006-01-11 12:17:36 -08001398 called cs89x0.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001399
1400config TC35815
1401 tristate "TOSHIBA TC35815 Ethernet support"
1402 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1403
1404config DGRS
1405 tristate "Digi Intl. RightSwitch SE-X support"
1406 depends on NET_PCI && (PCI || EISA)
1407 ---help---
1408 This is support for the Digi International RightSwitch series of
1409 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1410 models. If you have a network card of this type, say Y and read the
1411 Ethernet-HOWTO, available from
1412 <http://www.tldp.org/docs.html#howto>. More specific
1413 information is contained in <file:Documentation/networking/dgrs.txt>.
1414
1415 To compile this driver as a module, choose M here and read
1416 <file:Documentation/networking/net-modules.txt>. The module
1417 will be called dgrs.
1418
1419config EEPRO100
1420 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1421 depends on NET_PCI && PCI
1422 select MII
1423 help
1424 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1425 card, say Y and read the Ethernet-HOWTO, available from
1426 <http://www.tldp.org/docs.html#howto>.
1427
1428 To compile this driver as a module, choose M here and read
1429 <file:Documentation/networking/net-modules.txt>. The module
1430 will be called eepro100.
1431
1432
1433config E100
1434 tristate "Intel(R) PRO/100+ support"
1435 depends on NET_PCI && PCI
1436 select MII
1437 ---help---
1438 This driver supports Intel(R) PRO/100 family of adapters.
1439 To verify that your adapter is supported, find the board ID number
1440 on the adapter. Look for a label that has a barcode and a number
1441 in the format 123456-001 (six digits hyphen three digits).
1442
1443 Use the above information and the Adapter & Driver ID Guide at:
1444
1445 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1446
1447 to identify the adapter.
1448
1449 For the latest Intel PRO/100 network driver for Linux, see:
1450
1451 <http://appsr.intel.com/scripts-df/support_intel.asp>
1452
1453 More specific information on configuring the driver is in
1454 <file:Documentation/networking/e100.txt>.
1455
1456 To compile this driver as a module, choose M here and read
1457 <file:Documentation/networking/net-modules.txt>. The module
1458 will be called e100.
1459
1460config LNE390
1461 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1462 depends on NET_PCI && EISA && EXPERIMENTAL
1463 select CRC32
1464 help
1465 If you have a network (Ethernet) card of this type, say Y and read
1466 the Ethernet-HOWTO, available from
1467 <http://www.tldp.org/docs.html#howto>.
1468
1469 To compile this driver as a module, choose M here and read
1470 <file:Documentation/networking/net-modules.txt>. The module
1471 will be called lne390.
1472
1473config FEALNX
1474 tristate "Myson MTD-8xx PCI Ethernet support"
1475 depends on NET_PCI && PCI
1476 select CRC32
1477 select MII
1478 help
1479 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1480 cards. Specifications and data at
1481 <http://www.myson.com.hk/mtd/datasheet/>.
1482
1483config NATSEMI
1484 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1485 depends on NET_PCI && PCI
1486 select CRC32
1487 help
1488 This driver is for the National Semiconductor DP83810 series,
1489 which is used in cards from PureData, NetGear, Linksys
1490 and others, including the 83815 chip.
1491 More specific information and updates are available from
1492 <http://www.scyld.com/network/natsemi.html>.
1493
1494config NE2K_PCI
1495 tristate "PCI NE2000 and clones support (see help)"
1496 depends on NET_PCI && PCI
1497 select CRC32
1498 ---help---
1499 This driver is for NE2000 compatible PCI cards. It will not work
1500 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1501 support" below). If you have a PCI NE2000 network (Ethernet) card,
1502 say Y and read the Ethernet-HOWTO, available from
1503 <http://www.tldp.org/docs.html#howto>.
1504
1505 This driver also works for the following NE2000 clone cards:
1506 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1507 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1508 Holtek HT80232 Holtek HT80229
1509
1510 To compile this driver as a module, choose M here and read
1511 <file:Documentation/networking/net-modules.txt>. The module
1512 will be called ne2k-pci.
1513
1514config NE3210
1515 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1516 depends on NET_PCI && EISA && EXPERIMENTAL
1517 select CRC32
1518 ---help---
1519 If you have a network (Ethernet) card of this type, say Y and read
1520 the Ethernet-HOWTO, available from
1521 <http://www.tldp.org/docs.html#howto>. Note that this driver
1522 will NOT WORK for NE3200 cards as they are completely different.
1523
1524 To compile this driver as a module, choose M here and read
1525 <file:Documentation/networking/net-modules.txt>. The module
1526 will be called ne3210.
1527
1528config ES3210
1529 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1530 depends on NET_PCI && EISA && EXPERIMENTAL
1531 select CRC32
1532 help
1533 If you have a network (Ethernet) card of this type, say Y and read
1534 the Ethernet-HOWTO, available from
1535 <http://www.tldp.org/docs.html#howto>.
1536
1537 To compile this driver as a module, choose M here and read
1538 <file:Documentation/networking/net-modules.txt>. The module
1539 will be called es3210.
1540
1541config 8139CP
1542 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1543 depends on NET_PCI && PCI && EXPERIMENTAL
1544 select CRC32
1545 select MII
1546 help
1547 This is a driver for the Fast Ethernet PCI network cards based on
1548 the RTL8139C+ chips. If you have one of those, say Y and read
1549 the Ethernet-HOWTO, available from
1550 <http://www.tldp.org/docs.html#howto>.
1551
1552 To compile this driver as a module, choose M here: the module
1553 will be called 8139cp. This is recommended.
1554
1555config 8139TOO
Adrian Bunkf04e3f02005-05-16 21:13:03 +02001556 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001557 depends on NET_PCI && PCI
1558 select CRC32
1559 select MII
1560 ---help---
1561 This is a driver for the Fast Ethernet PCI network cards based on
Adrian Bunkf04e3f02005-05-16 21:13:03 +02001562 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1563 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001564
1565 To compile this driver as a module, choose M here: the module
1566 will be called 8139too. This is recommended.
1567
1568config 8139TOO_PIO
1569 bool "Use PIO instead of MMIO"
1570 default y
1571 depends on 8139TOO
1572 help
1573 This instructs the driver to use programmed I/O ports (PIO) instead
1574 of PCI shared memory (MMIO). This can possibly solve some problems
1575 in case your mainboard has memory consistency issues. If unsure,
1576 say N.
1577
1578config 8139TOO_TUNE_TWISTER
1579 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1580 depends on 8139TOO
1581 help
1582 This implements a function which might come in handy in case you
1583 are using low quality on long cabling. It is required for RealTek
1584 RTL-8139 revision K boards, and totally unused otherwise. It tries
1585 to match the transceiver to the cable characteristics. This is
1586 experimental since hardly documented by the manufacturer.
1587 If unsure, say Y.
1588
1589config 8139TOO_8129
1590 bool "Support for older RTL-8129/8130 boards"
1591 depends on 8139TOO
1592 help
1593 This enables support for the older and uncommon RTL-8129 and
1594 RTL-8130 chips, which support MII via an external transceiver,
1595 instead of an internal one. Disabling this option will save some
1596 memory by making the code size smaller. If unsure, say Y.
1597
1598config 8139_OLD_RX_RESET
1599 bool "Use older RX-reset method"
1600 depends on 8139TOO
1601 help
1602 The 8139too driver was recently updated to contain a more rapid
1603 reset sequence, in the face of severe receive errors. This "new"
1604 RX-reset method should be adequate for all boards. But if you
1605 experience problems, you can enable this option to restore the
1606 old RX-reset behavior. If unsure, say N.
1607
1608config SIS900
1609 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1610 depends on NET_PCI && PCI
1611 select CRC32
Adrian Bunk6da0f682005-04-30 13:52:49 +02001612 select MII
Linus Torvalds1da177e2005-04-16 15:20:36 -07001613 ---help---
1614 This is a driver for the Fast Ethernet PCI network cards based on
1615 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1616 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
1617 read the Ethernet-HOWTO, available at
1618 <http://www.tldp.org/docs.html#howto>. Please read
1619 <file:Documentation/networking/sis900.txt> and comments at the
1620 beginning of <file:drivers/net/sis900.c> for more information.
1621
1622 This driver also supports AMD 79C901 HomePNA so that you can use
1623 your phone line as a network cable.
1624
1625 To compile this driver as a module, choose M here: the module
1626 will be called sis900. This is recommended.
1627
1628config EPIC100
1629 tristate "SMC EtherPower II"
1630 depends on NET_PCI && PCI
1631 select CRC32
1632 select MII
1633 help
1634 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1635 which is based on the SMC83c17x (EPIC/100).
1636 More specific information and updates are available from
1637 <http://www.scyld.com/network/epic100.html>.
1638
1639config SUNDANCE
1640 tristate "Sundance Alta support"
1641 depends on NET_PCI && PCI
1642 select CRC32
1643 select MII
1644 help
1645 This driver is for the Sundance "Alta" chip.
1646 More specific information and updates are available from
1647 <http://www.scyld.com/network/sundance.html>.
1648
1649config SUNDANCE_MMIO
1650 bool "Use MMIO instead of PIO"
1651 depends on SUNDANCE
1652 help
1653 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1654 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1655 is known to solve bugs on certain chips.
1656
1657 If unsure, say N.
1658
1659config TLAN
1660 tristate "TI ThunderLAN support"
1661 depends on NET_PCI && (PCI || EISA) && !64BIT
1662 ---help---
1663 If you have a PCI Ethernet network card based on the ThunderLAN chip
1664 which is supported by this driver, say Y and read the
1665 Ethernet-HOWTO, available from
1666 <http://www.tldp.org/docs.html#howto>.
1667
1668 Devices currently supported by this driver are Compaq Netelligent,
1669 Compaq NetFlex and Olicom cards. Please read the file
1670 <file:Documentation/networking/tlan.txt> for more details.
1671
1672 To compile this driver as a module, choose M here and read
1673 <file:Documentation/networking/net-modules.txt>. The module
1674 will be called tlan.
1675
1676 Please email feedback to <torben.mathiasen@compaq.com>.
1677
1678config VIA_RHINE
1679 tristate "VIA Rhine support"
1680 depends on NET_PCI && PCI
1681 select CRC32
1682 select MII
1683 help
1684 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1685 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1686 Ethernet functions can also be found integrated on South Bridges
1687 (e.g. VT8235).
1688
1689 To compile this driver as a module, choose M here. The module
1690 will be called via-rhine.
1691
1692config VIA_RHINE_MMIO
1693 bool "Use MMIO instead of PIO"
1694 depends on VIA_RHINE
1695 help
1696 This instructs the driver to use PCI shared memory (MMIO) instead of
1697 programmed I/O ports (PIO). Enabling this gives an improvement in
1698 processing time in parts of the driver.
1699
1700 If unsure, say Y.
1701
1702config LAN_SAA9730
1703 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1704 depends on NET_PCI && EXPERIMENTAL && MIPS
1705 help
1706 The SAA9730 is a combined multimedia and peripheral controller used
1707 in thin clients, Internet access terminals, and diskless
1708 workstations.
1709 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1710
1711config NET_POCKET
1712 bool "Pocket and portable adapters"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001713 depends on NET_ETHERNET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001714 ---help---
1715 Cute little network (Ethernet) devices which attach to the parallel
1716 port ("pocket adapters"), commonly used with laptops. If you have
1717 one of those, say Y and read the Ethernet-HOWTO, available from
1718 <http://www.tldp.org/docs.html#howto>.
1719
1720 If you want to plug a network (or some other) card into the PCMCIA
1721 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1722 credit card size extension cards used by all modern laptops), you
1723 need the pcmcia-cs package (location contained in the file
1724 <file:Documentation/Changes>) and you can say N here.
1725
1726 Laptop users should read the Linux Laptop home page at
1727 <http://www.linux-on-laptops.com/> or
1728 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1729
1730 Note that the answer to this question doesn't directly affect the
1731 kernel: saying N will just cause the configurator to skip all
1732 the questions about this class of network devices. If you say Y, you
1733 will be asked for your specific device in the following questions.
1734
1735config ATP
1736 tristate "AT-LAN-TEC/RealTek pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001737 depends on NET_POCKET && PARPORT && X86
Linus Torvalds1da177e2005-04-16 15:20:36 -07001738 select CRC32
1739 ---help---
1740 This is a network (Ethernet) device which attaches to your parallel
1741 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1742 available from <http://www.tldp.org/docs.html#howto>, if you
1743 want to use this. If you intend to use this driver, you should have
1744 said N to the "Parallel printer support", because the two drivers
1745 don't like each other.
1746
1747 To compile this driver as a module, choose M here: the module
1748 will be called atp.
1749
1750config DE600
1751 tristate "D-Link DE600 pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001752 depends on NET_POCKET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001753 ---help---
1754 This is a network (Ethernet) device which attaches to your parallel
1755 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1756 Ethernet-HOWTO, available from
1757 <http://www.tldp.org/docs.html#howto>, if you want to use
1758 this. It is possible to have several devices share a single parallel
1759 port and it is safe to compile the corresponding drivers into the
1760 kernel.
1761
1762 To compile this driver as a module, choose M here: the module
1763 will be called de600.
1764
1765config DE620
1766 tristate "D-Link DE620 pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001767 depends on NET_POCKET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001768 ---help---
1769 This is a network (Ethernet) device which attaches to your parallel
1770 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1771 Ethernet-HOWTO, available from
1772 <http://www.tldp.org/docs.html#howto>, if you want to use
1773 this. It is possible to have several devices share a single parallel
1774 port and it is safe to compile the corresponding drivers into the
1775 kernel.
1776
1777 To compile this driver as a module, choose M here: the module
1778 will be called de620.
1779
1780config SGISEEQ
1781 tristate "SGI Seeq ethernet controller support"
1782 depends on NET_ETHERNET && SGI_IP22
1783 help
1784 Say Y here if you have an Seeq based Ethernet network card. This is
1785 used in many Silicon Graphics machines.
1786
1787config DECLANCE
1788 tristate "DEC LANCE ethernet controller support"
1789 depends on NET_ETHERNET && MACH_DECSTATION
1790 select CRC32
1791 help
1792 This driver is for the series of Ethernet controllers produced by
1793 DEC (now Compaq) based on the AMD Lance chipset, including the
1794 DEPCA series. (This chipset is better known via the NE2100 cards.)
1795
1796config 68360_ENET
1797 bool "Motorola 68360 ethernet controller"
1798 depends on M68360
1799 help
1800 Say Y here if you want to use the built-in ethernet controller of
1801 the Motorola 68360 processor.
1802
1803config FEC
Greg Ungerer2af69212005-09-12 11:18:10 +10001804 bool "FEC ethernet controller (of ColdFire CPUs)"
Greg Ungerer892b6252006-01-10 16:58:16 +10001805 depends on M523x || M527x || M5272 || M528x || M520x
Linus Torvalds1da177e2005-04-16 15:20:36 -07001806 help
1807 Say Y here if you want to use the built-in 10/100 Fast ethernet
Greg Ungerer2af69212005-09-12 11:18:10 +10001808 controller on some Motorola ColdFire processors.
1809
1810config FEC2
1811 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1812 depends on FEC
1813 help
1814 Say Y here if you want to use the second built-in 10/100 Fast
1815 ethernet controller on some Motorola ColdFire processors.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001816
1817config NE_H8300
1818 tristate "NE2000 compatible support for H8/300"
1819 depends on H8300 && NET_ETHERNET
1820 help
1821 Say Y here if you want to use the NE2000 compatible
1822 controller on the Renesas H8/300 processor.
1823
1824source "drivers/net/fec_8xx/Kconfig"
Pantelis Antoniou48257c42005-10-28 16:25:58 -04001825source "drivers/net/fs_enet/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001826
1827endmenu
1828
1829#
1830# Gigabit Ethernet
1831#
1832
1833menu "Ethernet (1000 Mbit)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07001834 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -07001835
1836config ACENIC
1837 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1838 depends on PCI
1839 ---help---
1840 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1841 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1842 adapter. The driver allows for using the Jumbo Frame option (9000
1843 bytes/frame) however it requires that your switches can handle this
1844 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1845 line.
1846
1847 To compile this driver as a module, choose M here: the
1848 module will be called acenic.
1849
1850config ACENIC_OMIT_TIGON_I
1851 bool "Omit support for old Tigon I based AceNICs"
1852 depends on ACENIC
1853 help
1854 Say Y here if you only have Tigon II based AceNICs and want to leave
1855 out support for the older Tigon I based cards which are no longer
1856 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1857 version)). This will reduce the size of the driver object by
1858 app. 100KB. If you are not sure whether your card is a Tigon I or a
1859 Tigon II, say N here.
1860
1861 The safe and default value for this is N.
1862
1863config DL2K
1864 tristate "D-Link DL2000-based Gigabit Ethernet support"
1865 depends on PCI
1866 select CRC32
1867 help
1868 This driver supports D-Link 2000-based gigabit ethernet cards, which
1869 includes
1870 D-Link DGE-550T Gigabit Ethernet Adapter.
1871 D-Link DL2000-based Gigabit Ethernet Adapter.
1872
1873 To compile this driver as a module, choose M here: the
1874 module will be called dl2k.
1875
1876config E1000
1877 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1878 depends on PCI
1879 ---help---
1880 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1881 adapters. For more information on how to identify your adapter, go
1882 to the Adapter & Driver ID Guide at:
1883
1884 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1885
1886 For general information and support, go to the Intel support
1887 website at:
1888
1889 <http://support.intel.com>
1890
1891 More specific information on configuring the driver is in
1892 <file:Documentation/networking/e1000.txt>.
1893
1894 To compile this driver as a module, choose M here and read
1895 <file:Documentation/networking/net-modules.txt>. The module
1896 will be called e1000.
1897
1898config E1000_NAPI
1899 bool "Use Rx Polling (NAPI)"
1900 depends on E1000
1901 help
1902 NAPI is a new driver API designed to reduce CPU and interrupt load
1903 when the driver is receiving lots of packets from the card. It is
1904 still somewhat experimental and thus not yet enabled by default.
1905
1906 If your estimated Rx load is 10kpps or more, or if the card will be
1907 deployed on potentially unfriendly networks (e.g. in a firewall),
1908 then say Y here.
1909
1910 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1911 information.
1912
1913 If in doubt, say N.
1914
Jesse Brandeburg35ec56b2006-01-18 13:01:30 -08001915config E1000_DISABLE_PACKET_SPLIT
1916 bool "Disable Packet Split for PCI express adapters"
1917 depends on E1000
1918 help
1919 Say Y here if you want to use the legacy receive path for PCI express
1920 hadware.
1921
1922 If in doubt, say N.
1923
Lennert Buytenhek15d014d2005-11-11 18:23:13 +01001924source "drivers/net/ixp2000/Kconfig"
1925
Linus Torvalds1da177e2005-04-16 15:20:36 -07001926config MYRI_SBUS
1927 tristate "MyriCOM Gigabit Ethernet support"
1928 depends on SBUS
1929 help
1930 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1931
1932 To compile this driver as a module, choose M here: the module
1933 will be called myri_sbus. This is recommended.
1934
1935config NS83820
Jon Mason47c51432006-02-12 11:53:04 -06001936 tristate "National Semiconductor DP83820 support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001937 depends on PCI
1938 help
1939 This is a driver for the National Semiconductor DP83820 series
1940 of gigabit ethernet MACs. Cards using this chipset include
1941 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1942 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1943 zero copy.
1944
1945config HAMACHI
1946 tristate "Packet Engines Hamachi GNIC-II support"
1947 depends on PCI
1948 select MII
1949 help
1950 If you have a Gigabit Ethernet card of this type, say Y and read
1951 the Ethernet-HOWTO, available from
1952 <http://www.tldp.org/docs.html#howto>.
1953
1954 To compile this driver as a module, choose M here and read
1955 <file:Documentation/networking/net-modules.txt>. The module will be
1956 called hamachi.
1957
1958config YELLOWFIN
1959 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1960 depends on PCI && EXPERIMENTAL
1961 select CRC32
1962 ---help---
1963 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1964 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1965 used by the Beowulf Linux cluster project. See
1966 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1967 information about this driver in particular and Beowulf in general.
1968
1969 To compile this driver as a module, choose M here: the module
1970 will be called yellowfin. This is recommended.
1971
1972config R8169
1973 tristate "Realtek 8169 gigabit ethernet support"
1974 depends on PCI
1975 select CRC32
1976 ---help---
1977 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1978
1979 To compile this driver as a module, choose M here: the module
1980 will be called r8169. This is recommended.
1981
1982config R8169_NAPI
1983 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
1984 depends on R8169 && EXPERIMENTAL
1985 help
1986 NAPI is a new driver API designed to reduce CPU and interrupt load
1987 when the driver is receiving lots of packets from the card. It is
1988 still somewhat experimental and thus not yet enabled by default.
1989
1990 If your estimated Rx load is 10kpps or more, or if the card will be
1991 deployed on potentially unfriendly networks (e.g. in a firewall),
1992 then say Y here.
1993
1994 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1995 information.
1996
1997 If in doubt, say N.
1998
1999config R8169_VLAN
2000 bool "VLAN support"
2001 depends on R8169 && VLAN_8021Q
2002 ---help---
2003 Say Y here for the r8169 driver to support the functions required
2004 by the kernel 802.1Q code.
2005
2006 If in doubt, say Y.
2007
Francois Romieu890e8d02005-07-30 13:08:43 +02002008config SIS190
Francois Romieue7976372005-09-03 00:57:51 +02002009 tristate "SiS190/SiS191 gigabit ethernet support"
Adrian Bunke9985d52005-08-09 02:41:00 +02002010 depends on PCI
2011 select CRC32
2012 select MII
2013 ---help---
Francois Romieue7976372005-09-03 00:57:51 +02002014 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2015 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2016 appear in lan on motherboard designs which are based on SiS 965
2017 and SiS 966 south bridge.
Francois Romieu890e8d02005-07-30 13:08:43 +02002018
Adrian Bunke9985d52005-08-09 02:41:00 +02002019 To compile this driver as a module, choose M here: the module
2020 will be called sis190. This is recommended.
Francois Romieu890e8d02005-07-30 13:08:43 +02002021
Stephen Hemmingerbaef58b2005-05-12 20:14:36 -04002022config SKGE
2023 tristate "New SysKonnect GigaEthernet support (EXPERIMENTAL)"
2024 depends on PCI && EXPERIMENTAL
2025 select CRC32
2026 ---help---
2027 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2028 and related Gigabit Ethernet adapters. It is a new smaller driver
Stephen Hemminger46a60f22005-09-09 12:54:56 -07002029 with better performance and more complete ethtool support.
Stephen Hemmingerbaef58b2005-05-12 20:14:36 -04002030
2031 It does not support the link failover and network management
2032 features that "portable" vendor supplied sk98lin driver does.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002033
Daniel Drakec6f0d752006-01-21 19:35:34 +00002034 This driver supports adapters based on the original Yukon chipset:
2035 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2036 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2037
2038 It does not support the newer Yukon2 chipset: a separate driver,
2039 sky2, is provided for Yukon2-based adapters.
2040
2041 To compile this driver as a module, choose M here: the module
2042 will be called skge. This is recommended.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002043
2044config SKY2
2045 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2046 depends on PCI && EXPERIMENTAL
2047 select CRC32
2048 ---help---
Daniel Drakec6f0d752006-01-21 19:35:34 +00002049 This driver supports Gigabit Ethernet adapters based on the the
2050 Marvell Yukon 2 chipset:
2051 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2052 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2053
2054 This driver does not support the original Yukon chipset: a seperate
2055 driver, skge, is provided for Yukon-based adapters.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002056
2057 To compile this driver as a module, choose M here: the module
2058 will be called sky2. This is recommended.
2059
Linus Torvalds1da177e2005-04-16 15:20:36 -07002060config SK98LIN
2061 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2062 depends on PCI
2063 ---help---
2064 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
Daniel Drakec6f0d752006-01-21 19:35:34 +00002065 compliant Gigabit Ethernet Adapter.
2066
2067 This driver supports the original Yukon chipset. A cleaner driver is
2068 also available (skge) which seems to work better than this one.
2069
2070 This driver does not support the newer Yukon2 chipset. A seperate
2071 driver, sky2, is provided to support Yukon2-based adapters.
2072
2073 The following adapters are supported by this driver:
Linus Torvalds1da177e2005-04-16 15:20:36 -07002074 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2075 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2076 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2077 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2078 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2079 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2080 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2081 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2082 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2083 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2084 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
2085 - DGE-530T Gigabit Ethernet Adapter
2086 - EG1032 v2 Instant Gigabit Network Adapter
2087 - EG1064 v2 Instant Gigabit Network Adapter
2088 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2089 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2090 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2091 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2092 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2093 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2094 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2095 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2096 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2097 - Marvell RDK-8001 Adapter
2098 - Marvell RDK-8002 Adapter
2099 - Marvell RDK-8003 Adapter
2100 - Marvell RDK-8004 Adapter
2101 - Marvell RDK-8006 Adapter
2102 - Marvell RDK-8007 Adapter
2103 - Marvell RDK-8008 Adapter
2104 - Marvell RDK-8009 Adapter
2105 - Marvell RDK-8010 Adapter
2106 - Marvell RDK-8011 Adapter
2107 - Marvell RDK-8012 Adapter
2108 - Marvell RDK-8052 Adapter
2109 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2110 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2111 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2112 - SK-9521 10/100/1000Base-T Adapter
2113 - SK-9521 V2.0 10/100/1000Base-T Adapter
2114 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2115 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2116 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2117 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2118 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2119 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2120 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2121 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2122 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2123 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2124 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2125 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2126 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2127 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2128 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2129 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2130 - SMC EZ Card 1000 (SMC9452TXV.2)
2131
2132 The adapters support Jumbo Frames.
2133 The dual link adapters support link-failover and dual port features.
2134 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2135 the scatter-gather functionality with sendfile(). Please refer to
2136 <file:Documentation/networking/sk98lin.txt> for more information about
2137 optional driver parameters.
2138 Questions concerning this driver may be addressed to:
2139 <linux@syskonnect.de>
2140
2141 If you want to compile this driver as a module ( = code which can be
2142 inserted in and removed from the running kernel whenever you want),
2143 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2144 be called sk98lin. This is recommended.
2145
2146config VIA_VELOCITY
2147 tristate "VIA Velocity support"
2148 depends on NET_PCI && PCI
2149 select CRC32
2150 select CRC_CCITT
2151 select MII
2152 help
2153 If you have a VIA "Velocity" based network card say Y here.
2154
2155 To compile this driver as a module, choose M here. The module
2156 will be called via-velocity.
2157
2158config TIGON3
2159 tristate "Broadcom Tigon3 support"
2160 depends on PCI
2161 help
2162 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2163
2164 To compile this driver as a module, choose M here: the module
2165 will be called tg3. This is recommended.
2166
Michael Chanb6016b72005-05-26 13:03:09 -07002167config BNX2
2168 tristate "Broadcom NetXtremeII support"
2169 depends on PCI
2170 help
2171 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2172
2173 To compile this driver as a module, choose M here: the module
2174 will be called bnx2. This is recommended.
2175
Jens Osterkampaaec0fa2005-09-05 15:19:29 -07002176config SPIDER_NET
2177 tristate "Spider Gigabit Ethernet driver"
Jens Osterkampb35de2e2005-12-15 13:42:21 +01002178 depends on PCI && PPC_CELL
Jens Osterkampaaec0fa2005-09-05 15:19:29 -07002179 help
2180 This driver supports the Gigabit Ethernet chips present on the
2181 Cell Processor-Based Blades from IBM.
2182
Linus Torvalds1da177e2005-04-16 15:20:36 -07002183config GIANFAR
2184 tristate "Gianfar Ethernet"
2185 depends on 85xx || 83xx
Andy Flemingbb40dcb2005-09-23 22:54:21 -04002186 select PHYLIB
Linus Torvalds1da177e2005-04-16 15:20:36 -07002187 help
2188 This driver supports the Gigabit TSEC on the MPC85xx
2189 family of chips, and the FEC on the 8540
2190
2191config GFAR_NAPI
2192 bool "NAPI Support"
2193 depends on GIANFAR
2194
2195config MV643XX_ETH
2196 tristate "MV-643XX Ethernet support"
Benjamin Herrenschmidt16b81752005-04-16 15:24:30 -07002197 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
Linus Torvalds1da177e2005-04-16 15:20:36 -07002198 help
2199 This driver supports the gigabit Ethernet on the Marvell MV643XX
2200 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2201 Pegasos II, amongst other PPC and MIPS boards.
2202
2203config MV643XX_ETH_0
2204 bool "MV-643XX Port 0"
2205 depends on MV643XX_ETH
2206 help
2207 This enables support for Port 0 of the Marvell MV643XX Gigabit
2208 Ethernet.
2209
2210config MV643XX_ETH_1
2211 bool "MV-643XX Port 1"
2212 depends on MV643XX_ETH
2213 help
2214 This enables support for Port 1 of the Marvell MV643XX Gigabit
2215 Ethernet.
2216
2217config MV643XX_ETH_2
2218 bool "MV-643XX Port 2"
2219 depends on MV643XX_ETH
2220 help
2221 This enables support for Port 2 of the Marvell MV643XX Gigabit
2222 Ethernet.
2223
2224endmenu
2225
2226#
2227# 10 Gigabit Ethernet
2228#
2229
2230menu "Ethernet (10000 Mbit)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002231 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -07002232
Christoph Lameter8199d3a2005-03-30 13:34:31 -08002233config CHELSIO_T1
2234 tristate "Chelsio 10Gb Ethernet support"
2235 depends on PCI
2236 help
2237 This driver supports Chelsio N110 and N210 models 10Gb Ethernet
2238 cards. More information about adapter features and performance
2239 tuning is in <file:Documentation/networking/cxgb.txt>.
2240
2241 For general information about Chelsio and our products, visit
2242 our website at <http://www.chelsio.com>.
2243
2244 For customer support, please visit our customer support page at
2245 <http://www.chelsio.com/support.htm>.
2246
2247 Please send feedback to <linux-bugs@chelsio.com>.
2248
2249 To compile this driver as a module, choose M here: the module
2250 will be called cxgb.
2251
Linus Torvalds1da177e2005-04-16 15:20:36 -07002252config IXGB
2253 tristate "Intel(R) PRO/10GbE support"
2254 depends on PCI
2255 ---help---
2256 This driver supports Intel(R) PRO/10GbE family of
2257 adapters. For more information on how to identify your adapter, go
2258 to the Adapter & Driver ID Guide at:
2259
2260 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2261
2262 For general information and support, go to the Intel support
2263 website at:
2264
2265 <http://support.intel.com>
2266
2267 More specific information on configuring the driver is in
2268 <file:Documentation/networking/ixgb.txt>.
2269
2270 To compile this driver as a module, choose M here and read
2271 <file:Documentation/networking/net-modules.txt>. The module
2272 will be called ixgb.
2273
2274config IXGB_NAPI
2275 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2276 depends on IXGB && EXPERIMENTAL
2277 help
2278 NAPI is a new driver API designed to reduce CPU and interrupt load
2279 when the driver is receiving lots of packets from the card. It is
2280 still somewhat experimental and thus not yet enabled by default.
2281
2282 If your estimated Rx load is 10kpps or more, or if the card will be
2283 deployed on potentially unfriendly networks (e.g. in a firewall),
2284 then say Y here.
2285
2286 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2287 information.
2288
2289 If in doubt, say N.
2290
2291config S2IO
2292 tristate "S2IO 10Gbe XFrame NIC"
2293 depends on PCI
2294 ---help---
2295 This driver supports the 10Gbe XFrame NIC of S2IO.
Akinobu Mita9eb343a2005-10-21 19:06:42 +09002296 More specific information on configuring the driver is in
2297 <file:Documentation/networking/s2io.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002298
2299config S2IO_NAPI
2300 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2301 depends on S2IO && EXPERIMENTAL
2302 help
2303 NAPI is a new driver API designed to reduce CPU and interrupt load
2304 when the driver is receiving lots of packets from the card. It is
2305 still somewhat experimental and thus not yet enabled by default.
2306
2307 If your estimated Rx load is 10kpps or more, or if the card will be
2308 deployed on potentially unfriendly networks (e.g. in a firewall),
2309 then say Y here.
2310
2311 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2312 information.
2313
2314 If in doubt, say N.
2315
Linus Torvalds1da177e2005-04-16 15:20:36 -07002316endmenu
2317
2318if !UML
2319source "drivers/net/tokenring/Kconfig"
2320
2321source "drivers/net/wireless/Kconfig"
2322
2323source "drivers/net/pcmcia/Kconfig"
2324endif
2325
2326source "drivers/net/wan/Kconfig"
2327
2328source "drivers/atm/Kconfig"
2329
2330source "drivers/s390/net/Kconfig"
2331
2332config ISERIES_VETH
2333 tristate "iSeries Virtual Ethernet driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002334 depends on PPC_ISERIES
Linus Torvalds1da177e2005-04-16 15:20:36 -07002335
Matt Porterf89efd52005-09-09 12:10:10 -07002336config RIONET
2337 tristate "RapidIO Ethernet over messaging driver support"
2338 depends on NETDEVICES && RAPIDIO
2339
2340config RIONET_TX_SIZE
2341 int "Number of outbound queue entries"
2342 depends on RIONET
2343 default "128"
2344
2345config RIONET_RX_SIZE
2346 int "Number of inbound queue entries"
2347 depends on RIONET
2348 default "128"
2349
Linus Torvalds1da177e2005-04-16 15:20:36 -07002350config FDDI
2351 bool "FDDI driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002352 depends on (PCI || EISA)
Linus Torvalds1da177e2005-04-16 15:20:36 -07002353 help
2354 Fiber Distributed Data Interface is a high speed local area network
2355 design; essentially a replacement for high speed Ethernet. FDDI can
2356 run over copper or fiber. If you are connected to such a network and
2357 want a driver for the FDDI card in your computer, say Y here (and
2358 then also Y to the driver for your FDDI card, below). Most people
2359 will say N.
2360
2361config DEFXX
2362 tristate "Digital DEFEA and DEFPA adapter support"
2363 depends on FDDI && (PCI || EISA)
2364 help
2365 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2366 (DEFPA) controllers which can connect you to a local FDDI network.
2367
2368config SKFP
2369 tristate "SysKonnect FDDI PCI support"
2370 depends on FDDI && PCI
2371 ---help---
2372 Say Y here if you have a SysKonnect FDDI PCI adapter.
2373 The following adapters are supported by this driver:
2374 - SK-5521 (SK-NET FDDI-UP)
2375 - SK-5522 (SK-NET FDDI-UP DAS)
2376 - SK-5541 (SK-NET FDDI-FP)
2377 - SK-5543 (SK-NET FDDI-LP)
2378 - SK-5544 (SK-NET FDDI-LP DAS)
2379 - SK-5821 (SK-NET FDDI-UP64)
2380 - SK-5822 (SK-NET FDDI-UP64 DAS)
2381 - SK-5841 (SK-NET FDDI-FP64)
2382 - SK-5843 (SK-NET FDDI-LP64)
2383 - SK-5844 (SK-NET FDDI-LP64 DAS)
2384 - Netelligent 100 FDDI DAS Fibre SC
2385 - Netelligent 100 FDDI SAS Fibre SC
2386 - Netelligent 100 FDDI DAS UTP
2387 - Netelligent 100 FDDI SAS UTP
2388 - Netelligent 100 FDDI SAS Fibre MIC
2389
2390 Read <file:Documentation/networking/skfp.txt> for information about
2391 the driver.
2392
2393 Questions concerning this driver can be addressed to:
2394 <linux@syskonnect.de>
2395
2396 To compile this driver as a module, choose M here: the module
2397 will be called skfp. This is recommended.
2398
2399config HIPPI
2400 bool "HIPPI driver support (EXPERIMENTAL)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002401 depends on EXPERIMENTAL && INET && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07002402 help
2403 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2404 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2405 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2406 single-mode). HIPPI networks are commonly used for clusters and to
2407 connect to super computers. If you are connected to a HIPPI network
2408 and have a HIPPI network card in your computer that you want to use
2409 under Linux, say Y here (you must also remember to enable the driver
2410 for your HIPPI card below). Most people will say N here.
2411
2412config ROADRUNNER
2413 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2414 depends on HIPPI && PCI
2415 help
2416 Say Y here if this is your PCI HIPPI network card.
2417
2418 To compile this driver as a module, choose M here: the module
2419 will be called rrunner. If unsure, say N.
2420
2421config ROADRUNNER_LARGE_RINGS
2422 bool "Use large TX/RX rings (EXPERIMENTAL)"
2423 depends on ROADRUNNER
2424 help
2425 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2426 of additional memory to allow for fastest operation, both for
2427 transmitting and receiving. This memory cannot be used by any other
2428 kernel code or by user space programs. Say Y here only if you have
2429 the memory.
2430
2431config PLIP
2432 tristate "PLIP (parallel port) support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002433 depends on PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07002434 ---help---
2435 PLIP (Parallel Line Internet Protocol) is used to create a
2436 reasonably fast mini network consisting of two (or, rarely, more)
2437 local machines. A PLIP link from a Linux box is a popular means to
2438 install a Linux distribution on a machine which doesn't have a
2439 CD-ROM drive (a minimal system has to be transferred with floppies
2440 first). The kernels on both machines need to have this PLIP option
2441 enabled for this to work.
2442
2443 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2444 ports (the connectors at the computers with 25 holes) are connected
2445 with "null printer" or "Turbo Laplink" cables which can transmit 4
2446 bits at a time (mode 0) or with special PLIP cables, to be used on
2447 bidirectional parallel ports only, which can transmit 8 bits at a
2448 time (mode 1); you can find the wiring of these cables in
2449 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2450 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2451 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2452 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2453 and winsock or NCSA's telnet.
2454
2455 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2456 as the NET-3-HOWTO, both available from
2457 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2458 protocol has been changed and this PLIP driver won't work together
2459 with the PLIP support in Linux versions 1.0.x. This option enlarges
2460 your kernel by about 8 KB.
2461
2462 To compile this driver as a module, choose M here and read
2463 <file:Documentation/networking/net-modules.txt>. The module will be
2464 called plip. If unsure, say Y or M, in case you buy a laptop
2465 later.
2466
2467config PPP
2468 tristate "PPP (point-to-point protocol) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07002469 ---help---
2470 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2471 the same purpose: sending Internet traffic over telephone (and other
2472 serial) lines. Ask your access provider if they support it, because
2473 otherwise you can't use it; most Internet access providers these
2474 days support PPP rather than SLIP.
2475
2476 To use PPP, you need an additional program called pppd as described
2477 in the PPP-HOWTO, available at
2478 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2479 the version of pppd recommended in <file:Documentation/Changes>.
2480 The PPP option enlarges your kernel by about 16 KB.
2481
2482 There are actually two versions of PPP: the traditional PPP for
2483 asynchronous lines, such as regular analog phone lines, and
2484 synchronous PPP which can be used over digital ISDN lines for
2485 example. If you want to use PPP over phone lines or other
2486 asynchronous serial lines, you need to say Y (or M) here and also to
2487 the next option, "PPP support for async serial ports". For PPP over
2488 synchronous lines, you should say Y (or M) here and to "Support
2489 synchronous PPP", below.
2490
2491 If you said Y to "Version information on all symbols" above, then
2492 you cannot compile the PPP driver into the kernel; you can then only
2493 compile it as a module. To compile this driver as a module, choose M
2494 here and read <file:Documentation/networking/net-modules.txt>.
2495 The module will be called ppp_generic.
2496
2497config PPP_MULTILINK
2498 bool "PPP multilink support (EXPERIMENTAL)"
2499 depends on PPP && EXPERIMENTAL
2500 help
2501 PPP multilink is a protocol (defined in RFC 1990) which allows you
2502 to combine several (logical or physical) lines into one logical PPP
2503 connection, so that you can utilize your full bandwidth.
2504
2505 This has to be supported at the other end as well and you need a
2506 version of the pppd daemon which understands the multilink protocol.
2507
2508 If unsure, say N.
2509
2510config PPP_FILTER
2511 bool "PPP filtering"
2512 depends on PPP
2513 help
2514 Say Y here if you want to be able to filter the packets passing over
2515 PPP interfaces. This allows you to control which packets count as
2516 activity (i.e. which packets will reset the idle timer or bring up
Jon Mason47c51432006-02-12 11:53:04 -06002517 a demand-dialed link) and which packets are to be dropped entirely.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002518 You need to say Y here if you wish to use the pass-filter and
2519 active-filter options to pppd.
2520
2521 If unsure, say N.
2522
2523config PPP_ASYNC
2524 tristate "PPP support for async serial ports"
2525 depends on PPP
2526 select CRC_CCITT
2527 ---help---
2528 Say Y (or M) here if you want to be able to use PPP over standard
2529 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2530 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2531 need this option.
2532
2533 To compile this driver as a module, choose M here.
2534
2535 If unsure, say Y.
2536
2537config PPP_SYNC_TTY
2538 tristate "PPP support for sync tty ports"
2539 depends on PPP
2540 help
2541 Say Y (or M) here if you want to be able to use PPP over synchronous
2542 (HDLC) tty devices, such as the SyncLink adapter. These devices
2543 are often used for high-speed leased lines like T1/E1.
2544
2545 To compile this driver as a module, choose M here.
2546
2547config PPP_DEFLATE
2548 tristate "PPP Deflate compression"
2549 depends on PPP
2550 select ZLIB_INFLATE
2551 select ZLIB_DEFLATE
2552 ---help---
2553 Support for the Deflate compression method for PPP, which uses the
2554 Deflate algorithm (the same algorithm that gzip uses) to compress
2555 each PPP packet before it is sent over the wire. The machine at the
2556 other end of the PPP link (usually your ISP) has to support the
2557 Deflate compression method as well for this to be useful. Even if
2558 they don't support it, it is safe to say Y here.
2559
2560 To compile this driver as a module, choose M here.
2561
2562config PPP_BSDCOMP
2563 tristate "PPP BSD-Compress compression"
2564 depends on PPP
2565 ---help---
2566 Support for the BSD-Compress compression method for PPP, which uses
2567 the LZW compression method to compress each PPP packet before it is
2568 sent over the wire. The machine at the other end of the PPP link
2569 (usually your ISP) has to support the BSD-Compress compression
2570 method as well for this to be useful. Even if they don't support it,
2571 it is safe to say Y here.
2572
2573 The PPP Deflate compression method ("PPP Deflate compression",
2574 above) is preferable to BSD-Compress, because it compresses better
2575 and is patent-free.
2576
2577 Note that the BSD compression code will always be compiled as a
2578 module; it is called bsd_comp and will show up in the directory
2579 modules once you have said "make modules". If unsure, say N.
2580
Matt Domschb3f9b922005-11-08 09:40:47 -08002581config PPP_MPPE
2582 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2583 depends on PPP && EXPERIMENTAL
2584 select CRYPTO
2585 select CRYPTO_SHA1
2586 select CRYPTO_ARC4
2587 ---help---
2588 Support for the MPPE Encryption protocol, as employed by the
2589 Microsoft Point-to-Point Tunneling Protocol.
2590
2591 See http://pptpclient.sourceforge.net/ for information on
2592 configuring PPTP clients and servers to utilize this method.
2593
Linus Torvalds1da177e2005-04-16 15:20:36 -07002594config PPPOE
2595 tristate "PPP over Ethernet (EXPERIMENTAL)"
2596 depends on EXPERIMENTAL && PPP
2597 help
2598 Support for PPP over Ethernet.
2599
2600 This driver requires the latest version of pppd from the CVS
2601 repository at cvs.samba.org. Alternatively, see the
2602 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2603 which contains instruction on how to use this driver (under
2604 the heading "Kernel mode PPPoE").
2605
2606config PPPOATM
2607 tristate "PPP over ATM"
2608 depends on ATM && PPP
2609 help
2610 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2611 This implementation does not yet comply with section 8 of RFC2364,
2612 which can lead to bad results if the ATM peer loses state and
2613 changes its encapsulation unilaterally.
2614
2615config SLIP
2616 tristate "SLIP (serial line) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07002617 ---help---
2618 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2619 connect to your Internet service provider or to connect to some
2620 other local Unix box or if you want to configure your Linux box as a
2621 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2622 Internet Protocol) is a protocol used to send Internet traffic over
2623 serial connections such as telephone lines or null modem cables;
2624 nowadays, the protocol PPP is more commonly used for this same
2625 purpose.
2626
2627 Normally, your access provider has to support SLIP in order for you
2628 to be able to use it, but there is now a SLIP emulator called SLiRP
2629 around (available from
2630 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2631 allows you to use SLIP over a regular dial up shell connection. If
2632 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2633 NET-3-HOWTO, available from
2634 <http://www.tldp.org/docs.html#howto>, explains how to
2635 configure SLIP. Note that you don't need this option if you just
2636 want to run term (term is a program which gives you almost full
2637 Internet connectivity if you have a regular dial up shell account on
2638 some Internet connected Unix computer. Read
2639 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2640 support will enlarge your kernel by about 4 KB. If unsure, say N.
2641
2642 To compile this driver as a module, choose M here and read
2643 <file:Documentation/networking/net-modules.txt>. The module will be
2644 called slip.
2645
2646config SLIP_COMPRESSED
2647 bool "CSLIP compressed headers"
2648 depends on SLIP
2649 ---help---
2650 This protocol is faster than SLIP because it uses compression on the
2651 TCP/IP headers (not on the data itself), but it has to be supported
2652 on both ends. Ask your access provider if you are not sure and
2653 answer Y, just in case. You will still be able to use plain SLIP. If
2654 you plan to use SLiRP, the SLIP emulator (available from
2655 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2656 allows you to use SLIP over a regular dial up shell connection, you
2657 definitely want to say Y here. The NET-3-HOWTO, available from
2658 <http://www.tldp.org/docs.html#howto>, explains how to configure
2659 CSLIP. This won't enlarge your kernel.
2660
2661config SLIP_SMART
2662 bool "Keepalive and linefill"
2663 depends on SLIP
2664 help
2665 Adds additional capabilities to the SLIP driver to support the
2666 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2667 analogue lines.
2668
2669config SLIP_MODE_SLIP6
2670 bool "Six bit SLIP encapsulation"
2671 depends on SLIP
2672 help
2673 Just occasionally you may need to run IP over hostile serial
2674 networks that don't pass all control characters or are only seven
2675 bit. Saying Y here adds an extra mode you can use with SLIP:
2676 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2677 the serial device. Naturally, this has to be supported at the other
2678 end of the link as well. It's good enough, for example, to run IP
2679 over the async ports of a Camtec JNT Pad. If unsure, say N.
2680
2681config NET_FC
2682 bool "Fibre Channel driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002683 depends on SCSI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07002684 help
2685 Fibre Channel is a high speed serial protocol mainly used to connect
2686 large storage devices to the computer; it is compatible with and
2687 intended to replace SCSI.
2688
2689 If you intend to use Fibre Channel, you need to have a Fibre channel
2690 adaptor card in your computer; say Y here and to the driver for your
2691 adaptor below. You also should have said Y to "SCSI support" and
2692 "SCSI generic support".
2693
2694config SHAPER
2695 tristate "Traffic Shaper (EXPERIMENTAL)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002696 depends on EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07002697 ---help---
2698 The traffic shaper is a virtual network device that allows you to
2699 limit the rate of outgoing data flow over some other network device.
2700 The traffic that you want to slow down can then be routed through
2701 these virtual devices. See
2702 <file:Documentation/networking/shaper.txt> for more information.
2703
2704 An alternative to this traffic shaper is the experimental
Jon Mason47c51432006-02-12 11:53:04 -06002705 Class-Based Queuing (CBQ) scheduling support which you get if you
2706 say Y to "QoS and/or fair queuing" above.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002707
Linus Torvalds1da177e2005-04-16 15:20:36 -07002708 To compile this driver as a module, choose M here: the module
2709 will be called shaper. If unsure, say N.
2710
2711config NETCONSOLE
2712 tristate "Network console logging support (EXPERIMENTAL)"
Matt Mackall5e43db72005-07-27 15:24:42 -07002713 depends on EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07002714 ---help---
2715 If you want to log kernel messages over the network, enable this.
2716 See <file:Documentation/networking/netconsole.txt> for details.
2717
Randy Dunlap54208992005-07-18 13:45:12 -07002718config NETPOLL
2719 def_bool NETCONSOLE
2720
2721config NETPOLL_RX
2722 bool "Netpoll support for trapping incoming packets"
2723 default n
2724 depends on NETPOLL
2725
2726config NETPOLL_TRAP
2727 bool "Netpoll traffic trapping"
2728 default n
2729 depends on NETPOLL
2730
2731config NET_POLL_CONTROLLER
2732 def_bool NETPOLL
2733
Sam Ravnborgd5950b42005-07-11 21:03:49 -07002734endmenu