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 (EXPERIMENTAL)"
12 depends on EXPERIMENTAL
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:
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.
27 To compile this driver as a module, choose M here: the
28 module will be called catc.
31 tristate "USB KLSI KL5USB101-based ethernet device support"
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:
38 ASANTE USB To Ethernet Adapter
39 AOX Endpoints USB Ethernet
41 D-Link DSB-650C and DU-E10
42 Entrega / Portgear E45
44 Jaton USB Ethernet Device Adapter
45 Kingston Technology USB Ethernet Adapter
47 Mobility USB-Ethernet Adapter
49 Peracom Enet and Enet2
50 Portsmith Express Ethernet Adapter
53 Sony Vaio port extender
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
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.
66 To compile this driver as a module, choose M here: the
67 module will be called kaweth.
70 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 (EXPERIMENTAL)"
86 depends on EXPERIMENTAL
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 "Multi-purpose USB Networking Framework"
100 This driver supports several kinds of network links over USB,
101 with "minidrivers" built around a common network driver core
102 that supports deep queues for efficient transfers. (This gives
103 better performance with small packets and at high speeds).
105 The USB host runs "usbnet", and the other end of the link might be:
107 - Another USB host, when using USB "network" or "data transfer"
108 cables. These are often used to network laptops to PCs, like
109 "Laplink" parallel cables or some motherboards. These rely
110 on specialized chips from many suppliers.
112 - An intelligent USB gadget, perhaps embedding a Linux system.
113 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
114 others), and devices that interoperate using the standard
115 CDC-Ethernet specification (including many cable modems).
117 - Network adapter hardware (like those for 10/100 Ethernet) which
118 uses this driver framework.
120 The link will appear with a name like "usb0", when the link is
121 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
122 two-node links are most easily managed with Ethernet Bridging
123 (CONFIG_BRIDGE) instead of routing.
125 For more information see <http://www.linux-usb.org/usbnet/>.
127 To compile this driver as a module, choose M here: the
128 module will be called usbnet.
130 config USB_NET_AX8817X
131 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
132 depends on USB_USBNET
136 This option adds support for ASIX AX88xxx based USB 2.0
137 10/100 Ethernet adapters.
139 This driver should work with at least the following devices:
142 * Billionton Systems, USB2AR
144 * Corega FEther USB2-TX
150 * Intellinet USB 2.0 Ethernet
151 * ST Lab USB 2.0 Ethernet
154 This driver creates an interface named "ethX", where X depends on
155 what other networking devices you have in use.
157 config USB_NET_CDCETHER
158 tristate "CDC Ethernet support (smart devices such as cable modems)"
159 depends on USB_USBNET
162 This option supports devices conforming to the Communication Device
163 Class (CDC) Ethernet Control Model, a specification that's easy to
164 implement in device firmware. The CDC specifications are available
165 from <http://www.usb.org/>.
167 CDC Ethernet is an implementation option for DOCSIS cable modems
168 that support USB connectivity, used for non-Microsoft USB hosts.
169 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
170 This driver should work with at least the following devices:
172 * Dell Wireless 5530 HSPA
173 * Ericsson PipeRider (all variants)
174 * Ericsson Mobile Broadband Module (all variants)
175 * Motorola (DM100 and SB4100)
176 * Broadcom Cable Modem (reference design)
177 * Toshiba (PCX1100U and F3507g)
180 This driver creates an interface named "ethX", where X depends on
181 what other networking devices you have in use. However, if the
182 IEEE 802 "local assignment" bit is set in the address, a "usbX"
183 name is used instead.
185 config USB_NET_CDC_EEM
186 tristate "CDC EEM support"
187 depends on USB_USBNET && EXPERIMENTAL
189 This option supports devices conforming to the Communication Device
190 Class (CDC) Ethernet Emulation Model, a specification that's easy to
191 implement in device firmware. The CDC EEM specifications are available
192 from <http://www.usb.org/>.
194 This driver creates an interface named "ethX", where X depends on
195 what other networking devices you have in use. However, if the
196 IEEE 802 "local assignment" bit is set in the address, a "usbX"
197 name is used instead.
199 config USB_NET_DM9601
200 tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices"
201 depends on USB_USBNET
204 This option adds support for Davicom DM9601 based USB 1.1
205 10/100 Ethernet adapters.
207 config USB_NET_SMSC95XX
208 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
209 depends on USB_USBNET
212 This option adds support for SMSC LAN95XX based USB 2.0
213 10/100 Ethernet adapters.
215 config USB_NET_GL620A
216 tristate "GeneSys GL620USB-A based cables"
217 depends on USB_USBNET
219 Choose this option if you're using a host-to-host cable,
220 or PC2PC motherboard, with this chip.
222 Note that the half-duplex "GL620USB" is not supported.
224 config USB_NET_NET1080
225 tristate "NetChip 1080 based cables (Laplink, ...)"
227 depends on USB_USBNET
229 Choose this option if you're using a host-to-host cable based
230 on this design: one NetChip 1080 chip and supporting logic,
231 optionally with LEDs that indicate traffic
234 tristate "Prolific PL-2301/2302 based cables"
235 # if the handshake/init/reset problems, from original 'plusb',
236 # are ever resolved ... then remove "experimental"
237 depends on USB_USBNET && EXPERIMENTAL
239 Choose this option if you're using a host-to-host cable
240 with one of these chips.
242 config USB_NET_MCS7830
243 tristate "MosChip MCS7830 based Ethernet adapters"
244 depends on USB_USBNET
246 Choose this option if you're using a 10/100 Ethernet USB2
247 adapter based on the MosChip 7830 controller. This includes
248 adapters marketed under the DeLOCK brand.
250 config USB_NET_RNDIS_HOST
251 tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)"
252 depends on USB_USBNET && EXPERIMENTAL
253 select USB_NET_CDCETHER
255 This option enables hosting "Remote NDIS" USB networking links,
256 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
257 various devices that may only support this protocol. A variant
258 of this protocol (with even less public documentation) seems to
259 be at the root of Microsoft's "ActiveSync" too.
261 Avoid using this protocol unless you have no better options.
262 The protocol specification is incomplete, and is controlled by
263 (and for) Microsoft; it isn't an "Open" ecosystem or market.
265 config USB_NET_CDC_SUBSET
266 tristate "Simple USB Network Links (CDC Ethernet subset)"
267 depends on USB_USBNET
270 This driver module supports USB network devices that can work
271 without any device-specific information. Select it if you have
272 one of these drivers.
274 Note that while many USB host-to-host cables can work in this mode,
275 that may mean not being able to talk to Win32 systems or more
276 commonly not being able to handle certain events (like replugging
277 the host on the other end) very well. Also, these devices will
278 not generally have permanently assigned Ethernet addresses.
281 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
282 depends on USB_NET_CDC_SUBSET
284 Choose this option if you're using a host-to-host cable
285 based on this design, which supports USB 2.0 high speed.
288 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
289 depends on USB_NET_CDC_SUBSET
291 Choose this option if you're using a host-to-host cable
292 based on this design. Note that AnchorChips is now a
296 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
297 depends on USB_NET_CDC_SUBSET
300 Choose this option if you're using a host-to-host cable
301 based on this design: two NetChip 2890 chips and an Atmel
302 microcontroller, with LEDs that indicate traffic.
305 boolean "Embedded ARM Linux links (iPaq, ...)"
306 depends on USB_NET_CDC_SUBSET
309 Choose this option to support the "usb-eth" networking driver
310 used by most of the ARM Linux community with device controllers
311 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
312 in some PXA versions of the "blob" boot loader.
314 Linux-based "Gumstix" PXA-25x based systems use this protocol
315 to talk with other Linux systems.
317 Although the ROMs shipped with Sharp Zaurus products use a
318 different link level framing protocol, you can have them use
319 this simpler protocol by installing a different kernel.
322 boolean "Epson 2888 based firmware (DEVELOPMENT)"
323 depends on USB_NET_CDC_SUBSET
325 Choose this option to support the usb networking links used
326 by some sample firmware from Epson.
329 boolean "KT Technology KC2190 based cables (InstaNet)"
330 depends on USB_NET_CDC_SUBSET && EXPERIMENTAL
332 Choose this option if you're using a host-to-host cable
333 with one of these chips.
335 config USB_NET_ZAURUS
336 tristate "Sharp Zaurus (stock ROMs) and compatible"
337 depends on USB_USBNET
338 select USB_NET_CDCETHER
342 Choose this option to support the usb networking links used by
343 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
344 This also supports some related device firmware, as used in some
345 PDAs from Olympus and some cell phones from Motorola.
347 If you install an alternate image, such as the Linux 2.6 based
348 versions of OpenZaurus, you should no longer need to support this
349 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
350 really need this non-conformant variant of CDC Ethernet (or in
351 some cases CDC MDLM) protocol, not "g_ether".
354 tristate "Option USB High Speed Mobile Devices"
355 depends on USB && RFKILL
358 Choose this option if you have an Option HSDPA/HSUPA card.
359 These cards support downlink speeds of 7.2Mbps or greater.
361 To compile this driver as a module, choose M here: the
362 module will be called hso.
364 config USB_NET_INT51X1
365 tristate "Intellon PLC based usb adapter"
366 depends on USB_USBNET
368 Choose this option if you're using a 14Mb USB-based PLC
369 (Powerline Communications) solution with an Intellon
370 INT51x1/INT5200 chip, like the "devolo dLan duo".