648 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# USB Network devices configuration4#5comment "Host-side USB support is needed for USB Network Adapter support"6 depends on !USB && NET7 8menuconfig USB_NET_DRIVERS9 tristate "USB Network Adapters"10 default USB if USB11 depends on USB && NET12 13if USB_NET_DRIVERS14 15config USB_CATC16 tristate "USB CATC NetMate-based Ethernet device support"17 select CRC3218 help19 Say Y if you want to use one of the following 10Mbps USB Ethernet20 device based on the EL1210A chip. Supported devices are:21 Belkin F5U01122 Belkin F5U11123 CATC NetMate24 CATC NetMate II25 smartBridges smartNIC26 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 on29 eth1, if you have a PCI or ISA ethernet card installed.30 31 To compile this driver as a module, choose M here: the32 module will be called catc.33 34config USB_KAWETH35 tristate "USB KLSI KL5USB101-based ethernet device support"36 help37 Say Y here if you want to use one of the following 10Mbps only38 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:39 3Com 3C1925040 ADS USB-10BT41 ATEN USB Ethernet42 ASANTE USB To Ethernet Adapter43 AOX Endpoints USB Ethernet44 Correga K.K.45 D-Link DSB-650C and DU-E1046 Entrega / Portgear E4547 I-O DATA USB-ET/T48 Jaton USB Ethernet Device Adapter49 Kingston Technology USB Ethernet Adapter50 Linksys USB10T51 Mobility USB-Ethernet Adapter52 NetGear EA-10153 Peracom Enet and Enet254 Portsmith Express Ethernet Adapter55 Shark Pocket Adapter56 SMC 2202USB57 Sony Vaio port extender58 59 This driver is likely to work with most 10Mbps only USB Ethernet60 adapters, including some "no brand" devices. It does NOT work on61 SmartBridges smartNIC or on Belkin F5U111 devices - you should use62 the CATC NetMate driver for those. If you are not sure which one63 you need, select both, and the correct one should be selected for64 you.65 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 on68 eth1, if you have a PCI or ISA ethernet card installed.69 70 To compile this driver as a module, choose M here: the71 module will be called kaweth.72 73config USB_PEGASUS74 tristate "USB Pegasus/Pegasus-II based ethernet device support"75 select MII76 help77 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 the79 complete list of supported devices.80 81 If your particular adapter is not in the list and you are _sure_ it82 is Pegasus or Pegasus II based then send me83 <petkan@users.sourceforge.net> vendor and device IDs.84 85 To compile this driver as a module, choose M here: the86 module will be called pegasus.87 88config USB_RTL815089 tristate "USB RTL8150 based ethernet device support"90 select MII91 help92 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/>.95 96 To compile this driver as a module, choose M here: the97 module will be called rtl8150.98 99config USB_RTL8152100 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"101 select MII102 select PHYLIB103 select CRC32104 select CRYPTO105 select CRYPTO_HASH106 select CRYPTO_SHA256107 help108 This option adds support for Realtek RTL8152 based USB 2.0109 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000110 Ethernet adapters.111 112 To compile this driver as a module, choose M here: the113 module will be called r8152.114 115config USB_LAN78XX116 tristate "Microchip LAN78XX Based USB Ethernet Adapters"117 select MII118 select PHYLIB119 select MICROCHIP_PHY120 select FIXED_PHY121 select CRC32122 help123 This option adds support for Microchip LAN78XX based USB 2124 & USB 3 10/100/1000 Ethernet adapters.125 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter126 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter127 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)128 129 Proper PHY driver is required for LAN7801.130 131 To compile this driver as a module, choose M here: the132 module will be called lan78xx.133 134config USB_USBNET135 tristate "Multi-purpose USB Networking Framework"136 select MII137 help138 This driver supports several kinds of network links over USB,139 with "minidrivers" built around a common network driver core140 that supports deep queues for efficient transfers. (This gives141 better performance with small packets and at high speeds).142 143 The USB host runs "usbnet", and the other end of the link might be:144 145 - Another USB host, when using USB "network" or "data transfer"146 cables. These are often used to network laptops to PCs, like147 "Laplink" parallel cables or some motherboards. These rely148 on specialized chips from many suppliers.149 150 - An intelligent USB gadget, perhaps embedding a Linux system.151 These include PDAs running Linux (iPaq, Yopy, Zaurus, and152 others), and devices that interoperate using the standard153 CDC-Ethernet specification (including many cable modems).154 155 - Network adapter hardware (like those for 10/100 Ethernet) which156 uses this driver framework.157 158 The link will appear with a name like "usb0", when the link is159 a two-node link, or "eth0" for most CDC-Ethernet devices. Those160 two-node links are most easily managed with Ethernet Bridging161 (CONFIG_BRIDGE) instead of routing.162 163 For more information see <http://www.linux-usb.org/usbnet/>.164 165 To compile this driver as a module, choose M here: the166 module will be called usbnet.167 168config USB_NET_AX8817X169 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"170 depends on USB_USBNET171 select CRC32172 select PHYLINK173 select AX88796B_PHY174 imply NET_SELFTESTS175 default y176 help177 This option adds support for ASIX AX88xxx based USB 2.0178 10/100 Ethernet adapters.179 180 This driver should work with at least the following devices:181 * Aten UC210T182 * ASIX AX88172183 * Billionton Systems, USB2AR184 * Billionton Systems, GUSB2AM-1G-B185 * Buffalo LUA-U2-KTX186 * Corega FEther USB2-TX187 * D-Link DUB-E100188 * Hawking UF200189 * Linksys USB200M190 * Netgear FA120191 * Sitecom LN-029192 * Sitecom LN-028193 * Intellinet USB 2.0 Ethernet194 * ST Lab USB 2.0 Ethernet195 * TrendNet TU2-ET100196 197 This driver creates an interface named "ethX", where X depends on198 what other networking devices you have in use.199 200config USB_NET_AX88179_178A201 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"202 depends on USB_USBNET203 select CRC32204 select PHYLIB205 default y206 help207 This option adds support for ASIX AX88179 based USB 3.0/2.0208 to Gigabit Ethernet adapters.209 210 This driver should work with at least the following devices:211 * ASIX AX88179212 * ASIX AX88178A213 * Sitcomm LN-032214 215 This driver creates an interface named "ethX", where X depends on216 what other networking devices you have in use.217 218config USB_NET_CDCETHER219 tristate "CDC Ethernet support (smart devices such as cable modems)"220 depends on USB_USBNET221 default y222 help223 This option supports devices conforming to the Communication Device224 Class (CDC) Ethernet Control Model, a specification that's easy to225 implement in device firmware. The CDC specifications are available226 from <http://www.usb.org/>.227 228 CDC Ethernet is an implementation option for DOCSIS cable modems229 that support USB connectivity, used for non-Microsoft USB hosts.230 The Linux-USB CDC Ethernet Gadget driver is an open implementation.231 This driver should work with at least the following devices:232 233 * Dell Wireless 5530 HSPA234 * Ericsson PipeRider (all variants)235 * Ericsson Mobile Broadband Module (all variants)236 * Motorola (DM100 and SB4100)237 * Broadcom Cable Modem (reference design)238 * Toshiba (PCX1100U and F3507g/F3607gw)239 * ...240 241 This driver creates an interface named "ethX", where X depends on242 what other networking devices you have in use. However, if the243 IEEE 802 "local assignment" bit is set in the address, a "usbX"244 name is used instead.245 246config USB_NET_CDC_EEM247 tristate "CDC EEM support"248 depends on USB_USBNET249 help250 This option supports devices conforming to the Communication Device251 Class (CDC) Ethernet Emulation Model, a specification that's easy to252 implement in device firmware. The CDC EEM specifications are available253 from <http://www.usb.org/>.254 255 This driver creates an interface named "ethX", where X depends on256 what other networking devices you have in use. However, if the257 IEEE 802 "local assignment" bit is set in the address, a "usbX"258 name is used instead.259 260config USB_NET_CDC_NCM261 tristate "CDC NCM support"262 depends on USB_USBNET263 select USB_NET_CDCETHER264 default y265 help266 This driver provides support for CDC NCM (Network Control Model267 Device USB Class Specification). The CDC NCM specification is268 available from <http://www.usb.org/>.269 270 Say "y" to link the driver statically, or "m" to build a271 dynamically linked module.272 273 This driver should work with at least the following devices:274 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)275 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)276 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)277 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)278 * Ericsson F5521gw Mobile Broadband Module279 280config USB_NET_HUAWEI_CDC_NCM281 tristate "Huawei NCM embedded AT channel support"282 depends on USB_USBNET283 select USB_WDM284 select USB_NET_CDC_NCM285 help286 This driver supports huawei-style NCM devices, that use NCM as a287 transport for other protocols, usually an embedded AT channel.288 Good examples are:289 * Huawei E3131290 * Huawei E3251291 292 To compile this driver as a module, choose M here: the module will be293 called huawei_cdc_ncm.ko.294 295config USB_NET_CDC_MBIM296 tristate "CDC MBIM support"297 depends on USB_USBNET298 select USB_WDM299 select USB_NET_CDC_NCM300 help301 This driver provides support for CDC MBIM (Mobile Broadband302 Interface Model) devices. The CDC MBIM specification is303 available from <http://www.usb.org/>.304 305 MBIM devices require configuration using the management306 protocol defined by the MBIM specification. This driver307 provides unfiltered access to the MBIM control channel308 through the associated /dev/cdc-wdmx character device.309 310 To compile this driver as a module, choose M here: the311 module will be called cdc_mbim.312 313config USB_NET_DM9601314 tristate "Davicom DM96xx based USB 10/100 ethernet devices"315 depends on USB_USBNET316 select CRC32317 help318 This option adds support for Davicom DM9601/DM9620/DM9621A319 based USB 10/100 Ethernet adapters.320 321config USB_NET_SR9700322 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"323 depends on USB_USBNET324 select CRC32325 help326 This option adds support for CoreChip-sz SR9700 based USB 1.1327 10/100 Ethernet adapters.328 329config USB_NET_SR9800330 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"331 depends on USB_USBNET332 select CRC32333 help334 Say Y if you want to use one of the following 100Mbps USB Ethernet335 device based on the CoreChip-sz SR9800 chip.336 337 This driver makes the adapter appear as a normal Ethernet interface,338 typically on eth0, if it is the only ethernet device, or perhaps on339 eth1, if you have a PCI or ISA ethernet card installed.340 341 To compile this driver as a module, choose M here: the342 module will be called sr9800.343 344config USB_NET_SMSC75XX345 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"346 depends on USB_USBNET347 select BITREVERSE348 select CRC16349 select CRC32350 help351 This option adds support for SMSC LAN75XX based USB 2.0352 Gigabit Ethernet adapters.353 354config USB_NET_SMSC95XX355 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"356 depends on USB_USBNET357 select PHYLIB358 select SMSC_PHY359 select BITREVERSE360 select CRC16361 select CRC32362 imply NET_SELFTESTS363 help364 This option adds support for SMSC LAN95XX based USB 2.0365 10/100 Ethernet adapters.366 367config USB_NET_GL620A368 tristate "GeneSys GL620USB-A based cables"369 depends on USB_USBNET370 help371 Choose this option if you're using a host-to-host cable,372 or PC2PC motherboard, with this chip.373 374 Note that the half-duplex "GL620USB" is not supported.375 376config USB_NET_NET1080377 tristate "NetChip 1080 based cables (Laplink, ...)"378 default y379 depends on USB_USBNET380 help381 Choose this option if you're using a host-to-host cable based382 on this design: one NetChip 1080 chip and supporting logic,383 optionally with LEDs that indicate traffic384 385config USB_NET_PLUSB386 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"387 # if the handshake/init/reset problems, from original 'plusb',388 # are ever resolved ... then remove "experimental"389 depends on USB_USBNET390 help391 Choose this option if you're using a host-to-host cable392 with one of these chips.393 394config USB_NET_MCS7830395 tristate "MosChip MCS7830 based Ethernet adapters"396 depends on USB_USBNET397 help398 Choose this option if you're using a 10/100 Ethernet USB2399 adapter based on the MosChip 7830 controller. This includes400 adapters marketed under the DeLOCK brand.401 402config USB_NET_RNDIS_HOST403 tristate "Host for RNDIS and ActiveSync devices"404 depends on USB_USBNET405 select USB_NET_CDCETHER406 help407 This option enables hosting "Remote NDIS" USB networking links,408 as encouraged by Microsoft (instead of CDC Ethernet!) for use in409 various devices that may only support this protocol. A variant410 of this protocol (with even less public documentation) seems to411 be at the root of Microsoft's "ActiveSync" too.412 413 Avoid using this protocol unless you have no better options.414 The protocol specification is incomplete, and is controlled by415 (and for) Microsoft; it isn't an "Open" ecosystem or market.416 417config USB_NET_CDC_SUBSET_ENABLE418 tristate419 depends on USB_NET_CDC_SUBSET420 421config USB_NET_CDC_SUBSET422 tristate "Simple USB Network Links (CDC Ethernet subset)"423 depends on USB_USBNET424 default y425 help426 This driver module supports USB network devices that can work427 without any device-specific information. Select it if you have428 one of these drivers.429 430 Note that while many USB host-to-host cables can work in this mode,431 that may mean not being able to talk to Win32 systems or more432 commonly not being able to handle certain events (like replugging433 the host on the other end) very well. Also, these devices will434 not generally have permanently assigned Ethernet addresses.435 436config USB_ALI_M5632437 bool "ALi M5632 based 'USB 2.0 Data Link' cables"438 depends on USB_NET_CDC_SUBSET439 select USB_NET_CDC_SUBSET_ENABLE440 help441 Choose this option if you're using a host-to-host cable442 based on this design, which supports USB 2.0 high speed.443 444config USB_AN2720445 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"446 depends on USB_NET_CDC_SUBSET447 select USB_NET_CDC_SUBSET_ENABLE448 help449 Choose this option if you're using a host-to-host cable450 based on this design. Note that AnchorChips is now a451 Cypress brand.452 453config USB_BELKIN454 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"455 depends on USB_NET_CDC_SUBSET456 select USB_NET_CDC_SUBSET_ENABLE457 default y458 help459 Choose this option if you're using a host-to-host cable460 based on this design: two NetChip 2890 chips and an Atmel461 microcontroller, with LEDs that indicate traffic.462 463config USB_ARMLINUX464 bool "Embedded ARM Linux links (iPaq, ...)"465 depends on USB_NET_CDC_SUBSET466 select USB_NET_CDC_SUBSET_ENABLE467 default y468 help469 Choose this option to support the "usb-eth" networking driver470 used by most of the ARM Linux community with device controllers471 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities472 in some PXA versions of the "blob" boot loader.473 474 Linux-based "Gumstix" PXA-25x based systems use this protocol475 to talk with other Linux systems.476 477 Although the ROMs shipped with Sharp Zaurus products use a478 different link level framing protocol, you can have them use479 this simpler protocol by installing a different kernel.480 481config USB_EPSON2888482 bool "Epson 2888 based firmware (DEVELOPMENT)"483 depends on USB_NET_CDC_SUBSET484 select USB_NET_CDC_SUBSET_ENABLE485 help486 Choose this option to support the usb networking links used487 by some sample firmware from Epson.488 489config USB_KC2190490 bool "KT Technology KC2190 based cables (InstaNet)"491 depends on USB_NET_CDC_SUBSET492 select USB_NET_CDC_SUBSET_ENABLE493 help494 Choose this option if you're using a host-to-host cable495 with one of these chips.496 497config USB_NET_ZAURUS498 tristate "Sharp Zaurus (stock ROMs) and compatible"499 depends on USB_USBNET500 select USB_NET_CDCETHER501 select CRC32502 default y503 help504 Choose this option to support the usb networking links used by505 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.506 This also supports some related device firmware, as used in some507 PDAs from Olympus and some cell phones from Motorola.508 509 If you install an alternate image, such as the Linux 2.6 based510 versions of OpenZaurus, you should no longer need to support this511 protocol. Only the "eth-fd" or "net_fd" drivers in these devices512 really need this non-conformant variant of CDC Ethernet (or in513 some cases CDC MDLM) protocol, not "g_ether".514 515config USB_NET_CX82310_ETH516 tristate "Conexant CX82310 USB ethernet port"517 depends on USB_USBNET518 help519 Choose this option if you're using a Conexant CX82310-based ADSL520 router with USB ethernet port. This driver is for routers only,521 it will not work with ADSL modems (use cxacru driver instead).522 523config USB_NET_KALMIA524 tristate "Samsung Kalmia based LTE USB modem"525 depends on USB_USBNET526 help527 Choose this option if you have a Samsung Kalmia based USB modem528 as Samsung GT-B3730.529 530 To compile this driver as a module, choose M here: the531 module will be called kalmia.532 533config USB_NET_QMI_WWAN534 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"535 depends on USB_USBNET536 select USB_WDM537 help538 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem539 (MDM) chipsets. Examples of such devices are540 * Huawei E392/E398541 542 This driver will only drive the ethernet part of the chips.543 The devices require additional configuration to be usable.544 Multiple management interfaces with linux drivers are545 available:546 547 * option: AT commands on /dev/ttyUSBx548 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx549 550 A modem manager with support for QMI is recommended.551 552 To compile this driver as a module, choose M here: the553 module will be called qmi_wwan.554 555config USB_HSO556 tristate "Option USB High Speed Mobile Devices"557 depends on USB && RFKILL && TTY558 default n559 help560 Choose this option if you have an Option HSDPA/HSUPA card.561 These cards support downlink speeds of 7.2Mbps or greater.562 563 To compile this driver as a module, choose M here: the564 module will be called hso.565 566config USB_NET_INT51X1567 tristate "Intellon PLC based usb adapter"568 depends on USB_USBNET569 help570 Choose this option if you're using a 14Mb USB-based PLC571 (Powerline Communications) solution with an Intellon572 INT51x1/INT5200 chip, like the "devolo dLan duo".573 574config USB_CDC_PHONET575 tristate "CDC Phonet support"576 depends on PHONET && USB_USBNET577 help578 Choose this option to support the Phonet interface to a Nokia579 cellular modem, as found on most Nokia handsets with the580 "PC suite" USB profile.581 582config USB_IPHETH583 tristate "Apple iPhone USB Ethernet driver"584 default n585 help586 Module used to share Internet connection (tethering) from your587 iPhone to your system.588 Note that you need a corresponding userspace library/program589 to pair your device with your system, for example usbmuxd590 <https://github.com/libimobiledevice/usbmuxd>.591 592config USB_SIERRA_NET593 tristate "USB-to-WWAN Driver for Sierra Wireless modems"594 depends on USB_USBNET595 help596 Choose this option if you have a Sierra Wireless USB-to-WWAN device.597 598 To compile this driver as a module, choose M here: the599 module will be called sierra_net.600 601config USB_VL600602 tristate "LG VL600 modem dongle"603 depends on USB_NET_CDCETHER && TTY604 select USB_ACM605 help606 Select this if you want to use an LG Electronics 4G/LTE usb modem607 called VL600. This driver only handles the ethernet608 interface exposed by the modem firmware. To establish a connection609 you will first need a userspace program that sends the right610 command to the modem through its CDC ACM port, and most611 likely also a DHCP client. See this thread about using the612 4G modem from Verizon:613 614 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17615 616config USB_NET_CH9200617 tristate "QingHeng CH9200 USB ethernet support"618 depends on USB_USBNET619 select MII620 help621 Choose this option if you have a USB ethernet adapter with a QinHeng622 CH9200 chipset.623 624 To compile this driver as a module, choose M here: the625 module will be called ch9200.626 627config USB_NET_AQC111628 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"629 depends on USB_USBNET630 select CRC32631 help632 This option adds support for Aquantia AQtion USB633 Ethernet adapters based on AQC111U/AQC112 chips.634 635 This driver should work with at least the following devices:636 * Aquantia AQtion USB to 5GbE637 638config USB_RTL8153_ECM639 tristate640 depends on USB_NET_CDCETHER && (USB_RTL8152 || USB_RTL8152=n)641 default y642 help643 This option supports ECM mode for RTL8153 ethernet adapter, when644 CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not645 supported by r8152 driver.646 647endif # USB_NET_DRIVERS648