## Network device configuration# menu "Network device support" depends on NET config NETDEVICES default y if UML bool "Network device support" ---help--- You can say N here if you don't intend to connect your Linux box to any other computer at all. You'll have to say Y if your computer contains a network card that you want to use under Linux. If you are going to run SLIP or PPP over telephone line or null modem cable you need say Y here. Connecting two machines with parallel ports using PLIP needs this, as well as AX.25/KISS for sending Internet traffic over amateur radio links. See also "The Linux Network Administrator's Guide" by Olaf Kirch and Terry Dawson. Available at <http://www.tldp.org/guides.html>. If unsure, say Y. config IFB tristate "Intermediate Functional Block support" depends on NET_CLS_ACT ---help--- This is an intermidiate driver that allows sharing of resources. To compile this driver as a module, choose M here: the module will be called ifb. If you want to use more than one ifb device at a time, you need to compile this driver as a module. Instead of 'ifb', the devices will then be called 'ifb0', 'ifb1' etc. Look at the iproute2 documentation directory for usage etc config DUMMY tristate "Dummy net driver support" ---help--- This is essentially a bit-bucket device (i.e. traffic you send to this device is consigned into oblivion) with a configurable IP address. It is most commonly used in order to make your currently inactive SLIP address seem like a real address for local programs. If you use SLIP or PPP, you might want to say Y here. Since this thing often comes in handy, the default is Y. It won't enlarge your kernel either. What a deal. Read about it in the Network Administrator's Guide, available from <http://www.tldp.org/docs.html#guide>. 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. config BONDING tristate "Bonding driver support" depends on INET ---help--- Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet Channels together. This is called 'Etherchannel' by Cisco, 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. The driver supports multiple bonding modes to allow for both high performance and high availability operation. Refer to <file:Documentation/networking/bonding.txt> for more information. To compile this driver as a module, choose M here: the module will be called bonding. config EQUALIZER tristate "EQL (serial line load balancing) support" ---help--- If you have two serial connections to some other computer (this usually requires two modems and two telephone lines) and you use SLIP (the protocol for sending Internet traffic over telephone lines) or PPP (a better SLIP) on them, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you want this and read <file:Documentation/networking/eql.txt>. You may also want to read section 6.2 of the NET-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here: the module will be called eql. If unsure, say N. config TUN tristate "Universal TUN/TAP device driver support" select CRC32 ---help--- TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a program opens /dev/net/tun, driver creates and registers corresponding net device tunX or tapX. After a program closed above devices, driver will automatically delete tunXX or tapXX device and all routes corresponding to it. Please read <file:Documentation/networking/tuntap.txt> for more information. 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. config NET_SB1000 tristate "General Instruments Surfboard 1000" depends on PNP ---help--- This is a driver for the General Instrument (also known as NextLevel) SURFboard 1000 internal cable modem. This is an ISA card which is used by a number of cable TV companies to provide cable modem access. It's a one-way downstream-only cable modem, meaning that your upstream net link is provided by your regular phone modem. At present this driver only compiles as a module, so say M here if you have this card. The module will be called sb1000. Then read <file:Documentation/networking/README.sb1000> for information on how to use this module, as it needs special ppp scripts for establishing a connection. Further documentation and the necessary scripts can be found at: <http://www.jacksonville.net/~fventuri/> <http://home.adelphia.net/~siglercm/sb1000.html> <http://linuxpower.cx/~cable/> If you don't have this card, of course say N. source "drivers/net/arcnet/Kconfig" source "drivers/net/phy/Kconfig" ## Ethernet# menu "Ethernet (10 or 100Mbit)" depends on !UML config NET_ETHERNET bool "Ethernet (10 or 100Mbit)" ---help--- Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common type of Local Area Network (LAN) in universities and companies. Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over coaxial cable, linking computers in a chain), 10BASE-T or twisted pair (10 Mbps over twisted pair cable, linking computers to central hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) [the 100BASE varieties are also known as Fast Ethernet], and Gigabit Ethernet (1 Gbps over optical fiber or short copper links). If your Linux machine will be connected to an Ethernet and you have an Ethernet network interface card (NIC) installed in your computer, say Y here and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. You will then also have to say Y to the driver for your particular NIC. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Ethernet network cards. If unsure, say N. config MII tristate "Generic Media Independent Interface device support" depends on NET_ETHERNET help Most ethernet controllers have MII transceiver either as an external or internal device. It is safe to say Y or M here even if your ethernet card lack MII. source "drivers/net/arm/Kconfig" config MACE tristate "MACE (Power Mac ethernet) support" depends on NET_ETHERNET && PPC_PMAC && PPC32 select CRC32 help Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. To compile this driver as a module, choose M here: the module will be called mace. config MACE_AAUI_PORT bool "Use AAUI port instead of TP by default" depends on MACE help Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. config BMAC tristate "BMAC (G3 ethernet) support" depends on NET_ETHERNET && PPC_PMAC && PPC32 select CRC32 help 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. config OAKNET tristate "National DP83902AV (Oak ethernet) support" depends on NET_ETHERNET && PPC && BROKEN select CRC32 help 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. config ARIADNE tristate "Ariadne support" depends on NET_ETHERNET && ZORRO help If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called ariadne. config A2065 tristate "A2065 support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config HYDRA tristate "Hydra support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config ZORRO8390 tristate "Zorro NS8390-based Ethernet support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config APNE tristate "PCMCIA NE2000 support" depends on NET_ETHERNET && AMIGA_PCMCIA select CRC32 help 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. config APOLLO_ELPLUS tristate "Apollo 3c505 support" depends on NET_ETHERNET && APOLLO help Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card. If you don't have one made for Apollos, you can use one from a PC, except that your Apollo won't be able to boot from it (because the code in the ROM will be for a PC). config MAC8390 bool "Macintosh NS 8390 based ethernet cards" depends on NET_ETHERNET && MAC select CRC32 help If you want to include a driver to support Nubus or LC-PDS Ethernet cards using an NS8390 chipset or its equivalent, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MAC89x0 tristate "Macintosh CS89x0 based ethernet cards" depends on NET_ETHERNET && MAC && BROKEN ---help--- Support for CS89x0 chipset based Ethernet cards. If you have a Nubus or LC-PDS network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. This module will be called mac89x0. config MACSONIC tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" depends on NET_ETHERNET && MAC ---help--- Support for NatSemi SONIC based Ethernet devices. This includes the onboard Ethernet in many Quadras as well as some LC-PDS, a few Nubus and all known Comm Slot Ethernet cards. If you have one of these say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. This module will be called macsonic. config MACMACE bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)" depends on NET_ETHERNET && MAC && EXPERIMENTAL select CRC32 help Support for the onboard AMD 79C940 MACE Ethernet controller used in the 660AV and 840AV Macintosh. If you have one of these Macintoshes say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MVME147_NET tristate "MVME147 (Lance) Ethernet support" depends on NET_ETHERNET && MVME147 select CRC32 help Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config MVME16x_NET tristate "MVME16x Ethernet support" depends on NET_ETHERNET && MVME16x help This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config BVME6000_NET tristate "BVME6000 Ethernet support" depends on NET_ETHERNET && BVME6000 help This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config ATARILANCE tristate "Atari Lance support" depends on NET_ETHERNET && ATARI help Say Y to include support for several Atari Ethernet adapters based on the AMD Lance chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). config ATARI_BIONET tristate "BioNet-100 support" depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN help Say Y to include support for BioData's BioNet-100 Ethernet adapter for the ACSI port. The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config ATARI_PAMSNET tristate "PAMsNet support" depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN help Say Y to include support for the PAMsNet Ethernet adapter for the ACSI port ("ACSI node"). The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config SUN3LANCE tristate "Sun3/Sun3x on-board LANCE support" depends on NET_ETHERNET && (SUN3 || SUN3X) help Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) featured an AMD Lance 10Mbit Ethernet controller on board; say Y here to compile in the Linux driver for this and enable Ethernet. General Linux information on the Sun 3 and 3x series (now discontinued) is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. If you're not building a kernel for a Sun 3, say N. config SUN3_82586 bool "Sun3 on-board Intel 82586 support" depends on NET_ETHERNET && SUN3 help This driver enables support for the on-board Intel 82586 based Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note that this driver does not support 82586-based adapters on additional VME boards. config HPLANCE bool "HP on-board LANCE support" depends on NET_ETHERNET && DIO select CRC32 help If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. config LASI_82596 tristate "Lasi ethernet" depends on NET_ETHERNET && PARISC && GSC_LASI help Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines. config MIPS_JAZZ_SONIC tristate "MIPS JAZZ onboard SONIC Ethernet support" depends on NET_ETHERNET && MACH_JAZZ help This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. config MIPS_GT96100ETH bool "MIPS GT96100 Ethernet support" depends on NET_ETHERNET && MIPS_GT96100 help Say Y here to support the Ethernet subsystem on your GT96100 card. config MIPS_AU1X00_ENET bool "MIPS AU1000 Ethernet support" depends on NET_ETHERNET && SOC_AU1X00 select PHYLIB select CRC32 help If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N. config NET_SB1250_MAC tristate "SB1250 Ethernet support" depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC config SGI_IOC3_ETH bool "SGI IOC3 Ethernet" depends on NET_ETHERNET && PCI && SGI_IP27 select CRC32 select MII help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config SGI_IOC3_ETH_HW_RX_CSUM bool "Receive hardware checksums" depends on SGI_IOC3_ETH && INET default y help 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. config SGI_IOC3_ETH_HW_TX_CSUM bool "Transmit hardware checksums" depends on SGI_IOC3_ETH && INET default y help 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. config MIPS_SIM_NET tristate "MIPS simulator Network device (EXPERIMENTAL)" depends on NETDEVICES && MIPS_SIM && EXPERIMENTAL help 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. config SGI_O2MACE_ETH tristate "SGI O2 MACE Fast Ethernet support" depends on NET_ETHERNET && SGI_IP32=yLines 1–500 of 2766. Load more
# # Network device configuration # menu "Network device support" depends on NET config NETDEVICES default y if UML bool "Network device support" ---help--- You can say N here if you don't intend to connect your Linux box to any other computer at all. You'll have to say Y if your computer contains a network card that you want to use under Linux. If you are going to run SLIP or PPP over telephone line or null modem cable you need say Y here. Connecting two machines with parallel ports using PLIP needs this, as well as AX.25/KISS for sending Internet traffic over amateur radio links. See also "The Linux Network Administrator's Guide" by Olaf Kirch and Terry Dawson. Available at <http://www.tldp.org/guides.html>. If unsure, say Y. config IFB tristate "Intermediate Functional Block support" depends on NET_CLS_ACT ---help--- This is an intermidiate driver that allows sharing of resources. To compile this driver as a module, choose M here: the module will be called ifb. If you want to use more than one ifb device at a time, you need to compile this driver as a module. Instead of 'ifb', the devices will then be called 'ifb0', 'ifb1' etc. Look at the iproute2 documentation directory for usage etc config DUMMY tristate "Dummy net driver support" ---help--- This is essentially a bit-bucket device (i.e. traffic you send to this device is consigned into oblivion) with a configurable IP address. It is most commonly used in order to make your currently inactive SLIP address seem like a real address for local programs. If you use SLIP or PPP, you might want to say Y here. Since this thing often comes in handy, the default is Y. It won't enlarge your kernel either. What a deal. Read about it in the Network Administrator's Guide, available from <http://www.tldp.org/docs.html#guide>. 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. config BONDING tristate "Bonding driver support" depends on INET ---help--- Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet Channels together. This is called 'Etherchannel' by Cisco, 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. The driver supports multiple bonding modes to allow for both high performance and high availability operation. Refer to <file:Documentation/networking/bonding.txt> for more information. To compile this driver as a module, choose M here: the module will be called bonding. config EQUALIZER tristate "EQL (serial line load balancing) support" ---help--- If you have two serial connections to some other computer (this usually requires two modems and two telephone lines) and you use SLIP (the protocol for sending Internet traffic over telephone lines) or PPP (a better SLIP) on them, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you want this and read <file:Documentation/networking/eql.txt>. You may also want to read section 6.2 of the NET-3-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here: the module will be called eql. If unsure, say N. config TUN tristate "Universal TUN/TAP device driver support" select CRC32 ---help--- TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a program opens /dev/net/tun, driver creates and registers corresponding net device tunX or tapX. After a program closed above devices, driver will automatically delete tunXX or tapXX device and all routes corresponding to it. Please read <file:Documentation/networking/tuntap.txt> for more information. 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. config NET_SB1000 tristate "General Instruments Surfboard 1000" depends on PNP ---help--- This is a driver for the General Instrument (also known as NextLevel) SURFboard 1000 internal cable modem. This is an ISA card which is used by a number of cable TV companies to provide cable modem access. It's a one-way downstream-only cable modem, meaning that your upstream net link is provided by your regular phone modem. At present this driver only compiles as a module, so say M here if you have this card. The module will be called sb1000. Then read <file:Documentation/networking/README.sb1000> for information on how to use this module, as it needs special ppp scripts for establishing a connection. Further documentation and the necessary scripts can be found at: <http://www.jacksonville.net/~fventuri/> <http://home.adelphia.net/~siglercm/sb1000.html> <http://linuxpower.cx/~cable/> If you don't have this card, of course say N. source "drivers/net/arcnet/Kconfig" source "drivers/net/phy/Kconfig" # # Ethernet # menu "Ethernet (10 or 100Mbit)" depends on !UML config NET_ETHERNET bool "Ethernet (10 or 100Mbit)" ---help--- Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common type of Local Area Network (LAN) in universities and companies. Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over coaxial cable, linking computers in a chain), 10BASE-T or twisted pair (10 Mbps over twisted pair cable, linking computers to central hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) [the 100BASE varieties are also known as Fast Ethernet], and Gigabit Ethernet (1 Gbps over optical fiber or short copper links). If your Linux machine will be connected to an Ethernet and you have an Ethernet network interface card (NIC) installed in your computer, say Y here and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. You will then also have to say Y to the driver for your particular NIC. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Ethernet network cards. If unsure, say N. config MII tristate "Generic Media Independent Interface device support" depends on NET_ETHERNET help Most ethernet controllers have MII transceiver either as an external or internal device. It is safe to say Y or M here even if your ethernet card lack MII. source "drivers/net/arm/Kconfig" config MACE tristate "MACE (Power Mac ethernet) support" depends on NET_ETHERNET && PPC_PMAC && PPC32 select CRC32 help Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. To compile this driver as a module, choose M here: the module will be called mace. config MACE_AAUI_PORT bool "Use AAUI port instead of TP by default" depends on MACE help Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. config BMAC tristate "BMAC (G3 ethernet) support" depends on NET_ETHERNET && PPC_PMAC && PPC32 select CRC32 help 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. config OAKNET tristate "National DP83902AV (Oak ethernet) support" depends on NET_ETHERNET && PPC && BROKEN select CRC32 help 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. config ARIADNE tristate "Ariadne support" depends on NET_ETHERNET && ZORRO help If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called ariadne. config A2065 tristate "A2065 support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config HYDRA tristate "Hydra support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config ZORRO8390 tristate "Zorro NS8390-based Ethernet support" depends on NET_ETHERNET && ZORRO select CRC32 help 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. config APNE tristate "PCMCIA NE2000 support" depends on NET_ETHERNET && AMIGA_PCMCIA select CRC32 help 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. config APOLLO_ELPLUS tristate "Apollo 3c505 support" depends on NET_ETHERNET && APOLLO help Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card. If you don't have one made for Apollos, you can use one from a PC, except that your Apollo won't be able to boot from it (because the code in the ROM will be for a PC). config MAC8390 bool "Macintosh NS 8390 based ethernet cards" depends on NET_ETHERNET && MAC select CRC32 help If you want to include a driver to support Nubus or LC-PDS Ethernet cards using an NS8390 chipset or its equivalent, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MAC89x0 tristate "Macintosh CS89x0 based ethernet cards" depends on NET_ETHERNET && MAC && BROKEN ---help--- Support for CS89x0 chipset based Ethernet cards. If you have a Nubus or LC-PDS network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. This module will be called mac89x0. config MACSONIC tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" depends on NET_ETHERNET && MAC ---help--- Support for NatSemi SONIC based Ethernet devices. This includes the onboard Ethernet in many Quadras as well as some LC-PDS, a few Nubus and all known Comm Slot Ethernet cards. If you have one of these say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. To compile this driver as a module, choose M here and read <file:Documentation/networking/net-modules.txt>. This module will be called macsonic. config MACMACE bool "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)" depends on NET_ETHERNET && MAC && EXPERIMENTAL select CRC32 help Support for the onboard AMD 79C940 MACE Ethernet controller used in the 660AV and 840AV Macintosh. If you have one of these Macintoshes say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config MVME147_NET tristate "MVME147 (Lance) Ethernet support" depends on NET_ETHERNET && MVME147 select CRC32 help Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config MVME16x_NET tristate "MVME16x Ethernet support" depends on NET_ETHERNET && MVME16x help This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config BVME6000_NET tristate "BVME6000 Ethernet support" depends on NET_ETHERNET && BVME6000 help This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config ATARILANCE tristate "Atari Lance support" depends on NET_ETHERNET && ATARI help Say Y to include support for several Atari Ethernet adapters based on the AMD Lance chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). config ATARI_BIONET tristate "BioNet-100 support" depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN help Say Y to include support for BioData's BioNet-100 Ethernet adapter for the ACSI port. The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config ATARI_PAMSNET tristate "PAMsNet support" depends on NET_ETHERNET && ATARI && ATARI_ACSI && BROKEN help Say Y to include support for the PAMsNet Ethernet adapter for the ACSI port ("ACSI node"). The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( config SUN3LANCE tristate "Sun3/Sun3x on-board LANCE support" depends on NET_ETHERNET && (SUN3 || SUN3X) help Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) featured an AMD Lance 10Mbit Ethernet controller on board; say Y here to compile in the Linux driver for this and enable Ethernet. General Linux information on the Sun 3 and 3x series (now discontinued) is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. If you're not building a kernel for a Sun 3, say N. config SUN3_82586 bool "Sun3 on-board Intel 82586 support" depends on NET_ETHERNET && SUN3 help This driver enables support for the on-board Intel 82586 based Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note that this driver does not support 82586-based adapters on additional VME boards. config HPLANCE bool "HP on-board LANCE support" depends on NET_ETHERNET && DIO select CRC32 help If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. config LASI_82596 tristate "Lasi ethernet" depends on NET_ETHERNET && PARISC && GSC_LASI help Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines. config MIPS_JAZZ_SONIC tristate "MIPS JAZZ onboard SONIC Ethernet support" depends on NET_ETHERNET && MACH_JAZZ help This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. config MIPS_GT96100ETH bool "MIPS GT96100 Ethernet support" depends on NET_ETHERNET && MIPS_GT96100 help Say Y here to support the Ethernet subsystem on your GT96100 card. config MIPS_AU1X00_ENET bool "MIPS AU1000 Ethernet support" depends on NET_ETHERNET && SOC_AU1X00 select PHYLIB select CRC32 help If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N. config NET_SB1250_MAC tristate "SB1250 Ethernet support" depends on NET_ETHERNET && SIBYTE_SB1xxx_SOC config SGI_IOC3_ETH bool "SGI IOC3 Ethernet" depends on NET_ETHERNET && PCI && SGI_IP27 select CRC32 select MII help If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>. config SGI_IOC3_ETH_HW_RX_CSUM bool "Receive hardware checksums" depends on SGI_IOC3_ETH && INET default y help 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. config SGI_IOC3_ETH_HW_TX_CSUM bool "Transmit hardware checksums" depends on SGI_IOC3_ETH && INET default y help 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. config MIPS_SIM_NET tristate "MIPS simulator Network device (EXPERIMENTAL)" depends on NETDEVICES && MIPS_SIM && EXPERIMENTAL help 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. config SGI_O2MACE_ETH tristate "SGI O2 MACE Fast Ethernet support" depends on NET_ETHERNET && SGI_IP32=y