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