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"
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"
121 This option adds support for Microchip LAN78XX based USB 2
122 & USB 3 10/100/1000 Ethernet adapters.
123 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
124 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
125 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
127 Proper PHY driver is required for LAN7801.
129 To compile this driver as a module, choose M here: the
130 module will be called lan78xx.
133 tristate "Multi-purpose USB Networking Framework"
136 This driver supports several kinds of network links over USB,
137 with "minidrivers" built around a common network driver core
138 that supports deep queues for efficient transfers. (This gives
139 better performance with small packets and at high speeds).
141 The USB host runs "usbnet", and the other end of the link might be:
143 - Another USB host, when using USB "network" or "data transfer"
144 cables. These are often used to network laptops to PCs, like
145 "Laplink" parallel cables or some motherboards. These rely
146 on specialized chips from many suppliers.
148 - An intelligent USB gadget, perhaps embedding a Linux system.
149 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
150 others), and devices that interoperate using the standard
151 CDC-Ethernet specification (including many cable modems).
153 - Network adapter hardware (like those for 10/100 Ethernet) which
154 uses this driver framework.
156 The link will appear with a name like "usb0", when the link is
157 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
158 two-node links are most easily managed with Ethernet Bridging
159 (CONFIG_BRIDGE) instead of routing.
161 For more information see <http://www.linux-usb.org/usbnet/>.
163 To compile this driver as a module, choose M here: the
164 module will be called usbnet.
166 config USB_NET_AX8817X
167 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
168 depends on USB_USBNET
175 This option adds support for ASIX AX88xxx based USB 2.0
176 10/100 Ethernet adapters.
178 This driver should work with at least the following devices:
181 * Billionton Systems, USB2AR
182 * Billionton Systems, GUSB2AM-1G-B
184 * Corega FEther USB2-TX
191 * Intellinet USB 2.0 Ethernet
192 * ST Lab USB 2.0 Ethernet
195 This driver creates an interface named "ethX", where X depends on
196 what other networking devices you have in use.
198 config USB_NET_AX88179_178A
199 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
200 depends on USB_USBNET
205 This option adds support for ASIX AX88179 based USB 3.0/2.0
206 to Gigabit Ethernet adapters.
208 This driver should work with at least the following devices:
213 This driver creates an interface named "ethX", where X depends on
214 what other networking devices you have in use.
216 config USB_NET_CDCETHER
217 tristate "CDC Ethernet support (smart devices such as cable modems)"
218 depends on USB_USBNET
221 This option supports devices conforming to the Communication Device
222 Class (CDC) Ethernet Control Model, a specification that's easy to
223 implement in device firmware. The CDC specifications are available
224 from <http://www.usb.org/>.
226 CDC Ethernet is an implementation option for DOCSIS cable modems
227 that support USB connectivity, used for non-Microsoft USB hosts.
228 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
229 This driver should work with at least the following devices:
231 * Dell Wireless 5530 HSPA
232 * Ericsson PipeRider (all variants)
233 * Ericsson Mobile Broadband Module (all variants)
234 * Motorola (DM100 and SB4100)
235 * Broadcom Cable Modem (reference design)
236 * Toshiba (PCX1100U and F3507g/F3607gw)
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_EEM
245 tristate "CDC EEM support"
246 depends on USB_USBNET
248 This option supports devices conforming to the Communication Device
249 Class (CDC) Ethernet Emulation Model, a specification that's easy to
250 implement in device firmware. The CDC EEM specifications are available
251 from <http://www.usb.org/>.
253 This driver creates an interface named "ethX", where X depends on
254 what other networking devices you have in use. However, if the
255 IEEE 802 "local assignment" bit is set in the address, a "usbX"
256 name is used instead.
258 config USB_NET_CDC_NCM
259 tristate "CDC NCM support"
260 depends on USB_USBNET
261 select USB_NET_CDCETHER
264 This driver provides support for CDC NCM (Network Control Model
265 Device USB Class Specification). The CDC NCM specification is
266 available from <http://www.usb.org/>.
268 Say "y" to link the driver statically, or "m" to build a
269 dynamically linked module.
271 This driver should work with at least the following devices:
272 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
273 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
274 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
275 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
276 * Ericsson F5521gw Mobile Broadband Module
278 config USB_NET_HUAWEI_CDC_NCM
279 tristate "Huawei NCM embedded AT channel support"
280 depends on USB_USBNET
282 select USB_NET_CDC_NCM
284 This driver supports huawei-style NCM devices, that use NCM as a
285 transport for other protocols, usually an embedded AT channel.
290 To compile this driver as a module, choose M here: the module will be
291 called huawei_cdc_ncm.ko.
293 config USB_NET_CDC_MBIM
294 tristate "CDC MBIM support"
295 depends on USB_USBNET
297 select USB_NET_CDC_NCM
299 This driver provides support for CDC MBIM (Mobile Broadband
300 Interface Model) devices. The CDC MBIM specification is
301 available from <http://www.usb.org/>.
303 MBIM devices require configuration using the management
304 protocol defined by the MBIM specification. This driver
305 provides unfiltered access to the MBIM control channel
306 through the associated /dev/cdc-wdmx character device.
308 To compile this driver as a module, choose M here: the
309 module will be called cdc_mbim.
311 config USB_NET_DM9601
312 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
313 depends on USB_USBNET
316 This option adds support for Davicom DM9601/DM9620/DM9621A
317 based USB 10/100 Ethernet adapters.
319 config USB_NET_SR9700
320 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
321 depends on USB_USBNET
324 This option adds support for CoreChip-sz SR9700 based USB 1.1
325 10/100 Ethernet adapters.
327 config USB_NET_SR9800
328 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
329 depends on USB_USBNET
332 Say Y if you want to use one of the following 100Mbps USB Ethernet
333 device based on the CoreChip-sz SR9800 chip.
335 This driver makes the adapter appear as a normal Ethernet interface,
336 typically on eth0, if it is the only ethernet device, or perhaps on
337 eth1, if you have a PCI or ISA ethernet card installed.
339 To compile this driver as a module, choose M here: the
340 module will be called sr9800.
342 config USB_NET_SMSC75XX
343 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
344 depends on USB_USBNET
349 This option adds support for SMSC LAN75XX based USB 2.0
350 Gigabit Ethernet adapters.
352 config USB_NET_SMSC95XX
353 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
354 depends on USB_USBNET
361 This option adds support for SMSC LAN95XX based USB 2.0
362 10/100 Ethernet adapters.
364 config USB_NET_GL620A
365 tristate "GeneSys GL620USB-A based cables"
366 depends on USB_USBNET
368 Choose this option if you're using a host-to-host cable,
369 or PC2PC motherboard, with this chip.
371 Note that the half-duplex "GL620USB" is not supported.
373 config USB_NET_NET1080
374 tristate "NetChip 1080 based cables (Laplink, ...)"
376 depends on USB_USBNET
378 Choose this option if you're using a host-to-host cable based
379 on this design: one NetChip 1080 chip and supporting logic,
380 optionally with LEDs that indicate traffic
383 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
384 # if the handshake/init/reset problems, from original 'plusb',
385 # are ever resolved ... then remove "experimental"
386 depends on USB_USBNET
388 Choose this option if you're using a host-to-host cable
389 with one of these chips.
391 config USB_NET_MCS7830
392 tristate "MosChip MCS7830 based Ethernet adapters"
393 depends on USB_USBNET
395 Choose this option if you're using a 10/100 Ethernet USB2
396 adapter based on the MosChip 7830 controller. This includes
397 adapters marketed under the DeLOCK brand.
399 config USB_NET_RNDIS_HOST
400 tristate "Host for RNDIS and ActiveSync devices"
401 depends on USB_USBNET
402 select USB_NET_CDCETHER
404 This option enables hosting "Remote NDIS" USB networking links,
405 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
406 various devices that may only support this protocol. A variant
407 of this protocol (with even less public documentation) seems to
408 be at the root of Microsoft's "ActiveSync" too.
410 Avoid using this protocol unless you have no better options.
411 The protocol specification is incomplete, and is controlled by
412 (and for) Microsoft; it isn't an "Open" ecosystem or market.
414 config USB_NET_CDC_SUBSET_ENABLE
416 depends on USB_NET_CDC_SUBSET
418 config USB_NET_CDC_SUBSET
419 tristate "Simple USB Network Links (CDC Ethernet subset)"
420 depends on USB_USBNET
423 This driver module supports USB network devices that can work
424 without any device-specific information. Select it if you have
425 one of these drivers.
427 Note that while many USB host-to-host cables can work in this mode,
428 that may mean not being able to talk to Win32 systems or more
429 commonly not being able to handle certain events (like replugging
430 the host on the other end) very well. Also, these devices will
431 not generally have permanently assigned Ethernet addresses.
434 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
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, which supports USB 2.0 high speed.
442 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
443 depends on USB_NET_CDC_SUBSET
444 select USB_NET_CDC_SUBSET_ENABLE
446 Choose this option if you're using a host-to-host cable
447 based on this design. Note that AnchorChips is now a
451 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
452 depends on USB_NET_CDC_SUBSET
453 select USB_NET_CDC_SUBSET_ENABLE
456 Choose this option if you're using a host-to-host cable
457 based on this design: two NetChip 2890 chips and an Atmel
458 microcontroller, with LEDs that indicate traffic.
461 bool "Embedded ARM Linux links (iPaq, ...)"
462 depends on USB_NET_CDC_SUBSET
463 select USB_NET_CDC_SUBSET_ENABLE
466 Choose this option to support the "usb-eth" networking driver
467 used by most of the ARM Linux community with device controllers
468 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
469 in some PXA versions of the "blob" boot loader.
471 Linux-based "Gumstix" PXA-25x based systems use this protocol
472 to talk with other Linux systems.
474 Although the ROMs shipped with Sharp Zaurus products use a
475 different link level framing protocol, you can have them use
476 this simpler protocol by installing a different kernel.
479 bool "Epson 2888 based firmware (DEVELOPMENT)"
480 depends on USB_NET_CDC_SUBSET
481 select USB_NET_CDC_SUBSET_ENABLE
483 Choose this option to support the usb networking links used
484 by some sample firmware from Epson.
487 bool "KT Technology KC2190 based cables (InstaNet)"
488 depends on USB_NET_CDC_SUBSET
489 select USB_NET_CDC_SUBSET_ENABLE
491 Choose this option if you're using a host-to-host cable
492 with one of these chips.
494 config USB_NET_ZAURUS
495 tristate "Sharp Zaurus (stock ROMs) and compatible"
496 depends on USB_USBNET
497 select USB_NET_CDCETHER
501 Choose this option to support the usb networking links used by
502 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
503 This also supports some related device firmware, as used in some
504 PDAs from Olympus and some cell phones from Motorola.
506 If you install an alternate image, such as the Linux 2.6 based
507 versions of OpenZaurus, you should no longer need to support this
508 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
509 really need this non-conformant variant of CDC Ethernet (or in
510 some cases CDC MDLM) protocol, not "g_ether".
512 config USB_NET_CX82310_ETH
513 tristate "Conexant CX82310 USB ethernet port"
514 depends on USB_USBNET
516 Choose this option if you're using a Conexant CX82310-based ADSL
517 router with USB ethernet port. This driver is for routers only,
518 it will not work with ADSL modems (use cxacru driver instead).
520 config USB_NET_KALMIA
521 tristate "Samsung Kalmia based LTE USB modem"
522 depends on USB_USBNET
524 Choose this option if you have a Samsung Kalmia based USB modem
527 To compile this driver as a module, choose M here: the
528 module will be called kalmia.
530 config USB_NET_QMI_WWAN
531 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
532 depends on USB_USBNET
535 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
536 (MDM) chipsets. Examples of such devices are
539 This driver will only drive the ethernet part of the chips.
540 The devices require additional configuration to be usable.
541 Multiple management interfaces with linux drivers are
544 * option: AT commands on /dev/ttyUSBx
545 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
547 A modem manager with support for QMI is recommended.
549 To compile this driver as a module, choose M here: the
550 module will be called qmi_wwan.
553 tristate "Option USB High Speed Mobile Devices"
554 depends on USB && RFKILL && TTY
557 Choose this option if you have an Option HSDPA/HSUPA card.
558 These cards support downlink speeds of 7.2Mbps or greater.
560 To compile this driver as a module, choose M here: the
561 module will be called hso.
563 config USB_NET_INT51X1
564 tristate "Intellon PLC based usb adapter"
565 depends on USB_USBNET
567 Choose this option if you're using a 14Mb USB-based PLC
568 (Powerline Communications) solution with an Intellon
569 INT51x1/INT5200 chip, like the "devolo dLan duo".
571 config USB_CDC_PHONET
572 tristate "CDC Phonet support"
573 depends on PHONET && USB_USBNET
575 Choose this option to support the Phonet interface to a Nokia
576 cellular modem, as found on most Nokia handsets with the
577 "PC suite" USB profile.
580 tristate "Apple iPhone USB Ethernet driver"
583 Module used to share Internet connection (tethering) from your
584 iPhone (Original, 3G and 3GS) to your system.
585 Note that you need userspace libraries and programs that are needed
586 to pair your device with your system and that understand the iPhone
589 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
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
638 tristate "RTL8153 ECM support"
639 depends on USB_NET_CDCETHER && (USB_RTL8152 || USB_RTL8152=n)
641 This option supports ECM mode for RTL8153 ethernet adapter, when
642 CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
643 supported by r8152 driver.
645 endif # USB_NET_DRIVERS