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