[GitHub/mt8127/android_kernel_alcatel_ttab.git] / drivers / net / usb / 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/net/usb/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
	select MII
	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"
	select MII
	---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
	select CRC32
	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:

	    * Dell Wireless 5530 HSPA
 	    * Ericsson PipeRider (all variants)
	    * Ericsson Mobile Broadband Module (all variants)
 	    * Motorola (DM100 and SB4100)
 	    * Broadcom Cable Modem (reference design)
	    * Toshiba (PCX1100U and F3507g)
	    * ...

	  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_CDC_EEM
	tristate "CDC EEM support"
	depends on USB_USBNET && EXPERIMENTAL
	help
	  This option supports devices conforming to the Communication Device
	  Class (CDC) Ethernet Emulation Model, a specification that's easy to
	  implement in device firmware.  The CDC EEM specifications are available
	  from <http://www.usb.org/>.

	  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_DM9601
	tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
	depends on USB_USBNET
	select CRC32
	help
	  This option adds support for Davicom DM9601 based USB 1.1
	  10/100 Ethernet adapters.

config USB_NET_SMSC95XX
	tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
	depends on USB_USBNET
	select CRC32
	help
	  This option adds support for SMSC LAN95XX based USB 2.0
	  10/100 Ethernet adapters.

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_MCS7830
	tristate "MosChip MCS7830 based Ethernet adapters"
	depends on USB_USBNET
	help
	  Choose this option if you're using a 10/100 Ethernet USB2
	  adapter based on the MosChip 7830 controller. This includes
	  adapters marketed under the DeLOCK brand.

config USB_NET_RNDIS_HOST
	tristate "Host for RNDIS and ActiveSync 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.  A variant
	  of this protocol (with even less public documentation) seems to
	  be at the root of Microsoft's "ActiveSync" too.

	  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
	default y
	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_KC2190
	boolean "KT Technology KC2190 based cables (InstaNet)"
	depends on USB_NET_CDC_SUBSET && EXPERIMENTAL
	help
	  Choose this option if you're using a host-to-host cable
	  with one of these chips.

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".

config USB_HSO
	tristate "Option USB High Speed Mobile Devices"
	depends on USB && RFKILL
	default n
	help
	  Choose this option if you have an Option HSDPA/HSUPA card.
	  These cards support downlink speeds of 7.2Mbps or greater.

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

config USB_NET_INT51X1
	tristate "Intellon PLC based usb adapter"
	depends on USB_USBNET
	help
	  Choose this option if you're using a 14Mb USB-based PLC
	  (Powerline Communications) solution with an Intellon
	  INT51x1/INT5200 chip, like the "devolo dLan duo".

config USB_CDC_PHONET
	tristate "CDC Phonet support"
	depends on PHONET
	help
	  Choose this option to support the Phonet interface to a Nokia
	  cellular modem, as found on most Nokia handsets with the
	  "PC suite" USB profile.

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.
582fe6fb	74	If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
1da177e4 LT	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
d0b4e310	87	select MII
1da177e4 LT	88	help
	89	Say Y here if you have RTL8150 based usb-ethernet adapter.
	90	Send me <petkan@users.sourceforge.net> any comments you may have.
	91	You can also check for updates at <http://pegasus2.sourceforge.net/>.
	92
	93	To compile this driver as a module, choose M here: the
	94	module will be called rtl8150.
	95
	96	config USB_USBNET
	97	tristate "Multi-purpose USB Networking Framework"
4aa92cd9	98	select MII
1da177e4 LT	99	---help---
	100	This driver supports several kinds of network links over USB,
	101	with "minidrivers" built around a common network driver core
	102	that supports deep queues for efficient transfers. (This gives
	103	better performance with small packets and at high speeds).
090ffa9d	104
1da177e4 LT	105	The USB host runs "usbnet", and the other end of the link might be:
	106
	107	- Another USB host, when using USB "network" or "data transfer"
	108	cables. These are often used to network laptops to PCs, like
	109	"Laplink" parallel cables or some motherboards. These rely
	110	on specialized chips from many suppliers.
	111
	112	- An intelligent USB gadget, perhaps embedding a Linux system.
	113	These include PDAs running Linux (iPaq, Yopy, Zaurus, and
	114	others), and devices that interoperate using the standard
	115	CDC-Ethernet specification (including many cable modems).
	116
	117	- Network adapter hardware (like those for 10/100 Ethernet) which
	118	uses this driver framework.
	119
	120	The link will appear with a name like "usb0", when the link is
	121	a two-node link, or "eth0" for most CDC-Ethernet devices. Those
	122	two-node links are most easily managed with Ethernet Bridging
	123	(CONFIG_BRIDGE) instead of routing.
	124
	125	For more information see <http://www.linux-usb.org/usbnet/>.
	126
	127	To compile this driver as a module, choose M here: the
	128	module will be called usbnet.
	129
