You can say N here if you don't intend to connect your Linux box to any other computer at all. You'll have to say Y if your computer contains a network card that you want to use under Linux. If you are going to run SLIP or PPP over telephone line or null modem cable you need say Y here. Connecting two machines with parallel ports using PLIP needs this, as well as AX.25/KISS for sending Internet traffic over amateur radio links. See also "The Linux Network Administrator's Guide" by Olaf Kirch and Terry Dawson. Available at <http://www.tldp.org/guides.html>. If unsure, say Y.
This is an intermediate driver that allows sharing of resources. To compile this driver as a module, choose M here: the module will be called ifb. If you want to use more than one ifb device at a time, you need to compile this driver as a module. Instead of 'ifb', the devices will then be called 'ifb0', 'ifb1' etc. Look at the iproute2 documentation directory for usage etc
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>. To compile this driver as a module, choose M here: 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.
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, 802.3ad by the IEEE, and 'Bonding' in Linux. The driver supports multiple bonding modes to allow for both high performance and high availability operation. Refer to <file:Documentation/networking/bonding.txt> for more information. To compile this driver as a module, choose M here: the module will be called bonding.
This allows one to create virtual interfaces that map packets to or from specific MAC addresses to a particular interface. Macvlan devices can be added using the "ip" command from the iproute2 package starting with the iproute2-2.6.23 release: "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" To compile this driver as a module, choose M here: the module will be called macvlan.
This adds a specialized tap character device driver that is based on the MAC-VLAN network interface, called macvtap. A macvtap device can be added in the same way as a macvlan device, using 'type macvlan', and then be accessed through the tap user space interface. To compile this driver as a module, choose M here: the module will be called macvtap.
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>. To compile this driver as a module, choose M here: the module will be called eql. If unsure, say N.
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. To compile this driver as a module, choose M here: the module will be called tun. If you don't know what to use this for, you don't need it.
This device is a local ethernet tunnel. Devices are created in pairs. When one end receives the packet it appears on its pair and vice versa.
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.
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 lacks MII.
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.
The Atmel MACB ethernet interface is found on many AT32 and AT91 parts. Say Y to include support for the MACB chip. To compile this driver as a module, choose M here: the module will be called macb.
AX88796 driver, using platform bus to provide chip detection and resources
Select this if your platform comes with an external 93CX6 eeprom.
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. To compile this driver as a module, choose M here: the module will be called mace.
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.
Say Y for support of BMAC Ethernet interfaces. These are used on G3 computers. To compile this driver as a module, choose M here: the module will be called bmac.
If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called ariadne.
If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called a2065.
If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called hydra.
This driver is for Zorro Ethernet cards using an NS8390-compatible chipset, like the Village Tronic Ariadne II and the Individual Computers X-Surf Ethernet cards. If you have such a card, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called zorro8390.
If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called apne.
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>.
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>. To compile this driver as a module, choose M here. This module will be called mac89x0.
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>. To compile this driver as a module, choose M here. This module will be called macsonic.
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>.
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. To compile this driver as a module, choose M here.
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. To compile this driver as a module, choose M here.
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. To compile this driver as a module, choose M here.
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).
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.
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.
If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here.
Say Y here to support the builtin Intel 82596 ethernet controller found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
Say Y here to support the on-board Intel 82596 ethernet controller built into SNI RM machines.
If you have a Mikrotik RouterBoard 500 or IDT RC32434 based system say Y. Otherwise say N.
This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
This is the driver for the onboard card of the Xtensa XT2000 board.
If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N.
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>.
The MIPSNET device is a simple Ethernet network device which is emulated by the MIPS Simulator. If you are not using a MIPSsim or are unsure, say N.
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.
Renesas SuperH Ethernet device driver. This driver supporting CPUs are: - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
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. To compile this driver as a module, choose M here: the module will be called sunlance.
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. To compile this driver as a module, choose M here: the module will be called sunhme.
This driver supports the "be" interface available as an Sbus option. This is Sun's older 100baseT Ethernet device. To compile this driver as a module, choose M here: the module will be called sunbmac.
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. To compile this driver as a module, choose M here: the module will be called sunqe.
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>.
Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
Support for virtual network devices under Sun Logical Domains.
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.
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.
To compile this driver as a module, choose M here. The module
will be called 3c501.
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>. To compile this driver as a module, choose M here. The module will be called 3c503.
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>. To compile this driver as a module, choose M here. The module will be called 3c505.
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>. To compile this driver as a module, choose M here. The module will be called 3c507.
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. To compile this driver as a module, choose M here. The module will be called 3c509.
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>. To compile this driver as a module, choose M here. The module will be called 3c515.
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>. To compile this driver as a module, choose M here. The module will be called 3c523.
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>. To compile this driver as a module, choose M here. The module will be called 3c527.
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>. To compile this support as a module, choose M here.
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>. To compile this driver as a module, choose M here. The module will be called typhoon.
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. To compile this driver as a module, choose M here: the module will be called lance. This is recommended.
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.
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>. To compile this driver as a module, choose M here. The module will be called wd.
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>. To compile this driver as a module, choose M here. The module will be called smc-mca.
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. To compile this driver as a module, choose M here. The module will be called smc-ultra.
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>. To compile this driver as a module, choose M here. The module will be called smc-ultra32.
This is the driver for Blackfin on-chip mac device. Say Y if you want it compiled into the kernel. 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 bfin_mac.
To get maximum network performance, you should use L1 memory as rx/tx buffers. Say N here if you want to reserve L1 memory for other uses.
Set the number of buffer packets used in driver.
Set the number of buffer packets used in driver.
To support the IEEE 1588 Precision Time Protocol (PTP), select y here
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>. To compile this driver as a module, choose M here. The module will be called smc9194.
This is a driver for SMC's 91x series of Ethernet chipsets, including the SMC91C94 and the SMC91C111. 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 smc91x. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>.
This driver supports the pxa168 Ethernet ports. To compile this driver as a module, choose M here. The module will be called pxa168_eth.
This is support for the Hilscher netX builtin Ethernet ports To compile this driver as a module, choose M here. The module will be called netx-eth.
This driver supports TI's DaVinci Ethernet . To compile this driver as a module, choose M here: the module will be called davinci_emac_driver. This is recommended.
This driver supports TI's DaVinci MDIO module. To compile this driver as a module, choose M here: the module will be called davinci_mdio. This is recommended.
This driver supports TI's DaVinci CPDMA dma engine. To compile this driver as a module, choose M here: the module will be called davinci_cpdma. This is recommended.
Support for DM9000 chipset. To compile this driver as a module, choose M here. The module will be called dm9000.
The maximum level of debugging code compiled into the DM9000 driver.
This configuration forces the DM9000 to use the NSR's LinkStatus bit to determine if the link is up or down instead of the more costly MII PHY reads. Note, this will not work if the chip is operating with an external PHY.
Support for the Microchip EN28J60 ethernet chip. To compile this driver as a module, choose M here. The module will be called enc28j60.
Enable the verify after the buffer write useful for debugging purpose. If unsure, say N.
Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
This is a driver for SMSC's LAN911x series of Ethernet chipsets including the new LAN9115, LAN9116, LAN9117, and LAN9118. Say Y if you want it compiled into the kernel, and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module. The module will be called smc911x. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>
Say Y here if you want support for SMSC LAN911x and LAN921x families of ethernet controllers. To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called smsc911x.
If the arch enables this, it allows the arch to implement various hooks for more comprehensive interrupt control and also to override the source of the MAC address.
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.
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. To compile this driver as a module, choose M here. The module will be called ni5010.
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>. To compile this driver as a module, choose M here. The module will be called ni52.
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>. To compile this driver as a module, choose M here. The module will be called ni65.
The Dave ethernet interface (DNET) is found on Qong Board FPGA. Say Y to include support for the DNET chip. To compile this driver as a module, choose M here: the module will be called dnet.
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>. To compile this driver as a module, choose M here. The module will be called at1700.
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>. To compile this driver as a module, choose M here. The module will be called depca.
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>. To compile this driver as a module, choose M here. The module will be called hp100.
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.
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>. To compile this driver as a module, choose M here. The module will be called e2100.
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>. To compile this driver as a module, choose M here. The module will be called ewrk3.
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. To compile this driver as a module, choose M here. The module will be called eexpress.
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>.
To compile this driver as a module, choose M here. The module
will be called eepro.
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>. To compile this driver as a module, choose M here. The module will be called hp-plus.
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>. To compile this driver as a module, choose M here. The module will be called hp.
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.
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>. To compile this driver as a module, choose M here. The module will be called eth16i.
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 and clone support" under "EISA, VLB, PCI and on board controllers" below. 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. To compile this driver as a module, choose M here. The module will be called ne.
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>.
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>. To compile this driver as a module, choose M here. The module will be called seeq8005.
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>. To compile this driver as a module, choose M here. The module will be called ne2.
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. To compile this driver as a module, choose M here. 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.
This driver supports virtual ethernet adapters on newer IBM iSeries and pSeries systems. To compile this driver as a module, choose M here. The module will be called ibmveth.
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.
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>. To compile this driver as a module, choose M here. The module will be called pcnet32.
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>. To compile this driver as a module, choose M here. The module will be called amd8111e.
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. To compile this driver as a module, choose M here: the module will be called starfire. This is recommended.
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>. To compile this driver as a module, choose M here. The module will be called ac3200.
This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. To compile this driver as a module, choose M here. The module will be called ksz884x.
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>. To compile this driver as a module, choose M here. The module will be called apricot.
If you have a network (Ethernet) controller of this type, say Y or M and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here. The module will be called b44.
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>. To compile this driver as a module, choose M here. The module will be called forcedeth.
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>. To compile this driver as a module, choose M here. The module will be called cs89x0.
This driver supports Intel(R) PRO/100 family of adapters. 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). Use the above information and the Adapter & Driver ID Guide at: <http://support.intel.com/support/network/adapter/pro100/21397.htm> to identify the adapter. For the latest Intel PRO/100 network driver for Linux, see: <http://www.intel.com/p/en_US/support/highlights/network/pro100plus> More specific information on configuring the driver is in <file:Documentation/networking/e100.txt>. To compile this driver as a module, choose M here. The module will be called e100.
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>. To compile this driver as a module, choose M here. The module will be called lne390.
Say Y here to support the Myson MTD-800 family of PCI-based Ethernet cards. <http://www.myson.com.tw/>
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>.
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 To compile this driver as a module, choose M here. The module will be called ne2k-pci.
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. To compile this driver as a module, choose M here. The module will be called ne3210.
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>. To compile this driver as a module, choose M here. The module will be called es3210.
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>. To compile this driver as a module, choose M here: the module will be called 8139cp. This is recommended.
This is a driver for the Fast Ethernet PCI network cards based on the RTL 8129/8130/8139 chips. If you have one of those, say Y and read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here: the module will be called 8139too. This is recommended.
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.
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.
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.
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.
This is a driver for the R6040 Fast Ethernet MACs found in the the RDC R-321x System-on-chips. To compile this driver as a module, choose M here: the module will be called r6040. This is recommended.
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. This driver also supports AMD 79C901 HomePNA so that you can use your phone line as a network cable. To compile this driver as a module, choose M here: the module will be called sis900. This is recommended.
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>.
This is a driver for SMSC's LAN9420 PCI ethernet adapter. Say Y if you want it compiled into the kernel, and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. This driver is also available as a module. The module will be called smsc9420. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.txt>
This driver is for the Sundance "Alta" chip. More specific information and updates are available from <http://www.scyld.com/network/sundance.html>.
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.
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. To compile this driver as a module, choose M here. The module will be called tlan. Please email feedback to <torben.mathiasen@compaq.com>.
This platform driver is for KSZ8841(1-port) / KS8842(2-port) ethernet switch chip (managed, VLAN, QoS) from Micrel or Timberdale(FPGA).
SPI driver for Micrel KS8851 SPI attached network chip.
This platform driver is for Micrel KS8851 Address/data bus multiplexed network chip.
If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type Ethernet functions can also be found integrated on South Bridges (e.g. VT8235). To compile this driver as a module, choose M here. The module will be called via-rhine.
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. If unsure, say Y.
This is a driver for the Fast Ethernet PCI network cards based on the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you have one of these, say Y here. To compile this driver as a module, choose M here: the module will be called sc92031. This is recommended.
TI AR7 CPMAC Ethernet support
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.linux-on-laptops.com/> or
Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
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.
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. To compile this driver as a module, choose M here: the module will be called atp.
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. To compile this driver as a module, choose M here: the module will be called de600.
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. To compile this driver as a module, choose M here: the module will be called de620.
Say Y here if you have an Seeq based Ethernet network card. This is used in many Silicon Graphics machines.
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.)
Say Y here if you want to use the built-in ethernet controller of the Motorola 68360 processor.
Say Y here if you want to use the built-in 10/100 Fast ethernet controller on some Motorola ColdFire and Freescale i.MX processors.
This option enables support for the MPC5200's on-chip Fast Ethernet Controller If compiled as module, it will be called fec_mpc52xx.
The MPC5200's FEC can connect to the Ethernet either with an external MII PHY chip or 10 Mbps 7-wire interface (Motorola? industry standard). If your board uses an external PHY connected to FEC, enable this. If not sure, enable. If compiled as module, it will be called fec_mpc52xx_phy.
Say Y here if you want to use the NE2000 compatible controller on the Renesas H8/300 processor.
This driver supports the Atheros L2 fast ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl2.
This driver supports the 10/100 Ethernet Lite from Xilinx.
This driver supports the ethernet MACs in the Broadcom 63xx MIPS chipset family (BCM63XX).
This driver supports the FTMAC100 10/100 Ethernet controller from Faraday. It is used on Faraday A320, Andes AG101 and some other ARM/NDS32 SoC's.
Support for the MII0 inside the Lantiq SoC
Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common type of Local Area Network (LAN) in universities and companies. Say Y here to get to see options for Gigabit Ethernet drivers. This option alone does not add any kernel code. Note that drivers supporting both 100 and 1000 MBit may be listed under "Ethernet (10 or 100MBit)" instead. If you say N, all options in this submenu will be skipped and disabled.
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. To compile this driver as a module, choose M here: the module will be called acenic.
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.
This driver supports DL2000/TC902x-based Gigabit ethernet cards, which includes D-Link DGE-550T Gigabit Ethernet Adapter. D-Link DL2000-based Gigabit Ethernet Adapter. Sundance/Tamarack TC902x Gigabit Ethernet Adapter. To compile this driver as a module, choose M here: the module will be called dl2k.
This driver supports Intel(R) PRO/1000 gigabit ethernet family of adapters. 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>. To compile this driver as a module, choose M here. The module will be called e1000.
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit ethernet family of adapters. For PCI or PCI-X e1000 adapters, use the regular e1000 driver 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> To compile this driver as a module, choose M here. The module will be called e1000e.
This driver supports IP1000 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called ipg. This is recommended.
This driver supports Intel(R) 82575/82576 gigabit ethernet family of adapters. 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>. To compile this driver as a module, choose M here. The module will be called igb.
Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses.
This driver supports Intel(R) 82576 virtual functions. 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>. To compile this driver as a module, choose M here. The module will be called igbvf.
This driver supports MyriCOM Sbus gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called myri_sbus. This is recommended.
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.
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>. To compile this driver as a module, choose M here. The module will be called hamachi.
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. To compile this driver as a module, choose M here: the module will be called yellowfin. This is recommended.
Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. To compile this driver as a module, choose M here: the module will be called r8169. This is recommended.
This driver supports Gigabit Ethernet interfaces based on the Broadcom SiByte family of System-On-a-Chip parts. They include the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 and BCM1480 chips. To compile this driver as a module, choose M here: the module will be called sb1250-mac.
Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to appear in lan on motherboard designs which are based on SiS 965 and SiS 966 south bridge. To compile this driver as a module, choose M here: the module will be called sis190. This is recommended.
This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx and related Gigabit Ethernet adapters. It is a new smaller driver with better performance and more complete ethtool support. It does not support the link failover and network management features that "portable" vendor supplied sk98lin driver does. This driver supports adapters based on the original Yukon chipset: Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. It does not support the newer Yukon2 chipset: a separate driver, sky2, is provided for Yukon2-based adapters. To compile this driver as a module, choose M here: the module will be called skge. This is recommended.
This option adds the ability to dump driver state for debugging. The file /sys/kernel/debug/skge/ethX displays the state of the internal transmit and receive rings. If unsure, say N.
This driver supports Gigabit Ethernet adapters based on the Marvell Yukon 2 chipset: Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 There is companion driver for the older Marvell Yukon and Genesis based adapters: skge. To compile this driver as a module, choose M here: the module will be called sky2. This is recommended.
This option adds the ability to dump driver state for debugging. The file /sys/kernel/debug/sky2/ethX displays the state of the internal transmit and receive rings. If unsure, say N.
If you have a VIA "Velocity" based network card say Y here. To compile this driver as a module, choose M here. The module will be called via-velocity.
This driver supports Broadcom Tigon3 based gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called tg3. This is recommended.
This driver supports Broadcom NetXtremeII gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called bnx2. This is recommended.
This driver supports offload features of Broadcom NetXtremeII gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called cnic. This is recommended.
This driver supports the Gigabit Ethernet chips present on the Cell Processor-Based Blades from IBM.
This driver supports Tundra TSI108 gigabit Ethernet ports. To compile this driver as a module, choose M here: the module will be called tsi108_eth.
This driver supports the network device on the PS3 game console. This driver has built-in support for Ethernet. To compile this driver as a module, choose M here: the module will be called ps3_gelic.
This option adds the support for the wireless feature of PS3. If you have the wireless-less model of PS3 or have no plan to use wireless feature, disabling this option saves memory. As the driver automatically distinguishes the models, you can safely enable this option even if you have a wireless-less model.
This driver supports the MDIO bus used by the gianfar and UCC drivers.
This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, and MPC86xx family of chips, and the FEC on the 8540.
This driver supports the Gigabit Ethernet mode of the QUICC Engine, which is available on some Freescale SOCs.
This driver supports the gigabit ethernet MACs in the Marvell Discovery PPC/MIPS chipset family (MV643XX) and in the Marvell Orion ARM SoC family. Some boards that use the Discovery chipset are the Momenco Ocelot C and Jaguar ATX and Pegasos II.
This driver supports the Xilinx 10/100/1000 LocalLink TEMAC core used in Xilinx Spartan and Virtex FPGAs
This driver supports QLogic ISP3XXX gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called qla3xxx.
This driver supports the Atheros/Attansic L1 gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1.
This driver supports the Atheros L1E gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1e.
This driver supports the Atheros L1C gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1c.
This driver supports the PCI-Express gigabit ethernet adapters based on JMicron JMC250 chipset. To compile this driver as a module, choose M here. The module will be called jme.
This driver supports the on chip ethernet device on the S6105 xtensa processor. To compile this driver as a module, choose M here. The module will be called s6gmac.
This is a gigabit ethernet driver for EG20T PCH. EG20T PCH is the platform controller hub that is used in Intel's general embedded platform. EG20T PCH has Gigabit Ethernet interface. Using this interface, it is able to access system devices connected to Gigabit Ethernet. This driver enables Gigabit Ethernet function. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ Output Hub), ML7223. ML7223 IOH is for MP(Media Phone) use. ML7223 is companion chip for Intel Atom E6xx series. ML7223 is completely compatible for Intel EG20T PCH.
Say Y here to get to see options for 10 Gigabit Ethernet drivers. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled.
This driver supports Chelsio gigabit and 10-gigabit Ethernet cards. More information about adapter features and performance tuning is in <file:Documentation/networking/cxgb.txt>. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module, choose M here: the module will be called cxgb.
Enables support for Chelsio's gigabit Ethernet PCI cards. If you are using only 10G cards say 'N' here.
This driver supports Chelsio T3-based gigabit and 10Gb Ethernet adapters. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module, choose M here: the module will be called cxgb3.
This driver supports Chelsio T4-based gigabit and 10Gb Ethernet adapters. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module choose M here; the module will be called cxgb4.
This driver supports Chelsio T4-based gigabit and 10Gb Ethernet adapters with PCI-E SR-IOV Virtual Functions. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module choose M here; the module will be called cxgb4vf.
This driver supports the IBM pSeries eHEA ethernet adapter. To compile the driver as a module, choose M here. The module will be called ehea.
This enables the support for the Cisco VIC Ethernet card.
This driver supports Intel(R) 10GbE PCI Express family of adapters. 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> To compile this driver as a module, choose M here. The module will be called ixgbe.
Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses.
Say Y here if you want to use Data Center Bridging (DCB) in the driver. If unsure, say N.
This driver supports Intel(R) 82599 virtual functions. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: <http://support.intel.com/support/network/sb/CS-008441.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/ixgbevf.txt>. To compile this driver as a module, choose M here. The module will be called ixgbevf. MSI-X interrupt support is required for this driver to work correctly.
This driver supports Intel(R) PRO/10GbE family of adapters for PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver instead. 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>. To compile this driver as a module, choose M here. The module will be called ixgb.
This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. More specific information on configuring the driver is in <file:Documentation/networking/s2io.txt>. To compile this driver as a module, choose M here. The module will be called s2io.
This driver supports Exar Corp's X3100 Series 10 GbE PCIe I/O Virtualized Server Adapter. More specific information on configuring the driver is in <file:Documentation/networking/vxge.txt>. To compile this driver as a module, choose M here. The module will be called vxge.
Say Y here if you want to enabling all the debug trace statements in the vxge driver. By default only few debug trace statements are enabled.
This driver supports Myricom Myri-10G Dual Protocol interface in Ethernet mode. If the eeprom on your board is not recent enough, you will need a newer firmware image. You may get this image or more information, at: <http://www.myri.com/scs/download-Myri10GE.html> To compile this driver as a module, choose M here. The module will be called myri10ge.
Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses.
This enables the support for NetXen's Gigabit Ethernet card.
This enables support for cards based upon Sun's Neptune chipset.
This driver supports the on-chip 1/10Gbit Ethernet controller on PA Semi's PWRficient line of chips.
This driver supports Mellanox Technologies ConnectX Ethernet devices.
This option causes debugging code to be compiled into the mlx4_core driver. The output can be turned on via the debug_level module parameter (which can also be set after the driver is loaded through sysfs).
Tehuti Networks 10G Ethernet NIC
This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called bnx2x. This is recommended.
This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet devices.
This driver supports QLogic ISP8XXX 10Gb Ethernet cards. To compile this driver as a module, choose M here: the module will be called qlge.
This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet cards. To compile this driver as a module, choose M here: the module will be called bna. For general information and support, go to the Brocade support website at: <http://support.brocade.com>
This is a standard Linux network device driver for the on-chip Tilera Gigabit Ethernet and XAUI interfaces. To compile this driver as a module, choose M here: the module will be called tile_net.
This driver provides support for Xen paravirtual network devices exported by a Xen network driver domain (often domain 0). The corresponding Linux backend driver is enabled by the CONFIG_XEN_NETDEV_BACKEND option. If you are compiling a kernel for use as Xen guest, you should say Y here. To compile this driver as a module, chose M here: the module will be called xen-netfront.
This driver allows the kernel to act as a Xen network driver domain which exports paravirtual network devices to other Xen domains. These devices can be accessed by any operating system that implements a compatible front end. The corresponding Linux frontend driver is enabled by the CONFIG_XEN_NETDEV_FRONTEND configuration option. The backend driver presents a standard network device endpoint for each paravirtual network device to the driver domain network stack. These can then be bridged or routed etc in order to provide full network connectivity. If you are compiling a kernel to run in a Xen network driver domain (often this is domain 0) you should say Y here. To compile this driver as a module, chose M here: the module will be called xen-netback.
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.
This is support for the DIGITAL series of TURBOchannel (DEFTA), EISA (DEFEA) and PCI (DEFPA) controllers which can connect you to a local FDDI network. To compile this driver as a module, choose M here: the module will be called defxx. If unsure, say N.
This instructs the driver to use EISA or PCI memory-mapped I/O (MMIO) as appropriate instead of programmed I/O ports (PIO). Enabling this gives an improvement in processing time in parts of the driver, but it may cause problems with EISA (DEFEA) adapters. TURBOchannel does not have the concept of I/O ports, so MMIO is always used for these (DEFTA) adapters. If unsure, say N.
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> To compile this driver as a module, choose M here: the module will be called skfp. This is recommended.
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.
Say Y here if this is your PCI HIPPI network card. To compile this driver as a module, choose M here: the module will be called rrunner. If unsure, say N.
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.
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. To compile this driver as a module, choose M here. The module will be called plip. If unsure, say Y or M, in case you buy a laptop later.
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. 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. To compile this driver as a module, choose M here. The module will be called ppp_generic.
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.
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-dialed 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.
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. To compile this driver as a module, choose M here. If unsure, say Y.
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. To compile this driver as a module, choose M here.
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. To compile this driver as a module, choose M here.
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.
Support for the MPPE Encryption protocol, as employed by the Microsoft Point-to-Point Tunneling Protocol. See http://pptpclient.sourceforge.net/ for information on configuring PPTP clients and servers to utilize this method.
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").
Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) This driver requires pppd plugin to work in client mode or modified pptpd (poptop) to work in server mode. See http://accel-pptp.sourceforge.net/ for information how to utilize this module.
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.
Support for PPP-over-L2TP socket family. L2TP is a protocol used by ISPs and enterprises to tunnel PPP traffic over UDP tunnels. L2TP is replacing PPTP for VPN uses.
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. To compile this driver as a module, choose M here. The module will be called slip.
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.
This option enables Van Jacobsen serial line header compression routines.
Adds additional capabilities to the SLIP driver to support the RELCOM line fill and keepalive monitoring. Ideal on poor quality analogue lines.
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.
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".
If you want to log kernel messages over the network, enable this. See <file:Documentation/networking/netconsole.txt> for details.
This option enables the ability to dynamically reconfigure target parameters (interface, IP addresses, port numbers, MAC addresses) at runtime through a userspace interface exported using configfs. See <file:Documentation/networking/netconsole.txt> for details.
This is the virtual network driver for virtio. It can be used with lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
This driver supports VMware's vmxnet3 virtual ethernet NIC. To compile this driver as a module, choose M here: the module will be called vmxnet3.