1# SPDX-License-Identifier: GPL-2.0-only 2# 3# USB Network devices configuration 4# 5comment "Host-side USB support is needed for USB Network Adapter support" 6 depends on !USB && NET 7 8menuconfig USB_NET_DRIVERS 9 tristate "USB Network Adapters" 10 default USB if USB 11 depends on USB && NET 12 13if USB_NET_DRIVERS 14 15config USB_CATC 16 tristate "USB CATC NetMate-based Ethernet device support" 17 select CRC32 18 help 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: 21 Belkin F5U011 22 Belkin F5U111 23 CATC NetMate 24 CATC NetMate II 25 smartBridges smartNIC 26 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. 30 31 To compile this driver as a module, choose M here: the 32 module will be called catc. 33 34config USB_KAWETH 35 tristate "USB KLSI KL5USB101-based ethernet device support" 36 help 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: 39 3Com 3C19250 40 ADS USB-10BT 41 ATEN USB Ethernet 42 ASANTE USB To Ethernet Adapter 43 AOX Endpoints USB Ethernet 44 Correga K.K. 45 D-Link DSB-650C and DU-E10 46 Entrega / Portgear E45 47 I-O DATA USB-ET/T 48 Jaton USB Ethernet Device Adapter 49 Kingston Technology USB Ethernet Adapter 50 Linksys USB10T 51 Mobility USB-Ethernet Adapter 52 NetGear EA-101 53 Peracom Enet and Enet2 54 Portsmith Express Ethernet Adapter 55 Shark Pocket Adapter 56 SMC 2202USB 57 Sony Vaio port extender 58 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 64 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 on 68 eth1, if you have a PCI or ISA ethernet card installed. 69 70 To compile this driver as a module, choose M here: the 71 module will be called kaweth. 72 73config USB_PEGASUS 74 tristate "USB Pegasus/Pegasus-II based ethernet device support" 75 select MII 76 help 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. 80 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. 84 85 To compile this driver as a module, choose M here: the 86 module will be called pegasus. 87 88config USB_RTL8150 89 tristate "USB RTL8150 based ethernet device support" 90 select MII 91 help 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/>. 95 96 To compile this driver as a module, choose M here: the 97 module will be called rtl8150. 98 99config USB_RTL8152 100 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters" 101 select MII 102 select PHYLIB 103 select CRC32 104 select CRYPTO_LIB_SHA256 105 help 106 This option adds support for Realtek RTL8152 based USB 2.0 107 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000 108 Ethernet adapters. 109 110 To compile this driver as a module, choose M here: the 111 module will be called r8152. 112 113config USB_LAN78XX 114 tristate "Microchip LAN78XX Based USB Ethernet Adapters" 115 select MII 116 select PHYLIB 117 select MICROCHIP_PHY 118 select FIXED_PHY 119 select CRC32 120 help 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) 126 127 Proper PHY driver is required for LAN7801. 128 129 To compile this driver as a module, choose M here: the 130 module will be called lan78xx. 131 132config USB_USBNET 133 tristate "Multi-purpose USB Networking Framework" 134 select MII 135 help 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). 140 141 The USB host runs "usbnet", and the other end of the link might be: 142 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. 147 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). 152 153 - Network adapter hardware (like those for 10/100 Ethernet) which 154 uses this driver framework. 155 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. 160 161 For more information see <http://www.linux-usb.org/usbnet/>. 162 163 To compile this driver as a module, choose M here: the 164 module will be called usbnet. 165 166config USB_NET_AX8817X 167 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" 168 depends on USB_USBNET 169 select CRC32 170 select PHYLINK 171 select AX88796B_PHY 172 imply NET_SELFTESTS 173 default y 174 help 175 This option adds support for ASIX AX88xxx based USB 2.0 176 10/100 Ethernet adapters. 177 178 This driver should work with at least the following devices: 179 * Aten UC210T 180 * ASIX AX88172 181 * Billionton Systems, USB2AR 182 * Billionton Systems, GUSB2AM-1G-B 183 * Buffalo LUA-U2-KTX 184 * Corega FEther USB2-TX 185 * D-Link DUB-E100 186 * Hawking UF200 187 * Linksys USB200M 188 * Netgear FA120 189 * Sitecom LN-029 190 * Sitecom LN-028 191 * Intellinet USB 2.0 Ethernet 192 * ST Lab USB 2.0 Ethernet 193 * TrendNet TU2-ET100 194 195 This driver creates an interface named "ethX", where X depends on 196 what other networking devices you have in use. 197 198config USB_NET_AX88179_178A 199 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet" 200 depends on USB_USBNET 201 select CRC32 202 select PHYLIB 203 default y 204 help 205 This option adds support for ASIX AX88179 based USB 3.0/2.0 206 to Gigabit Ethernet adapters. 207 208 This driver should work with at least the following devices: 209 * ASIX AX88179 210 * ASIX AX88178A 211 * Sitcomm LN-032 212 213 This driver creates an interface named "ethX", where X depends on 214 what other networking devices you have in use. 215 216config USB_NET_CDCETHER 217 tristate "CDC Ethernet support (smart devices such as cable modems)" 218 depends on USB_USBNET 219 default y 220 help 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/>. 225 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: 230 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) 237 * ... 238 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. 243 244config USB_NET_CDC_EEM 245 tristate "CDC EEM support" 246 depends on USB_USBNET 247 help 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/>. 252 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. 257 258config USB_NET_CDC_NCM 259 tristate "CDC NCM support" 260 depends on USB_USBNET 261 select USB_NET_CDCETHER 262 default y 263 help 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/>. 267 268 Say "y" to link the driver statically, or "m" to build a 269 dynamically linked module. 270 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 277 278config USB_NET_HUAWEI_CDC_NCM 279 tristate "Huawei NCM embedded AT channel support" 280 depends on USB_USBNET 281 select USB_WDM 282 select USB_NET_CDC_NCM 283 help 284 This driver supports huawei-style NCM devices, that use NCM as a 285 transport for other protocols, usually an embedded AT channel. 286 Good examples are: 287 * Huawei E3131 288 * Huawei E3251 289 290 To compile this driver as a module, choose M here: the module will be 291 called huawei_cdc_ncm.ko. 292 293config USB_NET_CDC_MBIM 294 tristate "CDC MBIM support" 295 depends on USB_USBNET 296 select USB_WDM 297 select USB_NET_CDC_NCM 298 help 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/>. 302 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. 307 308 To compile this driver as a module, choose M here: the 309 module will be called cdc_mbim. 310 311config USB_NET_DM9601 312 tristate "Davicom DM96xx based USB 10/100 ethernet devices" 313 depends on USB_USBNET 314 select CRC32 315 help 316 This option adds support for Davicom DM9601/DM9620/DM9621A 317 based USB 10/100 Ethernet adapters. 318 319config USB_NET_SR9700 320 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices" 321 depends on USB_USBNET 322 select CRC32 323 help 324 This option adds support for CoreChip-sz SR9700 based USB 1.1 325 10/100 Ethernet adapters. 326 327config USB_NET_SR9800 328 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices" 329 depends on USB_USBNET 330 select CRC32 331 help 332 Say Y if you want to use one of the following 100Mbps USB Ethernet 333 device based on the CoreChip-sz SR9800 chip. 334 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. 338 339 To compile this driver as a module, choose M here: the 340 module will be called sr9800. 341 342config USB_NET_SMSC75XX 343 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices" 344 depends on USB_USBNET 345 select BITREVERSE 346 select CRC16 347 select CRC32 348 help 349 This option adds support for SMSC LAN75XX based USB 2.0 350 Gigabit Ethernet adapters. 351 352config USB_NET_SMSC95XX 353 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices" 354 depends on USB_USBNET 355 select PHYLIB 356 select SMSC_PHY 357 select BITREVERSE 358 select CRC16 359 select CRC32 360 imply NET_SELFTESTS 361 help 362 This option adds support for SMSC LAN95XX based USB 2.0 363 10/100 Ethernet adapters. 364 365config USB_NET_GL620A 366 tristate "GeneSys GL620USB-A based cables" 367 depends on USB_USBNET 368 help 369 Choose this option if you're using a host-to-host cable, 370 or PC2PC motherboard, with this chip. 371 372 Note that the half-duplex "GL620USB" is not supported. 373 374config USB_NET_NET1080 375 tristate "NetChip 1080 based cables (Laplink, ...)" 376 default y 377 depends on USB_USBNET 378 help 379 Choose this option if you're using a host-to-host cable based 380 on this design: one NetChip 1080 chip and supporting logic, 381 optionally with LEDs that indicate traffic 382 383config USB_NET_PLUSB 384 tristate "Prolific PL-2301/2302/25A1/27A1 based cables" 385 # if the handshake/init/reset problems, from original 'plusb', 386 # are ever resolved ... then remove "experimental" 387 depends on USB_USBNET 388 help 389 Choose this option if you're using a host-to-host cable 390 with one of these chips. 391 392config USB_NET_MCS7830 393 tristate "MosChip MCS7830 based Ethernet adapters" 394 depends on USB_USBNET 395 help 396 Choose this option if you're using a 10/100 Ethernet USB2 397 adapter based on the MosChip 7830 controller. This includes 398 adapters marketed under the DeLOCK brand. 399 400config USB_NET_RNDIS_HOST 401 tristate "Host for RNDIS and ActiveSync devices" 402 depends on USB_USBNET 403 select USB_NET_CDCETHER 404 help 405 This option enables hosting "Remote NDIS" USB networking links, 406 as encouraged by Microsoft (instead of CDC Ethernet!) for use in 407 various devices that may only support this protocol. A variant 408 of this protocol (with even less public documentation) seems to 409 be at the root of Microsoft's "ActiveSync" too. 410 411 Avoid using this protocol unless you have no better options. 412 The protocol specification is incomplete, and is controlled by 413 (and for) Microsoft; it isn't an "Open" ecosystem or market. 414 415config USB_NET_CDC_SUBSET_ENABLE 416 tristate 417 depends on USB_NET_CDC_SUBSET 418 419config USB_NET_CDC_SUBSET 420 tristate "Simple USB Network Links (CDC Ethernet subset)" 421 depends on USB_USBNET 422 default y 423 help 424 This driver module supports USB network devices that can work 425 without any device-specific information. Select it if you have 426 one of these drivers. 427 428 Note that while many USB host-to-host cables can work in this mode, 429 that may mean not being able to talk to Win32 systems or more 430 commonly not being able to handle certain events (like replugging 431 the host on the other end) very well. Also, these devices will 432 not generally have permanently assigned Ethernet addresses. 433 434config USB_ALI_M5632 435 bool "ALi M5632 based 'USB 2.0 Data Link' cables" 436 depends on USB_NET_CDC_SUBSET 437 select USB_NET_CDC_SUBSET_ENABLE 438 help 439 Choose this option if you're using a host-to-host cable 440 based on this design, which supports USB 2.0 high speed. 441 442config USB_AN2720 443 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)" 444 depends on USB_NET_CDC_SUBSET 445 select USB_NET_CDC_SUBSET_ENABLE 446 help 447 Choose this option if you're using a host-to-host cable 448 based on this design. Note that AnchorChips is now a 449 Cypress brand. 450 451config USB_BELKIN 452 bool "eTEK based host-to-host cables (Advance, Belkin, ...)" 453 depends on USB_NET_CDC_SUBSET 454 select USB_NET_CDC_SUBSET_ENABLE 455 default y 456 help 457 Choose this option if you're using a host-to-host cable 458 based on this design: two NetChip 2890 chips and an Atmel 459 microcontroller, with LEDs that indicate traffic. 460 461config USB_ARMLINUX 462 bool "Embedded ARM Linux links (iPaq, ...)" 463 depends on USB_NET_CDC_SUBSET 464 select USB_NET_CDC_SUBSET_ENABLE 465 default y 466 help 467 Choose this option to support the "usb-eth" networking driver 468 used by most of the ARM Linux community with device controllers 469 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities 470 in some PXA versions of the "blob" boot loader. 471 472 Linux-based "Gumstix" PXA-25x based systems use this protocol 473 to talk with other Linux systems. 474 475 Although the ROMs shipped with Sharp Zaurus products use a 476 different link level framing protocol, you can have them use 477 this simpler protocol by installing a different kernel. 478 479config USB_EPSON2888 480 bool "Epson 2888 based firmware (DEVELOPMENT)" 481 depends on USB_NET_CDC_SUBSET 482 select USB_NET_CDC_SUBSET_ENABLE 483 help 484 Choose this option to support the usb networking links used 485 by some sample firmware from Epson. 486 487config USB_KC2190 488 bool "KT Technology KC2190 based cables (InstaNet)" 489 depends on USB_NET_CDC_SUBSET 490 select USB_NET_CDC_SUBSET_ENABLE 491 help 492 Choose this option if you're using a host-to-host cable 493 with one of these chips. 494 495config USB_NET_ZAURUS 496 tristate "Sharp Zaurus (stock ROMs) and compatible" 497 depends on USB_USBNET 498 select USB_NET_CDCETHER 499 select CRC32 500 default y 501 help 502 Choose this option to support the usb networking links used by 503 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. 504 This also supports some related device firmware, as used in some 505 PDAs from Olympus and some cell phones from Motorola. 506 507 If you install an alternate image, such as the Linux 2.6 based 508 versions of OpenZaurus, you should no longer need to support this 509 protocol. Only the "eth-fd" or "net_fd" drivers in these devices 510 really need this non-conformant variant of CDC Ethernet (or in 511 some cases CDC MDLM) protocol, not "g_ether". 512 513config USB_NET_CX82310_ETH 514 tristate "Conexant CX82310 USB ethernet port" 515 depends on USB_USBNET 516 help 517 Choose this option if you're using a Conexant CX82310-based ADSL 518 router with USB ethernet port. This driver is for routers only, 519 it will not work with ADSL modems (use cxacru driver instead). 520 521config USB_NET_KALMIA 522 tristate "Samsung Kalmia based LTE USB modem" 523 depends on USB_USBNET 524 help 525 Choose this option if you have a Samsung Kalmia based USB modem 526 as Samsung GT-B3730. 527 528 To compile this driver as a module, choose M here: the 529 module will be called kalmia. 530 531config USB_NET_QMI_WWAN 532 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems" 533 depends on USB_USBNET 534 select USB_WDM 535 help 536 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem 537 (MDM) chipsets. Examples of such devices are 538 * Huawei E392/E398 539 540 This driver will only drive the ethernet part of the chips. 541 The devices require additional configuration to be usable. 542 Multiple management interfaces with linux drivers are 543 available: 544 545 * option: AT commands on /dev/ttyUSBx 546 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx 547 548 A modem manager with support for QMI is recommended. 549 550 To compile this driver as a module, choose M here: the 551 module will be called qmi_wwan. 552 553config USB_HSO 554 tristate "Option USB High Speed Mobile Devices" 555 depends on USB && RFKILL && TTY 556 default n 557 help 558 Choose this option if you have an Option HSDPA/HSUPA card. 559 These cards support downlink speeds of 7.2Mbps or greater. 560 561 To compile this driver as a module, choose M here: the 562 module will be called hso. 563 564config USB_NET_INT51X1 565 tristate "Intellon PLC based usb adapter" 566 depends on USB_USBNET 567 help 568 Choose this option if you're using a 14Mb USB-based PLC 569 (Powerline Communications) solution with an Intellon 570 INT51x1/INT5200 chip, like the "devolo dLan duo". 571 572config USB_CDC_PHONET 573 tristate "CDC Phonet support" 574 depends on PHONET && USB_USBNET 575 help 576 Choose this option to support the Phonet interface to a Nokia 577 cellular modem, as found on most Nokia handsets with the 578 "PC suite" USB profile. 579 580config USB_IPHETH 581 tristate "Apple iPhone USB Ethernet driver" 582 default n 583 help 584 Module used to share Internet connection (tethering) from your 585 iPhone to your system. 586 Note that you need a corresponding userspace library/program 587 to pair your device with your system, for example usbmuxd 588 <https://github.com/libimobiledevice/usbmuxd>. 589 590config USB_SIERRA_NET 591 tristate "USB-to-WWAN Driver for Sierra Wireless modems" 592 depends on USB_USBNET 593 help 594 Choose this option if you have a Sierra Wireless USB-to-WWAN device. 595 596 To compile this driver as a module, choose M here: the 597 module will be called sierra_net. 598 599config USB_VL600 600 tristate "LG VL600 modem dongle" 601 depends on USB_NET_CDCETHER && TTY 602 select USB_ACM 603 help 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: 611 612 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17 613 614config USB_NET_CH9200 615 tristate "QingHeng CH9200 USB ethernet support" 616 depends on USB_USBNET 617 select MII 618 help 619 Choose this option if you have a USB ethernet adapter with a QinHeng 620 CH9200 chipset. 621 622 To compile this driver as a module, choose M here: the 623 module will be called ch9200. 624 625config USB_NET_AQC111 626 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support" 627 depends on USB_USBNET 628 select CRC32 629 help 630 This option adds support for Aquantia AQtion USB 631 Ethernet adapters based on AQC111U/AQC112 chips. 632 633 This driver should work with at least the following devices: 634 * Aquantia AQtion USB to 5GbE 635 636config USB_RTL8153_ECM 637 tristate 638 depends on USB_NET_CDCETHER && (USB_RTL8152 || USB_RTL8152=n) 639 default y 640 help 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. 644 645endif # USB_NET_DRIVERS 646