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
83 <petkan@users.sourceforge.net> vendor and device IDs.
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.
93 Send me <petkan@users.sourceforge.net> any comments you may have.
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"
103 This option adds support for Realtek RTL8152 based USB 2.0
104 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
107 To compile this driver as a module, choose M here: the
108 module will be called r8152.
111 tristate "Microchip LAN78XX Based USB Ethernet Adapters"
117 This option adds support for Microchip LAN78XX based USB 2
118 & USB 3 10/100/1000 Ethernet adapters.
119 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
120 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
121 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
123 Proper PHY driver is required for LAN7801.
125 To compile this driver as a module, choose M here: the
126 module will be called lan78xx.
129 tristate "Multi-purpose USB Networking Framework"
132 This driver supports several kinds of network links over USB,
133 with "minidrivers" built around a common network driver core
134 that supports deep queues for efficient transfers. (This gives
135 better performance with small packets and at high speeds).
137 The USB host runs "usbnet", and the other end of the link might be:
139 - Another USB host, when using USB "network" or "data transfer"
140 cables. These are often used to network laptops to PCs, like
141 "Laplink" parallel cables or some motherboards. These rely
142 on specialized chips from many suppliers.
144 - An intelligent USB gadget, perhaps embedding a Linux system.
145 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
146 others), and devices that interoperate using the standard
147 CDC-Ethernet specification (including many cable modems).
149 - Network adapter hardware (like those for 10/100 Ethernet) which
150 uses this driver framework.
152 The link will appear with a name like "usb0", when the link is
153 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
154 two-node links are most easily managed with Ethernet Bridging
155 (CONFIG_BRIDGE) instead of routing.
157 For more information see <http://www.linux-usb.org/usbnet/>.
159 To compile this driver as a module, choose M here: the
160 module will be called usbnet.
162 config USB_NET_AX8817X
163 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
164 depends on USB_USBNET
169 This option adds support for ASIX AX88xxx based USB 2.0
170 10/100 Ethernet adapters.
172 This driver should work with at least the following devices:
175 * Billionton Systems, USB2AR
176 * Billionton Systems, GUSB2AM-1G-B
178 * Corega FEther USB2-TX
185 * Intellinet USB 2.0 Ethernet
186 * ST Lab USB 2.0 Ethernet
189 This driver creates an interface named "ethX", where X depends on
190 what other networking devices you have in use.
192 config USB_NET_AX88179_178A
193 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
194 depends on USB_USBNET
199 This option adds support for ASIX AX88179 based USB 3.0/2.0
200 to Gigabit Ethernet adapters.
202 This driver should work with at least the following devices:
207 This driver creates an interface named "ethX", where X depends on
208 what other networking devices you have in use.
210 config USB_NET_CDCETHER
211 tristate "CDC Ethernet support (smart devices such as cable modems)"
212 depends on USB_USBNET
215 This option supports devices conforming to the Communication Device
216 Class (CDC) Ethernet Control Model, a specification that's easy to
217 implement in device firmware. The CDC specifications are available
218 from <http://www.usb.org/>.
220 CDC Ethernet is an implementation option for DOCSIS cable modems
221 that support USB connectivity, used for non-Microsoft USB hosts.
222 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
223 This driver should work with at least the following devices:
225 * Dell Wireless 5530 HSPA
226 * Ericsson PipeRider (all variants)
227 * Ericsson Mobile Broadband Module (all variants)
228 * Motorola (DM100 and SB4100)
229 * Broadcom Cable Modem (reference design)
230 * Toshiba (PCX1100U and F3507g/F3607gw)
233 This driver creates an interface named "ethX", where X depends on
234 what other networking devices you have in use. However, if the
235 IEEE 802 "local assignment" bit is set in the address, a "usbX"
236 name is used instead.
238 config USB_NET_CDC_EEM
239 tristate "CDC EEM support"
240 depends on USB_USBNET
242 This option supports devices conforming to the Communication Device
243 Class (CDC) Ethernet Emulation Model, a specification that's easy to
244 implement in device firmware. The CDC EEM specifications are available
245 from <http://www.usb.org/>.
247 This driver creates an interface named "ethX", where X depends on
248 what other networking devices you have in use. However, if the
249 IEEE 802 "local assignment" bit is set in the address, a "usbX"
250 name is used instead.
252 config USB_NET_CDC_NCM
253 tristate "CDC NCM support"
254 depends on USB_USBNET
255 select USB_NET_CDCETHER
258 This driver provides support for CDC NCM (Network Control Model
259 Device USB Class Specification). The CDC NCM specification is
260 available from <http://www.usb.org/>.
262 Say "y" to link the driver statically, or "m" to build a
263 dynamically linked module.
265 This driver should work with at least the following devices:
266 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
267 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
268 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
269 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
270 * Ericsson F5521gw Mobile Broadband Module
272 config USB_NET_HUAWEI_CDC_NCM
273 tristate "Huawei NCM embedded AT channel support"
274 depends on USB_USBNET
276 select USB_NET_CDC_NCM
278 This driver supports huawei-style NCM devices, that use NCM as a
279 transport for other protocols, usually an embedded AT channel.
284 To compile this driver as a module, choose M here: the module will be
285 called huawei_cdc_ncm.ko.
287 config USB_NET_CDC_MBIM
288 tristate "CDC MBIM support"
289 depends on USB_USBNET
291 select USB_NET_CDC_NCM
293 This driver provides support for CDC MBIM (Mobile Broadband
294 Interface Model) devices. The CDC MBIM specification is
295 available from <http://www.usb.org/>.
297 MBIM devices require configuration using the management
298 protocol defined by the MBIM specification. This driver
299 provides unfiltered access to the MBIM control channel
300 through the associated /dev/cdc-wdmx character device.
302 To compile this driver as a module, choose M here: the
303 module will be called cdc_mbim.
305 config USB_NET_DM9601
306 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
307 depends on USB_USBNET
310 This option adds support for Davicom DM9601/DM9620/DM9621A
311 based USB 10/100 Ethernet adapters.
313 config USB_NET_SR9700
314 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
315 depends on USB_USBNET
318 This option adds support for CoreChip-sz SR9700 based USB 1.1
319 10/100 Ethernet adapters.
321 config USB_NET_SR9800
322 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
323 depends on USB_USBNET
326 Say Y if you want to use one of the following 100Mbps USB Ethernet
327 device based on the CoreChip-sz SR9800 chip.
329 This driver makes the adapter appear as a normal Ethernet interface,
330 typically on eth0, if it is the only ethernet device, or perhaps on
331 eth1, if you have a PCI or ISA ethernet card installed.
333 To compile this driver as a module, choose M here: the
334 module will be called sr9800.
336 config USB_NET_SMSC75XX
337 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
338 depends on USB_USBNET
343 This option adds support for SMSC LAN75XX based USB 2.0
344 Gigabit Ethernet adapters.
346 config USB_NET_SMSC95XX
347 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
348 depends on USB_USBNET
353 This option adds support for SMSC LAN95XX based USB 2.0
354 10/100 Ethernet adapters.
356 config USB_NET_GL620A
357 tristate "GeneSys GL620USB-A based cables"
358 depends on USB_USBNET
360 Choose this option if you're using a host-to-host cable,
361 or PC2PC motherboard, with this chip.
363 Note that the half-duplex "GL620USB" is not supported.
365 config USB_NET_NET1080
366 tristate "NetChip 1080 based cables (Laplink, ...)"
368 depends on USB_USBNET
370 Choose this option if you're using a host-to-host cable based
371 on this design: one NetChip 1080 chip and supporting logic,
372 optionally with LEDs that indicate traffic
375 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
376 # if the handshake/init/reset problems, from original 'plusb',
377 # are ever resolved ... then remove "experimental"
378 depends on USB_USBNET
380 Choose this option if you're using a host-to-host cable
381 with one of these chips.
383 config USB_NET_MCS7830
384 tristate "MosChip MCS7830 based Ethernet adapters"
385 depends on USB_USBNET
387 Choose this option if you're using a 10/100 Ethernet USB2
388 adapter based on the MosChip 7830 controller. This includes
389 adapters marketed under the DeLOCK brand.
391 config USB_NET_RNDIS_HOST
392 tristate "Host for RNDIS and ActiveSync devices"
393 depends on USB_USBNET
394 select USB_NET_CDCETHER
396 This option enables hosting "Remote NDIS" USB networking links,
397 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
398 various devices that may only support this protocol. A variant
399 of this protocol (with even less public documentation) seems to
400 be at the root of Microsoft's "ActiveSync" too.
402 Avoid using this protocol unless you have no better options.
403 The protocol specification is incomplete, and is controlled by
404 (and for) Microsoft; it isn't an "Open" ecosystem or market.
406 config USB_NET_CDC_SUBSET_ENABLE
408 depends on USB_NET_CDC_SUBSET
410 config USB_NET_CDC_SUBSET
411 tristate "Simple USB Network Links (CDC Ethernet subset)"
412 depends on USB_USBNET
415 This driver module supports USB network devices that can work
416 without any device-specific information. Select it if you have
417 one of these drivers.
419 Note that while many USB host-to-host cables can work in this mode,
420 that may mean not being able to talk to Win32 systems or more
421 commonly not being able to handle certain events (like replugging
422 the host on the other end) very well. Also, these devices will
423 not generally have permanently assigned Ethernet addresses.
426 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
427 depends on USB_NET_CDC_SUBSET
428 select USB_NET_CDC_SUBSET_ENABLE
430 Choose this option if you're using a host-to-host cable
431 based on this design, which supports USB 2.0 high speed.
434 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
435 depends on USB_NET_CDC_SUBSET
436 select USB_NET_CDC_SUBSET_ENABLE
438 Choose this option if you're using a host-to-host cable
439 based on this design. Note that AnchorChips is now a
443 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
444 depends on USB_NET_CDC_SUBSET
445 select USB_NET_CDC_SUBSET_ENABLE
448 Choose this option if you're using a host-to-host cable
449 based on this design: two NetChip 2890 chips and an Atmel
450 microcontroller, with LEDs that indicate traffic.
453 bool "Embedded ARM Linux links (iPaq, ...)"
454 depends on USB_NET_CDC_SUBSET
455 select USB_NET_CDC_SUBSET_ENABLE
458 Choose this option to support the "usb-eth" networking driver
459 used by most of the ARM Linux community with device controllers
460 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
461 in some PXA versions of the "blob" boot loader.
463 Linux-based "Gumstix" PXA-25x based systems use this protocol
464 to talk with other Linux systems.
466 Although the ROMs shipped with Sharp Zaurus products use a
467 different link level framing protocol, you can have them use
468 this simpler protocol by installing a different kernel.
471 bool "Epson 2888 based firmware (DEVELOPMENT)"
472 depends on USB_NET_CDC_SUBSET
473 select USB_NET_CDC_SUBSET_ENABLE
475 Choose this option to support the usb networking links used
476 by some sample firmware from Epson.
479 bool "KT Technology KC2190 based cables (InstaNet)"
480 depends on USB_NET_CDC_SUBSET
481 select USB_NET_CDC_SUBSET_ENABLE
483 Choose this option if you're using a host-to-host cable
484 with one of these chips.
486 config USB_NET_ZAURUS
487 tristate "Sharp Zaurus (stock ROMs) and compatible"
488 depends on USB_USBNET
489 select USB_NET_CDCETHER
493 Choose this option to support the usb networking links used by
494 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
495 This also supports some related device firmware, as used in some
496 PDAs from Olympus and some cell phones from Motorola.
498 If you install an alternate image, such as the Linux 2.6 based
499 versions of OpenZaurus, you should no longer need to support this
500 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
501 really need this non-conformant variant of CDC Ethernet (or in
502 some cases CDC MDLM) protocol, not "g_ether".
504 config USB_NET_CX82310_ETH
505 tristate "Conexant CX82310 USB ethernet port"
506 depends on USB_USBNET
508 Choose this option if you're using a Conexant CX82310-based ADSL
509 router with USB ethernet port. This driver is for routers only,
510 it will not work with ADSL modems (use cxacru driver instead).
512 config USB_NET_KALMIA
513 tristate "Samsung Kalmia based LTE USB modem"
514 depends on USB_USBNET
516 Choose this option if you have a Samsung Kalmia based USB modem
519 To compile this driver as a module, choose M here: the
520 module will be called kalmia.
522 config USB_NET_QMI_WWAN
523 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
524 depends on USB_USBNET
527 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
528 (MDM) chipsets. Examples of such devices are
531 This driver will only drive the ethernet part of the chips.
532 The devices require additional configuration to be usable.
533 Multiple management interfaces with linux drivers are
536 * option: AT commands on /dev/ttyUSBx
537 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
539 A modem manager with support for QMI is recommended.
541 To compile this driver as a module, choose M here: the
542 module will be called qmi_wwan.
545 tristate "Option USB High Speed Mobile Devices"
546 depends on USB && RFKILL && TTY
549 Choose this option if you have an Option HSDPA/HSUPA card.
550 These cards support downlink speeds of 7.2Mbps or greater.
552 To compile this driver as a module, choose M here: the
553 module will be called hso.
555 config USB_NET_INT51X1
556 tristate "Intellon PLC based usb adapter"
557 depends on USB_USBNET
559 Choose this option if you're using a 14Mb USB-based PLC
560 (Powerline Communications) solution with an Intellon
561 INT51x1/INT5200 chip, like the "devolo dLan duo".
563 config USB_CDC_PHONET
564 tristate "CDC Phonet support"
565 depends on PHONET && USB_USBNET
567 Choose this option to support the Phonet interface to a Nokia
568 cellular modem, as found on most Nokia handsets with the
569 "PC suite" USB profile.
572 tristate "Apple iPhone USB Ethernet driver"
575 Module used to share Internet connection (tethering) from your
576 iPhone (Original, 3G and 3GS) to your system.
577 Note that you need userspace libraries and programs that are needed
578 to pair your device with your system and that understand the iPhone
581 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
583 config USB_SIERRA_NET
584 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
585 depends on USB_USBNET
587 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
589 To compile this driver as a module, choose M here: the
590 module will be called sierra_net.
593 tristate "LG VL600 modem dongle"
594 depends on USB_NET_CDCETHER && TTY
597 Select this if you want to use an LG Electronics 4G/LTE usb modem
598 called VL600. This driver only handles the ethernet
599 interface exposed by the modem firmware. To establish a connection
600 you will first need a userspace program that sends the right
601 command to the modem through its CDC ACM port, and most
602 likely also a DHCP client. See this thread about using the
603 4G modem from Verizon:
605 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
607 config USB_NET_CH9200
608 tristate "QingHeng CH9200 USB ethernet support"
609 depends on USB_USBNET
612 Choose this option if you have a USB ethernet adapter with a QinHeng
615 To compile this driver as a module, choose M here: the
616 module will be called ch9200.
618 config USB_NET_AQC111
619 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
620 depends on USB_USBNET
623 This option adds support for Aquantia AQtion USB
624 Ethernet adapters based on AQC111U/AQC112 chips.
626 This driver should work with at least the following devices:
627 * Aquantia AQtion USB to 5GbE
629 endif # USB_NET_DRIVERS