2e55cc72 DB	130	config USB_NET_AX8817X
2e55cc72 DB	131	tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
c6cbcad1	132	depends on USB_USBNET
1da177e4	133	select CRC32
1da177e4 LT	134	default y
	135	help
	136	This option adds support for ASIX AX88xxx based USB 2.0
2e55cc72	137	10/100 Ethernet adapters.
1da177e4 LT	138
	139	This driver should work with at least the following devices:
	140	* Aten UC210T
	141	* ASIX AX88172
2e55cc72	142	* Billionton Systems, USB2AR
1da177e4 LT	143	* Buffalo LUA-U2-KTX
	144	* Corega FEther USB2-TX
	145	* D-Link DUB-E100
	146	* Hawking UF200
	147	* Linksys USB200M
	148	* Netgear FA120
	149	* Sitecom LN-029
	150	* Intellinet USB 2.0 Ethernet
	151	* ST Lab USB 2.0 Ethernet
	152	* TrendNet TU2-ET100
	153
	154	This driver creates an interface named "ethX", where X depends on
2e55cc72	155	what other networking devices you have in use.
1da177e4	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
68924920	172	* Dell Wireless 5530 HSPA
4324fd49	173	* Ericsson PipeRider (all variants)
68924920	174	* Ericsson Mobile Broadband Module (all variants)
4324fd49 DB	175	* Motorola (DM100 and SB4100)
4324fd49 DB	176	* Broadcom Cable Modem (reference design)
68924920	177	* Toshiba (PCX1100U and F3507g)
4324fd49 DB	178	* ...
	179
	180	This driver creates an interface named "ethX", where X depends on
	181	what other networking devices you have in use. However, if the
	182	IEEE 802 "local assignment" bit is set in the address, a "usbX"
	183	name is used instead.
	184
9f722c09 OL	185	config USB_NET_CDC_EEM
	186	tristate "CDC EEM support"
	187	depends on USB_USBNET && EXPERIMENTAL
	188	help
	189	This option supports devices conforming to the Communication Device
	190	Class (CDC) Ethernet Emulation Model, a specification that's easy to
	191	implement in device firmware. The CDC EEM specifications are available
	192	from <http://www.usb.org/>.
	193
	194	This driver creates an interface named "ethX", where X depends on
	195	what other networking devices you have in use. However, if the
	196	IEEE 802 "local assignment" bit is set in the address, a "usbX"
4324fd49 DB	197	name is used instead.
4324fd49 DB	198
d0374f4f PK	199	config USB_NET_DM9601
	200	tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
	201	depends on USB_USBNET
	202	select CRC32
d0374f4f PK	203	help
	204	This option adds support for Davicom DM9601 based USB 1.1
	205	10/100 Ethernet adapters.
	206
2f7ca802 SG	207	config USB_NET_SMSC95XX
	208	tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
	209	depends on USB_USBNET
	210	select CRC32
	211	help
	212	This option adds support for SMSC LAN95XX based USB 2.0
	213	10/100 Ethernet adapters.
	214
47ee3051 DB	215	config USB_NET_GL620A
	216	tristate "GeneSys GL620USB-A based cables"
	217	depends on USB_USBNET
	218	help
	219	Choose this option if you're using a host-to-host cable,
	220	or PC2PC motherboard, with this chip.
	221
	222	Note that the half-duplex "GL620USB" is not supported.
	223
904813cd DB	224	config USB_NET_NET1080
	225	tristate "NetChip 1080 based cables (Laplink, ...)"
	226	default y
	227	depends on USB_USBNET
	228	help
	229	Choose this option if you're using a host-to-host cable based
	230	on this design: one NetChip 1080 chip and supporting logic,
	231	optionally with LEDs that indicate traffic
	232
090ffa9d DB	233	config USB_NET_PLUSB
	234	tristate "Prolific PL-2301/2302 based cables"
	235	# if the handshake/init/reset problems, from original 'plusb',
	236	# are ever resolved ... then remove "experimental"
	237	depends on USB_USBNET && EXPERIMENTAL
	238	help
	239	Choose this option if you're using a host-to-host cable
	240	with one of these chips.
	241
2a36d708 AB	242	config USB_NET_MCS7830
	243	tristate "MosChip MCS7830 based Ethernet adapters"
	244	depends on USB_USBNET
	245	help
	246	Choose this option if you're using a 10/100 Ethernet USB2
	247	adapter based on the MosChip 7830 controller. This includes
	248	adapters marketed under the DeLOCK brand.
	249
64e04910	250	config USB_NET_RNDIS_HOST
ad55d71a	251	tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)"
64e04910 DB	252	depends on USB_USBNET && EXPERIMENTAL
	253	select USB_NET_CDCETHER
	254	help
	255	This option enables hosting "Remote NDIS" USB networking links,
	256	as encouraged by Microsoft (instead of CDC Ethernet!) for use in
ad55d71a OAVR	257	various devices that may only support this protocol. A variant
	258	of this protocol (with even less public documentation) seems to
	259	be at the root of Microsoft's "ActiveSync" too.
