Kconfig 9.1 KB

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