fbui | Framebuffer-based graphical environment |
| download: https://git.y1.nz/archives/fbui.tar.gz | |
| README | Files | Log | Refs |
drivers/input/Kconfig
1 #
2 # Input device configuration
3 #
4
5 menu "Input device support"
6
7 config INPUT
8 tristate "Input devices (needed for keyboard, mouse, ...)" if EMBEDDED
9 default y
10 ---help---
11 Say Y here if you have any input device (mouse, keyboard, tablet,
12 joystick, steering wheel ...) connected to your system and want
13 it to be available to applications. This includes standard PS/2
14 keyboard and mouse.
15
16 Say N here if you have a headless (no monitor, no keyboard) system.
17
18 More information is available: <file:Documentation/input/input.txt>
19
20 If unsure, say Y.
21
22 To compile this driver as a module, choose M here: the
23 module will be called input.
24
25 comment "Userland interfaces"
26
27 config INPUT_MOUSEDEV
28 tristate "Mouse interface" if EMBEDDED
29 default y
30 depends on INPUT
31 ---help---
32 Say Y here if you want your mouse to be accessible as char devices
33 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
34 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
35 programs (includung SVGAlib, GPM and X) will be able to use your
36 mouse.
37
38 If unsure, say Y.
39
40 To compile this driver as a module, choose M here: the
41 module will be called mousedev.
42
43 config INPUT_MOUSEDEV_PSAUX
44 bool "Provide legacy /dev/psaux device"
45 default y
46 depends on INPUT_MOUSEDEV
47 ---help---
48 Say Y here if you want your mouse also be accessible as char device
49 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
50 the same as the data from /dev/input/mice.
51
52 If unsure, say Y.
53
54
55 config INPUT_MOUSEDEV_SCREEN_X
56 int "Horizontal screen resolution"
57 depends on INPUT_MOUSEDEV
58 default "1024"
59 help
60 If you're using a digitizer, or a graphic tablet, and want to use
61 it as a mouse then the mousedev driver needs to know the X window
62 screen resolution you are using to correctly scale the data. If
63 you're not using a digitizer, this value is ignored.
64
65 config INPUT_MOUSEDEV_SCREEN_Y
66 int "Vertical screen resolution"
67 depends on INPUT_MOUSEDEV
68 default "768"
69 help
70 If you're using a digitizer, or a graphic tablet, and want to use
71 it as a mouse then the mousedev driver needs to know the X window
72 screen resolution you are using to correctly scale the data. If
73 you're not using a digitizer, this value is ignored.
74
75 config INPUT_JOYDEV
76 tristate "Joystick interface"
77 depends on INPUT
78 ---help---
79 Say Y here if you want your joystick or gamepad to be
80 accessible as char device 13:0+ - /dev/input/jsX device.
81
82 If unsure, say Y.
83
84 More information is available: <file:Documentation/input/joystick.txt>
85
86 To compile this driver as a module, choose M here: the
87 module will be called joydev.
88
89 config INPUT_TSDEV
90 tristate "Touchscreen interface"
91 depends on INPUT
92 ---help---
93 Say Y here if you have an application that only can understand the
94 Compaq touchscreen protocol for absolute pointer data. This is
95 useful namely for embedded configurations.
96
97 If unsure, say N.
98
99 To compile this driver as a module, choose M here: the
100 module will be called tsdev.
101
102 config INPUT_TSDEV_SCREEN_X
103 int "Horizontal screen resolution"
104 depends on INPUT_TSDEV
105 default "240"
106
107 config INPUT_TSDEV_SCREEN_Y
108 int "Vertical screen resolution"
109 depends on INPUT_TSDEV
110 default "320"
111
112 config INPUT_EVDEV
113 tristate "Event interface"
114 depends on INPUT
115 help
116 Say Y here if you want your input device events be accessible
117 under char device 13:64+ - /dev/input/eventX in a generic way.
118
119 To compile this driver as a module, choose M here: the
120 module will be called evdev.
121
122 config INPUT_EVBUG
123 tristate "Event debugging"
124 depends on INPUT
125 ---help---
126 Say Y here if you have a problem with the input subsystem and
127 want all events (keypresses, mouse movements), to be output to
128 the system log. While this is useful for debugging, it's also
129 a security threat - your keypresses include your passwords, of
130 course.
131
132 If unsure, say N.
133
134 To compile this driver as a module, choose M here: the
135 module will be called evbug.
136
137 config INPUT_FBUI
138 tristate "FBUI input handling"
139 default y
140 depends on INPUT
141 ---help---
142 Say Y here if you will also enable FBUI, which is the
143 in-kernel framebuffer-based graphical user interface.
144
145
146 comment "Input I/O drivers"
147
148 source "drivers/input/gameport/Kconfig"
149
150 source "drivers/input/serio/Kconfig"
151
152 comment "Input Device Drivers"
153
154 source "drivers/input/keyboard/Kconfig"
155
156 source "drivers/input/mouse/Kconfig"
157
158 source "drivers/input/joystick/Kconfig"
159
160 source "drivers/input/touchscreen/Kconfig"
161
162 source "drivers/input/misc/Kconfig"
163
164 endmenu
165
This webpage is intended to be an accessible preview of this repository. To get a fuller picture, clone it and use the git CLI.