]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Network device configuration | |
3 | # | |
4 | ||
d1c0a65f | 5 | menuconfig NETDEVICES |
ce2d2aed | 6 | default y if UML |
e0009820 | 7 | depends on NET |
1da177e4 LT |
8 | bool "Network device support" |
9 | ---help--- | |
10 | You can say N here if you don't intend to connect your Linux box to | |
11 | any other computer at all. | |
12 | ||
13 | You'll have to say Y if your computer contains a network card that | |
14 | you want to use under Linux. If you are going to run SLIP or PPP over | |
15 | telephone line or null modem cable you need say Y here. Connecting | |
16 | two machines with parallel ports using PLIP needs this, as well as | |
17 | AX.25/KISS for sending Internet traffic over amateur radio links. | |
18 | ||
19 | See also "The Linux Network Administrator's Guide" by Olaf Kirch and | |
20 | Terry Dawson. Available at <http://www.tldp.org/guides.html>. | |
21 | ||
22 | If unsure, say Y. | |
23 | ||
1618cb0c RD |
24 | # All the following symbols are dependent on NETDEVICES - do not repeat |
25 | # that for each of the symbols. | |
26 | if NETDEVICES | |
cbcd2a4c | 27 | |
253af423 JHS |
28 | config IFB |
29 | tristate "Intermediate Functional Block support" | |
30 | depends on NET_CLS_ACT | |
31 | ---help--- | |
3cb2fccc | 32 | This is an intermediate driver that allows sharing of |
253af423 JHS |
33 | resources. |
34 | To compile this driver as a module, choose M here: the module | |
35 | will be called ifb. If you want to use more than one ifb | |
36 | device at a time, you need to compile this driver as a module. | |
37 | Instead of 'ifb', the devices will then be called 'ifb0', | |
38 | 'ifb1' etc. | |
39 | Look at the iproute2 documentation directory for usage etc | |
40 | ||
1da177e4 LT |
41 | config DUMMY |
42 | tristate "Dummy net driver support" | |
1da177e4 LT |
43 | ---help--- |
44 | This is essentially a bit-bucket device (i.e. traffic you send to | |
45 | this device is consigned into oblivion) with a configurable IP | |
46 | address. It is most commonly used in order to make your currently | |
47 | inactive SLIP address seem like a real address for local programs. | |
48 | If you use SLIP or PPP, you might want to say Y here. Since this | |
49 | thing often comes in handy, the default is Y. It won't enlarge your | |
50 | kernel either. What a deal. Read about it in the Network | |
51 | Administrator's Guide, available from | |
52 | <http://www.tldp.org/docs.html#guide>. | |
53 | ||
54 | To compile this driver as a module, choose M here: the module | |
55 | will be called dummy. If you want to use more than one dummy | |
56 | device at a time, you need to compile this driver as a module. | |
57 | Instead of 'dummy', the devices will then be called 'dummy0', | |
58 | 'dummy1' etc. | |
59 | ||
60 | config BONDING | |
61 | tristate "Bonding driver support" | |
1da177e4 | 62 | depends on INET |
305d552a | 63 | depends on IPV6 || IPV6=n |
1da177e4 LT |
64 | ---help--- |
65 | Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet | |
66 | Channels together. This is called 'Etherchannel' by Cisco, | |
67 | 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. | |
68 | ||
69 | The driver supports multiple bonding modes to allow for both high | |
47c51431 | 70 | performance and high availability operation. |
1da177e4 LT |
71 | |
72 | Refer to <file:Documentation/networking/bonding.txt> for more | |
73 | information. | |
74 | ||
75 | To compile this driver as a module, choose M here: the module | |
76 | will be called bonding. | |
77 | ||
b863ceb7 PM |
78 | config MACVLAN |
79 | tristate "MAC-VLAN support (EXPERIMENTAL)" | |
80 | depends on EXPERIMENTAL | |
81 | ---help--- | |
82 | This allows one to create virtual interfaces that map packets to | |
83 | or from specific MAC addresses to a particular interface. | |
84 | ||
3dbf8d56 PM |
85 | Macvlan devices can be added using the "ip" command from the |
86 | iproute2 package starting with the iproute2-2.6.23 release: | |
87 | ||
88 | "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" | |
89 | ||
b863ceb7 PM |
90 | To compile this driver as a module, choose M here: the module |
91 | will be called macvlan. | |
92 | ||
20d29d7a AB |
93 | config MACVTAP |
94 | tristate "MAC-VLAN based tap driver (EXPERIMENTAL)" | |
95 | depends on MACVLAN | |
96 | help | |
97 | This adds a specialized tap character device driver that is based | |
98 | on the MAC-VLAN network interface, called macvtap. A macvtap device | |
99 | can be added in the same way as a macvlan device, using 'type | |
100 | macvlan', and then be accessed through the tap user space interface. | |
101 | ||
102 | To compile this driver as a module, choose M here: the module | |
103 | will be called macvtap. | |
104 | ||
1da177e4 LT |
105 | config EQUALIZER |
106 | tristate "EQL (serial line load balancing) support" | |
1da177e4 LT |
107 | ---help--- |
108 | If you have two serial connections to some other computer (this | |
109 | usually requires two modems and two telephone lines) and you use | |
110 | SLIP (the protocol for sending Internet traffic over telephone | |
111 | lines) or PPP (a better SLIP) on them, you can make them behave like | |
112 | one double speed connection using this driver. Naturally, this has | |
113 | to be supported at the other end as well, either with a similar EQL | |
114 | Linux driver or with a Livingston Portmaster 2e. | |
115 | ||
116 | Say Y if you want this and read | |
117 | <file:Documentation/networking/eql.txt>. You may also want to read | |
118 | section 6.2 of the NET-3-HOWTO, available from | |
119 | <http://www.tldp.org/docs.html#howto>. | |
120 | ||
121 | To compile this driver as a module, choose M here: the module | |
122 | will be called eql. If unsure, say N. | |
123 | ||
124 | config TUN | |
125 | tristate "Universal TUN/TAP device driver support" | |
1da177e4 LT |
126 | select CRC32 |
127 | ---help--- | |
128 | TUN/TAP provides packet reception and transmission for user space | |
129 | programs. It can be viewed as a simple Point-to-Point or Ethernet | |
130 | device, which instead of receiving packets from a physical media, | |
131 | receives them from user space program and instead of sending packets | |
132 | via physical media writes them to the user space program. | |
133 | ||
134 | When a program opens /dev/net/tun, driver creates and registers | |
135 | corresponding net device tunX or tapX. After a program closed above | |
136 | devices, driver will automatically delete tunXX or tapXX device and | |
137 | all routes corresponding to it. | |
138 | ||
139 | Please read <file:Documentation/networking/tuntap.txt> for more | |
140 | information. | |
141 | ||
142 | To compile this driver as a module, choose M here: the module | |
143 | will be called tun. | |
144 | ||
145 | If you don't know what to use this for, you don't need it. | |
146 | ||
e314dbdc | 147 | config VETH |
6a9a0250 | 148 | tristate "Virtual ethernet pair device" |
e314dbdc | 149 | ---help--- |
6a9a0250 RR |
150 | This device is a local ethernet tunnel. Devices are created in pairs. |
151 | When one end receives the packet it appears on its pair and vice | |
152 | versa. | |
e314dbdc | 153 | |
1da177e4 LT |
154 | config NET_SB1000 |
155 | tristate "General Instruments Surfboard 1000" | |
cbcd2a4c | 156 | depends on PNP |
1da177e4 LT |
157 | ---help--- |
158 | This is a driver for the General Instrument (also known as | |
159 | NextLevel) SURFboard 1000 internal | |
160 | cable modem. This is an ISA card which is used by a number of cable | |
161 | TV companies to provide cable modem access. It's a one-way | |
162 | downstream-only cable modem, meaning that your upstream net link is | |
163 | provided by your regular phone modem. | |
164 | ||
165 | At present this driver only compiles as a module, so say M here if | |
166 | you have this card. The module will be called sb1000. Then read | |
167 | <file:Documentation/networking/README.sb1000> for information on how | |
168 | to use this module, as it needs special ppp scripts for establishing | |
169 | a connection. Further documentation and the necessary scripts can be | |
170 | found at: | |
171 | ||
172 | <http://www.jacksonville.net/~fventuri/> | |
173 | <http://home.adelphia.net/~siglercm/sb1000.html> | |
174 | <http://linuxpower.cx/~cable/> | |
175 | ||
176 | If you don't have this card, of course say N. | |
177 | ||
f65fd8fb | 178 | source "drivers/net/arcnet/Kconfig" |
1da177e4 | 179 | |
81ccb499 RD |
180 | config MII |
181 | tristate "Generic Media Independent Interface device support" | |
182 | help | |
183 | Most ethernet controllers have MII transceiver either as an external | |
184 | or internal device. It is safe to say Y or M here even if your | |
185 | ethernet card lacks MII. | |
186 | ||
00db8189 AF |
187 | source "drivers/net/phy/Kconfig" |
188 | ||
1da177e4 LT |
189 | # |
190 | # Ethernet | |
191 | # | |
192 | ||
c1abc95b JK |
193 | source "drivers/net/ethernet/Kconfig" |
194 | ||
d1c0a65f | 195 | menuconfig NET_ETHERNET |
1da177e4 | 196 | bool "Ethernet (10 or 100Mbit)" |
d1c0a65f | 197 | depends on !UML |
1da177e4 LT |
198 | ---help--- |
199 | Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common | |
200 | type of Local Area Network (LAN) in universities and companies. | |
201 | ||
202 | Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over | |
203 | coaxial cable, linking computers in a chain), 10BASE-T or twisted | |
204 | pair (10 Mbps over twisted pair cable, linking computers to central | |
205 | hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), | |
206 | 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), | |
207 | 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair | |
208 | cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) | |
209 | [the 100BASE varieties are also known as Fast Ethernet], and Gigabit | |
210 | Ethernet (1 Gbps over optical fiber or short copper links). | |
211 | ||
212 | If your Linux machine will be connected to an Ethernet and you have | |
213 | an Ethernet network interface card (NIC) installed in your computer, | |
214 | say Y here and read the Ethernet-HOWTO, available from | |
215 | <http://www.tldp.org/docs.html#howto>. You will then also have | |
216 | to say Y to the driver for your particular NIC. | |
217 | ||
218 | Note that the answer to this question won't directly affect the | |
219 | kernel: saying N will just cause the configurator to skip all | |
220 | the questions about Ethernet network cards. If unsure, say N. | |
221 | ||
d1c0a65f JE |
222 | if NET_ETHERNET |
223 | ||
86a74ff2 NI |
224 | config SH_ETH |
225 | tristate "Renesas SuperH Ethernet support" | |
226 | depends on SUPERH && \ | |
65ac8851 YS |
227 | (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ |
228 | CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ | |
f29a3d04 | 229 | CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757) |
86a74ff2 NI |
230 | select CRC32 |
231 | select MII | |
232 | select MDIO_BITBANG | |
233 | select PHYLIB | |
234 | help | |
235 | Renesas SuperH Ethernet device driver. | |
f29a3d04 YS |
236 | This driver supporting CPUs are: |
237 | - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757. | |
86a74ff2 | 238 | |
92aa674d SH |
239 | config NET_NETX |
240 | tristate "NetX Ethernet support" | |
241 | select MII | |
d1c0a65f | 242 | depends on ARCH_NETX |
92aa674d SH |
243 | help |
244 | This is support for the Hilscher netX builtin Ethernet ports | |
245 | ||
57ce45dd | 246 | To compile this driver as a module, choose M here. The module |
92aa674d SH |
247 | will be called netx-eth. |
248 | ||
a1365275 SH |
249 | config DM9000 |
250 | tristate "DM9000 support" | |
f40d24d9 | 251 | depends on ARM || BLACKFIN || MIPS |
a1365275 SH |
252 | select CRC32 |
253 | select MII | |
254 | ---help--- | |
255 | Support for DM9000 chipset. | |
256 | ||
57ce45dd AB |
257 | To compile this driver as a module, choose M here. The module |
258 | will be called dm9000. | |
a1365275 | 259 | |
485ca22a BD |
260 | config DM9000_DEBUGLEVEL |
261 | int "DM9000 maximum debug level" | |
262 | depends on DM9000 | |
263 | default 4 | |
264 | help | |
265 | The maximum level of debugging code compiled into the DM9000 | |
266 | driver. | |
267 | ||
f8dd0ecb BD |
268 | config DM9000_FORCE_SIMPLE_PHY_POLL |
269 | bool "Force simple NSR based PHY polling" | |
270 | depends on DM9000 | |
271 | ---help--- | |
272 | This configuration forces the DM9000 to use the NSR's LinkStatus | |
273 | bit to determine if the link is up or down instead of the more | |
274 | costly MII PHY reads. Note, this will not work if the chip is | |
275 | operating with an external PHY. | |
276 | ||
3ec9c11d CL |
277 | config ENC28J60 |
278 | tristate "ENC28J60 support" | |
279 | depends on EXPERIMENTAL && SPI && NET_ETHERNET | |
280 | select CRC32 | |
281 | ---help--- | |
282 | Support for the Microchip EN28J60 ethernet chip. | |
283 | ||
2bfc79de | 284 | To compile this driver as a module, choose M here. The module will be |
3ec9c11d CL |
285 | called enc28j60. |
286 | ||
287 | config ENC28J60_WRITEVERIFY | |
288 | bool "Enable write verify" | |
289 | depends on ENC28J60 | |
290 | ---help--- | |
291 | Enable the verify after the buffer write useful for debugging purpose. | |
292 | If unsure, say N. | |
293 | ||
a1702857 TR |
294 | config ETHOC |
295 | tristate "OpenCores 10/100 Mbps Ethernet MAC support" | |
0ebe74e7 | 296 | depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA |
a1702857 TR |
297 | select MII |
298 | select PHYLIB | |
c5cacb3b RD |
299 | select CRC32 |
300 | select BITREVERSE | |
a1702857 TR |
301 | help |
302 | Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. | |
303 | ||
d4c41139 KG |
304 | config GRETH |
305 | tristate "Aeroflex Gaisler GRETH Ethernet MAC support" | |
cf261b23 | 306 | depends on SPARC |
d4c41139 KG |
307 | select PHYLIB |
308 | select CRC32 | |
309 | help | |
310 | Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. | |
311 | ||
47964174 IY |
312 | config DNET |
313 | tristate "Dave ethernet support (DNET)" | |
4b97926d | 314 | depends on NET_ETHERNET && HAS_IOMEM |
47964174 IY |
315 | select PHYLIB |
316 | help | |
317 | The Dave ethernet interface (DNET) is found on Qong Board FPGA. | |
318 | Say Y to include support for the DNET chip. | |
319 | ||
320 | To compile this driver as a module, choose M here: the module | |
321 | will be called dnet. | |
322 | ||
1da177e4 LT |
323 | config HP100 |
324 | tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" | |
d1c0a65f | 325 | depends on ISA || EISA || PCI |
1da177e4 LT |
326 | help |
327 | If you have a network (Ethernet) card of this type, say Y and read | |
328 | the Ethernet-HOWTO, available from | |
329 | <http://www.tldp.org/docs.html#howto>. | |
330 | ||
57ce45dd | 331 | To compile this driver as a module, choose M here. The module |
1da177e4 LT |
332 | will be called hp100. |
333 | ||
1da177e4 LT |
334 | config NET_PCI |
335 | bool "EISA, VLB, PCI and on board controllers" | |
d1c0a65f | 336 | depends on ISA || EISA || PCI |
1da177e4 LT |
337 | help |
338 | This is another class of network cards which attach directly to the | |
339 | bus. If you have one of those, say Y and read the Ethernet-HOWTO, | |
340 | available from <http://www.tldp.org/docs.html#howto>. | |
341 | ||
342 | Note that the answer to this question doesn't directly affect the | |
343 | kernel: saying N will just cause the configurator to skip all | |
344 | the questions about this class of network cards. If you say Y, you | |
345 | will be asked for your specific card in the following questions. If | |
346 | you are unsure, say Y. | |
347 | ||
1da177e4 LT |
348 | config ADAPTEC_STARFIRE |
349 | tristate "Adaptec Starfire/DuraLAN support" | |
350 | depends on NET_PCI && PCI | |
351 | select CRC32 | |
352 | select MII | |
353 | help | |
354 | Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network | |
355 | adapter. The DuraLAN chip is used on the 64 bit PCI boards from | |
356 | Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip | |
357 | driver. | |
358 | ||
359 | To compile this driver as a module, choose M here: the module | |
360 | will be called starfire. This is recommended. | |
361 | ||
1da177e4 | 362 | config FORCEDETH |
82770086 AB |
363 | tristate "nForce Ethernet support" |
364 | depends on NET_PCI && PCI | |
1da177e4 LT |
365 | help |
366 | If you have a network (Ethernet) controller of this type, say Y and | |
367 | read the Ethernet-HOWTO, available from | |
368 | <http://www.tldp.org/docs.html#howto>. | |
369 | ||
57ce45dd AB |
370 | To compile this driver as a module, choose M here. The module |
371 | will be called forcedeth. | |
1da177e4 | 372 | |
1da177e4 LT |
373 | config FEALNX |
374 | tristate "Myson MTD-8xx PCI Ethernet support" | |
375 | depends on NET_PCI && PCI | |
376 | select CRC32 | |
377 | select MII | |
378 | help | |
631dd1a8 JM |
379 | Say Y here to support the Myson MTD-800 family of PCI-based Ethernet |
380 | cards. <http://www.myson.com.tw/> | |
1da177e4 | 381 | |
1da177e4 LT |
382 | config NET_POCKET |
383 | bool "Pocket and portable adapters" | |
d1c0a65f | 384 | depends on PARPORT |
1da177e4 LT |
385 | ---help--- |
386 | Cute little network (Ethernet) devices which attach to the parallel | |
387 | port ("pocket adapters"), commonly used with laptops. If you have | |
388 | one of those, say Y and read the Ethernet-HOWTO, available from | |
389 | <http://www.tldp.org/docs.html#howto>. | |
390 | ||
391 | If you want to plug a network (or some other) card into the PCMCIA | |
392 | (or PC-card) slot of your laptop instead (PCMCIA is the standard for | |
393 | credit card size extension cards used by all modern laptops), you | |
394 | need the pcmcia-cs package (location contained in the file | |
395 | <file:Documentation/Changes>) and you can say N here. | |
396 | ||
397 | Laptop users should read the Linux Laptop home page at | |
398 | <http://www.linux-on-laptops.com/> or | |
399 | Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. | |
400 | ||
401 | Note that the answer to this question doesn't directly affect the | |
402 | kernel: saying N will just cause the configurator to skip all | |
403 | the questions about this class of network devices. If you say Y, you | |
404 | will be asked for your specific device in the following questions. | |
405 | ||
d1c0a65f | 406 | endif # NET_ETHERNET |
1da177e4 LT |
407 | |
408 | # | |
409 | # Gigabit Ethernet | |
410 | # | |
411 | ||
f30486d5 JE |
412 | menuconfig NETDEV_1000 |
413 | bool "Ethernet (1000 Mbit)" | |
cbcd2a4c | 414 | depends on !UML |
f30486d5 | 415 | default y |
06bfb7eb JE |
416 | ---help--- |
417 | Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common | |
418 | type of Local Area Network (LAN) in universities and companies. | |
419 | ||
420 | Say Y here to get to see options for Gigabit Ethernet drivers. | |
421 | This option alone does not add any kernel code. | |
422 | Note that drivers supporting both 100 and 1000 MBit may be listed | |
423 | under "Ethernet (10 or 100MBit)" instead. | |
424 | ||
425 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
426 | |
427 | if NETDEV_1000 | |
1da177e4 | 428 | |
f30486d5 | 429 | endif # NETDEV_1000 |
1da177e4 LT |
430 | |
431 | # | |
432 | # 10 Gigabit Ethernet | |
433 | # | |
434 | ||
f30486d5 JE |
435 | menuconfig NETDEV_10000 |
436 | bool "Ethernet (10000 Mbit)" | |
cbcd2a4c | 437 | depends on !UML |
f30486d5 | 438 | default y |
06bfb7eb JE |
439 | ---help--- |
440 | Say Y here to get to see options for 10 Gigabit Ethernet drivers. | |
441 | This option alone does not add any kernel code. | |
442 | ||
443 | If you say N, all options in this submenu will be skipped and disabled. | |
f30486d5 JE |
444 | |
445 | if NETDEV_10000 | |
1da177e4 | 446 | |
1b1c2e95 BH |
447 | config MDIO |
448 | tristate | |
449 | ||
5ff2241d JK |
450 | config SUNGEM_PHY |
451 | tristate | |
452 | ||
f30486d5 | 453 | endif # NETDEV_10000 |
1da177e4 | 454 | |
1da177e4 LT |
455 | source "drivers/net/tokenring/Kconfig" |
456 | ||
457 | source "drivers/net/wireless/Kconfig" | |
458 | ||
143ee2d5 IPG |
459 | source "drivers/net/wimax/Kconfig" |
460 | ||
5b2fc499 JG |
461 | source "drivers/net/usb/Kconfig" |
462 | ||
1da177e4 | 463 | source "drivers/net/pcmcia/Kconfig" |
1da177e4 LT |
464 | |
465 | source "drivers/net/wan/Kconfig" | |
466 | ||
467 | source "drivers/atm/Kconfig" | |
468 | ||
8459464f SL |
469 | source "drivers/ieee802154/Kconfig" |
470 | ||
1da177e4 LT |
471 | source "drivers/s390/net/Kconfig" |
472 | ||
9b27105b SB |
473 | source "drivers/net/caif/Kconfig" |
474 | ||
e5a06939 CM |
475 | config TILE_NET |
476 | tristate "Tilera GBE/XGBE network driver support" | |
477 | depends on TILE | |
478 | default y | |
479 | select CRC32 | |
480 | help | |
481 | This is a standard Linux network device driver for the | |
482 | on-chip Tilera Gigabit Ethernet and XAUI interfaces. | |
483 | ||
484 | To compile this driver as a module, choose M here: the module | |
485 | will be called tile_net. | |
486 | ||
0d160211 JF |
487 | config XEN_NETDEV_FRONTEND |
488 | tristate "Xen network device frontend driver" | |
489 | depends on XEN | |
7003087c | 490 | select XEN_XENBUS_FRONTEND |
0d160211 JF |
491 | default y |
492 | help | |
f942dc25 IC |
493 | This driver provides support for Xen paravirtual network |
494 | devices exported by a Xen network driver domain (often | |
495 | domain 0). | |
496 | ||
497 | The corresponding Linux backend driver is enabled by the | |
498 | CONFIG_XEN_NETDEV_BACKEND option. | |
499 | ||
500 | If you are compiling a kernel for use as Xen guest, you | |
501 | should say Y here. To compile this driver as a module, chose | |
502 | M here: the module will be called xen-netfront. | |
503 | ||
504 | config XEN_NETDEV_BACKEND | |
505 | tristate "Xen backend network device" | |
506 | depends on XEN_BACKEND | |
507 | help | |
508 | This driver allows the kernel to act as a Xen network driver | |
509 | domain which exports paravirtual network devices to other | |
510 | Xen domains. These devices can be accessed by any operating | |
511 | system that implements a compatible front end. | |
512 | ||
513 | The corresponding Linux frontend driver is enabled by the | |
514 | CONFIG_XEN_NETDEV_FRONTEND configuration option. | |
515 | ||
516 | The backend driver presents a standard network device | |
517 | endpoint for each paravirtual network device to the driver | |
518 | domain network stack. These can then be bridged or routed | |
519 | etc in order to provide full network connectivity. | |
520 | ||
521 | If you are compiling a kernel to run in a Xen network driver | |
522 | domain (often this is domain 0) you should say Y here. To | |
523 | compile this driver as a module, chose M here: the module | |
524 | will be called xen-netback. | |
0d160211 | 525 | |
f89efd52 MP |
526 | config RIONET |
527 | tristate "RapidIO Ethernet over messaging driver support" | |
a81c52a8 | 528 | depends on RAPIDIO |
f89efd52 MP |
529 | |
530 | config RIONET_TX_SIZE | |
531 | int "Number of outbound queue entries" | |
532 | depends on RIONET | |
533 | default "128" | |
534 | ||
535 | config RIONET_RX_SIZE | |
536 | int "Number of inbound queue entries" | |
537 | depends on RIONET | |
538 | default "128" | |
539 | ||
1da177e4 | 540 | config FDDI |
eb56092f | 541 | tristate "FDDI driver support" |
e89a2cfb | 542 | depends on (PCI || EISA || TC) |
1da177e4 LT |
543 | help |
544 | Fiber Distributed Data Interface is a high speed local area network | |
545 | design; essentially a replacement for high speed Ethernet. FDDI can | |
546 | run over copper or fiber. If you are connected to such a network and | |
547 | want a driver for the FDDI card in your computer, say Y here (and | |
548 | then also Y to the driver for your FDDI card, below). Most people | |
549 | will say N. | |
550 | ||
551 | config DEFXX | |
e89a2cfb MR |
552 | tristate "Digital DEFTA/DEFEA/DEFPA adapter support" |
553 | depends on FDDI && (PCI || EISA || TC) | |
554 | ---help--- | |
555 | This is support for the DIGITAL series of TURBOchannel (DEFTA), | |
556 | EISA (DEFEA) and PCI (DEFPA) controllers which can connect you | |
557 | to a local FDDI network. | |
558 | ||
559 | To compile this driver as a module, choose M here: the module | |
560 | will be called defxx. If unsure, say N. | |
561 | ||
562 | config DEFXX_MMIO | |
563 | bool | |
564 | prompt "Use MMIO instead of PIO" if PCI || EISA | |
565 | depends on DEFXX | |
566 | default n if PCI || EISA | |
567 | default y | |
568 | ---help--- | |
569 | This instructs the driver to use EISA or PCI memory-mapped I/O | |
570 | (MMIO) as appropriate instead of programmed I/O ports (PIO). | |
571 | Enabling this gives an improvement in processing time in parts | |
572 | of the driver, but it may cause problems with EISA (DEFEA) | |
573 | adapters. TURBOchannel does not have the concept of I/O ports, | |
574 | so MMIO is always used for these (DEFTA) adapters. | |
575 | ||
576 | If unsure, say N. | |
1da177e4 LT |
577 | |
578 | config SKFP | |
579 | tristate "SysKonnect FDDI PCI support" | |
580 | depends on FDDI && PCI | |
bc63eb9c | 581 | select BITREVERSE |
1da177e4 LT |
582 | ---help--- |
583 | Say Y here if you have a SysKonnect FDDI PCI adapter. | |
584 | The following adapters are supported by this driver: | |
585 | - SK-5521 (SK-NET FDDI-UP) | |
586 | - SK-5522 (SK-NET FDDI-UP DAS) | |
587 | - SK-5541 (SK-NET FDDI-FP) | |
588 | - SK-5543 (SK-NET FDDI-LP) | |
589 | - SK-5544 (SK-NET FDDI-LP DAS) | |
590 | - SK-5821 (SK-NET FDDI-UP64) | |
591 | - SK-5822 (SK-NET FDDI-UP64 DAS) | |
592 | - SK-5841 (SK-NET FDDI-FP64) | |
593 | - SK-5843 (SK-NET FDDI-LP64) | |
594 | - SK-5844 (SK-NET FDDI-LP64 DAS) | |
595 | - Netelligent 100 FDDI DAS Fibre SC | |
596 | - Netelligent 100 FDDI SAS Fibre SC | |
597 | - Netelligent 100 FDDI DAS UTP | |
598 | - Netelligent 100 FDDI SAS UTP | |
599 | - Netelligent 100 FDDI SAS Fibre MIC | |
600 | ||
601 | Read <file:Documentation/networking/skfp.txt> for information about | |
602 | the driver. | |
603 | ||
604 | Questions concerning this driver can be addressed to: | |
605 | <linux@syskonnect.de> | |
606 | ||
607 | To compile this driver as a module, choose M here: the module | |
608 | will be called skfp. This is recommended. | |
609 | ||
610 | config HIPPI | |
611 | bool "HIPPI driver support (EXPERIMENTAL)" | |
cbcd2a4c | 612 | depends on EXPERIMENTAL && INET && PCI |
1da177e4 LT |
613 | help |
614 | HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and | |
615 | 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI | |
616 | can run over copper (25m) or fiber (300m on multi-mode or 10km on | |
617 | single-mode). HIPPI networks are commonly used for clusters and to | |
618 | connect to super computers. If you are connected to a HIPPI network | |
619 | and have a HIPPI network card in your computer that you want to use | |
620 | under Linux, say Y here (you must also remember to enable the driver | |
621 | for your HIPPI card below). Most people will say N here. | |
622 | ||
623 | config ROADRUNNER | |
624 | tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" | |
625 | depends on HIPPI && PCI | |
626 | help | |
627 | Say Y here if this is your PCI HIPPI network card. | |
628 | ||
629 | To compile this driver as a module, choose M here: the module | |
630 | will be called rrunner. If unsure, say N. | |
631 | ||
632 | config ROADRUNNER_LARGE_RINGS | |
633 | bool "Use large TX/RX rings (EXPERIMENTAL)" | |
634 | depends on ROADRUNNER | |
635 | help | |
636 | If you say Y here, the RoadRunner driver will preallocate up to 2 MB | |
637 | of additional memory to allow for fastest operation, both for | |
638 | transmitting and receiving. This memory cannot be used by any other | |
639 | kernel code or by user space programs. Say Y here only if you have | |
640 | the memory. | |
641 | ||
642 | config PLIP | |
643 | tristate "PLIP (parallel port) support" | |
cbcd2a4c | 644 | depends on PARPORT |
1da177e4 LT |
645 | ---help--- |
646 | PLIP (Parallel Line Internet Protocol) is used to create a | |
647 | reasonably fast mini network consisting of two (or, rarely, more) | |
648 | local machines. A PLIP link from a Linux box is a popular means to | |
649 | install a Linux distribution on a machine which doesn't have a | |
650 | CD-ROM drive (a minimal system has to be transferred with floppies | |
651 | first). The kernels on both machines need to have this PLIP option | |
652 | enabled for this to work. | |
653 | ||
654 | The PLIP driver has two modes, mode 0 and mode 1. The parallel | |
655 | ports (the connectors at the computers with 25 holes) are connected | |
656 | with "null printer" or "Turbo Laplink" cables which can transmit 4 | |
657 | bits at a time (mode 0) or with special PLIP cables, to be used on | |
658 | bidirectional parallel ports only, which can transmit 8 bits at a | |
659 | time (mode 1); you can find the wiring of these cables in | |
660 | <file:Documentation/networking/PLIP.txt>. The cables can be up to | |
661 | 15m long. Mode 0 works also if one of the machines runs DOS/Windows | |
662 | and has some PLIP software installed, e.g. the Crynwr PLIP packet | |
663 | driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) | |
664 | and winsock or NCSA's telnet. | |
665 | ||
666 | If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well | |
667 | as the NET-3-HOWTO, both available from | |
668 | <http://www.tldp.org/docs.html#howto>. Note that the PLIP | |
669 | protocol has been changed and this PLIP driver won't work together | |
670 | with the PLIP support in Linux versions 1.0.x. This option enlarges | |
671 | your kernel by about 8 KB. | |
672 | ||
57ce45dd AB |
673 | To compile this driver as a module, choose M here. The module |
674 | will be called plip. If unsure, say Y or M, in case you buy | |
675 | a laptop later. | |
1da177e4 LT |
676 | |
677 | config PPP | |
678 | tristate "PPP (point-to-point protocol) support" | |
b6e37e55 | 679 | select SLHC |
1da177e4 LT |
680 | ---help--- |
681 | PPP (Point to Point Protocol) is a newer and better SLIP. It serves | |
682 | the same purpose: sending Internet traffic over telephone (and other | |
683 | serial) lines. Ask your access provider if they support it, because | |
684 | otherwise you can't use it; most Internet access providers these | |
685 | days support PPP rather than SLIP. | |
686 | ||
687 | To use PPP, you need an additional program called pppd as described | |
688 | in the PPP-HOWTO, available at | |
689 | <http://www.tldp.org/docs.html#howto>. Make sure that you have | |
690 | the version of pppd recommended in <file:Documentation/Changes>. | |
691 | The PPP option enlarges your kernel by about 16 KB. | |
692 | ||
693 | There are actually two versions of PPP: the traditional PPP for | |
694 | asynchronous lines, such as regular analog phone lines, and | |
695 | synchronous PPP which can be used over digital ISDN lines for | |
696 | example. If you want to use PPP over phone lines or other | |
697 | asynchronous serial lines, you need to say Y (or M) here and also to | |
698 | the next option, "PPP support for async serial ports". For PPP over | |
699 | synchronous lines, you should say Y (or M) here and to "Support | |
700 | synchronous PPP", below. | |
701 | ||
702 | If you said Y to "Version information on all symbols" above, then | |
703 | you cannot compile the PPP driver into the kernel; you can then only | |
704 | compile it as a module. To compile this driver as a module, choose M | |
57ce45dd | 705 | here. The module will be called ppp_generic. |
1da177e4 LT |
706 | |
707 | config PPP_MULTILINK | |
708 | bool "PPP multilink support (EXPERIMENTAL)" | |
709 | depends on PPP && EXPERIMENTAL | |
710 | help | |
711 | PPP multilink is a protocol (defined in RFC 1990) which allows you | |
712 | to combine several (logical or physical) lines into one logical PPP | |
713 | connection, so that you can utilize your full bandwidth. | |
714 | ||
715 | This has to be supported at the other end as well and you need a | |
716 | version of the pppd daemon which understands the multilink protocol. | |
717 | ||
718 | If unsure, say N. | |
719 | ||
720 | config PPP_FILTER | |
721 | bool "PPP filtering" | |
722 | depends on PPP | |
723 | help | |
724 | Say Y here if you want to be able to filter the packets passing over | |
725 | PPP interfaces. This allows you to control which packets count as | |
726 | activity (i.e. which packets will reset the idle timer or bring up | |
47c51431 | 727 | a demand-dialed link) and which packets are to be dropped entirely. |
1da177e4 LT |
728 | You need to say Y here if you wish to use the pass-filter and |
729 | active-filter options to pppd. | |
730 | ||
731 | If unsure, say N. | |
732 | ||
733 | config PPP_ASYNC | |
734 | tristate "PPP support for async serial ports" | |
735 | depends on PPP | |
736 | select CRC_CCITT | |
737 | ---help--- | |
738 | Say Y (or M) here if you want to be able to use PPP over standard | |
739 | asynchronous serial ports, such as COM1 or COM2 on a PC. If you use | |
740 | a modem (not a synchronous or ISDN modem) to contact your ISP, you | |
741 | need this option. | |
742 | ||
743 | To compile this driver as a module, choose M here. | |
744 | ||
745 | If unsure, say Y. | |
746 | ||
747 | config PPP_SYNC_TTY | |
748 | tristate "PPP support for sync tty ports" | |
749 | depends on PPP | |
750 | help | |
751 | Say Y (or M) here if you want to be able to use PPP over synchronous | |
752 | (HDLC) tty devices, such as the SyncLink adapter. These devices | |
753 | are often used for high-speed leased lines like T1/E1. | |
754 | ||
755 | To compile this driver as a module, choose M here. | |
756 | ||
757 | config PPP_DEFLATE | |
758 | tristate "PPP Deflate compression" | |
759 | depends on PPP | |
760 | select ZLIB_INFLATE | |
761 | select ZLIB_DEFLATE | |
762 | ---help--- | |
763 | Support for the Deflate compression method for PPP, which uses the | |
764 | Deflate algorithm (the same algorithm that gzip uses) to compress | |
765 | each PPP packet before it is sent over the wire. The machine at the | |
766 | other end of the PPP link (usually your ISP) has to support the | |
767 | Deflate compression method as well for this to be useful. Even if | |
768 | they don't support it, it is safe to say Y here. | |
769 | ||
770 | To compile this driver as a module, choose M here. | |
771 | ||
772 | config PPP_BSDCOMP | |
773 | tristate "PPP BSD-Compress compression" | |
774 | depends on PPP | |
775 | ---help--- | |
776 | Support for the BSD-Compress compression method for PPP, which uses | |
777 | the LZW compression method to compress each PPP packet before it is | |
778 | sent over the wire. The machine at the other end of the PPP link | |
779 | (usually your ISP) has to support the BSD-Compress compression | |
780 | method as well for this to be useful. Even if they don't support it, | |
781 | it is safe to say Y here. | |
782 | ||
783 | The PPP Deflate compression method ("PPP Deflate compression", | |
784 | above) is preferable to BSD-Compress, because it compresses better | |
785 | and is patent-free. | |
786 | ||
787 | Note that the BSD compression code will always be compiled as a | |
788 | module; it is called bsd_comp and will show up in the directory | |
789 | modules once you have said "make modules". If unsure, say N. | |
790 | ||
b3f9b92a | 791 | config PPP_MPPE |
e85eb117 PDM |
792 | tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" |
793 | depends on PPP && EXPERIMENTAL | |
794 | select CRYPTO | |
795 | select CRYPTO_SHA1 | |
796 | select CRYPTO_ARC4 | |
797 | select CRYPTO_ECB | |
798 | ---help--- | |
799 | Support for the MPPE Encryption protocol, as employed by the | |
800 | Microsoft Point-to-Point Tunneling Protocol. | |
801 | ||
802 | See http://pptpclient.sourceforge.net/ for information on | |
803 | configuring PPTP clients and servers to utilize this method. | |
b3f9b92a | 804 | |
1da177e4 LT |
805 | config PPPOE |
806 | tristate "PPP over Ethernet (EXPERIMENTAL)" | |
807 | depends on EXPERIMENTAL && PPP | |
808 | help | |
809 | Support for PPP over Ethernet. | |
810 | ||
811 | This driver requires the latest version of pppd from the CVS | |
812 | repository at cvs.samba.org. Alternatively, see the | |
813 | RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) | |
814 | which contains instruction on how to use this driver (under | |
815 | the heading "Kernel mode PPPoE"). | |
816 | ||
00959ade DK |
817 | config PPTP |
818 | tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" | |
819 | depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX | |
820 | help | |
821 | Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) | |
822 | ||
823 | This driver requires pppd plugin to work in client mode or | |
824 | modified pptpd (poptop) to work in server mode. | |
825 | See http://accel-pptp.sourceforge.net/ for information how to | |
826 | utilize this module. | |
827 | ||
1da177e4 LT |
828 | config PPPOATM |
829 | tristate "PPP over ATM" | |
830 | depends on ATM && PPP | |
831 | help | |
832 | Support PPP (Point to Point Protocol) encapsulated in ATM frames. | |
833 | This implementation does not yet comply with section 8 of RFC2364, | |
834 | which can lead to bad results if the ATM peer loses state and | |
835 | changes its encapsulation unilaterally. | |
836 | ||
3557baab JC |
837 | config PPPOL2TP |
838 | tristate "PPP over L2TP (EXPERIMENTAL)" | |
fd558d18 | 839 | depends on EXPERIMENTAL && L2TP && PPP |
3557baab JC |
840 | help |
841 | Support for PPP-over-L2TP socket family. L2TP is a protocol | |
842 | used by ISPs and enterprises to tunnel PPP traffic over UDP | |
843 | tunnels. L2TP is replacing PPTP for VPN uses. | |
844 | ||
1da177e4 LT |
845 | config SLIP |
846 | tristate "SLIP (serial line) support" | |
1da177e4 LT |
847 | ---help--- |
848 | Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to | |
849 | connect to your Internet service provider or to connect to some | |
850 | other local Unix box or if you want to configure your Linux box as a | |
851 | Slip/CSlip server for other people to dial in. SLIP (Serial Line | |
852 | Internet Protocol) is a protocol used to send Internet traffic over | |
853 | serial connections such as telephone lines or null modem cables; | |
854 | nowadays, the protocol PPP is more commonly used for this same | |
855 | purpose. | |
856 | ||
857 | Normally, your access provider has to support SLIP in order for you | |
858 | to be able to use it, but there is now a SLIP emulator called SLiRP | |
859 | around (available from | |
860 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
861 | allows you to use SLIP over a regular dial up shell connection. If | |
862 | you plan to use SLiRP, make sure to say Y to CSLIP, below. The | |
863 | NET-3-HOWTO, available from | |
864 | <http://www.tldp.org/docs.html#howto>, explains how to | |
865 | configure SLIP. Note that you don't need this option if you just | |
866 | want to run term (term is a program which gives you almost full | |
867 | Internet connectivity if you have a regular dial up shell account on | |
868 | some Internet connected Unix computer. Read | |
869 | <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP | |
870 | support will enlarge your kernel by about 4 KB. If unsure, say N. | |
871 | ||
57ce45dd AB |
872 | To compile this driver as a module, choose M here. The module |
873 | will be called slip. | |
1da177e4 LT |
874 | |
875 | config SLIP_COMPRESSED | |
876 | bool "CSLIP compressed headers" | |
877 | depends on SLIP | |
b6e37e55 | 878 | select SLHC |
1da177e4 LT |
879 | ---help--- |
880 | This protocol is faster than SLIP because it uses compression on the | |
881 | TCP/IP headers (not on the data itself), but it has to be supported | |
882 | on both ends. Ask your access provider if you are not sure and | |
883 | answer Y, just in case. You will still be able to use plain SLIP. If | |
884 | you plan to use SLiRP, the SLIP emulator (available from | |
885 | <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which | |
886 | allows you to use SLIP over a regular dial up shell connection, you | |
887 | definitely want to say Y here. The NET-3-HOWTO, available from | |
888 | <http://www.tldp.org/docs.html#howto>, explains how to configure | |
889 | CSLIP. This won't enlarge your kernel. | |
890 | ||
b6e37e55 RB |
891 | config SLHC |
892 | tristate | |
893 | help | |
894 | This option enables Van Jacobsen serial line header compression | |
895 | routines. | |
896 | ||
1da177e4 LT |
897 | config SLIP_SMART |
898 | bool "Keepalive and linefill" | |
899 | depends on SLIP | |
900 | help | |
901 | Adds additional capabilities to the SLIP driver to support the | |
902 | RELCOM line fill and keepalive monitoring. Ideal on poor quality | |
903 | analogue lines. | |
904 | ||
905 | config SLIP_MODE_SLIP6 | |
906 | bool "Six bit SLIP encapsulation" | |
907 | depends on SLIP | |
908 | help | |
909 | Just occasionally you may need to run IP over hostile serial | |
910 | networks that don't pass all control characters or are only seven | |
911 | bit. Saying Y here adds an extra mode you can use with SLIP: | |
912 | "slip6". In this mode, SLIP will only send normal ASCII symbols over | |
913 | the serial device. Naturally, this has to be supported at the other | |
914 | end of the link as well. It's good enough, for example, to run IP | |
915 | over the async ports of a Camtec JNT Pad. If unsure, say N. | |
916 | ||
917 | config NET_FC | |
918 | bool "Fibre Channel driver support" | |
cbcd2a4c | 919 | depends on SCSI && PCI |
1da177e4 LT |
920 | help |
921 | Fibre Channel is a high speed serial protocol mainly used to connect | |
922 | large storage devices to the computer; it is compatible with and | |
923 | intended to replace SCSI. | |
924 | ||
925 | If you intend to use Fibre Channel, you need to have a Fibre channel | |
926 | adaptor card in your computer; say Y here and to the driver for your | |
927 | adaptor below. You also should have said Y to "SCSI support" and | |
928 | "SCSI generic support". | |
929 | ||
1da177e4 | 930 | config NETCONSOLE |
ecbacf8d | 931 | tristate "Network console logging support" |
1da177e4 LT |
932 | ---help--- |
933 | If you want to log kernel messages over the network, enable this. | |
934 | See <file:Documentation/networking/netconsole.txt> for details. | |
935 | ||
0bcc1816 | 936 | config NETCONSOLE_DYNAMIC |
ecbacf8d | 937 | bool "Dynamic reconfiguration of logging targets" |
58fa4597 RD |
938 | depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ |
939 | !(NETCONSOLE=y && CONFIGFS_FS=m) | |
0bcc1816 SS |
940 | help |
941 | This option enables the ability to dynamically reconfigure target | |
942 | parameters (interface, IP addresses, port numbers, MAC addresses) | |
943 | at runtime through a userspace interface exported using configfs. | |
944 | See <file:Documentation/networking/netconsole.txt> for details. | |
945 | ||
54208991 RD |
946 | config NETPOLL |
947 | def_bool NETCONSOLE | |
948 | ||
54208991 RD |
949 | config NETPOLL_TRAP |
950 | bool "Netpoll traffic trapping" | |
951 | default n | |
952 | depends on NETPOLL | |
953 | ||
954 | config NET_POLL_CONTROLLER | |
955 | def_bool NETPOLL | |
956 | ||
296f96fc RR |
957 | config VIRTIO_NET |
958 | tristate "Virtio network driver (EXPERIMENTAL)" | |
959 | depends on EXPERIMENTAL && VIRTIO | |
960 | ---help--- | |
0ad07ec1 | 961 | This is the virtual network driver for virtio. It can be used with |
e85eb117 | 962 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. |
296f96fc | 963 | |
d1a890fa | 964 | config VMXNET3 |
e85eb117 PDM |
965 | tristate "VMware VMXNET3 ethernet driver" |
966 | depends on PCI && INET | |
967 | help | |
968 | This driver supports VMware's vmxnet3 virtual ethernet NIC. | |
969 | To compile this driver as a module, choose M here: the | |
970 | module will be called vmxnet3. | |
d1a890fa | 971 | |
d1c0a65f | 972 | endif # NETDEVICES |