[linux-2.6-block.git] / drivers / usb / net / Kconfig

#
# USB Network devices configuration
#
comment "Networking support is needed for USB Network Adapter support"
	depends on USB && !NET

menu "USB Network Adapters"
	depends on USB && NET

config USB_CATC
	tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	select CRC32
	---help---
	  Say Y if you want to use one of the following 10Mbps USB Ethernet
	  device based on the EL1210A chip. Supported devices are:
	  Belkin F5U011
	  Belkin F5U111
	  CATC NetMate
	  CATC NetMate II
	  smartBridges smartNIC

	  This driver makes the adapter appear as a normal Ethernet interface,
	  typically on eth0, if it is the only ethernet device, or perhaps on
	  eth1, if you have a PCI or ISA ethernet card installed.

	  To compile this driver as a module, choose M here: the
	  module will be called catc.

config USB_KAWETH
	tristate "USB KLSI KL5USB101-based ethernet device support"
	---help---
	  Say Y here if you want to use one of the following 10Mbps only
	  USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
	  3Com 3C19250
	  ADS USB-10BT
	  ATEN USB Ethernet
	  ASANTE USB To Ethernet Adapter
	  AOX Endpoints USB Ethernet
	  Correga K.K.
	  D-Link DSB-650C and DU-E10
	  Entrega / Portgear E45
	  I-O DATA USB-ET/T
	  Jaton USB Ethernet Device Adapter
	  Kingston Technology USB Ethernet Adapter
	  Linksys USB10T
	  Mobility USB-Ethernet Adapter
	  NetGear EA-101
	  Peracom Enet and Enet2
	  Portsmith Express Ethernet Adapter
	  Shark Pocket Adapter
	  SMC 2202USB
	  Sony Vaio port extender

	  This driver is likely to work with most 10Mbps only USB Ethernet
	  adapters, including some "no brand" devices. It does NOT work on
	  SmartBridges smartNIC or on Belkin F5U111 devices - you should use
	  the CATC NetMate driver for those. If you are not sure which one
	  you need, select both, and the correct one should be selected for
	  you.

	  This driver makes the adapter appear as a normal Ethernet interface,
	  typically on eth0, if it is the only ethernet device, or perhaps on
	  eth1, if you have a PCI or ISA ethernet card installed.

	  To compile this driver as a module, choose M here: the
	  module will be called kaweth.

config USB_PEGASUS
	tristate "USB Pegasus/Pegasus-II based ethernet device support"
	select MII
	---help---
	  Say Y here if you know you have Pegasus or Pegasus-II based adapter.
	  If in doubt then look at <file:drivers/usb/net/pegasus.h> for the
	  complete list of supported devices.

	  If your particular adapter is not in the list and you are _sure_ it
	  is Pegasus or Pegasus II based then send me
	  <petkan@users.sourceforge.net> vendor and device IDs.

	  To compile this driver as a module, choose M here: the
	  module will be called pegasus.

config USB_RTL8150
	tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	help
	  Say Y here if you have RTL8150 based usb-ethernet adapter.
	  Send me <petkan@users.sourceforge.net> any comments you may have.
	  You can also check for updates at <http://pegasus2.sourceforge.net/>.

	  To compile this driver as a module, choose M here: the
	  module will be called rtl8150.

