Kconfig 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162
  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_AUERSWALD
  29. tristate "USB Auerswald ISDN support (EXPERIMENTAL)"
  30. depends on USB && EXPERIMENTAL
  31. help
  32. Say Y here if you want to connect an Auerswald USB ISDN Device
  33. to your computer's USB port.
  34. To compile this driver as a module, choose M here: the
  35. module will be called auerswald.
  36. config USB_RIO500
  37. tristate "USB Diamond Rio500 support (EXPERIMENTAL)"
  38. depends on USB && EXPERIMENTAL
  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 (EXPERIMENTAL)"
  47. depends on USB && EXPERIMENTAL
  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_LED
  67. tristate "USB LED driver support"
  68. depends on USB
  69. help
  70. Say Y here if you want to connect an USBLED device to your
  71. computer's USB port.
  72. To compile this driver as a module, choose M here: the
  73. module will be called usbled.
  74. config USB_CYTHERM
  75. tristate "Cypress USB thermometer driver support"
  76. depends on USB
  77. help
  78. Say Y here if you want to connect a Cypress USB thermometer
  79. device to your computer's USB port. This device is also known
  80. as the Cypress USB Starter kit or demo board. The Elektor
  81. magazine published a modified version of this device in issue
  82. #291.
  83. To compile this driver as a module, choose M here: the
  84. module will be called cytherm.
  85. config USB_PHIDGETKIT
  86. tristate "USB PhidgetKit support"
  87. depends on USB
  88. help
  89. Say Y here if you want to connect a PhidgetKit USB device from
  90. Phidgets Inc.
  91. To compile this driver as a module, choose M here: the
  92. module will be called phidgetkit.
  93. config USB_PHIDGETSERVO
  94. tristate "USB PhidgetServo support"
  95. depends on USB
  96. help
  97. Say Y here if you want to connect an 1 or 4 Motor PhidgetServo
  98. servo controller version 2.0 or 3.0.
  99. Phidgets Inc. has a web page at <http://www.phidgets.com/>.
  100. To compile this driver as a module, choose M here: the
  101. module will be called phidgetservo.
  102. config USB_IDMOUSE
  103. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  104. depends on USB
  105. help
  106. Say Y here if you want to use the fingerprint sensor on
  107. the Siemens ID Mouse. There is also a Siemens ID Mouse
  108. _Professional_, which has not been tested with this driver,
  109. but uses the same sensor and may therefore work.
  110. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  111. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  112. See also <http://www.fs.tum.de/~echtler/idmouse/>.
  113. source "drivers/usb/misc/sisusbvga/Kconfig"
  114. config USB_LD
  115. tristate "USB LD driver"
  116. depends on USB && EXPERIMENTAL
  117. help
  118. This driver is for generic USB devices that use interrupt transfers,
  119. like LD Didactic's USB devices.
  120. To compile this driver as a module, choose M here: the
  121. module will be called ldusb.
  122. config USB_TEST
  123. tristate "USB testing driver (DEVELOPMENT)"
  124. depends on USB && USB_DEVICEFS && EXPERIMENTAL
  125. help
  126. This driver is for testing host controller software. It is used
  127. with specialized device firmware for regression and stress testing,
  128. to help prevent problems from cropping up with "real" drivers.
  129. See <http://www.linux-usb.org/usbtest/> for more information,
  130. including sample test device firmware and "how to use it".