User:ZyMOS/Howto configure the linux kernel/drivers/net

User:ZyMOS/Howto configure the linux kernel / drivers / net


 * Network device configuration
 * Network device configuration

Network device support

 * Option: NETDEVICES
 * Kernel Versions: 2.6.15.6 ...
 * depends on NET
 * (on/off) "Network device support"
 * 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 .
 * If unsure, say Y.


 * All the following symbols are dependent on NETDEVICES - do not repeat
 * that for each of the symbols.

NETDEVICES


 * Option: DUMMY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Dummy net driver support"
 * 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 .
 * 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.


 * Option: BONDING
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Bonding driver support"
 * depends on INET
 * 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 perfomance and high availability operation.
 * Refer to  for more information.
 * To compile this driver as a module, choose M here: the module will be called bonding.


 * Option: EQUALIZER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "EQL (serial line load balancing) support"
 * 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 . You may also want to read section 6.2 of the NET-3-HOWTO, available from .
 * To compile this driver as a module, choose M here: the module will be called eql. If unsure, say N.


 * Option: TUN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Universal TUN/TAP device driver support"
 * select CRC32
 * 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  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.


 * Option: NET_SB1000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "General Instruments Surfboard 1000"
 * depends on PNP
 * 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  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:
 *   
 * If you don't have this card, of course say N.


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/arcnet


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/phy


 * Ethernet
 * Ethernet

