Kconfig 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575
  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_USBNET
  93. tristate "Multi-purpose USB Networking Framework"
  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_HUAWEI_CDC_NCM
  211. tristate "Huawei NCM embedded AT channel support"
  212. depends on USB_USBNET
  213. select USB_WDM
  214. select USB_NET_CDC_NCM
  215. help
  216. This driver supports huawei-style NCM devices, that use NCM as a
  217. transport for other protocols, usually an embedded AT channel.
  218. Good examples are:
  219. * Huawei E3131
  220. * Huawei E3251
  221. To compile this driver as a module, choose M here: the module will be
  222. called huawei_cdc_ncm.ko.
  223. config USB_NET_CDC_MBIM
  224. tristate "CDC MBIM support"
  225. depends on USB_USBNET
  226. select USB_WDM
  227. select USB_NET_CDC_NCM
  228. help
  229. This driver provides support for CDC MBIM (Mobile Broadband
  230. Interface Model) devices. The CDC MBIM specification is
  231. available from <http://www.usb.org/>.
  232. MBIM devices require configuration using the management
  233. protocol defined by the MBIM specification. This driver
  234. provides unfiltered access to the MBIM control channel
  235. through the associated /dev/cdc-wdmx character device.
  236. To compile this driver as a module, choose M here: the
  237. module will be called cdc_mbim.
  238. config USB_NET_DM9601
  239. tristate "Davicom DM96xx based USB 10/100 ethernet devices"
  240. depends on USB_USBNET
  241. select CRC32
  242. help
  243. This option adds support for Davicom DM9601/DM9620/DM9621A
  244. based USB 10/100 Ethernet adapters.
  245. config USB_NET_SR9700
  246. tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
  247. depends on USB_USBNET
  248. select CRC32
  249. help
  250. This option adds support for CoreChip-sz SR9700 based USB 1.1
  251. 10/100 Ethernet adapters.
  252. config USB_NET_SR9800
  253. tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
  254. depends on USB_USBNET
  255. select CRC32
  256. ---help---
  257. Say Y if you want to use one of the following 100Mbps USB Ethernet
  258. device based on the CoreChip-sz SR9800 chip.
  259. This driver makes the adapter appear as a normal Ethernet interface,
  260. typically on eth0, if it is the only ethernet device, or perhaps on
  261. eth1, if you have a PCI or ISA ethernet card installed.
  262. To compile this driver as a module, choose M here: the
  263. module will be called sr9800.
  264. config USB_NET_SMSC75XX
  265. tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
  266. depends on USB_USBNET
  267. select BITREVERSE
  268. select CRC16
  269. select CRC32
  270. help
  271. This option adds support for SMSC LAN75XX based USB 2.0
  272. Gigabit Ethernet adapters.
  273. config USB_NET_SMSC95XX
  274. tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
  275. depends on USB_USBNET
  276. select BITREVERSE
  277. select CRC16
  278. select CRC32
  279. help
  280. This option adds support for SMSC LAN95XX based USB 2.0
  281. 10/100 Ethernet adapters.
  282. config USB_NET_GL620A
  283. tristate "GeneSys GL620USB-A based cables"
  284. depends on USB_USBNET
  285. help
  286. Choose this option if you're using a host-to-host cable,
  287. or PC2PC motherboard, with this chip.
  288. Note that the half-duplex "GL620USB" is not supported.
  289. config USB_NET_NET1080
  290. tristate "NetChip 1080 based cables (Laplink, ...)"
  291. default y
  292. depends on USB_USBNET
  293. help
  294. Choose this option if you're using a host-to-host cable based
  295. on this design: one NetChip 1080 chip and supporting logic,
  296. optionally with LEDs that indicate traffic
  297. config USB_NET_PLUSB
  298. tristate "Prolific PL-2301/2302/25A1 based cables"
  299. # if the handshake/init/reset problems, from original 'plusb',
  300. # are ever resolved ... then remove "experimental"
  301. depends on USB_USBNET
  302. help
  303. Choose this option if you're using a host-to-host cable
  304. with one of these chips.
  305. config USB_NET_MCS7830
  306. tristate "MosChip MCS7830 based Ethernet adapters"
  307. depends on USB_USBNET
  308. help
  309. Choose this option if you're using a 10/100 Ethernet USB2
  310. adapter based on the MosChip 7830 controller. This includes
  311. adapters marketed under the DeLOCK brand.
  312. config USB_NET_RNDIS_HOST
  313. tristate "Host for RNDIS and ActiveSync devices"
  314. depends on USB_USBNET
  315. select USB_NET_CDCETHER
  316. help
  317. This option enables hosting "Remote NDIS" USB networking links,
  318. as encouraged by Microsoft (instead of CDC Ethernet!) for use in
  319. various devices that may only support this protocol. A variant
  320. of this protocol (with even less public documentation) seems to
  321. be at the root of Microsoft's "ActiveSync" too.
  322. Avoid using this protocol unless you have no better options.
  323. The protocol specification is incomplete, and is controlled by
  324. (and for) Microsoft; it isn't an "Open" ecosystem or market.
  325. config USB_NET_CDC_SUBSET
  326. tristate "Simple USB Network Links (CDC Ethernet subset)"
  327. depends on USB_USBNET
  328. default y
  329. help
  330. This driver module supports USB network devices that can work
  331. without any device-specific information. Select it if you have
  332. one of these drivers.
  333. Note that while many USB host-to-host cables can work in this mode,
  334. that may mean not being able to talk to Win32 systems or more
  335. commonly not being able to handle certain events (like replugging
  336. the host on the other end) very well. Also, these devices will
  337. not generally have permanently assigned Ethernet addresses.
  338. config USB_ALI_M5632
  339. boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
  340. depends on USB_NET_CDC_SUBSET
  341. help
  342. Choose this option if you're using a host-to-host cable
  343. based on this design, which supports USB 2.0 high speed.
  344. config USB_AN2720
  345. boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
  346. depends on USB_NET_CDC_SUBSET
  347. help
  348. Choose this option if you're using a host-to-host cable
  349. based on this design. Note that AnchorChips is now a
  350. Cypress brand.
  351. config USB_BELKIN
  352. boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
  353. depends on USB_NET_CDC_SUBSET
  354. default y
  355. help
  356. Choose this option if you're using a host-to-host cable
  357. based on this design: two NetChip 2890 chips and an Atmel
  358. microcontroller, with LEDs that indicate traffic.
  359. config USB_ARMLINUX
  360. boolean "Embedded ARM Linux links (iPaq, ...)"
  361. depends on USB_NET_CDC_SUBSET
  362. default y
  363. help
  364. Choose this option to support the "usb-eth" networking driver
  365. used by most of the ARM Linux community with device controllers
  366. such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
  367. in some PXA versions of the "blob" boot loader.
  368. Linux-based "Gumstix" PXA-25x based systems use this protocol
  369. to talk with other Linux systems.
  370. Although the ROMs shipped with Sharp Zaurus products use a
  371. different link level framing protocol, you can have them use
  372. this simpler protocol by installing a different kernel.
  373. config USB_EPSON2888
  374. boolean "Epson 2888 based firmware (DEVELOPMENT)"
  375. depends on USB_NET_CDC_SUBSET
  376. help
  377. Choose this option to support the usb networking links used
  378. by some sample firmware from Epson.
  379. config USB_KC2190
  380. boolean "KT Technology KC2190 based cables (InstaNet)"
  381. depends on USB_NET_CDC_SUBSET
  382. help
  383. Choose this option if you're using a host-to-host cable
  384. with one of these chips.
  385. config USB_NET_ZAURUS
  386. tristate "Sharp Zaurus (stock ROMs) and compatible"
  387. depends on USB_USBNET
  388. select USB_NET_CDCETHER
  389. select CRC32
  390. default y
  391. help
  392. Choose this option to support the usb networking links used by
  393. Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
  394. This also supports some related device firmware, as used in some
  395. PDAs from Olympus and some cell phones from Motorola.
  396. If you install an alternate image, such as the Linux 2.6 based
  397. versions of OpenZaurus, you should no longer need to support this
  398. protocol. Only the "eth-fd" or "net_fd" drivers in these devices
  399. really need this non-conformant variant of CDC Ethernet (or in
  400. some cases CDC MDLM) protocol, not "g_ether".
  401. config USB_NET_CX82310_ETH
  402. tristate "Conexant CX82310 USB ethernet port"
  403. depends on USB_USBNET
  404. help
  405. Choose this option if you're using a Conexant CX82310-based ADSL
  406. router with USB ethernet port. This driver is for routers only,
  407. it will not work with ADSL modems (use cxacru driver instead).
  408. config USB_NET_KALMIA
  409. tristate "Samsung Kalmia based LTE USB modem"
  410. depends on USB_USBNET
  411. help
  412. Choose this option if you have a Samsung Kalmia based USB modem
  413. as Samsung GT-B3730.
  414. To compile this driver as a module, choose M here: the
  415. module will be called kalmia.
  416. config USB_NET_QMI_WWAN
  417. tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
  418. depends on USB_USBNET
  419. select USB_WDM
  420. help
  421. Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
  422. (MDM) chipsets. Examples of such devices are
  423. * Huawei E392/E398
  424. This driver will only drive the ethernet part of the chips.
  425. The devices require additional configuration to be usable.
  426. Multiple management interfaces with linux drivers are
  427. available:
  428. * option: AT commands on /dev/ttyUSBx
  429. * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
  430. A modem manager with support for QMI is recommended.
  431. To compile this driver as a module, choose M here: the
  432. module will be called qmi_wwan.
  433. config USB_HSO
  434. tristate "Option USB High Speed Mobile Devices"
  435. depends on USB && RFKILL && TTY
  436. default n
  437. help
  438. Choose this option if you have an Option HSDPA/HSUPA card.
  439. These cards support downlink speeds of 7.2Mbps or greater.
  440. To compile this driver as a module, choose M here: the
  441. module will be called hso.
  442. config USB_NET_INT51X1
  443. tristate "Intellon PLC based usb adapter"
  444. depends on USB_USBNET
  445. help
  446. Choose this option if you're using a 14Mb USB-based PLC
  447. (Powerline Communications) solution with an Intellon
  448. INT51x1/INT5200 chip, like the "devolo dLan duo".
  449. config USB_CDC_PHONET
  450. tristate "CDC Phonet support"
  451. depends on PHONET
  452. help
  453. Choose this option to support the Phonet interface to a Nokia
  454. cellular modem, as found on most Nokia handsets with the
  455. "PC suite" USB profile.
  456. config USB_IPHETH
  457. tristate "Apple iPhone USB Ethernet driver"
  458. default n
  459. ---help---
  460. Module used to share Internet connection (tethering) from your
  461. iPhone (Original, 3G and 3GS) to your system.
  462. Note that you need userspace libraries and programs that are needed
  463. to pair your device with your system and that understand the iPhone
  464. protocol.
  465. For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
  466. config USB_SIERRA_NET
  467. tristate "USB-to-WWAN Driver for Sierra Wireless modems"
  468. depends on USB_USBNET
  469. help
  470. Choose this option if you have a Sierra Wireless USB-to-WWAN device.
  471. To compile this driver as a module, choose M here: the
  472. module will be called sierra_net.
  473. config USB_VL600
  474. tristate "LG VL600 modem dongle"
  475. depends on USB_NET_CDCETHER && TTY
  476. select USB_ACM
  477. help
  478. Select this if you want to use an LG Electronics 4G/LTE usb modem
  479. called VL600. This driver only handles the ethernet
  480. interface exposed by the modem firmware. To establish a connection
  481. you will first need a userspace program that sends the right
  482. command to the modem through its CDC ACM port, and most
  483. likely also a DHCP client. See this thread about using the
  484. 4G modem from Verizon:
  485. http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
  486. endif # USB_NET_DRIVERS