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"
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
174 This option adds support for ASIX AX88xxx based USB 2.0
175 10/100 Ethernet adapters.
177 This driver should work with at least the following devices:
180 * Billionton Systems, USB2AR
181 * Billionton Systems, GUSB2AM-1G-B
183 * Corega FEther USB2-TX
190 * Intellinet USB 2.0 Ethernet
191 * ST Lab USB 2.0 Ethernet
194 This driver creates an interface named "ethX", where X depends on
195 what other networking devices you have in use.
197 config USB_NET_AX88179_178A
198 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
199 depends on USB_USBNET
204 This option adds support for ASIX AX88179 based USB 3.0/2.0
205 to Gigabit Ethernet adapters.
207 This driver should work with at least the following devices:
212 This driver creates an interface named "ethX", where X depends on
213 what other networking devices you have in use.
215 config USB_NET_CDCETHER
216 tristate "CDC Ethernet support (smart devices such as cable modems)"
217 depends on USB_USBNET
220 This option supports devices conforming to the Communication Device
221 Class (CDC) Ethernet Control Model, a specification that's easy to
222 implement in device firmware. The CDC specifications are available
223 from <http://www.usb.org/>.
225 CDC Ethernet is an implementation option for DOCSIS cable modems
226 that support USB connectivity, used for non-Microsoft USB hosts.
227 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
228 This driver should work with at least the following devices:
230 * Dell Wireless 5530 HSPA
231 * Ericsson PipeRider (all variants)
232 * Ericsson Mobile Broadband Module (all variants)
233 * Motorola (DM100 and SB4100)
234 * Broadcom Cable Modem (reference design)
235 * Toshiba (PCX1100U and F3507g/F3607gw)
238 This driver creates an interface named "ethX", where X depends on
239 what other networking devices you have in use. However, if the
240 IEEE 802 "local assignment" bit is set in the address, a "usbX"
241 name is used instead.
243 config USB_NET_CDC_EEM
244 tristate "CDC EEM support"
245 depends on USB_USBNET
247 This option supports devices conforming to the Communication Device
248 Class (CDC) Ethernet Emulation Model, a specification that's easy to
249 implement in device firmware. The CDC EEM specifications are available
250 from <http://www.usb.org/>.
252 This driver creates an interface named "ethX", where X depends on
253 what other networking devices you have in use. However, if the
254 IEEE 802 "local assignment" bit is set in the address, a "usbX"
255 name is used instead.
257 config USB_NET_CDC_NCM
258 tristate "CDC NCM support"
259 depends on USB_USBNET
260 select USB_NET_CDCETHER
263 This driver provides support for CDC NCM (Network Control Model
264 Device USB Class Specification). The CDC NCM specification is
265 available from <http://www.usb.org/>.
267 Say "y" to link the driver statically, or "m" to build a
268 dynamically linked module.
270 This driver should work with at least the following devices:
271 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
272 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
273 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
274 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
275 * Ericsson F5521gw Mobile Broadband Module
277 config USB_NET_HUAWEI_CDC_NCM
278 tristate "Huawei NCM embedded AT channel support"
279 depends on USB_USBNET
281 select USB_NET_CDC_NCM
283 This driver supports huawei-style NCM devices, that use NCM as a
284 transport for other protocols, usually an embedded AT channel.
289 To compile this driver as a module, choose M here: the module will be
290 called huawei_cdc_ncm.ko.
292 config USB_NET_CDC_MBIM
293 tristate "CDC MBIM support"
294 depends on USB_USBNET
296 select USB_NET_CDC_NCM
298 This driver provides support for CDC MBIM (Mobile Broadband
299 Interface Model) devices. The CDC MBIM specification is
300 available from <http://www.usb.org/>.
302 MBIM devices require configuration using the management
303 protocol defined by the MBIM specification. This driver
304 provides unfiltered access to the MBIM control channel
305 through the associated /dev/cdc-wdmx character device.
307 To compile this driver as a module, choose M here: the
308 module will be called cdc_mbim.
310 config USB_NET_DM9601
311 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
312 depends on USB_USBNET
315 This option adds support for Davicom DM9601/DM9620/DM9621A
316 based USB 10/100 Ethernet adapters.
318 config USB_NET_SR9700
319 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
320 depends on USB_USBNET
323 This option adds support for CoreChip-sz SR9700 based USB 1.1
324 10/100 Ethernet adapters.
326 config USB_NET_SR9800
327 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
328 depends on USB_USBNET
331 Say Y if you want to use one of the following 100Mbps USB Ethernet
332 device based on the CoreChip-sz SR9800 chip.
334 This driver makes the adapter appear as a normal Ethernet interface,
335 typically on eth0, if it is the only ethernet device, or perhaps on
336 eth1, if you have a PCI or ISA ethernet card installed.
338 To compile this driver as a module, choose M here: the
339 module will be called sr9800.
341 config USB_NET_SMSC75XX
342 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
343 depends on USB_USBNET
348 This option adds support for SMSC LAN75XX based USB 2.0
349 Gigabit Ethernet adapters.
351 config USB_NET_SMSC95XX
352 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
353 depends on USB_USBNET
360 This option adds support for SMSC LAN95XX based USB 2.0
361 10/100 Ethernet adapters.
363 config USB_NET_GL620A
364 tristate "GeneSys GL620USB-A based cables"
365 depends on USB_USBNET
367 Choose this option if you're using a host-to-host cable,
368 or PC2PC motherboard, with this chip.
370 Note that the half-duplex "GL620USB" is not supported.
372 config USB_NET_NET1080
373 tristate "NetChip 1080 based cables (Laplink, ...)"
375 depends on USB_USBNET
377 Choose this option if you're using a host-to-host cable based
378 on this design: one NetChip 1080 chip and supporting logic,
379 optionally with LEDs that indicate traffic
382 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
383 # if the handshake/init/reset problems, from original 'plusb',
384 # are ever resolved ... then remove "experimental"
385 depends on USB_USBNET
387 Choose this option if you're using a host-to-host cable
388 with one of these chips.
390 config USB_NET_MCS7830
391 tristate "MosChip MCS7830 based Ethernet adapters"
392 depends on USB_USBNET
394 Choose this option if you're using a 10/100 Ethernet USB2
395 adapter based on the MosChip 7830 controller. This includes
396 adapters marketed under the DeLOCK brand.
398 config USB_NET_RNDIS_HOST
399 tristate "Host for RNDIS and ActiveSync devices"
400 depends on USB_USBNET
401 select USB_NET_CDCETHER
403 This option enables hosting "Remote NDIS" USB networking links,
404 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
405 various devices that may only support this protocol. A variant
406 of this protocol (with even less public documentation) seems to
407 be at the root of Microsoft's "ActiveSync" too.
409 Avoid using this protocol unless you have no better options.
410 The protocol specification is incomplete, and is controlled by
411 (and for) Microsoft; it isn't an "Open" ecosystem or market.
413 config USB_NET_CDC_SUBSET_ENABLE
415 depends on USB_NET_CDC_SUBSET
417 config USB_NET_CDC_SUBSET
418 tristate "Simple USB Network Links (CDC Ethernet subset)"
419 depends on USB_USBNET
422 This driver module supports USB network devices that can work
423 without any device-specific information. Select it if you have
424 one of these drivers.
426 Note that while many USB host-to-host cables can work in this mode,
427 that may mean not being able to talk to Win32 systems or more
428 commonly not being able to handle certain events (like replugging
429 the host on the other end) very well. Also, these devices will
430 not generally have permanently assigned Ethernet addresses.
433 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
434 depends on USB_NET_CDC_SUBSET
435 select USB_NET_CDC_SUBSET_ENABLE
437 Choose this option if you're using a host-to-host cable
438 based on this design, which supports USB 2.0 high speed.
441 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
442 depends on USB_NET_CDC_SUBSET
443 select USB_NET_CDC_SUBSET_ENABLE
445 Choose this option if you're using a host-to-host cable
446 based on this design. Note that AnchorChips is now a
450 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
451 depends on USB_NET_CDC_SUBSET
452 select USB_NET_CDC_SUBSET_ENABLE
455 Choose this option if you're using a host-to-host cable
456 based on this design: two NetChip 2890 chips and an Atmel
457 microcontroller, with LEDs that indicate traffic.
460 bool "Embedded ARM Linux links (iPaq, ...)"
461 depends on USB_NET_CDC_SUBSET
462 select USB_NET_CDC_SUBSET_ENABLE
465 Choose this option to support the "usb-eth" networking driver
466 used by most of the ARM Linux community with device controllers
467 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
468 in some PXA versions of the "blob" boot loader.
470 Linux-based "Gumstix" PXA-25x based systems use this protocol
471 to talk with other Linux systems.
473 Although the ROMs shipped with Sharp Zaurus products use a
474 different link level framing protocol, you can have them use
475 this simpler protocol by installing a different kernel.
478 bool "Epson 2888 based firmware (DEVELOPMENT)"
479 depends on USB_NET_CDC_SUBSET
480 select USB_NET_CDC_SUBSET_ENABLE
482 Choose this option to support the usb networking links used
483 by some sample firmware from Epson.
486 bool "KT Technology KC2190 based cables (InstaNet)"
487 depends on USB_NET_CDC_SUBSET
488 select USB_NET_CDC_SUBSET_ENABLE
490 Choose this option if you're using a host-to-host cable
491 with one of these chips.
493 config USB_NET_ZAURUS
494 tristate "Sharp Zaurus (stock ROMs) and compatible"
495 depends on USB_USBNET
496 select USB_NET_CDCETHER
500 Choose this option to support the usb networking links used by
501 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
502 This also supports some related device firmware, as used in some
503 PDAs from Olympus and some cell phones from Motorola.
505 If you install an alternate image, such as the Linux 2.6 based
506 versions of OpenZaurus, you should no longer need to support this
507 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
508 really need this non-conformant variant of CDC Ethernet (or in
509 some cases CDC MDLM) protocol, not "g_ether".
511 config USB_NET_CX82310_ETH
512 tristate "Conexant CX82310 USB ethernet port"
513 depends on USB_USBNET
515 Choose this option if you're using a Conexant CX82310-based ADSL
516 router with USB ethernet port. This driver is for routers only,
517 it will not work with ADSL modems (use cxacru driver instead).
519 config USB_NET_KALMIA
520 tristate "Samsung Kalmia based LTE USB modem"
521 depends on USB_USBNET
523 Choose this option if you have a Samsung Kalmia based USB modem
526 To compile this driver as a module, choose M here: the
527 module will be called kalmia.
529 config USB_NET_QMI_WWAN
530 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
531 depends on USB_USBNET
534 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
535 (MDM) chipsets. Examples of such devices are
538 This driver will only drive the ethernet part of the chips.
539 The devices require additional configuration to be usable.
540 Multiple management interfaces with linux drivers are
543 * option: AT commands on /dev/ttyUSBx
544 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
546 A modem manager with support for QMI is recommended.
548 To compile this driver as a module, choose M here: the
549 module will be called qmi_wwan.
552 tristate "Option USB High Speed Mobile Devices"
553 depends on USB && RFKILL && TTY
556 Choose this option if you have an Option HSDPA/HSUPA card.
557 These cards support downlink speeds of 7.2Mbps or greater.
559 To compile this driver as a module, choose M here: the
560 module will be called hso.
562 config USB_NET_INT51X1
563 tristate "Intellon PLC based usb adapter"
564 depends on USB_USBNET
566 Choose this option if you're using a 14Mb USB-based PLC
567 (Powerline Communications) solution with an Intellon
568 INT51x1/INT5200 chip, like the "devolo dLan duo".
570 config USB_CDC_PHONET
571 tristate "CDC Phonet support"
572 depends on PHONET && USB_USBNET
574 Choose this option to support the Phonet interface to a Nokia
575 cellular modem, as found on most Nokia handsets with the
576 "PC suite" USB profile.
579 tristate "Apple iPhone USB Ethernet driver"
582 Module used to share Internet connection (tethering) from your
583 iPhone (Original, 3G and 3GS) to your system.
584 Note that you need userspace libraries and programs that are needed
585 to pair your device with your system and that understand the iPhone
588 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
590 config USB_SIERRA_NET
591 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
592 depends on USB_USBNET
594 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
596 To compile this driver as a module, choose M here: the
597 module will be called sierra_net.
600 tristate "LG VL600 modem dongle"
601 depends on USB_NET_CDCETHER && TTY
604 Select this if you want to use an LG Electronics 4G/LTE usb modem
605 called VL600. This driver only handles the ethernet
606 interface exposed by the modem firmware. To establish a connection
607 you will first need a userspace program that sends the right
608 command to the modem through its CDC ACM port, and most
609 likely also a DHCP client. See this thread about using the
610 4G modem from Verizon:
612 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
614 config USB_NET_CH9200
615 tristate "QingHeng CH9200 USB ethernet support"
616 depends on USB_USBNET
619 Choose this option if you have a USB ethernet adapter with a QinHeng
622 To compile this driver as a module, choose M here: the
623 module will be called ch9200.
625 config USB_NET_AQC111
626 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
627 depends on USB_USBNET
630 This option adds support for Aquantia AQtion USB
631 Ethernet adapters based on AQC111U/AQC112 chips.
633 This driver should work with at least the following devices:
634 * Aquantia AQtion USB to 5GbE
636 endif # USB_NET_DRIVERS