Hi Hans Thanks for your reply but I've not got much further.
I don't have a /sys/class/ir but I do have /sys/class/lirc so maybe thats it? However, nowhere within there can I find a file containing protocol options: [root@bandana lirc]# cd /sys/class/lirc/ [root@bandana lirc]# ls lirc0 [root@bandana lirc]# cd lirc0 [root@bandana lirc0]# ls dev device power subsystem uevent [root@bandana lirc0]# cat dev 241:0 [root@bandana lirc0]# cat device cat: device: Is a directory [root@bandana lirc0]# cat power/ cat: power/: Is a directory [root@bandana lirc0]# cat subsystem cat: subsystem: Is a directory [root@bandana lirc0]# cat uevent MAJOR=241 MINOR=0 DEVNAME=lirc0 What kernel are you running on your BPi? I presume you have access to one? Have you successfully used the IR on the BPi under 4.4? Thanks for your help! On Wed, Jan 20, 2016 at 9:37 AM, Hans de Goede <[email protected]> wrote: > Hi, > > On 20-01-16 10:23, Dan MacDonald wrote: > >> Has anyone had any success using IR on the BPi under 4.4.0 or another >> recent kernel? I was trying last night without any luck. >> >> To get the kernel to recognise it, I first had to >> >> modprobe sunxi-cir >> >> After loading that, the kernel seems to create (at least) two new IR input >> devices, /dev/input/event1 and /dev/input/event2 IIRC (I'm not logged into >> my BPi right now to checkbut I think that's correct) - one is just >> labelled >> sunxi-ir and the other was sunxi-ir mouse and keyboard or something. I got >> IR working with on the BPi with my remote under the sunxi 3.x kernel but >> there was only one IR input device then, /dev/input/event0. >> >> I've been testing /dev/input/event1 and /dev/input/event2 using the >> keybinding app but I've yet to get any input. Has anyone had more luck? Is >> there a better way to test it than using keybinding? >> > > You need to first set a ir-protocol, from the top of my head > go to /sys/class/ir/ir0 and then do "cat protocols" and then > echo "one-of-them" > protocols. > > If you do not have the right protocol listed make sure to load the kernel > module. > > Note as said this is all from the top of my head, so to path / filenames > may be a bit different then what I'm typing here. > > Once you've set the right proto (typically nec, sometimes rc4) then you > can test using e.g. evemu-record on the input node. AFAIK you should > get only one input node related to the ir btw..., evemu-record will > print the human friendly names of all nodes which should explain which > node is what. > > Regards, > > Hans > -- 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.
