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