tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1#
2# USB Network devices configuration
3#
4comment "Networking support is needed for USB Network Adapter support"
5 depends on USB && !NET
6
7menu "USB Network Adapters"
8 depends on USB && NET
9
10config 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
30config 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
69config 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
84config 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
95config 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
128config USB_NET_AX8817X
129 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
130 depends on USB_USBNET && NET_ETHERNET
131 select CRC32
132 select MII
133 default y
134 help
135 This option adds support for ASIX AX88xxx based USB 2.0
136 10/100 Ethernet adapters.
137
138 This driver should work with at least the following devices:
139 * Aten UC210T
140 * ASIX AX88172
141 * Billionton Systems, USB2AR
142 * Buffalo LUA-U2-KTX
143 * Corega FEther USB2-TX
144 * D-Link DUB-E100
145 * Hawking UF200
146 * Linksys USB200M
147 * Netgear FA120
148 * Sitecom LN-029
149 * Intellinet USB 2.0 Ethernet
150 * ST Lab USB 2.0 Ethernet
151 * TrendNet TU2-ET100
152
153 This driver creates an interface named "ethX", where X depends on
154 what other networking devices you have in use.
155
156
157config USB_NET_CDCETHER
158 tristate "CDC Ethernet support (smart devices such as cable modems)"
159 depends on USB_USBNET
160 default y
161 help
162 This option supports devices conforming to the Communication Device
163 Class (CDC) Ethernet Control Model, a specification that's easy to
164 implement in device firmware. The CDC specifications are available
165 from <http://www.usb.org/>.
166
167 CDC Ethernet is an implementation option for DOCSIS cable modems
168 that support USB connectivity, used for non-Microsoft USB hosts.
169 The Linux-USB CDC Ethernet Gadget driver is an open implementation.
170 This driver should work with at least the following devices:
171
172 * Ericsson PipeRider (all variants)
173 * Motorola (DM100 and SB4100)
174 * Broadcom Cable Modem (reference design)
175 * Toshiba PCX1100U
176 * ...
177
178 This driver creates an interface named "ethX", where X depends on
179 what other networking devices you have in use. However, if the
180 IEEE 802 "local assignment" bit is set in the address, a "usbX"
181 name is used instead.
182
183config USB_NET_GL620A
184 tristate "GeneSys GL620USB-A based cables"
185 depends on USB_USBNET
186 help
187 Choose this option if you're using a host-to-host cable,
188 or PC2PC motherboard, with this chip.
189
190 Note that the half-duplex "GL620USB" is not supported.
191
192config USB_NET_NET1080
193 tristate "NetChip 1080 based cables (Laplink, ...)"
194 default y
195 depends on USB_USBNET
196 help
197 Choose this option if you're using a host-to-host cable based
198 on this design: one NetChip 1080 chip and supporting logic,
199 optionally with LEDs that indicate traffic
200
201config USB_NET_PLUSB
202 tristate "Prolific PL-2301/2302 based cables"
203 # if the handshake/init/reset problems, from original 'plusb',
204 # are ever resolved ... then remove "experimental"
205 depends on USB_USBNET && EXPERIMENTAL
206 help
207 Choose this option if you're using a host-to-host cable
208 with one of these chips.
209
210config USB_NET_RNDIS_HOST
211 tristate "Host for RNDIS devices (EXPERIMENTAL)"
212 depends on USB_USBNET && EXPERIMENTAL
213 select USB_NET_CDCETHER
214 help
215 This option enables hosting "Remote NDIS" USB networking links,
216 as encouraged by Microsoft (instead of CDC Ethernet!) for use in
217 various devices that may only support this protocol.
218
219 Avoid using this protocol unless you have no better options.
220 The protocol specification is incomplete, and is controlled by
221 (and for) Microsoft; it isn't an "Open" ecosystem or market.
222
223config USB_NET_CDC_SUBSET
224 tristate "Simple USB Network Links (CDC Ethernet subset)"
225 depends on USB_USBNET
226 help
227 This driver module supports USB network devices that can work
228 without any device-specific information. Select it if you have
229 one of these drivers.
230
231 Note that while many USB host-to-host cables can work in this mode,
232 that may mean not being able to talk to Win32 systems or more
233 commonly not being able to handle certain events (like replugging
234 the host on the other end) very well. Also, these devices will
235 not generally have permanently assigned Ethernet addresses.
236
237config USB_ALI_M5632
238 boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
239 depends on USB_NET_CDC_SUBSET
240 help
241 Choose this option if you're using a host-to-host cable
242 based on this design, which supports USB 2.0 high speed.
243
244config USB_AN2720
245 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
246 depends on USB_NET_CDC_SUBSET
247 help
248 Choose this option if you're using a host-to-host cable
249 based on this design. Note that AnchorChips is now a
250 Cypress brand.
251
252config USB_BELKIN
253 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
254 depends on USB_NET_CDC_SUBSET
255 default y
256 help
257 Choose this option if you're using a host-to-host cable
258 based on this design: two NetChip 2890 chips and an Atmel
259 microcontroller, with LEDs that indicate traffic.
260
261config USB_ARMLINUX
262 boolean "Embedded ARM Linux links (iPaq, ...)"
263 depends on USB_NET_CDC_SUBSET
264 default y
265 help
266 Choose this option to support the "usb-eth" networking driver
267 used by most of the ARM Linux community with device controllers
268 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
269 in some PXA versions of the "blob" boot loader.
270
271 Linux-based "Gumstix" PXA-25x based systems use this protocol
272 to talk with other Linux systems.
273
274 Although the ROMs shipped with Sharp Zaurus products use a
275 different link level framing protocol, you can have them use
276 this simpler protocol by installing a different kernel.
277
278config USB_EPSON2888
279 boolean "Epson 2888 based firmware (DEVELOPMENT)"
280 depends on USB_NET_CDC_SUBSET
281 help
282 Choose this option to support the usb networking links used
283 by some sample firmware from Epson.
284
285config USB_NET_ZAURUS
286 tristate "Sharp Zaurus (stock ROMs) and compatible"
287 depends on USB_USBNET
288 select USB_NET_CDCETHER
289 select CRC32
290 default y
291 help
292 Choose this option to support the usb networking links used by
293 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
294 This also supports some related device firmware, as used in some
295 PDAs from Olympus and some cell phones from Motorola.
296
297 If you install an alternate image, such as the Linux 2.6 based
298 versions of OpenZaurus, you should no longer need to support this
299 protocol. Only the "eth-fd" or "net_fd" drivers in these devices
300 really need this non-conformant variant of CDC Ethernet (or in
301 some cases CDC MDLM) protocol, not "g_ether".
302
303
304config USB_ZD1201
305 tristate "USB ZD1201 based Wireless device support"
306 depends on NET_RADIO
307 select FW_LOADER
308 ---help---
309 Say Y if you want to use wireless LAN adapters based on the ZyDAS
310 ZD1201 chip.
311
312 This driver makes the adapter appear as a normal Ethernet interface,
313 typically on wlan0.
314
315 The zd1201 device requires external firmware to be loaded.
316 This can be found at http://linux-lc100020.sourceforge.net/
317
318 To compile this driver as a module, choose M here: the
319 module will be called zd1201.
320
321endmenu