Kconfig revision b544dbac41218fd015ac79455cfc1e57736e9b0c
1# 2# Network device configuration 3# 4 5config HAVE_NET_MACB 6 bool 7 8menuconfig NETDEVICES 9 default y if UML 10 depends on NET 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 27# All the following symbols are dependent on NETDEVICES - do not repeat 28# that for each of the symbols. 29if NETDEVICES 30 31config IFB 32 tristate "Intermediate Functional Block support" 33 depends on NET_CLS_ACT 34 ---help--- 35 This is an intermediate driver that allows sharing of 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 44config DUMMY 45 tristate "Dummy net driver support" 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 63config BONDING 64 tristate "Bonding driver support" 65 depends on INET 66 depends on IPV6 || IPV6=n 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 73 performance and high availability operation. 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 81config 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 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 93 To compile this driver as a module, choose M here: the module 94 will be called macvlan. 95 96config 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 108config EQUALIZER 109 tristate "EQL (serial line load balancing) support" 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 127config TUN 128 tristate "Universal TUN/TAP device driver support" 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 150config VETH 151 tristate "Virtual ethernet pair device" 152 ---help--- 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. 156 157config NET_SB1000 158 tristate "General Instruments Surfboard 1000" 159 depends on PNP 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 181source "drivers/net/arcnet/Kconfig" 182 183config 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 190source "drivers/net/phy/Kconfig" 191 192# 193# Ethernet 194# 195 196source "drivers/net/ethernet/Kconfig" 197 198menuconfig NET_ETHERNET 199 bool "Ethernet (10 or 100Mbit)" 200 depends on !UML 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 225if NET_ETHERNET 226 227config MACB 228 tristate "Atmel MACB support" 229 depends on HAVE_NET_MACB 230 select PHYLIB 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 238source "drivers/net/arm/Kconfig" 239 240config KORINA 241 tristate "Korina (IDT RC32434) Ethernet support" 242 depends on NET_ETHERNET && MIKROTIK_RB532 243 help 244 If you have a Mikrotik RouterBoard 500 or IDT RC32434 245 based system say Y. Otherwise say N. 246 247config MIPS_SIM_NET 248 tristate "MIPS simulator Network device" 249 depends on MIPS_SIM 250 help 251 The MIPSNET device is a simple Ethernet network device which is 252 emulated by the MIPS Simulator. 253 If you are not using a MIPSsim or are unsure, say N. 254 255config SH_ETH 256 tristate "Renesas SuperH Ethernet support" 257 depends on SUPERH && \ 258 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ 259 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ 260 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757) 261 select CRC32 262 select MII 263 select MDIO_BITBANG 264 select PHYLIB 265 help 266 Renesas SuperH Ethernet device driver. 267 This driver supporting CPUs are: 268 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757. 269 270config BFIN_MAC 271 tristate "Blackfin on-chip MAC support" 272 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) 273 select CRC32 274 select MII 275 select PHYLIB 276 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE 277 help 278 This is the driver for Blackfin on-chip mac device. Say Y if you want it 279 compiled into the kernel. This driver is also available as a module 280 ( = code which can be inserted in and removed from the running kernel 281 whenever you want). The module will be called bfin_mac. 282 283config BFIN_MAC_USE_L1 284 bool "Use L1 memory for rx/tx packets" 285 depends on BFIN_MAC && (BF527 || BF537) 286 default y 287 help 288 To get maximum network performance, you should use L1 memory as rx/tx buffers. 289 Say N here if you want to reserve L1 memory for other uses. 290 291config BFIN_TX_DESC_NUM 292 int "Number of transmit buffer packets" 293 depends on BFIN_MAC 294 range 6 10 if BFIN_MAC_USE_L1 295 range 10 100 296 default "10" 297 help 298 Set the number of buffer packets used in driver. 299 300config BFIN_RX_DESC_NUM 301 int "Number of receive buffer packets" 302 depends on BFIN_MAC 303 range 20 100 if BFIN_MAC_USE_L1 304 range 20 800 305 default "20" 306 help 307 Set the number of buffer packets used in driver. 308 309config BFIN_MAC_USE_HWSTAMP 310 bool "Use IEEE 1588 hwstamp" 311 depends on BFIN_MAC && BF518 312 default y 313 help 314 To support the IEEE 1588 Precision Time Protocol (PTP), select y here 315 316config NET_NETX 317 tristate "NetX Ethernet support" 318 select MII 319 depends on ARCH_NETX 320 help 321 This is support for the Hilscher netX builtin Ethernet ports 322 323 To compile this driver as a module, choose M here. The module 324 will be called netx-eth. 325 326config DM9000 327 tristate "DM9000 support" 328 depends on ARM || BLACKFIN || MIPS 329 select CRC32 330 select MII 331 ---help--- 332 Support for DM9000 chipset. 333 334 To compile this driver as a module, choose M here. The module 335 will be called dm9000. 336 337config DM9000_DEBUGLEVEL 338 int "DM9000 maximum debug level" 339 depends on DM9000 340 default 4 341 help 342 The maximum level of debugging code compiled into the DM9000 343 driver. 344 345config DM9000_FORCE_SIMPLE_PHY_POLL 346 bool "Force simple NSR based PHY polling" 347 depends on DM9000 348 ---help--- 349 This configuration forces the DM9000 to use the NSR's LinkStatus 350 bit to determine if the link is up or down instead of the more 351 costly MII PHY reads. Note, this will not work if the chip is 352 operating with an external PHY. 353 354config ENC28J60 355 tristate "ENC28J60 support" 356 depends on EXPERIMENTAL && SPI && NET_ETHERNET 357 select CRC32 358 ---help--- 359 Support for the Microchip EN28J60 ethernet chip. 360 361 To compile this driver as a module, choose M here. The module will be 362 called enc28j60. 363 364config ENC28J60_WRITEVERIFY 365 bool "Enable write verify" 366 depends on ENC28J60 367 ---help--- 368 Enable the verify after the buffer write useful for debugging purpose. 369 If unsure, say N. 370 371config ETHOC 372 tristate "OpenCores 10/100 Mbps Ethernet MAC support" 373 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA 374 select MII 375 select PHYLIB 376 select CRC32 377 select BITREVERSE 378 help 379 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. 380 381config GRETH 382 tristate "Aeroflex Gaisler GRETH Ethernet MAC support" 383 depends on SPARC 384 select PHYLIB 385 select CRC32 386 help 387 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. 388 389config DNET 390 tristate "Dave ethernet support (DNET)" 391 depends on NET_ETHERNET && HAS_IOMEM 392 select PHYLIB 393 help 394 The Dave ethernet interface (DNET) is found on Qong Board FPGA. 395 Say Y to include support for the DNET chip. 396 397 To compile this driver as a module, choose M here: the module 398 will be called dnet. 399 400config HP100 401 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 402 depends on ISA || EISA || PCI 403 help 404 If you have a network (Ethernet) card of this type, say Y and read 405 the Ethernet-HOWTO, available from 406 <http://www.tldp.org/docs.html#howto>. 407 408 To compile this driver as a module, choose M here. The module 409 will be called hp100. 410 411config NET_PCI 412 bool "EISA, VLB, PCI and on board controllers" 413 depends on ISA || EISA || PCI 414 help 415 This is another class of network cards which attach directly to the 416 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 417 available from <http://www.tldp.org/docs.html#howto>. 418 419 Note that the answer to this question doesn't directly affect the 420 kernel: saying N will just cause the configurator to skip all 421 the questions about this class of network cards. If you say Y, you 422 will be asked for your specific card in the following questions. If 423 you are unsure, say Y. 424 425config ADAPTEC_STARFIRE 426 tristate "Adaptec Starfire/DuraLAN support" 427 depends on NET_PCI && PCI 428 select CRC32 429 select MII 430 help 431 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 432 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 433 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 434 driver. 435 436 To compile this driver as a module, choose M here: the module 437 will be called starfire. This is recommended. 438 439config FORCEDETH 440 tristate "nForce Ethernet support" 441 depends on NET_PCI && PCI 442 help 443 If you have a network (Ethernet) controller of this type, say Y and 444 read the Ethernet-HOWTO, available from 445 <http://www.tldp.org/docs.html#howto>. 446 447 To compile this driver as a module, choose M here. The module 448 will be called forcedeth. 449 450config FEALNX 451 tristate "Myson MTD-8xx PCI Ethernet support" 452 depends on NET_PCI && PCI 453 select CRC32 454 select MII 455 help 456 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet 457 cards. <http://www.myson.com.tw/> 458 459config R6040 460 tristate "RDC R6040 Fast Ethernet Adapter support" 461 depends on NET_PCI && PCI 462 select CRC32 463 select MII 464 select PHYLIB 465 help 466 This is a driver for the R6040 Fast Ethernet MACs found in the 467 the RDC R-321x System-on-chips. 468 469 To compile this driver as a module, choose M here: the module 470 will be called r6040. This is recommended. 471 472config NET_POCKET 473 bool "Pocket and portable adapters" 474 depends on PARPORT 475 ---help--- 476 Cute little network (Ethernet) devices which attach to the parallel 477 port ("pocket adapters"), commonly used with laptops. If you have 478 one of those, say Y and read the Ethernet-HOWTO, available from 479 <http://www.tldp.org/docs.html#howto>. 480 481 If you want to plug a network (or some other) card into the PCMCIA 482 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 483 credit card size extension cards used by all modern laptops), you 484 need the pcmcia-cs package (location contained in the file 485 <file:Documentation/Changes>) and you can say N here. 486 487 Laptop users should read the Linux Laptop home page at 488 <http://www.linux-on-laptops.com/> or 489 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 490 491 Note that the answer to this question doesn't directly affect the 492 kernel: saying N will just cause the configurator to skip all 493 the questions about this class of network devices. If you say Y, you 494 will be asked for your specific device in the following questions. 495 496config XILINX_EMACLITE 497 tristate "Xilinx 10/100 Ethernet Lite support" 498 depends on PPC32 || MICROBLAZE 499 select PHYLIB 500 help 501 This driver supports the 10/100 Ethernet Lite from Xilinx. 502 503config LANTIQ_ETOP 504 tristate "Lantiq SoC ETOP driver" 505 depends on SOC_TYPE_XWAY 506 help 507 Support for the MII0 inside the Lantiq SoC 508 509source "drivers/net/octeon/Kconfig" 510 511endif # NET_ETHERNET 512 513# 514# Gigabit Ethernet 515# 516 517menuconfig NETDEV_1000 518 bool "Ethernet (1000 Mbit)" 519 depends on !UML 520 default y 521 ---help--- 522 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 523 type of Local Area Network (LAN) in universities and companies. 524 525 Say Y here to get to see options for Gigabit Ethernet drivers. 526 This option alone does not add any kernel code. 527 Note that drivers supporting both 100 and 1000 MBit may be listed 528 under "Ethernet (10 or 100MBit)" instead. 529 530 If you say N, all options in this submenu will be skipped and disabled. 531 532if NETDEV_1000 533 534config IP1000 535 tristate "IP1000 Gigabit Ethernet support" 536 depends on PCI && EXPERIMENTAL 537 select MII 538 ---help--- 539 This driver supports IP1000 gigabit Ethernet cards. 540 541 To compile this driver as a module, choose M here: the module 542 will be called ipg. This is recommended. 543 544config HAMACHI 545 tristate "Packet Engines Hamachi GNIC-II support" 546 depends on PCI 547 select MII 548 help 549 If you have a Gigabit Ethernet card of this type, say Y and read 550 the Ethernet-HOWTO, available from 551 <http://www.tldp.org/docs.html#howto>. 552 553 To compile this driver as a module, choose M here. The module will be 554 called hamachi. 555 556config YELLOWFIN 557 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 558 depends on PCI && EXPERIMENTAL 559 select CRC32 560 ---help--- 561 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 562 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 563 used by the Beowulf Linux cluster project. See 564 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 565 information about this driver in particular and Beowulf in general. 566 567 To compile this driver as a module, choose M here: the module 568 will be called yellowfin. This is recommended. 569 570config XILINX_LL_TEMAC 571 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" 572 depends on PPC || MICROBLAZE 573 select PHYLIB 574 help 575 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC 576 core used in Xilinx Spartan and Virtex FPGAs 577 578config JME 579 tristate "JMicron(R) PCI-Express Gigabit Ethernet support" 580 depends on PCI 581 select CRC32 582 select MII 583 ---help--- 584 This driver supports the PCI-Express gigabit ethernet adapters 585 based on JMicron JMC250 chipset. 586 587 To compile this driver as a module, choose M here. The module 588 will be called jme. 589 590endif # NETDEV_1000 591 592# 593# 10 Gigabit Ethernet 594# 595 596menuconfig NETDEV_10000 597 bool "Ethernet (10000 Mbit)" 598 depends on !UML 599 default y 600 ---help--- 601 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 602 This option alone does not add any kernel code. 603 604 If you say N, all options in this submenu will be skipped and disabled. 605 606if NETDEV_10000 607 608config MDIO 609 tristate 610 611config SUNGEM_PHY 612 tristate 613 614endif # NETDEV_10000 615 616source "drivers/net/tokenring/Kconfig" 617 618source "drivers/net/wireless/Kconfig" 619 620source "drivers/net/wimax/Kconfig" 621 622source "drivers/net/usb/Kconfig" 623 624source "drivers/net/pcmcia/Kconfig" 625 626source "drivers/net/wan/Kconfig" 627 628source "drivers/atm/Kconfig" 629 630source "drivers/ieee802154/Kconfig" 631 632source "drivers/s390/net/Kconfig" 633 634source "drivers/net/caif/Kconfig" 635 636config TILE_NET 637 tristate "Tilera GBE/XGBE network driver support" 638 depends on TILE 639 default y 640 select CRC32 641 help 642 This is a standard Linux network device driver for the 643 on-chip Tilera Gigabit Ethernet and XAUI interfaces. 644 645 To compile this driver as a module, choose M here: the module 646 will be called tile_net. 647 648config XEN_NETDEV_FRONTEND 649 tristate "Xen network device frontend driver" 650 depends on XEN 651 select XEN_XENBUS_FRONTEND 652 default y 653 help 654 This driver provides support for Xen paravirtual network 655 devices exported by a Xen network driver domain (often 656 domain 0). 657 658 The corresponding Linux backend driver is enabled by the 659 CONFIG_XEN_NETDEV_BACKEND option. 660 661 If you are compiling a kernel for use as Xen guest, you 662 should say Y here. To compile this driver as a module, chose 663 M here: the module will be called xen-netfront. 664 665config XEN_NETDEV_BACKEND 666 tristate "Xen backend network device" 667 depends on XEN_BACKEND 668 help 669 This driver allows the kernel to act as a Xen network driver 670 domain which exports paravirtual network devices to other 671 Xen domains. These devices can be accessed by any operating 672 system that implements a compatible front end. 673 674 The corresponding Linux frontend driver is enabled by the 675 CONFIG_XEN_NETDEV_FRONTEND configuration option. 676 677 The backend driver presents a standard network device 678 endpoint for each paravirtual network device to the driver 679 domain network stack. These can then be bridged or routed 680 etc in order to provide full network connectivity. 681 682 If you are compiling a kernel to run in a Xen network driver 683 domain (often this is domain 0) you should say Y here. To 684 compile this driver as a module, chose M here: the module 685 will be called xen-netback. 686 687config RIONET 688 tristate "RapidIO Ethernet over messaging driver support" 689 depends on RAPIDIO 690 691config RIONET_TX_SIZE 692 int "Number of outbound queue entries" 693 depends on RIONET 694 default "128" 695 696config RIONET_RX_SIZE 697 int "Number of inbound queue entries" 698 depends on RIONET 699 default "128" 700 701config FDDI 702 tristate "FDDI driver support" 703 depends on (PCI || EISA || TC) 704 help 705 Fiber Distributed Data Interface is a high speed local area network 706 design; essentially a replacement for high speed Ethernet. FDDI can 707 run over copper or fiber. If you are connected to such a network and 708 want a driver for the FDDI card in your computer, say Y here (and 709 then also Y to the driver for your FDDI card, below). Most people 710 will say N. 711 712config DEFXX 713 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 714 depends on FDDI && (PCI || EISA || TC) 715 ---help--- 716 This is support for the DIGITAL series of TURBOchannel (DEFTA), 717 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 718 to a local FDDI network. 719 720 To compile this driver as a module, choose M here: the module 721 will be called defxx. If unsure, say N. 722 723config DEFXX_MMIO 724 bool 725 prompt "Use MMIO instead of PIO" if PCI || EISA 726 depends on DEFXX 727 default n if PCI || EISA 728 default y 729 ---help--- 730 This instructs the driver to use EISA or PCI memory-mapped I/O 731 (MMIO) as appropriate instead of programmed I/O ports (PIO). 732 Enabling this gives an improvement in processing time in parts 733 of the driver, but it may cause problems with EISA (DEFEA) 734 adapters. TURBOchannel does not have the concept of I/O ports, 735 so MMIO is always used for these (DEFTA) adapters. 736 737 If unsure, say N. 738 739config SKFP 740 tristate "SysKonnect FDDI PCI support" 741 depends on FDDI && PCI 742 select BITREVERSE 743 ---help--- 744 Say Y here if you have a SysKonnect FDDI PCI adapter. 745 The following adapters are supported by this driver: 746 - SK-5521 (SK-NET FDDI-UP) 747 - SK-5522 (SK-NET FDDI-UP DAS) 748 - SK-5541 (SK-NET FDDI-FP) 749 - SK-5543 (SK-NET FDDI-LP) 750 - SK-5544 (SK-NET FDDI-LP DAS) 751 - SK-5821 (SK-NET FDDI-UP64) 752 - SK-5822 (SK-NET FDDI-UP64 DAS) 753 - SK-5841 (SK-NET FDDI-FP64) 754 - SK-5843 (SK-NET FDDI-LP64) 755 - SK-5844 (SK-NET FDDI-LP64 DAS) 756 - Netelligent 100 FDDI DAS Fibre SC 757 - Netelligent 100 FDDI SAS Fibre SC 758 - Netelligent 100 FDDI DAS UTP 759 - Netelligent 100 FDDI SAS UTP 760 - Netelligent 100 FDDI SAS Fibre MIC 761 762 Read <file:Documentation/networking/skfp.txt> for information about 763 the driver. 764 765 Questions concerning this driver can be addressed to: 766 <linux@syskonnect.de> 767 768 To compile this driver as a module, choose M here: the module 769 will be called skfp. This is recommended. 770 771config HIPPI 772 bool "HIPPI driver support (EXPERIMENTAL)" 773 depends on EXPERIMENTAL && INET && PCI 774 help 775 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 776 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 777 can run over copper (25m) or fiber (300m on multi-mode or 10km on 778 single-mode). HIPPI networks are commonly used for clusters and to 779 connect to super computers. If you are connected to a HIPPI network 780 and have a HIPPI network card in your computer that you want to use 781 under Linux, say Y here (you must also remember to enable the driver 782 for your HIPPI card below). Most people will say N here. 783 784config ROADRUNNER 785 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 786 depends on HIPPI && PCI 787 help 788 Say Y here if this is your PCI HIPPI network card. 789 790 To compile this driver as a module, choose M here: the module 791 will be called rrunner. If unsure, say N. 792 793config ROADRUNNER_LARGE_RINGS 794 bool "Use large TX/RX rings (EXPERIMENTAL)" 795 depends on ROADRUNNER 796 help 797 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 798 of additional memory to allow for fastest operation, both for 799 transmitting and receiving. This memory cannot be used by any other 800 kernel code or by user space programs. Say Y here only if you have 801 the memory. 802 803config PLIP 804 tristate "PLIP (parallel port) support" 805 depends on PARPORT 806 ---help--- 807 PLIP (Parallel Line Internet Protocol) is used to create a 808 reasonably fast mini network consisting of two (or, rarely, more) 809 local machines. A PLIP link from a Linux box is a popular means to 810 install a Linux distribution on a machine which doesn't have a 811 CD-ROM drive (a minimal system has to be transferred with floppies 812 first). The kernels on both machines need to have this PLIP option 813 enabled for this to work. 814 815 The PLIP driver has two modes, mode 0 and mode 1. The parallel 816 ports (the connectors at the computers with 25 holes) are connected 817 with "null printer" or "Turbo Laplink" cables which can transmit 4 818 bits at a time (mode 0) or with special PLIP cables, to be used on 819 bidirectional parallel ports only, which can transmit 8 bits at a 820 time (mode 1); you can find the wiring of these cables in 821 <file:Documentation/networking/PLIP.txt>. The cables can be up to 822 15m long. Mode 0 works also if one of the machines runs DOS/Windows 823 and has some PLIP software installed, e.g. the Crynwr PLIP packet 824 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 825 and winsock or NCSA's telnet. 826 827 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 828 as the NET-3-HOWTO, both available from 829 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 830 protocol has been changed and this PLIP driver won't work together 831 with the PLIP support in Linux versions 1.0.x. This option enlarges 832 your kernel by about 8 KB. 833 834 To compile this driver as a module, choose M here. The module 835 will be called plip. If unsure, say Y or M, in case you buy 836 a laptop later. 837 838config PPP 839 tristate "PPP (point-to-point protocol) support" 840 select SLHC 841 ---help--- 842 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 843 the same purpose: sending Internet traffic over telephone (and other 844 serial) lines. Ask your access provider if they support it, because 845 otherwise you can't use it; most Internet access providers these 846 days support PPP rather than SLIP. 847 848 To use PPP, you need an additional program called pppd as described 849 in the PPP-HOWTO, available at 850 <http://www.tldp.org/docs.html#howto>. Make sure that you have 851 the version of pppd recommended in <file:Documentation/Changes>. 852 The PPP option enlarges your kernel by about 16 KB. 853 854 There are actually two versions of PPP: the traditional PPP for 855 asynchronous lines, such as regular analog phone lines, and 856 synchronous PPP which can be used over digital ISDN lines for 857 example. If you want to use PPP over phone lines or other 858 asynchronous serial lines, you need to say Y (or M) here and also to 859 the next option, "PPP support for async serial ports". For PPP over 860 synchronous lines, you should say Y (or M) here and to "Support 861 synchronous PPP", below. 862 863 If you said Y to "Version information on all symbols" above, then 864 you cannot compile the PPP driver into the kernel; you can then only 865 compile it as a module. To compile this driver as a module, choose M 866 here. The module will be called ppp_generic. 867 868config PPP_MULTILINK 869 bool "PPP multilink support (EXPERIMENTAL)" 870 depends on PPP && EXPERIMENTAL 871 help 872 PPP multilink is a protocol (defined in RFC 1990) which allows you 873 to combine several (logical or physical) lines into one logical PPP 874 connection, so that you can utilize your full bandwidth. 875 876 This has to be supported at the other end as well and you need a 877 version of the pppd daemon which understands the multilink protocol. 878 879 If unsure, say N. 880 881config PPP_FILTER 882 bool "PPP filtering" 883 depends on PPP 884 help 885 Say Y here if you want to be able to filter the packets passing over 886 PPP interfaces. This allows you to control which packets count as 887 activity (i.e. which packets will reset the idle timer or bring up 888 a demand-dialed link) and which packets are to be dropped entirely. 889 You need to say Y here if you wish to use the pass-filter and 890 active-filter options to pppd. 891 892 If unsure, say N. 893 894config PPP_ASYNC 895 tristate "PPP support for async serial ports" 896 depends on PPP 897 select CRC_CCITT 898 ---help--- 899 Say Y (or M) here if you want to be able to use PPP over standard 900 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 901 a modem (not a synchronous or ISDN modem) to contact your ISP, you 902 need this option. 903 904 To compile this driver as a module, choose M here. 905 906 If unsure, say Y. 907 908config PPP_SYNC_TTY 909 tristate "PPP support for sync tty ports" 910 depends on PPP 911 help 912 Say Y (or M) here if you want to be able to use PPP over synchronous 913 (HDLC) tty devices, such as the SyncLink adapter. These devices 914 are often used for high-speed leased lines like T1/E1. 915 916 To compile this driver as a module, choose M here. 917 918config PPP_DEFLATE 919 tristate "PPP Deflate compression" 920 depends on PPP 921 select ZLIB_INFLATE 922 select ZLIB_DEFLATE 923 ---help--- 924 Support for the Deflate compression method for PPP, which uses the 925 Deflate algorithm (the same algorithm that gzip uses) to compress 926 each PPP packet before it is sent over the wire. The machine at the 927 other end of the PPP link (usually your ISP) has to support the 928 Deflate compression method as well for this to be useful. Even if 929 they don't support it, it is safe to say Y here. 930 931 To compile this driver as a module, choose M here. 932 933config PPP_BSDCOMP 934 tristate "PPP BSD-Compress compression" 935 depends on PPP 936 ---help--- 937 Support for the BSD-Compress compression method for PPP, which uses 938 the LZW compression method to compress each PPP packet before it is 939 sent over the wire. The machine at the other end of the PPP link 940 (usually your ISP) has to support the BSD-Compress compression 941 method as well for this to be useful. Even if they don't support it, 942 it is safe to say Y here. 943 944 The PPP Deflate compression method ("PPP Deflate compression", 945 above) is preferable to BSD-Compress, because it compresses better 946 and is patent-free. 947 948 Note that the BSD compression code will always be compiled as a 949 module; it is called bsd_comp and will show up in the directory 950 modules once you have said "make modules". If unsure, say N. 951 952config PPP_MPPE 953 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 954 depends on PPP && EXPERIMENTAL 955 select CRYPTO 956 select CRYPTO_SHA1 957 select CRYPTO_ARC4 958 select CRYPTO_ECB 959 ---help--- 960 Support for the MPPE Encryption protocol, as employed by the 961 Microsoft Point-to-Point Tunneling Protocol. 962 963 See http://pptpclient.sourceforge.net/ for information on 964 configuring PPTP clients and servers to utilize this method. 965 966config PPPOE 967 tristate "PPP over Ethernet (EXPERIMENTAL)" 968 depends on EXPERIMENTAL && PPP 969 help 970 Support for PPP over Ethernet. 971 972 This driver requires the latest version of pppd from the CVS 973 repository at cvs.samba.org. Alternatively, see the 974 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 975 which contains instruction on how to use this driver (under 976 the heading "Kernel mode PPPoE"). 977 978config PPTP 979 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" 980 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX 981 help 982 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) 983 984 This driver requires pppd plugin to work in client mode or 985 modified pptpd (poptop) to work in server mode. 986 See http://accel-pptp.sourceforge.net/ for information how to 987 utilize this module. 988 989config PPPOATM 990 tristate "PPP over ATM" 991 depends on ATM && PPP 992 help 993 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 994 This implementation does not yet comply with section 8 of RFC2364, 995 which can lead to bad results if the ATM peer loses state and 996 changes its encapsulation unilaterally. 997 998config PPPOL2TP 999 tristate "PPP over L2TP (EXPERIMENTAL)" 1000 depends on EXPERIMENTAL && L2TP && PPP 1001 help 1002 Support for PPP-over-L2TP socket family. L2TP is a protocol 1003 used by ISPs and enterprises to tunnel PPP traffic over UDP 1004 tunnels. L2TP is replacing PPTP for VPN uses. 1005 1006config SLIP 1007 tristate "SLIP (serial line) support" 1008 ---help--- 1009 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 1010 connect to your Internet service provider or to connect to some 1011 other local Unix box or if you want to configure your Linux box as a 1012 Slip/CSlip server for other people to dial in. SLIP (Serial Line 1013 Internet Protocol) is a protocol used to send Internet traffic over 1014 serial connections such as telephone lines or null modem cables; 1015 nowadays, the protocol PPP is more commonly used for this same 1016 purpose. 1017 1018 Normally, your access provider has to support SLIP in order for you 1019 to be able to use it, but there is now a SLIP emulator called SLiRP 1020 around (available from 1021 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 1022 allows you to use SLIP over a regular dial up shell connection. If 1023 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 1024 NET-3-HOWTO, available from 1025 <http://www.tldp.org/docs.html#howto>, explains how to 1026 configure SLIP. Note that you don't need this option if you just 1027 want to run term (term is a program which gives you almost full 1028 Internet connectivity if you have a regular dial up shell account on 1029 some Internet connected Unix computer. Read 1030 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 1031 support will enlarge your kernel by about 4 KB. If unsure, say N. 1032 1033 To compile this driver as a module, choose M here. The module 1034 will be called slip. 1035 1036config SLIP_COMPRESSED 1037 bool "CSLIP compressed headers" 1038 depends on SLIP 1039 select SLHC 1040 ---help--- 1041 This protocol is faster than SLIP because it uses compression on the 1042 TCP/IP headers (not on the data itself), but it has to be supported 1043 on both ends. Ask your access provider if you are not sure and 1044 answer Y, just in case. You will still be able to use plain SLIP. If 1045 you plan to use SLiRP, the SLIP emulator (available from 1046 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 1047 allows you to use SLIP over a regular dial up shell connection, you 1048 definitely want to say Y here. The NET-3-HOWTO, available from 1049 <http://www.tldp.org/docs.html#howto>, explains how to configure 1050 CSLIP. This won't enlarge your kernel. 1051 1052config SLHC 1053 tristate 1054 help 1055 This option enables Van Jacobsen serial line header compression 1056 routines. 1057 1058config SLIP_SMART 1059 bool "Keepalive and linefill" 1060 depends on SLIP 1061 help 1062 Adds additional capabilities to the SLIP driver to support the 1063 RELCOM line fill and keepalive monitoring. Ideal on poor quality 1064 analogue lines. 1065 1066config SLIP_MODE_SLIP6 1067 bool "Six bit SLIP encapsulation" 1068 depends on SLIP 1069 help 1070 Just occasionally you may need to run IP over hostile serial 1071 networks that don't pass all control characters or are only seven 1072 bit. Saying Y here adds an extra mode you can use with SLIP: 1073 "slip6". In this mode, SLIP will only send normal ASCII symbols over 1074 the serial device. Naturally, this has to be supported at the other 1075 end of the link as well. It's good enough, for example, to run IP 1076 over the async ports of a Camtec JNT Pad. If unsure, say N. 1077 1078config NET_FC 1079 bool "Fibre Channel driver support" 1080 depends on SCSI && PCI 1081 help 1082 Fibre Channel is a high speed serial protocol mainly used to connect 1083 large storage devices to the computer; it is compatible with and 1084 intended to replace SCSI. 1085 1086 If you intend to use Fibre Channel, you need to have a Fibre channel 1087 adaptor card in your computer; say Y here and to the driver for your 1088 adaptor below. You also should have said Y to "SCSI support" and 1089 "SCSI generic support". 1090 1091config NETCONSOLE 1092 tristate "Network console logging support" 1093 ---help--- 1094 If you want to log kernel messages over the network, enable this. 1095 See <file:Documentation/networking/netconsole.txt> for details. 1096 1097config NETCONSOLE_DYNAMIC 1098 bool "Dynamic reconfiguration of logging targets" 1099 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 1100 !(NETCONSOLE=y && CONFIGFS_FS=m) 1101 help 1102 This option enables the ability to dynamically reconfigure target 1103 parameters (interface, IP addresses, port numbers, MAC addresses) 1104 at runtime through a userspace interface exported using configfs. 1105 See <file:Documentation/networking/netconsole.txt> for details. 1106 1107config NETPOLL 1108 def_bool NETCONSOLE 1109 1110config NETPOLL_TRAP 1111 bool "Netpoll traffic trapping" 1112 default n 1113 depends on NETPOLL 1114 1115config NET_POLL_CONTROLLER 1116 def_bool NETPOLL 1117 1118config VIRTIO_NET 1119 tristate "Virtio network driver (EXPERIMENTAL)" 1120 depends on EXPERIMENTAL && VIRTIO 1121 ---help--- 1122 This is the virtual network driver for virtio. It can be used with 1123 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 1124 1125config VMXNET3 1126 tristate "VMware VMXNET3 ethernet driver" 1127 depends on PCI && INET 1128 help 1129 This driver supports VMware's vmxnet3 virtual ethernet NIC. 1130 To compile this driver as a module, choose M here: the 1131 module will be called vmxnet3. 1132 1133endif # NETDEVICES 1134