drivers/usb/net/Kconfig

   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_MII
  96         tristate
  97         default n
  98
  99 config USB_USBNET
 100         tristate "Multi-purpose USB Networking Framework"
 101         select MII if USBNET_MII != n
 102         ---help---
 103           This driver supports several kinds of network links over USB,
 104           with "minidrivers" built around a common network driver core
 105           that supports deep queues for efficient transfers.  (This gives
 106           better performance with small packets and at high speeds).
 107
 108           The USB host runs "usbnet", and the other end of the link might be:
 109
 110           - Another USB host, when using USB "network" or "data transfer"
 111             cables.  These are often used to network laptops to PCs, like
 112             "Laplink" parallel cables or some motherboards.  These rely
 113             on specialized chips from many suppliers.
 114
 115           - An intelligent USB gadget, perhaps embedding a Linux system.
 116             These include PDAs running Linux (iPaq, Yopy, Zaurus, and
 117             others), and devices that interoperate using the standard
 118             CDC-Ethernet specification (including many cable modems).
 119
 120           - Network adapter hardware (like those for 10/100 Ethernet) which
 121             uses this driver framework.
 122
 123           The link will appear with a name like "usb0", when the link is
 124           a two-node link, or "eth0" for most CDC-Ethernet devices.  Those
 125           two-node links are most easily managed with Ethernet Bridging
 126           (CONFIG_BRIDGE) instead of routing.
 127
 128           For more information see <http://www.linux-usb.org/usbnet/>.
 129
 130           To compile this driver as a module, choose M here: the
 131           module will be called usbnet.
 132
 133 config USB_NET_AX8817X
 134         tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
 135         depends on USB_USBNET && NET_ETHERNET
 136         select CRC32
 137         select USB_USBNET_MII
 138         default y
 139         help
 140           This option adds support for ASIX AX88xxx based USB 2.0
 141           10/100 Ethernet adapters.
 142
 143           This driver should work with at least the following devices:
 144             * Aten UC210T
 145             * ASIX AX88172
 146             * Billionton Systems, USB2AR
 147             * Buffalo LUA-U2-KTX
 148             * Corega FEther USB2-TX
 149             * D-Link DUB-E100
 150             * Hawking UF200
 151             * Linksys USB200M
 152             * Netgear FA120
 153             * Sitecom LN-029
 154             * Intellinet USB 2.0 Ethernet
 155             * ST Lab USB 2.0 Ethernet
 156             * TrendNet TU2-ET100
 157
 158           This driver creates an interface named "ethX", where X depends on
 159           what other networking devices you have in use.
 160
 161
 162 config USB_NET_CDCETHER
 163         tristate "CDC Ethernet support (smart devices such as cable modems)"
 164         depends on USB_USBNET
 165         default y
 166         help
 167           This option supports devices conforming to the Communication Device
 168           Class (CDC) Ethernet Control Model, a specification that's easy to
 169           implement in device firmware.  The CDC specifications are available
 170           from <http://www.usb.org/>.
 171
 172           CDC Ethernet is an implementation option for DOCSIS cable modems
 173           that support USB connectivity, used for non-Microsoft USB hosts.
 174           The Linux-USB CDC Ethernet Gadget driver is an open implementation.
 175           This driver should work with at least the following devices:
 176
 177             * Ericsson PipeRider (all variants)
 178             * Motorola (DM100 and SB4100)
 179             * Broadcom Cable Modem (reference design)
 180             * Toshiba PCX1100U
 181             * ...
 182
 183           This driver creates an interface named "ethX", where X depends on
 184           what other networking devices you have in use.  However, if the
 185           IEEE 802 "local assignment" bit is set in the address, a "usbX"
 186           name is used instead.
 187
 188 config USB_NET_GL620A
 189         tristate "GeneSys GL620USB-A based cables"
 190         depends on USB_USBNET
 191         help
 192           Choose this option if you're using a host-to-host cable,
 193           or PC2PC motherboard, with this chip.
 194
 195           Note that the half-duplex "GL620USB" is not supported.
 196
 197 config USB_NET_NET1080
 198         tristate "NetChip 1080 based cables (Laplink, ...)"
 199         default y
 200         depends on USB_USBNET
 201         help
 202           Choose this option if you're using a host-to-host cable based
 203           on this design:  one NetChip 1080 chip and supporting logic,
 204           optionally with LEDs that indicate traffic
 205
 206 config USB_NET_PLUSB
 207         tristate "Prolific PL-2301/2302 based cables"
 208         # if the handshake/init/reset problems, from original 'plusb',
 209         # are ever resolved ... then remove "experimental"
 210         depends on USB_USBNET && EXPERIMENTAL
 211         help
 212           Choose this option if you're using a host-to-host cable
 213           with one of these chips.
 214
 215 config USB_NET_MCS7830
 216         tristate "MosChip MCS7830 based Ethernet adapters"
 217         depends on USB_USBNET
 218         select USB_USBNET_MII
 219         help
 220           Choose this option if you're using a 10/100 Ethernet USB2
 221           adapter based on the MosChip 7830 controller. This includes
 222           adapters marketed under the DeLOCK brand.
 223
 224 config USB_NET_RNDIS_HOST
 225         tristate "Host for RNDIS devices (EXPERIMENTAL)"
 226         depends on USB_USBNET && EXPERIMENTAL
 227         select USB_NET_CDCETHER
 228         help
 229           This option enables hosting "Remote NDIS" USB networking links,
 230           as encouraged by Microsoft (instead of CDC Ethernet!) for use in
 231           various devices that may only support this protocol.
 232
 233           Avoid using this protocol unless you have no better options.
 234           The protocol specification is incomplete, and is controlled by
 235           (and for) Microsoft; it isn't an "Open" ecosystem or market.
 236
 237 config USB_NET_CDC_SUBSET
 238         tristate "Simple USB Network Links (CDC Ethernet subset)"
 239         depends on USB_USBNET
 240         help
 241           This driver module supports USB network devices that can work
 242           without any device-specific information.  Select it if you have
 243           one of these drivers.
 244
 245           Note that while many USB host-to-host cables can work in this mode,
 246           that may mean not being able to talk to Win32 systems or more
 247           commonly not being able to handle certain events (like replugging
 248           the host on the other end) very well.  Also, these devices will
 249           not generally have permanently assigned Ethernet addresses.
 250
 251 config USB_ALI_M5632
 252         boolean "ALi M5632 based 'USB 2.0 Data Link' cables"
 253         depends on USB_NET_CDC_SUBSET
 254         help
 255           Choose this option if you're using a host-to-host cable
 256           based on this design, which supports USB 2.0 high speed.
 257
 258 config USB_AN2720
 259         boolean "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
 260         depends on USB_NET_CDC_SUBSET
 261         help
 262           Choose this option if you're using a host-to-host cable
 263           based on this design.  Note that AnchorChips is now a
 264           Cypress brand.
 265
 266 config USB_BELKIN
 267         boolean "eTEK based host-to-host cables (Advance, Belkin, ...)"
 268         depends on USB_NET_CDC_SUBSET
 269         default y
 270         help
 271           Choose this option if you're using a host-to-host cable
 272           based on this design:  two NetChip 2890 chips and an Atmel
 273           microcontroller, with LEDs that indicate traffic.
 274
 275 config USB_ARMLINUX
 276         boolean "Embedded ARM Linux links (iPaq, ...)"
 277         depends on USB_NET_CDC_SUBSET
 278         default y
 279         help
 280           Choose this option to support the "usb-eth" networking driver
 281           used by most of the ARM Linux community with device controllers
 282           such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
 283           in some PXA versions of the "blob" boot loader.
 284
 285           Linux-based "Gumstix" PXA-25x based systems use this protocol
 286           to talk with other Linux systems.
 287
 288           Although the ROMs shipped with Sharp Zaurus products use a
 289           different link level framing protocol, you can have them use
 290           this simpler protocol by installing a different kernel.
 291
 292 config USB_EPSON2888
 293         boolean "Epson 2888 based firmware (DEVELOPMENT)"
 294         depends on USB_NET_CDC_SUBSET
 295         help
 296           Choose this option to support the usb networking links used
 297           by some sample firmware from Epson.
 298
 299 config USB_NET_ZAURUS
 300         tristate "Sharp Zaurus (stock ROMs) and compatible"
 301         depends on USB_USBNET
 302         select USB_NET_CDCETHER
 303         select CRC32
 304         default y
 305         help
 306           Choose this option to support the usb networking links used by
 307           Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
 308           This also supports some related device firmware, as used in some
 309           PDAs from Olympus and some cell phones from Motorola.
 310
 311           If you install an alternate image, such as the Linux 2.6 based
 312           versions of OpenZaurus, you should no longer need to support this
 313           protocol.  Only the "eth-fd" or "net_fd" drivers in these devices
 314           really need this non-conformant variant of CDC Ethernet (or in
 315           some cases CDC MDLM) protocol, not "g_ether".
 316
 317
 318 endmenu