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"
14 Say Y if you want to use one of the following 10Mbps USB Ethernet
15 device based on the EL1210A chip. Supported devices are:
22 This driver makes the adapter appear as a normal Ethernet interface,
23 typically on eth0, if it is the only ethernet device, or perhaps on
24 eth1, if you have a PCI or ISA ethernet card installed.
26 To compile this driver as a module, choose M here: the
27 module will be called catc.
30 tristate "USB KLSI KL5USB101-based ethernet device support"
32 Say Y here if you want to use one of the following 10Mbps only
33 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
37 ASANTE USB To Ethernet Adapter
38 AOX Endpoints USB Ethernet
40 D-Link DSB-650C and DU-E10
41 Entrega / Portgear E45
43 Jaton USB Ethernet Device Adapter
44 Kingston Technology USB Ethernet Adapter
46 Mobility USB-Ethernet Adapter
48 Peracom Enet and Enet2
49 Portsmith Express Ethernet Adapter
52 Sony Vaio port extender
54 This driver is likely to work with most 10Mbps only USB Ethernet
55 adapters, including some "no brand" devices. It does NOT work on
56 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
57 the CATC NetMate driver for those. If you are not sure which one
58 you need, select both, and the correct one should be selected for
61 This driver makes the adapter appear as a normal Ethernet interface,
62 typically on eth0, if it is the only ethernet device, or perhaps on
63 eth1, if you have a PCI or ISA ethernet card installed.
65 To compile this driver as a module, choose M here: the
66 module will be called kaweth.
69 tristate "USB Pegasus/Pegasus-II based ethernet device support"
72 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
73 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
74 complete list of supported devices.
76 If your particular adapter is not in the list and you are _sure_ it
77 is Pegasus or Pegasus II based then send me
78 <petkan@users.sourceforge.net> vendor and device IDs.
80 To compile this driver as a module, choose M here: the
81 module will be called pegasus.
84 tristate "USB RTL8150 based ethernet device support"
87 Say Y here if you have RTL8150 based usb-ethernet adapter.
88 Send me <petkan@users.sourceforge.net> any comments you may have.
89 You can also check for updates at <http://pegasus2.sourceforge.net/>.
91 To compile this driver as a module, choose M here: the
92 module will be called rtl8150.
95 tristate "Realtek RTL8152 Based USB 2.0 Ethernet Adapters"
98 This option adds support for Realtek RTL8152 based USB 2.0
99 10/100 Ethernet adapters.
101 To compile this driver as a module, choose M here: the
102 module will be called r8152.
105 tristate "Multi-purpose USB Networking Framework"
108 This driver supports several kinds of network links over USB,
109 with "minidrivers" built around a common network driver core
110 that supports deep queues for efficient transfers. (This gives
111 better performance with small packets and at high speeds).
113 The USB host runs "usbnet", and the other end of the link might be:
115 - Another USB host, when using USB "network" or "data transfer"
116 cables. These are often used to network laptops to PCs, like
117 "Laplink" parallel cables or some motherboards. These rely
118 on specialized chips from many suppliers.
120 - An intelligent USB gadget, perhaps embedding a Linux system.
121 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
122 others), and devices that interoperate using the standard
123 CDC-Ethernet specification (including many cable modems).
125 - Network adapter hardware (like those for 10/100 Ethernet) which
126 uses this driver framework.
128 The link will appear with a name like "usb0", when the link is
129 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
130 two-node links are most easily managed with Ethernet Bridging
131 (CONFIG_BRIDGE) instead of routing.
133 For more information see <http://www.linux-usb.org/usbnet/>.
135 To compile this driver as a module, choose M here: the
136 module will be called usbnet.
138 config USB_NET_AX8817X
139 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
140 depends on USB_USBNET
145 This option adds support for ASIX AX88xxx based USB 2.0
146 10/100 Ethernet adapters.
148 This driver should work with at least the following devices:
151 * Billionton Systems, USB2AR
153 * Corega FEther USB2-TX
159 * Intellinet USB 2.0 Ethernet
160 * ST Lab USB 2.0 Ethernet
163 This driver creates an interface named "ethX", where X depends on
164 what other networking devices you have in use.
166 config USB_NET_AX88179_178A
167 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
168 depends on USB_USBNET
173 This option adds support for ASIX AX88179 based USB 3.0/2.0
174 to Gigabit Ethernet adapters.
176 This driver should work with at least the following devices:
181 This driver creates an interface named "ethX", where X depends on
182 what other networking devices you have in use.
184 config USB_NET_CDCETHER
185 tristate "CDC Ethernet support (smart devices such as cable modems)"
186 depends on USB_USBNET
189 This option supports devices conforming to the Communication Device
190 Class (CDC) Ethernet Control Model, a specification that's easy to
191 implement in device firmware. The CDC specifications are available
192 from <http://www.usb.org/>.
194 CDC Ethernet is an implementation option for DOCSIS cable modems
195 that support USB connectivity, used for non-Microsoft USB hosts.
196 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
197 This driver should work with at least the following devices:
199 * Dell Wireless 5530 HSPA
200 * Ericsson PipeRider (all variants)
201 * Ericsson Mobile Broadband Module (all variants)
202 * Motorola (DM100 and SB4100)
203 * Broadcom Cable Modem (reference design)
204 * Toshiba (PCX1100U and F3507g/F3607gw)
207 This driver creates an interface named "ethX", where X depends on
208 what other networking devices you have in use. However, if the
209 IEEE 802 "local assignment" bit is set in the address, a "usbX"
210 name is used instead.
212 config USB_NET_CDC_EEM
213 tristate "CDC EEM support"
214 depends on USB_USBNET
216 This option supports devices conforming to the Communication Device
217 Class (CDC) Ethernet Emulation Model, a specification that's easy to
218 implement in device firmware. The CDC EEM specifications are available
219 from <http://www.usb.org/>.
221 This driver creates an interface named "ethX", where X depends on
222 what other networking devices you have in use. However, if the
223 IEEE 802 "local assignment" bit is set in the address, a "usbX"
224 name is used instead.
226 config USB_NET_CDC_NCM
227 tristate "CDC NCM support"
228 depends on USB_USBNET
231 This driver provides support for CDC NCM (Network Control Model
232 Device USB Class Specification). The CDC NCM specification is
233 available from <http://www.usb.org/>.
235 Say "y" to link the driver statically, or "m" to build a
236 dynamically linked module.
238 This driver should work with at least the following devices:
239 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
240 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
241 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
242 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
243 * Ericsson F5521gw Mobile Broadband Module
245 config USB_NET_HUAWEI_CDC_NCM
246 tristate "Huawei NCM embedded AT channel support"
247 depends on USB_USBNET
249 select USB_NET_CDC_NCM
251 This driver supports huawei-style NCM devices, that use NCM as a
252 transport for other protocols, usually an embedded AT channel.
257 To compile this driver as a module, choose M here: the module will be
258 called huawei_cdc_ncm.ko.
260 config USB_NET_CDC_MBIM
261 tristate "CDC MBIM support"
262 depends on USB_USBNET
264 select USB_NET_CDC_NCM
266 This driver provides support for CDC MBIM (Mobile Broadband
267 Interface Model) devices. The CDC MBIM specification is
268 available from <http://www.usb.org/>.
270 MBIM devices require configuration using the management
271 protocol defined by the MBIM specification. This driver
272 provides unfiltered access to the MBIM control channel
273 through the associated /dev/cdc-wdmx character device.
275 To compile this driver as a module, choose M here: the
276 module will be called cdc_mbim.
278 config USB_NET_DM9601
279 tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
280 depends on USB_USBNET
283 This option adds support for Davicom DM9601 based USB 1.1
284 10/100 Ethernet adapters.
286 config USB_NET_SR9700
287 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
288 depends on USB_USBNET
291 This option adds support for CoreChip-sz SR9700 based USB 1.1
292 10/100 Ethernet adapters.
294 config USB_NET_SMSC75XX
295 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
296 depends on USB_USBNET
301 This option adds support for SMSC LAN75XX based USB 2.0
302 Gigabit Ethernet adapters.
304 config USB_NET_SMSC95XX
305 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
306 depends on USB_USBNET
311 This option adds support for SMSC LAN95XX based USB 2.0
312 10/100 Ethernet adapters.
314 config USB_NET_GL620A
315 tristate "GeneSys GL620USB-A based cables"
316 depends on USB_USBNET
318 Choose this option if you're using a host-to-host cable,
319 or PC2PC motherboard, with this chip.
321 Note that the half-duplex "GL620USB" is not supported.
323 config USB_NET_NET1080
324 tristate "NetChip 1080 based cables (Laplink, ...)"
326 depends on USB_USBNET
328 Choose this option if you're using a host-to-host cable based
329 on this design: one NetChip 1080 chip and supporting logic,
330 optionally with LEDs that indicate traffic
333 tristate "Prolific PL-2301/2302/25A1 based cables"
334 # if the handshake/init/reset problems, from original 'plusb',
335 # are ever resolved ... then remove "experimental"
336 depends on USB_USBNET
338 Choose this option if you're using a host-to-host cable
339 with one of these chips.
341 config USB_NET_MCS7830
342 tristate "MosChip MCS7830 based Ethernet adapters"
343 depends on USB_USBNET
345 Choose this option if you're using a 10/100 Ethernet USB2
346 adapter based on the MosChip 7830 controller. This includes
347 adapters marketed under the DeLOCK brand.
349 config USB_NET_RNDIS_HOST
350 tristate "Host for RNDIS and ActiveSync devices"
351 depends on USB_USBNET
352 select USB_NET_CDCETHER
354 This option enables hosting "Remote NDIS" USB networking links,
355 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
356 various devices that may only support this protocol. A variant
357 of this protocol (with even less public documentation) seems to
358 be at the root of Microsoft's "ActiveSync" too.
360 Avoid using this protocol unless you have no better options.
361 The protocol specification is incomplete, and is controlled by
362 (and for) Microsoft; it isn't an "Open" ecosystem or market.
364 config USB_NET_CDC_SUBSET
365 tristate "Simple USB Network Links (CDC Ethernet subset)"
366 depends on USB_USBNET
369 This driver module supports USB network devices that can work
370 without any device-specific information. Select it if you have
371 one of these drivers.
373 Note that while many USB host-to-host cables can work in this mode,
374 that may mean not being able to talk to Win32 systems or more
375 commonly not being able to handle certain events (like replugging
376 the host on the other end) very well. Also, these devices will
377 not generally have permanently assigned Ethernet addresses.
380 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
381 depends on USB_NET_CDC_SUBSET
383 Choose this option if you're using a host-to-host cable
384 based on this design, which supports USB 2.0 high speed.
387 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
388 depends on USB_NET_CDC_SUBSET
390 Choose this option if you're using a host-to-host cable
391 based on this design. Note that AnchorChips is now a
395 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
396 depends on USB_NET_CDC_SUBSET
399 Choose this option if you're using a host-to-host cable
400 based on this design: two NetChip 2890 chips and an Atmel
401 microcontroller, with LEDs that indicate traffic.
404 boolean "Embedded ARM Linux links (iPaq, ...)"
405 depends on USB_NET_CDC_SUBSET
408 Choose this option to support the "usb-eth" networking driver
409 used by most of the ARM Linux community with device controllers
410 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
411 in some PXA versions of the "blob" boot loader.
413 Linux-based "Gumstix" PXA-25x based systems use this protocol
414 to talk with other Linux systems.
416 Although the ROMs shipped with Sharp Zaurus products use a
417 different link level framing protocol, you can have them use
418 this simpler protocol by installing a different kernel.
421 boolean "Epson 2888 based firmware (DEVELOPMENT)"
422 depends on USB_NET_CDC_SUBSET
424 Choose this option to support the usb networking links used
425 by some sample firmware from Epson.
428 boolean "KT Technology KC2190 based cables (InstaNet)"
429 depends on USB_NET_CDC_SUBSET
431 Choose this option if you're using a host-to-host cable
432 with one of these chips.
434 config USB_NET_ZAURUS
435 tristate "Sharp Zaurus (stock ROMs) and compatible"
436 depends on USB_USBNET
437 select USB_NET_CDCETHER
441 Choose this option to support the usb networking links used by
442 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
443 This also supports some related device firmware, as used in some
444 PDAs from Olympus and some cell phones from Motorola.
446 If you install an alternate image, such as the Linux 2.6 based
447 versions of OpenZaurus, you should no longer need to support this
448 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
449 really need this non-conformant variant of CDC Ethernet (or in
450 some cases CDC MDLM) protocol, not "g_ether".
452 config USB_NET_CX82310_ETH
453 tristate "Conexant CX82310 USB ethernet port"
454 depends on USB_USBNET
456 Choose this option if you're using a Conexant CX82310-based ADSL
457 router with USB ethernet port. This driver is for routers only,
458 it will not work with ADSL modems (use cxacru driver instead).
460 config USB_NET_KALMIA
461 tristate "Samsung Kalmia based LTE USB modem"
462 depends on USB_USBNET
464 Choose this option if you have a Samsung Kalmia based USB modem
467 To compile this driver as a module, choose M here: the
468 module will be called kalmia.
470 config USB_NET_QMI_WWAN
471 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
472 depends on USB_USBNET
475 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
476 (MDM) chipsets. Examples of such devices are
479 This driver will only drive the ethernet part of the chips.
480 The devices require additional configuration to be usable.
481 Multiple management interfaces with linux drivers are
484 * option: AT commands on /dev/ttyUSBx
485 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
487 A modem manager with support for QMI is recommended.
489 To compile this driver as a module, choose M here: the
490 module will be called qmi_wwan.
493 tristate "Option USB High Speed Mobile Devices"
494 depends on USB && RFKILL && TTY
497 Choose this option if you have an Option HSDPA/HSUPA card.
498 These cards support downlink speeds of 7.2Mbps or greater.
500 To compile this driver as a module, choose M here: the
501 module will be called hso.
503 config USB_NET_INT51X1
504 tristate "Intellon PLC based usb adapter"
505 depends on USB_USBNET
507 Choose this option if you're using a 14Mb USB-based PLC
508 (Powerline Communications) solution with an Intellon
509 INT51x1/INT5200 chip, like the "devolo dLan duo".
511 config USB_CDC_PHONET
512 tristate "CDC Phonet support"
515 Choose this option to support the Phonet interface to a Nokia
516 cellular modem, as found on most Nokia handsets with the
517 "PC suite" USB profile.
520 tristate "Apple iPhone USB Ethernet driver"
523 Module used to share Internet connection (tethering) from your
524 iPhone (Original, 3G and 3GS) to your system.
525 Note that you need userspace libraries and programs that are needed
526 to pair your device with your system and that understand the iPhone
529 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
531 config USB_SIERRA_NET
532 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
533 depends on USB_USBNET
535 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
537 To compile this driver as a module, choose M here: the
538 module will be called sierra_net.
541 tristate "LG VL600 modem dongle"
542 depends on USB_NET_CDCETHER && TTY
545 Select this if you want to use an LG Electronics 4G/LTE usb modem
546 called VL600. This driver only handles the ethernet
547 interface exposed by the modem firmware. To establish a connection
548 you will first need a userspace program that sends the right
549 command to the modem through its CDC ACM port, and most
550 likely also a DHCP client. See this thread about using the
551 4G modem from Verizon:
553 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17