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/usb/net/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"
99 This driver supports several kinds of network links over USB,
100 with "minidrivers" built around a common network driver core
101 that supports deep queues for efficient transfers. (This gives
102 better performance with small packets and at high speeds).
104 The USB host runs "usbnet", and the other end of the link might be:
106 - Another USB host, when using USB "network" or "data transfer"
107 cables. These are often used to network laptops to PCs, like
108 "Laplink" parallel cables or some motherboards. These rely
109 on specialized chips from many suppliers.
111 - An intelligent USB gadget, perhaps embedding a Linux system.
112 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
113 others), and devices that interoperate using the standard
114 CDC-Ethernet specification (including many cable modems).
116 - Network adapter hardware (like those for 10/100 Ethernet) which
117 uses this driver framework.
119 The link will appear with a name like "usb0", when the link is
120 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
121 two-node links are most easily managed with Ethernet Bridging
122 (CONFIG_BRIDGE) instead of routing.
124 For more information see <http://www.linux-usb.org/usbnet/>.
126 To compile this driver as a module, choose M here: the
127 module will be called usbnet.
129 config USB_NET_AX8817X
130 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
131 depends on USB_USBNET && NET_ETHERNET
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.
158 config USB_NET_CDCETHER
159 tristate "CDC Ethernet support (smart devices such as cable modems)"
160 depends on USB_USBNET
163 This option supports devices conforming to the Communication Device
164 Class (CDC) Ethernet Control Model, a specification that's easy to
165 implement in device firmware. The CDC specifications are available
166 from <http://www.usb.org/>.
168 CDC Ethernet is an implementation option for DOCSIS cable modems
169 that support USB connectivity, used for non-Microsoft USB hosts.
170 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
171 This driver should work with at least the following devices:
173 * Ericsson PipeRider (all variants)
174 * Motorola (DM100 and SB4100)
175 * Broadcom Cable Modem (reference design)
179 This driver creates an interface named "ethX", where X depends on
180 what other networking devices you have in use. However, if the
181 IEEE 802 "local assignment" bit is set in the address, a "usbX"
182 name is used instead.
184 config USB_NET_GL620A
185 tristate "GeneSys GL620USB-A based cables"
186 depends on USB_USBNET
188 Choose this option if you're using a host-to-host cable,
189 or PC2PC motherboard, with this chip.
191 Note that the half-duplex "GL620USB" is not supported.
193 config USB_NET_NET1080
194 tristate "NetChip 1080 based cables (Laplink, ...)"
196 depends on USB_USBNET
198 Choose this option if you're using a host-to-host cable based
199 on this design: one NetChip 1080 chip and supporting logic,
200 optionally with LEDs that indicate traffic
203 tristate "Prolific PL-2301/2302 based cables"
204 # if the handshake/init/reset problems, from original 'plusb',
205 # are ever resolved ... then remove "experimental"
206 depends on USB_USBNET && EXPERIMENTAL
208 Choose this option if you're using a host-to-host cable
209 with one of these chips.
211 config USB_NET_RNDIS_HOST
212 tristate "Host for RNDIS devices (EXPERIMENTAL)"
213 depends on USB_USBNET && EXPERIMENTAL
214 select USB_NET_CDCETHER
216 This option enables hosting "Remote NDIS" USB networking links,
217 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
218 various devices that may only support this protocol.
220 Avoid using this protocol unless you have no better options.
221 The protocol specification is incomplete, and is controlled by
222 (and for) Microsoft; it isn't an "Open" ecosystem or market.
224 config USB_NET_CDC_SUBSET
225 tristate "Simple USB Network Links (CDC Ethernet subset)"
226 depends on USB_USBNET
228 This driver module supports USB network devices that can work
229 without any device-specific information. Select it if you have
230 one of these drivers.
232 Note that while many USB host-to-host cables can work in this mode,
233 that may mean not being able to talk to Win32 systems or more
234 commonly not being able to handle certain events (like replugging
235 the host on the other end) very well. Also, these devices will
236 not generally have permanently assigned Ethernet addresses.
239 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
240 depends on USB_NET_CDC_SUBSET
242 Choose this option if you're using a host-to-host cable
243 based on this design, which supports USB 2.0 high speed.
246 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
247 depends on USB_NET_CDC_SUBSET
249 Choose this option if you're using a host-to-host cable
250 based on this design. Note that AnchorChips is now a
254 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
255 depends on USB_NET_CDC_SUBSET
258 Choose this option if you're using a host-to-host cable
259 based on this design: two NetChip 2890 chips and an Atmel
260 microcontroller, with LEDs that indicate traffic.
263 boolean "Embedded ARM Linux links (iPaq, ...)"
264 depends on USB_NET_CDC_SUBSET
267 Choose this option to support the "usb-eth" networking driver
268 used by most of the ARM Linux community with device controllers
269 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
270 in some PXA versions of the "blob" boot loader.
272 Linux-based "Gumstix" PXA-25x based systems use this protocol
273 to talk with other Linux systems.
275 Although the ROMs shipped with Sharp Zaurus products use a
276 different link level framing protocol, you can have them use
277 this simpler protocol by installing a different kernel.
280 boolean "Epson 2888 based firmware (DEVELOPMENT)"
281 depends on USB_NET_CDC_SUBSET
283 Choose this option to support the usb networking links used
284 by some sample firmware from Epson.
286 config USB_NET_ZAURUS
287 tristate "Sharp Zaurus (stock ROMs) and compatible"
288 depends on USB_USBNET
289 select USB_NET_CDCETHER
293 Choose this option to support the usb networking links used by
294 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
295 This also supports some related device firmware, as used in some
296 PDAs from Olympus and some cell phones from Motorola.
298 If you install an alternate image, such as the Linux 2.6 based
299 versions of OpenZaurus, you should no longer need to support this
300 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
301 really need this non-conformant variant of CDC Ethernet (or in
302 some cases CDC MDLM) protocol, not "g_ether".
306 tristate "USB ZD1201 based Wireless device support"
310 Say Y if you want to use wireless LAN adapters based on the ZyDAS
313 This driver makes the adapter appear as a normal Ethernet interface,
316 The zd1201 device requires external firmware to be loaded.
317 This can be found at http://linux-lc100020.sourceforge.net/
319 To compile this driver as a module, choose M here: the
320 module will be called zd1201.