# # Network device configuration # config NETDEVICES depends on NET bool "Network device support" ---help--- You can say N here if you don't intend to connect your Linux box to any other computer at all or if all your connections will be over a telephone line with a modem either via UUCP (UUCP is a protocol to forward mail and news between unix hosts over telephone lines; read the UUCP-HOWTO, available from <http://www.tldp.org/docs.html#howto>) or dialing up a shell account or a BBS, even using term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). You'll have to say Y if your computer contains a network card that you want to use under Linux (make sure you know its name because you will be asked for it and read the Ethernet-HOWTO (especially if you plan to use more than one network card under Linux)) or if you want to use SLIP (Serial Line Internet Protocol is the protocol used to send Internet traffic over telephone lines or null modem cables) or CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better and newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol is mainly used to create a mini network by connecting the parallel ports of two local machines) or AX.25/KISS (protocol for sending Internet traffic over amateur radio links). Make sure to read the NET-3-HOWTO. Eventually, you will have to read Olaf Kirch's excellent and free book "Network Administrator's Guide", to be found in <http://www.tldp.org/docs.html#guide>. If unsure, say Y. if NETDEVICES source "drivers/net/arcnet/Kconfig" endif config DUMMY tristate "Dummy net driver support" depends on NETDEVICES ---help--- This is essentially a bit-bucket device (i.e. traffic you send to this device is consigned into oblivion) with a configurable IP address. It is most commonly used in order to make your currently inactive SLIP address seem like a real address for local programs. If you use SLIP or PPP, you might want to say Y here. Since this thing often comes in handy, the default is Y. It won't enlarge your kernel either. What a deal. Read about it in the Network Administrator's Guide, available from <http://www.tldp.org/docs.html#guide>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. The module will be called dummy. If you want to use more than one dummy device at a time, you need to compile this driver as a module. Instead of 'dummy', the devices will then be called 'dummy0', 'dummy1' etc. config BONDING tristate "Bonding driver support" depends on NETDEVICES ---help--- Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet Channels together. This is called 'Etherchannel' by Cisco, 'Trunking' by Sun, and 'Bonding' in Linux. If you have two Ethernet connections to some other computer, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar Bonding Linux driver, a Cisco 5500 switch or a SunTrunking SunSoft driver. This is similar to the EQL driver, but it merges Ethernet segments instead of serial lines. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. The module will be called bonding. config EQUALIZER tristate "EQL (serial line load balancing) support" depends on NETDEVICES ---help--- If you have two serial connections to some other computer (this usually requires two modems and two telephone lines) and you use SLIP (the protocol for sending Internet traffic over telephone lines) or PPP (a better SLIP) on them, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you want this and read <file:Documentation/networking/eql.txt>. You may also want to read section 6.2 of the NET-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eql. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If unsure, say N. config TUN tristate "Universal TUN/TAP device driver support" depends on NETDEVICES ---help--- TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a program opens /dev/net/tun, driver creates and registers corresponding net device tunX or tapX. After a program closed above devices, driver will automatically delete tunXX or tapXX device and all routes corresponding to it. Please read <file:Documentation/networking/tuntap.txt> for more information. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tun. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If you don't know what to use this for, you don't need it. config ETHERTAP tristate "Ethertap network tap (OBSOLETE)" depends on NETDEVICES && EXPERIMENTAL ---help--- If you say Y here (and have said Y to "Kernel/User network link driver", above) and create a character special file /dev/tap0 with major number 36 and minor number 16 using mknod ("man mknod"), you will be able to have a user space program read and write raw Ethernet frames from/to that special file. tap0 can be configured with ifconfig and route like any other Ethernet device but it is not connected to any physical LAN; everything written by the user to /dev/tap0 is treated by the kernel as if it had come in from a LAN to the device tap0; everything the kernel wants to send out over the device tap0 can instead be read by the user from /dev/tap0: the user mode program replaces the LAN that would be attached to an ordinary Ethernet device. Please read the file <file:Documentation/networking/ethertap.txt> for more information. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ethertap. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If you don't know what to use this for, you don't need it. config NET_SB1000 tristate "General Instruments Surfboard 1000" depends on NETDEVICES && PNP ---help--- This is a driver for the General Instrument (also known as NextLevel) SURFboard 1000 internal cable modem. This is an ISA card which is used by a number of cable TV companies to provide cable modem access. It's a one-way downstream-only cable modem, meaning that your upstream net link is provided by your regular phone modem. At present this driver only compiles as a module, so say M here if you have this card. The module will be called sb1000. Then read <file:Documentation/networking/README.sb1000> for information on how to use this module, as it needs special ppp scripts for establishing a connection. Further documentation and the necessary scripts can be found at: <http://www.jacksonville.net/~fventuri/> <http://home.adelphia.net/~siglercm/sb1000.html> <http://linuxpower.cx/~cable/> If you don't have this card, of course say N. # # Ethernet # menu "Ethernet (10 or 100Mbit)" depends on NETDEVICES config NET_ETHERNET bool "Ethernet (10 or 100Mbit)" ---help--- Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common type of Local Area Network (LAN) in universities and companies. Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over coaxial cable, linking computers in a chain), 10BASE-T or twisted pair (10 Mbps over twisted pair cable, linking computers to central hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) [the 100BASE varieties are also known as Fast Ethernet], and Gigabit Ethernet (1 Gbps over optical fiber or short copper links). If your Linux machine will be connected to an Ethernet and you have an Ethernet network interface card (NIC) installed in your computer, say Y here and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. You will then also have to say Y to the driver for your particular NIC. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Ethernet network cards. If unsure, say N. config MII tristate "Generic Media Independent Interface device support" depends on NET_ETHERNET help Most ethernet controllers have MII transceiver either as an external or internal device. It is safe to say Y or M here even if your ethernet card lack MII. source "drivers/net/arm/Kconfig" config MACE tristate "MACE (Power Mac ethernet) support" depends on NET_ETHERNET && PPC_PMAC help Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. This driver is also available as a module called mace ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config MACE_AAUI_PORT bool "Use AAUI port instead of TP by default" depends on MACE help Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. config BMAC tristate "BMAC (G3 ethernet) support" depends on NET_ETHERNET && PPC_PMAC help Say Y for support of BMAC Ethernet interfaces. These are used on G3 computers. This driver is also available as a module called bmac ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config OAKNET tristate "National DP83902AV (Oak ethernet) support" depends on NET_ETHERNET && PPC help Say Y if your machine has this type of Ethernet network card. This driver is also available as a module called oaknet ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config ARIADNE tristate "Ariadne support" depends on NET_ETHERNET && ZORRO help If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called ariadne. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config ARIADNE2 tristate "Ariadne II support" depends on NETDEVICES && ZORRO help This driver is for the Village Tronic Ariadne II and the Individual Computers X-Surf Ethernet cards. If you have such a card, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ariadne2. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config NE2K_ZORRO tristate "Ariadne II and X-Surf support" depends on NET_ETHERNET && ZORRO config A2065 tristate "A2065 support" depends on NET_ETHERNET && ZORRO help If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called a2065. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config HYDRA tristate "Hydra support" depends on NET_ETHERNET && ZORRO help If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called hydra. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config APNE tristate "PCMCIA NE2000 support" depends on NETDEVICES && AMIGA_PCMCIA help If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called apne. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config APOLLO_ELPLUS tristate "Apollo 3c505 support" depends on NETDEVICES && APOLLO help Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card. If you don't have one made for Apollos, you can use one from a PC, except that your Apollo won't be able to boot from it (because the code in the ROM will be for a PC). config MAC8390 bool "Macintosh NS 8390 based ethernet cards" depends on NETDEVICES && MAC help If you want to include a driver to support Nubus or LC-PDS Ethernet cards using an NS8390 chipset or its equivalent, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MAC89x0 tristate "Macintosh CS89x0 based ethernet cards" depends on NETDEVICES && MAC ---help--- Support for CS89x0 chipset based Ethernet cards. If you have a Nubus or LC-PDS network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. This module will be called mac89x0. config MACSONIC tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" depends on NETDEVICES && MAC ---help--- Support for NatSemi SONIC based Ethernet devices. This includes the onboard Ethernet in many Quadras as well as some LC-PDS, a few Nubus and all known Comm Slot Ethernet cards. If you have one of these say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. This module will be called macsonic. config MACMACE bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)" depends on NETDEVICES && MAC && EXPERIMENTAL help Support for the onboard AMD 79C940 MACE Ethernet controller used in the 660AV and 840AV Macintosh. If you have one of these Macintoshes say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MVME147_NET tristate "MVME147 (Lance) Ethernet support" depends on NETDEVICES && MVME147 help Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config MVME16x_NET tristate "MVME16x Ethernet support" depends on NETDEVICES && MVME16x help This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config BVME6000_NET tristate "BVME6000 Ethernet support" depends on NETDEVICES && BVME6000 help This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config ATARILANCE tristate "Atari Lance support" depends on NETDEVICES && ATARI help Say Y to include support for several Atari Ethernet adapters based on the AMD Lance chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). config ATARI_BIONET tristate "BioNet-100 support" depends on NETDEVICES && ATARI && ATARI_ACSI!=n help Say Y to include support for BioData's BioNet-100 Ethernet adapter for the ACSI port. The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config ATARI_PAMSNET tristate "PAMsNet support" depends on NETDEVICES && ATARI && ATARI_ACSI!=n help Say Y to include support for the PAMsNet Ethernet adapter for the ACSI port ("ACSI node"). The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config SUN3LANCE tristate "Sun3/Sun3x on-board LANCE support" depends on NETDEVICES && (SUN3 || SUN3X) help Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) featured an AMD Lance 10Mbit Ethernet controller on board; say Y here to compile in the Linux driver for this and enable Ethernet. General Linux information on the Sun 3 and 3x series (now discontinued) is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. If you're not building a kernel for a Sun 3, say N. config SUN3_82586 tristate "Sun3 on-board Intel 82586 support" depends on NETDEVICES && SUN3 help This driver enables support for the on-board Intel 82586 based Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note that this driver does not support 82586-based adapters on additional VME boards. config HPLANCE bool "HP on-board LANCE support" depends on NETDEVICES && HP300 help If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. config LASI_82596 tristate "Lasi ethernet" depends on NET_ETHERNET && PARISC && GSC_LASI help Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines. config MIPS_JAZZ_SONIC tristate "MIPS JAZZ onboard SONIC Ethernet support" depends on NET_ETHERNET && MIPS_JAZZ help This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. config MIPS_GT96100ETH bool "MIPS GT96100 Ethernet support" depends on NET_ETHERNET && MIPS_GT96100 help Say Y here to support the Ethernet subsystem on your GT96100 card. config MIPS_AU1000_ENET bool "MIPS AU1000 Ethernet support" depends on NET_ETHERNET && MIPS_AU1000 help If you have an Alchemy Semi AU1000 ethernet controller on an SGI MIPS system, say Y. Otherwise, say N. config NET_SB1250_MAC tristate "SB1250 Ethernet support" depends on NET_ETHERNET && SIBYTE_SB1250 config SGI_IOC3_ETH bool "SGI IOC3 Ethernet" depends on NET_ETHERNET && (IA64_SGI_SN1 || SGI_IP27) help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config STNIC tristate "National DP83902AV support" depends on NET_ETHERNET && SUPERH help Support for cards based on the National Semiconductor DP83902AV ST-NIC Serial Network Interface Controller for Twisted Pair. This is a 10Mbit/sec Ethernet controller. Product overview and specs at <http://www.national.com/pf/DP/DP83902A.html>. If unsure, say N. config SUNLANCE tristate "Sun LANCE support" depends on NET_ETHERNET && SBUS help This driver supports the "le" interface present on all 32-bit Sparc systems, on some older Ultra systems and as an Sbus option. These cards are based on the AMD Lance chipset, which is better known via the NE2100 cards. This support is also available as a module called sunlance ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config HAPPYMEAL tristate "Sun Happy Meal 10/100baseT support" depends on NET_ETHERNET && (SBUS || PCI) help This driver supports the "hme" interface present on most Ultra systems and as an option on older Sbus systems. This driver supports both PCI and Sbus devices. This driver also supports the "qfe" quad 100baseT device available in both PCI and Sbus configurations. This support is also available as a module called sunhme ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config SUNBMAC tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)" depends on NET_ETHERNET && SBUS && EXPERIMENTAL help This driver supports the "be" interface available as an Sbus option. This is Sun's older 100baseT Ethernet device. This support is also available as a module called sunbmac ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config SUNQE tristate "Sun QuadEthernet support" depends on NET_ETHERNET && SBUS help This driver supports the "qe" 10baseT Ethernet device, available as an Sbus option. Note that this is not the same as Quad FastEthernet "qfe" which is supported by the Happy Meal driver instead. This support is also available as a module called sunqe ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config SUNGEM tristate "Sun GEM support" depends on NET_ETHERNET && PCI help Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>. config NET_VENDOR_3COM bool "3COM cards" depends on NET_ETHERNET && (ISA || EISA || MCA || PCI) help If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about 3COM cards. If you say Y, you will be asked for your specific card in the following questions. config EL1 tristate "3c501 \"EtherLink\" support" depends on NET_VENDOR_3COM && ISA ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Also, consider buying a new card, since the 3c501 is slow, broken, and obsolete: you will have problems. Some people suggest to ping ("man ping") a nearby machine every minute ("man cron") when using this card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c501. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config EL2 tristate "3c503 \"EtherLink II\" support" depends on NET_VENDOR_3COM && ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c503. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ELPLUS tristate "3c505 \"EtherLink Plus\" support" depends on NET_VENDOR_3COM && ISA ---help--- Information about this network (Ethernet) card can be found in <file:Documentation/networking/3c505.txt>. If you have a card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called 3c505. config EL16 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)" depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c507. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config EL3 tristate "3c509/3c529 (MCA)/3c569B (98)/3c579 \"EtherLink III\" support" depends on NET_VENDOR_3COM && (ISA || EISA || MCA) ---help--- If you have a network (Ethernet) card belonging to the 3Com EtherLinkIII series, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If your card is not working you may need to use the DOS setup disk to disable Plug & Play mode, and to select the default media type. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called 3c509. config 3C515 tristate "3c515 ISA \"Fast EtherLink\"" depends on NET_VENDOR_3COM && (ISA || EISA) help If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet network card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called 3c515. config ELMC tristate "3c523 \"EtherLink/MC\" support" depends on NET_VENDOR_3COM && MCA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c523. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ELMC_II tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)" depends on NET_VENDOR_3COM && MCA && EXPERIMENTAL help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c527. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config VORTEX tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support" depends on NET_VENDOR_3COM && (PCI || EISA) ---help--- This option enables driver support for a large number of 10mbps and 10/100mbps EISA, PCI and PCMCIA 3Com network cards: "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI "Boomerang" (EtherLink XL 3c900 or 3c905) PCI "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus "Tornado" (3c905) PCI "Hurricane" (3c555/3cSOHO) PCI If you have such a card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. More specific information is in <file:Documentation/networking/vortex.txt> and in the comments at the beginning of <file:drivers/net/3c59x.c>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config TYPHOON tristate "3cr990 series \"Typhoon\" support" depends on NET_VENDOR_3COM && PCI ---help--- This option enables driver support for the 3cr990 series of cards: 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server, 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called typhoon.o. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config LANCE tristate "AMD LANCE and PCnet (AT1500 and NE2100) support" depends on NET_ETHERNET && ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are of this type. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called lance. config NET_VENDOR_SMC bool "Western Digital/SMC cards" depends on NET_ETHERNET && (ISA || MCA || EISA || MAC) help If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Western Digital cards. If you say Y, you will be asked for your specific card in the following questions. config WD80x3 tristate "WD80*3 support" depends on NET_VENDOR_SMC && ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wd. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ULTRAMCA tristate "SMC Ultra MCA support" depends on NET_VENDOR_SMC && MCA help If you have a network (Ethernet) card of this type and are running an MCA based system (PS/2), say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-mca. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ULTRA tristate "SMC Ultra support" depends on NET_VENDOR_SMC && ISA ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Important: There have been many reports that, with some motherboards mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, such as some BusLogic models) causes corruption problems with many operating systems. The Linux smc-ultra driver has a work-around for this but keep it in mind if you have such a SCSI card and have problems. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-ultra. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ULTRA32 tristate "SMC Ultra32 EISA support" depends on NET_VENDOR_SMC && EISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-ultra32. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config SMC9194 tristate "SMC 9194 support" depends on NET_VENDOR_SMC && (ISA || MAC) ---help--- This is support for the SMC9xxx based Ethernet cards. Choose this option if you have a DELL laptop with the docking station, or another SMC9192/9194 based chipset. Say Y if you want it compiled into the kernel, and read the file <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc9194. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NET_VENDOR_RACAL bool "Racal-Interlan (Micom) NI cards" depends on NET_ETHERNET && ISA help If you have a network (Ethernet) card belonging to this class, such as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about NI cards. If you say Y, you will be asked for your specific card in the following questions. config NI5010 tristate "NI5010 support (EXPERIMENTAL)" depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that this is still experimental code. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni5010. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NI52 tristate "NI5210 support" depends on NET_VENDOR_RACAL && ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni52. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NI65 tristate "NI6510 support" depends on NET_VENDOR_RACAL && ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni65. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. source "drivers/net/tulip/Kconfig" config AT1700 tristate "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)" depends on NET_ETHERNET && (ISA || MCA) && EXPERIMENTAL ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called at1700. config DEPCA tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" depends on NET_ETHERNET && (ISA || EISA || MCA) ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto> as well as <file:drivers/net/depca.c>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called depca. config HP100 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" depends on NET_ETHERNET && (ISA || EISA || PCI) help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called hp100. config NET_ISA bool "Other ISA cards" depends on NET_ETHERNET && ISA && !X86_PC9800 ---help--- If your network (Ethernet) card hasn't been mentioned yet and its bus system (that's the way the cards talks to the other components of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. Make sure you know the name of your card. Read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If unsure, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the remaining ISA network card questions. If you say Y, you will be asked for your specific card in the following questions. config E2100 tristate "Cabletron E21xx support" depends on NET_ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e2100. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config EWRK3 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" depends on NET_ISA ---help--- This driver supports the DE203, DE204 and DE205 network (Ethernet) cards. If this is for you, say Y and read <file:Documentation/networking/ewrk3.txt> in the kernel source as well as the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called ewrk3. config EEXPRESS tristate "EtherExpress 16 support" depends on NET_ISA ---help--- If you have an EtherExpress16 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that the Intel EtherExpress16 card used to be regarded as a very poor choice because the driver was very unreliable. We now have a new driver that should do better. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called eexpress. config EEXPRESS_PRO tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" depends on NET_ISA ---help--- If you have a network (Ethernet) card of this type, say Y. This driver supports intel i82595{FX,TX} based boards. Note however that the EtherExpress PRO/100 Ethernet card has its own separate driver. Please read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eepro. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config FMV18X tristate "FMV-181/182/183/184 support (OBSOLETE)" depends on NET_ISA && OBSOLETE ---help--- If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you use an FMV-183 or FMV-184 and it is not working, you may need to disable Plug & Play mode of the card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fmv18x. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config HPLAN_PLUS tristate "HP PCLAN+ (27247B and 27252A) support" depends on NET_ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called hp-plus. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config HPLAN tristate "HP PCLAN (27245 and other 27xxx series) support" depends on NET_ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called hp. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config LP486E tristate "LP486E on board Ethernet" depends on NET_ISA help Say Y here to support the 82596-based on-board Ethernet controller for the Panther motherboard, which is one of the two shipped in the Intel Professional Workstation. config ETH16I tristate "ICL EtherTeam 16i/32 support" depends on NET_ISA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eth16i. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NE2000 tristate "NE2000/NE1000 support" depends on NET_ISA || (Q40 && m) ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Many Ethernet cards without a specific driver are compatible with NE2000. If you have a PCI NE2000 card however, say N here and Y to "PCI NE2000 support", above. If you have a NE2000 card and are running on an MCA system (a bus system used on some IBM PS/2 computers and laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", below. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ZNET tristate "Zenith Z-Note support (EXPERIMENTAL)" depends on NET_ISA && EXPERIMENTAL help The Zenith Z-Note notebook computer has a built-in network (Ethernet) card, and this is the Linux driver for it. Note that the IBM Thinkpad 300 is compatible with the Z-Note and is also supported by this driver. Read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config SEEQ8005 tristate "SEEQ8005 support (EXPERIMENTAL)" depends on NET_ISA && OBSOLETE && EXPERIMENTAL help This is a driver for the SEEQ 8005 network (Ethernet) card. If this is for you, read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called ewrk3. config SK_G16 tristate "SK_G16 support (OBSOLETE)" depends on NET_ISA && OBSOLETE help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config NET_CBUS bool "NEC PC-9800 C-bus cards" depends on NET_ETHERNET && ISA && X86_PC9800 ---help--- If your network (Ethernet) card hasn't been mentioned yet and its bus system (that's the way the cards talks to the other components of your computer) is NEC PC-9800 C-Bus, say Y. config NE2K_CBUS tristate "Most NE2000-based Ethernet support" depends on NET_CBUS config NE2K_CBUS_EGY98 bool "Melco EGY-98 support" depends on NE2K_CBUS config NE2K_CBUS_LGY98 bool "Melco LGY-98 support" depends on NE2K_CBUS config NE2K_CBUS_ICM bool "ICM IF-27xxET support" depends on NE2K_CBUS config NE2K_CBUS_IOLA98 bool "I-O DATA LA-98 support" depends on NE2K_CBUS config NE2K_CBUS_CNET98EL bool "Contec C-NET(98)E/L support" depends on NE2K_CBUS config NE2K_CBUS_CNET98EL_IO_BASE hex "C-NET(98)E/L I/O base address (0xaaed or 0x55ed)" depends on NE2K_CBUS_CNET98EL default "0xaaed" config NE2K_CBUS_ATLA98 bool "Allied Telesis LA-98 Support" depends on NE2K_CBUS config NE2K_CBUS_BDN bool "ELECOM Laneed LD-BDN[123]A Support" depends on NE2K_CBUS config NE2K_CBUS_NEC108 bool "NEC PC-9801-108 Support" depends on NE2K_CBUS config SKMC tristate "SKnet MCA support" depends on NET_ETHERNET && MCA ---help--- These are Micro Channel Ethernet adapters. You need to say Y to "MCA support" in order to use this driver. Supported cards are the SKnet Junior MC2 and the SKnet MC2(+). The driver automatically distinguishes between the two cards. Note that using multiple boards of different type hasn't been tested with this driver. Say Y if you have one of these Ethernet adapters. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called sk_mca. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NE2_MCA tristate "NE/2 (ne2000 MCA version) support" depends on NET_ETHERNET && MCA help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne2. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config IBMLANA tristate "IBM LAN Adapter/A support" depends on NET_ETHERNET && MCA ---help--- This is a Micro Channel Ethernet adapter. You need to set CONFIG_MCA to use this driver. It is both available as an in-kernel driver and as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The only currently supported card is the IBM LAN Adapter/A for Ethernet. It will both support 16K and 32K memory windows, however a 32K window gives a better security against packet losses. Usage of multiple boards with this driver should be possible, but has not been tested up to now due to lack of hardware. config NET_PCI bool "EISA, VLB, PCI and on board controllers" depends on NET_ETHERNET && (ISA || EISA || PCI) help This is another class of network cards which attach directly to the bus. If you have one of those, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about this class of network cards. If you say Y, you will be asked for your specific card in the following questions. If you are unsure, say Y. config PCNET32 tristate "AMD PCnet32 PCI support" depends on NET_PCI && PCI help If you have a PCnet32 or PCnetPCI based network (Ethernet) card, answer Y here and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called pcnet32. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config AMD8111_ETH tristate "AMD 8111 (new PCI lance) support" depends on NET_PCI && PCI help If you have an AMD 8111-based PCI lance ethernet card, answer Y here and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called amd8111e. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ADAPTEC_STARFIRE tristate "Adaptec Starfire/DuraLAN support" depends on NET_PCI && PCI help Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network adapter. The DuraLAN chip is used on the 64 bit PCI boards from Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip driver. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called starfire. config ADAPTEC_STARFIRE_NAPI bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" depends on ADAPTEC_STARFIRE && EXPERIMENTAL help NAPI is a new driver API designed to reduce CPU and interrupt load when the driver is receiving lots of packets from the card. It is still somewhat experimental and thus not yet enabled by default. If your estimated Rx load is 10kpps or more, or if the card will be deployed on potentially unfriendly networks (e.g. in a firewall), then say Y here. config AC3200 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ac3200. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config APRICOT tristate "Apricot Xen-II on board Ethernet" depends on NET_PCI && ISA help If you have a network (Ethernet) controller of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called apricot. config B44 tristate "Broadcom 4400 ethernet support (EXPERIMENTAL)" depends on NET_PCI && PCI && EXPERIMENTAL help If you have a network (Ethernet) controller of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called b44. config CS89x0 tristate "CS89x0 support" depends on NET_PCI && ISA ---help--- Support for CS89x0 chipset based Ethernet cards. If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto> as well as <file:Documentation/networking/cs89x0.txt>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called cs89x. config DGRS tristate "Digi Intl. RightSwitch SE-X support" depends on NET_PCI && (PCI || EISA) ---help--- This is support for the Digi International RightSwitch series of PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6 models. If you have a network card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. More specific information is contained in <file:Documentation/networking/dgrs.txt>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dgrs. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config EEPRO100 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)" depends on NET_PCI && PCI help If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eepro100. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config EEPRO100_PIO bool "Use PIO instead of MMIO" if !X86_VISWS depends on EEPRO100 default y if X86_VISWS help This instructs the driver to use programmed I/O ports (PIO) instead of PCI shared memory (MMIO). This can possibly solve some problems in case your mainboard has memory consistency issues. If unsure, say N. config E100 tristate "EtherExpressPro/100 support (e100, Alternate Intel driver)" depends on NET_PCI && PCI ---help--- This driver supports Intel(R) PRO/100 family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82558 PRO/100+ PCI Adapter 668081-xxx, 689661-xxx 82558 PRO/100+ Management Adapter 691334-xxx, 701738-xxx, 721383-xxx 82558 PRO/100+ Dual Port Server Adapter 714303-xxx, 711269-xxx, A28276-xxx 82558 PRO/100+ PCI Server Adapter 710550-xxx 82550 PRO/100 S Server Adapter 752438-xxx 82559 A56831-xxx, A10563-xxx, A12171-xxx, A12321-xxx, A12320-xxx, A12170-xxx 748568-xxx 748565-xxx 82550 PRO/100 S Desktop Adapter 751767-xxx 82559 748592-xxx, A12167-xxx, A12318-xxx, A12317-xxx, A12165-xxx, 748569-xxx 82559 PRO/100+ Server Adapter 729757-xxx 82559 PRO/100 S Management Adapter 748566-xxx, 748564-xxx 82550 PRO/100 S Dual Port Server Adapter A56831-xxx 82551 PRO/100 M Desktop Adapter A80897-xxx PRO/100 S Advanced Management Adapter 747842-xxx, 745171-xxx CNR PRO/100 VE Desktop Adapter A10386-xxx, A10725-xxx, A23801-xxx, A19716-xxx PRO/100 VM Desktop Adapter A14323-xxx, A19725-xxx, A23801-xxx, A22220-xxx, A23796-xxx To verify that your adapter is supported, find the board ID number on the adapter. Look for a label that has a barcode and a number in the format 123456-001 (six digits hyphen three digits). Match this to the list of numbers above. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: http://support.intel.com/support/network/adapter/pro100/21397.htm For the latest Intel PRO/100 network driver for Linux, see: http://appsr.intel.com/scripts-df/support_intel.asp More specific information on configuring the driver is in <file:Documentation/networking/e100.txt>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e100. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config LNE390 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" depends on NET_PCI && EISA && EXPERIMENTAL help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called lne390. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config FEALNX tristate "Myson MTD-8xx PCI Ethernet support" depends on NET_PCI && PCI help Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet cards. Specifications and data at <http://www.myson.com.hk/mtd/datasheet/>. config NATSEMI tristate "National Semiconductor DP8381x series PCI Ethernet support" depends on NET_PCI && PCI help This driver is for the National Semiconductor DP83810 series, which is used in cards from PureData, NetGear, Linksys and others, including the 83815 chip. More specific information and updates are available from <http://www.scyld.com/network/natsemi.html>. config NE2K_PCI tristate "PCI NE2000 and clones support (see help)" depends on NET_PCI && PCI ---help--- This driver is for NE2000 compatible PCI cards. It will not work with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 support" below). If you have a PCI NE2000 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver also works for the following NE2000 clone cards: RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond Holtek HT80232 Holtek HT80229 This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne2k-pci. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config NE3210 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" depends on NET_PCI && EISA && EXPERIMENTAL ---help--- If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Note that this driver will NOT WORK for NE3200 cards as they are completely different. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne3210. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config ES3210 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" depends on NET_PCI && EISA && EXPERIMENTAL help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called es3210. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config 8139CP tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" depends on NET_PCI && PCI && EXPERIMENTAL help This is a driver for the Fast Ethernet PCI network cards based on the RTL8139C+ chips. If you have one of those, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. This is recommended. The module will be called 8139cp. config 8139TOO tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support" depends on NET_PCI && PCI ---help--- This is a driver for the Fast Ethernet PCI network cards based on the RTL8139 chips. If you have one of those, say Y and read <file:Documentation/networking/8139too.txt> as well as the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called 8139too. config 8139TOO_PIO bool "Use PIO instead of MMIO" depends on 8139TOO help This instructs the driver to use programmed I/O ports (PIO) instead of PCI shared memory (MMIO). This can possibly solve some problems in case your mainboard has memory consistency issues. If unsure, say N. config 8139TOO_TUNE_TWISTER bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" depends on 8139TOO help This implements a function which might come in handy in case you are using low quality on long cabling. It is required for RealTek RTL-8139 revision K boards, and totally unused otherwise. It tries to match the transceiver to the cable characteristics. This is experimental since hardly documented by the manufacturer. If unsure, say Y. config 8139TOO_8129 bool "Support for older RTL-8129/8130 boards" depends on 8139TOO help This enables support for the older and uncommon RTL-8129 and RTL-8130 chips, which support MII via an external transceiver, instead of an internal one. Disabling this option will save some memory by making the code size smaller. If unsure, say Y. config 8139_OLD_RX_RESET bool "Use older RX-reset method" depends on 8139TOO help The 8139too driver was recently updated to contain a more rapid reset sequence, in the face of severe receive errors. This "new" RX-reset method should be adequate for all boards. But if you experience problems, you can enable this option to restore the old RX-reset behavior. If unsure, say N. config SIS900 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" depends on NET_PCI && PCI ---help--- This is a driver for the Fast Ethernet PCI network cards based on the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in SiS 630 and SiS 540 chipsets. If you have one of those, say Y and read the Ethernet-HOWTO, available at <http://www.tldp.org/docs.html#howto>. Please read <file:Documentation/networking/sis900.txt> and comments at the beginning of <file:drivers/net/sis900.c> for more information. This driver also supports AMD 79C901 HomePNA so that you can use your phone line as a network cable. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called sis900. config EPIC100 tristate "SMC EtherPower II" depends on NET_PCI && PCI help This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, which is based on the SMC83c17x (EPIC/100). More specific information and updates are available from <http://www.scyld.com/network/epic100.html>. config SUNDANCE tristate "Sundance Alta support" depends on NET_PCI && PCI help This driver is for the Sundance "Alta" chip. More specific information and updates are available from <http://www.scyld.com/network/sundance.html>. config SUNDANCE_MMIO bool "Use MMIO instead of PIO" depends on SUNDANCE help Enable memory-mapped I/O for interaction with Sundance NIC registers. Do NOT enable this by default, PIO (enabled when MMIO is disabled) is known to solve bugs on certain chips. If unsure, say N. config TLAN tristate "TI ThunderLAN support" depends on NET_PCI && (PCI || EISA) ---help--- If you have a PCI Ethernet network card based on the ThunderLAN chip which is supported by this driver, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. Devices currently supported by this driver are Compaq Netelligent, Compaq NetFlex and Olicom cards. Please read the file <file:Documentation/networking/tlan.txt> for more details. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tlan. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. Please email feedback to torben.mathiasen@compaq.com. config VIA_RHINE tristate "VIA Rhine support" depends on NET_PCI && PCI help If you have a VIA "rhine" based network card (Rhine-I (3043) or Rhine-2 (VT86c100A)), say Y here. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called via-rhine. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config VIA_RHINE_MMIO bool "Use MMIO instead of PIO (EXPERIMENTAL)" depends on VIA_RHINE && EXPERIMENTAL help This instructs the driver to use PCI shared memory (MMIO) instead of programmed I/O ports (PIO). Enabling this gives an improvement in processing time in parts of the driver. It is not known if this works reliably on all "rhine" based cards, but it has been tested successfully on some DFE-530TX adapters. If unsure, say N. config LAN_SAA9730 bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)" depends on NET_PCI && EXPERIMENTAL && MIPS help The SAA9730 is a combined multimedia and peripheral controller used in thin clients, Internet access terminals, and diskless workstations. See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>. config NET_POCKET bool "Pocket and portable adapters" depends on NET_ETHERNET && ISA ---help--- Cute little network (Ethernet) devices which attach to the parallel port ("pocket adapters"), commonly used with laptops. If you have one of those, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to plug a network (or some other) card into the PCMCIA (or PC-card) slot of your laptop instead (PCMCIA is the standard for credit card size extension cards used by all modern laptops), you need the pcmcia-cs package (location contained in the file <file:Documentation/Changes>) and you can say N here. Laptop users should read the Linux Laptop home page at <http://www.cs.utexas.edu/users/kharker/linux-laptop/>. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about this class of network devices. If you say Y, you will be asked for your specific device in the following questions. config ATP tristate "AT-LAN-TEC/RealTek pocket adapter support" depends on NET_POCKET && ISA && X86 ---help--- This is a network (Ethernet) device which attaches to your parallel port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>, if you want to use this. If you intend to use this driver, you should have said N to the "Parallel printer support", because the two drivers don't like each other. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. The module will be called atp. config DE600 tristate "D-Link DE600 pocket adapter support" depends on NET_POCKET && ISA ---help--- This is a network (Ethernet) device which attaches to your parallel port. Read <file:Documentation/networking/DLINK.txt> as well as the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>, if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. The module will be called de600. config DE620 tristate "D-Link DE620 pocket adapter support" depends on NET_POCKET && ISA ---help--- This is a network (Ethernet) device which attaches to your parallel port. Read <file:Documentation/networking/DLINK.txt> as well as the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>, if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. The module will be called de620. config SGISEEQ bool "SGI Seeq ethernet controller support" depends on NET_ETHERNET && SGI_IP22 help Say Y here if you have an Seeq based Ethernet network card. This is used in many Silicon Graphics machines. config DECLANCE bool "DEC LANCE ethernet controller support" depends on NET_ETHERNET && DECSTATION help This driver is for the series of Ethernet controllers produced by DEC (now Compaq) based on the AMD Lance chipset, including the DEPCA series. (This chipset is better known via the NE2100 cards.) config BAGETLANCE tristate "Baget AMD LANCE support" depends on NET_ETHERNET && BAGET_MIPS help Say Y to enable kernel support for AMD Lance Ethernet cards on the MIPS-32-based Baget embedded system. This chipset is better known via the NE2100 cards. config 68360_ENET bool "Motorola 68360 ethernet controller" depends on M68360 help Say Y here if you want to use the built-in ethernet controller of the Motorola 68360 processor. config FEC bool "FEC ethernet controller (of ColdFire 5272)" depends on M5272 || M5282 help Say Y here if you want to use the built-in 10/100 Fast ethernet controller on the Motorola ColdFire 5272 processor. endmenu # # Gigabit Ethernet # menu "Ethernet (1000 Mbit)" depends on NETDEVICES config ACENIC tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" depends on PCI ---help--- Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet adapter. The driver allows for using the Jumbo Frame option (9000 bytes/frame) however it requires that your switches can handle this as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig line. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called acenic. config ACENIC_OMIT_TIGON_I bool "Omit support for old Tigon I based AceNICs" depends on ACENIC help Say Y here if you only have Tigon II based AceNICs and want to leave out support for the older Tigon I based cards which are no longer being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B version)). This will reduce the size of the driver object by app. 100KB. If you are not sure whether your card is a Tigon I or a Tigon II, say N here. The safe and default value for this is N. config DL2K tristate "D-Link DL2000-based Gigabit Ethernet support" depends on PCI help This driver supports D-Link 2000-based gigabit ethernet cards, which includes D-Link DGE-550T Gigabit Ethernet Adapter. D-Link DL2000-based Gigabit Ethernet Adapter. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called dl2k. config E1000 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" depends on PCI ---help--- This driver supports Intel(R) PRO/1000 gigabit ethernet family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82542 PRO/1000 Gigabit Server Adapter 700262-xxx, 717037-xxx 82543 PRO/1000 F Server Adapter 738640-xxx, A38888-xxx 82543 PRO/1000 T Server Adapter A19845-xxx, A33948-xxx 82544 PRO/1000 XT Server Adapter A51580-xxx 82544 PRO/1000 XF Server Adapter A50484-xxx 82544 PRO/1000 T Desktop Adapter A62947-xxx 82540 PRO/1000 MT Desktop Adapter A78408-xxx 82541 PRO/1000 MT Desktop Adapter C91016-xxx 82545 PRO/1000 MT Server Adapter A92165-xxx 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx 82545 PRO/1000 MF Server Adapter A91622-xxx 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: <http://support.intel.com/support/network/adapter/pro100/21397.htm> For general information and support, go to the Intel support website at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/e1000.txt>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e1000. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config E1000_NAPI bool "Use Rx Polling (NAPI)" depends on E1000 config MYRI_SBUS tristate "MyriCOM Gigabit Ethernet support" depends on SBUS help This driver supports MyriCOM Sbus gigabit Ethernet cards. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called myri_sbus. config NS83820 tristate "National Semiconduct DP83820 support" depends on PCI help This is a driver for the National Semiconductor DP83820 series of gigabit ethernet MACs. Cards using this chipset include the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of zero copy. config HAMACHI tristate "Packet Engines Hamachi GNIC-II support" depends on PCI help If you have a Gigabit Ethernet card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called hamachi. config YELLOWFIN tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" depends on PCI && EXPERIMENTAL ---help--- Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is used by the Beowulf Linux cluster project. See <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more information about this driver in particular and Beowulf in general. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called yellowfin. config R8169 tristate "Realtek 8169 gigabit ethernet support" depends on PCI ---help--- Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called r8169. config SK98LIN tristate "SysKonnect SK-98xx support" depends on PCI ---help--- Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server Adapter. The following adapters are supported by this driver: - SK-9841 (single link 1000Base-LX) - SK-9842 (dual link 1000Base-LX) - SK-9843 (single link 1000Base-SX) - SK-9844 (dual link 1000Base-SX) - SK-9821 (single link 1000Base-T) - SK-9822 (dual link 1000Base-T) - SK-9861 (single link Volition connector) - SK-9862 (dual link Volition connector) The driver also supports the following adapters from Allied Telesyn: - AT2970... The dual link adapters support a link-failover feature. Read <file:Documentation/networking/sk98lin.txt> for information about optional driver parameters. Questions concerning this driver may be addressed to: linux@syskonnect.de If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called sk98lin. config TIGON3 tristate "Broadcom Tigon3 support" depends on PCI help This driver supports Broadcom Tigon3 based gigabit Ethernet cards. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called tg3. endmenu # # 10 Gigabit Ethernet # menu "Ethernet (10000 Mbit)" depends on NETDEVICES config IXGB tristate "Intel(R) PRO/10GbE support" depends on PCI ---help--- This driver supports Intel(R) PRO/10GbE family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: <http://support.intel.com/support/network/adapter/pro100/21397.htm> For general information and support, go to the Intel support website at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/ixgb.txt>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ixgb. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config IXGB_NAPI bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" depends on IXGB && EXPERIMENTAL endmenu config VETH tristate "iSeries Virtual Ethernet driver support" depends on NETDEVICES && PPC_ISERIES config FDDI bool "FDDI driver support" depends on NETDEVICES && (PCI || EISA) help Fiber Distributed Data Interface is a high speed local area network design; essentially a replacement for high speed Ethernet. FDDI can run over copper or fiber. If you are connected to such a network and want a driver for the FDDI card in your computer, say Y here (and then also Y to the driver for your FDDI card, below). Most people will say N. config DEFXX tristate "Digital DEFEA and DEFPA adapter support" depends on FDDI && (PCI || EISA) help This is support for the DIGITAL series of EISA (DEFEA) and PCI (DEFPA) controllers which can connect you to a local FDDI network. config SKFP tristate "SysKonnect FDDI PCI support" depends on FDDI && PCI ---help--- Say Y here if you have a SysKonnect FDDI PCI adapter. The following adapters are supported by this driver: - SK-5521 (SK-NET FDDI-UP) - SK-5522 (SK-NET FDDI-UP DAS) - SK-5541 (SK-NET FDDI-FP) - SK-5543 (SK-NET FDDI-LP) - SK-5544 (SK-NET FDDI-LP DAS) - SK-5821 (SK-NET FDDI-UP64) - SK-5822 (SK-NET FDDI-UP64 DAS) - SK-5841 (SK-NET FDDI-FP64) - SK-5843 (SK-NET FDDI-LP64) - SK-5844 (SK-NET FDDI-LP64 DAS) - Netelligent 100 FDDI DAS Fibre SC - Netelligent 100 FDDI SAS Fibre SC - Netelligent 100 FDDI DAS UTP - Netelligent 100 FDDI SAS UTP - Netelligent 100 FDDI SAS Fibre MIC Read <file:Documentation/networking/skfp.txt> for information about the driver. Questions concerning this driver can be addressed to: linux@syskonnect.de If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt>. This is recommended. The module will be called skfp. config HIPPI bool "HIPPI driver support (EXPERIMENTAL)" depends on NETDEVICES && EXPERIMENTAL && INET && PCI help HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI can run over copper (25m) or fiber (300m on multi-mode or 10km on single-mode). HIPPI networks are commonly used for clusters and to connect to super computers. If you are connected to a HIPPI network and have a HIPPI network card in your computer that you want to use under Linux, say Y here (you must also remember to enable the driver for your HIPPI card below). Most people will say N here. config ROADRUNNER tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" depends on HIPPI && PCI help Say Y here if this is your PCI HIPPI network card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called rrunner. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If unsure, say N. config ROADRUNNER_LARGE_RINGS bool "Use large TX/RX rings (EXPERIMENTAL)" depends on ROADRUNNER help If you say Y here, the RoadRunner driver will preallocate up to 2 MB of additional memory to allow for fastest operation, both for transmitting and receiving. This memory cannot be used by any other kernel code or by user space programs. Say Y here only if you have the memory. config PLIP tristate "PLIP (parallel port) support" depends on NETDEVICES && PARPORT ---help--- PLIP (Parallel Line Internet Protocol) is used to create a reasonably fast mini network consisting of two (or, rarely, more) local machines. A PLIP link from a Linux box is a popular means to install a Linux distribution on a machine which doesn't have a CD-ROM drive (a minimal system has to be transferred with floppies first). The kernels on both machines need to have this PLIP option enabled for this to work. The PLIP driver has two modes, mode 0 and mode 1. The parallel ports (the connectors at the computers with 25 holes) are connected with "null printer" or "Turbo Laplink" cables which can transmit 4 bits at a time (mode 0) or with special PLIP cables, to be used on bidirectional parallel ports only, which can transmit 8 bits at a time (mode 1); you can find the wiring of these cables in <file:Documentation/networking/PLIP.txt>. The cables can be up to 15m long. Mode 0 works also if one of the machines runs DOS/Windows and has some PLIP software installed, e.g. the Crynwr PLIP packet driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) and winsock or NCSA's telnet. If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well as the NET-3-HOWTO, both available from <http://www.tldp.org/docs.html#howto>. Note that the PLIP protocol has been changed and this PLIP driver won't work together with the PLIP support in Linux versions 1.0.x. This option enlarges your kernel by about 8 KB. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called plip. If unsure, say Y or M, in case you buy a laptop later. config PPP tristate "PPP (point-to-point protocol) support" depends on NETDEVICES ---help--- PPP (Point to Point Protocol) is a newer and better SLIP. It serves the same purpose: sending Internet traffic over telephone (and other serial) lines. Ask your access provider if they support it, because otherwise you can't use it; most Internet access providers these days support PPP rather than SLIP. To use PPP, you need an additional program called pppd as described in the PPP-HOWTO, available at <http://www.tldp.org/docs.html#howto>. Make sure that you have the version of pppd recommended in <file:Documentation/Changes>. The PPP option enlarges your kernel by about 16 KB. There are actually two versions of PPP: the traditional PPP for asynchronous lines, such as regular analog phone lines, and synchronous PPP which can be used over digital ISDN lines for example. If you want to use PPP over phone lines or other asynchronous serial lines, you need to say Y (or M) here and also to the next option, "PPP support for async serial ports". For PPP over synchronous lines, you should say Y (or M) here and to "Support synchronous PPP", below. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you said Y to "Version information on all symbols" above, then you cannot compile the PPP driver into the kernel; you can then only compile it as a module. The module will be called ppp_generic. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. config PPP_MULTILINK bool "PPP multilink support (EXPERIMENTAL)" depends on PPP && EXPERIMENTAL help PPP multilink is a protocol (defined in RFC 1990) which allows you to combine several (logical or physical) lines into one logical PPP connection, so that you can utilize your full bandwidth. This has to be supported at the other end as well and you need a version of the pppd daemon which understands the multilink protocol. If unsure, say N. config PPP_FILTER bool "PPP filtering" depends on PPP help Say Y here if you want to be able to filter the packets passing over PPP interfaces. This allows you to control which packets count as activity (i.e. which packets will reset the idle timer or bring up a demand-dialled link) and which packets are to be dropped entirely. You need to say Y here if you wish to use the pass-filter and active-filter options to pppd. If unsure, say N. config PPP_ASYNC tristate "PPP support for async serial ports" depends on PPP ---help--- Say Y (or M) here if you want to be able to use PPP over standard asynchronous serial ports, such as COM1 or COM2 on a PC. If you use a modem (not a synchronous or ISDN modem) to contact your ISP, you need this option. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If unsure, say Y. config PPP_SYNC_TTY tristate "PPP support for sync tty ports" depends on PPP help Say Y (or M) here if you want to be able to use PPP over synchronous (HDLC) tty devices, such as the SyncLink adapter. These devices are often used for high-speed leased lines like T1/E1. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config PPP_DEFLATE tristate "PPP Deflate compression" depends on PPP ---help--- Support for the Deflate compression method for PPP, which uses the Deflate algorithm (the same algorithm that gzip uses) to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the Deflate compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config PPP_BSDCOMP tristate "PPP BSD-Compress compression" depends on PPP ---help--- Support for the BSD-Compress compression method for PPP, which uses the LZW compression method to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the BSD-Compress compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. The PPP Deflate compression method ("PPP Deflate compression", above) is preferable to BSD-Compress, because it compresses better and is patent-free. Note that the BSD compression code will always be compiled as a module; it is called bsd_comp and will show up in the directory modules once you have said "make modules". If unsure, say N. config PPPOE tristate "PPP over Ethernet (EXPERIMENTAL)" depends on EXPERIMENTAL && PPP help Support for PPP over Ethernet. This driver requires the latest version of pppd from the CVS repository at cvs.samba.org. Alternatively, see the RoaringPenguin package (http://www.roaringpenguin.com/pppoe) which contains instruction on how to use this driver (under the heading "Kernel mode PPPoE"). config PPPOATM tristate "PPP over ATM" depends on ATM && PPP help Support PPP (Point to Point Protocol) encapsulated in ATM frames. This implementation does not yet comply with section 8 of RFC2364, which can lead to bad results if the ATM peer loses state and changes its encapsulation unilaterally. config SLIP tristate "SLIP (serial line) support" depends on NETDEVICES ---help--- Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to connect to your Internet service provider or to connect to some other local Unix box or if you want to configure your Linux box as a Slip/CSlip server for other people to dial in. SLIP (Serial Line Internet Protocol) is a protocol used to send Internet traffic over serial connections such as telephone lines or null modem cables; nowadays, the protocol PPP is more commonly used for this same purpose. Normally, your access provider has to support SLIP in order for you to be able to use it, but there is now a SLIP emulator called SLiRP around (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection. If you plan to use SLiRP, make sure to say Y to CSLIP, below. The NET-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>, explains how to configure SLIP. Note that you don't need this option if you just want to run term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP support will enlarge your kernel by about 4 KB. If unsure, say N. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read <file:Documentation/modules.txt> as well as <file:Documentation/networking/net-modules.txt>. The module will be called slip. config SLIP_COMPRESSED bool "CSLIP compressed headers" depends on SLIP ---help--- This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>, explains how to configure CSLIP. This won't enlarge your kernel. config SLIP_SMART bool "Keepalive and linefill" depends on SLIP help Adds additional capabilities to the SLIP driver to support the RELCOM line fill and keepalive monitoring. Ideal on poor quality analogue lines. config SLIP_MODE_SLIP6 bool "Six bit SLIP encapsulation" depends on SLIP help Just occasionally you may need to run IP over hostile serial networks that don't pass all control characters or are only seven bit. Saying Y here adds an extra mode you can use with SLIP: "slip6". In this mode, SLIP will only send normal ASCII symbols over the serial device. Naturally, this has to be supported at the other end of the link as well. It's good enough, for example, to run IP over the async ports of a Camtec JNT Pad. If unsure, say N. source "drivers/net/wireless/Kconfig" source "drivers/net/tokenring/Kconfig" config NET_FC bool "Fibre Channel driver support" depends on NETDEVICES && SCSI && PCI help Fibre Channel is a high speed serial protocol mainly used to connect large storage devices to the computer; it is compatible with and intended to replace SCSI. If you intend to use Fibre Channel, you need to have a Fibre channel adaptor card in your computer; say Y here and to the driver for your adaptor below. You also should have said Y to "SCSI support" and "SCSI generic support". config IPHASE5526 tristate "Interphase 5526 Tachyon chipset based adapter support" depends on NET_FC && SCSI && PCI help Say Y here if you have a Fibre Channel adaptor of this kind. The driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called iph5526. For general information about modules read <file:Documentation/modules.txt>. config RCPCI tristate "Red Creek Hardware VPN (EXPERIMENTAL)" depends on NETDEVICES && EXPERIMENTAL && PCI help This is a driver for hardware which provides a Virtual Private Network (VPN). Say Y if you have it. This code is also available as a module called rcpci ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. config SHAPER tristate "Traffic Shaper (EXPERIMENTAL)" depends on NETDEVICES && EXPERIMENTAL ---help--- The traffic shaper is a virtual network device that allows you to limit the rate of outgoing data flow over some other network device. The traffic that you want to slow down can then be routed through these virtual devices. See <file:Documentation/networking/shaper.txt> for more information. An alternative to this traffic shaper is the experimental Class-Based Queueing (CBQ) scheduling support which you get if you say Y to "QoS and/or fair queueing" above. To set up and configure shaper devices, you need the shapecfg program, available from <ftp://shadow.cabi.net/pub/Linux/> in the shaper package. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called shaper. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>. If unsure, say N. source "drivers/net/wan/Kconfig" source "drivers/net/pcmcia/Kconfig" source "drivers/atm/Kconfig" source "drivers/s390/net/Kconfig"