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