drivers/net/Kconfig

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