2 # USB Network devices configuration
4 comment "USB Network adaptors"
7 comment "Networking support is needed for USB Networking device support"
11 tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
12 depends on USB && NET && 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"
34 Say Y here if you want to use one of the following 10Mbps only
35 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
39 ASANTE USB To Ethernet Adapter
40 AOX Endpoints USB Ethernet
42 D-Link DSB-650C and DU-E10
43 Entrega / Portgear E45
45 Jaton USB Ethernet Device Adapter
46 Kingston Technology USB Ethernet Adapter
48 Mobility USB-Ethernet Adapter
50 Peracom Enet and Enet2
51 Portsmith Express Ethernet Adapter
54 Sony Vaio port extender
56 This driver is likely to work with most 10Mbps only USB Ethernet
57 adapters, including some "no brand" devices. It does NOT work on
58 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
59 the CATC NetMate driver for those. If you are not sure which one
60 you need, select both, and the correct one should be selected for
63 This driver makes the adapter appear as a normal Ethernet interface,
64 typically on eth0, if it is the only ethernet device, or perhaps on
65 eth1, if you have a PCI or ISA ethernet card installed.
67 To compile this driver as a module, choose M here: the
68 module will be called kaweth.
71 tristate "USB Pegasus/Pegasus-II based ethernet device support"
75 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
76 If in doubt then look at <file:drivers/usb/net/pegasus.h> for the
77 complete list of supported devices.
79 If your particular adapter is not in the list and you are _sure_ it
80 is Pegasus or Pegasus II based then send me
81 <petkan@users.sourceforge.net> vendor and device IDs.
83 To compile this driver as a module, choose M here: the
84 module will be called pegasus.
87 tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
88 depends on USB && NET && EXPERIMENTAL
90 Say Y here if you have RTL8150 based usb-ethernet adapter.
91 Send me <petkan@users.sourceforge.net> any comments you may have.
92 You can also check for updates at <http://pegasus2.sourceforge.net/>.
94 To compile this driver as a module, choose M here: the
95 module will be called rtl8150.
98 tristate "Multi-purpose USB Networking Framework"
101 This driver supports several kinds of network links over USB,
102 with "minidrivers" built around a common network driver core
103 that supports deep queues for efficient transfers. (This gives
104 better performance with small packets and at high speeds).
106 The USB host runs "usbnet", and the other end of the link might be:
108 - Another USB host, when using USB "network" or "data transfer"
109 cables. These are often used to network laptops to PCs, like
110 "Laplink" parallel cables or some motherboards. These rely
111 on specialized chips from many suppliers.
113 - An intelligent USB gadget, perhaps embedding a Linux system.
114 These include PDAs running Linux (iPaq, Yopy, Zaurus, and
115 others), and devices that interoperate using the standard
116 CDC-Ethernet specification (including many cable modems).
118 - Network adapter hardware (like those for 10/100 Ethernet) which
119 uses this driver framework.
121 The link will appear with a name like "usb0", when the link is
122 a two-node link, or "eth0" for most CDC-Ethernet devices. Those
123 two-node links are most easily managed with Ethernet Bridging
124 (CONFIG_BRIDGE) instead of routing.
126 For more information see <http://www.linux-usb.org/usbnet/>.
128 To compile this driver as a module, choose M here: the
129 module will be called usbnet.
131 comment "USB Host-to-Host Cables"
132 depends on USB_USBNET
135 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
136 depends on USB_USBNET
139 Choose this option if you're using a host-to-host cable
140 based on this design, which supports USB 2.0 high speed.
143 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
144 depends on USB_USBNET
147 Choose this option if you're using a host-to-host cable
148 based on this design. Note that AnchorChips is now a
152 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
153 depends on USB_USBNET
156 Choose this option if you're using a host-to-host cable
157 based on this design: two NetChip 2890 chips and an Atmel
158 microcontroller, with LEDs that indicate traffic.
161 boolean "GeneSys GL620USB-A based cables"
163 depends on USB_USBNET
165 Choose this option if you're using a host-to-host cable,
166 or PC2PC motherboard, with this chip.
168 Note that the half-duplex "GL620USB" is not supported.
171 boolean "NetChip 1080 based cables (Laplink, ...)"
173 depends on USB_USBNET
175 Choose this option if you're using a host-to-host cable based
176 on this design: one NetChip 1080 chips and supporting logic,
177 supporting LEDs that indicate traffic
180 boolean "Prolific PL-2301/2302 based cables"
182 # handshake/init/reset problems, from original 'plusb' driver
183 depends on USB_USBNET && EXPERIMENTAL
185 Choose this option if you're using a host-to-host cable
186 with one of these chips.
188 comment "Intelligent USB Devices/Gadgets"
189 depends on USB_USBNET
192 boolean "Embedded ARM Linux links (iPaq, ...)"
193 depends on USB_USBNET
196 Choose this option to support the "usb-eth" networking driver
197 used by most of the ARM Linux community with device controllers
198 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
199 in some PXA versions of the "blob" boot loader.
201 Although the ROMs shipped with Sharp Zaurus products use a
202 different link level framing protocol, you can have them use
203 this simpler protocol by installing a different kernel.
206 boolean "Epson 2888 based firmware (DEVELOPMENT)"
207 depends on USB_USBNET
210 Choose this option to support the usb networking links used
211 by some sample firmware from Epson.
214 boolean "Sharp Zaurus (stock ROMs)"
215 depends on USB_USBNET
219 Choose this option to support the usb networking links used by
220 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
222 If you install an alternate ROM image, you may no longer need
223 to support this protocol. Only the "eth-fd" driver really needs
224 this non-conformant variant of CDC Ethernet protocol.
227 boolean "CDC Ethernet support (smart devices such as cable modems)"
228 depends on USB_USBNET
231 This option supports devices conforming to the Communication Device
232 Class (CDC) Ethernet Control Model, a specification that's easy to
233 implement in device firmware. The CDC specifications are available
234 from <http://www.usb.org/>.
236 CDC Ethernet is an implementation option for DOCSIS cable modems
237 that support USB connectivity, used for non-Microsoft USB hosts.
238 This driver should work with at least the following devices:
240 * Ericsson PipeRider (all variants)
241 * Motorola (DM100 and SB4100)
242 * Broadcom Cable Modem (reference design)
246 This driver creates an interface named "ethX", where X depends on
247 what other networking devices you have in use. However, if the
248 IEEE 802 "local assignment" bit is set in the address, a "usbX"
249 name is used instead.
251 comment "USB Network Adapters"
252 depends on USB_USBNET
255 boolean "ASIX AX88172 Based USB 2.0 Ethernet Devices"
256 depends on USB_USBNET && NET_ETHERNET
262 This option adds support for ASIX AX88172 based USB 2.0
263 10/100 Ethernet devices.
265 This driver should work with at least the following devices:
272 * Intellinet USB 2.0 Ethernet
273 * ST Lab USB 2.0 Ethernet
276 This driver creates an interface named "ethX", where X depends on
277 what other networking devices you have in use.