Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Network device configuration | |
3 | # | |
4 | ||
ee621dd6 JCPV |
5 | config HAVE_NET_MACB |
6 | bool | |
7 | ||
d1c0a65f | 8 | menuconfig NETDEVICES |
ce2d2aed | 9 | default y if UML |
e0009820 | 10 | depends on NET |
1da177e4 LT |
11 | bool "Network device support" |
12 | ---help--- | |
13 | You can say N here if you don't intend to connect your Linux box to | |
14 | any other computer at all. | |
15 | ||
16 | You'll have to say Y if your computer contains a network card that | |
17 | you want to use under Linux. If you are going to run SLIP or PPP over | |
18 | telephone line or null modem cable you need say Y here. Connecting | |
19 | two machines with parallel ports using PLIP needs this, as well as | |
20 | AX.25/KISS for sending Internet traffic over amateur radio links. | |
21 | ||
22 | See also "The Linux Network Administrator's Guide" by Olaf Kirch and | |
23 | Terry Dawson. Available at <http://www.tldp.org/guides.html>. | |
24 | ||
25 | If unsure, say Y. | |
26 | ||
1618cb0c RD |
27 | # All the following symbols are dependent on NETDEVICES - do not repeat |
28 | # that for each of the symbols. | |
29 | if NETDEVICES | |
cbcd2a4c | 30 | |
253af423 JHS |
31 | config IFB |
32 | tristate "Intermediate Functional Block support" | |
33 | depends on NET_CLS_ACT | |
34 | ---help--- | |
3cb2fccc | 35 | This is an intermediate driver that allows sharing of |
253af423 JHS |
36 | resources. |
37 | To compile this driver as a module, choose M here: the module | |
38 | will be called ifb. If you want to use more than one ifb | |
39 | device at a time, you need to compile this driver as a module. | |
40 | Instead of 'ifb', the devices will then be called 'ifb0', | |
41 | 'ifb1' etc. | |
42 | Look at the iproute2 documentation directory for usage etc | |
43 | ||
1da177e4 LT |
44 | config DUMMY |
45 | tristate "Dummy net driver support" | |
1da177e4 LT |
46 | ---help--- |
47 | This is essentially a bit-bucket device (i.e. traffic you send to | |
48 | this device is consigned into oblivion) with a configurable IP | |
49 | address. It is most commonly used in order to make your currently | |
50 | inactive SLIP address seem like a real address for local programs. | |
51 | If you use SLIP or PPP, you might want to say Y here. Since this | |
52 | thing often comes in handy, the default is Y. It won't enlarge your | |
53 | kernel either. What a deal. Read about it in the Network | |
54 | Administrator's Guide, available from | |
55 | <http://www.tldp.org/docs.html#guide>. | |
56 | ||
57 | To compile this driver as a module, choose M here: the module | |
58 | will be called dummy. If you want to use more than one dummy | |
59 | device at a time, you need to compile this driver as a module. | |
60 | Instead of 'dummy', the devices will then be called 'dummy0', | |
61 | 'dummy1' etc. | |
62 | ||
63 | config BONDING | |
64 | tristate "Bonding driver support" | |
1da177e4 | 65 | depends on INET |
305d552a | 66 | depends on IPV6 || IPV6=n |
1da177e4 LT |
67 | ---help--- |
68 | Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet | |
69 | Channels together. This is called 'Etherchannel' by Cisco, | |
70 | 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. | |
71 | ||
72 | The driver supports multiple bonding modes to allow for both high | |
47c51431 | 73 | performance and high availability operation. |
1da177e4 LT |
74 | |
75 | Refer to <file:Documentation/networking/bonding.txt> for more | |
76 | information. | |
77 | ||
78 | To compile this driver as a module, choose M here: the module | |
79 | will be called bonding. | |
80 | ||
b863ceb7 PM |
81 | config MACVLAN |
82 | tristate "MAC-VLAN support (EXPERIMENTAL)" | |
83 | depends on EXPERIMENTAL | |
84 | ---help--- | |
85 | This allows one to create virtual interfaces that map packets to | |
86 | or from specific MAC addresses to a particular interface. | |
87 | ||
3dbf8d56 PM |
88 | Macvlan devices can be added using the "ip" command from the |
89 | iproute2 package starting with the iproute2-2.6.23 release: | |
90 | ||
91 | "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" | |
92 | ||
b863ceb7 PM |
93 | To compile this driver as a module, choose M here: the module |
94 | will be called macvlan. | |
95 | ||
20d29d7a AB |
96 | config MACVTAP |
97 | tristate "MAC-VLAN based tap driver (EXPERIMENTAL)" | |
98 | depends on MACVLAN | |
99 | help | |
100 | This adds a specialized tap character device driver that is based | |
101 | on the MAC-VLAN network interface, called macvtap. A macvtap device | |
102 | can be added in the same way as a macvlan device, using 'type | |
103 | macvlan', and then be accessed through the tap user space interface. | |
104 | ||
105 | To compile this driver as a module, choose M here: the module | |
106 | will be called macvtap. | |
107 | ||
1da177e4 LT |
108 | config EQUALIZER |
109 | tristate "EQL (serial line load balancing) support" | |
1da177e4 LT |
110 | ---help--- |
111 | If you have two serial connections to some other computer (this | |
112 | usually requires two modems and two telephone lines) and you use | |
113 | SLIP (the protocol for sending Internet traffic over telephone | |
114 | lines) or PPP (a better SLIP) on them, you can make them behave like | |
115 | one double speed connection using this driver. Naturally, this has | |
116 | to be supported at the other end as well, either with a similar EQL | |
117 | Linux driver or with a Livingston Portmaster 2e. | |
118 | ||
119 | Say Y if you want this and read | |
120 | <file:Documentation/networking/eql.txt>. You may also want to read | |
121 | section 6.2 of the NET-3-HOWTO, available from | |
122 | <http://www.tldp.org/docs.html#howto>. | |
123 | ||
124 | To compile this driver as a module, choose M here: the module | |
125 | will be called eql. If unsure, say N. | |
126 | ||
127 | config TUN | |
128 | tristate "Universal TUN/TAP device driver support" | |
1da177e4 LT |
129 | select CRC32 |
130 | ---help--- | |
131 | TUN/TAP provides packet reception and transmission for user space | |
132 | programs. It can be viewed as a simple Point-to-Point or Ethernet | |
133 | device, which instead of receiving packets from a physical media, | |
134 | receives them from user space program and instead of sending packets | |
135 | via physical media writes them to the user space program. | |
136 | ||
137 | When a program opens /dev/net/tun, driver creates and registers | |
138 | corresponding net device tunX or tapX. After a program closed above | |
139 | devices, driver will automatically delete tunXX or tapXX device and | |
140 | all routes corresponding to it. | |
141 | ||
142 | Please read <file:Documentation/networking/tuntap.txt> for more | |
143 | information. | |
144 | ||
145 | To compile this driver as a module, choose M here: the module | |
146 | will be called tun. | |
147 | ||
148 | If you don't know what to use this for, you don't need it. | |
149 | ||
e314dbdc | 150 | config VETH |
6a9a0250 | 151 | tristate "Virtual ethernet pair device" |
e314dbdc | 152 | ---help--- |
6a9a0250 RR |
153 | This device is a local ethernet tunnel. Devices are created in pairs. |
154 | When one end receives the packet it appears on its pair and vice | |
155 | versa. | |
e314dbdc | 156 | |
1da177e4 LT |
157 | config NET_SB1000 |
158 | tristate "General Instruments Surfboard 1000" | |
cbcd2a4c | 159 | depends on PNP |
1da177e4 LT |
160 | ---help--- |
161 | This is a driver for the General Instrument (also known as | |
162 | NextLevel) SURFboard 1000 internal | |
163 | cable modem. This is an ISA card which is used by a number of cable | |
164 | TV companies to provide cable modem access. It's a one-way | |
165 | downstream-only cable modem, meaning that your upstream net link is | |
166 | provided by your regular phone modem. | |
167 | ||
168 | At present this driver only compiles as a module, so say M here if | |
169 | you have this card. The module will be called sb1000. Then read | |
170 | <file:Documentation/networking/README.sb1000> for information on how | |
171 | to use this module, as it needs special ppp scripts for establishing | |
172 | a connection. Further documentation and the necessary scripts can be | |
173 | found at: | |
174 | ||
175 | <http://www.jacksonville.net/~fventuri/> | |
176 | <http://home.adelphia.net/~siglercm/sb1000.html> | |
177 | <http://linuxpower.cx/~cable/> | |
178 | ||
179 | If you don't have this card, of course say N. | |
180 | ||
f65fd8fb | 181 | source "drivers/net/arcnet/Kconfig" |
1da177e4 | 182 | |
81ccb499 RD |
183 | config MII |
184 | tristate "Generic Media Independent Interface device support" | |
185 | help | |
186 | Most ethernet controllers have MII transceiver either as an external | |
187 | or internal device. It is safe to say Y or M here even if your | |
188 | ethernet card lacks MII. | |
189 | ||
00db8189 AF |
190 | source "drivers/net/phy/Kconfig" |
191 | ||
1da177e4 LT |
192 | # |
193 | # Ethernet | |
194 | # | |
195 | ||
c1abc95b JK |
196 | source "drivers/net/ethernet/Kconfig" |
197 | ||
d1c0a65f | 198 | menuconfig NET_ETHERNET |
1da177e4 | 199 | bool "Ethernet (10 or 100Mbit)" |
d1c0a65f | 200 | depends on !UML |
1da177e4 LT |
201 | ---help--- |
202 | Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common | |
203 | type of Local Area Network (LAN) in universities and companies. | |
204 | ||
205 | Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over | |
206 | coaxial cable, linking computers in a chain), 10BASE-T or twisted | |
207 | pair (10 Mbps over twisted pair cable, linking computers to central | |
208 | hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), | |
209 | 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), | |
210 | 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair | |
211 | cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) | |
212 | [the 100BASE varieties are also known as Fast Ethernet], and Gigabit | |
213 | Ethernet (1 Gbps over optical fiber or short copper links). | |
214 | ||
215 | If your Linux machine will be connected to an Ethernet and you have | |
216 | an Ethernet network interface card (NIC) installed in your computer, | |
217 | say Y here and read the Ethernet-HOWTO, available from | |
218 | <http://www.tldp.org/docs.html#howto>. You will then also have | |
219 | to say Y to the driver for your particular NIC. | |
220 | ||
221 | Note that the answer to this question won't directly affect the | |
222 | kernel: saying N will just cause the configurator to skip all | |
223 | the questions about Ethernet network cards. If unsure, say N. | |
224 | ||
d1c0a65f JE |
225 | if NET_ETHERNET |
226 | ||
89e5785f HS |
227 | config MACB |
228 | tristate "Atmel MACB support" | |
ee621dd6 | 229 | depends on HAVE_NET_MACB |
6c36a707 | 230 | select PHYLIB |
89e5785f HS |
231 | help |
232 | The Atmel MACB ethernet interface is found on many AT32 and AT91 | |
233 | parts. Say Y to include support for the MACB chip. | |
234 | ||
235 | To compile this driver as a module, choose M here: the module | |
236 | will be called macb. | |
237 | ||
1da177e4 LT |
238 | source "drivers/net/arm/Kconfig" |
239 | ||
240 | config MACE | |
241 | tristate "MACE (Power Mac ethernet) support" | |
d1c0a65f | 242 | depends on PPC_PMAC && PPC32 |
1da177e4 LT |
243 | select CRC32 |
244 | help | |
245 | Power Macintoshes and clones with Ethernet built-in on the | |
246 | motherboard will usually use a MACE (Medium Access Control for | |
247 | Ethernet) interface. Say Y to include support for the MACE chip. | |
248 | ||
249 | To compile this driver as a module, choose M here: the module | |
250 | will be called mace. | |
251 | ||
252 | config MACE_AAUI_PORT | |
253 | bool "Use AAUI port instead of TP by default" | |
254 | depends on MACE | |
255 | help | |
256 | Some Apple machines (notably the Apple Network Server) which use the | |
257 | MACE ethernet chip have an Apple AUI port (small 15-pin connector), | |
258 | instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say | |
259 | Y here if you have such a machine. If unsure, say N. | |
260 | The driver will default to AAUI on ANS anyway, and if you use it as | |
261 | a module, you can provide the port_aaui=0|1 to force the driver. | |
262 | ||
263 | config BMAC | |
264 | tristate "BMAC (G3 ethernet) support" | |
d1c0a65f | 265 | depends on PPC_PMAC && PPC32 |
1da177e4 LT |
266 | select CRC32 |
267 | help | |
268 | Say Y for support of BMAC Ethernet interfaces. These are used on G3 | |
269 | computers. | |
270 | ||
271 | To compile this driver as a module, choose M here: the module | |
272 | will be called bmac. | |
273 | ||
1da177e4 LT |
274 | config MAC89x0 |
275 | tristate "Macintosh CS89x0 based ethernet cards" | |
d1c0a65f | 276 | depends on MAC |
1da177e4 LT |
277 | ---help--- |
278 | Support for CS89x0 chipset based Ethernet cards. If you have a | |
279 | Nubus or LC-PDS network (Ethernet) card of this type, say Y and | |
280 | read the Ethernet-HOWTO, available from | |
281 | <http://www.tldp.org/docs.html#howto>. | |
282 | ||
57ce45dd | 283 | To compile this driver as a module, choose M here. This module will |
1da177e4 LT |
284 | be called mac89x0. |
285 | ||
286 | config MACSONIC | |
287 | tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" | |
d1c0a65f | 288 | depends on MAC |
1da177e4 LT |
289 | ---help--- |
290 | Support for NatSemi SONIC based Ethernet devices. This includes | |
291 | the onboard Ethernet in many Quadras as well as some LC-PDS, | |
292 | a few Nubus and all known Comm Slot Ethernet cards. If you have | |
293 | one of these say Y and read the Ethernet-HOWTO, available from | |
294 | <http://www.tldp.org/docs.html#howto>. | |
295 | ||
57ce45dd | 296 | To compile this driver as a module, choose M here. This module will |
1da177e4 LT |
297 | be called macsonic. |
298 | ||
299 | config MACMACE | |
8b6aaab8 | 300 | bool "Macintosh (AV) onboard MACE ethernet" |
d1c0a65f | 301 | depends on MAC |
1da177e4 LT |
302 | select CRC32 |
303 | help | |
304 | Support for the onboard AMD 79C940 MACE Ethernet controller used in | |
305 | the 660AV and 840AV Macintosh. If you have one of these Macintoshes | |
306 | say Y and read the Ethernet-HOWTO, available from | |
307 | <http://www.tldp.org/docs.html#howto>. | |
308 | ||
ef11291b FF |
309 | config KORINA |
310 | tristate "Korina (IDT RC32434) Ethernet support" | |
f57b2061 | 311 | depends on NET_ETHERNET && MIKROTIK_RB532 |
ef11291b FF |
312 | help |
313 | If you have a Mikrotik RouterBoard 500 or IDT RC32434 | |
314 | based system say Y. Otherwise say N. | |
315 | ||
1da177e4 LT |
316 | config MIPS_JAZZ_SONIC |
317 | tristate "MIPS JAZZ onboard SONIC Ethernet support" | |
d1c0a65f | 318 | depends on MACH_JAZZ |
1da177e4 LT |
319 | help |
320 | This is the driver for the onboard card of MIPS Magnum 4000, | |
321 | Acer PICA, Olivetti M700-10 and a few other identical OEM systems. | |
322 | ||
74f2a5f0 CZ |
323 | config XTENSA_XT2000_SONIC |
324 | tristate "Xtensa XT2000 onboard SONIC Ethernet support" | |
325 | depends on XTENSA_PLATFORM_XT2000 | |
326 | help | |
327 | This is the driver for the onboard card of the Xtensa XT2000 board. | |
328 | ||
1da177e4 LT |
329 | config SGI_IOC3_ETH |
330 | bool "SGI IOC3 Ethernet" | |
d1c0a65f | 331 | depends on PCI && SGI_IP27 |
1da177e4 LT |
332 | select CRC32 |
333 | select MII | |
334 | help | |
335 | If you have a network (Ethernet) card of this type, say Y and read | |
336 | the Ethernet-HOWTO, available from | |
337 | <http://www.tldp.org/docs.html#howto>. | |
338 | ||
dcbf8477 | 339 | config MIPS_SIM_NET |
1e2b980f | 340 | tristate "MIPS simulator Network device" |
d1c0a65f | 341 | depends on MIPS_SIM |
dcbf8477 RB |
342 | help |
343 | The MIPSNET device is a simple Ethernet network device which is | |
344 | emulated by the MIPS Simulator. | |
345 | If you are not using a MIPSsim or are unsure, say N. | |
346 | ||
1da177e4 LT |
347 | config SGI_O2MACE_ETH |
348 | tristate "SGI O2 MACE Fast Ethernet support" | |
d1c0a65f | 349 | depends on SGI_IP32=y |
1da177e4 | 350 | |
86a74ff2 NI |
351 | config SH_ETH |
352 | tristate "Renesas SuperH Ethernet support" | |
353 | depends on SUPERH && \ | |
65ac8851 YS |
354 | (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ |
355 | CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ | |
f29a3d04 | 356 | CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757) |
86a74ff2 NI |
357 | select CRC32 |
358 | select MII | |
359 | select MDIO_BITBANG | |
360 | select PHYLIB | |
361 | help | |
362 | Renesas SuperH Ethernet device driver. | |
f29a3d04 YS |
363 | This driver supporting CPUs are: |
364 | - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757. | |
86a74ff2 | 365 | |
e190d6b1 | 366 | config BFIN_MAC |
736783b8 | 367 | tristate "Blackfin on-chip MAC support" |
33a2a2b4 | 368 | depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) |
e190d6b1 | 369 | select CRC32 |
eeb70af9 BW |
370 | select MII |
371 | select PHYLIB | |
e190d6b1 BW |
372 | select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE |
373 | help | |
736783b8 | 374 | This is the driver for Blackfin on-chip mac device. Say Y if you want it |
e190d6b1 BW |
375 | compiled into the kernel. This driver is also available as a module |
376 | ( = code which can be inserted in and removed from the running kernel | |
377 | whenever you want). The module will be called bfin_mac. | |
378 | ||
379 | config BFIN_MAC_USE_L1 | |
380 | bool "Use L1 memory for rx/tx packets" | |
6893ff1c | 381 | depends on BFIN_MAC && (BF527 || BF537) |
e190d6b1 BW |
382 | default y |
383 | help | |
01dd2fbf | 384 | To get maximum network performance, you should use L1 memory as rx/tx buffers. |
e190d6b1 BW |
385 | Say N here if you want to reserve L1 memory for other uses. |
386 | ||
387 | config BFIN_TX_DESC_NUM | |
388 | int "Number of transmit buffer packets" | |
389 | depends on BFIN_MAC | |
390 | range 6 10 if BFIN_MAC_USE_L1 | |
391 | range 10 100 | |
392 | default "10" | |
393 | help | |
394 | Set the number of buffer packets used in driver. | |
395 | ||
396 | config BFIN_RX_DESC_NUM | |
397 | int "Number of receive buffer packets" | |
398 | depends on BFIN_MAC | |
399 | range 20 100 if BFIN_MAC_USE_L1 | |
400 | range 20 800 | |
401 | default "20" | |
402 | help | |
403 | Set the number of buffer packets used in driver. | |
404 | ||
fe92afed BS |
405 | config BFIN_MAC_USE_HWSTAMP |
406 | bool "Use IEEE 1588 hwstamp" | |
407 | depends on BFIN_MAC && BF518 | |
408 | default y | |
409 | help | |
410 | To support the IEEE 1588 Precision Time Protocol (PTP), select y here | |
411 | ||
a49f37ee SS |
412 | config PXA168_ETH |
413 | tristate "Marvell pxa168 ethernet support" | |
414 | depends on CPU_PXA168 | |
415 | select PHYLIB | |
416 | help | |
417 | This driver supports the pxa168 Ethernet ports. | |
418 | ||
419 | To compile this driver as a module, choose M here. The module | |
420 | will be called pxa168_eth. | |
421 | ||
92aa674d SH |
422 | config NET_NETX |
423 | tristate "NetX Ethernet support" | |
424 | select MII | |
d1c0a65f | 425 | depends on ARCH_NETX |
92aa674d SH |
426 | help |
427 | This is support for the Hilscher netX builtin Ethernet ports | |
428 | ||
57ce45dd | 429 | To compile this driver as a module, choose M here. The module |
92aa674d SH |
430 | will be called netx-eth. |
431 | ||
a6286ee6 AG |
432 | config TI_DAVINCI_EMAC |
433 | tristate "TI DaVinci EMAC Support" | |
8ee2bf9a | 434 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) |
5d69e007 | 435 | select TI_DAVINCI_MDIO |
ef8c2dab | 436 | select TI_DAVINCI_CPDMA |
a6286ee6 AG |
437 | select PHYLIB |
438 | help | |
439 | This driver supports TI's DaVinci Ethernet . | |
440 | ||
441 | To compile this driver as a module, choose M here: the module | |
442 | will be called davinci_emac_driver. This is recommended. | |
443 | ||
f20136eb CC |
444 | config TI_DAVINCI_MDIO |
445 | tristate "TI DaVinci MDIO Support" | |
446 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) | |
447 | select PHYLIB | |
448 | help | |
449 | This driver supports TI's DaVinci MDIO module. | |
450 | ||
451 | To compile this driver as a module, choose M here: the module | |
452 | will be called davinci_mdio. This is recommended. | |
453 | ||
ef8c2dab CC |
454 | config TI_DAVINCI_CPDMA |
455 | tristate "TI DaVinci CPDMA Support" | |
456 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) | |
457 | help | |
458 | This driver supports TI's DaVinci CPDMA dma engine. | |
459 | ||
460 | To compile this driver as a module, choose M here: the module | |
461 | will be called davinci_cpdma. This is recommended. | |
462 | ||
a1365275 SH |
463 | config DM9000 |
464 | tristate "DM9000 support" | |
f40d24d9 | 465 | depends on ARM || BLACKFIN || MIPS |
a1365275 SH |
466 | select CRC32 |
467 | select MII | |
468 | ---help--- | |
469 | Support for DM9000 chipset. | |
470 | ||
57ce45dd AB |
471 | To compile this driver as a module, choose M here. The module |
472 | will be called dm9000. | |
a1365275 | 473 | |
485ca22a BD |
474 | config DM9000_DEBUGLEVEL |
475 | int "DM9000 maximum debug level" | |
476 | depends on DM9000 | |
477 | default 4 | |
478 | help | |
479 | The maximum level of debugging code compiled into the DM9000 | |
480 | driver. | |
481 | ||
f8dd0ecb BD |
482 | config DM9000_FORCE_SIMPLE_PHY_POLL |
483 | bool "Force simple NSR based PHY polling" | |
484 | depends on DM9000 | |
485 | ---help--- | |
486 | This configuration forces the DM9000 to use the NSR's LinkStatus | |
487 | bit to determine if the link is up or down instead of the more | |
488 | costly MII PHY reads. Note, this will not work if the chip is | |
489 | operating with an external PHY. | |
490 | ||
3ec9c11d CL |
491 | config ENC28J60 |
492 | tristate "ENC28J60 support" | |
493 | depends on EXPERIMENTAL && SPI && NET_ETHERNET | |
494 | select CRC32 | |
495 | ---help--- | |
496 | Support for the Microchip EN28J60 ethernet chip. | |
497 | ||
2bfc79de | 498 | To compile this driver as a module, choose M here. The module will be |
3ec9c11d CL |
499 | called enc28j60. |
500 | ||
501 | config ENC28J60_WRITEVERIFY | |
502 | bool "Enable write verify" | |
503 | depends on ENC28J60 | |
504 | ---help--- | |
505 | Enable the verify after the buffer write useful for debugging purpose. | |
506 | If unsure, say N. | |
507 | ||
a1702857 TR |
508 | config ETHOC |
509 | tristate "OpenCores 10/100 Mbps Ethernet MAC support" | |
0ebe74e7 | 510 | depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA |
a1702857 TR |
511 | select MII |
512 | select PHYLIB | |
c5cacb3b RD |
513 | select CRC32 |
514 | select BITREVERSE | |
a1702857 TR |
515 | help |
516 | Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. | |
517 | ||
d4c41139 KG |
518 | config GRETH |
519 | tristate "Aeroflex Gaisler GRETH Ethernet MAC support" | |
cf261b23 | 520 | depends on SPARC |
d4c41139 KG |
521 | select PHYLIB |
522 | select CRC32 | |
523 | help | |
524 | Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. | |
525 | ||
47964174 IY |
526 | config DNET |
527 | tristate "Dave ethernet support (DNET)" | |
4b97926d | 528 | depends on NET_ETHERNET && HAS_IOMEM |
47964174 IY |
529 | select PHYLIB |
530 | help | |
531 | The Dave ethernet interface (DNET) is found on Qong Board FPGA. | |
532 | Say Y to include support for the DNET chip. | |
533 | ||
534 | To compile this driver as a module, choose M here: the module | |
535 | will be called dnet. | |
536 | ||
1da177e4 LT |
537 | source "drivers/net/tulip/Kconfig" |
538 | ||
539 | config AT1700 | |
540 | tristate "AT1700/1720 support (EXPERIMENTAL)" | |
d1c0a65f | 541 | depends on (ISA || MCA_LEGACY) && EXPERIMENTAL |
1da177e4 LT |
542 | select CRC32 |
543 | ---help--- | |
544 | If you have a network (Ethernet) card of this type, say Y and read | |
545 | the Ethernet-HOWTO, available from | |
546 | <http://www.tldp.org/docs.html#howto>. | |
547 | ||
57ce45dd | 548 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
549 | will be called at1700. |
550 | ||
1da177e4 LT |
551 | config HP100 |
552 | tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" | |
d1c0a65f | 553 | depends on ISA || EISA || PCI |
1da177e4 LT |
554 | help |
555 | If you have a network (Ethernet) card of this type, say Y and read | |
556 | the Ethernet-HOWTO, available from | |
557 | <http://www.tldp.org/docs.html#howto>. | |
558 | ||
57ce45dd | 559 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
560 | will be called hp100. |
561 | ||
562 | config NET_ISA | |
563 | bool "Other ISA cards" | |
d1c0a65f | 564 | depends on ISA |
1da177e4 LT |
565 | ---help--- |
566 | If your network (Ethernet) card hasn't been mentioned yet and its | |
567 | bus system (that's the way the cards talks to the other components | |
568 | of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. | |
569 | Make sure you know the name of your card. Read the Ethernet-HOWTO, | |
570 | available from <http://www.tldp.org/docs.html#howto>. | |
571 | ||
572 | If unsure, say Y. | |
573 | ||
574 | Note that the answer to this question doesn't directly affect the | |
575 | kernel: saying N will just cause the configurator to skip all | |
576 | the remaining ISA network card questions. If you say Y, you will be | |
577 | asked for your specific card in the following questions. | |
578 | ||
1da177e4 LT |
579 | config EWRK3 |
580 | tristate "EtherWORKS 3 (DE203, DE204, DE205) support" | |
581 | depends on NET_ISA | |
582 | select CRC32 | |
583 | ---help--- | |
584 | This driver supports the DE203, DE204 and DE205 network (Ethernet) | |
585 | cards. If this is for you, say Y and read | |
586 | <file:Documentation/networking/ewrk3.txt> in the kernel source as | |
587 | well as the Ethernet-HOWTO, available from | |
588 | <http://www.tldp.org/docs.html#howto>. | |
589 | ||
57ce45dd | 590 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
591 | will be called ewrk3. |
592 | ||
1da177e4 LT |
593 | config ETH16I |
594 | tristate "ICL EtherTeam 16i/32 support" | |
595 | depends on NET_ISA | |
596 | help | |
597 | If you have a network (Ethernet) card of this type, say Y and read | |
598 | the Ethernet-HOWTO, available from | |
599 | <http://www.tldp.org/docs.html#howto>. | |
600 | ||
57ce45dd | 601 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
602 | will be called eth16i. |
603 | ||
1da177e4 LT |
604 | config SEEQ8005 |
605 | tristate "SEEQ8005 support (EXPERIMENTAL)" | |
606 | depends on NET_ISA && EXPERIMENTAL | |
607 | help | |
608 | This is a driver for the SEEQ 8005 network (Ethernet) card. If this | |
609 | is for you, read the Ethernet-HOWTO, available from | |
610 | <http://www.tldp.org/docs.html#howto>. | |
611 | ||
57ce45dd | 612 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
613 | will be called seeq8005. |
614 | ||
1da177e4 LT |
615 | config IBMLANA |
616 | tristate "IBM LAN Adapter/A support" | |
e6353f30 | 617 | depends on MCA |
1da177e4 LT |
618 | ---help--- |
619 | This is a Micro Channel Ethernet adapter. You need to set | |
620 | CONFIG_MCA to use this driver. It is both available as an in-kernel | |
621 | driver and as a module. | |
622 | ||
57ce45dd | 623 | To compile this driver as a module, choose M here. The only |
1da177e4 LT |
624 | currently supported card is the IBM LAN Adapter/A for Ethernet. It |
625 | will both support 16K and 32K memory windows, however a 32K window | |
626 | gives a better security against packet losses. Usage of multiple | |
627 | boards with this driver should be possible, but has not been tested | |
628 | up to now due to lack of hardware. | |
629 | ||
630 | config IBMVETH | |
631 | tristate "IBM LAN Virtual Ethernet support" | |
d1c0a65f | 632 | depends on PPC_PSERIES |
1da177e4 LT |
633 | ---help--- |
634 | This driver supports virtual ethernet adapters on newer IBM iSeries | |
635 | and pSeries systems. | |
636 | ||
57ce45dd | 637 | To compile this driver as a module, choose M here. The module will |
1da177e4 LT |
638 | be called ibmveth. |
639 | ||
1d3bb996 | 640 | source "drivers/net/ibm_newemac/Kconfig" |
1da177e4 LT |
641 | |
642 | config NET_PCI | |
643 | bool "EISA, VLB, PCI and on board controllers" | |
d1c0a65f | 644 | depends on ISA || EISA || PCI |
1da177e4 LT |
645 | help |
646 | This is another class of network cards which attach directly to the | |
647 | bus. If you have one of those, say Y and read the Ethernet-HOWTO, | |
648 | available from <http://www.tldp.org/docs.html#howto>. | |
649 | ||
650 | Note that the answer to this question doesn't directly affect the | |
651 | kernel: saying N will just cause the configurator to skip all | |
652 | the questions about this class of network cards. If you say Y, you | |
653 | will be asked for your specific card in the following questions. If | |
654 | you are unsure, say Y. | |
655 | ||
1da177e4 LT |
656 | config ADAPTEC_STARFIRE |
657 | tristate "Adaptec Starfire/DuraLAN support" | |
658 | depends on NET_PCI && PCI | |
659 | select CRC32 | |
660 | select MII | |
661 | help | |
662 | Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network | |
663 | adapter. The DuraLAN chip is used on the 64 bit PCI boards from | |
664 | Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip | |
665 | driver. | |
666 | ||
667 | To compile this driver as a module, choose M here: the module | |
668 | will be called starfire. This is recommended. | |
669 | ||
1eb1cc7a TH |
670 | config KSZ884X_PCI |
671 | tristate "Micrel KSZ8841/2 PCI" | |
672 | depends on NET_PCI && PCI | |
673 | select MII | |
674 | select CRC32 | |
675 | help | |
676 | This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. | |
677 | ||
678 | To compile this driver as a module, choose M here. The module | |
679 | will be called ksz884x. | |
680 | ||
1da177e4 | 681 | config FORCEDETH |
82770086 AB |
682 | tristate "nForce Ethernet support" |
683 | depends on NET_PCI && PCI | |
1da177e4 LT |
684 | help |
685 | If you have a network (Ethernet) controller of this type, say Y and | |
686 | read the Ethernet-HOWTO, available from | |
687 | <http://www.tldp.org/docs.html#howto>. | |
688 | ||
57ce45dd AB |
689 | To compile this driver as a module, choose M here. The module |
690 | will be called forcedeth. | |
1da177e4 | 691 | |
1da177e4 LT |
692 | config CS89x0 |
693 | tristate "CS89x0 support" | |
0ac4ed9d | 694 | depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \ |
2ce8c07d | 695 | || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440) |
1da177e4 LT |
696 | ---help--- |
697 | Support for CS89x0 chipset based Ethernet cards. If you have a | |
698 | network (Ethernet) card of this type, say Y and read the | |
699 | Ethernet-HOWTO, available from | |
700 | <http://www.tldp.org/docs.html#howto> as well as | |
701 | <file:Documentation/networking/cs89x0.txt>. | |
702 | ||
57ce45dd AB |
703 | To compile this driver as a module, choose M here. The module |
704 | will be called cs89x0. | |
1da177e4 | 705 | |
0ac4ed9d GC |
706 | config CS89x0_NONISA_IRQ |
707 | def_bool y | |
708 | depends on CS89x0 != n | |
2ce8c07d | 709 | depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440 |
0ac4ed9d | 710 | |
1da177e4 LT |
711 | config TC35815 |
712 | tristate "TOSHIBA TC35815 Ethernet support" | |
eea221ce | 713 | depends on NET_PCI && PCI && MIPS |
c6686fe3 | 714 | select PHYLIB |
1da177e4 | 715 | |
1da177e4 LT |
716 | config FEALNX |
717 | tristate "Myson MTD-8xx PCI Ethernet support" | |
718 | depends on NET_PCI && PCI | |
719 | select CRC32 | |
720 | select MII | |
721 | help | |
631dd1a8 JM |
722 | Say Y here to support the Myson MTD-800 family of PCI-based Ethernet |
723 | cards. <http://www.myson.com.tw/> | |
1da177e4 LT |
724 | |
725 | config NATSEMI | |
726 | tristate "National Semiconductor DP8381x series PCI Ethernet support" | |
727 | depends on NET_PCI && PCI | |
728 | select CRC32 | |
729 | help | |
730 | This driver is for the National Semiconductor DP83810 series, | |
731 | which is used in cards from PureData, NetGear, Linksys | |
732 | and others, including the 83815 chip. | |
733 | More specific information and updates are available from | |
734 | <http://www.scyld.com/network/natsemi.html>. | |
735 | ||
1da177e4 LT |
736 | config 8139CP |
737 | tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" | |
738 | depends on NET_PCI && PCI && EXPERIMENTAL | |
739 | select CRC32 | |
740 | select MII | |
741 | help | |
742 | This is a driver for the Fast Ethernet PCI network cards based on | |
743 | the RTL8139C+ chips. If you have one of those, say Y and read | |
744 | the Ethernet-HOWTO, available from | |
745 | <http://www.tldp.org/docs.html#howto>. | |
746 | ||
747 | To compile this driver as a module, choose M here: the module | |
748 | will be called 8139cp. This is recommended. | |
749 | ||
750 | config 8139TOO | |
f04e3f09 | 751 | tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" |
1da177e4 LT |
752 | depends on NET_PCI && PCI |
753 | select CRC32 | |
754 | select MII | |
755 | ---help--- | |
756 | This is a driver for the Fast Ethernet PCI network cards based on | |
f04e3f09 AB |
757 | the RTL 8129/8130/8139 chips. If you have one of those, say Y and |
758 | read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. | |
1da177e4 LT |
759 | |
760 | To compile this driver as a module, choose M here: the module | |
761 | will be called 8139too. This is recommended. | |
762 | ||
763 | config 8139TOO_PIO | |
764 | bool "Use PIO instead of MMIO" | |
765 | default y | |
766 | depends on 8139TOO | |
767 | help | |
768 | This instructs the driver to use programmed I/O ports (PIO) instead | |
769 | of PCI shared memory (MMIO). This can possibly solve some problems | |
770 | in case your mainboard has memory consistency issues. If unsure, | |
771 | say N. | |
772 | ||
773 | config 8139TOO_TUNE_TWISTER | |
774 | bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" | |
775 | depends on 8139TOO | |
776 | help | |
777 | This implements a function which might come in handy in case you | |
778 | are using low quality on long cabling. It is required for RealTek | |
779 | RTL-8139 revision K boards, and totally unused otherwise. It tries | |
780 | to match the transceiver to the cable characteristics. This is | |
781 | experimental since hardly documented by the manufacturer. | |
782 | If unsure, say Y. | |
783 | ||
784 | config 8139TOO_8129 | |
785 | bool "Support for older RTL-8129/8130 boards" | |
786 | depends on 8139TOO | |
787 | help | |
788 | This enables support for the older and uncommon RTL-8129 and | |
789 | RTL-8130 chips, which support MII via an external transceiver, | |
790 | instead of an internal one. Disabling this option will save some | |
791 | memory by making the code size smaller. If unsure, say Y. | |
792 | ||
793 | config 8139_OLD_RX_RESET | |
794 | bool "Use older RX-reset method" | |
795 | depends on 8139TOO | |
796 | help | |
797 | The 8139too driver was recently updated to contain a more rapid | |
798 | reset sequence, in the face of severe receive errors. This "new" | |
799 | RX-reset method should be adequate for all boards. But if you | |
800 | experience problems, you can enable this option to restore the | |
801 | old RX-reset behavior. If unsure, say N. | |
802 | ||
7a47dd7a | 803 | config R6040 |
68334115 | 804 | tristate "RDC R6040 Fast Ethernet Adapter support" |
7a47dd7a SW |
805 | depends on NET_PCI && PCI |
806 | select CRC32 | |
807 | select MII | |
3831861b | 808 | select PHYLIB |
7a47dd7a SW |
809 | help |
810 | This is a driver for the R6040 Fast Ethernet MACs found in the | |
811 | the RDC R-321x System-on-chips. | |
812 | ||
813 | To compile this driver as a module, choose M here: the module | |
814 | will be called r6040. This is recommended. | |
815 | ||
1da177e4 LT |
816 | config SIS900 |
817 | tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" | |
818 | depends on NET_PCI && PCI | |
819 | select CRC32 | |
6da0f685 | 820 | select MII |
1da177e4 LT |
821 | ---help--- |
822 | This is a driver for the Fast Ethernet PCI network cards based on | |
823 | the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in | |
c3cf560e | 824 | SiS 630 and SiS 540 chipsets. |
1da177e4 LT |
825 | |
826 | This driver also supports AMD 79C901 HomePNA so that you can use | |
827 | your phone line as a network cable. | |
828 | ||
829 | To compile this driver as a module, choose M here: the module | |
830 | will be called sis900. This is recommended. | |
831 | ||
1da177e4 LT |
832 | config SUNDANCE |
833 | tristate "Sundance Alta support" | |
834 | depends on NET_PCI && PCI | |
835 | select CRC32 | |
836 | select MII | |
837 | help | |
838 | This driver is for the Sundance "Alta" chip. | |
839 | More specific information and updates are available from | |
840 | <http://www.scyld.com/network/sundance.html>. | |
841 | ||
842 | config SUNDANCE_MMIO | |
843 | bool "Use MMIO instead of PIO" | |
844 | depends on SUNDANCE | |
845 | help | |
846 | Enable memory-mapped I/O for interaction with Sundance NIC registers. | |
847 | Do NOT enable this by default, PIO (enabled when MMIO is disabled) | |
848 | is known to solve bugs on certain chips. | |
849 | ||
850 | If unsure, say N. | |
851 | ||
852 | config TLAN | |
853 | tristate "TI ThunderLAN support" | |
93e16847 | 854 | depends on NET_PCI && (PCI || EISA) |
1da177e4 LT |
855 | ---help--- |
856 | If you have a PCI Ethernet network card based on the ThunderLAN chip | |
857 | which is supported by this driver, say Y and read the | |
858 | Ethernet-HOWTO, available from | |
859 | <http://www.tldp.org/docs.html#howto>. | |
860 | ||
861 | Devices currently supported by this driver are Compaq Netelligent, | |
862 | Compaq NetFlex and Olicom cards. Please read the file | |
863 | <file:Documentation/networking/tlan.txt> for more details. | |
864 | ||
57ce45dd | 865 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
866 | will be called tlan. |
867 | ||
868 | Please email feedback to <torben.mathiasen@compaq.com>. | |
869 | ||
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 870 | config KS8842 |
28bd620c | 871 | tristate "Micrel KSZ8841/42 with generic bus interface" |
19de1e38 | 872 | depends on HAS_IOMEM && DMA_ENGINE |
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 873 | help |
e85eb117 PDM |
874 | This platform driver is for KSZ8841(1-port) / KS8842(2-port) |
875 | ethernet switch chip (managed, VLAN, QoS) from Micrel or | |
876 | Timberdale(FPGA). | |
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 877 | |
3ba81f3e | 878 | config KS8851 |
e85eb117 PDM |
879 | tristate "Micrel KS8851 SPI" |
880 | depends on SPI | |
881 | select MII | |
cbb35f8a | 882 | select CRC32 |
e85eb117 PDM |
883 | help |
884 | SPI driver for Micrel KS8851 SPI attached network chip. | |
3ba81f3e | 885 | |
a55c0a0e CD |
886 | config KS8851_MLL |
887 | tristate "Micrel KS8851 MLL" | |
888 | depends on HAS_IOMEM | |
47a01a0c | 889 | select MII |
a55c0a0e CD |
890 | help |
891 | This platform driver is for Micrel KS8851 Address/data bus | |
892 | multiplexed network chip. | |
893 | ||
1da177e4 LT |
894 | config VIA_RHINE |
895 | tristate "VIA Rhine support" | |
896 | depends on NET_PCI && PCI | |
897 | select CRC32 | |
898 | select MII | |
899 | help | |
900 | If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), | |
901 | Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type | |
902 | Ethernet functions can also be found integrated on South Bridges | |
903 | (e.g. VT8235). | |
904 | ||
905 | To compile this driver as a module, choose M here. The module | |
906 | will be called via-rhine. | |
907 | ||
908 | config VIA_RHINE_MMIO | |
909 | bool "Use MMIO instead of PIO" | |
910 | depends on VIA_RHINE | |
911 | help | |
912 | This instructs the driver to use PCI shared memory (MMIO) instead of | |
913 | programmed I/O ports (PIO). Enabling this gives an improvement in | |
914 | processing time in parts of the driver. | |
915 | ||
916 | If unsure, say Y. | |
917 | ||
bf345707 CEB |
918 | config SC92031 |
919 | tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" | |
920 | depends on NET_PCI && PCI && EXPERIMENTAL | |
921 | select CRC32 | |
922 | ---help--- | |
923 | This is a driver for the Fast Ethernet PCI network cards based on | |
924 | the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you | |
925 | have one of these, say Y here. | |
926 | ||
927 | To compile this driver as a module, choose M here: the module | |
928 | will be called sc92031. This is recommended. | |
929 | ||
d95b39c3 MC |
930 | config CPMAC |
931 | tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" | |
839b04c4 | 932 | depends on NET_ETHERNET && EXPERIMENTAL && AR7 |
d95b39c3 | 933 | select PHYLIB |
d95b39c3 MC |
934 | help |
935 | TI AR7 CPMAC Ethernet support | |
936 | ||
1da177e4 LT |
937 | config NET_POCKET |
938 | bool "Pocket and portable adapters" | |
d1c0a65f | 939 | depends on PARPORT |
1da177e4 LT |
940 | ---help--- |
941 | Cute little network (Ethernet) devices which attach to the parallel | |
942 | port ("pocket adapters"), commonly used with laptops. If you have | |
943 | one of those, say Y and read the Ethernet-HOWTO, available from | |
944 | <http://www.tldp.org/docs.html#howto>. | |
945 | ||
946 | If you want to plug a network (or some other) card into the PCMCIA | |
947 | (or PC-card) slot of your laptop instead (PCMCIA is the standard for | |
948 | credit card size extension cards used by all modern laptops), you | |
949 | need the pcmcia-cs package (location contained in the file | |
950 | <file:Documentation/Changes>) and you can say N here. | |
951 | ||
952 | Laptop users should read the Linux Laptop home page at | |
953 | <http://www.linux-on-laptops.com/> or | |
954 | Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. | |
955 | ||
956 | Note that the answer to this question doesn't directly affect the | |
957 | kernel: saying N will just cause the configurator to skip all | |
958 | the questions about this class of network devices. If you say Y, you | |
959 | will be asked for your specific device in the following questions. | |
960 | ||
961 | config ATP | |
962 | tristate "AT-LAN-TEC/RealTek pocket adapter support" | |
32fa2bfc | 963 | depends on NET_POCKET && PARPORT && X86 |
1da177e4 LT |
964 | select CRC32 |
965 | ---help--- | |
966 | This is a network (Ethernet) device which attaches to your parallel | |
967 | port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, | |
968 | available from <http://www.tldp.org/docs.html#howto>, if you | |
969 | want to use this. If you intend to use this driver, you should have | |
970 | said N to the "Parallel printer support", because the two drivers | |
971 | don't like each other. | |
972 | ||
973 | To compile this driver as a module, choose M here: the module | |
974 | will be called atp. | |
975 | ||
976 | config DE600 | |
977 | tristate "D-Link DE600 pocket adapter support" | |
32fa2bfc | 978 | depends on NET_POCKET && PARPORT |
1da177e4 LT |
979 | ---help--- |
980 | This is a network (Ethernet) device which attaches to your parallel | |
981 | port. Read <file:Documentation/networking/DLINK.txt> as well as the | |
982 | Ethernet-HOWTO, available from | |
983 | <http://www.tldp.org/docs.html#howto>, if you want to use | |
984 | this. It is possible to have several devices share a single parallel | |
985 | port and it is safe to compile the corresponding drivers into the | |
986 | kernel. | |
987 | ||
988 | To compile this driver as a module, choose M here: the module | |
989 | will be called de600. | |
990 | ||
991 | config DE620 | |
992 | tristate "D-Link DE620 pocket adapter support" | |
32fa2bfc | 993 | depends on NET_POCKET && PARPORT |
1da177e4 LT |
994 | ---help--- |
995 | This is a network (Ethernet) device which attaches to your parallel | |
996 | port. Read <file:Documentation/networking/DLINK.txt> as well as the | |
997 | Ethernet-HOWTO, available from | |
998 | <http://www.tldp.org/docs.html#howto>, if you want to use | |
999 | this. It is possible to have several devices share a single parallel | |
1000 | port and it is safe to compile the corresponding drivers into the | |
1001 | kernel. | |
1002 | ||
1003 | To compile this driver as a module, choose M here: the module | |
1004 | will be called de620. | |
1005 | ||
1006 | config SGISEEQ | |
1007 | tristate "SGI Seeq ethernet controller support" | |
49b11bc3 | 1008 | depends on SGI_HAS_SEEQ |
1da177e4 LT |
1009 | help |
1010 | Say Y here if you have an Seeq based Ethernet network card. This is | |
1011 | used in many Silicon Graphics machines. | |
1012 | ||
1da177e4 | 1013 | config FEC |
64423307 | 1014 | bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" |
bd011e88 | 1015 | depends on M523x || M527x || M5272 || M528x || M520x || M532x || \ |
085e79ed UKK |
1016 | IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC |
1017 | default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM | |
e6b043d5 | 1018 | select PHYLIB |
1da177e4 LT |
1019 | help |
1020 | Say Y here if you want to use the built-in 10/100 Fast ethernet | |
196719ec | 1021 | controller on some Motorola ColdFire and Freescale i.MX processors. |
2af6921f | 1022 | |
5d031e9e DP |
1023 | config FEC_MPC52xx |
1024 | tristate "MPC52xx FEC driver" | |
847cdf42 | 1025 | depends on PPC_MPC52xx && PPC_BESTCOMM |
5d031e9e DP |
1026 | select CRC32 |
1027 | select PHYLIB | |
847cdf42 | 1028 | select PPC_BESTCOMM_FEC |
5d031e9e DP |
1029 | ---help--- |
1030 | This option enables support for the MPC5200's on-chip | |
1031 | Fast Ethernet Controller | |
4737f097 | 1032 | If compiled as module, it will be called fec_mpc52xx. |
5d031e9e DP |
1033 | |
1034 | config FEC_MPC52xx_MDIO | |
1035 | bool "MPC52xx FEC MDIO bus driver" | |
1036 | depends on FEC_MPC52xx | |
1037 | default y | |
1038 | ---help--- | |
1039 | The MPC5200's FEC can connect to the Ethernet either with | |
1040 | an external MII PHY chip or 10 Mbps 7-wire interface | |
1041 | (Motorola? industry standard). | |
1042 | If your board uses an external PHY connected to FEC, enable this. | |
1043 | If not sure, enable. | |
4737f097 | 1044 | If compiled as module, it will be called fec_mpc52xx_phy. |
5d031e9e | 1045 | |
452c1ce2 CS |
1046 | config ATL2 |
1047 | tristate "Atheros L2 Fast Ethernet support" | |
1048 | depends on PCI | |
1049 | select CRC32 | |
1050 | select MII | |
1051 | help | |
1052 | This driver supports the Atheros L2 fast ethernet adapter. | |
1053 | ||
1054 | To compile this driver as a module, choose M here. The module | |
1055 | will be called atl2. | |
1056 | ||
bb81b2dd JL |
1057 | config XILINX_EMACLITE |
1058 | tristate "Xilinx 10/100 Ethernet Lite support" | |
1059 | depends on PPC32 || MICROBLAZE | |
5cdaaa12 | 1060 | select PHYLIB |
bb81b2dd JL |
1061 | help |
1062 | This driver supports the 10/100 Ethernet Lite from Xilinx. | |
1063 | ||
8d77c036 PYC |
1064 | config FTMAC100 |
1065 | tristate "Faraday FTMAC100 10/100 Ethernet support" | |
1066 | depends on ARM | |
1067 | select MII | |
1068 | help | |
1069 | This driver supports the FTMAC100 10/100 Ethernet controller | |
1070 | from Faraday. It is used on Faraday A320, Andes AG101 and some | |
1071 | other ARM/NDS32 SoC's. | |
1072 | ||
504d4721 JC |
1073 | config LANTIQ_ETOP |
1074 | tristate "Lantiq SoC ETOP driver" | |
1075 | depends on SOC_TYPE_XWAY | |
1076 | help | |
1077 | Support for the MII0 inside the Lantiq SoC | |
1078 | ||
1079 | ||
48257c4f | 1080 | source "drivers/net/fs_enet/Kconfig" |
1da177e4 | 1081 | |
d6aa60a1 DD |
1082 | source "drivers/net/octeon/Kconfig" |
1083 | ||
d1c0a65f | 1084 | endif # NET_ETHERNET |
1da177e4 LT |
1085 | |
1086 | # | |
1087 | # Gigabit Ethernet | |
1088 | # | |
1089 | ||
f30486d5 JE |
1090 | menuconfig NETDEV_1000 |
1091 | bool "Ethernet (1000 Mbit)" | |
cbcd2a4c | 1092 | depends on !UML |
f30486d5 | 1093 | default y |
06bfb7eb JE |
1094 | ---help--- |
1095 | Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common | |
1096 | type of Local Area Network (LAN) in universities and companies. | |
1097 | ||
1098 | Say Y here to get to see options for Gigabit Ethernet drivers. | |
1099 | This option alone does not add any kernel code. | |
1100 | Note that drivers supporting both 100 and 1000 MBit may be listed | |
1101 | under "Ethernet (10 or 100MBit)" instead. | |
1102 | ||
1103 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
1104 | |
1105 | if NETDEV_1000 | |
1da177e4 | 1106 | |
1da177e4 | 1107 | config DL2K |
df950828 | 1108 | tristate "DL2000/TC902x-based Gigabit Ethernet support" |
1da177e4 LT |
1109 | depends on PCI |
1110 | select CRC32 | |
1111 | help | |
df950828 K |
1112 | This driver supports DL2000/TC902x-based Gigabit ethernet cards, |
1113 | which includes | |
1da177e4 LT |
1114 | D-Link DGE-550T Gigabit Ethernet Adapter. |
1115 | D-Link DL2000-based Gigabit Ethernet Adapter. | |
df950828 | 1116 | Sundance/Tamarack TC902x Gigabit Ethernet Adapter. |
1da177e4 LT |
1117 | |
1118 | To compile this driver as a module, choose M here: the | |
1119 | module will be called dl2k. | |
1120 | ||
ab7a9831 SH |
1121 | config IP1000 |
1122 | tristate "IP1000 Gigabit Ethernet support" | |
1123 | depends on PCI && EXPERIMENTAL | |
1124 | select MII | |
1125 | ---help--- | |
1126 | This driver supports IP1000 gigabit Ethernet cards. | |
1127 | ||
1128 | To compile this driver as a module, choose M here: the module | |
1129 | will be called ipg. This is recommended. | |
1130 | ||
15d014d1 LB |
1131 | source "drivers/net/ixp2000/Kconfig" |
1132 | ||
1da177e4 | 1133 | config NS83820 |
47c51431 | 1134 | tristate "National Semiconductor DP83820 support" |
1da177e4 LT |
1135 | depends on PCI |
1136 | help | |
1137 | This is a driver for the National Semiconductor DP83820 series | |
1138 | of gigabit ethernet MACs. Cards using this chipset include | |
1139 | the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, | |
1140 | SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of | |
1141 | zero copy. | |
1142 | ||
1143 | config HAMACHI | |
1144 | tristate "Packet Engines Hamachi GNIC-II support" | |
1145 | depends on PCI | |
1146 | select MII | |
1147 | help | |
1148 | If you have a Gigabit Ethernet card of this type, say Y and read | |
1149 | the Ethernet-HOWTO, available from | |
1150 | <http://www.tldp.org/docs.html#howto>. | |
1151 | ||
57ce45dd | 1152 | To compile this driver as a module, choose M here. The module will be |
1da177e4 LT |
1153 | called hamachi. |
1154 | ||
1155 | config YELLOWFIN | |
1156 | tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" | |
1157 | depends on PCI && EXPERIMENTAL | |
1158 | select CRC32 | |
1159 | ---help--- | |
1160 | Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet | |
1161 | adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is | |
1162 | used by the Beowulf Linux cluster project. See | |
1163 | <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more | |
1164 | information about this driver in particular and Beowulf in general. | |
1165 | ||
1166 | To compile this driver as a module, choose M here: the module | |
1167 | will be called yellowfin. This is recommended. | |
1168 | ||
1169 | config R8169 | |
1170 | tristate "Realtek 8169 gigabit ethernet support" | |
1171 | depends on PCI | |
bca03d5f | 1172 | select FW_LOADER |
1da177e4 | 1173 | select CRC32 |
b7372492 | 1174 | select MII |
1da177e4 LT |
1175 | ---help--- |
1176 | Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. | |
1177 | ||
1178 | To compile this driver as a module, choose M here: the module | |
1179 | will be called r8169. This is recommended. | |
1180 | ||
890e8d0a | 1181 | config SIS190 |
e797637f | 1182 | tristate "SiS190/SiS191 gigabit ethernet support" |
e9985d53 AB |
1183 | depends on PCI |
1184 | select CRC32 | |
1185 | select MII | |
1186 | ---help--- | |
e797637f FR |
1187 | Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or |
1188 | a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to | |
1189 | appear in lan on motherboard designs which are based on SiS 965 | |
1190 | and SiS 966 south bridge. | |
e9985d53 AB |
1191 | |
1192 | To compile this driver as a module, choose M here: the module | |
1193 | will be called sis190. This is recommended. | |
890e8d0a | 1194 | |
baef58b1 | 1195 | config SKGE |
560040b8 | 1196 | tristate "Marvell Yukon Gigabit Ethernet support" |
7a160c73 | 1197 | depends on PCI |
baef58b1 SH |
1198 | select CRC32 |
1199 | ---help--- | |
1200 | This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx | |
1201 | and related Gigabit Ethernet adapters. It is a new smaller driver | |
46a60f2d | 1202 | with better performance and more complete ethtool support. |
baef58b1 SH |
1203 | |
1204 | It does not support the link failover and network management | |
5ad887fa | 1205 | features that "portable" vendor supplied sk98lin driver does. |
cd28ab6a | 1206 | |
c6f0d75a DD |
1207 | This driver supports adapters based on the original Yukon chipset: |
1208 | Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, | |
1209 | Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. | |
1210 | ||
1211 | It does not support the newer Yukon2 chipset: a separate driver, | |
560040b8 | 1212 | sky2, is provided for these adapters. |
c6f0d75a DD |
1213 | |
1214 | To compile this driver as a module, choose M here: the module | |
1215 | will be called skge. This is recommended. | |
cd28ab6a | 1216 | |
678aa1f6 | 1217 | config SKGE_DEBUG |
e85eb117 PDM |
1218 | bool "Debugging interface" |
1219 | depends on SKGE && DEBUG_FS | |
1220 | help | |
1221 | This option adds the ability to dump driver state for debugging. | |
1222 | The file /sys/kernel/debug/skge/ethX displays the state of the internal | |
1223 | transmit and receive rings. | |
678aa1f6 | 1224 | |
e85eb117 | 1225 | If unsure, say N. |
678aa1f6 | 1226 | |
57d6fa37 | 1227 | config SKGE_GENESIS |
1228 | bool "Support for older SysKonnect Genesis boards" | |
1229 | depends on SKGE | |
1230 | help | |
1231 | This enables support for the older and uncommon SysKonnect Genesis | |
1232 | chips, which support MII via an external transceiver, instead of | |
1233 | an internal one. Disabling this option will save some memory | |
1234 | by making code smaller. If unsure say Y. | |
1235 | ||
cd28ab6a | 1236 | config SKY2 |
560040b8 | 1237 | tristate "Marvell Yukon 2 support" |
f479b322 | 1238 | depends on PCI |
cd28ab6a SH |
1239 | select CRC32 |
1240 | ---help--- | |
cab00891 | 1241 | This driver supports Gigabit Ethernet adapters based on the |
c6f0d75a DD |
1242 | Marvell Yukon 2 chipset: |
1243 | Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ | |
1244 | 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 | |
1245 | ||
f479b322 | 1246 | There is companion driver for the older Marvell Yukon and |
560040b8 | 1247 | SysKonnect Genesis based adapters: skge. |
cd28ab6a SH |
1248 | |
1249 | To compile this driver as a module, choose M here: the module | |
1250 | will be called sky2. This is recommended. | |
1251 | ||
3cf26753 | 1252 | config SKY2_DEBUG |
e85eb117 PDM |
1253 | bool "Debugging interface" |
1254 | depends on SKY2 && DEBUG_FS | |
1255 | help | |
1256 | This option adds the ability to dump driver state for debugging. | |
1257 | The file /sys/kernel/debug/sky2/ethX displays the state of the internal | |
1258 | transmit and receive rings. | |
3cf26753 | 1259 | |
e85eb117 | 1260 | If unsure, say N. |
1da177e4 LT |
1261 | |
1262 | config VIA_VELOCITY | |
1263 | tristate "VIA Velocity support" | |
73815538 | 1264 | depends on PCI |
1da177e4 LT |
1265 | select CRC32 |
1266 | select CRC_CCITT | |
1267 | select MII | |
1268 | help | |
1269 | If you have a VIA "Velocity" based network card say Y here. | |
1270 | ||
1271 | To compile this driver as a module, choose M here. The module | |
1272 | will be called via-velocity. | |
1273 | ||
aaec0fab JO |
1274 | config SPIDER_NET |
1275 | tristate "Spider Gigabit Ethernet driver" | |
3342cf0e | 1276 | depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) |
9b15879a | 1277 | select FW_LOADER |
aaec0fab JO |
1278 | help |
1279 | This driver supports the Gigabit Ethernet chips present on the | |
1280 | Cell Processor-Based Blades from IBM. | |
1281 | ||
5e123b84 | 1282 | config TSI108_ETH |
dd68ad22 PDM |
1283 | tristate "Tundra TSI108 gigabit Ethernet support" |
1284 | depends on TSI108_BRIDGE | |
1285 | help | |
1286 | This driver supports Tundra TSI108 gigabit Ethernet ports. | |
1287 | To compile this driver as a module, choose M here: the module | |
1288 | will be called tsi108_eth. | |
5e123b84 | 1289 | |
02c18891 MM |
1290 | config GELIC_NET |
1291 | tristate "PS3 Gigabit Ethernet driver" | |
1292 | depends on PPC_PS3 | |
1d32e218 | 1293 | select PS3_SYS_MANAGER |
02c18891 MM |
1294 | help |
1295 | This driver supports the network device on the PS3 game | |
1296 | console. This driver has built-in support for Ethernet. | |
1297 | ||
1298 | To compile this driver as a module, choose M here: the | |
1299 | module will be called ps3_gelic. | |
1300 | ||
09dde54c | 1301 | config GELIC_WIRELESS |
97ed8390 | 1302 | bool "PS3 Wireless support" |
92c6f8d8 | 1303 | depends on WLAN |
97ed8390 JL |
1304 | depends on GELIC_NET |
1305 | select WIRELESS_EXT | |
1306 | help | |
1307 | This option adds the support for the wireless feature of PS3. | |
1308 | If you have the wireless-less model of PS3 or have no plan to | |
1309 | use wireless feature, disabling this option saves memory. As | |
1310 | the driver automatically distinguishes the models, you can | |
1311 | safely enable this option even if you have a wireless-less model. | |
09dde54c | 1312 | |
1577ecef AF |
1313 | config FSL_PQ_MDIO |
1314 | tristate "Freescale PQ MDIO" | |
1315 | depends on FSL_SOC | |
1316 | select PHYLIB | |
1317 | help | |
1318 | This driver supports the MDIO bus used by the gianfar and UCC drivers. | |
1319 | ||
1da177e4 LT |
1320 | config GIANFAR |
1321 | tristate "Gianfar Ethernet" | |
3a83156b | 1322 | depends on FSL_SOC |
1577ecef | 1323 | select FSL_PQ_MDIO |
bb40dcbb | 1324 | select PHYLIB |
bf41a7c5 | 1325 | select CRC32 |
1da177e4 | 1326 | help |
ef82a306 JL |
1327 | This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, |
1328 | and MPC86xx family of chips, and the FEC on the 8540. | |
1da177e4 | 1329 | |
ce973b14 | 1330 | config UCC_GETH |
7d776cb5 TT |
1331 | tristate "Freescale QE Gigabit Ethernet" |
1332 | depends on QUICC_ENGINE | |
1577ecef | 1333 | select FSL_PQ_MDIO |
296baae2 | 1334 | select PHYLIB |
ce973b14 | 1335 | help |
7d776cb5 TT |
1336 | This driver supports the Gigabit Ethernet mode of the QUICC Engine, |
1337 | which is available on some Freescale SOCs. | |
ce973b14 | 1338 | |
d5b9049d MR |
1339 | config UGETH_TX_ON_DEMAND |
1340 | bool "Transmit on Demand support" | |
ce973b14 LY |
1341 | depends on UCC_GETH |
1342 | ||
1da177e4 | 1343 | config MV643XX_ETH |
9c1bbdfe | 1344 | tristate "Marvell Discovery (643XX) and Orion ethernet support" |
10ccff62 | 1345 | depends on (MV64X60 || PPC32 || PLAT_ORION) && INET |
ab307a39 | 1346 | select INET_LRO |
ed94493f | 1347 | select PHYLIB |
1da177e4 | 1348 | help |
9c1bbdfe LB |
1349 | This driver supports the gigabit ethernet MACs in the |
1350 | Marvell Discovery PPC/MIPS chipset family (MV643XX) and | |
1351 | in the Marvell Orion ARM SoC family. | |
1352 | ||
1353 | Some boards that use the Discovery chipset are the Momenco | |
1354 | Ocelot C and Jaguar ATX and Pegasos II. | |
1da177e4 | 1355 | |
92744989 GL |
1356 | config XILINX_LL_TEMAC |
1357 | tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" | |
e44171f1 | 1358 | depends on PPC || MICROBLAZE |
92744989 | 1359 | select PHYLIB |
92744989 GL |
1360 | help |
1361 | This driver supports the Xilinx 10/100/1000 LocalLink TEMAC | |
1362 | core used in Xilinx Spartan and Virtex FPGAs | |
1363 | ||
f3cc28c7 | 1364 | config ATL1 |
a6d1f369 JC |
1365 | tristate "Atheros/Attansic L1 Gigabit Ethernet support" |
1366 | depends on PCI | |
f3cc28c7 JC |
1367 | select CRC32 |
1368 | select MII | |
1369 | help | |
a6d1f369 JC |
1370 | This driver supports the Atheros/Attansic L1 gigabit ethernet |
1371 | adapter. | |
f3cc28c7 JC |
1372 | |
1373 | To compile this driver as a module, choose M here. The module | |
1374 | will be called atl1. | |
1375 | ||
a6a53252 JY |
1376 | config ATL1E |
1377 | tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)" | |
1378 | depends on PCI && EXPERIMENTAL | |
1379 | select CRC32 | |
1380 | select MII | |
1381 | help | |
1382 | This driver supports the Atheros L1E gigabit ethernet adapter. | |
1383 | ||
1384 | To compile this driver as a module, choose M here. The module | |
1385 | will be called atl1e. | |
1386 | ||
43250ddd JY |
1387 | config ATL1C |
1388 | tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)" | |
1389 | depends on PCI && EXPERIMENTAL | |
1390 | select CRC32 | |
1391 | select MII | |
1392 | help | |
1393 | This driver supports the Atheros L1C gigabit ethernet adapter. | |
1394 | ||
1395 | To compile this driver as a module, choose M here. The module | |
1396 | will be called atl1c. | |
1397 | ||
95252236 GFT |
1398 | config JME |
1399 | tristate "JMicron(R) PCI-Express Gigabit Ethernet support" | |
1400 | depends on PCI | |
1401 | select CRC32 | |
1402 | select MII | |
1403 | ---help--- | |
1404 | This driver supports the PCI-Express gigabit ethernet adapters | |
1405 | based on JMicron JMC250 chipset. | |
1406 | ||
1407 | To compile this driver as a module, choose M here. The module | |
1408 | will be called jme. | |
1409 | ||
8b0215aa OS |
1410 | config S6GMAC |
1411 | tristate "S6105 GMAC ethernet support" | |
1412 | depends on XTENSA_VARIANT_S6000 | |
1413 | select PHYLIB | |
1414 | help | |
1415 | This driver supports the on chip ethernet device on the | |
1416 | S6105 xtensa processor. | |
1417 | ||
1418 | To compile this driver as a module, choose M here. The module | |
1419 | will be called s6gmac. | |
1420 | ||
47dd7a54 GC |
1421 | source "drivers/net/stmmac/Kconfig" |
1422 | ||
77555ee7 | 1423 | config PCH_GBE |
b0e6baf5 | 1424 | tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE" |
77555ee7 | 1425 | depends on PCI |
116c1ea0 | 1426 | select MII |
77555ee7 | 1427 | ---help--- |
a1dcfcb7 TO |
1428 | This is a gigabit ethernet driver for EG20T PCH. |
1429 | EG20T PCH is the platform controller hub that is used in Intel's | |
77555ee7 | 1430 | general embedded platform. |
a1dcfcb7 | 1431 | EG20T PCH has Gigabit Ethernet interface. |
77555ee7 MO |
1432 | Using this interface, it is able to access system devices connected |
1433 | to Gigabit Ethernet. | |
1434 | This driver enables Gigabit Ethernet function. | |
1435 | ||
b0e6baf5 T |
1436 | This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ |
1437 | Output Hub), ML7223. | |
1438 | ML7223 IOH is for MP(Media Phone) use. | |
1439 | ML7223 is companion chip for Intel Atom E6xx series. | |
1440 | ML7223 is completely compatible for Intel EG20T PCH. | |
1441 | ||
69785b79 PYC |
1442 | config FTGMAC100 |
1443 | tristate "Faraday FTGMAC100 Gigabit Ethernet support" | |
1444 | depends on ARM | |
1445 | select PHYLIB | |
1446 | help | |
1447 | This driver supports the FTGMAC100 Gigabit Ethernet controller | |
1448 | from Faraday. It is used on Faraday A369, Andes AG102 and some | |
1449 | other ARM/NDS32 SoC's. | |
1450 | ||
f30486d5 | 1451 | endif # NETDEV_1000 |
1da177e4 LT |
1452 | |
1453 | # | |
1454 | # 10 Gigabit Ethernet | |
1455 | # | |
1456 | ||
f30486d5 JE |
1457 | menuconfig NETDEV_10000 |
1458 | bool "Ethernet (10000 Mbit)" | |
cbcd2a4c | 1459 | depends on !UML |
f30486d5 | 1460 | default y |
06bfb7eb JE |
1461 | ---help--- |
1462 | Say Y here to get to see options for 10 Gigabit Ethernet drivers. | |
1463 | This option alone does not add any kernel code. | |
1464 | ||
1465 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
1466 | |
1467 | if NETDEV_10000 | |
1da177e4 | 1468 | |
1b1c2e95 BH |
1469 | config MDIO |
1470 | tristate | |
1471 | ||
7a291083 JBT |
1472 | config EHEA |
1473 | tristate "eHEA Ethernet support" | |
60d5019b | 1474 | depends on IBMEBUS && INET && SPARSEMEM |
d4dc4ec9 | 1475 | select INET_LRO |
7a291083 JBT |
1476 | ---help--- |
1477 | This driver supports the IBM pSeries eHEA ethernet adapter. | |
1478 | ||
1479 | To compile the driver as a module, choose M here. The module | |
1480 | will be called ehea. | |
1481 | ||
01f2e4ea | 1482 | config ENIC |
641cb85e | 1483 | tristate "Cisco VIC Ethernet NIC Support" |
01f2e4ea | 1484 | depends on PCI && INET |
01f2e4ea | 1485 | help |
641cb85e | 1486 | This enables the support for the Cisco VIC Ethernet card. |
01f2e4ea | 1487 | |
1da177e4 | 1488 | config S2IO |
1901d042 | 1489 | tristate "Exar Xframe 10Gb Ethernet Adapter" |
1da177e4 LT |
1490 | depends on PCI |
1491 | ---help--- | |
1901d042 JM |
1492 | This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. |
1493 | ||
9eb343ae AM |
1494 | More specific information on configuring the driver is in |
1495 | <file:Documentation/networking/s2io.txt>. | |
1da177e4 | 1496 | |
1901d042 JM |
1497 | To compile this driver as a module, choose M here. The module |
1498 | will be called s2io. | |
1499 | ||
f1782852 | 1500 | config VXGE |
1901d042 | 1501 | tristate "Exar X3100 Series 10GbE PCIe Server Adapter" |
f1782852 RV |
1502 | depends on PCI && INET |
1503 | ---help--- | |
1901d042 | 1504 | This driver supports Exar Corp's X3100 Series 10 GbE PCIe |
f1782852 | 1505 | I/O Virtualized Server Adapter. |
1901d042 | 1506 | |
f1782852 RV |
1507 | More specific information on configuring the driver is in |
1508 | <file:Documentation/networking/vxge.txt>. | |
1509 | ||
1901d042 JM |
1510 | To compile this driver as a module, choose M here. The module |
1511 | will be called vxge. | |
1512 | ||
f1782852 RV |
1513 | config VXGE_DEBUG_TRACE_ALL |
1514 | bool "Enabling All Debug trace statments in driver" | |
1515 | default n | |
1516 | depends on VXGE | |
1517 | ---help--- | |
1518 | Say Y here if you want to enabling all the debug trace statements in | |
1901d042 JM |
1519 | the vxge driver. By default only few debug trace statements are |
1520 | enabled. | |
f1782852 | 1521 | |
0da34b6d BG |
1522 | config MYRI10GE |
1523 | tristate "Myricom Myri-10G Ethernet support" | |
e0d5dab2 | 1524 | depends on PCI && INET |
0da34b6d BG |
1525 | select FW_LOADER |
1526 | select CRC32 | |
1e6e9342 | 1527 | select INET_LRO |
0da34b6d BG |
1528 | ---help--- |
1529 | This driver supports Myricom Myri-10G Dual Protocol interface in | |
1530 | Ethernet mode. If the eeprom on your board is not recent enough, | |
1531 | you will need a newer firmware image. | |
1532 | You may get this image or more information, at: | |
1533 | ||
d2794905 | 1534 | <http://www.myri.com/scs/download-Myri10GE.html> |
0da34b6d | 1535 | |
57ce45dd | 1536 | To compile this driver as a module, choose M here. The module |
0da34b6d BG |
1537 | will be called myri10ge. |
1538 | ||
5dd2d332 | 1539 | config MYRI10GE_DCA |
1d19ecfc | 1540 | bool "Direct Cache Access (DCA) Support" |
5dd2d332 JG |
1541 | default y |
1542 | depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) | |
1d19ecfc JK |
1543 | ---help--- |
1544 | Say Y here if you want to use Direct Cache Access (DCA) in the | |
1545 | driver. DCA is a method for warming the CPU cache before data | |
1546 | is used, with the intent of lessening the impact of cache misses. | |
5dd2d332 | 1547 | |
f5cd7872 OJ |
1548 | config PASEMI_MAC |
1549 | tristate "PA Semi 1/10Gbit MAC" | |
10ccff62 | 1550 | depends on PPC_PASEMI && PCI && INET |
bb6e9590 | 1551 | select PHYLIB |
28ae79f5 | 1552 | select INET_LRO |
f5cd7872 OJ |
1553 | help |
1554 | This driver supports the on-chip 1/10Gbit Ethernet controller on | |
1555 | PA Semi's PWRficient line of chips. | |
1556 | ||
c27a02cd YP |
1557 | config MLX4_EN |
1558 | tristate "Mellanox Technologies 10Gbit Ethernet support" | |
1559 | depends on PCI && INET | |
1560 | select MLX4_CORE | |
1561 | select INET_LRO | |
1562 | help | |
1563 | This driver supports Mellanox Technologies ConnectX Ethernet | |
1564 | devices. | |
1565 | ||
225c7b1f RD |
1566 | config MLX4_CORE |
1567 | tristate | |
1568 | depends on PCI | |
1569 | default n | |
1570 | ||
1571 | config MLX4_DEBUG | |
6a108a14 | 1572 | bool "Verbose debugging output" if (MLX4_CORE && EXPERT) |
f550d94c | 1573 | depends on MLX4_CORE |
225c7b1f RD |
1574 | default y |
1575 | ---help--- | |
1576 | This option causes debugging code to be compiled into the | |
1577 | mlx4_core driver. The output can be turned on via the | |
1578 | debug_level module parameter (which can also be set after | |
1579 | the driver is loaded through sysfs). | |
1580 | ||
1a348ccc AG |
1581 | config TEHUTI |
1582 | tristate "Tehuti Networks 10G Ethernet" | |
1583 | depends on PCI | |
1584 | help | |
1585 | Tehuti Networks 10G Ethernet NIC | |
1586 | ||
8b230ed8 | 1587 | config BNA |
e85eb117 PDM |
1588 | tristate "Brocade 1010/1020 10Gb Ethernet Driver support" |
1589 | depends on PCI | |
1590 | ---help--- | |
1591 | This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet | |
1592 | cards. | |
1593 | To compile this driver as a module, choose M here: the module | |
1594 | will be called bna. | |
8b230ed8 | 1595 | |
e85eb117 PDM |
1596 | For general information and support, go to the Brocade support |
1597 | website at: | |
8b230ed8 | 1598 | |
e85eb117 | 1599 | <http://support.brocade.com> |
8b230ed8 | 1600 | |
f30486d5 | 1601 | endif # NETDEV_10000 |
1da177e4 | 1602 | |
1da177e4 LT |
1603 | source "drivers/net/tokenring/Kconfig" |
1604 | ||
1605 | source "drivers/net/wireless/Kconfig" | |
1606 | ||
143ee2d5 IPG |
1607 | source "drivers/net/wimax/Kconfig" |
1608 | ||
5b2fc499 JG |
1609 | source "drivers/net/usb/Kconfig" |
1610 | ||
1da177e4 | 1611 | source "drivers/net/pcmcia/Kconfig" |
1da177e4 LT |
1612 | |
1613 | source "drivers/net/wan/Kconfig" | |
1614 | ||
1615 | source "drivers/atm/Kconfig" | |
1616 | ||
8459464f SL |
1617 | source "drivers/ieee802154/Kconfig" |
1618 | ||
1da177e4 LT |
1619 | source "drivers/s390/net/Kconfig" |
1620 | ||
9b27105b SB |
1621 | source "drivers/net/caif/Kconfig" |
1622 | ||
e5a06939 CM |
1623 | config TILE_NET |
1624 | tristate "Tilera GBE/XGBE network driver support" | |
1625 | depends on TILE | |
1626 | default y | |
1627 | select CRC32 | |
1628 | help | |
1629 | This is a standard Linux network device driver for the | |
1630 | on-chip Tilera Gigabit Ethernet and XAUI interfaces. | |
1631 | ||
1632 | To compile this driver as a module, choose M here: the module | |
1633 | will be called tile_net. | |
1634 | ||
0d160211 JF |
1635 | config XEN_NETDEV_FRONTEND |
1636 | tristate "Xen network device frontend driver" | |
1637 | depends on XEN | |
7003087c | 1638 | select XEN_XENBUS_FRONTEND |
0d160211 JF |
1639 | default y |
1640 | help | |
f942dc25 IC |
1641 | This driver provides support for Xen paravirtual network |
1642 | devices exported by a Xen network driver domain (often | |
1643 | domain 0). | |
1644 | ||
1645 | The corresponding Linux backend driver is enabled by the | |
1646 | CONFIG_XEN_NETDEV_BACKEND option. | |
1647 | ||
1648 | If you are compiling a kernel for use as Xen guest, you | |
1649 | should say Y here. To compile this driver as a module, chose | |
1650 | M here: the module will be called xen-netfront. | |
1651 | ||
1652 | config XEN_NETDEV_BACKEND | |
1653 | tristate "Xen backend network device" | |
1654 | depends on XEN_BACKEND | |
1655 | help | |
1656 | This driver allows the kernel to act as a Xen network driver | |
1657 | domain which exports paravirtual network devices to other | |
1658 | Xen domains. These devices can be accessed by any operating | |
1659 | system that implements a compatible front end. | |
1660 | ||
1661 | The corresponding Linux frontend driver is enabled by the | |
1662 | CONFIG_XEN_NETDEV_FRONTEND configuration option. | |
1663 | ||
1664 | The backend driver presents a standard network device | |
1665 | endpoint for each paravirtual network device to the driver | |
1666 | domain network stack. These can then be bridged or routed | |
1667 | etc in order to provide full network connectivity. | |
1668 | ||
1669 | If you are compiling a kernel to run in a Xen network driver | |
1670 | domain (often this is domain 0) you should say Y here. To | |
1671 | compile this driver as a module, chose M here: the module | |
1672 | will be called xen-netback. | |
0d160211 | 1673 | |
1da177e4 LT |
1674 | config ISERIES_VETH |
1675 | tristate "iSeries Virtual Ethernet driver support" | |
cbcd2a4c | 1676 | depends on PPC_ISERIES |
1da177e4 | 1677 | |
f89efd52 MP |
1678 | config RIONET |
1679 | tristate "RapidIO Ethernet over messaging driver support" | |
a81c52a8 | 1680 | depends on RAPIDIO |
f89efd52 MP |
1681 | |
1682 | config RIONET_TX_SIZE | |
1683 | int "Number of outbound queue entries" | |
1684 | depends on RIONET | |
1685 | default "128" | |
1686 | ||
1687 | config RIONET_RX_SIZE | |
1688 | int "Number of inbound queue entries" | |
1689 | depends on RIONET | |
1690 | default "128" | |
1691 | ||
1da177e4 | 1692 | config FDDI |
eb56092f | 1693 | tristate "FDDI driver support" |
e89a2cfb | 1694 | depends on (PCI || EISA || TC) |
1da177e4 LT |
1695 | help |
1696 | Fiber Distributed Data Interface is a high speed local area network | |
1697 | design; essentially a replacement for high speed Ethernet. FDDI can | |
1698 | run over copper or fiber. If you are connected to such a network and | |
1699 | want a driver for the FDDI card in your computer, say Y here (and | |
1700 | then also Y to the driver for your FDDI card, below). Most people | |
1701 | will say N. | |
1702 | ||
1703 | config DEFXX | |
e89a2cfb MR |
1704 | tristate "Digital DEFTA/DEFEA/DEFPA adapter support" |
1705 | depends on FDDI && (PCI || EISA || TC) | |
1706 | ---help--- | |
1707 | This is support for the DIGITAL series of TURBOchannel (DEFTA), | |
1708 | EISA (DEFEA) and PCI (DEFPA) controllers which can connect you | |
1709 | to a local FDDI network. | |
1710 | ||
1711 | To compile this driver as a module, choose M here: the module | |
1712 | will be called defxx. If unsure, say N. | |
1713 | ||
1714 | config DEFXX_MMIO | |
1715 | bool | |
1716 | prompt "Use MMIO instead of PIO" if PCI || EISA | |
1717 | depends on DEFXX | |
1718 | default n if PCI || EISA | |
1719 | default y | |
1720 | ---help--- | |
1721 | This instructs the driver to use EISA or PCI memory-mapped I/O | |
1722 | (MMIO) as appropriate instead of programmed I/O ports (PIO). | |
1723 | Enabling this gives an improvement in processing time in parts | |
1724 | of the driver, but it may cause problems with EISA (DEFEA) | |
1725 | adapters. TURBOchannel does not have the concept of I/O ports, | |
1726 | so MMIO is always used for these (DEFTA) adapters. | |
1727 | ||
1728 | If unsure, say N. | |
1da177e4 LT |
1729 | |
1730 | config SKFP | |
1731 | tristate "SysKonnect FDDI PCI support" | |
1732 | depends on FDDI && PCI | |
bc63eb9c | 1733 | select BITREVERSE |
1da177e4 LT |
1734 | ---help--- |
1735 | Say Y here if you have a SysKonnect FDDI PCI adapter. | |
1736 | The following adapters are supported by this driver: | |
1737 | - SK-5521 (SK-NET FDDI-UP) | |
1738 | - SK-5522 (SK-NET FDDI-UP DAS) | |
1739 | - SK-5541 (SK-NET FDDI-FP) | |
1740 | - SK-5543 (SK-NET FDDI-LP) | |
1741 | - SK-5544 (SK-NET FDDI-LP DAS) | |
1742 | - SK-5821 (SK-NET FDDI-UP64) | |
1743 | - SK-5822 (SK-NET FDDI-UP64 DAS) | |
1744 | - SK-5841 (SK-NET FDDI-FP64) | |
1745 | - SK-5843 (SK-NET FDDI-LP64) | |
1746 | - SK-5844 (SK-NET FDDI-LP64 DAS) | |
1747 | - Netelligent 100 FDDI DAS Fibre SC | |
1748 | - Netelligent 100 FDDI SAS Fibre SC | |
1749 | - Netelligent 100 FDDI DAS UTP | |
1750 | - Netelligent 100 FDDI SAS UTP | |
1751 | - Netelligent 100 FDDI SAS Fibre MIC | |
1752 | ||
1753 | Read <file:Documentation/networking/skfp.txt> for information about | |
1754 | the driver. | |
1755 | ||
1756 | Questions concerning this driver can be addressed to: | |
1757 | <linux@syskonnect.de> | |
1758 | ||
1759 | To compile this driver as a module, choose M here: the module | |
1760 | will be called skfp. This is recommended. | |
1761 | ||
1762 | config HIPPI | |
1763 | bool "HIPPI driver support (EXPERIMENTAL)" | |
cbcd2a4c | 1764 | depends on EXPERIMENTAL && INET && PCI |
1da177e4 LT |
1765 | help |
1766 | HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and | |
1767 | 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI | |
1768 | can run over copper (25m) or fiber (300m on multi-mode or 10km on | |
1769 | single-mode). HIPPI networks are commonly used for clusters and to | |
1770 | connect to super computers. If you are connected to a HIPPI network | |
1771 | and have a HIPPI network card in your computer that you want to use | |
1772 | under Linux, say Y here (you must also remember to enable the driver | |
1773 | for your HIPPI card below). Most people will say N here. | |
1774 | ||
1775 | config ROADRUNNER | |
1776 | tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" | |
1777 | depends on HIPPI && PCI | |
1778 | help | |
1779 | Say Y here if this is your PCI HIPPI network card. | |
1780 | ||
1781 | To compile this driver as a module, choose M here: the module | |
1782 | will be called rrunner. If unsure, say N. | |
1783 | ||
1784 | config ROADRUNNER_LARGE_RINGS | |
1785 | bool "Use large TX/RX rings (EXPERIMENTAL)" | |
1786 | depends on ROADRUNNER | |
1787 | help | |
1788 | If you say Y here, the RoadRunner driver will preallocate up to 2 MB | |
1789 | of additional memory to allow for fastest operation, both for | |
1790 | transmitting and receiving. This memory cannot be used by any other | |
1791 | kernel code or by user space programs. Say Y here only if you have | |
1792 | the memory. | |
1793 | ||
1794 | config PLIP | |
1795 | tristate "PLIP (parallel port) support" | |
cbcd2a4c | 1796 | depends on PARPORT |
1da177e4 LT |
1797 | ---help--- |
1798 | PLIP (Parallel Line Internet Protocol) is used to create a | |
1799 | reasonably fast mini network consisting of two (or, rarely, more) | |
1800 | local machines. A PLIP link from a Linux box is a popular means to | |
1801 | install a Linux distribution on a machine which doesn't have a | |
1802 | CD-ROM drive (a minimal system has to be transferred with floppies | |
1803 | first). The kernels on both machines need to have this PLIP option | |
1804 | enabled for this to work. | |
1805 | ||
1806 | The PLIP driver has two modes, mode 0 and mode 1. The parallel | |
1807 | ports (the connectors at the computers with 25 holes) are connected | |
1808 | with "null printer" or "Turbo Laplink" cables which can transmit 4 | |
1809 | bits at a time (mode 0) or with special PLIP cables, to be used on | |
1810 | bidirectional parallel ports only, which can transmit 8 bits at a | |
1811 | time (mode 1); you can find the wiring of these cables in | |
1812 | <file:Documentation/networking/PLIP.txt>. The cables can be up to | |
1813 | 15m long. Mode 0 works also if one of the machines runs DOS/Windows | |
1814 | and has some PLIP software installed, e.g. the Crynwr PLIP packet | |
1815 | driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) | |
1816 | and winsock or NCSA's telnet. | |
1817 | ||
1818 | If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well | |
1819 | as the NET-3-HOWTO, both available from | |
1820 | <http://www.tldp.org/docs.html#howto>. Note that the PLIP | |
1821 | protocol has been changed and this PLIP driver won't work together | |
1822 | with the PLIP support in Linux versions 1.0.x. This option enlarges | |
1823 | your kernel by about 8 KB. | |
1824 | ||
57ce45dd AB |
1825 | To compile this driver as a module, choose M here. The module |
1826 | will be called plip. If unsure, say Y or M, in case you buy | |
1827 | a laptop later. | |
1da177e4 LT |
1828 | |
1829 | config PPP | |
1830 | tristate "PPP (point-to-point protocol) support" | |
b6e37e55 | 1831 | select SLHC |
1da177e4 LT |
1832 | ---help--- |
1833 | PPP (Point to Point Protocol) is a newer and better SLIP. It serves | |
1834 | the same purpose: sending Internet traffic over telephone (and other | |
1835 | serial) lines. Ask your access provider if they support it, because | |
1836 | otherwise you can't use it; most Internet access providers these | |
1837 | days support PPP rather than SLIP. | |
1838 | ||
1839 | To use PPP, you need an additional program called pppd as described | |
1840 | in the PPP-HOWTO, available at | |
1841 | <http://www.tldp.org/docs.html#howto>. Make sure that you have | |
1842 | the version of pppd recommended in <file:Documentation/Changes>. | |
1843 | The PPP option enlarges your kernel by about 16 KB. | |
1844 | ||
1845 | There are actually two versions of PPP: the traditional PPP for | |
1846 | asynchronous lines, such as regular analog phone lines, and | |
1847 | synchronous PPP which can be used over digital ISDN lines for | |
1848 | example. If you want to use PPP over phone lines or other | |
1849 | asynchronous serial lines, you need to say Y (or M) here and also to | |
1850 | the next option, "PPP support for async serial ports". For PPP over | |
1851 | synchronous lines, you should say Y (or M) here and to "Support | |
1852 | synchronous PPP", below. | |
1853 | ||
1854 | If you said Y to "Version information on all symbols" above, then | |
1855 | you cannot compile the PPP driver into the kernel; you can then only | |
1856 | compile it as a module. To compile this driver as a module, choose M | |
57ce45dd | 1857 | here. The module will be called ppp_generic. |
1da177e4 LT |
1858 | |
1859 | config PPP_MULTILINK | |
1860 | bool "PPP multilink support (EXPERIMENTAL)" | |
1861 | depends on PPP && EXPERIMENTAL | |
1862 | help | |
1863 | PPP multilink is a protocol (defined in RFC 1990) which allows you | |
1864 | to combine several (logical or physical) lines into one logical PPP | |
1865 | connection, so that you can utilize your full bandwidth. | |
1866 | ||
1867 | This has to be supported at the other end as well and you need a | |
1868 | version of the pppd daemon which understands the multilink protocol. | |
1869 | ||
1870 | If unsure, say N. | |
1871 | ||
1872 | config PPP_FILTER | |
1873 | bool "PPP filtering" | |
1874 | depends on PPP | |
1875 | help | |
1876 | Say Y here if you want to be able to filter the packets passing over | |
1877 | PPP interfaces. This allows you to control which packets count as | |
1878 | activity (i.e. which packets will reset the idle timer or bring up | |
47c51431 | 1879 | a demand-dialed link) and which packets are to be dropped entirely. |
1da177e4 LT |
1880 | You need to say Y here if you wish to use the pass-filter and |
1881 | active-filter options to pppd. | |
1882 | ||
1883 | If unsure, say N. | |
1884 | ||
1885 | config PPP_ASYNC | |
1886 | tristate "PPP support for async serial ports" | |
1887 | depends on PPP | |
1888 | select CRC_CCITT | |
1889 | ---help--- | |
1890 | Say Y (or M) here if you want to be able to use PPP over standard | |
1891 | asynchronous serial ports, such as COM1 or COM2 on a PC. If you use | |
1892 | a modem (not a synchronous or ISDN modem) to contact your ISP, you | |
1893 | need this option. | |
1894 | ||
1895 | To compile this driver as a module, choose M here. | |
1896 | ||
1897 | If unsure, say Y. | |
1898 | ||
1899 | config PPP_SYNC_TTY | |
1900 | tristate "PPP support for sync tty ports" | |
1901 | depends on PPP | |
1902 | help | |
1903 | Say Y (or M) here if you want to be able to use PPP over synchronous | |
1904 | (HDLC) tty devices, such as the SyncLink adapter. These devices | |
1905 | are often used for high-speed leased lines like T1/E1. | |
1906 | ||
1907 | To compile this driver as a module, choose M here. | |
1908 | ||
1909 | config PPP_DEFLATE | |
1910 | tristate "PPP Deflate compression" | |
1911 | depends on PPP | |
1912 | select ZLIB_INFLATE | |
1913 | select ZLIB_DEFLATE | |
1914 | ---help--- | |
1915 | Support for the Deflate compression method for PPP, which uses the | |
1916 | Deflate algorithm (the same algorithm that gzip uses) to compress | |
1917 | each PPP packet before it is sent over the wire. The machine at the | |
1918 | other end of the PPP link (usually your ISP) has to support the | |
1919 | Deflate compression method as well for this to be useful. Even if | |
1920 | they don't support it, it is safe to say Y here. | |
1921 | ||
1922 | To compile this driver as a module, choose M here. | |
1923 | ||
1924 | config PPP_BSDCOMP | |
1925 | tristate "PPP BSD-Compress compression" | |
1926 | depends on PPP | |
1927 | ---help--- | |
1928 | Support for the BSD-Compress compression method for PPP, which uses | |
1929 | the LZW compression method to compress each PPP packet before it is | |
1930 | sent over the wire. The machine at the other end of the PPP link | |
1931 | (usually your ISP) has to support the BSD-Compress compression | |
1932 | method as well for this to be useful. Even if they don't support it, | |
1933 | it is safe to say Y here. | |
1934 | ||
1935 | The PPP Deflate compression method ("PPP Deflate compression", | |
1936 | above) is preferable to BSD-Compress, because it compresses better | |
1937 | and is patent-free. | |
1938 | ||
1939 | Note that the BSD compression code will always be compiled as a | |
1940 | module; it is called bsd_comp and will show up in the directory | |
1941 | modules once you have said "make modules". If unsure, say N. | |
1942 | ||
b3f9b92a | 1943 | config PPP_MPPE |
e85eb117 PDM |
1944 | tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" |
1945 | depends on PPP && EXPERIMENTAL | |
1946 | select CRYPTO | |
1947 | select CRYPTO_SHA1 | |
1948 | select CRYPTO_ARC4 | |
1949 | select CRYPTO_ECB | |
1950 | ---help--- | |
1951 | Support for the MPPE Encryption protocol, as employed by the | |
1952 | Microsoft Point-to-Point Tunneling Protocol. | |
1953 | ||
1954 | See http://pptpclient.sourceforge.net/ for information on | |
1955 | configuring PPTP clients and servers to utilize this method. | |
b3f9b92a | 1956 | |
1da177e4 LT |
1957 | config PPPOE |
1958 | tristate "PPP over Ethernet (EXPERIMENTAL)" | |
1959 | depends on EXPERIMENTAL && PPP | |
1960 | help | |
1961 | Support for PPP over Ethernet. | |
1962 | ||
1963 | This driver requires the latest version of pppd from the CVS | |
1964 | repository at cvs.samba.org. Alternatively, see the | |
1965 | RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) | |
1966 | which contains instruction on how to use this driver (under | |
1967 | the heading "Kernel mode PPPoE"). | |
1968 | ||
00959ade DK |
1969 | config PPTP |
1970 | tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" | |
1971 | depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX | |
1972 | help | |
1973 | Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) | |
1974 | ||
1975 | This driver requires pppd plugin to work in client mode or | |
1976 | modified pptpd (poptop) to work in server mode. | |
1977 | See http://accel-pptp.sourceforge.net/ for information how to | |
1978 | utilize this module. | |
1979 | ||
1da177e4 LT |
1980 | config PPPOATM |
1981 | tristate "PPP over ATM" | |
1982 | depends on ATM && PPP | |
1983 | help | |
1984 | Support PPP (Point to Point Protocol) encapsulated in ATM frames. | |
1985 | This implementation does not yet comply with section 8 of RFC2364, | |
1986 | which can lead to bad results if the ATM peer loses state and | |
1987 | changes its encapsulation unilaterally. | |
1988 | ||
3557baab JC |
1989 | config PPPOL2TP |
1990 | tristate "PPP over L2TP (EXPERIMENTAL)" | |
fd558d18 | 1991 | depends on EXPERIMENTAL && L2TP && PPP |
3557baab JC |
1992 | help |
1993 | Support for PPP-over-L2TP socket family. L2TP is a protocol | |
1994 | used by ISPs and enterprises to tunnel PPP traffic over UDP | |
1995 | tunnels. L2TP is replacing PPTP for VPN uses. | |
1996 | ||
1da177e4 LT |
1997 | config SLIP |
1998 | tristate "SLIP (serial line) support" | |
1da177e4 LT |
1999 | ---help--- |
2000 | Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to | |
2001 | connect to your Internet service provider or to connect to some | |
2002 | other local Unix box or if you want to configure your Linux box as a | |
2003 | Slip/CSlip server for other people to dial in. SLIP (Serial Line | |
2004 | Internet Protocol) is a protocol used to send Internet traffic over | |
2005 | serial connections such as telephone lines or null modem cables; | |
2006 | nowadays, the protocol PPP is more commonly used for this same | |
2007 | purpose. | |
2008 | ||
2009 | Normally, your access provider has to support SLIP in order for you | |
2010 | to be able to use it, but there is now a SLIP emulator called SLiRP | |
2011 | around (available from | |
2012 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
2013 | allows you to use SLIP over a regular dial up shell connection. If | |
2014 | you plan to use SLiRP, make sure to say Y to CSLIP, below. The | |
2015 | NET-3-HOWTO, available from | |
2016 | <http://www.tldp.org/docs.html#howto>, explains how to | |
2017 | configure SLIP. Note that you don't need this option if you just | |
2018 | want to run term (term is a program which gives you almost full | |
2019 | Internet connectivity if you have a regular dial up shell account on | |
2020 | some Internet connected Unix computer. Read | |
2021 | <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP | |
2022 | support will enlarge your kernel by about 4 KB. If unsure, say N. | |
2023 | ||
57ce45dd AB |
2024 | To compile this driver as a module, choose M here. The module |
2025 | will be called slip. | |
1da177e4 LT |
2026 | |
2027 | config SLIP_COMPRESSED | |
2028 | bool "CSLIP compressed headers" | |
2029 | depends on SLIP | |
b6e37e55 | 2030 | select SLHC |
1da177e4 LT |
2031 | ---help--- |
2032 | This protocol is faster than SLIP because it uses compression on the | |
2033 | TCP/IP headers (not on the data itself), but it has to be supported | |
2034 | on both ends. Ask your access provider if you are not sure and | |
2035 | answer Y, just in case. You will still be able to use plain SLIP. If | |
2036 | you plan to use SLiRP, the SLIP emulator (available from | |
2037 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
2038 | allows you to use SLIP over a regular dial up shell connection, you | |
2039 | definitely want to say Y here. The NET-3-HOWTO, available from | |
2040 | <http://www.tldp.org/docs.html#howto>, explains how to configure | |
2041 | CSLIP. This won't enlarge your kernel. | |
2042 | ||
b6e37e55 RB |
2043 | config SLHC |
2044 | tristate | |
2045 | help | |
2046 | This option enables Van Jacobsen serial line header compression | |
2047 | routines. | |
2048 | ||
1da177e4 LT |
2049 | config SLIP_SMART |
2050 | bool "Keepalive and linefill" | |
2051 | depends on SLIP | |
2052 | help | |
2053 | Adds additional capabilities to the SLIP driver to support the | |
2054 | RELCOM line fill and keepalive monitoring. Ideal on poor quality | |
2055 | analogue lines. | |
2056 | ||
2057 | config SLIP_MODE_SLIP6 | |
2058 | bool "Six bit SLIP encapsulation" | |
2059 | depends on SLIP | |
2060 | help | |
2061 | Just occasionally you may need to run IP over hostile serial | |
2062 | networks that don't pass all control characters or are only seven | |
2063 | bit. Saying Y here adds an extra mode you can use with SLIP: | |
2064 | "slip6". In this mode, SLIP will only send normal ASCII symbols over | |
2065 | the serial device. Naturally, this has to be supported at the other | |
2066 | end of the link as well. It's good enough, for example, to run IP | |
2067 | over the async ports of a Camtec JNT Pad. If unsure, say N. | |
2068 | ||
2069 | config NET_FC | |
2070 | bool "Fibre Channel driver support" | |
cbcd2a4c | 2071 | depends on SCSI && PCI |
1da177e4 LT |
2072 | help |
2073 | Fibre Channel is a high speed serial protocol mainly used to connect | |
2074 | large storage devices to the computer; it is compatible with and | |
2075 | intended to replace SCSI. | |
2076 | ||
2077 | If you intend to use Fibre Channel, you need to have a Fibre channel | |
2078 | adaptor card in your computer; say Y here and to the driver for your | |
2079 | adaptor below. You also should have said Y to "SCSI support" and | |
2080 | "SCSI generic support". | |
2081 | ||
1da177e4 | 2082 | config NETCONSOLE |
ecbacf8d | 2083 | tristate "Network console logging support" |
1da177e4 LT |
2084 | ---help--- |
2085 | If you want to log kernel messages over the network, enable this. | |
2086 | See <file:Documentation/networking/netconsole.txt> for details. | |
2087 | ||
0bcc1816 | 2088 | config NETCONSOLE_DYNAMIC |
ecbacf8d | 2089 | bool "Dynamic reconfiguration of logging targets" |
58fa4597 RD |
2090 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ |
2091 | !(NETCONSOLE=y && CONFIGFS_FS=m) | |
0bcc1816 SS |
2092 | help |
2093 | This option enables the ability to dynamically reconfigure target | |
2094 | parameters (interface, IP addresses, port numbers, MAC addresses) | |
2095 | at runtime through a userspace interface exported using configfs. | |
2096 | See <file:Documentation/networking/netconsole.txt> for details. | |
2097 | ||
54208991 RD |
2098 | config NETPOLL |
2099 | def_bool NETCONSOLE | |
2100 | ||
54208991 RD |
2101 | config NETPOLL_TRAP |
2102 | bool "Netpoll traffic trapping" | |
2103 | default n | |
2104 | depends on NETPOLL | |
2105 | ||
2106 | config NET_POLL_CONTROLLER | |
2107 | def_bool NETPOLL | |
2108 | ||
296f96fc RR |
2109 | config VIRTIO_NET |
2110 | tristate "Virtio network driver (EXPERIMENTAL)" | |
2111 | depends on EXPERIMENTAL && VIRTIO | |
2112 | ---help--- | |
0ad07ec1 | 2113 | This is the virtual network driver for virtio. It can be used with |
e85eb117 | 2114 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. |
296f96fc | 2115 | |
d1a890fa | 2116 | config VMXNET3 |
e85eb117 PDM |
2117 | tristate "VMware VMXNET3 ethernet driver" |
2118 | depends on PCI && INET | |
2119 | help | |
2120 | This driver supports VMware's vmxnet3 virtual ethernet NIC. | |
2121 | To compile this driver as a module, choose M here: the | |
2122 | module will be called vmxnet3. | |
d1a890fa | 2123 | |
d1c0a65f | 2124 | endif # NETDEVICES |