Kconfig 18 KB

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