Version:  2.0.40 2.2.26 2.4.37 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17

Linux/drivers/net/usb/Kconfig

  1 #
  2 # USB Network devices configuration
  3 #
  4 comment "Host-side USB support is needed for USB Network Adapter support"
  5         depends on !USB && NET
  6 
  7 menuconfig USB_NET_DRIVERS
  8         tristate "USB Network Adapters"
  9         default USB if USB
 10         depends on USB && NET
 11 
 12 if USB_NET_DRIVERS
 13 
 14 config USB_CATC
 15         tristate "USB CATC NetMate-based Ethernet device support"
 16         select CRC32
 17         ---help---
 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:
 20           Belkin F5U011
 21           Belkin F5U111
 22           CATC NetMate
 23           CATC NetMate II
 24           smartBridges smartNIC
 25 
 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.
 29 
 30           To compile this driver as a module, choose M here: the
 31           module will be called catc.
 32 
 33 config USB_KAWETH
 34         tristate "USB KLSI KL5USB101-based ethernet device support"
 35         ---help---
 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:
 38           3Com 3C19250
 39           ADS USB-10BT
 40           ATEN USB Ethernet
 41           ASANTE USB To Ethernet Adapter
 42           AOX Endpoints USB Ethernet
 43           Correga K.K.
 44           D-Link DSB-650C and DU-E10
 45           Entrega / Portgear E45
 46           I-O DATA USB-ET/T
 47           Jaton USB Ethernet Device Adapter
 48           Kingston Technology USB Ethernet Adapter
 49           Linksys USB10T
 50           Mobility USB-Ethernet Adapter
 51           NetGear EA-101
 52           Peracom Enet and Enet2
 53           Portsmith Express Ethernet Adapter
 54           Shark Pocket Adapter
 55           SMC 2202USB
 56           Sony Vaio port extender
 57 
 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
 63           you.
 64 
 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.
 68 
 69           To compile this driver as a module, choose M here: the
 70           module will be called kaweth.
 71 
 72 config USB_PEGASUS
 73         tristate "USB Pegasus/Pegasus-II based ethernet device support"
 74         select MII
 75         ---help---
 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.
 79 
 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.
 83 
 84           To compile this driver as a module, choose M here: the
 85           module will be called pegasus.
 86 
 87 config USB_RTL8150
 88         tristate "USB RTL8150 based ethernet device support"
 89         select MII
 90         help
 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/>.
 94 
 95           To compile this driver as a module, choose M here: the
 96           module will be called rtl8150.
 97 
 98 config USB_RTL8152
 99         tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
