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