2 # USB Network devices configuration
4 comment "Host-side USB support is needed for USB Network Adapter support"
7 menuconfig USB_NET_DRIVERS
8 tristate "USB Network Adapters"
15 tristate "USB CATC NetMate-based Ethernet device support"
18 Say Y if you want to use one of the following 10Mbps USB Ethernet
19 device based on the EL1210A chip. Supported devices are:
26 This driver makes the adapter appear as a normal Ethernet interface,
27 typically on eth0, if it is the only ethernet device, or perhaps on
28 eth1, if you have a PCI or ISA ethernet card installed.
30 To compile this driver as a module, choose M here: the
31 module will be called catc.
34 tristate "USB KLSI KL5USB101-based ethernet device support"
36 Say Y here if you want to use one of the following 10Mbps only
37 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
41 ASANTE USB To Ethernet Adapter
42 AOX Endpoints USB Ethernet
44 D-Link DSB-650C and DU-E10
45 Entrega / Portgear E45
47 Jaton USB Ethernet Device Adapter
48 Kingston Technology USB Ethernet Adapter
50 Mobility USB-Ethernet Adapter
52 Peracom Enet and Enet2
53 Portsmith Express Ethernet Adapter
56 Sony Vaio port extender
58 This driver is likely to work with most 10Mbps only USB Ethernet
59 adapters, including some "no brand" devices. It does NOT work on
60 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
61 the CATC NetMate driver for those. If you are not sure which one
62 you need, select both, and the correct one should be selected for
65 This driver makes the adapter appear as a normal Ethernet interface,
66 typically on eth0, if it is the only ethernet device, or perhaps on
67 eth1, if you have a PCI or ISA ethernet card installed.
69 To compile this driver as a module, choose M here: the
70 module will be called kaweth.
73 tristate "USB Pegasus/Pegasus-II based ethernet device support"
76 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
77 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
78 complete list of supported devices.
80 If your particular adapter is not in the list and you are _sure_ it
81 is Pegasus or Pegasus II based then send me
82 <petkan@users.sourceforge.net> vendor and device IDs.
84 To compile this driver as a module, choose M here: the
85 module will be called pegasus.
88 tristate "USB RTL8150 based ethernet device support"
91 Say Y here if you have RTL8150 based usb-ethernet adapter.
92 Send me <petkan@users.sourceforge.net> any comments you may have.
93 You can also check for updates at <http://pegasus2.sourceforge.net/>.
95 To compile this driver as a module, choose M here: the
96 module will be called rtl8150.
99 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
102 This option adds support for Realtek RTL8152 based USB 2.0
103 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
106 To compile this driver as a module, choose M here: the
107 module will be called r8152.
110 tristate "Microchip LAN78XX Based USB Ethernet Adapters"
115 This option adds support for Microchip LAN78XX based USB 2
116 & USB 3 10/100/1000 Ethernet adapters.
118 To compile this driver as a module, choose M here: the
119 module will be called lan78xx.
122 tristate "Multi-purpose USB Networking Framework"
125 This driver supports several kinds of network links over USB,
126 with "minidrivers" built around a common network driver core
127 that supports deep queues for efficient transfers. (This gives
128 better performance with small packets and at high speeds).
130 The USB host runs "usbnet", and the other end of the link might be:
132 - Another USB host, when using USB "network" or "data transfer"
133 cables. These are often used to network laptops to PCs, like
134 "Laplink" parallel cables or some motherboards. These rely
135 on specialized chips from many suppliers.
137 - An intelligent USB gadget, perhaps embedding a Linux system.
138 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
139 others), and devices that interoperate using the standard
140 CDC-Ethernet specification (including many cable modems).
142 - Network adapter hardware (like those for 10/100 Ethernet) which
143 uses this driver framework.
145 The link will appear with a name like "usb0", when the link is
146 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
147 two-node links are most easily managed with Ethernet Bridging
148 (CONFIG_BRIDGE) instead of routing.
150 For more information see <http://www.linux-usb.org/usbnet/>.
152 To compile this driver as a module, choose M here: the
153 module will be called usbnet.
155 config USB_NET_AX8817X
156 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
157 depends on USB_USBNET
162 This option adds support for ASIX AX88xxx based USB 2.0
163 10/100 Ethernet adapters.
165 This driver should work with at least the following devices:
168 * Billionton Systems, USB2AR
170 * Corega FEther USB2-TX
177 * Intellinet USB 2.0 Ethernet
178 * ST Lab USB 2.0 Ethernet
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_AX88179_178A
185 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
186 depends on USB_USBNET
191 This option adds support for ASIX AX88179 based USB 3.0/2.0
192 to Gigabit Ethernet adapters.
194 This driver should work with at least the following devices:
199 This driver creates an interface named "ethX", where X depends on
200 what other networking devices you have in use.
202 config USB_NET_CDCETHER
203 tristate "CDC Ethernet support (smart devices such as cable modems)"
204 depends on USB_USBNET
207 This option supports devices conforming to the Communication Device
208 Class (CDC) Ethernet Control Model, a specification that's easy to
209 implement in device firmware. The CDC specifications are available
210 from <http://www.usb.org/>.
212 CDC Ethernet is an implementation option for DOCSIS cable modems
213 that support USB connectivity, used for non-Microsoft USB hosts.
214 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
215 This driver should work with at least the following devices:
217 * Dell Wireless 5530 HSPA
218 * Ericsson PipeRider (all variants)
219 * Ericsson Mobile Broadband Module (all variants)
220 * Motorola (DM100 and SB4100)
221 * Broadcom Cable Modem (reference design)
222 * Toshiba (PCX1100U and F3507g/F3607gw)
225 This driver creates an interface named "ethX", where X depends on
226 what other networking devices you have in use. However, if the
227 IEEE 802 "local assignment" bit is set in the address, a "usbX"
228 name is used instead.
230 config USB_NET_CDC_EEM
231 tristate "CDC EEM support"
232 depends on USB_USBNET
234 This option supports devices conforming to the Communication Device
235 Class (CDC) Ethernet Emulation Model, a specification that's easy to
236 implement in device firmware. The CDC EEM specifications are available
237 from <http://www.usb.org/>.
239 This driver creates an interface named "ethX", where X depends on
240 what other networking devices you have in use. However, if the
241 IEEE 802 "local assignment" bit is set in the address, a "usbX"
242 name is used instead.
244 config USB_NET_CDC_NCM
245 tristate "CDC NCM support"
246 depends on USB_USBNET
249 This driver provides support for CDC NCM (Network Control Model
250 Device USB Class Specification). The CDC NCM specification is
251 available from <http://www.usb.org/>.
253 Say "y" to link the driver statically, or "m" to build a
254 dynamically linked module.
256 This driver should work with at least the following devices:
257 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
258 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
259 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
260 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
261 * Ericsson F5521gw Mobile Broadband Module
263 config USB_NET_HUAWEI_CDC_NCM
264 tristate "Huawei NCM embedded AT channel support"
265 depends on USB_USBNET
267 select USB_NET_CDC_NCM
269 This driver supports huawei-style NCM devices, that use NCM as a
270 transport for other protocols, usually an embedded AT channel.
275 To compile this driver as a module, choose M here: the module will be
276 called huawei_cdc_ncm.ko.
278 config USB_NET_CDC_MBIM
279 tristate "CDC MBIM support"
280 depends on USB_USBNET
282 select USB_NET_CDC_NCM
284 This driver provides support for CDC MBIM (Mobile Broadband
285 Interface Model) devices. The CDC MBIM specification is
286 available from <http://www.usb.org/>.
288 MBIM devices require configuration using the management
289 protocol defined by the MBIM specification. This driver
290 provides unfiltered access to the MBIM control channel
291 through the associated /dev/cdc-wdmx character device.
293 To compile this driver as a module, choose M here: the
294 module will be called cdc_mbim.
296 config USB_NET_DM9601
297 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
298 depends on USB_USBNET
301 This option adds support for Davicom DM9601/DM9620/DM9621A
302 based USB 10/100 Ethernet adapters.
304 config USB_NET_SR9700
305 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
306 depends on USB_USBNET
309 This option adds support for CoreChip-sz SR9700 based USB 1.1
310 10/100 Ethernet adapters.
312 config USB_NET_SR9800
313 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
314 depends on USB_USBNET
317 Say Y if you want to use one of the following 100Mbps USB Ethernet
318 device based on the CoreChip-sz SR9800 chip.
320 This driver makes the adapter appear as a normal Ethernet interface,
321 typically on eth0, if it is the only ethernet device, or perhaps on
322 eth1, if you have a PCI or ISA ethernet card installed.
324 To compile this driver as a module, choose M here: the
325 module will be called sr9800.
327 config USB_NET_SMSC75XX
328 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
329 depends on USB_USBNET
334 This option adds support for SMSC LAN75XX based USB 2.0
335 Gigabit Ethernet adapters.
337 config USB_NET_SMSC95XX
338 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
339 depends on USB_USBNET
344 This option adds support for SMSC LAN95XX based USB 2.0
345 10/100 Ethernet adapters.
347 config USB_NET_GL620A
348 tristate "GeneSys GL620USB-A based cables"
349 depends on USB_USBNET
351 Choose this option if you're using a host-to-host cable,
352 or PC2PC motherboard, with this chip.
354 Note that the half-duplex "GL620USB" is not supported.
356 config USB_NET_NET1080
357 tristate "NetChip 1080 based cables (Laplink, ...)"
359 depends on USB_USBNET
361 Choose this option if you're using a host-to-host cable based
362 on this design: one NetChip 1080 chip and supporting logic,
363 optionally with LEDs that indicate traffic
366 tristate "Prolific PL-2301/2302/25A1 based cables"
367 # if the handshake/init/reset problems, from original 'plusb',
368 # are ever resolved ... then remove "experimental"
369 depends on USB_USBNET
371 Choose this option if you're using a host-to-host cable
372 with one of these chips.
374 config USB_NET_MCS7830
375 tristate "MosChip MCS7830 based Ethernet adapters"
376 depends on USB_USBNET
378 Choose this option if you're using a 10/100 Ethernet USB2
379 adapter based on the MosChip 7830 controller. This includes
380 adapters marketed under the DeLOCK brand.
382 config USB_NET_RNDIS_HOST
383 tristate "Host for RNDIS and ActiveSync devices"
384 depends on USB_USBNET
385 select USB_NET_CDCETHER
387 This option enables hosting "Remote NDIS" USB networking links,
388 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
389 various devices that may only support this protocol. A variant
390 of this protocol (with even less public documentation) seems to
391 be at the root of Microsoft's "ActiveSync" too.
393 Avoid using this protocol unless you have no better options.
394 The protocol specification is incomplete, and is controlled by
395 (and for) Microsoft; it isn't an "Open" ecosystem or market.
397 config USB_NET_CDC_SUBSET
398 tristate "Simple USB Network Links (CDC Ethernet subset)"
399 depends on USB_USBNET
402 This driver module supports USB network devices that can work
403 without any device-specific information. Select it if you have
404 one of these drivers.
406 Note that while many USB host-to-host cables can work in this mode,
407 that may mean not being able to talk to Win32 systems or more
408 commonly not being able to handle certain events (like replugging
409 the host on the other end) very well. Also, these devices will
410 not generally have permanently assigned Ethernet addresses.
413 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
414 depends on USB_NET_CDC_SUBSET
416 Choose this option if you're using a host-to-host cable
417 based on this design, which supports USB 2.0 high speed.
420 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
421 depends on USB_NET_CDC_SUBSET
423 Choose this option if you're using a host-to-host cable
424 based on this design. Note that AnchorChips is now a
428 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
429 depends on USB_NET_CDC_SUBSET
432 Choose this option if you're using a host-to-host cable
433 based on this design: two NetChip 2890 chips and an Atmel
434 microcontroller, with LEDs that indicate traffic.
437 bool "Embedded ARM Linux links (iPaq, ...)"
438 depends on USB_NET_CDC_SUBSET
441 Choose this option to support the "usb-eth" networking driver
442 used by most of the ARM Linux community with device controllers
443 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
444 in some PXA versions of the "blob" boot loader.
446 Linux-based "Gumstix" PXA-25x based systems use this protocol
447 to talk with other Linux systems.
449 Although the ROMs shipped with Sharp Zaurus products use a
450 different link level framing protocol, you can have them use
451 this simpler protocol by installing a different kernel.
454 bool "Epson 2888 based firmware (DEVELOPMENT)"
455 depends on USB_NET_CDC_SUBSET
457 Choose this option to support the usb networking links used
458 by some sample firmware from Epson.
461 bool "KT Technology KC2190 based cables (InstaNet)"
462 depends on USB_NET_CDC_SUBSET
464 Choose this option if you're using a host-to-host cable
465 with one of these chips.
467 config USB_NET_ZAURUS
468 tristate "Sharp Zaurus (stock ROMs) and compatible"
469 depends on USB_USBNET
470 select USB_NET_CDCETHER
474 Choose this option to support the usb networking links used by
475 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
476 This also supports some related device firmware, as used in some
477 PDAs from Olympus and some cell phones from Motorola.
479 If you install an alternate image, such as the Linux 2.6 based
480 versions of OpenZaurus, you should no longer need to support this
481 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
482 really need this non-conformant variant of CDC Ethernet (or in
483 some cases CDC MDLM) protocol, not "g_ether".
485 config USB_NET_CX82310_ETH
486 tristate "Conexant CX82310 USB ethernet port"
487 depends on USB_USBNET
489 Choose this option if you're using a Conexant CX82310-based ADSL
490 router with USB ethernet port. This driver is for routers only,
491 it will not work with ADSL modems (use cxacru driver instead).
493 config USB_NET_KALMIA
494 tristate "Samsung Kalmia based LTE USB modem"
495 depends on USB_USBNET
497 Choose this option if you have a Samsung Kalmia based USB modem
500 To compile this driver as a module, choose M here: the
501 module will be called kalmia.
503 config USB_NET_QMI_WWAN
504 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
505 depends on USB_USBNET
508 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
509 (MDM) chipsets. Examples of such devices are
512 This driver will only drive the ethernet part of the chips.
513 The devices require additional configuration to be usable.
514 Multiple management interfaces with linux drivers are
517 * option: AT commands on /dev/ttyUSBx
518 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
520 A modem manager with support for QMI is recommended.
522 To compile this driver as a module, choose M here: the
523 module will be called qmi_wwan.
526 tristate "Option USB High Speed Mobile Devices"
527 depends on USB && RFKILL && TTY
530 Choose this option if you have an Option HSDPA/HSUPA card.
531 These cards support downlink speeds of 7.2Mbps or greater.
533 To compile this driver as a module, choose M here: the
534 module will be called hso.
536 config USB_NET_INT51X1
537 tristate "Intellon PLC based usb adapter"
538 depends on USB_USBNET
540 Choose this option if you're using a 14Mb USB-based PLC
541 (Powerline Communications) solution with an Intellon
542 INT51x1/INT5200 chip, like the "devolo dLan duo".
544 config USB_CDC_PHONET
545 tristate "CDC Phonet support"
546 depends on PHONET && USB_USBNET
548 Choose this option to support the Phonet interface to a Nokia
549 cellular modem, as found on most Nokia handsets with the
550 "PC suite" USB profile.
553 tristate "Apple iPhone USB Ethernet driver"
556 Module used to share Internet connection (tethering) from your
557 iPhone (Original, 3G and 3GS) to your system.
558 Note that you need userspace libraries and programs that are needed
559 to pair your device with your system and that understand the iPhone
562 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
564 config USB_SIERRA_NET
565 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
566 depends on USB_USBNET
568 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
570 To compile this driver as a module, choose M here: the
571 module will be called sierra_net.
574 tristate "LG VL600 modem dongle"
575 depends on USB_NET_CDCETHER && TTY
578 Select this if you want to use an LG Electronics 4G/LTE usb modem
579 called VL600. This driver only handles the ethernet
580 interface exposed by the modem firmware. To establish a connection
581 you will first need a userspace program that sends the right
582 command to the modem through its CDC ACM port, and most
583 likely also a DHCP client. See this thread about using the
584 4G modem from Verizon:
586 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
588 config USB_NET_CH9200
589 tristate "QingHeng CH9200 USB ethernet support"
590 depends on USB_USBNET
593 Choose this option if you have a USB ethernet adapter with a QinHeng
596 To compile this driver as a module, choose M here: the
597 module will be called ch9200.
599 endif # USB_NET_DRIVERS