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