media/rc/rc-protos.rst

14 Therefore out the output of the IR decoder is a scancode; a single u32
35 The scancode encoding is *not* consistent with the lirc daemon (lircd) rc5
38 .. flat-table:: rc5 bits scancode mapping
43      - scancode bit
80 schemes. This bit is stored in bit 6 of the scancode, inverted. This is
85 This is much like rc-5 but one bit longer. The scancode is encoded
88 .. flat-table:: rc-5-sz bits scancode mapping
93      - scancode bit
133 .. flat-table:: rc-5x-20 bits scancode mapping
138      - scancode bit
185 The scancode is a 16 bits value, where the address is the lower 8 bits
192 which just differ in number of bits and scancode encoding.
194 .. flat-table:: sony-12 bits scancode mapping
199      - scancode bit
219 which just differ in number of bits and scancode encoding.
221 .. flat-table:: sony-12 bits scancode mapping
226      - scancode bit
246 which just differ in number of bits and scancode encoding.
248 .. flat-table:: sony-20 bits scancode mapping
253      - scancode bit
305 The scancode has a somewhat unusual encoding.
307 .. flat-table:: nec-32 bits scancode mapping
311      - scancode bit
336 Bis 8 to 20 of the scancode is the 13 bits address, and the lower 8
356 The scancode is the exact 16 bits as in the protocol. There is also a
364 The scancode is the exact 20 bits
372 The scancode is the exact 24 bits
402 There is a 5 bit address and a 8 bit command. In the scancode the address is
426 31 bits, and the scancode is simply the 31 bits with the top bit always 0.
432 https://www.sbprojects.net/knowledge/ir/rcmm.php. The scancode is simply
439 https://www.sbprojects.net/knowledge/ir/rcmm.php. The scancode is simply
446 https://www.sbprojects.net/knowledge/ir/rcmm.php. The scancode is simply