aboutsummaryrefslogtreecommitdiffstats
path: root/util/av7110_loadkeys/philips1358.rc5
blob: 805755ed61943ef1d50e1fd0fa5e3ce65336de06 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

0x00 KEY_0
0x01 KEY_1
0x02 KEY_2
0x03 KEY_3
0x04 KEY_4
0x05 KEY_5
0x06 KEY_6
0x07 KEY_7
0x08 KEY_8
0x09 KEY_9
0x0C KEY_POWER
0x0D KEY_MUTE
0x0E KEY_OK
0x0F KEY_DIGITS
0x10 KEY_RIGHT
0x11 KEY_LEFT
0x1E KEY_STOP
0x20 KEY_UP
0x21 KEY_DOWN
0x23 KEY_AB
0x24 KEY_RECORD
0x25 KEY_SUBTITLE
0x26 KEY_INFO
0x29 KEY_PLAY
0x2A KEY_FORWARD
0x2B KEY_PAUSE
0x2C KEY_REWIND
0x2D KEY_F4
0x2E KEY_F3
0x32 KEY_YELLOW
0x34 KEY_BLUE
0x36 KEY_GREEN
0x37 KEY_RED
0x38 KEY_AUX
0x3C KEY_F2
0x3D KEY_SCREEN
0x3F KEY_F1
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 11:32:27 +0000
g the /proc/av7110_ir interface. just call # ./av7110_loadkeys [-i|--invert] [-a|--address <num>] keymapname.(rc5|rcmm) > /proc/av7110_ir If your IR receiver hardware inverts the signal, you should use the -i or --invert command line option. If you have two or more devices which use the same IR protocol, you should specify the -a or --address parameter. If the parameter is omitted, the driver listens to all device addresses. Some examples: Listen to *any* IR transmitter with uses the RC5 protocol: # ./av7110_loadkeys hauppauge.rc5 > /proc/av7110_ir Listen to RC5 transmitter with address 2: # ./av7110_loadkeys -a 2 hauppauge.rc5 > /proc/av7110_ir If you don't know the correct value for the -a parameter, take a look on the debug output of the driver (see below). Now you can test your hardware setup using evtest # ./evtest /dev/input/eventX where eventX is the IR input event device, usually event0 if you don't use USB mice or keyboards. ------------------------------------------------------------------------ Keymaps are in format: <key> <associated input keycode> 0x00 KEY_0 0x01 KEY_1 0x42 KEY_HOME ------------------------------------------------------------------------ In order to write a new keymap you might want to see the raw key values in the kernel log. Use # insmod dvb-ttpci.o av7110_ir_debug=1 in order to enable some verbosity in the av7110_ir driver. Then watch the kernel log while pressing your remote control keys. When you don't see any messages in your kernel log you should check all electrical connections, the selected protocol (RC5 or RCMM?) and the inversion setting. You find a list of all linux input key identifiers in </usr/include/input.h> and "./input_fake.h". Please post new keymaps on the linux-dvb mailing list or send them to me <holger@convergence.de>. have fun! Holger
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 11:32:26 +0000