100         select MII
101         help
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
104           Ethernet adapters.
105 
106           To compile this driver as a module, choose M here: the
107           module will be called r8152.
108 
109 config USB_USBNET
110         tristate "Multi-purpose USB Networking Framework"
111         select MII
112         ---help---
113           This driver supports several kinds of network links over USB,
114           with "minidrivers" built around a common network driver core
115           that supports deep queues for efficient transfers.  (This gives
116           better performance with small packets and at high speeds).
117 
118           The USB host runs "usbnet", and the other end of the link might be:
119 
120           - Another USB host, when using USB "network" or "data transfer"
121             cables.  These are often used to network laptops to PCs, like
122             "Laplink" parallel cables or some motherboards.  These rely
123             on specialized chips from many suppliers.
124 
125           - An intelligent USB gadget, perhaps embedding a Linux system.
126             These include PDAs running Linux (iPaq, Yopy, Zaurus, and
127             others), and devices that interoperate using the standard
128             CDC-Ethernet specification (including many cable modems).
129 
130           - Network adapter hardware (like those for 10/100 Ethernet) which
131             uses this driver framework.
132 
133           The link will appear with a name like "usb0", when the link is
134           a two-node link, or "eth0" for most CDC-Ethernet devices.  Those
135           two-node links are most easily managed with Ethernet Bridging
136           (CONFIG_BRIDGE) instead of routing.
137 
138           For more information see <http://www.linux-usb.org/usbnet/>.
139 
140           To compile this driver as a module, choose M here: the
141           module will be called usbnet.
142 
143 config USB_NET_AX8817X
144         tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
145         depends on USB_USBNET
146         select CRC32
147         select PHYLIB
148         default y
149         help
150           This option adds support for ASIX AX88xxx based USB 2.0
151           10/100 Ethernet adapters.
152 
153           This driver should work with at least the following devices:
154             * Aten UC210T
155             * ASIX AX88172
156             * Billionton Systems, USB2AR
157             * Buffalo LUA-U2-KTX
158             * Corega FEther USB2-TX
159             * D-Link DUB-E100
160             * Hawking UF200
161             * Linksys USB200M
162             * Netgear FA120
163             * Sitecom LN-029
164             * Intellinet USB 2.0 Ethernet
165             * ST Lab USB 2.0 Ethernet
166             * TrendNet TU2-ET100
167 
168           This driver creates an interface named "ethX", where X depends on
169           what other networking devices you have in use.
170 
171 config USB_NET_AX88179_178A
172         tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
173         depends on USB_USBNET
174         select CRC32
175         select PHYLIB
176         default y
177         help
178           This option adds support for ASIX AX88179 based USB 3.0/2.0
179           to Gigabit Ethernet adapters.
180 
181           This driver should work with at least the following devices:
182             * ASIX AX88179
183             * ASIX AX88178A
184             * Sitcomm LN-032
185 
186           This driver creates an interface named "ethX", where X depends on
187           what other networking devices you have in use.
188 
189 config USB_NET_CDCETHER
190         tristate "CDC Ethernet support (smart devices such as cable modems)"
191         depends on USB_USBNET
192         default y
193         help
194           This option supports devices conforming to the Communication Device
195           Class (CDC) Ethernet Control Model, a specification that's easy to
196           implement in device firmware.  The CDC specifications are available
197           from <http://www.usb.org/>.
198 
199           CDC Ethernet is an implementation option for DOCSIS cable modems
200           that support USB connectivity, used for non-Microsoft USB hosts.
201           The Linux-USB CDC Ethernet Gadget driver is an open implementation.
202           This driver should work with at least the following devices:
203 
204             * Dell Wireless 5530 HSPA
205             * Ericsson PipeRider (all variants)
206             * Ericsson Mobile Broadband Module (all variants)
207             * Motorola (DM100 and SB4100)
208             * Broadcom Cable Modem (reference design)
209             * Toshiba (PCX1100U and F3507g/F3607gw)
210             * ...
211 
212           This driver creates an interface named "ethX", where X depends on
213           what other networking devices you have in use.  However, if the
214           IEEE 802 "local assignment" bit is set in the address, a "usbX"
215           name is used instead.
216 
217 config USB_NET_CDC_EEM
218         tristate "CDC EEM support"
219         depends on USB_USBNET
220         help
221           This option supports devices conforming to the Communication Device
222           Class (CDC) Ethernet Emulation Model, a specification that's easy to
223           implement in device firmware.  The CDC EEM specifications are available
224           from <http://www.usb.org/>.
225 
226           This driver creates an interface named "ethX", where X depends on
227           what other networking devices you have in use.  However, if the
228           IEEE 802 "local assignment" bit is set in the address, a "usbX"
229           name is used instead.
230 
231 config USB_NET_CDC_NCM
232         tristate "CDC NCM support"
233         depends on USB_USBNET
234         default y
235         help
236           This driver provides support for CDC NCM (Network Control Model
237           Device USB Class Specification). The CDC NCM specification is
238           available from <http://www.usb.org/>.
239 
240           Say "y" to link the driver statically, or "m" to build a
241           dynamically linked module.
242 
243           This driver should work with at least the following devices:
244             * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
245             * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
246             * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
247             * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
248             * Ericsson F5521gw Mobile Broadband Module
249 
250 config USB_NET_HUAWEI_CDC_NCM
251         tristate "Huawei NCM embedded AT channel support"
252         depends on USB_USBNET
253         select USB_WDM
254         select USB_NET_CDC_NCM
255         help
256                 This driver supports huawei-style NCM devices, that use NCM as a
257                 transport for other protocols, usually an embedded AT channel.
258                 Good examples are:
259                 * Huawei E3131
260                 * Huawei E3251
261 
262                 To compile this driver as a module, choose M here: the module will be
263                 called huawei_cdc_ncm.ko.
264 
265 config USB_NET_CDC_MBIM
266         tristate "CDC MBIM support"
267         depends on USB_USBNET
268         select USB_WDM
269         select USB_NET_CDC_NCM
270         help
271           This driver provides support for CDC MBIM (Mobile Broadband
272           Interface Model) devices. The CDC MBIM specification is
273           available from <http://www.usb.org/>.
274 
275           MBIM devices require configuration using the management
276           protocol defined by the MBIM specification.  This driver
277           provides unfiltered access to the MBIM control channel
278           through the associated /dev/cdc-wdmx character device.
279 
280           To compile this driver as a module, choose M here: the
281           module will be called cdc_mbim.
282 
283 config USB_NET_DM9601
284         tristate "Davicom DM96xx based USB 10/100 ethernet devices"
285         depends on USB_USBNET
286         select CRC32
287         help
288           This option adds support for Davicom DM9601/DM9620/DM9621A
289           based USB 10/100 Ethernet adapters.
290 
291 config USB_NET_SR9700
292         tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
293         depends on USB_USBNET
294         select CRC32
295         help
296           This option adds support for CoreChip-sz SR9700 based USB 1.1
297           10/100 Ethernet adapters.
298 
299 config USB_NET_SR9800
300         tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
301         depends on USB_USBNET
302         select CRC32
303         ---help---
304           Say Y if you want to use one of the following 100Mbps USB Ethernet
305           device based on the CoreChip-sz SR9800 chip.
306 
307           This driver makes the adapter appear as a normal Ethernet interface,
308           typically on eth0, if it is the only ethernet device, or perhaps on
309           eth1, if you have a PCI or ISA ethernet card installed.
310 
311           To compile this driver as a module, choose M here: the
312           module will be called sr9800.
313 
314 config USB_NET_SMSC75XX
315         tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
316         depends on USB_USBNET
317         select BITREVERSE
318         select CRC16
319         select CRC32
320         help
321           This option adds support for SMSC LAN75XX based USB 2.0
322           Gigabit Ethernet adapters.
323 
324 config USB_NET_SMSC95XX
325         tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
326         depends on USB_USBNET
327         select BITREVERSE
328         select CRC16
329         select CRC32
330         help
331           This option adds support for SMSC LAN95XX based USB 2.0
332           10/100 Ethernet adapters.
333 
334 config USB_NET_GL620A
335         tristate "GeneSys GL620USB-A based cables"
336         depends on USB_USBNET
337         help
338           Choose this option if you're using a host-to-host cable,
339           or PC2PC motherboard, with this chip.
340 
341           Note that the half-duplex "GL620USB" is not supported.
342 
343 config USB_NET_NET1080
344         tristate "NetChip 1080 based cables (Laplink, ...)"
345         default y
346         depends on USB_USBNET
347         help
348           Choose this option if you're using a host-to-host cable based
349           on this design:  one NetChip 1080 chip and supporting logic,
350           optionally with LEDs that indicate traffic
351 
352 config USB_NET_PLUSB
353         tristate "Prolific PL-2301/2302/25A1 based cables"
354         # if the handshake/init/reset problems, from original 'plusb',
355         # are ever resolved ... then remove "experimental"
356         depends on USB_USBNET
357         help
358           Choose this option if you're using a host-to-host cable
359           with one of these chips.
360 
361 config USB_NET_MCS7830
362         tristate "MosChip MCS7830 based Ethernet adapters"
363         depends on USB_USBNET
364         help
365           Choose this option if you're using a 10/100 Ethernet USB2
366           adapter based on the MosChip 7830 controller. This includes
367           adapters marketed under the DeLOCK brand.
368 
369 config USB_NET_RNDIS_HOST
370         tristate "Host for RNDIS and ActiveSync devices"
371         depends on USB_USBNET
372         select USB_NET_CDCETHER
373         help
374           This option enables hosting "Remote NDIS" USB networking links,
375           as encouraged by Microsoft (instead of CDC Ethernet!) for use in
376           various devices that may only support this protocol.  A variant
377           of this protocol (with even less public documentation) seems to
378           be at the root of Microsoft's "ActiveSync" too.
379 
380           Avoid using this protocol unless you have no better options.
381           The protocol specification is incomplete, and is controlled by
382           (and for) Microsoft; it isn't an "Open" ecosystem or market.
383 
384 config USB_NET_CDC_SUBSET
385         tristate "Simple USB Network Links (CDC Ethernet subset)"
386         depends on USB_USBNET
387         default y
388         help
389           This driver module supports USB network devices that can work
390           without any device-specific information.  Select it if you have
391           one of these drivers.
392 
393           Note that while many USB host-to-host cables can work in this mode,
394           that may mean not being able to talk to Win32 systems or more
395           commonly not being able to handle certain events (like replugging
396           the host on the other end) very well.  Also, these devices will
397           not generally have permanently assigned Ethernet addresses.
398 
399 config USB_ALI_M5632
400         boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
401         depends on USB_NET_CDC_SUBSET
402         help
403           Choose this option if you're using a host-to-host cable
404           based on this design, which supports USB 2.0 high speed.
405 
406 config USB_AN2720
407         boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
408         depends on USB_NET_CDC_SUBSET
409         help
410           Choose this option if you're using a host-to-host cable
411           based on this design.  Note that AnchorChips is now a
412           Cypress brand.
413 
414 config USB_BELKIN
415         boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
416         depends on USB_NET_CDC_SUBSET
417         default y
418         help
419           Choose this option if you're using a host-to-host cable
420           based on this design:  two NetChip 2890 chips and an Atmel
421           microcontroller, with LEDs that indicate traffic.
422 
423 config USB_ARMLINUX
424         boolean "Embedded ARM Linux links (iPaq, ...)"
425         depends on USB_NET_CDC_SUBSET
426         default y
427         help
428           Choose this option to support the "usb-eth" networking driver
429           used by most of the ARM Linux community with device controllers
430           such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
431           in some PXA versions of the "blob" boot loader.
432 
433           Linux-based "Gumstix" PXA-25x based systems use this protocol
434           to talk with other Linux systems.
435 
436           Although the ROMs shipped with Sharp Zaurus products use a
437           different link level framing protocol, you can have them use
438           this simpler protocol by installing a different kernel.
439 
440 config USB_EPSON2888
441         boolean "Epson 2888 based firmware (DEVELOPMENT)"
442         depends on USB_NET_CDC_SUBSET
443         help
444           Choose this option to support the usb networking links used
445           by some sample firmware from Epson.
446 
447 config USB_KC2190
448         boolean "KT Technology KC2190 based cables (InstaNet)"
449         depends on USB_NET_CDC_SUBSET
450         help
451           Choose this option if you're using a host-to-host cable
452           with one of these chips.
453 
454 config USB_NET_ZAURUS
455         tristate "Sharp Zaurus (stock ROMs) and compatible"
456         depends on USB_USBNET
457         select USB_NET_CDCETHER
458         select CRC32
459         default y
460         help
461           Choose this option to support the usb networking links used by
462           Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
463           This also supports some related device firmware, as used in some
464           PDAs from Olympus and some cell phones from Motorola.
465 
466           If you install an alternate image, such as the Linux 2.6 based
467           versions of OpenZaurus, you should no longer need to support this
468           protocol.  Only the "eth-fd" or "net_fd" drivers in these devices
469           really need this non-conformant variant of CDC Ethernet (or in
470           some cases CDC MDLM) protocol, not "g_ether".
471 
472 config USB_NET_CX82310_ETH
473         tristate "Conexant CX82310 USB ethernet port"
474         depends on USB_USBNET
475         help
476           Choose this option if you're using a Conexant CX82310-based ADSL
477           router with USB ethernet port. This driver is for routers only,
478           it will not work with ADSL modems (use cxacru driver instead).
479 
480 config USB_NET_KALMIA
481         tristate "Samsung Kalmia based LTE USB modem"
482         depends on USB_USBNET
483         help
484           Choose this option if you have a Samsung Kalmia based USB modem
485           as Samsung GT-B3730.
486 
487           To compile this driver as a module, choose M here: the
488           module will be called kalmia.
489 
490 config USB_NET_QMI_WWAN
491         tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
492         depends on USB_USBNET
493         select USB_WDM
494         help
495           Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
496           (MDM) chipsets.  Examples of such devices are
497             * Huawei E392/E398
498 
499           This driver will only drive the ethernet part of the chips.
500           The devices require additional configuration to be usable.
501           Multiple management interfaces with linux drivers are
502           available:
503 
504             * option: AT commands on /dev/ttyUSBx
505             * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
506 
507           A modem manager with support for QMI is recommended.
508 
509           To compile this driver as a module, choose M here: the
510           module will be called qmi_wwan.
511 
512 config USB_HSO
513         tristate "Option USB High Speed Mobile Devices"
514         depends on USB && RFKILL && TTY
515         default n
516         help
517           Choose this option if you have an Option HSDPA/HSUPA card.
518           These cards support downlink speeds of 7.2Mbps or greater.
519 
520           To compile this driver as a module, choose M here: the
521           module will be called hso.
522 
523 config USB_NET_INT51X1
524         tristate "Intellon PLC based usb adapter"
525         depends on USB_USBNET
526         help
527           Choose this option if you're using a 14Mb USB-based PLC
528           (Powerline Communications) solution with an Intellon
529           INT51x1/INT5200 chip, like the "devolo dLan duo".
530 
531 config USB_CDC_PHONET
532         tristate "CDC Phonet support"
533         depends on PHONET
534         help
535           Choose this option to support the Phonet interface to a Nokia
536           cellular modem, as found on most Nokia handsets with the
537           "PC suite" USB profile.
538 
539 config USB_IPHETH
540         tristate "Apple iPhone USB Ethernet driver"
541         default n
542         ---help---
543           Module used to share Internet connection (tethering) from your
544           iPhone (Original, 3G and 3GS) to your system.
545           Note that you need userspace libraries and programs that are needed
546           to pair your device with your system and that understand the iPhone
547           protocol.
548 
549           For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
550 
551 config USB_SIERRA_NET
552         tristate "USB-to-WWAN Driver for Sierra Wireless modems"
553         depends on USB_USBNET
554         help
555           Choose this option if you have a Sierra Wireless USB-to-WWAN device.
556 
557           To compile this driver as a module, choose M here: the
558           module will be called sierra_net.
559 
560 config USB_VL600
561         tristate "LG VL600 modem dongle"
562         depends on USB_NET_CDCETHER && TTY
563         select USB_ACM
564         help
565           Select this if you want to use an LG Electronics 4G/LTE usb modem
566           called VL600.  This driver only handles the ethernet
567           interface exposed by the modem firmware.  To establish a connection
568           you will first need a userspace program that sends the right
569           command to the modem through its CDC ACM port, and most
570           likely also a DHCP client.  See this thread about using the
571           4G modem from Verizon:
572 
573           http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
574 
575 endif # USB_NET_DRIVERS

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us