Ethernet (10 or 100Mbit)

 * depends on !UML


 * Option: NET_ETHERNET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Ethernet (10 or 100Mbit)"
 * 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 . 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.


 * Option: MII
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Generic Media Independent Interface device support"
 * depends on NET_ETHERNET
 * 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.


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/arm


 * Option: MACE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MACE (Power Mac ethernet) support"
 * depends on NET_ETHERNET && PPC_PMAC && PPC32
 * select CRC32
 * 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.


 * Option: MACE_AAUI_PORT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use AAUI port instead of TP by default"
 * depends on 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.


 * Option: BMAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "BMAC (G3 ethernet) support"
 * depends on NET_ETHERNET && PPC_PMAC && PPC32
 * select CRC32
 * 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.


 * Option: OAKNET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "National DP83902AV (Oak ethernet) support"
 * depends on NET_ETHERNET && PPC && BROKEN
 * select CRC32
 * Say Y if your machine has this type of Ethernet network card.
 * To compile this driver as a module, choose M here: the module will be called oaknet.


 * Option: ARIADNE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Ariadne support"
 * depends on NET_ETHERNET && ZORRO
 * 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.


 * Option: A2065
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "A2065 support"
 * depends on NET_ETHERNET && ZORRO
 * select CRC32
 * 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.


 * Option: HYDRA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Hydra support"
 * depends on NET_ETHERNET && ZORRO
 * select CRC32
 * 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.


 * Option: ZORRO8390
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Zorro NS8390-based Ethernet support"
 * depends on NET_ETHERNET && ZORRO
 * select CRC32
 * 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.


 * Option: APNE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PCMCIA NE2000 support"
 * depends on NET_ETHERNET && AMIGA_PCMCIA
 * select CRC32
 * 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.


 * Option: APOLLO_ELPLUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Apollo 3c505 support"
 * depends on NET_ETHERNET && APOLLO
 * 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).


 * Option: MAC8390
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Macintosh NS 8390 based ethernet cards"
 * depends on NET_ETHERNET && MAC
 * select CRC32
 * 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 .


 * Option: MAC89x0
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Macintosh CS89x0 based ethernet cards"
 * depends on NET_ETHERNET && MAC && BROKEN
 * 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 .
 * To compile this driver as a module, choose M here and read . This module will be called mac89x0.


 * Option: MACSONIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
 * depends on NET_ETHERNET && MAC
 * 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 .
 * To compile this driver as a module, choose M here and read . This module will be called macsonic.


 * Option: MACMACE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)"
 * depends on NET_ETHERNET && MAC && EXPERIMENTAL
 * select CRC32
 * 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>.


 * Option: MVME147_NET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MVME147 (Lance) Ethernet support"
 * depends on NET_ETHERNET && MVME147
 * select CRC32
 * 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.


 * Option: MVME16x_NET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MVME16x Ethernet support"
 * depends on NET_ETHERNET && MVME16x
 * 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.


 * Option: BVME6000_NET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "BVME6000 Ethernet support"
 * depends on NET_ETHERNET && BVME6000
 * 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.


 * Option: ATARILANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Atari Lance support"
 * depends on NET_ETHERNET && ATARI
 * 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).


 * Option: ATARI_BIONET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "BioNet-100 support"
 * depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
 * 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 :-(


 * Option: ATARI_PAMSNET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PAMsNet support"
 * depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN
 * 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 :-(


 * Option: SUN3LANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun3/Sun3x on-board LANCE support"
 * depends on NET_ETHERNET && (SUN3 || SUN3X)
 * 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.


 * Option: SUN3_82586
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Sun3 on-board Intel 82586 support"
 * depends on NET_ETHERNET && SUN3
 * 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.


 * Option: HPLANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "HP on-board LANCE support"
 * depends on NET_ETHERNET && DIO
 * select CRC32
 * If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here.


 * Option: LASI_82596
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Lasi ethernet"
 * depends on NET_ETHERNET && PARISC && GSC_LASI
 * Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines.


 * Option: MIPS_JAZZ_SONIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MIPS JAZZ onboard SONIC Ethernet support"
 * depends on NET_ETHERNET && MACH_JAZZ
 * This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems.


 * Option: MIPS_GT96100ETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "MIPS GT96100 Ethernet support"
 * depends on NET_ETHERNET && MIPS_GT96100
 * Say Y here to support the Ethernet subsystem on your GT96100 card.


 * Option: MIPS_AU1X00_ENET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "MIPS AU1000 Ethernet support"
 * depends on NET_ETHERNET && SOC_AU1X00
 * select CRC32
 * If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N.


 * Option: NET_SB1250_MAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SB1250 Ethernet support"
 * depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC


 * Option: SGI_IOC3_ETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SGI IOC3 Ethernet"
 * depends on NET_ETHERNET && PCI && SGI_IP27
 * select CRC32
 * select MII
 * 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>.


 * Option: SGI_IOC3_ETH_HW_RX_CSUM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Receive hardware checksums"
 * depends on SGI_IOC3_ETH && INET
 * default y
 * The SGI IOC3 network adapter supports TCP and UDP checksums in hardware to offload processing of these checksums from the CPU. At the moment only acceleration of IPv4 is supported.  This option enables offloading for checksums on receive.  If unsure, say Y.


 * Option: SGI_IOC3_ETH_HW_TX_CSUM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Transmit hardware checksums"
 * depends on SGI_IOC3_ETH && INET
 * default y
 * The SGI IOC3 network adapter supports TCP and UDP checksums in hardware to offload processing of these checksums from the CPU. At the moment only acceleration of IPv4 is supported.  This option enables offloading for checksums on transmit.  If unsure, say Y.


 * Option: MIPS_SIM_NET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MIPS simulator Network device (EXPERIMENTAL)"
 * depends on NETDEVICES && MIPS_SIM && EXPERIMENTAL
 * 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.


 * Option: SGI_O2MACE_ETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SGI O2 MACE Fast Ethernet support"
 * depends on NET_ETHERNET && SGI_IP32=y


 * Option: STNIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "National DP83902AV  support"
 * depends on NET_ETHERNET && SUPERH
 * select CRC32
 * 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.


 * Option: SUNLANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun LANCE support"
 * depends on NET_ETHERNET && SBUS
 * select CRC32
 * 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.


 * Option: HAPPYMEAL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun Happy Meal 10/100baseT support"
 * depends on NET_ETHERNET && (SBUS || PCI)
 * select CRC32
 * 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.


 * Option: SUNBMAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
 * depends on NET_ETHERNET && SBUS && EXPERIMENTAL
 * select CRC32
 * 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.


 * Option: SUNQE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun QuadEthernet support"
 * depends on NET_ETHERNET && SBUS
 * select CRC32
 * 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.


 * Option: SUNGEM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun GEM support"
 * depends on NET_ETHERNET && PCI
 * select CRC32
 * 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>.


 * Option: CASSINI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sun Cassini support"
 * depends on NET_ETHERNET && PCI
 * select CRC32
 * 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>


 * Option: NET_VENDOR_3COM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "3COM cards"
 * depends on NET_ETHERNET && (ISA || EISA || MCA || PCI)
 * 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.


 * Option: EL1
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c501 \"EtherLink\" support"
 * depends on NET_VENDOR_3COM && ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c501.


 * Option: EL2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c503 \"EtherLink II\" support"
 * depends on NET_VENDOR_3COM && ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c503.


 * Option: ELPLUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c505 \"EtherLink Plus\" support"
 * depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c505.


 * Option: EL16
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
 * depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c507.


 * Option: EL3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
 * depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c509.


 * Option: 3C515
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c515 ISA \"Fast EtherLink\""
 * depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c515.


 * Option: ELMC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c523 \"EtherLink/MC\" support"
 * depends on NET_VENDOR_3COM && MCA_LEGACY
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c523.


 * Option: ELMC_II
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
 * depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called 3c527.


 * Option: VORTEX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
 * depends on NET_VENDOR_3COM && (PCI || EISA)
 * select MII
 * 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 and read <file:Documentation/networking/net-modules.txt>.


 * Option: TYPHOON
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "3cr990 series \"Typhoon\" support"
 * depends on NET_VENDOR_3COM && PCI
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called typhoon.


 * Option: LANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "AMD LANCE and PCnet (AT1500 and NE2100) support"
 * depends on NET_ETHERNET && ISA && ISA_DMA_API
 * 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.


 * Option: NET_VENDOR_SMC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Western Digital/SMC cards"
 * depends on NET_ETHERNET && (ISA || MCA || EISA || MAC)
 * 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.


 * Option: WD80x3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "WD80*3 support"
 * depends on NET_VENDOR_SMC && ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called wd.


 * Option: ULTRAMCA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC Ultra MCA support"
 * depends on NET_VENDOR_SMC && MCA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called smc-mca.


 * Option: ULTRA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC Ultra support"
 * depends on NET_VENDOR_SMC && ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called smc-ultra.


 * Option: ULTRA32
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC Ultra32 EISA support"
 * depends on NET_VENDOR_SMC && EISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called smc-ultra32.


 * Option: SMC91X
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC 91C9x/91C1xxx support"
 * select CRC32
 * select MII
 * depends on NET_ETHERNET && (ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00)
 * 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.linuxdoc.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/modules.txt> as well as <file:Documentation/networking/net-modules.txt>.


 * Option: SMC9194
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC 9194 support"
 * depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called smc9194.


 * Option: DM9000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "DM9000 support"
 * depends on ARM && NET_ETHERNET
 * select CRC32
 * select MII
 * Support for DM9000 chipset.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called dm9000.


 * Option: NET_VENDOR_RACAL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Racal-Interlan (Micom) NI cards"
 * depends on NET_ETHERNET && ISA
 * 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.


 * Option: NI5010
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NI5010 support (EXPERIMENTAL)"
 * depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ni5010.


 * Option: NI52
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NI5210 support"
 * depends on NET_VENDOR_RACAL && ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ni52.


 * Option: NI65
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NI6510 support"
 * depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ni65.


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/tulip


 * Option: AT1700
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "AT1700/1720 support (EXPERIMENTAL)"
 * depends on NET_ETHERNET && (ISA || MCA_LEGACY) && EXPERIMENTAL
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called at1700.


 * Option: DEPCA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
 * depends on NET_ETHERNET && (ISA || EISA || MCA)
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called depca.


 * Option: HP100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
 * depends on NET_ETHERNET && (ISA || EISA || 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>.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called hp100.


 * Option: NET_ISA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Other ISA cards"
 * depends on NET_ETHERNET && ISA
 * 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.


 * Option: E2100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Cabletron E21xx support"
 * depends on NET_ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called e2100.


 * Option: EWRK3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "EtherWORKS 3 (DE203, DE204, DE205) support"
 * depends on NET_ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ewrk3.


 * Option: EEXPRESS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "EtherExpress 16 support"
 * depends on NET_ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called eexpress.


 * Option: EEXPRESS_PRO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "EtherExpressPro support/EtherExpress 10 (i82595) support"
 * depends on NET_ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called eepro.


 * Option: HPLAN_PLUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "HP PCLAN+ (27247B and 27252A) support"
 * depends on NET_ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called hp-plus.


 * Option: HPLAN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "HP PCLAN (27245 and other 27xxx series) support"
 * depends on NET_ISA
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called hp.


 * Option: LP486E
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "LP486E on board Ethernet"
 * depends on NET_ISA
 * 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.


 * Option: ETH16I
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "ICL EtherTeam 16i/32 support"
 * depends on NET_ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called eth16i.


 * Option: NE2000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NE2000/NE1000 support"
 * depends on NET_ISA || (Q40 && m) || M32R
 * select CRC32
 * 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.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called ne.


 * Option: ZNET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Zenith Z-Note support (EXPERIMENTAL)"
 * depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
 * 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>.


 * Option: SEEQ8005
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SEEQ8005 support (EXPERIMENTAL)"
 * depends on NET_ISA && EXPERIMENTAL
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called seeq8005.


 * Option: SKMC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SKnet MCA support"
 * depends on NET_ETHERNET && MCA && BROKEN
 * 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.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called sk_mca.


 * Option: NE2_MCA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NE/2 (ne2000 MCA version) support"
 * depends on NET_ETHERNET && MCA_LEGACY
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ne2.


 * Option: IBMLANA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "IBM LAN Adapter/A support"
 * depends on NET_ETHERNET && MCA && MCA_LEGACY
 * 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 and read <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.


 * Option: IBMVETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "IBM LAN Virtual Ethernet support"
 * depends on NET_ETHERNET && PPC_PSERIES
 * This driver supports virtual ethernet adapters on newer IBM iSeries and pSeries systems.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called ibmveth.


 * Option: IBM_EMAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PowerPC 4xx on-chip Ethernet support"
 * depends on 4xx
 * This driver supports the PowerPC 4xx EMAC family of on-chip        Ethernet controllers.

"Number of receive buffers"
 * Option: IBM_EMAC_RXB
 * Kernel Versions: 2.6.15.6 ...
 * depends on IBM_EMAC
 * default "128"

"Number of transmit buffers"
 * Option: IBM_EMAC_TXB
 * Kernel Versions: 2.6.15.6 ...
 * depends on IBM_EMAC
 * default "64"

"MAL NAPI polling weight"
 * Option: IBM_EMAC_POLL_WEIGHT
 * Kernel Versions: 2.6.15.6 ...
 * depends on IBM_EMAC
 * default "32"

"RX skb copy threshold (bytes)"
 * Option: IBM_EMAC_RX_COPY_THRESHOLD
 * Kernel Versions: 2.6.15.6 ...
 * depends on IBM_EMAC
 * default "256"

"Additional RX skb headroom (bytes)"
 * Option: IBM_EMAC_RX_SKB_HEADROOM
 * Kernel Versions: 2.6.15.6 ...
 * depends on IBM_EMAC
 * default "0"
 * Additional receive skb headroom. Note, that driver will always reserve at least 2 bytes to make IP header aligned, so usualy there is no need to add any additional headroom. If unsure, set to 0.


 * Option: IBM_EMAC_PHY_RX_CLK_FIX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PHY Rx clock workaround"
 * depends on IBM_EMAC && (405EP || 440GX || 440EP || 440GR)
 * Enable this if EMAC attached to a PHY which doesn't generate RX clock if there is no link, if this is the case, you will see "TX disable timeout" or "RX disable timeout" in the system log.  If unsure, say N.


 * Option: IBM_EMAC_DEBUG
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Debugging"
 * depends on IBM_EMAC
 * default n


 * Option: IBM_EMAC_ZMII
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on IBM_EMAC && (NP405H || NP405L || 44x)
 * default y


 * Option: IBM_EMAC_RGMII
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on IBM_EMAC && 440GX
 * default y


 * Option: IBM_EMAC_TAH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on IBM_EMAC && 440GX
 * default y


 * Option: NET_PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "EISA, VLB, PCI and on board controllers"
 * depends on NET_ETHERNET && (ISA || EISA || PCI)
 * 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.


 * Option: PCNET32
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "AMD PCnet32 PCI support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called pcnet32.


 * Option: AMD8111_ETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "AMD 8111 (new PCI lance) support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called amd8111e.


 * Option: AMD8111E_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Enable NAPI support"
 * depends on AMD8111_ETH
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.


 * Option: ADAPTEC_STARFIRE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Adaptec Starfire/DuraLAN support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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.


 * Option: ADAPTEC_STARFIRE_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 * depends on ADAPTEC_STARFIRE && EXPERIMENTAL
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.


 * Option: AC3200
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
 * depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ac3200.


 * Option: APRICOT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Apricot Xen-II on board Ethernet"
 * depends on NET_PCI && ISA
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called apricot.


 * Option: B44
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Broadcom 4400 ethernet support (EXPERIMENTAL)"
 * depends on NET_PCI && PCI && EXPERIMENTAL
 * select MII
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called b44.


 * Option: FORCEDETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
 * depends on NET_PCI && PCI && EXPERIMENTAL
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called forcedeth.


 * Option: CS89x0
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "CS89x0 support"
 * depends on (NET_PCI && (ISA || ARCH_IXDP2X01)) || ARCH_PNX0105
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called cs89x.


 * Option: TC35815
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "TOSHIBA TC35815 Ethernet support"
 * depends on NET_PCI && PCI && TOSHIBA_JMR3927


 * Option: DGRS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Digi Intl. RightSwitch SE-X support"
 * depends on NET_PCI && (PCI || EISA)
 * 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>.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called dgrs.


 * Option: EEPRO100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "EtherExpressPro/100 support (eepro100, original Becker driver)"
 * depends on NET_PCI && PCI
 * select MII
 * 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>.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called eepro100.


 * Option: E100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Intel(R) PRO/100+ support"
 * depends on NET_PCI && PCI
 * select MII
 * 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://appsr.intel.com/scripts-df/support_intel.asp>
 * More specific information on configuring the driver is in <file:Documentation/networking/e100.txt>.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called e100.


 * Option: LNE390
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
 * depends on NET_PCI && EISA && EXPERIMENTAL
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called lne390.


 * Option: FEALNX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Myson MTD-8xx PCI Ethernet support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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/>.


 * Option: NATSEMI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "National Semiconductor DP8381x series PCI Ethernet support"
 * depends on NET_PCI && PCI
 * select CRC32
 * 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>.


 * Option: NE2K_PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PCI NE2000 and clones support (see help)"
 * depends on NET_PCI && PCI
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ne2k-pci.


 * Option: NE3210
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
 * depends on NET_PCI && EISA && EXPERIMENTAL
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ne3210.


 * Option: ES3210
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
 * depends on NET_PCI && EISA && EXPERIMENTAL
 * select CRC32
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called es3210.


 * Option: 8139CP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
 * depends on NET_PCI && PCI && EXPERIMENTAL
 * select CRC32
 * select MII
 * 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.


 * Option: 8139TOO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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.


 * Option: 8139TOO_PIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use PIO instead of MMIO"
 * default y
 * depends on 8139TOO
 * 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.


 * Option: 8139TOO_TUNE_TWISTER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
 * depends on 8139TOO
 * 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.


 * Option: 8139TOO_8129
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for older RTL-8129/8130 boards"
 * depends on 8139TOO
 * 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.


 * Option: 8139_OLD_RX_RESET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use older RX-reset method"
 * depends on 8139TOO
 * 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.


 * Option: SIS900
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SiS 900/7016 PCI Fast Ethernet Adapter support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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.
 * To compile this driver as a module, choose M here: the module will be called sis900. This is recommended.


 * Option: EPIC100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SMC EtherPower II"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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>.


 * Option: SUNDANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Sundance Alta support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * This driver is for the Sundance "Alta" chip. More specific information and updates are available from <http://www.scyld.com/network/sundance.html>.


 * Option: SUNDANCE_MMIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use MMIO instead of PIO"
 * depends on SUNDANCE
 * 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.


 * Option: TLAN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "TI ThunderLAN support"
 * depends on NET_PCI && (PCI || EISA) && !64BIT
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called tlan.
 * Please email feedback to <torben.mathiasen@compaq.com>.


 * Option: VIA_RHINE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "VIA Rhine support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select MII
 * 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.


 * Option: VIA_RHINE_MMIO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use MMIO instead of PIO"
 * depends on 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.


 * Option: LAN_SAA9730
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
 * depends on NET_PCI && EXPERIMENTAL && MIPS
 * 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>.


 * Option: NET_POCKET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Pocket and portable adapters"
 * depends on NET_ETHERNET && PARPORT
 * 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.


 * Option: ATP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "AT-LAN-TEC/RealTek pocket adapter support"
 * depends on NET_POCKET && PARPORT && X86
 * select CRC32
 * 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.


 * Option: DE600
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "D-Link DE600 pocket adapter support"
 * depends on NET_POCKET && PARPORT
 * 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.


 * Option: DE620
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "D-Link DE620 pocket adapter support"
 * depends on NET_POCKET && PARPORT
 * 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.


 * Option: SGISEEQ
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SGI Seeq ethernet controller support"
 * depends on NET_ETHERNET && SGI_IP22
 * Say Y here if you have an Seeq based Ethernet network card. This is used in many Silicon Graphics machines.


 * Option: DECLANCE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "DEC LANCE ethernet controller support"
 * depends on NET_ETHERNET && MACH_DECSTATION
 * select CRC32
 * 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.)


 * Option: 68360_ENET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Motorola 68360 ethernet controller"
 * depends on M68360
 * Say Y here if you want to use the built-in ethernet controller of the Motorola 68360 processor.


 * Option: FEC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "FEC ethernet controller (of ColdFire CPUs)"
 * depends on M523x || M527x || M5272 || M528x
 * Say Y here if you want to use the built-in 10/100 Fast ethernet controller on some Motorola ColdFire processors.


 * Option: FEC2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Second FEC ethernet controller (on some ColdFire CPUs)"
 * depends on FEC
 * Say Y here if you want to use the second built-in 10/100 Fast ethernet controller on some Motorola ColdFire processors.


 * Option: NE_H8300
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "NE2000 compatible support for H8/300"
 * depends on H8300 && NET_ETHERNET
 * Say Y here if you want to use the NE2000 compatible controller on the Renesas H8/300 processor.


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/fec_8xx


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/fs_enet


 * Gigabit Ethernet
 * Gigabit Ethernet

Ethernet (1000 Mbit)

 * depends on !UML


 * Option: ACENIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
 * depends on PCI
 * 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.


 * Option: ACENIC_OMIT_TIGON_I
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Omit support for old Tigon I based AceNICs"
 * depends on 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.


 * Option: DL2K
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "D-Link DL2000-based Gigabit Ethernet support"
 * depends on PCI
 * select CRC32
 * 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.
 * To compile this driver as a module, choose M here: the module will be called dl2k.


 * Option: E1000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Intel(R) PRO/1000 Gigabit Ethernet support"
 * depends on PCI
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called e1000.


 * Option: E1000_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use Rx Polling (NAPI)"
 * depends on E1000
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.


 * Option: MYRI_SBUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MyriCOM Gigabit Ethernet support"
 * depends on SBUS
 * 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.


 * Option: NS83820
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "National Semiconduct DP83820 support"
 * depends on PCI
 * 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.


 * Option: HAMACHI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Packet Engines Hamachi GNIC-II support"
 * depends on PCI
 * select MII
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called hamachi.


 * Option: YELLOWFIN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
 * depends on PCI && EXPERIMENTAL
 * select CRC32
 * 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.


 * Option: R8169
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Realtek 8169 gigabit ethernet support"
 * depends on PCI
 * select CRC32
 * 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.


 * Option: R8169_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)"
 * depends on R8169 && EXPERIMENTAL
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.


 * Option: R8169_VLAN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "VLAN support"
 * depends on R8169 && VLAN_8021Q
 * Say Y here for the r8169 driver to support the functions required by the kernel 802.1Q code. If in doubt, say Y.


 * Option: SIS190
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SiS190/SiS191 gigabit ethernet support"
 * depends on PCI
 * select CRC32
 * select MII
 * 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.


 * Option: SKGE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "New SysKonnect GigaEthernet support (EXPERIMENTAL)"
 * depends on PCI && EXPERIMENTAL
 * select CRC32
 * 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.


 * Option: SK98LIN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Marvell Yukon Chipset / SysKonnect SK-98xx Support"
 * depends on PCI
 * Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx compliant Gigabit Ethernet Adapter. The following adapters are supported by this driver:  - 3Com 3C940 Gigabit LOM Ethernet Adapter   - 3Com 3C941 Gigabit LOM Ethernet Adapter   - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter   - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter   - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter   - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter   - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter   - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter   - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter   - Allied Telesyn AT-2971T Gigabit Ethernet Adapter   - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45   - DGE-530T Gigabit Ethernet Adapter   - EG1032 v2 Instant Gigabit Network Adapter   - EG1064 v2 Instant Gigabit Network Adapter   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)   - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)   - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel)   - Marvell RDK-8001 Adapter   - Marvell RDK-8002 Adapter   - Marvell RDK-8003 Adapter   - Marvell RDK-8004 Adapter   - Marvell RDK-8006 Adapter   - Marvell RDK-8007 Adapter   - Marvell RDK-8008 Adapter   - Marvell RDK-8009 Adapter   - Marvell RDK-8010 Adapter   - Marvell RDK-8011 Adapter   - Marvell RDK-8012 Adapter   - Marvell RDK-8052 Adapter   - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)   - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)   - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)   - SK-9521 10/100/1000Base-T Adapter   - SK-9521 V2.0 10/100/1000Base-T Adapter   - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)   - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter   - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)   - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)   - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter   - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)   - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)   - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter   - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)   - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter   - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)   - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter   - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)   - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)   - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter   - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)   - SMC EZ Card 1000 (SMC9452TXV.2)  The adapters support Jumbo Frames. The dual link adapters support link-failover and dual port features. Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support  the scatter-gather functionality with sendfile. Please refer to  <file:Documentation/networking/sk98lin.txt> for more 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/kbuild/modules.txt>. The module will be called sk98lin. This is recommended.


 * Option: VIA_VELOCITY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "VIA Velocity support"
 * depends on NET_PCI && PCI
 * select CRC32
 * select CRC_CCITT
 * select MII
 * 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.


 * Option: TIGON3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Broadcom Tigon3 support"
 * depends on PCI
 * 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.


 * Option: BNX2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Broadcom NetXtremeII support"
 * depends on PCI
 * 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.


 * Option: SPIDER_NET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Spider Gigabit Ethernet driver"
 * depends on PCI && PPC_BPA
 * This driver supports the Gigabit Ethernet chips present on the Cell Processor-Based Blades from IBM.


 * Option: GIANFAR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Gianfar Ethernet"
 * depends on 85xx || 83xx
 * select PHYLIB
 * This driver supports the Gigabit TSEC on the MPC85xx family of chips, and the FEC on the 8540


 * Option: GFAR_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "NAPI Support"
 * depends on GIANFAR


 * Option: MV643XX_ETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "MV-643XX Ethernet support"
 * depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || MOMENCO_OCELOT_3 || PPC_MULTIPLATFORM
 * This driver supports the gigabit Ethernet on the Marvell MV643XX chipset which is used in the Momenco Ocelot C and Jaguar ATX and Pegasos II, amongst other PPC and MIPS boards.


 * Option: MV643XX_ETH_0
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "MV-643XX Port 0"
 * depends on MV643XX_ETH
 * This enables support for Port 0 of the Marvell MV643XX Gigabit Ethernet.


 * Option: MV643XX_ETH_1
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "MV-643XX Port 1"
 * depends on MV643XX_ETH
 * This enables support for Port 1 of the Marvell MV643XX Gigabit Ethernet.


 * Option: MV643XX_ETH_2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "MV-643XX Port 2"
 * depends on MV643XX_ETH
 * This enables support for Port 2 of the Marvell MV643XX Gigabit Ethernet.


 * 10 Gigabit Ethernet
 * 10 Gigabit Ethernet

