2 # USB Network devices configuration
4 comment "Host-side USB support is needed for USB Network Adapter support"
7 menuconfig USB_NET_DRIVERS
8 tristate "USB Network Adapters"
15 tristate "USB CATC NetMate-based Ethernet device support"
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:
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.
30 To compile this driver as a module, choose M here: the
31 module will be called catc.
34 tristate "USB KLSI KL5USB101-based ethernet device support"
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:
41 ASANTE USB To Ethernet Adapter
42 AOX Endpoints USB Ethernet
44 D-Link DSB-650C and DU-E10
45 Entrega / Portgear E45
47 Jaton USB Ethernet Device Adapter
48 Kingston Technology USB Ethernet Adapter
50 Mobility USB-Ethernet Adapter
52 Peracom Enet and Enet2
53 Portsmith Express Ethernet Adapter
56 Sony Vaio port extender
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
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.
69 To compile this driver as a module, choose M here: the
70 module will be called kaweth.
73 tristate "USB Pegasus/Pegasus-II based ethernet device support"
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.
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.
84 To compile this driver as a module, choose M here: the
85 module will be called pegasus.
88 tristate "USB RTL8150 based ethernet device support"
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/>.
95 To compile this driver as a module, choose M here: the
96 module will be called rtl8150.
99 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
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
106 To compile this driver as a module, choose M here: the
107 module will be called r8152.
110 tristate "Microchip LAN78XX Based USB Ethernet Adapters"
116 This option adds support for Microchip LAN78XX based USB 2
117 & USB 3 10/100/1000 Ethernet adapters.
118 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
119 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
120 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
122 Proper PHY driver is required for LAN7801.
124 To compile this driver as a module, choose M here: the
125 module will be called lan78xx.
128 tristate "Multi-purpose USB Networking Framework"
131 This driver supports several kinds of network links over USB,
132 with "minidrivers" built around a common network driver core
133 that supports deep queues for efficient transfers. (This gives
134 better performance with small packets and at high speeds).
136 The USB host runs "usbnet", and the other end of the link might be:
138 - Another USB host, when using USB "network" or "data transfer"
139 cables. These are often used to network laptops to PCs, like
140 "Laplink" parallel cables or some motherboards. These rely
141 on specialized chips from many suppliers.
143 - An intelligent USB gadget, perhaps embedding a Linux system.
144 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
145 others), and devices that interoperate using the standard
146 CDC-Ethernet specification (including many cable modems).
148 - Network adapter hardware (like those for 10/100 Ethernet) which
149 uses this driver framework.
151 The link will appear with a name like "usb0", when the link is
152 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
153 two-node links are most easily managed with Ethernet Bridging
154 (CONFIG_BRIDGE) instead of routing.
156 For more information see <http://www.linux-usb.org/usbnet/>.
158 To compile this driver as a module, choose M here: the
159 module will be called usbnet.
161 config USB_NET_AX8817X
162 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
163 depends on USB_USBNET
168 This option adds support for ASIX AX88xxx based USB 2.0
169 10/100 Ethernet adapters.
171 This driver should work with at least the following devices:
174 * Billionton Systems, USB2AR
175 * Billionton Systems, GUSB2AM-1G-B
177 * Corega FEther USB2-TX
184 * Intellinet USB 2.0 Ethernet
185 * ST Lab USB 2.0 Ethernet
188 This driver creates an interface named "ethX", where X depends on
189 what other networking devices you have in use.
191 config USB_NET_AX88179_178A
192 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
193 depends on USB_USBNET
198 This option adds support for ASIX AX88179 based USB 3.0/2.0
199 to Gigabit Ethernet adapters.
201 This driver should work with at least the following devices:
206 This driver creates an interface named "ethX", where X depends on
207 what other networking devices you have in use.
209 config USB_NET_CDCETHER
210 tristate "CDC Ethernet support (smart devices such as cable modems)"
211 depends on USB_USBNET
214 This option supports devices conforming to the Communication Device
215 Class (CDC) Ethernet Control Model, a specification that's easy to
216 implement in device firmware. The CDC specifications are available
217 from <http://www.usb.org/>.
219 CDC Ethernet is an implementation option for DOCSIS cable modems
220 that support USB connectivity, used for non-Microsoft USB hosts.
221 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
222 This driver should work with at least the following devices:
224 * Dell Wireless 5530 HSPA
225 * Ericsson PipeRider (all variants)
226 * Ericsson Mobile Broadband Module (all variants)
227 * Motorola (DM100 and SB4100)
228 * Broadcom Cable Modem (reference design)
229 * Toshiba (PCX1100U and F3507g/F3607gw)
232 This driver creates an interface named "ethX", where X depends on
233 what other networking devices you have in use. However, if the
234 IEEE 802 "local assignment" bit is set in the address, a "usbX"
235 name is used instead.
237 config USB_NET_CDC_EEM
238 tristate "CDC EEM support"
239 depends on USB_USBNET
241 This option supports devices conforming to the Communication Device
242 Class (CDC) Ethernet Emulation Model, a specification that's easy to
243 implement in device firmware. The CDC EEM specifications are available
244 from <http://www.usb.org/>.
246 This driver creates an interface named "ethX", where X depends on
247 what other networking devices you have in use. However, if the
248 IEEE 802 "local assignment" bit is set in the address, a "usbX"
249 name is used instead.
251 config USB_NET_CDC_NCM
252 tristate "CDC NCM support"
253 depends on USB_USBNET
256 This driver provides support for CDC NCM (Network Control Model
257 Device USB Class Specification). The CDC NCM specification is
258 available from <http://www.usb.org/>.
260 Say "y" to link the driver statically, or "m" to build a
261 dynamically linked module.
263 This driver should work with at least the following devices:
264 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
265 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
266 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
267 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
268 * Ericsson F5521gw Mobile Broadband Module
270 config USB_NET_HUAWEI_CDC_NCM
271 tristate "Huawei NCM embedded AT channel support"
272 depends on USB_USBNET
274 select USB_NET_CDC_NCM
276 This driver supports huawei-style NCM devices, that use NCM as a
277 transport for other protocols, usually an embedded AT channel.
282 To compile this driver as a module, choose M here: the module will be
283 called huawei_cdc_ncm.ko.
285 config USB_NET_CDC_MBIM
286 tristate "CDC MBIM support"
287 depends on USB_USBNET
289 select USB_NET_CDC_NCM
291 This driver provides support for CDC MBIM (Mobile Broadband
292 Interface Model) devices. The CDC MBIM specification is
293 available from <http://www.usb.org/>.
295 MBIM devices require configuration using the management
296 protocol defined by the MBIM specification. This driver
297 provides unfiltered access to the MBIM control channel
298 through the associated /dev/cdc-wdmx character device.
300 To compile this driver as a module, choose M here: the
301 module will be called cdc_mbim.
303 config USB_NET_DM9601
304 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
305 depends on USB_USBNET
308 This option adds support for Davicom DM9601/DM9620/DM9621A
309 based USB 10/100 Ethernet adapters.
311 config USB_NET_SR9700
312 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
313 depends on USB_USBNET
316 This option adds support for CoreChip-sz SR9700 based USB 1.1
317 10/100 Ethernet adapters.
319 config USB_NET_SR9800
320 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
321 depends on USB_USBNET
324 Say Y if you want to use one of the following 100Mbps USB Ethernet
325 device based on the CoreChip-sz SR9800 chip.
327 This driver makes the adapter appear as a normal Ethernet interface,
328 typically on eth0, if it is the only ethernet device, or perhaps on
329 eth1, if you have a PCI or ISA ethernet card installed.
331 To compile this driver as a module, choose M here: the
332 module will be called sr9800.
334 config USB_NET_SMSC75XX
335 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
336 depends on USB_USBNET
341 This option adds support for SMSC LAN75XX based USB 2.0
342 Gigabit Ethernet adapters.
344 config USB_NET_SMSC95XX
345 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
346 depends on USB_USBNET
351 This option adds support for SMSC LAN95XX based USB 2.0
352 10/100 Ethernet adapters.
354 config USB_NET_GL620A
355 tristate "GeneSys GL620USB-A based cables"
356 depends on USB_USBNET
358 Choose this option if you're using a host-to-host cable,
359 or PC2PC motherboard, with this chip.
361 Note that the half-duplex "GL620USB" is not supported.
363 config USB_NET_NET1080
364 tristate "NetChip 1080 based cables (Laplink, ...)"
366 depends on USB_USBNET
368 Choose this option if you're using a host-to-host cable based
369 on this design: one NetChip 1080 chip and supporting logic,
370 optionally with LEDs that indicate traffic
373 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
374 # if the handshake/init/reset problems, from original 'plusb',
375 # are ever resolved ... then remove "experimental"
376 depends on USB_USBNET
378 Choose this option if you're using a host-to-host cable
379 with one of these chips.
381 config USB_NET_MCS7830
382 tristate "MosChip MCS7830 based Ethernet adapters"
383 depends on USB_USBNET
385 Choose this option if you're using a 10/100 Ethernet USB2
386 adapter based on the MosChip 7830 controller. This includes
387 adapters marketed under the DeLOCK brand.
389 config USB_NET_RNDIS_HOST
390 tristate "Host for RNDIS and ActiveSync devices"
391 depends on USB_USBNET
392 select USB_NET_CDCETHER
394 This option enables hosting "Remote NDIS" USB networking links,
395 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
396 various devices that may only support this protocol. A variant
397 of this protocol (with even less public documentation) seems to
398 be at the root of Microsoft's "ActiveSync" too.
400 Avoid using this protocol unless you have no better options.
401 The protocol specification is incomplete, and is controlled by
402 (and for) Microsoft; it isn't an "Open" ecosystem or market.
404 config USB_NET_CDC_SUBSET_ENABLE
406 depends on USB_NET_CDC_SUBSET
408 config USB_NET_CDC_SUBSET
409 tristate "Simple USB Network Links (CDC Ethernet subset)"
410 depends on USB_USBNET
413 This driver module supports USB network devices that can work
414 without any device-specific information. Select it if you have
415 one of these drivers.
417 Note that while many USB host-to-host cables can work in this mode,
418 that may mean not being able to talk to Win32 systems or more
419 commonly not being able to handle certain events (like replugging
420 the host on the other end) very well. Also, these devices will
421 not generally have permanently assigned Ethernet addresses.
424 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
425 depends on USB_NET_CDC_SUBSET
426 select USB_NET_CDC_SUBSET_ENABLE
428 Choose this option if you're using a host-to-host cable
429 based on this design, which supports USB 2.0 high speed.
432 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
433 depends on USB_NET_CDC_SUBSET
434 select USB_NET_CDC_SUBSET_ENABLE
436 Choose this option if you're using a host-to-host cable
437 based on this design. Note that AnchorChips is now a
441 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
442 depends on USB_NET_CDC_SUBSET
443 select USB_NET_CDC_SUBSET_ENABLE
446 Choose this option if you're using a host-to-host cable
447 based on this design: two NetChip 2890 chips and an Atmel
448 microcontroller, with LEDs that indicate traffic.
451 bool "Embedded ARM Linux links (iPaq, ...)"
452 depends on USB_NET_CDC_SUBSET
453 select USB_NET_CDC_SUBSET_ENABLE
456 Choose this option to support the "usb-eth" networking driver
457 used by most of the ARM Linux community with device controllers
458 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
459 in some PXA versions of the "blob" boot loader.
461 Linux-based "Gumstix" PXA-25x based systems use this protocol
462 to talk with other Linux systems.
464 Although the ROMs shipped with Sharp Zaurus products use a
465 different link level framing protocol, you can have them use
466 this simpler protocol by installing a different kernel.
469 bool "Epson 2888 based firmware (DEVELOPMENT)"
470 depends on USB_NET_CDC_SUBSET
471 select USB_NET_CDC_SUBSET_ENABLE
473 Choose this option to support the usb networking links used
474 by some sample firmware from Epson.
477 bool "KT Technology KC2190 based cables (InstaNet)"
478 depends on USB_NET_CDC_SUBSET
479 select USB_NET_CDC_SUBSET_ENABLE
481 Choose this option if you're using a host-to-host cable
482 with one of these chips.
484 config USB_NET_ZAURUS
485 tristate "Sharp Zaurus (stock ROMs) and compatible"
486 depends on USB_USBNET
487 select USB_NET_CDCETHER
491 Choose this option to support the usb networking links used by
492 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
493 This also supports some related device firmware, as used in some
494 PDAs from Olympus and some cell phones from Motorola.
496 If you install an alternate image, such as the Linux 2.6 based
497 versions of OpenZaurus, you should no longer need to support this
498 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
499 really need this non-conformant variant of CDC Ethernet (or in
500 some cases CDC MDLM) protocol, not "g_ether".
502 config USB_NET_CX82310_ETH
503 tristate "Conexant CX82310 USB ethernet port"
504 depends on USB_USBNET
506 Choose this option if you're using a Conexant CX82310-based ADSL
507 router with USB ethernet port. This driver is for routers only,
508 it will not work with ADSL modems (use cxacru driver instead).
510 config USB_NET_KALMIA
511 tristate "Samsung Kalmia based LTE USB modem"
512 depends on USB_USBNET
514 Choose this option if you have a Samsung Kalmia based USB modem
517 To compile this driver as a module, choose M here: the
518 module will be called kalmia.
520 config USB_NET_QMI_WWAN
521 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
522 depends on USB_USBNET
525 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
526 (MDM) chipsets. Examples of such devices are
529 This driver will only drive the ethernet part of the chips.
530 The devices require additional configuration to be usable.
531 Multiple management interfaces with linux drivers are
534 * option: AT commands on /dev/ttyUSBx
535 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
537 A modem manager with support for QMI is recommended.
539 To compile this driver as a module, choose M here: the
540 module will be called qmi_wwan.
543 tristate "Option USB High Speed Mobile Devices"
544 depends on USB && RFKILL && TTY
547 Choose this option if you have an Option HSDPA/HSUPA card.
548 These cards support downlink speeds of 7.2Mbps or greater.
550 To compile this driver as a module, choose M here: the
551 module will be called hso.
553 config USB_NET_INT51X1
554 tristate "Intellon PLC based usb adapter"
555 depends on USB_USBNET
557 Choose this option if you're using a 14Mb USB-based PLC
558 (Powerline Communications) solution with an Intellon
559 INT51x1/INT5200 chip, like the "devolo dLan duo".
561 config USB_CDC_PHONET
562 tristate "CDC Phonet support"
563 depends on PHONET && USB_USBNET
565 Choose this option to support the Phonet interface to a Nokia
566 cellular modem, as found on most Nokia handsets with the
567 "PC suite" USB profile.
570 tristate "Apple iPhone USB Ethernet driver"
573 Module used to share Internet connection (tethering) from your
574 iPhone (Original, 3G and 3GS) to your system.
575 Note that you need userspace libraries and programs that are needed
576 to pair your device with your system and that understand the iPhone
579 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
581 config USB_SIERRA_NET
582 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
583 depends on USB_USBNET
585 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
587 To compile this driver as a module, choose M here: the
588 module will be called sierra_net.
591 tristate "LG VL600 modem dongle"
592 depends on USB_NET_CDCETHER && TTY
595 Select this if you want to use an LG Electronics 4G/LTE usb modem
596 called VL600. This driver only handles the ethernet
597 interface exposed by the modem firmware. To establish a connection
598 you will first need a userspace program that sends the right
599 command to the modem through its CDC ACM port, and most
600 likely also a DHCP client. See this thread about using the
601 4G modem from Verizon:
603 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
605 config USB_NET_CH9200
606 tristate "QingHeng CH9200 USB ethernet support"
607 depends on USB_USBNET
610 Choose this option if you have a USB ethernet adapter with a QinHeng
613 To compile this driver as a module, choose M here: the
614 module will be called ch9200.
616 config USB_NET_AQC111
617 tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
618 depends on USB_USBNET
621 This option adds support for Aquantia AQtion USB
622 Ethernet adapters based on AQC111U/AQC112 chips.
624 This driver should work with at least the following devices:
625 * Aquantia AQtion USB to 5GbE
627 endif # USB_NET_DRIVERS