2 # Input core configuration
4 menuconfig INPUT_KEYBOARD
5 bool "Keyboards" if EMBEDDED || !X86
8 Say Y here, and a list of supported keyboards will be displayed.
9 This option doesn't affect the kernel.
16 tristate "AT keyboard" if EMBEDDED || !X86_PC
20 select SERIO_I8042 if X86_PC
21 select SERIO_GSCPS2 if GSC
23 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
24 you'll need this, unless you have a different type keyboard (USB, ADB
25 or other). This also works for AT and PS/2 keyboards connected over a
26 PS/2 to serial converter.
30 To compile this driver as a module, choose M here: the
31 module will be called atkbd.
33 config KEYBOARD_ATKBD_HP_KEYCODES
34 bool "Use HP keyboard scancodes"
35 depends on PARISC && KEYBOARD_ATKBD
38 Say Y here if you have a PA-RISC machine and want to use an AT or
39 PS/2 keyboard, and your keyboard uses keycodes that are specific to
42 Say N if you use a standard keyboard.
44 config KEYBOARD_ATKBD_RDI_KEYCODES
45 bool "Use PrecisionBook keyboard scancodes"
46 depends on KEYBOARD_ATKBD_HP_KEYCODES
49 If you have an RDI PrecisionBook, say Y here if you want to use its
50 built-in keyboard (as opposed to an external keyboard).
52 The PrecisionBook has five keys that conflict with those used by most
53 AT and PS/2 keyboards. These are as follows:
55 PrecisionBook Standard AT or PS/2
61 Left 102nd key (the key to the right of Left Shift)
63 If you say N here, and use the PrecisionBook keyboard, then each key
64 in the left-hand column will be interpreted as the corresponding key
65 in the right-hand column.
67 If you say Y here, and use an external keyboard, then each key in the
68 right-hand column will be interpreted as the key shown in the
71 config KEYBOARD_SUNKBD
72 tristate "Sun Type 4 and Type 5 keyboard"
75 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
76 connected either to the Sun keyboard connector or to an serial
77 (RS-232) port via a simple adapter.
79 To compile this driver as a module, choose M here: the
80 module will be called sunkbd.
83 tristate "DECstation/VAXstation LK201/LK401 keyboard"
86 Say Y here if you want to use a LK201 or LK401 style serial
87 keyboard. This keyboard is also useable on PCs if you attach
88 it with the inputattach program. The connector pinout is
89 described within lkkbd.c.
91 To compile this driver as a module, choose M here: the
92 module will be called lkkbd.
94 config KEYBOARD_LOCOMO
95 tristate "LoCoMo Keyboard Support"
96 depends on SHARP_LOCOMO && INPUT_KEYBOARD
98 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
100 To compile this driver as a module, choose M here: the
101 module will be called locomokbd.
103 config KEYBOARD_XTKBD
104 tristate "XT keyboard"
107 Say Y here if you want to use the old IBM PC/XT keyboard (or
108 compatible) on your system. This is only possible with a
109 parallel port keyboard adapter, you cannot connect it to the
110 keyboard port on a PC that runs Linux.
112 To compile this driver as a module, choose M here: the
113 module will be called xtkbd.
115 config KEYBOARD_NEWTON
116 tristate "Newton keyboard"
119 Say Y here if you have a Newton keyboard on a serial port.
121 To compile this driver as a module, choose M here: the
122 module will be called newtonkbd.
124 config KEYBOARD_STOWAWAY
125 tristate "Stowaway keyboard"
128 Say Y here if you have a Stowaway keyboard on a serial port.
129 Stowaway compatible keyboards like Dicota Input-PDA keyboard
130 are also supported by this driver.
132 To compile this driver as a module, choose M here: the
133 module will be called stowaway.
135 config KEYBOARD_CORGI
136 tristate "Corgi keyboard"
137 depends on PXA_SHARPSL
140 Say Y here to enable the keyboard on the Sharp Zaurus SL-C7xx
143 To compile this driver as a module, choose M here: the
144 module will be called corgikbd.
146 config KEYBOARD_SPITZ
147 tristate "Spitz keyboard"
148 depends on PXA_SHARPSL
151 Say Y here to enable the keyboard on the Sharp Zaurus SL-C1000,
152 SL-C3000 and Sl-C3100 series of PDAs.
154 To compile this driver as a module, choose M here: the
155 module will be called spitzkbd.
157 config KEYBOARD_AMIGA
158 tristate "Amiga keyboard"
161 Say Y here if you are running Linux on any AMIGA and have a keyboard
164 To compile this driver as a module, choose M here: the
165 module will be called amikbd.
167 config KEYBOARD_HIL_OLD
168 tristate "HP HIL keyboard support (simple driver)"
169 depends on GSC || HP300
172 The "Human Interface Loop" is a older, 8-channel USB-like
173 controller used in several Hewlett Packard models. This driver
174 was adapted from the one written for m68k/hp300, and implements
175 support for a keyboard attached to the HIL port, but not for
176 any other types of HIL input devices like mice or tablets.
177 However, it has been thoroughly tested and is stable.
179 If you want full HIL support including support for multiple
180 keyboards, mice, and tablets, you have to enable the
181 "HP System Device Controller i8042 Support" in the input/serio
185 tristate "HP HIL keyboard support"
186 depends on GSC || HP300
192 The "Human Interface Loop" is a older, 8-channel USB-like
193 controller used in several Hewlett Packard models.
194 This driver implements support for HIL-keyboards attached
195 to your machine, so normally you should say Y here.
198 tristate "TI OMAP keypad support"
199 depends on (ARCH_OMAP1 || ARCH_OMAP2)
201 Say Y here if you want to use the OMAP keypad.
203 To compile this driver as a module, choose M here: the
204 module will be called omap-keypad.
206 config KEYBOARD_AAED2000
207 tristate "AAED-2000 keyboard"
208 depends on MACH_AAED2000
211 Say Y here to enable the keyboard on the Agilent AAED-2000
214 To compile this driver as a module, choose M here: the
215 module will be called aaed2000_kbd.
218 tristate "GPIO Buttons"
219 depends on GENERIC_GPIO
221 This driver implements support for buttons connected
222 to GPIO pins of various CPUs (and some other chips).
224 Say Y here if your device has buttons connected
225 directly to such GPIO pins. Your board-specific
226 setup logic must also provide a platform device,
227 with configuration data saying which GPIOs are used.
229 To compile this driver as a module, choose M here: the
230 module will be called gpio-keys.