Kconfig 8.6 KB

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