Ethernet (10000 Mbit)

 * depends on !UML


 * Option: CHELSIO_T1
 * Kernel Versions: 2.6.15.6 ...      tristate "Chelsio 10Gb Ethernet support"       depends on PCI       help         This driver supports Chelsio N110 and N210 models 10Gb 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.htm>.
 * Please send feedback to <linux-bugs@chelsio.com>.
 * To compile this driver as a module, choose M here: the module        will be called cxgb.


 * Option: IXGB
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Intel(R) PRO/10GbE support"
 * depends on PCI
 * This driver supports Intel(R) PRO/10GbE 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/ixgb.txt>.
 * To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. The module will be called ixgb.


 * Option: IXGB_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 * depends on IXGB && EXPERIMENTAL
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.


 * Option: S2IO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "S2IO 10Gbe XFrame NIC"
 * depends on PCI
 * This driver supports the 10Gbe XFrame NIC of S2IO. More specific information on configuring the driver is in  <file:Documentation/networking/s2io.txt>.


 * Option: S2IO_NAPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 * depends on S2IO && EXPERIMENTAL
 * 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.
 * See <file:Documentation/networking/NAPI_HOWTO.txt> for more information.
 * If in doubt, say N.

!UML


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/tokenring


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/wireless


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/pcmcia


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/net/wan


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/atm


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/s390/net


 * Option: ISERIES_VETH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "iSeries Virtual Ethernet driver support"
 * depends on PPC_ISERIES


 * Option: RIONET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "RapidIO Ethernet over messaging driver support"
 * depends on NETDEVICES && RAPIDIO