config USB_USBNET
	tristate "Multi-purpose USB Networking Framework"
	---help---
	  This driver supports several kinds of network links over USB,
	  with "minidrivers" built around a common network driver core
	  that supports deep queues for efficient transfers.  (This gives
	  better performance with small packets and at high speeds).

	  The USB host runs "usbnet", and the other end of the link might be:

	  - Another USB host, when using USB "network" or "data transfer"
	    cables.  These are often used to network laptops to PCs, like
	    "Laplink" parallel cables or some motherboards.  These rely
	    on specialized chips from many suppliers.

	  - An intelligent USB gadget, perhaps embedding a Linux system.
	    These include PDAs running Linux (iPaq, Yopy, Zaurus, and
	    others), and devices that interoperate using the standard
	    CDC-Ethernet specification (including many cable modems).

	  - Network adapter hardware (like those for 10/100 Ethernet) which
	    uses this driver framework.

	  The link will appear with a name like "usb0", when the link is
	  a two-node link, or "eth0" for most CDC-Ethernet devices.  Those
	  two-node links are most easily managed with Ethernet Bridging
	  (CONFIG_BRIDGE) instead of routing.

	  For more information see <http://www.linux-usb.org/usbnet/>.

	  To compile this driver as a module, choose M here: the
	  module will be called usbnet.

config USB_NET_AX8817X
	tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
	depends on USB_USBNET && NET_ETHERNET
	select CRC32
	select MII
	default y
	help
	  This option adds support for ASIX AX88xxx based USB 2.0
	  10/100 Ethernet adapters.

 	  This driver should work with at least the following devices:
	    * Aten UC210T
	    * ASIX AX88172
	    * Billionton Systems, USB2AR
	    * Buffalo LUA-U2-KTX
	    * Corega FEther USB2-TX
	    * D-Link DUB-E100
	    * Hawking UF200
	    * Linksys USB200M
	    * Netgear FA120
	    * Sitecom LN-029
	    * Intellinet USB 2.0 Ethernet
	    * ST Lab USB 2.0 Ethernet
	    * TrendNet TU2-ET100

	  This driver creates an interface named "ethX", where X depends on
	  what other networking devices you have in use.


config USB_NET_CDCETHER
	tristate "CDC Ethernet support (smart devices such as cable modems)"
	depends on USB_USBNET
	default y
	help
	  This option supports devices conforming to the Communication Device
	  Class (CDC) Ethernet Control Model, a specification that's easy to
	  implement in device firmware.  The CDC specifications are available
	  from <http://www.usb.org/>.

	  CDC Ethernet is an implementation option for DOCSIS cable modems
	  that support USB connectivity, used for non-Microsoft USB hosts.
	  The Linux-USB CDC Ethernet Gadget driver is an open implementation.
 	  This driver should work with at least the following devices:

 	    * Ericsson PipeRider (all variants)
 	    * Motorola (DM100 and SB4100)
 	    * Broadcom Cable Modem (reference design)
 	    * Toshiba PCX1100U
	    * ...

	  This driver creates an interface named "ethX", where X depends on
	  what other networking devices you have in use.  However, if the
	  IEEE 802 "local assignment" bit is set in the address, a "usbX"
	  name is used instead.

config USB_NET_GL620A
	tristate "GeneSys GL620USB-A based cables"
	depends on USB_USBNET
	help
	  Choose this option if you're using a host-to-host cable,
	  or PC2PC motherboard, with this chip.

	  Note that the half-duplex "GL620USB" is not supported.

config USB_NET_NET1080
	tristate "NetChip 1080 based cables (Laplink, ...)"
	default y
	depends on USB_USBNET
	help
	  Choose this option if you're using a host-to-host cable based
	  on this design:  one NetChip 1080 chip and supporting logic,
	  optionally with LEDs that indicate traffic

config USB_NET_PLUSB
	tristate "Prolific PL-2301/2302 based cables"
	# if the handshake/init/reset problems, from original 'plusb',
	# are ever resolved ... then remove "experimental"
	depends on USB_USBNET && EXPERIMENTAL
	help
	  Choose this option if you're using a host-to-host cable
	  with one of these chips.

config USB_NET_RNDIS_HOST
	tristate "Host for RNDIS devices (EXPERIMENTAL)"
	depends on USB_USBNET && EXPERIMENTAL
	select USB_NET_CDCETHER
	help
	  This option enables hosting "Remote NDIS" USB networking links,
	  as encouraged by Microsoft (instead of CDC Ethernet!) for use in
	  various devices that may only support this protocol.

	  Avoid using this protocol unless you have no better options.
	  The protocol specification is incomplete, and is controlled by
	  (and for) Microsoft; it isn't an "Open" ecosystem or market.

