Kconfig 18 KB

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