15b2fc499SJeff Garzik# 25b2fc499SJeff Garzik# USB Network devices configuration 35b2fc499SJeff Garzik# 41bb5a356SFrancois Romieucomment "Host-side USB support is needed for USB Network Adapter support" 51bb5a356SFrancois Romieu depends on !USB && NET 65b2fc499SJeff Garzik 71bb5a356SFrancois Romieumenuconfig USB_NET_DRIVERS 8269f8cb2SFrancois Romieu tristate "USB Network Adapters" 9269f8cb2SFrancois Romieu default USB if USB 105b2fc499SJeff Garzik depends on USB && NET 115b2fc499SJeff Garzik 121bb5a356SFrancois Romieuif USB_NET_DRIVERS 131bb5a356SFrancois Romieu 145b2fc499SJeff Garzikconfig USB_CATC 157d6bce7aSKees Cook tristate "USB CATC NetMate-based Ethernet device support" 165b2fc499SJeff Garzik select CRC32 175b2fc499SJeff Garzik ---help--- 185b2fc499SJeff Garzik Say Y if you want to use one of the following 10Mbps USB Ethernet 195b2fc499SJeff Garzik device based on the EL1210A chip. Supported devices are: 205b2fc499SJeff Garzik Belkin F5U011 215b2fc499SJeff Garzik Belkin F5U111 225b2fc499SJeff Garzik CATC NetMate 235b2fc499SJeff Garzik CATC NetMate II 245b2fc499SJeff Garzik smartBridges smartNIC 255b2fc499SJeff Garzik 265b2fc499SJeff Garzik This driver makes the adapter appear as a normal Ethernet interface, 275b2fc499SJeff Garzik typically on eth0, if it is the only ethernet device, or perhaps on 285b2fc499SJeff Garzik eth1, if you have a PCI or ISA ethernet card installed. 295b2fc499SJeff Garzik 305b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 315b2fc499SJeff Garzik module will be called catc. 325b2fc499SJeff Garzik 335b2fc499SJeff Garzikconfig USB_KAWETH 345b2fc499SJeff Garzik tristate "USB KLSI KL5USB101-based ethernet device support" 355b2fc499SJeff Garzik ---help--- 365b2fc499SJeff Garzik Say Y here if you want to use one of the following 10Mbps only 375b2fc499SJeff Garzik USB Ethernet adapters based on the KLSI KL5KUSB101B chipset: 385b2fc499SJeff Garzik 3Com 3C19250 395b2fc499SJeff Garzik ADS USB-10BT 405b2fc499SJeff Garzik ATEN USB Ethernet 415b2fc499SJeff Garzik ASANTE USB To Ethernet Adapter 425b2fc499SJeff Garzik AOX Endpoints USB Ethernet 435b2fc499SJeff Garzik Correga K.K. 445b2fc499SJeff Garzik D-Link DSB-650C and DU-E10 455b2fc499SJeff Garzik Entrega / Portgear E45 465b2fc499SJeff Garzik I-O DATA USB-ET/T 475b2fc499SJeff Garzik Jaton USB Ethernet Device Adapter 485b2fc499SJeff Garzik Kingston Technology USB Ethernet Adapter 495b2fc499SJeff Garzik Linksys USB10T 505b2fc499SJeff Garzik Mobility USB-Ethernet Adapter 515b2fc499SJeff Garzik NetGear EA-101 525b2fc499SJeff Garzik Peracom Enet and Enet2 535b2fc499SJeff Garzik Portsmith Express Ethernet Adapter 545b2fc499SJeff Garzik Shark Pocket Adapter 555b2fc499SJeff Garzik SMC 2202USB 565b2fc499SJeff Garzik Sony Vaio port extender 575b2fc499SJeff Garzik 585b2fc499SJeff Garzik This driver is likely to work with most 10Mbps only USB Ethernet 595b2fc499SJeff Garzik adapters, including some "no brand" devices. It does NOT work on 605b2fc499SJeff Garzik SmartBridges smartNIC or on Belkin F5U111 devices - you should use 615b2fc499SJeff Garzik the CATC NetMate driver for those. If you are not sure which one 625b2fc499SJeff Garzik you need, select both, and the correct one should be selected for 635b2fc499SJeff Garzik you. 645b2fc499SJeff Garzik 655b2fc499SJeff Garzik This driver makes the adapter appear as a normal Ethernet interface, 665b2fc499SJeff Garzik typically on eth0, if it is the only ethernet device, or perhaps on 675b2fc499SJeff Garzik eth1, if you have a PCI or ISA ethernet card installed. 685b2fc499SJeff Garzik 695b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 705b2fc499SJeff Garzik module will be called kaweth. 715b2fc499SJeff Garzik 725b2fc499SJeff Garzikconfig USB_PEGASUS 735b2fc499SJeff Garzik tristate "USB Pegasus/Pegasus-II based ethernet device support" 745b2fc499SJeff Garzik select MII 755b2fc499SJeff Garzik ---help--- 765b2fc499SJeff Garzik Say Y here if you know you have Pegasus or Pegasus-II based adapter. 77582fe6fbSCal Peake If in doubt then look at <file:drivers/net/usb/pegasus.h> for the 785b2fc499SJeff Garzik complete list of supported devices. 795b2fc499SJeff Garzik 805b2fc499SJeff Garzik If your particular adapter is not in the list and you are _sure_ it 815b2fc499SJeff Garzik is Pegasus or Pegasus II based then send me 825b2fc499SJeff Garzik <petkan@users.sourceforge.net> vendor and device IDs. 835b2fc499SJeff Garzik 845b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 855b2fc499SJeff Garzik module will be called pegasus. 865b2fc499SJeff Garzik 875b2fc499SJeff Garzikconfig USB_RTL8150 887d6bce7aSKees Cook tristate "USB RTL8150 based ethernet device support" 895b2fc499SJeff Garzik select MII 905b2fc499SJeff Garzik help 915b2fc499SJeff Garzik Say Y here if you have RTL8150 based usb-ethernet adapter. 925b2fc499SJeff Garzik Send me <petkan@users.sourceforge.net> any comments you may have. 935b2fc499SJeff Garzik You can also check for updates at <http://pegasus2.sourceforge.net/>. 945b2fc499SJeff Garzik 955b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 965b2fc499SJeff Garzik module will be called rtl8150. 975b2fc499SJeff Garzik 98ac718b69Shayeswangconfig USB_RTL8152 9944d942a9Shayeswang tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters" 100ac718b69Shayeswang select MII 101ac718b69Shayeswang help 102ac718b69Shayeswang This option adds support for Realtek RTL8152 based USB 2.0 10344d942a9Shayeswang 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000 10444d942a9Shayeswang Ethernet adapters. 105ac718b69Shayeswang 106ac718b69Shayeswang To compile this driver as a module, choose M here: the 107ac718b69Shayeswang module will be called r8152. 108ac718b69Shayeswang 1095b2fc499SJeff Garzikconfig USB_USBNET 1105b2fc499SJeff Garzik tristate "Multi-purpose USB Networking Framework" 1114aa92cd9SAdrian Bunk select MII 1125b2fc499SJeff Garzik ---help--- 1135b2fc499SJeff Garzik This driver supports several kinds of network links over USB, 1145b2fc499SJeff Garzik with "minidrivers" built around a common network driver core 1155b2fc499SJeff Garzik that supports deep queues for efficient transfers. (This gives 1165b2fc499SJeff Garzik better performance with small packets and at high speeds). 1175b2fc499SJeff Garzik 1185b2fc499SJeff Garzik The USB host runs "usbnet", and the other end of the link might be: 1195b2fc499SJeff Garzik 1205b2fc499SJeff Garzik - Another USB host, when using USB "network" or "data transfer" 1215b2fc499SJeff Garzik cables. These are often used to network laptops to PCs, like 1225b2fc499SJeff Garzik "Laplink" parallel cables or some motherboards. These rely 1235b2fc499SJeff Garzik on specialized chips from many suppliers. 1245b2fc499SJeff Garzik 1255b2fc499SJeff Garzik - An intelligent USB gadget, perhaps embedding a Linux system. 1265b2fc499SJeff Garzik These include PDAs running Linux (iPaq, Yopy, Zaurus, and 1275b2fc499SJeff Garzik others), and devices that interoperate using the standard 1285b2fc499SJeff Garzik CDC-Ethernet specification (including many cable modems). 1295b2fc499SJeff Garzik 1305b2fc499SJeff Garzik - Network adapter hardware (like those for 10/100 Ethernet) which 1315b2fc499SJeff Garzik uses this driver framework. 1325b2fc499SJeff Garzik 1335b2fc499SJeff Garzik The link will appear with a name like "usb0", when the link is 1345b2fc499SJeff Garzik a two-node link, or "eth0" for most CDC-Ethernet devices. Those 1355b2fc499SJeff Garzik two-node links are most easily managed with Ethernet Bridging 1365b2fc499SJeff Garzik (CONFIG_BRIDGE) instead of routing. 1375b2fc499SJeff Garzik 1385b2fc499SJeff Garzik For more information see <http://www.linux-usb.org/usbnet/>. 1395b2fc499SJeff Garzik 1405b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 1415b2fc499SJeff Garzik module will be called usbnet. 1425b2fc499SJeff Garzik 1435b2fc499SJeff Garzikconfig USB_NET_AX8817X 1445b2fc499SJeff Garzik tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" 145c6cbcad1SMike Frysinger depends on USB_USBNET 1465b2fc499SJeff Garzik select CRC32 14721502937SChristian Riesch select PHYLIB 1485b2fc499SJeff Garzik default y 1495b2fc499SJeff Garzik help 1505b2fc499SJeff Garzik This option adds support for ASIX AX88xxx based USB 2.0 1515b2fc499SJeff Garzik 10/100 Ethernet adapters. 1525b2fc499SJeff Garzik 1535b2fc499SJeff Garzik This driver should work with at least the following devices: 1545b2fc499SJeff Garzik * Aten UC210T 1555b2fc499SJeff Garzik * ASIX AX88172 1565b2fc499SJeff Garzik * Billionton Systems, USB2AR 1575b2fc499SJeff Garzik * Buffalo LUA-U2-KTX 1585b2fc499SJeff Garzik * Corega FEther USB2-TX 1595b2fc499SJeff Garzik * D-Link DUB-E100 1605b2fc499SJeff Garzik * Hawking UF200 1615b2fc499SJeff Garzik * Linksys USB200M 1625b2fc499SJeff Garzik * Netgear FA120 1635b2fc499SJeff Garzik * Sitecom LN-029 164*7488c3e3SLuca Ceresoli * Sitecom LN-028 1655b2fc499SJeff Garzik * Intellinet USB 2.0 Ethernet 1665b2fc499SJeff Garzik * ST Lab USB 2.0 Ethernet 1675b2fc499SJeff Garzik * TrendNet TU2-ET100 1685b2fc499SJeff Garzik 1695b2fc499SJeff Garzik This driver creates an interface named "ethX", where X depends on 1705b2fc499SJeff Garzik what other networking devices you have in use. 1715b2fc499SJeff Garzik 172e2ca90c2SFreddy Xinconfig USB_NET_AX88179_178A 173e2ca90c2SFreddy Xin tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet" 174e2ca90c2SFreddy Xin depends on USB_USBNET 175e2ca90c2SFreddy Xin select CRC32 176e2ca90c2SFreddy Xin select PHYLIB 177e2ca90c2SFreddy Xin default y 178e2ca90c2SFreddy Xin help 179e2ca90c2SFreddy Xin This option adds support for ASIX AX88179 based USB 3.0/2.0 180e2ca90c2SFreddy Xin to Gigabit Ethernet adapters. 181e2ca90c2SFreddy Xin 182e2ca90c2SFreddy Xin This driver should work with at least the following devices: 183e2ca90c2SFreddy Xin * ASIX AX88179 184e2ca90c2SFreddy Xin * ASIX AX88178A 185e2ca90c2SFreddy Xin * Sitcomm LN-032 186e2ca90c2SFreddy Xin 187e2ca90c2SFreddy Xin This driver creates an interface named "ethX", where X depends on 188e2ca90c2SFreddy Xin what other networking devices you have in use. 189e2ca90c2SFreddy Xin 1905b2fc499SJeff Garzikconfig USB_NET_CDCETHER 1915b2fc499SJeff Garzik tristate "CDC Ethernet support (smart devices such as cable modems)" 1925b2fc499SJeff Garzik depends on USB_USBNET 1935b2fc499SJeff Garzik default y 1945b2fc499SJeff Garzik help 1955b2fc499SJeff Garzik This option supports devices conforming to the Communication Device 1965b2fc499SJeff Garzik Class (CDC) Ethernet Control Model, a specification that's easy to 1975b2fc499SJeff Garzik implement in device firmware. The CDC specifications are available 1985b2fc499SJeff Garzik from <http://www.usb.org/>. 1995b2fc499SJeff Garzik 2005b2fc499SJeff Garzik CDC Ethernet is an implementation option for DOCSIS cable modems 2015b2fc499SJeff Garzik that support USB connectivity, used for non-Microsoft USB hosts. 2025b2fc499SJeff Garzik The Linux-USB CDC Ethernet Gadget driver is an open implementation. 2035b2fc499SJeff Garzik This driver should work with at least the following devices: 2045b2fc499SJeff Garzik 20568924920SJonas Sjöquist * Dell Wireless 5530 HSPA 2065b2fc499SJeff Garzik * Ericsson PipeRider (all variants) 20768924920SJonas Sjöquist * Ericsson Mobile Broadband Module (all variants) 2085b2fc499SJeff Garzik * Motorola (DM100 and SB4100) 2095b2fc499SJeff Garzik * Broadcom Cable Modem (reference design) 2103a19d56cSTorgny Johansson * Toshiba (PCX1100U and F3507g/F3607gw) 2115b2fc499SJeff Garzik * ... 2125b2fc499SJeff Garzik 2135b2fc499SJeff Garzik This driver creates an interface named "ethX", where X depends on 2145b2fc499SJeff Garzik what other networking devices you have in use. However, if the 2155b2fc499SJeff Garzik IEEE 802 "local assignment" bit is set in the address, a "usbX" 2165b2fc499SJeff Garzik name is used instead. 2175b2fc499SJeff Garzik 2189f722c09SOmar Laazimaniconfig USB_NET_CDC_EEM 2199f722c09SOmar Laazimani tristate "CDC EEM support" 2207d6bce7aSKees Cook depends on USB_USBNET 2219f722c09SOmar Laazimani help 2229f722c09SOmar Laazimani This option supports devices conforming to the Communication Device 2239f722c09SOmar Laazimani Class (CDC) Ethernet Emulation Model, a specification that's easy to 2249f722c09SOmar Laazimani implement in device firmware. The CDC EEM specifications are available 2259f722c09SOmar Laazimani from <http://www.usb.org/>. 2269f722c09SOmar Laazimani 2279f722c09SOmar Laazimani This driver creates an interface named "ethX", where X depends on 2289f722c09SOmar Laazimani what other networking devices you have in use. However, if the 2299f722c09SOmar Laazimani IEEE 802 "local assignment" bit is set in the address, a "usbX" 2309f722c09SOmar Laazimani name is used instead. 2319f722c09SOmar Laazimani 232900d495aSAlexey Orishkoconfig USB_NET_CDC_NCM 233900d495aSAlexey Orishko tristate "CDC NCM support" 234900d495aSAlexey Orishko depends on USB_USBNET 235900d495aSAlexey Orishko default y 236900d495aSAlexey Orishko help 237900d495aSAlexey Orishko This driver provides support for CDC NCM (Network Control Model 238900d495aSAlexey Orishko Device USB Class Specification). The CDC NCM specification is 239900d495aSAlexey Orishko available from <http://www.usb.org/>. 240900d495aSAlexey Orishko 241900d495aSAlexey Orishko Say "y" to link the driver statically, or "m" to build a 242900d495aSAlexey Orishko dynamically linked module. 243900d495aSAlexey Orishko 244900d495aSAlexey Orishko This driver should work with at least the following devices: 245900d495aSAlexey Orishko * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design) 246900d495aSAlexey Orishko * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design) 247900d495aSAlexey Orishko * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design) 248900d495aSAlexey Orishko * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design) 249900d495aSAlexey Orishko * Ericsson F5521gw Mobile Broadband Module 250900d495aSAlexey Orishko 25141c47d8cSEnrico Miosoconfig USB_NET_HUAWEI_CDC_NCM 25241c47d8cSEnrico Mioso tristate "Huawei NCM embedded AT channel support" 25341c47d8cSEnrico Mioso depends on USB_USBNET 25441c47d8cSEnrico Mioso select USB_WDM 25541c47d8cSEnrico Mioso select USB_NET_CDC_NCM 25641c47d8cSEnrico Mioso help 25741c47d8cSEnrico Mioso This driver supports huawei-style NCM devices, that use NCM as a 25841c47d8cSEnrico Mioso transport for other protocols, usually an embedded AT channel. 25941c47d8cSEnrico Mioso Good examples are: 26041c47d8cSEnrico Mioso * Huawei E3131 26141c47d8cSEnrico Mioso * Huawei E3251 26241c47d8cSEnrico Mioso 26341c47d8cSEnrico Mioso To compile this driver as a module, choose M here: the module will be 26441c47d8cSEnrico Mioso called huawei_cdc_ncm.ko. 26541c47d8cSEnrico Mioso 2669084ccf9SBjørn Morkconfig USB_NET_CDC_MBIM 2679084ccf9SBjørn Mork tristate "CDC MBIM support" 2689084ccf9SBjørn Mork depends on USB_USBNET 2699084ccf9SBjørn Mork select USB_WDM 2709084ccf9SBjørn Mork select USB_NET_CDC_NCM 2719084ccf9SBjørn Mork help 2729084ccf9SBjørn Mork This driver provides support for CDC MBIM (Mobile Broadband 2739084ccf9SBjørn Mork Interface Model) devices. The CDC MBIM specification is 2749084ccf9SBjørn Mork available from <http://www.usb.org/>. 2759084ccf9SBjørn Mork 2769084ccf9SBjørn Mork MBIM devices require configuration using the management 2779084ccf9SBjørn Mork protocol defined by the MBIM specification. This driver 2789084ccf9SBjørn Mork provides unfiltered access to the MBIM control channel 2799084ccf9SBjørn Mork through the associated /dev/cdc-wdmx character device. 2809084ccf9SBjørn Mork 2819084ccf9SBjørn Mork To compile this driver as a module, choose M here: the 2829084ccf9SBjørn Mork module will be called cdc_mbim. 2839084ccf9SBjørn Mork 2845b2fc499SJeff Garzikconfig USB_NET_DM9601 285cabd0e3aSPeter Korsgaard tristate "Davicom DM96xx based USB 10/100 ethernet devices" 2865b2fc499SJeff Garzik depends on USB_USBNET 2875b2fc499SJeff Garzik select CRC32 2885b2fc499SJeff Garzik help 289cabd0e3aSPeter Korsgaard This option adds support for Davicom DM9601/DM9620/DM9621A 290cabd0e3aSPeter Korsgaard based USB 10/100 Ethernet adapters. 2915b2fc499SJeff Garzik 292c9b37458SLiu Junliangconfig USB_NET_SR9700 293c9b37458SLiu Junliang tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices" 294c9b37458SLiu Junliang depends on USB_USBNET 295c9b37458SLiu Junliang select CRC32 296c9b37458SLiu Junliang help 297c9b37458SLiu Junliang This option adds support for CoreChip-sz SR9700 based USB 1.1 298c9b37458SLiu Junliang 10/100 Ethernet adapters. 299c9b37458SLiu Junliang 30019a38d8eSLiu Junliangconfig USB_NET_SR9800 30119a38d8eSLiu Junliang tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices" 30219a38d8eSLiu Junliang depends on USB_USBNET 30319a38d8eSLiu Junliang select CRC32 30419a38d8eSLiu Junliang ---help--- 30519a38d8eSLiu Junliang Say Y if you want to use one of the following 100Mbps USB Ethernet 30619a38d8eSLiu Junliang device based on the CoreChip-sz SR9800 chip. 30719a38d8eSLiu Junliang 30819a38d8eSLiu Junliang This driver makes the adapter appear as a normal Ethernet interface, 30919a38d8eSLiu Junliang typically on eth0, if it is the only ethernet device, or perhaps on 31019a38d8eSLiu Junliang eth1, if you have a PCI or ISA ethernet card installed. 31119a38d8eSLiu Junliang 31219a38d8eSLiu Junliang To compile this driver as a module, choose M here: the 31319a38d8eSLiu Junliang module will be called sr9800. 31419a38d8eSLiu Junliang 315d0cad871SSteve Glendinningconfig USB_NET_SMSC75XX 316d0cad871SSteve Glendinning tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices" 317d0cad871SSteve Glendinning depends on USB_USBNET 318899a391bSSteve Glendinning select BITREVERSE 319899a391bSSteve Glendinning select CRC16 320d0cad871SSteve Glendinning select CRC32 321d0cad871SSteve Glendinning help 3221e731cb9SRobert de Vries This option adds support for SMSC LAN75XX based USB 2.0 323d0cad871SSteve Glendinning Gigabit Ethernet adapters. 324d0cad871SSteve Glendinning 3252f7ca802SSteve Glendinningconfig USB_NET_SMSC95XX 3262f7ca802SSteve Glendinning tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices" 3272f7ca802SSteve Glendinning depends on USB_USBNET 328bbd9f9eeSSteve Glendinning select BITREVERSE 329bbd9f9eeSSteve Glendinning select CRC16 3302f7ca802SSteve Glendinning select CRC32 3312f7ca802SSteve Glendinning help 3322f7ca802SSteve Glendinning This option adds support for SMSC LAN95XX based USB 2.0 3332f7ca802SSteve Glendinning 10/100 Ethernet adapters. 3342f7ca802SSteve Glendinning 3355b2fc499SJeff Garzikconfig USB_NET_GL620A 3365b2fc499SJeff Garzik tristate "GeneSys GL620USB-A based cables" 3375b2fc499SJeff Garzik depends on USB_USBNET 3385b2fc499SJeff Garzik help 3395b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable, 3405b2fc499SJeff Garzik or PC2PC motherboard, with this chip. 3415b2fc499SJeff Garzik 3425b2fc499SJeff Garzik Note that the half-duplex "GL620USB" is not supported. 3435b2fc499SJeff Garzik 3445b2fc499SJeff Garzikconfig USB_NET_NET1080 3455b2fc499SJeff Garzik tristate "NetChip 1080 based cables (Laplink, ...)" 3465b2fc499SJeff Garzik default y 3475b2fc499SJeff Garzik depends on USB_USBNET 3485b2fc499SJeff Garzik help 3495b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable based 3505b2fc499SJeff Garzik on this design: one NetChip 1080 chip and supporting logic, 3515b2fc499SJeff Garzik optionally with LEDs that indicate traffic 3525b2fc499SJeff Garzik 3535b2fc499SJeff Garzikconfig USB_NET_PLUSB 354647da406Ssimon tristate "Prolific PL-2301/2302/25A1 based cables" 3555b2fc499SJeff Garzik # if the handshake/init/reset problems, from original 'plusb', 3565b2fc499SJeff Garzik # are ever resolved ... then remove "experimental" 3577d6bce7aSKees Cook depends on USB_USBNET 3585b2fc499SJeff Garzik help 3595b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 3605b2fc499SJeff Garzik with one of these chips. 3615b2fc499SJeff Garzik 3625b2fc499SJeff Garzikconfig USB_NET_MCS7830 3635b2fc499SJeff Garzik tristate "MosChip MCS7830 based Ethernet adapters" 3645b2fc499SJeff Garzik depends on USB_USBNET 3655b2fc499SJeff Garzik help 3665b2fc499SJeff Garzik Choose this option if you're using a 10/100 Ethernet USB2 3675b2fc499SJeff Garzik adapter based on the MosChip 7830 controller. This includes 3685b2fc499SJeff Garzik adapters marketed under the DeLOCK brand. 3695b2fc499SJeff Garzik 3705b2fc499SJeff Garzikconfig USB_NET_RNDIS_HOST 3717d6bce7aSKees Cook tristate "Host for RNDIS and ActiveSync devices" 3727d6bce7aSKees Cook depends on USB_USBNET 3735b2fc499SJeff Garzik select USB_NET_CDCETHER 3745b2fc499SJeff Garzik help 3755b2fc499SJeff Garzik This option enables hosting "Remote NDIS" USB networking links, 3765b2fc499SJeff Garzik as encouraged by Microsoft (instead of CDC Ethernet!) for use in 3775b2fc499SJeff Garzik various devices that may only support this protocol. A variant 3785b2fc499SJeff Garzik of this protocol (with even less public documentation) seems to 3795b2fc499SJeff Garzik be at the root of Microsoft's "ActiveSync" too. 3805b2fc499SJeff Garzik 3815b2fc499SJeff Garzik Avoid using this protocol unless you have no better options. 3825b2fc499SJeff Garzik The protocol specification is incomplete, and is controlled by 3835b2fc499SJeff Garzik (and for) Microsoft; it isn't an "Open" ecosystem or market. 3845b2fc499SJeff Garzik 3855b2fc499SJeff Garzikconfig USB_NET_CDC_SUBSET 3865b2fc499SJeff Garzik tristate "Simple USB Network Links (CDC Ethernet subset)" 3875b2fc499SJeff Garzik depends on USB_USBNET 3885b2fc499SJeff Garzik default y 3895b2fc499SJeff Garzik help 3905b2fc499SJeff Garzik This driver module supports USB network devices that can work 3915b2fc499SJeff Garzik without any device-specific information. Select it if you have 3925b2fc499SJeff Garzik one of these drivers. 3935b2fc499SJeff Garzik 3945b2fc499SJeff Garzik Note that while many USB host-to-host cables can work in this mode, 3955b2fc499SJeff Garzik that may mean not being able to talk to Win32 systems or more 3965b2fc499SJeff Garzik commonly not being able to handle certain events (like replugging 3975b2fc499SJeff Garzik the host on the other end) very well. Also, these devices will 3985b2fc499SJeff Garzik not generally have permanently assigned Ethernet addresses. 3995b2fc499SJeff Garzik 4005b2fc499SJeff Garzikconfig USB_ALI_M5632 4015b2fc499SJeff Garzik boolean "ALi M5632 based 'USB 2.0 Data Link' cables" 4025b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 4035b2fc499SJeff Garzik help 4045b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 4055b2fc499SJeff Garzik based on this design, which supports USB 2.0 high speed. 4065b2fc499SJeff Garzik 4075b2fc499SJeff Garzikconfig USB_AN2720 4085b2fc499SJeff Garzik boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)" 4095b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 4105b2fc499SJeff Garzik help 4115b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 4125b2fc499SJeff Garzik based on this design. Note that AnchorChips is now a 4135b2fc499SJeff Garzik Cypress brand. 4145b2fc499SJeff Garzik 4155b2fc499SJeff Garzikconfig USB_BELKIN 4165b2fc499SJeff Garzik boolean "eTEK based host-to-host cables (Advance, Belkin, ...)" 4175b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 4185b2fc499SJeff Garzik default y 4195b2fc499SJeff Garzik help 4205b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 4215b2fc499SJeff Garzik based on this design: two NetChip 2890 chips and an Atmel 4225b2fc499SJeff Garzik microcontroller, with LEDs that indicate traffic. 4235b2fc499SJeff Garzik 4245b2fc499SJeff Garzikconfig USB_ARMLINUX 4255b2fc499SJeff Garzik boolean "Embedded ARM Linux links (iPaq, ...)" 4265b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 4275b2fc499SJeff Garzik default y 4285b2fc499SJeff Garzik help 4295b2fc499SJeff Garzik Choose this option to support the "usb-eth" networking driver 4305b2fc499SJeff Garzik used by most of the ARM Linux community with device controllers 4315b2fc499SJeff Garzik such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities 4325b2fc499SJeff Garzik in some PXA versions of the "blob" boot loader. 4335b2fc499SJeff Garzik 4345b2fc499SJeff Garzik Linux-based "Gumstix" PXA-25x based systems use this protocol 4355b2fc499SJeff Garzik to talk with other Linux systems. 4365b2fc499SJeff Garzik 4375b2fc499SJeff Garzik Although the ROMs shipped with Sharp Zaurus products use a 4385b2fc499SJeff Garzik different link level framing protocol, you can have them use 4395b2fc499SJeff Garzik this simpler protocol by installing a different kernel. 4405b2fc499SJeff Garzik 4415b2fc499SJeff Garzikconfig USB_EPSON2888 4425b2fc499SJeff Garzik boolean "Epson 2888 based firmware (DEVELOPMENT)" 4435b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 4445b2fc499SJeff Garzik help 4455b2fc499SJeff Garzik Choose this option to support the usb networking links used 4465b2fc499SJeff Garzik by some sample firmware from Epson. 4475b2fc499SJeff Garzik 4485b2fc499SJeff Garzikconfig USB_KC2190 4495b2fc499SJeff Garzik boolean "KT Technology KC2190 based cables (InstaNet)" 4507d6bce7aSKees Cook depends on USB_NET_CDC_SUBSET 4515b2fc499SJeff Garzik help 452c0811987SSam Ravnborg Choose this option if you're using a host-to-host cable 453c0811987SSam Ravnborg with one of these chips. 4545b2fc499SJeff Garzik 4555b2fc499SJeff Garzikconfig USB_NET_ZAURUS 4565b2fc499SJeff Garzik tristate "Sharp Zaurus (stock ROMs) and compatible" 4575b2fc499SJeff Garzik depends on USB_USBNET 4585b2fc499SJeff Garzik select USB_NET_CDCETHER 4595b2fc499SJeff Garzik select CRC32 4605b2fc499SJeff Garzik default y 4615b2fc499SJeff Garzik help 4625b2fc499SJeff Garzik Choose this option to support the usb networking links used by 4635b2fc499SJeff Garzik Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. 4645b2fc499SJeff Garzik This also supports some related device firmware, as used in some 4655b2fc499SJeff Garzik PDAs from Olympus and some cell phones from Motorola. 4665b2fc499SJeff Garzik 4675b2fc499SJeff Garzik If you install an alternate image, such as the Linux 2.6 based 4685b2fc499SJeff Garzik versions of OpenZaurus, you should no longer need to support this 4695b2fc499SJeff Garzik protocol. Only the "eth-fd" or "net_fd" drivers in these devices 4705b2fc499SJeff Garzik really need this non-conformant variant of CDC Ethernet (or in 4715b2fc499SJeff Garzik some cases CDC MDLM) protocol, not "g_ether". 4725b2fc499SJeff Garzik 473cc28a20eSOndrej Zaryconfig USB_NET_CX82310_ETH 474cc28a20eSOndrej Zary tristate "Conexant CX82310 USB ethernet port" 475cc28a20eSOndrej Zary depends on USB_USBNET 476cc28a20eSOndrej Zary help 477cc28a20eSOndrej Zary Choose this option if you're using a Conexant CX82310-based ADSL 478cc28a20eSOndrej Zary router with USB ethernet port. This driver is for routers only, 479cc28a20eSOndrej Zary it will not work with ADSL modems (use cxacru driver instead). 480cc28a20eSOndrej Zary 481d4026123SMarius B. Kotsbakconfig USB_NET_KALMIA 482d4026123SMarius B. Kotsbak tristate "Samsung Kalmia based LTE USB modem" 483d4026123SMarius B. Kotsbak depends on USB_USBNET 484d4026123SMarius B. Kotsbak help 485d4026123SMarius B. Kotsbak Choose this option if you have a Samsung Kalmia based USB modem 486d4026123SMarius B. Kotsbak as Samsung GT-B3730. 487d4026123SMarius B. Kotsbak 488d4026123SMarius B. Kotsbak To compile this driver as a module, choose M here: the 489d4026123SMarius B. Kotsbak module will be called kalmia. 490d4026123SMarius B. Kotsbak 4919b28ecd6SBjørn Morkconfig USB_NET_QMI_WWAN 4929b28ecd6SBjørn Mork tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems" 4939b28ecd6SBjørn Mork depends on USB_USBNET 49474cba4a8SBjørn Mork select USB_WDM 4959b28ecd6SBjørn Mork help 4969b28ecd6SBjørn Mork Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem 4979b28ecd6SBjørn Mork (MDM) chipsets. Examples of such devices are 4989b28ecd6SBjørn Mork * Huawei E392/E398 4999b28ecd6SBjørn Mork 5009b28ecd6SBjørn Mork This driver will only drive the ethernet part of the chips. 5019b28ecd6SBjørn Mork The devices require additional configuration to be usable. 5029b28ecd6SBjørn Mork Multiple management interfaces with linux drivers are 5039b28ecd6SBjørn Mork available: 5049b28ecd6SBjørn Mork 5059b28ecd6SBjørn Mork * option: AT commands on /dev/ttyUSBx 5069b28ecd6SBjørn Mork * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx 5079b28ecd6SBjørn Mork 5089b28ecd6SBjørn Mork A modem manager with support for QMI is recommended. 5099b28ecd6SBjørn Mork 5109b28ecd6SBjørn Mork To compile this driver as a module, choose M here: the 5119b28ecd6SBjørn Mork module will be called qmi_wwan. 5129b28ecd6SBjørn Mork 51385a73b33SDavid Brownellconfig USB_HSO 51485a73b33SDavid Brownell tristate "Option USB High Speed Mobile Devices" 5154f73bc4dSJoe Millenbach depends on USB && RFKILL && TTY 51685a73b33SDavid Brownell default n 51785a73b33SDavid Brownell help 51885a73b33SDavid Brownell Choose this option if you have an Option HSDPA/HSUPA card. 51985a73b33SDavid Brownell These cards support downlink speeds of 7.2Mbps or greater. 52085a73b33SDavid Brownell 52185a73b33SDavid Brownell To compile this driver as a module, choose M here: the 52285a73b33SDavid Brownell module will be called hso. 5235b2fc499SJeff Garzik 5244510d7cbSPeter Holikconfig USB_NET_INT51X1 5254510d7cbSPeter Holik tristate "Intellon PLC based usb adapter" 5264510d7cbSPeter Holik depends on USB_USBNET 5274510d7cbSPeter Holik help 5284510d7cbSPeter Holik Choose this option if you're using a 14Mb USB-based PLC 5294510d7cbSPeter Holik (Powerline Communications) solution with an Intellon 5304510d7cbSPeter Holik INT51x1/INT5200 chip, like the "devolo dLan duo". 5314510d7cbSPeter Holik 53287cf6560SRémi Denis-Courmontconfig USB_CDC_PHONET 53387cf6560SRémi Denis-Courmont tristate "CDC Phonet support" 53487cf6560SRémi Denis-Courmont depends on PHONET 53587cf6560SRémi Denis-Courmont help 53687cf6560SRémi Denis-Courmont Choose this option to support the Phonet interface to a Nokia 53787cf6560SRémi Denis-Courmont cellular modem, as found on most Nokia handsets with the 53887cf6560SRémi Denis-Courmont "PC suite" USB profile. 53987cf6560SRémi Denis-Courmont 540a19259c3SDiego Giagioconfig USB_IPHETH 541a19259c3SDiego Giagio tristate "Apple iPhone USB Ethernet driver" 542a19259c3SDiego Giagio default n 543a19259c3SDiego Giagio ---help--- 544a19259c3SDiego Giagio Module used to share Internet connection (tethering) from your 545a19259c3SDiego Giagio iPhone (Original, 3G and 3GS) to your system. 546a19259c3SDiego Giagio Note that you need userspace libraries and programs that are needed 547a19259c3SDiego Giagio to pair your device with your system and that understand the iPhone 548a19259c3SDiego Giagio protocol. 549a19259c3SDiego Giagio 550a19259c3SDiego Giagio For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver 551a19259c3SDiego Giagio 552eb4fd8cdSElina Pashevaconfig USB_SIERRA_NET 553eb4fd8cdSElina Pasheva tristate "USB-to-WWAN Driver for Sierra Wireless modems" 554eb4fd8cdSElina Pasheva depends on USB_USBNET 555eb4fd8cdSElina Pasheva help 556eb4fd8cdSElina Pasheva Choose this option if you have a Sierra Wireless USB-to-WWAN device. 557eb4fd8cdSElina Pasheva 558eb4fd8cdSElina Pasheva To compile this driver as a module, choose M here: the 559eb4fd8cdSElina Pasheva module will be called sierra_net. 560eb4fd8cdSElina Pasheva 5617a635ea9SAndrzej Zaborowskiconfig USB_VL600 5627a635ea9SAndrzej Zaborowski tristate "LG VL600 modem dongle" 5634f73bc4dSJoe Millenbach depends on USB_NET_CDCETHER && TTY 5647a635ea9SAndrzej Zaborowski select USB_ACM 5657a635ea9SAndrzej Zaborowski help 5667a635ea9SAndrzej Zaborowski Select this if you want to use an LG Electronics 4G/LTE usb modem 5677a635ea9SAndrzej Zaborowski called VL600. This driver only handles the ethernet 5687a635ea9SAndrzej Zaborowski interface exposed by the modem firmware. To establish a connection 5697a635ea9SAndrzej Zaborowski you will first need a userspace program that sends the right 5707a635ea9SAndrzej Zaborowski command to the modem through its CDC ACM port, and most 5717a635ea9SAndrzej Zaborowski likely also a DHCP client. See this thread about using the 5727a635ea9SAndrzej Zaborowski 4G modem from Verizon: 5737a635ea9SAndrzej Zaborowski 5747a635ea9SAndrzej Zaborowski http://ubuntuforums.org/showpost.php?p=10589647&postcount=17 5757a635ea9SAndrzej Zaborowski 5761bb5a356SFrancois Romieuendif # USB_NET_DRIVERS 577