Kconfig 20 KB

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