config USB_NET_CDC_SUBSET
	tristate "Simple USB Network Links (CDC Ethernet subset)"
	depends on USB_USBNET
	help
	  This driver module supports USB network devices that can work
	  without any device-specific information.  Select it if you have
	  one of these drivers.

	  Note that while many USB host-to-host cables can work in this mode,
	  that may mean not being able to talk to Win32 systems or more
	  commonly not being able to handle certain events (like replugging
	  the host on the other end) very well.  Also, these devices will
	  not generally have permanently assigned Ethernet addresses.

config USB_ALI_M5632
	boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
	depends on USB_NET_CDC_SUBSET
	help
	  Choose this option if you're using a host-to-host cable
	  based on this design, which supports USB 2.0 high speed.

config USB_AN2720
	boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
	depends on USB_NET_CDC_SUBSET
	help
	  Choose this option if you're using a host-to-host cable
	  based on this design.  Note that AnchorChips is now a
	  Cypress brand.

config USB_BELKIN
	boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
	depends on USB_NET_CDC_SUBSET
	default y
	help
	  Choose this option if you're using a host-to-host cable
	  based on this design:  two NetChip 2890 chips and an Atmel
	  microcontroller, with LEDs that indicate traffic.

config USB_ARMLINUX
	boolean "Embedded ARM Linux links (iPaq, ...)"
	depends on USB_NET_CDC_SUBSET
	default y
	help
	  Choose this option to support the "usb-eth" networking driver
	  used by most of the ARM Linux community with device controllers
	  such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
	  in some PXA versions of the "blob" boot loader.

	  Linux-based "Gumstix" PXA-25x based systems use this protocol
	  to talk with other Linux systems.

	  Although the ROMs shipped with Sharp Zaurus products use a
	  different link level framing protocol, you can have them use
	  this simpler protocol by installing a different kernel.

config USB_EPSON2888
	boolean "Epson 2888 based firmware (DEVELOPMENT)"
	depends on USB_NET_CDC_SUBSET
	help
	  Choose this option to support the usb networking links used
	  by some sample firmware from Epson.

config USB_NET_ZAURUS
	tristate "Sharp Zaurus (stock ROMs) and compatible"
	depends on USB_USBNET
	select USB_NET_CDCETHER
	select CRC32
	default y
	help
	  Choose this option to support the usb networking links used by
	  Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
	  This also supports some related device firmware, as used in some
	  PDAs from Olympus and some cell phones from Motorola.

	  If you install an alternate image, such as the Linux 2.6 based
	  versions of OpenZaurus, you should no longer need to support this
	  protocol.  Only the "eth-fd" or "net_fd" drivers in these devices
	  really need this non-conformant variant of CDC Ethernet (or in
	  some cases CDC MDLM) protocol, not "g_ether".


