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