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 (EXPERIMENTAL)" 37 depends on USB && EXPERIMENTAL 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 (EXPERIMENTAL)" 47 depends on USB && EXPERIMENTAL 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 (EXPERIMENTAL)" 57 depends on USB && EXPERIMENTAL 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 (EXPERIMENTAL)" 68 depends on USB && EXPERIMENTAL 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_LED 92 tristate "USB LED driver support" 93 depends on USB 94 help 95 Say Y here if you want to connect an USBLED device to your 96 computer's USB port. 97 98 To compile this driver as a module, choose M here: the 99 module will be called usbled. 100 101config USB_CYPRESS_CY7C63 102 tristate "Cypress CY7C63xxx USB driver support" 103 depends on USB 104 help 105 Say Y here if you want to connect a Cypress CY7C63xxx 106 micro controller to your computer's USB port. Currently this 107 driver supports the pre-programmed devices (incl. firmware) 108 by AK Modul-Bus Computer GmbH. 109 110 Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html 111 112 To compile this driver as a module, choose M here: the 113 module will be called cypress_cy7c63. 114 115config USB_CYTHERM 116 tristate "Cypress USB thermometer driver support" 117 depends on USB 118 help 119 Say Y here if you want to connect a Cypress USB thermometer 120 device to your computer's USB port. This device is also known 121 as the Cypress USB Starter kit or demo board. The Elektor 122 magazine published a modified version of this device in issue 123 #291. 124 125 To compile this driver as a module, choose M here: the 126 module will be called cytherm. 127 128config USB_PHIDGET 129 tristate "USB Phidgets drivers" 130 depends on USB 131 help 132 Say Y here to enable the various drivers for devices from 133 Phidgets inc. 134 135config USB_PHIDGETKIT 136 tristate "USB PhidgetInterfaceKit support" 137 depends on USB_PHIDGET 138 help 139 Say Y here if you want to connect a PhidgetInterfaceKit USB device 140 from Phidgets Inc. 141 142 To compile this driver as a module, choose M here: the 143 module will be called phidgetkit. 144 145config USB_PHIDGETMOTORCONTROL 146 tristate "USB PhidgetMotorControl support" 147 depends on USB_PHIDGET 148 help 149 Say Y here if you want to connect a PhidgetMotorControl USB device 150 from Phidgets Inc. 151 152 To compile this driver as a module, choose M here: the 153 module will be called phidgetmotorcontrol. 154 155config USB_PHIDGETSERVO 156 tristate "USB PhidgetServo support" 157 depends on USB_PHIDGET 158 help 159 Say Y here if you want to connect an 1 or 4 Motor PhidgetServo 160 servo controller version 2.0 or 3.0. 161 162 Phidgets Inc. has a web page at <http://www.phidgets.com/>. 163 164 To compile this driver as a module, choose M here: the 165 module will be called phidgetservo. 166 167config USB_IDMOUSE 168 tristate "Siemens ID USB Mouse Fingerprint sensor support" 169 depends on USB 170 help 171 Say Y here if you want to use the fingerprint sensor on 172 the Siemens ID Mouse. There is also a Siemens ID Mouse 173 _Professional_, which has not been tested with this driver, 174 but uses the same sensor and may therefore work. 175 176 This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX", 177 which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm". 178 179 See also <http://www.fs.tum.de/~echtler/idmouse/>. 180 181config USB_FTDI_ELAN 182 tristate "Elan PCMCIA CardBus Adapter USB Client" 183 depends on USB 184 default M 185 help 186 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters. 187 Currently only the U132 adapter is available. 188 189 The U132 is specifically designed for CardBus PC cards that contain 190 an OHCI host controller. Typical PC cards are the Orange Mobile 3G 191 Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work 192 with PC cards that do not contain an OHCI controller. To use a U132 193 adapter you will need this "ftdi-elan" module as well as the "u132-hcd" 194 module which is a USB host controller driver that talks to the OHCI 195 controller within CardBus card that are inserted in the U132 adapter. 196 197 This driver has been tested with a CardBus OHCI USB adapter, and 198 worked with a USB PEN Drive inserted into the first USB port of 199 the PCCARD. A rather pointless thing to do, but useful for testing. 200 201 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller" 202 203 It is safe to say M here. 204 205config USB_APPLEDISPLAY 206 tristate "Apple Cinema Display support" 207 depends on USB 208 select BACKLIGHT_LCD_SUPPORT 209 select BACKLIGHT_CLASS_DEVICE 210 help 211 Say Y here if you want to control the backlight of Apple Cinema 212 Displays over USB. This driver provides a sysfs interface. 213 214source "drivers/usb/misc/sisusbvga/Kconfig" 215 216config USB_LD 217 tristate "USB LD driver" 218 depends on USB 219 help 220 This driver is for generic USB devices that use interrupt transfers, 221 like LD Didactic's USB devices. 222 223 To compile this driver as a module, choose M here: the 224 module will be called ldusb. 225 226config USB_TEST 227 tristate "USB testing driver (DEVELOPMENT)" 228 depends on USB && USB_DEVICEFS && EXPERIMENTAL 229 help 230 This driver is for testing host controller software. It is used 231 with specialized device firmware for regression and stress testing, 232 to help prevent problems from cropping up with "real" drivers. 233 234 See <http://www.linux-usb.org/usbtest/> for more information, 235 including sample test device firmware and "how to use it". 236 237