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