"Number of outbound queue entries"
 * Option: RIONET_TX_SIZE
 * Kernel Versions: 2.6.15.6 ...
 * depends on RIONET
 * default "128"

"Number of inbound queue entries"
 * Option: RIONET_RX_SIZE
 * Kernel Versions: 2.6.15.6 ...
 * depends on RIONET
 * default "128"


 * Option: FDDI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "FDDI driver support"
 * depends on (PCI || EISA)
 * 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.


 * Option: DEFXX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Digital DEFEA and DEFPA adapter support"
 * depends on FDDI && (PCI || EISA)
 * This is support for the DIGITAL series of EISA (DEFEA) and PCI (DEFPA) controllers which can connect you to a local FDDI network.


 * Option: SKFP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SysKonnect FDDI PCI support"
 * depends on FDDI && PCI
 * 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.


 * Option: HIPPI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "HIPPI driver support (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && INET && PCI
 * 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.


 * Option: ROADRUNNER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
 * depends on HIPPI && PCI
 * 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.


 * Option: ROADRUNNER_LARGE_RINGS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Use large TX/RX rings (EXPERIMENTAL)"
 * depends on ROADRUNNER
 * 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.


 * Option: PLIP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PLIP (parallel port) support"
 * depends on PARPORT
 * 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 and read <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.


 * Option: PPP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP (point-to-point protocol) support"
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called ppp_generic.


 * Option: PPP_MULTILINK
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PPP multilink support (EXPERIMENTAL)"
 * depends on PPP && EXPERIMENTAL
 * 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.


 * Option: PPP_FILTER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PPP filtering"
 * depends on PPP
 * 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.


 * Option: PPP_ASYNC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP support for async serial ports"
 * depends on PPP
 * select CRC_CCITT
 * 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.


 * Option: PPP_SYNC_TTY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP support for sync tty ports"
 * depends on PPP
 * 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.


 * Option: PPP_DEFLATE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP Deflate compression"
 * depends on PPP
 * select ZLIB_INFLATE
 * select ZLIB_DEFLATE
 * 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.


 * Option: PPP_BSDCOMP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP BSD-Compress compression"
 * depends on PPP
 * 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.

