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