drivers/net/Kconfig

   1 #
   2 # Network device configuration
   3 #
   4
   5 menuconfig NETDEVICES
   6         default y if UML
   7         depends on NET
   8         bool "Network device support"
   9         ---help---
  10           You can say N here if you don't intend to connect your Linux box to
  11           any other computer at all.
  12
  13           You'll have to say Y if your computer contains a network card that
  14           you want to use under Linux. If you are going to run SLIP or PPP over
  15           telephone line or null modem cable you need say Y here. Connecting
  16           two machines with parallel ports using PLIP needs this, as well as
  17           AX.25/KISS for sending Internet traffic over amateur radio links.
  18
  19           See also "The Linux Network Administrator's Guide" by Olaf Kirch and
  20           Terry Dawson. Available at <http://www.tldp.org/guides.html>.
  21
  22           If unsure, say Y.
  23
  24 # All the following symbols are dependent on NETDEVICES - do not repeat
  25 # that for each of the symbols.
  26 if NETDEVICES
  27
  28 config NET_CORE
  29         default y
  30         bool "Network core driver support"
  31         ---help---
  32           You can say N here if you do not intend to use any of the
  33           networking core drivers (i.e. VLAN, bridging, bonding, etc.)
  34
  35 if NET_CORE
  36
  37 config BONDING
  38         tristate "Bonding driver support"
  39         depends on INET
  40         depends on IPV6 || IPV6=n
  41         ---help---
  42           Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
  43           Channels together. This is called 'Etherchannel' by Cisco,
  44           'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
  45
  46           The driver supports multiple bonding modes to allow for both high
  47           performance and high availability operation.
  48
  49           Refer to <file:Documentation/networking/bonding.txt> for more
  50           information.
  51
  52           To compile this driver as a module, choose M here: the module
  53           will be called bonding.
  54
  55 config DUMMY
  56         tristate "Dummy net driver support"
  57         ---help---
  58           This is essentially a bit-bucket device (i.e. traffic you send to
  59           this device is consigned into oblivion) with a configurable IP
  60           address. It is most commonly used in order to make your currently
  61           inactive SLIP address seem like a real address for local programs.
  62           If you use SLIP or PPP, you might want to say Y here. Since this
  63           thing often comes in handy, the default is Y. It won't enlarge your
  64           kernel either. What a deal. Read about it in the Network
  65           Administrator's Guide, available from
  66           <http://www.tldp.org/docs.html#guide>.
  67
  68           To compile this driver as a module, choose M here: the module
  69           will be called dummy.
  70
  71 config EQUALIZER
  72         tristate "EQL (serial line load balancing) support"
  73         ---help---
  74           If you have two serial connections to some other computer (this
  75           usually requires two modems and two telephone lines) and you use
  76           SLIP (the protocol for sending Internet traffic over telephone
  77           lines) or PPP (a better SLIP) on them, you can make them behave like
  78           one double speed connection using this driver.  Naturally, this has
  79           to be supported at the other end as well, either with a similar EQL
  80           Linux driver or with a Livingston Portmaster 2e.
  81
  82           Say Y if you want this and read
  83           <file:Documentation/networking/eql.txt>.  You may also want to read
  84           section 6.2 of the NET-3-HOWTO, available from
  85           <http://www.tldp.org/docs.html#howto>.
  86
  87           To compile this driver as a module, choose M here: the module
  88           will be called eql.  If unsure, say N.
  89
  90 config NET_FC
  91         bool "Fibre Channel driver support"
  92         depends on SCSI && PCI
  93         help
  94           Fibre Channel is a high speed serial protocol mainly used to connect
  95           large storage devices to the computer; it is compatible with and
  96           intended to replace SCSI.
  97
  98           If you intend to use Fibre Channel, you need to have a Fibre channel
  99           adaptor card in your computer; say Y here and to the driver for your
 100           adaptor below. You also should have said Y to "SCSI support" and
 101           "SCSI generic support".
 102
 103 config MII
 104         tristate "Generic Media Independent Interface device support"
 105         help
 106           Most ethernet controllers have MII transceiver either as an external
 107           or internal device.  It is safe to say Y or M here even if your
 108           ethernet card lacks MII.
 109
 110 config IFB
 111         tristate "Intermediate Functional Block support"
 112         depends on NET_CLS_ACT
 113         ---help---
 114           This is an intermediate driver that allows sharing of
 115           resources.
 116           To compile this driver as a module, choose M here: the module
 117           will be called ifb.  If you want to use more than one ifb
 118           device at a time, you need to compile this driver as a module.
 119           Instead of 'ifb', the devices will then be called 'ifb0',
 120           'ifb1' etc.
 121           Look at the iproute2 documentation directory for usage etc
 122
 123 source "drivers/net/team/Kconfig"
 124
 125 config MACVLAN
 126         tristate "MAC-VLAN support (EXPERIMENTAL)"
 127         depends on EXPERIMENTAL
 128         ---help---
 129           This allows one to create virtual interfaces that map packets to
 130           or from specific MAC addresses to a particular interface.
 131
 132           Macvlan devices can be added using the "ip" command from the
 133           iproute2 package starting with the iproute2-2.6.23 release:
 134
 135           "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
 136
 137           To compile this driver as a module, choose M here: the module
 138           will be called macvlan.
 139
 140 config MACVTAP
 141         tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
 142         depends on MACVLAN
 143         help
 144           This adds a specialized tap character device driver that is based
 145           on the MAC-VLAN network interface, called macvtap. A macvtap device
 146           can be added in the same way as a macvlan device, using 'type
 147           macvlan', and then be accessed through the tap user space interface.
 148
 149           To compile this driver as a module, choose M here: the module
 150           will be called macvtap.
 151
 152 config VXLAN
 153        tristate "Virtual eXtensible Local Area Network (VXLAN)"
 154        depends on EXPERIMENTAL && INET
 155        ---help---
 156           This allows one to create vxlan virtual interfaces that provide
 157           Layer 2 Networks over Layer 3 Networks. VXLAN is often used
 158           to tunnel virtual network infrastructure in virtualized environments.
 159           For more information see:
 160             http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
 161
 162           To compile this driver as a module, choose M here: the module
 163           will be called vxlan.
 164
 165 config NETCONSOLE
 166         tristate "Network console logging support"
 167         ---help---
 168         If you want to log kernel messages over the network, enable this.
 169         See <file:Documentation/networking/netconsole.txt> for details.
 170
 171 config NETCONSOLE_DYNAMIC
 172         bool "Dynamic reconfiguration of logging targets"
 173         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
 174                         !(NETCONSOLE=y && CONFIGFS_FS=m)
 175         help
 176           This option enables the ability to dynamically reconfigure target
 177           parameters (interface, IP addresses, port numbers, MAC addresses)
 178           at runtime through a userspace interface exported using configfs.
 179           See <file:Documentation/networking/netconsole.txt> for details.
 180
 181 config NETPOLL
 182         def_bool NETCONSOLE
 183
 184 config NETPOLL_TRAP
 185         bool "Netpoll traffic trapping"
 186         default n
 187         depends on NETPOLL
 188
 189 config NET_POLL_CONTROLLER
 190         def_bool NETPOLL
 191
 192 config RIONET
 193         tristate "RapidIO Ethernet over messaging driver support"
 194         depends on RAPIDIO
 195
 196 config RIONET_TX_SIZE
 197         int "Number of outbound queue entries"
 198         depends on RIONET
 199         default "128"
 200
 201 config RIONET_RX_SIZE
 202         int "Number of inbound queue entries"
 203         depends on RIONET
 204         default "128"
 205
 206 config TUN
 207         tristate "Universal TUN/TAP device driver support"
 208         select CRC32
 209         ---help---
 210           TUN/TAP provides packet reception and transmission for user space
 211           programs.  It can be viewed as a simple Point-to-Point or Ethernet
 212           device, which instead of receiving packets from a physical media,
 213           receives them from user space program and instead of sending packets
 214           via physical media writes them to the user space program.
 215
 216           When a program opens /dev/net/tun, driver creates and registers
 217           corresponding net device tunX or tapX.  After a program closed above
 218           devices, driver will automatically delete tunXX or tapXX device and
 219           all routes corresponding to it.
 220
 221           Please read <file:Documentation/networking/tuntap.txt> for more
 222           information.
 223
 224           To compile this driver as a module, choose M here: the module
 225           will be called tun.
 226
 227           If you don't know what to use this for, you don't need it.
 228
 229 config VETH
 230         tristate "Virtual ethernet pair device"
 231         ---help---
 232           This device is a local ethernet tunnel. Devices are created in pairs.
 233           When one end receives the packet it appears on its pair and vice
 234           versa.
 235
 236 config VIRTIO_NET
 237         tristate "Virtio network driver (EXPERIMENTAL)"
 238         depends on EXPERIMENTAL && VIRTIO
 239         ---help---
 240           This is the virtual network driver for virtio.  It can be used with
 241           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
 242
 243 endif # NET_CORE
 244
 245 config SUNGEM_PHY
 246         tristate
 247
 248 source "drivers/net/arcnet/Kconfig"
 249
 250 source "drivers/atm/Kconfig"
 251
 252 source "drivers/net/caif/Kconfig"
 253
 254 source "drivers/net/dsa/Kconfig"
 255
 256 source "drivers/net/ethernet/Kconfig"
 257
 258 source "drivers/net/fddi/Kconfig"
 259
 260 source "drivers/net/hippi/Kconfig"
 261
 262 config NET_SB1000
 263         tristate "General Instruments Surfboard 1000"
 264         depends on PNP
 265         ---help---
 266           This is a driver for the General Instrument (also known as
 267           NextLevel) SURFboard 1000 internal
 268           cable modem. This is an ISA card which is used by a number of cable
 269           TV companies to provide cable modem access. It's a one-way
 270           downstream-only cable modem, meaning that your upstream net link is
 271           provided by your regular phone modem.
 272
 273           At present this driver only compiles as a module, so say M here if
 274           you have this card. The module will be called sb1000. Then read
 275           <file:Documentation/networking/README.sb1000> for information on how
 276           to use this module, as it needs special ppp scripts for establishing
 277           a connection. Further documentation and the necessary scripts can be
 278           found at:
 279
 280           <http://www.jacksonville.net/~fventuri/>
 281           <http://home.adelphia.net/~siglercm/sb1000.html>
 282           <http://linuxpower.cx/~cable/>
 283
 284           If you don't have this card, of course say N.
 285
 286 source "drivers/net/phy/Kconfig"
 287
 288 source "drivers/net/plip/Kconfig"
 289
 290 source "drivers/net/ppp/Kconfig"
 291
 292 source "drivers/net/slip/Kconfig"
 293
 294 source "drivers/s390/net/Kconfig"
 295
 296 source "drivers/net/usb/Kconfig"
 297
 298 source "drivers/net/wireless/Kconfig"
 299
 300 source "drivers/net/wimax/Kconfig"
 301
 302 source "drivers/net/wan/Kconfig"
 303
 304 source "drivers/net/ieee802154/Kconfig"
 305
 306 config XEN_NETDEV_FRONTEND
 307         tristate "Xen network device frontend driver"
 308         depends on XEN
 309         select XEN_XENBUS_FRONTEND
 310         default y
 311         help
 312           This driver provides support for Xen paravirtual network
 313           devices exported by a Xen network driver domain (often
 314           domain 0).
 315
 316           The corresponding Linux backend driver is enabled by the
 317           CONFIG_XEN_NETDEV_BACKEND option.
 318
 319           If you are compiling a kernel for use as Xen guest, you
 320           should say Y here. To compile this driver as a module, chose
 321           M here: the module will be called xen-netfront.
 322
 323 config XEN_NETDEV_BACKEND
 324         tristate "Xen backend network device"
 325         depends on XEN_BACKEND
 326         help
 327           This driver allows the kernel to act as a Xen network driver
 328           domain which exports paravirtual network devices to other
 329           Xen domains. These devices can be accessed by any operating
 330           system that implements a compatible front end.
 331
 332           The corresponding Linux frontend driver is enabled by the
 333           CONFIG_XEN_NETDEV_FRONTEND configuration option.
 334
 335           The backend driver presents a standard network device
 336           endpoint for each paravirtual network device to the driver
 337           domain network stack. These can then be bridged or routed
 338           etc in order to provide full network connectivity.
 339
 340           If you are compiling a kernel to run in a Xen network driver
 341           domain (often this is domain 0) you should say Y here. To
 342           compile this driver as a module, chose M here: the module
 343           will be called xen-netback.
 344
 345 config VMXNET3
 346         tristate "VMware VMXNET3 ethernet driver"
 347         depends on PCI && INET
 348         help
 349           This driver supports VMware's vmxnet3 virtual ethernet NIC.
 350           To compile this driver as a module, choose M here: the
 351           module will be called vmxnet3.
 352
 353 source "drivers/net/hyperv/Kconfig"
 354
 355 endif # NETDEVICES