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