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"
73 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
74 If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
75 complete list of supported devices.
77 If your particular adapter is not in the list and you are _sure_ it
78 is Pegasus or Pegasus II based then send me
79 <petkan@users.sourceforge.net> vendor and device IDs.
81 To compile this driver as a module, choose M here: the
82 module will be called pegasus.
85 tristate "USB RTL8150 based ethernet device support"
89 Say Y here if you have RTL8150 based usb-ethernet adapter.
90 Send me <petkan@users.sourceforge.net> any comments you may have.
91 You can also check for updates at <http://pegasus2.sourceforge.net/>.
93 To compile this driver as a module, choose M here: the
94 module will be called rtl8150.
97 tristate "Realtek RTL8152 Based USB 2.0 Ethernet Adapters"
101 This option adds support for Realtek RTL8152 based USB 2.0
102 10/100 Ethernet adapters.
104 To compile this driver as a module, choose M here: the
105 module will be called r8152.
108 tristate "Multi-purpose USB Networking Framework"
112 This driver supports several kinds of network links over USB,
113 with "minidrivers" built around a common network driver core
114 that supports deep queues for efficient transfers. (This gives
115 better performance with small packets and at high speeds).
117 The USB host runs "usbnet", and the other end of the link might be:
119 - Another USB host, when using USB "network" or "data transfer"
120 cables. These are often used to network laptops to PCs, like
121 "Laplink" parallel cables or some motherboards. These rely
122 on specialized chips from many suppliers.
124 - An intelligent USB gadget, perhaps embedding a Linux system.
125 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
126 others), and devices that interoperate using the standard
127 CDC-Ethernet specification (including many cable modems).
129 - Network adapter hardware (like those for 10/100 Ethernet) which
130 uses this driver framework.
132 The link will appear with a name like "usb0", when the link is
133 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
134 two-node links are most easily managed with Ethernet Bridging
135 (CONFIG_BRIDGE) instead of routing.
137 For more information see <http://www.linux-usb.org/usbnet/>.
139 To compile this driver as a module, choose M here: the
140 module will be called usbnet.
142 config USB_NET_AX8817X
143 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
144 depends on USB_USBNET
149 This option adds support for ASIX AX88xxx based USB 2.0
150 10/100 Ethernet adapters.
152 This driver should work with at least the following devices:
155 * Billionton Systems, USB2AR
157 * Corega FEther USB2-TX
163 * Intellinet USB 2.0 Ethernet
164 * ST Lab USB 2.0 Ethernet
167 This driver creates an interface named "ethX", where X depends on
168 what other networking devices you have in use.
170 config USB_NET_AX88179_178A
171 tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
172 depends on USB_USBNET
177 This option adds support for ASIX AX88179 based USB 3.0/2.0
178 to Gigabit Ethernet adapters.
180 This driver should work with at least the following devices:
185 This driver creates an interface named "ethX", where X depends on
186 what other networking devices you have in use.
188 config USB_NET_CDCETHER
189 tristate "CDC Ethernet support (smart devices such as cable modems)"
190 depends on USB_USBNET
193 This option supports devices conforming to the Communication Device
194 Class (CDC) Ethernet Control Model, a specification that's easy to
195 implement in device firmware. The CDC specifications are available
196 from <http://www.usb.org/>.
198 CDC Ethernet is an implementation option for DOCSIS cable modems
199 that support USB connectivity, used for non-Microsoft USB hosts.
200 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
201 This driver should work with at least the following devices:
203 * Dell Wireless 5530 HSPA
204 * Ericsson PipeRider (all variants)
205 * Ericsson Mobile Broadband Module (all variants)
206 * Motorola (DM100 and SB4100)
207 * Broadcom Cable Modem (reference design)
208 * Toshiba (PCX1100U and F3507g/F3607gw)
211 This driver creates an interface named "ethX", where X depends on
212 what other networking devices you have in use. However, if the
213 IEEE 802 "local assignment" bit is set in the address, a "usbX"
214 name is used instead.
216 config USB_NET_CDC_EEM
217 tristate "CDC EEM support"
218 depends on USB_USBNET
220 This option supports devices conforming to the Communication Device
221 Class (CDC) Ethernet Emulation Model, a specification that's easy to
222 implement in device firmware. The CDC EEM specifications are available
223 from <http://www.usb.org/>.
225 This driver creates an interface named "ethX", where X depends on
226 what other networking devices you have in use. However, if the
227 IEEE 802 "local assignment" bit is set in the address, a "usbX"
228 name is used instead.
230 config USB_NET_CDC_NCM
231 tristate "CDC NCM support"
232 depends on USB_USBNET
235 This driver provides support for CDC NCM (Network Control Model
236 Device USB Class Specification). The CDC NCM specification is
237 available from <http://www.usb.org/>.
239 Say "y" to link the driver statically, or "m" to build a
240 dynamically linked module.
242 This driver should work with at least the following devices:
243 * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
244 * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
245 * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
246 * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
247 * Ericsson F5521gw Mobile Broadband Module
249 config USB_NET_CDC_MBIM
250 tristate "CDC MBIM support"
251 depends on USB_USBNET
253 select USB_NET_CDC_NCM
255 This driver provides support for CDC MBIM (Mobile Broadband
256 Interface Model) devices. The CDC MBIM specification is
257 available from <http://www.usb.org/>.
259 MBIM devices require configuration using the management
260 protocol defined by the MBIM specification. This driver
261 provides unfiltered access to the MBIM control channel
262 through the associated /dev/cdc-wdmx character device.
264 To compile this driver as a module, choose M here: the
265 module will be called cdc_mbim.
267 config USB_NET_DM9601
268 tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
269 depends on USB_USBNET
272 This option adds support for Davicom DM9601 based USB 1.1
273 10/100 Ethernet adapters.
275 config USB_NET_SMSC75XX
276 tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
277 depends on USB_USBNET
282 This option adds support for SMSC LAN75XX based USB 2.0
283 Gigabit Ethernet adapters.
285 config USB_NET_SMSC95XX
286 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
287 depends on USB_USBNET
292 This option adds support for SMSC LAN95XX based USB 2.0
293 10/100 Ethernet adapters.
295 config USB_NET_GL620A
296 tristate "GeneSys GL620USB-A based cables"
297 depends on USB_USBNET
299 Choose this option if you're using a host-to-host cable,
300 or PC2PC motherboard, with this chip.
302 Note that the half-duplex "GL620USB" is not supported.
304 config USB_NET_NET1080
305 tristate "NetChip 1080 based cables (Laplink, ...)"
307 depends on USB_USBNET
309 Choose this option if you're using a host-to-host cable based
310 on this design: one NetChip 1080 chip and supporting logic,
311 optionally with LEDs that indicate traffic
314 tristate "Prolific PL-2301/2302/25A1 based cables"
315 # if the handshake/init/reset problems, from original 'plusb',
316 # are ever resolved ... then remove "experimental"
317 depends on USB_USBNET
319 Choose this option if you're using a host-to-host cable
320 with one of these chips.
322 config USB_NET_MCS7830
323 tristate "MosChip MCS7830 based Ethernet adapters"
324 depends on USB_USBNET
326 Choose this option if you're using a 10/100 Ethernet USB2
327 adapter based on the MosChip 7830 controller. This includes
328 adapters marketed under the DeLOCK brand.
330 config USB_NET_RNDIS_HOST
331 tristate "Host for RNDIS and ActiveSync devices"
332 depends on USB_USBNET
333 select USB_NET_CDCETHER
335 This option enables hosting "Remote NDIS" USB networking links,
336 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
337 various devices that may only support this protocol. A variant
338 of this protocol (with even less public documentation) seems to
339 be at the root of Microsoft's "ActiveSync" too.
341 Avoid using this protocol unless you have no better options.
342 The protocol specification is incomplete, and is controlled by
343 (and for) Microsoft; it isn't an "Open" ecosystem or market.
345 config USB_NET_CDC_SUBSET
346 tristate "Simple USB Network Links (CDC Ethernet subset)"
347 depends on USB_USBNET
350 This driver module supports USB network devices that can work
351 without any device-specific information. Select it if you have
352 one of these drivers.
354 Note that while many USB host-to-host cables can work in this mode,
355 that may mean not being able to talk to Win32 systems or more
356 commonly not being able to handle certain events (like replugging
357 the host on the other end) very well. Also, these devices will
358 not generally have permanently assigned Ethernet addresses.
361 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
362 depends on USB_NET_CDC_SUBSET
364 Choose this option if you're using a host-to-host cable
365 based on this design, which supports USB 2.0 high speed.
368 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
369 depends on USB_NET_CDC_SUBSET
371 Choose this option if you're using a host-to-host cable
372 based on this design. Note that AnchorChips is now a
376 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
377 depends on USB_NET_CDC_SUBSET
380 Choose this option if you're using a host-to-host cable
381 based on this design: two NetChip 2890 chips and an Atmel
382 microcontroller, with LEDs that indicate traffic.
385 boolean "Embedded ARM Linux links (iPaq, ...)"
386 depends on USB_NET_CDC_SUBSET
389 Choose this option to support the "usb-eth" networking driver
390 used by most of the ARM Linux community with device controllers
391 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
392 in some PXA versions of the "blob" boot loader.
394 Linux-based "Gumstix" PXA-25x based systems use this protocol
395 to talk with other Linux systems.
397 Although the ROMs shipped with Sharp Zaurus products use a
398 different link level framing protocol, you can have them use
399 this simpler protocol by installing a different kernel.
402 boolean "Epson 2888 based firmware (DEVELOPMENT)"
403 depends on USB_NET_CDC_SUBSET
405 Choose this option to support the usb networking links used
406 by some sample firmware from Epson.
409 boolean "KT Technology KC2190 based cables (InstaNet)"
410 depends on USB_NET_CDC_SUBSET
412 Choose this option if you're using a host-to-host cable
413 with one of these chips.
415 config USB_NET_ZAURUS
416 tristate "Sharp Zaurus (stock ROMs) and compatible"
417 depends on USB_USBNET
418 select USB_NET_CDCETHER
422 Choose this option to support the usb networking links used by
423 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
424 This also supports some related device firmware, as used in some
425 PDAs from Olympus and some cell phones from Motorola.
427 If you install an alternate image, such as the Linux 2.6 based
428 versions of OpenZaurus, you should no longer need to support this
429 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
430 really need this non-conformant variant of CDC Ethernet (or in
431 some cases CDC MDLM) protocol, not "g_ether".
433 config USB_NET_CX82310_ETH
434 tristate "Conexant CX82310 USB ethernet port"
435 depends on USB_USBNET
437 Choose this option if you're using a Conexant CX82310-based ADSL
438 router with USB ethernet port. This driver is for routers only,
439 it will not work with ADSL modems (use cxacru driver instead).
441 config USB_NET_KALMIA
442 tristate "Samsung Kalmia based LTE USB modem"
443 depends on USB_USBNET
445 Choose this option if you have a Samsung Kalmia based USB modem
448 To compile this driver as a module, choose M here: the
449 module will be called kalmia.
451 config USB_NET_QMI_WWAN
452 tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
453 depends on USB_USBNET
456 Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
457 (MDM) chipsets. Examples of such devices are
460 This driver will only drive the ethernet part of the chips.
461 The devices require additional configuration to be usable.
462 Multiple management interfaces with linux drivers are
465 * option: AT commands on /dev/ttyUSBx
466 * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
468 A modem manager with support for QMI is recommended.
470 To compile this driver as a module, choose M here: the
471 module will be called qmi_wwan.
474 tristate "Option USB High Speed Mobile Devices"
475 depends on USB && RFKILL && TTY
478 Choose this option if you have an Option HSDPA/HSUPA card.
479 These cards support downlink speeds of 7.2Mbps or greater.
481 To compile this driver as a module, choose M here: the
482 module will be called hso.
484 config USB_NET_INT51X1
485 tristate "Intellon PLC based usb adapter"
486 depends on USB_USBNET
488 Choose this option if you're using a 14Mb USB-based PLC
489 (Powerline Communications) solution with an Intellon
490 INT51x1/INT5200 chip, like the "devolo dLan duo".
492 config USB_CDC_PHONET
493 tristate "CDC Phonet support"
496 Choose this option to support the Phonet interface to a Nokia
497 cellular modem, as found on most Nokia handsets with the
498 "PC suite" USB profile.
501 tristate "Apple iPhone USB Ethernet driver"
504 Module used to share Internet connection (tethering) from your
505 iPhone (Original, 3G and 3GS) to your system.
506 Note that you need userspace libraries and programs that are needed
507 to pair your device with your system and that understand the iPhone
510 For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
512 config USB_SIERRA_NET
513 tristate "USB-to-WWAN Driver for Sierra Wireless modems"
514 depends on USB_USBNET
516 Choose this option if you have a Sierra Wireless USB-to-WWAN device.
518 To compile this driver as a module, choose M here: the
519 module will be called sierra_net.
522 tristate "LG VL600 modem dongle"
523 depends on USB_NET_CDCETHER && TTY
526 Select this if you want to use an LG Electronics 4G/LTE usb modem
527 called VL600. This driver only handles the ethernet
528 interface exposed by the modem firmware. To establish a connection
529 you will first need a userspace program that sends the right
530 command to the modem through its CDC ACM port, and most
531 likely also a DHCP client. See this thread about using the
532 4G modem from Verizon:
534 http://ubuntuforums.org/showpost.php?p=10589647&postcount=17