drivers/net/Kconfig

   1 #
   2 # Network device configuration
   3 #
   4
   5 config HAVE_NET_MACB
   6         bool
   7
   8 menuconfig NETDEVICES
   9         default y if UML
  10         depends on NET
  11         bool "Network device support"
  12         ---help---
  13           You can say N here if you don't intend to connect your Linux box to
  14           any other computer at all.
  15
  16           You'll have to say Y if your computer contains a network card that
  17           you want to use under Linux. If you are going to run SLIP or PPP over
  18           telephone line or null modem cable you need say Y here. Connecting
  19           two machines with parallel ports using PLIP needs this, as well as
  20           AX.25/KISS for sending Internet traffic over amateur radio links.
  21
  22           See also "The Linux Network Administrator's Guide" by Olaf Kirch and
  23           Terry Dawson. Available at <http://www.tldp.org/guides.html>.
  24
  25           If unsure, say Y.
  26
  27 # All the following symbols are dependent on NETDEVICES - do not repeat
  28 # that for each of the symbols.
  29 if NETDEVICES
  30
  31 config IFB
  32         tristate "Intermediate Functional Block support"
  33         depends on NET_CLS_ACT
  34         ---help---
  35           This is an intermediate driver that allows sharing of
  36           resources.
  37           To compile this driver as a module, choose M here: the module
  38           will be called ifb.  If you want to use more than one ifb
  39           device at a time, you need to compile this driver as a module.
  40           Instead of 'ifb', the devices will then be called 'ifb0',
  41           'ifb1' etc.
  42           Look at the iproute2 documentation directory for usage etc
  43
  44 config DUMMY
  45         tristate "Dummy net driver support"
  46         ---help---
  47           This is essentially a bit-bucket device (i.e. traffic you send to
  48           this device is consigned into oblivion) with a configurable IP
  49           address. It is most commonly used in order to make your currently
  50           inactive SLIP address seem like a real address for local programs.
  51           If you use SLIP or PPP, you might want to say Y here. Since this
  52           thing often comes in handy, the default is Y. It won't enlarge your
  53           kernel either. What a deal. Read about it in the Network
  54           Administrator's Guide, available from
  55           <http://www.tldp.org/docs.html#guide>.
  56
  57           To compile this driver as a module, choose M here: the module
  58           will be called dummy.  If you want to use more than one dummy
  59           device at a time, you need to compile this driver as a module.
  60           Instead of 'dummy', the devices will then be called 'dummy0',
  61           'dummy1' etc.
  62
  63 config BONDING
  64         tristate "Bonding driver support"
  65         depends on INET
  66         depends on IPV6 || IPV6=n
  67         ---help---
  68           Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
  69           Channels together. This is called 'Etherchannel' by Cisco,
  70           'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
  71
  72           The driver supports multiple bonding modes to allow for both high
  73           performance and high availability operation.
  74
  75           Refer to <file:Documentation/networking/bonding.txt> for more
  76           information.
  77
  78           To compile this driver as a module, choose M here: the module
  79           will be called bonding.
  80
  81 config MACVLAN
  82         tristate "MAC-VLAN support (EXPERIMENTAL)"
  83         depends on EXPERIMENTAL
  84         ---help---
  85           This allows one to create virtual interfaces that map packets to
  86           or from specific MAC addresses to a particular interface.
  87
  88           Macvlan devices can be added using the "ip" command from the
  89           iproute2 package starting with the iproute2-2.6.23 release:
  90
  91           "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
  92
  93           To compile this driver as a module, choose M here: the module
  94           will be called macvlan.
  95
  96 config MACVTAP
  97         tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
  98         depends on MACVLAN
  99         help
 100           This adds a specialized tap character device driver that is based
 101           on the MAC-VLAN network interface, called macvtap. A macvtap device
 102           can be added in the same way as a macvlan device, using 'type
 103           macvlan', and then be accessed through the tap user space interface.
 104
 105           To compile this driver as a module, choose M here: the module
 106           will be called macvtap.
 107
 108 config EQUALIZER
 109         tristate "EQL (serial line load balancing) support"
 110         ---help---
 111           If you have two serial connections to some other computer (this
 112           usually requires two modems and two telephone lines) and you use
 113           SLIP (the protocol for sending Internet traffic over telephone
 114           lines) or PPP (a better SLIP) on them, you can make them behave like
 115           one double speed connection using this driver.  Naturally, this has
 116           to be supported at the other end as well, either with a similar EQL
 117           Linux driver or with a Livingston Portmaster 2e.
 118
 119           Say Y if you want this and read
 120           <file:Documentation/networking/eql.txt>.  You may also want to read
 121           section 6.2 of the NET-3-HOWTO, available from
 122           <http://www.tldp.org/docs.html#howto>.
 123
 124           To compile this driver as a module, choose M here: the module
 125           will be called eql.  If unsure, say N.
 126
 127 config TUN
 128         tristate "Universal TUN/TAP device driver support"
 129         select CRC32
 130         ---help---
 131           TUN/TAP provides packet reception and transmission for user space
 132           programs.  It can be viewed as a simple Point-to-Point or Ethernet
 133           device, which instead of receiving packets from a physical media,
 134           receives them from user space program and instead of sending packets
 135           via physical media writes them to the user space program.
 136
 137           When a program opens /dev/net/tun, driver creates and registers
 138           corresponding net device tunX or tapX.  After a program closed above
 139           devices, driver will automatically delete tunXX or tapXX device and
 140           all routes corresponding to it.
 141
 142           Please read <file:Documentation/networking/tuntap.txt> for more
 143           information.
 144
 145           To compile this driver as a module, choose M here: the module
 146           will be called tun.
 147
 148           If you don't know what to use this for, you don't need it.
 149
 150 config VETH
 151         tristate "Virtual ethernet pair device"
 152         ---help---
 153           This device is a local ethernet tunnel. Devices are created in pairs.
 154           When one end receives the packet it appears on its pair and vice
 155           versa.
 156
 157 config NET_SB1000
 158         tristate "General Instruments Surfboard 1000"
 159         depends on PNP
 160         ---help---
 161           This is a driver for the General Instrument (also known as
 162           NextLevel) SURFboard 1000 internal
 163           cable modem. This is an ISA card which is used by a number of cable
 164           TV companies to provide cable modem access. It's a one-way
 165           downstream-only cable modem, meaning that your upstream net link is
 166           provided by your regular phone modem.
 167
 168           At present this driver only compiles as a module, so say M here if
 169           you have this card. The module will be called sb1000. Then read
 170           <file:Documentation/networking/README.sb1000> for information on how
 171           to use this module, as it needs special ppp scripts for establishing
 172           a connection. Further documentation and the necessary scripts can be
 173           found at:
 174
 175           <http://www.jacksonville.net/~fventuri/>
 176           <http://home.adelphia.net/~siglercm/sb1000.html>
 177           <http://linuxpower.cx/~cable/>
 178
 179           If you don't have this card, of course say N.
 180
 181 source "drivers/net/arcnet/Kconfig"
 182
 183 config MII
 184         tristate "Generic Media Independent Interface device support"
 185         help
 186           Most ethernet controllers have MII transceiver either as an external
 187           or internal device.  It is safe to say Y or M here even if your
 188           ethernet card lacks MII.
 189
 190 source "drivers/net/phy/Kconfig"
 191
 192 #
 193 #       Ethernet
 194 #
 195
 196 source "drivers/net/ethernet/Kconfig"
 197
 198 menuconfig NET_ETHERNET
 199         bool "Ethernet (10 or 100Mbit)"
 200         depends on !UML
 201         ---help---
 202           Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
 203           type of Local Area Network (LAN) in universities and companies.
 204
 205           Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
 206           coaxial cable, linking computers in a chain), 10BASE-T or twisted
 207           pair (10 Mbps over twisted pair cable, linking computers to central
 208           hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
 209           100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
 210           100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
 211           cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
 212           [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
 213           Ethernet (1 Gbps over optical fiber or short copper links).
 214
 215           If your Linux machine will be connected to an Ethernet and you have
 216           an Ethernet network interface card (NIC) installed in your computer,
 217           say Y here and read the Ethernet-HOWTO, available from
 218           <http://www.tldp.org/docs.html#howto>. You will then also have
 219           to say Y to the driver for your particular NIC.
 220
 221           Note that the answer to this question won't directly affect the
 222           kernel: saying N will just cause the configurator to skip all
 223           the questions about Ethernet network cards. If unsure, say N.
 224
 225 if NET_ETHERNET
 226
 227 config MACB
 228         tristate "Atmel MACB support"
 229         depends on HAVE_NET_MACB
 230         select PHYLIB
 231         help
 232           The Atmel MACB ethernet interface is found on many AT32 and AT91
 233           parts. Say Y to include support for the MACB chip.
 234
 235           To compile this driver as a module, choose M here: the module
 236           will be called macb.
 237
 238 source "drivers/net/arm/Kconfig"
 239
 240 config KORINA
 241         tristate "Korina (IDT RC32434) Ethernet support"
 242         depends on NET_ETHERNET && MIKROTIK_RB532
 243         help
 244           If you have a Mikrotik RouterBoard 500 or IDT RC32434
 245           based system say Y. Otherwise say N.
 246
 247 config MIPS_SIM_NET
 248         tristate "MIPS simulator Network device"
 249         depends on MIPS_SIM
 250         help
 251           The MIPSNET device is a simple Ethernet network device which is
 252           emulated by the MIPS Simulator.
 253           If you are not using a MIPSsim or are unsure, say N.
 254
 255 config SH_ETH
 256         tristate "Renesas SuperH Ethernet support"
 257         depends on SUPERH && \
 258                 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
 259                  CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
 260                  CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
 261         select CRC32
 262         select MII
 263         select MDIO_BITBANG
 264         select PHYLIB
 265         help
 266           Renesas SuperH Ethernet device driver.
 267           This driver supporting CPUs are:
 268                 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
 269
 270 config BFIN_MAC
 271         tristate "Blackfin on-chip MAC support"
 272         depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
 273         select CRC32
 274         select MII
 275         select PHYLIB
 276         select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
 277         help
 278           This is the driver for Blackfin on-chip mac device. Say Y if you want it
 279           compiled into the kernel. This driver is also available as a module
 280           ( = code which can be inserted in and removed from the running kernel
 281           whenever you want). The module will be called bfin_mac.
 282
 283 config BFIN_MAC_USE_L1
 284         bool "Use L1 memory for rx/tx packets"
 285         depends on BFIN_MAC && (BF527 || BF537)
 286         default y
 287         help
 288           To get maximum network performance, you should use L1 memory as rx/tx buffers.
 289           Say N here if you want to reserve L1 memory for other uses.
 290
 291 config BFIN_TX_DESC_NUM
 292         int "Number of transmit buffer packets"
 293         depends on BFIN_MAC
 294         range 6 10 if BFIN_MAC_USE_L1
 295         range 10 100
 296         default "10"
 297         help
 298           Set the number of buffer packets used in driver.
 299
 300 config BFIN_RX_DESC_NUM
 301         int "Number of receive buffer packets"
 302         depends on BFIN_MAC
 303         range 20 100 if BFIN_MAC_USE_L1
 304         range 20 800
 305         default "20"
 306         help
 307           Set the number of buffer packets used in driver.
 308
 309 config BFIN_MAC_USE_HWSTAMP
 310         bool "Use IEEE 1588 hwstamp"
 311         depends on BFIN_MAC && BF518
 312         default y
 313         help
 314           To support the IEEE 1588 Precision Time Protocol (PTP), select y here
 315
 316 config NET_NETX
 317         tristate "NetX Ethernet support"
 318         select MII
 319         depends on ARCH_NETX
 320         help
 321           This is support for the Hilscher netX builtin Ethernet ports
 322
 323           To compile this driver as a module, choose M here. The module
 324           will be called netx-eth.
 325
 326 config TI_DAVINCI_EMAC
 327         tristate "TI DaVinci EMAC Support"
 328         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 329         select TI_DAVINCI_MDIO
 330         select TI_DAVINCI_CPDMA
 331         select PHYLIB
 332         help
 333           This driver supports TI's DaVinci Ethernet .
 334
 335           To compile this driver as a module, choose M here: the module
 336           will be called davinci_emac_driver.  This is recommended.
 337
 338 config TI_DAVINCI_MDIO
 339         tristate "TI DaVinci MDIO Support"
 340         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 341         select PHYLIB
 342         help
 343           This driver supports TI's DaVinci MDIO module.
 344
 345           To compile this driver as a module, choose M here: the module
 346           will be called davinci_mdio.  This is recommended.
 347
 348 config TI_DAVINCI_CPDMA
 349         tristate "TI DaVinci CPDMA Support"
 350         depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
 351         help
 352           This driver supports TI's DaVinci CPDMA dma engine.
 353
 354           To compile this driver as a module, choose M here: the module
 355           will be called davinci_cpdma.  This is recommended.
 356
 357 config DM9000
 358         tristate "DM9000 support"
 359         depends on ARM || BLACKFIN || MIPS
 360         select CRC32
 361         select MII
 362         ---help---
 363           Support for DM9000 chipset.
 364
 365           To compile this driver as a module, choose M here.  The module
 366           will be called dm9000.
 367
 368 config DM9000_DEBUGLEVEL
 369         int "DM9000 maximum debug level"
 370         depends on DM9000
 371         default 4
 372         help
 373           The maximum level of debugging code compiled into the DM9000
 374           driver.
 375
 376 config DM9000_FORCE_SIMPLE_PHY_POLL
 377         bool "Force simple NSR based PHY polling"
 378         depends on DM9000
 379         ---help---
 380           This configuration forces the DM9000 to use the NSR's LinkStatus
 381           bit to determine if the link is up or down instead of the more
 382           costly MII PHY reads. Note, this will not work if the chip is
 383           operating with an external PHY.
 384
 385 config ENC28J60
 386         tristate "ENC28J60 support"
 387         depends on EXPERIMENTAL && SPI && NET_ETHERNET
 388         select CRC32
 389         ---help---
 390           Support for the Microchip EN28J60 ethernet chip.
 391
 392           To compile this driver as a module, choose M here. The module will be
 393           called enc28j60.
 394
 395 config ENC28J60_WRITEVERIFY
 396         bool "Enable write verify"
 397         depends on ENC28J60
 398         ---help---
 399           Enable the verify after the buffer write useful for debugging purpose.
 400           If unsure, say N.
 401
 402 config ETHOC
 403         tristate "OpenCores 10/100 Mbps Ethernet MAC support"
 404         depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
 405         select MII
 406         select PHYLIB
 407         select CRC32
 408         select BITREVERSE
 409         help
 410           Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
 411
 412 config GRETH
 413         tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
 414         depends on SPARC
 415         select PHYLIB
 416         select CRC32
 417         help
 418           Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
 419
 420 config DNET
 421         tristate "Dave ethernet support (DNET)"
 422         depends on NET_ETHERNET && HAS_IOMEM
 423         select PHYLIB
 424         help
 425           The Dave ethernet interface (DNET) is found on Qong Board FPGA.
 426           Say Y to include support for the DNET chip.
 427
 428           To compile this driver as a module, choose M here: the module
 429           will be called dnet.
 430
 431 config HP100
 432         tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
 433         depends on ISA || EISA || PCI
 434         help
 435           If you have a network (Ethernet) card of this type, say Y and read
 436           the Ethernet-HOWTO, available from
 437           <http://www.tldp.org/docs.html#howto>.
 438
 439           To compile this driver as a module, choose M here. The module
 440           will be called hp100.
 441
 442 config NET_PCI
 443         bool "EISA, VLB, PCI and on board controllers"
 444         depends on ISA || EISA || PCI
 445         help
 446           This is another class of network cards which attach directly to the
 447           bus. If you have one of those, say Y and read the Ethernet-HOWTO,
 448           available from <http://www.tldp.org/docs.html#howto>.
 449
 450           Note that the answer to this question doesn't directly affect the
 451           kernel: saying N will just cause the configurator to skip all
 452           the questions about this class of network cards. If you say Y, you
 453           will be asked for your specific card in the following questions. If
 454           you are unsure, say Y.
 455
 456 config ADAPTEC_STARFIRE
 457         tristate "Adaptec Starfire/DuraLAN support"
 458         depends on NET_PCI && PCI
 459         select CRC32
 460         select MII
 461         help
 462           Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
 463           adapter. The DuraLAN chip is used on the 64 bit PCI boards from
 464           Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
 465           driver.
 466
 467           To compile this driver as a module, choose M here: the module
 468           will be called starfire.  This is recommended.
 469
 470 config FORCEDETH
 471         tristate "nForce Ethernet support"
 472         depends on NET_PCI && PCI
 473         help
 474           If you have a network (Ethernet) controller of this type, say Y and
 475           read the Ethernet-HOWTO, available from
 476           <http://www.tldp.org/docs.html#howto>.
 477
 478           To compile this driver as a module, choose M here. The module
 479           will be called forcedeth.
 480
 481 config FEALNX
 482         tristate "Myson MTD-8xx PCI Ethernet support"
 483         depends on NET_PCI && PCI
 484         select CRC32
 485         select MII
 486         help
 487           Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
 488           cards. <http://www.myson.com.tw/>
 489
 490 config R6040
 491         tristate "RDC R6040 Fast Ethernet Adapter support"
 492         depends on NET_PCI && PCI
 493         select CRC32
 494         select MII
 495         select PHYLIB
 496         help
 497           This is a driver for the R6040 Fast Ethernet MACs found in the
 498           the RDC R-321x System-on-chips.
 499
 500           To compile this driver as a module, choose M here: the module
 501           will be called r6040. This is recommended.
 502
 503 config SIS900
 504         tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
 505         depends on NET_PCI && PCI
 506         select CRC32
 507         select MII
 508         ---help---
 509           This is a driver for the Fast Ethernet PCI network cards based on
 510           the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
 511           SiS 630 and SiS 540 chipsets.
 512
 513           This driver also supports AMD 79C901 HomePNA so that you can use
 514           your phone line as a network cable.
 515
 516           To compile this driver as a module, choose M here: the module
 517           will be called sis900.  This is recommended.
 518
 519 config TLAN
 520         tristate "TI ThunderLAN support"
 521         depends on NET_PCI && (PCI || EISA)
 522         ---help---
 523           If you have a PCI Ethernet network card based on the ThunderLAN chip
 524           which is supported by this driver, say Y and read the
 525           Ethernet-HOWTO, available from
 526           <http://www.tldp.org/docs.html#howto>.
 527
 528           Devices currently supported by this driver are Compaq Netelligent,
 529           Compaq NetFlex and Olicom cards.  Please read the file
 530           <file:Documentation/networking/tlan.txt> for more details.
 531
 532           To compile this driver as a module, choose M here. The module
 533           will be called tlan.
 534
 535           Please email feedback to <torben.mathiasen@compaq.com>.
 536
 537 config CPMAC
 538         tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
 539         depends on NET_ETHERNET && EXPERIMENTAL && AR7
 540         select PHYLIB
 541         help
 542           TI AR7 CPMAC Ethernet support
 543
 544 config NET_POCKET
 545         bool "Pocket and portable adapters"
 546         depends on PARPORT
 547         ---help---
 548           Cute little network (Ethernet) devices which attach to the parallel
 549           port ("pocket adapters"), commonly used with laptops. If you have
 550           one of those, say Y and read the Ethernet-HOWTO, available from
 551           <http://www.tldp.org/docs.html#howto>.
 552
 553           If you want to plug a network (or some other) card into the PCMCIA
 554           (or PC-card) slot of your laptop instead (PCMCIA is the standard for
 555           credit card size extension cards used by all modern laptops), you
 556           need the pcmcia-cs package (location contained in the file
 557           <file:Documentation/Changes>) and you can say N here.
 558
 559           Laptop users should read the Linux Laptop home page at
 560           <http://www.linux-on-laptops.com/> or
 561           Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
 562
 563           Note that the answer to this question doesn't directly affect the
 564           kernel: saying N will just cause the configurator to skip all
 565           the questions about this class of network devices. If you say Y, you
 566           will be asked for your specific device in the following questions.
 567
 568 config XILINX_EMACLITE
 569         tristate "Xilinx 10/100 Ethernet Lite support"
 570         depends on PPC32 || MICROBLAZE
 571         select PHYLIB
 572         help
 573           This driver supports the 10/100 Ethernet Lite from Xilinx.
 574
 575 config LANTIQ_ETOP
 576         tristate "Lantiq SoC ETOP driver"
 577         depends on SOC_TYPE_XWAY
 578         help
 579           Support for the MII0 inside the Lantiq SoC
 580
 581 source "drivers/net/octeon/Kconfig"
 582
 583 endif # NET_ETHERNET
 584
 585 #
 586 #       Gigabit Ethernet
 587 #
 588
 589 menuconfig NETDEV_1000
 590         bool "Ethernet (1000 Mbit)"
 591         depends on !UML
 592         default y
 593         ---help---
 594           Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
 595           type of Local Area Network (LAN) in universities and companies.
 596
 597           Say Y here to get to see options for Gigabit Ethernet drivers.
 598           This option alone does not add any kernel code.
 599           Note that drivers supporting both 100 and 1000 MBit may be listed
 600           under "Ethernet (10 or 100MBit)" instead.
 601
 602           If you say N, all options in this submenu will be skipped and disabled.
 603
 604 if NETDEV_1000
 605
 606 config IP1000
 607         tristate "IP1000 Gigabit Ethernet support"
 608         depends on PCI && EXPERIMENTAL
 609         select MII
 610         ---help---
 611           This driver supports IP1000 gigabit Ethernet cards.
 612
 613           To compile this driver as a module, choose M here: the module
 614           will be called ipg.  This is recommended.
 615
 616 config HAMACHI
 617         tristate "Packet Engines Hamachi GNIC-II support"
 618         depends on PCI
 619         select MII
 620         help
 621           If you have a Gigabit Ethernet card of this type, say Y and read
 622           the Ethernet-HOWTO, available from
 623           <http://www.tldp.org/docs.html#howto>.
 624
 625           To compile this driver as a module, choose M here. The module will be
 626           called hamachi.
 627
 628 config YELLOWFIN
 629         tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
 630         depends on PCI && EXPERIMENTAL
 631         select CRC32
 632         ---help---
 633           Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
 634           adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
 635           used by the Beowulf Linux cluster project.  See
 636           <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
 637           information about this driver in particular and Beowulf in general.
 638
 639           To compile this driver as a module, choose M here: the module
 640           will be called yellowfin.  This is recommended.
 641
 642 config SIS190
 643         tristate "SiS190/SiS191 gigabit ethernet support"
 644         depends on PCI
 645         select CRC32
 646         select MII
 647         ---help---
 648           Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
 649           a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
 650           appear in lan on motherboard designs which are based on SiS 965
 651           and SiS 966 south bridge.
 652
 653           To compile this driver as a module, choose M here: the module
 654           will be called sis190.  This is recommended.
 655
 656 config TSI108_ETH
 657         tristate "Tundra TSI108 gigabit Ethernet support"
 658         depends on TSI108_BRIDGE
 659         help
 660           This driver supports Tundra TSI108 gigabit Ethernet ports.
 661           To compile this driver as a module, choose M here: the module
 662           will be called tsi108_eth.
 663
 664 config XILINX_LL_TEMAC
 665         tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
 666         depends on PPC || MICROBLAZE
 667         select PHYLIB
 668         help
 669           This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
 670           core used in Xilinx Spartan and Virtex FPGAs
 671
 672 config JME
 673         tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
 674         depends on PCI
 675         select CRC32
 676         select MII
 677         ---help---
 678           This driver supports the PCI-Express gigabit ethernet adapters
 679           based on JMicron JMC250 chipset.
 680
 681           To compile this driver as a module, choose M here. The module
 682           will be called jme.
 683
 684 config S6GMAC
 685         tristate "S6105 GMAC ethernet support"
 686         depends on XTENSA_VARIANT_S6000
 687         select PHYLIB
 688         help
 689           This driver supports the on chip ethernet device on the
 690           S6105 xtensa processor.
 691
 692           To compile this driver as a module, choose M here. The module
 693           will be called s6gmac.
 694
 695 endif # NETDEV_1000
 696
 697 #
 698 #       10 Gigabit Ethernet
 699 #
 700
 701 menuconfig NETDEV_10000
 702         bool "Ethernet (10000 Mbit)"
 703         depends on !UML
 704         default y
 705         ---help---
 706           Say Y here to get to see options for 10 Gigabit Ethernet drivers.
 707           This option alone does not add any kernel code.
 708
 709           If you say N, all options in this submenu will be skipped and disabled.
 710
 711 if NETDEV_10000
 712
 713 config MDIO
 714         tristate
 715
 716 config SUNGEM_PHY
 717         tristate
 718
 719 endif # NETDEV_10000
 720
 721 source "drivers/net/tokenring/Kconfig"
 722
 723 source "drivers/net/wireless/Kconfig"
 724
 725 source "drivers/net/wimax/Kconfig"
 726
 727 source "drivers/net/usb/Kconfig"
 728
 729 source "drivers/net/pcmcia/Kconfig"
 730
 731 source "drivers/net/wan/Kconfig"
 732
 733 source "drivers/atm/Kconfig"
 734
 735 source "drivers/ieee802154/Kconfig"
 736
 737 source "drivers/s390/net/Kconfig"
 738
 739 source "drivers/net/caif/Kconfig"
 740
 741 config TILE_NET
 742         tristate "Tilera GBE/XGBE network driver support"
 743         depends on TILE
 744         default y
 745         select CRC32
 746         help
 747           This is a standard Linux network device driver for the
 748           on-chip Tilera Gigabit Ethernet and XAUI interfaces.
 749
 750           To compile this driver as a module, choose M here: the module
 751           will be called tile_net.
 752
 753 config XEN_NETDEV_FRONTEND
 754         tristate "Xen network device frontend driver"
 755         depends on XEN
 756         select XEN_XENBUS_FRONTEND
 757         default y
 758         help
 759           This driver provides support for Xen paravirtual network
 760           devices exported by a Xen network driver domain (often
 761           domain 0).
 762
 763           The corresponding Linux backend driver is enabled by the
 764           CONFIG_XEN_NETDEV_BACKEND option.
 765
 766           If you are compiling a kernel for use as Xen guest, you
 767           should say Y here. To compile this driver as a module, chose
 768           M here: the module will be called xen-netfront.
 769
 770 config XEN_NETDEV_BACKEND
 771         tristate "Xen backend network device"
 772         depends on XEN_BACKEND
 773         help
 774           This driver allows the kernel to act as a Xen network driver
 775           domain which exports paravirtual network devices to other
 776           Xen domains. These devices can be accessed by any operating
 777           system that implements a compatible front end.
 778
 779           The corresponding Linux frontend driver is enabled by the
 780           CONFIG_XEN_NETDEV_FRONTEND configuration option.
 781
 782           The backend driver presents a standard network device
 783           endpoint for each paravirtual network device to the driver
 784           domain network stack. These can then be bridged or routed
 785           etc in order to provide full network connectivity.
 786
 787           If you are compiling a kernel to run in a Xen network driver
 788           domain (often this is domain 0) you should say Y here. To
 789           compile this driver as a module, chose M here: the module
 790           will be called xen-netback.
 791
 792 config RIONET
 793         tristate "RapidIO Ethernet over messaging driver support"
 794         depends on RAPIDIO
 795
 796 config RIONET_TX_SIZE
 797         int "Number of outbound queue entries"
 798         depends on RIONET
 799         default "128"
 800
 801 config RIONET_RX_SIZE
 802         int "Number of inbound queue entries"
 803         depends on RIONET
 804         default "128"
 805
 806 config FDDI
 807         tristate "FDDI driver support"
 808         depends on (PCI || EISA || TC)
 809         help
 810           Fiber Distributed Data Interface is a high speed local area network
 811           design; essentially a replacement for high speed Ethernet. FDDI can
 812           run over copper or fiber. If you are connected to such a network and
 813           want a driver for the FDDI card in your computer, say Y here (and
 814           then also Y to the driver for your FDDI card, below). Most people
 815           will say N.
 816
 817 config DEFXX
 818         tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
 819         depends on FDDI && (PCI || EISA || TC)
 820         ---help---
 821           This is support for the DIGITAL series of TURBOchannel (DEFTA),
 822           EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
 823           to a local FDDI network.
 824
 825           To compile this driver as a module, choose M here: the module
 826           will be called defxx.  If unsure, say N.
 827
 828 config DEFXX_MMIO
 829         bool
 830         prompt "Use MMIO instead of PIO" if PCI || EISA
 831         depends on DEFXX
 832         default n if PCI || EISA
 833         default y
 834         ---help---
 835           This instructs the driver to use EISA or PCI memory-mapped I/O
 836           (MMIO) as appropriate instead of programmed I/O ports (PIO).
 837           Enabling this gives an improvement in processing time in parts
 838           of the driver, but it may cause problems with EISA (DEFEA)
 839           adapters.  TURBOchannel does not have the concept of I/O ports,
 840           so MMIO is always used for these (DEFTA) adapters.
 841
 842           If unsure, say N.
 843
 844 config SKFP
 845         tristate "SysKonnect FDDI PCI support"
 846         depends on FDDI && PCI
 847         select BITREVERSE
 848         ---help---
 849           Say Y here if you have a SysKonnect FDDI PCI adapter.
 850           The following adapters are supported by this driver:
 851           - SK-5521 (SK-NET FDDI-UP)
 852           - SK-5522 (SK-NET FDDI-UP DAS)
 853           - SK-5541 (SK-NET FDDI-FP)
 854           - SK-5543 (SK-NET FDDI-LP)
 855           - SK-5544 (SK-NET FDDI-LP DAS)
 856           - SK-5821 (SK-NET FDDI-UP64)
 857           - SK-5822 (SK-NET FDDI-UP64 DAS)
 858           - SK-5841 (SK-NET FDDI-FP64)
 859           - SK-5843 (SK-NET FDDI-LP64)
 860           - SK-5844 (SK-NET FDDI-LP64 DAS)
 861           - Netelligent 100 FDDI DAS Fibre SC
 862           - Netelligent 100 FDDI SAS Fibre SC
 863           - Netelligent 100 FDDI DAS UTP
 864           - Netelligent 100 FDDI SAS UTP
 865           - Netelligent 100 FDDI SAS Fibre MIC
 866
 867           Read <file:Documentation/networking/skfp.txt> for information about
 868           the driver.
 869
 870           Questions concerning this driver can be addressed to:
 871           <linux@syskonnect.de>
 872
 873           To compile this driver as a module, choose M here: the module
 874           will be called skfp.  This is recommended.
 875
 876 config HIPPI
 877         bool "HIPPI driver support (EXPERIMENTAL)"
 878         depends on EXPERIMENTAL && INET && PCI
 879         help
 880           HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
 881           1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
 882           can run over copper (25m) or fiber (300m on multi-mode or 10km on
 883           single-mode). HIPPI networks are commonly used for clusters and to
 884           connect to super computers. If you are connected to a HIPPI network
 885           and have a HIPPI network card in your computer that you want to use
 886           under Linux, say Y here (you must also remember to enable the driver
 887           for your HIPPI card below). Most people will say N here.
 888
 889 config ROADRUNNER
 890         tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
 891         depends on HIPPI && PCI
 892         help
 893           Say Y here if this is your PCI HIPPI network card.
 894
 895           To compile this driver as a module, choose M here: the module
 896           will be called rrunner.  If unsure, say N.
 897
 898 config ROADRUNNER_LARGE_RINGS
 899         bool "Use large TX/RX rings (EXPERIMENTAL)"
 900         depends on ROADRUNNER
 901         help
 902           If you say Y here, the RoadRunner driver will preallocate up to 2 MB
 903           of additional memory to allow for fastest operation, both for
 904           transmitting and receiving. This memory cannot be used by any other
 905           kernel code or by user space programs. Say Y here only if you have
 906           the memory.
 907
 908 config PLIP
 909         tristate "PLIP (parallel port) support"
 910         depends on PARPORT
 911         ---help---
 912           PLIP (Parallel Line Internet Protocol) is used to create a
 913           reasonably fast mini network consisting of two (or, rarely, more)
 914           local machines.  A PLIP link from a Linux box is a popular means to
 915           install a Linux distribution on a machine which doesn't have a
 916           CD-ROM drive (a minimal system has to be transferred with floppies
 917           first). The kernels on both machines need to have this PLIP option
 918           enabled for this to work.
 919
 920           The PLIP driver has two modes, mode 0 and mode 1.  The parallel
 921           ports (the connectors at the computers with 25 holes) are connected
 922           with "null printer" or "Turbo Laplink" cables which can transmit 4
 923           bits at a time (mode 0) or with special PLIP cables, to be used on
 924           bidirectional parallel ports only, which can transmit 8 bits at a
 925           time (mode 1); you can find the wiring of these cables in
 926           <file:Documentation/networking/PLIP.txt>.  The cables can be up to
 927           15m long.  Mode 0 works also if one of the machines runs DOS/Windows
 928           and has some PLIP software installed, e.g. the Crynwr PLIP packet
 929           driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
 930           and winsock or NCSA's telnet.
 931
 932           If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
 933           as the NET-3-HOWTO, both available from
 934           <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
 935           protocol has been changed and this PLIP driver won't work together
 936           with the PLIP support in Linux versions 1.0.x.  This option enlarges
 937           your kernel by about 8 KB.
 938
 939           To compile this driver as a module, choose M here. The module
 940           will be called plip. If unsure, say Y or M, in case you buy
 941           a laptop later.
 942
 943 config PPP
 944         tristate "PPP (point-to-point protocol) support"
 945         select SLHC
 946         ---help---
 947           PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
 948           the same purpose: sending Internet traffic over telephone (and other
 949           serial) lines.  Ask your access provider if they support it, because
 950           otherwise you can't use it; most Internet access providers these
 951           days support PPP rather than SLIP.
 952
 953           To use PPP, you need an additional program called pppd as described
 954           in the PPP-HOWTO, available at
 955           <http://www.tldp.org/docs.html#howto>.  Make sure that you have
 956           the version of pppd recommended in <file:Documentation/Changes>.
 957           The PPP option enlarges your kernel by about 16 KB.
 958
 959           There are actually two versions of PPP: the traditional PPP for
 960           asynchronous lines, such as regular analog phone lines, and
 961           synchronous PPP which can be used over digital ISDN lines for
 962           example.  If you want to use PPP over phone lines or other
 963           asynchronous serial lines, you need to say Y (or M) here and also to
 964           the next option, "PPP support for async serial ports".  For PPP over
 965           synchronous lines, you should say Y (or M) here and to "Support
 966           synchronous PPP", below.
 967
 968           If you said Y to "Version information on all symbols" above, then
 969           you cannot compile the PPP driver into the kernel; you can then only
 970           compile it as a module. To compile this driver as a module, choose M
 971           here. The module will be called ppp_generic.
 972
 973 config PPP_MULTILINK
 974         bool "PPP multilink support (EXPERIMENTAL)"
 975         depends on PPP && EXPERIMENTAL
 976         help
 977           PPP multilink is a protocol (defined in RFC 1990) which allows you
 978           to combine several (logical or physical) lines into one logical PPP
 979           connection, so that you can utilize your full bandwidth.
 980
 981           This has to be supported at the other end as well and you need a
 982           version of the pppd daemon which understands the multilink protocol.
 983
 984           If unsure, say N.
 985
 986 config PPP_FILTER
 987         bool "PPP filtering"
 988         depends on PPP
 989         help
 990           Say Y here if you want to be able to filter the packets passing over
 991           PPP interfaces.  This allows you to control which packets count as
 992           activity (i.e. which packets will reset the idle timer or bring up
 993           a demand-dialed link) and which packets are to be dropped entirely.
 994           You need to say Y here if you wish to use the pass-filter and
 995           active-filter options to pppd.
 996
 997           If unsure, say N.
 998
 999 config PPP_ASYNC
1000         tristate "PPP support for async serial ports"
1001         depends on PPP
1002         select CRC_CCITT
1003         ---help---
1004           Say Y (or M) here if you want to be able to use PPP over standard
1005           asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
1006           a modem (not a synchronous or ISDN modem) to contact your ISP, you
1007           need this option.
1008
1009           To compile this driver as a module, choose M here.
1010
1011           If unsure, say Y.
1012
1013 config PPP_SYNC_TTY
1014         tristate "PPP support for sync tty ports"
1015         depends on PPP
1016         help
1017           Say Y (or M) here if you want to be able to use PPP over synchronous
1018           (HDLC) tty devices, such as the SyncLink adapter. These devices
1019           are often used for high-speed leased lines like T1/E1.
1020
1021           To compile this driver as a module, choose M here.
1022
1023 config PPP_DEFLATE
1024         tristate "PPP Deflate compression"
1025         depends on PPP
1026         select ZLIB_INFLATE
1027         select ZLIB_DEFLATE
1028         ---help---
1029           Support for the Deflate compression method for PPP, which uses the
1030           Deflate algorithm (the same algorithm that gzip uses) to compress
1031           each PPP packet before it is sent over the wire.  The machine at the
1032           other end of the PPP link (usually your ISP) has to support the
1033           Deflate compression method as well for this to be useful.  Even if
1034           they don't support it, it is safe to say Y here.
1035
1036           To compile this driver as a module, choose M here.
1037
1038 config PPP_BSDCOMP
1039         tristate "PPP BSD-Compress compression"
1040         depends on PPP
1041         ---help---
1042           Support for the BSD-Compress compression method for PPP, which uses
1043           the LZW compression method to compress each PPP packet before it is
1044           sent over the wire. The machine at the other end of the PPP link
1045           (usually your ISP) has to support the BSD-Compress compression
1046           method as well for this to be useful. Even if they don't support it,
1047           it is safe to say Y here.
1048
1049           The PPP Deflate compression method ("PPP Deflate compression",
1050           above) is preferable to BSD-Compress, because it compresses better
1051           and is patent-free.
1052
1053           Note that the BSD compression code will always be compiled as a
1054           module; it is called bsd_comp and will show up in the directory
1055           modules once you have said "make modules". If unsure, say N.
1056
1057 config PPP_MPPE
1058         tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
1059         depends on PPP && EXPERIMENTAL
1060         select CRYPTO
1061         select CRYPTO_SHA1
1062         select CRYPTO_ARC4
1063         select CRYPTO_ECB
1064         ---help---
1065           Support for the MPPE Encryption protocol, as employed by the
1066           Microsoft Point-to-Point Tunneling Protocol.
1067
1068           See http://pptpclient.sourceforge.net/ for information on
1069           configuring PPTP clients and servers to utilize this method.
1070
1071 config PPPOE
1072         tristate "PPP over Ethernet (EXPERIMENTAL)"
1073         depends on EXPERIMENTAL && PPP
1074         help
1075           Support for PPP over Ethernet.
1076
1077           This driver requires the latest version of pppd from the CVS
1078           repository at cvs.samba.org.  Alternatively, see the
1079           RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
1080           which contains instruction on how to use this driver (under
1081           the heading "Kernel mode PPPoE").
1082
1083 config PPTP
1084         tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
1085         depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
1086         help
1087           Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
1088
1089           This driver requires pppd plugin to work in client mode or
1090           modified pptpd (poptop) to work in server mode.
1091           See http://accel-pptp.sourceforge.net/ for information how to
1092           utilize this module.
1093
1094 config PPPOATM
1095         tristate "PPP over ATM"
1096         depends on ATM && PPP
1097         help
1098           Support PPP (Point to Point Protocol) encapsulated in ATM frames.
1099           This implementation does not yet comply with section 8 of RFC2364,
1100           which can lead to bad results if the ATM peer loses state and
1101           changes its encapsulation unilaterally.
1102
1103 config PPPOL2TP
1104         tristate "PPP over L2TP (EXPERIMENTAL)"
1105         depends on EXPERIMENTAL && L2TP && PPP
1106         help
1107           Support for PPP-over-L2TP socket family. L2TP is a protocol
1108           used by ISPs and enterprises to tunnel PPP traffic over UDP
1109           tunnels. L2TP is replacing PPTP for VPN uses.
1110
1111 config SLIP
1112         tristate "SLIP (serial line) support"
1113         ---help---
1114           Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
1115           connect to your Internet service provider or to connect to some
1116           other local Unix box or if you want to configure your Linux box as a
1117           Slip/CSlip server for other people to dial in. SLIP (Serial Line
1118           Internet Protocol) is a protocol used to send Internet traffic over
1119           serial connections such as telephone lines or null modem cables;
1120           nowadays, the protocol PPP is more commonly used for this same
1121           purpose.
1122
1123           Normally, your access provider has to support SLIP in order for you
1124           to be able to use it, but there is now a SLIP emulator called SLiRP
1125           around (available from
1126           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1127           allows you to use SLIP over a regular dial up shell connection. If
1128           you plan to use SLiRP, make sure to say Y to CSLIP, below. The
1129           NET-3-HOWTO, available from
1130           <http://www.tldp.org/docs.html#howto>, explains how to
1131           configure SLIP. Note that you don't need this option if you just
1132           want to run term (term is a program which gives you almost full
1133           Internet connectivity if you have a regular dial up shell account on
1134           some Internet connected Unix computer. Read
1135           <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
1136           support will enlarge your kernel by about 4 KB. If unsure, say N.
1137
1138           To compile this driver as a module, choose M here. The module
1139           will be called slip.
1140
1141 config SLIP_COMPRESSED
1142         bool "CSLIP compressed headers"
1143         depends on SLIP
1144         select SLHC
1145         ---help---
1146           This protocol is faster than SLIP because it uses compression on the
1147           TCP/IP headers (not on the data itself), but it has to be supported
1148           on both ends. Ask your access provider if you are not sure and
1149           answer Y, just in case. You will still be able to use plain SLIP. If
1150           you plan to use SLiRP, the SLIP emulator (available from
1151           <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
1152           allows you to use SLIP over a regular dial up shell connection, you
1153           definitely want to say Y here. The NET-3-HOWTO, available from
1154           <http://www.tldp.org/docs.html#howto>, explains how to configure
1155           CSLIP. This won't enlarge your kernel.
1156
1157 config SLHC
1158         tristate
1159         help
1160           This option enables Van Jacobsen serial line header compression
1161           routines.
1162
1163 config SLIP_SMART
1164         bool "Keepalive and linefill"
1165         depends on SLIP
1166         help
1167           Adds additional capabilities to the SLIP driver to support the
1168           RELCOM line fill and keepalive monitoring. Ideal on poor quality
1169           analogue lines.
1170
1171 config SLIP_MODE_SLIP6
1172         bool "Six bit SLIP encapsulation"
1173         depends on SLIP
1174         help
1175           Just occasionally you may need to run IP over hostile serial
1176           networks that don't pass all control characters or are only seven
1177           bit. Saying Y here adds an extra mode you can use with SLIP:
1178           "slip6". In this mode, SLIP will only send normal ASCII symbols over
1179           the serial device. Naturally, this has to be supported at the other
1180           end of the link as well. It's good enough, for example, to run IP
1181           over the async ports of a Camtec JNT Pad. If unsure, say N.
1182
1183 config NET_FC
1184         bool "Fibre Channel driver support"
1185         depends on SCSI && PCI
1186         help
1187           Fibre Channel is a high speed serial protocol mainly used to connect
1188           large storage devices to the computer; it is compatible with and
1189           intended to replace SCSI.
1190
1191           If you intend to use Fibre Channel, you need to have a Fibre channel
1192           adaptor card in your computer; say Y here and to the driver for your
1193           adaptor below. You also should have said Y to "SCSI support" and
1194           "SCSI generic support".
1195
1196 config NETCONSOLE
1197         tristate "Network console logging support"
1198         ---help---
1199         If you want to log kernel messages over the network, enable this.
1200         See <file:Documentation/networking/netconsole.txt> for details.
1201
1202 config NETCONSOLE_DYNAMIC
1203         bool "Dynamic reconfiguration of logging targets"
1204         depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
1205                         !(NETCONSOLE=y && CONFIGFS_FS=m)
1206         help
1207           This option enables the ability to dynamically reconfigure target
1208           parameters (interface, IP addresses, port numbers, MAC addresses)
1209           at runtime through a userspace interface exported using configfs.
1210           See <file:Documentation/networking/netconsole.txt> for details.
1211
1212 config NETPOLL
1213         def_bool NETCONSOLE
1214
1215 config NETPOLL_TRAP
1216         bool "Netpoll traffic trapping"
1217         default n
1218         depends on NETPOLL
1219
1220 config NET_POLL_CONTROLLER
1221         def_bool NETPOLL
1222
1223 config VIRTIO_NET
1224         tristate "Virtio network driver (EXPERIMENTAL)"
1225         depends on EXPERIMENTAL && VIRTIO
1226         ---help---
1227           This is the virtual network driver for virtio.  It can be used with
1228           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
1229
1230 config VMXNET3
1231         tristate "VMware VMXNET3 ethernet driver"
1232         depends on PCI && INET
1233         help
1234           This driver supports VMware's vmxnet3 virtual ethernet NIC.
1235           To compile this driver as a module, choose M here: the
1236           module will be called vmxnet3.
1237
1238 endif # NETDEVICES