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