2 # USB Miscellaneous driver configuration
4 comment "USB Miscellaneous drivers"
7 tristate "EMI 6|2m USB Audio interface support"
9 This driver loads firmware to Emagic EMI 6|2m low latency USB
10 Audio and Midi interface.
12 After firmware load the device is handled with standard linux
15 This code is also available as a module ( = code which can be
16 inserted in and removed from the running kernel whenever you want).
17 The module will be called audio. If you want to compile it as a
18 module, say M here and read <file:Documentation/kbuild/modules.txt>.
21 tristate "EMI 2|6 USB Audio interface support"
23 This driver loads firmware to Emagic EMI 2|6 low latency USB
26 After firmware load the device is handled with standard linux
29 To compile this driver as a module, choose M here: the
30 module will be called emi26.
33 tristate "ADU devices from Ontrak Control Systems"
35 Say Y if you want to use an ADU device from Ontrak Control
38 To compile this driver as a module, choose M here. The module
39 will be called adutux.
42 tristate "USB 7-Segment LED Display"
44 Say Y here if you have a USB 7-Segment Display by Delcom
46 To compile this driver as a module, choose M here: the
47 module will be called usbsevseg.
50 tristate "USB Lego Infrared Tower support"
52 Say Y here if you want to connect a USB Lego Infrared Tower to your
55 This code is also available as a module ( = code which can be
56 inserted in and removed from the running kernel whenever you want).
57 The module will be called legousbtower. If you want to compile it as
58 a module, say M here and read
59 <file:Documentation/kbuild/modules.txt>.
62 tristate "USB LCD driver support"
64 Say Y here if you want to connect an USBLCD to your computer's
65 USB port. The USBLCD is a small USB interface board for
66 alphanumeric LCD modules. See <http://www.usblcd.de/> for more
69 To compile this driver as a module, choose M here: the
70 module will be called usblcd.
73 tristate "USB LED driver support"
75 Say Y here if you want to connect an USBLED device to your
78 To compile this driver as a module, choose M here: the
79 module will be called usbled.
81 config USB_CYPRESS_CY7C63
82 tristate "Cypress CY7C63xxx USB driver support"
84 Say Y here if you want to connect a Cypress CY7C63xxx
85 micro controller to your computer's USB port. Currently this
86 driver supports the pre-programmed devices (incl. firmware)
87 by AK Modul-Bus Computer GmbH.
89 Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
91 To compile this driver as a module, choose M here: the
92 module will be called cypress_cy7c63.
95 tristate "Cypress USB thermometer driver support"
97 Say Y here if you want to connect a Cypress USB thermometer
98 device to your computer's USB port. This device is also known
99 as the Cypress USB Starter kit or demo board. The Elektor
100 magazine published a modified version of this device in issue
103 To compile this driver as a module, choose M here: the
104 module will be called cytherm.
107 tristate "Siemens ID USB Mouse Fingerprint sensor support"
109 Say Y here if you want to use the fingerprint sensor on
110 the Siemens ID Mouse. There is also a Siemens ID Mouse
111 _Professional_, which has not been tested with this driver,
112 but uses the same sensor and may therefore work.
114 This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
115 which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
117 See also <http://www.fs.tum.de/~echtler/idmouse/>.
120 tristate "Elan PCMCIA CardBus Adapter USB Client"
122 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
123 Currently only the U132 adapter is available.
125 The U132 is specifically designed for CardBus PC cards that contain
126 an OHCI host controller. Typical PC cards are the Orange Mobile 3G
127 Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
128 with PC cards that do not contain an OHCI controller. To use a U132
129 adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
130 module which is a USB host controller driver that talks to the OHCI
131 controller within CardBus card that are inserted in the U132 adapter.
133 This driver has been tested with a CardBus OHCI USB adapter, and
134 worked with a USB PEN Drive inserted into the first USB port of
135 the PCCARD. A rather pointless thing to do, but useful for testing.
137 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
139 It is safe to say M here.
141 config USB_APPLEDISPLAY
142 tristate "Apple Cinema Display support"
143 select BACKLIGHT_LCD_SUPPORT
144 select BACKLIGHT_CLASS_DEVICE
146 Say Y here if you want to control the backlight of Apple Cinema
147 Displays over USB. This driver provides a sysfs interface.
149 source "drivers/usb/misc/sisusbvga/Kconfig"
152 tristate "USB LD driver"
154 This driver is for generic USB devices that use interrupt transfers,
155 like LD Didactic's USB devices.
157 To compile this driver as a module, choose M here: the
158 module will be called ldusb.
160 config USB_TRANCEVIBRATOR
161 tristate "PlayStation 2 Trance Vibrator driver support"
163 Say Y here if you want to connect a PlayStation 2 Trance Vibrator
164 device to your computer's USB port.
166 To compile this driver as a module, choose M here: the
167 module will be called trancevibrator.
170 tristate "IO Warrior driver support"
172 Say Y here if you want to support the IO Warrior devices from Code
173 Mercenaries. This includes support for the following devices:
177 IO Warrior 24 Power Vampire
179 To compile this driver as a module, choose M here: the
180 module will be called iowarrior.
183 tristate "USB testing driver"
185 This driver is for testing host controller software. It is used
186 with specialized device firmware for regression and stress testing,
187 to help prevent problems from cropping up with "real" drivers.
189 See <http://www.linux-usb.org/usbtest/> for more information,
190 including sample test device firmware and "how to use it".
192 config USB_EHSET_TEST_FIXTURE
193 tristate "USB EHSET Test Fixture driver"
195 Say Y here if you want to support the special test fixture device
196 used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
198 When the test fixture is connected, it can enumerate as one of several
199 VID/PID pairs. This driver then initiates a corresponding test mode on
200 the downstream port to which the test fixture is attached.
202 See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
206 tristate "iSight firmware loading support"
209 This driver loads firmware for USB Apple iSight cameras, allowing
210 them to be driven by the USB video class driver available at
211 http://linux-uvc.berlios.de
213 The firmware for this driver must be extracted from the MacOS
214 driver beforehand. Tools for doing so are available at
215 http://bersace03.free.fr
218 tristate "USB YUREX driver support"
220 Say Y here if you want to connect a YUREX to your computer's
221 USB port. The YUREX is a leg-shakes sensor. See
222 <http://bbu.kayac.com/en/> for further information.
223 This driver supports read/write of leg-shakes counter and
224 fasync for the counter update via a device file /dev/yurex*.
226 To compile this driver as a module, choose M here: the
227 module will be called yurex.
230 tristate "Functions for loading firmware on EZUSB chips"
232 Say Y here if you need EZUSB device support.
233 (Cypress FX/FX2/FX2LP microcontrollers)
235 config USB_HSIC_USB3503
236 tristate "USB3503 HSIC to USB20 Driver"
240 This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
242 config USB_LINK_LAYER_TEST
243 tristate "USB Link Layer Test driver"
245 This driver is for generating specific traffic for Super Speed Link
246 Layer Test Device. Say Y only when you want to conduct USB Super Speed
247 Link Layer Test for host controllers.
250 tristate "ChaosKey random number generator driver support"
253 Say Y here if you want to connect an AltusMetrum ChaosKey to
254 your computer's USB port. The ChaosKey is a hardware random
255 number generator which hooks into the kernel entropy pool to
256 ensure a large supply of entropy for /dev/random and
257 /dev/urandom and also provides direct access via /dev/chaoskeyX
259 To compile this driver as a module, choose M here: the
260 module will be called chaoskey.