1# 2# USB Miscellaneous driver configuration 3# 4comment "USB Miscellaneous drivers" 5 depends on USB 6 7config USB_EMI62 8 tristate "EMI 6|2m USB Audio interface support" 9 depends on USB 10 ---help--- 11 This driver loads firmware to Emagic EMI 6|2m low latency USB 12 Audio and Midi interface. 13 14 After firmware load the device is handled with standard linux 15 USB Audio driver. 16 17 This code is also available as a module ( = code which can be 18 inserted in and removed from the running kernel whenever you want). 19 The module will be called audio. If you want to compile it as a 20 module, say M here and read <file:Documentation/kbuild/modules.txt>. 21 22config USB_EMI26 23 tristate "EMI 2|6 USB Audio interface support" 24 depends on USB 25 ---help--- 26 This driver loads firmware to Emagic EMI 2|6 low latency USB 27 Audio interface. 28 29 After firmware load the device is handled with standard linux 30 USB Audio driver. 31 32 To compile this driver as a module, choose M here: the 33 module will be called emi26. 34 35config USB_ADUTUX 36 tristate "ADU devices from Ontrak Control Systems" 37 depends on USB 38 help 39 Say Y if you want to use an ADU device from Ontrak Control 40 Systems. 41 42 To compile this driver as a module, choose M here. The module 43 will be called adutux. 44 45config USB_SEVSEG 46 tristate "USB 7-Segment LED Display" 47 depends on USB 48 help 49 Say Y here if you have a USB 7-Segment Display by Delcom 50 51 To compile this driver as a module, choose M here: the 52 module will be called usbsevseg. 53 54config USB_RIO500 55 tristate "USB Diamond Rio500 support" 56 depends on USB 57 help 58 Say Y here if you want to connect a USB Rio500 mp3 player to your 59 computer's USB port. Please read <file:Documentation/usb/rio.txt> 60 for more information. 61 62 To compile this driver as a module, choose M here: the 63 module will be called rio500. 64 65config USB_LEGOTOWER 66 tristate "USB Lego Infrared Tower support" 67 depends on USB 68 help 69 Say Y here if you want to connect a USB Lego Infrared Tower to your 70 computer's USB port. 71 72 This code is also available as a module ( = code which can be 73 inserted in and removed from the running kernel whenever you want). 74 The module will be called legousbtower. If you want to compile it as 75 a module, say M here and read 76 <file:Documentation/kbuild/modules.txt>. 77 78config USB_LCD 79 tristate "USB LCD driver support" 80 depends on USB 81 help 82 Say Y here if you want to connect an USBLCD to your computer's 83 USB port. The USBLCD is a small USB interface board for 84 alphanumeric LCD modules. See <http://www.usblcd.de/> for more 85 information. 86 87 To compile this driver as a module, choose M here: the 88 module will be called usblcd. 89 90config USB_BERRY_CHARGE 91 tristate "USB BlackBerry recharge support" 92 depends on USB 93 help 94 Say Y here if you want to connect a BlackBerry device to your 95 computer's USB port and have it automatically switch to "recharge" 96 mode. 97 98 To compile this driver as a module, choose M here: the 99 module will be called berry_charge. 100 101config USB_LED 102 tristate "USB LED driver support" 103 depends on USB 104 help 105 Say Y here if you want to connect an USBLED device to your 106 computer's USB port. 107 108 To compile this driver as a module, choose M here: the 109 module will be called usbled. 110 111config USB_CYPRESS_CY7C63 112 tristate "Cypress CY7C63xxx USB driver support" 113 depends on USB 114 help 115 Say Y here if you want to connect a Cypress CY7C63xxx 116 micro controller to your computer's USB port. Currently this 117 driver supports the pre-programmed devices (incl. firmware) 118 by AK Modul-Bus Computer GmbH. 119 120 Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html 121 122 To compile this driver as a module, choose M here: the 123 module will be called cypress_cy7c63. 124 125config USB_CYTHERM 126 tristate "Cypress USB thermometer driver support" 127 depends on USB 128 help 129 Say Y here if you want to connect a Cypress USB thermometer 130 device to your computer's USB port. This device is also known 131 as the Cypress USB Starter kit or demo board. The Elektor 132 magazine published a modified version of this device in issue 133 #291. 134 135 To compile this driver as a module, choose M here: the 136 module will be called cytherm. 137 138config USB_PHIDGET 139 tristate "USB Phidgets drivers" 140 depends on USB 141 help 142 Say Y here to enable the various drivers for devices from 143 Phidgets inc. 144 145config USB_PHIDGETKIT 146 tristate "USB PhidgetInterfaceKit support" 147 depends on USB_PHIDGET 148 help 149 Say Y here if you want to connect a PhidgetInterfaceKit USB device 150 from Phidgets Inc. 151 152 To compile this driver as a module, choose M here: the 153 module will be called phidgetkit. 154 155config USB_PHIDGETMOTORCONTROL 156 tristate "USB PhidgetMotorControl support" 157 depends on USB_PHIDGET 158 help 159 Say Y here if you want to connect a PhidgetMotorControl USB device 160 from Phidgets Inc. 161 162 To compile this driver as a module, choose M here: the 163 module will be called phidgetmotorcontrol. 164 165config USB_PHIDGETSERVO 166 tristate "USB PhidgetServo support" 167 depends on USB_PHIDGET 168 help 169 Say Y here if you want to connect an 1 or 4 Motor PhidgetServo 170 servo controller version 2.0 or 3.0. 171 172 Phidgets Inc. has a web page at <http://www.phidgets.com/>. 173 174 To compile this driver as a module, choose M here: the 175 module will be called phidgetservo. 176 177config USB_IDMOUSE 178 tristate "Siemens ID USB Mouse Fingerprint sensor support" 179 depends on USB 180 help 181 Say Y here if you want to use the fingerprint sensor on 182 the Siemens ID Mouse. There is also a Siemens ID Mouse 183 _Professional_, which has not been tested with this driver, 184 but uses the same sensor and may therefore work. 185 186 This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX", 187 which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm". 188 189 See also <http://www.fs.tum.de/~echtler/idmouse/>. 190 191config USB_FTDI_ELAN 192 tristate "Elan PCMCIA CardBus Adapter USB Client" 193 depends on USB 194 default M 195 help 196 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters. 197 Currently only the U132 adapter is available. 198 199 The U132 is specifically designed for CardBus PC cards that contain 200 an OHCI host controller. Typical PC cards are the Orange Mobile 3G 201 Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work 202 with PC cards that do not contain an OHCI controller. To use a U132 203 adapter you will need this "ftdi-elan" module as well as the "u132-hcd" 204 module which is a USB host controller driver that talks to the OHCI 205 controller within CardBus card that are inserted in the U132 adapter. 206 207 This driver has been tested with a CardBus OHCI USB adapter, and 208 worked with a USB PEN Drive inserted into the first USB port of 209 the PCCARD. A rather pointless thing to do, but useful for testing. 210 211 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller" 212 213 It is safe to say M here. 214 215config USB_APPLEDISPLAY 216 tristate "Apple Cinema Display support" 217 depends on USB 218 select BACKLIGHT_LCD_SUPPORT 219 select BACKLIGHT_CLASS_DEVICE 220 help 221 Say Y here if you want to control the backlight of Apple Cinema 222 Displays over USB. This driver provides a sysfs interface. 223 224source "drivers/usb/misc/sisusbvga/Kconfig" 225 226config USB_LD 227 tristate "USB LD driver" 228 depends on USB 229 help 230 This driver is for generic USB devices that use interrupt transfers, 231 like LD Didactic's USB devices. 232 233 To compile this driver as a module, choose M here: the 234 module will be called ldusb. 235 236config USB_TRANCEVIBRATOR 237 tristate "PlayStation 2 Trance Vibrator driver support" 238 depends on USB 239 help 240 Say Y here if you want to connect a PlayStation 2 Trance Vibrator 241 device to your computer's USB port. 242 243 To compile this driver as a module, choose M here: the 244 module will be called trancevibrator. 245 246config USB_IOWARRIOR 247 tristate "IO Warrior driver support" 248 depends on USB 249 help 250 Say Y here if you want to support the IO Warrior devices from Code 251 Mercenaries. This includes support for the following devices: 252 IO Warrior 40 253 IO Warrior 24 254 IO Warrior 56 255 IO Warrior 24 Power Vampire 256 257 To compile this driver as a module, choose M here: the 258 module will be called iowarrior. 259 260config USB_TEST 261 tristate "USB testing driver" 262 depends on USB && USB_DEVICEFS 263 help 264 This driver is for testing host controller software. It is used 265 with specialized device firmware for regression and stress testing, 266 to help prevent problems from cropping up with "real" drivers. 267 268 See <http://www.linux-usb.org/usbtest/> for more information, 269 including sample test device firmware and "how to use it". 270 271config USB_ISIGHTFW 272 tristate "iSight firmware loading support" 273 depends on USB 274 select FW_LOADER 275 help 276 This driver loads firmware for USB Apple iSight cameras, allowing 277 them to be driven by the USB video class driver available at 278 http://linux-uvc.berlios.de 279 280 The firmware for this driver must be extracted from the MacOS 281 driver beforehand. Tools for doing so are available at 282 http://bersace03.free.fr 283 284config USB_VST 285 tristate "USB VST driver" 286 depends on USB 287 help 288 This driver is intended for Vernier Software Technologies 289 bulk usb devices such as their Ocean-Optics spectrometers or 290 Labquest. 291 It is a bulk channel driver with configurable read and write 292 timeouts. 293 294 To compile this driver as a module, choose M here: the 295 module will be called vstusb. 296 297 298