Kconfig 21 KB

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