http://pptpclient.sourceforge.net/ for information onconfiguring PPTP clients and servers to utilize this method.
 * Option: PPP_MPPE
 * Kernel Versions: 2.6.15.6 ...     tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"      depends on PPP && EXPERIMENTAL      select CRYPTO      select CRYPTO_SHA1      select CRYPTO_ARC4      ---help---        Support for the MPPE Encryption protocol, as employed by theMicrosoft Point-to-Point Tunneling Protocol.


 * Option: PPPOE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP over Ethernet (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && PPP
 * 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").


 * Option: PPPOATM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "PPP over ATM"
 * depends on ATM && PPP
 * 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.


 * Option: SLIP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "SLIP (serial line) support"
 * 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 and read <file:Documentation/networking/net-modules.txt>. The module will be called slip.


 * Option: SLIP_COMPRESSED
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "CSLIP compressed headers"
 * depends on 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.


 * Option: SLIP_SMART
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Keepalive and linefill"
 * depends on SLIP
 * Adds additional capabilities to the SLIP driver to support the RELCOM line fill and keepalive monitoring. Ideal on poor quality analogue lines.


 * Option: SLIP_MODE_SLIP6
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Six bit SLIP encapsulation"
 * depends on SLIP
 * 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.


 * Option: NET_FC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Fibre Channel driver support"
 * depends on SCSI && PCI
 * 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".


 * Option: SHAPER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Traffic Shaper (EXPERIMENTAL)"
 * depends on EXPERIMENTAL
 * 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.
 * To compile this driver as a module, choose M here: the module will be called shaper. If unsure, say N.

you want to log kernel messages over the network, enable this. <file:Documentation/networking/netconsole.txt> for details.
 * Option: NETCONSOLE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Network console logging support (EXPERIMENTAL)"
 * depends on EXPERIMENTAL


 * 1) NETDEVICES

_bool NETCONSOLE
 * Option: NETPOLL
 * Kernel Versions: 2.6.15.6 ...


 * Option: NETPOLL_RX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Netpoll support for trapping incoming packets"
 * default n
 * depends on NETPOLL


 * Option: NETPOLL_TRAP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Netpoll traffic trapping"
 * default n
 * depends on NETPOLL

_bool NETPOLL
 * Option: NET_POLL_CONTROLLER
 * Kernel Versions: 2.6.15.6 ...