15b2fc499SJeff Garzik# 25b2fc499SJeff Garzik# USB Network devices configuration 35b2fc499SJeff Garzik# 45b2fc499SJeff Garzikcomment "Networking support is needed for USB Network Adapter support" 55b2fc499SJeff Garzik depends on USB && !NET 65b2fc499SJeff Garzik 75b2fc499SJeff Garzikmenu "USB Network Adapters" 85b2fc499SJeff Garzik depends on USB && NET 95b2fc499SJeff Garzik 105b2fc499SJeff Garzikconfig USB_CATC 115b2fc499SJeff Garzik tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)" 125b2fc499SJeff Garzik depends on EXPERIMENTAL 135b2fc499SJeff Garzik select CRC32 145b2fc499SJeff Garzik ---help--- 155b2fc499SJeff Garzik Say Y if you want to use one of the following 10Mbps USB Ethernet 165b2fc499SJeff Garzik device based on the EL1210A chip. Supported devices are: 175b2fc499SJeff Garzik Belkin F5U011 185b2fc499SJeff Garzik Belkin F5U111 195b2fc499SJeff Garzik CATC NetMate 205b2fc499SJeff Garzik CATC NetMate II 215b2fc499SJeff Garzik smartBridges smartNIC 225b2fc499SJeff Garzik 235b2fc499SJeff Garzik This driver makes the adapter appear as a normal Ethernet interface, 245b2fc499SJeff Garzik typically on eth0, if it is the only ethernet device, or perhaps on 255b2fc499SJeff Garzik eth1, if you have a PCI or ISA ethernet card installed. 265b2fc499SJeff Garzik 275b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 285b2fc499SJeff Garzik module will be called catc. 295b2fc499SJeff Garzik 305b2fc499SJeff Garzikconfig USB_KAWETH 315b2fc499SJeff Garzik tristate "USB KLSI KL5USB101-based ethernet device support" 325b2fc499SJeff Garzik ---help--- 335b2fc499SJeff Garzik Say Y here if you want to use one of the following 10Mbps only 345b2fc499SJeff Garzik USB Ethernet adapters based on the KLSI KL5KUSB101B chipset: 355b2fc499SJeff Garzik 3Com 3C19250 365b2fc499SJeff Garzik ADS USB-10BT 375b2fc499SJeff Garzik ATEN USB Ethernet 385b2fc499SJeff Garzik ASANTE USB To Ethernet Adapter 395b2fc499SJeff Garzik AOX Endpoints USB Ethernet 405b2fc499SJeff Garzik Correga K.K. 415b2fc499SJeff Garzik D-Link DSB-650C and DU-E10 425b2fc499SJeff Garzik Entrega / Portgear E45 435b2fc499SJeff Garzik I-O DATA USB-ET/T 445b2fc499SJeff Garzik Jaton USB Ethernet Device Adapter 455b2fc499SJeff Garzik Kingston Technology USB Ethernet Adapter 465b2fc499SJeff Garzik Linksys USB10T 475b2fc499SJeff Garzik Mobility USB-Ethernet Adapter 485b2fc499SJeff Garzik NetGear EA-101 495b2fc499SJeff Garzik Peracom Enet and Enet2 505b2fc499SJeff Garzik Portsmith Express Ethernet Adapter 515b2fc499SJeff Garzik Shark Pocket Adapter 525b2fc499SJeff Garzik SMC 2202USB 535b2fc499SJeff Garzik Sony Vaio port extender 545b2fc499SJeff Garzik 555b2fc499SJeff Garzik This driver is likely to work with most 10Mbps only USB Ethernet 565b2fc499SJeff Garzik adapters, including some "no brand" devices. It does NOT work on 575b2fc499SJeff Garzik SmartBridges smartNIC or on Belkin F5U111 devices - you should use 585b2fc499SJeff Garzik the CATC NetMate driver for those. If you are not sure which one 595b2fc499SJeff Garzik you need, select both, and the correct one should be selected for 605b2fc499SJeff Garzik you. 615b2fc499SJeff Garzik 625b2fc499SJeff Garzik This driver makes the adapter appear as a normal Ethernet interface, 635b2fc499SJeff Garzik typically on eth0, if it is the only ethernet device, or perhaps on 645b2fc499SJeff Garzik eth1, if you have a PCI or ISA ethernet card installed. 655b2fc499SJeff Garzik 665b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 675b2fc499SJeff Garzik module will be called kaweth. 685b2fc499SJeff Garzik 695b2fc499SJeff Garzikconfig USB_PEGASUS 705b2fc499SJeff Garzik tristate "USB Pegasus/Pegasus-II based ethernet device support" 71aaba215cSJeff Kirsher select NET_CORE 725b2fc499SJeff Garzik select MII 735b2fc499SJeff Garzik ---help--- 745b2fc499SJeff Garzik Say Y here if you know you have Pegasus or Pegasus-II based adapter. 75582fe6fbSCal Peake If in doubt then look at <file:drivers/net/usb/pegasus.h> for the 765b2fc499SJeff Garzik complete list of supported devices. 775b2fc499SJeff Garzik 785b2fc499SJeff Garzik If your particular adapter is not in the list and you are _sure_ it 795b2fc499SJeff Garzik is Pegasus or Pegasus II based then send me 805b2fc499SJeff Garzik <petkan@users.sourceforge.net> vendor and device IDs. 815b2fc499SJeff Garzik 825b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 835b2fc499SJeff Garzik module will be called pegasus. 845b2fc499SJeff Garzik 855b2fc499SJeff Garzikconfig USB_RTL8150 865b2fc499SJeff Garzik tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)" 875b2fc499SJeff Garzik depends on EXPERIMENTAL 88aaba215cSJeff Kirsher select NET_CORE 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 985b2fc499SJeff Garzikconfig USB_USBNET 995b2fc499SJeff Garzik tristate "Multi-purpose USB Networking Framework" 100aaba215cSJeff Kirsher select NET_CORE 1014aa92cd9SAdrian Bunk select MII 1025b2fc499SJeff Garzik ---help--- 1035b2fc499SJeff Garzik This driver supports several kinds of network links over USB, 1045b2fc499SJeff Garzik with "minidrivers" built around a common network driver core 1055b2fc499SJeff Garzik that supports deep queues for efficient transfers. (This gives 1065b2fc499SJeff Garzik better performance with small packets and at high speeds). 1075b2fc499SJeff Garzik 1085b2fc499SJeff Garzik The USB host runs "usbnet", and the other end of the link might be: 1095b2fc499SJeff Garzik 1105b2fc499SJeff Garzik - Another USB host, when using USB "network" or "data transfer" 1115b2fc499SJeff Garzik cables. These are often used to network laptops to PCs, like 1125b2fc499SJeff Garzik "Laplink" parallel cables or some motherboards. These rely 1135b2fc499SJeff Garzik on specialized chips from many suppliers. 1145b2fc499SJeff Garzik 1155b2fc499SJeff Garzik - An intelligent USB gadget, perhaps embedding a Linux system. 1165b2fc499SJeff Garzik These include PDAs running Linux (iPaq, Yopy, Zaurus, and 1175b2fc499SJeff Garzik others), and devices that interoperate using the standard 1185b2fc499SJeff Garzik CDC-Ethernet specification (including many cable modems). 1195b2fc499SJeff Garzik 1205b2fc499SJeff Garzik - Network adapter hardware (like those for 10/100 Ethernet) which 1215b2fc499SJeff Garzik uses this driver framework. 1225b2fc499SJeff Garzik 1235b2fc499SJeff Garzik The link will appear with a name like "usb0", when the link is 1245b2fc499SJeff Garzik a two-node link, or "eth0" for most CDC-Ethernet devices. Those 1255b2fc499SJeff Garzik two-node links are most easily managed with Ethernet Bridging 1265b2fc499SJeff Garzik (CONFIG_BRIDGE) instead of routing. 1275b2fc499SJeff Garzik 1285b2fc499SJeff Garzik For more information see <http://www.linux-usb.org/usbnet/>. 1295b2fc499SJeff Garzik 1305b2fc499SJeff Garzik To compile this driver as a module, choose M here: the 1315b2fc499SJeff Garzik module will be called usbnet. 1325b2fc499SJeff Garzik 1335b2fc499SJeff Garzikconfig USB_NET_AX8817X 1345b2fc499SJeff Garzik tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" 135c6cbcad1SMike Frysinger depends on USB_USBNET 1365b2fc499SJeff Garzik select CRC32 13721502937SChristian Riesch select PHYLIB 1385b2fc499SJeff Garzik default y 1395b2fc499SJeff Garzik help 1405b2fc499SJeff Garzik This option adds support for ASIX AX88xxx based USB 2.0 1415b2fc499SJeff Garzik 10/100 Ethernet adapters. 1425b2fc499SJeff Garzik 1435b2fc499SJeff Garzik This driver should work with at least the following devices: 1445b2fc499SJeff Garzik * Aten UC210T 1455b2fc499SJeff Garzik * ASIX AX88172 1465b2fc499SJeff Garzik * Billionton Systems, USB2AR 1475b2fc499SJeff Garzik * Buffalo LUA-U2-KTX 1485b2fc499SJeff Garzik * Corega FEther USB2-TX 1495b2fc499SJeff Garzik * D-Link DUB-E100 1505b2fc499SJeff Garzik * Hawking UF200 1515b2fc499SJeff Garzik * Linksys USB200M 1525b2fc499SJeff Garzik * Netgear FA120 1535b2fc499SJeff Garzik * Sitecom LN-029 1545b2fc499SJeff Garzik * Intellinet USB 2.0 Ethernet 1555b2fc499SJeff Garzik * ST Lab USB 2.0 Ethernet 1565b2fc499SJeff Garzik * TrendNet TU2-ET100 1575b2fc499SJeff Garzik 1585b2fc499SJeff Garzik This driver creates an interface named "ethX", where X depends on 1595b2fc499SJeff Garzik what other networking devices you have in use. 1605b2fc499SJeff Garzik 1615b2fc499SJeff Garzikconfig USB_NET_CDCETHER 1625b2fc499SJeff Garzik tristate "CDC Ethernet support (smart devices such as cable modems)" 1635b2fc499SJeff Garzik depends on USB_USBNET 1645b2fc499SJeff Garzik default y 1655b2fc499SJeff Garzik help 1665b2fc499SJeff Garzik This option supports devices conforming to the Communication Device 1675b2fc499SJeff Garzik Class (CDC) Ethernet Control Model, a specification that's easy to 1685b2fc499SJeff Garzik implement in device firmware. The CDC specifications are available 1695b2fc499SJeff Garzik from <http://www.usb.org/>. 1705b2fc499SJeff Garzik 1715b2fc499SJeff Garzik CDC Ethernet is an implementation option for DOCSIS cable modems 1725b2fc499SJeff Garzik that support USB connectivity, used for non-Microsoft USB hosts. 1735b2fc499SJeff Garzik The Linux-USB CDC Ethernet Gadget driver is an open implementation. 1745b2fc499SJeff Garzik This driver should work with at least the following devices: 1755b2fc499SJeff Garzik 17668924920SJonas Sjöquist * Dell Wireless 5530 HSPA 1775b2fc499SJeff Garzik * Ericsson PipeRider (all variants) 17868924920SJonas Sjöquist * Ericsson Mobile Broadband Module (all variants) 1795b2fc499SJeff Garzik * Motorola (DM100 and SB4100) 1805b2fc499SJeff Garzik * Broadcom Cable Modem (reference design) 1813a19d56cSTorgny Johansson * Toshiba (PCX1100U and F3507g/F3607gw) 1825b2fc499SJeff Garzik * ... 1835b2fc499SJeff Garzik 1845b2fc499SJeff Garzik This driver creates an interface named "ethX", where X depends on 1855b2fc499SJeff Garzik what other networking devices you have in use. However, if the 1865b2fc499SJeff Garzik IEEE 802 "local assignment" bit is set in the address, a "usbX" 1875b2fc499SJeff Garzik name is used instead. 1885b2fc499SJeff Garzik 1899f722c09SOmar Laazimaniconfig USB_NET_CDC_EEM 1909f722c09SOmar Laazimani tristate "CDC EEM support" 1919f722c09SOmar Laazimani depends on USB_USBNET && EXPERIMENTAL 1929f722c09SOmar Laazimani help 1939f722c09SOmar Laazimani This option supports devices conforming to the Communication Device 1949f722c09SOmar Laazimani Class (CDC) Ethernet Emulation Model, a specification that's easy to 1959f722c09SOmar Laazimani implement in device firmware. The CDC EEM specifications are available 1969f722c09SOmar Laazimani from <http://www.usb.org/>. 1979f722c09SOmar Laazimani 1989f722c09SOmar Laazimani This driver creates an interface named "ethX", where X depends on 1999f722c09SOmar Laazimani what other networking devices you have in use. However, if the 2009f722c09SOmar Laazimani IEEE 802 "local assignment" bit is set in the address, a "usbX" 2019f722c09SOmar Laazimani name is used instead. 2029f722c09SOmar Laazimani 203900d495aSAlexey Orishkoconfig USB_NET_CDC_NCM 204900d495aSAlexey Orishko tristate "CDC NCM support" 205900d495aSAlexey Orishko depends on USB_USBNET 206900d495aSAlexey Orishko default y 207900d495aSAlexey Orishko help 208900d495aSAlexey Orishko This driver provides support for CDC NCM (Network Control Model 209900d495aSAlexey Orishko Device USB Class Specification). The CDC NCM specification is 210900d495aSAlexey Orishko available from <http://www.usb.org/>. 211900d495aSAlexey Orishko 212900d495aSAlexey Orishko Say "y" to link the driver statically, or "m" to build a 213900d495aSAlexey Orishko dynamically linked module. 214900d495aSAlexey Orishko 215900d495aSAlexey Orishko This driver should work with at least the following devices: 216900d495aSAlexey Orishko * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design) 217900d495aSAlexey Orishko * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design) 218900d495aSAlexey Orishko * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design) 219900d495aSAlexey Orishko * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design) 220900d495aSAlexey Orishko * Ericsson F5521gw Mobile Broadband Module 221900d495aSAlexey Orishko 2229084ccf9SBjørn Morkconfig USB_NET_CDC_MBIM 2239084ccf9SBjørn Mork tristate "CDC MBIM support" 2249084ccf9SBjørn Mork depends on USB_USBNET 2259084ccf9SBjørn Mork select USB_WDM 2269084ccf9SBjørn Mork select USB_NET_CDC_NCM 2279084ccf9SBjørn Mork help 2289084ccf9SBjørn Mork This driver provides support for CDC MBIM (Mobile Broadband 2299084ccf9SBjørn Mork Interface Model) devices. The CDC MBIM specification is 2309084ccf9SBjørn Mork available from <http://www.usb.org/>. 2319084ccf9SBjørn Mork 2329084ccf9SBjørn Mork MBIM devices require configuration using the management 2339084ccf9SBjørn Mork protocol defined by the MBIM specification. This driver 2349084ccf9SBjørn Mork provides unfiltered access to the MBIM control channel 2359084ccf9SBjørn Mork through the associated /dev/cdc-wdmx character device. 2369084ccf9SBjørn Mork 2379084ccf9SBjørn Mork To compile this driver as a module, choose M here: the 2389084ccf9SBjørn Mork module will be called cdc_mbim. 2399084ccf9SBjørn Mork 2405b2fc499SJeff Garzikconfig USB_NET_DM9601 2415b2fc499SJeff Garzik tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices" 2425b2fc499SJeff Garzik depends on USB_USBNET 2435b2fc499SJeff Garzik select CRC32 2445b2fc499SJeff Garzik help 2455b2fc499SJeff Garzik This option adds support for Davicom DM9601 based USB 1.1 2465b2fc499SJeff Garzik 10/100 Ethernet adapters. 2475b2fc499SJeff Garzik 248d0cad871SSteve Glendinningconfig USB_NET_SMSC75XX 249d0cad871SSteve Glendinning tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices" 250d0cad871SSteve Glendinning depends on USB_USBNET 251*899a391bSSteve Glendinning select BITREVERSE 252*899a391bSSteve Glendinning select CRC16 253d0cad871SSteve Glendinning select CRC32 254d0cad871SSteve Glendinning help 255d0cad871SSteve Glendinning This option adds support for SMSC LAN95XX based USB 2.0 256d0cad871SSteve Glendinning Gigabit Ethernet adapters. 257d0cad871SSteve Glendinning 2582f7ca802SSteve Glendinningconfig USB_NET_SMSC95XX 2592f7ca802SSteve Glendinning tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices" 2602f7ca802SSteve Glendinning depends on USB_USBNET 261bbd9f9eeSSteve Glendinning select BITREVERSE 262bbd9f9eeSSteve Glendinning select CRC16 2632f7ca802SSteve Glendinning select CRC32 2642f7ca802SSteve Glendinning help 2652f7ca802SSteve Glendinning This option adds support for SMSC LAN95XX based USB 2.0 2662f7ca802SSteve Glendinning 10/100 Ethernet adapters. 2672f7ca802SSteve Glendinning 2685b2fc499SJeff Garzikconfig USB_NET_GL620A 2695b2fc499SJeff Garzik tristate "GeneSys GL620USB-A based cables" 2705b2fc499SJeff Garzik depends on USB_USBNET 2715b2fc499SJeff Garzik help 2725b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable, 2735b2fc499SJeff Garzik or PC2PC motherboard, with this chip. 2745b2fc499SJeff Garzik 2755b2fc499SJeff Garzik Note that the half-duplex "GL620USB" is not supported. 2765b2fc499SJeff Garzik 2775b2fc499SJeff Garzikconfig USB_NET_NET1080 2785b2fc499SJeff Garzik tristate "NetChip 1080 based cables (Laplink, ...)" 2795b2fc499SJeff Garzik default y 2805b2fc499SJeff Garzik depends on USB_USBNET 2815b2fc499SJeff Garzik help 2825b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable based 2835b2fc499SJeff Garzik on this design: one NetChip 1080 chip and supporting logic, 2845b2fc499SJeff Garzik optionally with LEDs that indicate traffic 2855b2fc499SJeff Garzik 2865b2fc499SJeff Garzikconfig USB_NET_PLUSB 287647da406Ssimon tristate "Prolific PL-2301/2302/25A1 based cables" 2885b2fc499SJeff Garzik # if the handshake/init/reset problems, from original 'plusb', 2895b2fc499SJeff Garzik # are ever resolved ... then remove "experimental" 2905b2fc499SJeff Garzik depends on USB_USBNET && EXPERIMENTAL 2915b2fc499SJeff Garzik help 2925b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 2935b2fc499SJeff Garzik with one of these chips. 2945b2fc499SJeff Garzik 2955b2fc499SJeff Garzikconfig USB_NET_MCS7830 2965b2fc499SJeff Garzik tristate "MosChip MCS7830 based Ethernet adapters" 2975b2fc499SJeff Garzik depends on USB_USBNET 2985b2fc499SJeff Garzik help 2995b2fc499SJeff Garzik Choose this option if you're using a 10/100 Ethernet USB2 3005b2fc499SJeff Garzik adapter based on the MosChip 7830 controller. This includes 3015b2fc499SJeff Garzik adapters marketed under the DeLOCK brand. 3025b2fc499SJeff Garzik 3035b2fc499SJeff Garzikconfig USB_NET_RNDIS_HOST 3045b2fc499SJeff Garzik tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)" 3055b2fc499SJeff Garzik depends on USB_USBNET && EXPERIMENTAL 3065b2fc499SJeff Garzik select USB_NET_CDCETHER 3075b2fc499SJeff Garzik help 3085b2fc499SJeff Garzik This option enables hosting "Remote NDIS" USB networking links, 3095b2fc499SJeff Garzik as encouraged by Microsoft (instead of CDC Ethernet!) for use in 3105b2fc499SJeff Garzik various devices that may only support this protocol. A variant 3115b2fc499SJeff Garzik of this protocol (with even less public documentation) seems to 3125b2fc499SJeff Garzik be at the root of Microsoft's "ActiveSync" too. 3135b2fc499SJeff Garzik 3145b2fc499SJeff Garzik Avoid using this protocol unless you have no better options. 3155b2fc499SJeff Garzik The protocol specification is incomplete, and is controlled by 3165b2fc499SJeff Garzik (and for) Microsoft; it isn't an "Open" ecosystem or market. 3175b2fc499SJeff Garzik 3185b2fc499SJeff Garzikconfig USB_NET_CDC_SUBSET 3195b2fc499SJeff Garzik tristate "Simple USB Network Links (CDC Ethernet subset)" 3205b2fc499SJeff Garzik depends on USB_USBNET 3215b2fc499SJeff Garzik default y 3225b2fc499SJeff Garzik help 3235b2fc499SJeff Garzik This driver module supports USB network devices that can work 3245b2fc499SJeff Garzik without any device-specific information. Select it if you have 3255b2fc499SJeff Garzik one of these drivers. 3265b2fc499SJeff Garzik 3275b2fc499SJeff Garzik Note that while many USB host-to-host cables can work in this mode, 3285b2fc499SJeff Garzik that may mean not being able to talk to Win32 systems or more 3295b2fc499SJeff Garzik commonly not being able to handle certain events (like replugging 3305b2fc499SJeff Garzik the host on the other end) very well. Also, these devices will 3315b2fc499SJeff Garzik not generally have permanently assigned Ethernet addresses. 3325b2fc499SJeff Garzik 3335b2fc499SJeff Garzikconfig USB_ALI_M5632 3345b2fc499SJeff Garzik boolean "ALi M5632 based 'USB 2.0 Data Link' cables" 3355b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 3365b2fc499SJeff Garzik help 3375b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 3385b2fc499SJeff Garzik based on this design, which supports USB 2.0 high speed. 3395b2fc499SJeff Garzik 3405b2fc499SJeff Garzikconfig USB_AN2720 3415b2fc499SJeff Garzik boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)" 3425b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 3435b2fc499SJeff Garzik help 3445b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 3455b2fc499SJeff Garzik based on this design. Note that AnchorChips is now a 3465b2fc499SJeff Garzik Cypress brand. 3475b2fc499SJeff Garzik 3485b2fc499SJeff Garzikconfig USB_BELKIN 3495b2fc499SJeff Garzik boolean "eTEK based host-to-host cables (Advance, Belkin, ...)" 3505b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 3515b2fc499SJeff Garzik default y 3525b2fc499SJeff Garzik help 3535b2fc499SJeff Garzik Choose this option if you're using a host-to-host cable 3545b2fc499SJeff Garzik based on this design: two NetChip 2890 chips and an Atmel 3555b2fc499SJeff Garzik microcontroller, with LEDs that indicate traffic. 3565b2fc499SJeff Garzik 3575b2fc499SJeff Garzikconfig USB_ARMLINUX 3585b2fc499SJeff Garzik boolean "Embedded ARM Linux links (iPaq, ...)" 3595b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 3605b2fc499SJeff Garzik default y 3615b2fc499SJeff Garzik help 3625b2fc499SJeff Garzik Choose this option to support the "usb-eth" networking driver 3635b2fc499SJeff Garzik used by most of the ARM Linux community with device controllers 3645b2fc499SJeff Garzik such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities 3655b2fc499SJeff Garzik in some PXA versions of the "blob" boot loader. 3665b2fc499SJeff Garzik 3675b2fc499SJeff Garzik Linux-based "Gumstix" PXA-25x based systems use this protocol 3685b2fc499SJeff Garzik to talk with other Linux systems. 3695b2fc499SJeff Garzik 3705b2fc499SJeff Garzik Although the ROMs shipped with Sharp Zaurus products use a 3715b2fc499SJeff Garzik different link level framing protocol, you can have them use 3725b2fc499SJeff Garzik this simpler protocol by installing a different kernel. 3735b2fc499SJeff Garzik 3745b2fc499SJeff Garzikconfig USB_EPSON2888 3755b2fc499SJeff Garzik boolean "Epson 2888 based firmware (DEVELOPMENT)" 3765b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET 3775b2fc499SJeff Garzik help 3785b2fc499SJeff Garzik Choose this option to support the usb networking links used 3795b2fc499SJeff Garzik by some sample firmware from Epson. 3805b2fc499SJeff Garzik 3815b2fc499SJeff Garzikconfig USB_KC2190 3825b2fc499SJeff Garzik boolean "KT Technology KC2190 based cables (InstaNet)" 3835b2fc499SJeff Garzik depends on USB_NET_CDC_SUBSET && EXPERIMENTAL 3845b2fc499SJeff Garzik help 385c0811987SSam Ravnborg Choose this option if you're using a host-to-host cable 386c0811987SSam Ravnborg with one of these chips. 3875b2fc499SJeff Garzik 3885b2fc499SJeff Garzikconfig USB_NET_ZAURUS 3895b2fc499SJeff Garzik tristate "Sharp Zaurus (stock ROMs) and compatible" 3905b2fc499SJeff Garzik depends on USB_USBNET 3915b2fc499SJeff Garzik select USB_NET_CDCETHER 3925b2fc499SJeff Garzik select CRC32 3935b2fc499SJeff Garzik default y 3945b2fc499SJeff Garzik help 3955b2fc499SJeff Garzik Choose this option to support the usb networking links used by 3965b2fc499SJeff Garzik Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. 3975b2fc499SJeff Garzik This also supports some related device firmware, as used in some 3985b2fc499SJeff Garzik PDAs from Olympus and some cell phones from Motorola. 3995b2fc499SJeff Garzik 4005b2fc499SJeff Garzik If you install an alternate image, such as the Linux 2.6 based 4015b2fc499SJeff Garzik versions of OpenZaurus, you should no longer need to support this 4025b2fc499SJeff Garzik protocol. Only the "eth-fd" or "net_fd" drivers in these devices 4035b2fc499SJeff Garzik really need this non-conformant variant of CDC Ethernet (or in 4045b2fc499SJeff Garzik some cases CDC MDLM) protocol, not "g_ether". 4055b2fc499SJeff Garzik 406cc28a20eSOndrej Zaryconfig USB_NET_CX82310_ETH 407cc28a20eSOndrej Zary tristate "Conexant CX82310 USB ethernet port" 408cc28a20eSOndrej Zary depends on USB_USBNET 409cc28a20eSOndrej Zary help 410cc28a20eSOndrej Zary Choose this option if you're using a Conexant CX82310-based ADSL 411cc28a20eSOndrej Zary router with USB ethernet port. This driver is for routers only, 412cc28a20eSOndrej Zary it will not work with ADSL modems (use cxacru driver instead). 413cc28a20eSOndrej Zary 414d4026123SMarius B. Kotsbakconfig USB_NET_KALMIA 415d4026123SMarius B. Kotsbak tristate "Samsung Kalmia based LTE USB modem" 416d4026123SMarius B. Kotsbak depends on USB_USBNET 417d4026123SMarius B. Kotsbak help 418d4026123SMarius B. Kotsbak Choose this option if you have a Samsung Kalmia based USB modem 419d4026123SMarius B. Kotsbak as Samsung GT-B3730. 420d4026123SMarius B. Kotsbak 421d4026123SMarius B. Kotsbak To compile this driver as a module, choose M here: the 422d4026123SMarius B. Kotsbak module will be called kalmia. 423d4026123SMarius B. Kotsbak 4249b28ecd6SBjørn Morkconfig USB_NET_QMI_WWAN 4259b28ecd6SBjørn Mork tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems" 4269b28ecd6SBjørn Mork depends on USB_USBNET 42774cba4a8SBjørn Mork select USB_WDM 4289b28ecd6SBjørn Mork help 4299b28ecd6SBjørn Mork Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem 4309b28ecd6SBjørn Mork (MDM) chipsets. Examples of such devices are 4319b28ecd6SBjørn Mork * Huawei E392/E398 4329b28ecd6SBjørn Mork 4339b28ecd6SBjørn Mork This driver will only drive the ethernet part of the chips. 4349b28ecd6SBjørn Mork The devices require additional configuration to be usable. 4359b28ecd6SBjørn Mork Multiple management interfaces with linux drivers are 4369b28ecd6SBjørn Mork available: 4379b28ecd6SBjørn Mork 4389b28ecd6SBjørn Mork * option: AT commands on /dev/ttyUSBx 4399b28ecd6SBjørn Mork * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx 4409b28ecd6SBjørn Mork 4419b28ecd6SBjørn Mork A modem manager with support for QMI is recommended. 4429b28ecd6SBjørn Mork 4439b28ecd6SBjørn Mork To compile this driver as a module, choose M here: the 4449b28ecd6SBjørn Mork module will be called qmi_wwan. 4459b28ecd6SBjørn Mork 44685a73b33SDavid Brownellconfig USB_HSO 44785a73b33SDavid Brownell tristate "Option USB High Speed Mobile Devices" 44885a73b33SDavid Brownell depends on USB && RFKILL 44985a73b33SDavid Brownell default n 45085a73b33SDavid Brownell help 45185a73b33SDavid Brownell Choose this option if you have an Option HSDPA/HSUPA card. 45285a73b33SDavid Brownell These cards support downlink speeds of 7.2Mbps or greater. 45385a73b33SDavid Brownell 45485a73b33SDavid Brownell To compile this driver as a module, choose M here: the 45585a73b33SDavid Brownell module will be called hso. 4565b2fc499SJeff Garzik 4574510d7cbSPeter Holikconfig USB_NET_INT51X1 4584510d7cbSPeter Holik tristate "Intellon PLC based usb adapter" 4594510d7cbSPeter Holik depends on USB_USBNET 4604510d7cbSPeter Holik help 4614510d7cbSPeter Holik Choose this option if you're using a 14Mb USB-based PLC 4624510d7cbSPeter Holik (Powerline Communications) solution with an Intellon 4634510d7cbSPeter Holik INT51x1/INT5200 chip, like the "devolo dLan duo". 4644510d7cbSPeter Holik 46587cf6560SRémi Denis-Courmontconfig USB_CDC_PHONET 46687cf6560SRémi Denis-Courmont tristate "CDC Phonet support" 46787cf6560SRémi Denis-Courmont depends on PHONET 46887cf6560SRémi Denis-Courmont help 46987cf6560SRémi Denis-Courmont Choose this option to support the Phonet interface to a Nokia 47087cf6560SRémi Denis-Courmont cellular modem, as found on most Nokia handsets with the 47187cf6560SRémi Denis-Courmont "PC suite" USB profile. 47287cf6560SRémi Denis-Courmont 473a19259c3SDiego Giagioconfig USB_IPHETH 474a19259c3SDiego Giagio tristate "Apple iPhone USB Ethernet driver" 475a19259c3SDiego Giagio default n 476a19259c3SDiego Giagio ---help--- 477a19259c3SDiego Giagio Module used to share Internet connection (tethering) from your 478a19259c3SDiego Giagio iPhone (Original, 3G and 3GS) to your system. 479a19259c3SDiego Giagio Note that you need userspace libraries and programs that are needed 480a19259c3SDiego Giagio to pair your device with your system and that understand the iPhone 481a19259c3SDiego Giagio protocol. 482a19259c3SDiego Giagio 483a19259c3SDiego Giagio For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver 484a19259c3SDiego Giagio 485eb4fd8cdSElina Pashevaconfig USB_SIERRA_NET 486eb4fd8cdSElina Pasheva tristate "USB-to-WWAN Driver for Sierra Wireless modems" 487eb4fd8cdSElina Pasheva depends on USB_USBNET 488eb4fd8cdSElina Pasheva help 489eb4fd8cdSElina Pasheva Choose this option if you have a Sierra Wireless USB-to-WWAN device. 490eb4fd8cdSElina Pasheva 491eb4fd8cdSElina Pasheva To compile this driver as a module, choose M here: the 492eb4fd8cdSElina Pasheva module will be called sierra_net. 493eb4fd8cdSElina Pasheva 4947a635ea9SAndrzej Zaborowskiconfig USB_VL600 4957a635ea9SAndrzej Zaborowski tristate "LG VL600 modem dongle" 4967a635ea9SAndrzej Zaborowski depends on USB_NET_CDCETHER 4977a635ea9SAndrzej Zaborowski select USB_ACM 4987a635ea9SAndrzej Zaborowski help 4997a635ea9SAndrzej Zaborowski Select this if you want to use an LG Electronics 4G/LTE usb modem 5007a635ea9SAndrzej Zaborowski called VL600. This driver only handles the ethernet 5017a635ea9SAndrzej Zaborowski interface exposed by the modem firmware. To establish a connection 5027a635ea9SAndrzej Zaborowski you will first need a userspace program that sends the right 5037a635ea9SAndrzej Zaborowski command to the modem through its CDC ACM port, and most 5047a635ea9SAndrzej Zaborowski likely also a DHCP client. See this thread about using the 5057a635ea9SAndrzej Zaborowski 4G modem from Verizon: 5067a635ea9SAndrzej Zaborowski 5077a635ea9SAndrzej Zaborowski http://ubuntuforums.org/showpost.php?p=10589647&postcount=17 5087a635ea9SAndrzej Zaborowski 5099b28ecd6SBjørn Mork 5105b2fc499SJeff Garzikendmenu 511