- lirc_serial move out of staging (is no longer part of the kernel)
and/or rename to serial_ir.
Here are my notes about those lirc changes from March 2019.
You still need to release the serial port from normal serial driver: setserial /dev/ttyS0 uart none
Load serial_ir module, no need for lirc_serial.
serial_ir will create a /dev/lircN device, and also a /dev/input/eventM
Load one of the ir_*_decoder modules too, for example ir_rc5_decoder or ir_rc6_decoder depending on the type of your remote. This way you'll probably don't need to teach remotes to lircd with irrecord, but can just read events from /dev/input/eventM
Do a cat /sys/class/rc/rc*/protocols That will show you list(s) of supported remote models and you can change the model by writing your choice back to the protocols file.
Before I knew all this, I tried to teach remote to lircd with irrecord, like irrecord -H default -d /dev/lircN
This way I couldn't get irrecord to learn about a Technotrend remote I have.
After I chose rc-5 with the protocols file, I started to get events from /dev/ input/eventM. This wasn't enough to get lircd to react to the events, so I had to teach them to lircd by running irrecord -H devinput -d /dev/input/eventM
After that I ran lircd with lircd -e lirc -H devinput \ -d /dev/input/by-path/platform-serial_ir.0-event-ir \ /etc/lircd.conf
And now lirc works again!
Unfortunately I still couldn't figure out how I could use the Technotrend remote with built-in ir receiver of CT2-4400. There is a /dev/input/event- device for it, but no events come through.