blob: 39189903e35579f921d51e8365f55dc43a22f809 [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
441config MIPS_GT96100ETH
442 bool "MIPS GT96100 Ethernet support"
443 depends on NET_ETHERNET && MIPS_GT96100
444 help
445 Say Y here to support the Ethernet subsystem on your GT96100 card.
446
447config MIPS_AU1X00_ENET
448 bool "MIPS AU1000 Ethernet support"
449 depends on NET_ETHERNET && SOC_AU1X00
Herbert Valerio Riedel0638dec2006-06-01 09:41:04 +0200450 select PHYLIB
Linus Torvalds1da177e2005-04-16 15:20:36 -0700451 select CRC32
452 help
453 If you have an Alchemy Semi AU1X00 based system
454 say Y. Otherwise, say N.
455
456config NET_SB1250_MAC
457 tristate "SB1250 Ethernet support"
458 depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC
459
460config SGI_IOC3_ETH
461 bool "SGI IOC3 Ethernet"
Ralf Baechlef406db82005-11-08 19:10:24 +0000462 depends on NET_ETHERNET && PCI && SGI_IP27
Linus Torvalds1da177e2005-04-16 15:20:36 -0700463 select CRC32
464 select MII
465 help
466 If you have a network (Ethernet) card of this type, say Y and read
467 the Ethernet-HOWTO, available from
468 <http://www.tldp.org/docs.html#howto>.
469
470config SGI_IOC3_ETH_HW_RX_CSUM
471 bool "Receive hardware checksums"
472 depends on SGI_IOC3_ETH && INET
473 default y
474 help
475 The SGI IOC3 network adapter supports TCP and UDP checksums in
476 hardware to offload processing of these checksums from the CPU. At
477 the moment only acceleration of IPv4 is supported. This option
478 enables offloading for checksums on receive. If unsure, say Y.
479
480config SGI_IOC3_ETH_HW_TX_CSUM
481 bool "Transmit hardware checksums"
482 depends on SGI_IOC3_ETH && INET
483 default y
484 help
485 The SGI IOC3 network adapter supports TCP and UDP checksums in
486 hardware to offload processing of these checksums from the CPU. At
487 the moment only acceleration of IPv4 is supported. This option
488 enables offloading for checksums on transmit. If unsure, say Y.
489
Ralf Baechledcbf8472005-10-10 14:51:27 +0100490config MIPS_SIM_NET
491 tristate "MIPS simulator Network device (EXPERIMENTAL)"
492 depends on NETDEVICES && MIPS_SIM && EXPERIMENTAL
493 help
494 The MIPSNET device is a simple Ethernet network device which is
495 emulated by the MIPS Simulator.
496 If you are not using a MIPSsim or are unsure, say N.
497
Linus Torvalds1da177e2005-04-16 15:20:36 -0700498config SGI_O2MACE_ETH
499 tristate "SGI O2 MACE Fast Ethernet support"
500 depends on NET_ETHERNET && SGI_IP32=y
501
502config STNIC
503 tristate "National DP83902AV support"
504 depends on NET_ETHERNET && SUPERH
505 select CRC32
506 help
507 Support for cards based on the National Semiconductor DP83902AV
508 ST-NIC Serial Network Interface Controller for Twisted Pair. This
509 is a 10Mbit/sec Ethernet controller. Product overview and specs at
510 <http://www.national.com/pf/DP/DP83902A.html>.
511
512 If unsure, say N.
513
514config SUNLANCE
515 tristate "Sun LANCE support"
516 depends on NET_ETHERNET && SBUS
517 select CRC32
518 help
519 This driver supports the "le" interface present on all 32-bit Sparc
520 systems, on some older Ultra systems and as an Sbus option. These
521 cards are based on the AMD Lance chipset, which is better known
522 via the NE2100 cards.
523
524 To compile this driver as a module, choose M here: the module
525 will be called sunlance.
526
527config HAPPYMEAL
528 tristate "Sun Happy Meal 10/100baseT support"
529 depends on NET_ETHERNET && (SBUS || PCI)
530 select CRC32
531 help
532 This driver supports the "hme" interface present on most Ultra
533 systems and as an option on older Sbus systems. This driver supports
534 both PCI and Sbus devices. This driver also supports the "qfe" quad
535 100baseT device available in both PCI and Sbus configurations.
536
537 To compile this driver as a module, choose M here: the module
538 will be called sunhme.
539
540config SUNBMAC
541 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
542 depends on NET_ETHERNET && SBUS && EXPERIMENTAL
543 select CRC32
544 help
545 This driver supports the "be" interface available as an Sbus option.
546 This is Sun's older 100baseT Ethernet device.
547
548 To compile this driver as a module, choose M here: the module
549 will be called sunbmac.
550
551config SUNQE
552 tristate "Sun QuadEthernet support"
553 depends on NET_ETHERNET && SBUS
554 select CRC32
555 help
556 This driver supports the "qe" 10baseT Ethernet device, available as
557 an Sbus option. Note that this is not the same as Quad FastEthernet
558 "qfe" which is supported by the Happy Meal driver instead.
559
560 To compile this driver as a module, choose M here: the module
561 will be called sunqe.
562
563config SUNGEM
564 tristate "Sun GEM support"
565 depends on NET_ETHERNET && PCI
566 select CRC32
567 help
568 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
569 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
570
David S. Miller1f26dac2005-09-27 15:24:13 -0700571config CASSINI
572 tristate "Sun Cassini support"
573 depends on NET_ETHERNET && PCI
574 select CRC32
575 help
576 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
577 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
578
Linus Torvalds1da177e2005-04-16 15:20:36 -0700579config NET_VENDOR_3COM
580 bool "3COM cards"
581 depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
582 help
583 If you have a network (Ethernet) card belonging to this class, say Y
584 and read the Ethernet-HOWTO, available from
585 <http://www.tldp.org/docs.html#howto>.
586
587 Note that the answer to this question doesn't directly affect the
588 kernel: saying N will just cause the configurator to skip all
589 the questions about 3COM cards. If you say Y, you will be asked for
590 your specific card in the following questions.
591
592config EL1
593 tristate "3c501 \"EtherLink\" support"
594 depends on NET_VENDOR_3COM && ISA
595 ---help---
596 If you have a network (Ethernet) card of this type, say Y and read
597 the Ethernet-HOWTO, available from
598 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
599 new card, since the 3c501 is slow, broken, and obsolete: you will
600 have problems. Some people suggest to ping ("man ping") a nearby
601 machine every minute ("man cron") when using this card.
602
603 To compile this driver as a module, choose M here and read
604 <file:Documentation/networking/net-modules.txt>. The module
605 will be called 3c501.
606
607config EL2
608 tristate "3c503 \"EtherLink II\" support"
609 depends on NET_VENDOR_3COM && ISA
610 select CRC32
611 help
612 If you have a network (Ethernet) card of this type, say Y and read
613 the Ethernet-HOWTO, available from
614 <http://www.tldp.org/docs.html#howto>.
615
616 To compile this driver as a module, choose M here and read
617 <file:Documentation/networking/net-modules.txt>. The module
618 will be called 3c503.
619
620config ELPLUS
621 tristate "3c505 \"EtherLink Plus\" support"
Al Viroa5532602005-05-04 05:39:42 +0100622 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700623 ---help---
624 Information about this network (Ethernet) card can be found in
625 <file:Documentation/networking/3c505.txt>. If you have a card of
626 this type, say Y and read the Ethernet-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>.
628
629 To compile this driver as a module, choose M here and read
630 <file:Documentation/networking/net-modules.txt>. The module
631 will be called 3c505.
632
633config EL16
634 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
635 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
636 help
637 If you have a network (Ethernet) card of this type, say Y and read
638 the Ethernet-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>.
640
641 To compile this driver as a module, choose M here and read
642 <file:Documentation/networking/net-modules.txt>. The module
643 will be called 3c507.
644
645config EL3
646 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
647 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
648 ---help---
649 If you have a network (Ethernet) card belonging to the 3Com
650 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
651 from <http://www.tldp.org/docs.html#howto>.
652
653 If your card is not working you may need to use the DOS
654 setup disk to disable Plug & Play mode, and to select the default
655 media type.
656
657 To compile this driver as a module, choose M here and read
658 <file:Documentation/networking/net-modules.txt>. The module
659 will be called 3c509.
660
661config 3C515
662 tristate "3c515 ISA \"Fast EtherLink\""
Al Viroa5532602005-05-04 05:39:42 +0100663 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700664 help
665 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
666 network card, say Y and read the Ethernet-HOWTO, available from
667 <http://www.tldp.org/docs.html#howto>.
668
669 To compile this driver as a module, choose M here and read
670 <file:Documentation/networking/net-modules.txt>. The module
671 will be called 3c515.
672
673config ELMC
674 tristate "3c523 \"EtherLink/MC\" support"
675 depends on NET_VENDOR_3COM && MCA_LEGACY
676 help
677 If you have a network (Ethernet) card of this type, say Y and read
678 the Ethernet-HOWTO, available from
679 <http://www.tldp.org/docs.html#howto>.
680
681 To compile this driver as a module, choose M here and read
682 <file:Documentation/networking/net-modules.txt>. The module
683 will be called 3c523.
684
685config ELMC_II
686 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
687 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
688 help
689 If you have a network (Ethernet) card of this type, say Y and read
690 the Ethernet-HOWTO, available from
691 <http://www.tldp.org/docs.html#howto>.
692
693 To compile this driver as a module, choose M here and read
694 <file:Documentation/networking/net-modules.txt>. The module
695 will be called 3c527.
696
697config VORTEX
698 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
699 depends on NET_VENDOR_3COM && (PCI || EISA)
700 select MII
701 ---help---
Jon Mason47c51432006-02-12 11:53:04 -0600702 This option enables driver support for a large number of 10Mbps and
703 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700704
705 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
706 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
707 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
708 "Tornado" (3c905) PCI
709 "Hurricane" (3c555/3cSOHO) PCI
710
711 If you have such a card, say Y and read the Ethernet-HOWTO,
712 available from <http://www.tldp.org/docs.html#howto>. More
713 specific information is in
714 <file:Documentation/networking/vortex.txt> and in the comments at
715 the beginning of <file:drivers/net/3c59x.c>.
716
717 To compile this support as a module, choose M here and read
718 <file:Documentation/networking/net-modules.txt>.
719
720config TYPHOON
721 tristate "3cr990 series \"Typhoon\" support"
722 depends on NET_VENDOR_3COM && PCI
723 select CRC32
724 ---help---
725 This option enables driver support for the 3cr990 series of cards:
726
727 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
728 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
729 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
730
731 If you have a network (Ethernet) card of this type, say Y and read
732 the Ethernet-HOWTO, available from
733 <http://www.tldp.org/docs.html#howto>.
734
735 To compile this driver as a module, choose M here and read
736 <file:Documentation/networking/net-modules.txt>. The module
737 will be called typhoon.
738
739config LANCE
740 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
Al Viroa5532602005-05-04 05:39:42 +0100741 depends on NET_ETHERNET && ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700742 help
743 If you have a network (Ethernet) card of this type, say Y and read
744 the Ethernet-HOWTO, available from
745 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
746 of this type.
747
748 To compile this driver as a module, choose M here: the module
749 will be called lance. This is recommended.
750
751config NET_VENDOR_SMC
752 bool "Western Digital/SMC cards"
753 depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
754 help
755 If you have a network (Ethernet) card belonging to this class, say Y
756 and read the Ethernet-HOWTO, available from
757 <http://www.tldp.org/docs.html#howto>.
758
759 Note that the answer to this question doesn't directly affect the
760 kernel: saying N will just cause the configurator to skip all
761 the questions about Western Digital cards. If you say Y, you will be
762 asked for your specific card in the following questions.
763
764config WD80x3
765 tristate "WD80*3 support"
766 depends on NET_VENDOR_SMC && ISA
767 select CRC32
768 help
769 If you have a network (Ethernet) card of this type, say Y and read
770 the Ethernet-HOWTO, available from
771 <http://www.tldp.org/docs.html#howto>.
772
773 To compile this driver as a module, choose M here and read
774 <file:Documentation/networking/net-modules.txt>. The module
775 will be called wd.
776
777config ULTRAMCA
778 tristate "SMC Ultra MCA support"
779 depends on NET_VENDOR_SMC && MCA
780 select CRC32
781 help
782 If you have a network (Ethernet) card of this type and are running
783 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
784 available from <http://www.tldp.org/docs.html#howto>.
785
786 To compile this driver as a module, choose M here and read
787 <file:Documentation/networking/net-modules.txt>. The module
788 will be called smc-mca.
789
790config ULTRA
791 tristate "SMC Ultra support"
792 depends on NET_VENDOR_SMC && ISA
793 select CRC32
794 ---help---
795 If you have a network (Ethernet) card of this type, say Y and read
796 the Ethernet-HOWTO, available from
797 <http://www.tldp.org/docs.html#howto>.
798
799 Important: There have been many reports that, with some motherboards
800 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
801 such as some BusLogic models) causes corruption problems with many
802 operating systems. The Linux smc-ultra driver has a work-around for
803 this but keep it in mind if you have such a SCSI card and have
804 problems.
805
806 To compile this driver as a module, choose M here and read
807 <file:Documentation/networking/net-modules.txt>. The module
808 will be called smc-ultra.
809
810config ULTRA32
811 tristate "SMC Ultra32 EISA support"
812 depends on NET_VENDOR_SMC && EISA
813 select CRC32
814 help
815 If you have a network (Ethernet) card of this type, say Y and read
816 the Ethernet-HOWTO, available from
817 <http://www.tldp.org/docs.html#howto>.
818
819 To compile this driver as a module, choose M here and read
820 <file:Documentation/networking/net-modules.txt>. The module
821 will be called smc-ultra32.
822
823config SMC91X
824 tristate "SMC 91C9x/91C1xxx support"
825 select CRC32
826 select MII
Pete Popov55793452005-11-09 22:46:05 -0500827 depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700828 help
829 This is a driver for SMC's 91x series of Ethernet chipsets,
830 including the SMC91C94 and the SMC91C111. Say Y if you want it
831 compiled into the kernel, and read the file
832 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
833 available from <http://www.linuxdoc.org/docs.html#howto>.
834
835 This driver is also available as a module ( = code which can be
836 inserted in and removed from the running kernel whenever you want).
837 The module will be called smc91x. If you want to compile it as a
838 module, say M here and read <file:Documentation/modules.txt> as well
839 as <file:Documentation/networking/net-modules.txt>.
840
841config SMC9194
842 tristate "SMC 9194 support"
843 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
844 select CRC32
845 ---help---
846 This is support for the SMC9xxx based Ethernet cards. Choose this
847 option if you have a DELL laptop with the docking station, or
848 another SMC9192/9194 based chipset. Say Y if you want it compiled
849 into the kernel, and read the file
850 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
851 available from <http://www.tldp.org/docs.html#howto>.
852
853 To compile this driver as a module, choose M here and read
854 <file:Documentation/networking/net-modules.txt>. The module
855 will be called smc9194.
856
Sascha Hauer92aa6742006-06-22 07:11:13 +0200857config NET_NETX
858 tristate "NetX Ethernet support"
859 select MII
860 depends on NET_ETHERNET && ARCH_NETX
861 help
862 This is support for the Hilscher netX builtin Ethernet ports
863
864 To compile this driver as a module, choose M here and read
865 <file:Documentation/networking/net-modules.txt>. The module
866 will be called netx-eth.
867
Sascha Hauera1365272005-05-05 15:14:15 -0700868config DM9000
869 tristate "DM9000 support"
Franckb6d08c02006-01-05 22:45:39 -0800870 depends on (ARM || MIPS) && NET_ETHERNET
Sascha Hauera1365272005-05-05 15:14:15 -0700871 select CRC32
872 select MII
873 ---help---
874 Support for DM9000 chipset.
875
876 To compile this driver as a module, choose M here and read
877 <file:Documentation/networking/net-modules.txt>. The module will be
878 called dm9000.
879
Dustin McIntire0a0c72c2006-04-19 20:24:51 -0700880config SMC911X
881 tristate "SMSC LAN911[5678] support"
882 select CRC32
883 select MII
Andrew Mortonb89fa8b2006-06-08 22:19:41 -0700884 depends on NET_ETHERNET && ARCH_PXA
Dustin McIntire0a0c72c2006-04-19 20:24:51 -0700885 help
886 This is a driver for SMSC's LAN911x series of Ethernet chipsets
887 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
888 Say Y if you want it compiled into the kernel,
889 and read the Ethernet-HOWTO, available from
890 <http://www.linuxdoc.org/docs.html#howto>.
891
892 This driver is also available as a module. The module will be
893 called smc911x. If you want to compile it as a module, say M
894 here and read <file:Documentation/modules.txt>
895
Linus Torvalds1da177e2005-04-16 15:20:36 -0700896config NET_VENDOR_RACAL
897 bool "Racal-Interlan (Micom) NI cards"
898 depends on NET_ETHERNET && ISA
899 help
900 If you have a network (Ethernet) card belonging to this class, such
901 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
902 available from <http://www.tldp.org/docs.html#howto>.
903
904 Note that the answer to this question doesn't directly affect the
905 kernel: saying N will just cause the configurator to skip all
906 the questions about NI cards. If you say Y, you will be asked for
907 your specific card in the following questions.
908
909config NI5010
910 tristate "NI5010 support (EXPERIMENTAL)"
911 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
912 ---help---
913 If you have a network (Ethernet) card of this type, say Y and read
914 the Ethernet-HOWTO, available from
915 <http://www.tldp.org/docs.html#howto>. Note that this is still
916 experimental code.
917
918 To compile this driver as a module, choose M here and read
919 <file:Documentation/networking/net-modules.txt>. The module
920 will be called ni5010.
921
922config NI52
923 tristate "NI5210 support"
924 depends on NET_VENDOR_RACAL && ISA
925 help
926 If you have a network (Ethernet) card of this type, say Y and read
927 the Ethernet-HOWTO, available from
928 <http://www.tldp.org/docs.html#howto>.
929
930 To compile this driver as a module, choose M here and read
931 <file:Documentation/networking/net-modules.txt>. The module
932 will be called ni52.
933
934config NI65
935 tristate "NI6510 support"
Al Viroa5532602005-05-04 05:39:42 +0100936 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700937 help
938 If you have a network (Ethernet) card of this type, say Y and read
939 the Ethernet-HOWTO, available from
940 <http://www.tldp.org/docs.html#howto>.
941
942 To compile this driver as a module, choose M here and read
943 <file:Documentation/networking/net-modules.txt>. The module
944 will be called ni65.
945
946source "drivers/net/tulip/Kconfig"
947
948config AT1700
949 tristate "AT1700/1720 support (EXPERIMENTAL)"
950 depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
951 select CRC32
952 ---help---
953 If you have a network (Ethernet) card of this type, say Y and read
954 the Ethernet-HOWTO, available from
955 <http://www.tldp.org/docs.html#howto>.
956
957 To compile this driver as a module, choose M here and read
958 <file:Documentation/networking/net-modules.txt>. The module
959 will be called at1700.
960
961config DEPCA
962 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
963 depends on NET_ETHERNET && (ISA || EISA || MCA)
964 select CRC32
965 ---help---
966 If you have a network (Ethernet) card of this type, say Y and read
967 the Ethernet-HOWTO, available from
968 <http://www.tldp.org/docs.html#howto> as well as
969 <file:drivers/net/depca.c>.
970
971 To compile this driver as a module, choose M here and read
972 <file:Documentation/networking/net-modules.txt>. The module
973 will be called depca.
974
975config HP100
976 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
977 depends on NET_ETHERNET && (ISA || EISA || PCI)
978 help
979 If you have a network (Ethernet) card of this type, say Y and read
980 the Ethernet-HOWTO, available from
981 <http://www.tldp.org/docs.html#howto>.
982
983 To compile this driver as a module, choose M here and read
984 <file:Documentation/networking/net-modules.txt>. The module
985 will be called hp100.
986
987config NET_ISA
988 bool "Other ISA cards"
989 depends on NET_ETHERNET && ISA
990 ---help---
991 If your network (Ethernet) card hasn't been mentioned yet and its
992 bus system (that's the way the cards talks to the other components
993 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
994 Make sure you know the name of your card. Read the Ethernet-HOWTO,
995 available from <http://www.tldp.org/docs.html#howto>.
996
997 If unsure, say Y.
998
999 Note that the answer to this question doesn't directly affect the
1000 kernel: saying N will just cause the configurator to skip all
1001 the remaining ISA network card questions. If you say Y, you will be
1002 asked for your specific card in the following questions.
1003
1004config E2100
1005 tristate "Cabletron E21xx support"
1006 depends on NET_ISA
1007 select CRC32
1008 help
1009 If you have a network (Ethernet) card of this type, say Y and read
1010 the Ethernet-HOWTO, available from
1011 <http://www.tldp.org/docs.html#howto>.
1012
1013 To compile this driver as a module, choose M here and read
1014 <file:Documentation/networking/net-modules.txt>. The module
1015 will be called e2100.
1016
1017config EWRK3
1018 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1019 depends on NET_ISA
1020 select CRC32
1021 ---help---
1022 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1023 cards. If this is for you, say Y and read
1024 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1025 well as the Ethernet-HOWTO, available from
1026 <http://www.tldp.org/docs.html#howto>.
1027
1028 To compile this driver as a module, choose M here and read
1029 <file:Documentation/networking/net-modules.txt>. The module
1030 will be called ewrk3.
1031
1032config EEXPRESS
1033 tristate "EtherExpress 16 support"
1034 depends on NET_ISA
1035 ---help---
1036 If you have an EtherExpress16 network (Ethernet) card, say Y and
1037 read the Ethernet-HOWTO, available from
1038 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1039 EtherExpress16 card used to be regarded as a very poor choice
1040 because the driver was very unreliable. We now have a new driver
1041 that should do better.
1042
1043 To compile this driver as a module, choose M here and read
1044 <file:Documentation/networking/net-modules.txt>. The module
1045 will be called eexpress.
1046
1047config EEXPRESS_PRO
1048 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1049 depends on NET_ISA
1050 ---help---
1051 If you have a network (Ethernet) card of this type, say Y. This
Jon Mason47c51432006-02-12 11:53:04 -06001052 driver supports Intel i82595{FX,TX} based boards. Note however
Linus Torvalds1da177e2005-04-16 15:20:36 -07001053 that the EtherExpress PRO/100 Ethernet card has its own separate
1054 driver. Please read the Ethernet-HOWTO, available from
1055 <http://www.tldp.org/docs.html#howto>.
1056
1057 To compile this driver as a module, choose M here and read
1058 <file:Documentation/networking/net-modules.txt>. The module
1059 will be called eepro.
1060
Linus Torvalds1da177e2005-04-16 15:20:36 -07001061config HPLAN_PLUS
1062 tristate "HP PCLAN+ (27247B and 27252A) support"
1063 depends on NET_ISA
1064 select CRC32
1065 help
1066 If you have a network (Ethernet) card of this type, say Y and read
1067 the Ethernet-HOWTO, available from
1068 <http://www.tldp.org/docs.html#howto>.
1069
1070 To compile this driver as a module, choose M here and read
1071 <file:Documentation/networking/net-modules.txt>. The module
1072 will be called hp-plus.
1073
1074config HPLAN
1075 tristate "HP PCLAN (27245 and other 27xxx series) support"
1076 depends on NET_ISA
1077 select CRC32
1078 help
1079 If you have a network (Ethernet) card of this type, say Y and read
1080 the Ethernet-HOWTO, available from
1081 <http://www.tldp.org/docs.html#howto>.
1082
1083 To compile this driver as a module, choose M here and read
1084 <file:Documentation/networking/net-modules.txt>. The module
1085 will be called hp.
1086
1087config LP486E
1088 tristate "LP486E on board Ethernet"
1089 depends on NET_ISA
1090 help
1091 Say Y here to support the 82596-based on-board Ethernet controller
1092 for the Panther motherboard, which is one of the two shipped in the
1093 Intel Professional Workstation.
1094
1095config ETH16I
1096 tristate "ICL EtherTeam 16i/32 support"
1097 depends on NET_ISA
1098 help
1099 If you have a network (Ethernet) card of this type, say Y and read
1100 the Ethernet-HOWTO, available from
1101 <http://www.tldp.org/docs.html#howto>.
1102
1103 To compile this driver as a module, choose M here and read
1104 <file:Documentation/networking/net-modules.txt>. The module
1105 will be called eth16i.
1106
1107config NE2000
1108 tristate "NE2000/NE1000 support"
1109 depends on NET_ISA || (Q40 && m) || M32R
1110 select CRC32
1111 ---help---
1112 If you have a network (Ethernet) card of this type, say Y and read
1113 the Ethernet-HOWTO, available from
1114 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1115 without a specific driver are compatible with NE2000.
1116
1117 If you have a PCI NE2000 card however, say N here and Y to "PCI
Jesper Juhl28beaf62006-03-08 00:06:31 -08001118 NE2000 and clone support" under "EISA, VLB, PCI and on board
1119 controllers" below. If you have a NE2000 card and are running on
Linus Torvalds1da177e2005-04-16 15:20:36 -07001120 an MCA system (a bus system used on some IBM PS/2 computers and
1121 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1122 below.
1123
1124 To compile this driver as a module, choose M here and read
1125 <file:Documentation/networking/net-modules.txt>. The module
1126 will be called ne.
1127
1128config ZNET
1129 tristate "Zenith Z-Note support (EXPERIMENTAL)"
Al Viroa5532602005-05-04 05:39:42 +01001130 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -07001131 help
1132 The Zenith Z-Note notebook computer has a built-in network
1133 (Ethernet) card, and this is the Linux driver for it. Note that the
1134 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1135 by this driver. Read the Ethernet-HOWTO, available from
1136 <http://www.tldp.org/docs.html#howto>.
1137
1138config SEEQ8005
1139 tristate "SEEQ8005 support (EXPERIMENTAL)"
1140 depends on NET_ISA && EXPERIMENTAL
1141 help
1142 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1143 is for you, read the Ethernet-HOWTO, available from
1144 <http://www.tldp.org/docs.html#howto>.
1145
1146 To compile this driver as a module, choose M here and read
1147 <file:Documentation/networking/net-modules.txt>. The module
1148 will be called seeq8005.
1149
Linus Torvalds1da177e2005-04-16 15:20:36 -07001150config SKMC
1151 tristate "SKnet MCA support"
1152 depends on NET_ETHERNET && MCA && BROKEN
1153 ---help---
1154 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
1155 support" in order to use this driver. Supported cards are the SKnet
1156 Junior MC2 and the SKnet MC2(+). The driver automatically
1157 distinguishes between the two cards. Note that using multiple boards
1158 of different type hasn't been tested with this driver. Say Y if you
1159 have one of these Ethernet adapters.
1160
1161 To compile this driver as a module, choose M here and read
1162 <file:Documentation/networking/net-modules.txt>. The module
1163 will be called sk_mca.
1164
1165config NE2_MCA
1166 tristate "NE/2 (ne2000 MCA version) support"
1167 depends on NET_ETHERNET && MCA_LEGACY
1168 select CRC32
1169 help
1170 If you have a network (Ethernet) card of this type, say Y and read
1171 the Ethernet-HOWTO, available from
1172 <http://www.tldp.org/docs.html#howto>.
1173
1174 To compile this driver as a module, choose M here and read
1175 <file:Documentation/networking/net-modules.txt>. The module
1176 will be called ne2.
1177
1178config IBMLANA
1179 tristate "IBM LAN Adapter/A support"
1180 depends on NET_ETHERNET && MCA && MCA_LEGACY
1181 ---help---
1182 This is a Micro Channel Ethernet adapter. You need to set
1183 CONFIG_MCA to use this driver. It is both available as an in-kernel
1184 driver and as a module.
1185
1186 To compile this driver as a module, choose M here and read
1187 <file:Documentation/networking/net-modules.txt>. The only
1188 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1189 will both support 16K and 32K memory windows, however a 32K window
1190 gives a better security against packet losses. Usage of multiple
1191 boards with this driver should be possible, but has not been tested
1192 up to now due to lack of hardware.
1193
1194config IBMVETH
1195 tristate "IBM LAN Virtual Ethernet support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07001196 depends on NET_ETHERNET && PPC_PSERIES
Linus Torvalds1da177e2005-04-16 15:20:36 -07001197 ---help---
1198 This driver supports virtual ethernet adapters on newer IBM iSeries
1199 and pSeries systems.
1200
1201 To compile this driver as a module, choose M here and read
1202 <file:Documentation/networking/net-modules.txt>. The module will
1203 be called ibmveth.
1204
1205config IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001206 tristate "PowerPC 4xx on-chip Ethernet support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001207 depends on 4xx
Eugene Surovegin37448f72005-10-10 16:58:14 -07001208 help
1209 This driver supports the PowerPC 4xx EMAC family of on-chip
1210 Ethernet controllers.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001211
1212config IBM_EMAC_RXB
1213 int "Number of receive buffers"
1214 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001215 default "128"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001216
1217config IBM_EMAC_TXB
1218 int "Number of transmit buffers"
1219 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001220 default "64"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001221
Eugene Surovegin37448f72005-10-10 16:58:14 -07001222config IBM_EMAC_POLL_WEIGHT
1223 int "MAL NAPI polling weight"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001224 depends on IBM_EMAC
Eugene Surovegin37448f72005-10-10 16:58:14 -07001225 default "32"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001226
Eugene Surovegin37448f72005-10-10 16:58:14 -07001227config IBM_EMAC_RX_COPY_THRESHOLD
1228 int "RX skb copy threshold (bytes)"
1229 depends on IBM_EMAC
1230 default "256"
1231
1232config IBM_EMAC_RX_SKB_HEADROOM
1233 int "Additional RX skb headroom (bytes)"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001234 depends on IBM_EMAC
1235 default "0"
Eugene Surovegin37448f72005-10-10 16:58:14 -07001236 help
1237 Additional receive skb headroom. Note, that driver
1238 will always reserve at least 2 bytes to make IP header
Jon Mason47c51432006-02-12 11:53:04 -06001239 aligned, so usually there is no need to add any additional
Eugene Surovegin37448f72005-10-10 16:58:14 -07001240 headroom.
1241
1242 If unsure, set to 0.
1243
1244config IBM_EMAC_PHY_RX_CLK_FIX
1245 bool "PHY Rx clock workaround"
Eugene Surovegin1b195912005-10-29 12:45:31 -07001246 depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
Eugene Surovegin37448f72005-10-10 16:58:14 -07001247 help
1248 Enable this if EMAC attached to a PHY which doesn't generate
1249 RX clock if there is no link, if this is the case, you will
1250 see "TX disable timeout" or "RX disable timeout" in the system
1251 log.
1252
1253 If unsure, say N.
1254
1255config IBM_EMAC_DEBUG
1256 bool "Debugging"
1257 depends on IBM_EMAC
1258 default n
1259
1260config IBM_EMAC_ZMII
1261 bool
1262 depends on IBM_EMAC && (NP405H || NP405L || 44x)
1263 default y
1264
1265config IBM_EMAC_RGMII
1266 bool
1267 depends on IBM_EMAC && 440GX
1268 default y
1269
1270config IBM_EMAC_TAH
1271 bool
1272 depends on IBM_EMAC && 440GX
1273 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001274
1275config NET_PCI
1276 bool "EISA, VLB, PCI and on board controllers"
1277 depends on NET_ETHERNET && (ISA || EISA || PCI)
1278 help
1279 This is another class of network cards which attach directly to the
1280 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1281 available from <http://www.tldp.org/docs.html#howto>.
1282
1283 Note that the answer to this question doesn't directly affect the
1284 kernel: saying N will just cause the configurator to skip all
1285 the questions about this class of network cards. If you say Y, you
1286 will be asked for your specific card in the following questions. If
1287 you are unsure, say Y.
1288
1289config PCNET32
1290 tristate "AMD PCnet32 PCI support"
1291 depends on NET_PCI && PCI
1292 select CRC32
1293 select MII
1294 help
1295 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1296 answer Y here and read the Ethernet-HOWTO, available from
1297 <http://www.tldp.org/docs.html#howto>.
1298
1299 To compile this driver as a module, choose M here and read
1300 <file:Documentation/networking/net-modules.txt>. The module
1301 will be called pcnet32.
1302
1303config AMD8111_ETH
1304 tristate "AMD 8111 (new PCI lance) support"
1305 depends on NET_PCI && PCI
1306 select CRC32
1307 select MII
1308 help
1309 If you have an AMD 8111-based PCI lance ethernet card,
1310 answer Y here and read the Ethernet-HOWTO, available from
1311 <http://www.tldp.org/docs.html#howto>.
1312
1313 To compile this driver as a module, choose M here and read
1314 <file:Documentation/networking/net-modules.txt>. The module
1315 will be called amd8111e.
1316config AMD8111E_NAPI
1317 bool "Enable NAPI support"
1318 depends on AMD8111_ETH
1319 help
1320 NAPI is a new driver API designed to reduce CPU and interrupt load
1321 when the driver is receiving lots of packets from the card. It is
1322 still somewhat experimental and thus not yet enabled by default.
1323
1324 If your estimated Rx load is 10kpps or more, or if the card will be
1325 deployed on potentially unfriendly networks (e.g. in a firewall),
1326 then say Y here.
1327
1328 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1329 information.
1330
1331 If in doubt, say N.
1332
1333config ADAPTEC_STARFIRE
1334 tristate "Adaptec Starfire/DuraLAN support"
1335 depends on NET_PCI && PCI
1336 select CRC32
1337 select MII
1338 help
1339 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1340 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1341 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1342 driver.
1343
1344 To compile this driver as a module, choose M here: the module
1345 will be called starfire. This is recommended.
1346
1347config ADAPTEC_STARFIRE_NAPI
1348 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1349 depends on ADAPTEC_STARFIRE && EXPERIMENTAL
1350 help
1351 NAPI is a new driver API designed to reduce CPU and interrupt load
1352 when the driver is receiving lots of packets from the card. It is
1353 still somewhat experimental and thus not yet enabled by default.
1354
1355 If your estimated Rx load is 10kpps or more, or if the card will be
1356 deployed on potentially unfriendly networks (e.g. in a firewall),
1357 then say Y here.
1358
1359 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1360 information.
1361
1362 If in doubt, say N.
1363
1364config AC3200
1365 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1366 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1367 select CRC32
1368 help
1369 If you have a network (Ethernet) card of this type, say Y and read
1370 the Ethernet-HOWTO, available from
1371 <http://www.tldp.org/docs.html#howto>.
1372
1373 To compile this driver as a module, choose M here and read
1374 <file:Documentation/networking/net-modules.txt>. The module
1375 will be called ac3200.
1376
1377config APRICOT
1378 tristate "Apricot Xen-II on board Ethernet"
1379 depends on NET_PCI && ISA
1380 help
1381 If you have a network (Ethernet) controller of this type, say Y and
1382 read the Ethernet-HOWTO, available from
1383 <http://www.tldp.org/docs.html#howto>.
1384
1385 To compile this driver as a module, choose M here and read
1386 <file:Documentation/networking/net-modules.txt>. The module will be
1387 called apricot.
1388
1389config B44
Gary Zambranofc13dca2006-06-20 15:34:46 -07001390 tristate "Broadcom 4400 ethernet support"
1391 depends on NET_PCI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07001392 select MII
1393 help
1394 If you have a network (Ethernet) controller of this type, say Y and
1395 read the Ethernet-HOWTO, available from
1396 <http://www.tldp.org/docs.html#howto>.
1397
1398 To compile this driver as a module, choose M here and read
1399 <file:Documentation/networking/net-modules.txt>. The module will be
1400 called b44.
1401
1402config FORCEDETH
Adrian Bunk82770082006-03-08 00:06:30 -08001403 tristate "nForce Ethernet support"
1404 depends on NET_PCI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07001405 help
1406 If you have a network (Ethernet) controller of this type, say Y and
1407 read the Ethernet-HOWTO, available from
1408 <http://www.tldp.org/docs.html#howto>.
1409
1410 To compile this driver as a module, choose M here and read
1411 <file:Documentation/networking/net-modules.txt>. The module will be
1412 called forcedeth.
1413
1414
1415config CS89x0
1416 tristate "CS89x0 support"
Deepak Saxena9c878962006-01-14 13:21:18 -08001417 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001418 ---help---
1419 Support for CS89x0 chipset based Ethernet cards. If you have a
1420 network (Ethernet) card of this type, say Y and read the
1421 Ethernet-HOWTO, available from
1422 <http://www.tldp.org/docs.html#howto> as well as
1423 <file:Documentation/networking/cs89x0.txt>.
1424
1425 To compile this driver as a module, choose M here and read
1426 <file:Documentation/networking/net-modules.txt>. The module will be
Jean Delvarefd85d762006-01-11 12:17:36 -08001427 called cs89x0.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001428
1429config TC35815
1430 tristate "TOSHIBA TC35815 Ethernet support"
1431 depends on NET_PCI && PCI && TOSHIBA_JMR3927
1432
1433config DGRS
1434 tristate "Digi Intl. RightSwitch SE-X support"
1435 depends on NET_PCI && (PCI || EISA)
1436 ---help---
1437 This is support for the Digi International RightSwitch series of
1438 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
1439 models. If you have a network card of this type, say Y and read the
1440 Ethernet-HOWTO, available from
1441 <http://www.tldp.org/docs.html#howto>. More specific
1442 information is contained in <file:Documentation/networking/dgrs.txt>.
1443
1444 To compile this driver as a module, choose M here and read
1445 <file:Documentation/networking/net-modules.txt>. The module
1446 will be called dgrs.
1447
1448config EEPRO100
1449 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
1450 depends on NET_PCI && PCI
1451 select MII
1452 help
1453 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
1454 card, say Y and read the Ethernet-HOWTO, available from
1455 <http://www.tldp.org/docs.html#howto>.
1456
1457 To compile this driver as a module, choose M here and read
1458 <file:Documentation/networking/net-modules.txt>. The module
1459 will be called eepro100.
1460
1461
1462config E100
1463 tristate "Intel(R) PRO/100+ support"
1464 depends on NET_PCI && PCI
1465 select MII
1466 ---help---
1467 This driver supports Intel(R) PRO/100 family of adapters.
1468 To verify that your adapter is supported, find the board ID number
1469 on the adapter. Look for a label that has a barcode and a number
1470 in the format 123456-001 (six digits hyphen three digits).
1471
1472 Use the above information and the Adapter & Driver ID Guide at:
1473
1474 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1475
1476 to identify the adapter.
1477
1478 For the latest Intel PRO/100 network driver for Linux, see:
1479
1480 <http://appsr.intel.com/scripts-df/support_intel.asp>
1481
1482 More specific information on configuring the driver is in
1483 <file:Documentation/networking/e100.txt>.
1484
1485 To compile this driver as a module, choose M here and read
1486 <file:Documentation/networking/net-modules.txt>. The module
1487 will be called e100.
1488
1489config LNE390
1490 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1491 depends on NET_PCI && EISA && EXPERIMENTAL
1492 select CRC32
1493 help
1494 If you have a network (Ethernet) card of this type, say Y and read
1495 the Ethernet-HOWTO, available from
1496 <http://www.tldp.org/docs.html#howto>.
1497
1498 To compile this driver as a module, choose M here and read
1499 <file:Documentation/networking/net-modules.txt>. The module
1500 will be called lne390.
1501
1502config FEALNX
1503 tristate "Myson MTD-8xx PCI Ethernet support"
1504 depends on NET_PCI && PCI
1505 select CRC32
1506 select MII
1507 help
1508 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1509 cards. Specifications and data at
1510 <http://www.myson.com.hk/mtd/datasheet/>.
1511
1512config NATSEMI
1513 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1514 depends on NET_PCI && PCI
1515 select CRC32
1516 help
1517 This driver is for the National Semiconductor DP83810 series,
1518 which is used in cards from PureData, NetGear, Linksys
1519 and others, including the 83815 chip.
1520 More specific information and updates are available from
1521 <http://www.scyld.com/network/natsemi.html>.
1522
1523config NE2K_PCI
1524 tristate "PCI NE2000 and clones support (see help)"
1525 depends on NET_PCI && PCI
1526 select CRC32
1527 ---help---
1528 This driver is for NE2000 compatible PCI cards. It will not work
1529 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1530 support" below). If you have a PCI NE2000 network (Ethernet) card,
1531 say Y and read the Ethernet-HOWTO, available from
1532 <http://www.tldp.org/docs.html#howto>.
1533
1534 This driver also works for the following NE2000 clone cards:
1535 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1536 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1537 Holtek HT80232 Holtek HT80229
1538
1539 To compile this driver as a module, choose M here and read
1540 <file:Documentation/networking/net-modules.txt>. The module
1541 will be called ne2k-pci.
1542
1543config NE3210
1544 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1545 depends on NET_PCI && EISA && EXPERIMENTAL
1546 select CRC32
1547 ---help---
1548 If you have a network (Ethernet) card of this type, say Y and read
1549 the Ethernet-HOWTO, available from
1550 <http://www.tldp.org/docs.html#howto>. Note that this driver
1551 will NOT WORK for NE3200 cards as they are completely different.
1552
1553 To compile this driver as a module, choose M here and read
1554 <file:Documentation/networking/net-modules.txt>. The module
1555 will be called ne3210.
1556
1557config ES3210
1558 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1559 depends on NET_PCI && EISA && EXPERIMENTAL
1560 select CRC32
1561 help
1562 If you have a network (Ethernet) card of this type, say Y and read
1563 the Ethernet-HOWTO, available from
1564 <http://www.tldp.org/docs.html#howto>.
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 es3210.
1569
1570config 8139CP
1571 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1572 depends on NET_PCI && PCI && EXPERIMENTAL
1573 select CRC32
1574 select MII
1575 help
1576 This is a driver for the Fast Ethernet PCI network cards based on
1577 the RTL8139C+ chips. If you have one of those, say Y and read
1578 the Ethernet-HOWTO, available from
1579 <http://www.tldp.org/docs.html#howto>.
1580
1581 To compile this driver as a module, choose M here: the module
1582 will be called 8139cp. This is recommended.
1583
1584config 8139TOO
Adrian Bunkf04e3f02005-05-16 21:13:03 +02001585 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001586 depends on NET_PCI && PCI
1587 select CRC32
1588 select MII
1589 ---help---
1590 This is a driver for the Fast Ethernet PCI network cards based on
Adrian Bunkf04e3f02005-05-16 21:13:03 +02001591 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1592 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001593
1594 To compile this driver as a module, choose M here: the module
1595 will be called 8139too. This is recommended.
1596
1597config 8139TOO_PIO
1598 bool "Use PIO instead of MMIO"
1599 default y
1600 depends on 8139TOO
1601 help
1602 This instructs the driver to use programmed I/O ports (PIO) instead
1603 of PCI shared memory (MMIO). This can possibly solve some problems
1604 in case your mainboard has memory consistency issues. If unsure,
1605 say N.
1606
1607config 8139TOO_TUNE_TWISTER
1608 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1609 depends on 8139TOO
1610 help
1611 This implements a function which might come in handy in case you
1612 are using low quality on long cabling. It is required for RealTek
1613 RTL-8139 revision K boards, and totally unused otherwise. It tries
1614 to match the transceiver to the cable characteristics. This is
1615 experimental since hardly documented by the manufacturer.
1616 If unsure, say Y.
1617
1618config 8139TOO_8129
1619 bool "Support for older RTL-8129/8130 boards"
1620 depends on 8139TOO
1621 help
1622 This enables support for the older and uncommon RTL-8129 and
1623 RTL-8130 chips, which support MII via an external transceiver,
1624 instead of an internal one. Disabling this option will save some
1625 memory by making the code size smaller. If unsure, say Y.
1626
1627config 8139_OLD_RX_RESET
1628 bool "Use older RX-reset method"
1629 depends on 8139TOO
1630 help
1631 The 8139too driver was recently updated to contain a more rapid
1632 reset sequence, in the face of severe receive errors. This "new"
1633 RX-reset method should be adequate for all boards. But if you
1634 experience problems, you can enable this option to restore the
1635 old RX-reset behavior. If unsure, say N.
1636
1637config SIS900
1638 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1639 depends on NET_PCI && PCI
1640 select CRC32
Adrian Bunk6da0f682005-04-30 13:52:49 +02001641 select MII
Linus Torvalds1da177e2005-04-16 15:20:36 -07001642 ---help---
1643 This is a driver for the Fast Ethernet PCI network cards based on
1644 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
Adrian Bunkc3cf5602006-03-04 17:07:57 +01001645 SiS 630 and SiS 540 chipsets.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001646
1647 This driver also supports AMD 79C901 HomePNA so that you can use
1648 your phone line as a network cable.
1649
1650 To compile this driver as a module, choose M here: the module
1651 will be called sis900. This is recommended.
1652
1653config EPIC100
1654 tristate "SMC EtherPower II"
1655 depends on NET_PCI && PCI
1656 select CRC32
1657 select MII
1658 help
1659 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1660 which is based on the SMC83c17x (EPIC/100).
1661 More specific information and updates are available from
1662 <http://www.scyld.com/network/epic100.html>.
1663
1664config SUNDANCE
1665 tristate "Sundance Alta support"
1666 depends on NET_PCI && PCI
1667 select CRC32
1668 select MII
1669 help
1670 This driver is for the Sundance "Alta" chip.
1671 More specific information and updates are available from
1672 <http://www.scyld.com/network/sundance.html>.
1673
1674config SUNDANCE_MMIO
1675 bool "Use MMIO instead of PIO"
1676 depends on SUNDANCE
1677 help
1678 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1679 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1680 is known to solve bugs on certain chips.
1681
1682 If unsure, say N.
1683
1684config TLAN
1685 tristate "TI ThunderLAN support"
1686 depends on NET_PCI && (PCI || EISA) && !64BIT
1687 ---help---
1688 If you have a PCI Ethernet network card based on the ThunderLAN chip
1689 which is supported by this driver, say Y and read the
1690 Ethernet-HOWTO, available from
1691 <http://www.tldp.org/docs.html#howto>.
1692
1693 Devices currently supported by this driver are Compaq Netelligent,
1694 Compaq NetFlex and Olicom cards. Please read the file
1695 <file:Documentation/networking/tlan.txt> for more details.
1696
1697 To compile this driver as a module, choose M here and read
1698 <file:Documentation/networking/net-modules.txt>. The module
1699 will be called tlan.
1700
1701 Please email feedback to <torben.mathiasen@compaq.com>.
1702
1703config VIA_RHINE
1704 tristate "VIA Rhine support"
1705 depends on NET_PCI && PCI
1706 select CRC32
1707 select MII
1708 help
1709 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1710 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1711 Ethernet functions can also be found integrated on South Bridges
1712 (e.g. VT8235).
1713
1714 To compile this driver as a module, choose M here. The module
1715 will be called via-rhine.
1716
1717config VIA_RHINE_MMIO
1718 bool "Use MMIO instead of PIO"
1719 depends on VIA_RHINE
1720 help
1721 This instructs the driver to use PCI shared memory (MMIO) instead of
1722 programmed I/O ports (PIO). Enabling this gives an improvement in
1723 processing time in parts of the driver.
1724
1725 If unsure, say Y.
1726
1727config LAN_SAA9730
1728 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
1729 depends on NET_PCI && EXPERIMENTAL && MIPS
1730 help
1731 The SAA9730 is a combined multimedia and peripheral controller used
1732 in thin clients, Internet access terminals, and diskless
1733 workstations.
1734 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
1735
1736config NET_POCKET
1737 bool "Pocket and portable adapters"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001738 depends on NET_ETHERNET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001739 ---help---
1740 Cute little network (Ethernet) devices which attach to the parallel
1741 port ("pocket adapters"), commonly used with laptops. If you have
1742 one of those, say Y and read the Ethernet-HOWTO, available from
1743 <http://www.tldp.org/docs.html#howto>.
1744
1745 If you want to plug a network (or some other) card into the PCMCIA
1746 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1747 credit card size extension cards used by all modern laptops), you
1748 need the pcmcia-cs package (location contained in the file
1749 <file:Documentation/Changes>) and you can say N here.
1750
1751 Laptop users should read the Linux Laptop home page at
1752 <http://www.linux-on-laptops.com/> or
1753 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1754
1755 Note that the answer to this question doesn't directly affect the
1756 kernel: saying N will just cause the configurator to skip all
1757 the questions about this class of network devices. If you say Y, you
1758 will be asked for your specific device in the following questions.
1759
1760config ATP
1761 tristate "AT-LAN-TEC/RealTek pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001762 depends on NET_POCKET && PARPORT && X86
Linus Torvalds1da177e2005-04-16 15:20:36 -07001763 select CRC32
1764 ---help---
1765 This is a network (Ethernet) device which attaches to your parallel
1766 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1767 available from <http://www.tldp.org/docs.html#howto>, if you
1768 want to use this. If you intend to use this driver, you should have
1769 said N to the "Parallel printer support", because the two drivers
1770 don't like each other.
1771
1772 To compile this driver as a module, choose M here: the module
1773 will be called atp.
1774
1775config DE600
1776 tristate "D-Link DE600 pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001777 depends on NET_POCKET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001778 ---help---
1779 This is a network (Ethernet) device which attaches to your parallel
1780 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1781 Ethernet-HOWTO, available from
1782 <http://www.tldp.org/docs.html#howto>, if you want to use
1783 this. It is possible to have several devices share a single parallel
1784 port and it is safe to compile the corresponding drivers into the
1785 kernel.
1786
1787 To compile this driver as a module, choose M here: the module
1788 will be called de600.
1789
1790config DE620
1791 tristate "D-Link DE620 pocket adapter support"
Grant Coady32fa2bf2005-09-10 00:14:05 +10001792 depends on NET_POCKET && PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07001793 ---help---
1794 This is a network (Ethernet) device which attaches to your parallel
1795 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1796 Ethernet-HOWTO, available from
1797 <http://www.tldp.org/docs.html#howto>, if you want to use
1798 this. It is possible to have several devices share a single parallel
1799 port and it is safe to compile the corresponding drivers into the
1800 kernel.
1801
1802 To compile this driver as a module, choose M here: the module
1803 will be called de620.
1804
1805config SGISEEQ
1806 tristate "SGI Seeq ethernet controller support"
1807 depends on NET_ETHERNET && SGI_IP22
1808 help
1809 Say Y here if you have an Seeq based Ethernet network card. This is
1810 used in many Silicon Graphics machines.
1811
1812config DECLANCE
1813 tristate "DEC LANCE ethernet controller support"
1814 depends on NET_ETHERNET && MACH_DECSTATION
1815 select CRC32
1816 help
1817 This driver is for the series of Ethernet controllers produced by
1818 DEC (now Compaq) based on the AMD Lance chipset, including the
1819 DEPCA series. (This chipset is better known via the NE2100 cards.)
1820
1821config 68360_ENET
1822 bool "Motorola 68360 ethernet controller"
1823 depends on M68360
1824 help
1825 Say Y here if you want to use the built-in ethernet controller of
1826 the Motorola 68360 processor.
1827
1828config FEC
Greg Ungerer2af69212005-09-12 11:18:10 +10001829 bool "FEC ethernet controller (of ColdFire CPUs)"
Greg Ungerer892b6252006-01-10 16:58:16 +10001830 depends on M523x || M527x || M5272 || M528x || M520x
Linus Torvalds1da177e2005-04-16 15:20:36 -07001831 help
1832 Say Y here if you want to use the built-in 10/100 Fast ethernet
Greg Ungerer2af69212005-09-12 11:18:10 +10001833 controller on some Motorola ColdFire processors.
1834
1835config FEC2
1836 bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1837 depends on FEC
1838 help
1839 Say Y here if you want to use the second built-in 10/100 Fast
1840 ethernet controller on some Motorola ColdFire processors.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001841
1842config NE_H8300
1843 tristate "NE2000 compatible support for H8/300"
1844 depends on H8300 && NET_ETHERNET
1845 help
1846 Say Y here if you want to use the NE2000 compatible
1847 controller on the Renesas H8/300 processor.
1848
1849source "drivers/net/fec_8xx/Kconfig"
Pantelis Antoniou48257c42005-10-28 16:25:58 -04001850source "drivers/net/fs_enet/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001851
1852endmenu
1853
1854#
1855# Gigabit Ethernet
1856#
1857
1858menu "Ethernet (1000 Mbit)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07001859 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -07001860
1861config ACENIC
1862 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1863 depends on PCI
1864 ---help---
1865 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1866 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1867 adapter. The driver allows for using the Jumbo Frame option (9000
1868 bytes/frame) however it requires that your switches can handle this
1869 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1870 line.
1871
1872 To compile this driver as a module, choose M here: the
1873 module will be called acenic.
1874
1875config ACENIC_OMIT_TIGON_I
1876 bool "Omit support for old Tigon I based AceNICs"
1877 depends on ACENIC
1878 help
1879 Say Y here if you only have Tigon II based AceNICs and want to leave
1880 out support for the older Tigon I based cards which are no longer
1881 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1882 version)). This will reduce the size of the driver object by
1883 app. 100KB. If you are not sure whether your card is a Tigon I or a
1884 Tigon II, say N here.
1885
1886 The safe and default value for this is N.
1887
1888config DL2K
1889 tristate "D-Link DL2000-based Gigabit Ethernet support"
1890 depends on PCI
1891 select CRC32
1892 help
1893 This driver supports D-Link 2000-based gigabit ethernet cards, which
1894 includes
1895 D-Link DGE-550T Gigabit Ethernet Adapter.
1896 D-Link DL2000-based Gigabit Ethernet Adapter.
1897
1898 To compile this driver as a module, choose M here: the
1899 module will be called dl2k.
1900
1901config E1000
1902 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1903 depends on PCI
1904 ---help---
1905 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1906 adapters. For more information on how to identify your adapter, go
1907 to the Adapter & Driver ID Guide at:
1908
1909 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1910
1911 For general information and support, go to the Intel support
1912 website at:
1913
1914 <http://support.intel.com>
1915
1916 More specific information on configuring the driver is in
1917 <file:Documentation/networking/e1000.txt>.
1918
1919 To compile this driver as a module, choose M here and read
1920 <file:Documentation/networking/net-modules.txt>. The module
1921 will be called e1000.
1922
1923config E1000_NAPI
1924 bool "Use Rx Polling (NAPI)"
1925 depends on E1000
1926 help
1927 NAPI is a new driver API designed to reduce CPU and interrupt load
1928 when the driver is receiving lots of packets from the card. It is
1929 still somewhat experimental and thus not yet enabled by default.
1930
1931 If your estimated Rx load is 10kpps or more, or if the card will be
1932 deployed on potentially unfriendly networks (e.g. in a firewall),
1933 then say Y here.
1934
1935 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
1936 information.
1937
1938 If in doubt, say N.
1939
Jesse Brandeburg35ec56b2006-01-18 13:01:30 -08001940config E1000_DISABLE_PACKET_SPLIT
1941 bool "Disable Packet Split for PCI express adapters"
1942 depends on E1000
1943 help
1944 Say Y here if you want to use the legacy receive path for PCI express
James Ring9e6b4872006-03-22 00:51:11 +01001945 hardware.
Jesse Brandeburg35ec56b2006-01-18 13:01:30 -08001946
1947 If in doubt, say N.
1948
Lennert Buytenhek15d014d2005-11-11 18:23:13 +01001949source "drivers/net/ixp2000/Kconfig"
1950
Linus Torvalds1da177e2005-04-16 15:20:36 -07001951config MYRI_SBUS
1952 tristate "MyriCOM Gigabit Ethernet support"
1953 depends on SBUS
1954 help
1955 This driver supports MyriCOM Sbus gigabit Ethernet cards.
1956
1957 To compile this driver as a module, choose M here: the module
1958 will be called myri_sbus. This is recommended.
1959
1960config NS83820
Jon Mason47c51432006-02-12 11:53:04 -06001961 tristate "National Semiconductor DP83820 support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001962 depends on PCI
1963 help
1964 This is a driver for the National Semiconductor DP83820 series
1965 of gigabit ethernet MACs. Cards using this chipset include
1966 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1967 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
1968 zero copy.
1969
1970config HAMACHI
1971 tristate "Packet Engines Hamachi GNIC-II support"
1972 depends on PCI
1973 select MII
1974 help
1975 If you have a Gigabit Ethernet card of this type, say Y and read
1976 the Ethernet-HOWTO, available from
1977 <http://www.tldp.org/docs.html#howto>.
1978
1979 To compile this driver as a module, choose M here and read
1980 <file:Documentation/networking/net-modules.txt>. The module will be
1981 called hamachi.
1982
1983config YELLOWFIN
1984 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1985 depends on PCI && EXPERIMENTAL
1986 select CRC32
1987 ---help---
1988 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1989 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1990 used by the Beowulf Linux cluster project. See
1991 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1992 information about this driver in particular and Beowulf in general.
1993
1994 To compile this driver as a module, choose M here: the module
1995 will be called yellowfin. This is recommended.
1996
1997config R8169
1998 tristate "Realtek 8169 gigabit ethernet support"
1999 depends on PCI
2000 select CRC32
2001 ---help---
2002 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2003
2004 To compile this driver as a module, choose M here: the module
2005 will be called r8169. This is recommended.
2006
2007config R8169_NAPI
2008 bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
2009 depends on R8169 && EXPERIMENTAL
2010 help
2011 NAPI is a new driver API designed to reduce CPU and interrupt load
2012 when the driver is receiving lots of packets from the card. It is
2013 still somewhat experimental and thus not yet enabled by default.
2014
2015 If your estimated Rx load is 10kpps or more, or if the card will be
2016 deployed on potentially unfriendly networks (e.g. in a firewall),
2017 then say Y here.
2018
2019 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2020 information.
2021
2022 If in doubt, say N.
2023
2024config R8169_VLAN
2025 bool "VLAN support"
2026 depends on R8169 && VLAN_8021Q
2027 ---help---
2028 Say Y here for the r8169 driver to support the functions required
2029 by the kernel 802.1Q code.
2030
2031 If in doubt, say Y.
2032
Francois Romieu890e8d02005-07-30 13:08:43 +02002033config SIS190
Francois Romieue7976372005-09-03 00:57:51 +02002034 tristate "SiS190/SiS191 gigabit ethernet support"
Adrian Bunke9985d52005-08-09 02:41:00 +02002035 depends on PCI
2036 select CRC32
2037 select MII
2038 ---help---
Francois Romieue7976372005-09-03 00:57:51 +02002039 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2040 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2041 appear in lan on motherboard designs which are based on SiS 965
2042 and SiS 966 south bridge.
Francois Romieu890e8d02005-07-30 13:08:43 +02002043
Adrian Bunke9985d52005-08-09 02:41:00 +02002044 To compile this driver as a module, choose M here: the module
2045 will be called sis190. This is recommended.
Francois Romieu890e8d02005-07-30 13:08:43 +02002046
Stephen Hemmingerbaef58b2005-05-12 20:14:36 -04002047config SKGE
Stephen Hemminger7a160c72006-02-13 15:48:08 -08002048 tristate "New SysKonnect GigaEthernet support"
2049 depends on PCI
Stephen Hemmingerbaef58b2005-05-12 20:14:36 -04002050 select CRC32
2051 ---help---
2052 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2053 and related Gigabit Ethernet adapters. It is a new smaller driver
Stephen Hemminger46a60f22005-09-09 12:54:56 -07002054 with better performance and more complete ethtool support.
Stephen Hemmingerbaef58b2005-05-12 20:14:36 -04002055
2056 It does not support the link failover and network management
2057 features that "portable" vendor supplied sk98lin driver does.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002058
Daniel Drakec6f0d752006-01-21 19:35:34 +00002059 This driver supports adapters based on the original Yukon chipset:
2060 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2061 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2062
2063 It does not support the newer Yukon2 chipset: a separate driver,
2064 sky2, is provided for Yukon2-based adapters.
2065
2066 To compile this driver as a module, choose M here: the module
2067 will be called skge. This is recommended.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002068
2069config SKY2
2070 tristate "SysKonnect Yukon2 support (EXPERIMENTAL)"
2071 depends on PCI && EXPERIMENTAL
2072 select CRC32
2073 ---help---
Daniel Drakec6f0d752006-01-21 19:35:34 +00002074 This driver supports Gigabit Ethernet adapters based on the the
2075 Marvell Yukon 2 chipset:
2076 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2077 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2078
2079 This driver does not support the original Yukon chipset: a seperate
2080 driver, skge, is provided for Yukon-based adapters.
Stephen Hemmingercd28ab62005-08-16 16:36:49 -07002081
2082 To compile this driver as a module, choose M here: the module
2083 will be called sky2. This is recommended.
2084
Linus Torvalds1da177e2005-04-16 15:20:36 -07002085config SK98LIN
2086 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
2087 depends on PCI
2088 ---help---
2089 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
Daniel Drakec6f0d752006-01-21 19:35:34 +00002090 compliant Gigabit Ethernet Adapter.
2091
2092 This driver supports the original Yukon chipset. A cleaner driver is
2093 also available (skge) which seems to work better than this one.
2094
2095 This driver does not support the newer Yukon2 chipset. A seperate
2096 driver, sky2, is provided to support Yukon2-based adapters.
2097
2098 The following adapters are supported by this driver:
Linus Torvalds1da177e2005-04-16 15:20:36 -07002099 - 3Com 3C940 Gigabit LOM Ethernet Adapter
2100 - 3Com 3C941 Gigabit LOM Ethernet Adapter
2101 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
2102 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
2103 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
2104 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
2105 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
2106 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
2107 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
2108 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
2109 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45
Linus Torvalds1da177e2005-04-16 15:20:36 -07002110 - EG1032 v2 Instant Gigabit Network Adapter
2111 - EG1064 v2 Instant Gigabit Network Adapter
2112 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
2113 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
2114 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
2115 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
2116 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
2117 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
2118 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
2119 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
2120 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)
2121 - Marvell RDK-8001 Adapter
2122 - Marvell RDK-8002 Adapter
2123 - Marvell RDK-8003 Adapter
2124 - Marvell RDK-8004 Adapter
2125 - Marvell RDK-8006 Adapter
2126 - Marvell RDK-8007 Adapter
2127 - Marvell RDK-8008 Adapter
2128 - Marvell RDK-8009 Adapter
2129 - Marvell RDK-8010 Adapter
2130 - Marvell RDK-8011 Adapter
2131 - Marvell RDK-8012 Adapter
2132 - Marvell RDK-8052 Adapter
2133 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
2134 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
2135 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
2136 - SK-9521 10/100/1000Base-T Adapter
2137 - SK-9521 V2.0 10/100/1000Base-T Adapter
2138 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
2139 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
2140 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
2141 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
2142 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
2143 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
2144 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
2145 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2146 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
2147 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2148 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
2149 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
2150 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
2151 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
2152 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
2153 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
2154 - SMC EZ Card 1000 (SMC9452TXV.2)
2155
2156 The adapters support Jumbo Frames.
2157 The dual link adapters support link-failover and dual port features.
2158 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
2159 the scatter-gather functionality with sendfile(). Please refer to
2160 <file:Documentation/networking/sk98lin.txt> for more information about
2161 optional driver parameters.
2162 Questions concerning this driver may be addressed to:
2163 <linux@syskonnect.de>
2164
2165 If you want to compile this driver as a module ( = code which can be
2166 inserted in and removed from the running kernel whenever you want),
2167 say M here and read <file:Documentation/kbuild/modules.txt>. The module will
2168 be called sk98lin. This is recommended.
2169
2170config VIA_VELOCITY
2171 tristate "VIA Velocity support"
2172 depends on NET_PCI && PCI
2173 select CRC32
2174 select CRC_CCITT
2175 select MII
2176 help
2177 If you have a VIA "Velocity" based network card say Y here.
2178
2179 To compile this driver as a module, choose M here. The module
2180 will be called via-velocity.
2181
2182config TIGON3
2183 tristate "Broadcom Tigon3 support"
2184 depends on PCI
2185 help
2186 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2187
2188 To compile this driver as a module, choose M here: the module
2189 will be called tg3. This is recommended.
2190
Michael Chanb6016b72005-05-26 13:03:09 -07002191config BNX2
2192 tristate "Broadcom NetXtremeII support"
2193 depends on PCI
Michael Chanfba9fe92006-06-12 22:21:25 -07002194 select CRC32
2195 select ZLIB_INFLATE
Michael Chanb6016b72005-05-26 13:03:09 -07002196 help
2197 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2198
2199 To compile this driver as a module, choose M here: the module
2200 will be called bnx2. This is recommended.
2201
Jens Osterkampaaec0fa2005-09-05 15:19:29 -07002202config SPIDER_NET
2203 tristate "Spider Gigabit Ethernet driver"
Geoff Levandc01ea722006-06-19 20:33:28 +02002204 depends on PCI && PPC_IBM_CELL_BLADE
Christoph Hellwig9b158792006-03-15 11:30:44 +01002205 select FW_LOADER
Jens Osterkampaaec0fa2005-09-05 15:19:29 -07002206 help
2207 This driver supports the Gigabit Ethernet chips present on the
2208 Cell Processor-Based Blades from IBM.
2209
Linus Torvalds1da177e2005-04-16 15:20:36 -07002210config GIANFAR
2211 tristate "Gianfar Ethernet"
Jon Loeligeref82a302006-06-17 17:52:55 -05002212 depends on 85xx || 83xx || PPC_86xx
Andy Flemingbb40dcb2005-09-23 22:54:21 -04002213 select PHYLIB
Linus Torvalds1da177e2005-04-16 15:20:36 -07002214 help
Jon Loeligeref82a302006-06-17 17:52:55 -05002215 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2216 and MPC86xx family of chips, and the FEC on the 8540.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002217
2218config GFAR_NAPI
2219 bool "NAPI Support"
2220 depends on GIANFAR
2221
2222config MV643XX_ETH
2223 tristate "MV-643XX Ethernet support"
Benjamin Herrenschmidt16b81752005-04-16 15:24:30 -07002224 depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
Dale Farnsworthcd6478c2006-03-03 10:01:08 -07002225 select MII
Linus Torvalds1da177e2005-04-16 15:20:36 -07002226 help
2227 This driver supports the gigabit Ethernet on the Marvell MV643XX
2228 chipset which is used in the Momenco Ocelot C and Jaguar ATX and
2229 Pegasos II, amongst other PPC and MIPS boards.
2230
2231config MV643XX_ETH_0
2232 bool "MV-643XX Port 0"
2233 depends on MV643XX_ETH
2234 help
2235 This enables support for Port 0 of the Marvell MV643XX Gigabit
2236 Ethernet.
2237
2238config MV643XX_ETH_1
2239 bool "MV-643XX Port 1"
2240 depends on MV643XX_ETH
2241 help
2242 This enables support for Port 1 of the Marvell MV643XX Gigabit
2243 Ethernet.
2244
2245config MV643XX_ETH_2
2246 bool "MV-643XX Port 2"
2247 depends on MV643XX_ETH
2248 help
2249 This enables support for Port 2 of the Marvell MV643XX Gigabit
2250 Ethernet.
2251
2252endmenu
2253
2254#
2255# 10 Gigabit Ethernet
2256#
2257
2258menu "Ethernet (10000 Mbit)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002259 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -07002260
Christoph Lameter8199d3a2005-03-30 13:34:31 -08002261config CHELSIO_T1
2262 tristate "Chelsio 10Gb Ethernet support"
2263 depends on PCI
2264 help
2265 This driver supports Chelsio N110 and N210 models 10Gb Ethernet
2266 cards. More information about adapter features and performance
2267 tuning is in <file:Documentation/networking/cxgb.txt>.
2268
2269 For general information about Chelsio and our products, visit
2270 our website at <http://www.chelsio.com>.
2271
2272 For customer support, please visit our customer support page at
2273 <http://www.chelsio.com/support.htm>.
2274
2275 Please send feedback to <linux-bugs@chelsio.com>.
2276
2277 To compile this driver as a module, choose M here: the module
2278 will be called cxgb.
2279
Linus Torvalds1da177e2005-04-16 15:20:36 -07002280config IXGB
2281 tristate "Intel(R) PRO/10GbE support"
2282 depends on PCI
2283 ---help---
2284 This driver supports Intel(R) PRO/10GbE family of
2285 adapters. For more information on how to identify your adapter, go
2286 to the Adapter & Driver ID Guide at:
2287
2288 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2289
2290 For general information and support, go to the Intel support
2291 website at:
2292
2293 <http://support.intel.com>
2294
2295 More specific information on configuring the driver is in
2296 <file:Documentation/networking/ixgb.txt>.
2297
2298 To compile this driver as a module, choose M here and read
2299 <file:Documentation/networking/net-modules.txt>. The module
2300 will be called ixgb.
2301
2302config IXGB_NAPI
2303 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2304 depends on IXGB && EXPERIMENTAL
2305 help
2306 NAPI is a new driver API designed to reduce CPU and interrupt load
2307 when the driver is receiving lots of packets from the card. It is
2308 still somewhat experimental and thus not yet enabled by default.
2309
2310 If your estimated Rx load is 10kpps or more, or if the card will be
2311 deployed on potentially unfriendly networks (e.g. in a firewall),
2312 then say Y here.
2313
2314 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2315 information.
2316
2317 If in doubt, say N.
2318
2319config S2IO
2320 tristate "S2IO 10Gbe XFrame NIC"
2321 depends on PCI
2322 ---help---
2323 This driver supports the 10Gbe XFrame NIC of S2IO.
Akinobu Mita9eb343a2005-10-21 19:06:42 +09002324 More specific information on configuring the driver is in
2325 <file:Documentation/networking/s2io.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002326
2327config S2IO_NAPI
2328 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
2329 depends on S2IO && EXPERIMENTAL
2330 help
2331 NAPI is a new driver API designed to reduce CPU and interrupt load
2332 when the driver is receiving lots of packets from the card. It is
2333 still somewhat experimental and thus not yet enabled by default.
2334
2335 If your estimated Rx load is 10kpps or more, or if the card will be
2336 deployed on potentially unfriendly networks (e.g. in a firewall),
2337 then say Y here.
2338
2339 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
2340 information.
2341
2342 If in doubt, say N.
2343
Brice Goglin0da34b62006-05-23 06:10:15 -04002344config MYRI10GE
2345 tristate "Myricom Myri-10G Ethernet support"
2346 depends on PCI
2347 select FW_LOADER
2348 select CRC32
2349 ---help---
2350 This driver supports Myricom Myri-10G Dual Protocol interface in
2351 Ethernet mode. If the eeprom on your board is not recent enough,
2352 you will need a newer firmware image.
2353 You may get this image or more information, at:
2354
2355 <http://www.myri.com/Myri-10G/>
2356
2357 To compile this driver as a module, choose M here and read
2358 <file:Documentation/networking/net-modules.txt>. The module
2359 will be called myri10ge.
2360
Linus Torvalds1da177e2005-04-16 15:20:36 -07002361endmenu
2362
Linus Torvalds1da177e2005-04-16 15:20:36 -07002363source "drivers/net/tokenring/Kconfig"
2364
2365source "drivers/net/wireless/Kconfig"
2366
2367source "drivers/net/pcmcia/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -07002368
2369source "drivers/net/wan/Kconfig"
2370
2371source "drivers/atm/Kconfig"
2372
2373source "drivers/s390/net/Kconfig"
2374
2375config ISERIES_VETH
2376 tristate "iSeries Virtual Ethernet driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002377 depends on PPC_ISERIES
Linus Torvalds1da177e2005-04-16 15:20:36 -07002378
Matt Porterf89efd52005-09-09 12:10:10 -07002379config RIONET
2380 tristate "RapidIO Ethernet over messaging driver support"
2381 depends on NETDEVICES && RAPIDIO
2382
2383config RIONET_TX_SIZE
2384 int "Number of outbound queue entries"
2385 depends on RIONET
2386 default "128"
2387
2388config RIONET_RX_SIZE
2389 int "Number of inbound queue entries"
2390 depends on RIONET
2391 default "128"
2392
Linus Torvalds1da177e2005-04-16 15:20:36 -07002393config FDDI
2394 bool "FDDI driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002395 depends on (PCI || EISA)
Linus Torvalds1da177e2005-04-16 15:20:36 -07002396 help
2397 Fiber Distributed Data Interface is a high speed local area network
2398 design; essentially a replacement for high speed Ethernet. FDDI can
2399 run over copper or fiber. If you are connected to such a network and
2400 want a driver for the FDDI card in your computer, say Y here (and
2401 then also Y to the driver for your FDDI card, below). Most people
2402 will say N.
2403
2404config DEFXX
2405 tristate "Digital DEFEA and DEFPA adapter support"
2406 depends on FDDI && (PCI || EISA)
2407 help
2408 This is support for the DIGITAL series of EISA (DEFEA) and PCI
2409 (DEFPA) controllers which can connect you to a local FDDI network.
2410
2411config SKFP
2412 tristate "SysKonnect FDDI PCI support"
2413 depends on FDDI && PCI
2414 ---help---
2415 Say Y here if you have a SysKonnect FDDI PCI adapter.
2416 The following adapters are supported by this driver:
2417 - SK-5521 (SK-NET FDDI-UP)
2418 - SK-5522 (SK-NET FDDI-UP DAS)
2419 - SK-5541 (SK-NET FDDI-FP)
2420 - SK-5543 (SK-NET FDDI-LP)
2421 - SK-5544 (SK-NET FDDI-LP DAS)
2422 - SK-5821 (SK-NET FDDI-UP64)
2423 - SK-5822 (SK-NET FDDI-UP64 DAS)
2424 - SK-5841 (SK-NET FDDI-FP64)
2425 - SK-5843 (SK-NET FDDI-LP64)
2426 - SK-5844 (SK-NET FDDI-LP64 DAS)
2427 - Netelligent 100 FDDI DAS Fibre SC
2428 - Netelligent 100 FDDI SAS Fibre SC
2429 - Netelligent 100 FDDI DAS UTP
2430 - Netelligent 100 FDDI SAS UTP
2431 - Netelligent 100 FDDI SAS Fibre MIC
2432
2433 Read <file:Documentation/networking/skfp.txt> for information about
2434 the driver.
2435
2436 Questions concerning this driver can be addressed to:
2437 <linux@syskonnect.de>
2438
2439 To compile this driver as a module, choose M here: the module
2440 will be called skfp. This is recommended.
2441
2442config HIPPI
2443 bool "HIPPI driver support (EXPERIMENTAL)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002444 depends on EXPERIMENTAL && INET && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07002445 help
2446 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2447 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2448 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2449 single-mode). HIPPI networks are commonly used for clusters and to
2450 connect to super computers. If you are connected to a HIPPI network
2451 and have a HIPPI network card in your computer that you want to use
2452 under Linux, say Y here (you must also remember to enable the driver
2453 for your HIPPI card below). Most people will say N here.
2454
2455config ROADRUNNER
2456 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2457 depends on HIPPI && PCI
2458 help
2459 Say Y here if this is your PCI HIPPI network card.
2460
2461 To compile this driver as a module, choose M here: the module
2462 will be called rrunner. If unsure, say N.
2463
2464config ROADRUNNER_LARGE_RINGS
2465 bool "Use large TX/RX rings (EXPERIMENTAL)"
2466 depends on ROADRUNNER
2467 help
2468 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2469 of additional memory to allow for fastest operation, both for
2470 transmitting and receiving. This memory cannot be used by any other
2471 kernel code or by user space programs. Say Y here only if you have
2472 the memory.
2473
2474config PLIP
2475 tristate "PLIP (parallel port) support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002476 depends on PARPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -07002477 ---help---
2478 PLIP (Parallel Line Internet Protocol) is used to create a
2479 reasonably fast mini network consisting of two (or, rarely, more)
2480 local machines. A PLIP link from a Linux box is a popular means to
2481 install a Linux distribution on a machine which doesn't have a
2482 CD-ROM drive (a minimal system has to be transferred with floppies
2483 first). The kernels on both machines need to have this PLIP option
2484 enabled for this to work.
2485
2486 The PLIP driver has two modes, mode 0 and mode 1. The parallel
2487 ports (the connectors at the computers with 25 holes) are connected
2488 with "null printer" or "Turbo Laplink" cables which can transmit 4
2489 bits at a time (mode 0) or with special PLIP cables, to be used on
2490 bidirectional parallel ports only, which can transmit 8 bits at a
2491 time (mode 1); you can find the wiring of these cables in
2492 <file:Documentation/networking/PLIP.txt>. The cables can be up to
2493 15m long. Mode 0 works also if one of the machines runs DOS/Windows
2494 and has some PLIP software installed, e.g. the Crynwr PLIP packet
2495 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2496 and winsock or NCSA's telnet.
2497
2498 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2499 as the NET-3-HOWTO, both available from
2500 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
2501 protocol has been changed and this PLIP driver won't work together
2502 with the PLIP support in Linux versions 1.0.x. This option enlarges
2503 your kernel by about 8 KB.
2504
2505 To compile this driver as a module, choose M here and read
2506 <file:Documentation/networking/net-modules.txt>. The module will be
2507 called plip. If unsure, say Y or M, in case you buy a laptop
2508 later.
2509
2510config PPP
2511 tristate "PPP (point-to-point protocol) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07002512 ---help---
2513 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
2514 the same purpose: sending Internet traffic over telephone (and other
2515 serial) lines. Ask your access provider if they support it, because
2516 otherwise you can't use it; most Internet access providers these
2517 days support PPP rather than SLIP.
2518
2519 To use PPP, you need an additional program called pppd as described
2520 in the PPP-HOWTO, available at
2521 <http://www.tldp.org/docs.html#howto>. Make sure that you have
2522 the version of pppd recommended in <file:Documentation/Changes>.
2523 The PPP option enlarges your kernel by about 16 KB.
2524
2525 There are actually two versions of PPP: the traditional PPP for
2526 asynchronous lines, such as regular analog phone lines, and
2527 synchronous PPP which can be used over digital ISDN lines for
2528 example. If you want to use PPP over phone lines or other
2529 asynchronous serial lines, you need to say Y (or M) here and also to
2530 the next option, "PPP support for async serial ports". For PPP over
2531 synchronous lines, you should say Y (or M) here and to "Support
2532 synchronous PPP", below.
2533
2534 If you said Y to "Version information on all symbols" above, then
2535 you cannot compile the PPP driver into the kernel; you can then only
2536 compile it as a module. To compile this driver as a module, choose M
2537 here and read <file:Documentation/networking/net-modules.txt>.
2538 The module will be called ppp_generic.
2539
2540config PPP_MULTILINK
2541 bool "PPP multilink support (EXPERIMENTAL)"
2542 depends on PPP && EXPERIMENTAL
2543 help
2544 PPP multilink is a protocol (defined in RFC 1990) which allows you
2545 to combine several (logical or physical) lines into one logical PPP
2546 connection, so that you can utilize your full bandwidth.
2547
2548 This has to be supported at the other end as well and you need a
2549 version of the pppd daemon which understands the multilink protocol.
2550
2551 If unsure, say N.
2552
2553config PPP_FILTER
2554 bool "PPP filtering"
2555 depends on PPP
2556 help
2557 Say Y here if you want to be able to filter the packets passing over
2558 PPP interfaces. This allows you to control which packets count as
2559 activity (i.e. which packets will reset the idle timer or bring up
Jon Mason47c51432006-02-12 11:53:04 -06002560 a demand-dialed link) and which packets are to be dropped entirely.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002561 You need to say Y here if you wish to use the pass-filter and
2562 active-filter options to pppd.
2563
2564 If unsure, say N.
2565
2566config PPP_ASYNC
2567 tristate "PPP support for async serial ports"
2568 depends on PPP
2569 select CRC_CCITT
2570 ---help---
2571 Say Y (or M) here if you want to be able to use PPP over standard
2572 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
2573 a modem (not a synchronous or ISDN modem) to contact your ISP, you
2574 need this option.
2575
2576 To compile this driver as a module, choose M here.
2577
2578 If unsure, say Y.
2579
2580config PPP_SYNC_TTY
2581 tristate "PPP support for sync tty ports"
2582 depends on PPP
2583 help
2584 Say Y (or M) here if you want to be able to use PPP over synchronous
2585 (HDLC) tty devices, such as the SyncLink adapter. These devices
2586 are often used for high-speed leased lines like T1/E1.
2587
2588 To compile this driver as a module, choose M here.
2589
2590config PPP_DEFLATE
2591 tristate "PPP Deflate compression"
2592 depends on PPP
2593 select ZLIB_INFLATE
2594 select ZLIB_DEFLATE
2595 ---help---
2596 Support for the Deflate compression method for PPP, which uses the
2597 Deflate algorithm (the same algorithm that gzip uses) to compress
2598 each PPP packet before it is sent over the wire. The machine at the
2599 other end of the PPP link (usually your ISP) has to support the
2600 Deflate compression method as well for this to be useful. Even if
2601 they don't support it, it is safe to say Y here.
2602
2603 To compile this driver as a module, choose M here.
2604
2605config PPP_BSDCOMP
2606 tristate "PPP BSD-Compress compression"
2607 depends on PPP
2608 ---help---
2609 Support for the BSD-Compress compression method for PPP, which uses
2610 the LZW compression method to compress each PPP packet before it is
2611 sent over the wire. The machine at the other end of the PPP link
2612 (usually your ISP) has to support the BSD-Compress compression
2613 method as well for this to be useful. Even if they don't support it,
2614 it is safe to say Y here.
2615
2616 The PPP Deflate compression method ("PPP Deflate compression",
2617 above) is preferable to BSD-Compress, because it compresses better
2618 and is patent-free.
2619
2620 Note that the BSD compression code will always be compiled as a
2621 module; it is called bsd_comp and will show up in the directory
2622 modules once you have said "make modules". If unsure, say N.
2623
Matt Domschb3f9b922005-11-08 09:40:47 -08002624config PPP_MPPE
2625 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2626 depends on PPP && EXPERIMENTAL
2627 select CRYPTO
2628 select CRYPTO_SHA1
2629 select CRYPTO_ARC4
2630 ---help---
2631 Support for the MPPE Encryption protocol, as employed by the
2632 Microsoft Point-to-Point Tunneling Protocol.
2633
2634 See http://pptpclient.sourceforge.net/ for information on
2635 configuring PPTP clients and servers to utilize this method.
2636
Linus Torvalds1da177e2005-04-16 15:20:36 -07002637config PPPOE
2638 tristate "PPP over Ethernet (EXPERIMENTAL)"
2639 depends on EXPERIMENTAL && PPP
2640 help
2641 Support for PPP over Ethernet.
2642
2643 This driver requires the latest version of pppd from the CVS
2644 repository at cvs.samba.org. Alternatively, see the
2645 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
2646 which contains instruction on how to use this driver (under
2647 the heading "Kernel mode PPPoE").
2648
2649config PPPOATM
2650 tristate "PPP over ATM"
2651 depends on ATM && PPP
2652 help
2653 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
2654 This implementation does not yet comply with section 8 of RFC2364,
2655 which can lead to bad results if the ATM peer loses state and
2656 changes its encapsulation unilaterally.
2657
2658config SLIP
2659 tristate "SLIP (serial line) support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07002660 ---help---
2661 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
2662 connect to your Internet service provider or to connect to some
2663 other local Unix box or if you want to configure your Linux box as a
2664 Slip/CSlip server for other people to dial in. SLIP (Serial Line
2665 Internet Protocol) is a protocol used to send Internet traffic over
2666 serial connections such as telephone lines or null modem cables;
2667 nowadays, the protocol PPP is more commonly used for this same
2668 purpose.
2669
2670 Normally, your access provider has to support SLIP in order for you
2671 to be able to use it, but there is now a SLIP emulator called SLiRP
2672 around (available from
2673 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2674 allows you to use SLIP over a regular dial up shell connection. If
2675 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
2676 NET-3-HOWTO, available from
2677 <http://www.tldp.org/docs.html#howto>, explains how to
2678 configure SLIP. Note that you don't need this option if you just
2679 want to run term (term is a program which gives you almost full
2680 Internet connectivity if you have a regular dial up shell account on
2681 some Internet connected Unix computer. Read
2682 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
2683 support will enlarge your kernel by about 4 KB. If unsure, say N.
2684
2685 To compile this driver as a module, choose M here and read
2686 <file:Documentation/networking/net-modules.txt>. The module will be
2687 called slip.
2688
2689config SLIP_COMPRESSED
2690 bool "CSLIP compressed headers"
2691 depends on SLIP
2692 ---help---
2693 This protocol is faster than SLIP because it uses compression on the
2694 TCP/IP headers (not on the data itself), but it has to be supported
2695 on both ends. Ask your access provider if you are not sure and
2696 answer Y, just in case. You will still be able to use plain SLIP. If
2697 you plan to use SLiRP, the SLIP emulator (available from
2698 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
2699 allows you to use SLIP over a regular dial up shell connection, you
2700 definitely want to say Y here. The NET-3-HOWTO, available from
2701 <http://www.tldp.org/docs.html#howto>, explains how to configure
2702 CSLIP. This won't enlarge your kernel.
2703
2704config SLIP_SMART
2705 bool "Keepalive and linefill"
2706 depends on SLIP
2707 help
2708 Adds additional capabilities to the SLIP driver to support the
2709 RELCOM line fill and keepalive monitoring. Ideal on poor quality
2710 analogue lines.
2711
2712config SLIP_MODE_SLIP6
2713 bool "Six bit SLIP encapsulation"
2714 depends on SLIP
2715 help
2716 Just occasionally you may need to run IP over hostile serial
2717 networks that don't pass all control characters or are only seven
2718 bit. Saying Y here adds an extra mode you can use with SLIP:
2719 "slip6". In this mode, SLIP will only send normal ASCII symbols over
2720 the serial device. Naturally, this has to be supported at the other
2721 end of the link as well. It's good enough, for example, to run IP
2722 over the async ports of a Camtec JNT Pad. If unsure, say N.
2723
2724config NET_FC
2725 bool "Fibre Channel driver support"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002726 depends on SCSI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07002727 help
2728 Fibre Channel is a high speed serial protocol mainly used to connect
2729 large storage devices to the computer; it is compatible with and
2730 intended to replace SCSI.
2731
2732 If you intend to use Fibre Channel, you need to have a Fibre channel
2733 adaptor card in your computer; say Y here and to the driver for your
2734 adaptor below. You also should have said Y to "SCSI support" and
2735 "SCSI generic support".
2736
2737config SHAPER
2738 tristate "Traffic Shaper (EXPERIMENTAL)"
Randy Dunlapcbcd2a42005-07-27 13:04:35 -07002739 depends on EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07002740 ---help---
2741 The traffic shaper is a virtual network device that allows you to
2742 limit the rate of outgoing data flow over some other network device.
2743 The traffic that you want to slow down can then be routed through
2744 these virtual devices. See
2745 <file:Documentation/networking/shaper.txt> for more information.
2746
2747 An alternative to this traffic shaper is the experimental
Jon Mason47c51432006-02-12 11:53:04 -06002748 Class-Based Queuing (CBQ) scheduling support which you get if you
2749 say Y to "QoS and/or fair queuing" above.
Linus Torvalds1da177e2005-04-16 15:20:36 -07002750
Linus Torvalds1da177e2005-04-16 15:20:36 -07002751 To compile this driver as a module, choose M here: the module
2752 will be called shaper. If unsure, say N.
2753
2754config NETCONSOLE
2755 tristate "Network console logging support (EXPERIMENTAL)"
Matt Mackall5e43db72005-07-27 15:24:42 -07002756 depends on EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07002757 ---help---
2758 If you want to log kernel messages over the network, enable this.
2759 See <file:Documentation/networking/netconsole.txt> for details.
2760
Randy Dunlap54208992005-07-18 13:45:12 -07002761config NETPOLL
2762 def_bool NETCONSOLE
2763
2764config NETPOLL_RX
2765 bool "Netpoll support for trapping incoming packets"
2766 default n
2767 depends on NETPOLL
2768
2769config NETPOLL_TRAP
2770 bool "Netpoll traffic trapping"
2771 default n
2772 depends on NETPOLL
2773
2774config NET_POLL_CONTROLLER
2775 def_bool NETPOLL
2776
Sam Ravnborgd5950b42005-07-11 21:03:49 -07002777endmenu