Kconfig 18 KB

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