Lines Matching full:input

12 Input subsystem  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
25 events (keystrokes, mouse movements) to the input module.
30 These modules get events from input core and pass them where needed
41 	input
57 	mkdir input
58 	mknod input/mice c 13 63
63 	gpm -t ps2 -m /dev/input/mice
69 	    Device      "/dev/input/mice"
87 ``evdev`` is the generic input event interface. It passes the events
93 input, and all clients are encouraged to use it.
97 The devices are in /dev/input::
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
123 Mousedev devices in /dev/input (as shown above) are::
159 As soon as any joystick is connected, it can be accessed in /dev/input on::
189 The monitor and speaker controls should be easy to add to the hid/input
246 Doing a ``cat /dev/input/mouse0`` (c, 13, 32) will verify that a mouse
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.
281 See :ref:`input-event-codes` for more information about various even codes.