]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # USB Network devices configuration | |
3 | # | |
4 | comment "Networking support is needed for USB Network Adapter support" | |
5 | depends on USB && !NET | |
6 | ||
7 | menu "USB Network Adapters" | |
8 | depends on USB && NET | |
9 | ||
10 | config USB_CATC | |
11 | tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)" | |
12 | depends on EXPERIMENTAL | |
13 | select CRC32 | |
14 | ---help--- | |
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: | |
17 | Belkin F5U011 | |
18 | Belkin F5U111 | |
19 | CATC NetMate | |
20 | CATC NetMate II | |
21 | smartBridges smartNIC | |
22 | ||
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. | |
26 | ||
27 | To compile this driver as a module, choose M here: the | |
28 | module will be called catc. | |
29 | ||
30 | config USB_KAWETH | |
31 | tristate "USB KLSI KL5USB101-based ethernet device support" | |
32 | ---help--- | |
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: | |
35 | 3Com 3C19250 | |
36 | ADS USB-10BT | |
37 | ATEN USB Ethernet | |
38 | ASANTE USB To Ethernet Adapter | |
39 | AOX Endpoints USB Ethernet | |
40 | Correga K.K. | |
41 | D-Link DSB-650C and DU-E10 | |
42 | Entrega / Portgear E45 | |
43 | I-O DATA USB-ET/T | |
44 | Jaton USB Ethernet Device Adapter | |
45 | Kingston Technology USB Ethernet Adapter | |
46 | Linksys USB10T | |
47 | Mobility USB-Ethernet Adapter | |
48 | NetGear EA-101 | |
49 | Peracom Enet and Enet2 | |
50 | Portsmith Express Ethernet Adapter | |
51 | Shark Pocket Adapter | |
52 | SMC 2202USB | |
53 | Sony Vaio port extender | |
54 | ||
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 | |
60 | you. | |
61 | ||
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. | |
65 | ||
66 | To compile this driver as a module, choose M here: the | |
67 | module will be called kaweth. | |
68 | ||
69 | config USB_PEGASUS | |
70 | tristate "USB Pegasus/Pegasus-II based ethernet device support" | |
71 | select MII | |
72 | ---help--- | |
73 | Say Y here if you know you have Pegasus or Pegasus-II based adapter. | |
582fe6fb | 74 | If in doubt then look at <file:drivers/net/usb/pegasus.h> for the |
1da177e4 LT |
75 | complete list of supported devices. |
76 | ||
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. | |
80 | ||
81 | To compile this driver as a module, choose M here: the | |
82 | module will be called pegasus. | |
83 | ||
84 | config USB_RTL8150 | |
85 | tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)" | |
86 | depends on EXPERIMENTAL | |
d0b4e310 | 87 | select MII |
1da177e4 LT |
88 | help |
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/>. | |
92 | ||
93 | To compile this driver as a module, choose M here: the | |
94 | module will be called rtl8150. | |
95 | ||
96 | config USB_USBNET | |
97 | tristate "Multi-purpose USB Networking Framework" | |
4aa92cd9 | 98 | select MII |
1da177e4 LT |
99 | ---help--- |
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). | |
090ffa9d | 104 | |
1da177e4 LT |
105 | The USB host runs "usbnet", and the other end of the link might be: |
106 | ||
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. | |
111 | ||
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). | |
116 | ||
117 | - Network adapter hardware (like those for 10/100 Ethernet) which | |
118 | uses this driver framework. | |
119 | ||
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. | |
124 | ||
125 | For more information see <http://www.linux-usb.org/usbnet/>. | |
126 | ||
127 | To compile this driver as a module, choose M here: the | |
128 | module will be called usbnet. | |
129 | ||
2e55cc72 DB |
130 | config USB_NET_AX8817X |
131 | tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" | |
c6cbcad1 | 132 | depends on USB_USBNET |
1da177e4 | 133 | select CRC32 |
1da177e4 LT |
134 | default y |
135 | help | |
136 | This option adds support for ASIX AX88xxx based USB 2.0 | |
2e55cc72 | 137 | 10/100 Ethernet adapters. |
1da177e4 LT |
138 | |
139 | This driver should work with at least the following devices: | |
140 | * Aten UC210T | |
141 | * ASIX AX88172 | |
2e55cc72 | 142 | * Billionton Systems, USB2AR |
1da177e4 LT |
143 | * Buffalo LUA-U2-KTX |
144 | * Corega FEther USB2-TX | |
145 | * D-Link DUB-E100 | |
146 | * Hawking UF200 | |
147 | * Linksys USB200M | |
148 | * Netgear FA120 | |
149 | * Sitecom LN-029 | |
150 | * Intellinet USB 2.0 Ethernet | |
151 | * ST Lab USB 2.0 Ethernet | |
152 | * TrendNet TU2-ET100 | |
153 | ||
154 | This driver creates an interface named "ethX", where X depends on | |
2e55cc72 | 155 | what other networking devices you have in use. |
1da177e4 | 156 | |
72dc1c09 GKH |
157 | config USB_HSO |
158 | tristate "Option USB High Speed Mobile Devices" | |
159 | depends on USB && RFKILL | |
160 | default n | |
161 | help | |
162 | Choose this option if you have an Option HSDPA/HSUPA card. | |
163 | These cards support downlink speeds of 7.2Mbps or greater. | |
164 | ||
165 | To compile this driver as a module, choose M here: the | |
166 | module will be called hso. | |
38bde1d4 | 167 | |
4324fd49 DB |
168 | config USB_NET_CDCETHER |
169 | tristate "CDC Ethernet support (smart devices such as cable modems)" | |
170 | depends on USB_USBNET | |
171 | default y | |
172 | help | |
173 | This option supports devices conforming to the Communication Device | |
174 | Class (CDC) Ethernet Control Model, a specification that's easy to | |
175 | implement in device firmware. The CDC specifications are available | |
176 | from <http://www.usb.org/>. | |
177 | ||
178 | CDC Ethernet is an implementation option for DOCSIS cable modems | |
179 | that support USB connectivity, used for non-Microsoft USB hosts. | |
180 | The Linux-USB CDC Ethernet Gadget driver is an open implementation. | |
181 | This driver should work with at least the following devices: | |
182 | ||
183 | * Ericsson PipeRider (all variants) | |
184 | * Motorola (DM100 and SB4100) | |
185 | * Broadcom Cable Modem (reference design) | |
186 | * Toshiba PCX1100U | |
187 | * ... | |
188 | ||
189 | This driver creates an interface named "ethX", where X depends on | |
190 | what other networking devices you have in use. However, if the | |
191 | IEEE 802 "local assignment" bit is set in the address, a "usbX" | |
192 | name is used instead. | |
193 | ||
d0374f4f PK |
194 | config USB_NET_DM9601 |
195 | tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices" | |
196 | depends on USB_USBNET | |
197 | select CRC32 | |
d0374f4f PK |
198 | help |
199 | This option adds support for Davicom DM9601 based USB 1.1 | |
200 | 10/100 Ethernet adapters. | |
201 | ||
47ee3051 DB |
202 | config USB_NET_GL620A |
203 | tristate "GeneSys GL620USB-A based cables" | |
204 | depends on USB_USBNET | |
205 | help | |
206 | Choose this option if you're using a host-to-host cable, | |
207 | or PC2PC motherboard, with this chip. | |
208 | ||
209 | Note that the half-duplex "GL620USB" is not supported. | |
210 | ||
904813cd DB |
211 | config USB_NET_NET1080 |
212 | tristate "NetChip 1080 based cables (Laplink, ...)" | |
213 | default y | |
214 | depends on USB_USBNET | |
215 | help | |
216 | Choose this option if you're using a host-to-host cable based | |
217 | on this design: one NetChip 1080 chip and supporting logic, | |
218 | optionally with LEDs that indicate traffic | |
219 | ||
090ffa9d DB |
220 | config USB_NET_PLUSB |
221 | tristate "Prolific PL-2301/2302 based cables" | |
222 | # if the handshake/init/reset problems, from original 'plusb', | |
223 | # are ever resolved ... then remove "experimental" | |
224 | depends on USB_USBNET && EXPERIMENTAL | |
225 | help | |
226 | Choose this option if you're using a host-to-host cable | |
227 | with one of these chips. | |
228 | ||
2a36d708 AB |
229 | config USB_NET_MCS7830 |
230 | tristate "MosChip MCS7830 based Ethernet adapters" | |
231 | depends on USB_USBNET | |
232 | help | |
233 | Choose this option if you're using a 10/100 Ethernet USB2 | |
234 | adapter based on the MosChip 7830 controller. This includes | |
235 | adapters marketed under the DeLOCK brand. | |
236 | ||
64e04910 | 237 | config USB_NET_RNDIS_HOST |
ad55d71a | 238 | tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)" |
64e04910 DB |
239 | depends on USB_USBNET && EXPERIMENTAL |
240 | select USB_NET_CDCETHER | |
241 | help | |
242 | This option enables hosting "Remote NDIS" USB networking links, | |
243 | as encouraged by Microsoft (instead of CDC Ethernet!) for use in | |
ad55d71a OAVR |
244 | various devices that may only support this protocol. A variant |
245 | of this protocol (with even less public documentation) seems to | |
246 | be at the root of Microsoft's "ActiveSync" too. | |
64e04910 DB |
247 | |
248 | Avoid using this protocol unless you have no better options. | |
249 | The protocol specification is incomplete, and is controlled by | |
250 | (and for) Microsoft; it isn't an "Open" ecosystem or market. | |
251 | ||
38bde1d4 DB |
252 | config USB_NET_CDC_SUBSET |
253 | tristate "Simple USB Network Links (CDC Ethernet subset)" | |
254 | depends on USB_USBNET | |
691895c6 | 255 | default y |
38bde1d4 DB |
256 | help |
257 | This driver module supports USB network devices that can work | |
258 | without any device-specific information. Select it if you have | |
259 | one of these drivers. | |
260 | ||
261 | Note that while many USB host-to-host cables can work in this mode, | |
262 | that may mean not being able to talk to Win32 systems or more | |
263 | commonly not being able to handle certain events (like replugging | |
264 | the host on the other end) very well. Also, these devices will | |
265 | not generally have permanently assigned Ethernet addresses. | |
266 | ||
267 | config USB_ALI_M5632 | |
268 | boolean "ALi M5632 based 'USB 2.0 Data Link' cables" | |
269 | depends on USB_NET_CDC_SUBSET | |
270 | help | |
271 | Choose this option if you're using a host-to-host cable | |
272 | based on this design, which supports USB 2.0 high speed. | |
273 | ||
274 | config USB_AN2720 | |
275 | boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)" | |
276 | depends on USB_NET_CDC_SUBSET | |
277 | help | |
278 | Choose this option if you're using a host-to-host cable | |
279 | based on this design. Note that AnchorChips is now a | |
280 | Cypress brand. | |
281 | ||
282 | config USB_BELKIN | |
283 | boolean "eTEK based host-to-host cables (Advance, Belkin, ...)" | |
284 | depends on USB_NET_CDC_SUBSET | |
285 | default y | |
286 | help | |
287 | Choose this option if you're using a host-to-host cable | |
288 | based on this design: two NetChip 2890 chips and an Atmel | |
289 | microcontroller, with LEDs that indicate traffic. | |
290 | ||
291 | config USB_ARMLINUX | |
292 | boolean "Embedded ARM Linux links (iPaq, ...)" | |
293 | depends on USB_NET_CDC_SUBSET | |
294 | default y | |
295 | help | |
296 | Choose this option to support the "usb-eth" networking driver | |
297 | used by most of the ARM Linux community with device controllers | |
298 | such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities | |
299 | in some PXA versions of the "blob" boot loader. | |
300 | ||
301 | Linux-based "Gumstix" PXA-25x based systems use this protocol | |
302 | to talk with other Linux systems. | |
303 | ||
304 | Although the ROMs shipped with Sharp Zaurus products use a | |
305 | different link level framing protocol, you can have them use | |
306 | this simpler protocol by installing a different kernel. | |
307 | ||
308 | config USB_EPSON2888 | |
309 | boolean "Epson 2888 based firmware (DEVELOPMENT)" | |
310 | depends on USB_NET_CDC_SUBSET | |
311 | help | |
312 | Choose this option to support the usb networking links used | |
313 | by some sample firmware from Epson. | |
314 | ||
691895c6 DB |
315 | config USB_KC2190 |
316 | boolean "KT Technology KC2190 based cables (InstaNet)" | |
317 | depends on USB_NET_CDC_SUBSET && EXPERIMENTAL | |
318 | help | |
c0811987 SR |
319 | Choose this option if you're using a host-to-host cable |
320 | with one of these chips. | |
691895c6 | 321 | |
0aa599c5 DB |
322 | config USB_NET_ZAURUS |
323 | tristate "Sharp Zaurus (stock ROMs) and compatible" | |
324 | depends on USB_USBNET | |
4324fd49 | 325 | select USB_NET_CDCETHER |
0aa599c5 DB |
326 | select CRC32 |
327 | default y | |
328 | help | |
329 | Choose this option to support the usb networking links used by | |
330 | Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. | |
331 | This also supports some related device firmware, as used in some | |
332 | PDAs from Olympus and some cell phones from Motorola. | |
333 | ||
46a0cf81 | 334 | If you install an alternate image, such as the Linux 2.6 based |
0aa599c5 DB |
335 | versions of OpenZaurus, you should no longer need to support this |
336 | protocol. Only the "eth-fd" or "net_fd" drivers in these devices | |
337 | really need this non-conformant variant of CDC Ethernet (or in | |
338 | some cases CDC MDLM) protocol, not "g_ether". | |
339 | ||
38bde1d4 | 340 | |
1da177e4 | 341 | endmenu |