Lines Matching +full:input +full:- +full:no +full:- +full:autorepeat
7 :Copyright: |copy| 1999-2001 Vojtech Pavlik <vojtech@ucw.cz> - Sponsored by SuSE
12 Input subsystem is a collection of drivers that is designed to support
13 all input devices under Linux. Most of the drivers reside in
14 drivers/input, although quite a few live in drivers/hid and
17 The core of the input subsystem is the input module, which must be
18 loaded before any other of the input modules - it serves as a way of
22 --------------
25 events (keystrokes, mouse movements) to the input module.
28 --------------
30 These modules get events from input core and pass them where needed
31 via various interfaces - keystrokes to the kernel, mouse movements via
41 input
51 crw-r--r-- 1 root root 13, 63 Mar 28 22:45 mice
57 mkdir input
58 mknod input/mice c 13 63
61 XFree to this device to use it - GPM should be called like::
63 gpm -t ps2 -m /dev/input/mice
69 Device "/dev/input/mice"
79 --------------
82 in-kernel consumers, as needed.
87 ``evdev`` is the generic input event interface. It passes the events
93 input, and all clients are encouraged to use it.
95 See :ref:`event-interface` for notes on API.
97 The devices are in /dev/input::
99 crw-r--r-- 1 root root 13, 64 Apr 1 10:49 event0
100 crw-r--r-- 1 root root 13, 65 Apr 1 10:50 event1
101 crw-r--r-- 1 root root 13, 66 Apr 1 10:50 event2
102 crw-r--r-- 1 root root 13, 67 Apr 1 10:50 event3
106 range. If there are more than 32 input devices in a system, additional
112 ``keyboard`` is in-kernel input handler and is a part of VT code. It
113 consumes keyboard keystrokes and handles user input for VT consoles.
118 ``mousedev`` is a hack to make legacy programs that use mouse input
120 a PS/2-style (a la /dev/psaux) mouse device available to the
123 Mousedev devices in /dev/input (as shown above) are::
125 crw-r--r-- 1 root root 13, 32 Mar 28 22:45 mouse0
126 crw-r--r-- 1 root root 13, 33 Mar 29 00:41 mouse1
127 crw-r--r-- 1 root root 13, 34 Mar 29 00:41 mouse2
128 crw-r--r-- 1 root root 13, 35 Apr 1 10:50 mouse3
131 crw-r--r-- 1 root root 13, 62 Apr 1 10:50 mouse30
132 crw-r--r-- 1 root root 13, 63 Apr 1 10:50 mice
135 the last one - ``mice``. This single character device is shared by all
138 that do not handle hotplug can open the device even when no mice are
157 :ref:`joystick-api` for details.
159 As soon as any joystick is connected, it can be accessed in /dev/input on::
161 crw-r--r-- 1 root root 13, 0 Apr 1 10:50 js0
162 crw-r--r-- 1 root root 13, 1 Apr 1 10:50 js1
163 crw-r--r-- 1 root root 13, 2 Apr 1 10:50 js2
164 crw-r--r-- 1 root root 13, 3 Apr 1 10:50 js3
171 --------------
175 hid-generic
178 ``hid-generic`` is one of the largest and most complex driver of the
189 The monitor and speaker controls should be easy to add to the hid/input
194 The usage of the usbhid module is very simple, it takes no parameters,
200 of hid-core.c and send me the syslog traces.
234 A driver for I-Force joysticks and wheels, both over USB and RS232.
246 Doing a ``cat /dev/input/mouse0`` (c, 13, 32) will verify that a mouse
250 available in the joystick package (see :ref:`joystick-doc`).
254 .. _event-interface:
260 /dev/input/eventX devices, and you'll always get a whole number of input
272 release. More types are defined in include/uapi/linux/input-event-codes.h.
275 list is in include/uapi/linux/input-event-codes.h.
279 release, 1 for keypress and 2 for autorepeat.
281 See :ref:`input-event-codes` for more information about various even codes.