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