2 # Network device configuration
11 bool "Network device support"
13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all.
16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links.
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols.
32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT
35 This is an intermediate driver that allows sharing of
37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0',
42 Look at the iproute2 documentation directory for usage etc
45 tristate "Dummy net driver support"
47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>.
57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0',
64 tristate "Bonding driver support"
66 depends on IPV6 || IPV6=n
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation.
75 Refer to <file:Documentation/networking/bonding.txt> for more
78 To compile this driver as a module, choose M here: the module
79 will be called bonding.
82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL
85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface.
88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release:
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
93 To compile this driver as a module, choose M here: the module
94 will be called macvlan.
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface.
105 To compile this driver as a module, choose M here: the module
106 will be called macvtap.
109 tristate "EQL (serial line load balancing) support"
111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e.
119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>.
124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N.
128 tristate "Universal TUN/TAP device driver support"
131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program.
137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it.
142 Please read <file:Documentation/networking/tuntap.txt> for more
145 To compile this driver as a module, choose M here: the module
148 If you don't know what to use this for, you don't need it.
151 tristate "Virtual ethernet pair device"
153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice
158 tristate "General Instruments Surfboard 1000"
161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem.
168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be
175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/>
179 If you don't have this card, of course say N.
181 source "drivers/net/arcnet/Kconfig"
184 tristate "Generic Media Independent Interface device support"
186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII.
190 source "drivers/net/phy/Kconfig"
196 source "drivers/net/ethernet/Kconfig"
198 menuconfig NET_ETHERNET
199 bool "Ethernet (10 or 100Mbit)"
202 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
203 type of Local Area Network (LAN) in universities and companies.
205 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
206 coaxial cable, linking computers in a chain), 10BASE-T or twisted
207 pair (10 Mbps over twisted pair cable, linking computers to central
208 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
209 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
210 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
211 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
212 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
213 Ethernet (1 Gbps over optical fiber or short copper links).
215 If your Linux machine will be connected to an Ethernet and you have
216 an Ethernet network interface card (NIC) installed in your computer,
217 say Y here and read the Ethernet-HOWTO, available from
218 <http://www.tldp.org/docs.html#howto>. You will then also have
219 to say Y to the driver for your particular NIC.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about Ethernet network cards. If unsure, say N.
228 tristate "Atmel MACB support"
229 depends on HAVE_NET_MACB
232 The Atmel MACB ethernet interface is found on many AT32 and AT91
233 parts. Say Y to include support for the MACB chip.
235 To compile this driver as a module, choose M here: the module
238 source "drivers/net/arm/Kconfig"
241 tristate "ASIX AX88796 NE2000 clone support"
242 depends on ARM || MIPS || SUPERH
246 AX88796 driver, using platform bus to provide
247 chip detection and resources
250 bool "ASIX AX88796 external 93CX6 eeprom support"
254 Select this if your platform comes with an external 93CX6 eeprom.
257 tristate "MACE (Power Mac ethernet) support"
258 depends on PPC_PMAC && PPC32
261 Power Macintoshes and clones with Ethernet built-in on the
262 motherboard will usually use a MACE (Medium Access Control for
263 Ethernet) interface. Say Y to include support for the MACE chip.
265 To compile this driver as a module, choose M here: the module
268 config MACE_AAUI_PORT
269 bool "Use AAUI port instead of TP by default"
272 Some Apple machines (notably the Apple Network Server) which use the
273 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
274 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
275 Y here if you have such a machine. If unsure, say N.
276 The driver will default to AAUI on ANS anyway, and if you use it as
277 a module, you can provide the port_aaui=0|1 to force the driver.
280 tristate "BMAC (G3 ethernet) support"
281 depends on PPC_PMAC && PPC32
284 Say Y for support of BMAC Ethernet interfaces. These are used on G3
287 To compile this driver as a module, choose M here: the module
291 tristate "Ariadne support"
294 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
297 To compile this driver as a module, choose M here: the module
298 will be called ariadne.
301 tristate "A2065 support"
305 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
308 To compile this driver as a module, choose M here: the module
309 will be called a2065.
312 tristate "Hydra support"
316 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
318 To compile this driver as a module, choose M here: the module
319 will be called hydra.
322 tristate "Zorro NS8390-based Ethernet support"
326 This driver is for Zorro Ethernet cards using an NS8390-compatible
327 chipset, like the Village Tronic Ariadne II and the Individual
328 Computers X-Surf Ethernet cards. If you have such a card, say Y.
331 To compile this driver as a module, choose M here: the module
332 will be called zorro8390.
335 tristate "PCMCIA NE2000 support"
336 depends on AMIGA_PCMCIA
339 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
342 To compile this driver as a module, choose M here: the module
346 bool "Macintosh NS 8390 based ethernet cards"
350 If you want to include a driver to support Nubus or LC-PDS
351 Ethernet cards using an NS8390 chipset or its equivalent, say Y
352 and read the Ethernet-HOWTO, available from
353 <http://www.tldp.org/docs.html#howto>.
356 tristate "Macintosh CS89x0 based ethernet cards"
359 Support for CS89x0 chipset based Ethernet cards. If you have a
360 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
361 read the Ethernet-HOWTO, available from
362 <http://www.tldp.org/docs.html#howto>.
364 To compile this driver as a module, choose M here. This module will
368 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
371 Support for NatSemi SONIC based Ethernet devices. This includes
372 the onboard Ethernet in many Quadras as well as some LC-PDS,
373 a few Nubus and all known Comm Slot Ethernet cards. If you have
374 one of these say Y and read the Ethernet-HOWTO, available from
375 <http://www.tldp.org/docs.html#howto>.
377 To compile this driver as a module, choose M here. This module will
381 bool "Macintosh (AV) onboard MACE ethernet"
385 Support for the onboard AMD 79C940 MACE Ethernet controller used in
386 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
387 say Y and read the Ethernet-HOWTO, available from
388 <http://www.tldp.org/docs.html#howto>.
391 tristate "MVME147 (Lance) Ethernet support"
395 Support for the on-board Ethernet interface on the Motorola MVME147
396 single-board computer. Say Y here to include the
397 driver for this chip in your kernel.
398 To compile this driver as a module, choose M here.
401 tristate "MVME16x Ethernet support"
404 This is the driver for the Ethernet interface on the Motorola
405 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
406 driver for this chip in your kernel.
407 To compile this driver as a module, choose M here.
410 tristate "BVME6000 Ethernet support"
413 This is the driver for the Ethernet interface on BVME4000 and
414 BVME6000 VME boards. Say Y here to include the driver for this chip
416 To compile this driver as a module, choose M here.
419 tristate "Atari Lance support"
422 Say Y to include support for several Atari Ethernet adapters based
423 on the AMD Lance chipset: RieblCard (with or without battery), or
424 PAMCard VME (also the version by Rhotron, with different addresses).
427 tristate "Sun3/Sun3x on-board LANCE support"
428 depends on SUN3 || SUN3X
430 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
431 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
432 here to compile in the Linux driver for this and enable Ethernet.
433 General Linux information on the Sun 3 and 3x series (now
435 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
437 If you're not building a kernel for a Sun 3, say N.
440 bool "Sun3 on-board Intel 82586 support"
443 This driver enables support for the on-board Intel 82586 based
444 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
445 that this driver does not support 82586-based adapters on additional
449 bool "HP on-board LANCE support"
453 If you want to use the builtin "LANCE" Ethernet controller on an
454 HP300 machine, say Y here.
457 tristate "Lasi ethernet"
460 Say Y here to support the builtin Intel 82596 ethernet controller
461 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
464 tristate "SNI RM ethernet"
465 depends on NET_ETHERNET && SNI_RM
467 Say Y here to support the on-board Intel 82596 ethernet controller
468 built into SNI RM machines.
471 tristate "Korina (IDT RC32434) Ethernet support"
472 depends on NET_ETHERNET && MIKROTIK_RB532
474 If you have a Mikrotik RouterBoard 500 or IDT RC32434
475 based system say Y. Otherwise say N.
477 config MIPS_JAZZ_SONIC
478 tristate "MIPS JAZZ onboard SONIC Ethernet support"
481 This is the driver for the onboard card of MIPS Magnum 4000,
482 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
484 config XTENSA_XT2000_SONIC
485 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
486 depends on XTENSA_PLATFORM_XT2000
488 This is the driver for the onboard card of the Xtensa XT2000 board.
490 config MIPS_AU1X00_ENET
491 tristate "MIPS AU1000 Ethernet support"
492 depends on MIPS_ALCHEMY
496 If you have an Alchemy Semi AU1X00 based system
497 say Y. Otherwise, say N.
500 bool "SGI IOC3 Ethernet"
501 depends on PCI && SGI_IP27
505 If you have a network (Ethernet) card of this type, say Y and read
506 the Ethernet-HOWTO, available from
507 <http://www.tldp.org/docs.html#howto>.
510 tristate "MIPS simulator Network device"
513 The MIPSNET device is a simple Ethernet network device which is
514 emulated by the MIPS Simulator.
515 If you are not using a MIPSsim or are unsure, say N.
517 config SGI_O2MACE_ETH
518 tristate "SGI O2 MACE Fast Ethernet support"
519 depends on SGI_IP32=y
522 tristate "National DP83902AV support"
526 Support for cards based on the National Semiconductor DP83902AV
527 ST-NIC Serial Network Interface Controller for Twisted Pair. This
528 is a 10Mbit/sec Ethernet controller. Product overview and specs at
529 <http://www.national.com/pf/DP/DP83902A.html>.
534 tristate "Renesas SuperH Ethernet support"
535 depends on SUPERH && \
536 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
537 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
538 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
544 Renesas SuperH Ethernet device driver.
545 This driver supporting CPUs are:
546 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
549 tristate "Sun LANCE support"
553 This driver supports the "le" interface present on all 32-bit Sparc
554 systems, on some older Ultra systems and as an Sbus option. These
555 cards are based on the AMD Lance chipset, which is better known
556 via the NE2100 cards.
558 To compile this driver as a module, choose M here: the module
559 will be called sunlance.
562 tristate "Sun Happy Meal 10/100baseT support"
563 depends on SBUS || PCI
566 This driver supports the "hme" interface present on most Ultra
567 systems and as an option on older Sbus systems. This driver supports
568 both PCI and Sbus devices. This driver also supports the "qfe" quad
569 100baseT device available in both PCI and Sbus configurations.
571 To compile this driver as a module, choose M here: the module
572 will be called sunhme.
575 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
576 depends on SBUS && EXPERIMENTAL
579 This driver supports the "be" interface available as an Sbus option.
580 This is Sun's older 100baseT Ethernet device.
582 To compile this driver as a module, choose M here: the module
583 will be called sunbmac.
586 tristate "Sun QuadEthernet support"
590 This driver supports the "qe" 10baseT Ethernet device, available as
591 an Sbus option. Note that this is not the same as Quad FastEthernet
592 "qfe" which is supported by the Happy Meal driver instead.
594 To compile this driver as a module, choose M here: the module
595 will be called sunqe.
598 tristate "Sun GEM support"
602 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
603 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
606 tristate "Sun Cassini support"
610 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
611 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
614 tristate "Sun Virtual Network support"
617 Support for virtual network devices under Sun Logical Domains.
620 tristate "3c503 \"EtherLink II\" support"
624 If you have a network (Ethernet) card of this type, say Y and read
625 the Ethernet-HOWTO, available from
626 <http://www.tldp.org/docs.html#howto>.
628 To compile this driver as a module, choose M here. The module
629 will be called 3c503.
632 tristate "3c505 \"EtherLink Plus\" support"
633 depends on ISA && ISA_DMA_API
635 Information about this network (Ethernet) card can be found in
636 <file:Documentation/networking/3c505.txt>. If you have a card of
637 this type, say Y and read the Ethernet-HOWTO, available from
638 <http://www.tldp.org/docs.html#howto>.
640 To compile this driver as a module, choose M here. The module
641 will be called 3c505.
644 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
645 depends on ISA && EXPERIMENTAL
647 If you have a network (Ethernet) card of this type, say Y and read
648 the Ethernet-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>.
651 To compile this driver as a module, choose M here. The module
652 will be called 3c507.
655 tristate "3c523 \"EtherLink/MC\" support"
656 depends on MCA_LEGACY
658 If you have a network (Ethernet) card of this type, say Y and read
659 the Ethernet-HOWTO, available from
660 <http://www.tldp.org/docs.html#howto>.
662 To compile this driver as a module, choose M here. The module
663 will be called 3c523.
666 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
667 depends on MCA && MCA_LEGACY
669 If you have a network (Ethernet) card of this type, say Y and read
670 the Ethernet-HOWTO, available from
671 <http://www.tldp.org/docs.html#howto>.
673 To compile this driver as a module, choose M here. The module
674 will be called 3c527.
677 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
678 depends on ISA && ISA_DMA_API
680 If you have a network (Ethernet) card of this type, say Y and read
681 the Ethernet-HOWTO, available from
682 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
685 To compile this driver as a module, choose M here: the module
686 will be called lance. This is recommended.
688 config NET_VENDOR_SMC
689 bool "Western Digital/SMC cards"
690 depends on ISA || MCA || EISA || MAC
692 If you have a network (Ethernet) card belonging to this class, say Y
693 and read the Ethernet-HOWTO, available from
694 <http://www.tldp.org/docs.html#howto>.
696 Note that the answer to this question doesn't directly affect the
697 kernel: saying N will just cause the configurator to skip all
698 the questions about Western Digital cards. If you say Y, you will be
699 asked for your specific card in the following questions.
702 tristate "WD80*3 support"
703 depends on NET_VENDOR_SMC && ISA
706 If you have a network (Ethernet) card of this type, say Y and read
707 the Ethernet-HOWTO, available from
708 <http://www.tldp.org/docs.html#howto>.
710 To compile this driver as a module, choose M here. The module
714 tristate "SMC Ultra MCA support"
715 depends on NET_VENDOR_SMC && MCA
718 If you have a network (Ethernet) card of this type and are running
719 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
720 available from <http://www.tldp.org/docs.html#howto>.
722 To compile this driver as a module, choose M here. The module
723 will be called smc-mca.
726 tristate "SMC Ultra support"
727 depends on NET_VENDOR_SMC && ISA
730 If you have a network (Ethernet) card of this type, say Y and read
731 the Ethernet-HOWTO, available from
732 <http://www.tldp.org/docs.html#howto>.
734 Important: There have been many reports that, with some motherboards
735 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
736 such as some BusLogic models) causes corruption problems with many
737 operating systems. The Linux smc-ultra driver has a work-around for
738 this but keep it in mind if you have such a SCSI card and have
741 To compile this driver as a module, choose M here. The module
742 will be called smc-ultra.
745 tristate "SMC Ultra32 EISA support"
746 depends on NET_VENDOR_SMC && EISA
749 If you have a network (Ethernet) card of this type, say Y and read
750 the Ethernet-HOWTO, available from
751 <http://www.tldp.org/docs.html#howto>.
753 To compile this driver as a module, choose M here. The module
754 will be called smc-ultra32.
757 tristate "Blackfin on-chip MAC support"
758 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
762 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
764 This is the driver for Blackfin on-chip mac device. Say Y if you want it
765 compiled into the kernel. This driver is also available as a module
766 ( = code which can be inserted in and removed from the running kernel
767 whenever you want). The module will be called bfin_mac.
769 config BFIN_MAC_USE_L1
770 bool "Use L1 memory for rx/tx packets"
771 depends on BFIN_MAC && (BF527 || BF537)
774 To get maximum network performance, you should use L1 memory as rx/tx buffers.
775 Say N here if you want to reserve L1 memory for other uses.
777 config BFIN_TX_DESC_NUM
778 int "Number of transmit buffer packets"
780 range 6 10 if BFIN_MAC_USE_L1
784 Set the number of buffer packets used in driver.
786 config BFIN_RX_DESC_NUM
787 int "Number of receive buffer packets"
789 range 20 100 if BFIN_MAC_USE_L1
793 Set the number of buffer packets used in driver.
795 config BFIN_MAC_USE_HWSTAMP
796 bool "Use IEEE 1588 hwstamp"
797 depends on BFIN_MAC && BF518
800 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
803 tristate "SMC 9194 support"
804 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
807 This is support for the SMC9xxx based Ethernet cards. Choose this
808 option if you have a DELL laptop with the docking station, or
809 another SMC9192/9194 based chipset. Say Y if you want it compiled
810 into the kernel, and read the file
811 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
812 available from <http://www.tldp.org/docs.html#howto>.
814 To compile this driver as a module, choose M here. The module
815 will be called smc9194.
818 tristate "SMC 91C9x/91C1xxx support"
821 depends on ARM || M32R || SUPERH || \
822 MIPS || BLACKFIN || MN10300 || COLDFIRE
824 This is a driver for SMC's 91x series of Ethernet chipsets,
825 including the SMC91C94 and the SMC91C111. Say Y if you want it
826 compiled into the kernel, and read the file
827 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
828 available from <http://www.tldp.org/docs.html#howto>.
830 This driver is also available as a module ( = code which can be
831 inserted in and removed from the running kernel whenever you want).
832 The module will be called smc91x. If you want to compile it as a
833 module, say M here and read <file:Documentation/kbuild/modules.txt>.
836 tristate "Marvell pxa168 ethernet support"
837 depends on CPU_PXA168
840 This driver supports the pxa168 Ethernet ports.
842 To compile this driver as a module, choose M here. The module
843 will be called pxa168_eth.
846 tristate "NetX Ethernet support"
850 This is support for the Hilscher netX builtin Ethernet ports
852 To compile this driver as a module, choose M here. The module
853 will be called netx-eth.
855 config TI_DAVINCI_EMAC
856 tristate "TI DaVinci EMAC Support"
857 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
858 select TI_DAVINCI_MDIO
859 select TI_DAVINCI_CPDMA
862 This driver supports TI's DaVinci Ethernet .
864 To compile this driver as a module, choose M here: the module
865 will be called davinci_emac_driver. This is recommended.
867 config TI_DAVINCI_MDIO
868 tristate "TI DaVinci MDIO Support"
869 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
872 This driver supports TI's DaVinci MDIO module.
874 To compile this driver as a module, choose M here: the module
875 will be called davinci_mdio. This is recommended.
877 config TI_DAVINCI_CPDMA
878 tristate "TI DaVinci CPDMA Support"
879 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
881 This driver supports TI's DaVinci CPDMA dma engine.
883 To compile this driver as a module, choose M here: the module
884 will be called davinci_cpdma. This is recommended.
887 tristate "DM9000 support"
888 depends on ARM || BLACKFIN || MIPS
892 Support for DM9000 chipset.
894 To compile this driver as a module, choose M here. The module
895 will be called dm9000.
897 config DM9000_DEBUGLEVEL
898 int "DM9000 maximum debug level"
902 The maximum level of debugging code compiled into the DM9000
905 config DM9000_FORCE_SIMPLE_PHY_POLL
906 bool "Force simple NSR based PHY polling"
909 This configuration forces the DM9000 to use the NSR's LinkStatus
910 bit to determine if the link is up or down instead of the more
911 costly MII PHY reads. Note, this will not work if the chip is
912 operating with an external PHY.
915 tristate "ENC28J60 support"
916 depends on EXPERIMENTAL && SPI && NET_ETHERNET
919 Support for the Microchip EN28J60 ethernet chip.
921 To compile this driver as a module, choose M here. The module will be
924 config ENC28J60_WRITEVERIFY
925 bool "Enable write verify"
928 Enable the verify after the buffer write useful for debugging purpose.
932 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
933 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
939 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
942 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
947 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
950 tristate "SMSC LAN911[5678] support"
953 depends on ARM || SUPERH || MN10300
955 This is a driver for SMSC's LAN911x series of Ethernet chipsets
956 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
957 Say Y if you want it compiled into the kernel,
958 and read the Ethernet-HOWTO, available from
959 <http://www.tldp.org/docs.html#howto>.
961 This driver is also available as a module. The module will be
962 called smc911x. If you want to compile it as a module, say M
963 here and read <file:Documentation/kbuild/modules.txt>
966 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
967 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
972 Say Y here if you want support for SMSC LAN911x and LAN921x families
973 of ethernet controllers.
975 To compile this driver as a module, choose M here and read
976 <file:Documentation/networking/net-modules.txt>. The module
977 will be called smsc911x.
979 config SMSC911X_ARCH_HOOKS
983 If the arch enables this, it allows the arch to implement various
984 hooks for more comprehensive interrupt control and also to override
985 the source of the MAC address.
987 config NET_VENDOR_RACAL
988 bool "Racal-Interlan (Micom) NI cards"
991 If you have a network (Ethernet) card belonging to this class, such
992 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
993 available from <http://www.tldp.org/docs.html#howto>.
995 Note that the answer to this question doesn't directly affect the
996 kernel: saying N will just cause the configurator to skip all
997 the questions about NI cards. If you say Y, you will be asked for
998 your specific card in the following questions.
1001 tristate "NI5010 support (EXPERIMENTAL)"
1002 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1004 If you have a network (Ethernet) card of this type, say Y and read
1005 the Ethernet-HOWTO, available from
1006 <http://www.tldp.org/docs.html#howto>. Note that this is still
1009 To compile this driver as a module, choose M here. The module
1010 will be called ni5010.
1013 tristate "NI5210 support"
1014 depends on NET_VENDOR_RACAL && ISA
1016 If you have a network (Ethernet) card of this type, say Y and read
1017 the Ethernet-HOWTO, available from
1018 <http://www.tldp.org/docs.html#howto>.
1020 To compile this driver as a module, choose M here. The module
1021 will be called ni52.
1024 tristate "NI6510 support"
1025 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1027 If you have a network (Ethernet) card of this type, say Y and read
1028 the Ethernet-HOWTO, available from
1029 <http://www.tldp.org/docs.html#howto>.
1031 To compile this driver as a module, choose M here. The module
1032 will be called ni65.
1035 tristate "Dave ethernet support (DNET)"
1036 depends on NET_ETHERNET && HAS_IOMEM
1039 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1040 Say Y to include support for the DNET chip.
1042 To compile this driver as a module, choose M here: the module
1043 will be called dnet.
1045 source "drivers/net/tulip/Kconfig"
1048 tristate "AT1700/1720 support (EXPERIMENTAL)"
1049 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1052 If you have a network (Ethernet) card of this type, say Y and read
1053 the Ethernet-HOWTO, available from
1054 <http://www.tldp.org/docs.html#howto>.
1056 To compile this driver as a module, choose M here. The module
1057 will be called at1700.
1060 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1061 depends on ISA || EISA || MCA
1064 If you have a network (Ethernet) card of this type, say Y and read
1065 the Ethernet-HOWTO, available from
1066 <http://www.tldp.org/docs.html#howto> as well as
1067 <file:drivers/net/depca.c>.
1069 To compile this driver as a module, choose M here. The module
1070 will be called depca.
1073 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1074 depends on ISA || EISA || PCI
1076 If you have a network (Ethernet) card of this type, say Y and read
1077 the Ethernet-HOWTO, available from
1078 <http://www.tldp.org/docs.html#howto>.
1080 To compile this driver as a module, choose M here. The module
1081 will be called hp100.
1084 bool "Other ISA cards"
1087 If your network (Ethernet) card hasn't been mentioned yet and its
1088 bus system (that's the way the cards talks to the other components
1089 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1090 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1091 available from <http://www.tldp.org/docs.html#howto>.
1095 Note that the answer to this question doesn't directly affect the
1096 kernel: saying N will just cause the configurator to skip all
1097 the remaining ISA network card questions. If you say Y, you will be
1098 asked for your specific card in the following questions.
1101 tristate "Cabletron E21xx support"
1105 If you have a network (Ethernet) card of this type, say Y and read
1106 the Ethernet-HOWTO, available from
1107 <http://www.tldp.org/docs.html#howto>.
1109 To compile this driver as a module, choose M here. The module
1110 will be called e2100.
1113 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1117 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1118 cards. If this is for you, say Y and read
1119 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1120 well as the Ethernet-HOWTO, available from
1121 <http://www.tldp.org/docs.html#howto>.
1123 To compile this driver as a module, choose M here. The module
1124 will be called ewrk3.
1127 tristate "EtherExpress 16 support"
1130 If you have an EtherExpress16 network (Ethernet) card, say Y and
1131 read the Ethernet-HOWTO, available from
1132 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1133 EtherExpress16 card used to be regarded as a very poor choice
1134 because the driver was very unreliable. We now have a new driver
1135 that should do better.
1137 To compile this driver as a module, choose M here. The module
1138 will be called eexpress.
1141 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1144 If you have a network (Ethernet) card of this type, say Y. This
1145 driver supports Intel i82595{FX,TX} based boards. Note however
1146 that the EtherExpress PRO/100 Ethernet card has its own separate
1147 driver. Please read the Ethernet-HOWTO, available from
1148 <http://www.tldp.org/docs.html#howto>.
1150 To compile this driver as a module, choose M here. The module
1151 will be called eepro.
1154 tristate "HP PCLAN+ (27247B and 27252A) support"
1158 If you have a network (Ethernet) card of this type, say Y and read
1159 the Ethernet-HOWTO, available from
1160 <http://www.tldp.org/docs.html#howto>.
1162 To compile this driver as a module, choose M here. The module
1163 will be called hp-plus.
1166 tristate "HP PCLAN (27245 and other 27xxx series) support"
1170 If you have a network (Ethernet) card of this type, say Y and read
1171 the Ethernet-HOWTO, available from
1172 <http://www.tldp.org/docs.html#howto>.
1174 To compile this driver as a module, choose M here. The module
1178 tristate "LP486E on board Ethernet"
1181 Say Y here to support the 82596-based on-board Ethernet controller
1182 for the Panther motherboard, which is one of the two shipped in the
1183 Intel Professional Workstation.
1186 tristate "ICL EtherTeam 16i/32 support"
1189 If you have a network (Ethernet) card of this type, say Y and read
1190 the Ethernet-HOWTO, available from
1191 <http://www.tldp.org/docs.html#howto>.
1193 To compile this driver as a module, choose M here. The module
1194 will be called eth16i.
1197 tristate "NE2000/NE1000 support"
1198 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1201 If you have a network (Ethernet) card of this type, say Y and read
1202 the Ethernet-HOWTO, available from
1203 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1204 without a specific driver are compatible with NE2000.
1206 If you have a PCI NE2000 card however, say N here and Y to "PCI
1207 NE2000 and clone support" under "EISA, VLB, PCI and on board
1208 controllers" below. If you have a NE2000 card and are running on
1209 an MCA system (a bus system used on some IBM PS/2 computers and
1210 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1213 To compile this driver as a module, choose M here. The module
1217 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1218 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1220 The Zenith Z-Note notebook computer has a built-in network
1221 (Ethernet) card, and this is the Linux driver for it. Note that the
1222 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1223 by this driver. Read the Ethernet-HOWTO, available from
1224 <http://www.tldp.org/docs.html#howto>.
1227 tristate "SEEQ8005 support (EXPERIMENTAL)"
1228 depends on NET_ISA && EXPERIMENTAL
1230 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1231 is for you, read the Ethernet-HOWTO, available from
1232 <http://www.tldp.org/docs.html#howto>.
1234 To compile this driver as a module, choose M here. The module
1235 will be called seeq8005.
1238 tristate "NE/2 (ne2000 MCA version) support"
1239 depends on MCA_LEGACY
1242 If you have a network (Ethernet) card of this type, say Y and read
1243 the Ethernet-HOWTO, available from
1244 <http://www.tldp.org/docs.html#howto>.
1246 To compile this driver as a module, choose M here. The module
1250 tristate "IBM LAN Adapter/A support"
1253 This is a Micro Channel Ethernet adapter. You need to set
1254 CONFIG_MCA to use this driver. It is both available as an in-kernel
1255 driver and as a module.
1257 To compile this driver as a module, choose M here. The only
1258 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1259 will both support 16K and 32K memory windows, however a 32K window
1260 gives a better security against packet losses. Usage of multiple
1261 boards with this driver should be possible, but has not been tested
1262 up to now due to lack of hardware.
1265 tristate "IBM LAN Virtual Ethernet support"
1266 depends on PPC_PSERIES
1268 This driver supports virtual ethernet adapters on newer IBM iSeries
1269 and pSeries systems.
1271 To compile this driver as a module, choose M here. The module will
1274 source "drivers/net/ibm_newemac/Kconfig"
1277 bool "EISA, VLB, PCI and on board controllers"
1278 depends on ISA || EISA || PCI
1280 This is another class of network cards which attach directly to the
1281 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1282 available from <http://www.tldp.org/docs.html#howto>.
1284 Note that the answer to this question doesn't directly affect the
1285 kernel: saying N will just cause the configurator to skip all
1286 the questions about this class of network cards. If you say Y, you
1287 will be asked for your specific card in the following questions. If
1288 you are unsure, say Y.
1291 tristate "AMD PCnet32 PCI support"
1292 depends on NET_PCI && PCI
1296 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1297 answer Y here and read the Ethernet-HOWTO, available from
1298 <http://www.tldp.org/docs.html#howto>.
1300 To compile this driver as a module, choose M here. The module
1301 will be called pcnet32.
1304 tristate "AMD 8111 (new PCI lance) support"
1305 depends on NET_PCI && PCI
1309 If you have an AMD 8111-based PCI lance ethernet card,
1310 answer Y here and read the Ethernet-HOWTO, available from
1311 <http://www.tldp.org/docs.html#howto>.
1313 To compile this driver as a module, choose M here. The module
1314 will be called amd8111e.
1316 config ADAPTEC_STARFIRE
1317 tristate "Adaptec Starfire/DuraLAN support"
1318 depends on NET_PCI && PCI
1322 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1323 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1324 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1327 To compile this driver as a module, choose M here: the module
1328 will be called starfire. This is recommended.
1331 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1332 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1335 If you have a network (Ethernet) card of this type, say Y and read
1336 the Ethernet-HOWTO, available from
1337 <http://www.tldp.org/docs.html#howto>.
1339 To compile this driver as a module, choose M here. The module
1340 will be called ac3200.
1343 tristate "Micrel KSZ8841/2 PCI"
1344 depends on NET_PCI && PCI
1348 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1350 To compile this driver as a module, choose M here. The module
1351 will be called ksz884x.
1354 tristate "Apricot Xen-II on board Ethernet"
1355 depends on NET_PCI && ISA
1357 If you have a network (Ethernet) controller of this type, say Y and
1358 read the Ethernet-HOWTO, available from
1359 <http://www.tldp.org/docs.html#howto>.
1361 To compile this driver as a module, choose M here. The module
1362 will be called apricot.
1365 tristate "Broadcom 440x/47xx ethernet support"
1366 depends on SSB_POSSIBLE && HAS_DMA
1370 If you have a network (Ethernet) controller of this type, say Y
1371 or M and read the Ethernet-HOWTO, available from
1372 <http://www.tldp.org/docs.html#howto>.
1374 To compile this driver as a module, choose M here. The module
1377 # Auto-select SSB PCI-HOST support, if possible
1378 config B44_PCI_AUTOSELECT
1380 depends on B44 && SSB_PCIHOST_POSSIBLE
1384 # Auto-select SSB PCICORE driver, if possible
1385 config B44_PCICORE_AUTOSELECT
1387 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1388 select SSB_DRIVER_PCICORE
1393 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1397 tristate "nForce Ethernet support"
1398 depends on NET_PCI && PCI
1400 If you have a network (Ethernet) controller of this type, say Y and
1401 read the Ethernet-HOWTO, available from
1402 <http://www.tldp.org/docs.html#howto>.
1404 To compile this driver as a module, choose M here. The module
1405 will be called forcedeth.
1408 tristate "CS89x0 support"
1409 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1410 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
1412 Support for CS89x0 chipset based Ethernet cards. If you have a
1413 network (Ethernet) card of this type, say Y and read the
1414 Ethernet-HOWTO, available from
1415 <http://www.tldp.org/docs.html#howto> as well as
1416 <file:Documentation/networking/cs89x0.txt>.
1418 To compile this driver as a module, choose M here. The module
1419 will be called cs89x0.
1421 config CS89x0_NONISA_IRQ
1423 depends on CS89x0 != n
1424 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
1427 tristate "TOSHIBA TC35815 Ethernet support"
1428 depends on NET_PCI && PCI && MIPS
1432 tristate "Intel(R) PRO/100+ support"
1433 depends on NET_PCI && PCI
1436 This driver supports Intel(R) PRO/100 family of adapters.
1437 To verify that your adapter is supported, find the board ID number
1438 on the adapter. Look for a label that has a barcode and a number
1439 in the format 123456-001 (six digits hyphen three digits).
1441 Use the above information and the Adapter & Driver ID Guide at:
1443 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1445 to identify the adapter.
1447 For the latest Intel PRO/100 network driver for Linux, see:
1449 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1451 More specific information on configuring the driver is in
1452 <file:Documentation/networking/e100.txt>.
1454 To compile this driver as a module, choose M here. The module
1455 will be called e100.
1458 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1459 depends on NET_PCI && EISA && EXPERIMENTAL
1462 If you have a network (Ethernet) card of this type, say Y and read
1463 the Ethernet-HOWTO, available from
1464 <http://www.tldp.org/docs.html#howto>.
1466 To compile this driver as a module, choose M here. The module
1467 will be called lne390.
1470 tristate "Myson MTD-8xx PCI Ethernet support"
1471 depends on NET_PCI && PCI
1475 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1476 cards. <http://www.myson.com.tw/>
1479 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1480 depends on NET_PCI && PCI
1483 This driver is for the National Semiconductor DP83810 series,
1484 which is used in cards from PureData, NetGear, Linksys
1485 and others, including the 83815 chip.
1486 More specific information and updates are available from
1487 <http://www.scyld.com/network/natsemi.html>.
1490 tristate "PCI NE2000 and clones support (see help)"
1491 depends on NET_PCI && PCI
1494 This driver is for NE2000 compatible PCI cards. It will not work
1495 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1496 support" below). If you have a PCI NE2000 network (Ethernet) card,
1497 say Y and read the Ethernet-HOWTO, available from
1498 <http://www.tldp.org/docs.html#howto>.
1500 This driver also works for the following NE2000 clone cards:
1501 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1502 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1503 Holtek HT80232 Holtek HT80229
1505 To compile this driver as a module, choose M here. The module
1506 will be called ne2k-pci.
1509 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1510 depends on NET_PCI && EISA && EXPERIMENTAL
1513 If you have a network (Ethernet) card of this type, say Y and read
1514 the Ethernet-HOWTO, available from
1515 <http://www.tldp.org/docs.html#howto>. Note that this driver
1516 will NOT WORK for NE3200 cards as they are completely different.
1518 To compile this driver as a module, choose M here. The module
1519 will be called ne3210.
1522 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1523 depends on NET_PCI && EISA && EXPERIMENTAL
1526 If you have a network (Ethernet) card of this type, say Y and read
1527 the Ethernet-HOWTO, available from
1528 <http://www.tldp.org/docs.html#howto>.
1530 To compile this driver as a module, choose M here. The module
1531 will be called es3210.
1534 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1535 depends on NET_PCI && PCI && EXPERIMENTAL
1539 This is a driver for the Fast Ethernet PCI network cards based on
1540 the RTL8139C+ chips. If you have one of those, say Y and read
1541 the Ethernet-HOWTO, available from
1542 <http://www.tldp.org/docs.html#howto>.
1544 To compile this driver as a module, choose M here: the module
1545 will be called 8139cp. This is recommended.
1548 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1549 depends on NET_PCI && PCI
1553 This is a driver for the Fast Ethernet PCI network cards based on
1554 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1555 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1557 To compile this driver as a module, choose M here: the module
1558 will be called 8139too. This is recommended.
1561 bool "Use PIO instead of MMIO"
1565 This instructs the driver to use programmed I/O ports (PIO) instead
1566 of PCI shared memory (MMIO). This can possibly solve some problems
1567 in case your mainboard has memory consistency issues. If unsure,
1570 config 8139TOO_TUNE_TWISTER
1571 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1574 This implements a function which might come in handy in case you
1575 are using low quality on long cabling. It is required for RealTek
1576 RTL-8139 revision K boards, and totally unused otherwise. It tries
1577 to match the transceiver to the cable characteristics. This is
1578 experimental since hardly documented by the manufacturer.
1582 bool "Support for older RTL-8129/8130 boards"
1585 This enables support for the older and uncommon RTL-8129 and
1586 RTL-8130 chips, which support MII via an external transceiver,
1587 instead of an internal one. Disabling this option will save some
1588 memory by making the code size smaller. If unsure, say Y.
1590 config 8139_OLD_RX_RESET
1591 bool "Use older RX-reset method"
1594 The 8139too driver was recently updated to contain a more rapid
1595 reset sequence, in the face of severe receive errors. This "new"
1596 RX-reset method should be adequate for all boards. But if you
1597 experience problems, you can enable this option to restore the
1598 old RX-reset behavior. If unsure, say N.
1601 tristate "RDC R6040 Fast Ethernet Adapter support"
1602 depends on NET_PCI && PCI
1607 This is a driver for the R6040 Fast Ethernet MACs found in the
1608 the RDC R-321x System-on-chips.
1610 To compile this driver as a module, choose M here: the module
1611 will be called r6040. This is recommended.
1614 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1615 depends on NET_PCI && PCI
1619 This is a driver for the Fast Ethernet PCI network cards based on
1620 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1621 SiS 630 and SiS 540 chipsets.
1623 This driver also supports AMD 79C901 HomePNA so that you can use
1624 your phone line as a network cable.
1626 To compile this driver as a module, choose M here: the module
1627 will be called sis900. This is recommended.
1630 tristate "SMC EtherPower II"
1631 depends on NET_PCI && PCI
1635 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1636 which is based on the SMC83c17x (EPIC/100).
1637 More specific information and updates are available from
1638 <http://www.scyld.com/network/epic100.html>.
1641 tristate "SMSC LAN9420 PCI ethernet adapter support"
1642 depends on NET_PCI && PCI
1647 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1648 Say Y if you want it compiled into the kernel,
1649 and read the Ethernet-HOWTO, available from
1650 <http://www.tldp.org/docs.html#howto>.
1652 This driver is also available as a module. The module will be
1653 called smsc9420. If you want to compile it as a module, say M
1654 here and read <file:Documentation/kbuild/modules.txt>
1657 tristate "Sundance Alta support"
1658 depends on NET_PCI && PCI
1662 This driver is for the Sundance "Alta" chip.
1663 More specific information and updates are available from
1664 <http://www.scyld.com/network/sundance.html>.
1666 config SUNDANCE_MMIO
1667 bool "Use MMIO instead of PIO"
1670 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1671 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1672 is known to solve bugs on certain chips.
1677 tristate "TI ThunderLAN support"
1678 depends on NET_PCI && (PCI || EISA)
1680 If you have a PCI Ethernet network card based on the ThunderLAN chip
1681 which is supported by this driver, say Y and read the
1682 Ethernet-HOWTO, available from
1683 <http://www.tldp.org/docs.html#howto>.
1685 Devices currently supported by this driver are Compaq Netelligent,
1686 Compaq NetFlex and Olicom cards. Please read the file
1687 <file:Documentation/networking/tlan.txt> for more details.
1689 To compile this driver as a module, choose M here. The module
1690 will be called tlan.
1692 Please email feedback to <torben.mathiasen@compaq.com>.
1695 tristate "Micrel KSZ8841/42 with generic bus interface"
1696 depends on HAS_IOMEM && DMA_ENGINE
1698 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1699 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1703 tristate "Micrel KS8851 SPI"
1708 SPI driver for Micrel KS8851 SPI attached network chip.
1711 tristate "Micrel KS8851 MLL"
1712 depends on HAS_IOMEM
1715 This platform driver is for Micrel KS8851 Address/data bus
1716 multiplexed network chip.
1719 tristate "VIA Rhine support"
1720 depends on NET_PCI && PCI
1724 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1725 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1726 Ethernet functions can also be found integrated on South Bridges
1729 To compile this driver as a module, choose M here. The module
1730 will be called via-rhine.
1732 config VIA_RHINE_MMIO
1733 bool "Use MMIO instead of PIO"
1734 depends on VIA_RHINE
1736 This instructs the driver to use PCI shared memory (MMIO) instead of
1737 programmed I/O ports (PIO). Enabling this gives an improvement in
1738 processing time in parts of the driver.
1743 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1744 depends on NET_PCI && PCI && EXPERIMENTAL
1747 This is a driver for the Fast Ethernet PCI network cards based on
1748 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1749 have one of these, say Y here.
1751 To compile this driver as a module, choose M here: the module
1752 will be called sc92031. This is recommended.
1755 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1756 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1759 TI AR7 CPMAC Ethernet support
1762 bool "Pocket and portable adapters"
1765 Cute little network (Ethernet) devices which attach to the parallel
1766 port ("pocket adapters"), commonly used with laptops. If you have
1767 one of those, say Y and read the Ethernet-HOWTO, available from
1768 <http://www.tldp.org/docs.html#howto>.
1770 If you want to plug a network (or some other) card into the PCMCIA
1771 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1772 credit card size extension cards used by all modern laptops), you
1773 need the pcmcia-cs package (location contained in the file
1774 <file:Documentation/Changes>) and you can say N here.
1776 Laptop users should read the Linux Laptop home page at
1777 <http://www.linux-on-laptops.com/> or
1778 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1780 Note that the answer to this question doesn't directly affect the
1781 kernel: saying N will just cause the configurator to skip all
1782 the questions about this class of network devices. If you say Y, you
1783 will be asked for your specific device in the following questions.
1786 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1787 depends on NET_POCKET && PARPORT && X86
1790 This is a network (Ethernet) device which attaches to your parallel
1791 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1792 available from <http://www.tldp.org/docs.html#howto>, if you
1793 want to use this. If you intend to use this driver, you should have
1794 said N to the "Parallel printer support", because the two drivers
1795 don't like each other.
1797 To compile this driver as a module, choose M here: the module
1801 tristate "D-Link DE600 pocket adapter support"
1802 depends on NET_POCKET && PARPORT
1804 This is a network (Ethernet) device which attaches to your parallel
1805 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1806 Ethernet-HOWTO, available from
1807 <http://www.tldp.org/docs.html#howto>, if you want to use
1808 this. It is possible to have several devices share a single parallel
1809 port and it is safe to compile the corresponding drivers into the
1812 To compile this driver as a module, choose M here: the module
1813 will be called de600.
1816 tristate "D-Link DE620 pocket adapter support"
1817 depends on NET_POCKET && PARPORT
1819 This is a network (Ethernet) device which attaches to your parallel
1820 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1821 Ethernet-HOWTO, available from
1822 <http://www.tldp.org/docs.html#howto>, if you want to use
1823 this. It is possible to have several devices share a single parallel
1824 port and it is safe to compile the corresponding drivers into the
1827 To compile this driver as a module, choose M here: the module
1828 will be called de620.
1831 tristate "SGI Seeq ethernet controller support"
1832 depends on SGI_HAS_SEEQ
1834 Say Y here if you have an Seeq based Ethernet network card. This is
1835 used in many Silicon Graphics machines.
1838 tristate "DEC LANCE ethernet controller support"
1839 depends on MACH_DECSTATION
1842 This driver is for the series of Ethernet controllers produced by
1843 DEC (now Compaq) based on the AMD Lance chipset, including the
1844 DEPCA series. (This chipset is better known via the NE2100 cards.)
1847 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1848 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1849 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
1850 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
1853 Say Y here if you want to use the built-in 10/100 Fast ethernet
1854 controller on some Motorola ColdFire and Freescale i.MX processors.
1857 tristate "MPC52xx FEC driver"
1858 depends on PPC_MPC52xx && PPC_BESTCOMM
1861 select PPC_BESTCOMM_FEC
1863 This option enables support for the MPC5200's on-chip
1864 Fast Ethernet Controller
1865 If compiled as module, it will be called fec_mpc52xx.
1867 config FEC_MPC52xx_MDIO
1868 bool "MPC52xx FEC MDIO bus driver"
1869 depends on FEC_MPC52xx
1872 The MPC5200's FEC can connect to the Ethernet either with
1873 an external MII PHY chip or 10 Mbps 7-wire interface
1874 (Motorola? industry standard).
1875 If your board uses an external PHY connected to FEC, enable this.
1876 If not sure, enable.
1877 If compiled as module, it will be called fec_mpc52xx_phy.
1880 tristate "NE2000 compatible support for H8/300"
1883 Say Y here if you want to use the NE2000 compatible
1884 controller on the Renesas H8/300 processor.
1887 tristate "Atheros L2 Fast Ethernet support"
1892 This driver supports the Atheros L2 fast ethernet adapter.
1894 To compile this driver as a module, choose M here. The module
1895 will be called atl2.
1897 config XILINX_EMACLITE
1898 tristate "Xilinx 10/100 Ethernet Lite support"
1899 depends on PPC32 || MICROBLAZE
1902 This driver supports the 10/100 Ethernet Lite from Xilinx.
1905 tristate "Broadcom 63xx internal mac support"
1910 This driver supports the ethernet MACs in the Broadcom 63xx
1911 MIPS chipset family (BCM63XX).
1914 tristate "Faraday FTMAC100 10/100 Ethernet support"
1918 This driver supports the FTMAC100 10/100 Ethernet controller
1919 from Faraday. It is used on Faraday A320, Andes AG101 and some
1920 other ARM/NDS32 SoC's.
1923 tristate "Lantiq SoC ETOP driver"
1924 depends on SOC_TYPE_XWAY
1926 Support for the MII0 inside the Lantiq SoC
1929 source "drivers/net/fs_enet/Kconfig"
1931 source "drivers/net/octeon/Kconfig"
1933 endif # NET_ETHERNET
1939 menuconfig NETDEV_1000
1940 bool "Ethernet (1000 Mbit)"
1944 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1945 type of Local Area Network (LAN) in universities and companies.
1947 Say Y here to get to see options for Gigabit Ethernet drivers.
1948 This option alone does not add any kernel code.
1949 Note that drivers supporting both 100 and 1000 MBit may be listed
1950 under "Ethernet (10 or 100MBit)" instead.
1952 If you say N, all options in this submenu will be skipped and disabled.
1957 tristate "DL2000/TC902x-based Gigabit Ethernet support"
1961 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1963 D-Link DGE-550T Gigabit Ethernet Adapter.
1964 D-Link DL2000-based Gigabit Ethernet Adapter.
1965 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1967 To compile this driver as a module, choose M here: the
1968 module will be called dl2k.
1971 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1974 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1975 adapters. For more information on how to identify your adapter, go
1976 to the Adapter & Driver ID Guide at:
1978 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1980 For general information and support, go to the Intel support
1983 <http://support.intel.com>
1985 More specific information on configuring the driver is in
1986 <file:Documentation/networking/e1000.txt>.
1988 To compile this driver as a module, choose M here. The module
1989 will be called e1000.
1992 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
1993 depends on PCI && (!SPARC32 || BROKEN)
1996 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
1997 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
1998 use the regular e1000 driver For more information on how to
1999 identify your adapter, go to the Adapter & Driver ID Guide at:
2001 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2003 For general information and support, go to the Intel support
2006 <http://support.intel.com>
2008 To compile this driver as a module, choose M here. The module
2009 will be called e1000e.
2012 tristate "IP1000 Gigabit Ethernet support"
2013 depends on PCI && EXPERIMENTAL
2016 This driver supports IP1000 gigabit Ethernet cards.
2018 To compile this driver as a module, choose M here: the module
2019 will be called ipg. This is recommended.
2022 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2025 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2026 adapters. For more information on how to identify your adapter, go
2027 to the Adapter & Driver ID Guide at:
2029 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2031 For general information and support, go to the Intel support
2034 <http://support.intel.com>
2036 More specific information on configuring the driver is in
2037 <file:Documentation/networking/e1000.txt>.
2039 To compile this driver as a module, choose M here. The module
2043 bool "Direct Cache Access (DCA) Support"
2045 depends on IGB && DCA && !(IGB=y && DCA=m)
2047 Say Y here if you want to use Direct Cache Access (DCA) in the
2048 driver. DCA is a method for warming the CPU cache before data
2049 is used, with the intent of lessening the impact of cache misses.
2052 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2055 This driver supports Intel(R) 82576 virtual functions. For more
2056 information on how to identify your adapter, go to the Adapter &
2059 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2061 For general information and support, go to the Intel support
2064 <http://support.intel.com>
2066 More specific information on configuring the driver is in
2067 <file:Documentation/networking/e1000.txt>.
2069 To compile this driver as a module, choose M here. The module
2070 will be called igbvf.
2072 source "drivers/net/ixp2000/Kconfig"
2075 tristate "National Semiconductor DP83820 support"
2078 This is a driver for the National Semiconductor DP83820 series
2079 of gigabit ethernet MACs. Cards using this chipset include
2080 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2081 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2085 tristate "Packet Engines Hamachi GNIC-II support"
2089 If you have a Gigabit Ethernet card of this type, say Y and read
2090 the Ethernet-HOWTO, available from
2091 <http://www.tldp.org/docs.html#howto>.
2093 To compile this driver as a module, choose M here. The module will be
2097 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2098 depends on PCI && EXPERIMENTAL
2101 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2102 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2103 used by the Beowulf Linux cluster project. See
2104 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2105 information about this driver in particular and Beowulf in general.
2107 To compile this driver as a module, choose M here: the module
2108 will be called yellowfin. This is recommended.
2111 tristate "Realtek 8169 gigabit ethernet support"
2117 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2119 To compile this driver as a module, choose M here: the module
2120 will be called r8169. This is recommended.
2123 tristate "SB1250 Gigabit Ethernet support"
2124 depends on SIBYTE_SB1xxx_SOC
2127 This driver supports Gigabit Ethernet interfaces based on the
2128 Broadcom SiByte family of System-On-a-Chip parts. They include
2129 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2132 To compile this driver as a module, choose M here: the module
2133 will be called sb1250-mac.
2136 tristate "SiS190/SiS191 gigabit ethernet support"
2141 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2142 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2143 appear in lan on motherboard designs which are based on SiS 965
2144 and SiS 966 south bridge.
2146 To compile this driver as a module, choose M here: the module
2147 will be called sis190. This is recommended.
2150 tristate "Marvell Yukon Gigabit Ethernet support"
2154 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2155 and related Gigabit Ethernet adapters. It is a new smaller driver
2156 with better performance and more complete ethtool support.
2158 It does not support the link failover and network management
2159 features that "portable" vendor supplied sk98lin driver does.
2161 This driver supports adapters based on the original Yukon chipset:
2162 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2163 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2165 It does not support the newer Yukon2 chipset: a separate driver,
2166 sky2, is provided for these adapters.
2168 To compile this driver as a module, choose M here: the module
2169 will be called skge. This is recommended.
2172 bool "Debugging interface"
2173 depends on SKGE && DEBUG_FS
2175 This option adds the ability to dump driver state for debugging.
2176 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2177 transmit and receive rings.
2182 bool "Support for older SysKonnect Genesis boards"
2185 This enables support for the older and uncommon SysKonnect Genesis
2186 chips, which support MII via an external transceiver, instead of
2187 an internal one. Disabling this option will save some memory
2188 by making code smaller. If unsure say Y.
2191 tristate "Marvell Yukon 2 support"
2195 This driver supports Gigabit Ethernet adapters based on the
2196 Marvell Yukon 2 chipset:
2197 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2198 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2200 There is companion driver for the older Marvell Yukon and
2201 SysKonnect Genesis based adapters: skge.
2203 To compile this driver as a module, choose M here: the module
2204 will be called sky2. This is recommended.
2207 bool "Debugging interface"
2208 depends on SKY2 && DEBUG_FS
2210 This option adds the ability to dump driver state for debugging.
2211 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2212 transmit and receive rings.
2217 tristate "VIA Velocity support"
2223 If you have a VIA "Velocity" based network card say Y here.
2225 To compile this driver as a module, choose M here. The module
2226 will be called via-velocity.
2229 tristate "Broadcom Tigon3 support"
2233 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2235 To compile this driver as a module, choose M here: the module
2236 will be called tg3. This is recommended.
2239 tristate "Broadcom NetXtremeII support"
2244 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2246 To compile this driver as a module, choose M here: the module
2247 will be called bnx2. This is recommended.
2250 tristate "Broadcom CNIC support"
2255 This driver supports offload features of Broadcom NetXtremeII
2256 gigabit Ethernet cards.
2258 To compile this driver as a module, choose M here: the module
2259 will be called cnic. This is recommended.
2262 tristate "Spider Gigabit Ethernet driver"
2263 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2266 This driver supports the Gigabit Ethernet chips present on the
2267 Cell Processor-Based Blades from IBM.
2270 tristate "Tundra TSI108 gigabit Ethernet support"
2271 depends on TSI108_BRIDGE
2273 This driver supports Tundra TSI108 gigabit Ethernet ports.
2274 To compile this driver as a module, choose M here: the module
2275 will be called tsi108_eth.
2278 tristate "PS3 Gigabit Ethernet driver"
2280 select PS3_SYS_MANAGER
2282 This driver supports the network device on the PS3 game
2283 console. This driver has built-in support for Ethernet.
2285 To compile this driver as a module, choose M here: the
2286 module will be called ps3_gelic.
2288 config GELIC_WIRELESS
2289 bool "PS3 Wireless support"
2291 depends on GELIC_NET
2294 This option adds the support for the wireless feature of PS3.
2295 If you have the wireless-less model of PS3 or have no plan to
2296 use wireless feature, disabling this option saves memory. As
2297 the driver automatically distinguishes the models, you can
2298 safely enable this option even if you have a wireless-less model.
2301 tristate "Freescale PQ MDIO"
2305 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2308 tristate "Gianfar Ethernet"
2314 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2315 and MPC86xx family of chips, and the FEC on the 8540.
2318 tristate "Freescale QE Gigabit Ethernet"
2319 depends on QUICC_ENGINE
2323 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2324 which is available on some Freescale SOCs.
2326 config UGETH_TX_ON_DEMAND
2327 bool "Transmit on Demand support"
2331 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2332 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2336 This driver supports the gigabit ethernet MACs in the
2337 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2338 in the Marvell Orion ARM SoC family.
2340 Some boards that use the Discovery chipset are the Momenco
2341 Ocelot C and Jaguar ATX and Pegasos II.
2343 config XILINX_LL_TEMAC
2344 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2345 depends on PPC || MICROBLAZE
2348 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2349 core used in Xilinx Spartan and Virtex FPGAs
2352 tristate "QLogic QLA3XXX Network Driver Support"
2355 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2357 To compile this driver as a module, choose M here: the module
2358 will be called qla3xxx.
2361 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2366 This driver supports the Atheros/Attansic L1 gigabit ethernet
2369 To compile this driver as a module, choose M here. The module
2370 will be called atl1.
2373 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2374 depends on PCI && EXPERIMENTAL
2378 This driver supports the Atheros L1E gigabit ethernet adapter.
2380 To compile this driver as a module, choose M here. The module
2381 will be called atl1e.
2384 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2385 depends on PCI && EXPERIMENTAL
2389 This driver supports the Atheros L1C gigabit ethernet adapter.
2391 To compile this driver as a module, choose M here. The module
2392 will be called atl1c.
2395 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2400 This driver supports the PCI-Express gigabit ethernet adapters
2401 based on JMicron JMC250 chipset.
2403 To compile this driver as a module, choose M here. The module
2407 tristate "S6105 GMAC ethernet support"
2408 depends on XTENSA_VARIANT_S6000
2411 This driver supports the on chip ethernet device on the
2412 S6105 xtensa processor.
2414 To compile this driver as a module, choose M here. The module
2415 will be called s6gmac.
2417 source "drivers/net/stmmac/Kconfig"
2420 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
2424 This is a gigabit ethernet driver for EG20T PCH.
2425 EG20T PCH is the platform controller hub that is used in Intel's
2426 general embedded platform.
2427 EG20T PCH has Gigabit Ethernet interface.
2428 Using this interface, it is able to access system devices connected
2429 to Gigabit Ethernet.
2430 This driver enables Gigabit Ethernet function.
2432 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
2433 Output Hub), ML7223.
2434 ML7223 IOH is for MP(Media Phone) use.
2435 ML7223 is companion chip for Intel Atom E6xx series.
2436 ML7223 is completely compatible for Intel EG20T PCH.
2439 tristate "Faraday FTGMAC100 Gigabit Ethernet support"
2443 This driver supports the FTGMAC100 Gigabit Ethernet controller
2444 from Faraday. It is used on Faraday A369, Andes AG102 and some
2445 other ARM/NDS32 SoC's.
2450 # 10 Gigabit Ethernet
2453 menuconfig NETDEV_10000
2454 bool "Ethernet (10000 Mbit)"
2458 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2459 This option alone does not add any kernel code.
2461 If you say N, all options in this submenu will be skipped and disabled.
2469 tristate "Chelsio 10Gb Ethernet support"
2474 This driver supports Chelsio gigabit and 10-gigabit
2475 Ethernet cards. More information about adapter features and
2476 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2478 For general information about Chelsio and our products, visit
2479 our website at <http://www.chelsio.com>.
2481 For customer support, please visit our customer support page at
2482 <http://www.chelsio.com/support.html>.
2484 Please send feedback to <linux-bugs@chelsio.com>.
2486 To compile this driver as a module, choose M here: the module
2487 will be called cxgb.
2489 config CHELSIO_T1_1G
2490 bool "Chelsio gigabit Ethernet support"
2491 depends on CHELSIO_T1
2493 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2494 are using only 10G cards say 'N' here.
2497 tristate "Chelsio Communications T3 10Gb Ethernet support"
2498 depends on PCI && INET
2502 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2505 For general information about Chelsio and our products, visit
2506 our website at <http://www.chelsio.com>.
2508 For customer support, please visit our customer support page at
2509 <http://www.chelsio.com/support.html>.
2511 Please send feedback to <linux-bugs@chelsio.com>.
2513 To compile this driver as a module, choose M here: the module
2514 will be called cxgb3.
2517 tristate "Chelsio Communications T4 Ethernet support"
2522 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2525 For general information about Chelsio and our products, visit
2526 our website at <http://www.chelsio.com>.
2528 For customer support, please visit our customer support page at
2529 <http://www.chelsio.com/support.html>.
2531 Please send feedback to <linux-bugs@chelsio.com>.
2533 To compile this driver as a module choose M here; the module
2534 will be called cxgb4.
2537 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2540 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2541 adapters with PCI-E SR-IOV Virtual Functions.
2543 For general information about Chelsio and our products, visit
2544 our website at <http://www.chelsio.com>.
2546 For customer support, please visit our customer support page at
2547 <http://www.chelsio.com/support.html>.
2549 Please send feedback to <linux-bugs@chelsio.com>.
2551 To compile this driver as a module choose M here; the module
2552 will be called cxgb4vf.
2555 tristate "eHEA Ethernet support"
2556 depends on IBMEBUS && INET && SPARSEMEM
2559 This driver supports the IBM pSeries eHEA ethernet adapter.
2561 To compile the driver as a module, choose M here. The module
2562 will be called ehea.
2565 tristate "Cisco VIC Ethernet NIC Support"
2566 depends on PCI && INET
2568 This enables the support for the Cisco VIC Ethernet card.
2571 tristate "Intel(R) 10GbE PCI Express adapters support"
2572 depends on PCI && INET
2575 This driver supports Intel(R) 10GbE PCI Express family of
2576 adapters. For more information on how to identify your adapter, go
2577 to the Adapter & Driver ID Guide at:
2579 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2581 For general information and support, go to the Intel support
2584 <http://support.intel.com>
2586 To compile this driver as a module, choose M here. The module
2587 will be called ixgbe.
2590 bool "Direct Cache Access (DCA) Support"
2592 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2594 Say Y here if you want to use Direct Cache Access (DCA) in the
2595 driver. DCA is a method for warming the CPU cache before data
2596 is used, with the intent of lessening the impact of cache misses.
2599 bool "Data Center Bridging (DCB) Support"
2601 depends on IXGBE && DCB
2603 Say Y here if you want to use Data Center Bridging (DCB) in the
2609 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2612 This driver supports Intel(R) 82599 virtual functions. For more
2613 information on how to identify your adapter, go to the Adapter &
2616 <http://support.intel.com/support/network/sb/CS-008441.htm>
2618 For general information and support, go to the Intel support
2621 <http://support.intel.com>
2623 More specific information on configuring the driver is in
2624 <file:Documentation/networking/ixgbevf.txt>.
2626 To compile this driver as a module, choose M here. The module
2627 will be called ixgbevf. MSI-X interrupt support is required
2628 for this driver to work correctly.
2631 tristate "Intel(R) PRO/10GbE support"
2634 This driver supports Intel(R) PRO/10GbE family of adapters for
2635 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2636 instead. For more information on how to identify your adapter, go
2637 to the Adapter & Driver ID Guide at:
2639 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2641 For general information and support, go to the Intel support
2644 <http://support.intel.com>
2646 More specific information on configuring the driver is in
2647 <file:Documentation/networking/ixgb.txt>.
2649 To compile this driver as a module, choose M here. The module
2650 will be called ixgb.
2653 tristate "Exar Xframe 10Gb Ethernet Adapter"
2656 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2658 More specific information on configuring the driver is in
2659 <file:Documentation/networking/s2io.txt>.
2661 To compile this driver as a module, choose M here. The module
2662 will be called s2io.
2665 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2666 depends on PCI && INET
2668 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2669 I/O Virtualized Server Adapter.
2671 More specific information on configuring the driver is in
2672 <file:Documentation/networking/vxge.txt>.
2674 To compile this driver as a module, choose M here. The module
2675 will be called vxge.
2677 config VXGE_DEBUG_TRACE_ALL
2678 bool "Enabling All Debug trace statments in driver"
2682 Say Y here if you want to enabling all the debug trace statements in
2683 the vxge driver. By default only few debug trace statements are
2687 tristate "Myricom Myri-10G Ethernet support"
2688 depends on PCI && INET
2693 This driver supports Myricom Myri-10G Dual Protocol interface in
2694 Ethernet mode. If the eeprom on your board is not recent enough,
2695 you will need a newer firmware image.
2696 You may get this image or more information, at:
2698 <http://www.myri.com/scs/download-Myri10GE.html>
2700 To compile this driver as a module, choose M here. The module
2701 will be called myri10ge.
2704 bool "Direct Cache Access (DCA) Support"
2706 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2708 Say Y here if you want to use Direct Cache Access (DCA) in the
2709 driver. DCA is a method for warming the CPU cache before data
2710 is used, with the intent of lessening the impact of cache misses.
2713 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2717 This enables the support for NetXen's Gigabit Ethernet card.
2720 tristate "Sun Neptune 10Gbit Ethernet support"
2724 This enables support for cards based upon Sun's
2728 tristate "PA Semi 1/10Gbit MAC"
2729 depends on PPC_PASEMI && PCI && INET
2733 This driver supports the on-chip 1/10Gbit Ethernet controller on
2734 PA Semi's PWRficient line of chips.
2737 tristate "Mellanox Technologies 10Gbit Ethernet support"
2738 depends on PCI && INET
2742 This driver supports Mellanox Technologies ConnectX Ethernet
2751 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
2752 depends on MLX4_CORE
2755 This option causes debugging code to be compiled into the
2756 mlx4_core driver. The output can be turned on via the
2757 debug_level module parameter (which can also be set after
2758 the driver is loaded through sysfs).
2761 tristate "Tehuti Networks 10G Ethernet"
2764 Tehuti Networks 10G Ethernet NIC
2767 tristate "Broadcom NetXtremeII 10Gb support"
2774 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2775 To compile this driver as a module, choose M here: the module
2776 will be called bnx2x. This is recommended.
2779 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2783 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2787 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2790 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2792 To compile this driver as a module, choose M here: the module
2793 will be called qlge.
2796 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2799 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2801 To compile this driver as a module, choose M here: the module
2804 For general information and support, go to the Brocade support
2807 <http://support.brocade.com>
2809 source "drivers/net/sfc/Kconfig"
2811 source "drivers/net/benet/Kconfig"
2813 endif # NETDEV_10000
2815 source "drivers/net/tokenring/Kconfig"
2817 source "drivers/net/wireless/Kconfig"
2819 source "drivers/net/wimax/Kconfig"
2821 source "drivers/net/usb/Kconfig"
2823 source "drivers/net/pcmcia/Kconfig"
2825 source "drivers/net/wan/Kconfig"
2827 source "drivers/atm/Kconfig"
2829 source "drivers/ieee802154/Kconfig"
2831 source "drivers/s390/net/Kconfig"
2833 source "drivers/net/caif/Kconfig"
2836 tristate "Tilera GBE/XGBE network driver support"
2841 This is a standard Linux network device driver for the
2842 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2844 To compile this driver as a module, choose M here: the module
2845 will be called tile_net.
2847 config XEN_NETDEV_FRONTEND
2848 tristate "Xen network device frontend driver"
2850 select XEN_XENBUS_FRONTEND
2853 This driver provides support for Xen paravirtual network
2854 devices exported by a Xen network driver domain (often
2857 The corresponding Linux backend driver is enabled by the
2858 CONFIG_XEN_NETDEV_BACKEND option.
2860 If you are compiling a kernel for use as Xen guest, you
2861 should say Y here. To compile this driver as a module, chose
2862 M here: the module will be called xen-netfront.
2864 config XEN_NETDEV_BACKEND
2865 tristate "Xen backend network device"
2866 depends on XEN_BACKEND
2868 This driver allows the kernel to act as a Xen network driver
2869 domain which exports paravirtual network devices to other
2870 Xen domains. These devices can be accessed by any operating
2871 system that implements a compatible front end.
2873 The corresponding Linux frontend driver is enabled by the
2874 CONFIG_XEN_NETDEV_FRONTEND configuration option.
2876 The backend driver presents a standard network device
2877 endpoint for each paravirtual network device to the driver
2878 domain network stack. These can then be bridged or routed
2879 etc in order to provide full network connectivity.
2881 If you are compiling a kernel to run in a Xen network driver
2882 domain (often this is domain 0) you should say Y here. To
2883 compile this driver as a module, chose M here: the module
2884 will be called xen-netback.
2887 tristate "iSeries Virtual Ethernet driver support"
2888 depends on PPC_ISERIES
2891 tristate "RapidIO Ethernet over messaging driver support"
2894 config RIONET_TX_SIZE
2895 int "Number of outbound queue entries"
2899 config RIONET_RX_SIZE
2900 int "Number of inbound queue entries"
2905 tristate "FDDI driver support"
2906 depends on (PCI || EISA || TC)
2908 Fiber Distributed Data Interface is a high speed local area network
2909 design; essentially a replacement for high speed Ethernet. FDDI can
2910 run over copper or fiber. If you are connected to such a network and
2911 want a driver for the FDDI card in your computer, say Y here (and
2912 then also Y to the driver for your FDDI card, below). Most people
2916 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2917 depends on FDDI && (PCI || EISA || TC)
2919 This is support for the DIGITAL series of TURBOchannel (DEFTA),
2920 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2921 to a local FDDI network.
2923 To compile this driver as a module, choose M here: the module
2924 will be called defxx. If unsure, say N.
2928 prompt "Use MMIO instead of PIO" if PCI || EISA
2930 default n if PCI || EISA
2933 This instructs the driver to use EISA or PCI memory-mapped I/O
2934 (MMIO) as appropriate instead of programmed I/O ports (PIO).
2935 Enabling this gives an improvement in processing time in parts
2936 of the driver, but it may cause problems with EISA (DEFEA)
2937 adapters. TURBOchannel does not have the concept of I/O ports,
2938 so MMIO is always used for these (DEFTA) adapters.
2943 tristate "SysKonnect FDDI PCI support"
2944 depends on FDDI && PCI
2947 Say Y here if you have a SysKonnect FDDI PCI adapter.
2948 The following adapters are supported by this driver:
2949 - SK-5521 (SK-NET FDDI-UP)
2950 - SK-5522 (SK-NET FDDI-UP DAS)
2951 - SK-5541 (SK-NET FDDI-FP)
2952 - SK-5543 (SK-NET FDDI-LP)
2953 - SK-5544 (SK-NET FDDI-LP DAS)
2954 - SK-5821 (SK-NET FDDI-UP64)
2955 - SK-5822 (SK-NET FDDI-UP64 DAS)
2956 - SK-5841 (SK-NET FDDI-FP64)
2957 - SK-5843 (SK-NET FDDI-LP64)
2958 - SK-5844 (SK-NET FDDI-LP64 DAS)
2959 - Netelligent 100 FDDI DAS Fibre SC
2960 - Netelligent 100 FDDI SAS Fibre SC
2961 - Netelligent 100 FDDI DAS UTP
2962 - Netelligent 100 FDDI SAS UTP
2963 - Netelligent 100 FDDI SAS Fibre MIC
2965 Read <file:Documentation/networking/skfp.txt> for information about
2968 Questions concerning this driver can be addressed to:
2969 <linux@syskonnect.de>
2971 To compile this driver as a module, choose M here: the module
2972 will be called skfp. This is recommended.
2975 bool "HIPPI driver support (EXPERIMENTAL)"
2976 depends on EXPERIMENTAL && INET && PCI
2978 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2979 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2980 can run over copper (25m) or fiber (300m on multi-mode or 10km on
2981 single-mode). HIPPI networks are commonly used for clusters and to
2982 connect to super computers. If you are connected to a HIPPI network
2983 and have a HIPPI network card in your computer that you want to use
2984 under Linux, say Y here (you must also remember to enable the driver
2985 for your HIPPI card below). Most people will say N here.
2988 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2989 depends on HIPPI && PCI
2991 Say Y here if this is your PCI HIPPI network card.
2993 To compile this driver as a module, choose M here: the module
2994 will be called rrunner. If unsure, say N.
2996 config ROADRUNNER_LARGE_RINGS
2997 bool "Use large TX/RX rings (EXPERIMENTAL)"
2998 depends on ROADRUNNER
3000 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3001 of additional memory to allow for fastest operation, both for
3002 transmitting and receiving. This memory cannot be used by any other
3003 kernel code or by user space programs. Say Y here only if you have
3007 tristate "PLIP (parallel port) support"
3010 PLIP (Parallel Line Internet Protocol) is used to create a
3011 reasonably fast mini network consisting of two (or, rarely, more)
3012 local machines. A PLIP link from a Linux box is a popular means to
3013 install a Linux distribution on a machine which doesn't have a
3014 CD-ROM drive (a minimal system has to be transferred with floppies
3015 first). The kernels on both machines need to have this PLIP option
3016 enabled for this to work.
3018 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3019 ports (the connectors at the computers with 25 holes) are connected
3020 with "null printer" or "Turbo Laplink" cables which can transmit 4
3021 bits at a time (mode 0) or with special PLIP cables, to be used on
3022 bidirectional parallel ports only, which can transmit 8 bits at a
3023 time (mode 1); you can find the wiring of these cables in
3024 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3025 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3026 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3027 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3028 and winsock or NCSA's telnet.
3030 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3031 as the NET-3-HOWTO, both available from
3032 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3033 protocol has been changed and this PLIP driver won't work together
3034 with the PLIP support in Linux versions 1.0.x. This option enlarges
3035 your kernel by about 8 KB.
3037 To compile this driver as a module, choose M here. The module
3038 will be called plip. If unsure, say Y or M, in case you buy
3042 tristate "PPP (point-to-point protocol) support"
3045 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3046 the same purpose: sending Internet traffic over telephone (and other
3047 serial) lines. Ask your access provider if they support it, because
3048 otherwise you can't use it; most Internet access providers these
3049 days support PPP rather than SLIP.
3051 To use PPP, you need an additional program called pppd as described
3052 in the PPP-HOWTO, available at
3053 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3054 the version of pppd recommended in <file:Documentation/Changes>.
3055 The PPP option enlarges your kernel by about 16 KB.
3057 There are actually two versions of PPP: the traditional PPP for
3058 asynchronous lines, such as regular analog phone lines, and
3059 synchronous PPP which can be used over digital ISDN lines for
3060 example. If you want to use PPP over phone lines or other
3061 asynchronous serial lines, you need to say Y (or M) here and also to
3062 the next option, "PPP support for async serial ports". For PPP over
3063 synchronous lines, you should say Y (or M) here and to "Support
3064 synchronous PPP", below.
3066 If you said Y to "Version information on all symbols" above, then
3067 you cannot compile the PPP driver into the kernel; you can then only
3068 compile it as a module. To compile this driver as a module, choose M
3069 here. The module will be called ppp_generic.
3071 config PPP_MULTILINK
3072 bool "PPP multilink support (EXPERIMENTAL)"
3073 depends on PPP && EXPERIMENTAL
3075 PPP multilink is a protocol (defined in RFC 1990) which allows you
3076 to combine several (logical or physical) lines into one logical PPP
3077 connection, so that you can utilize your full bandwidth.
3079 This has to be supported at the other end as well and you need a
3080 version of the pppd daemon which understands the multilink protocol.
3085 bool "PPP filtering"
3088 Say Y here if you want to be able to filter the packets passing over
3089 PPP interfaces. This allows you to control which packets count as
3090 activity (i.e. which packets will reset the idle timer or bring up
3091 a demand-dialed link) and which packets are to be dropped entirely.
3092 You need to say Y here if you wish to use the pass-filter and
3093 active-filter options to pppd.
3098 tristate "PPP support for async serial ports"
3102 Say Y (or M) here if you want to be able to use PPP over standard
3103 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3104 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3107 To compile this driver as a module, choose M here.
3112 tristate "PPP support for sync tty ports"
3115 Say Y (or M) here if you want to be able to use PPP over synchronous
3116 (HDLC) tty devices, such as the SyncLink adapter. These devices
3117 are often used for high-speed leased lines like T1/E1.
3119 To compile this driver as a module, choose M here.
3122 tristate "PPP Deflate compression"
3127 Support for the Deflate compression method for PPP, which uses the
3128 Deflate algorithm (the same algorithm that gzip uses) to compress
3129 each PPP packet before it is sent over the wire. The machine at the
3130 other end of the PPP link (usually your ISP) has to support the
3131 Deflate compression method as well for this to be useful. Even if
3132 they don't support it, it is safe to say Y here.
3134 To compile this driver as a module, choose M here.
3137 tristate "PPP BSD-Compress compression"
3140 Support for the BSD-Compress compression method for PPP, which uses
3141 the LZW compression method to compress each PPP packet before it is
3142 sent over the wire. The machine at the other end of the PPP link
3143 (usually your ISP) has to support the BSD-Compress compression
3144 method as well for this to be useful. Even if they don't support it,
3145 it is safe to say Y here.
3147 The PPP Deflate compression method ("PPP Deflate compression",
3148 above) is preferable to BSD-Compress, because it compresses better
3151 Note that the BSD compression code will always be compiled as a
3152 module; it is called bsd_comp and will show up in the directory
3153 modules once you have said "make modules". If unsure, say N.
3156 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3157 depends on PPP && EXPERIMENTAL
3163 Support for the MPPE Encryption protocol, as employed by the
3164 Microsoft Point-to-Point Tunneling Protocol.
3166 See http://pptpclient.sourceforge.net/ for information on
3167 configuring PPTP clients and servers to utilize this method.
3170 tristate "PPP over Ethernet (EXPERIMENTAL)"
3171 depends on EXPERIMENTAL && PPP
3173 Support for PPP over Ethernet.
3175 This driver requires the latest version of pppd from the CVS
3176 repository at cvs.samba.org. Alternatively, see the
3177 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3178 which contains instruction on how to use this driver (under
3179 the heading "Kernel mode PPPoE").
3182 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3183 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3185 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3187 This driver requires pppd plugin to work in client mode or
3188 modified pptpd (poptop) to work in server mode.
3189 See http://accel-pptp.sourceforge.net/ for information how to
3190 utilize this module.
3193 tristate "PPP over ATM"
3194 depends on ATM && PPP
3196 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3197 This implementation does not yet comply with section 8 of RFC2364,
3198 which can lead to bad results if the ATM peer loses state and
3199 changes its encapsulation unilaterally.
3202 tristate "PPP over L2TP (EXPERIMENTAL)"
3203 depends on EXPERIMENTAL && L2TP && PPP
3205 Support for PPP-over-L2TP socket family. L2TP is a protocol
3206 used by ISPs and enterprises to tunnel PPP traffic over UDP
3207 tunnels. L2TP is replacing PPTP for VPN uses.
3210 tristate "SLIP (serial line) support"
3212 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3213 connect to your Internet service provider or to connect to some
3214 other local Unix box or if you want to configure your Linux box as a
3215 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3216 Internet Protocol) is a protocol used to send Internet traffic over
3217 serial connections such as telephone lines or null modem cables;
3218 nowadays, the protocol PPP is more commonly used for this same
3221 Normally, your access provider has to support SLIP in order for you
3222 to be able to use it, but there is now a SLIP emulator called SLiRP
3223 around (available from
3224 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3225 allows you to use SLIP over a regular dial up shell connection. If
3226 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3227 NET-3-HOWTO, available from
3228 <http://www.tldp.org/docs.html#howto>, explains how to
3229 configure SLIP. Note that you don't need this option if you just
3230 want to run term (term is a program which gives you almost full
3231 Internet connectivity if you have a regular dial up shell account on
3232 some Internet connected Unix computer. Read
3233 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3234 support will enlarge your kernel by about 4 KB. If unsure, say N.
3236 To compile this driver as a module, choose M here. The module
3237 will be called slip.
3239 config SLIP_COMPRESSED
3240 bool "CSLIP compressed headers"
3244 This protocol is faster than SLIP because it uses compression on the
3245 TCP/IP headers (not on the data itself), but it has to be supported
3246 on both ends. Ask your access provider if you are not sure and
3247 answer Y, just in case. You will still be able to use plain SLIP. If
3248 you plan to use SLiRP, the SLIP emulator (available from
3249 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3250 allows you to use SLIP over a regular dial up shell connection, you
3251 definitely want to say Y here. The NET-3-HOWTO, available from
3252 <http://www.tldp.org/docs.html#howto>, explains how to configure
3253 CSLIP. This won't enlarge your kernel.
3258 This option enables Van Jacobsen serial line header compression
3262 bool "Keepalive and linefill"
3265 Adds additional capabilities to the SLIP driver to support the
3266 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3269 config SLIP_MODE_SLIP6
3270 bool "Six bit SLIP encapsulation"
3273 Just occasionally you may need to run IP over hostile serial
3274 networks that don't pass all control characters or are only seven
3275 bit. Saying Y here adds an extra mode you can use with SLIP:
3276 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3277 the serial device. Naturally, this has to be supported at the other
3278 end of the link as well. It's good enough, for example, to run IP
3279 over the async ports of a Camtec JNT Pad. If unsure, say N.
3282 bool "Fibre Channel driver support"
3283 depends on SCSI && PCI
3285 Fibre Channel is a high speed serial protocol mainly used to connect
3286 large storage devices to the computer; it is compatible with and
3287 intended to replace SCSI.
3289 If you intend to use Fibre Channel, you need to have a Fibre channel
3290 adaptor card in your computer; say Y here and to the driver for your
3291 adaptor below. You also should have said Y to "SCSI support" and
3292 "SCSI generic support".
3295 tristate "Network console logging support"
3297 If you want to log kernel messages over the network, enable this.
3298 See <file:Documentation/networking/netconsole.txt> for details.
3300 config NETCONSOLE_DYNAMIC
3301 bool "Dynamic reconfiguration of logging targets"
3302 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
3303 !(NETCONSOLE=y && CONFIGFS_FS=m)
3305 This option enables the ability to dynamically reconfigure target
3306 parameters (interface, IP addresses, port numbers, MAC addresses)
3307 at runtime through a userspace interface exported using configfs.
3308 See <file:Documentation/networking/netconsole.txt> for details.
3314 bool "Netpoll traffic trapping"
3318 config NET_POLL_CONTROLLER
3322 tristate "Virtio network driver (EXPERIMENTAL)"
3323 depends on EXPERIMENTAL && VIRTIO
3325 This is the virtual network driver for virtio. It can be used with
3326 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3329 tristate "VMware VMXNET3 ethernet driver"
3330 depends on PCI && INET
3332 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3333 To compile this driver as a module, choose M here: the
3334 module will be called vmxnet3.