Home
last modified time | relevance | path

Searched refs:keyboard (Results 1 – 25 of 92) sorted by relevance

1234

/linux-2.6.39/drivers/input/keyboard/
DKconfig36 tristate "Amiga keyboard"
39 Say Y here if you are running Linux on any AMIGA and have a keyboard
49 tristate "Atari keyboard"
53 Say Y here if you are running Linux on any Atari and have a keyboard
60 tristate "AT keyboard" if EXPERT || !X86
67 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
68 you'll need this, unless you have a different type keyboard (USB, ADB
78 bool "Use HP keyboard scancodes"
83 PS/2 keyboard, and your keyboard uses keycodes that are specific to
86 Say N if you use a standard keyboard.
[all …]
DMakefile41 obj-$(CONFIG_KEYBOARD_SPEAR) += spear-keyboard.o
/linux-2.6.39/drivers/input/serio/
DKconfig10 * standard AT keyboard and PS/2 mouse *
27 i8042 is the chip over which the standard AT keyboard and PS/2
64 tristate "Q40 keyboard controller"
68 tristate "Parallel port keyboard adapter"
72 an additional AT keyboard, XT keyboard or PS/2 mouse.
82 tristate "Acorn RiscPC keyboard controller"
87 keyboard connected to its keyboard controller.
93 tristate "AVR32 PSIF PS/2 keyboard and mouse controller"
97 and connect a PS/2 keyboard and/or mouse to it.
103 tristate "AMBA KMI keyboard controller"
[all …]
/linux-2.6.39/drivers/misc/ibmasm/
Dremote.c150 input->data.keyboard.key_code, in print_input()
151 input->data.keyboard.key_code, in print_input()
152 input->data.keyboard.key_flag, in print_input()
153 input->data.keyboard.key_down in print_input()
174 unsigned short code = input->data.keyboard.key_code; in send_keyboard_event()
180 input_report_key(dev, key, input->data.keyboard.key_down); in send_keyboard_event()
/linux-2.6.39/Documentation/input/
Dnotifier.txt3 One can use register_keyboard_notifier to get called back on keyboard
7 - 'vc' always provide the VC for which the keyboard event applies;
23 order to "eat" the event: the notify loop is stopped and the keyboard event is
Dinput.txt54 For the most usual configuration, with one USB mouse and one USB keyboard,
65 After this, the USB keyboard will work straight away, and the USB mouse
90 When you do all of the above, you can use your USB mouse and keyboard.
162 events into architecture-specific keyboard raw mode (Xlated AT Set2 on
164 keyboard.c module. This works well enough on all architectures that
168 The right way would be to pass the events to keyboard.c directly,
169 best if keyboard.c would itself be an event handler. This is done in
232 This should be the way for GPM and X to get keyboard and mouse
249 Typing a couple keys on the keyboard should be enough to check that
250 a USB keyboard works and is correctly connected to the kernel keyboard
Datarikbd.txt6 The Atari Corp. Intelligent Keyboard (ikbd) is a general purpose keyboard
8 products without modification. The keyboard, with its microcontroller,
17 different applications of the keyboard, joysticks, or mouse. Limited use of
23 The keyboard always returns key make/break scan codes. The ikbd generates
24 keyboard scan codes for each key press and release. The key scan make (key
27 exists in that position on a particular keyboard. The break code for each key
51 within the ikbd, or by converting mouse motion into keyboard cursor control
54 keyboard keys.
65 relative mouse motion events will be generated: (a) while the keyboard has
66 been 'paused' ( the event will be stored until keyboard communications is
[all …]
Dbcm5974.txt36 The Apple multi-touch trackpads report both mouse and keyboard events via
39 HID mouse and keyboard, and claim the whole device. To remedy, the usb
/linux-2.6.39/drivers/hid/
DKconfig97 tristate "Belkin Flip KVM and Wireless keyboard" if EXPERT
101 Support for Belkin Flip KVM and Wireless keyboard.
110 tristate "Cherry Cymotion keyboard" if EXPERT
114 Support for Cherry Cymotion keyboard.
130 - Prodikeys PC-MIDI keyboard.
135 multimedia keyboard, but will lack support for the musical keyboard
181 tristate "Ezkey BTC 8193 keyboard" if EXPERT
185 Support for Ezkey BTC 8193 keyboard.
310 tristate "Monterey Genius KB29E keyboard" if EXPERT
343 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
[all …]
/linux-2.6.39/drivers/input/
DKconfig9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
12 Say Y here if you have any input device (mouse, keyboard, tablet,
15 keyboard and mouse.
17 Say N here if you have a headless (no monitor, no keyboard) system.
166 source "drivers/input/keyboard/Kconfig"
DMakefile19 obj-$(CONFIG_INPUT_KEYBOARD) += keyboard/
/linux-2.6.39/drivers/hid/usbhid/
DKconfig15 You can't use this driver and the HIDBP (Boot Protocol) keyboard
55 to use the generic HID driver for your USB keyboard and prefer
56 to use the keyboard in its limited Boot Protocol mode instead.
/linux-2.6.39/Documentation/ABI/testing/
Dsysfs-driver-hid-roccat-arvo14 Description: The keyboard can store short macros with consist of 1 button with
34 Description: The keyboard lets the user deactivate 5 certain keys like the
47 Description: The keyboard has a condensed layout without num-lock key.
Dsysfs-driver-hid-prodikeys7 that the pc-midi keyboard will output.midi data.
/linux-2.6.39/Documentation/
DSAK.txt10 From the PC keyboard, Linux has two similar but different ways of
19 SAK works correctly when the keyboard is in raw mode. This means that
43 2: On the PC keyboard, SAK kills all applications which have
/linux-2.6.39/Documentation/usb/
Dgadget_hid.txt24 /* hid descriptor for a keyboard */
85 device type (keyboard / mouse / joystick) - E.G.:
87 # hid_gadget_test /dev/hidg0 keyboard
91 values are listed at program start. In keyboard mode you can
329 printf(" keyboard options:\n"
333 printf("\n keyboard values:\n"
369 fprintf(stderr, "Usage: %s devname mouse|keyboard|joystick\n",
/linux-2.6.39/Documentation/x86/
Dusb-legacy-support.txt8 feature that allows one to use the USB mouse and keyboard as if they were
9 their classic PS/2 counterparts. This means one can use an USB keyboard to
/linux-2.6.39/drivers/tty/vt/
DMakefile7 selection.o keyboard.o
/linux-2.6.39/lib/
DKconfig.kgdb76 bool "KGDB_KDB: keyboard as input device"
80 KDB can use a PS/2 type keyboard for an input device
/linux-2.6.39/arch/m68k/hp300/
DREADME.hp3009 The serial console is probably broken at the moment but the Topcat/HIL keyboard
/linux-2.6.39/arch/arm/mach-omap1/
Dams-delta-fiq-handler.S135 ands r10, r13, #KEYBRD_CLK_MASK @ extract keyboard status - set?
146 @ Process keyboard data
173 ands r8, r8, #KEYBRD_DATA_MASK @ is keyboard data line low?
/linux-2.6.39/arch/arm/mach-h720x/
DKconfig35 pins with the keyboard matrix controller, so you have to decide.
/linux-2.6.39/drivers/s390/char/
DMakefile5 obj-y += ctrlchar.o keyboard.o defkeymap.o sclp.o sclp_rw.o sclp_quiesce.o \
/linux-2.6.39/drivers/accessibility/
DKconfig8 That includes braille devices, speech synthesis, keyboard
/linux-2.6.39/arch/m68k/q40/
DREADME81 keyboard interface, 1 Programmable LED, 2x8bit DACs and up to 1MB ROM, 1MB
122 q40 receives AT make/break codes from the keyboard, these are translated to
123 the PC scancodes x86 Linux uses. So by theory every national keyboard should

1234