Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616
  1. #
  2. # USB Network devices configuration
  3. #
  4. comment "Host-side USB support is needed for USB Network Adapter support"
  5. depends on !USB && NET
  6. menuconfig USB_NET_DRIVERS
  7. tristate "USB Network Adapters"
  8. default USB if USB
  9. depends on USB && NET
  10. if USB_NET_DRIVERS
  11. config USB_CATC
  12. tristate "USB CATC NetMate-based Ethernet device support"
  13. select CRC32
  14. ---help---
  15. Say Y if you want to use one of the following 10Mbps USB Ethernet
  16. device based on the EL1210A chip. Supported devices are:
  17. Belkin F5U011
  18. Belkin F5U111
  19. CATC NetMate
  20. CATC NetMate II
  21. smartBridges smartNIC
  22. This driver makes the adapter appear as a normal Ethernet interface,
  23. typically on eth0, if it is the only ethernet device, or perhaps on
  24. eth1, if you have a PCI or ISA ethernet card installed.
  25. To compile this driver as a module, choose M here: the
  26. module will be called catc.
  27. config USB_KAWETH
  28. tristate "USB KLSI KL5USB101-based ethernet device support"
  29. ---help---
  30. Say Y here if you want to use one of the following 10Mbps only
  31. USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
  32. 3Com 3C19250
  33. ADS USB-10BT
  34. ATEN USB Ethernet
  35. ASANTE USB To Ethernet Adapter
  36. AOX Endpoints USB Ethernet
  37. Correga K.K.
  38. D-Link DSB-650C and DU-E10
  39. Entrega / Portgear E45
  40. I-O DATA USB-ET/T
  41. Jaton USB Ethernet Device Adapter
  42. Kingston Technology USB Ethernet Adapter
  43. Linksys USB10T
  44. Mobility USB-Ethernet Adapter
  45. NetGear EA-101
  46. Peracom Enet and Enet2
  47. Portsmith Express Ethernet Adapter
  48. Shark Pocket Adapter
  49. SMC 2202USB
  50. Sony Vaio port extender
  51. This driver is likely to work with most 10Mbps only USB Ethernet
  52. adapters, including some "no brand" devices. It does NOT work on
  53. SmartBridges smartNIC or on Belkin F5U111 devices - you should use
  54. the CATC NetMate driver for those. If you are not sure which one
  55. you need, select both, and the correct one should be selected for
  56. you.
  57. This driver makes the adapter appear as a normal Ethernet interface,
  58. typically on eth0, if it is the only ethernet device, or perhaps on
  59. eth1, if you have a PCI or ISA ethernet card installed.
  60. To compile this driver as a module, choose M here: the
  61. module will be called kaweth.
  62. config USB_PEGASUS
  63. tristate "USB Pegasus/Pegasus-II based ethernet device support"
  64. select MII
  65. ---help---
  66. Say Y here if you know you have Pegasus or Pegasus-II based adapter.
  67. If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
  68. complete list of supported devices.
  69. If your particular adapter is not in the list and you are _sure_ it
  70. is Pegasus or Pegasus II based then send me
  71. <petkan@users.sourceforge.net> vendor and device IDs.
  72. To compile this driver as a module, choose M here: the
  73. module will be called pegasus.
  74. config USB_RTL8150
  75. tristate "USB RTL8150 based ethernet device support"
  76. select MII
  77. help
  78. Say Y here if you have RTL8150 based usb-ethernet adapter.
  79. Send me <petkan@users.sourceforge.net> any comments you may have.
  80. You can also check for updates at <http://pegasus2.sourceforge.net/>.
  81. To compile this driver as a module, choose M here: the
  82. module will be called rtl8150.
  83. config USB_RTL8152
  84. tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
  85. select MII
  86. help
  87. This option adds support for Realtek RTL8152 based USB 2.0
  88. 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
  89. Ethernet adapters.
  90. To compile this driver as a module, choose M here: the
  91. module will be called r8152.
  92. config USB_LAN78XX
  93. tristate "Microchip LAN78XX Based USB Ethernet Adapters"
  94. select MII
  95. select PHYLIB
  96. select MICROCHIP_PHY
  97. select FIXED_PHY
  98. help
  99. This option adds support for Microchip LAN78XX based USB 2
  100. & USB 3 10/100/1000 Ethernet adapters.
  101. LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
  102. LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
  103. LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
  104. Proper PHY driver is required for LAN7801.
  105. To compile this driver as a module, choose M here: the
  106. module will be called lan78xx.
  107. config USB_USBNET
  108. tristate "Multi-purpose USB Networking Framework"
  109. select MII
  110. ---help---
  111. This driver supports several kinds of network links over USB,
  112. with "minidrivers" built around a common network driver core
  113. that supports deep queues for efficient transfers. (This gives
  114. better performance with small packets and at high speeds).
  115. The USB host runs "usbnet", and the other end of the link might be:
  116. - Another USB host, when using USB "network" or "data transfer"
  117. cables. These are often used to network laptops to PCs, like
  118. "Laplink" parallel cables or some motherboards. These rely
  119. on specialized chips from many suppliers.
  120. - An intelligent USB gadget, perhaps embedding a Linux system.
  121. These include PDAs running Linux (iPaq, Yopy, Zaurus, and
  122. others), and devices that interoperate using the standard
  123. CDC-Ethernet specification (including many cable modems).
  124. - Network adapter hardware (like those for 10/100 Ethernet) which
  125. uses this driver framework.
  126. The link will appear with a name like "usb0", when the link is
  127. a two-node link, or "eth0" for most CDC-Ethernet devices. Those
  128. two-node links are most easily managed with Ethernet Bridging
  129. (CONFIG_BRIDGE) instead of routing.
  130. For more information see <http://www.linux-usb.org/usbnet/>.
  131. To compile this driver as a module, choose M here: the
  132. module will be called usbnet.
  133. config USB_NET_AX8817X
  134. tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
  135. depends on USB_USBNET
  136. select CRC32
  137. select PHYLIB
  138. default y
  139. help
  140. This option adds support for ASIX AX88xxx based USB 2.0
  141. 10/100 Ethernet adapters.
  142. This driver should work with at least the following devices:
  143. * Aten UC210T
  144. * ASIX AX88172
  145. * Billionton Systems, USB2AR
  146. * Billionton Systems, GUSB2AM-1G-B
  147. * Buffalo LUA-U2-KTX
  148. * Corega FEther USB2-TX
  149. * D-Link DUB-E100
  150. * Hawking UF200
  151. * Linksys USB200M
  152. * Netgear FA120
  153. * Sitecom LN-029
  154. * Sitecom LN-028
  155. * Intellinet USB 2.0 Ethernet
  156. * ST Lab USB 2.0 Ethernet
  157. * TrendNet TU2-ET100
  158. This driver creates an interface named "ethX", where X depends on
  159. what other networking devices you have in use.
  160. config USB_NET_AX88179_178A
  161. tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
  162. depends on USB_USBNET
  163. select CRC32
  164. select PHYLIB
  165. default y
  166. help
  167. This option adds support for ASIX AX88179 based USB 3.0/2.0
  168. to Gigabit Ethernet adapters.
  169. This driver should work with at least the following devices:
  170. * ASIX AX88179
  171. * ASIX AX88178A
  172. * Sitcomm LN-032
  173. This driver creates an interface named "ethX", where X depends on
  174. what other networking devices you have in use.
  175. config USB_NET_CDCETHER
  176. tristate "CDC Ethernet support (smart devices such as cable modems)"
  177. depends on USB_USBNET
  178. default y
  179. help
  180. This option supports devices conforming to the Communication Device
  181. Class (CDC) Ethernet Control Model, a specification that's easy to
  182. implement in device firmware. The CDC specifications are available
  183. from <http://www.usb.org/>.
  184. CDC Ethernet is an implementation option for DOCSIS cable modems
  185. that support USB connectivity, used for non-Microsoft USB hosts.
  186. The Linux-USB CDC Ethernet Gadget driver is an open implementation.
  187. This driver should work with at least the following devices:
  188. * Dell Wireless 5530 HSPA
  189. * Ericsson PipeRider (all variants)
  190. * Ericsson Mobile Broadband Module (all variants)
  191. * Motorola (DM100 and SB4100)
  192. * Broadcom Cable Modem (reference design)
  193. * Toshiba (PCX1100U and F3507g/F3607gw)
  194. * ...
  195. This driver creates an interface named "ethX", where X depends on
  196. what other networking devices you have in use. However, if the
  197. IEEE 802 "local assignment" bit is set in the address, a "usbX"
  198. name is used instead.
  199. config USB_NET_CDC_EEM
  200. tristate "CDC EEM support"
  201. depends on USB_USBNET
  202. help
  203. This option supports devices conforming to the Communication Device
  204. Class (CDC) Ethernet Emulation Model, a specification that's easy to
  205. implement in device firmware. The CDC EEM specifications are available
  206. from <http://www.usb.org/>.
  207. This driver creates an interface named "ethX", where X depends on
  208. what other networking devices you have in use. However, if the
  209. IEEE 802 "local assignment" bit is set in the address, a "usbX"
  210. name is used instead.
  211. config USB_NET_CDC_NCM
  212. tristate "CDC NCM support"
  213. depends on USB_USBNET
  214. default y
  215. help
  216. This driver provides support for CDC NCM (Network Control Model
  217. Device USB Class Specification). The CDC NCM specification is
  218. available from <http://www.usb.org/>.
  219. Say "y" to link the driver statically, or "m" to build a
  220. dynamically linked module.
  221. This driver should work with at least the following devices:
  222. * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
  223. * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
  224. * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
  225. * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
  226. * Ericsson F5521gw Mobile Broadband Module
  227. config USB_NET_HUAWEI_CDC_NCM
  228. tristate "Huawei NCM embedded AT channel support"
  229. depends on USB_USBNET
  230. select USB_WDM
  231. select USB_NET_CDC_NCM
  232. help
  233. This driver supports huawei-style NCM devices, that use NCM as a
  234. transport for other protocols, usually an embedded AT channel.
  235. Good examples are:
  236. * Huawei E3131
  237. * Huawei E3251
  238. To compile this driver as a module, choose M here: the module will be
  239. called huawei_cdc_ncm.ko.
  240. config USB_NET_CDC_MBIM
  241. tristate "CDC MBIM support"
  242. depends on USB_USBNET
  243. select USB_WDM
  244. select USB_NET_CDC_NCM
  245. help
  246. This driver provides support for CDC MBIM (Mobile Broadband
  247. Interface Model) devices. The CDC MBIM specification is
  248. available from <http://www.usb.org/>.
  249. MBIM devices require configuration using the management
  250. protocol defined by the MBIM specification. This driver
  251. provides unfiltered access to the MBIM control channel
  252. through the associated /dev/cdc-wdmx character device.
  253. To compile this driver as a module, choose M here: the
  254. module will be called cdc_mbim.
  255. config USB_NET_DM9601
  256. tristate "Davicom DM96xx based USB 10/100 ethernet devices"
  257. depends on USB_USBNET
  258. select CRC32
  259. help
  260. This option adds support for Davicom DM9601/DM9620/DM9621A
  261. based USB 10/100 Ethernet adapters.
  262. config USB_NET_SR9700
  263. tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
  264. depends on USB_USBNET
  265. select CRC32
  266. help
  267. This option adds support for CoreChip-sz SR9700 based USB 1.1
  268. 10/100 Ethernet adapters.
  269. config USB_NET_SR9800
  270. tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
  271. depends on USB_USBNET
  272. select CRC32
  273. ---help---
  274. Say Y if you want to use one of the following 100Mbps USB Ethernet
  275. device based on the CoreChip-sz SR9800 chip.
  276. This driver makes the adapter appear as a normal Ethernet interface,
  277. typically on eth0, if it is the only ethernet device, or perhaps on
  278. eth1, if you have a PCI or ISA ethernet card installed.
  279. To compile this driver as a module, choose M here: the
  280. module will be called sr9800.
  281. config USB_NET_SMSC75XX
  282. tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
  283. depends on USB_USBNET
  284. select BITREVERSE
  285. select CRC16
  286. select CRC32
  287. help
  288. This option adds support for SMSC LAN75XX based USB 2.0
  289. Gigabit Ethernet adapters.
  290. config USB_NET_SMSC95XX
  291. tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
  292. depends on USB_USBNET
  293. select BITREVERSE
  294. select CRC16
  295. select CRC32
  296. help
  297. This option adds support for SMSC LAN95XX based USB 2.0
  298. 10/100 Ethernet adapters.
  299. config USB_NET_GL620A
  300. tristate "GeneSys GL620USB-A based cables"
  301. depends on USB_USBNET
  302. help
  303. Choose this option if you're using a host-to-host cable,
  304. or PC2PC motherboard, with this chip.
  305. Note that the half-duplex "GL620USB" is not supported.
  306. config USB_NET_NET1080
  307. tristate "NetChip 1080 based cables (Laplink, ...)"
  308. default y
  309. depends on USB_USBNET
  310. help
  311. Choose this option if you're using a host-to-host cable based
  312. on this design: one NetChip 1080 chip and supporting logic,
  313. optionally with LEDs that indicate traffic
  314. config USB_NET_PLUSB
  315. tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
  316. # if the handshake/init/reset problems, from original 'plusb',
  317. # are ever resolved ... then remove "experimental"
  318. depends on USB_USBNET
  319. help
  320. Choose this option if you're using a host-to-host cable
  321. with one of these chips.
  322. config USB_NET_MCS7830
  323. tristate "MosChip MCS7830 based Ethernet adapters"
  324. depends on USB_USBNET
  325. help
  326. Choose this option if you're using a 10/100 Ethernet USB2
  327. adapter based on the MosChip 7830 controller. This includes
  328. adapters marketed under the DeLOCK brand.
  329. config USB_NET_RNDIS_HOST
  330. tristate "Host for RNDIS and ActiveSync devices"
  331. depends on USB_USBNET
  332. select USB_NET_CDCETHER
  333. help
  334. This option enables hosting "Remote NDIS" USB networking links,
  335. as encouraged by Microsoft (instead of CDC Ethernet!) for use in
  336. various devices that may only support this protocol. A variant
  337. of this protocol (with even less public documentation) seems to
  338. be at the root of Microsoft's "ActiveSync" too.
  339. Avoid using this protocol unless you have no better options.
  340. The protocol specification is incomplete, and is controlled by
  341. (and for) Microsoft; it isn't an "Open" ecosystem or market.
  342. config USB_NET_CDC_SUBSET_ENABLE
  343. tristate
  344. depends on USB_NET_CDC_SUBSET
  345. config USB_NET_CDC_SUBSET
  346. tristate "Simple USB Network Links (CDC Ethernet subset)"
  347. depends on USB_USBNET
  348. default y
  349. help
  350. This driver module supports USB network devices that can work
  351. without any device-specific information. Select it if you have
  352. one of these drivers.
  353. Note that while many USB host-to-host cables can work in this mode,
  354. that may mean not being able to talk to Win32 systems or more
  355. commonly not being able to handle certain events (like replugging
  356. the host on the other end) very well. Also, these devices will
  357. not generally have permanently assigned Ethernet addresses.
  358. config USB_ALI_M5632
  359. bool "ALi M5632 based 'USB 2.0 Data Link' cables"
  360. depends on USB_NET_CDC_SUBSET
  361. select USB_NET_CDC_SUBSET_ENABLE
  362. help
  363. Choose this option if you're using a host-to-host cable
  364. based on this design, which supports USB 2.0 high speed.
  365. config USB_AN2720
  366. bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
  367. depends on USB_NET_CDC_SUBSET
  368. select USB_NET_CDC_SUBSET_ENABLE
  369. help
  370. Choose this option if you're using a host-to-host cable
  371. based on this design. Note that AnchorChips is now a
  372. Cypress brand.
  373. config USB_BELKIN
  374. bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
  375. depends on USB_NET_CDC_SUBSET
  376. select USB_NET_CDC_SUBSET_ENABLE
  377. default y
  378. help
  379. Choose this option if you're using a host-to-host cable
  380. based on this design: two NetChip 2890 chips and an Atmel
  381. microcontroller, with LEDs that indicate traffic.
  382. config USB_ARMLINUX
  383. bool "Embedded ARM Linux links (iPaq, ...)"
  384. depends on USB_NET_CDC_SUBSET
  385. select USB_NET_CDC_SUBSET_ENABLE
  386. default y
  387. help
  388. Choose this option to support the "usb-eth" networking driver
  389. used by most of the ARM Linux community with device controllers
  390. such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
  391. in some PXA versions of the "blob" boot loader.
  392. Linux-based "Gumstix" PXA-25x based systems use this protocol
  393. to talk with other Linux systems.
  394. Although the ROMs shipped with Sharp Zaurus products use a
  395. different link level framing protocol, you can have them use
  396. this simpler protocol by installing a different kernel.
  397. config USB_EPSON2888
  398. bool "Epson 2888 based firmware (DEVELOPMENT)"
  399. depends on USB_NET_CDC_SUBSET
  400. select USB_NET_CDC_SUBSET_ENABLE
  401. help
  402. Choose this option to support the usb networking links used
  403. by some sample firmware from Epson.
  404. config USB_KC2190
  405. bool "KT Technology KC2190 based cables (InstaNet)"
  406. depends on USB_NET_CDC_SUBSET
  407. select USB_NET_CDC_SUBSET_ENABLE
  408. help
  409. Choose this option if you're using a host-to-host cable
  410. with one of these chips.
  411. config USB_NET_ZAURUS
  412. tristate "Sharp Zaurus (stock ROMs) and compatible"
  413. depends on USB_USBNET
  414. select USB_NET_CDCETHER
  415. select CRC32
  416. default y
  417. help
  418. Choose this option to support the usb networking links used by
  419. Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
  420. This also supports some related device firmware, as used in some
  421. PDAs from Olympus and some cell phones from Motorola.
  422. If you install an alternate image, such as the Linux 2.6 based
  423. versions of OpenZaurus, you should no longer need to support this
  424. protocol. Only the "eth-fd" or "net_fd" drivers in these devices
  425. really need this non-conformant variant of CDC Ethernet (or in
  426. some cases CDC MDLM) protocol, not "g_ether".
  427. config USB_NET_CX82310_ETH
  428. tristate "Conexant CX82310 USB ethernet port"
  429. depends on USB_USBNET
  430. help
  431. Choose this option if you're using a Conexant CX82310-based ADSL
  432. router with USB ethernet port. This driver is for routers only,
  433. it will not work with ADSL modems (use cxacru driver instead).
  434. config USB_NET_KALMIA
  435. tristate "Samsung Kalmia based LTE USB modem"
  436. depends on USB_USBNET
  437. help
  438. Choose this option if you have a Samsung Kalmia based USB modem
  439. as Samsung GT-B3730.
  440. To compile this driver as a module, choose M here: the
  441. module will be called kalmia.
  442. config USB_NET_QMI_WWAN
  443. tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
  444. depends on USB_USBNET
  445. select USB_WDM
  446. help
  447. Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
  448. (MDM) chipsets. Examples of such devices are
  449. * Huawei E392/E398
  450. This driver will only drive the ethernet part of the chips.
  451. The devices require additional configuration to be usable.
  452. Multiple management interfaces with linux drivers are
  453. available:
  454. * option: AT commands on /dev/ttyUSBx
  455. * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
  456. A modem manager with support for QMI is recommended.
  457. To compile this driver as a module, choose M here: the
  458. module will be called qmi_wwan.
  459. config USB_HSO
  460. tristate "Option USB High Speed Mobile Devices"
  461. depends on USB && RFKILL && TTY
  462. default n
  463. help
  464. Choose this option if you have an Option HSDPA/HSUPA card.
  465. These cards support downlink speeds of 7.2Mbps or greater.
  466. To compile this driver as a module, choose M here: the
  467. module will be called hso.
  468. config USB_NET_INT51X1
  469. tristate "Intellon PLC based usb adapter"
  470. depends on USB_USBNET
  471. help
  472. Choose this option if you're using a 14Mb USB-based PLC
  473. (Powerline Communications) solution with an Intellon
  474. INT51x1/INT5200 chip, like the "devolo dLan duo".
  475. config USB_CDC_PHONET
  476. tristate "CDC Phonet support"
  477. depends on PHONET && USB_USBNET
  478. help
  479. Choose this option to support the Phonet interface to a Nokia
  480. cellular modem, as found on most Nokia handsets with the
  481. "PC suite" USB profile.
  482. config USB_IPHETH
  483. tristate "Apple iPhone USB Ethernet driver"
  484. default n
  485. ---help---
  486. Module used to share Internet connection (tethering) from your
  487. iPhone (Original, 3G and 3GS) to your system.
  488. Note that you need userspace libraries and programs that are needed
  489. to pair your device with your system and that understand the iPhone
  490. protocol.
  491. For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
  492. config USB_SIERRA_NET
  493. tristate "USB-to-WWAN Driver for Sierra Wireless modems"
  494. depends on USB_USBNET
  495. help
  496. Choose this option if you have a Sierra Wireless USB-to-WWAN device.
  497. To compile this driver as a module, choose M here: the
  498. module will be called sierra_net.
  499. config USB_VL600
  500. tristate "LG VL600 modem dongle"
  501. depends on USB_NET_CDCETHER && TTY
  502. select USB_ACM
  503. help
  504. Select this if you want to use an LG Electronics 4G/LTE usb modem
  505. called VL600. This driver only handles the ethernet
  506. interface exposed by the modem firmware. To establish a connection
  507. you will first need a userspace program that sends the right
  508. command to the modem through its CDC ACM port, and most
  509. likely also a DHCP client. See this thread about using the
  510. 4G modem from Verizon:
  511. http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
  512. config USB_NET_CH9200
  513. tristate "QingHeng CH9200 USB ethernet support"
  514. depends on USB_USBNET
  515. select MII
  516. help
  517. Choose this option if you have a USB ethernet adapter with a QinHeng
  518. CH9200 chipset.
  519. To compile this driver as a module, choose M here: the
  520. module will be called ch9200.
  521. endif # USB_NET_DRIVERS