]>
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 | ||
ef11291b FF |
240 | config KORINA |
241 | tristate "Korina (IDT RC32434) Ethernet support" | |
f57b2061 | 242 | depends on NET_ETHERNET && MIKROTIK_RB532 |
ef11291b FF |
243 | help |
244 | If you have a Mikrotik RouterBoard 500 or IDT RC32434 | |
245 | based system say Y. Otherwise say N. | |
246 | ||
1da177e4 LT |
247 | config SGI_IOC3_ETH |
248 | bool "SGI IOC3 Ethernet" | |
d1c0a65f | 249 | depends on PCI && SGI_IP27 |
1da177e4 LT |
250 | select CRC32 |
251 | select MII | |
252 | help | |
253 | If you have a network (Ethernet) card of this type, say Y and read | |
254 | the Ethernet-HOWTO, available from | |
255 | <http://www.tldp.org/docs.html#howto>. | |
256 | ||
dcbf8477 | 257 | config MIPS_SIM_NET |
1e2b980f | 258 | tristate "MIPS simulator Network device" |
d1c0a65f | 259 | depends on MIPS_SIM |
dcbf8477 RB |
260 | help |
261 | The MIPSNET device is a simple Ethernet network device which is | |
262 | emulated by the MIPS Simulator. | |
263 | If you are not using a MIPSsim or are unsure, say N. | |
264 | ||
1da177e4 LT |
265 | config SGI_O2MACE_ETH |
266 | tristate "SGI O2 MACE Fast Ethernet support" | |
d1c0a65f | 267 | depends on SGI_IP32=y |
1da177e4 | 268 | |
86a74ff2 NI |
269 | config SH_ETH |
270 | tristate "Renesas SuperH Ethernet support" | |
271 | depends on SUPERH && \ | |
65ac8851 YS |
272 | (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ |
273 | CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ | |
f29a3d04 | 274 | CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757) |
86a74ff2 NI |
275 | select CRC32 |
276 | select MII | |
277 | select MDIO_BITBANG | |
278 | select PHYLIB | |
279 | help | |
280 | Renesas SuperH Ethernet device driver. | |
f29a3d04 YS |
281 | This driver supporting CPUs are: |
282 | - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757. | |
86a74ff2 | 283 | |
e190d6b1 | 284 | config BFIN_MAC |
736783b8 | 285 | tristate "Blackfin on-chip MAC support" |
33a2a2b4 | 286 | depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) |
e190d6b1 | 287 | select CRC32 |
eeb70af9 BW |
288 | select MII |
289 | select PHYLIB | |
e190d6b1 BW |
290 | select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE |
291 | help | |
736783b8 | 292 | This is the driver for Blackfin on-chip mac device. Say Y if you want it |
e190d6b1 BW |
293 | compiled into the kernel. This driver is also available as a module |
294 | ( = code which can be inserted in and removed from the running kernel | |
295 | whenever you want). The module will be called bfin_mac. | |
296 | ||
297 | config BFIN_MAC_USE_L1 | |
298 | bool "Use L1 memory for rx/tx packets" | |
6893ff1c | 299 | depends on BFIN_MAC && (BF527 || BF537) |
e190d6b1 BW |
300 | default y |
301 | help | |
01dd2fbf | 302 | To get maximum network performance, you should use L1 memory as rx/tx buffers. |
e190d6b1 BW |
303 | Say N here if you want to reserve L1 memory for other uses. |
304 | ||
305 | config BFIN_TX_DESC_NUM | |
306 | int "Number of transmit buffer packets" | |
307 | depends on BFIN_MAC | |
308 | range 6 10 if BFIN_MAC_USE_L1 | |
309 | range 10 100 | |
310 | default "10" | |
311 | help | |
312 | Set the number of buffer packets used in driver. | |
313 | ||
314 | config BFIN_RX_DESC_NUM | |
315 | int "Number of receive buffer packets" | |
316 | depends on BFIN_MAC | |
317 | range 20 100 if BFIN_MAC_USE_L1 | |
318 | range 20 800 | |
319 | default "20" | |
320 | help | |
321 | Set the number of buffer packets used in driver. | |
322 | ||
fe92afed BS |
323 | config BFIN_MAC_USE_HWSTAMP |
324 | bool "Use IEEE 1588 hwstamp" | |
325 | depends on BFIN_MAC && BF518 | |
326 | default y | |
327 | help | |
328 | To support the IEEE 1588 Precision Time Protocol (PTP), select y here | |
329 | ||
a49f37ee SS |
330 | config PXA168_ETH |
331 | tristate "Marvell pxa168 ethernet support" | |
332 | depends on CPU_PXA168 | |
333 | select PHYLIB | |
334 | help | |
335 | This driver supports the pxa168 Ethernet ports. | |
336 | ||
337 | To compile this driver as a module, choose M here. The module | |
338 | will be called pxa168_eth. | |
339 | ||
92aa674d SH |
340 | config NET_NETX |
341 | tristate "NetX Ethernet support" | |
342 | select MII | |
d1c0a65f | 343 | depends on ARCH_NETX |
92aa674d SH |
344 | help |
345 | This is support for the Hilscher netX builtin Ethernet ports | |
346 | ||
57ce45dd | 347 | To compile this driver as a module, choose M here. The module |
92aa674d SH |
348 | will be called netx-eth. |
349 | ||
a6286ee6 AG |
350 | config TI_DAVINCI_EMAC |
351 | tristate "TI DaVinci EMAC Support" | |
8ee2bf9a | 352 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) |
5d69e007 | 353 | select TI_DAVINCI_MDIO |
ef8c2dab | 354 | select TI_DAVINCI_CPDMA |
a6286ee6 AG |
355 | select PHYLIB |
356 | help | |
357 | This driver supports TI's DaVinci Ethernet . | |
358 | ||
359 | To compile this driver as a module, choose M here: the module | |
360 | will be called davinci_emac_driver. This is recommended. | |
361 | ||
f20136eb CC |
362 | config TI_DAVINCI_MDIO |
363 | tristate "TI DaVinci MDIO Support" | |
364 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) | |
365 | select PHYLIB | |
366 | help | |
367 | This driver supports TI's DaVinci MDIO module. | |
368 | ||
369 | To compile this driver as a module, choose M here: the module | |
370 | will be called davinci_mdio. This is recommended. | |
371 | ||
ef8c2dab CC |
372 | config TI_DAVINCI_CPDMA |
373 | tristate "TI DaVinci CPDMA Support" | |
374 | depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) | |
375 | help | |
376 | This driver supports TI's DaVinci CPDMA dma engine. | |
377 | ||
378 | To compile this driver as a module, choose M here: the module | |
379 | will be called davinci_cpdma. This is recommended. | |
380 | ||
a1365275 SH |
381 | config DM9000 |
382 | tristate "DM9000 support" | |
f40d24d9 | 383 | depends on ARM || BLACKFIN || MIPS |
a1365275 SH |
384 | select CRC32 |
385 | select MII | |
386 | ---help--- | |
387 | Support for DM9000 chipset. | |
388 | ||
57ce45dd AB |
389 | To compile this driver as a module, choose M here. The module |
390 | will be called dm9000. | |
a1365275 | 391 | |
485ca22a BD |
392 | config DM9000_DEBUGLEVEL |
393 | int "DM9000 maximum debug level" | |
394 | depends on DM9000 | |
395 | default 4 | |
396 | help | |
397 | The maximum level of debugging code compiled into the DM9000 | |
398 | driver. | |
399 | ||
f8dd0ecb BD |
400 | config DM9000_FORCE_SIMPLE_PHY_POLL |
401 | bool "Force simple NSR based PHY polling" | |
402 | depends on DM9000 | |
403 | ---help--- | |
404 | This configuration forces the DM9000 to use the NSR's LinkStatus | |
405 | bit to determine if the link is up or down instead of the more | |
406 | costly MII PHY reads. Note, this will not work if the chip is | |
407 | operating with an external PHY. | |
408 | ||
3ec9c11d CL |
409 | config ENC28J60 |
410 | tristate "ENC28J60 support" | |
411 | depends on EXPERIMENTAL && SPI && NET_ETHERNET | |
412 | select CRC32 | |
413 | ---help--- | |
414 | Support for the Microchip EN28J60 ethernet chip. | |
415 | ||
2bfc79de | 416 | To compile this driver as a module, choose M here. The module will be |
3ec9c11d CL |
417 | called enc28j60. |
418 | ||
419 | config ENC28J60_WRITEVERIFY | |
420 | bool "Enable write verify" | |
421 | depends on ENC28J60 | |
422 | ---help--- | |
423 | Enable the verify after the buffer write useful for debugging purpose. | |
424 | If unsure, say N. | |
425 | ||
a1702857 TR |
426 | config ETHOC |
427 | tristate "OpenCores 10/100 Mbps Ethernet MAC support" | |
0ebe74e7 | 428 | depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA |
a1702857 TR |
429 | select MII |
430 | select PHYLIB | |
c5cacb3b RD |
431 | select CRC32 |
432 | select BITREVERSE | |
a1702857 TR |
433 | help |
434 | Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. | |
435 | ||
d4c41139 KG |
436 | config GRETH |
437 | tristate "Aeroflex Gaisler GRETH Ethernet MAC support" | |
cf261b23 | 438 | depends on SPARC |
d4c41139 KG |
439 | select PHYLIB |
440 | select CRC32 | |
441 | help | |
442 | Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. | |
443 | ||
47964174 IY |
444 | config DNET |
445 | tristate "Dave ethernet support (DNET)" | |
4b97926d | 446 | depends on NET_ETHERNET && HAS_IOMEM |
47964174 IY |
447 | select PHYLIB |
448 | help | |
449 | The Dave ethernet interface (DNET) is found on Qong Board FPGA. | |
450 | Say Y to include support for the DNET chip. | |
451 | ||
452 | To compile this driver as a module, choose M here: the module | |
453 | will be called dnet. | |
454 | ||
1da177e4 LT |
455 | source "drivers/net/tulip/Kconfig" |
456 | ||
457 | config AT1700 | |
458 | tristate "AT1700/1720 support (EXPERIMENTAL)" | |
d1c0a65f | 459 | depends on (ISA || MCA_LEGACY) && EXPERIMENTAL |
1da177e4 LT |
460 | select CRC32 |
461 | ---help--- | |
462 | If you have a network (Ethernet) card of this type, say Y and read | |
463 | the Ethernet-HOWTO, available from | |
464 | <http://www.tldp.org/docs.html#howto>. | |
465 | ||
57ce45dd | 466 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
467 | will be called at1700. |
468 | ||
1da177e4 LT |
469 | config HP100 |
470 | tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" | |
d1c0a65f | 471 | depends on ISA || EISA || PCI |
1da177e4 LT |
472 | help |
473 | If you have a network (Ethernet) card of this type, say Y and read | |
474 | the Ethernet-HOWTO, available from | |
475 | <http://www.tldp.org/docs.html#howto>. | |
476 | ||
57ce45dd | 477 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
478 | will be called hp100. |
479 | ||
480 | config NET_ISA | |
481 | bool "Other ISA cards" | |
d1c0a65f | 482 | depends on ISA |
1da177e4 LT |
483 | ---help--- |
484 | If your network (Ethernet) card hasn't been mentioned yet and its | |
485 | bus system (that's the way the cards talks to the other components | |
486 | of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. | |
487 | Make sure you know the name of your card. Read the Ethernet-HOWTO, | |
488 | available from <http://www.tldp.org/docs.html#howto>. | |
489 | ||
490 | If unsure, say Y. | |
491 | ||
492 | Note that the answer to this question doesn't directly affect the | |
493 | kernel: saying N will just cause the configurator to skip all | |
494 | the remaining ISA network card questions. If you say Y, you will be | |
495 | asked for your specific card in the following questions. | |
496 | ||
1da177e4 LT |
497 | config EWRK3 |
498 | tristate "EtherWORKS 3 (DE203, DE204, DE205) support" | |
499 | depends on NET_ISA | |
500 | select CRC32 | |
501 | ---help--- | |
502 | This driver supports the DE203, DE204 and DE205 network (Ethernet) | |
503 | cards. If this is for you, say Y and read | |
504 | <file:Documentation/networking/ewrk3.txt> in the kernel source as | |
505 | well as the Ethernet-HOWTO, available from | |
506 | <http://www.tldp.org/docs.html#howto>. | |
507 | ||
57ce45dd | 508 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
509 | will be called ewrk3. |
510 | ||
1da177e4 LT |
511 | config ETH16I |
512 | tristate "ICL EtherTeam 16i/32 support" | |
513 | depends on NET_ISA | |
514 | help | |
515 | If you have a network (Ethernet) card of this type, say Y and read | |
516 | the Ethernet-HOWTO, available from | |
517 | <http://www.tldp.org/docs.html#howto>. | |
518 | ||
57ce45dd | 519 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
520 | will be called eth16i. |
521 | ||
1da177e4 LT |
522 | config SEEQ8005 |
523 | tristate "SEEQ8005 support (EXPERIMENTAL)" | |
524 | depends on NET_ISA && EXPERIMENTAL | |
525 | help | |
526 | This is a driver for the SEEQ 8005 network (Ethernet) card. If this | |
527 | is for you, read the Ethernet-HOWTO, available from | |
528 | <http://www.tldp.org/docs.html#howto>. | |
529 | ||
57ce45dd | 530 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
531 | will be called seeq8005. |
532 | ||
1da177e4 LT |
533 | config NET_PCI |
534 | bool "EISA, VLB, PCI and on board controllers" | |
d1c0a65f | 535 | depends on ISA || EISA || PCI |
1da177e4 LT |
536 | help |
537 | This is another class of network cards which attach directly to the | |
538 | bus. If you have one of those, say Y and read the Ethernet-HOWTO, | |
539 | available from <http://www.tldp.org/docs.html#howto>. | |
540 | ||
541 | Note that the answer to this question doesn't directly affect the | |
542 | kernel: saying N will just cause the configurator to skip all | |
543 | the questions about this class of network cards. If you say Y, you | |
544 | will be asked for your specific card in the following questions. If | |
545 | you are unsure, say Y. | |
546 | ||
1da177e4 LT |
547 | config ADAPTEC_STARFIRE |
548 | tristate "Adaptec Starfire/DuraLAN support" | |
549 | depends on NET_PCI && PCI | |
550 | select CRC32 | |
551 | select MII | |
552 | help | |
553 | Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network | |
554 | adapter. The DuraLAN chip is used on the 64 bit PCI boards from | |
555 | Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip | |
556 | driver. | |
557 | ||
558 | To compile this driver as a module, choose M here: the module | |
559 | will be called starfire. This is recommended. | |
560 | ||
1eb1cc7a TH |
561 | config KSZ884X_PCI |
562 | tristate "Micrel KSZ8841/2 PCI" | |
563 | depends on NET_PCI && PCI | |
564 | select MII | |
565 | select CRC32 | |
566 | help | |
567 | This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. | |
568 | ||
569 | To compile this driver as a module, choose M here. The module | |
570 | will be called ksz884x. | |
571 | ||
1da177e4 | 572 | config FORCEDETH |
82770086 AB |
573 | tristate "nForce Ethernet support" |
574 | depends on NET_PCI && PCI | |
1da177e4 LT |
575 | help |
576 | If you have a network (Ethernet) controller of this type, say Y and | |
577 | read the Ethernet-HOWTO, available from | |
578 | <http://www.tldp.org/docs.html#howto>. | |
579 | ||
57ce45dd AB |
580 | To compile this driver as a module, choose M here. The module |
581 | will be called forcedeth. | |
1da177e4 | 582 | |
1da177e4 LT |
583 | config TC35815 |
584 | tristate "TOSHIBA TC35815 Ethernet support" | |
eea221ce | 585 | depends on NET_PCI && PCI && MIPS |
c6686fe3 | 586 | select PHYLIB |
1da177e4 | 587 | |
1da177e4 LT |
588 | config FEALNX |
589 | tristate "Myson MTD-8xx PCI Ethernet support" | |
590 | depends on NET_PCI && PCI | |
591 | select CRC32 | |
592 | select MII | |
593 | help | |
631dd1a8 JM |
594 | Say Y here to support the Myson MTD-800 family of PCI-based Ethernet |
595 | cards. <http://www.myson.com.tw/> | |
1da177e4 | 596 | |
7a47dd7a | 597 | config R6040 |
68334115 | 598 | tristate "RDC R6040 Fast Ethernet Adapter support" |
7a47dd7a SW |
599 | depends on NET_PCI && PCI |
600 | select CRC32 | |
601 | select MII | |
3831861b | 602 | select PHYLIB |
7a47dd7a SW |
603 | help |
604 | This is a driver for the R6040 Fast Ethernet MACs found in the | |
605 | the RDC R-321x System-on-chips. | |
606 | ||
607 | To compile this driver as a module, choose M here: the module | |
608 | will be called r6040. This is recommended. | |
609 | ||
1da177e4 LT |
610 | config SIS900 |
611 | tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" | |
612 | depends on NET_PCI && PCI | |
613 | select CRC32 | |
6da0f685 | 614 | select MII |
1da177e4 LT |
615 | ---help--- |
616 | This is a driver for the Fast Ethernet PCI network cards based on | |
617 | the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in | |
c3cf560e | 618 | SiS 630 and SiS 540 chipsets. |
1da177e4 LT |
619 | |
620 | This driver also supports AMD 79C901 HomePNA so that you can use | |
621 | your phone line as a network cable. | |
622 | ||
623 | To compile this driver as a module, choose M here: the module | |
624 | will be called sis900. This is recommended. | |
625 | ||
1da177e4 LT |
626 | config TLAN |
627 | tristate "TI ThunderLAN support" | |
93e16847 | 628 | depends on NET_PCI && (PCI || EISA) |
1da177e4 LT |
629 | ---help--- |
630 | If you have a PCI Ethernet network card based on the ThunderLAN chip | |
631 | which is supported by this driver, say Y and read the | |
632 | Ethernet-HOWTO, available from | |
633 | <http://www.tldp.org/docs.html#howto>. | |
634 | ||
635 | Devices currently supported by this driver are Compaq Netelligent, | |
636 | Compaq NetFlex and Olicom cards. Please read the file | |
637 | <file:Documentation/networking/tlan.txt> for more details. | |
638 | ||
57ce45dd | 639 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
640 | will be called tlan. |
641 | ||
642 | Please email feedback to <torben.mathiasen@compaq.com>. | |
643 | ||
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 644 | config KS8842 |
28bd620c | 645 | tristate "Micrel KSZ8841/42 with generic bus interface" |
19de1e38 | 646 | depends on HAS_IOMEM && DMA_ENGINE |
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 647 | help |
e85eb117 PDM |
648 | This platform driver is for KSZ8841(1-port) / KS8842(2-port) |
649 | ethernet switch chip (managed, VLAN, QoS) from Micrel or | |
650 | Timberdale(FPGA). | |
\9aöjfors, 2009-06-04 03:35:55 +0000">b07878e5 | 651 | |
3ba81f3e | 652 | config KS8851 |
e85eb117 PDM |
653 | tristate "Micrel KS8851 SPI" |
654 | depends on SPI | |
655 | select MII | |
cbb35f8a | 656 | select CRC32 |
e85eb117 PDM |
657 | help |
658 | SPI driver for Micrel KS8851 SPI attached network chip. | |
3ba81f3e | 659 | |
a55c0a0e CD |
660 | config KS8851_MLL |
661 | tristate "Micrel KS8851 MLL" | |
662 | depends on HAS_IOMEM | |
47a01a0c | 663 | select MII |
a55c0a0e CD |
664 | help |
665 | This platform driver is for Micrel KS8851 Address/data bus | |
666 | multiplexed network chip. | |
667 | ||
1da177e4 LT |
668 | config VIA_RHINE |
669 | tristate "VIA Rhine support" | |
670 | depends on NET_PCI && PCI | |
671 | select CRC32 | |
672 | select MII | |
673 | help | |
674 | If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), | |
675 | Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type | |
676 | Ethernet functions can also be found integrated on South Bridges | |
677 | (e.g. VT8235). | |
678 | ||
679 | To compile this driver as a module, choose M here. The module | |
680 | will be called via-rhine. | |
681 | ||
682 | config VIA_RHINE_MMIO | |
683 | bool "Use MMIO instead of PIO" | |
684 | depends on VIA_RHINE | |
685 | help | |
686 | This instructs the driver to use PCI shared memory (MMIO) instead of | |
687 | programmed I/O ports (PIO). Enabling this gives an improvement in | |
688 | processing time in parts of the driver. | |
689 | ||
690 | If unsure, say Y. | |
691 | ||
d95b39c3 MC |
692 | config CPMAC |
693 | tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" | |
839b04c4 | 694 | depends on NET_ETHERNET && EXPERIMENTAL && AR7 |
d95b39c3 | 695 | select PHYLIB |
d95b39c3 MC |
696 | help |
697 | TI AR7 CPMAC Ethernet support | |
698 | ||
1da177e4 LT |
699 | config NET_POCKET |
700 | bool "Pocket and portable adapters" | |
d1c0a65f | 701 | depends on PARPORT |
1da177e4 LT |
702 | ---help--- |
703 | Cute little network (Ethernet) devices which attach to the parallel | |
704 | port ("pocket adapters"), commonly used with laptops. If you have | |
705 | one of those, say Y and read the Ethernet-HOWTO, available from | |
706 | <http://www.tldp.org/docs.html#howto>. | |
707 | ||
708 | If you want to plug a network (or some other) card into the PCMCIA | |
709 | (or PC-card) slot of your laptop instead (PCMCIA is the standard for | |
710 | credit card size extension cards used by all modern laptops), you | |
711 | need the pcmcia-cs package (location contained in the file | |
712 | <file:Documentation/Changes>) and you can say N here. | |
713 | ||
714 | Laptop users should read the Linux Laptop home page at | |
715 | <http://www.linux-on-laptops.com/> or | |
716 | Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. | |
717 | ||
718 | Note that the answer to this question doesn't directly affect the | |
719 | kernel: saying N will just cause the configurator to skip all | |
720 | the questions about this class of network devices. If you say Y, you | |
721 | will be asked for your specific device in the following questions. | |
722 | ||
1da177e4 LT |
723 | config SGISEEQ |
724 | tristate "SGI Seeq ethernet controller support" | |
49b11bc3 | 725 | depends on SGI_HAS_SEEQ |
1da177e4 LT |
726 | help |
727 | Say Y here if you have an Seeq based Ethernet network card. This is | |
728 | used in many Silicon Graphics machines. | |
729 | ||
1da177e4 | 730 | config FEC |
64423307 | 731 | bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" |
bd011e88 | 732 | depends on M523x || M527x || M5272 || M528x || M520x || M532x || \ |
085e79ed UKK |
733 | IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC |
734 | default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM | |
e6b043d5 | 735 | select PHYLIB |
1da177e4 LT |
736 | help |
737 | Say Y here if you want to use the built-in 10/100 Fast ethernet | |
196719ec | 738 | controller on some Motorola ColdFire and Freescale i.MX processors. |
2af6921f | 739 | |
5d031e9e DP |
740 | config FEC_MPC52xx |
741 | tristate "MPC52xx FEC driver" | |
847cdf42 | 742 | depends on PPC_MPC52xx && PPC_BESTCOMM |
5d031e9e DP |
743 | select CRC32 |
744 | select PHYLIB | |
847cdf42 | 745 | select PPC_BESTCOMM_FEC |
5d031e9e DP |
746 | ---help--- |
747 | This option enables support for the MPC5200's on-chip | |
748 | Fast Ethernet Controller | |
4737f097 | 749 | If compiled as module, it will be called fec_mpc52xx. |
5d031e9e DP |
750 | |
751 | config FEC_MPC52xx_MDIO | |
752 | bool "MPC52xx FEC MDIO bus driver" | |
753 | depends on FEC_MPC52xx | |
754 | default y | |
755 | ---help--- | |
756 | The MPC5200's FEC can connect to the Ethernet either with | |
757 | an external MII PHY chip or 10 Mbps 7-wire interface | |
758 | (Motorola? industry standard). | |
759 | If your board uses an external PHY connected to FEC, enable this. | |
760 | If not sure, enable. | |
4737f097 | 761 | If compiled as module, it will be called fec_mpc52xx_phy. |
5d031e9e | 762 | |
bb81b2dd JL |
763 | config XILINX_EMACLITE |
764 | tristate "Xilinx 10/100 Ethernet Lite support" | |
765 | depends on PPC32 || MICROBLAZE | |
5cdaaa12 | 766 | select PHYLIB |
bb81b2dd JL |
767 | help |
768 | This driver supports the 10/100 Ethernet Lite from Xilinx. | |
769 | ||
504d4721 JC |
770 | config LANTIQ_ETOP |
771 | tristate "Lantiq SoC ETOP driver" | |
772 | depends on SOC_TYPE_XWAY | |
773 | help | |
774 | Support for the MII0 inside the Lantiq SoC | |
775 | ||
776 | ||
48257c4f | 777 | source "drivers/net/fs_enet/Kconfig" |
1da177e4 | 778 | |
d6aa60a1 DD |
779 | source "drivers/net/octeon/Kconfig" |
780 | ||
d1c0a65f | 781 | endif # NET_ETHERNET |
1da177e4 LT |
782 | |
783 | # | |
784 | # Gigabit Ethernet | |
785 | # | |
786 | ||
f30486d5 JE |
787 | menuconfig NETDEV_1000 |
788 | bool "Ethernet (1000 Mbit)" | |
cbcd2a4c | 789 | depends on !UML |
f30486d5 | 790 | default y |
06bfb7eb JE |
791 | ---help--- |
792 | Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common | |
793 | type of Local Area Network (LAN) in universities and companies. | |
794 | ||
795 | Say Y here to get to see options for Gigabit Ethernet drivers. | |
796 | This option alone does not add any kernel code. | |
797 | Note that drivers supporting both 100 and 1000 MBit may be listed | |
798 | under "Ethernet (10 or 100MBit)" instead. | |
799 | ||
800 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
801 | |
802 | if NETDEV_1000 | |
1da177e4 | 803 | |
ab7a9831 SH |
804 | config IP1000 |
805 | tristate "IP1000 Gigabit Ethernet support" | |
806 | depends on PCI && EXPERIMENTAL | |
807 | select MII | |
808 | ---help--- | |
809 | This driver supports IP1000 gigabit Ethernet cards. | |
810 | ||
811 | To compile this driver as a module, choose M here: the module | |
812 | will be called ipg. This is recommended. | |
813 | ||
1da177e4 LT |
814 | config HAMACHI |
815 | tristate "Packet Engines Hamachi GNIC-II support" | |
816 | depends on PCI | |
817 | select MII | |
818 | help | |
819 | If you have a Gigabit Ethernet card of this type, say Y and read | |
820 | the Ethernet-HOWTO, available from | |
821 | <http://www.tldp.org/docs.html#howto>. | |
822 | ||
57ce45dd | 823 | To compile this driver as a module, choose M here. The module will be |
1da177e4 LT |
824 | called hamachi. |
825 | ||
826 | config YELLOWFIN | |
827 | tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" | |
828 | depends on PCI && EXPERIMENTAL | |
829 | select CRC32 | |
830 | ---help--- | |
831 | Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet | |
832 | adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is | |
833 | used by the Beowulf Linux cluster project. See | |
834 | <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more | |
835 | information about this driver in particular and Beowulf in general. | |
836 | ||
837 | To compile this driver as a module, choose M here: the module | |
838 | will be called yellowfin. This is recommended. | |
839 | ||
890e8d0a | 840 | config SIS190 |
e797637f | 841 | tristate "SiS190/SiS191 gigabit ethernet support" |
e9985d53 AB |
842 | depends on PCI |
843 | select CRC32 | |
844 | select MII | |
845 | ---help--- | |
e797637f FR |
846 | Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or |
847 | a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to | |
848 | appear in lan on motherboard designs which are based on SiS 965 | |
849 | and SiS 966 south bridge. | |
e9985d53 AB |
850 | |
851 | To compile this driver as a module, choose M here: the module | |
852 | will be called sis190. This is recommended. | |
890e8d0a | 853 | |
baef58b1 | 854 | config SKGE |
560040b8 | 855 | tristate "Marvell Yukon Gigabit Ethernet support" |
7a160c73 | 856 | depends on PCI |
baef58b1 SH |
857 | select CRC32 |
858 | ---help--- | |
859 | This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx | |
860 | and related Gigabit Ethernet adapters. It is a new smaller driver | |
46a60f2d | 861 | with better performance and more complete ethtool support. |
baef58b1 SH |
862 | |
863 | It does not support the link failover and network management | |
5ad887fa | 864 | features that "portable" vendor supplied sk98lin driver does. |
cd28ab6a | 865 | |
c6f0d75a DD |
866 | This driver supports adapters based on the original Yukon chipset: |
867 | Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, | |
868 | Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. | |
869 | ||
870 | It does not support the newer Yukon2 chipset: a separate driver, | |
560040b8 | 871 | sky2, is provided for these adapters. |
c6f0d75a DD |
872 | |
873 | To compile this driver as a module, choose M here: the module | |
874 | will be called skge. This is recommended. | |
cd28ab6a | 875 | |
678aa1f6 | 876 | config SKGE_DEBUG |
e85eb117 PDM |
877 | bool "Debugging interface" |
878 | depends on SKGE && DEBUG_FS | |
879 | help | |
880 | This option adds the ability to dump driver state for debugging. | |
881 | The file /sys/kernel/debug/skge/ethX displays the state of the internal | |
882 | transmit and receive rings. | |
678aa1f6 | 883 | |
e85eb117 | 884 | If unsure, say N. |
678aa1f6 | 885 | |
57d6fa37 | 886 | config SKGE_GENESIS |
887 | bool "Support for older SysKonnect Genesis boards" | |
888 | depends on SKGE | |
889 | help | |
890 | This enables support for the older and uncommon SysKonnect Genesis | |
891 | chips, which support MII via an external transceiver, instead of | |
892 | an internal one. Disabling this option will save some memory | |
893 | by making code smaller. If unsure say Y. | |
894 | ||
cd28ab6a | 895 | config SKY2 |
560040b8 | 896 | tristate "Marvell Yukon 2 support" |
f479b322 | 897 | depends on PCI |
cd28ab6a SH |
898 | select CRC32 |
899 | ---help--- | |
cab00891 | 900 | This driver supports Gigabit Ethernet adapters based on the |
c6f0d75a DD |
901 | Marvell Yukon 2 chipset: |
902 | Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ | |
903 | 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 | |
904 | ||
f479b322 | 905 | There is companion driver for the older Marvell Yukon and |
560040b8 | 906 | SysKonnect Genesis based adapters: skge. |
cd28ab6a SH |
907 | |
908 | To compile this driver as a module, choose M here: the module | |
909 | will be called sky2. This is recommended. | |
910 | ||
3cf26753 | 911 | config SKY2_DEBUG |
e85eb117 PDM |
912 | bool "Debugging interface" |
913 | depends on SKY2 && DEBUG_FS | |
914 | help | |
915 | This option adds the ability to dump driver state for debugging. | |
916 | The file /sys/kernel/debug/sky2/ethX displays the state of the internal | |
917 | transmit and receive rings. | |
3cf26753 | 918 | |
e85eb117 | 919 | If unsure, say N. |
1da177e4 LT |
920 | |
921 | config VIA_VELOCITY | |
922 | tristate "VIA Velocity support" | |
73815538 | 923 | depends on PCI |
1da177e4 LT |
924 | select CRC32 |
925 | select CRC_CCITT | |
926 | select MII | |
927 | help | |
928 | If you have a VIA "Velocity" based network card say Y here. | |
929 | ||
930 | To compile this driver as a module, choose M here. The module | |
931 | will be called via-velocity. | |
932 | ||
aaec0fab JO |
933 | config SPIDER_NET |
934 | tristate "Spider Gigabit Ethernet driver" | |
3342cf0e | 935 | depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) |
9b15879a | 936 | select FW_LOADER |
aaec0fab JO |
937 | help |
938 | This driver supports the Gigabit Ethernet chips present on the | |
939 | Cell Processor-Based Blades from IBM. | |
940 | ||
5e123b84 | 941 | config TSI108_ETH |
dd68ad22 PDM |
942 | tristate "Tundra TSI108 gigabit Ethernet support" |
943 | depends on TSI108_BRIDGE | |
944 | help | |
945 | This driver supports Tundra TSI108 gigabit Ethernet ports. | |
946 | To compile this driver as a module, choose M here: the module | |
947 | will be called tsi108_eth. | |
5e123b84 | 948 | |
02c18891 MM |
949 | config GELIC_NET |
950 | tristate "PS3 Gigabit Ethernet driver" | |
951 | depends on PPC_PS3 | |
1d32e218 | 952 | select PS3_SYS_MANAGER |
02c18891 MM |
953 | help |
954 | This driver supports the network device on the PS3 game | |
955 | console. This driver has built-in support for Ethernet. | |
956 | ||
957 | To compile this driver as a module, choose M here: the | |
958 | module will be called ps3_gelic. | |
959 | ||
09dde54c | 960 | config GELIC_WIRELESS |
97ed8390 | 961 | bool "PS3 Wireless support" |
92c6f8d8 | 962 | depends on WLAN |
97ed8390 JL |
963 | depends on GELIC_NET |
964 | select WIRELESS_EXT | |
965 | help | |
966 | This option adds the support for the wireless feature of PS3. | |
967 | If you have the wireless-less model of PS3 or have no plan to | |
968 | use wireless feature, disabling this option saves memory. As | |
969 | the driver automatically distinguishes the models, you can | |
970 | safely enable this option even if you have a wireless-less model. | |
09dde54c | 971 | |
1577ecef AF |
972 | config FSL_PQ_MDIO |
973 | tristate "Freescale PQ MDIO" | |
974 | depends on FSL_SOC | |
975 | select PHYLIB | |
976 | help | |
977 | This driver supports the MDIO bus used by the gianfar and UCC drivers. | |
978 | ||
1da177e4 LT |
979 | config GIANFAR |
980 | tristate "Gianfar Ethernet" | |
3a83156b | 981 | depends on FSL_SOC |
1577ecef | 982 | select FSL_PQ_MDIO |
bb40dcbb | 983 | select PHYLIB |
bf41a7c5 | 984 | select CRC32 |
1da177e4 | 985 | help |
ef82a306 JL |
986 | This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, |
987 | and MPC86xx family of chips, and the FEC on the 8540. | |
1da177e4 | 988 | |
ce973b14 | 989 | config UCC_GETH |
7d776cb5 TT |
990 | tristate "Freescale QE Gigabit Ethernet" |
991 | depends on QUICC_ENGINE | |
1577ecef | 992 | select FSL_PQ_MDIO |
296baae2 | 993 | select PHYLIB |
ce973b14 | 994 | help |
7d776cb5 TT |
995 | This driver supports the Gigabit Ethernet mode of the QUICC Engine, |
996 | which is available on some Freescale SOCs. | |
ce973b14 | 997 | |
d5b9049d MR |
998 | config UGETH_TX_ON_DEMAND |
999 | bool "Transmit on Demand support" | |
ce973b14 LY |
1000 | depends on UCC_GETH |
1001 | ||
1da177e4 | 1002 | config MV643XX_ETH |
9c1bbdfe | 1003 | tristate "Marvell Discovery (643XX) and Orion ethernet support" |
10ccff62 | 1004 | depends on (MV64X60 || PPC32 || PLAT_ORION) && INET |
ab307a39 | 1005 | select INET_LRO |
ed94493f | 1006 | select PHYLIB |
1da177e4 | 1007 | help |
9c1bbdfe LB |
1008 | This driver supports the gigabit ethernet MACs in the |
1009 | Marvell Discovery PPC/MIPS chipset family (MV643XX) and | |
1010 | in the Marvell Orion ARM SoC family. | |
1011 | ||
1012 | Some boards that use the Discovery chipset are the Momenco | |
1013 | Ocelot C and Jaguar ATX and Pegasos II. | |
1da177e4 | 1014 | |
92744989 GL |
1015 | config XILINX_LL_TEMAC |
1016 | tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" | |
e44171f1 | 1017 | depends on PPC || MICROBLAZE |
92744989 | 1018 | select PHYLIB |
92744989 GL |
1019 | help |
1020 | This driver supports the Xilinx 10/100/1000 LocalLink TEMAC | |
1021 | core used in Xilinx Spartan and Virtex FPGAs | |
1022 | ||
95252236 GFT |
1023 | config JME |
1024 | tristate "JMicron(R) PCI-Express Gigabit Ethernet support" | |
1025 | depends on PCI | |
1026 | select CRC32 | |
1027 | select MII | |
1028 | ---help--- | |
1029 | This driver supports the PCI-Express gigabit ethernet adapters | |
1030 | based on JMicron JMC250 chipset. | |
1031 | ||
1032 | To compile this driver as a module, choose M here. The module | |
1033 | will be called jme. | |
1034 | ||
8b0215aa OS |
1035 | config S6GMAC |
1036 | tristate "S6105 GMAC ethernet support" | |
1037 | depends on XTENSA_VARIANT_S6000 | |
1038 | select PHYLIB | |
1039 | help | |
1040 | This driver supports the on chip ethernet device on the | |
1041 | S6105 xtensa processor. | |
1042 | ||
1043 | To compile this driver as a module, choose M here. The module | |
1044 | will be called s6gmac. | |
1045 | ||
77555ee7 | 1046 | config PCH_GBE |
b0e6baf5 | 1047 | tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE" |
77555ee7 | 1048 | depends on PCI |
116c1ea0 | 1049 | select MII |
77555ee7 | 1050 | ---help--- |
a1dcfcb7 TO |
1051 | This is a gigabit ethernet driver for EG20T PCH. |
1052 | EG20T PCH is the platform controller hub that is used in Intel's | |
77555ee7 | 1053 | general embedded platform. |
a1dcfcb7 | 1054 | EG20T PCH has Gigabit Ethernet interface. |
77555ee7 MO |
1055 | Using this interface, it is able to access system devices connected |
1056 | to Gigabit Ethernet. | |
1057 | This driver enables Gigabit Ethernet function. | |
1058 | ||
b0e6baf5 T |
1059 | This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ |
1060 | Output Hub), ML7223. | |
1061 | ML7223 IOH is for MP(Media Phone) use. | |
1062 | ML7223 is companion chip for Intel Atom E6xx series. | |
1063 | ML7223 is completely compatible for Intel EG20T PCH. | |
1064 | ||
f30486d5 | 1065 | endif # NETDEV_1000 |
1da177e4 LT |
1066 | |
1067 | # | |
1068 | # 10 Gigabit Ethernet | |
1069 | # | |
1070 | ||
f30486d5 JE |
1071 | menuconfig NETDEV_10000 |
1072 | bool "Ethernet (10000 Mbit)" | |
cbcd2a4c | 1073 | depends on !UML |
f30486d5 | 1074 | default y |
06bfb7eb JE |
1075 | ---help--- |
1076 | Say Y here to get to see options for 10 Gigabit Ethernet drivers. | |
1077 | This option alone does not add any kernel code. | |
1078 | ||
1079 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
1080 | |
1081 | if NETDEV_10000 | |
1da177e4 | 1082 | |
1b1c2e95 BH |
1083 | config MDIO |
1084 | tristate | |
1085 | ||
f30486d5 | 1086 | endif # NETDEV_10000 |
1da177e4 | 1087 | |
1da177e4 LT |
1088 | source "drivers/net/tokenring/Kconfig" |
1089 | ||
1090 | source "drivers/net/wireless/Kconfig" | |
1091 | ||
143ee2d5 IPG |
1092 | source "drivers/net/wimax/Kconfig" |
1093 | ||
5b2fc499 JG |
1094 | source "drivers/net/usb/Kconfig" |
1095 | ||
1da177e4 | 1096 | source "drivers/net/pcmcia/Kconfig" |
1da177e4 LT |
1097 | |
1098 | source "drivers/net/wan/Kconfig" | |
1099 | ||
1100 | source "drivers/atm/Kconfig" | |
1101 | ||
8459464f SL |
1102 | source "drivers/ieee802154/Kconfig" |
1103 | ||
1da177e4 LT |
1104 | source "drivers/s390/net/Kconfig" |
1105 | ||
9b27105b SB |
1106 | source "drivers/net/caif/Kconfig" |
1107 | ||
e5a06939 CM |
1108 | config TILE_NET |
1109 | tristate "Tilera GBE/XGBE network driver support" | |
1110 | depends on TILE | |
1111 | default y | |
1112 | select CRC32 | |
1113 | help | |
1114 | This is a standard Linux network device driver for the | |
1115 | on-chip Tilera Gigabit Ethernet and XAUI interfaces. | |
1116 | ||
1117 | To compile this driver as a module, choose M here: the module | |
1118 | will be called tile_net. | |
1119 | ||
0d160211 JF |
1120 | config XEN_NETDEV_FRONTEND |
1121 | tristate "Xen network device frontend driver" | |
1122 | depends on XEN | |
7003087c | 1123 | select XEN_XENBUS_FRONTEND |
0d160211 JF |
1124 | default y |
1125 | help | |
f942dc25 IC |
1126 | This driver provides support for Xen paravirtual network |
1127 | devices exported by a Xen network driver domain (often | |
1128 | domain 0). | |
1129 | ||
1130 | The corresponding Linux backend driver is enabled by the | |
1131 | CONFIG_XEN_NETDEV_BACKEND option. | |
1132 | ||
1133 | If you are compiling a kernel for use as Xen guest, you | |
1134 | should say Y here. To compile this driver as a module, chose | |
1135 | M here: the module will be called xen-netfront. | |
1136 | ||
1137 | config XEN_NETDEV_BACKEND | |
1138 | tristate "Xen backend network device" | |
1139 | depends on XEN_BACKEND | |
1140 | help | |
1141 | This driver allows the kernel to act as a Xen network driver | |
1142 | domain which exports paravirtual network devices to other | |
1143 | Xen domains. These devices can be accessed by any operating | |
1144 | system that implements a compatible front end. | |
1145 | ||
1146 | The corresponding Linux frontend driver is enabled by the | |
1147 | CONFIG_XEN_NETDEV_FRONTEND configuration option. | |
1148 | ||
1149 | The backend driver presents a standard network device | |
1150 | endpoint for each paravirtual network device to the driver | |
1151 | domain network stack. These can then be bridged or routed | |
1152 | etc in order to provide full network connectivity. | |
1153 | ||
1154 | If you are compiling a kernel to run in a Xen network driver | |
1155 | domain (often this is domain 0) you should say Y here. To | |
1156 | compile this driver as a module, chose M here: the module | |
1157 | will be called xen-netback. | |
0d160211 | 1158 | |
f89efd52 MP |
1159 | config RIONET |
1160 | tristate "RapidIO Ethernet over messaging driver support" | |
a81c52a8 | 1161 | depends on RAPIDIO |
f89efd52 MP |
1162 | |
1163 | config RIONET_TX_SIZE | |
1164 | int "Number of outbound queue entries" | |
1165 | depends on RIONET | |
1166 | default "128" | |
1167 | ||
1168 | config RIONET_RX_SIZE | |
1169 | int "Number of inbound queue entries" | |
1170 | depends on RIONET | |
1171 | default "128" | |
1172 | ||
1da177e4 | 1173 | config FDDI |
eb56092f | 1174 | tristate "FDDI driver support" |
e89a2cfb | 1175 | depends on (PCI || EISA || TC) |
1da177e4 LT |
1176 | help |
1177 | Fiber Distributed Data Interface is a high speed local area network | |
1178 | design; essentially a replacement for high speed Ethernet. FDDI can | |
1179 | run over copper or fiber. If you are connected to such a network and | |
1180 | want a driver for the FDDI card in your computer, say Y here (and | |
1181 | then also Y to the driver for your FDDI card, below). Most people | |
1182 | will say N. | |
1183 | ||
1184 | config DEFXX | |
e89a2cfb MR |
1185 | tristate "Digital DEFTA/DEFEA/DEFPA adapter support" |
1186 | depends on FDDI && (PCI || EISA || TC) | |
1187 | ---help--- | |
1188 | This is support for the DIGITAL series of TURBOchannel (DEFTA), | |
1189 | EISA (DEFEA) and PCI (DEFPA) controllers which can connect you | |
1190 | to a local FDDI network. | |
1191 | ||
1192 | To compile this driver as a module, choose M here: the module | |
1193 | will be called defxx. If unsure, say N. | |
1194 | ||
1195 | config DEFXX_MMIO | |
1196 | bool | |
1197 | prompt "Use MMIO instead of PIO" if PCI || EISA | |
1198 | depends on DEFXX | |
1199 | default n if PCI || EISA | |
1200 | default y | |
1201 | ---help--- | |
1202 | This instructs the driver to use EISA or PCI memory-mapped I/O | |
1203 | (MMIO) as appropriate instead of programmed I/O ports (PIO). | |
1204 | Enabling this gives an improvement in processing time in parts | |
1205 | of the driver, but it may cause problems with EISA (DEFEA) | |
1206 | adapters. TURBOchannel does not have the concept of I/O ports, | |
1207 | so MMIO is always used for these (DEFTA) adapters. | |
1208 | ||
1209 | If unsure, say N. | |
1da177e4 LT |
1210 | |
1211 | config SKFP | |
1212 | tristate "SysKonnect FDDI PCI support" | |
1213 | depends on FDDI && PCI | |
bc63eb9c | 1214 | select BITREVERSE |
1da177e4 LT |
1215 | ---help--- |
1216 | Say Y here if you have a SysKonnect FDDI PCI adapter. | |
1217 | The following adapters are supported by this driver: | |
1218 | - SK-5521 (SK-NET FDDI-UP) | |
1219 | - SK-5522 (SK-NET FDDI-UP DAS) | |
1220 | - SK-5541 (SK-NET FDDI-FP) | |
1221 | - SK-5543 (SK-NET FDDI-LP) | |
1222 | - SK-5544 (SK-NET FDDI-LP DAS) | |
1223 | - SK-5821 (SK-NET FDDI-UP64) | |
1224 | - SK-5822 (SK-NET FDDI-UP64 DAS) | |
1225 | - SK-5841 (SK-NET FDDI-FP64) | |
1226 | - SK-5843 (SK-NET FDDI-LP64) | |
1227 | - SK-5844 (SK-NET FDDI-LP64 DAS) | |
1228 | - Netelligent 100 FDDI DAS Fibre SC | |
1229 | - Netelligent 100 FDDI SAS Fibre SC | |
1230 | - Netelligent 100 FDDI DAS UTP | |
1231 | - Netelligent 100 FDDI SAS UTP | |
1232 | - Netelligent 100 FDDI SAS Fibre MIC | |
1233 | ||
1234 | Read <file:Documentation/networking/skfp.txt> for information about | |
1235 | the driver. | |
1236 | ||
1237 | Questions concerning this driver can be addressed to: | |
1238 | <linux@syskonnect.de> | |
1239 | ||
1240 | To compile this driver as a module, choose M here: the module | |
1241 | will be called skfp. This is recommended. | |
1242 | ||
1243 | config HIPPI | |
1244 | bool "HIPPI driver support (EXPERIMENTAL)" | |
cbcd2a4c | 1245 | depends on EXPERIMENTAL && INET && PCI |
1da177e4 LT |
1246 | help |
1247 | HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and | |
1248 | 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI | |
1249 | can run over copper (25m) or fiber (300m on multi-mode or 10km on | |
1250 | single-mode). HIPPI networks are commonly used for clusters and to | |
1251 | connect to super computers. If you are connected to a HIPPI network | |
1252 | and have a HIPPI network card in your computer that you want to use | |
1253 | under Linux, say Y here (you must also remember to enable the driver | |
1254 | for your HIPPI card below). Most people will say N here. | |
1255 | ||
1256 | config ROADRUNNER | |
1257 | tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" | |
1258 | depends on HIPPI && PCI | |
1259 | help | |
1260 | Say Y here if this is your PCI HIPPI network card. | |
1261 | ||
1262 | To compile this driver as a module, choose M here: the module | |
1263 | will be called rrunner. If unsure, say N. | |
1264 | ||
1265 | config ROADRUNNER_LARGE_RINGS | |
1266 | bool "Use large TX/RX rings (EXPERIMENTAL)" | |
1267 | depends on ROADRUNNER | |
1268 | help | |
1269 | If you say Y here, the RoadRunner driver will preallocate up to 2 MB | |
1270 | of additional memory to allow for fastest operation, both for | |
1271 | transmitting and receiving. This memory cannot be used by any other | |
1272 | kernel code or by user space programs. Say Y here only if you have | |
1273 | the memory. | |
1274 | ||
1275 | config PLIP | |
1276 | tristate "PLIP (parallel port) support" | |
cbcd2a4c | 1277 | depends on PARPORT |
1da177e4 LT |
1278 | ---help--- |
1279 | PLIP (Parallel Line Internet Protocol) is used to create a | |
1280 | reasonably fast mini network consisting of two (or, rarely, more) | |
1281 | local machines. A PLIP link from a Linux box is a popular means to | |
1282 | install a Linux distribution on a machine which doesn't have a | |
1283 | CD-ROM drive (a minimal system has to be transferred with floppies | |
1284 | first). The kernels on both machines need to have this PLIP option | |
1285 | enabled for this to work. | |
1286 | ||
1287 | The PLIP driver has two modes, mode 0 and mode 1. The parallel | |
1288 | ports (the connectors at the computers with 25 holes) are connected | |
1289 | with "null printer" or "Turbo Laplink" cables which can transmit 4 | |
1290 | bits at a time (mode 0) or with special PLIP cables, to be used on | |
1291 | bidirectional parallel ports only, which can transmit 8 bits at a | |
1292 | time (mode 1); you can find the wiring of these cables in | |
1293 | <file:Documentation/networking/PLIP.txt>. The cables can be up to | |
1294 | 15m long. Mode 0 works also if one of the machines runs DOS/Windows | |
1295 | and has some PLIP software installed, e.g. the Crynwr PLIP packet | |
1296 | driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) | |
1297 | and winsock or NCSA's telnet. | |
1298 | ||
1299 | If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well | |
1300 | as the NET-3-HOWTO, both available from | |
1301 | <http://www.tldp.org/docs.html#howto>. Note that the PLIP | |
1302 | protocol has been changed and this PLIP driver won't work together | |
1303 | with the PLIP support in Linux versions 1.0.x. This option enlarges | |
1304 | your kernel by about 8 KB. | |
1305 | ||
57ce45dd AB |
1306 | To compile this driver as a module, choose M here. The module |
1307 | will be called plip. If unsure, say Y or M, in case you buy | |
1308 | a laptop later. | |
1da177e4 LT |
1309 | |
1310 | config PPP | |
1311 | tristate "PPP (point-to-point protocol) support" | |
b6e37e55 | 1312 | select SLHC |
1da177e4 LT |
1313 | ---help--- |
1314 | PPP (Point to Point Protocol) is a newer and better SLIP. It serves | |
1315 | the same purpose: sending Internet traffic over telephone (and other | |
1316 | serial) lines. Ask your access provider if they support it, because | |
1317 | otherwise you can't use it; most Internet access providers these | |
1318 | days support PPP rather than SLIP. | |
1319 | ||
1320 | To use PPP, you need an additional program called pppd as described | |
1321 | in the PPP-HOWTO, available at | |
1322 | <http://www.tldp.org/docs.html#howto>. Make sure that you have | |
1323 | the version of pppd recommended in <file:Documentation/Changes>. | |
1324 | The PPP option enlarges your kernel by about 16 KB. | |
1325 | ||
1326 | There are actually two versions of PPP: the traditional PPP for | |
1327 | asynchronous lines, such as regular analog phone lines, and | |
1328 | synchronous PPP which can be used over digital ISDN lines for | |
1329 | example. If you want to use PPP over phone lines or other | |
1330 | asynchronous serial lines, you need to say Y (or M) here and also to | |
1331 | the next option, "PPP support for async serial ports". For PPP over | |
1332 | synchronous lines, you should say Y (or M) here and to "Support | |
1333 | synchronous PPP", below. | |
1334 | ||
1335 | If you said Y to "Version information on all symbols" above, then | |
1336 | you cannot compile the PPP driver into the kernel; you can then only | |
1337 | compile it as a module. To compile this driver as a module, choose M | |
57ce45dd | 1338 | here. The module will be called ppp_generic. |
1da177e4 LT |
1339 | |
1340 | config PPP_MULTILINK | |
1341 | bool "PPP multilink support (EXPERIMENTAL)" | |
1342 | depends on PPP && EXPERIMENTAL | |
1343 | help | |
1344 | PPP multilink is a protocol (defined in RFC 1990) which allows you | |
1345 | to combine several (logical or physical) lines into one logical PPP | |
1346 | connection, so that you can utilize your full bandwidth. | |
1347 | ||
1348 | This has to be supported at the other end as well and you need a | |
1349 | version of the pppd daemon which understands the multilink protocol. | |
1350 | ||
1351 | If unsure, say N. | |
1352 | ||
1353 | config PPP_FILTER | |
1354 | bool "PPP filtering" | |
1355 | depends on PPP | |
1356 | help | |
1357 | Say Y here if you want to be able to filter the packets passing over | |
1358 | PPP interfaces. This allows you to control which packets count as | |
1359 | activity (i.e. which packets will reset the idle timer or bring up | |
47c51431 | 1360 | a demand-dialed link) and which packets are to be dropped entirely. |
1da177e4 LT |
1361 | You need to say Y here if you wish to use the pass-filter and |
1362 | active-filter options to pppd. | |
1363 | ||
1364 | If unsure, say N. | |
1365 | ||
1366 | config PPP_ASYNC | |
1367 | tristate "PPP support for async serial ports" | |
1368 | depends on PPP | |
1369 | select CRC_CCITT | |
1370 | ---help--- | |
1371 | Say Y (or M) here if you want to be able to use PPP over standard | |
1372 | asynchronous serial ports, such as COM1 or COM2 on a PC. If you use | |
1373 | a modem (not a synchronous or ISDN modem) to contact your ISP, you | |
1374 | need this option. | |
1375 | ||
1376 | To compile this driver as a module, choose M here. | |
1377 | ||
1378 | If unsure, say Y. | |
1379 | ||
1380 | config PPP_SYNC_TTY | |
1381 | tristate "PPP support for sync tty ports" | |
1382 | depends on PPP | |
1383 | help | |
1384 | Say Y (or M) here if you want to be able to use PPP over synchronous | |
1385 | (HDLC) tty devices, such as the SyncLink adapter. These devices | |
1386 | are often used for high-speed leased lines like T1/E1. | |
1387 | ||
1388 | To compile this driver as a module, choose M here. | |
1389 | ||
1390 | config PPP_DEFLATE | |
1391 | tristate "PPP Deflate compression" | |
1392 | depends on PPP | |
1393 | select ZLIB_INFLATE | |
1394 | select ZLIB_DEFLATE | |
1395 | ---help--- | |
1396 | Support for the Deflate compression method for PPP, which uses the | |
1397 | Deflate algorithm (the same algorithm that gzip uses) to compress | |
1398 | each PPP packet before it is sent over the wire. The machine at the | |
1399 | other end of the PPP link (usually your ISP) has to support the | |
1400 | Deflate compression method as well for this to be useful. Even if | |
1401 | they don't support it, it is safe to say Y here. | |
1402 | ||
1403 | To compile this driver as a module, choose M here. | |
1404 | ||
1405 | config PPP_BSDCOMP | |
1406 | tristate "PPP BSD-Compress compression" | |
1407 | depends on PPP | |
1408 | ---help--- | |
1409 | Support for the BSD-Compress compression method for PPP, which uses | |
1410 | the LZW compression method to compress each PPP packet before it is | |
1411 | sent over the wire. The machine at the other end of the PPP link | |
1412 | (usually your ISP) has to support the BSD-Compress compression | |
1413 | method as well for this to be useful. Even if they don't support it, | |
1414 | it is safe to say Y here. | |
1415 | ||
1416 | The PPP Deflate compression method ("PPP Deflate compression", | |
1417 | above) is preferable to BSD-Compress, because it compresses better | |
1418 | and is patent-free. | |
1419 | ||
1420 | Note that the BSD compression code will always be compiled as a | |
1421 | module; it is called bsd_comp and will show up in the directory | |
1422 | modules once you have said "make modules". If unsure, say N. | |
1423 | ||
b3f9b92a | 1424 | config PPP_MPPE |
e85eb117 PDM |
1425 | tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" |
1426 | depends on PPP && EXPERIMENTAL | |
1427 | select CRYPTO | |
1428 | select CRYPTO_SHA1 | |
1429 | select CRYPTO_ARC4 | |
1430 | select CRYPTO_ECB | |
1431 | ---help--- | |
1432 | Support for the MPPE Encryption protocol, as employed by the | |
1433 | Microsoft Point-to-Point Tunneling Protocol. | |
1434 | ||
1435 | See http://pptpclient.sourceforge.net/ for information on | |
1436 | configuring PPTP clients and servers to utilize this method. | |
b3f9b92a | 1437 | |
1da177e4 LT |
1438 | config PPPOE |
1439 | tristate "PPP over Ethernet (EXPERIMENTAL)" | |
1440 | depends on EXPERIMENTAL && PPP | |
1441 | help | |
1442 | Support for PPP over Ethernet. | |
1443 | ||
1444 | This driver requires the latest version of pppd from the CVS | |
1445 | repository at cvs.samba.org. Alternatively, see the | |
1446 | RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) | |
1447 | which contains instruction on how to use this driver (under | |
1448 | the heading "Kernel mode PPPoE"). | |
1449 | ||
00959ade DK |
1450 | config PPTP |
1451 | tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" | |
1452 | depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX | |
1453 | help | |
1454 | Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) | |
1455 | ||
1456 | This driver requires pppd plugin to work in client mode or | |
1457 | modified pptpd (poptop) to work in server mode. | |
1458 | See http://accel-pptp.sourceforge.net/ for information how to | |
1459 | utilize this module. | |
1460 | ||
1da177e4 LT |
1461 | config PPPOATM |
1462 | tristate "PPP over ATM" | |
1463 | depends on ATM && PPP | |
1464 | help | |
1465 | Support PPP (Point to Point Protocol) encapsulated in ATM frames. | |
1466 | This implementation does not yet comply with section 8 of RFC2364, | |
1467 | which can lead to bad results if the ATM peer loses state and | |
1468 | changes its encapsulation unilaterally. | |
1469 | ||
3557baab JC |
1470 | config PPPOL2TP |
1471 | tristate "PPP over L2TP (EXPERIMENTAL)" | |
fd558d18 | 1472 | depends on EXPERIMENTAL && L2TP && PPP |
3557baab JC |
1473 | help |
1474 | Support for PPP-over-L2TP socket family. L2TP is a protocol | |
1475 | used by ISPs and enterprises to tunnel PPP traffic over UDP | |
1476 | tunnels. L2TP is replacing PPTP for VPN uses. | |
1477 | ||
1da177e4 LT |
1478 | config SLIP |
1479 | tristate "SLIP (serial line) support" | |
1da177e4 LT |
1480 | ---help--- |
1481 | Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to | |
1482 | connect to your Internet service provider or to connect to some | |
1483 | other local Unix box or if you want to configure your Linux box as a | |
1484 | Slip/CSlip server for other people to dial in. SLIP (Serial Line | |
1485 | Internet Protocol) is a protocol used to send Internet traffic over | |
1486 | serial connections such as telephone lines or null modem cables; | |
1487 | nowadays, the protocol PPP is more commonly used for this same | |
1488 | purpose. | |
1489 | ||
1490 | Normally, your access provider has to support SLIP in order for you | |
1491 | to be able to use it, but there is now a SLIP emulator called SLiRP | |
1492 | around (available from | |
1493 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
1494 | allows you to use SLIP over a regular dial up shell connection. If | |
1495 | you plan to use SLiRP, make sure to say Y to CSLIP, below. The | |
1496 | NET-3-HOWTO, available from | |
1497 | <http://www.tldp.org/docs.html#howto>, explains how to | |
1498 | configure SLIP. Note that you don't need this option if you just | |
1499 | want to run term (term is a program which gives you almost full | |
1500 | Internet connectivity if you have a regular dial up shell account on | |
1501 | some Internet connected Unix computer. Read | |
1502 | <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP | |
1503 | support will enlarge your kernel by about 4 KB. If unsure, say N. | |
1504 | ||
57ce45dd AB |
1505 | To compile this driver as a module, choose M here. The module |
1506 | will be called slip. | |
1da177e4 LT |
1507 | |
1508 | config SLIP_COMPRESSED | |
1509 | bool "CSLIP compressed headers" | |
1510 | depends on SLIP | |
b6e37e55 | 1511 | select SLHC |
1da177e4 LT |
1512 | ---help--- |
1513 | This protocol is faster than SLIP because it uses compression on the | |
1514 | TCP/IP headers (not on the data itself), but it has to be supported | |
1515 | on both ends. Ask your access provider if you are not sure and | |
1516 | answer Y, just in case. You will still be able to use plain SLIP. If | |
1517 | you plan to use SLiRP, the SLIP emulator (available from | |
1518 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
1519 | allows you to use SLIP over a regular dial up shell connection, you | |
1520 | definitely want to say Y here. The NET-3-HOWTO, available from | |
1521 | <http://www.tldp.org/docs.html#howto>, explains how to configure | |
1522 | CSLIP. This won't enlarge your kernel. | |
1523 | ||
b6e37e55 RB |
1524 | config SLHC |
1525 | tristate | |
1526 | help | |
1527 | This option enables Van Jacobsen serial line header compression | |
1528 | routines. | |
1529 | ||
1da177e4 LT |
1530 | config SLIP_SMART |
1531 | bool "Keepalive and linefill" | |
1532 | depends on SLIP | |
1533 | help | |
1534 | Adds additional capabilities to the SLIP driver to support the | |
1535 | RELCOM line fill and keepalive monitoring. Ideal on poor quality | |
1536 | analogue lines. | |
1537 | ||
1538 | config SLIP_MODE_SLIP6 | |
1539 | bool "Six bit SLIP encapsulation" | |
1540 | depends on SLIP | |
1541 | help | |
1542 | Just occasionally you may need to run IP over hostile serial | |
1543 | networks that don't pass all control characters or are only seven | |
1544 | bit. Saying Y here adds an extra mode you can use with SLIP: | |
1545 | "slip6". In this mode, SLIP will only send normal ASCII symbols over | |
1546 | the serial device. Naturally, this has to be supported at the other | |
1547 | end of the link as well. It's good enough, for example, to run IP | |
1548 | over the async ports of a Camtec JNT Pad. If unsure, say N. | |
1549 | ||
1550 | config NET_FC | |
1551 | bool "Fibre Channel driver support" | |
cbcd2a4c | 1552 | depends on SCSI && PCI |
1da177e4 LT |
1553 | help |
1554 | Fibre Channel is a high speed serial protocol mainly used to connect | |
1555 | large storage devices to the computer; it is compatible with and | |
1556 | intended to replace SCSI. | |
1557 | ||
1558 | If you intend to use Fibre Channel, you need to have a Fibre channel | |
1559 | adaptor card in your computer; say Y here and to the driver for your | |
1560 | adaptor below. You also should have said Y to "SCSI support" and | |
1561 | "SCSI generic support". | |
1562 | ||
1da177e4 | 1563 | config NETCONSOLE |
ecbacf8d | 1564 | tristate "Network console logging support" |
1da177e4 LT |
1565 | ---help--- |
1566 | If you want to log kernel messages over the network, enable this. | |
1567 | See <file:Documentation/networking/netconsole.txt> for details. | |
1568 | ||
0bcc1816 | 1569 | config NETCONSOLE_DYNAMIC |
ecbacf8d | 1570 | bool "Dynamic reconfiguration of logging targets" |
58fa4597 RD |
1571 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ |
1572 | !(NETCONSOLE=y && CONFIGFS_FS=m) | |
0bcc1816 SS |
1573 | help |
1574 | This option enables the ability to dynamically reconfigure target | |
1575 | parameters (interface, IP addresses, port numbers, MAC addresses) | |
1576 | at runtime through a userspace interface exported using configfs. | |
1577 | See <file:Documentation/networking/netconsole.txt> for details. | |
1578 | ||
54208991 RD |
1579 | config NETPOLL |
1580 | def_bool NETCONSOLE | |
1581 | ||
54208991 RD |
1582 | config NETPOLL_TRAP |
1583 | bool "Netpoll traffic trapping" | |
1584 | default n | |
1585 | depends on NETPOLL | |
1586 | ||
1587 | config NET_POLL_CONTROLLER | |
1588 | def_bool NETPOLL | |
1589 | ||
296f96fc RR |
1590 | config VIRTIO_NET |
1591 | tristate "Virtio network driver (EXPERIMENTAL)" | |
1592 | depends on EXPERIMENTAL && VIRTIO | |
1593 | ---help--- | |
0ad07ec1 | 1594 | This is the virtual network driver for virtio. It can be used with |
e85eb117 | 1595 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. |
296f96fc | 1596 | |
d1a890fa | 1597 | config VMXNET3 |
e85eb117 PDM |
1598 | tristate "VMware VMXNET3 ethernet driver" |
1599 | depends on PCI && INET | |
1600 | help | |
1601 | This driver supports VMware's vmxnet3 virtual ethernet NIC. | |
1602 | To compile this driver as a module, choose M here: the | |
1603 | module will be called vmxnet3. | |
d1a890fa | 1604 | |
d1c0a65f | 1605 | endif # NETDEVICES |