Context Navigation

Kconfig @ 14511

Last change on this file since 14511 was 14511, checked in by BrainSlayer, 3 years ago
wndr3700 usb led
File size: 116.5 KB

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

Note: See TracBrowser for help on using the repository browser.

Download in other formats:

Original Format