Kernel

Kernel Git Source Tree

Root/drivers/net/Kconfig

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

Download this file

Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.2
jz-3.3
jz-3.4
jz47xx
jz47xx-2.6.38
master
xiangfu/openwrt/v3.0.0
xiangfu/openwrt/v3.2.1

Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7

Kernel

Kernel Git Source Tree

Root/drivers/net/Kconfig

interactive