-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update lirc #1101
Update lirc #1101
Conversation
I think you can drop lirc-0005-uinput.patch, this should be fixed upstream https://sourceforge.net/p/lirc/tickets/213/ lircd-uinput should now also work fine (https://sourceforge.net/p/lirc/tickets/211/) so I think we're now good to switch to that and drop the deprecated --uinput option of lircd. |
We might want this back then, lrusak@cd18f93 |
@HiassofT @lrusak Thanks!, wasn't sure about the uinput patch to begin with. I have now dropped Should |
I'm not sure about the |
Updated again: |
It is probably best to leave From lircd socket:
From eventlircd socket:
|
Seems to be working on NUC (Skylake, Harmony One with RC6 profile). Will include in build tonight. Please keep an eye out for issues. Edit: Build I just tested includes:
|
@MilhouseVH thanks for including this in your build! I have no more changes planed as everything seems to be back to "normal" after the |
I've tested Milhouse build 1231 on a RPi3 with GPIO receiver and so far everything seems to be fine! |
@MilhouseVH all good? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problems reported so far - seems to be good.
This PR updates lirc to 0.9.4c and fixes a build issue when python is not installed on the build host.
This needs more runtime testing before merge.
Dropped patches have been replaced by upstream.