2 # USB Network devices configuration
5 comment "Networking support is needed for USB Networking device support"
8 menu "USB Network adaptors"
12 tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
13 depends on USB && NET && EXPERIMENTAL
16 Say Y if you want to use one of the following 10Mbps USB Ethernet
17 device based on the EL1210A chip. Supported devices are:
24 This driver makes the adapter appear as a normal Ethernet interface,
25 typically on eth0, if it is the only ethernet device, or perhaps on
26 eth1, if you have a PCI or ISA ethernet card installed.
28 To compile this driver as a module, choose M here: the
29 module will be called catc.
32 tristate "USB ZyDAS Wireless Ethernet device support"
35 This is a module by USB. To support Wi-Fi 802.11g device.
37 #source "drivers/usb/net/Zydas/Kconfig"
40 tristate "USB KLSI KL5USB101-based ethernet device support"
43 Say Y here if you want to use one of the following 10Mbps only
44 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
48 ASANTE USB To Ethernet Adapter
49 AOX Endpoints USB Ethernet
51 D-Link DSB-650C and DU-E10
52 Entrega / Portgear E45
54 Jaton USB Ethernet Device Adapter
55 Kingston Technology USB Ethernet Adapter
57 Mobility USB-Ethernet Adapter
59 Peracom Enet and Enet2
60 Portsmith Express Ethernet Adapter
63 Sony Vaio port extender
65 This driver is likely to work with most 10Mbps only USB Ethernet
66 adapters, including some "no brand" devices. It does NOT work on
67 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
68 the CATC NetMate driver for those. If you are not sure which one
69 you need, select both, and the correct one should be selected for
72 This driver makes the adapter appear as a normal Ethernet interface,
73 typically on eth0, if it is the only ethernet device, or perhaps on
74 eth1, if you have a PCI or ISA ethernet card installed.
76 To compile this driver as a module, choose M here: the
77 module will be called kaweth.
80 tristate "USB Pegasus/Pegasus-II based ethernet device support"
84 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
85 If in doubt then look at <file:drivers/usb/net/pegasus.h> for the
86 complete list of supported devices.
88 If your particular adapter is not in the list and you are _sure_ it
89 is Pegasus or Pegasus II based then send me
90 <petkan@users.sourceforge.net> vendor and device IDs.
92 To compile this driver as a module, choose M here: the
93 module will be called pegasus.
96 tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
97 depends on USB && NET && EXPERIMENTAL
99 Say Y here if you have RTL8150 based usb-ethernet adapter.
100 Send me <petkan@users.sourceforge.net> any comments you may have.
101 You can also check for updates at <http://pegasus2.sourceforge.net/>.
103 To compile this driver as a module, choose M here: the
104 module will be called rtl8150.
107 tristate "Multi-purpose USB Networking Framework"
108 depends on USB && NET
110 This driver supports several kinds of network links over USB,
111 with "minidrivers" built around a common network driver core
112 that supports deep queues for efficient transfers. (This gives
113 better performance with small packets and at high speeds).
115 The USB host runs "usbnet", and the other end of the link might be:
117 - Another USB host, when using USB "network" or "data transfer"
118 cables. These are often used to network laptops to PCs, like
119 "Laplink" parallel cables or some motherboards. These rely
120 on specialized chips from many suppliers.
122 - An intelligent USB gadget, perhaps embedding a Linux system.
123 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
124 others), and devices that interoperate using the standard
125 CDC-Ethernet specification (including many cable modems).
127 - Network adapter hardware (like those for 10/100 Ethernet) which
128 uses this driver framework.
130 The link will appear with a name like "usb0", when the link is
131 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
132 two-node links are most easily managed with Ethernet Bridging
133 (CONFIG_BRIDGE) instead of routing.
135 For more information see <http://www.linux-usb.org/usbnet/>.
137 To compile this driver as a module, choose M here: the
138 module will be called usbnet.
140 comment "USB Host-to-Host Cables"
141 depends on USB_USBNET
144 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
145 depends on USB_USBNET
148 Choose this option if you're using a host-to-host cable
149 based on this design, which supports USB 2.0 high speed.
152 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
153 depends on USB_USBNET
156 Choose this option if you're using a host-to-host cable
157 based on this design. Note that AnchorChips is now a
161 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
162 depends on USB_USBNET
165 Choose this option if you're using a host-to-host cable
166 based on this design: two NetChip 2890 chips and an Atmel
167 microcontroller, with LEDs that indicate traffic.
170 boolean "GeneSys GL620USB-A based cables"
172 depends on USB_USBNET
174 Choose this option if you're using a host-to-host cable,
175 or PC2PC motherboard, with this chip.
177 Note that the half-duplex "GL620USB" is not supported.
180 boolean "NetChip 1080 based cables (Laplink, ...)"
182 depends on USB_USBNET
184 Choose this option if you're using a host-to-host cable based
185 on this design: one NetChip 1080 chips and supporting logic,
186 supporting LEDs that indicate traffic
189 boolean "Prolific PL-2301/2302 based cables"
191 # handshake/init/reset problems, from original 'plusb' driver
192 depends on USB_USBNET && EXPERIMENTAL
194 Choose this option if you're using a host-to-host cable
195 with one of these chips.
197 comment "Intelligent USB Devices/Gadgets"
198 depends on USB_USBNET
201 boolean "Embedded ARM Linux links (iPaq, ...)"
202 depends on USB_USBNET
205 Choose this option to support the "usb-eth" networking driver
206 used by most of the ARM Linux community with device controllers
207 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
208 in some PXA versions of the "blob" boot loader.
210 Although the ROMs shipped with Sharp Zaurus products use a
211 different link level framing protocol, you can have them use
212 this simpler protocol by installing a different kernel.
215 boolean "Epson 2888 based firmware (DEVELOPMENT)"
216 depends on USB_USBNET
219 Choose this option to support the usb networking links used
220 by some sample firmware from Epson.
223 boolean "Sharp Zaurus (stock ROMs)"
224 depends on USB_USBNET
228 Choose this option to support the usb networking links used by
229 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
231 If you install an alternate ROM image, you may no longer need
232 to support this protocol. Only the "eth-fd" driver really needs
233 this non-conformant variant of CDC Ethernet protocol.
236 boolean "CDC Ethernet support (smart devices such as cable modems)"
237 depends on USB_USBNET
240 This option supports devices conforming to the Communication Device
241 Class (CDC) Ethernet Control Model, a specification that's easy to
242 implement in device firmware. The CDC specifications are available
243 from <http://www.usb.org/>.
245 CDC Ethernet is an implementation option for DOCSIS cable modems
246 that support USB connectivity, used for non-Microsoft USB hosts.
247 This driver should work with at least the following devices:
249 * Ericsson PipeRider (all variants)
250 * Motorola (DM100 and SB4100)
251 * Broadcom Cable Modem (reference design)
255 This driver creates an interface named "ethX", where X depends on
256 what other networking devices you have in use. However, if the
257 IEEE 802 "local assignment" bit is set in the address, a "usbX"
258 name is used instead.
260 comment "USB Network Adapters"
261 depends on USB_USBNET
264 boolean "ASIX AX88172 Based USB 2.0 Ethernet Devices"
265 depends on USB_USBNET && NET_ETHERNET
271 This option adds support for ASIX AX88172 based USB 2.0
272 10/100 Ethernet devices.
274 This driver should work with at least the following devices:
281 * Intellinet USB 2.0 Ethernet
282 * ST Lab USB 2.0 Ethernet
285 This driver creates an interface named "ethX", where X depends on
286 what other networking devices you have in use.
290 tristate "Usb wireless for zd1201 & zd1201b"
291 depends on ARCH_MOXACPU
293 Say Y if you want to use zydas zd1201 wireless driver.