2 # USB Network devices configuration
4 comment "Networking support is needed for USB Network Adapter support"
7 menu "USB Network Adapters"
11 tristate "USB CATC NetMate-based Ethernet device support"
14 Say Y if you want to use one of the following 10Mbps USB Ethernet
15 device based on the EL1210A chip. Supported devices are:
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.
26 To compile this driver as a module, choose M here: the
27 module will be called catc.
30 tristate "USB KLSI KL5USB101-based ethernet device support"
32 Say Y here if you want to use one of the following 10Mbps only
33 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
37 ASANTE USB To Ethernet Adapter
38 AOX Endpoints USB Ethernet
40 D-Link DSB-650C and DU-E10
41 Entrega / Portgear E45
43 Jaton USB Ethernet Device Adapter
44 Kingston Technology USB Ethernet Adapter
46 Mobility USB-Ethernet Adapter
48 Peracom Enet and Enet2
49 Portsmith Express Ethernet Adapter
52 Sony Vaio port extender
54 This driver is likely to work with most 10Mbps only USB Ethernet
55 adapters, including some "no brand" devices. It does NOT work on
56 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
57 the CATC NetMate driver for those. If you are not sure which one
58 you need, select both, and the correct one should be selected for
61 This driver makes the adapter appear as a normal Ethernet interface,
62 typically on eth0, if it is the only ethernet device, or perhaps on
63 eth1, if you have a PCI or ISA ethernet card installed.
65 To compile this driver as a module, choose M here: the
66 module will be called kaweth.
69 tristate "USB Pegasus/Pegasus-II based ethernet device support"
72 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
73 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
74 complete list of supported devices.
76 If your particular adapter is not in the list and you are _sure_ it
77 is Pegasus or Pegasus II based then send me
78 <petkan@users.sourceforge.net> vendor and device IDs.
80 To compile this driver as a module, choose M here: the
81 module will be called pegasus.
84 tristate "USB RTL8150 based ethernet device support"
87 Say Y here if you have RTL8150 based usb-ethernet adapter.
88 Send me <petkan@users.sourceforge.net> any comments you may have.
89 You can also check for updates at <http://pegasus2.sourceforge.net/>.
91 To compile this driver as a module, choose M here: the
92 module will be called rtl8150.
95 tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
98 This option adds support for Realtek RTL8152 based USB 2.0
99 10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
102 To compile this driver as a module, choose M here: the
103 module will be called r8152.
106 tristate "Multi-purpose USB Networking Framework"
109 This driver supports several kinds of network links over USB,
110 with "minidrivers" built around a common network driver core
111 that supports deep queues for efficient transfers. (This gives
112 better performance with small packets and at high speeds).
114 The USB host runs "usbnet", and the other end of the link might be:
116 - Another USB host, when using USB "network" or "data transfer"
117 cables. These are often used to network laptops to PCs, like
118 "Laplink" parallel cables or some motherboards. These rely
119 on specialized chips from many suppliers.
121 - An intelligent USB gadget, perhaps embedding a Linux system.
122 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
123 others), and devices that interoperate using the standard
124 CDC-Ethernet specification (including many cable modems).
126 - Network adapter hardware (like those for 10/100 Ethernet) which
127 uses this driver framework.
129 The link will appear with a name like "usb0", when the link is
130 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
131 two-node links are most easily managed with Ethernet Bridging
132 (CONFIG_BRIDGE) instead of routing.
134 For more information see <http://www.linux-usb.org/usbnet/>.
136 To compile this driver as a module, choose M here: the
137 module will be called usbnet.
139 config USB_NET_AX8817X
140 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
141 depends on USB_USBNET
146 This option adds support for ASIX AX88xxx based USB 2.0
147 10/100 Ethernet adapters.
149 This driver should work with at least the following devices:
152 * Billionton Systems, USB2AR
154 * Corega FEther USB2-TX
160 * Intellinet USB 2.0 Ethernet
161 * ST Lab USB 2.0 Ethernet
164 This driver creates an interface named "ethX", where X depends on
165 what other networking devices you have in use.
167 config USB_NET_AX88179_178A
168 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
169 depends on USB_USBNET
174 This option adds support for ASIX AX88179 based USB 3.0/2.0
175 to Gigabit Ethernet adapters.
177 This driver should work with at least the following devices:
182 This driver creates an interface named "ethX", where X depends on
183 what other networking devices you have in use.
185 config USB_NET_CDCETHER
186 tristate "CDC Ethernet support (smart devices such as cable modems)"
187 depends on USB_USBNET
190 This option supports devices conforming to the Communication Device
191 Class (CDC) Ethernet Control Model, a specification that's easy to
192 implement in device firmware. The CDC specifications are available
193 from <http://www.usb.org/>.
195 CDC Ethernet is an implementation option for DOCSIS cable modems
196 that support USB connectivity, used for non-Microsoft USB hosts.
197 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
198 This driver should work with at least the following devices:
200 * Dell Wireless 5530 HSPA
201 * Ericsson PipeRider (all variants)
202 * Ericsson Mobile Broadband Module (all variants)
203 * Motorola (DM100 and SB4100)
204 * Broadcom Cable Modem (reference design)
205 * Toshiba (PCX1100U and F3507g/F3607gw)
208 This driver creates an interface named "ethX", where X depends on
209 what other networking devices you have in use. However, if the
210 IEEE 802 "local assignment" bit is set in the address, a "usbX"
211 name is used instead.
213 config USB_NET_CDC_EEM
214 tristate "CDC EEM support"
215 depends on USB_USBNET
217 This option supports devices conforming to the Communication Device
218 Class (CDC) Ethernet Emulation Model, a specification that's easy to
219 implement in device firmware. The CDC EEM specifications are available
220 from <http://www.usb.org/>.
222 This driver creates an interface named "ethX", where X depends on
223 what other networking devices you have in use. However, if the
224 IEEE 802 "local assignment" bit is set in the address, a "usbX"
225 name is used instead.
227 config USB_NET_CDC_NCM
228 tristate "CDC NCM support"
229 depends on USB_USBNET
232 This driver provides support for CDC NCM (Network Control Model
233 Device USB Class Specification). The CDC NCM specification is
234 available from <http://www.usb.org/>.
236 Say "y" to link the driver statically, or "m" to build a
237 dynamically linked module.
239 This driver should work with at least the following devices:
240 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
241 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
242 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
243 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
244 * Ericsson F5521gw Mobile Broadband Module
246 config USB_NET_HUAWEI_CDC_NCM
247 tristate "Huawei NCM embedded AT channel support"
248 depends on USB_USBNET
250 select USB_NET_CDC_NCM
252 This driver supports huawei-style NCM devices, that use NCM as a
253 transport for other protocols, usually an embedded AT channel.
258 To compile this driver as a module, choose M here: the module will be
259 called huawei_cdc_ncm.ko.
261 config USB_NET_CDC_MBIM
262 tristate "CDC MBIM support"
263 depends on USB_USBNET
265 select USB_NET_CDC_NCM
267 This driver provides support for CDC MBIM (Mobile Broadband
268 Interface Model) devices. The CDC MBIM specification is
269 available from <http://www.usb.org/>.
271 MBIM devices require configuration using the management
272 protocol defined by the MBIM specification. This driver
273 provides unfiltered access to the MBIM control channel
274 through the associated /dev/cdc-wdmx character device.
276 To compile this driver as a module, choose M here: the
277 module will be called cdc_mbim.
279 config USB_NET_DM9601
280 tristate "Davicom DM96xx based USB 10/100 ethernet devices"
281 depends on USB_USBNET
284 This option adds support for Davicom DM9601/DM9620/DM9621A
285 based USB 10/100 Ethernet adapters.
287 config USB_NET_SR9700
288 tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
289 depends on USB_USBNET
292 This option adds support for CoreChip-sz SR9700 based USB 1.1
293 10/100 Ethernet adapters.
295 config USB_NET_SR9800
296 tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
297 depends on USB_USBNET
300 Say Y if you want to use one of the following 100Mbps USB Ethernet
301 device based on the CoreChip-sz SR9800 chip.
303 This driver makes the adapter appear as a normal Ethernet interface,
304 typically on eth0, if it is the only ethernet device, or perhaps on
305 eth1, if you have a PCI or ISA ethernet card installed.
307 To compile this driver as a module, choose M here: the
308 module will be called sr9800.
310 config USB_NET_SMSC75XX
311 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
312 depends on USB_USBNET
317 This option adds support for SMSC LAN75XX based USB 2.0
318 Gigabit Ethernet adapters.
320 config USB_NET_SMSC95XX
321 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
322 depends on USB_USBNET
327 This option adds support for SMSC LAN95XX based USB 2.0
328 10/100 Ethernet adapters.
330 config USB_NET_GL620A
331 tristate "GeneSys GL620USB-A based cables"
332 depends on USB_USBNET
334 Choose this option if you're using a host-to-host cable,
335 or PC2PC motherboard, with this chip.
337 Note that the half-duplex "GL620USB" is not supported.
339 config USB_NET_NET1080
340 tristate "NetChip 1080 based cables (Laplink, ...)"
342 depends on USB_USBNET
344 Choose this option if you're using a host-to-host cable based
345 on this design: one NetChip 1080 chip and supporting logic,
346 optionally with LEDs that indicate traffic
349 tristate "Prolific PL-2301/2302/25A1 based cables"
350 # if the handshake/init/reset problems, from original 'plusb',
351 # are ever resolved ... then remove "experimental"
352 depends on USB_USBNET
354 Choose this option if you're using a host-to-host cable
355 with one of these chips.
357 config USB_NET_MCS7830
358 tristate "MosChip MCS7830 based Ethernet adapters"
359 depends on USB_USBNET
361 Choose this option if you're using a 10/100 Ethernet USB2
362 adapter based on the MosChip 7830 controller. This includes
363 adapters marketed under the DeLOCK brand.
365 config USB_NET_RNDIS_HOST
366 tristate "Host for RNDIS and ActiveSync devices"
367 depends on USB_USBNET
368 select USB_NET_CDCETHER
370 This option enables hosting "Remote NDIS" USB networking links,
371 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
372 various devices that may only support this protocol. A variant
373 of this protocol (with even less public documentation) seems to
374 be at the root of Microsoft's "ActiveSync" too.
376 Avoid using this protocol unless you have no better options.
377 The protocol specification is incomplete, and is controlled by
378 (and for) Microsoft; it isn't an "Open" ecosystem or market.
380 config USB_NET_CDC_SUBSET
381 tristate "Simple USB Network Links (CDC Ethernet subset)"
382 depends on USB_USBNET
385 This driver module supports USB network devices that can work
386 without any device-specific information. Select it if you have
387 one of these drivers.
389 Note that while many USB host-to-host cables can work in this mode,
390 that may mean not being able to talk to Win32 systems or more
391 commonly not being able to handle certain events (like replugging
392 the host on the other end) very well. Also, these devices will
393 not generally have permanently assigned Ethernet addresses.
396 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
397 depends on USB_NET_CDC_SUBSET
399 Choose this option if you're using a host-to-host cable
400 based on this design, which supports USB 2.0 high speed.
403 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
404 depends on USB_NET_CDC_SUBSET
406 Choose this option if you're using a host-to-host cable
407 based on this design. Note that AnchorChips is now a
411 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
412 depends on USB_NET_CDC_SUBSET
415 Choose this option if you're using a host-to-host cable
416 based on this design: two NetChip 2890 chips and an Atmel
417 microcontroller, with LEDs that indicate traffic.
420 boolean "Embedded ARM Linux links (iPaq, ...)"
421 depends on USB_NET_CDC_SUBSET
424 Choose this option to support the "usb-eth" networking driver
425 used by most of the ARM Linux community with device controllers
426 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
427 in some PXA versions of the "blob" boot loader.
429 Linux-based "Gumstix" PXA-25x based systems use this protocol
430 to talk with other Linux systems.
432 Although the ROMs shipped with Sharp Zaurus products use a
433 different link level framing protocol, you can have them use
434 this simpler protocol by installing a different kernel.
437 boolean "Epson 2888 based firmware (DEVELOPMENT)"
438 depends on USB_NET_CDC_SUBSET
440 Choose this option to support the usb networking links used
441 by some sample firmware from Epson.
444 boolean "KT Technology KC2190 based cables (InstaNet)"
445 depends on USB_NET_CDC_SUBSET
447 Choose this option if you're using a host-to-host cable
448 with one of these chips.
450 config USB_NET_ZAURUS
451 tristate "Sharp Zaurus (stock ROMs) and compatible"
452 depends on USB_USBNET
453 select USB_NET_CDCETHER
457 Choose this option to support the usb networking links used by
458 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
459 This also supports some related device firmware, as used in some
460 PDAs from Olympus and some cell phones from Motorola.
462 If you install an alternate image, such as the Linux 2.6 based
463 versions of OpenZaurus, you should no longer need to support this
464 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
465 really need this non-conformant variant of CDC Ethernet (or in
466 some cases CDC MDLM) protocol, not "g_ether".
468 config USB_NET_CX82310_ETH
469 tristate "Conexant CX82310 USB ethernet port"
470 depends on USB_USBNET
472 Choose this option if you're using a Conexant CX82310-based ADSL
473 router with USB ethernet port. This driver is for routers only,
474 it will not work with ADSL modems (use cxacru driver instead).
476 config USB_NET_KALMIA
477 tristate "Samsung Kalmia based LTE USB modem"
478 depends on USB_USBNET
480 Choose this option if you have a Samsung Kalmia based USB modem
483 To compile this driver as a module, choose M here: the
484 module will be called kalmia.
486 config USB_NET_QMI_WWAN
487 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
488 depends on USB_USBNET
491 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
492 (MDM) chipsets. Examples of such devices are
495 This driver will only drive the ethernet part of the chips.
496 The devices require additional configuration to be usable.
497 Multiple management interfaces with linux drivers are
500 * option: AT commands on /dev/ttyUSBx
501 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
503 A modem manager with support for QMI is recommended.
505 To compile this driver as a module, choose M here: the
506 module will be called qmi_wwan.
509 tristate "Option USB High Speed Mobile Devices"
510 depends on USB && RFKILL && TTY
513 Choose this option if you have an Option HSDPA/HSUPA card.
514 These cards support downlink speeds of 7.2Mbps or greater.
516 To compile this driver as a module, choose M here: the
517 module will be called hso.
519 config USB_NET_INT51X1
520 tristate "Intellon PLC based usb adapter"
521 depends on USB_USBNET
523 Choose this option if you're using a 14Mb USB-based PLC
524 (Powerline Communications) solution with an Intellon
525 INT51x1/INT5200 chip, like the "devolo dLan duo".
527 config USB_CDC_PHONET
528 tristate "CDC Phonet support"
531 Choose this option to support the Phonet interface to a Nokia
532 cellular modem, as found on most Nokia handsets with the
533 "PC suite" USB profile.
536 tristate "Apple iPhone USB Ethernet driver"
539 Module used to share Internet connection (tethering) from your
540 iPhone (Original, 3G and 3GS) to your system.
541 Note that you need userspace libraries and programs that are needed
542 to pair your device with your system and that understand the iPhone
545 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
547 config USB_SIERRA_NET
548 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
549 depends on USB_USBNET
551 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
553 To compile this driver as a module, choose M here: the
554 module will be called sierra_net.
557 tristate "LG VL600 modem dongle"
558 depends on USB_NET_CDCETHER && TTY
561 Select this if you want to use an LG Electronics 4G/LTE usb modem
562 called VL600. This driver only handles the ethernet
563 interface exposed by the modem firmware. To establish a connection
564 you will first need a userspace program that sends the right
565 command to the modem through its CDC ACM port, and most
566 likely also a DHCP client. See this thread about using the
567 4G modem from Verizon:
569 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17