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