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
88 Say Y here if you have RTL8150 based usb-ethernet adapter.
89 Send me <petkan@users.sourceforge.net> any comments you may have.
90 You can also check for updates at <http://pegasus2.sourceforge.net/>.
92 To compile this driver as a module, choose M here: the
93 module will be called rtl8150.
96 tristate "Multi-purpose USB Networking Framework"
98 This driver supports several kinds of network links over USB,
99 with "minidrivers" built around a common network driver core
100 that supports deep queues for efficient transfers. (This gives
101 better performance with small packets and at high speeds).
103 The USB host runs "usbnet", and the other end of the link might be:
105 - Another USB host, when using USB "network" or "data transfer"
106 cables. These are often used to network laptops to PCs, like
107 "Laplink" parallel cables or some motherboards. These rely
108 on specialized chips from many suppliers.
110 - An intelligent USB gadget, perhaps embedding a Linux system.
111 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
112 others), and devices that interoperate using the standard
113 CDC-Ethernet specification (including many cable modems).
115 - Network adapter hardware (like those for 10/100 Ethernet) which
116 uses this driver framework.
118 The link will appear with a name like "usb0", when the link is
119 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
120 two-node links are most easily managed with Ethernet Bridging
121 (CONFIG_BRIDGE) instead of routing.
123 For more information see <http://www.linux-usb.org/usbnet/>.
125 To compile this driver as a module, choose M here: the
126 module will be called usbnet.
128 comment "USB Host-to-Host Cables"
129 depends on USB_USBNET
132 boolean "GeneSys GL620USB-A based cables"
134 depends on USB_USBNET
136 Choose this option if you're using a host-to-host cable,
137 or PC2PC motherboard, with this chip.
139 Note that the half-duplex "GL620USB" is not supported.
142 boolean "NetChip 1080 based cables (Laplink, ...)"
144 depends on USB_USBNET
146 Choose this option if you're using a host-to-host cable based
147 on this design: one NetChip 1080 chips and supporting logic,
148 supporting LEDs that indicate traffic
151 boolean "Prolific PL-2301/2302 based cables"
153 # handshake/init/reset problems, from original 'plusb' driver
154 depends on USB_USBNET && EXPERIMENTAL
156 Choose this option if you're using a host-to-host cable
157 with one of these chips.
159 comment "Intelligent USB Devices/Gadgets"
160 depends on USB_USBNET
163 boolean "Sharp Zaurus (stock ROMs) and compatible"
164 depends on USB_USBNET
168 Choose this option to support the usb networking links used by
169 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
170 This also supports some related device firmware, as used in some
171 PDAs from Olympus and some cell phones from Motorola.
173 If you install an alternate ROM image, such as the Linux 2.6 based
174 versions of OpenZaurus, you should no longer need to support this
175 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
176 really need this non-conformant variant of CDC Ethernet (or in
177 some cases CDC MDLM) protocol, not "g_ether".
180 boolean "CDC Ethernet support (smart devices such as cable modems)"
181 depends on USB_USBNET
184 This option supports devices conforming to the Communication Device
185 Class (CDC) Ethernet Control Model, a specification that's easy to
186 implement in device firmware. The CDC specifications are available
187 from <http://www.usb.org/>.
189 CDC Ethernet is an implementation option for DOCSIS cable modems
190 that support USB connectivity, used for non-Microsoft USB hosts.
191 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
192 This driver should work with at least the following devices:
194 * Ericsson PipeRider (all variants)
195 * Motorola (DM100 and SB4100)
196 * Broadcom Cable Modem (reference design)
200 This driver creates an interface named "ethX", where X depends on
201 what other networking devices you have in use. However, if the
202 IEEE 802 "local assignment" bit is set in the address, a "usbX"
203 name is used instead.
205 comment "USB Network Adapters"
206 depends on USB_USBNET
209 boolean "ASIX AX88xxx Based USB 2.0 Ethernet Devices"
210 depends on USB_USBNET && NET_ETHERNET
215 This option adds support for ASIX AX88xxx based USB 2.0
216 10/100 Ethernet devices.
218 This driver should work with at least the following devices:
221 * Billionton Systems, USB2AR
223 * Corega FEther USB2-TX
229 * Intellinet USB 2.0 Ethernet
230 * ST Lab USB 2.0 Ethernet
233 This driver creates an interface named "ethX", where X depends on
234 what other networking devices you have in use.
237 config USB_NET_CDC_SUBSET
238 tristate "Simple USB Network Links (CDC Ethernet subset)"
239 depends on USB_USBNET
241 This driver module supports USB network devices that can work
242 without any device-specific information. Select it if you have
243 one of these drivers.
245 Note that while many USB host-to-host cables can work in this mode,
246 that may mean not being able to talk to Win32 systems or more
247 commonly not being able to handle certain events (like replugging
248 the host on the other end) very well. Also, these devices will
249 not generally have permanently assigned Ethernet addresses.
252 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
253 depends on USB_NET_CDC_SUBSET
255 Choose this option if you're using a host-to-host cable
256 based on this design, which supports USB 2.0 high speed.
259 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
260 depends on USB_NET_CDC_SUBSET
262 Choose this option if you're using a host-to-host cable
263 based on this design. Note that AnchorChips is now a
267 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
268 depends on USB_NET_CDC_SUBSET
271 Choose this option if you're using a host-to-host cable
272 based on this design: two NetChip 2890 chips and an Atmel
273 microcontroller, with LEDs that indicate traffic.
276 boolean "Embedded ARM Linux links (iPaq, ...)"
277 depends on USB_NET_CDC_SUBSET
280 Choose this option to support the "usb-eth" networking driver
281 used by most of the ARM Linux community with device controllers
282 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
283 in some PXA versions of the "blob" boot loader.
285 Linux-based "Gumstix" PXA-25x based systems use this protocol
286 to talk with other Linux systems.
288 Although the ROMs shipped with Sharp Zaurus products use a
289 different link level framing protocol, you can have them use
290 this simpler protocol by installing a different kernel.
293 boolean "Epson 2888 based firmware (DEVELOPMENT)"
294 depends on USB_NET_CDC_SUBSET
296 Choose this option to support the usb networking links used
297 by some sample firmware from Epson.
301 tristate "USB ZD1201 based Wireless device support"
305 Say Y if you want to use wireless LAN adapters based on the ZyDAS
308 This driver makes the adapter appear as a normal Ethernet interface,
311 The zd1201 device requires external firmware to be loaded.
312 This can be found at http://linux-lc100020.sourceforge.net/
314 To compile this driver as a module, choose M here: the
315 module will be called zd1201.