64e04910 DB	260
	261	Avoid using this protocol unless you have no better options.
	262	The protocol specification is incomplete, and is controlled by
	263	(and for) Microsoft; it isn't an "Open" ecosystem or market.
	264
38bde1d4 DB	265	config USB_NET_CDC_SUBSET
	266	tristate "Simple USB Network Links (CDC Ethernet subset)"
	267	depends on USB_USBNET
691895c6	268	default y
38bde1d4 DB	269	help
	270	This driver module supports USB network devices that can work
	271	without any device-specific information. Select it if you have
	272	one of these drivers.
	273
	274	Note that while many USB host-to-host cables can work in this mode,
	275	that may mean not being able to talk to Win32 systems or more
	276	commonly not being able to handle certain events (like replugging
	277	the host on the other end) very well. Also, these devices will
	278	not generally have permanently assigned Ethernet addresses.
	279
	280	config USB_ALI_M5632
	281	boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
	282	depends on USB_NET_CDC_SUBSET
	283	help
	284	Choose this option if you're using a host-to-host cable
	285	based on this design, which supports USB 2.0 high speed.
	286
	287	config USB_AN2720
	288	boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
	289	depends on USB_NET_CDC_SUBSET
	290	help
	291	Choose this option if you're using a host-to-host cable
	292	based on this design. Note that AnchorChips is now a
	293	Cypress brand.
	294
	295	config USB_BELKIN
	296	boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
	297	depends on USB_NET_CDC_SUBSET
	298	default y
	299	help
	300	Choose this option if you're using a host-to-host cable
	301	based on this design: two NetChip 2890 chips and an Atmel
	302	microcontroller, with LEDs that indicate traffic.
	303
	304	config USB_ARMLINUX
	305	boolean "Embedded ARM Linux links (iPaq, ...)"
	306	depends on USB_NET_CDC_SUBSET
	307	default y
	308	help
	309	Choose this option to support the "usb-eth" networking driver
	310	used by most of the ARM Linux community with device controllers
	311	such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
	312	in some PXA versions of the "blob" boot loader.
	313
	314	Linux-based "Gumstix" PXA-25x based systems use this protocol
	315	to talk with other Linux systems.
	316
	317	Although the ROMs shipped with Sharp Zaurus products use a
	318	different link level framing protocol, you can have them use
	319	this simpler protocol by installing a different kernel.
	320
	321	config USB_EPSON2888
	322	boolean "Epson 2888 based firmware (DEVELOPMENT)"
	323	depends on USB_NET_CDC_SUBSET
	324	help
	325	Choose this option to support the usb networking links used
	326	by some sample firmware from Epson.
	327
691895c6 DB	328	config USB_KC2190
	329	boolean "KT Technology KC2190 based cables (InstaNet)"
	330	depends on USB_NET_CDC_SUBSET && EXPERIMENTAL
	331	help
c0811987 SR	332	Choose this option if you're using a host-to-host cable
c0811987 SR	333	with one of these chips.
691895c6	334
0aa599c5 DB	335	config USB_NET_ZAURUS
	336	tristate "Sharp Zaurus (stock ROMs) and compatible"
	337	depends on USB_USBNET
4324fd49	338	select USB_NET_CDCETHER
0aa599c5 DB	339	select CRC32
	340	default y
	341	help
	342	Choose this option to support the usb networking links used by
	343	Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
	344	This also supports some related device firmware, as used in some
	345	PDAs from Olympus and some cell phones from Motorola.
	346
46a0cf81	347	If you install an alternate image, such as the Linux 2.6 based
0aa599c5 DB	348	versions of OpenZaurus, you should no longer need to support this
	349	protocol. Only the "eth-fd" or "net_fd" drivers in these devices
	350	really need this non-conformant variant of CDC Ethernet (or in
	351	some cases CDC MDLM) protocol, not "g_ether".
	352
85a73b33 DB	353	config USB_HSO
	354	tristate "Option USB High Speed Mobile Devices"
	355	depends on USB && RFKILL
	356	default n
	357	help
	358	Choose this option if you have an Option HSDPA/HSUPA card.
	359	These cards support downlink speeds of 7.2Mbps or greater.
	360
	361	To compile this driver as a module, choose M here: the
	362	module will be called hso.
38bde1d4	363
4510d7cb PH	364	config USB_NET_INT51X1
	365	tristate "Intellon PLC based usb adapter"
	366	depends on USB_USBNET
	367	help
	368	Choose this option if you're using a 14Mb USB-based PLC
	369	(Powerline Communications) solution with an Intellon
	370	INT51x1/INT5200 chip, like the "devolo dLan duo".
	371
87cf6560 RDC	372	config USB_CDC_PHONET
	373	tristate "CDC Phonet support"
	374	depends on PHONET
	375	help
	376	Choose this option to support the Phonet interface to a Nokia
	377	cellular modem, as found on most Nokia handsets with the
	378	"PC suite" USB profile.
	379
1da177e4	380	endmenu