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