Lines Matching refs:a
12 Every time a key is pressed on a remote controller, a scan code is produced.
13 Also, on most hardware, keeping a key pressed for more than a few dozens of
14 milliseconds produce a repeat key event. That's somewhat similar to what
15 a normal keyboard or mouse is handled internally on Linux\ [#f1]_. So, the
22 produces one event for a key press and another one for key release. On
31 The infrared transmission is done by blinking a infrared emitter using a
36 In other words, a typical IR transmission can be viewed as a sequence of
37 *PULSE* and *SPACE* events, each with a given duration.
41 For example, the NEC protocol uses a carrier of 38kHz, and transmissions
42 start with a 9ms *PULSE* and a 4.5ms SPACE. It then transmits 16 bits of
43 scan code, being 8 bits for address (usually it is a fixed number for a
45 with 560µs *PULSE* followed by 1690µs *SPACE* and a bit "0" is modulated
48 At receiver, a simple low-pass filter can be used to convert the received
49 signal in a sequence of *PULSE/SPACE* events, filtering out the carrier
53 So, a simple IR receiver hardware will just provide a sequence of timings
56 :c:type:`rc_driver_type`\ [#f2]_. Other hardware come with a
73 When the RC code receives a scan code (either directly, by a driver
75 to convert into a Linux input event code. This is done via a mapping
79 devices. It also supports loading a table in runtime, via some