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