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/tokenring/Kconfig"
 201
 202 source "drivers/net/wireless/Kconfig"
 203
 204 source "drivers/net/wimax/Kconfig"
 205
 206 source "drivers/net/usb/Kconfig"
 207
 208 source "drivers/net/pcmcia/Kconfig"
 209
 210 source "drivers/net/ppp/Kconfig"
 211
 212 source "drivers/net/wan/Kconfig"
 213
 214 source "drivers/atm/Kconfig"
 215
 216 source "drivers/ieee802154/Kconfig"
 217
 218 source "drivers/s390/net/Kconfig"
 219
 220 source "drivers/net/caif/Kconfig"
 221
 222 config XEN_NETDEV_FRONTEND
 223         tristate "Xen network device frontend driver"
 224         depends on XEN
 225         select XEN_XENBUS_FRONTEND
 226         default y
 227         help
 228           This driver provides support for Xen paravirtual network
 229           devices exported by a Xen network driver domain (often
 230           domain 0).
 231
 232           The corresponding Linux backend driver is enabled by the
 233           CONFIG_XEN_NETDEV_BACKEND option.
 234
 235           If you are compiling a kernel for use as Xen guest, you
 236           should say Y here. To compile this driver as a module, chose
 237           M here: the module will be called xen-netfront.
 238
 239 config XEN_NETDEV_BACKEND
 240         tristate "Xen backend network device"
 241         depends on XEN_BACKEND
 242         help
 243           This driver allows the kernel to act as a Xen network driver
 244           domain which exports paravirtual network devices to other
 245           Xen domains. These devices can be accessed by any operating
 246           system that implements a compatible front end.
 247
 248           The corresponding Linux frontend driver is enabled by the
 249           CONFIG_XEN_NETDEV_FRONTEND configuration option.
 250
 251           The backend driver presents a standard network device
 252           endpoint for each paravirtual network device to the driver
 253           domain network stack. These can then be bridged or routed
 254           etc in order to provide full network connectivity.
 255
 256           If you are compiling a kernel to run in a Xen network driver
 257           domain (often this is domain 0) you should say Y here. To
 258           compile this driver as a module, chose M here: the module
 259           will be called xen-netback.
 260
 261 config RIONET
 262         tristate "RapidIO Ethernet over messaging driver support"
 263         depends on RAPIDIO
 264
 265 config RIONET_TX_SIZE
 266         int "Number of outbound queue entries"
 267         depends on RIONET
 268         default "128"
 269
 270 config RIONET_RX_SIZE
 271         int "Number of inbound queue entries"
 272         depends on RIONET
 273         default "128"
 274
 275 config PLIP
 276         tristate "PLIP (parallel port) support"
 277         depends on PARPORT
 278         ---help---
 279           PLIP (Parallel Line Internet Protocol) is used to create a
 280           reasonably fast mini network consisting of two (or, rarely, more)
 281           local machines.  A PLIP link from a Linux box is a popular means to
 282           install a Linux distribution on a machine which doesn't have a
 283           CD-ROM drive (a minimal system has to be transferred with floppies
 284           first). The kernels on both machines need to have this PLIP option
 285           enabled for this to work.
 286
 287           The PLIP driver has two modes, mode 0 and mode 1.  The parallel
 288           ports (the connectors at the computers with 25 holes) are connected
 289           with "null printer" or "Turbo Laplink" cables which can transmit 4
 290           bits at a time (mode 0) or with special PLIP cables, to be used on
 291           bidirectional parallel ports only, which can transmit 8 bits at a
 292           time (mode 1); you can find the wiring of these cables in
 293           <file:Documentation/networking/PLIP.txt>.  The cables can be up to
 294           15m long.  Mode 0 works also if one of the machines runs DOS/Windows
 295           and has some PLIP software installed, e.g. the Crynwr PLIP packet
 296           driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
 297           and winsock or NCSA's telnet.
 298
 299           If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
 300           as the NET-3-HOWTO, both available from
 301           <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
 302           protocol has been changed and this PLIP driver won't work together
 303           with the PLIP support in Linux versions 1.0.x.  This option enlarges
 304           your kernel by about 8 KB.
 305
 306           To compile this driver as a module, choose M here. The module
 307           will be called plip. If unsure, say Y or M, in case you buy
 308           a laptop later.
 309
 310 config SLIP
 311         tristate "SLIP (serial line) support"
 312         ---help---
 313           Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
 314           connect to your Internet service provider or to connect to some
 315           other local Unix box or if you want to configure your Linux box as a
 316           Slip/CSlip server for other people to dial in. SLIP (Serial Line
 317           Internet Protocol) is a protocol used to send Internet traffic over
 318           serial connections such as telephone lines or null modem cables;
 319           nowadays, the protocol PPP is more commonly used for this same
 320           purpose.
 321
 322           Normally, your access provider has to support SLIP in order for you
 323           to be able to use it, but there is now a SLIP emulator called SLiRP
 324           around (available from
 325           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
 326           allows you to use SLIP over a regular dial up shell connection. If
 327           you plan to use SLiRP, make sure to say Y to CSLIP, below. The
 328           NET-3-HOWTO, available from
 329           <http://www.tldp.org/docs.html#howto>, explains how to
 330           configure SLIP. Note that you don't need this option if you just
 331           want to run term (term is a program which gives you almost full
 332           Internet connectivity if you have a regular dial up shell account on
 333           some Internet connected Unix computer. Read
 334           <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
 335           support will enlarge your kernel by about 4 KB. If unsure, say N.
 336
 337           To compile this driver as a module, choose M here. The module
 338           will be called slip.
 339
 340 config SLIP_COMPRESSED
 341         bool "CSLIP compressed headers"
 342         depends on SLIP
 343         select SLHC
 344         ---help---
 345           This protocol is faster than SLIP because it uses compression on the
 346           TCP/IP headers (not on the data itself), but it has to be supported
 347           on both ends. Ask your access provider if you are not sure and
 348           answer Y, just in case. You will still be able to use plain SLIP. If
 349           you plan to use SLiRP, the SLIP emulator (available from
 350           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
 351           allows you to use SLIP over a regular dial up shell connection, you
 352           definitely want to say Y here. The NET-3-HOWTO, available from
 353           <http://www.tldp.org/docs.html#howto>, explains how to configure
 354           CSLIP. This won't enlarge your kernel.
 355
 356 config SLHC
 357         tristate
 358         help
 359           This option enables Van Jacobsen serial line header compression
 360           routines.
 361
 362 config SLIP_SMART
 363         bool "Keepalive and linefill"
 364         depends on SLIP
 365         help
 366           Adds additional capabilities to the SLIP driver to support the
 367           RELCOM line fill and keepalive monitoring. Ideal on poor quality
 368           analogue lines.
 369
 370 config SLIP_MODE_SLIP6
 371         bool "Six bit SLIP encapsulation"
 372         depends on SLIP
 373         help
 374           Just occasionally you may need to run IP over hostile serial
 375           networks that don't pass all control characters or are only seven
 376           bit. Saying Y here adds an extra mode you can use with SLIP:
 377           "slip6". In this mode, SLIP will only send normal ASCII symbols over
 378           the serial device. Naturally, this has to be supported at the other
 379           end of the link as well. It's good enough, for example, to run IP
 380           over the async ports of a Camtec JNT Pad. If unsure, say N.
 381
 382 config NET_FC
 383         bool "Fibre Channel driver support"
 384         depends on SCSI && PCI
 385         help
 386           Fibre Channel is a high speed serial protocol mainly used to connect
 387           large storage devices to the computer; it is compatible with and
 388           intended to replace SCSI.
 389
 390           If you intend to use Fibre Channel, you need to have a Fibre channel
 391           adaptor card in your computer; say Y here and to the driver for your
 392           adaptor below. You also should have said Y to "SCSI support" and
 393           "SCSI generic support".
 394
 395 config NETCONSOLE
 396         tristate "Network console logging support"
 397         ---help---
 398         If you want to log kernel messages over the network, enable this.
 399         See <file:Documentation/networking/netconsole.txt> for details.
 400
 401 config NETCONSOLE_DYNAMIC
 402         bool "Dynamic reconfiguration of logging targets"
 403         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
 404                         !(NETCONSOLE=y && CONFIGFS_FS=m)
 405         help
 406           This option enables the ability to dynamically reconfigure target
 407           parameters (interface, IP addresses, port numbers, MAC addresses)
 408           at runtime through a userspace interface exported using configfs.
 409           See <file:Documentation/networking/netconsole.txt> for details.
 410
 411 config NETPOLL
 412         def_bool NETCONSOLE
 413
 414 config NETPOLL_TRAP
 415         bool "Netpoll traffic trapping"
 416         default n
 417         depends on NETPOLL
 418
 419 config NET_POLL_CONTROLLER
 420         def_bool NETPOLL
 421
 422 config VIRTIO_NET
 423         tristate "Virtio network driver (EXPERIMENTAL)"
 424         depends on EXPERIMENTAL && VIRTIO
 425         ---help---
 426           This is the virtual network driver for virtio.  It can be used with
 427           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
 428
 429 config VMXNET3
 430         tristate "VMware VMXNET3 ethernet driver"
 431         depends on PCI && INET
 432         help
 433           This driver supports VMware's vmxnet3 virtual ethernet NIC.
 434           To compile this driver as a module, choose M here: the
 435           module will be called vmxnet3.
 436
 437 endif # NETDEVICES