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