[mirror_ubuntu-zesty-kernel.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
	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_MII
	tristate
	default n

config USB_USBNET
	tristate "Multi-purpose USB Networking Framework"
	select MII if USB_USBNET_MII != n
	---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 USB_USBNET_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_MCS7830
	tristate "MosChip MCS7830 based Ethernet adapters"
	depends on USB_USBNET
	select USB_USBNET_MII
	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
	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
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
18ee91fa DB	96	config USB_USBNET_MII
	97	tristate
	98	default n
	99
1da177e4 LT	100	config USB_USBNET
1da177e4 LT	101	tristate "Multi-purpose USB Networking Framework"
0207c808	102	select MII if USB_USBNET_MII != n
1da177e4 LT	103	---help---
	104	This driver supports several kinds of network links over USB,
	105	with "minidrivers" built around a common network driver core
	106	that supports deep queues for efficient transfers. (This gives
	107	better performance with small packets and at high speeds).
090ffa9d	108
1da177e4 LT	109	The USB host runs "usbnet", and the other end of the link might be:
	110
	111	- Another USB host, when using USB "network" or "data transfer"
	112	cables. These are often used to network laptops to PCs, like
	113	"Laplink" parallel cables or some motherboards. These rely
	114	on specialized chips from many suppliers.
	115
	116	- An intelligent USB gadget, perhaps embedding a Linux system.
	117	These include PDAs running Linux (iPaq, Yopy, Zaurus, and
	118	others), and devices that interoperate using the standard
	119	CDC-Ethernet specification (including many cable modems).
	120
	121	- Network adapter hardware (like those for 10/100 Ethernet) which
	122	uses this driver framework.
	123
	124	The link will appear with a name like "usb0", when the link is
	125	a two-node link, or "eth0" for most CDC-Ethernet devices. Those
	126	two-node links are most easily managed with Ethernet Bridging
	127	(CONFIG_BRIDGE) instead of routing.
	128
	129	For more information see <http://www.linux-usb.org/usbnet/>.
	130
	131	To compile this driver as a module, choose M here: the
	132	module will be called usbnet.
	133
2e55cc72 DB	134	config USB_NET_AX8817X
2e55cc72 DB	135	tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
1da177e4 LT	136	depends on USB_USBNET && NET_ETHERNET
1da177e4 LT	137	select CRC32
18ee91fa	138	select USB_USBNET_MII
1da177e4 LT	139	default y
	140	help
	141	This option adds support for ASIX AX88xxx based USB 2.0
2e55cc72	142	10/100 Ethernet adapters.
1da177e4 LT	143
	144	This driver should work with at least the following devices:
	145	* Aten UC210T
	146	* ASIX AX88172
2e55cc72	147	* Billionton Systems, USB2AR
1da177e4 LT	148	* Buffalo LUA-U2-KTX
	149	* Corega FEther USB2-TX
	150	* D-Link DUB-E100
	151	* Hawking UF200
	152	* Linksys USB200M
	153	* Netgear FA120
	154	* Sitecom LN-029
	155	* Intellinet USB 2.0 Ethernet
	156	* ST Lab USB 2.0 Ethernet
	157	* TrendNet TU2-ET100
	158
	159	This driver creates an interface named "ethX", where X depends on
2e55cc72	160	what other networking devices you have in use.
1da177e4	161
38bde1d4	162
4324fd49 DB	163	config USB_NET_CDCETHER
	164	tristate "CDC Ethernet support (smart devices such as cable modems)"
	165	depends on USB_USBNET
	166	default y
	167	help
	168	This option supports devices conforming to the Communication Device
	169	Class (CDC) Ethernet Control Model, a specification that's easy to
	170	implement in device firmware. The CDC specifications are available
	171	from <http://www.usb.org/>.
	172
	173	CDC Ethernet is an implementation option for DOCSIS cable modems
	174	that support USB connectivity, used for non-Microsoft USB hosts.
	175	The Linux-USB CDC Ethernet Gadget driver is an open implementation.
	176	This driver should work with at least the following devices:
	177
	178	* Ericsson PipeRider (all variants)
	179	* Motorola (DM100 and SB4100)
	180	* Broadcom Cable Modem (reference design)
	181	* Toshiba PCX1100U
	182	* ...
	183
	184	This driver creates an interface named "ethX", where X depends on
	185	what other networking devices you have in use. However, if the
	186	IEEE 802 "local assignment" bit is set in the address, a "usbX"
	187	name is used instead.
	188
47ee3051 DB	189	config USB_NET_GL620A
	190	tristate "GeneSys GL620USB-A based cables"
	191	depends on USB_USBNET
	192	help
	193	Choose this option if you're using a host-to-host cable,
	194	or PC2PC motherboard, with this chip.
	195
	196	Note that the half-duplex "GL620USB" is not supported.
	197
904813cd DB	198	config USB_NET_NET1080
	199	tristate "NetChip 1080 based cables (Laplink, ...)"
	200	default y
	201	depends on USB_USBNET
	202	help
	203	Choose this option if you're using a host-to-host cable based
	204	on this design: one NetChip 1080 chip and supporting logic,
	205	optionally with LEDs that indicate traffic
	206
090ffa9d DB	207	config USB_NET_PLUSB
	208	tristate "Prolific PL-2301/2302 based cables"
	209	# if the handshake/init/reset problems, from original 'plusb',
	210	# are ever resolved ... then remove "experimental"
	211	depends on USB_USBNET && EXPERIMENTAL
	212	help
	213	Choose this option if you're using a host-to-host cable
	214	with one of these chips.
	215
2a36d708 AB	216	config USB_NET_MCS7830
	217	tristate "MosChip MCS7830 based Ethernet adapters"
	218	depends on USB_USBNET
18ee91fa	219	select USB_USBNET_MII
2a36d708 AB	220	help
	221	Choose this option if you're using a 10/100 Ethernet USB2
	222	adapter based on the MosChip 7830 controller. This includes
	223	adapters marketed under the DeLOCK brand.
	224
64e04910	225	config USB_NET_RNDIS_HOST
ad55d71a	226	tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)"
64e04910 DB	227	depends on USB_USBNET && EXPERIMENTAL
	228	select USB_NET_CDCETHER
	229	help
	230	This option enables hosting "Remote NDIS" USB networking links,
	231	as encouraged by Microsoft (instead of CDC Ethernet!) for use in
