1 # SPDX-License-Identifier: GPL-2.0-only
3 # USB Network devices configuration
5 comment "Host-side USB support is needed for USB Network Adapter support"
8 menuconfig USB_NET_DRIVERS
9 tristate "USB Network Adapters"
16 tristate "USB CATC NetMate-based Ethernet device support"
19 Say Y if you want to use one of the following 10Mbps USB Ethernet
20 device based on the EL1210A chip. Supported devices are:
27 This driver makes the adapter appear as a normal Ethernet interface,
28 typically on eth0, if it is the only ethernet device, or perhaps on
29 eth1, if you have a PCI or ISA ethernet card installed.
31 To compile this driver as a module, choose M here: the
32 module will be called catc.
35 tristate "USB KLSI KL5USB101-based ethernet device support"
37 Say Y here if you want to use one of the following 10Mbps only
38 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
42 ASANTE USB To Ethernet Adapter
43 AOX Endpoints USB Ethernet
45 D-Link DSB-650C and DU-E10
46 Entrega / Portgear E45
48 Jaton USB Ethernet Device Adapter
49 Kingston Technology USB Ethernet Adapter
51 Mobility USB-Ethernet Adapter
53 Peracom Enet and Enet2
54 Portsmith Express Ethernet Adapter
57 Sony Vaio port extender
59 This driver is likely to work with most 10Mbps only USB Ethernet
60 adapters, including some "no brand" devices. It does NOT work on
61 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
62 the CATC NetMate driver for those. If you are not sure which one
63 you need, select both, and the correct one should be selected for
66 This driver makes the adapter appear as a normal Ethernet interface,
67 typically on eth0, if it is the only ethernet device, or perhaps on
68 eth1, if you have a PCI or ISA ethernet card installed.
70 To compile this driver as a module, choose M here: the
71 module will be called kaweth.
74 tristate "USB Pegasus/Pegasus-II based ethernet device support"
77 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
78 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
79 complete list of supported devices.
81 If your particular adapter is not in the list and you are _sure_ it
82 is Pegasus or Pegasus II based then send me
85 To compile this driver as a module, choose M here: the
86 module will be called pegasus.
89 tristate "USB RTL8150 based ethernet device support"
92 Say Y here if you have RTL8150 based usb-ethernet adapter.
94 You can also check for updates at <http://pegasus2.sourceforge.net/>.
96 To compile this driver as a module, choose M here: the
97 module will be called rtl8150.
100 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
107 This option adds support for Realtek RTL8152 based USB 2.0
108 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
111 To compile this driver as a module, choose M here: the
112 module will be called r8152.
115 tristate "Microchip LAN78XX Based USB Ethernet Adapters"
122 This option adds support for Microchip LAN78XX based USB 2
123 & USB 3 10/100/1000 Ethernet adapters.
124 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
125 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
126 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
128 Proper PHY driver is required for LAN7801.
130 To compile this driver as a module, choose M here: the
131 module will be called lan78xx.
134 tristate "Multi-purpose USB Networking Framework"
137 This driver supports several kinds of network links over USB,
138 with "minidrivers" built around a common network driver core
139 that supports deep queues for efficient transfers. (This gives
140 better performance with small packets and at high speeds).
142 The USB host runs "usbnet", and the other end of the link might be:
144 - Another USB host, when using USB "network" or "data transfer"
145 cables. These are often used to network laptops to PCs, like
146 "Laplink" parallel cables or some motherboards. These rely
147 on specialized chips from many suppliers.
149 - An intelligent USB gadget, perhaps embedding a Linux system.
150 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
151 others), and devices that interoperate using the standard
152 CDC-Ethernet specification (including many cable modems).
154 - Network adapter hardware (like those for 10/100 Ethernet) which
155 uses this driver framework.
157 The link will appear with a name like "usb0", when the link is
158 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
159 two-node links are most easily managed with Ethernet Bridging
160 (CONFIG_BRIDGE) instead of routing.
162 For more information see <http://www.linux-usb.org/usbnet/>.
164 To compile this driver as a module, choose M here: the
165 module will be called usbnet.
167 config USB_NET_AX8817X
168 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
169 depends on USB_USBNET
176 This option adds support for ASIX AX88xxx based USB 2.0
177 10/100 Ethernet adapters.
179 This driver should work with at least the following devices:
182 * Billionton Systems, USB2AR
183 * Billionton Systems, GUSB2AM-1G-B
185 * Corega FEther USB2-TX
192 * Intellinet USB 2.0 Ethernet
193 * ST Lab USB 2.0 Ethernet
196 This driver creates an interface named "ethX", where X depends on
197 what other networking devices you have in use.
199 config USB_NET_AX88179_178A
200 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
201 depends on USB_USBNET
206 This option adds support for ASIX AX88179 based USB 3.0/2.0
207 to Gigabit Ethernet adapters.
209 This driver should work with at least the following devices:
214 This driver creates an interface named "ethX", where X depends on
215 what other networking devices you have in use.
217 config USB_NET_CDCETHER
218 tristate "CDC Ethernet support (smart devices such as cable modems)"
219 depends on USB_USBNET
222 This option supports devices conforming to the Communication Device
223 Class (CDC) Ethernet Control Model, a specification that's easy to
224 implement in device firmware. The CDC specifications are available
225 from <http://www.usb.org/>.
227 CDC Ethernet is an implementation option for DOCSIS cable modems
228 that support USB connectivity, used for non-Microsoft USB hosts.
229 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
230 This driver should work with at least the following devices:
232 * Dell Wireless 5530 HSPA
233 * Ericsson PipeRider (all variants)
234 * Ericsson Mobile Broadband Module (all variants)
235 * Motorola (DM100 and SB4100)
236 * Broadcom Cable Modem (reference design)
237 * Toshiba (PCX1100U and F3507g/F3607gw)
240 This driver creates an interface named "ethX", where X depends on
241 what other networking devices you have in use. However, if the
242 IEEE 802 "local assignment" bit is set in the address, a "usbX"
243 name is used instead.
245 config USB_NET_CDC_EEM
246 tristate "CDC EEM support"
247 depends on USB_USBNET
249 This option supports devices conforming to the Communication Device
250 Class (CDC) Ethernet Emulation Model, a specification that's easy to
251 implement in device firmware. The CDC EEM specifications are available
252 from <http://www.usb.org/>.
254 This driver creates an interface named "ethX", where X depends on
255 what other networking devices you have in use. However, if the
256 IEEE 802 "local assignment" bit is set in the address, a "usbX"
257 name is used instead.
259 config USB_NET_CDC_NCM
260 tristate "CDC NCM support"
261 depends on USB_USBNET
262 select USB_NET_CDCETHER
265 This driver provides support for CDC NCM (Network Control Model
266 Device USB Class Specification). The CDC NCM specification is
267 available from <http://www.usb.org/>.
269 Say "y" to link the driver statically, or "m" to build a
270 dynamically linked module.
272 This driver should work with at least the following devices:
273 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
274 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
275 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
276 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
277 * Ericsson F5521gw Mobile Broadband Module
279 config USB_NET_HUAWEI_CDC_NCM
280 tristate "Huawei NCM embedded AT channel support"
281 depends on USB_USBNET
283 select USB_NET_CDC_NCM
285 This driver supports huawei-style NCM devices, that use NCM as a
286 transport for other protocols, usually an embedded AT channel.
291 To compile this driver as a module, choose M here: the module will be
292 called huawei_cdc_ncm.ko.
294 config USB_NET_CDC_MBIM
295 tristate "CDC MBIM support"
296 depends on USB_USBNET
298 select USB_NET_CDC_NCM
300 This driver provides support for CDC MBIM (Mobile Broadband
301 Interface Model) devices. The CDC MBIM specification is
302 available from <http://www.usb.org/>.
304 MBIM devices require configuration using the management
305 protocol defined by the MBIM specification. This driver
306 provides unfiltered access to the MBIM control channel
307 through the associated /dev/cdc-wdmx character device.
309 To compile this driver as a module, choose M here: the
310 module will be called cdc_mbim.
312 config USB_NET_DM9601
313 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
314 depends on USB_USBNET
317 This option adds support for Davicom DM9601/DM9620/DM9621A
318 based USB 10/100 Ethernet adapters.
320 config USB_NET_SR9700
321 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
322 depends on USB_USBNET
325 This option adds support for CoreChip-sz SR9700 based USB 1.1
326 10/100 Ethernet adapters.
328 config USB_NET_SR9800
329 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
330 depends on USB_USBNET
333 Say Y if you want to use one of the following 100Mbps USB Ethernet
334 device based on the CoreChip-sz SR9800 chip.
336 This driver makes the adapter appear as a normal Ethernet interface,
337 typically on eth0, if it is the only ethernet device, or perhaps on
338 eth1, if you have a PCI or ISA ethernet card installed.
340 To compile this driver as a module, choose M here: the
341 module will be called sr9800.
343 config USB_NET_SMSC75XX
344 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
345 depends on USB_USBNET
350 This option adds support for SMSC LAN75XX based USB 2.0
351 Gigabit Ethernet adapters.
353 config USB_NET_SMSC95XX
354 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
355 depends on USB_USBNET
363 This option adds support for SMSC LAN95XX based USB 2.0
364 10/100 Ethernet adapters.
366 config USB_NET_GL620A
367 tristate "GeneSys GL620USB-A based cables"
368 depends on USB_USBNET
370 Choose this option if you're using a host-to-host cable,
371 or PC2PC motherboard, with this chip.
373 Note that the half-duplex "GL620USB" is not supported.
375 config USB_NET_NET1080
376 tristate "NetChip 1080 based cables (Laplink, ...)"
378 depends on USB_USBNET
380 Choose this option if you're using a host-to-host cable based
381 on this design: one NetChip 1080 chip and supporting logic,
382 optionally with LEDs that indicate traffic
385 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
386 # if the handshake/init/reset problems, from original 'plusb',
387 # are ever resolved ... then remove "experimental"
388 depends on USB_USBNET
390 Choose this option if you're using a host-to-host cable
391 with one of these chips.
393 config USB_NET_MCS7830
394 tristate "MosChip MCS7830 based Ethernet adapters"
395 depends on USB_USBNET
397 Choose this option if you're using a 10/100 Ethernet USB2
398 adapter based on the MosChip 7830 controller. This includes
399 adapters marketed under the DeLOCK brand.
401 config USB_NET_RNDIS_HOST
402 tristate "Host for RNDIS and ActiveSync devices"
403 depends on USB_USBNET
404 select USB_NET_CDCETHER
406 This option enables hosting "Remote NDIS" USB networking links,
407 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
408 various devices that may only support this protocol. A variant
409 of this protocol (with even less public documentation) seems to
410 be at the root of Microsoft's "ActiveSync" too.
412 Avoid using this protocol unless you have no better options.
413 The protocol specification is incomplete, and is controlled by
414 (and for) Microsoft; it isn't an "Open" ecosystem or market.
416 config USB_NET_CDC_SUBSET_ENABLE
418 depends on USB_NET_CDC_SUBSET
420 config USB_NET_CDC_SUBSET
421 tristate "Simple USB Network Links (CDC Ethernet subset)"
422 depends on USB_USBNET
425 This driver module supports USB network devices that can work
426 without any device-specific information. Select it if you have
427 one of these drivers.
429 Note that while many USB host-to-host cables can work in this mode,
430 that may mean not being able to talk to Win32 systems or more
431 commonly not being able to handle certain events (like replugging
432 the host on the other end) very well. Also, these devices will
433 not generally have permanently assigned Ethernet addresses.
436 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
437 depends on USB_NET_CDC_SUBSET
438 select USB_NET_CDC_SUBSET_ENABLE
440 Choose this option if you're using a host-to-host cable
441 based on this design, which supports USB 2.0 high speed.
444 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
445 depends on USB_NET_CDC_SUBSET
446 select USB_NET_CDC_SUBSET_ENABLE
448 Choose this option if you're using a host-to-host cable
449 based on this design. Note that AnchorChips is now a
453 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
454 depends on USB_NET_CDC_SUBSET
455 select USB_NET_CDC_SUBSET_ENABLE
458 Choose this option if you're using a host-to-host cable
459 based on this design: two NetChip 2890 chips and an Atmel
460 microcontroller, with LEDs that indicate traffic.
463 bool "Embedded ARM Linux links (iPaq, ...)"
464 depends on USB_NET_CDC_SUBSET
465 select USB_NET_CDC_SUBSET_ENABLE
468 Choose this option to support the "usb-eth" networking driver
469 used by most of the ARM Linux community with device controllers
470 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
471 in some PXA versions of the "blob" boot loader.
473 Linux-based "Gumstix" PXA-25x based systems use this protocol
474 to talk with other Linux systems.
476 Although the ROMs shipped with Sharp Zaurus products use a
477 different link level framing protocol, you can have them use
478 this simpler protocol by installing a different kernel.
481 bool "Epson 2888 based firmware (DEVELOPMENT)"
482 depends on USB_NET_CDC_SUBSET
483 select USB_NET_CDC_SUBSET_ENABLE
485 Choose this option to support the usb networking links used
486 by some sample firmware from Epson.
489 bool "KT Technology KC2190 based cables (InstaNet)"
490 depends on USB_NET_CDC_SUBSET
491 select USB_NET_CDC_SUBSET_ENABLE
493 Choose this option if you're using a host-to-host cable
494 with one of these chips.
496 config USB_NET_ZAURUS
497 tristate "Sharp Zaurus (stock ROMs) and compatible"
498 depends on USB_USBNET
499 select USB_NET_CDCETHER
503 Choose this option to support the usb networking links used by
504 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
505 This also supports some related device firmware, as used in some
506 PDAs from Olympus and some cell phones from Motorola.
508 If you install an alternate image, such as the Linux 2.6 based
509 versions of OpenZaurus, you should no longer need to support this
510 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
511 really need this non-conformant variant of CDC Ethernet (or in
512 some cases CDC MDLM) protocol, not "g_ether".
514 config USB_NET_CX82310_ETH
515 tristate "Conexant CX82310 USB ethernet port"
516 depends on USB_USBNET
518 Choose this option if you're using a Conexant CX82310-based ADSL
519 router with USB ethernet port. This driver is for routers only,
520 it will not work with ADSL modems (use cxacru driver instead).
522 config USB_NET_KALMIA
523 tristate "Samsung Kalmia based LTE USB modem"
524 depends on USB_USBNET
526 Choose this option if you have a Samsung Kalmia based USB modem
529 To compile this driver as a module, choose M here: the
530 module will be called kalmia.
532 config USB_NET_QMI_WWAN
533 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
534 depends on USB_USBNET
537 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
538 (MDM) chipsets. Examples of such devices are
541 This driver will only drive the ethernet part of the chips.
542 The devices require additional configuration to be usable.
543 Multiple management interfaces with linux drivers are
546 * option: AT commands on /dev/ttyUSBx
547 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
549 A modem manager with support for QMI is recommended.
551 To compile this driver as a module, choose M here: the
552 module will be called qmi_wwan.
555 tristate "Option USB High Speed Mobile Devices"
556 depends on USB && RFKILL && TTY
559 Choose this option if you have an Option HSDPA/HSUPA card.
560 These cards support downlink speeds of 7.2Mbps or greater.
562 To compile this driver as a module, choose M here: the
563 module will be called hso.
565 config USB_NET_INT51X1
566 tristate "Intellon PLC based usb adapter"
567 depends on USB_USBNET
569 Choose this option if you're using a 14Mb USB-based PLC
570 (Powerline Communications) solution with an Intellon
571 INT51x1/INT5200 chip, like the "devolo dLan duo".
573 config USB_CDC_PHONET
574 tristate "CDC Phonet support"
575 depends on PHONET && USB_USBNET
577 Choose this option to support the Phonet interface to a Nokia
578 cellular modem, as found on most Nokia handsets with the
579 "PC suite" USB profile.
582 tristate "Apple iPhone USB Ethernet driver"
585 Module used to share Internet connection (tethering) from your
586 iPhone to your system.
587 Note that you need a corresponding userspace library/program
588 to pair your device with your system, for example usbmuxd
589 <https://github.com/libimobiledevice/usbmuxd>.
591 config USB_SIERRA_NET
592 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
593 depends on USB_USBNET
595 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
597 To compile this driver as a module, choose M here: the
598 module will be called sierra_net.
601 tristate "LG VL600 modem dongle"
602 depends on USB_NET_CDCETHER && TTY
605 Select this if you want to use an LG Electronics 4G/LTE usb modem
606 called VL600. This driver only handles the ethernet
607 interface exposed by the modem firmware. To establish a connection
608 you will first need a userspace program that sends the right
609 command to the modem through its CDC ACM port, and most
610 likely also a DHCP client. See this thread about using the
611 4G modem from Verizon:
613 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
615 config USB_NET_CH9200
616 tristate "QingHeng CH9200 USB ethernet support"
617 depends on USB_USBNET
620 Choose this option if you have a USB ethernet adapter with a QinHeng
623 To compile this driver as a module, choose M here: the
624 module will be called ch9200.
626 config USB_NET_AQC111
627 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
628 depends on USB_USBNET
631 This option adds support for Aquantia AQtion USB
632 Ethernet adapters based on AQC111U/AQC112 chips.
634 This driver should work with at least the following devices:
635 * Aquantia AQtion USB to 5GbE
637 config USB_RTL8153_ECM
639 depends on USB_NET_CDCETHER && (USB_RTL8152 || USB_RTL8152=n)
642 This option supports ECM mode for RTL8153 ethernet adapter, when
643 CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
644 supported by r8152 driver.
646 endif # USB_NET_DRIVERS