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
257 This driver provides support for CDC NCM (Network Control Model
258 Device USB Class Specification). The CDC NCM specification is
259 available from <http://www.usb.org/>.
261 Say "y" to link the driver statically, or "m" to build a
262 dynamically linked module.
264 This driver should work with at least the following devices:
265 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
266 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
267 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
268 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
269 * Ericsson F5521gw Mobile Broadband Module
271 config USB_NET_HUAWEI_CDC_NCM
272 tristate "Huawei NCM embedded AT channel support"
273 depends on USB_USBNET
275 select USB_NET_CDC_NCM
277 This driver supports huawei-style NCM devices, that use NCM as a
278 transport for other protocols, usually an embedded AT channel.
283 To compile this driver as a module, choose M here: the module will be
284 called huawei_cdc_ncm.ko.
286 config USB_NET_CDC_MBIM
287 tristate "CDC MBIM support"
288 depends on USB_USBNET
290 select USB_NET_CDC_NCM
292 This driver provides support for CDC MBIM (Mobile Broadband
293 Interface Model) devices. The CDC MBIM specification is
294 available from <http://www.usb.org/>.
296 MBIM devices require configuration using the management
297 protocol defined by the MBIM specification. This driver
298 provides unfiltered access to the MBIM control channel
299 through the associated /dev/cdc-wdmx character device.
301 To compile this driver as a module, choose M here: the
302 module will be called cdc_mbim.
304 config USB_NET_DM9601
305 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
306 depends on USB_USBNET
309 This option adds support for Davicom DM9601/DM9620/DM9621A
310 based USB 10/100 Ethernet adapters.
312 config USB_NET_SR9700
313 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
314 depends on USB_USBNET
317 This option adds support for CoreChip-sz SR9700 based USB 1.1
318 10/100 Ethernet adapters.
320 config USB_NET_SR9800
321 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
322 depends on USB_USBNET
325 Say Y if you want to use one of the following 100Mbps USB Ethernet
326 device based on the CoreChip-sz SR9800 chip.
328 This driver makes the adapter appear as a normal Ethernet interface,
329 typically on eth0, if it is the only ethernet device, or perhaps on
330 eth1, if you have a PCI or ISA ethernet card installed.
332 To compile this driver as a module, choose M here: the
333 module will be called sr9800.
335 config USB_NET_SMSC75XX
336 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
337 depends on USB_USBNET
342 This option adds support for SMSC LAN75XX based USB 2.0
343 Gigabit Ethernet adapters.
345 config USB_NET_SMSC95XX
346 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
347 depends on USB_USBNET
352 This option adds support for SMSC LAN95XX based USB 2.0
353 10/100 Ethernet adapters.
355 config USB_NET_GL620A
356 tristate "GeneSys GL620USB-A based cables"
357 depends on USB_USBNET
359 Choose this option if you're using a host-to-host cable,
360 or PC2PC motherboard, with this chip.
362 Note that the half-duplex "GL620USB" is not supported.
364 config USB_NET_NET1080
365 tristate "NetChip 1080 based cables (Laplink, ...)"
367 depends on USB_USBNET
369 Choose this option if you're using a host-to-host cable based
370 on this design: one NetChip 1080 chip and supporting logic,
371 optionally with LEDs that indicate traffic
374 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
375 # if the handshake/init/reset problems, from original 'plusb',
376 # are ever resolved ... then remove "experimental"
377 depends on USB_USBNET
379 Choose this option if you're using a host-to-host cable
380 with one of these chips.
382 config USB_NET_MCS7830
383 tristate "MosChip MCS7830 based Ethernet adapters"
384 depends on USB_USBNET
386 Choose this option if you're using a 10/100 Ethernet USB2
387 adapter based on the MosChip 7830 controller. This includes
388 adapters marketed under the DeLOCK brand.
390 config USB_NET_RNDIS_HOST
391 tristate "Host for RNDIS and ActiveSync devices"
392 depends on USB_USBNET
393 select USB_NET_CDCETHER
395 This option enables hosting "Remote NDIS" USB networking links,
396 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
397 various devices that may only support this protocol. A variant
398 of this protocol (with even less public documentation) seems to
399 be at the root of Microsoft's "ActiveSync" too.
401 Avoid using this protocol unless you have no better options.
402 The protocol specification is incomplete, and is controlled by
403 (and for) Microsoft; it isn't an "Open" ecosystem or market.
405 config USB_NET_CDC_SUBSET_ENABLE
407 depends on USB_NET_CDC_SUBSET
409 config USB_NET_CDC_SUBSET
410 tristate "Simple USB Network Links (CDC Ethernet subset)"
411 depends on USB_USBNET
414 This driver module supports USB network devices that can work
415 without any device-specific information. Select it if you have
416 one of these drivers.
418 Note that while many USB host-to-host cables can work in this mode,
419 that may mean not being able to talk to Win32 systems or more
420 commonly not being able to handle certain events (like replugging
421 the host on the other end) very well. Also, these devices will
422 not generally have permanently assigned Ethernet addresses.
425 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
426 depends on USB_NET_CDC_SUBSET
427 select USB_NET_CDC_SUBSET_ENABLE
429 Choose this option if you're using a host-to-host cable
430 based on this design, which supports USB 2.0 high speed.
433 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
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. Note that AnchorChips is now a
442 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
443 depends on USB_NET_CDC_SUBSET
444 select USB_NET_CDC_SUBSET_ENABLE
447 Choose this option if you're using a host-to-host cable
448 based on this design: two NetChip 2890 chips and an Atmel
449 microcontroller, with LEDs that indicate traffic.
452 bool "Embedded ARM Linux links (iPaq, ...)"
453 depends on USB_NET_CDC_SUBSET
454 select USB_NET_CDC_SUBSET_ENABLE
457 Choose this option to support the "usb-eth" networking driver
458 used by most of the ARM Linux community with device controllers
459 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
460 in some PXA versions of the "blob" boot loader.
462 Linux-based "Gumstix" PXA-25x based systems use this protocol
463 to talk with other Linux systems.
465 Although the ROMs shipped with Sharp Zaurus products use a
466 different link level framing protocol, you can have them use
467 this simpler protocol by installing a different kernel.
470 bool "Epson 2888 based firmware (DEVELOPMENT)"
471 depends on USB_NET_CDC_SUBSET
472 select USB_NET_CDC_SUBSET_ENABLE
474 Choose this option to support the usb networking links used
475 by some sample firmware from Epson.
478 bool "KT Technology KC2190 based cables (InstaNet)"
479 depends on USB_NET_CDC_SUBSET
480 select USB_NET_CDC_SUBSET_ENABLE
482 Choose this option if you're using a host-to-host cable
483 with one of these chips.
485 config USB_NET_ZAURUS
486 tristate "Sharp Zaurus (stock ROMs) and compatible"
487 depends on USB_USBNET
488 select USB_NET_CDCETHER
492 Choose this option to support the usb networking links used by
493 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
494 This also supports some related device firmware, as used in some
495 PDAs from Olympus and some cell phones from Motorola.
497 If you install an alternate image, such as the Linux 2.6 based
498 versions of OpenZaurus, you should no longer need to support this
499 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
500 really need this non-conformant variant of CDC Ethernet (or in
501 some cases CDC MDLM) protocol, not "g_ether".
503 config USB_NET_CX82310_ETH
504 tristate "Conexant CX82310 USB ethernet port"
505 depends on USB_USBNET
507 Choose this option if you're using a Conexant CX82310-based ADSL
508 router with USB ethernet port. This driver is for routers only,
509 it will not work with ADSL modems (use cxacru driver instead).
511 config USB_NET_KALMIA
512 tristate "Samsung Kalmia based LTE USB modem"
513 depends on USB_USBNET
515 Choose this option if you have a Samsung Kalmia based USB modem
518 To compile this driver as a module, choose M here: the
519 module will be called kalmia.
521 config USB_NET_QMI_WWAN
522 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
523 depends on USB_USBNET
526 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
527 (MDM) chipsets. Examples of such devices are
530 This driver will only drive the ethernet part of the chips.
531 The devices require additional configuration to be usable.
532 Multiple management interfaces with linux drivers are
535 * option: AT commands on /dev/ttyUSBx
536 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
538 A modem manager with support for QMI is recommended.
540 To compile this driver as a module, choose M here: the
541 module will be called qmi_wwan.
544 tristate "Option USB High Speed Mobile Devices"
545 depends on USB && RFKILL && TTY
548 Choose this option if you have an Option HSDPA/HSUPA card.
549 These cards support downlink speeds of 7.2Mbps or greater.
551 To compile this driver as a module, choose M here: the
552 module will be called hso.
554 config USB_NET_INT51X1
555 tristate "Intellon PLC based usb adapter"
556 depends on USB_USBNET
558 Choose this option if you're using a 14Mb USB-based PLC
559 (Powerline Communications) solution with an Intellon
560 INT51x1/INT5200 chip, like the "devolo dLan duo".
562 config USB_CDC_PHONET
563 tristate "CDC Phonet support"
564 depends on PHONET && USB_USBNET
566 Choose this option to support the Phonet interface to a Nokia
567 cellular modem, as found on most Nokia handsets with the
568 "PC suite" USB profile.
571 tristate "Apple iPhone USB Ethernet driver"
574 Module used to share Internet connection (tethering) from your
575 iPhone (Original, 3G and 3GS) to your system.
576 Note that you need userspace libraries and programs that are needed
577 to pair your device with your system and that understand the iPhone
580 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
582 config USB_SIERRA_NET
583 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
584 depends on USB_USBNET
586 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
588 To compile this driver as a module, choose M here: the
589 module will be called sierra_net.
592 tristate "LG VL600 modem dongle"
593 depends on USB_NET_CDCETHER && TTY
596 Select this if you want to use an LG Electronics 4G/LTE usb modem
597 called VL600. This driver only handles the ethernet
598 interface exposed by the modem firmware. To establish a connection
599 you will first need a userspace program that sends the right
600 command to the modem through its CDC ACM port, and most
601 likely also a DHCP client. See this thread about using the
602 4G modem from Verizon:
604 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
606 config USB_NET_CH9200
607 tristate "QingHeng CH9200 USB ethernet support"
608 depends on USB_USBNET
611 Choose this option if you have a USB ethernet adapter with a QinHeng
614 To compile this driver as a module, choose M here: the
615 module will be called ch9200.
617 config USB_NET_AQC111
618 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
619 depends on USB_USBNET
622 This option adds support for Aquantia AQtion USB
623 Ethernet adapters based on AQC111U/AQC112 chips.
625 This driver should work with at least the following devices:
626 * Aquantia AQtion USB to 5GbE
628 endif # USB_NET_DRIVERS