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/net/usb/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 select MII 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 96config USB_USBNET 97 tristate "Multi-purpose USB Networking Framework" 98 select MII 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). 104 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 130config USB_NET_AX8817X 131 tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters" 132 depends on USB_USBNET 133 select CRC32 134 default y 135 help 136 This option adds support for ASIX AX88xxx based USB 2.0 137 10/100 Ethernet adapters. 138 139 This driver should work with at least the following devices: 140 * Aten UC210T 141 * ASIX AX88172 142 * Billionton Systems, USB2AR 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 155 what other networking devices you have in use. 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_CDC_EEM 184 tristate "CDC EEM support" 185 depends on USB_USBNET && EXPERIMENTAL 186 help 187 This option supports devices conforming to the Communication Device 188 Class (CDC) Ethernet Emulation Model, a specification that's easy to 189 implement in device firmware. The CDC EEM specifications are available 190 from <http://www.usb.org/>. 191 192 This driver creates an interface named "ethX", where X depends on 193 what other networking devices you have in use. However, if the 194 IEEE 802 "local assignment" bit is set in the address, a "usbX" 195 name is used instead. 196 197config USB_NET_DM9601 198 tristate "Davicom DM9601 based USB 1.1 10/100 ethernet devices" 199 depends on USB_USBNET 200 select CRC32 201 help 202 This option adds support for Davicom DM9601 based USB 1.1 203 10/100 Ethernet adapters. 204 205config USB_NET_SMSC95XX 206 tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices" 207 depends on USB_USBNET 208 select CRC32 209 help 210 This option adds support for SMSC LAN95XX based USB 2.0 211 10/100 Ethernet adapters. 212 213config USB_NET_GL620A 214 tristate "GeneSys GL620USB-A based cables" 215 depends on USB_USBNET 216 help 217 Choose this option if you're using a host-to-host cable, 218 or PC2PC motherboard, with this chip. 219 220 Note that the half-duplex "GL620USB" is not supported. 221 222config USB_NET_NET1080 223 tristate "NetChip 1080 based cables (Laplink, ...)" 224 default y 225 depends on USB_USBNET 226 help 227 Choose this option if you're using a host-to-host cable based 228 on this design: one NetChip 1080 chip and supporting logic, 229 optionally with LEDs that indicate traffic 230 231config USB_NET_PLUSB 232 tristate "Prolific PL-2301/2302 based cables" 233 # if the handshake/init/reset problems, from original 'plusb', 234 # are ever resolved ... then remove "experimental" 235 depends on USB_USBNET && EXPERIMENTAL 236 help 237 Choose this option if you're using a host-to-host cable 238 with one of these chips. 239 240config USB_NET_MCS7830 241 tristate "MosChip MCS7830 based Ethernet adapters" 242 depends on USB_USBNET 243 help 244 Choose this option if you're using a 10/100 Ethernet USB2 245 adapter based on the MosChip 7830 controller. This includes 246 adapters marketed under the DeLOCK brand. 247 248config USB_NET_RNDIS_HOST 249 tristate "Host for RNDIS and ActiveSync devices (EXPERIMENTAL)" 250 depends on USB_USBNET && EXPERIMENTAL 251 select USB_NET_CDCETHER 252 help 253 This option enables hosting "Remote NDIS" USB networking links, 254 as encouraged by Microsoft (instead of CDC Ethernet!) for use in 255 various devices that may only support this protocol. A variant 256 of this protocol (with even less public documentation) seems to 257 be at the root of Microsoft's "ActiveSync" too. 258 259 Avoid using this protocol unless you have no better options. 260 The protocol specification is incomplete, and is controlled by 261 (and for) Microsoft; it isn't an "Open" ecosystem or market. 262 263config USB_NET_CDC_SUBSET 264 tristate "Simple USB Network Links (CDC Ethernet subset)" 265 depends on USB_USBNET 266 default y 267 help 268 This driver module supports USB network devices that can work 269 without any device-specific information. Select it if you have 270 one of these drivers. 271 272 Note that while many USB host-to-host cables can work in this mode, 273 that may mean not being able to talk to Win32 systems or more 274 commonly not being able to handle certain events (like replugging 275 the host on the other end) very well. Also, these devices will 276 not generally have permanently assigned Ethernet addresses. 277 278config USB_ALI_M5632 279 boolean "ALi M5632 based 'USB 2.0 Data Link' cables" 280 depends on USB_NET_CDC_SUBSET 281 help 282 Choose this option if you're using a host-to-host cable 283 based on this design, which supports USB 2.0 high speed. 284 285config USB_AN2720 286 boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)" 287 depends on USB_NET_CDC_SUBSET 288 help 289 Choose this option if you're using a host-to-host cable 290 based on this design. Note that AnchorChips is now a 291 Cypress brand. 292 293config USB_BELKIN 294 boolean "eTEK based host-to-host cables (Advance, Belkin, ...)" 295 depends on USB_NET_CDC_SUBSET 296 default y 297 help 298 Choose this option if you're using a host-to-host cable 299 based on this design: two NetChip 2890 chips and an Atmel 300 microcontroller, with LEDs that indicate traffic. 301 302config USB_ARMLINUX 303 boolean "Embedded ARM Linux links (iPaq, ...)" 304 depends on USB_NET_CDC_SUBSET 305 default y 306 help 307 Choose this option to support the "usb-eth" networking driver 308 used by most of the ARM Linux community with device controllers 309 such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities 310 in some PXA versions of the "blob" boot loader. 311 312 Linux-based "Gumstix" PXA-25x based systems use this protocol 313 to talk with other Linux systems. 314 315 Although the ROMs shipped with Sharp Zaurus products use a 316 different link level framing protocol, you can have them use 317 this simpler protocol by installing a different kernel. 318 319config USB_EPSON2888 320 boolean "Epson 2888 based firmware (DEVELOPMENT)" 321 depends on USB_NET_CDC_SUBSET 322 help 323 Choose this option to support the usb networking links used 324 by some sample firmware from Epson. 325 326config USB_KC2190 327 boolean "KT Technology KC2190 based cables (InstaNet)" 328 depends on USB_NET_CDC_SUBSET && EXPERIMENTAL 329 help 330 Choose this option if you're using a host-to-host cable 331 with one of these chips. 332 333config USB_NET_ZAURUS 334 tristate "Sharp Zaurus (stock ROMs) and compatible" 335 depends on USB_USBNET 336 select USB_NET_CDCETHER 337 select CRC32 338 default y 339 help 340 Choose this option to support the usb networking links used by 341 Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500. 342 This also supports some related device firmware, as used in some 343 PDAs from Olympus and some cell phones from Motorola. 344 345 If you install an alternate image, such as the Linux 2.6 based 346 versions of OpenZaurus, you should no longer need to support this 347 protocol. Only the "eth-fd" or "net_fd" drivers in these devices 348 really need this non-conformant variant of CDC Ethernet (or in 349 some cases CDC MDLM) protocol, not "g_ether". 350 351config USB_HSO 352 tristate "Option USB High Speed Mobile Devices" 353 depends on USB && RFKILL 354 default n 355 help 356 Choose this option if you have an Option HSDPA/HSUPA card. 357 These cards support downlink speeds of 7.2Mbps or greater. 358 359 To compile this driver as a module, choose M here: the 360 module will be called hso. 361 362endmenu 363