diff options
author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
commit | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch) | |
tree | 0bba044c4ce775e45a88a51686b5d9f90697ea9d /drivers/usb/net/Kconfig |
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!
Diffstat (limited to 'drivers/usb/net/Kconfig')
-rw-r--r-- | drivers/usb/net/Kconfig | 307 |
1 files changed, 307 insertions, 0 deletions
diff --git a/drivers/usb/net/Kconfig b/drivers/usb/net/Kconfig new file mode 100644 index 000000000000..db64c908d4a7 --- /dev/null +++ b/drivers/usb/net/Kconfig | |||
@@ -0,0 +1,307 @@ | |||
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. | ||
74 | If in doubt then look at <file:drivers/usb/net/pegasus.h> for the | ||
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 | ||
87 | help | ||
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/>. | ||
91 | |||
92 | To compile this driver as a module, choose M here: the | ||
93 | module will be called rtl8150. | ||
94 | |||
95 | config USB_USBNET | ||
96 | tristate "Multi-purpose USB Networking Framework" | ||
97 | ---help--- | ||
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). | ||
102 | |||
103 | The USB host runs "usbnet", and the other end of the link might be: | ||
104 | |||
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. | ||
109 | |||
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). | ||
114 | |||
115 | - Network adapter hardware (like those for 10/100 Ethernet) which | ||
116 | uses this driver framework. | ||
117 | |||
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. | ||
122 | |||
123 | For more information see <http://www.linux-usb.org/usbnet/>. | ||
124 | |||
125 | To compile this driver as a module, choose M here: the | ||
126 | module will be called usbnet. | ||
127 | |||
128 | comment "USB Host-to-Host Cables" | ||
129 | depends on USB_USBNET | ||
130 | |||
131 | config USB_ALI_M5632 | ||
132 | boolean "ALi M5632 based 'USB 2.0 Data Link' cables" | ||
133 | depends on USB_USBNET | ||
134 | default y | ||
135 | help | ||
136 | Choose this option if you're using a host-to-host cable | ||
137 | based on this design, which supports USB 2.0 high speed. | ||
138 | |||
139 | config USB_AN2720 | ||
140 | boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)" | ||
141 | depends on USB_USBNET | ||
142 | default y | ||
143 | help | ||
144 | Choose this option if you're using a host-to-host cable | ||
145 | based on this design. Note that AnchorChips is now a | ||
146 | Cypress brand. | ||
147 | |||
148 | config USB_BELKIN | ||
149 | boolean "eTEK based host-to-host cables (Advance, Belkin, ...)" | ||
150 | depends on USB_USBNET | ||
151 | default y | ||
152 | help | ||
153 | Choose this option if you're using a host-to-host cable | ||
154 | based on this design: two NetChip 2890 chips and an Atmel | ||
155 | microcontroller, with LEDs that indicate traffic. | ||
156 | |||
157 | config USB_GENESYS | ||
158 | boolean "GeneSys GL620USB-A based cables" | ||
159 | default y | ||
160 | depends on USB_USBNET | ||
161 | help | ||
162 | Choose this option if you're using a host-to-host cable, | ||
163 | or PC2PC motherboard, with this chip. | ||
164 | |||
165 | Note that the half-duplex "GL620USB" is not supported. | ||
166 | |||
167 | config USB_NET1080 | ||
168 | boolean "NetChip 1080 based cables (Laplink, ...)" | ||
169 | default y | ||
170 | depends on USB_USBNET | ||
171 | help | ||
172 | Choose this option if you're using a host-to-host cable based | ||
173 | on this design: one NetChip 1080 chips and supporting logic, | ||
174 | supporting LEDs that indicate traffic | ||
175 | |||
176 | config USB_PL2301 | ||
177 | boolean "Prolific PL-2301/2302 based cables" | ||
178 | default y | ||
179 | # handshake/init/reset problems, from original 'plusb' driver | ||
180 | depends on USB_USBNET && EXPERIMENTAL | ||
181 | help | ||
182 | Choose this option if you're using a host-to-host cable | ||
183 | with one of these chips. | ||
184 | |||
185 | config USB_KC2190 | ||
186 | boolean "KT Technology KC2190 based cables (InstaNet)" | ||
187 | default y | ||
188 | depends on USB_USBNET && EXPERIMENTAL | ||
189 | help | ||
190 | Choose this option if you're using a host-to-host cable | ||
191 | with one of these chips. | ||
192 | |||
193 | comment "Intelligent USB Devices/Gadgets" | ||
194 | depends on USB_USBNET | ||
195 | |||
196 | config USB_ARMLINUX | ||
197 | boolean "Embedded ARM Linux links (iPaq, ...)" | ||
198 | depends on USB_USBNET | ||
199 | default y | ||
200 | help | ||
201 | Choose this option to support the "usb-eth" networking driver | ||
202 | used by most of the ARM Linux community with device controllers | ||
203 | such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities | ||
204 | in some PXA versions of the "blob" boot loader. | ||
205 | |||
206 | Linux-based "Gumstix" PXA-25x based systems use this protocol | ||
207 | to talk with other Linux systems. | ||
208 | |||
209 | Although the ROMs shipped with Sharp Zaurus products use a | ||
210 | different link level framing protocol, you can have them use | ||
211 | this simpler protocol by installing a different kernel. | ||
212 | |||
213 | config USB_EPSON2888 | ||
214 | boolean "Epson 2888 based firmware (DEVELOPMENT)" | ||
215 | depends on USB_USBNET | ||
216 | default y | ||
217 | help | ||
218 | Choose this option to support the usb networking links used | ||
219 | by some sample firmware from Epson. | ||
220 | |||
221 | config USB_ZAURUS | ||
222 | boolean "Sharp Zaurus (stock ROMs)" | ||
223 | depends on USB_USBNET | ||
224 | select CRC32 | ||
225 | default y | ||
226 | help | ||
227 | Choose this option to support the usb networking links used by | ||
228 | Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. | ||
229 | |||
230 | If you install an alternate ROM image, you may no longer need | ||
231 | to support this protocol. Only the "eth-fd" driver really needs | ||
232 | this non-conformant variant of CDC Ethernet protocol. | ||
233 | |||
234 | config USB_CDCETHER | ||
235 | boolean "CDC Ethernet support (smart devices such as cable modems)" | ||
236 | depends on USB_USBNET | ||
237 | default y | ||
238 | help | ||
239 | This option supports devices conforming to the Communication Device | ||
240 | Class (CDC) Ethernet Control Model, a specification that's easy to | ||
241 | implement in device firmware. The CDC specifications are available | ||
242 | from <http://www.usb.org/>. | ||
243 | |||
244 | CDC Ethernet is an implementation option for DOCSIS cable modems | ||
245 | that support USB connectivity, used for non-Microsoft USB hosts. | ||
246 | This driver should work with at least the following devices: | ||
247 | |||
248 | * Ericsson PipeRider (all variants) | ||
249 | * Motorola (DM100 and SB4100) | ||
250 | * Broadcom Cable Modem (reference design) | ||
251 | * Toshiba PCX1100U | ||
252 | * ... | ||
253 | |||
254 | This driver creates an interface named "ethX", where X depends on | ||
255 | what other networking devices you have in use. However, if the | ||
256 | IEEE 802 "local assignment" bit is set in the address, a "usbX" | ||
257 | name is used instead. | ||
258 | |||
259 | comment "USB Network Adapters" | ||
260 | depends on USB_USBNET | ||
261 | |||
262 | config USB_AX8817X | ||
263 | boolean "ASIX AX88xxx Based USB 2.0 Ethernet Devices" | ||
264 | depends on USB_USBNET && NET_ETHERNET | ||
265 | select CRC32 | ||
266 | select MII | ||
267 | default y | ||
268 | help | ||
269 | This option adds support for ASIX AX88xxx based USB 2.0 | ||
270 | 10/100 Ethernet devices. | ||
271 | |||
272 | This driver should work with at least the following devices: | ||
273 | * Aten UC210T | ||
274 | * ASIX AX88172 | ||
275 | * Billionton Systems, USB2AR | ||
276 | * Buffalo LUA-U2-KTX | ||
277 | * Corega FEther USB2-TX | ||
278 | * D-Link DUB-E100 | ||
279 | * Hawking UF200 | ||
280 | * Linksys USB200M | ||
281 | * Netgear FA120 | ||
282 | * Sitecom LN-029 | ||
283 | * Intellinet USB 2.0 Ethernet | ||
284 | * ST Lab USB 2.0 Ethernet | ||
285 | * TrendNet TU2-ET100 | ||
286 | |||
287 | This driver creates an interface named "ethX", where X depends on | ||
288 | what other networking devices you have in use. | ||
289 | |||
290 | config USB_ZD1201 | ||
291 | tristate "USB ZD1201 based Wireless device support" | ||
292 | depends on NET_RADIO | ||
293 | select FW_LOADER | ||
294 | ---help--- | ||
295 | Say Y if you want to use wireless LAN adapters based on the ZyDAS | ||
296 | ZD1201 chip. | ||
297 | |||
298 | This driver makes the adapter appear as a normal Ethernet interface, | ||
299 | typically on wlan0. | ||
300 | |||
301 | The zd1201 device requires external firmware to be loaded. | ||
302 | This can be found at http://linux-lc100020.sourceforge.net/ | ||
303 | |||
304 | To compile this driver as a module, choose M here: the | ||
305 | module will be called zd1201. | ||
306 | |||
307 | endmenu | ||