endmenu
Commit	Line	Data
1da177e4 LT	1	#
	2	# USB Network devices configuration
	3	#
	4	comment "Networking support is needed for USB Network Adapter support"
	5	depends on USB && !NET
	6
	7	menu "USB Network Adapters"
	8	depends on USB && NET
	9
	10	config USB_CATC
	11	tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
	12	depends on EXPERIMENTAL
	13	select CRC32
	14	---help---
	15	Say Y if you want to use one of the following 10Mbps USB Ethernet
	16	device based on the EL1210A chip. Supported devices are:
	17	Belkin F5U011
	18	Belkin F5U111
	19	CATC NetMate
	20	CATC NetMate II
	21	smartBridges smartNIC
	22
	23	This driver makes the adapter appear as a normal Ethernet interface,
	24	typically on eth0, if it is the only ethernet device, or perhaps on
	25	eth1, if you have a PCI or ISA ethernet card installed.
	26
	27	To compile this driver as a module, choose M here: the
	28	module will be called catc.
	29
	30	config USB_KAWETH
	31	tristate "USB KLSI KL5USB101-based ethernet device support"
	32	---help---
	33	Say Y here if you want to use one of the following 10Mbps only
	34	USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
	35	3Com 3C19250
	36	ADS USB-10BT
	37	ATEN USB Ethernet
	38	ASANTE USB To Ethernet Adapter
	39	AOX Endpoints USB Ethernet
	40	Correga K.K.
	41	D-Link DSB-650C and DU-E10
	42	Entrega / Portgear E45
	43	I-O DATA USB-ET/T
	44	Jaton USB Ethernet Device Adapter
	45	Kingston Technology USB Ethernet Adapter
	46	Linksys USB10T
	47	Mobility USB-Ethernet Adapter
	48	NetGear EA-101
	49	Peracom Enet and Enet2
	50	Portsmith Express Ethernet Adapter
	51	Shark Pocket Adapter
	52	SMC 2202USB
	53	Sony Vaio port extender
	54
	55	This driver is likely to work with most 10Mbps only USB Ethernet
	56	adapters, including some "no brand" devices. It does NOT work on
	57	SmartBridges smartNIC or on Belkin F5U111 devices - you should use
	58	the CATC NetMate driver for those. If you are not sure which one
	59	you need, select both, and the correct one should be selected for
	60	you.
	61
	62	This driver makes the adapter appear as a normal Ethernet interface,
	63	typically on eth0, if it is the only ethernet device, or perhaps on
	64	eth1, if you have a PCI or ISA ethernet card installed.
65
66	To compile this driver as a module, choose M here: the
67	module will be called kaweth.
68
69	config USB_PEGASUS
70	tristate "USB Pegasus/Pegasus-II based ethernet device support"
71	select MII
72	---help---
73	Say Y here if you know you have Pegasus or Pegasus-II based adapter.
74	If in doubt then look at <file:drivers/usb/net/pegasus.h> for the
75	complete list of supported devices.
76
77	If your particular adapter is not in the list and you are _sure_ it
78	is Pegasus or Pegasus II based then send me
79	<petkan@users.sourceforge.net> vendor and device IDs.
80
81	To compile this driver as a module, choose M here: the
82	module will be called pegasus.
83
84	config USB_RTL8150
85	tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
86	depends on EXPERIMENTAL
87	help
88	Say Y here if you have RTL8150 based usb-ethernet adapter.
89	Send me <petkan@users.sourceforge.net> any comments you may have.
90	You can also check for updates at <http://pegasus2.sourceforge.net/>.
91
92	To compile this driver as a module, choose M here: the
93	module will be called rtl8150.
94
95	config USB_USBNET
96	tristate "Multi-purpose USB Networking Framework"
97	---help---
98	This driver supports several kinds of network links over USB,
99	with "minidrivers" built around a common network driver core
100	that supports deep queues for efficient transfers. (This gives
101	better performance with small packets and at high speeds).
090ffa9d	102
1da177e4 LT	103	The USB host runs "usbnet", and the other end of the link might be:
	104
	105	- Another USB host, when using USB "network" or "data transfer"
	106	cables. These are often used to network laptops to PCs, like
	107	"Laplink" parallel cables or some motherboards. These rely
	108	on specialized chips from many suppliers.
	109
	110	- An intelligent USB gadget, perhaps embedding a Linux system.
	111	These include PDAs running Linux (iPaq, Yopy, Zaurus, and
	112	others), and devices that interoperate using the standard
	113	CDC-Ethernet specification (including many cable modems).
	114
	115	- Network adapter hardware (like those for 10/100 Ethernet) which
	116	uses this driver framework.
	117
	118	The link will appear with a name like "usb0", when the link is
	119	a two-node link, or "eth0" for most CDC-Ethernet devices. Those
	120	two-node links are most easily managed with Ethernet Bridging
	121	(CONFIG_BRIDGE) instead of routing.
	122
	123	For more information see <http://www.linux-usb.org/usbnet/>.
	124
	125	To compile this driver as a module, choose M here: the
	126	module will be called usbnet.
	127
