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