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 help 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 105 Ethernet adapters. 106 107 To compile this driver as a module, choose M here: the 108 module will be called r8152. 109 110config USB_LAN78XX 111 tristate "Microchip LAN78XX Based USB Ethernet Adapters" 112 select MII 113 select PHYLIB 114 select MICROCHIP_PHY 115 select FIXED_PHY 116 help 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) 122 123 Proper PHY driver is required for LAN7801. 124 125 To compile this driver as a module, choose M here: the 126 module will be called lan78xx. 127 128config USB_USBNET 129 tristate "Multi-purpose USB Networking Framework" 130 select MII 131 help 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). 136 137 The USB host runs "usbnet", and the other end of the link might be: 138 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. 143 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). 148 149 - Network adapter hardware (like those for 10/100 Ethernet) which 150 uses this driver framework. 151 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. 156 157 For more information see <http://www.linux-usb.org/usbnet/>. 158 159 To compile this driver as a module, choose M here: the 160 module will be called usbnet. 161 162config USB_NET_AX8817X 163 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" 164 depends on USB_USBNET 165 select CRC32 166 select PHYLIB 167 default y 168 help 169 This option adds support for ASIX AX88xxx based USB 2.0 170 10/100 Ethernet adapters. 171 172 This driver should work with at least the following devices: 173 * Aten UC210T 174 * ASIX AX88172 175 * Billionton Systems, USB2AR 176 * Billionton Systems, GUSB2AM-1G-B 177 * Buffalo LUA-U2-KTX 178 * Corega FEther USB2-TX 179 * D-Link DUB-E100 180 * Hawking UF200 181 * Linksys USB200M 182 * Netgear FA120 183 * Sitecom LN-029 184 * Sitecom LN-028 185 * Intellinet USB 2.0 Ethernet 186 * ST Lab USB 2.0 Ethernet 187 * TrendNet TU2-ET100 188 189 This driver creates an interface named "ethX", where X depends on 190 what other networking devices you have in use. 191 192config USB_NET_AX88179_178A 193 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet" 194 depends on USB_USBNET 195 select CRC32 196 select PHYLIB 197 default y 198 help 199 This option adds support for ASIX AX88179 based USB 3.0/2.0 200 to Gigabit Ethernet adapters. 201 202 This driver should work with at least the following devices: 203 * ASIX AX88179 204 * ASIX AX88178A 205 * Sitcomm LN-032 206 207 This driver creates an interface named "ethX", where X depends on 208 what other networking devices you have in use. 209 210config USB_NET_CDCETHER 211 tristate "CDC Ethernet support (smart devices such as cable modems)" 212 depends on USB_USBNET 213 default y 214 help 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/>. 219 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: 224 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) 231 * ... 232 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. 237 238config USB_NET_CDC_EEM 239 tristate "CDC EEM support" 240 depends on USB_USBNET 241 help 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/>. 246 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. 251 252config USB_NET_CDC_NCM 253 tristate "CDC NCM support" 254 depends on USB_USBNET 255 select USB_NET_CDCETHER 256 default y 257 help 258 This driver provides support for CDC NCM (Network Control Model 259 Device USB Class Specification). The CDC NCM specification is 260 available from <http://www.usb.org/>. 261 262 Say "y" to link the driver statically, or "m" to build a 263 dynamically linked module. 264 265 This driver should work with at least the following devices: 266 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design) 267 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design) 268 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design) 269 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design) 270 * Ericsson F5521gw Mobile Broadband Module 271 272config USB_NET_HUAWEI_CDC_NCM 273 tristate "Huawei NCM embedded AT channel support" 274 depends on USB_USBNET 275 select USB_WDM 276 select USB_NET_CDC_NCM 277 help 278 This driver supports huawei-style NCM devices, that use NCM as a 279 transport for other protocols, usually an embedded AT channel. 280 Good examples are: 281 * Huawei E3131 282 * Huawei E3251 283 284 To compile this driver as a module, choose M here: the module will be 285 called huawei_cdc_ncm.ko. 286 287config USB_NET_CDC_MBIM 288 tristate "CDC MBIM support" 289 depends on USB_USBNET 290 select USB_WDM 291 select USB_NET_CDC_NCM 292 help 293 This driver provides support for CDC MBIM (Mobile Broadband 294 Interface Model) devices. The CDC MBIM specification is 295 available from <http://www.usb.org/>. 296 297 MBIM devices require configuration using the management 298 protocol defined by the MBIM specification. This driver 299 provides unfiltered access to the MBIM control channel 300 through the associated /dev/cdc-wdmx character device. 301 302 To compile this driver as a module, choose M here: the 303 module will be called cdc_mbim. 304 305config USB_NET_DM9601 306 tristate "Davicom DM96xx based USB 10/100 ethernet devices" 307 depends on USB_USBNET 308 select CRC32 309 help 310 This option adds support for Davicom DM9601/DM9620/DM9621A 311 based USB 10/100 Ethernet adapters. 312 313config USB_NET_SR9700 314 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices" 315 depends on USB_USBNET 316 select CRC32 317 help 318 This option adds support for CoreChip-sz SR9700 based USB 1.1 319 10/100 Ethernet adapters. 320 321config USB_NET_SR9800 322 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices" 323 depends on USB_USBNET 324 select CRC32 325 help 326 Say Y if you want to use one of the following 100Mbps USB Ethernet 327 device based on the CoreChip-sz SR9800 chip. 328 329 This driver makes the adapter appear as a normal Ethernet interface, 330 typically on eth0, if it is the only ethernet device, or perhaps on 331 eth1, if you have a PCI or ISA ethernet card installed. 332 333 To compile this driver as a module, choose M here: the 334 module will be called sr9800. 335 336config USB_NET_SMSC75XX 337 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices" 338 depends on USB_USBNET 339 select BITREVERSE 340 select CRC16 341 select CRC32 342 help 343 This option adds support for SMSC LAN75XX based USB 2.0 344 Gigabit Ethernet adapters. 345 346config USB_NET_SMSC95XX 347 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices" 348 depends on USB_USBNET 349 select BITREVERSE 350 select CRC16 351 select CRC32 352 help 353 This option adds support for SMSC LAN95XX based USB 2.0 354 10/100 Ethernet adapters. 355 356config USB_NET_GL620A 357 tristate "GeneSys GL620USB-A based cables" 358 depends on USB_USBNET 359 help 360 Choose this option if you're using a host-to-host cable, 361 or PC2PC motherboard, with this chip. 362 363 Note that the half-duplex "GL620USB" is not supported. 364 365config USB_NET_NET1080 366 tristate "NetChip 1080 based cables (Laplink, ...)" 367 default y 368 depends on USB_USBNET 369 help 370 Choose this option if you're using a host-to-host cable based 371 on this design: one NetChip 1080 chip and supporting logic, 372 optionally with LEDs that indicate traffic 373 374config USB_NET_PLUSB 375 tristate "Prolific PL-2301/2302/25A1/27A1 based cables" 376 # if the handshake/init/reset problems, from original 'plusb', 377 # are ever resolved ... then remove "experimental" 378 depends on USB_USBNET 379 help 380 Choose this option if you're using a host-to-host cable 381 with one of these chips. 382 383config USB_NET_MCS7830 384 tristate "MosChip MCS7830 based Ethernet adapters" 385 depends on USB_USBNET 386 help 387 Choose this option if you're using a 10/100 Ethernet USB2 388 adapter based on the MosChip 7830 controller. This includes 389 adapters marketed under the DeLOCK brand. 390 391config USB_NET_RNDIS_HOST 392 tristate "Host for RNDIS and ActiveSync devices" 393 depends on USB_USBNET 394 select USB_NET_CDCETHER 395 help 396 This option enables hosting "Remote NDIS" USB networking links, 397 as encouraged by Microsoft (instead of CDC Ethernet!) for use in 398 various devices that may only support this protocol. A variant 399 of this protocol (with even less public documentation) seems to 400 be at the root of Microsoft's "ActiveSync" too. 401 402 Avoid using this protocol unless you have no better options. 403 The protocol specification is incomplete, and is controlled by 404 (and for) Microsoft; it isn't an "Open" ecosystem or market. 405 406config USB_NET_CDC_SUBSET_ENABLE 407 tristate 408 depends on USB_NET_CDC_SUBSET 409 410config USB_NET_CDC_SUBSET 411 tristate "Simple USB Network Links (CDC Ethernet subset)" 412 depends on USB_USBNET 413 default y 414 help 415 This driver module supports USB network devices that can work 416 without any device-specific information. Select it if you have 417 one of these drivers. 418 419 Note that while many USB host-to-host cables can work in this mode, 420 that may mean not being able to talk to Win32 systems or more 421 commonly not being able to handle certain events (like replugging 422 the host on the other end) very well. Also, these devices will 423 not generally have permanently assigned Ethernet addresses. 424 425config USB_ALI_M5632 426 bool "ALi M5632 based 'USB 2.0 Data Link' cables" 427 depends on USB_NET_CDC_SUBSET 428 select USB_NET_CDC_SUBSET_ENABLE 429 help 430 Choose this option if you're using a host-to-host cable 431 based on this design, which supports USB 2.0 high speed. 432 433config USB_AN2720 434 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)" 435 depends on USB_NET_CDC_SUBSET 436 select USB_NET_CDC_SUBSET_ENABLE 437 help 438 Choose this option if you're using a host-to-host cable 439 based on this design. Note that AnchorChips is now a 440 Cypress brand. 441 442config USB_BELKIN 443 bool "eTEK based host-to-host cables (Advance, Belkin, ...)" 444 depends on USB_NET_CDC_SUBSET 445 select USB_NET_CDC_SUBSET_ENABLE 446 default y 447 help 448 Choose this option if you're using a host-to-host cable 449 based on this design: two NetChip 2890 chips and an Atmel 450 microcontroller, with LEDs that indicate traffic. 451 452config USB_ARMLINUX 453 bool "Embedded ARM Linux links (iPaq, ...)" 454 depends on USB_NET_CDC_SUBSET 455 select USB_NET_CDC_SUBSET_ENABLE 456 default y 457 help 458 Choose this option to support the "usb-eth" networking driver 459 used by most of the ARM Linux community with device controllers 460 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities 461 in some PXA versions of the "blob" boot loader. 462 463 Linux-based "Gumstix" PXA-25x based systems use this protocol 464 to talk with other Linux systems. 465 466 Although the ROMs shipped with Sharp Zaurus products use a 467 different link level framing protocol, you can have them use 468 this simpler protocol by installing a different kernel. 469 470config USB_EPSON2888 471 bool "Epson 2888 based firmware (DEVELOPMENT)" 472 depends on USB_NET_CDC_SUBSET 473 select USB_NET_CDC_SUBSET_ENABLE 474 help 475 Choose this option to support the usb networking links used 476 by some sample firmware from Epson. 477 478config USB_KC2190 479 bool "KT Technology KC2190 based cables (InstaNet)" 480 depends on USB_NET_CDC_SUBSET 481 select USB_NET_CDC_SUBSET_ENABLE 482 help 483 Choose this option if you're using a host-to-host cable 484 with one of these chips. 485 486config USB_NET_ZAURUS 487 tristate "Sharp Zaurus (stock ROMs) and compatible" 488 depends on USB_USBNET 489 select USB_NET_CDCETHER 490 select CRC32 491 default y 492 help 493 Choose this option to support the usb networking links used by 494 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. 495 This also supports some related device firmware, as used in some 496 PDAs from Olympus and some cell phones from Motorola. 497 498 If you install an alternate image, such as the Linux 2.6 based 499 versions of OpenZaurus, you should no longer need to support this 500 protocol. Only the "eth-fd" or "net_fd" drivers in these devices 501 really need this non-conformant variant of CDC Ethernet (or in 502 some cases CDC MDLM) protocol, not "g_ether". 503 504config USB_NET_CX82310_ETH 505 tristate "Conexant CX82310 USB ethernet port" 506 depends on USB_USBNET 507 help 508 Choose this option if you're using a Conexant CX82310-based ADSL 509 router with USB ethernet port. This driver is for routers only, 510 it will not work with ADSL modems (use cxacru driver instead). 511 512config USB_NET_KALMIA 513 tristate "Samsung Kalmia based LTE USB modem" 514 depends on USB_USBNET 515 help 516 Choose this option if you have a Samsung Kalmia based USB modem 517 as Samsung GT-B3730. 518 519 To compile this driver as a module, choose M here: the 520 module will be called kalmia. 521 522config USB_NET_QMI_WWAN 523 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems" 524 depends on USB_USBNET 525 select USB_WDM 526 help 527 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem 528 (MDM) chipsets. Examples of such devices are 529 * Huawei E392/E398 530 531 This driver will only drive the ethernet part of the chips. 532 The devices require additional configuration to be usable. 533 Multiple management interfaces with linux drivers are 534 available: 535 536 * option: AT commands on /dev/ttyUSBx 537 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx 538 539 A modem manager with support for QMI is recommended. 540 541 To compile this driver as a module, choose M here: the 542 module will be called qmi_wwan. 543 544config USB_HSO 545 tristate "Option USB High Speed Mobile Devices" 546 depends on USB && RFKILL && TTY 547 default n 548 help 549 Choose this option if you have an Option HSDPA/HSUPA card. 550 These cards support downlink speeds of 7.2Mbps or greater. 551 552 To compile this driver as a module, choose M here: the 553 module will be called hso. 554 555config USB_NET_INT51X1 556 tristate "Intellon PLC based usb adapter" 557 depends on USB_USBNET 558 help 559 Choose this option if you're using a 14Mb USB-based PLC 560 (Powerline Communications) solution with an Intellon 561 INT51x1/INT5200 chip, like the "devolo dLan duo". 562 563config USB_CDC_PHONET 564 tristate "CDC Phonet support" 565 depends on PHONET && USB_USBNET 566 help 567 Choose this option to support the Phonet interface to a Nokia 568 cellular modem, as found on most Nokia handsets with the 569 "PC suite" USB profile. 570 571config USB_IPHETH 572 tristate "Apple iPhone USB Ethernet driver" 573 default n 574 help 575 Module used to share Internet connection (tethering) from your 576 iPhone (Original, 3G and 3GS) to your system. 577 Note that you need userspace libraries and programs that are needed 578 to pair your device with your system and that understand the iPhone 579 protocol. 580 581 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver 582 583config USB_SIERRA_NET 584 tristate "USB-to-WWAN Driver for Sierra Wireless modems" 585 depends on USB_USBNET 586 help 587 Choose this option if you have a Sierra Wireless USB-to-WWAN device. 588 589 To compile this driver as a module, choose M here: the 590 module will be called sierra_net. 591 592config USB_VL600 593 tristate "LG VL600 modem dongle" 594 depends on USB_NET_CDCETHER && TTY 595 select USB_ACM 596 help 597 Select this if you want to use an LG Electronics 4G/LTE usb modem 598 called VL600. This driver only handles the ethernet 599 interface exposed by the modem firmware. To establish a connection 600 you will first need a userspace program that sends the right 601 command to the modem through its CDC ACM port, and most 602 likely also a DHCP client. See this thread about using the 603 4G modem from Verizon: 604 605 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17 606 607config USB_NET_CH9200 608 tristate "QingHeng CH9200 USB ethernet support" 609 depends on USB_USBNET 610 select MII 611 help 612 Choose this option if you have a USB ethernet adapter with a QinHeng 613 CH9200 chipset. 614 615 To compile this driver as a module, choose M here: the 616 module will be called ch9200. 617 618config USB_NET_AQC111 619 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support" 620 depends on USB_USBNET 621 select CRC32 622 help 623 This option adds support for Aquantia AQtion USB 624 Ethernet adapters based on AQC111U/AQC112 chips. 625 626 This driver should work with at least the following devices: 627 * Aquantia AQtion USB to 5GbE 628 629endif # USB_NET_DRIVERS 630