2e55cc72 DB	128	config USB_NET_AX8817X
2e55cc72 DB	129	tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
1da177e4 LT	130	depends on USB_USBNET && NET_ETHERNET
	131	select CRC32
	132	select MII
	133	default y
	134	help
	135	This option adds support for ASIX AX88xxx based USB 2.0
2e55cc72	136	10/100 Ethernet adapters.
1da177e4 LT	137
	138	This driver should work with at least the following devices:
	139	* Aten UC210T
	140	* ASIX AX88172
2e55cc72	141	* Billionton Systems, USB2AR
1da177e4 LT	142	* Buffalo LUA-U2-KTX
	143	* Corega FEther USB2-TX
	144	* D-Link DUB-E100
	145	* Hawking UF200
	146	* Linksys USB200M
	147	* Netgear FA120
	148	* Sitecom LN-029
	149	* Intellinet USB 2.0 Ethernet
	150	* ST Lab USB 2.0 Ethernet
	151	* TrendNet TU2-ET100
	152
	153	This driver creates an interface named "ethX", where X depends on
2e55cc72	154	what other networking devices you have in use.
1da177e4	155
38bde1d4	156
4324fd49 DB	157	config USB_NET_CDCETHER
	158	tristate "CDC Ethernet support (smart devices such as cable modems)"
	159	depends on USB_USBNET
	160	default y
	161	help
	162	This option supports devices conforming to the Communication Device
	163	Class (CDC) Ethernet Control Model, a specification that's easy to
	164	implement in device firmware. The CDC specifications are available
	165	from <http://www.usb.org/>.
	166
	167	CDC Ethernet is an implementation option for DOCSIS cable modems
	168	that support USB connectivity, used for non-Microsoft USB hosts.
	169	The Linux-USB CDC Ethernet Gadget driver is an open implementation.
	170	This driver should work with at least the following devices:
	171
	172	* Ericsson PipeRider (all variants)
	173	* Motorola (DM100 and SB4100)
	174	* Broadcom Cable Modem (reference design)
	175	* Toshiba PCX1100U
	176	* ...
	177
	178	This driver creates an interface named "ethX", where X depends on
	179	what other networking devices you have in use. However, if the
	180	IEEE 802 "local assignment" bit is set in the address, a "usbX"
	181	name is used instead.
	182
47ee3051 DB	183	config USB_NET_GL620A
	184	tristate "GeneSys GL620USB-A based cables"
	185	depends on USB_USBNET
	186	help
	187	Choose this option if you're using a host-to-host cable,
	188	or PC2PC motherboard, with this chip.
	189
	190	Note that the half-duplex "GL620USB" is not supported.
	191
904813cd DB	192	config USB_NET_NET1080
	193	tristate "NetChip 1080 based cables (Laplink, ...)"
	194	default y
	195	depends on USB_USBNET
	196	help
	197	Choose this option if you're using a host-to-host cable based
	198	on this design: one NetChip 1080 chip and supporting logic,
	199	optionally with LEDs that indicate traffic
	200
090ffa9d DB	201	config USB_NET_PLUSB
	202	tristate "Prolific PL-2301/2302 based cables"
	203	# if the handshake/init/reset problems, from original 'plusb',
	204	# are ever resolved ... then remove "experimental"
	205	depends on USB_USBNET && EXPERIMENTAL
	206	help
	207	Choose this option if you're using a host-to-host cable
	208	with one of these chips.
	209
