Kconfig 20 KB

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