Kconfig 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258
  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_IDMOUSE
  113. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  114. depends on USB
  115. help
  116. Say Y here if you want to use the fingerprint sensor on
  117. the Siemens ID Mouse. There is also a Siemens ID Mouse
  118. _Professional_, which has not been tested with this driver,
  119. but uses the same sensor and may therefore work.
  120. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  121. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  122. See also <http://www.fs.tum.de/~echtler/idmouse/>.
  123. config USB_FTDI_ELAN
  124. tristate "Elan PCMCIA CardBus Adapter USB Client"
  125. depends on USB
  126. default M
  127. help
  128. ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
  129. Currently only the U132 adapter is available.
  130. The U132 is specifically designed for CardBus PC cards that contain
  131. an OHCI host controller. Typical PC cards are the Orange Mobile 3G
  132. Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
  133. with PC cards that do not contain an OHCI controller. To use a U132
  134. adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
  135. module which is a USB host controller driver that talks to the OHCI
  136. controller within CardBus card that are inserted in the U132 adapter.
  137. This driver has been tested with a CardBus OHCI USB adapter, and
  138. worked with a USB PEN Drive inserted into the first USB port of
  139. the PCCARD. A rather pointless thing to do, but useful for testing.
  140. See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
  141. It is safe to say M here.
  142. config USB_APPLEDISPLAY
  143. tristate "Apple Cinema Display support"
  144. depends on USB
  145. select BACKLIGHT_LCD_SUPPORT
  146. select BACKLIGHT_CLASS_DEVICE
  147. help
  148. Say Y here if you want to control the backlight of Apple Cinema
  149. Displays over USB. This driver provides a sysfs interface.
  150. source "drivers/usb/misc/sisusbvga/Kconfig"
  151. config USB_LD
  152. tristate "USB LD driver"
  153. depends on USB
  154. help
  155. This driver is for generic USB devices that use interrupt transfers,
  156. like LD Didactic's USB devices.
  157. To compile this driver as a module, choose M here: the
  158. module will be called ldusb.
  159. config USB_TRANCEVIBRATOR
  160. tristate "PlayStation 2 Trance Vibrator driver support"
  161. depends on USB
  162. help
  163. Say Y here if you want to connect a PlayStation 2 Trance Vibrator
  164. device to your computer's USB port.
  165. To compile this driver as a module, choose M here: the
  166. module will be called trancevibrator.
  167. config USB_IOWARRIOR
  168. tristate "IO Warrior driver support"
  169. depends on USB
  170. help
  171. Say Y here if you want to support the IO Warrior devices from Code
  172. Mercenaries. This includes support for the following devices:
  173. IO Warrior 40
  174. IO Warrior 24
  175. IO Warrior 56
  176. IO Warrior 24 Power Vampire
  177. To compile this driver as a module, choose M here: the
  178. module will be called iowarrior.
  179. config USB_TEST
  180. tristate "USB testing driver"
  181. depends on USB && USB_DEVICEFS
  182. help
  183. This driver is for testing host controller software. It is used
  184. with specialized device firmware for regression and stress testing,
  185. to help prevent problems from cropping up with "real" drivers.
  186. See <http://www.linux-usb.org/usbtest/> for more information,
  187. including sample test device firmware and "how to use it".
  188. config USB_ISIGHTFW
  189. tristate "iSight firmware loading support"
  190. depends on USB
  191. select FW_LOADER
  192. help
  193. This driver loads firmware for USB Apple iSight cameras, allowing
  194. them to be driven by the USB video class driver available at
  195. http://linux-uvc.berlios.de
  196. The firmware for this driver must be extracted from the MacOS
  197. driver beforehand. Tools for doing so are available at
  198. http://bersace03.free.fr
  199. config USB_VST
  200. tristate "USB VST driver"
  201. depends on USB
  202. help
  203. This driver is intended for Vernier Software Technologies
  204. bulk usb devices such as their Ocean-Optics spectrometers or
  205. Labquest.
  206. It is a bulk channel driver with configurable read and write
  207. timeouts.
  208. To compile this driver as a module, choose M here: the
  209. module will be called vstusb.