64e04910 DB	210	config USB_NET_RNDIS_HOST
	211	tristate "Host for RNDIS devices (EXPERIMENTAL)"
	212	depends on USB_USBNET && EXPERIMENTAL
	213	select USB_NET_CDCETHER
	214	help
	215	This option enables hosting "Remote NDIS" USB networking links,
	216	as encouraged by Microsoft (instead of CDC Ethernet!) for use in
	217	various devices that may only support this protocol.
	218
	219	Avoid using this protocol unless you have no better options.
	220	The protocol specification is incomplete, and is controlled by
	221	(and for) Microsoft; it isn't an "Open" ecosystem or market.
	222
38bde1d4 DB	223	config USB_NET_CDC_SUBSET
	224	tristate "Simple USB Network Links (CDC Ethernet subset)"
	225	depends on USB_USBNET
	226	help
	227	This driver module supports USB network devices that can work
	228	without any device-specific information. Select it if you have
	229	one of these drivers.
	230
	231	Note that while many USB host-to-host cables can work in this mode,
	232	that may mean not being able to talk to Win32 systems or more
	233	commonly not being able to handle certain events (like replugging
	234	the host on the other end) very well. Also, these devices will
	235	not generally have permanently assigned Ethernet addresses.
	236
	237	config USB_ALI_M5632
	238	boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
	239	depends on USB_NET_CDC_SUBSET
	240	help
	241	Choose this option if you're using a host-to-host cable
	242	based on this design, which supports USB 2.0 high speed.
	243
	244	config USB_AN2720
	245	boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
	246	depends on USB_NET_CDC_SUBSET
	247	help
	248	Choose this option if you're using a host-to-host cable
	249	based on this design. Note that AnchorChips is now a
	250	Cypress brand.
	251
	252	config USB_BELKIN
	253	boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
	254	depends on USB_NET_CDC_SUBSET
	255	default y
	256	help
	257	Choose this option if you're using a host-to-host cable
	258	based on this design: two NetChip 2890 chips and an Atmel
	259	microcontroller, with LEDs that indicate traffic.
	260
	261	config USB_ARMLINUX
	262	boolean "Embedded ARM Linux links (iPaq, ...)"
	263	depends on USB_NET_CDC_SUBSET
	264	default y
	265	help
	266	Choose this option to support the "usb-eth" networking driver
	267	used by most of the ARM Linux community with device controllers
	268	such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
	269	in some PXA versions of the "blob" boot loader.
	270
	271	Linux-based "Gumstix" PXA-25x based systems use this protocol
	272	to talk with other Linux systems.
	273
	274	Although the ROMs shipped with Sharp Zaurus products use a
	275	different link level framing protocol, you can have them use
	276	this simpler protocol by installing a different kernel.
	277
	278	config USB_EPSON2888
	279	boolean "Epson 2888 based firmware (DEVELOPMENT)"
	280	depends on USB_NET_CDC_SUBSET
	281	help
	282	Choose this option to support the usb networking links used
	283	by some sample firmware from Epson.
	284
0aa599c5 DB	285	config USB_NET_ZAURUS
	286	tristate "Sharp Zaurus (stock ROMs) and compatible"
	287	depends on USB_USBNET
4324fd49	288	select USB_NET_CDCETHER
0aa599c5 DB	289	select CRC32
	290	default y
	291	help
	292	Choose this option to support the usb networking links used by
	293	Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
	294	This also supports some related device firmware, as used in some
	295	PDAs from Olympus and some cell phones from Motorola.
	296
46a0cf81	297	If you install an alternate image, such as the Linux 2.6 based
0aa599c5 DB	298	versions of OpenZaurus, you should no longer need to support this
	299	protocol. Only the "eth-fd" or "net_fd" drivers in these devices
	300	really need this non-conformant variant of CDC Ethernet (or in
	301	some cases CDC MDLM) protocol, not "g_ether".
	302
38bde1d4	303
1da177e4	304	endmenu