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