ad55d71a OAVR	232	various devices that may only support this protocol. A variant
	233	of this protocol (with even less public documentation) seems to
	234	be at the root of Microsoft's "ActiveSync" too.
64e04910 DB	235
	236	Avoid using this protocol unless you have no better options.
	237	The protocol specification is incomplete, and is controlled by
	238	(and for) Microsoft; it isn't an "Open" ecosystem or market.
	239
38bde1d4 DB	240	config USB_NET_CDC_SUBSET
	241	tristate "Simple USB Network Links (CDC Ethernet subset)"
	242	depends on USB_USBNET
	243	help
	244	This driver module supports USB network devices that can work
	245	without any device-specific information. Select it if you have
	246	one of these drivers.
	247
	248	Note that while many USB host-to-host cables can work in this mode,
	249	that may mean not being able to talk to Win32 systems or more
	250	commonly not being able to handle certain events (like replugging
	251	the host on the other end) very well. Also, these devices will
	252	not generally have permanently assigned Ethernet addresses.
	253
	254	config USB_ALI_M5632
	255	boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
	256	depends on USB_NET_CDC_SUBSET
	257	help
	258	Choose this option if you're using a host-to-host cable
	259	based on this design, which supports USB 2.0 high speed.
	260
	261	config USB_AN2720
	262	boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
	263	depends on USB_NET_CDC_SUBSET
	264	help
	265	Choose this option if you're using a host-to-host cable
	266	based on this design. Note that AnchorChips is now a
	267	Cypress brand.
	268
	269	config USB_BELKIN
	270	boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
	271	depends on USB_NET_CDC_SUBSET
	272	default y
	273	help
	274	Choose this option if you're using a host-to-host cable
	275	based on this design: two NetChip 2890 chips and an Atmel
	276	microcontroller, with LEDs that indicate traffic.
	277
	278	config USB_ARMLINUX
	279	boolean "Embedded ARM Linux links (iPaq, ...)"
	280	depends on USB_NET_CDC_SUBSET
	281	default y
	282	help
	283	Choose this option to support the "usb-eth" networking driver
	284	used by most of the ARM Linux community with device controllers
	285	such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
	286	in some PXA versions of the "blob" boot loader.
	287
	288	Linux-based "Gumstix" PXA-25x based systems use this protocol
	289	to talk with other Linux systems.
	290
	291	Although the ROMs shipped with Sharp Zaurus products use a
	292	different link level framing protocol, you can have them use
	293	this simpler protocol by installing a different kernel.
	294
	295	config USB_EPSON2888
	296	boolean "Epson 2888 based firmware (DEVELOPMENT)"
	297	depends on USB_NET_CDC_SUBSET
	298	help
	299	Choose this option to support the usb networking links used
	300	by some sample firmware from Epson.
	301
0aa599c5 DB	302	config USB_NET_ZAURUS
	303	tristate "Sharp Zaurus (stock ROMs) and compatible"
	304	depends on USB_USBNET
4324fd49	305	select USB_NET_CDCETHER
0aa599c5 DB	306	select CRC32
	307	default y
	308	help
	309	Choose this option to support the usb networking links used by
	310	Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
	311	This also supports some related device firmware, as used in some
	312	PDAs from Olympus and some cell phones from Motorola.
	313
46a0cf81	314	If you install an alternate image, such as the Linux 2.6 based
0aa599c5 DB	315	versions of OpenZaurus, you should no longer need to support this
	316	protocol. Only the "eth-fd" or "net_fd" drivers in these devices
	317	really need this non-conformant variant of CDC Ethernet (or in
	318	some cases CDC MDLM) protocol, not "g_ether".
	319
38bde1d4	320
1da177e4	321	endmenu