IR remotes use different protocols. These protocols are supported by different kernel modules like NEC, RC5, etc. You also need keymaps for mapping the remote protocols into standard key events. Look in the kernel source at drivers/media/rc/...... If you get things set up right Linux can decode every IR remote on the market.
On Thu, Dec 4, 2014 at 8:42 AM, Simo Xefil <[email protected]> wrote: > > Hello to all! > I'm trying to debug IR signals on a A20 based board with Arch Linux. > I'm trying to test if I'm able to read values from a remote IR control. > During boot I can recognise the ir as follow: > > > [ 2.478959] input: sunxi-ir as /devices/virtual/input/input0 > > > > Looking on the devices I get: > > # cat /proc/bus/input/devices > > > I: Bus=0019 Vendor=0001 Product=0001 Version=0100 > N: Name="sunxi-ir" > P: Phys=RemoteIR/input1 > S: Sysfs=/devices/virtual/input/input0 > U: Uniq= > H: Handlers=sysrq rfkill kbd event0 > B: PROP=0 > B: EV=3 > B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff > fffffffe > > > (...) > > > > Then, using this command I expect to see some signals: > > # evtest /dev/input/event0 > Input driver version is 1.0.1 > Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100 > Input device name: "sunxi-ir" > Supported events: > Event type 0 (EV_SYN) > Event type 1 (EV_KEY) > Event code 1 (KEY_ESC) > Event code 2 (KEY_1) > Event code 3 (KEY_2) > (...) > Event code 247 (KEY_RFKILL) > Event code 248 (?) > Event code 249 (?) > Event code 250 (?) > Event code 251 (?) > Event code 252 (?) > Event code 253 (?) > Event code 254 (?) > Event code 255 (?) > Properties: > Testing ... (interrupt to exit) > > > I've tested a PHILIPS remote, no signal, and a SAMSUNG remote. On the > samsung remote I get values. > > Event: time 1417698487.436218, type 1 (EV_KEY), code 2 (KEY_1), value 1 > Event: time 1417698487.436227, -------------- EV_SYN ------------ > Event: time 1417698487.959104, type 1 (EV_KEY), code 2 (KEY_1), value 0 > Event: time 1417698487.959113, -------------- EV_SYN ------------ > Event: time 1417698489.688749, type 1 (EV_KEY), code 2 (KEY_1), value 1 > Event: time 1417698489.688757, -------------- EV_SYN ------------ > Event: time 1417698489.989063, type 1 (EV_KEY), code 2 (KEY_1), value 0 > Event: time 1417698489.989070, -------------- EV_SYN ------------ > Event: time 1417698490.761935, type 1 (EV_KEY), code 2 (KEY_1), value 1 > Event: time 1417698490.761947, -------------- EV_SYN ------------ > Event: time 1417698491.069059, type 1 (EV_KEY), code 2 (KEY_1), value 0 > Event: time 1417698491.069065, -------------- EV_SYN ------------ > Event: time 1417698491.961707, type 1 (EV_KEY), code 2 (KEY_1), value 1 > Event: time 1417698491.961715, -------------- EV_SYN ------------ > Event: time 1417698492.269065, type 1 (EV_KEY), code 2 (KEY_1), value 0 > Event: time 1417698492.269072, -------------- EV_SYN ------------ > > Also the device works. All remote are working used on their own devices. > My goal is to remplicate the signal of a remote command of an automatic > pellet stove. I would like to clone the signal. The remote works on the > stove, also it's not a remote issue. Is there a way to debug or to know if > the remote is incompatible? Reading the instructions it's defined as Infra > Red. Are there different IR signals? I've read that in some cases, values > sent above 255 are ignored. Could be the case? How in case to solve? > > Thanks! > > Simon > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Jon Smirl [email protected] -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
