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 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
 247 config 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
 255 config 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
 270 config 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
 283 config 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
 291 config 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
 300 config 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
 309 config 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
 316 config 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
 326 config TI_DAVINCI_EMAC
 327         tristate "TI DaVinci EMAC Support"
 328         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 329         select TI_DAVINCI_MDIO
 330         select TI_DAVINCI_CPDMA
 331         select PHYLIB
 332         help
 333           This driver supports TI's DaVinci Ethernet .
 334
 335           To compile this driver as a module, choose M here: the module
 336           will be called davinci_emac_driver.  This is recommended.
 337
 338 config TI_DAVINCI_MDIO
 339         tristate "TI DaVinci MDIO Support"
 340         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 341         select PHYLIB
 342         help
 343           This driver supports TI's DaVinci MDIO module.
 344
 345           To compile this driver as a module, choose M here: the module
 346           will be called davinci_mdio.  This is recommended.
 347
 348 config TI_DAVINCI_CPDMA
 349         tristate "TI DaVinci CPDMA Support"
 350         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 351         help
 352           This driver supports TI's DaVinci CPDMA dma engine.
 353
 354           To compile this driver as a module, choose M here: the module
 355           will be called davinci_cpdma.  This is recommended.
 356
 357 config DM9000
 358         tristate "DM9000 support"
 359         depends on ARM || BLACKFIN || MIPS
 360         select CRC32
 361         select MII
 362         ---help---
 363           Support for DM9000 chipset.
 364
 365           To compile this driver as a module, choose M here.  The module
 366           will be called dm9000.
 367
 368 config DM9000_DEBUGLEVEL
 369         int "DM9000 maximum debug level"
 370         depends on DM9000
 371         default 4
 372         help
 373           The maximum level of debugging code compiled into the DM9000
 374           driver.
 375
 376 config DM9000_FORCE_SIMPLE_PHY_POLL
 377         bool "Force simple NSR based PHY polling"
 378         depends on DM9000
 379         ---help---
 380           This configuration forces the DM9000 to use the NSR's LinkStatus
 381           bit to determine if the link is up or down instead of the more
 382           costly MII PHY reads. Note, this will not work if the chip is
 383           operating with an external PHY.
 384
 385 config ENC28J60
 386         tristate "ENC28J60 support"
 387         depends on EXPERIMENTAL && SPI && NET_ETHERNET
 388         select CRC32
 389         ---help---
 390           Support for the Microchip EN28J60 ethernet chip.
 391
 392           To compile this driver as a module, choose M here. The module will be
 393           called enc28j60.
 394
 395 config ENC28J60_WRITEVERIFY
 396         bool "Enable write verify"
 397         depends on ENC28J60
 398         ---help---
 399           Enable the verify after the buffer write useful for debugging purpose.
 400           If unsure, say N.
 401
 402 config ETHOC
 403         tristate "OpenCores 10/100 Mbps Ethernet MAC support"
 404         depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
 405         select MII
 406         select PHYLIB
 407         select CRC32
 408         select BITREVERSE
 409         help
 410           Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
 411
 412 config GRETH
 413         tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
 414         depends on SPARC
 415         select PHYLIB
 416         select CRC32
 417         help
 418           Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
 419
 420 config DNET
 421         tristate "Dave ethernet support (DNET)"
 422         depends on NET_ETHERNET && HAS_IOMEM
 423         select PHYLIB
 424         help
 425           The Dave ethernet interface (DNET) is found on Qong Board FPGA.
 426           Say Y to include support for the DNET chip.
 427
 428           To compile this driver as a module, choose M here: the module
 429           will be called dnet.
 430
 431 config AT1700
 432         tristate "AT1700/1720 support (EXPERIMENTAL)"
 433         depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
 434         select CRC32
 435         ---help---
 436           If you have a network (Ethernet) card of this type, say Y and read
 437           the Ethernet-HOWTO, available from
 438           <http://www.tldp.org/docs.html#howto>.
 439
 440           To compile this driver as a module, choose M here. The module
 441           will be called at1700.
 442
 443 config HP100
 444         tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
 445         depends on ISA || EISA || PCI
 446         help
 447           If you have a network (Ethernet) card of this type, say Y and read
 448           the Ethernet-HOWTO, available from
 449           <http://www.tldp.org/docs.html#howto>.
 450
 451           To compile this driver as a module, choose M here. The module
 452           will be called hp100.
 453
 454 config NET_ISA
 455         bool "Other ISA cards"
 456         depends on ISA
 457         ---help---
 458           If your network (Ethernet) card hasn't been mentioned yet and its
 459           bus system (that's the way the cards talks to the other components
 460           of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
 461           Make sure you know the name of your card. Read the Ethernet-HOWTO,
 462           available from <http://www.tldp.org/docs.html#howto>.
 463
 464           If unsure, say Y.
 465
 466           Note that the answer to this question doesn't directly affect the
 467           kernel: saying N will just cause the configurator to skip all
 468           the remaining ISA network card questions. If you say Y, you will be
 469           asked for your specific card in the following questions.
 470
 471 config ETH16I
 472         tristate "ICL EtherTeam 16i/32 support"
 473         depends on NET_ISA
 474         help
 475           If you have a network (Ethernet) card of this type, say Y and read
 476           the Ethernet-HOWTO, available from
 477           <http://www.tldp.org/docs.html#howto>.
 478
 479           To compile this driver as a module, choose M here. The module
 480           will be called eth16i.
 481
 482 config NET_PCI
 483         bool "EISA, VLB, PCI and on board controllers"
 484         depends on ISA || EISA || PCI
 485         help
 486           This is another class of network cards which attach directly to the
 487           bus. If you have one of those, say Y and read the Ethernet-HOWTO,
 488           available from <http://www.tldp.org/docs.html#howto>.
 489
 490           Note that the answer to this question doesn't directly affect the
 491           kernel: saying N will just cause the configurator to skip all
 492           the questions about this class of network cards. If you say Y, you
 493           will be asked for your specific card in the following questions. If
 494           you are unsure, say Y.
 495
 496 config ADAPTEC_STARFIRE
 497         tristate "Adaptec Starfire/DuraLAN support"
 498         depends on NET_PCI && PCI
 499         select CRC32
 500         select MII
 501         help
 502           Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
 503           adapter. The DuraLAN chip is used on the 64 bit PCI boards from
 504           Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
 505           driver.
 506
 507           To compile this driver as a module, choose M here: the module
 508           will be called starfire.  This is recommended.
 509
 510 config KSZ884X_PCI
 511         tristate "Micrel KSZ8841/2 PCI"
 512         depends on NET_PCI && PCI
 513         select MII
 514         select CRC32
 515         help
 516           This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
 517
 518           To compile this driver as a module, choose M here. The module
 519           will be called ksz884x.
 520
 521 config FORCEDETH
 522         tristate "nForce Ethernet support"
 523         depends on NET_PCI && PCI
 524         help
 525           If you have a network (Ethernet) controller of this type, say Y and
 526           read the Ethernet-HOWTO, available from
 527           <http://www.tldp.org/docs.html#howto>.
 528
 529           To compile this driver as a module, choose M here. The module
 530           will be called forcedeth.
 531
 532 config TC35815
 533         tristate "TOSHIBA TC35815 Ethernet support"
 534         depends on NET_PCI && PCI && MIPS
 535         select PHYLIB
 536
 537 config FEALNX
 538         tristate "Myson MTD-8xx PCI Ethernet support"
 539         depends on NET_PCI && PCI
 540         select CRC32
 541         select MII
 542         help
 543           Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
 544           cards. <http://www.myson.com.tw/>
 545
 546 config R6040
 547         tristate "RDC R6040 Fast Ethernet Adapter support"
 548         depends on NET_PCI && PCI
 549         select CRC32
 550         select MII
 551         select PHYLIB
 552         help
 553           This is a driver for the R6040 Fast Ethernet MACs found in the
 554           the RDC R-321x System-on-chips.
 555
 556           To compile this driver as a module, choose M here: the module
 557           will be called r6040. This is recommended.
 558
 559 config SIS900
 560         tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
 561         depends on NET_PCI && PCI
 562         select CRC32
 563         select MII
 564         ---help---
 565           This is a driver for the Fast Ethernet PCI network cards based on
 566           the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
 567           SiS 630 and SiS 540 chipsets.
 568
 569           This driver also supports AMD 79C901 HomePNA so that you can use
 570           your phone line as a network cable.
 571
 572           To compile this driver as a module, choose M here: the module
 573           will be called sis900.  This is recommended.
 574
 575 config TLAN
 576         tristate "TI ThunderLAN support"
 577         depends on NET_PCI && (PCI || EISA)
 578         ---help---
 579           If you have a PCI Ethernet network card based on the ThunderLAN chip
 580           which is supported by this driver, say Y and read the
 581           Ethernet-HOWTO, available from
 582           <http://www.tldp.org/docs.html#howto>.
 583
 584           Devices currently supported by this driver are Compaq Netelligent,
 585           Compaq NetFlex and Olicom cards.  Please read the file
 586           <file:Documentation/networking/tlan.txt> for more details.
 587
 588           To compile this driver as a module, choose M here. The module
 589           will be called tlan.
 590
 591           Please email feedback to <torben.mathiasen@compaq.com>.
 592
 593 config KS8842
 594         tristate "Micrel KSZ8841/42 with generic bus interface"
 595         depends on HAS_IOMEM && DMA_ENGINE
 596         help
 597           This platform driver is for KSZ8841(1-port) / KS8842(2-port)
 598           ethernet switch chip (managed, VLAN, QoS) from Micrel or
 599           Timberdale(FPGA).
 600
 601 config KS8851
 602         tristate "Micrel KS8851 SPI"
 603         depends on SPI
 604         select MII
 605         select CRC32
 606         help
 607           SPI driver for Micrel KS8851 SPI attached network chip.
 608
 609 config KS8851_MLL
 610         tristate "Micrel KS8851 MLL"
 611         depends on HAS_IOMEM
 612         select MII
 613         help
 614           This platform driver is for Micrel KS8851 Address/data bus
 615           multiplexed network chip.
 616
 617 config CPMAC
 618         tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
 619         depends on NET_ETHERNET && EXPERIMENTAL && AR7
 620         select PHYLIB
 621         help
 622           TI AR7 CPMAC Ethernet support
 623
 624 config NET_POCKET
 625         bool "Pocket and portable adapters"
 626         depends on PARPORT
 627         ---help---
 628           Cute little network (Ethernet) devices which attach to the parallel
 629           port ("pocket adapters"), commonly used with laptops. If you have
 630           one of those, say Y and read the Ethernet-HOWTO, available from
 631           <http://www.tldp.org/docs.html#howto>.
 632
 633           If you want to plug a network (or some other) card into the PCMCIA
 634           (or PC-card) slot of your laptop instead (PCMCIA is the standard for
 635           credit card size extension cards used by all modern laptops), you
 636           need the pcmcia-cs package (location contained in the file
 637           <file:Documentation/Changes>) and you can say N here.
 638
 639           Laptop users should read the Linux Laptop home page at
 640           <http://www.linux-on-laptops.com/> or
 641           Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
 642
 643           Note that the answer to this question doesn't directly affect the
 644           kernel: saying N will just cause the configurator to skip all
 645           the questions about this class of network devices. If you say Y, you
 646           will be asked for your specific device in the following questions.
 647
 648 config FEC
 649         bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
 650         depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
 651                 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
 652         default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
 653         select PHYLIB
 654         help
 655           Say Y here if you want to use the built-in 10/100 Fast ethernet
 656           controller on some Motorola ColdFire and Freescale i.MX processors.
 657
 658 config FEC_MPC52xx
 659         tristate "MPC52xx FEC driver"
 660         depends on PPC_MPC52xx && PPC_BESTCOMM
 661         select CRC32
 662         select PHYLIB
 663         select PPC_BESTCOMM_FEC
 664         ---help---
 665           This option enables support for the MPC5200's on-chip
 666           Fast Ethernet Controller
 667           If compiled as module, it will be called fec_mpc52xx.
 668
 669 config FEC_MPC52xx_MDIO
 670         bool "MPC52xx FEC MDIO bus driver"
 671         depends on FEC_MPC52xx
 672         default y
 673         ---help---
 674           The MPC5200's FEC can connect to the Ethernet either with
 675           an external MII PHY chip or 10 Mbps 7-wire interface
 676           (Motorola? industry standard).
 677           If your board uses an external PHY connected to FEC, enable this.
 678           If not sure, enable.
 679           If compiled as module, it will be called fec_mpc52xx_phy.
 680
 681 config XILINX_EMACLITE
 682         tristate "Xilinx 10/100 Ethernet Lite support"
 683         depends on PPC32 || MICROBLAZE
 684         select PHYLIB
 685         help
 686           This driver supports the 10/100 Ethernet Lite from Xilinx.
 687
 688 config LANTIQ_ETOP
 689         tristate "Lantiq SoC ETOP driver"
 690         depends on SOC_TYPE_XWAY
 691         help
 692           Support for the MII0 inside the Lantiq SoC
 693
 694
 695 source "drivers/net/fs_enet/Kconfig"
 696
 697 source "drivers/net/octeon/Kconfig"
 698
 699 endif # NET_ETHERNET
 700
 701 #
 702 #       Gigabit Ethernet
 703 #
 704
 705 menuconfig NETDEV_1000
 706         bool "Ethernet (1000 Mbit)"
 707         depends on !UML
 708         default y
 709         ---help---
 710           Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
 711           type of Local Area Network (LAN) in universities and companies.
 712
 713           Say Y here to get to see options for Gigabit Ethernet drivers.
 714           This option alone does not add any kernel code.
 715           Note that drivers supporting both 100 and 1000 MBit may be listed
 716           under "Ethernet (10 or 100MBit)" instead.
 717
 718           If you say N, all options in this submenu will be skipped and disabled.
 719
 720 if NETDEV_1000
 721
 722 config IP1000
 723         tristate "IP1000 Gigabit Ethernet support"
 724         depends on PCI && EXPERIMENTAL
 725         select MII
 726         ---help---
 727           This driver supports IP1000 gigabit Ethernet cards.
 728
 729           To compile this driver as a module, choose M here: the module
 730           will be called ipg.  This is recommended.
 731
 732 config HAMACHI
 733         tristate "Packet Engines Hamachi GNIC-II support"
 734         depends on PCI
 735         select MII
 736         help
 737           If you have a Gigabit Ethernet card of this type, say Y and read
 738           the Ethernet-HOWTO, available from
 739           <http://www.tldp.org/docs.html#howto>.
 740
 741           To compile this driver as a module, choose M here. The module will be
 742           called hamachi.
 743
 744 config YELLOWFIN
 745         tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
 746         depends on PCI && EXPERIMENTAL
 747         select CRC32
 748         ---help---
 749           Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
 750           adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
 751           used by the Beowulf Linux cluster project.  See
 752           <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
 753           information about this driver in particular and Beowulf in general.
 754
 755           To compile this driver as a module, choose M here: the module
 756           will be called yellowfin.  This is recommended.
 757
 758 config SIS190
 759         tristate "SiS190/SiS191 gigabit ethernet support"
 760         depends on PCI
 761         select CRC32
 762         select MII
 763         ---help---
 764           Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
 765           a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
 766           appear in lan on motherboard designs which are based on SiS 965
 767           and SiS 966 south bridge.
 768
 769           To compile this driver as a module, choose M here: the module
 770           will be called sis190.  This is recommended.
 771
 772 config SPIDER_NET
 773         tristate "Spider Gigabit Ethernet driver"
 774         depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
 775         select FW_LOADER
 776         select SUNGEM_PHY
 777         help
 778           This driver supports the Gigabit Ethernet chips present on the
 779           Cell Processor-Based Blades from IBM.
 780
 781 config TSI108_ETH
 782         tristate "Tundra TSI108 gigabit Ethernet support"
 783         depends on TSI108_BRIDGE
 784         help
 785           This driver supports Tundra TSI108 gigabit Ethernet ports.
 786           To compile this driver as a module, choose M here: the module
 787           will be called tsi108_eth.
 788
 789 config GELIC_NET
 790         tristate "PS3 Gigabit Ethernet driver"
 791         depends on PPC_PS3
 792         select PS3_SYS_MANAGER
 793         help
 794           This driver supports the network device on the PS3 game
 795           console.  This driver has built-in support for Ethernet.
 796
 797           To compile this driver as a module, choose M here: the
 798           module will be called ps3_gelic.
 799
 800 config GELIC_WIRELESS
 801         bool "PS3 Wireless support"
 802         depends on WLAN
 803         depends on GELIC_NET
 804         select WIRELESS_EXT
 805         help
 806           This option adds the support for the wireless feature of PS3.
 807           If you have the wireless-less model of PS3 or have no plan to
 808           use wireless feature, disabling this option saves memory.  As
 809           the driver automatically distinguishes the models, you can
 810           safely enable this option even if you have a wireless-less model.
 811
 812 config FSL_PQ_MDIO
 813         tristate "Freescale PQ MDIO"
 814         depends on FSL_SOC
 815         select PHYLIB
 816         help
 817           This driver supports the MDIO bus used by the gianfar and UCC drivers.
 818
 819 config GIANFAR
 820         tristate "Gianfar Ethernet"
 821         depends on FSL_SOC
 822         select FSL_PQ_MDIO
 823         select PHYLIB
 824         select CRC32
 825         help
 826           This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
 827           and MPC86xx family of chips, and the FEC on the 8540.
 828
 829 config UCC_GETH
 830         tristate "Freescale QE Gigabit Ethernet"
 831         depends on QUICC_ENGINE
 832         select FSL_PQ_MDIO
 833         select PHYLIB
 834         help
 835           This driver supports the Gigabit Ethernet mode of the QUICC Engine,
 836           which is available on some Freescale SOCs.
 837
 838 config UGETH_TX_ON_DEMAND
 839         bool "Transmit on Demand support"
 840         depends on UCC_GETH
 841
 842 config XILINX_LL_TEMAC
 843         tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
 844         depends on PPC || MICROBLAZE
 845         select PHYLIB
 846         help
 847           This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
 848           core used in Xilinx Spartan and Virtex FPGAs
 849
 850 config JME
 851         tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
 852         depends on PCI
 853         select CRC32
 854         select MII
 855         ---help---
 856           This driver supports the PCI-Express gigabit ethernet adapters
 857           based on JMicron JMC250 chipset.
 858
 859           To compile this driver as a module, choose M here. The module
 860           will be called jme.
 861
 862 config S6GMAC
 863         tristate "S6105 GMAC ethernet support"
 864         depends on XTENSA_VARIANT_S6000
 865         select PHYLIB
 866         help
 867           This driver supports the on chip ethernet device on the
 868           S6105 xtensa processor.
 869
 870           To compile this driver as a module, choose M here. The module
 871           will be called s6gmac.
 872
 873 endif # NETDEV_1000
 874
 875 #
 876 #       10 Gigabit Ethernet
 877 #
 878
 879 menuconfig NETDEV_10000
 880         bool "Ethernet (10000 Mbit)"
 881         depends on !UML
 882         default y
 883         ---help---
 884           Say Y here to get to see options for 10 Gigabit Ethernet drivers.
 885           This option alone does not add any kernel code.
 886
 887           If you say N, all options in this submenu will be skipped and disabled.
 888
 889 if NETDEV_10000
 890
 891 config MDIO
 892         tristate
 893
 894 config SUNGEM_PHY
 895         tristate
 896
 897 endif # NETDEV_10000
 898
 899 source "drivers/net/tokenring/Kconfig"
 900
 901 source "drivers/net/wireless/Kconfig"
 902
 903 source "drivers/net/wimax/Kconfig"
 904
 905 source "drivers/net/usb/Kconfig"
 906
 907 source "drivers/net/pcmcia/Kconfig"
 908
 909 source "drivers/net/wan/Kconfig"
 910
 911 source "drivers/atm/Kconfig"
 912
 913 source "drivers/ieee802154/Kconfig"
 914
 915 source "drivers/s390/net/Kconfig"
 916
 917 source "drivers/net/caif/Kconfig"
 918
 919 config TILE_NET
 920         tristate "Tilera GBE/XGBE network driver support"
 921         depends on TILE
 922         default y
 923         select CRC32
 924         help
 925           This is a standard Linux network device driver for the
 926           on-chip Tilera Gigabit Ethernet and XAUI interfaces.
 927
 928           To compile this driver as a module, choose M here: the module
 929           will be called tile_net.
 930
 931 config XEN_NETDEV_FRONTEND
 932         tristate "Xen network device frontend driver"
 933         depends on XEN
 934         select XEN_XENBUS_FRONTEND
 935         default y
 936         help
 937           This driver provides support for Xen paravirtual network
 938           devices exported by a Xen network driver domain (often
 939           domain 0).
 940
 941           The corresponding Linux backend driver is enabled by the
 942           CONFIG_XEN_NETDEV_BACKEND option.
 943
 944           If you are compiling a kernel for use as Xen guest, you
 945           should say Y here. To compile this driver as a module, chose
 946           M here: the module will be called xen-netfront.
 947
 948 config XEN_NETDEV_BACKEND
 949         tristate "Xen backend network device"
 950         depends on XEN_BACKEND
 951         help
 952           This driver allows the kernel to act as a Xen network driver
 953           domain which exports paravirtual network devices to other
 954           Xen domains. These devices can be accessed by any operating
 955           system that implements a compatible front end.
 956
 957           The corresponding Linux frontend driver is enabled by the
 958           CONFIG_XEN_NETDEV_FRONTEND configuration option.
 959
 960           The backend driver presents a standard network device
 961           endpoint for each paravirtual network device to the driver
 962           domain network stack. These can then be bridged or routed
 963           etc in order to provide full network connectivity.
 964
 965           If you are compiling a kernel to run in a Xen network driver
 966           domain (often this is domain 0) you should say Y here. To
 967           compile this driver as a module, chose M here: the module
 968           will be called xen-netback.
 969
 970 config RIONET
 971         tristate "RapidIO Ethernet over messaging driver support"
 972         depends on RAPIDIO
 973
 974 config RIONET_TX_SIZE
 975         int "Number of outbound queue entries"
 976         depends on RIONET
 977         default "128"
 978
 979 config RIONET_RX_SIZE
 980         int "Number of inbound queue entries"
 981         depends on RIONET
 982         default "128"
 983
 984 config FDDI
 985         tristate "FDDI driver support"
 986         depends on (PCI || EISA || TC)
 987         help
 988           Fiber Distributed Data Interface is a high speed local area network
 989           design; essentially a replacement for high speed Ethernet. FDDI can
 990           run over copper or fiber. If you are connected to such a network and
 991           want a driver for the FDDI card in your computer, say Y here (and
 992           then also Y to the driver for your FDDI card, below). Most people
 993           will say N.
 994
 995 config DEFXX
 996         tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
 997         depends on FDDI && (PCI || EISA || TC)
 998         ---help---
 999           This is support for the DIGITAL series of TURBOchannel (DEFTA),
1000           EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1001           to a local FDDI network.
1002
1003           To compile this driver as a module, choose M here: the module
1004           will be called defxx.  If unsure, say N.
1005
1006 config DEFXX_MMIO
1007         bool
1008         prompt "Use MMIO instead of PIO" if PCI || EISA
1009         depends on DEFXX
1010         default n if PCI || EISA
1011         default y
1012         ---help---
1013           This instructs the driver to use EISA or PCI memory-mapped I/O
1014           (MMIO) as appropriate instead of programmed I/O ports (PIO).
1015           Enabling this gives an improvement in processing time in parts
1016           of the driver, but it may cause problems with EISA (DEFEA)
1017           adapters.  TURBOchannel does not have the concept of I/O ports,
1018           so MMIO is always used for these (DEFTA) adapters.
1019
1020           If unsure, say N.
1021
1022 config SKFP
1023         tristate "SysKonnect FDDI PCI support"
1024         depends on FDDI && PCI
1025         select BITREVERSE
1026         ---help---
1027           Say Y here if you have a SysKonnect FDDI PCI adapter.
1028           The following adapters are supported by this driver:
1029           - SK-5521 (SK-NET FDDI-UP)
1030           - SK-5522 (SK-NET FDDI-UP DAS)
1031           - SK-5541 (SK-NET FDDI-FP)
1032           - SK-5543 (SK-NET FDDI-LP)
1033           - SK-5544 (SK-NET FDDI-LP DAS)
1034           - SK-5821 (SK-NET FDDI-UP64)
1035           - SK-5822 (SK-NET FDDI-UP64 DAS)
1036           - SK-5841 (SK-NET FDDI-FP64)
1037           - SK-5843 (SK-NET FDDI-LP64)
1038           - SK-5844 (SK-NET FDDI-LP64 DAS)
1039           - Netelligent 100 FDDI DAS Fibre SC
1040           - Netelligent 100 FDDI SAS Fibre SC
1041           - Netelligent 100 FDDI DAS UTP
1042           - Netelligent 100 FDDI SAS UTP
1043           - Netelligent 100 FDDI SAS Fibre MIC
1044
1045           Read <file:Documentation/networking/skfp.txt> for information about
1046           the driver.
1047
1048           Questions concerning this driver can be addressed to:
1049           <linux@syskonnect.de>
1050
1051           To compile this driver as a module, choose M here: the module
1052           will be called skfp.  This is recommended.
1053
1054 config HIPPI
1055         bool "HIPPI driver support (EXPERIMENTAL)"
1056         depends on EXPERIMENTAL && INET && PCI
1057         help
1058           HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1059           1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1060           can run over copper (25m) or fiber (300m on multi-mode or 10km on
1061           single-mode). HIPPI networks are commonly used for clusters and to
1062           connect to super computers. If you are connected to a HIPPI network
1063           and have a HIPPI network card in your computer that you want to use
1064           under Linux, say Y here (you must also remember to enable the driver
1065           for your HIPPI card below). Most people will say N here.
1066
1067 config ROADRUNNER
1068         tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1069         depends on HIPPI && PCI
1070         help
1071           Say Y here if this is your PCI HIPPI network card.
1072
1073           To compile this driver as a module, choose M here: the module
1074           will be called rrunner.  If unsure, say N.
1075
1076 config ROADRUNNER_LARGE_RINGS
1077         bool "Use large TX/RX rings (EXPERIMENTAL)"
1078         depends on ROADRUNNER
1079         help
1080           If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1081           of additional memory to allow for fastest operation, both for
1082           transmitting and receiving. This memory cannot be used by any other
1083           kernel code or by user space programs. Say Y here only if you have
1084           the memory.
1085
1086 config PLIP
1087         tristate "PLIP (parallel port) support"
1088         depends on PARPORT
1089         ---help---
1090           PLIP (Parallel Line Internet Protocol) is used to create a
1091           reasonably fast mini network consisting of two (or, rarely, more)
1092           local machines.  A PLIP link from a Linux box is a popular means to
1093           install a Linux distribution on a machine which doesn't have a
1094           CD-ROM drive (a minimal system has to be transferred with floppies
1095           first). The kernels on both machines need to have this PLIP option
1096           enabled for this to work.
1097
1098           The PLIP driver has two modes, mode 0 and mode 1.  The parallel
1099           ports (the connectors at the computers with 25 holes) are connected
1100           with "null printer" or "Turbo Laplink" cables which can transmit 4
1101           bits at a time (mode 0) or with special PLIP cables, to be used on
1102           bidirectional parallel ports only, which can transmit 8 bits at a
1103           time (mode 1); you can find the wiring of these cables in
1104           <file:Documentation/networking/PLIP.txt>.  The cables can be up to
1105           15m long.  Mode 0 works also if one of the machines runs DOS/Windows
1106           and has some PLIP software installed, e.g. the Crynwr PLIP packet
1107           driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1108           and winsock or NCSA's telnet.
1109
1110           If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1111           as the NET-3-HOWTO, both available from
1112           <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
1113           protocol has been changed and this PLIP driver won't work together
1114           with the PLIP support in Linux versions 1.0.x.  This option enlarges
1115           your kernel by about 8 KB.
1116
1117           To compile this driver as a module, choose M here. The module
1118           will be called plip. If unsure, say Y or M, in case you buy
1119           a laptop later.
1120
1121 config PPP
1122         tristate "PPP (point-to-point protocol) support"
1123         select SLHC
1124         ---help---
1125           PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
1126           the same purpose: sending Internet traffic over telephone (and other
1127           serial) lines.  Ask your access provider if they support it, because
1128           otherwise you can't use it; most Internet access providers these
1129           days support PPP rather than SLIP.
1130
1131           To use PPP, you need an additional program called pppd as described
1132           in the PPP-HOWTO, available at
1133           <http://www.tldp.org/docs.html#howto>.  Make sure that you have
1134           the version of pppd recommended in <file:Documentation/Changes>.
1135           The PPP option enlarges your kernel by about 16 KB.
1136
1137           There are actually two versions of PPP: the traditional PPP for
1138           asynchronous lines, such as regular analog phone lines, and
1139           synchronous PPP which can be used over digital ISDN lines for
1140           example.  If you want to use PPP over phone lines or other
1141           asynchronous serial lines, you need to say Y (or M) here and also to
1142           the next option, "PPP support for async serial ports".  For PPP over
1143           synchronous lines, you should say Y (or M) here and to "Support
1144           synchronous PPP", below.
1145
1146           If you said Y to "Version information on all symbols" above, then
1147           you cannot compile the PPP driver into the kernel; you can then only
1148           compile it as a module. To compile this driver as a module, choose M
1149           here. The module will be called ppp_generic.
1150
1151 config PPP_MULTILINK
1152         bool "PPP multilink support (EXPERIMENTAL)"
1153         depends on PPP && EXPERIMENTAL
1154         help
1155           PPP multilink is a protocol (defined in RFC 1990) which allows you
1156           to combine several (logical or physical) lines into one logical PPP
1157           connection, so that you can utilize your full bandwidth.
1158
1159           This has to be supported at the other end as well and you need a
1160           version of the pppd daemon which understands the multilink protocol.
1161
1162           If unsure, say N.
1163
1164 config PPP_FILTER
1165         bool "PPP filtering"
1166         depends on PPP
1167         help
1168           Say Y here if you want to be able to filter the packets passing over
1169           PPP interfaces.  This allows you to control which packets count as
1170           activity (i.e. which packets will reset the idle timer or bring up
1171           a demand-dialed link) and which packets are to be dropped entirely.
1172           You need to say Y here if you wish to use the pass-filter and
1173           active-filter options to pppd.
1174
1175           If unsure, say N.
1176
1177 config PPP_ASYNC
1178         tristate "PPP support for async serial ports"
1179         depends on PPP
1180         select CRC_CCITT
1181         ---help---
1182           Say Y (or M) here if you want to be able to use PPP over standard
1183           asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
1184           a modem (not a synchronous or ISDN modem) to contact your ISP, you
1185           need this option.
1186
1187           To compile this driver as a module, choose M here.
1188
1189           If unsure, say Y.
1190
1191 config PPP_SYNC_TTY
1192         tristate "PPP support for sync tty ports"
1193         depends on PPP
1194         help
1195           Say Y (or M) here if you want to be able to use PPP over synchronous
1196           (HDLC) tty devices, such as the SyncLink adapter. These devices
1197           are often used for high-speed leased lines like T1/E1.
1198
1199           To compile this driver as a module, choose M here.
1200
1201 config PPP_DEFLATE
1202         tristate "PPP Deflate compression"
1203         depends on PPP
1204         select ZLIB_INFLATE
1205         select ZLIB_DEFLATE
1206         ---help---
1207           Support for the Deflate compression method for PPP, which uses the
1208           Deflate algorithm (the same algorithm that gzip uses) to compress
1209           each PPP packet before it is sent over the wire.  The machine at the
1210           other end of the PPP link (usually your ISP) has to support the
1211           Deflate compression method as well for this to be useful.  Even if
1212           they don't support it, it is safe to say Y here.
1213
1214           To compile this driver as a module, choose M here.
1215
1216 config PPP_BSDCOMP
1217         tristate "PPP BSD-Compress compression"
1218         depends on PPP
1219         ---help---
1220           Support for the BSD-Compress compression method for PPP, which uses
1221           the LZW compression method to compress each PPP packet before it is
1222           sent over the wire. The machine at the other end of the PPP link
1223           (usually your ISP) has to support the BSD-Compress compression
1224           method as well for this to be useful. Even if they don't support it,
1225           it is safe to say Y here.
1226
1227           The PPP Deflate compression method ("PPP Deflate compression",
1228           above) is preferable to BSD-Compress, because it compresses better
1229           and is patent-free.
1230
1231           Note that the BSD compression code will always be compiled as a
1232           module; it is called bsd_comp and will show up in the directory
1233           modules once you have said "make modules". If unsure, say N.
1234
1235 config PPP_MPPE
1236         tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1237         depends on PPP && EXPERIMENTAL
1238         select CRYPTO
1239         select CRYPTO_SHA1
1240         select CRYPTO_ARC4
1241         select CRYPTO_ECB
1242         ---help---
1243           Support for the MPPE Encryption protocol, as employed by the
1244           Microsoft Point-to-Point Tunneling Protocol.
1245
1246           See http://pptpclient.sourceforge.net/ for information on
1247           configuring PPTP clients and servers to utilize this method.
1248
1249 config PPPOE
1250         tristate "PPP over Ethernet (EXPERIMENTAL)"
1251         depends on EXPERIMENTAL && PPP
1252         help
1253           Support for PPP over Ethernet.
1254
1255           This driver requires the latest version of pppd from the CVS
1256           repository at cvs.samba.org.  Alternatively, see the
1257           RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1258           which contains instruction on how to use this driver (under
1259           the heading "Kernel mode PPPoE").
1260
1261 config PPTP
1262         tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1263         depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1264         help
1265           Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1266
1267           This driver requires pppd plugin to work in client mode or
1268           modified pptpd (poptop) to work in server mode.
1269           See http://accel-pptp.sourceforge.net/ for information how to
1270           utilize this module.
1271
1272 config PPPOATM
1273         tristate "PPP over ATM"
1274         depends on ATM && PPP
1275         help
1276           Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1277           This implementation does not yet comply with section 8 of RFC2364,
1278           which can lead to bad results if the ATM peer loses state and
1279           changes its encapsulation unilaterally.
1280
1281 config PPPOL2TP
1282         tristate "PPP over L2TP (EXPERIMENTAL)"
1283         depends on EXPERIMENTAL && L2TP && PPP
1284         help
1285           Support for PPP-over-L2TP socket family. L2TP is a protocol
1286           used by ISPs and enterprises to tunnel PPP traffic over UDP
1287           tunnels. L2TP is replacing PPTP for VPN uses.
1288
1289 config SLIP
1290         tristate "SLIP (serial line) support"
1291         ---help---
1292           Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1293           connect to your Internet service provider or to connect to some
1294           other local Unix box or if you want to configure your Linux box as a
1295           Slip/CSlip server for other people to dial in. SLIP (Serial Line
1296           Internet Protocol) is a protocol used to send Internet traffic over
1297           serial connections such as telephone lines or null modem cables;
1298           nowadays, the protocol PPP is more commonly used for this same
1299           purpose.
1300
1301           Normally, your access provider has to support SLIP in order for you
1302           to be able to use it, but there is now a SLIP emulator called SLiRP
1303           around (available from
1304           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1305           allows you to use SLIP over a regular dial up shell connection. If
1306           you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1307           NET-3-HOWTO, available from
1308           <http://www.tldp.org/docs.html#howto>, explains how to
1309           configure SLIP. Note that you don't need this option if you just
1310           want to run term (term is a program which gives you almost full
1311           Internet connectivity if you have a regular dial up shell account on
1312           some Internet connected Unix computer. Read
1313           <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1314           support will enlarge your kernel by about 4 KB. If unsure, say N.
1315
1316           To compile this driver as a module, choose M here. The module
1317           will be called slip.
1318
1319 config SLIP_COMPRESSED
1320         bool "CSLIP compressed headers"
1321         depends on SLIP
1322         select SLHC
1323         ---help---
1324           This protocol is faster than SLIP because it uses compression on the
1325           TCP/IP headers (not on the data itself), but it has to be supported
1326           on both ends. Ask your access provider if you are not sure and
1327           answer Y, just in case. You will still be able to use plain SLIP. If
1328           you plan to use SLiRP, the SLIP emulator (available from
1329           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1330           allows you to use SLIP over a regular dial up shell connection, you
1331           definitely want to say Y here. The NET-3-HOWTO, available from
1332           <http://www.tldp.org/docs.html#howto>, explains how to configure
1333           CSLIP. This won't enlarge your kernel.
1334
1335 config SLHC
1336         tristate
1337         help
1338           This option enables Van Jacobsen serial line header compression
1339           routines.
1340
1341 config SLIP_SMART
1342         bool "Keepalive and linefill"
1343         depends on SLIP
1344         help
1345           Adds additional capabilities to the SLIP driver to support the
1346           RELCOM line fill and keepalive monitoring. Ideal on poor quality
1347           analogue lines.
1348
1349 config SLIP_MODE_SLIP6
1350         bool "Six bit SLIP encapsulation"
1351         depends on SLIP
1352         help
1353           Just occasionally you may need to run IP over hostile serial
1354           networks that don't pass all control characters or are only seven
1355           bit. Saying Y here adds an extra mode you can use with SLIP:
1356           "slip6". In this mode, SLIP will only send normal ASCII symbols over
1357           the serial device. Naturally, this has to be supported at the other
1358           end of the link as well. It's good enough, for example, to run IP
1359           over the async ports of a Camtec JNT Pad. If unsure, say N.
1360
1361 config NET_FC
1362         bool "Fibre Channel driver support"
1363         depends on SCSI && PCI
1364         help
1365           Fibre Channel is a high speed serial protocol mainly used to connect
1366           large storage devices to the computer; it is compatible with and
1367           intended to replace SCSI.
1368
1369           If you intend to use Fibre Channel, you need to have a Fibre channel
1370           adaptor card in your computer; say Y here and to the driver for your
1371           adaptor below. You also should have said Y to "SCSI support" and
1372           "SCSI generic support".
1373
1374 config NETCONSOLE
1375         tristate "Network console logging support"
1376         ---help---
1377         If you want to log kernel messages over the network, enable this.
1378         See <file:Documentation/networking/netconsole.txt> for details.
1379
1380 config NETCONSOLE_DYNAMIC
1381         bool "Dynamic reconfiguration of logging targets"
1382         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1383                         !(NETCONSOLE=y && CONFIGFS_FS=m)
1384         help
1385           This option enables the ability to dynamically reconfigure target
1386           parameters (interface, IP addresses, port numbers, MAC addresses)
1387           at runtime through a userspace interface exported using configfs.
1388           See <file:Documentation/networking/netconsole.txt> for details.
1389
1390 config NETPOLL
1391         def_bool NETCONSOLE
1392
1393 config NETPOLL_TRAP
1394         bool "Netpoll traffic trapping"
1395         default n
1396         depends on NETPOLL
1397
1398 config NET_POLL_CONTROLLER
1399         def_bool NETPOLL
1400
1401 config VIRTIO_NET
1402         tristate "Virtio network driver (EXPERIMENTAL)"
1403         depends on EXPERIMENTAL && VIRTIO
1404         ---help---
1405           This is the virtual network driver for virtio.  It can be used with
1406           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
1407
1408 config VMXNET3
1409         tristate "VMware VMXNET3 ethernet driver"
1410         depends on PCI && INET
1411         help
1412           This driver supports VMware's vmxnet3 virtual ethernet NIC.
1413           To compile this driver as a module, choose M here: the
1414           module will be called vmxnet3.
1415
1416 endif # NETDEVICES