Kconfig 8.6 KB

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