xref: /openbmc/linux/drivers/net/Kconfig (revision 82ced6fd)
1
2#
3# Network device configuration
4#
5
6menuconfig NETDEVICES
7	default y if UML
8	depends on NET
9	bool "Network device support"
10	---help---
11	  You can say N here if you don't intend to connect your Linux box to
12	  any other computer at all.
13
14	  You'll have to say Y if your computer contains a network card that
15	  you want to use under Linux. If you are going to run SLIP or PPP over
16	  telephone line or null modem cable you need say Y here. Connecting
17	  two machines with parallel ports using PLIP needs this, as well as
18	  AX.25/KISS for sending Internet traffic over amateur radio links.
19
20	  See also "The Linux Network Administrator's Guide" by Olaf Kirch and
21	  Terry Dawson. Available at <http://www.tldp.org/guides.html>.
22
23	  If unsure, say Y.
24
25# All the following symbols are dependent on NETDEVICES - do not repeat
26# that for each of the symbols.
27if NETDEVICES
28
29config COMPAT_NET_DEV_OPS
30       default y
31       bool "Enable older network device API compatibility"
32       ---help---
33          This option enables kernel compatibility with older network devices
34          that do not use net_device_ops interface.
35
36	  If unsure, say Y.
37
38config IFB
39	tristate "Intermediate Functional Block support"
40	depends on NET_CLS_ACT
41	---help---
42	  This is an intermediate driver that allows sharing of
43	  resources.
44	  To compile this driver as a module, choose M here: the module
45	  will be called ifb.  If you want to use more than one ifb
46	  device at a time, you need to compile this driver as a module.
47	  Instead of 'ifb', the devices will then be called 'ifb0',
48	  'ifb1' etc.
49	  Look at the iproute2 documentation directory for usage etc
50
51config DUMMY
52	tristate "Dummy net driver support"
53	---help---
54	  This is essentially a bit-bucket device (i.e. traffic you send to
55	  this device is consigned into oblivion) with a configurable IP
56	  address. It is most commonly used in order to make your currently
57	  inactive SLIP address seem like a real address for local programs.
58	  If you use SLIP or PPP, you might want to say Y here. Since this
59	  thing often comes in handy, the default is Y. It won't enlarge your
60	  kernel either. What a deal. Read about it in the Network
61	  Administrator's Guide, available from
62	  <http://www.tldp.org/docs.html#guide>.
63
64	  To compile this driver as a module, choose M here: the module
65	  will be called dummy.  If you want to use more than one dummy
66	  device at a time, you need to compile this driver as a module.
67	  Instead of 'dummy', the devices will then be called 'dummy0',
68	  'dummy1' etc.
69
70config BONDING
71	tristate "Bonding driver support"
72	depends on INET
73	depends on IPV6 || IPV6=n
74	---help---
75	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
76	  Channels together. This is called 'Etherchannel' by Cisco,
77	  'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
78
79	  The driver supports multiple bonding modes to allow for both high
80	  performance and high availability operation.
81
82	  Refer to <file:Documentation/networking/bonding.txt> for more
83	  information.
84
85	  To compile this driver as a module, choose M here: the module
86	  will be called bonding.
87
88config MACVLAN
89	tristate "MAC-VLAN support (EXPERIMENTAL)"
90	depends on EXPERIMENTAL
91	---help---
92	  This allows one to create virtual interfaces that map packets to
93	  or from specific MAC addresses to a particular interface.
94
95	  Macvlan devices can be added using the "ip" command from the
96	  iproute2 package starting with the iproute2-2.6.23 release:
97
98	  "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
99
100	  To compile this driver as a module, choose M here: the module
101	  will be called macvlan.
102
103config EQUALIZER
104	tristate "EQL (serial line load balancing) support"
105	---help---
106	  If you have two serial connections to some other computer (this
107	  usually requires two modems and two telephone lines) and you use
108	  SLIP (the protocol for sending Internet traffic over telephone
109	  lines) or PPP (a better SLIP) on them, you can make them behave like
110	  one double speed connection using this driver.  Naturally, this has
111	  to be supported at the other end as well, either with a similar EQL
112	  Linux driver or with a Livingston Portmaster 2e.
113
114	  Say Y if you want this and read
115	  <file:Documentation/networking/eql.txt>.  You may also want to read
116	  section 6.2 of the NET-3-HOWTO, available from
117	  <http://www.tldp.org/docs.html#howto>.
118
119	  To compile this driver as a module, choose M here: the module
120	  will be called eql.  If unsure, say N.
121
122config TUN
123	tristate "Universal TUN/TAP device driver support"
124	select CRC32
125	---help---
126	  TUN/TAP provides packet reception and transmission for user space
127	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
128	  device, which instead of receiving packets from a physical media,
129	  receives them from user space program and instead of sending packets
130	  via physical media writes them to the user space program.
131
132	  When a program opens /dev/net/tun, driver creates and registers
133	  corresponding net device tunX or tapX.  After a program closed above
134	  devices, driver will automatically delete tunXX or tapXX device and
135	  all routes corresponding to it.
136
137	  Please read <file:Documentation/networking/tuntap.txt> for more
138	  information.
139
140	  To compile this driver as a module, choose M here: the module
141	  will be called tun.
142
143	  If you don't know what to use this for, you don't need it.
144
145config VETH
146	tristate "Virtual ethernet pair device"
147	---help---
148	  This device is a local ethernet tunnel. Devices are created in pairs.
149	  When one end receives the packet it appears on its pair and vice
150	  versa.
151
152config NET_SB1000
153	tristate "General Instruments Surfboard 1000"
154	depends on PNP
155	---help---
156	  This is a driver for the General Instrument (also known as
157	  NextLevel) SURFboard 1000 internal
158	  cable modem. This is an ISA card which is used by a number of cable
159	  TV companies to provide cable modem access. It's a one-way
160	  downstream-only cable modem, meaning that your upstream net link is
161	  provided by your regular phone modem.
162
163	  At present this driver only compiles as a module, so say M here if
164	  you have this card. The module will be called sb1000. Then read
165	  <file:Documentation/networking/README.sb1000> for information on how
166	  to use this module, as it needs special ppp scripts for establishing
167	  a connection. Further documentation and the necessary scripts can be
168	  found at:
169
170	  <http://www.jacksonville.net/~fventuri/>
171	  <http://home.adelphia.net/~siglercm/sb1000.html>
172	  <http://linuxpower.cx/~cable/>
173
174	  If you don't have this card, of course say N.
175
176source "drivers/net/arcnet/Kconfig"
177
178source "drivers/net/phy/Kconfig"
179
180#
181#	Ethernet
182#
183
184menuconfig NET_ETHERNET
185	bool "Ethernet (10 or 100Mbit)"
186	depends on !UML
187	---help---
188	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
189	  type of Local Area Network (LAN) in universities and companies.
190
191	  Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
192	  coaxial cable, linking computers in a chain), 10BASE-T or twisted
193	  pair (10 Mbps over twisted pair cable, linking computers to central
194	  hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
195	  100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
196	  100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
197	  cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
198	  [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
199	  Ethernet (1 Gbps over optical fiber or short copper links).
200
201	  If your Linux machine will be connected to an Ethernet and you have
202	  an Ethernet network interface card (NIC) installed in your computer,
203	  say Y here and read the Ethernet-HOWTO, available from
204	  <http://www.tldp.org/docs.html#howto>. You will then also have
205	  to say Y to the driver for your particular NIC.
206
207	  Note that the answer to this question won't directly affect the
208	  kernel: saying N will just cause the configurator to skip all
209	  the questions about Ethernet network cards. If unsure, say N.
210
211if NET_ETHERNET
212
213config MII
214	tristate "Generic Media Independent Interface device support"
215	help
216	  Most ethernet controllers have MII transceiver either as an external
217	  or internal device.  It is safe to say Y or M here even if your
218	  ethernet card lack MII.
219
220config MACB
221	tristate "Atmel MACB support"
222	depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91CAP9
223	select PHYLIB
224	help
225	  The Atmel MACB ethernet interface is found on many AT32 and AT91
226	  parts. Say Y to include support for the MACB chip.
227
228	  To compile this driver as a module, choose M here: the module
229	  will be called macb.
230
231source "drivers/net/arm/Kconfig"
232
233config AX88796
234	tristate "ASIX AX88796 NE2000 clone support"
235	depends on ARM || MIPS || SUPERH
236	select CRC32
237	select MII
238	help
239	  AX88796 driver, using platform bus to provide
240	  chip detection and resources
241
242config AX88796_93CX6
243	bool "ASIX AX88796 external 93CX6 eeprom support"
244	depends on AX88796
245	select EEPROM_93CX6
246	help
247	  Select this if your platform comes with an external 93CX6 eeprom.
248
249config MACE
250	tristate "MACE (Power Mac ethernet) support"
251	depends on PPC_PMAC && PPC32
252	select CRC32
253	help
254	  Power Macintoshes and clones with Ethernet built-in on the
255	  motherboard will usually use a MACE (Medium Access Control for
256	  Ethernet) interface. Say Y to include support for the MACE chip.
257
258	  To compile this driver as a module, choose M here: the module
259	  will be called mace.
260
261config MACE_AAUI_PORT
262	bool "Use AAUI port instead of TP by default"
263	depends on MACE
264	help
265	  Some Apple machines (notably the Apple Network Server) which use the
266	  MACE ethernet chip have an Apple AUI port (small 15-pin connector),
267	  instead of an 8-pin RJ45 connector for twisted-pair ethernet.  Say
268	  Y here if you have such a machine.  If unsure, say N.
269	  The driver will default to AAUI on ANS anyway, and if you use it as
270	  a module, you can provide the port_aaui=0|1 to force the driver.
271
272config BMAC
273	tristate "BMAC (G3 ethernet) support"
274	depends on PPC_PMAC && PPC32
275	select CRC32
276	help
277	  Say Y for support of BMAC Ethernet interfaces. These are used on G3
278	  computers.
279
280	  To compile this driver as a module, choose M here: the module
281	  will be called bmac.
282
283config ARIADNE
284	tristate "Ariadne support"
285	depends on ZORRO
286	help
287	  If you have a Village Tronic Ariadne Ethernet adapter, say Y.
288	  Otherwise, say N.
289
290	  To compile this driver as a module, choose M here: the module
291	  will be called ariadne.
292
293config A2065
294	tristate "A2065 support"
295	depends on ZORRO
296	select CRC32
297	help
298	  If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
299	  say N.
300
301	  To compile this driver as a module, choose M here: the module
302	  will be called a2065.
303
304config HYDRA
305	tristate "Hydra support"
306	depends on ZORRO
307	select CRC32
308	help
309	  If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
310
311	  To compile this driver as a module, choose M here: the module
312	  will be called hydra.
313
314config ZORRO8390
315	tristate "Zorro NS8390-based Ethernet support"
316	depends on ZORRO
317	select CRC32
318	help
319	  This driver is for Zorro Ethernet cards using an NS8390-compatible
320	  chipset, like the Village Tronic Ariadne II and the Individual
321	  Computers X-Surf Ethernet cards. If you have such a card, say Y.
322	  Otherwise, say N.
323
324	  To compile this driver as a module, choose M here: the module
325	  will be called zorro8390.
326
327config APNE
328	tristate "PCMCIA NE2000 support"
329	depends on AMIGA_PCMCIA
330	select CRC32
331	help
332	  If you have a PCMCIA NE2000 compatible adapter, say Y.  Otherwise,
333	  say N.
334
335	  To compile this driver as a module, choose M here: the module
336	  will be called apne.
337
338config MAC8390
339	bool "Macintosh NS 8390 based ethernet cards"
340	depends on MAC
341	select CRC32
342	help
343	  If you want to include a driver to support Nubus or LC-PDS
344	  Ethernet cards using an NS8390 chipset or its equivalent, say Y
345	  and read the Ethernet-HOWTO, available from
346	  <http://www.tldp.org/docs.html#howto>.
347
348config MAC89x0
349	tristate "Macintosh CS89x0 based ethernet cards"
350	depends on MAC
351	---help---
352	  Support for CS89x0 chipset based Ethernet cards.  If you have a
353	  Nubus or LC-PDS network (Ethernet) card of this type, say Y and
354	  read the Ethernet-HOWTO, available from
355	  <http://www.tldp.org/docs.html#howto>.
356
357	  To compile this driver as a module, choose M here. This module will
358	  be called mac89x0.
359
360config MACSONIC
361	tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
362	depends on MAC
363	---help---
364	  Support for NatSemi SONIC based Ethernet devices.  This includes
365	  the onboard Ethernet in many Quadras as well as some LC-PDS,
366	  a few Nubus and all known Comm Slot Ethernet cards.  If you have
367	  one of these say Y and read the Ethernet-HOWTO, available from
368	  <http://www.tldp.org/docs.html#howto>.
369
370	  To compile this driver as a module, choose M here. This module will
371	  be called macsonic.
372
373config MACMACE
374	bool "Macintosh (AV) onboard MACE ethernet"
375	depends on MAC
376	select CRC32
377	help
378	  Support for the onboard AMD 79C940 MACE Ethernet controller used in
379	  the 660AV and 840AV Macintosh.  If you have one of these Macintoshes
380	  say Y and read the Ethernet-HOWTO, available from
381	  <http://www.tldp.org/docs.html#howto>.
382
383config MVME147_NET
384	tristate "MVME147 (Lance) Ethernet support"
385	depends on MVME147
386	select CRC32
387	help
388	  Support for the on-board Ethernet interface on the Motorola MVME147
389	  single-board computer.  Say Y here to include the
390	  driver for this chip in your kernel.
391	  To compile this driver as a module, choose M here.
392
393config MVME16x_NET
394	tristate "MVME16x Ethernet support"
395	depends on MVME16x
396	help
397	  This is the driver for the Ethernet interface on the Motorola
398	  MVME162, 166, 167, 172 and 177 boards.  Say Y here to include the
399	  driver for this chip in your kernel.
400	  To compile this driver as a module, choose M here.
401
402config BVME6000_NET
403	tristate "BVME6000 Ethernet support"
404	depends on BVME6000
405	help
406	  This is the driver for the Ethernet interface on BVME4000 and
407	  BVME6000 VME boards.  Say Y here to include the driver for this chip
408	  in your kernel.
409	  To compile this driver as a module, choose M here.
410
411config ATARILANCE
412	tristate "Atari Lance support"
413	depends on ATARI
414	help
415	  Say Y to include support for several Atari Ethernet adapters based
416	  on the AMD Lance chipset: RieblCard (with or without battery), or
417	  PAMCard VME (also the version by Rhotron, with different addresses).
418
419config SUN3LANCE
420	tristate "Sun3/Sun3x on-board LANCE support"
421	depends on SUN3 || SUN3X
422	help
423	  Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
424	  featured an AMD Lance 10Mbit Ethernet controller on board; say Y
425	  here to compile in the Linux driver for this and enable Ethernet.
426	  General Linux information on the Sun 3 and 3x series (now
427	  discontinued) is at
428	  <http://www.angelfire.com/ca2/tech68k/sun3.html>.
429
430	  If you're not building a kernel for a Sun 3, say N.
431
432config SUN3_82586
433	bool "Sun3 on-board Intel 82586 support"
434	depends on SUN3
435	help
436	  This driver enables support for the on-board Intel 82586 based
437	  Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards.  Note
438	  that this driver does not support 82586-based adapters on additional
439	  VME boards.
440
441config HPLANCE
442	bool "HP on-board LANCE support"
443	depends on DIO
444	select CRC32
445	help
446	  If you want to use the builtin "LANCE" Ethernet controller on an
447	  HP300 machine, say Y here.
448
449config LASI_82596
450	tristate "Lasi ethernet"
451	depends on GSC
452	help
453	  Say Y here to support the builtin Intel 82596 ethernet controller
454	  found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
455
456config SNI_82596
457	tristate "SNI RM ethernet"
458	depends on NET_ETHERNET && SNI_RM
459	help
460	  Say Y here to support the on-board Intel 82596 ethernet controller
461	  built into SNI RM machines.
462
463config KORINA
464	tristate "Korina (IDT RC32434) Ethernet support"
465	depends on NET_ETHERNET && MIKROTIK_RB532
466	help
467	  If you have a Mikrotik RouterBoard 500 or IDT RC32434
468	  based system say Y. Otherwise say N.
469
470config MIPS_JAZZ_SONIC
471	tristate "MIPS JAZZ onboard SONIC Ethernet support"
472	depends on MACH_JAZZ
473	help
474	  This is the driver for the onboard card of MIPS Magnum 4000,
475	  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
476
477config XTENSA_XT2000_SONIC
478	tristate "Xtensa XT2000 onboard SONIC Ethernet support"
479	depends on XTENSA_PLATFORM_XT2000
480	help
481	  This is the driver for the onboard card of the Xtensa XT2000 board.
482
483config MIPS_AU1X00_ENET
484	bool "MIPS AU1000 Ethernet support"
485	depends on SOC_AU1X00
486	select PHYLIB
487	select CRC32
488	help
489	  If you have an Alchemy Semi AU1X00 based system
490	  say Y.  Otherwise, say N.
491
492config SGI_IOC3_ETH
493	bool "SGI IOC3 Ethernet"
494	depends on PCI && SGI_IP27
495	select CRC32
496	select MII
497	help
498	  If you have a network (Ethernet) card of this type, say Y and read
499	  the Ethernet-HOWTO, available from
500	  <http://www.tldp.org/docs.html#howto>.
501
502config MIPS_SIM_NET
503	tristate "MIPS simulator Network device"
504	depends on MIPS_SIM
505	help
506	  The MIPSNET device is a simple Ethernet network device which is
507	  emulated by the MIPS Simulator.
508	  If you are not using a MIPSsim or are unsure, say N.
509
510config SGI_O2MACE_ETH
511	tristate "SGI O2 MACE Fast Ethernet support"
512	depends on SGI_IP32=y
513
514config STNIC
515	tristate "National DP83902AV  support"
516	depends on SUPERH
517	select CRC32
518	help
519	  Support for cards based on the National Semiconductor DP83902AV
520	  ST-NIC Serial Network Interface Controller for Twisted Pair.  This
521	  is a 10Mbit/sec Ethernet controller.  Product overview and specs at
522	  <http://www.national.com/pf/DP/DP83902A.html>.
523
524	  If unsure, say N.
525
526config SH_ETH
527	tristate "Renesas SuperH Ethernet support"
528	depends on SUPERH && \
529		(CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || \
530		 CPU_SUBTYPE_SH7619)
531	select CRC32
532	select MII
533	select MDIO_BITBANG
534	select PHYLIB
535	help
536	  Renesas SuperH Ethernet device driver.
537	  This driver support SH7710, SH7712, SH7763 and SH7619.
538
539config SUNLANCE
540	tristate "Sun LANCE support"
541	depends on SBUS
542	select CRC32
543	help
544	  This driver supports the "le" interface present on all 32-bit Sparc
545	  systems, on some older Ultra systems and as an Sbus option.  These
546	  cards are based on the AMD Lance chipset, which is better known
547	  via the NE2100 cards.
548
549	  To compile this driver as a module, choose M here: the module
550	  will be called sunlance.
551
552config HAPPYMEAL
553	tristate "Sun Happy Meal 10/100baseT support"
554	depends on SBUS || PCI
555	select CRC32
556	help
557	  This driver supports the "hme" interface present on most Ultra
558	  systems and as an option on older Sbus systems. This driver supports
559	  both PCI and Sbus devices. This driver also supports the "qfe" quad
560	  100baseT device available in both PCI and Sbus configurations.
561
562	  To compile this driver as a module, choose M here: the module
563	  will be called sunhme.
564
565config SUNBMAC
566	tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
567	depends on SBUS && EXPERIMENTAL
568	select CRC32
569	help
570	  This driver supports the "be" interface available as an Sbus option.
571	  This is Sun's older 100baseT Ethernet device.
572
573	  To compile this driver as a module, choose M here: the module
574	  will be called sunbmac.
575
576config SUNQE
577	tristate "Sun QuadEthernet support"
578	depends on SBUS
579	select CRC32
580	help
581	  This driver supports the "qe" 10baseT Ethernet device, available as
582	  an Sbus option. Note that this is not the same as Quad FastEthernet
583	  "qfe" which is supported by the Happy Meal driver instead.
584
585	  To compile this driver as a module, choose M here: the module
586	  will be called sunqe.
587
588config SUNGEM
589	tristate "Sun GEM support"
590	depends on PCI
591	select CRC32
592	help
593	  Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0.  See also
594	  <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
595
596config CASSINI
597	tristate "Sun Cassini support"
598	depends on PCI
599	select CRC32
600	help
601	  Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
602	  <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
603
604config SUNVNET
605	tristate "Sun Virtual Network support"
606	depends on SUN_LDOMS
607	help
608	  Support for virtual network devices under Sun Logical Domains.
609
610config NET_VENDOR_3COM
611	bool "3COM cards"
612	depends on ISA || EISA || MCA || PCI
613	help
614	  If you have a network (Ethernet) card belonging to this class, say Y
615	  and read the Ethernet-HOWTO, available from
616	  <http://www.tldp.org/docs.html#howto>.
617
618	  Note that the answer to this question doesn't directly affect the
619	  kernel: saying N will just cause the configurator to skip all
620	  the questions about 3COM cards. If you say Y, you will be asked for
621	  your specific card in the following questions.
622
623config EL1
624	tristate "3c501 \"EtherLink\" support"
625	depends on NET_VENDOR_3COM && ISA
626	---help---
627	  If you have a network (Ethernet) card of this type, say Y and read
628	  the Ethernet-HOWTO, available from
629	  <http://www.tldp.org/docs.html#howto>.  Also, consider buying a
630	  new card, since the 3c501 is slow, broken, and obsolete: you will
631	  have problems.  Some people suggest to ping ("man ping") a nearby
632	  machine every minute ("man cron") when using this card.
633
634	  To compile this driver as a module, choose M here. The module
635	  will be called 3c501.
636
637config EL2
638	tristate "3c503 \"EtherLink II\" support"
639	depends on NET_VENDOR_3COM && ISA
640	select CRC32
641	help
642	  If you have a network (Ethernet) card of this type, say Y and read
643	  the Ethernet-HOWTO, available from
644	  <http://www.tldp.org/docs.html#howto>.
645
646	  To compile this driver as a module, choose M here. The module
647	  will be called 3c503.
648
649config ELPLUS
650	tristate "3c505 \"EtherLink Plus\" support"
651	depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
652	---help---
653	  Information about this network (Ethernet) card can be found in
654	  <file:Documentation/networking/3c505.txt>.  If you have a card of
655	  this type, say Y and read the Ethernet-HOWTO, available from
656	  <http://www.tldp.org/docs.html#howto>.
657
658	  To compile this driver as a module, choose M here. The module
659	  will be called 3c505.
660
661config EL16
662	tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
663	depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
664	help
665	  If you have a network (Ethernet) card of this type, say Y and read
666	  the Ethernet-HOWTO, available from
667	  <http://www.tldp.org/docs.html#howto>.
668
669	  To compile this driver as a module, choose M here. The module
670	  will be called 3c507.
671
672config EL3
673	tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
674	depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
675	---help---
676	  If you have a network (Ethernet) card belonging to the 3Com
677	  EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
678	  from <http://www.tldp.org/docs.html#howto>.
679
680	  If your card is not working you may need to use the DOS
681	  setup disk to disable Plug & Play mode, and to select the default
682	  media type.
683
684	  To compile this driver as a module, choose M here. The module
685	  will be called 3c509.
686
687config 3C515
688	tristate "3c515 ISA \"Fast EtherLink\""
689	depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
690	help
691	  If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
692	  network card, say Y and read the Ethernet-HOWTO, available from
693	  <http://www.tldp.org/docs.html#howto>.
694
695	  To compile this driver as a module, choose M here. The module
696	  will be called 3c515.
697
698config ELMC
699	tristate "3c523 \"EtherLink/MC\" support"
700	depends on NET_VENDOR_3COM && MCA_LEGACY
701	help
702	  If you have a network (Ethernet) card of this type, say Y and read
703	  the Ethernet-HOWTO, available from
704	  <http://www.tldp.org/docs.html#howto>.
705
706	  To compile this driver as a module, choose M here. The module
707	  will be called 3c523.
708
709config ELMC_II
710	tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
711	depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
712	help
713	  If you have a network (Ethernet) card of this type, say Y and read
714	  the Ethernet-HOWTO, available from
715	  <http://www.tldp.org/docs.html#howto>.
716
717	  To compile this driver as a module, choose M here. The module
718	  will be called 3c527.
719
720config VORTEX
721	tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
722	depends on NET_VENDOR_3COM && (PCI || EISA)
723	select MII
724	---help---
725	  This option enables driver support for a large number of 10Mbps and
726	  10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
727
728	  "Vortex"    (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
729	  "Boomerang" (EtherLink XL 3c900 or 3c905)            PCI
730	  "Cyclone"   (3c540/3c900/3c905/3c980/3c575/3c656)    PCI and Cardbus
731	  "Tornado"   (3c905)                                  PCI
732	  "Hurricane" (3c555/3cSOHO)                           PCI
733
734	  If you have such a card, say Y and read the Ethernet-HOWTO,
735	  available from <http://www.tldp.org/docs.html#howto>. More
736	  specific information is in
737	  <file:Documentation/networking/vortex.txt> and in the comments at
738	  the beginning of <file:drivers/net/3c59x.c>.
739
740	  To compile this support as a module, choose M here.
741
742config TYPHOON
743	tristate "3cr990 series \"Typhoon\" support"
744	depends on NET_VENDOR_3COM && PCI
745	select CRC32
746	---help---
747	  This option enables driver support for the 3cr990 series of cards:
748
749	  3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
750	  3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
751	  3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
752
753	  If you have a network (Ethernet) card of this type, say Y and read
754	  the Ethernet-HOWTO, available from
755	  <http://www.tldp.org/docs.html#howto>.
756
757	  To compile this driver as a module, choose M here. The module
758	  will be called typhoon.
759
760config LANCE
761	tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
762	depends on ISA && ISA_DMA_API
763	help
764	  If you have a network (Ethernet) card of this type, say Y and read
765	  the Ethernet-HOWTO, available from
766	  <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
767	  of this type.
768
769	  To compile this driver as a module, choose M here: the module
770	  will be called lance.  This is recommended.
771
772config NET_VENDOR_SMC
773	bool "Western Digital/SMC cards"
774	depends on ISA || MCA || EISA || MAC
775	help
776	  If you have a network (Ethernet) card belonging to this class, say Y
777	  and read the Ethernet-HOWTO, available from
778	  <http://www.tldp.org/docs.html#howto>.
779
780	  Note that the answer to this question doesn't directly affect the
781	  kernel: saying N will just cause the configurator to skip all
782	  the questions about Western Digital cards. If you say Y, you will be
783	  asked for your specific card in the following questions.
784
785config WD80x3
786	tristate "WD80*3 support"
787	depends on NET_VENDOR_SMC && ISA
788	select CRC32
789	help
790	  If you have a network (Ethernet) card of this type, say Y and read
791	  the Ethernet-HOWTO, available from
792	  <http://www.tldp.org/docs.html#howto>.
793
794	  To compile this driver as a module, choose M here. The module
795	  will be called wd.
796
797config ULTRAMCA
798	tristate "SMC Ultra MCA support"
799	depends on NET_VENDOR_SMC && MCA
800	select CRC32
801	help
802	  If you have a network (Ethernet) card of this type and are running
803	  an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
804	  available from <http://www.tldp.org/docs.html#howto>.
805
806	  To compile this driver as a module, choose M here. The module
807	  will be called smc-mca.
808
809config ULTRA
810	tristate "SMC Ultra support"
811	depends on NET_VENDOR_SMC && ISA
812	select CRC32
813	---help---
814	  If you have a network (Ethernet) card of this type, say Y and read
815	  the Ethernet-HOWTO, available from
816	  <http://www.tldp.org/docs.html#howto>.
817
818	  Important: There have been many reports that, with some motherboards
819	  mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
820	  such as some BusLogic models) causes corruption problems with many
821	  operating systems. The Linux smc-ultra driver has a work-around for
822	  this but keep it in mind if you have such a SCSI card and have
823	  problems.
824
825	  To compile this driver as a module, choose M here. The module
826	  will be called smc-ultra.
827
828config ULTRA32
829	tristate "SMC Ultra32 EISA support"
830	depends on NET_VENDOR_SMC && EISA
831	select CRC32
832	help
833	  If you have a network (Ethernet) card of this type, say Y and read
834	  the Ethernet-HOWTO, available from
835	  <http://www.tldp.org/docs.html#howto>.
836
837	  To compile this driver as a module, choose M here. The module
838	  will be called smc-ultra32.
839
840config BFIN_MAC
841	tristate "Blackfin on-chip MAC support"
842	depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
843	select CRC32
844	select MII
845	select PHYLIB
846	select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
847	help
848	  This is the driver for Blackfin on-chip mac device. Say Y if you want it
849	  compiled into the kernel. This driver is also available as a module
850	  ( = code which can be inserted in and removed from the running kernel
851	  whenever you want). The module will be called bfin_mac.
852
853config BFIN_MAC_USE_L1
854	bool "Use L1 memory for rx/tx packets"
855	depends on BFIN_MAC && (BF527 || BF537)
856	default y
857	help
858	  To get maximum network performance, you should use L1 memory as rx/tx buffers.
859	  Say N here if you want to reserve L1 memory for other uses.
860
861config BFIN_TX_DESC_NUM
862	int "Number of transmit buffer packets"
863	depends on BFIN_MAC
864	range 6 10 if BFIN_MAC_USE_L1
865	range 10 100
866	default "10"
867	help
868	  Set the number of buffer packets used in driver.
869
870config BFIN_RX_DESC_NUM
871	int "Number of receive buffer packets"
872	depends on BFIN_MAC
873	range 20 100 if BFIN_MAC_USE_L1
874	range 20 800
875	default "20"
876	help
877	  Set the number of buffer packets used in driver.
878
879config BFIN_MAC_RMII
880	bool "RMII PHY Interface (EXPERIMENTAL)"
881	depends on BFIN_MAC && EXPERIMENTAL
882	default y if BFIN527_EZKIT
883	default n if BFIN537_STAMP
884	help
885	  Use Reduced PHY MII Interface
886
887config SMC9194
888	tristate "SMC 9194 support"
889	depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
890	select CRC32
891	---help---
892	  This is support for the SMC9xxx based Ethernet cards. Choose this
893	  option if you have a DELL laptop with the docking station, or
894	  another SMC9192/9194 based chipset.  Say Y if you want it compiled
895	  into the kernel, and read the file
896	  <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
897	  available from <http://www.tldp.org/docs.html#howto>.
898
899	  To compile this driver as a module, choose M here. The module
900	  will be called smc9194.
901
902config SMC91X
903	tristate "SMC 91C9x/91C1xxx support"
904	select CRC32
905	select MII
906	depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
907		MIPS || BLACKFIN || MN10300
908	help
909	  This is a driver for SMC's 91x series of Ethernet chipsets,
910	  including the SMC91C94 and the SMC91C111. Say Y if you want it
911	  compiled into the kernel, and read the file
912	  <file:Documentation/networking/smc9.txt>  and the Ethernet-HOWTO,
913	  available from  <http://www.linuxdoc.org/docs.html#howto>.
914
915	  This driver is also available as a module ( = code which can be
916	  inserted in and removed from the running kernel whenever you want).
917	  The module will be called smc91x.  If you want to compile it as a
918	  module, say M here and read <file:Documentation/kbuild/modules.txt>.
919
920config NET_NETX
921	tristate "NetX Ethernet support"
922	select MII
923	depends on ARCH_NETX
924	help
925	  This is support for the Hilscher netX builtin Ethernet ports
926
927	  To compile this driver as a module, choose M here. The module
928	  will be called netx-eth.
929
930config DM9000
931	tristate "DM9000 support"
932	depends on ARM || BLACKFIN || MIPS
933	select CRC32
934	select MII
935	---help---
936	  Support for DM9000 chipset.
937
938	  To compile this driver as a module, choose M here.  The module
939	  will be called dm9000.
940
941config DM9000_DEBUGLEVEL
942	int "DM9000 maximum debug level"
943	depends on DM9000
944	default 4
945	help
946	  The maximum level of debugging code compiled into the DM9000
947	  driver.
948
949config DM9000_FORCE_SIMPLE_PHY_POLL
950	bool "Force simple NSR based PHY polling"
951	depends on DM9000
952	---help---
953	  This configuration forces the DM9000 to use the NSR's LinkStatus
954	  bit to determine if the link is up or down instead of the more
955	  costly MII PHY reads. Note, this will not work if the chip is
956	  operating with an external PHY.
957
958config ENC28J60
959	tristate "ENC28J60 support"
960	depends on EXPERIMENTAL && SPI && NET_ETHERNET
961	select CRC32
962	---help---
963	  Support for the Microchip EN28J60 ethernet chip.
964
965	  To compile this driver as a module, choose M here. The module will be
966	  called enc28j60.
967
968config ENC28J60_WRITEVERIFY
969	bool "Enable write verify"
970	depends on ENC28J60
971	---help---
972	  Enable the verify after the buffer write useful for debugging purpose.
973	  If unsure, say N.
974
975config ETHOC
976	tristate "OpenCores 10/100 Mbps Ethernet MAC support"
977	depends on NET_ETHERNET && HAS_IOMEM
978	select MII
979	select PHYLIB
980	select CRC32
981	select BITREVERSE
982	help
983	  Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
984
985config SMC911X
986	tristate "SMSC LAN911[5678] support"
987	select CRC32
988	select MII
989	depends on ARM || SUPERH
990	help
991	  This is a driver for SMSC's LAN911x series of Ethernet chipsets
992	  including the new LAN9115, LAN9116, LAN9117, and LAN9118.
993	  Say Y if you want it compiled into the kernel,
994	  and read the Ethernet-HOWTO, available from
995	  <http://www.linuxdoc.org/docs.html#howto>.
996
997	  This driver is also available as a module. The module will be
998	  called smc911x.  If you want to compile it as a module, say M
999	  here and read <file:Documentation/kbuild/modules.txt>
1000
1001config SMSC911X
1002	tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1003	depends on ARM || SUPERH
1004	select CRC32
1005	select MII
1006	select PHYLIB
1007	---help---
1008	  Say Y here if you want support for SMSC LAN911x and LAN921x families
1009	  of ethernet controllers.
1010
1011	  To compile this driver as a module, choose M here and read
1012	  <file:Documentation/networking/net-modules.txt>. The module
1013	  will be called smsc911x.
1014
1015config NET_VENDOR_RACAL
1016	bool "Racal-Interlan (Micom) NI cards"
1017	depends on ISA
1018	help
1019	  If you have a network (Ethernet) card belonging to this class, such
1020	  as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1021	  available from <http://www.tldp.org/docs.html#howto>.
1022
1023	  Note that the answer to this question doesn't directly affect the
1024	  kernel: saying N will just cause the configurator to skip all
1025	  the questions about NI cards. If you say Y, you will be asked for
1026	  your specific card in the following questions.
1027
1028config NI5010
1029	tristate "NI5010 support (EXPERIMENTAL)"
1030	depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1031	---help---
1032	  If you have a network (Ethernet) card of this type, say Y and read
1033	  the Ethernet-HOWTO, available from
1034	  <http://www.tldp.org/docs.html#howto>. Note that this is still
1035	  experimental code.
1036
1037	  To compile this driver as a module, choose M here. The module
1038	  will be called ni5010.
1039
1040config NI52
1041	tristate "NI5210 support"
1042	depends on NET_VENDOR_RACAL && ISA
1043	help
1044	  If you have a network (Ethernet) card of this type, say Y and read
1045	  the Ethernet-HOWTO, available from
1046	  <http://www.tldp.org/docs.html#howto>.
1047
1048	  To compile this driver as a module, choose M here. The module
1049	  will be called ni52.
1050
1051config NI65
1052	tristate "NI6510 support"
1053	depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1054	help
1055	  If you have a network (Ethernet) card of this type, say Y and read
1056	  the Ethernet-HOWTO, available from
1057	  <http://www.tldp.org/docs.html#howto>.
1058
1059	  To compile this driver as a module, choose M here. The module
1060	  will be called ni65.
1061
1062config DNET
1063	tristate "Dave ethernet support (DNET)"
1064	depends on NET_ETHERNET && HAS_IOMEM
1065	select PHYLIB
1066	help
1067	  The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1068	  Say Y to include support for the DNET chip.
1069
1070	  To compile this driver as a module, choose M here: the module
1071	  will be called dnet.
1072
1073source "drivers/net/tulip/Kconfig"
1074
1075config AT1700
1076	tristate "AT1700/1720 support (EXPERIMENTAL)"
1077	depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1078	select CRC32
1079	---help---
1080	  If you have a network (Ethernet) card of this type, say Y and read
1081	  the Ethernet-HOWTO, available from
1082	  <http://www.tldp.org/docs.html#howto>.
1083
1084	  To compile this driver as a module, choose M here. The module
1085	  will be called at1700.
1086
1087config DEPCA
1088	tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1089	depends on ISA || EISA || MCA
1090	select CRC32
1091	---help---
1092	  If you have a network (Ethernet) card of this type, say Y and read
1093	  the Ethernet-HOWTO, available from
1094	  <http://www.tldp.org/docs.html#howto> as well as
1095	  <file:drivers/net/depca.c>.
1096
1097	  To compile this driver as a module, choose M here. The module
1098	  will be called depca.
1099
1100config HP100
1101	tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1102	depends on ISA || EISA || PCI
1103	help
1104	  If you have a network (Ethernet) card of this type, say Y and read
1105	  the Ethernet-HOWTO, available from
1106	  <http://www.tldp.org/docs.html#howto>.
1107
1108	  To compile this driver as a module, choose M here. The module
1109	  will be called hp100.
1110
1111config NET_ISA
1112	bool "Other ISA cards"
1113	depends on ISA
1114	---help---
1115	  If your network (Ethernet) card hasn't been mentioned yet and its
1116	  bus system (that's the way the cards talks to the other components
1117	  of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1118	  Make sure you know the name of your card. Read the Ethernet-HOWTO,
1119	  available from <http://www.tldp.org/docs.html#howto>.
1120
1121	  If unsure, say Y.
1122
1123	  Note that the answer to this question doesn't directly affect the
1124	  kernel: saying N will just cause the configurator to skip all
1125	  the remaining ISA network card questions. If you say Y, you will be
1126	  asked for your specific card in the following questions.
1127
1128config E2100
1129	tristate "Cabletron E21xx support"
1130	depends on NET_ISA
1131	select CRC32
1132	help
1133	  If you have a network (Ethernet) card of this type, say Y and read
1134	  the Ethernet-HOWTO, available from
1135	  <http://www.tldp.org/docs.html#howto>.
1136
1137	  To compile this driver as a module, choose M here. The module
1138	  will be called e2100.
1139
1140config EWRK3
1141	tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1142	depends on NET_ISA
1143	select CRC32
1144	---help---
1145	  This driver supports the DE203, DE204 and DE205 network (Ethernet)
1146	  cards. If this is for you, say Y and read
1147	  <file:Documentation/networking/ewrk3.txt> in the kernel source as
1148	  well as the Ethernet-HOWTO, available from
1149	  <http://www.tldp.org/docs.html#howto>.
1150
1151	  To compile this driver as a module, choose M here. The module
1152	  will be called ewrk3.
1153
1154config EEXPRESS
1155	tristate "EtherExpress 16 support"
1156	depends on NET_ISA
1157	---help---
1158	  If you have an EtherExpress16 network (Ethernet) card, say Y and
1159	  read the Ethernet-HOWTO, available from
1160	  <http://www.tldp.org/docs.html#howto>.  Note that the Intel
1161	  EtherExpress16 card used to be regarded as a very poor choice
1162	  because the driver was very unreliable. We now have a new driver
1163	  that should do better.
1164
1165	  To compile this driver as a module, choose M here. The module
1166	  will be called eexpress.
1167
1168config EEXPRESS_PRO
1169	tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1170	depends on NET_ISA
1171	---help---
1172	  If you have a network (Ethernet) card of this type, say Y. This
1173	  driver supports Intel i82595{FX,TX} based boards. Note however
1174	  that the EtherExpress PRO/100 Ethernet card has its own separate
1175	  driver.  Please read the Ethernet-HOWTO, available from
1176	  <http://www.tldp.org/docs.html#howto>.
1177
1178	  To compile this driver as a module, choose M here. The module
1179	  will be called eepro.
1180
1181config HPLAN_PLUS
1182	tristate "HP PCLAN+ (27247B and 27252A) support"
1183	depends on NET_ISA
1184	select CRC32
1185	help
1186	  If you have a network (Ethernet) card of this type, say Y and read
1187	  the Ethernet-HOWTO, available from
1188	  <http://www.tldp.org/docs.html#howto>.
1189
1190	  To compile this driver as a module, choose M here. The module
1191	  will be called hp-plus.
1192
1193config HPLAN
1194	tristate "HP PCLAN (27245 and other 27xxx series) support"
1195	depends on NET_ISA
1196	select CRC32
1197	help
1198	  If you have a network (Ethernet) card of this type, say Y and read
1199	  the Ethernet-HOWTO, available from
1200	  <http://www.tldp.org/docs.html#howto>.
1201
1202	  To compile this driver as a module, choose M here. The module
1203	  will be called hp.
1204
1205config LP486E
1206	tristate "LP486E on board Ethernet"
1207	depends on NET_ISA
1208	help
1209	  Say Y here to support the 82596-based on-board Ethernet controller
1210	  for the Panther motherboard, which is one of the two shipped in the
1211	  Intel Professional Workstation.
1212
1213config ETH16I
1214	tristate "ICL EtherTeam 16i/32 support"
1215	depends on NET_ISA
1216	help
1217	  If you have a network (Ethernet) card of this type, say Y and read
1218	  the Ethernet-HOWTO, available from
1219	  <http://www.tldp.org/docs.html#howto>.
1220
1221	  To compile this driver as a module, choose M here. The module
1222	  will be called eth16i.
1223
1224config NE2000
1225	tristate "NE2000/NE1000 support"
1226	depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1227	select CRC32
1228	---help---
1229	  If you have a network (Ethernet) card of this type, say Y and read
1230	  the Ethernet-HOWTO, available from
1231	  <http://www.tldp.org/docs.html#howto>.  Many Ethernet cards
1232	  without a specific driver are compatible with NE2000.
1233
1234	  If you have a PCI NE2000 card however, say N here and Y to "PCI
1235	  NE2000 and clone support" under "EISA, VLB, PCI and on board
1236	  controllers" below. If you have a NE2000 card and are running on
1237	  an MCA system (a bus system used on some IBM PS/2 computers and
1238	  laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1239	  below.
1240
1241	  To compile this driver as a module, choose M here. The module
1242	  will be called ne.
1243
1244config ZNET
1245	tristate "Zenith Z-Note support (EXPERIMENTAL)"
1246	depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1247	help
1248	  The Zenith Z-Note notebook computer has a built-in network
1249	  (Ethernet) card, and this is the Linux driver for it. Note that the
1250	  IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1251	  by this driver. Read the Ethernet-HOWTO, available from
1252	  <http://www.tldp.org/docs.html#howto>.
1253
1254config SEEQ8005
1255	tristate "SEEQ8005 support (EXPERIMENTAL)"
1256	depends on NET_ISA && EXPERIMENTAL
1257	help
1258	  This is a driver for the SEEQ 8005 network (Ethernet) card.  If this
1259	  is for you, read the Ethernet-HOWTO, available from
1260	  <http://www.tldp.org/docs.html#howto>.
1261
1262	  To compile this driver as a module, choose M here. The module
1263	  will be called seeq8005.
1264
1265config NE2_MCA
1266	tristate "NE/2 (ne2000 MCA version) support"
1267	depends on MCA_LEGACY
1268	select CRC32
1269	help
1270	  If you have a network (Ethernet) card of this type, say Y and read
1271	  the Ethernet-HOWTO, available from
1272	  <http://www.tldp.org/docs.html#howto>.
1273
1274	  To compile this driver as a module, choose M here. The module
1275	  will be called ne2.
1276
1277config IBMLANA
1278	tristate "IBM LAN Adapter/A support"
1279	depends on MCA
1280	---help---
1281	  This is a Micro Channel Ethernet adapter.  You need to set
1282	  CONFIG_MCA to use this driver.  It is both available as an in-kernel
1283	  driver and as a module.
1284
1285	  To compile this driver as a module, choose M here. The only
1286	  currently supported card is the IBM LAN Adapter/A for Ethernet.  It
1287	  will both support 16K and 32K memory windows, however a 32K window
1288	  gives a better security against packet losses.  Usage of multiple
1289	  boards with this driver should be possible, but has not been tested
1290	  up to now due to lack of hardware.
1291
1292config IBMVETH
1293	tristate "IBM LAN Virtual Ethernet support"
1294	depends on PPC_PSERIES
1295	---help---
1296	  This driver supports virtual ethernet adapters on newer IBM iSeries
1297	  and pSeries systems.
1298
1299	  To compile this driver as a module, choose M here. The module will
1300	  be called ibmveth.
1301
1302source "drivers/net/ibm_newemac/Kconfig"
1303
1304config NET_PCI
1305	bool "EISA, VLB, PCI and on board controllers"
1306	depends on ISA || EISA || PCI
1307	help
1308	  This is another class of network cards which attach directly to the
1309	  bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1310	  available from <http://www.tldp.org/docs.html#howto>.
1311
1312	  Note that the answer to this question doesn't directly affect the
1313	  kernel: saying N will just cause the configurator to skip all
1314	  the questions about this class of network cards. If you say Y, you
1315	  will be asked for your specific card in the following questions. If
1316	  you are unsure, say Y.
1317
1318config PCNET32
1319	tristate "AMD PCnet32 PCI support"
1320	depends on NET_PCI && PCI
1321	select CRC32
1322	select MII
1323	help
1324	  If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1325	  answer Y here and read the Ethernet-HOWTO, available from
1326	  <http://www.tldp.org/docs.html#howto>.
1327
1328	  To compile this driver as a module, choose M here. The module
1329	  will be called pcnet32.
1330
1331config AMD8111_ETH
1332	tristate "AMD 8111 (new PCI lance) support"
1333	depends on NET_PCI && PCI
1334	select CRC32
1335	select MII
1336	help
1337	  If you have an AMD 8111-based PCI lance ethernet card,
1338	  answer Y here and read the Ethernet-HOWTO, available from
1339	  <http://www.tldp.org/docs.html#howto>.
1340
1341	  To compile this driver as a module, choose M here. The module
1342	  will be called amd8111e.
1343
1344config ADAPTEC_STARFIRE
1345	tristate "Adaptec Starfire/DuraLAN support"
1346	depends on NET_PCI && PCI
1347	select CRC32
1348	select MII
1349	help
1350	  Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1351	  adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1352	  Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1353	  driver.
1354
1355	  To compile this driver as a module, choose M here: the module
1356	  will be called starfire.  This is recommended.
1357
1358config AC3200
1359	tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1360	depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1361	select CRC32
1362	help
1363	  If you have a network (Ethernet) card of this type, say Y and read
1364	  the Ethernet-HOWTO, available from
1365	  <http://www.tldp.org/docs.html#howto>.
1366
1367	  To compile this driver as a module, choose M here. The module
1368	  will be called ac3200.
1369
1370config APRICOT
1371	tristate "Apricot Xen-II on board Ethernet"
1372	depends on NET_PCI && ISA
1373	help
1374	  If you have a network (Ethernet) controller of this type, say Y and
1375	  read the Ethernet-HOWTO, available from
1376	  <http://www.tldp.org/docs.html#howto>.
1377
1378	  To compile this driver as a module, choose M here. The module
1379	  will be called apricot.
1380
1381config B44
1382	tristate "Broadcom 440x/47xx ethernet support"
1383	depends on SSB_POSSIBLE && HAS_DMA
1384	select SSB
1385	select MII
1386	help
1387	  If you have a network (Ethernet) controller of this type, say Y
1388	  or M and read the Ethernet-HOWTO, available from
1389	  <http://www.tldp.org/docs.html#howto>.
1390
1391	  To compile this driver as a module, choose M here. The module
1392	  will be called b44.
1393
1394# Auto-select SSB PCI-HOST support, if possible
1395config B44_PCI_AUTOSELECT
1396	bool
1397	depends on B44 && SSB_PCIHOST_POSSIBLE
1398	select SSB_PCIHOST
1399	default y
1400
1401# Auto-select SSB PCICORE driver, if possible
1402config B44_PCICORE_AUTOSELECT
1403	bool
1404	depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1405	select SSB_DRIVER_PCICORE
1406	default y
1407
1408config B44_PCI
1409	bool
1410	depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1411	default y
1412
1413config FORCEDETH
1414	tristate "nForce Ethernet support"
1415	depends on NET_PCI && PCI
1416	help
1417	  If you have a network (Ethernet) controller of this type, say Y and
1418	  read the Ethernet-HOWTO, available from
1419	  <http://www.tldp.org/docs.html#howto>.
1420
1421	  To compile this driver as a module, choose M here. The module
1422	  will be called forcedeth.
1423
1424config FORCEDETH_NAPI
1425	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
1426	depends on FORCEDETH && EXPERIMENTAL
1427	help
1428	  NAPI is a new driver API designed to reduce CPU and interrupt load
1429	  when the driver is receiving lots of packets from the card. It is
1430	  still somewhat experimental and thus not yet enabled by default.
1431
1432	  If your estimated Rx load is 10kpps or more, or if the card will be
1433	  deployed on potentially unfriendly networks (e.g. in a firewall),
1434	  then say Y here.
1435
1436	  If in doubt, say N.
1437
1438config CS89x0
1439	tristate "CS89x0 support"
1440	depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1441		|| ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS)
1442	---help---
1443	  Support for CS89x0 chipset based Ethernet cards. If you have a
1444	  network (Ethernet) card of this type, say Y and read the
1445	  Ethernet-HOWTO, available from
1446	  <http://www.tldp.org/docs.html#howto> as well as
1447	  <file:Documentation/networking/cs89x0.txt>.
1448
1449	  To compile this driver as a module, choose M here. The module
1450	  will be called cs89x0.
1451
1452config CS89x0_NONISA_IRQ
1453	def_bool y
1454	depends on CS89x0 != n
1455	depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS
1456
1457config TC35815
1458	tristate "TOSHIBA TC35815 Ethernet support"
1459	depends on NET_PCI && PCI && MIPS
1460	select PHYLIB
1461
1462config E100
1463	tristate "Intel(R) PRO/100+ support"
1464	depends on NET_PCI && PCI
1465	select MII
1466	---help---
1467	  This driver supports Intel(R) PRO/100 family of adapters.
1468	  To verify that your adapter is supported, find the board ID number
1469	  on the adapter. Look for a label that has a barcode and a number
1470	  in the format 123456-001 (six digits hyphen three digits).
1471
1472	  Use the above information and the Adapter & Driver ID Guide at:
1473
1474	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1475
1476          to identify the adapter.
1477
1478	  For the latest Intel PRO/100 network driver for Linux, see:
1479
1480	  <http://appsr.intel.com/scripts-df/support_intel.asp>
1481
1482	  More specific information on configuring the driver is in
1483	  <file:Documentation/networking/e100.txt>.
1484
1485	  To compile this driver as a module, choose M here. The module
1486	  will be called e100.
1487
1488config LNE390
1489	tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1490	depends on NET_PCI && EISA && EXPERIMENTAL
1491	select CRC32
1492	help
1493	  If you have a network (Ethernet) card of this type, say Y and read
1494	  the Ethernet-HOWTO, available from
1495	  <http://www.tldp.org/docs.html#howto>.
1496
1497	  To compile this driver as a module, choose M here. The module
1498	  will be called lne390.
1499
1500config FEALNX
1501	tristate "Myson MTD-8xx PCI Ethernet support"
1502	depends on NET_PCI && PCI
1503	select CRC32
1504	select MII
1505	help
1506	  Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
1507	  cards. Specifications and data at
1508	  <http://www.myson.com.hk/mtd/datasheet/>.
1509
1510config NATSEMI
1511	tristate "National Semiconductor DP8381x series PCI Ethernet support"
1512	depends on NET_PCI && PCI
1513	select CRC32
1514	help
1515	  This driver is for the National Semiconductor DP83810 series,
1516	  which is used in cards from PureData, NetGear, Linksys
1517	  and others, including the 83815 chip.
1518	  More specific information and updates are available from
1519	  <http://www.scyld.com/network/natsemi.html>.
1520
1521config NE2K_PCI
1522	tristate "PCI NE2000 and clones support (see help)"
1523	depends on NET_PCI && PCI
1524	select CRC32
1525	---help---
1526	  This driver is for NE2000 compatible PCI cards. It will not work
1527	  with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1528	  support" below). If you have a PCI NE2000 network (Ethernet) card,
1529	  say Y and read the Ethernet-HOWTO, available from
1530	  <http://www.tldp.org/docs.html#howto>.
1531
1532	  This driver also works for the following NE2000 clone cards:
1533	  RealTek RTL-8029  Winbond 89C940  Compex RL2000  KTI ET32P2
1534	  NetVin NV5000SC   Via 86C926      SureCom NE34   Winbond
1535	  Holtek HT80232    Holtek HT80229
1536
1537	  To compile this driver as a module, choose M here. The module
1538	  will be called ne2k-pci.
1539
1540config NE3210
1541	tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1542	depends on NET_PCI && EISA && EXPERIMENTAL
1543	select CRC32
1544	---help---
1545	  If you have a network (Ethernet) card of this type, say Y and read
1546	  the Ethernet-HOWTO, available from
1547	  <http://www.tldp.org/docs.html#howto>.  Note that this driver
1548	  will NOT WORK for NE3200 cards as they are completely different.
1549
1550	  To compile this driver as a module, choose M here. The module
1551	  will be called ne3210.
1552
1553config ES3210
1554	tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1555	depends on NET_PCI && EISA && EXPERIMENTAL
1556	select CRC32
1557	help
1558	  If you have a network (Ethernet) card of this type, say Y and read
1559	  the Ethernet-HOWTO, available from
1560	  <http://www.tldp.org/docs.html#howto>.
1561
1562	  To compile this driver as a module, choose M here. The module
1563	  will be called es3210.
1564
1565config 8139CP
1566	tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1567	depends on NET_PCI && PCI && EXPERIMENTAL
1568	select CRC32
1569	select MII
1570	help
1571	  This is a driver for the Fast Ethernet PCI network cards based on
1572	  the RTL8139C+ chips. If you have one of those, say Y and read
1573	  the Ethernet-HOWTO, available from
1574	  <http://www.tldp.org/docs.html#howto>.
1575
1576	  To compile this driver as a module, choose M here: the module
1577	  will be called 8139cp.  This is recommended.
1578
1579config 8139TOO
1580	tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1581	depends on NET_PCI && PCI
1582	select CRC32
1583	select MII
1584	---help---
1585	  This is a driver for the Fast Ethernet PCI network cards based on
1586	  the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1587	  read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1588
1589	  To compile this driver as a module, choose M here: the module
1590	  will be called 8139too.  This is recommended.
1591
1592config 8139TOO_PIO
1593	bool "Use PIO instead of MMIO"
1594	default y
1595	depends on 8139TOO
1596	help
1597	  This instructs the driver to use programmed I/O ports (PIO) instead
1598	  of PCI shared memory (MMIO).  This can possibly solve some problems
1599	  in case your mainboard has memory consistency issues.  If unsure,
1600	  say N.
1601
1602config 8139TOO_TUNE_TWISTER
1603	bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1604	depends on 8139TOO
1605	help
1606	  This implements a function which might come in handy in case you
1607	  are using low quality on long cabling. It is required for RealTek
1608	  RTL-8139 revision K boards, and totally unused otherwise.  It tries
1609	  to match the transceiver to the cable characteristics. This is
1610	  experimental since hardly documented by the manufacturer.
1611	  If unsure, say Y.
1612
1613config 8139TOO_8129
1614	bool "Support for older RTL-8129/8130 boards"
1615	depends on 8139TOO
1616	help
1617	  This enables support for the older and uncommon RTL-8129 and
1618	  RTL-8130 chips, which support MII via an external transceiver,
1619	  instead of an internal one.  Disabling this option will save some
1620	  memory by making the code size smaller.  If unsure, say Y.
1621
1622config 8139_OLD_RX_RESET
1623	bool "Use older RX-reset method"
1624	depends on 8139TOO
1625	help
1626	  The 8139too driver was recently updated to contain a more rapid
1627	  reset sequence, in the face of severe receive errors.  This "new"
1628	  RX-reset method should be adequate for all boards.  But if you
1629	  experience problems, you can enable this option to restore the
1630	  old RX-reset behavior.  If unsure, say N.
1631
1632config R6040
1633	tristate "RDC R6040 Fast Ethernet Adapter support"
1634	depends on NET_PCI && PCI
1635	select CRC32
1636	select MII
1637	help
1638	  This is a driver for the R6040 Fast Ethernet MACs found in the
1639	  the RDC R-321x System-on-chips.
1640
1641	  To compile this driver as a module, choose M here: the module
1642	  will be called r6040. This is recommended.
1643
1644config SIS900
1645	tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1646	depends on NET_PCI && PCI
1647	select CRC32
1648	select MII
1649	---help---
1650	  This is a driver for the Fast Ethernet PCI network cards based on
1651	  the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1652	  SiS 630 and SiS 540 chipsets.
1653
1654	  This driver also supports AMD 79C901 HomePNA so that you can use
1655	  your phone line as a network cable.
1656
1657	  To compile this driver as a module, choose M here: the module
1658	  will be called sis900.  This is recommended.
1659
1660config EPIC100
1661	tristate "SMC EtherPower II"
1662	depends on NET_PCI && PCI
1663	select CRC32
1664	select MII
1665	help
1666	  This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1667	  which is based on the SMC83c17x (EPIC/100).
1668	  More specific information and updates are available from
1669	  <http://www.scyld.com/network/epic100.html>.
1670
1671config SMSC9420
1672	tristate "SMSC LAN9420 PCI ethernet adapter support"
1673	depends on NET_PCI && PCI
1674	select CRC32
1675	select PHYLIB
1676	select SMSC_PHY
1677	help
1678	  This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1679	  Say Y if you want it compiled into the kernel,
1680	  and read the Ethernet-HOWTO, available from
1681	  <http://www.linuxdoc.org/docs.html#howto>.
1682
1683	  This driver is also available as a module. The module will be
1684	  called smsc9420.  If you want to compile it as a module, say M
1685	  here and read <file:Documentation/kbuild/modules.txt>
1686
1687config SUNDANCE
1688	tristate "Sundance Alta support"
1689	depends on NET_PCI && PCI
1690	select CRC32
1691	select MII
1692	help
1693	  This driver is for the Sundance "Alta" chip.
1694	  More specific information and updates are available from
1695	  <http://www.scyld.com/network/sundance.html>.
1696
1697config SUNDANCE_MMIO
1698	bool "Use MMIO instead of PIO"
1699	depends on SUNDANCE
1700	help
1701	  Enable memory-mapped I/O for interaction with Sundance NIC registers.
1702	  Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1703	  is known to solve bugs on certain chips.
1704
1705	  If unsure, say N.
1706
1707config TLAN
1708	tristate "TI ThunderLAN support"
1709	depends on NET_PCI && (PCI || EISA)
1710	---help---
1711	  If you have a PCI Ethernet network card based on the ThunderLAN chip
1712	  which is supported by this driver, say Y and read the
1713	  Ethernet-HOWTO, available from
1714	  <http://www.tldp.org/docs.html#howto>.
1715
1716	  Devices currently supported by this driver are Compaq Netelligent,
1717	  Compaq NetFlex and Olicom cards.  Please read the file
1718	  <file:Documentation/networking/tlan.txt> for more details.
1719
1720	  To compile this driver as a module, choose M here. The module
1721	  will be called tlan.
1722
1723	  Please email feedback to <torben.mathiasen@compaq.com>.
1724
1725config VIA_RHINE
1726	tristate "VIA Rhine support"
1727	depends on NET_PCI && PCI
1728	select CRC32
1729	select MII
1730	help
1731	  If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1732	  Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1733	  Ethernet functions can also be found integrated on South Bridges
1734	  (e.g. VT8235).
1735
1736	  To compile this driver as a module, choose M here. The module
1737	  will be called via-rhine.
1738
1739config VIA_RHINE_MMIO
1740	bool "Use MMIO instead of PIO"
1741	depends on VIA_RHINE
1742	help
1743	  This instructs the driver to use PCI shared memory (MMIO) instead of
1744	  programmed I/O ports (PIO). Enabling this gives an improvement in
1745	  processing time in parts of the driver.
1746
1747	  If unsure, say Y.
1748
1749config SC92031
1750	tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1751	depends on NET_PCI && PCI && EXPERIMENTAL
1752	select CRC32
1753	---help---
1754	  This is a driver for the Fast Ethernet PCI network cards based on
1755	  the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1756	  have one of these, say Y here.
1757
1758	  To compile this driver as a module, choose M here: the module
1759	  will be called sc92031.  This is recommended.
1760
1761config CPMAC
1762	tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1763	depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
1764	select PHYLIB
1765	help
1766	  TI AR7 CPMAC Ethernet support
1767
1768config NET_POCKET
1769	bool "Pocket and portable adapters"
1770	depends on PARPORT
1771	---help---
1772	  Cute little network (Ethernet) devices which attach to the parallel
1773	  port ("pocket adapters"), commonly used with laptops. If you have
1774	  one of those, say Y and read the Ethernet-HOWTO, available from
1775	  <http://www.tldp.org/docs.html#howto>.
1776
1777	  If you want to plug a network (or some other) card into the PCMCIA
1778	  (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1779	  credit card size extension cards used by all modern laptops), you
1780	  need the pcmcia-cs package (location contained in the file
1781	  <file:Documentation/Changes>) and you can say N here.
1782
1783	  Laptop users should read the Linux Laptop home page at
1784	  <http://www.linux-on-laptops.com/> or
1785	  Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1786
1787	  Note that the answer to this question doesn't directly affect the
1788	  kernel: saying N will just cause the configurator to skip all
1789	  the questions about this class of network devices. If you say Y, you
1790	  will be asked for your specific device in the following questions.
1791
1792config ATP
1793	tristate "AT-LAN-TEC/RealTek pocket adapter support"
1794	depends on NET_POCKET && PARPORT && X86
1795	select CRC32
1796	---help---
1797	  This is a network (Ethernet) device which attaches to your parallel
1798	  port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1799	  available from <http://www.tldp.org/docs.html#howto>, if you
1800	  want to use this.  If you intend to use this driver, you should have
1801	  said N to the "Parallel printer support", because the two drivers
1802	  don't like each other.
1803
1804	  To compile this driver as a module, choose M here: the module
1805	  will be called atp.
1806
1807config DE600
1808	tristate "D-Link DE600 pocket adapter support"
1809	depends on NET_POCKET && PARPORT
1810	---help---
1811	  This is a network (Ethernet) device which attaches to your parallel
1812	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
1813	  Ethernet-HOWTO, available from
1814	  <http://www.tldp.org/docs.html#howto>, if you want to use
1815	  this. It is possible to have several devices share a single parallel
1816	  port and it is safe to compile the corresponding drivers into the
1817	  kernel.
1818
1819	  To compile this driver as a module, choose M here: the module
1820	  will be called de600.
1821
1822config DE620
1823	tristate "D-Link DE620 pocket adapter support"
1824	depends on NET_POCKET && PARPORT
1825	---help---
1826	  This is a network (Ethernet) device which attaches to your parallel
1827	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
1828	  Ethernet-HOWTO, available from
1829	  <http://www.tldp.org/docs.html#howto>, if you want to use
1830	  this. It is possible to have several devices share a single parallel
1831	  port and it is safe to compile the corresponding drivers into the
1832	  kernel.
1833
1834	  To compile this driver as a module, choose M here: the module
1835	  will be called de620.
1836
1837config SGISEEQ
1838	tristate "SGI Seeq ethernet controller support"
1839	depends on SGI_HAS_SEEQ
1840	help
1841	  Say Y here if you have an Seeq based Ethernet network card. This is
1842	  used in many Silicon Graphics machines.
1843
1844config DECLANCE
1845	tristate "DEC LANCE ethernet controller support"
1846	depends on MACH_DECSTATION
1847	select CRC32
1848	help
1849	  This driver is for the series of Ethernet controllers produced by
1850	  DEC (now Compaq) based on the AMD Lance chipset, including the
1851	  DEPCA series.  (This chipset is better known via the NE2100 cards.)
1852
1853config 68360_ENET
1854	bool "Motorola 68360 ethernet controller"
1855	depends on M68360
1856	help
1857	  Say Y here if you want to use the built-in ethernet controller of
1858	  the Motorola 68360 processor.
1859
1860config FEC
1861	bool "FEC ethernet controller (of ColdFire CPUs)"
1862	depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27
1863	help
1864	  Say Y here if you want to use the built-in 10/100 Fast ethernet
1865	  controller on some Motorola ColdFire and Freescale i.MX processors.
1866
1867config FEC2
1868	bool "Second FEC ethernet controller (on some ColdFire CPUs)"
1869	depends on FEC
1870	help
1871	  Say Y here if you want to use the second built-in 10/100 Fast
1872	  ethernet controller on some Motorola ColdFire processors.
1873
1874config FEC_MPC52xx
1875	tristate "MPC52xx FEC driver"
1876	depends on PPC_MPC52xx && PPC_BESTCOMM
1877	select CRC32
1878	select PHYLIB
1879	select PPC_BESTCOMM_FEC
1880	---help---
1881	  This option enables support for the MPC5200's on-chip
1882	  Fast Ethernet Controller
1883	  If compiled as module, it will be called 'fec_mpc52xx.ko'.
1884
1885config FEC_MPC52xx_MDIO
1886	bool "MPC52xx FEC MDIO bus driver"
1887	depends on FEC_MPC52xx
1888	default y
1889	---help---
1890	  The MPC5200's FEC can connect to the Ethernet either with
1891	  an external MII PHY chip or 10 Mbps 7-wire interface
1892	  (Motorola? industry standard).
1893	  If your board uses an external PHY connected to FEC, enable this.
1894	  If not sure, enable.
1895	  If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
1896
1897config NE_H8300
1898	tristate "NE2000 compatible support for H8/300"
1899	depends on H8300
1900	help
1901	  Say Y here if you want to use the NE2000 compatible
1902	  controller on the Renesas H8/300 processor.
1903
1904config ATL2
1905	tristate "Atheros L2 Fast Ethernet support"
1906	depends on PCI
1907	select CRC32
1908	select MII
1909	help
1910	  This driver supports the Atheros L2 fast ethernet adapter.
1911
1912	  To compile this driver as a module, choose M here.  The module
1913	  will be called atl2.
1914
1915source "drivers/net/fs_enet/Kconfig"
1916
1917endif # NET_ETHERNET
1918
1919#
1920#	Gigabit Ethernet
1921#
1922
1923menuconfig NETDEV_1000
1924	bool "Ethernet (1000 Mbit)"
1925	depends on !UML
1926	default y
1927	---help---
1928	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
1929	  type of Local Area Network (LAN) in universities and companies.
1930
1931	  Say Y here to get to see options for Gigabit Ethernet drivers.
1932	  This option alone does not add any kernel code.
1933	  Note that drivers supporting both 100 and 1000 MBit may be listed
1934	  under "Ethernet (10 or 100MBit)" instead.
1935
1936	  If you say N, all options in this submenu will be skipped and disabled.
1937
1938if NETDEV_1000
1939
1940config ACENIC
1941	tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
1942	depends on PCI
1943	---help---
1944	  Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
1945	  GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
1946	  adapter. The driver allows for using the Jumbo Frame option (9000
1947	  bytes/frame) however it requires that your switches can handle this
1948	  as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
1949	  line.
1950
1951	  To compile this driver as a module, choose M here: the
1952	  module will be called acenic.
1953
1954config ACENIC_OMIT_TIGON_I
1955	bool "Omit support for old Tigon I based AceNICs"
1956	depends on ACENIC
1957	help
1958	  Say Y here if you only have Tigon II based AceNICs and want to leave
1959	  out support for the older Tigon I based cards which are no longer
1960	  being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
1961	  version)).  This will reduce the size of the driver object by
1962	  app. 100KB.  If you are not sure whether your card is a Tigon I or a
1963	  Tigon II, say N here.
1964
1965	  The safe and default value for this is N.
1966
1967config DL2K
1968	tristate "DL2000/TC902x-based Gigabit Ethernet support"
1969	depends on PCI
1970	select CRC32
1971	help
1972	  This driver supports DL2000/TC902x-based Gigabit ethernet cards,
1973	  which includes
1974	  D-Link DGE-550T Gigabit Ethernet Adapter.
1975	  D-Link DL2000-based Gigabit Ethernet Adapter.
1976	  Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
1977
1978	  To compile this driver as a module, choose M here: the
1979	  module will be called dl2k.
1980
1981config E1000
1982	tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
1983	depends on PCI
1984	---help---
1985	  This driver supports Intel(R) PRO/1000 gigabit ethernet family of
1986	  adapters.  For more information on how to identify your adapter, go
1987	  to the Adapter & Driver ID Guide at:
1988
1989	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1990
1991	  For general information and support, go to the Intel support
1992	  website at:
1993
1994	  <http://support.intel.com>
1995
1996	  More specific information on configuring the driver is in
1997	  <file:Documentation/networking/e1000.txt>.
1998
1999	  To compile this driver as a module, choose M here. The module
2000	  will be called e1000.
2001
2002config E1000E
2003	tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2004	depends on PCI && (!SPARC32 || BROKEN)
2005	---help---
2006	  This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2007	  ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2008	  use the regular e1000 driver For more information on how to
2009	  identify your adapter, go to the Adapter & Driver ID Guide at:
2010
2011	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2012
2013	  For general information and support, go to the Intel support
2014	  website at:
2015
2016	  <http://support.intel.com>
2017
2018	  To compile this driver as a module, choose M here. The module
2019	  will be called e1000e.
2020
2021config IP1000
2022	tristate "IP1000 Gigabit Ethernet support"
2023	depends on PCI && EXPERIMENTAL
2024	select MII
2025	---help---
2026	  This driver supports IP1000 gigabit Ethernet cards.
2027
2028	  To compile this driver as a module, choose M here: the module
2029	  will be called ipg.  This is recommended.
2030
2031config IGB
2032       tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2033       depends on PCI
2034       ---help---
2035         This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2036         adapters.  For more information on how to identify your adapter, go
2037         to the Adapter & Driver ID Guide at:
2038
2039         <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2040
2041         For general information and support, go to the Intel support
2042         website at:
2043
2044         <http://support.intel.com>
2045
2046         More specific information on configuring the driver is in
2047         <file:Documentation/networking/e1000.txt>.
2048
2049         To compile this driver as a module, choose M here. The module
2050         will be called igb.
2051
2052config IGB_DCA
2053	bool "Direct Cache Access (DCA) Support"
2054	default y
2055	depends on IGB && DCA && !(IGB=y && DCA=m)
2056	---help---
2057	  Say Y here if you want to use Direct Cache Access (DCA) in the
2058	  driver.  DCA is a method for warming the CPU cache before data
2059	  is used, with the intent of lessening the impact of cache misses.
2060
2061config IGBVF
2062       tristate "Intel(R) 82576 Virtual Function Ethernet support"
2063       depends on PCI
2064       ---help---
2065         This driver supports Intel(R) 82576 virtual functions.  For more
2066         information on how to identify your adapter, go to the Adapter &
2067         Driver ID Guide at:
2068
2069         <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2070
2071         For general information and support, go to the Intel support
2072         website at:
2073
2074         <http://support.intel.com>
2075
2076         More specific information on configuring the driver is in
2077         <file:Documentation/networking/e1000.txt>.
2078
2079         To compile this driver as a module, choose M here. The module
2080         will be called igbvf.
2081
2082source "drivers/net/ixp2000/Kconfig"
2083
2084config MYRI_SBUS
2085	tristate "MyriCOM Gigabit Ethernet support"
2086	depends on SBUS
2087	help
2088	  This driver supports MyriCOM Sbus gigabit Ethernet cards.
2089
2090	  To compile this driver as a module, choose M here: the module
2091	  will be called myri_sbus.  This is recommended.
2092
2093config NS83820
2094	tristate "National Semiconductor DP83820 support"
2095	depends on PCI
2096	help
2097	  This is a driver for the National Semiconductor DP83820 series
2098	  of gigabit ethernet MACs.  Cards using this chipset include
2099	  the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2100	  SOHO-GA2000T, SOHO-GA2500T.  The driver supports the use of
2101	  zero copy.
2102
2103config HAMACHI
2104	tristate "Packet Engines Hamachi GNIC-II support"
2105	depends on PCI
2106	select MII
2107	help
2108	  If you have a Gigabit Ethernet card of this type, say Y and read
2109	  the Ethernet-HOWTO, available from
2110	  <http://www.tldp.org/docs.html#howto>.
2111
2112	  To compile this driver as a module, choose M here. The module will be
2113	  called hamachi.
2114
2115config YELLOWFIN
2116	tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2117	depends on PCI && EXPERIMENTAL
2118	select CRC32
2119	---help---
2120	  Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2121	  adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2122	  used by the Beowulf Linux cluster project.  See
2123	  <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2124	  information about this driver in particular and Beowulf in general.
2125
2126	  To compile this driver as a module, choose M here: the module
2127	  will be called yellowfin.  This is recommended.
2128
2129config R8169
2130	tristate "Realtek 8169 gigabit ethernet support"
2131	depends on PCI
2132	select CRC32
2133	select MII
2134	---help---
2135	  Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2136
2137	  To compile this driver as a module, choose M here: the module
2138	  will be called r8169.  This is recommended.
2139
2140config R8169_VLAN
2141	bool "VLAN support"
2142	depends on R8169 && VLAN_8021Q
2143	---help---
2144	  Say Y here for the r8169 driver to support the functions required
2145	  by the kernel 802.1Q code.
2146
2147	  If in doubt, say Y.
2148
2149config SB1250_MAC
2150	tristate "SB1250 Gigabit Ethernet support"
2151	depends on SIBYTE_SB1xxx_SOC
2152	select PHYLIB
2153	---help---
2154	  This driver supports Gigabit Ethernet interfaces based on the
2155	  Broadcom SiByte family of System-On-a-Chip parts.  They include
2156	  the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2157	  and BCM1480 chips.
2158
2159	  To compile this driver as a module, choose M here: the module
2160	  will be called sb1250-mac.
2161
2162config SIS190
2163	tristate "SiS190/SiS191 gigabit ethernet support"
2164	depends on PCI
2165	select CRC32
2166	select MII
2167	---help---
2168	  Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2169	  a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2170	  appear in lan on motherboard designs which are based on SiS 965
2171	  and SiS 966 south bridge.
2172
2173	  To compile this driver as a module, choose M here: the module
2174	  will be called sis190.  This is recommended.
2175
2176config SKGE
2177	tristate "New SysKonnect GigaEthernet support"
2178	depends on PCI
2179	select CRC32
2180	---help---
2181	  This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2182	  and related Gigabit Ethernet adapters. It is a new smaller driver
2183	  with better performance and more complete ethtool support.
2184
2185	  It does not support the link failover and network management
2186	  features that "portable" vendor supplied sk98lin driver does.
2187
2188	  This driver supports adapters based on the original Yukon chipset:
2189	  Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2190	  Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2191
2192	  It does not support the newer Yukon2 chipset: a separate driver,
2193	  sky2, is provided for Yukon2-based adapters.
2194
2195	  To compile this driver as a module, choose M here: the module
2196	  will be called skge.  This is recommended.
2197
2198config SKGE_DEBUG
2199       bool "Debugging interface"
2200       depends on SKGE && DEBUG_FS
2201       help
2202	 This option adds the ability to dump driver state for debugging.
2203	 The file debugfs/skge/ethX displays the state of the internal
2204	 transmit and receive rings.
2205
2206	 If unsure, say N.
2207
2208config SKY2
2209	tristate "SysKonnect Yukon2 support"
2210	depends on PCI
2211	select CRC32
2212	---help---
2213	  This driver supports Gigabit Ethernet adapters based on the
2214	  Marvell Yukon 2 chipset:
2215	  Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2216	  88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2217
2218	  There is companion driver for the older Marvell Yukon and
2219	  Genesis based adapters: skge.
2220
2221	  To compile this driver as a module, choose M here: the module
2222	  will be called sky2.  This is recommended.
2223
2224config SKY2_DEBUG
2225       bool "Debugging interface"
2226       depends on SKY2 && DEBUG_FS
2227       help
2228	 This option adds the ability to dump driver state for debugging.
2229	 The file debugfs/sky2/ethX displays the state of the internal
2230	 transmit and receive rings.
2231
2232	 If unsure, say N.
2233
2234config VIA_VELOCITY
2235	tristate "VIA Velocity support"
2236	depends on PCI
2237	select CRC32
2238	select CRC_CCITT
2239	select MII
2240	help
2241	  If you have a VIA "Velocity" based network card say Y here.
2242
2243	  To compile this driver as a module, choose M here. The module
2244	  will be called via-velocity.
2245
2246config TIGON3
2247	tristate "Broadcom Tigon3 support"
2248	depends on PCI
2249	select PHYLIB
2250	help
2251	  This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2252
2253	  To compile this driver as a module, choose M here: the module
2254	  will be called tg3.  This is recommended.
2255
2256config BNX2
2257	tristate "Broadcom NetXtremeII support"
2258	depends on PCI
2259	select CRC32
2260	select FW_LOADER
2261	help
2262	  This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2263
2264	  To compile this driver as a module, choose M here: the module
2265	  will be called bnx2.  This is recommended.
2266
2267config SPIDER_NET
2268	tristate "Spider Gigabit Ethernet driver"
2269	depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2270	select FW_LOADER
2271	help
2272	  This driver supports the Gigabit Ethernet chips present on the
2273	  Cell Processor-Based Blades from IBM.
2274
2275config TSI108_ETH
2276	   tristate "Tundra TSI108 gigabit Ethernet support"
2277	   depends on TSI108_BRIDGE
2278	   help
2279	     This driver supports Tundra TSI108 gigabit Ethernet ports.
2280	     To compile this driver as a module, choose M here: the module
2281	     will be called tsi108_eth.
2282
2283config GELIC_NET
2284	tristate "PS3 Gigabit Ethernet driver"
2285	depends on PPC_PS3
2286	select PS3_SYS_MANAGER
2287	help
2288	  This driver supports the network device on the PS3 game
2289	  console.  This driver has built-in support for Ethernet.
2290
2291	  To compile this driver as a module, choose M here: the
2292	  module will be called ps3_gelic.
2293
2294config GELIC_WIRELESS
2295	bool "PS3 Wireless support"
2296	depends on GELIC_NET
2297	select WIRELESS_EXT
2298	help
2299	  This option adds the support for the wireless feature of PS3.
2300	  If you have the wireless-less model of PS3 or have no plan to
2301	  use wireless feature, disabling this option saves memory.  As
2302	  the driver automatically distinguishes the models, you can
2303	  safely enable this option even if you have a wireless-less model.
2304
2305config GELIC_WIRELESS_OLD_PSK_INTERFACE
2306       bool "PS3 Wireless private PSK interface (OBSOLETE)"
2307       depends on GELIC_WIRELESS
2308       help
2309          This option retains the obsolete private interface to pass
2310          the PSK from user space programs to the driver.  The PSK
2311          stands for 'Pre Shared Key' and is used for WPA[2]-PSK
2312          (WPA-Personal) environment.
2313          If WPA[2]-PSK is used and you need to use old programs that
2314          support only this old interface, say Y.  Otherwise N.
2315
2316          If unsure, say N.
2317
2318config FSL_PQ_MDIO
2319	tristate "Freescale PQ MDIO"
2320	depends on FSL_SOC
2321	select PHYLIB
2322	help
2323	  This driver supports the MDIO bus used by the gianfar and UCC drivers.
2324
2325config GIANFAR
2326	tristate "Gianfar Ethernet"
2327	depends on FSL_SOC
2328	select FSL_PQ_MDIO
2329	select PHYLIB
2330	select CRC32
2331	help
2332	  This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2333	  and MPC86xx family of chips, and the FEC on the 8540.
2334
2335config UCC_GETH
2336	tristate "Freescale QE Gigabit Ethernet"
2337	depends on QUICC_ENGINE
2338	select FSL_PQ_MDIO
2339	select PHYLIB
2340	help
2341	  This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2342	  which is available on some Freescale SOCs.
2343
2344config UGETH_MAGIC_PACKET
2345	bool "Magic Packet detection support"
2346	depends on UCC_GETH
2347
2348config UGETH_TX_ON_DEMAND
2349	bool "Transmit on Demand support"
2350	depends on UCC_GETH
2351
2352config MV643XX_ETH
2353	tristate "Marvell Discovery (643XX) and Orion ethernet support"
2354	depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
2355	select INET_LRO
2356	select PHYLIB
2357	help
2358	  This driver supports the gigabit ethernet MACs in the
2359	  Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2360	  in the Marvell Orion ARM SoC family.
2361
2362	  Some boards that use the Discovery chipset are the Momenco
2363	  Ocelot C and Jaguar ATX and Pegasos II.
2364
2365config QLA3XXX
2366	tristate "QLogic QLA3XXX Network Driver Support"
2367	depends on PCI
2368	help
2369	  This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2370
2371	  To compile this driver as a module, choose M here: the module
2372	  will be called qla3xxx.
2373
2374config ATL1
2375	tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2376	depends on PCI
2377	select CRC32
2378	select MII
2379	help
2380	  This driver supports the Atheros/Attansic L1 gigabit ethernet
2381	  adapter.
2382
2383	  To compile this driver as a module, choose M here.  The module
2384	  will be called atl1.
2385
2386config ATL1E
2387	tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2388	depends on PCI && EXPERIMENTAL
2389	select CRC32
2390	select MII
2391	help
2392	  This driver supports the Atheros L1E gigabit ethernet adapter.
2393
2394	  To compile this driver as a module, choose M here.  The module
2395	  will be called atl1e.
2396
2397config ATL1C
2398	tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2399	depends on PCI && EXPERIMENTAL
2400	select CRC32
2401	select MII
2402	help
2403	  This driver supports the Atheros L1C gigabit ethernet adapter.
2404
2405	  To compile this driver as a module, choose M here.  The module
2406	  will be called atl1c.
2407
2408config JME
2409	tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2410	depends on PCI
2411	select CRC32
2412	select MII
2413	---help---
2414	  This driver supports the PCI-Express gigabit ethernet adapters
2415	  based on JMicron JMC250 chipset.
2416
2417	  To compile this driver as a module, choose M here. The module
2418	  will be called jme.
2419
2420endif # NETDEV_1000
2421
2422#
2423#	10 Gigabit Ethernet
2424#
2425
2426menuconfig NETDEV_10000
2427	bool "Ethernet (10000 Mbit)"
2428	depends on !UML
2429	default y
2430	---help---
2431	  Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2432	  This option alone does not add any kernel code.
2433
2434	  If you say N, all options in this submenu will be skipped and disabled.
2435
2436if NETDEV_10000
2437
2438config CHELSIO_T1
2439        tristate "Chelsio 10Gb Ethernet support"
2440        depends on PCI
2441	select CRC32
2442        help
2443          This driver supports Chelsio gigabit and 10-gigabit
2444          Ethernet cards. More information about adapter features and
2445	  performance tuning is in <file:Documentation/networking/cxgb.txt>.
2446
2447          For general information about Chelsio and our products, visit
2448          our website at <http://www.chelsio.com>.
2449
2450          For customer support, please visit our customer support page at
2451          <http://www.chelsio.com/support.htm>.
2452
2453          Please send feedback to <linux-bugs@chelsio.com>.
2454
2455          To compile this driver as a module, choose M here: the module
2456          will be called cxgb.
2457
2458config CHELSIO_T1_1G
2459        bool "Chelsio gigabit Ethernet support"
2460        depends on CHELSIO_T1
2461        help
2462          Enables support for Chelsio's gigabit Ethernet PCI cards.  If you
2463          are using only 10G cards say 'N' here.
2464
2465config CHELSIO_T3_DEPENDS
2466	tristate
2467	depends on PCI && INET
2468	default y
2469
2470config CHELSIO_T3
2471	tristate "Chelsio Communications T3 10Gb Ethernet support"
2472	depends on CHELSIO_T3_DEPENDS
2473	select FW_LOADER
2474	help
2475	  This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2476	  adapters.
2477
2478	  For general information about Chelsio and our products, visit
2479	  our website at <http://www.chelsio.com>.
2480
2481	  For customer support, please visit our customer support page at
2482	  <http://www.chelsio.com/support.htm>.
2483
2484	  Please send feedback to <linux-bugs@chelsio.com>.
2485
2486	  To compile this driver as a module, choose M here: the module
2487	  will be called cxgb3.
2488
2489config EHEA
2490	tristate "eHEA Ethernet support"
2491	depends on IBMEBUS && INET && SPARSEMEM
2492	select INET_LRO
2493	---help---
2494	  This driver supports the IBM pSeries eHEA ethernet adapter.
2495
2496	  To compile the driver as a module, choose M here. The module
2497	  will be called ehea.
2498
2499config ENIC
2500	tristate "Cisco 10G Ethernet NIC support"
2501	depends on PCI && INET
2502	select INET_LRO
2503	help
2504	  This enables the support for the Cisco 10G Ethernet card.
2505
2506config IXGBE
2507	tristate "Intel(R) 10GbE PCI Express adapters support"
2508	depends on PCI && INET
2509	---help---
2510	  This driver supports Intel(R) 10GbE PCI Express family of
2511	  adapters.  For more information on how to identify your adapter, go
2512	  to the Adapter & Driver ID Guide at:
2513
2514	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2515
2516	  For general information and support, go to the Intel support
2517	  website at:
2518
2519	  <http://support.intel.com>
2520
2521	  To compile this driver as a module, choose M here. The module
2522	  will be called ixgbe.
2523
2524config IXGBE_DCA
2525	bool "Direct Cache Access (DCA) Support"
2526	default y
2527	depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2528	---help---
2529	  Say Y here if you want to use Direct Cache Access (DCA) in the
2530	  driver.  DCA is a method for warming the CPU cache before data
2531	  is used, with the intent of lessening the impact of cache misses.
2532
2533config IXGBE_DCB
2534	bool "Data Center Bridging (DCB) Support"
2535	default n
2536	depends on IXGBE && DCB
2537	---help---
2538	  Say Y here if you want to use Data Center Bridging (DCB) in the
2539	  driver.
2540
2541	  If unsure, say N.
2542
2543config IXGB
2544	tristate "Intel(R) PRO/10GbE support"
2545	depends on PCI
2546	---help---
2547	  This driver supports Intel(R) PRO/10GbE family of adapters for
2548	  PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2549	  instead. For more information on how to identify your adapter, go
2550	  to the Adapter & Driver ID Guide at:
2551
2552	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2553
2554	  For general information and support, go to the Intel support
2555	  website at:
2556
2557	  <http://support.intel.com>
2558
2559	  More specific information on configuring the driver is in
2560	  <file:Documentation/networking/ixgb.txt>.
2561
2562	  To compile this driver as a module, choose M here. The module
2563	  will be called ixgb.
2564
2565config S2IO
2566	tristate "S2IO 10Gbe XFrame NIC"
2567	depends on PCI
2568	---help---
2569	  This driver supports the 10Gbe XFrame NIC of S2IO.
2570	  More specific information on configuring the driver is in
2571	  <file:Documentation/networking/s2io.txt>.
2572
2573config VXGE
2574	tristate "Neterion X3100 Series 10GbE PCIe Server Adapter"
2575	depends on PCI && INET
2576	---help---
2577	  This driver supports Neterion Inc's X3100 Series 10 GbE PCIe
2578	  I/O Virtualized Server Adapter.
2579	  More specific information on configuring the driver is in
2580	  <file:Documentation/networking/vxge.txt>.
2581
2582config VXGE_DEBUG_TRACE_ALL
2583	bool "Enabling All Debug trace statments in driver"
2584	default n
2585	depends on VXGE
2586	---help---
2587	  Say Y here if you want to enabling all the debug trace statements in
2588	  driver. By  default only few debug trace statements are enabled.
2589
2590config MYRI10GE
2591	tristate "Myricom Myri-10G Ethernet support"
2592	depends on PCI && INET
2593	select FW_LOADER
2594	select CRC32
2595	select INET_LRO
2596	---help---
2597	  This driver supports Myricom Myri-10G Dual Protocol interface in
2598	  Ethernet mode. If the eeprom on your board is not recent enough,
2599	  you will need a newer firmware image.
2600	  You may get this image or more information, at:
2601
2602	  <http://www.myri.com/scs/download-Myri10GE.html>
2603
2604	  To compile this driver as a module, choose M here. The module
2605	  will be called myri10ge.
2606
2607config MYRI10GE_DCA
2608	bool "Direct Cache Access (DCA) Support"
2609	default y
2610	depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2611	---help---
2612	  Say Y here if you want to use Direct Cache Access (DCA) in the
2613	  driver.  DCA is a method for warming the CPU cache before data
2614	  is used, with the intent of lessening the impact of cache misses.
2615
2616config NETXEN_NIC
2617	tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2618	depends on PCI
2619	help
2620	  This enables the support for NetXen's Gigabit Ethernet card.
2621
2622config NIU
2623	tristate "Sun Neptune 10Gbit Ethernet support"
2624	depends on PCI
2625	help
2626	  This enables support for cards based upon Sun's
2627	  Neptune chipset.
2628
2629config PASEMI_MAC
2630	tristate "PA Semi 1/10Gbit MAC"
2631	depends on PPC_PASEMI && PCI
2632	select PHYLIB
2633	select INET_LRO
2634	help
2635	  This driver supports the on-chip 1/10Gbit Ethernet controller on
2636	  PA Semi's PWRficient line of chips.
2637
2638config MLX4_EN
2639	tristate "Mellanox Technologies 10Gbit Ethernet support"
2640	depends on PCI && INET
2641	select MLX4_CORE
2642	select INET_LRO
2643	help
2644	  This driver supports Mellanox Technologies ConnectX Ethernet
2645	  devices.
2646
2647config MLX4_CORE
2648	tristate
2649	depends on PCI
2650	default n
2651
2652config MLX4_DEBUG
2653	bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2654	depends on MLX4_CORE
2655	default y
2656	---help---
2657	  This option causes debugging code to be compiled into the
2658	  mlx4_core driver.  The output can be turned on via the
2659	  debug_level module parameter (which can also be set after
2660	  the driver is loaded through sysfs).
2661
2662config TEHUTI
2663	tristate "Tehuti Networks 10G Ethernet"
2664	depends on PCI
2665	help
2666	  Tehuti Networks 10G Ethernet NIC
2667
2668config BNX2X
2669	tristate "Broadcom NetXtremeII 10Gb support"
2670	depends on PCI
2671	select ZLIB_INFLATE
2672	select LIBCRC32C
2673	help
2674	  This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2675	  To compile this driver as a module, choose M here: the module
2676	  will be called bnx2x.  This is recommended.
2677
2678config QLGE
2679	tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2680	depends on PCI
2681	help
2682	  This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2683
2684	  To compile this driver as a module, choose M here: the module
2685	  will be called qlge.
2686
2687source "drivers/net/sfc/Kconfig"
2688
2689source "drivers/net/benet/Kconfig"
2690
2691endif # NETDEV_10000
2692
2693source "drivers/net/tokenring/Kconfig"
2694
2695source "drivers/net/wireless/Kconfig"
2696
2697source "drivers/net/wimax/Kconfig"
2698
2699source "drivers/net/usb/Kconfig"
2700
2701source "drivers/net/pcmcia/Kconfig"
2702
2703source "drivers/net/wan/Kconfig"
2704
2705source "drivers/atm/Kconfig"
2706
2707source "drivers/s390/net/Kconfig"
2708
2709config XEN_NETDEV_FRONTEND
2710	tristate "Xen network device frontend driver"
2711	depends on XEN
2712	default y
2713	help
2714	  The network device frontend driver allows the kernel to
2715	  access network devices exported exported by a virtual
2716	  machine containing a physical network device driver. The
2717	  frontend driver is intended for unprivileged guest domains;
2718	  if you are compiling a kernel for a Xen guest, you almost
2719	  certainly want to enable this.
2720
2721config ISERIES_VETH
2722	tristate "iSeries Virtual Ethernet driver support"
2723	depends on PPC_ISERIES
2724
2725config RIONET
2726	tristate "RapidIO Ethernet over messaging driver support"
2727	depends on RAPIDIO
2728
2729config RIONET_TX_SIZE
2730	int "Number of outbound queue entries"
2731	depends on RIONET
2732	default "128"
2733
2734config RIONET_RX_SIZE
2735	int "Number of inbound queue entries"
2736	depends on RIONET
2737	default "128"
2738
2739config FDDI
2740	tristate "FDDI driver support"
2741	depends on (PCI || EISA || TC)
2742	help
2743	  Fiber Distributed Data Interface is a high speed local area network
2744	  design; essentially a replacement for high speed Ethernet. FDDI can
2745	  run over copper or fiber. If you are connected to such a network and
2746	  want a driver for the FDDI card in your computer, say Y here (and
2747	  then also Y to the driver for your FDDI card, below). Most people
2748	  will say N.
2749
2750config DEFXX
2751	tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
2752	depends on FDDI && (PCI || EISA || TC)
2753	---help---
2754	  This is support for the DIGITAL series of TURBOchannel (DEFTA),
2755	  EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
2756	  to a local FDDI network.
2757
2758	  To compile this driver as a module, choose M here: the module
2759	  will be called defxx.  If unsure, say N.
2760
2761config DEFXX_MMIO
2762	bool
2763	prompt "Use MMIO instead of PIO" if PCI || EISA
2764	depends on DEFXX
2765	default n if PCI || EISA
2766	default y
2767	---help---
2768	  This instructs the driver to use EISA or PCI memory-mapped I/O
2769	  (MMIO) as appropriate instead of programmed I/O ports (PIO).
2770	  Enabling this gives an improvement in processing time in parts
2771	  of the driver, but it may cause problems with EISA (DEFEA)
2772	  adapters.  TURBOchannel does not have the concept of I/O ports,
2773	  so MMIO is always used for these (DEFTA) adapters.
2774
2775	  If unsure, say N.
2776
2777config SKFP
2778	tristate "SysKonnect FDDI PCI support"
2779	depends on FDDI && PCI
2780	select BITREVERSE
2781	---help---
2782	  Say Y here if you have a SysKonnect FDDI PCI adapter.
2783	  The following adapters are supported by this driver:
2784	  - SK-5521 (SK-NET FDDI-UP)
2785	  - SK-5522 (SK-NET FDDI-UP DAS)
2786	  - SK-5541 (SK-NET FDDI-FP)
2787	  - SK-5543 (SK-NET FDDI-LP)
2788	  - SK-5544 (SK-NET FDDI-LP DAS)
2789	  - SK-5821 (SK-NET FDDI-UP64)
2790	  - SK-5822 (SK-NET FDDI-UP64 DAS)
2791	  - SK-5841 (SK-NET FDDI-FP64)
2792	  - SK-5843 (SK-NET FDDI-LP64)
2793	  - SK-5844 (SK-NET FDDI-LP64 DAS)
2794	  - Netelligent 100 FDDI DAS Fibre SC
2795	  - Netelligent 100 FDDI SAS Fibre SC
2796	  - Netelligent 100 FDDI DAS UTP
2797	  - Netelligent 100 FDDI SAS UTP
2798	  - Netelligent 100 FDDI SAS Fibre MIC
2799
2800	  Read <file:Documentation/networking/skfp.txt> for information about
2801	  the driver.
2802
2803	  Questions concerning this driver can be addressed to:
2804	  <linux@syskonnect.de>
2805
2806	  To compile this driver as a module, choose M here: the module
2807	  will be called skfp.  This is recommended.
2808
2809config HIPPI
2810	bool "HIPPI driver support (EXPERIMENTAL)"
2811	depends on EXPERIMENTAL && INET && PCI
2812	help
2813	  HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
2814	  1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
2815	  can run over copper (25m) or fiber (300m on multi-mode or 10km on
2816	  single-mode). HIPPI networks are commonly used for clusters and to
2817	  connect to super computers. If you are connected to a HIPPI network
2818	  and have a HIPPI network card in your computer that you want to use
2819	  under Linux, say Y here (you must also remember to enable the driver
2820	  for your HIPPI card below). Most people will say N here.
2821
2822config ROADRUNNER
2823	tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
2824	depends on HIPPI && PCI
2825	help
2826	  Say Y here if this is your PCI HIPPI network card.
2827
2828	  To compile this driver as a module, choose M here: the module
2829	  will be called rrunner.  If unsure, say N.
2830
2831config ROADRUNNER_LARGE_RINGS
2832	bool "Use large TX/RX rings (EXPERIMENTAL)"
2833	depends on ROADRUNNER
2834	help
2835	  If you say Y here, the RoadRunner driver will preallocate up to 2 MB
2836	  of additional memory to allow for fastest operation, both for
2837	  transmitting and receiving. This memory cannot be used by any other
2838	  kernel code or by user space programs. Say Y here only if you have
2839	  the memory.
2840
2841config PLIP
2842	tristate "PLIP (parallel port) support"
2843	depends on PARPORT
2844	---help---
2845	  PLIP (Parallel Line Internet Protocol) is used to create a
2846	  reasonably fast mini network consisting of two (or, rarely, more)
2847	  local machines.  A PLIP link from a Linux box is a popular means to
2848	  install a Linux distribution on a machine which doesn't have a
2849	  CD-ROM drive (a minimal system has to be transferred with floppies
2850	  first). The kernels on both machines need to have this PLIP option
2851	  enabled for this to work.
2852
2853	  The PLIP driver has two modes, mode 0 and mode 1.  The parallel
2854	  ports (the connectors at the computers with 25 holes) are connected
2855	  with "null printer" or "Turbo Laplink" cables which can transmit 4
2856	  bits at a time (mode 0) or with special PLIP cables, to be used on
2857	  bidirectional parallel ports only, which can transmit 8 bits at a
2858	  time (mode 1); you can find the wiring of these cables in
2859	  <file:Documentation/networking/PLIP.txt>.  The cables can be up to
2860	  15m long.  Mode 0 works also if one of the machines runs DOS/Windows
2861	  and has some PLIP software installed, e.g. the Crynwr PLIP packet
2862	  driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
2863	  and winsock or NCSA's telnet.
2864
2865	  If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
2866	  as the NET-3-HOWTO, both available from
2867	  <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
2868	  protocol has been changed and this PLIP driver won't work together
2869	  with the PLIP support in Linux versions 1.0.x.  This option enlarges
2870	  your kernel by about 8 KB.
2871
2872	  To compile this driver as a module, choose M here. The module
2873	  will be called plip. If unsure, say Y or M, in case you buy
2874	  a laptop later.
2875
2876config PPP
2877	tristate "PPP (point-to-point protocol) support"
2878	select SLHC
2879	---help---
2880	  PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
2881	  the same purpose: sending Internet traffic over telephone (and other
2882	  serial) lines.  Ask your access provider if they support it, because
2883	  otherwise you can't use it; most Internet access providers these
2884	  days support PPP rather than SLIP.
2885
2886	  To use PPP, you need an additional program called pppd as described
2887	  in the PPP-HOWTO, available at
2888	  <http://www.tldp.org/docs.html#howto>.  Make sure that you have
2889	  the version of pppd recommended in <file:Documentation/Changes>.
2890	  The PPP option enlarges your kernel by about 16 KB.
2891
2892	  There are actually two versions of PPP: the traditional PPP for
2893	  asynchronous lines, such as regular analog phone lines, and
2894	  synchronous PPP which can be used over digital ISDN lines for
2895	  example.  If you want to use PPP over phone lines or other
2896	  asynchronous serial lines, you need to say Y (or M) here and also to
2897	  the next option, "PPP support for async serial ports".  For PPP over
2898	  synchronous lines, you should say Y (or M) here and to "Support
2899	  synchronous PPP", below.
2900
2901	  If you said Y to "Version information on all symbols" above, then
2902	  you cannot compile the PPP driver into the kernel; you can then only
2903	  compile it as a module. To compile this driver as a module, choose M
2904	  here. The module will be called ppp_generic.
2905
2906config PPP_MULTILINK
2907	bool "PPP multilink support (EXPERIMENTAL)"
2908	depends on PPP && EXPERIMENTAL
2909	help
2910	  PPP multilink is a protocol (defined in RFC 1990) which allows you
2911	  to combine several (logical or physical) lines into one logical PPP
2912	  connection, so that you can utilize your full bandwidth.
2913
2914	  This has to be supported at the other end as well and you need a
2915	  version of the pppd daemon which understands the multilink protocol.
2916
2917	  If unsure, say N.
2918
2919config PPP_FILTER
2920	bool "PPP filtering"
2921	depends on PPP
2922	help
2923	  Say Y here if you want to be able to filter the packets passing over
2924	  PPP interfaces.  This allows you to control which packets count as
2925	  activity (i.e. which packets will reset the idle timer or bring up
2926	  a demand-dialed link) and which packets are to be dropped entirely.
2927	  You need to say Y here if you wish to use the pass-filter and
2928	  active-filter options to pppd.
2929
2930	  If unsure, say N.
2931
2932config PPP_ASYNC
2933	tristate "PPP support for async serial ports"
2934	depends on PPP
2935	select CRC_CCITT
2936	---help---
2937	  Say Y (or M) here if you want to be able to use PPP over standard
2938	  asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
2939	  a modem (not a synchronous or ISDN modem) to contact your ISP, you
2940	  need this option.
2941
2942	  To compile this driver as a module, choose M here.
2943
2944	  If unsure, say Y.
2945
2946config PPP_SYNC_TTY
2947	tristate "PPP support for sync tty ports"
2948	depends on PPP
2949	help
2950	  Say Y (or M) here if you want to be able to use PPP over synchronous
2951	  (HDLC) tty devices, such as the SyncLink adapter. These devices
2952	  are often used for high-speed leased lines like T1/E1.
2953
2954	  To compile this driver as a module, choose M here.
2955
2956config PPP_DEFLATE
2957	tristate "PPP Deflate compression"
2958	depends on PPP
2959	select ZLIB_INFLATE
2960	select ZLIB_DEFLATE
2961	---help---
2962	  Support for the Deflate compression method for PPP, which uses the
2963	  Deflate algorithm (the same algorithm that gzip uses) to compress
2964	  each PPP packet before it is sent over the wire.  The machine at the
2965	  other end of the PPP link (usually your ISP) has to support the
2966	  Deflate compression method as well for this to be useful.  Even if
2967	  they don't support it, it is safe to say Y here.
2968
2969	  To compile this driver as a module, choose M here.
2970
2971config PPP_BSDCOMP
2972	tristate "PPP BSD-Compress compression"
2973	depends on PPP
2974	---help---
2975	  Support for the BSD-Compress compression method for PPP, which uses
2976	  the LZW compression method to compress each PPP packet before it is
2977	  sent over the wire. The machine at the other end of the PPP link
2978	  (usually your ISP) has to support the BSD-Compress compression
2979	  method as well for this to be useful. Even if they don't support it,
2980	  it is safe to say Y here.
2981
2982	  The PPP Deflate compression method ("PPP Deflate compression",
2983	  above) is preferable to BSD-Compress, because it compresses better
2984	  and is patent-free.
2985
2986	  Note that the BSD compression code will always be compiled as a
2987	  module; it is called bsd_comp and will show up in the directory
2988	  modules once you have said "make modules". If unsure, say N.
2989
2990config PPP_MPPE
2991       tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
2992       depends on PPP && EXPERIMENTAL
2993       select CRYPTO
2994       select CRYPTO_SHA1
2995       select CRYPTO_ARC4
2996       select CRYPTO_ECB
2997       ---help---
2998         Support for the MPPE Encryption protocol, as employed by the
2999	 Microsoft Point-to-Point Tunneling Protocol.
3000
3001	 See http://pptpclient.sourceforge.net/ for information on
3002	 configuring PPTP clients and servers to utilize this method.
3003
3004config PPPOE
3005	tristate "PPP over Ethernet (EXPERIMENTAL)"
3006	depends on EXPERIMENTAL && PPP
3007	help
3008	  Support for PPP over Ethernet.
3009
3010	  This driver requires the latest version of pppd from the CVS
3011	  repository at cvs.samba.org.  Alternatively, see the
3012	  RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3013	  which contains instruction on how to use this driver (under
3014	  the heading "Kernel mode PPPoE").
3015
3016config PPPOATM
3017	tristate "PPP over ATM"
3018	depends on ATM && PPP
3019	help
3020	  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3021	  This implementation does not yet comply with section 8 of RFC2364,
3022	  which can lead to bad results if the ATM peer loses state and
3023	  changes its encapsulation unilaterally.
3024
3025config PPPOL2TP
3026	tristate "PPP over L2TP (EXPERIMENTAL)"
3027	depends on EXPERIMENTAL && PPP && INET
3028	help
3029	  Support for PPP-over-L2TP socket family. L2TP is a protocol
3030	  used by ISPs and enterprises to tunnel PPP traffic over UDP
3031	  tunnels. L2TP is replacing PPTP for VPN uses.
3032
3033	  This kernel component handles only L2TP data packets: a
3034	  userland daemon handles L2TP the control protocol (tunnel
3035	  and session setup). One such daemon is OpenL2TP
3036	  (http://openl2tp.sourceforge.net/).
3037
3038config SLIP
3039	tristate "SLIP (serial line) support"
3040	---help---
3041	  Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3042	  connect to your Internet service provider or to connect to some
3043	  other local Unix box or if you want to configure your Linux box as a
3044	  Slip/CSlip server for other people to dial in. SLIP (Serial Line
3045	  Internet Protocol) is a protocol used to send Internet traffic over
3046	  serial connections such as telephone lines or null modem cables;
3047	  nowadays, the protocol PPP is more commonly used for this same
3048	  purpose.
3049
3050	  Normally, your access provider has to support SLIP in order for you
3051	  to be able to use it, but there is now a SLIP emulator called SLiRP
3052	  around (available from
3053	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3054	  allows you to use SLIP over a regular dial up shell connection. If
3055	  you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3056	  NET-3-HOWTO, available from
3057	  <http://www.tldp.org/docs.html#howto>, explains how to
3058	  configure SLIP. Note that you don't need this option if you just
3059	  want to run term (term is a program which gives you almost full
3060	  Internet connectivity if you have a regular dial up shell account on
3061	  some Internet connected Unix computer. Read
3062	  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3063	  support will enlarge your kernel by about 4 KB. If unsure, say N.
3064
3065	  To compile this driver as a module, choose M here. The module
3066	  will be called slip.
3067
3068config SLIP_COMPRESSED
3069	bool "CSLIP compressed headers"
3070	depends on SLIP
3071	select SLHC
3072	---help---
3073	  This protocol is faster than SLIP because it uses compression on the
3074	  TCP/IP headers (not on the data itself), but it has to be supported
3075	  on both ends. Ask your access provider if you are not sure and
3076	  answer Y, just in case. You will still be able to use plain SLIP. If
3077	  you plan to use SLiRP, the SLIP emulator (available from
3078	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3079	  allows you to use SLIP over a regular dial up shell connection, you
3080	  definitely want to say Y here. The NET-3-HOWTO, available from
3081	  <http://www.tldp.org/docs.html#howto>, explains how to configure
3082	  CSLIP. This won't enlarge your kernel.
3083
3084config SLHC
3085	tristate
3086	help
3087	  This option enables Van Jacobsen serial line header compression
3088	  routines.
3089
3090config SLIP_SMART
3091	bool "Keepalive and linefill"
3092	depends on SLIP
3093	help
3094	  Adds additional capabilities to the SLIP driver to support the
3095	  RELCOM line fill and keepalive monitoring. Ideal on poor quality
3096	  analogue lines.
3097
3098config SLIP_MODE_SLIP6
3099	bool "Six bit SLIP encapsulation"
3100	depends on SLIP
3101	help
3102	  Just occasionally you may need to run IP over hostile serial
3103	  networks that don't pass all control characters or are only seven
3104	  bit. Saying Y here adds an extra mode you can use with SLIP:
3105	  "slip6". In this mode, SLIP will only send normal ASCII symbols over
3106	  the serial device. Naturally, this has to be supported at the other
3107	  end of the link as well. It's good enough, for example, to run IP
3108	  over the async ports of a Camtec JNT Pad. If unsure, say N.
3109
3110config NET_FC
3111	bool "Fibre Channel driver support"
3112	depends on SCSI && PCI
3113	help
3114	  Fibre Channel is a high speed serial protocol mainly used to connect
3115	  large storage devices to the computer; it is compatible with and
3116	  intended to replace SCSI.
3117
3118	  If you intend to use Fibre Channel, you need to have a Fibre channel
3119	  adaptor card in your computer; say Y here and to the driver for your
3120	  adaptor below. You also should have said Y to "SCSI support" and
3121	  "SCSI generic support".
3122
3123config NETCONSOLE
3124	tristate "Network console logging support (EXPERIMENTAL)"
3125	depends on EXPERIMENTAL
3126	---help---
3127	If you want to log kernel messages over the network, enable this.
3128	See <file:Documentation/networking/netconsole.txt> for details.
3129
3130config NETCONSOLE_DYNAMIC
3131	bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
3132	depends on NETCONSOLE && SYSFS && EXPERIMENTAL
3133	select CONFIGFS_FS
3134	help
3135	  This option enables the ability to dynamically reconfigure target
3136	  parameters (interface, IP addresses, port numbers, MAC addresses)
3137	  at runtime through a userspace interface exported using configfs.
3138	  See <file:Documentation/networking/netconsole.txt> for details.
3139
3140config NETPOLL
3141	def_bool NETCONSOLE
3142
3143config NETPOLL_TRAP
3144	bool "Netpoll traffic trapping"
3145	default n
3146	depends on NETPOLL
3147
3148config NET_POLL_CONTROLLER
3149	def_bool NETPOLL
3150
3151config VIRTIO_NET
3152	tristate "Virtio network driver (EXPERIMENTAL)"
3153	depends on EXPERIMENTAL && VIRTIO
3154	---help---
3155	  This is the virtual network driver for virtio.  It can be used with
3156          lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
3157
3158endif # NETDEVICES
3159