From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] LIRC on RPi 3 B+ does not work with IR receivers connected via GPIO
Date: Fri, 29 Apr 2022 04:13:04 +0200 [thread overview]
Message-ID: <20220429021304.jieKjlY_9U0nSwwT7VA_Hysw2axEEb2HCbbWyCRwGe4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10905@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
Closed issue by Leon-Plickat on void-packages repository
https://github.com/void-linux/void-packages/issues/10905
Description:
I tried using a IR receiver connected to the GPIO ports of the Pi, but was unable to get the LIRC driver to work.
I followed the steps described on [this website](http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/). Other website describe a similar procedure to get IR via GPIO working, so I believe this is the correct way. As basically all Pi related information on the internet, it assumes one is using Raspbian. However it should still apply to every distribution whichs kernel has the correct driver.
I tried both: Doing exactly as described in the article as well as adapting it to void (meaning things like creating `/etc/modules-load.d/lirc.conf` instead of modifying `/etc/modules`). But `/dev/lirc0` never appeared.
Appearently, the LIRC driver in the kernel needs to patched in order for it to work with GPIO, [as described on the website of the author of mentioned patch](http://aron.ws/projects/lirc_rpi/).
Since someone on Reddit (from where I was referred to here) mentioned that they got LIRC to work with an USB IR receiver on the Pi, I believe that the default LIRC drivers are in voids kernel, however as the user space tools of LIRC are not packaged in void aarch64, I am tempted to believe that the patch is also not applied to the driver.
Is my assumption, that the version of LIRC patched to work with the GPIO ports of the Pi is not included in voids aarch64 kernel, correct? Or am I missing something? And if this is the case, is there any way of getting LIRC to work with a IR receiver connected via GPIO?
next parent reply other threads:[~2022-04-29 2:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10905@inbox.vuxu.org>
2022-04-29 2:13 ` github-actions [this message]
2022-05-18 20:18 ` Anachron
2022-05-19 7:03 ` Anachron
2022-05-19 7:04 ` Anachron
2022-05-19 8:33 ` Anachron
2022-05-19 9:05 ` Anachron
2022-05-19 9:57 ` Anachron
2022-05-19 9:58 ` Anachron
2022-05-19 10:00 ` Anachron
2022-05-19 10:07 ` Anachron
2022-05-19 10:08 ` Anachron
2022-05-19 10:33 ` Anachron
2022-05-19 10:34 ` Anachron
2022-05-19 10:38 ` Anachron
2023-01-19 23:14 ` zdykstra
2023-01-20 7:44 ` Anachron
2023-01-20 7:45 ` Anachron
2023-01-20 14:03 ` zdykstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220429021304.jieKjlY_9U0nSwwT7VA_Hysw2axEEb2HCbbWyCRwGe4@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).