Menu

#359 lirc client with Raspberry Pi gpio kernel driver

Future
closed
nobody
None
na
2023-03-23
2020-05-22
No

First of all, sorry if I am missing completely the point or this is off-topic here. My best guess was that this was related to lircclient and thus related to this codebase, but maybe I'm misunderstanding things.

This ticket is related to this thread:
https://www.raspberrypi.org/forums/viewtopic.php?t=235256

I will try to summarize the important aspects:

Raspbian (Debian-base distro for the Raspberry Pi "card-sized computer") used a lirc_dev kernel thingy to have support for LIRC through GPIO pins (with /dev/lircX devices). Eventually (kernel 4.19.x?) the kernel driver dropped that lirc_dev and used gpio-ir, which was a drop-in replacement compatible with the /dev/lircX devices, lircclient and everything else... except the irrecord which broke because reasons. To quote that thread:

However, the command "irrecord" included in lirc does not work with gpio-ir
because the signal from /dev/lircX generated by gpio-ir is
slightly different from that of lirc_dev as follows: (...)

The OP provides a patch which solves the issue and is available here.

I don't know if
the patch is generic
the behaviour of gpio-ir is reasonable
support for gpio-ir is something desirable in lirc
lirc should not be changed, gpio-ir should be changed instead

For the time being, I used that patch and I have been able to scan all my remotes, so it Works For Me[TM] but I wanted to make life easier for my future self when I inevitably have to reinstall Raspbian and everything breaks on me again --which I know will happen eventually.

Discussion

  • Sean Young

    Sean Young - 2023-03-23
    • status: open --> closed
     
  • Sean Young

    Sean Young - 2023-03-23

    A similar patch has been applied.

     

Log in to post a comment.