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 MACE
 241         tristate "MACE (Power Mac ethernet) support"
 242         depends on PPC_PMAC && PPC32
 243         select CRC32
 244         help
 245           Power Macintoshes and clones with Ethernet built-in on the
 246           motherboard will usually use a MACE (Medium Access Control for
 247           Ethernet) interface. Say Y to include support for the MACE chip.
 248
 249           To compile this driver as a module, choose M here: the module
 250           will be called mace.
 251
 252 config MACE_AAUI_PORT
 253         bool "Use AAUI port instead of TP by default"
 254         depends on MACE
 255         help
 256           Some Apple machines (notably the Apple Network Server) which use the
 257           MACE ethernet chip have an Apple AUI port (small 15-pin connector),
 258           instead of an 8-pin RJ45 connector for twisted-pair ethernet.  Say
 259           Y here if you have such a machine.  If unsure, say N.
 260           The driver will default to AAUI on ANS anyway, and if you use it as
 261           a module, you can provide the port_aaui=0|1 to force the driver.
 262
 263 config BMAC
 264         tristate "BMAC (G3 ethernet) support"
 265         depends on PPC_PMAC && PPC32
 266         select CRC32
 267         help
 268           Say Y for support of BMAC Ethernet interfaces. These are used on G3
 269           computers.
 270
 271           To compile this driver as a module, choose M here: the module
 272           will be called bmac.
 273
 274 config MAC89x0
 275         tristate "Macintosh CS89x0 based ethernet cards"
 276         depends on MAC
 277         ---help---
 278           Support for CS89x0 chipset based Ethernet cards.  If you have a
 279           Nubus or LC-PDS network (Ethernet) card of this type, say Y and
 280           read the Ethernet-HOWTO, available from
 281           <http://www.tldp.org/docs.html#howto>.
 282
 283           To compile this driver as a module, choose M here. This module will
 284           be called mac89x0.
 285
 286 config MACSONIC
 287         tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
 288         depends on MAC
 289         ---help---
 290           Support for NatSemi SONIC based Ethernet devices.  This includes
 291           the onboard Ethernet in many Quadras as well as some LC-PDS,
 292           a few Nubus and all known Comm Slot Ethernet cards.  If you have
 293           one of these say Y and read the Ethernet-HOWTO, available from
 294           <http://www.tldp.org/docs.html#howto>.
 295
 296           To compile this driver as a module, choose M here. This module will
 297           be called macsonic.
 298
 299 config MACMACE
 300         bool "Macintosh (AV) onboard MACE ethernet"
 301         depends on MAC
 302         select CRC32
 303         help
 304           Support for the onboard AMD 79C940 MACE Ethernet controller used in
 305           the 660AV and 840AV Macintosh.  If you have one of these Macintoshes
 306           say Y and read the Ethernet-HOWTO, available from
 307           <http://www.tldp.org/docs.html#howto>.
 308
 309 config KORINA
 310         tristate "Korina (IDT RC32434) Ethernet support"
 311         depends on NET_ETHERNET && MIKROTIK_RB532
 312         help
 313           If you have a Mikrotik RouterBoard 500 or IDT RC32434
 314           based system say Y. Otherwise say N.
 315
 316 config MIPS_JAZZ_SONIC
 317         tristate "MIPS JAZZ onboard SONIC Ethernet support"
 318         depends on MACH_JAZZ
 319         help
 320           This is the driver for the onboard card of MIPS Magnum 4000,
 321           Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
 322
 323 config XTENSA_XT2000_SONIC
 324         tristate "Xtensa XT2000 onboard SONIC Ethernet support"
 325         depends on XTENSA_PLATFORM_XT2000
 326         help
 327           This is the driver for the onboard card of the Xtensa XT2000 board.
 328
 329 config SGI_IOC3_ETH
 330         bool "SGI IOC3 Ethernet"
 331         depends on PCI && SGI_IP27
 332         select CRC32
 333         select MII
 334         help
 335           If you have a network (Ethernet) card of this type, say Y and read
 336           the Ethernet-HOWTO, available from
 337           <http://www.tldp.org/docs.html#howto>.
 338
 339 config MIPS_SIM_NET
 340         tristate "MIPS simulator Network device"
 341         depends on MIPS_SIM
 342         help
 343           The MIPSNET device is a simple Ethernet network device which is
 344           emulated by the MIPS Simulator.
 345           If you are not using a MIPSsim or are unsure, say N.
 346
 347 config SGI_O2MACE_ETH
 348         tristate "SGI O2 MACE Fast Ethernet support"
 349         depends on SGI_IP32=y
 350
 351 config SH_ETH
 352         tristate "Renesas SuperH Ethernet support"
 353         depends on SUPERH && \
 354                 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
 355                  CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
 356                  CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
 357         select CRC32
 358         select MII
 359         select MDIO_BITBANG
 360         select PHYLIB
 361         help
 362           Renesas SuperH Ethernet device driver.
 363           This driver supporting CPUs are:
 364                 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
 365
 366 config BFIN_MAC
 367         tristate "Blackfin on-chip MAC support"
 368         depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
 369         select CRC32
 370         select MII
 371         select PHYLIB
 372         select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
 373         help
 374           This is the driver for Blackfin on-chip mac device. Say Y if you want it
 375           compiled into the kernel. This driver is also available as a module
 376           ( = code which can be inserted in and removed from the running kernel
 377           whenever you want). The module will be called bfin_mac.
 378
 379 config BFIN_MAC_USE_L1
 380         bool "Use L1 memory for rx/tx packets"
 381         depends on BFIN_MAC && (BF527 || BF537)
 382         default y
 383         help
 384           To get maximum network performance, you should use L1 memory as rx/tx buffers.
 385           Say N here if you want to reserve L1 memory for other uses.
 386
 387 config BFIN_TX_DESC_NUM
 388         int "Number of transmit buffer packets"
 389         depends on BFIN_MAC
 390         range 6 10 if BFIN_MAC_USE_L1
 391         range 10 100
 392         default "10"
 393         help
 394           Set the number of buffer packets used in driver.
 395
 396 config BFIN_RX_DESC_NUM
 397         int "Number of receive buffer packets"
 398         depends on BFIN_MAC
 399         range 20 100 if BFIN_MAC_USE_L1
 400         range 20 800
 401         default "20"
 402         help
 403           Set the number of buffer packets used in driver.
 404
 405 config BFIN_MAC_USE_HWSTAMP
 406         bool "Use IEEE 1588 hwstamp"
 407         depends on BFIN_MAC && BF518
 408         default y
 409         help
 410           To support the IEEE 1588 Precision Time Protocol (PTP), select y here
 411
 412 config PXA168_ETH
 413         tristate "Marvell pxa168 ethernet support"
 414         depends on CPU_PXA168
 415         select PHYLIB
 416         help
 417           This driver supports the pxa168 Ethernet ports.
 418
 419           To compile this driver as a module, choose M here. The module
 420           will be called pxa168_eth.
 421
 422 config NET_NETX
 423         tristate "NetX Ethernet support"
 424         select MII
 425         depends on ARCH_NETX
 426         help
 427           This is support for the Hilscher netX builtin Ethernet ports
 428
 429           To compile this driver as a module, choose M here. The module
 430           will be called netx-eth.
 431
 432 config TI_DAVINCI_EMAC
 433         tristate "TI DaVinci EMAC Support"
 434         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 435         select TI_DAVINCI_MDIO
 436         select TI_DAVINCI_CPDMA
 437         select PHYLIB
 438         help
 439           This driver supports TI's DaVinci Ethernet .
 440
 441           To compile this driver as a module, choose M here: the module
 442           will be called davinci_emac_driver.  This is recommended.
 443
 444 config TI_DAVINCI_MDIO
 445         tristate "TI DaVinci MDIO Support"
 446         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 447         select PHYLIB
 448         help
 449           This driver supports TI's DaVinci MDIO module.
 450
 451           To compile this driver as a module, choose M here: the module
 452           will be called davinci_mdio.  This is recommended.
 453
 454 config TI_DAVINCI_CPDMA
 455         tristate "TI DaVinci CPDMA Support"
 456         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 457         help
 458           This driver supports TI's DaVinci CPDMA dma engine.
 459
 460           To compile this driver as a module, choose M here: the module
 461           will be called davinci_cpdma.  This is recommended.
 462
 463 config DM9000
 464         tristate "DM9000 support"
 465         depends on ARM || BLACKFIN || MIPS
 466         select CRC32
 467         select MII
 468         ---help---
 469           Support for DM9000 chipset.
 470
 471           To compile this driver as a module, choose M here.  The module
 472           will be called dm9000.
 473
 474 config DM9000_DEBUGLEVEL
 475         int "DM9000 maximum debug level"
 476         depends on DM9000
 477         default 4
 478         help
 479           The maximum level of debugging code compiled into the DM9000
 480           driver.
 481
 482 config DM9000_FORCE_SIMPLE_PHY_POLL
 483         bool "Force simple NSR based PHY polling"
 484         depends on DM9000
 485         ---help---
 486           This configuration forces the DM9000 to use the NSR's LinkStatus
 487           bit to determine if the link is up or down instead of the more
 488           costly MII PHY reads. Note, this will not work if the chip is
 489           operating with an external PHY.
 490
 491 config ENC28J60
 492         tristate "ENC28J60 support"
 493         depends on EXPERIMENTAL && SPI && NET_ETHERNET
 494         select CRC32
 495         ---help---
 496           Support for the Microchip EN28J60 ethernet chip.
 497
 498           To compile this driver as a module, choose M here. The module will be
 499           called enc28j60.
 500
 501 config ENC28J60_WRITEVERIFY
 502         bool "Enable write verify"
 503         depends on ENC28J60
 504         ---help---
 505           Enable the verify after the buffer write useful for debugging purpose.
 506           If unsure, say N.
 507
 508 config ETHOC
 509         tristate "OpenCores 10/100 Mbps Ethernet MAC support"
 510         depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
 511         select MII
 512         select PHYLIB
 513         select CRC32
 514         select BITREVERSE
 515         help
 516           Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
 517
 518 config GRETH
 519         tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
 520         depends on SPARC
 521         select PHYLIB
 522         select CRC32
 523         help
 524           Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
 525
 526 config DNET
 527         tristate "Dave ethernet support (DNET)"
 528         depends on NET_ETHERNET && HAS_IOMEM
 529         select PHYLIB
 530         help
 531           The Dave ethernet interface (DNET) is found on Qong Board FPGA.
 532           Say Y to include support for the DNET chip.
 533
 534           To compile this driver as a module, choose M here: the module
 535           will be called dnet.
 536
 537 source "drivers/net/tulip/Kconfig"
 538
 539 config AT1700
 540         tristate "AT1700/1720 support (EXPERIMENTAL)"
 541         depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
 542         select CRC32
 543         ---help---
 544           If you have a network (Ethernet) card of this type, say Y and read
 545           the Ethernet-HOWTO, available from
 546           <http://www.tldp.org/docs.html#howto>.
 547
 548           To compile this driver as a module, choose M here. The module
 549           will be called at1700.
 550
 551 config HP100
 552         tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
 553         depends on ISA || EISA || PCI
 554         help
 555           If you have a network (Ethernet) card of this type, say Y and read
 556           the Ethernet-HOWTO, available from
 557           <http://www.tldp.org/docs.html#howto>.
 558
 559           To compile this driver as a module, choose M here. The module
 560           will be called hp100.
 561
 562 config NET_ISA
 563         bool "Other ISA cards"
 564         depends on ISA
 565         ---help---
 566           If your network (Ethernet) card hasn't been mentioned yet and its
 567           bus system (that's the way the cards talks to the other components
 568           of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
 569           Make sure you know the name of your card. Read the Ethernet-HOWTO,
 570           available from <http://www.tldp.org/docs.html#howto>.
 571
 572           If unsure, say Y.
 573
 574           Note that the answer to this question doesn't directly affect the
 575           kernel: saying N will just cause the configurator to skip all
 576           the remaining ISA network card questions. If you say Y, you will be
 577           asked for your specific card in the following questions.
 578
 579 config EWRK3
 580         tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
 581         depends on NET_ISA
 582         select CRC32
 583         ---help---
 584           This driver supports the DE203, DE204 and DE205 network (Ethernet)
 585           cards. If this is for you, say Y and read
 586           <file:Documentation/networking/ewrk3.txt> in the kernel source as
 587           well as the Ethernet-HOWTO, available from
 588           <http://www.tldp.org/docs.html#howto>.
 589
 590           To compile this driver as a module, choose M here. The module
 591           will be called ewrk3.
 592
 593 config ETH16I
 594         tristate "ICL EtherTeam 16i/32 support"
 595         depends on NET_ISA
 596         help
 597           If you have a network (Ethernet) card of this type, say Y and read
 598           the Ethernet-HOWTO, available from
 599           <http://www.tldp.org/docs.html#howto>.
 600
 601           To compile this driver as a module, choose M here. The module
 602           will be called eth16i.
 603
 604 config SEEQ8005
 605         tristate "SEEQ8005 support (EXPERIMENTAL)"
 606         depends on NET_ISA && EXPERIMENTAL
 607         help
 608           This is a driver for the SEEQ 8005 network (Ethernet) card.  If this
 609           is for you, read the Ethernet-HOWTO, available from
 610           <http://www.tldp.org/docs.html#howto>.
 611
 612           To compile this driver as a module, choose M here. The module
 613           will be called seeq8005.
 614
 615 config IBMLANA
 616         tristate "IBM LAN Adapter/A support"
 617         depends on MCA
 618         ---help---
 619           This is a Micro Channel Ethernet adapter.  You need to set
 620           CONFIG_MCA to use this driver.  It is both available as an in-kernel
 621           driver and as a module.
 622
 623           To compile this driver as a module, choose M here. The only
 624           currently supported card is the IBM LAN Adapter/A for Ethernet.  It
 625           will both support 16K and 32K memory windows, however a 32K window
 626           gives a better security against packet losses.  Usage of multiple
 627           boards with this driver should be possible, but has not been tested
 628           up to now due to lack of hardware.
 629
 630 config NET_PCI
 631         bool "EISA, VLB, PCI and on board controllers"
 632         depends on ISA || EISA || PCI
 633         help
 634           This is another class of network cards which attach directly to the
 635           bus. If you have one of those, say Y and read the Ethernet-HOWTO,
 636           available from <http://www.tldp.org/docs.html#howto>.
 637
 638           Note that the answer to this question doesn't directly affect the
 639           kernel: saying N will just cause the configurator to skip all
 640           the questions about this class of network cards. If you say Y, you
 641           will be asked for your specific card in the following questions. If
 642           you are unsure, say Y.
 643
 644 config ADAPTEC_STARFIRE
 645         tristate "Adaptec Starfire/DuraLAN support"
 646         depends on NET_PCI && PCI
 647         select CRC32
 648         select MII
 649         help
 650           Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
 651           adapter. The DuraLAN chip is used on the 64 bit PCI boards from
 652           Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
 653           driver.
 654
 655           To compile this driver as a module, choose M here: the module
 656           will be called starfire.  This is recommended.
 657
 658 config KSZ884X_PCI
 659         tristate "Micrel KSZ8841/2 PCI"
 660         depends on NET_PCI && PCI
 661         select MII
 662         select CRC32
 663         help
 664           This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
 665
 666           To compile this driver as a module, choose M here. The module
 667           will be called ksz884x.
 668
 669 config FORCEDETH
 670         tristate "nForce Ethernet support"
 671         depends on NET_PCI && PCI
 672         help
 673           If you have a network (Ethernet) controller of this type, say Y and
 674           read the Ethernet-HOWTO, available from
 675           <http://www.tldp.org/docs.html#howto>.
 676
 677           To compile this driver as a module, choose M here. The module
 678           will be called forcedeth.
 679
 680 config CS89x0
 681         tristate "CS89x0 support"
 682         depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
 683                 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
 684         ---help---
 685           Support for CS89x0 chipset based Ethernet cards. If you have a
 686           network (Ethernet) card of this type, say Y and read the
 687           Ethernet-HOWTO, available from
 688           <http://www.tldp.org/docs.html#howto> as well as
 689           <file:Documentation/networking/cs89x0.txt>.
 690
 691           To compile this driver as a module, choose M here. The module
 692           will be called cs89x0.
 693
 694 config CS89x0_NONISA_IRQ
 695         def_bool y
 696         depends on CS89x0 != n
 697         depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
 698
 699 config TC35815
 700         tristate "TOSHIBA TC35815 Ethernet support"
 701         depends on NET_PCI && PCI && MIPS
 702         select PHYLIB
 703
 704 config FEALNX
 705         tristate "Myson MTD-8xx PCI Ethernet support"
 706         depends on NET_PCI && PCI
 707         select CRC32
 708         select MII
 709         help
 710           Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
 711           cards. <http://www.myson.com.tw/>
 712
 713 config NATSEMI
 714         tristate "National Semiconductor DP8381x series PCI Ethernet support"
 715         depends on NET_PCI && PCI
 716         select CRC32
 717         help
 718           This driver is for the National Semiconductor DP83810 series,
 719           which is used in cards from PureData, NetGear, Linksys
 720           and others, including the 83815 chip.
 721           More specific information and updates are available from
 722           <http://www.scyld.com/network/natsemi.html>.
 723
 724 config 8139CP
 725         tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
 726         depends on NET_PCI && PCI && EXPERIMENTAL
 727         select CRC32
 728         select MII
 729         help
 730           This is a driver for the Fast Ethernet PCI network cards based on
 731           the RTL8139C+ chips. If you have one of those, say Y and read
 732           the Ethernet-HOWTO, available from
 733           <http://www.tldp.org/docs.html#howto>.
 734
 735           To compile this driver as a module, choose M here: the module
 736           will be called 8139cp.  This is recommended.
 737
 738 config 8139TOO
 739         tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
 740         depends on NET_PCI && PCI
 741         select CRC32
 742         select MII
 743         ---help---
 744           This is a driver for the Fast Ethernet PCI network cards based on
 745           the RTL 8129/8130/8139 chips. If you have one of those, say Y and
 746           read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
 747
 748           To compile this driver as a module, choose M here: the module
 749           will be called 8139too.  This is recommended.
 750
 751 config 8139TOO_PIO
 752         bool "Use PIO instead of MMIO"
 753         default y
 754         depends on 8139TOO
 755         help
 756           This instructs the driver to use programmed I/O ports (PIO) instead
 757           of PCI shared memory (MMIO).  This can possibly solve some problems
 758           in case your mainboard has memory consistency issues.  If unsure,
 759           say N.
 760
 761 config 8139TOO_TUNE_TWISTER
 762         bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
 763         depends on 8139TOO
 764         help
 765           This implements a function which might come in handy in case you
 766           are using low quality on long cabling. It is required for RealTek
 767           RTL-8139 revision K boards, and totally unused otherwise.  It tries
 768           to match the transceiver to the cable characteristics. This is
 769           experimental since hardly documented by the manufacturer.
 770           If unsure, say Y.
 771
 772 config 8139TOO_8129
 773         bool "Support for older RTL-8129/8130 boards"
 774         depends on 8139TOO
 775         help
 776           This enables support for the older and uncommon RTL-8129 and
 777           RTL-8130 chips, which support MII via an external transceiver,
 778           instead of an internal one.  Disabling this option will save some
 779           memory by making the code size smaller.  If unsure, say Y.
 780
 781 config 8139_OLD_RX_RESET
 782         bool "Use older RX-reset method"
 783         depends on 8139TOO
 784         help
 785           The 8139too driver was recently updated to contain a more rapid
 786           reset sequence, in the face of severe receive errors.  This "new"
 787           RX-reset method should be adequate for all boards.  But if you
 788           experience problems, you can enable this option to restore the
 789           old RX-reset behavior.  If unsure, say N.
 790
 791 config R6040
 792         tristate "RDC R6040 Fast Ethernet Adapter support"
 793         depends on NET_PCI && PCI
 794         select CRC32
 795         select MII
 796         select PHYLIB
 797         help
 798           This is a driver for the R6040 Fast Ethernet MACs found in the
 799           the RDC R-321x System-on-chips.
 800
 801           To compile this driver as a module, choose M here: the module
 802           will be called r6040. This is recommended.
 803
 804 config SIS900
 805         tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
 806         depends on NET_PCI && PCI
 807         select CRC32
 808         select MII
 809         ---help---
 810           This is a driver for the Fast Ethernet PCI network cards based on
 811           the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
 812           SiS 630 and SiS 540 chipsets.
 813
 814           This driver also supports AMD 79C901 HomePNA so that you can use
 815           your phone line as a network cable.
 816
 817           To compile this driver as a module, choose M here: the module
 818           will be called sis900.  This is recommended.
 819
 820 config SUNDANCE
 821         tristate "Sundance Alta support"
 822         depends on NET_PCI && PCI
 823         select CRC32
 824         select MII
 825         help
 826           This driver is for the Sundance "Alta" chip.
 827           More specific information and updates are available from
 828           <http://www.scyld.com/network/sundance.html>.
 829
 830 config SUNDANCE_MMIO
 831         bool "Use MMIO instead of PIO"
 832         depends on SUNDANCE
 833         help
 834           Enable memory-mapped I/O for interaction with Sundance NIC registers.
 835           Do NOT enable this by default, PIO (enabled when MMIO is disabled)
 836           is known to solve bugs on certain chips.
 837
 838           If unsure, say N.
 839
 840 config TLAN
 841         tristate "TI ThunderLAN support"
 842         depends on NET_PCI && (PCI || EISA)
 843         ---help---
 844           If you have a PCI Ethernet network card based on the ThunderLAN chip
 845           which is supported by this driver, say Y and read the
 846           Ethernet-HOWTO, available from
 847           <http://www.tldp.org/docs.html#howto>.
 848
 849           Devices currently supported by this driver are Compaq Netelligent,
 850           Compaq NetFlex and Olicom cards.  Please read the file
 851           <file:Documentation/networking/tlan.txt> for more details.
 852
 853           To compile this driver as a module, choose M here. The module
 854           will be called tlan.
 855
 856           Please email feedback to <torben.mathiasen@compaq.com>.
 857
 858 config KS8842
 859         tristate "Micrel KSZ8841/42 with generic bus interface"
 860         depends on HAS_IOMEM && DMA_ENGINE
 861         help
 862           This platform driver is for KSZ8841(1-port) / KS8842(2-port)
 863           ethernet switch chip (managed, VLAN, QoS) from Micrel or
 864           Timberdale(FPGA).
 865
 866 config KS8851
 867         tristate "Micrel KS8851 SPI"
 868         depends on SPI
 869         select MII
 870         select CRC32
 871         help
 872           SPI driver for Micrel KS8851 SPI attached network chip.
 873
 874 config KS8851_MLL
 875         tristate "Micrel KS8851 MLL"
 876         depends on HAS_IOMEM
 877         select MII
 878         help
 879           This platform driver is for Micrel KS8851 Address/data bus
 880           multiplexed network chip.
 881
 882 config VIA_RHINE
 883         tristate "VIA Rhine support"
 884         depends on NET_PCI && PCI
 885         select CRC32
 886         select MII
 887         help
 888           If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
 889           Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
 890           Ethernet functions can also be found integrated on South Bridges
 891           (e.g. VT8235).
 892
 893           To compile this driver as a module, choose M here. The module
 894           will be called via-rhine.
 895
 896 config VIA_RHINE_MMIO
 897         bool "Use MMIO instead of PIO"
 898         depends on VIA_RHINE
 899         help
 900           This instructs the driver to use PCI shared memory (MMIO) instead of
 901           programmed I/O ports (PIO). Enabling this gives an improvement in
 902           processing time in parts of the driver.
 903
 904           If unsure, say Y.
 905
 906 config SC92031
 907         tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
 908         depends on NET_PCI && PCI && EXPERIMENTAL
 909         select CRC32
 910         ---help---
 911           This is a driver for the Fast Ethernet PCI network cards based on
 912           the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
 913           have one of these, say Y here.
 914
 915           To compile this driver as a module, choose M here: the module
 916           will be called sc92031.  This is recommended.
 917
 918 config CPMAC
 919         tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
 920         depends on NET_ETHERNET && EXPERIMENTAL && AR7
 921         select PHYLIB
 922         help
 923           TI AR7 CPMAC Ethernet support
 924
 925 config NET_POCKET
 926         bool "Pocket and portable adapters"
 927         depends on PARPORT
 928         ---help---
 929           Cute little network (Ethernet) devices which attach to the parallel
 930           port ("pocket adapters"), commonly used with laptops. If you have
 931           one of those, say Y and read the Ethernet-HOWTO, available from
 932           <http://www.tldp.org/docs.html#howto>.
 933
 934           If you want to plug a network (or some other) card into the PCMCIA
 935           (or PC-card) slot of your laptop instead (PCMCIA is the standard for
 936           credit card size extension cards used by all modern laptops), you
 937           need the pcmcia-cs package (location contained in the file
 938           <file:Documentation/Changes>) and you can say N here.
 939
 940           Laptop users should read the Linux Laptop home page at
 941           <http://www.linux-on-laptops.com/> or
 942           Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
 943
 944           Note that the answer to this question doesn't directly affect the
 945           kernel: saying N will just cause the configurator to skip all
 946           the questions about this class of network devices. If you say Y, you
 947           will be asked for your specific device in the following questions.
 948
 949 config ATP
 950         tristate "AT-LAN-TEC/RealTek pocket adapter support"
 951         depends on NET_POCKET && PARPORT && X86
 952         select CRC32
 953         ---help---
 954           This is a network (Ethernet) device which attaches to your parallel
 955           port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
 956           available from <http://www.tldp.org/docs.html#howto>, if you
 957           want to use this.  If you intend to use this driver, you should have
 958           said N to the "Parallel printer support", because the two drivers
 959           don't like each other.
 960
 961           To compile this driver as a module, choose M here: the module
 962           will be called atp.
 963
 964 config DE600
 965         tristate "D-Link DE600 pocket adapter support"
 966         depends on NET_POCKET && PARPORT
 967         ---help---
 968           This is a network (Ethernet) device which attaches to your parallel
 969           port. Read <file:Documentation/networking/DLINK.txt> as well as the
 970           Ethernet-HOWTO, available from
 971           <http://www.tldp.org/docs.html#howto>, if you want to use
 972           this. It is possible to have several devices share a single parallel
 973           port and it is safe to compile the corresponding drivers into the
 974           kernel.
 975
 976           To compile this driver as a module, choose M here: the module
 977           will be called de600.
 978
 979 config DE620
 980         tristate "D-Link DE620 pocket adapter support"
 981         depends on NET_POCKET && PARPORT
 982         ---help---
 983           This is a network (Ethernet) device which attaches to your parallel
 984           port. Read <file:Documentation/networking/DLINK.txt> as well as the
 985           Ethernet-HOWTO, available from
 986           <http://www.tldp.org/docs.html#howto>, if you want to use
 987           this. It is possible to have several devices share a single parallel
 988           port and it is safe to compile the corresponding drivers into the
 989           kernel.
 990
 991           To compile this driver as a module, choose M here: the module
 992           will be called de620.
 993
 994 config SGISEEQ
 995         tristate "SGI Seeq ethernet controller support"
 996         depends on SGI_HAS_SEEQ
 997         help
 998           Say Y here if you have an Seeq based Ethernet network card. This is
 999           used in many Silicon Graphics machines.
1000
1001 config FEC
1002         bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1003         depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1004                 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1005         default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1006         select PHYLIB
1007         help
1008           Say Y here if you want to use the built-in 10/100 Fast ethernet
1009           controller on some Motorola ColdFire and Freescale i.MX processors.
1010
1011 config FEC_MPC52xx
1012         tristate "MPC52xx FEC driver"
1013         depends on PPC_MPC52xx && PPC_BESTCOMM
1014         select CRC32
1015         select PHYLIB
1016         select PPC_BESTCOMM_FEC
1017         ---help---
1018           This option enables support for the MPC5200's on-chip
1019           Fast Ethernet Controller
1020           If compiled as module, it will be called fec_mpc52xx.
1021
1022 config FEC_MPC52xx_MDIO
1023         bool "MPC52xx FEC MDIO bus driver"
1024         depends on FEC_MPC52xx
1025         default y
1026         ---help---
1027           The MPC5200's FEC can connect to the Ethernet either with
1028           an external MII PHY chip or 10 Mbps 7-wire interface
1029           (Motorola? industry standard).
1030           If your board uses an external PHY connected to FEC, enable this.
1031           If not sure, enable.
1032           If compiled as module, it will be called fec_mpc52xx_phy.
1033
1034 config ATL2
1035         tristate "Atheros L2 Fast Ethernet support"
1036         depends on PCI
1037         select CRC32
1038         select MII
1039         help
1040           This driver supports the Atheros L2 fast ethernet adapter.
1041
1042           To compile this driver as a module, choose M here.  The module
1043           will be called atl2.
1044
1045 config XILINX_EMACLITE
1046         tristate "Xilinx 10/100 Ethernet Lite support"
1047         depends on PPC32 || MICROBLAZE
1048         select PHYLIB
1049         help
1050           This driver supports the 10/100 Ethernet Lite from Xilinx.
1051
1052 config FTMAC100
1053         tristate "Faraday FTMAC100 10/100 Ethernet support"
1054         depends on ARM
1055         select MII
1056         help
1057           This driver supports the FTMAC100 10/100 Ethernet controller
1058           from Faraday. It is used on Faraday A320, Andes AG101 and some
1059           other ARM/NDS32 SoC's.
1060
1061 config LANTIQ_ETOP
1062         tristate "Lantiq SoC ETOP driver"
1063         depends on SOC_TYPE_XWAY
1064         help
1065           Support for the MII0 inside the Lantiq SoC
1066
1067
1068 source "drivers/net/fs_enet/Kconfig"
1069
1070 source "drivers/net/octeon/Kconfig"
1071
1072 endif # NET_ETHERNET
1073
1074 #
1075 #       Gigabit Ethernet
1076 #
1077
1078 menuconfig NETDEV_1000
1079         bool "Ethernet (1000 Mbit)"
1080         depends on !UML
1081         default y
1082         ---help---
1083           Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1084           type of Local Area Network (LAN) in universities and companies.
1085
1086           Say Y here to get to see options for Gigabit Ethernet drivers.
1087           This option alone does not add any kernel code.
1088           Note that drivers supporting both 100 and 1000 MBit may be listed
1089           under "Ethernet (10 or 100MBit)" instead.
1090
1091           If you say N, all options in this submenu will be skipped and disabled.
1092
1093 if NETDEV_1000
1094
1095 config DL2K
1096         tristate "DL2000/TC902x-based Gigabit Ethernet support"
1097         depends on PCI
1098         select CRC32
1099         help
1100           This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1101           which includes
1102           D-Link DGE-550T Gigabit Ethernet Adapter.
1103           D-Link DL2000-based Gigabit Ethernet Adapter.
1104           Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1105
1106           To compile this driver as a module, choose M here: the
1107           module will be called dl2k.
1108
1109 config IP1000
1110         tristate "IP1000 Gigabit Ethernet support"
1111         depends on PCI && EXPERIMENTAL
1112         select MII
1113         ---help---
1114           This driver supports IP1000 gigabit Ethernet cards.
1115
1116           To compile this driver as a module, choose M here: the module
1117           will be called ipg.  This is recommended.
1118
1119 source "drivers/net/ixp2000/Kconfig"
1120
1121 config NS83820
1122         tristate "National Semiconductor DP83820 support"
1123         depends on PCI
1124         help
1125           This is a driver for the National Semiconductor DP83820 series
1126           of gigabit ethernet MACs.  Cards using this chipset include
1127           the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
1128           SOHO-GA2000T, SOHO-GA2500T.  The driver supports the use of
1129           zero copy.
1130
1131 config HAMACHI
1132         tristate "Packet Engines Hamachi GNIC-II support"
1133         depends on PCI
1134         select MII
1135         help
1136           If you have a Gigabit Ethernet card of this type, say Y and read
1137           the Ethernet-HOWTO, available from
1138           <http://www.tldp.org/docs.html#howto>.
1139
1140           To compile this driver as a module, choose M here. The module will be
1141           called hamachi.
1142
1143 config YELLOWFIN
1144         tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
1145         depends on PCI && EXPERIMENTAL
1146         select CRC32
1147         ---help---
1148           Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
1149           adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
1150           used by the Beowulf Linux cluster project.  See
1151           <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
1152           information about this driver in particular and Beowulf in general.
1153
1154           To compile this driver as a module, choose M here: the module
1155           will be called yellowfin.  This is recommended.
1156
1157 config R8169
1158         tristate "Realtek 8169 gigabit ethernet support"
1159         depends on PCI
1160         select FW_LOADER
1161         select CRC32
1162         select MII
1163         ---help---
1164           Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
1165
1166           To compile this driver as a module, choose M here: the module
1167           will be called r8169.  This is recommended.
1168
1169 config SIS190
1170         tristate "SiS190/SiS191 gigabit ethernet support"
1171         depends on PCI
1172         select CRC32
1173         select MII
1174         ---help---
1175           Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
1176           a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
1177           appear in lan on motherboard designs which are based on SiS 965
1178           and SiS 966 south bridge.
1179
1180           To compile this driver as a module, choose M here: the module
1181           will be called sis190.  This is recommended.
1182
1183 config SKGE
1184         tristate "Marvell Yukon Gigabit Ethernet support"
1185         depends on PCI
1186         select CRC32
1187         ---help---
1188           This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
1189           and related Gigabit Ethernet adapters. It is a new smaller driver
1190           with better performance and more complete ethtool support.
1191
1192           It does not support the link failover and network management
1193           features that "portable" vendor supplied sk98lin driver does.
1194
1195           This driver supports adapters based on the original Yukon chipset:
1196           Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
1197           Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
1198
1199           It does not support the newer Yukon2 chipset: a separate driver,
1200           sky2, is provided for these adapters.
1201
1202           To compile this driver as a module, choose M here: the module
1203           will be called skge.  This is recommended.
1204
1205 config SKGE_DEBUG
1206         bool "Debugging interface"
1207         depends on SKGE && DEBUG_FS
1208         help
1209           This option adds the ability to dump driver state for debugging.
1210           The file /sys/kernel/debug/skge/ethX displays the state of the internal
1211           transmit and receive rings.
1212
1213           If unsure, say N.
1214
1215 config SKGE_GENESIS
1216        bool "Support for older SysKonnect Genesis boards"
1217        depends on SKGE
1218        help
1219          This enables support for the older and uncommon SysKonnect Genesis
1220          chips, which support MII via an external transceiver, instead of
1221          an internal one. Disabling this option will save some memory
1222          by making code smaller. If unsure say Y.
1223
1224 config SKY2
1225         tristate "Marvell Yukon 2 support"
1226         depends on PCI
1227         select CRC32
1228         ---help---
1229           This driver supports Gigabit Ethernet adapters based on the
1230           Marvell Yukon 2 chipset:
1231           Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
1232           88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
1233
1234           There is companion driver for the older Marvell Yukon and
1235           SysKonnect Genesis based adapters: skge.
1236
1237           To compile this driver as a module, choose M here: the module
1238           will be called sky2.  This is recommended.
1239
1240 config SKY2_DEBUG
1241         bool "Debugging interface"
1242         depends on SKY2 && DEBUG_FS
1243         help
1244           This option adds the ability to dump driver state for debugging.
1245           The file /sys/kernel/debug/sky2/ethX displays the state of the internal
1246           transmit and receive rings.
1247
1248           If unsure, say N.
1249
1250 config VIA_VELOCITY
1251         tristate "VIA Velocity support"
1252         depends on PCI
1253         select CRC32
1254         select CRC_CCITT
1255         select MII
1256         help
1257           If you have a VIA "Velocity" based network card say Y here.
1258
1259           To compile this driver as a module, choose M here. The module
1260           will be called via-velocity.
1261
1262 config SPIDER_NET
1263         tristate "Spider Gigabit Ethernet driver"
1264         depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
1265         select FW_LOADER
1266         help
1267           This driver supports the Gigabit Ethernet chips present on the
1268           Cell Processor-Based Blades from IBM.
1269
1270 config TSI108_ETH
1271         tristate "Tundra TSI108 gigabit Ethernet support"
1272         depends on TSI108_BRIDGE
1273         help
1274           This driver supports Tundra TSI108 gigabit Ethernet ports.
1275           To compile this driver as a module, choose M here: the module
1276           will be called tsi108_eth.
1277
1278 config GELIC_NET
1279         tristate "PS3 Gigabit Ethernet driver"
1280         depends on PPC_PS3
1281         select PS3_SYS_MANAGER
1282         help
1283           This driver supports the network device on the PS3 game
1284           console.  This driver has built-in support for Ethernet.
1285
1286           To compile this driver as a module, choose M here: the
1287           module will be called ps3_gelic.
1288
1289 config GELIC_WIRELESS
1290         bool "PS3 Wireless support"
1291         depends on WLAN
1292         depends on GELIC_NET
1293         select WIRELESS_EXT
1294         help
1295           This option adds the support for the wireless feature of PS3.
1296           If you have the wireless-less model of PS3 or have no plan to
1297           use wireless feature, disabling this option saves memory.  As
1298           the driver automatically distinguishes the models, you can
1299           safely enable this option even if you have a wireless-less model.
1300
1301 config FSL_PQ_MDIO
1302         tristate "Freescale PQ MDIO"
1303         depends on FSL_SOC
1304         select PHYLIB
1305         help
1306           This driver supports the MDIO bus used by the gianfar and UCC drivers.
1307
1308 config GIANFAR
1309         tristate "Gianfar Ethernet"
1310         depends on FSL_SOC
1311         select FSL_PQ_MDIO
1312         select PHYLIB
1313         select CRC32
1314         help
1315           This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
1316           and MPC86xx family of chips, and the FEC on the 8540.
1317
1318 config UCC_GETH
1319         tristate "Freescale QE Gigabit Ethernet"
1320         depends on QUICC_ENGINE
1321         select FSL_PQ_MDIO
1322         select PHYLIB
1323         help
1324           This driver supports the Gigabit Ethernet mode of the QUICC Engine,
1325           which is available on some Freescale SOCs.
1326
1327 config UGETH_TX_ON_DEMAND
1328         bool "Transmit on Demand support"
1329         depends on UCC_GETH
1330
1331 config MV643XX_ETH
1332         tristate "Marvell Discovery (643XX) and Orion ethernet support"
1333         depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
1334         select INET_LRO
1335         select PHYLIB
1336         help
1337           This driver supports the gigabit ethernet MACs in the
1338           Marvell Discovery PPC/MIPS chipset family (MV643XX) and
1339           in the Marvell Orion ARM SoC family.
1340
1341           Some boards that use the Discovery chipset are the Momenco
1342           Ocelot C and Jaguar ATX and Pegasos II.
1343
1344 config XILINX_LL_TEMAC
1345         tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
1346         depends on PPC || MICROBLAZE
1347         select PHYLIB
1348         help
1349           This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
1350           core used in Xilinx Spartan and Virtex FPGAs
1351
1352 config ATL1
1353         tristate "Atheros/Attansic L1 Gigabit Ethernet support"
1354         depends on PCI
1355         select CRC32
1356         select MII
1357         help
1358           This driver supports the Atheros/Attansic L1 gigabit ethernet
1359           adapter.
1360
1361           To compile this driver as a module, choose M here.  The module
1362           will be called atl1.
1363
1364 config ATL1E
1365         tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
1366         depends on PCI && EXPERIMENTAL
1367         select CRC32
1368         select MII
1369         help
1370           This driver supports the Atheros L1E gigabit ethernet adapter.
1371
1372           To compile this driver as a module, choose M here.  The module
1373           will be called atl1e.
1374
1375 config ATL1C
1376         tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
1377         depends on PCI && EXPERIMENTAL
1378         select CRC32
1379         select MII
1380         help
1381           This driver supports the Atheros L1C gigabit ethernet adapter.
1382
1383           To compile this driver as a module, choose M here.  The module
1384           will be called atl1c.
1385
1386 config JME
1387         tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
1388         depends on PCI
1389         select CRC32
1390         select MII
1391         ---help---
1392           This driver supports the PCI-Express gigabit ethernet adapters
1393           based on JMicron JMC250 chipset.
1394
1395           To compile this driver as a module, choose M here. The module
1396           will be called jme.
1397
1398 config S6GMAC
1399         tristate "S6105 GMAC ethernet support"
1400         depends on XTENSA_VARIANT_S6000
1401         select PHYLIB
1402         help
1403           This driver supports the on chip ethernet device on the
1404           S6105 xtensa processor.
1405
1406           To compile this driver as a module, choose M here. The module
1407           will be called s6gmac.
1408
1409 source "drivers/net/stmmac/Kconfig"
1410
1411 config PCH_GBE
1412         tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
1413         depends on PCI
1414         select MII
1415         ---help---
1416           This is a gigabit ethernet driver for EG20T PCH.
1417           EG20T PCH is the platform controller hub that is used in Intel's
1418           general embedded platform.
1419           EG20T PCH has Gigabit Ethernet interface.
1420           Using this interface, it is able to access system devices connected
1421           to Gigabit Ethernet.
1422           This driver enables Gigabit Ethernet function.
1423
1424           This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
1425           Output Hub), ML7223.
1426           ML7223 IOH is for MP(Media Phone) use.
1427           ML7223 is companion chip for Intel Atom E6xx series.
1428           ML7223 is completely compatible for Intel EG20T PCH.
1429
1430 config FTGMAC100
1431         tristate "Faraday FTGMAC100 Gigabit Ethernet support"
1432         depends on ARM
1433         select PHYLIB
1434         help
1435           This driver supports the FTGMAC100 Gigabit Ethernet controller
1436           from Faraday. It is used on Faraday A369, Andes AG102 and some
1437           other ARM/NDS32 SoC's.
1438
1439 endif # NETDEV_1000
1440
1441 #
1442 #       10 Gigabit Ethernet
1443 #
1444
1445 menuconfig NETDEV_10000
1446         bool "Ethernet (10000 Mbit)"
1447         depends on !UML
1448         default y
1449         ---help---
1450           Say Y here to get to see options for 10 Gigabit Ethernet drivers.
1451           This option alone does not add any kernel code.
1452
1453           If you say N, all options in this submenu will be skipped and disabled.
1454
1455 if NETDEV_10000
1456
1457 config MDIO
1458         tristate
1459
1460 config TEHUTI
1461         tristate "Tehuti Networks 10G Ethernet"
1462         depends on PCI
1463         help
1464           Tehuti Networks 10G Ethernet NIC
1465
1466 endif # NETDEV_10000
1467
1468 source "drivers/net/tokenring/Kconfig"
1469
1470 source "drivers/net/wireless/Kconfig"
1471
1472 source "drivers/net/wimax/Kconfig"
1473
1474 source "drivers/net/usb/Kconfig"
1475
1476 source "drivers/net/pcmcia/Kconfig"
1477
1478 source "drivers/net/wan/Kconfig"
1479
1480 source "drivers/atm/Kconfig"
1481
1482 source "drivers/ieee802154/Kconfig"
1483
1484 source "drivers/s390/net/Kconfig"
1485
1486 source "drivers/net/caif/Kconfig"
1487
1488 config TILE_NET
1489         tristate "Tilera GBE/XGBE network driver support"
1490         depends on TILE
1491         default y
1492         select CRC32
1493         help
1494           This is a standard Linux network device driver for the
1495           on-chip Tilera Gigabit Ethernet and XAUI interfaces.
1496
1497           To compile this driver as a module, choose M here: the module
1498           will be called tile_net.
1499
1500 config XEN_NETDEV_FRONTEND
1501         tristate "Xen network device frontend driver"
1502         depends on XEN
1503         select XEN_XENBUS_FRONTEND
1504         default y
1505         help
1506           This driver provides support for Xen paravirtual network
1507           devices exported by a Xen network driver domain (often
1508           domain 0).
1509
1510           The corresponding Linux backend driver is enabled by the
1511           CONFIG_XEN_NETDEV_BACKEND option.
1512
1513           If you are compiling a kernel for use as Xen guest, you
1514           should say Y here. To compile this driver as a module, chose
1515           M here: the module will be called xen-netfront.
1516
1517 config XEN_NETDEV_BACKEND
1518         tristate "Xen backend network device"
1519         depends on XEN_BACKEND
1520         help
1521           This driver allows the kernel to act as a Xen network driver
1522           domain which exports paravirtual network devices to other
1523           Xen domains. These devices can be accessed by any operating
1524           system that implements a compatible front end.
1525
1526           The corresponding Linux frontend driver is enabled by the
1527           CONFIG_XEN_NETDEV_FRONTEND configuration option.
1528
1529           The backend driver presents a standard network device
1530           endpoint for each paravirtual network device to the driver
1531           domain network stack. These can then be bridged or routed
1532           etc in order to provide full network connectivity.
1533
1534           If you are compiling a kernel to run in a Xen network driver
1535           domain (often this is domain 0) you should say Y here. To
1536           compile this driver as a module, chose M here: the module
1537           will be called xen-netback.
1538
1539 config RIONET
1540         tristate "RapidIO Ethernet over messaging driver support"
1541         depends on RAPIDIO
1542
1543 config RIONET_TX_SIZE
1544         int "Number of outbound queue entries"
1545         depends on RIONET
1546         default "128"
1547
1548 config RIONET_RX_SIZE
1549         int "Number of inbound queue entries"
1550         depends on RIONET
1551         default "128"
1552
1553 config FDDI
1554         tristate "FDDI driver support"
1555         depends on (PCI || EISA || TC)
1556         help
1557           Fiber Distributed Data Interface is a high speed local area network
1558           design; essentially a replacement for high speed Ethernet. FDDI can
1559           run over copper or fiber. If you are connected to such a network and
1560           want a driver for the FDDI card in your computer, say Y here (and
1561           then also Y to the driver for your FDDI card, below). Most people
1562           will say N.
1563
1564 config DEFXX
1565         tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
1566         depends on FDDI && (PCI || EISA || TC)
1567         ---help---
1568           This is support for the DIGITAL series of TURBOchannel (DEFTA),
1569           EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
1570           to a local FDDI network.
1571
1572           To compile this driver as a module, choose M here: the module
1573           will be called defxx.  If unsure, say N.
1574
1575 config DEFXX_MMIO
1576         bool
1577         prompt "Use MMIO instead of PIO" if PCI || EISA
1578         depends on DEFXX
1579         default n if PCI || EISA
1580         default y
1581         ---help---
1582           This instructs the driver to use EISA or PCI memory-mapped I/O
1583           (MMIO) as appropriate instead of programmed I/O ports (PIO).
1584           Enabling this gives an improvement in processing time in parts
1585           of the driver, but it may cause problems with EISA (DEFEA)
1586           adapters.  TURBOchannel does not have the concept of I/O ports,
1587           so MMIO is always used for these (DEFTA) adapters.
1588
1589           If unsure, say N.
1590
1591 config SKFP
1592         tristate "SysKonnect FDDI PCI support"
1593         depends on FDDI && PCI
1594         select BITREVERSE
1595         ---help---
1596           Say Y here if you have a SysKonnect FDDI PCI adapter.
1597           The following adapters are supported by this driver:
1598           - SK-5521 (SK-NET FDDI-UP)
1599           - SK-5522 (SK-NET FDDI-UP DAS)
1600           - SK-5541 (SK-NET FDDI-FP)
1601           - SK-5543 (SK-NET FDDI-LP)
1602           - SK-5544 (SK-NET FDDI-LP DAS)
1603           - SK-5821 (SK-NET FDDI-UP64)
1604           - SK-5822 (SK-NET FDDI-UP64 DAS)
1605           - SK-5841 (SK-NET FDDI-FP64)
1606           - SK-5843 (SK-NET FDDI-LP64)
1607           - SK-5844 (SK-NET FDDI-LP64 DAS)
1608           - Netelligent 100 FDDI DAS Fibre SC
1609           - Netelligent 100 FDDI SAS Fibre SC
1610           - Netelligent 100 FDDI DAS UTP
1611           - Netelligent 100 FDDI SAS UTP
1612           - Netelligent 100 FDDI SAS Fibre MIC
1613
1614           Read <file:Documentation/networking/skfp.txt> for information about
1615           the driver.
1616
1617           Questions concerning this driver can be addressed to:
1618           <linux@syskonnect.de>
1619
1620           To compile this driver as a module, choose M here: the module
1621           will be called skfp.  This is recommended.
1622
1623 config HIPPI
1624         bool "HIPPI driver support (EXPERIMENTAL)"
1625         depends on EXPERIMENTAL && INET && PCI
1626         help
1627           HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1628           1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
1629           can run over copper (25m) or fiber (300m on multi-mode or 10km on
1630           single-mode). HIPPI networks are commonly used for clusters and to
1631           connect to super computers. If you are connected to a HIPPI network
1632           and have a HIPPI network card in your computer that you want to use
1633           under Linux, say Y here (you must also remember to enable the driver
1634           for your HIPPI card below). Most people will say N here.
1635
1636 config ROADRUNNER
1637         tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
1638         depends on HIPPI && PCI
1639         help
1640           Say Y here if this is your PCI HIPPI network card.
1641
1642           To compile this driver as a module, choose M here: the module
1643           will be called rrunner.  If unsure, say N.
1644
1645 config ROADRUNNER_LARGE_RINGS
1646         bool "Use large TX/RX rings (EXPERIMENTAL)"
1647         depends on ROADRUNNER
1648         help
1649           If you say Y here, the RoadRunner driver will preallocate up to 2 MB
1650           of additional memory to allow for fastest operation, both for
1651           transmitting and receiving. This memory cannot be used by any other
1652           kernel code or by user space programs. Say Y here only if you have
1653           the memory.
1654
1655 config PLIP
1656         tristate "PLIP (parallel port) support"
1657         depends on PARPORT
1658         ---help---
1659           PLIP (Parallel Line Internet Protocol) is used to create a
1660           reasonably fast mini network consisting of two (or, rarely, more)
1661           local machines.  A PLIP link from a Linux box is a popular means to
1662           install a Linux distribution on a machine which doesn't have a
1663           CD-ROM drive (a minimal system has to be transferred with floppies
1664           first). The kernels on both machines need to have this PLIP option
1665           enabled for this to work.
1666
1667           The PLIP driver has two modes, mode 0 and mode 1.  The parallel
1668           ports (the connectors at the computers with 25 holes) are connected
1669           with "null printer" or "Turbo Laplink" cables which can transmit 4
1670           bits at a time (mode 0) or with special PLIP cables, to be used on
1671           bidirectional parallel ports only, which can transmit 8 bits at a
1672           time (mode 1); you can find the wiring of these cables in
1673           <file:Documentation/networking/PLIP.txt>.  The cables can be up to
1674           15m long.  Mode 0 works also if one of the machines runs DOS/Windows
1675           and has some PLIP software installed, e.g. the Crynwr PLIP packet
1676           driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
1677           and winsock or NCSA's telnet.
1678
1679           If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
1680           as the NET-3-HOWTO, both available from
1681           <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
1682           protocol has been changed and this PLIP driver won't work together
1683           with the PLIP support in Linux versions 1.0.x.  This option enlarges
1684           your kernel by about 8 KB.
1685
1686           To compile this driver as a module, choose M here. The module
1687           will be called plip. If unsure, say Y or M, in case you buy
1688           a laptop later.
1689
1690 config PPP
1691         tristate "PPP (point-to-point protocol) support"
1692         select SLHC
1693         ---help---
1694           PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
1695           the same purpose: sending Internet traffic over telephone (and other
1696           serial) lines.  Ask your access provider if they support it, because
1697           otherwise you can't use it; most Internet access providers these
1698           days support PPP rather than SLIP.
1699
1700           To use PPP, you need an additional program called pppd as described
1701           in the PPP-HOWTO, available at
1702           <http://www.tldp.org/docs.html#howto>.  Make sure that you have
1703           the version of pppd recommended in <file:Documentation/Changes>.
1704           The PPP option enlarges your kernel by about 16 KB.
1705
1706           There are actually two versions of PPP: the traditional PPP for
1707           asynchronous lines, such as regular analog phone lines, and
1708           synchronous PPP which can be used over digital ISDN lines for
1709           example.  If you want to use PPP over phone lines or other
1710           asynchronous serial lines, you need to say Y (or M) here and also to
1711           the next option, "PPP support for async serial ports".  For PPP over
1712           synchronous lines, you should say Y (or M) here and to "Support
1713           synchronous PPP", below.
1714
1715           If you said Y to "Version information on all symbols" above, then
1716           you cannot compile the PPP driver into the kernel; you can then only
1717           compile it as a module. To compile this driver as a module, choose M
1718           here. The module will be called ppp_generic.
1719
1720 config PPP_MULTILINK
1721         bool "PPP multilink support (EXPERIMENTAL)"
1722         depends on PPP && EXPERIMENTAL
1723         help
1724           PPP multilink is a protocol (defined in RFC 1990) which allows you
1725           to combine several (logical or physical) lines into one logical PPP
1726           connection, so that you can utilize your full bandwidth.
1727
1728           This has to be supported at the other end as well and you need a
1729           version of the pppd daemon which understands the multilink protocol.
1730
1731           If unsure, say N.
1732
1733 config PPP_FILTER
1734         bool "PPP filtering"
1735         depends on PPP
1736         help
1737           Say Y here if you want to be able to filter the packets passing over
1738           PPP interfaces.  This allows you to control which packets count as
1739           activity (i.e. which packets will reset the idle timer or bring up
1740           a demand-dialed link) and which packets are to be dropped entirely.
1741           You need to say Y here if you wish to use the pass-filter and
1742           active-filter options to pppd.
1743
1744           If unsure, say N.
1745
1746 config PPP_ASYNC
1747         tristate "PPP support for async serial ports"
1748         depends on PPP
1749         select CRC_CCITT
1750         ---help---
1751           Say Y (or M) here if you want to be able to use PPP over standard
1752           asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
1753           a modem (not a synchronous or ISDN modem) to contact your ISP, you
1754           need this option.
1755
1756           To compile this driver as a module, choose M here.
1757
1758           If unsure, say Y.
1759
1760 config PPP_SYNC_TTY
1761         tristate "PPP support for sync tty ports"
1762         depends on PPP
1763         help
1764           Say Y (or M) here if you want to be able to use PPP over synchronous
1765           (HDLC) tty devices, such as the SyncLink adapter. These devices
1766           are often used for high-speed leased lines like T1/E1.
1767
1768           To compile this driver as a module, choose M here.
1769
1770 config PPP_DEFLATE
1771         tristate "PPP Deflate compression"
1772         depends on PPP
1773         select ZLIB_INFLATE
1774         select ZLIB_DEFLATE
1775         ---help---
1776           Support for the Deflate compression method for PPP, which uses the
1777           Deflate algorithm (the same algorithm that gzip uses) to compress
1778           each PPP packet before it is sent over the wire.  The machine at the
1779           other end of the PPP link (usually your ISP) has to support the
1780           Deflate compression method as well for this to be useful.  Even if
1781           they don't support it, it is safe to say Y here.
1782
1783           To compile this driver as a module, choose M here.
1784
1785 config PPP_BSDCOMP
1786         tristate "PPP BSD-Compress compression"
1787         depends on PPP
1788         ---help---
1789           Support for the BSD-Compress compression method for PPP, which uses
1790           the LZW compression method to compress each PPP packet before it is
1791           sent over the wire. The machine at the other end of the PPP link
1792           (usually your ISP) has to support the BSD-Compress compression
1793           method as well for this to be useful. Even if they don't support it,
1794           it is safe to say Y here.
1795
1796           The PPP Deflate compression method ("PPP Deflate compression",
1797           above) is preferable to BSD-Compress, because it compresses better
1798           and is patent-free.
1799
1800           Note that the BSD compression code will always be compiled as a
1801           module; it is called bsd_comp and will show up in the directory
1802           modules once you have said "make modules". If unsure, say N.
1803
1804 config PPP_MPPE
1805         tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1806         depends on PPP && EXPERIMENTAL
1807         select CRYPTO
1808         select CRYPTO_SHA1
1809         select CRYPTO_ARC4
1810         select CRYPTO_ECB
1811         ---help---
1812           Support for the MPPE Encryption protocol, as employed by the
1813           Microsoft Point-to-Point Tunneling Protocol.
1814
1815           See http://pptpclient.sourceforge.net/ for information on
1816           configuring PPTP clients and servers to utilize this method.
1817
1818 config PPPOE
1819         tristate "PPP over Ethernet (EXPERIMENTAL)"
1820         depends on EXPERIMENTAL && PPP
1821         help
1822           Support for PPP over Ethernet.
1823
1824           This driver requires the latest version of pppd from the CVS
1825           repository at cvs.samba.org.  Alternatively, see the
1826           RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1827           which contains instruction on how to use this driver (under
1828           the heading "Kernel mode PPPoE").
1829
1830 config PPTP
1831         tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1832         depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1833         help
1834           Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1835
1836           This driver requires pppd plugin to work in client mode or
1837           modified pptpd (poptop) to work in server mode.
1838           See http://accel-pptp.sourceforge.net/ for information how to
1839           utilize this module.
1840
1841 config PPPOATM
1842         tristate "PPP over ATM"
1843         depends on ATM && PPP
1844         help
1845           Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1846           This implementation does not yet comply with section 8 of RFC2364,
1847           which can lead to bad results if the ATM peer loses state and
1848           changes its encapsulation unilaterally.
1849
1850 config PPPOL2TP
1851         tristate "PPP over L2TP (EXPERIMENTAL)"
1852         depends on EXPERIMENTAL && L2TP && PPP
1853         help
1854           Support for PPP-over-L2TP socket family. L2TP is a protocol
1855           used by ISPs and enterprises to tunnel PPP traffic over UDP
1856           tunnels. L2TP is replacing PPTP for VPN uses.
1857
1858 config SLIP
1859         tristate "SLIP (serial line) support"
1860         ---help---
1861           Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1862           connect to your Internet service provider or to connect to some
1863           other local Unix box or if you want to configure your Linux box as a
1864           Slip/CSlip server for other people to dial in. SLIP (Serial Line
1865           Internet Protocol) is a protocol used to send Internet traffic over
1866           serial connections such as telephone lines or null modem cables;
1867           nowadays, the protocol PPP is more commonly used for this same
1868           purpose.
1869
1870           Normally, your access provider has to support SLIP in order for you
1871           to be able to use it, but there is now a SLIP emulator called SLiRP
1872           around (available from
1873           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1874           allows you to use SLIP over a regular dial up shell connection. If
1875           you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1876           NET-3-HOWTO, available from
1877           <http://www.tldp.org/docs.html#howto>, explains how to
1878           configure SLIP. Note that you don't need this option if you just
1879           want to run term (term is a program which gives you almost full
1880           Internet connectivity if you have a regular dial up shell account on
1881           some Internet connected Unix computer. Read
1882           <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1883           support will enlarge your kernel by about 4 KB. If unsure, say N.
1884
1885           To compile this driver as a module, choose M here. The module
1886           will be called slip.
1887
1888 config SLIP_COMPRESSED
1889         bool "CSLIP compressed headers"
1890         depends on SLIP
1891         select SLHC
1892         ---help---
1893           This protocol is faster than SLIP because it uses compression on the
1894           TCP/IP headers (not on the data itself), but it has to be supported
1895           on both ends. Ask your access provider if you are not sure and
1896           answer Y, just in case. You will still be able to use plain SLIP. If
1897           you plan to use SLiRP, the SLIP emulator (available from
1898           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1899           allows you to use SLIP over a regular dial up shell connection, you
1900           definitely want to say Y here. The NET-3-HOWTO, available from
1901           <http://www.tldp.org/docs.html#howto>, explains how to configure
1902           CSLIP. This won't enlarge your kernel.
1903
1904 config SLHC
1905         tristate
1906         help
1907           This option enables Van Jacobsen serial line header compression
1908           routines.
1909
1910 config SLIP_SMART
1911         bool "Keepalive and linefill"
1912         depends on SLIP
1913         help
1914           Adds additional capabilities to the SLIP driver to support the
1915           RELCOM line fill and keepalive monitoring. Ideal on poor quality
1916           analogue lines.
1917
1918 config SLIP_MODE_SLIP6
1919         bool "Six bit SLIP encapsulation"
1920         depends on SLIP
1921         help
1922           Just occasionally you may need to run IP over hostile serial
1923           networks that don't pass all control characters or are only seven
1924           bit. Saying Y here adds an extra mode you can use with SLIP:
1925           "slip6". In this mode, SLIP will only send normal ASCII symbols over
1926           the serial device. Naturally, this has to be supported at the other
1927           end of the link as well. It's good enough, for example, to run IP
1928           over the async ports of a Camtec JNT Pad. If unsure, say N.
1929
1930 config NET_FC
1931         bool "Fibre Channel driver support"
1932         depends on SCSI && PCI
1933         help
1934           Fibre Channel is a high speed serial protocol mainly used to connect
1935           large storage devices to the computer; it is compatible with and
1936           intended to replace SCSI.
1937
1938           If you intend to use Fibre Channel, you need to have a Fibre channel
1939           adaptor card in your computer; say Y here and to the driver for your
1940           adaptor below. You also should have said Y to "SCSI support" and
1941           "SCSI generic support".
1942
1943 config NETCONSOLE
1944         tristate "Network console logging support"
1945         ---help---
1946         If you want to log kernel messages over the network, enable this.
1947         See <file:Documentation/networking/netconsole.txt> for details.
1948
1949 config NETCONSOLE_DYNAMIC
1950         bool "Dynamic reconfiguration of logging targets"
1951         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1952                         !(NETCONSOLE=y && CONFIGFS_FS=m)
1953         help
1954           This option enables the ability to dynamically reconfigure target
1955           parameters (interface, IP addresses, port numbers, MAC addresses)
1956           at runtime through a userspace interface exported using configfs.
1957           See <file:Documentation/networking/netconsole.txt> for details.
1958
1959 config NETPOLL
1960         def_bool NETCONSOLE
1961
1962 config NETPOLL_TRAP
1963         bool "Netpoll traffic trapping"
1964         default n
1965         depends on NETPOLL
1966
1967 config NET_POLL_CONTROLLER
1968         def_bool NETPOLL
1969
1970 config VIRTIO_NET
1971         tristate "Virtio network driver (EXPERIMENTAL)"
1972         depends on EXPERIMENTAL && VIRTIO
1973         ---help---
1974           This is the virtual network driver for virtio.  It can be used with
1975           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
1976
1977 config VMXNET3
1978         tristate "VMware VMXNET3 ethernet driver"
1979         depends on PCI && INET
1980         help
1981           This driver supports VMware's vmxnet3 virtual ethernet NIC.
1982           To compile this driver as a module, choose M here: the
1983           module will be called vmxnet3.
1984
1985 endif # NETDEVICES