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.
122 To compile this driver as a module, choose M here: the
123 module will be called lan78xx.
126 tristate "Multi-purpose USB Networking Framework"
129 This driver supports several kinds of network links over USB,
130 with "minidrivers" built around a common network driver core
131 that supports deep queues for efficient transfers. (This gives
132 better performance with small packets and at high speeds).
134 The USB host runs "usbnet", and the other end of the link might be:
136 - Another USB host, when using USB "network" or "data transfer"
137 cables. These are often used to network laptops to PCs, like
138 "Laplink" parallel cables or some motherboards. These rely
139 on specialized chips from many suppliers.
141 - An intelligent USB gadget, perhaps embedding a Linux system.
142 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
143 others), and devices that interoperate using the standard
144 CDC-Ethernet specification (including many cable modems).
146 - Network adapter hardware (like those for 10/100 Ethernet) which
147 uses this driver framework.
149 The link will appear with a name like "usb0", when the link is
150 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
151 two-node links are most easily managed with Ethernet Bridging
152 (CONFIG_BRIDGE) instead of routing.
154 For more information see <http://www.linux-usb.org/usbnet/>.
156 To compile this driver as a module, choose M here: the
157 module will be called usbnet.
159 config USB_NET_AX8817X
160 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
161 depends on USB_USBNET
166 This option adds support for ASIX AX88xxx based USB 2.0
167 10/100 Ethernet adapters.
169 This driver should work with at least the following devices:
172 * Billionton Systems, USB2AR
173 * Billionton Systems, GUSB2AM-1G-B
175 * Corega FEther USB2-TX
182 * Intellinet USB 2.0 Ethernet
183 * ST Lab USB 2.0 Ethernet
186 This driver creates an interface named "ethX", where X depends on
187 what other networking devices you have in use.
189 config USB_NET_AX88179_178A
190 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
191 depends on USB_USBNET
196 This option adds support for ASIX AX88179 based USB 3.0/2.0
197 to Gigabit Ethernet adapters.
199 This driver should work with at least the following devices:
204 This driver creates an interface named "ethX", where X depends on
205 what other networking devices you have in use.
207 config USB_NET_CDCETHER
208 tristate "CDC Ethernet support (smart devices such as cable modems)"
209 depends on USB_USBNET
212 This option supports devices conforming to the Communication Device
213 Class (CDC) Ethernet Control Model, a specification that's easy to
214 implement in device firmware. The CDC specifications are available
215 from <http://www.usb.org/>.
217 CDC Ethernet is an implementation option for DOCSIS cable modems
218 that support USB connectivity, used for non-Microsoft USB hosts.
219 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
220 This driver should work with at least the following devices:
222 * Dell Wireless 5530 HSPA
223 * Ericsson PipeRider (all variants)
224 * Ericsson Mobile Broadband Module (all variants)
225 * Motorola (DM100 and SB4100)
226 * Broadcom Cable Modem (reference design)
227 * Toshiba (PCX1100U and F3507g/F3607gw)
230 This driver creates an interface named "ethX", where X depends on
231 what other networking devices you have in use. However, if the
232 IEEE 802 "local assignment" bit is set in the address, a "usbX"
233 name is used instead.
235 config USB_NET_CDC_EEM
236 tristate "CDC EEM support"
237 depends on USB_USBNET
239 This option supports devices conforming to the Communication Device
240 Class (CDC) Ethernet Emulation Model, a specification that's easy to
241 implement in device firmware. The CDC EEM specifications are available
242 from <http://www.usb.org/>.
244 This driver creates an interface named "ethX", where X depends on
245 what other networking devices you have in use. However, if the
246 IEEE 802 "local assignment" bit is set in the address, a "usbX"
247 name is used instead.
249 config USB_NET_CDC_NCM
250 tristate "CDC NCM support"
251 depends on USB_USBNET
254 This driver provides support for CDC NCM (Network Control Model
255 Device USB Class Specification). The CDC NCM specification is
256 available from <http://www.usb.org/>.
258 Say "y" to link the driver statically, or "m" to build a
259 dynamically linked module.
261 This driver should work with at least the following devices:
262 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
263 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
264 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
265 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
266 * Ericsson F5521gw Mobile Broadband Module
268 config USB_NET_HUAWEI_CDC_NCM
269 tristate "Huawei NCM embedded AT channel support"
270 depends on USB_USBNET
272 select USB_NET_CDC_NCM
274 This driver supports huawei-style NCM devices, that use NCM as a
275 transport for other protocols, usually an embedded AT channel.
280 To compile this driver as a module, choose M here: the module will be
281 called huawei_cdc_ncm.ko.
283 config USB_NET_CDC_MBIM
284 tristate "CDC MBIM support"
285 depends on USB_USBNET
287 select USB_NET_CDC_NCM
289 This driver provides support for CDC MBIM (Mobile Broadband
290 Interface Model) devices. The CDC MBIM specification is
291 available from <http://www.usb.org/>.
293 MBIM devices require configuration using the management
294 protocol defined by the MBIM specification. This driver
295 provides unfiltered access to the MBIM control channel
296 through the associated /dev/cdc-wdmx character device.
298 To compile this driver as a module, choose M here: the
299 module will be called cdc_mbim.
301 config USB_NET_DM9601
302 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
303 depends on USB_USBNET
306 This option adds support for Davicom DM9601/DM9620/DM9621A
307 based USB 10/100 Ethernet adapters.
309 config USB_NET_SR9700
310 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
311 depends on USB_USBNET
314 This option adds support for CoreChip-sz SR9700 based USB 1.1
315 10/100 Ethernet adapters.
317 config USB_NET_SR9800
318 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
319 depends on USB_USBNET
322 Say Y if you want to use one of the following 100Mbps USB Ethernet
323 device based on the CoreChip-sz SR9800 chip.
325 This driver makes the adapter appear as a normal Ethernet interface,
326 typically on eth0, if it is the only ethernet device, or perhaps on
327 eth1, if you have a PCI or ISA ethernet card installed.
329 To compile this driver as a module, choose M here: the
330 module will be called sr9800.
332 config USB_NET_SMSC75XX
333 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
334 depends on USB_USBNET
339 This option adds support for SMSC LAN75XX based USB 2.0
340 Gigabit Ethernet adapters.
342 config USB_NET_SMSC95XX
343 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
344 depends on USB_USBNET
349 This option adds support for SMSC LAN95XX based USB 2.0
350 10/100 Ethernet adapters.
352 config USB_NET_GL620A
353 tristate "GeneSys GL620USB-A based cables"
354 depends on USB_USBNET
356 Choose this option if you're using a host-to-host cable,
357 or PC2PC motherboard, with this chip.
359 Note that the half-duplex "GL620USB" is not supported.
361 config USB_NET_NET1080
362 tristate "NetChip 1080 based cables (Laplink, ...)"
364 depends on USB_USBNET
366 Choose this option if you're using a host-to-host cable based
367 on this design: one NetChip 1080 chip and supporting logic,
368 optionally with LEDs that indicate traffic
371 tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
372 # if the handshake/init/reset problems, from original 'plusb',
373 # are ever resolved ... then remove "experimental"
374 depends on USB_USBNET
376 Choose this option if you're using a host-to-host cable
377 with one of these chips.
379 config USB_NET_MCS7830
380 tristate "MosChip MCS7830 based Ethernet adapters"
381 depends on USB_USBNET
383 Choose this option if you're using a 10/100 Ethernet USB2
384 adapter based on the MosChip 7830 controller. This includes
385 adapters marketed under the DeLOCK brand.
387 config USB_NET_RNDIS_HOST
388 tristate "Host for RNDIS and ActiveSync devices"
389 depends on USB_USBNET
390 select USB_NET_CDCETHER
392 This option enables hosting "Remote NDIS" USB networking links,
393 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
394 various devices that may only support this protocol. A variant
395 of this protocol (with even less public documentation) seems to
396 be at the root of Microsoft's "ActiveSync" too.
398 Avoid using this protocol unless you have no better options.
399 The protocol specification is incomplete, and is controlled by
400 (and for) Microsoft; it isn't an "Open" ecosystem or market.
402 config USB_NET_CDC_SUBSET_ENABLE
404 depends on USB_NET_CDC_SUBSET
406 config USB_NET_CDC_SUBSET
407 tristate "Simple USB Network Links (CDC Ethernet subset)"
408 depends on USB_USBNET
411 This driver module supports USB network devices that can work
412 without any device-specific information. Select it if you have
413 one of these drivers.
415 Note that while many USB host-to-host cables can work in this mode,
416 that may mean not being able to talk to Win32 systems or more
417 commonly not being able to handle certain events (like replugging
418 the host on the other end) very well. Also, these devices will
419 not generally have permanently assigned Ethernet addresses.
422 bool "ALi M5632 based 'USB 2.0 Data Link' cables"
423 depends on USB_NET_CDC_SUBSET
424 select USB_NET_CDC_SUBSET_ENABLE
426 Choose this option if you're using a host-to-host cable
427 based on this design, which supports USB 2.0 high speed.
430 bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
431 depends on USB_NET_CDC_SUBSET
432 select USB_NET_CDC_SUBSET_ENABLE
434 Choose this option if you're using a host-to-host cable
435 based on this design. Note that AnchorChips is now a
439 bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
440 depends on USB_NET_CDC_SUBSET
441 select USB_NET_CDC_SUBSET_ENABLE
444 Choose this option if you're using a host-to-host cable
445 based on this design: two NetChip 2890 chips and an Atmel
446 microcontroller, with LEDs that indicate traffic.
449 bool "Embedded ARM Linux links (iPaq, ...)"
450 depends on USB_NET_CDC_SUBSET
451 select USB_NET_CDC_SUBSET_ENABLE
454 Choose this option to support the "usb-eth" networking driver
455 used by most of the ARM Linux community with device controllers
456 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
457 in some PXA versions of the "blob" boot loader.
459 Linux-based "Gumstix" PXA-25x based systems use this protocol
460 to talk with other Linux systems.
462 Although the ROMs shipped with Sharp Zaurus products use a
463 different link level framing protocol, you can have them use
464 this simpler protocol by installing a different kernel.
467 bool "Epson 2888 based firmware (DEVELOPMENT)"
468 depends on USB_NET_CDC_SUBSET
469 select USB_NET_CDC_SUBSET_ENABLE
471 Choose this option to support the usb networking links used
472 by some sample firmware from Epson.
475 bool "KT Technology KC2190 based cables (InstaNet)"
476 depends on USB_NET_CDC_SUBSET
477 select USB_NET_CDC_SUBSET_ENABLE
479 Choose this option if you're using a host-to-host cable
480 with one of these chips.
482 config USB_NET_ZAURUS
483 tristate "Sharp Zaurus (stock ROMs) and compatible"
484 depends on USB_USBNET
485 select USB_NET_CDCETHER
489 Choose this option to support the usb networking links used by
490 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
491 This also supports some related device firmware, as used in some
492 PDAs from Olympus and some cell phones from Motorola.
494 If you install an alternate image, such as the Linux 2.6 based
495 versions of OpenZaurus, you should no longer need to support this
496 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
497 really need this non-conformant variant of CDC Ethernet (or in
498 some cases CDC MDLM) protocol, not "g_ether".
500 config USB_NET_CX82310_ETH
501 tristate "Conexant CX82310 USB ethernet port"
502 depends on USB_USBNET
504 Choose this option if you're using a Conexant CX82310-based ADSL
505 router with USB ethernet port. This driver is for routers only,
506 it will not work with ADSL modems (use cxacru driver instead).
508 config USB_NET_KALMIA
509 tristate "Samsung Kalmia based LTE USB modem"
510 depends on USB_USBNET
512 Choose this option if you have a Samsung Kalmia based USB modem
515 To compile this driver as a module, choose M here: the
516 module will be called kalmia.
518 config USB_NET_QMI_WWAN
519 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
520 depends on USB_USBNET
523 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
524 (MDM) chipsets. Examples of such devices are
527 This driver will only drive the ethernet part of the chips.
528 The devices require additional configuration to be usable.
529 Multiple management interfaces with linux drivers are
532 * option: AT commands on /dev/ttyUSBx
533 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
535 A modem manager with support for QMI is recommended.
537 To compile this driver as a module, choose M here: the
538 module will be called qmi_wwan.
541 tristate "Option USB High Speed Mobile Devices"
542 depends on USB && RFKILL && TTY
545 Choose this option if you have an Option HSDPA/HSUPA card.
546 These cards support downlink speeds of 7.2Mbps or greater.
548 To compile this driver as a module, choose M here: the
549 module will be called hso.
551 config USB_NET_INT51X1
552 tristate "Intellon PLC based usb adapter"
553 depends on USB_USBNET
555 Choose this option if you're using a 14Mb USB-based PLC
556 (Powerline Communications) solution with an Intellon
557 INT51x1/INT5200 chip, like the "devolo dLan duo".
559 config USB_CDC_PHONET
560 tristate "CDC Phonet support"
561 depends on PHONET && USB_USBNET
563 Choose this option to support the Phonet interface to a Nokia
564 cellular modem, as found on most Nokia handsets with the
565 "PC suite" USB profile.
568 tristate "Apple iPhone USB Ethernet driver"
571 Module used to share Internet connection (tethering) from your
572 iPhone (Original, 3G and 3GS) to your system.
573 Note that you need userspace libraries and programs that are needed
574 to pair your device with your system and that understand the iPhone
577 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
579 config USB_SIERRA_NET
580 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
581 depends on USB_USBNET
583 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
585 To compile this driver as a module, choose M here: the
586 module will be called sierra_net.
589 tristate "LG VL600 modem dongle"
590 depends on USB_NET_CDCETHER && TTY
593 Select this if you want to use an LG Electronics 4G/LTE usb modem
594 called VL600. This driver only handles the ethernet
595 interface exposed by the modem firmware. To establish a connection
596 you will first need a userspace program that sends the right
597 command to the modem through its CDC ACM port, and most
598 likely also a DHCP client. See this thread about using the
599 4G modem from Verizon:
601 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
603 config USB_NET_CH9200
604 tristate "QingHeng CH9200 USB ethernet support"
605 depends on USB_USBNET
608 Choose this option if you have a USB ethernet adapter with a QinHeng
611 To compile this driver as a module, choose M here: the
612 module will be called ch9200.
614 endif # USB_NET_DRIVERS