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"
106 This option adds support for Realtek RTL8152 based USB 2.0
107 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
110 To compile this driver as a module, choose M here: the
111 module will be called r8152.
114 tristate "Microchip LAN78XX Based USB Ethernet Adapters"
119 This option adds support for Microchip LAN78XX based USB 2
120 & USB 3 10/100/1000 Ethernet adapters.
121 LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
122 LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
123 LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
125 Proper PHY driver is required for LAN7801.
127 To compile this driver as a module, choose M here: the
128 module will be called lan78xx.
131 tristate "Multi-purpose USB Networking Framework"
134 This driver supports several kinds of network links over USB,
135 with "minidrivers" built around a common network driver core
136 that supports deep queues for efficient transfers. (This gives
137 better performance with small packets and at high speeds).
139 The USB host runs "usbnet", and the other end of the link might be:
141 - Another USB host, when using USB "network" or "data transfer"
142 cables. These are often used to network laptops to PCs, like
143 "Laplink" parallel cables or some motherboards. These rely
144 on specialized chips from many suppliers.
146 - An intelligent USB gadget, perhaps embedding a Linux system.
147 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
148 others), and devices that interoperate using the standard
149 CDC-Ethernet specification (including many cable modems).
151 - Network adapter hardware (like those for 10/100 Ethernet) which
152 uses this driver framework.
154 The link will appear with a name like "usb0", when the link is
155 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
156 two-node links are most easily managed with Ethernet Bridging
157 (CONFIG_BRIDGE) instead of routing.
159 For more information see <http://www.linux-usb.org/usbnet/>.
161 To compile this driver as a module, choose M here: the
162 module will be called usbnet.
164 config USB_NET_AX8817X
165 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
166 depends on USB_USBNET
171 This option adds support for ASIX AX88xxx based USB 2.0
172 10/100 Ethernet adapters.
174 This driver should work with at least the following devices:
177 * Billionton Systems, USB2AR
178 * Billionton Systems, GUSB2AM-1G-B
180 * Corega FEther USB2-TX
187 * Intellinet USB 2.0 Ethernet
188 * ST Lab USB 2.0 Ethernet
191 This driver creates an interface named "ethX", where X depends on
192 what other networking devices you have in use.
194 config USB_NET_AX88179_178A
195 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
196 depends on USB_USBNET
201 This option adds support for ASIX AX88179 based USB 3.0/2.0
202 to Gigabit Ethernet adapters.
204 This driver should work with at least the following devices:
209 This driver creates an interface named "ethX", where X depends on
210 what other networking devices you have in use.
212 config USB_NET_CDCETHER
213 tristate "CDC Ethernet support (smart devices such as cable modems)"
214 depends on USB_USBNET
217 This option supports devices conforming to the Communication Device
218 Class (CDC) Ethernet Control Model, a specification that's easy to
219 implement in device firmware. The CDC specifications are available
220 from <http://www.usb.org/>.
222 CDC Ethernet is an implementation option for DOCSIS cable modems
223 that support USB connectivity, used for non-Microsoft USB hosts.
224 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
225 This driver should work with at least the following devices:
227 * Dell Wireless 5530 HSPA
228 * Ericsson PipeRider (all variants)
229 * Ericsson Mobile Broadband Module (all variants)
230 * Motorola (DM100 and SB4100)
231 * Broadcom Cable Modem (reference design)
232 * Toshiba (PCX1100U and F3507g/F3607gw)
235 This driver creates an interface named "ethX", where X depends on
236 what other networking devices you have in use. However, if the
237 IEEE 802 "local assignment" bit is set in the address, a "usbX"
238 name is used instead.
240 config USB_NET_CDC_EEM
241 tristate "CDC EEM support"
242 depends on USB_USBNET
244 This option supports devices conforming to the Communication Device
245 Class (CDC) Ethernet Emulation Model, a specification that's easy to
246 implement in device firmware. The CDC EEM specifications are available
247 from <http://www.usb.org/>.
249 This driver creates an interface named "ethX", where X depends on
250 what other networking devices you have in use. However, if the
251 IEEE 802 "local assignment" bit is set in the address, a "usbX"
252 name is used instead.
254 config USB_NET_CDC_NCM
255 tristate "CDC NCM support"
256 depends on USB_USBNET
259 This driver provides support for CDC NCM (Network Control Model
260 Device USB Class Specification). The CDC NCM specification is
261 available from <http://www.usb.org/>.
263 Say "y" to link the driver statically, or "m" to build a
264 dynamically linked module.
266 This driver should work with at least the following devices:
267 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
268 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
269 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
270 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
271 * Ericsson F5521gw Mobile Broadband Module
273 config USB_NET_HUAWEI_CDC_NCM
274 tristate "Huawei NCM embedded AT channel support"
275 depends on USB_USBNET
277 select USB_NET_CDC_NCM
279 This driver supports huawei-style NCM devices, that use NCM as a
280 transport for other protocols, usually an embedded AT channel.
285 To compile this driver as a module, choose M here: the module will be
286 called huawei_cdc_ncm.ko.
288 config USB_NET_CDC_MBIM
289 tristate "CDC MBIM support"
290 depends on USB_USBNET
292 select USB_NET_CDC_NCM
294 This driver provides support for CDC MBIM (Mobile Broadband
295 Interface Model) devices. The CDC MBIM specification is
296 available from <http://www.usb.org/>.
298 MBIM devices require configuration using the management
299 protocol defined by the MBIM specification. This driver
300 provides unfiltered access to the MBIM control channel
301 through the associated /dev/cdc-wdmx character device.
303 To compile this driver as a module, choose M here: the
304 module will be called cdc_mbim.
306 config USB_NET_DM9601
307 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
308 depends on USB_USBNET
311 This option adds support for Davicom DM9601/DM9620/DM9621A
312 based USB 10/100 Ethernet adapters.
314 config USB_NET_SR9700
315 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
316 depends on USB_USBNET
319 This option adds support for CoreChip-sz SR9700 based USB 1.1
320 10/100 Ethernet adapters.
322 config USB_NET_SR9800
323 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
324 depends on USB_USBNET
327 Say Y if you want to use one of the following 100Mbps USB Ethernet
328 device based on the CoreChip-sz SR9800 chip.
330 This driver makes the adapter appear as a normal Ethernet interface,
331 typically on eth0, if it is the only ethernet device, or perhaps on
332 eth1, if you have a PCI or ISA ethernet card installed.
334 To compile this driver as a module, choose M here: the
335 module will be called sr9800.
337 config USB_NET_SMSC75XX
338 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
339 depends on USB_USBNET
344 This option adds support for SMSC LAN75XX based USB 2.0
345 Gigabit Ethernet adapters.
347 config USB_NET_SMSC95XX
348 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
349 depends on USB_USBNET
354 This option adds support for SMSC LAN95XX based USB 2.0
355 10/100 Ethernet adapters.
357 config USB_NET_GL620A
358 tristate "GeneSys GL620USB-A based cables"
359 depends on USB_USBNET
361 Choose this option if you're using a host-to-host cable,
362 or PC2PC motherboard, with this chip.
364 Note that the half-duplex "GL620USB" is not supported.
366 config USB_NET_NET1080
367 tristate "NetChip 1080 based cables (Laplink, ...)"
369 depends on USB_USBNET
371 Choose this option if you're using a host-to-host cable based
372 on this design: one NetChip 1080 chip and supporting logic,
373 optionally with LEDs that indicate traffic
376 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
377 # if the handshake/init/reset problems, from original 'plusb',
378 # are ever resolved ... then remove "experimental"
379 depends on USB_USBNET
381 Choose this option if you're using a host-to-host cable
382 with one of these chips.
384 config USB_NET_MCS7830
385 tristate "MosChip MCS7830 based Ethernet adapters"
386 depends on USB_USBNET
388 Choose this option if you're using a 10/100 Ethernet USB2
389 adapter based on the MosChip 7830 controller. This includes
390 adapters marketed under the DeLOCK brand.
392 config USB_NET_RNDIS_HOST
393 tristate "Host for RNDIS and ActiveSync devices"
394 depends on USB_USBNET
395 select USB_NET_CDCETHER
397 This option enables hosting "Remote NDIS" USB networking links,
398 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
399 various devices that may only support this protocol. A variant
400 of this protocol (with even less public documentation) seems to
401 be at the root of Microsoft's "ActiveSync" too.
403 Avoid using this protocol unless you have no better options.
404 The protocol specification is incomplete, and is controlled by
405 (and for) Microsoft; it isn't an "Open" ecosystem or market.
407 config USB_NET_CDC_SUBSET_ENABLE
409 depends on USB_NET_CDC_SUBSET
411 config USB_NET_CDC_SUBSET
412 tristate "Simple USB Network Links (CDC Ethernet subset)"
413 depends on USB_USBNET
416 This driver module supports USB network devices that can work
417 without any device-specific information. Select it if you have
418 one of these drivers.
420 Note that while many USB host-to-host cables can work in this mode,
421 that may mean not being able to talk to Win32 systems or more
422 commonly not being able to handle certain events (like replugging
423 the host on the other end) very well. Also, these devices will
424 not generally have permanently assigned Ethernet addresses.
427 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
428 depends on USB_NET_CDC_SUBSET
429 select USB_NET_CDC_SUBSET_ENABLE
431 Choose this option if you're using a host-to-host cable
432 based on this design, which supports USB 2.0 high speed.
435 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
436 depends on USB_NET_CDC_SUBSET
437 select USB_NET_CDC_SUBSET_ENABLE
439 Choose this option if you're using a host-to-host cable
440 based on this design. Note that AnchorChips is now a
444 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
445 depends on USB_NET_CDC_SUBSET
446 select USB_NET_CDC_SUBSET_ENABLE
449 Choose this option if you're using a host-to-host cable
450 based on this design: two NetChip 2890 chips and an Atmel
451 microcontroller, with LEDs that indicate traffic.
454 bool "Embedded ARM Linux links (iPaq, ...)"
455 depends on USB_NET_CDC_SUBSET
456 select USB_NET_CDC_SUBSET_ENABLE
459 Choose this option to support the "usb-eth" networking driver
460 used by most of the ARM Linux community with device controllers
461 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
462 in some PXA versions of the "blob" boot loader.
464 Linux-based "Gumstix" PXA-25x based systems use this protocol
465 to talk with other Linux systems.
467 Although the ROMs shipped with Sharp Zaurus products use a
468 different link level framing protocol, you can have them use
469 this simpler protocol by installing a different kernel.
472 bool "Epson 2888 based firmware (DEVELOPMENT)"
473 depends on USB_NET_CDC_SUBSET
474 select USB_NET_CDC_SUBSET_ENABLE
476 Choose this option to support the usb networking links used
477 by some sample firmware from Epson.
480 bool "KT Technology KC2190 based cables (InstaNet)"
481 depends on USB_NET_CDC_SUBSET
482 select USB_NET_CDC_SUBSET_ENABLE
484 Choose this option if you're using a host-to-host cable
485 with one of these chips.
487 config USB_NET_ZAURUS
488 tristate "Sharp Zaurus (stock ROMs) and compatible"
489 depends on USB_USBNET
490 select USB_NET_CDCETHER
494 Choose this option to support the usb networking links used by
495 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
496 This also supports some related device firmware, as used in some
497 PDAs from Olympus and some cell phones from Motorola.
499 If you install an alternate image, such as the Linux 2.6 based
500 versions of OpenZaurus, you should no longer need to support this
501 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
502 really need this non-conformant variant of CDC Ethernet (or in
503 some cases CDC MDLM) protocol, not "g_ether".
505 config USB_NET_CX82310_ETH
506 tristate "Conexant CX82310 USB ethernet port"
507 depends on USB_USBNET
509 Choose this option if you're using a Conexant CX82310-based ADSL
510 router with USB ethernet port. This driver is for routers only,
511 it will not work with ADSL modems (use cxacru driver instead).
513 config USB_NET_KALMIA
514 tristate "Samsung Kalmia based LTE USB modem"
515 depends on USB_USBNET
517 Choose this option if you have a Samsung Kalmia based USB modem
520 To compile this driver as a module, choose M here: the
521 module will be called kalmia.
523 config USB_NET_QMI_WWAN
524 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
525 depends on USB_USBNET
528 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
529 (MDM) chipsets. Examples of such devices are
532 This driver will only drive the ethernet part of the chips.
533 The devices require additional configuration to be usable.
534 Multiple management interfaces with linux drivers are
537 * option: AT commands on /dev/ttyUSBx
538 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
540 A modem manager with support for QMI is recommended.
542 To compile this driver as a module, choose M here: the
543 module will be called qmi_wwan.
546 tristate "Option USB High Speed Mobile Devices"
547 depends on USB && RFKILL && TTY
550 Choose this option if you have an Option HSDPA/HSUPA card.
551 These cards support downlink speeds of 7.2Mbps or greater.
553 To compile this driver as a module, choose M here: the
554 module will be called hso.
556 config USB_NET_INT51X1
557 tristate "Intellon PLC based usb adapter"
558 depends on USB_USBNET
560 Choose this option if you're using a 14Mb USB-based PLC
561 (Powerline Communications) solution with an Intellon
562 INT51x1/INT5200 chip, like the "devolo dLan duo".
564 config USB_CDC_PHONET
565 tristate "CDC Phonet support"
566 depends on PHONET && USB_USBNET
568 Choose this option to support the Phonet interface to a Nokia
569 cellular modem, as found on most Nokia handsets with the
570 "PC suite" USB profile.
573 tristate "Apple iPhone USB Ethernet driver"
576 Module used to share Internet connection (tethering) from your
577 iPhone (Original, 3G and 3GS) to your system.
578 Note that you need userspace libraries and programs that are needed
579 to pair your device with your system and that understand the iPhone
582 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
584 config USB_SIERRA_NET
585 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
586 depends on USB_USBNET
588 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
590 To compile this driver as a module, choose M here: the
591 module will be called sierra_net.
594 tristate "LG VL600 modem dongle"
595 depends on USB_NET_CDCETHER && TTY
598 Select this if you want to use an LG Electronics 4G/LTE usb modem
599 called VL600. This driver only handles the ethernet
600 interface exposed by the modem firmware. To establish a connection
601 you will first need a userspace program that sends the right
602 command to the modem through its CDC ACM port, and most
603 likely also a DHCP client. See this thread about using the
604 4G modem from Verizon:
606 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
608 config USB_NET_CH9200
609 tristate "QingHeng CH9200 USB ethernet support"
610 depends on USB_USBNET
613 Choose this option if you have a USB ethernet adapter with a QinHeng
616 To compile this driver as a module, choose M here: the
617 module will be called ch9200.
619 endif # USB_NET_DRIVERS