2 # USB Network devices configuration
4 comment "Networking support is needed for USB Network Adapter support"
7 menu "USB Network Adapters"
11 tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
12 depends on EXPERIMENTAL
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:
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.
27 To compile this driver as a module, choose M here: the
28 module will be called catc.
31 tristate "USB KLSI KL5USB101-based ethernet device support"
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:
38 ASANTE USB To Ethernet Adapter
39 AOX Endpoints USB Ethernet
41 D-Link DSB-650C and DU-E10
42 Entrega / Portgear E45
44 Jaton USB Ethernet Device Adapter
45 Kingston Technology USB Ethernet Adapter
47 Mobility USB-Ethernet Adapter
49 Peracom Enet and Enet2
50 Portsmith Express Ethernet Adapter
53 Sony Vaio port extender
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
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.
66 To compile this driver as a module, choose M here: the
67 module will be called kaweth.
70 tristate "USB Pegasus/Pegasus-II based ethernet device support"
73 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
74 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
75 complete list of supported devices.
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.
81 To compile this driver as a module, choose M here: the
82 module will be called pegasus.
85 tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
86 depends on EXPERIMENTAL
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/>.
93 To compile this driver as a module, choose M here: the
94 module will be called rtl8150.
97 tristate "Multi-purpose USB Networking Framework"
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).
105 The USB host runs "usbnet", and the other end of the link might be:
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.
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).
117 - Network adapter hardware (like those for 10/100 Ethernet) which
118 uses this driver framework.
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.
125 For more information see <http://www.linux-usb.org/usbnet/>.
127 To compile this driver as a module, choose M here: the
128 module will be called usbnet.
130 config USB_NET_AX8817X
131 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
132 depends on USB_USBNET
136 This option adds support for ASIX AX88xxx based USB 2.0
137 10/100 Ethernet adapters.
139 This driver should work with at least the following devices:
142 * Billionton Systems, USB2AR
144 * Corega FEther USB2-TX
150 * Intellinet USB 2.0 Ethernet
151 * ST Lab USB 2.0 Ethernet
154 This driver creates an interface named "ethX", where X depends on
155 what other networking devices you have in use.
157 config USB_NET_CDCETHER
158 tristate "CDC Ethernet support (smart devices such as cable modems)"
159 depends on USB_USBNET
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/>.
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:
172 * Dell Wireless 5530 HSPA
173 * Ericsson PipeRider (all variants)
174 * Ericsson Mobile Broadband Module (all variants)
175 * Motorola (DM100 and SB4100)
176 * Broadcom Cable Modem (reference design)
177 * Toshiba (PCX1100U and F3507g/F3607gw)
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.
185 config USB_NET_HW_CDCDRIVER
186 tristate "HW CDC Driver (Huawei driver for E3372 non-Hilink)"
187 depends on USB_USBNET
190 This driver creates an interface named "ethX", where X depends on
191 what other networking devices you have in use. However, if the
192 IEEE 802 "local assignment" bit is set in the address, a "usbX"
193 name is used instead.
195 config USB_NET_CDC_EEM
196 tristate "CDC EEM support"
197 depends on USB_USBNET && EXPERIMENTAL
199 This option supports devices conforming to the Communication Device
200 Class (CDC) Ethernet Emulation Model, a specification that's easy to
201 implement in device firmware. The CDC EEM specifications are available
202 from <http://www.usb.org/>.
204 This driver creates an interface named "ethX", where X depends on
205 what other networking devices you have in use. However, if the
206 IEEE 802 "local assignment" bit is set in the address, a "usbX"
207 name is used instead.
209 config USB_NET_CDC_NCM
210 tristate "CDC NCM support"
211 depends on USB_USBNET
213 This driver provides support for CDC NCM (Network Control Model
214 Device USB Class Specification). The CDC NCM specification is
215 available from <http://www.usb.org/>.
217 Say "y" to link the driver statically, or "m" to build a
218 dynamically linked module.
220 This driver should work with at least the following devices:
221 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
222 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
223 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
224 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
225 * Ericsson F5521gw Mobile Broadband Module
227 config USB_NET_CDC_MBIM
228 tristate "CDC MBIM support"
229 depends on USB_USBNET
231 select USB_NET_CDC_NCM
233 This driver provides support for CDC MBIM (Mobile Broadband
234 Interface Model) devices. The CDC MBIM specification is
235 available from <http://www.usb.org/>.
237 MBIM devices require configuration using the management
238 protocol defined by the MBIM specification. This driver
239 provides unfiltered access to the MBIM control channel
240 through the associated /dev/cdc-wdmx character device.
242 To compile this driver as a module, choose M here: the
243 module will be called cdc_mbim.
245 config USB_NET_DM9601
246 tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
247 depends on USB_USBNET
250 This option adds support for Davicom DM9601 based USB 1.1
251 10/100 Ethernet adapters.
253 config USB_NET_SMSC75XX
254 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
255 depends on USB_USBNET
258 This option adds support for SMSC LAN95XX based USB 2.0
259 Gigabit Ethernet adapters.
261 config USB_NET_SMSC95XX
262 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
263 depends on USB_USBNET
266 This option adds support for SMSC LAN95XX based USB 2.0
267 10/100 Ethernet adapters.
269 config USB_NET_GL620A
270 tristate "GeneSys GL620USB-A based cables"
271 depends on USB_USBNET
273 Choose this option if you're using a host-to-host cable,
274 or PC2PC motherboard, with this chip.
276 Note that the half-duplex "GL620USB" is not supported.
278 config USB_NET_NET1080
279 tristate "NetChip 1080 based cables (Laplink, ...)"
281 depends on USB_USBNET
283 Choose this option if you're using a host-to-host cable based
284 on this design: one NetChip 1080 chip and supporting logic,
285 optionally with LEDs that indicate traffic
288 tristate "Prolific PL-2301/2302 based cables"
289 # if the handshake/init/reset problems, from original 'plusb',
290 # are ever resolved ... then remove "experimental"
291 depends on USB_USBNET && EXPERIMENTAL
293 Choose this option if you're using a host-to-host cable
294 with one of these chips.
296 config USB_NET_MCS7830
297 tristate "MosChip MCS7830 based Ethernet adapters"
298 depends on USB_USBNET
300 Choose this option if you're using a 10/100 Ethernet USB2
301 adapter based on the MosChip 7830 controller. This includes
302 adapters marketed under the DeLOCK brand.
304 config USB_NET_RNDIS_HOST
305 tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)"
306 depends on USB_USBNET && EXPERIMENTAL
307 select USB_NET_CDCETHER
309 This option enables hosting "Remote NDIS" USB networking links,
310 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
311 various devices that may only support this protocol. A variant
312 of this protocol (with even less public documentation) seems to
313 be at the root of Microsoft's "ActiveSync" too.
315 Avoid using this protocol unless you have no better options.
316 The protocol specification is incomplete, and is controlled by
317 (and for) Microsoft; it isn't an "Open" ecosystem or market.
319 config USB_NET_CDC_SUBSET
320 tristate "Simple USB Network Links (CDC Ethernet subset)"
321 depends on USB_USBNET
324 This driver module supports USB network devices that can work
325 without any device-specific information. Select it if you have
326 one of these drivers.
328 Note that while many USB host-to-host cables can work in this mode,
329 that may mean not being able to talk to Win32 systems or more
330 commonly not being able to handle certain events (like replugging
331 the host on the other end) very well. Also, these devices will
332 not generally have permanently assigned Ethernet addresses.
335 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
336 depends on USB_NET_CDC_SUBSET
338 Choose this option if you're using a host-to-host cable
339 based on this design, which supports USB 2.0 high speed.
342 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
343 depends on USB_NET_CDC_SUBSET
345 Choose this option if you're using a host-to-host cable
346 based on this design. Note that AnchorChips is now a
350 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
351 depends on USB_NET_CDC_SUBSET
354 Choose this option if you're using a host-to-host cable
355 based on this design: two NetChip 2890 chips and an Atmel
356 microcontroller, with LEDs that indicate traffic.
359 boolean "Embedded ARM Linux links (iPaq, ...)"
360 depends on USB_NET_CDC_SUBSET
363 Choose this option to support the "usb-eth" networking driver
364 used by most of the ARM Linux community with device controllers
365 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
366 in some PXA versions of the "blob" boot loader.
368 Linux-based "Gumstix" PXA-25x based systems use this protocol
369 to talk with other Linux systems.
371 Although the ROMs shipped with Sharp Zaurus products use a
372 different link level framing protocol, you can have them use
373 this simpler protocol by installing a different kernel.
376 boolean "Epson 2888 based firmware (DEVELOPMENT)"
377 depends on USB_NET_CDC_SUBSET
379 Choose this option to support the usb networking links used
380 by some sample firmware from Epson.
383 boolean "KT Technology KC2190 based cables (InstaNet)"
384 depends on USB_NET_CDC_SUBSET && EXPERIMENTAL
386 Choose this option if you're using a host-to-host cable
387 with one of these chips.
389 config USB_NET_ZAURUS
390 tristate "Sharp Zaurus (stock ROMs) and compatible"
391 depends on USB_USBNET
392 select USB_NET_CDCETHER
396 Choose this option to support the usb networking links used by
397 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
398 This also supports some related device firmware, as used in some
399 PDAs from Olympus and some cell phones from Motorola.
401 If you install an alternate image, such as the Linux 2.6 based
402 versions of OpenZaurus, you should no longer need to support this
403 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
404 really need this non-conformant variant of CDC Ethernet (or in
405 some cases CDC MDLM) protocol, not "g_ether".
408 tristate "Option USB High Speed Mobile Devices"
409 depends on USB && RFKILL
412 Choose this option if you have an Option HSDPA/HSUPA card.
413 These cards support downlink speeds of 7.2Mbps or greater.
415 To compile this driver as a module, choose M here: the
416 module will be called hso.
418 config USB_NET_INT51X1
419 tristate "Intellon PLC based usb adapter"
420 depends on USB_USBNET
422 Choose this option if you're using a 14Mb USB-based PLC
423 (Powerline Communications) solution with an Intellon
424 INT51x1/INT5200 chip, like the "devolo dLan duo".
426 config USB_CDC_PHONET
427 tristate "CDC Phonet support"
430 Choose this option to support the Phonet interface to a Nokia
431 cellular modem, as found on most Nokia handsets with the
432 "PC suite" USB profile.
434 config USB_NET_QMI_WWAN
435 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
436 depends on USB_USBNET
439 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
440 (MDM) chipsets. Examples of such devices are
443 This driver will only drive the ethernet part of the chips.
444 The devices require additional configuration to be usable.
445 Multiple management interfaces with linux drivers are
448 * option: AT commands on /dev/ttyUSBx
449 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
451 A modem manager with support for QMI is recommended.
453 To compile this driver as a module, choose M here: the
454 module will be called qmi_wwan.
457 tristate "Apple iPhone USB Ethernet driver"
460 Module used to share Internet connection (tethering) from your
461 iPhone (Original, 3G and 3GS) to your system.
462 Note that you need userspace libraries and programs that are needed
463 to pair your device with your system and that understand the iPhone
466 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
468 config USB_SIERRA_NET
469 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
470 depends on USB_USBNET
472 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
474 To compile this driver as a module, choose M here: the
475 module will be called sierra_net.