Mailing List Archive

Anybody get the replacement for the lirc_zilog driver working in newer kernels?
Hello!

tl;dr - Is anyone successfully using the ir-kbd-i2c driver to do HD-PVR IR
blasting? If yes, what kernel and OS?

Long form:
I upgraded my Mythbuntu 16.04 LTS systems a few months back (in order to
get to v31 and other unrelated reasons). I knew that lirc in 18.04+ had
changed due to new lirc packages (based on the discussions here), so I was
bracing myself for that. But, I hadn't seen any reports specifically
regarding the lirc_zilog driver post 2018. In my case, I found I couldn't
get it working--I transmit only. I currently have Ubuntu 18.04 with the
highest 4.13* kernel that still had a working lirc_zilog (there was a batch
of kernels where lirc_zilog stopped working properly as well
<https://bugzilla.redhat.com/show_bug.cgi?id=1531927>).

Stuff I found
<https://git.linuxtv.org/media_tree.git/commit/drivers/media/i2c/ir-kbd-i2c.c?id=acaa34bf06e963f0b9481a3c16bfd6867e2369a0>
indicates lirc_zilog was to be replaced by ir-kbd-i2c, but at the time that
didn't work (for transmit anyways) for the HD-PVR in the standard 18.04
kernels for me. I don't know if the default kernel in 20.04 worked with
ir-kbd-i2c as I was still on v30 at the time I did the OS upgrade and
couldn't go to 20.04 without also going to v31. I know terms like "not
worked" / "didn't work" aren't that useful, but I remember in some cases I
got something like "hardware does not support sending", in other cases it
appeared successful, but there were no IR signals sent. Mostly I'm seeing
if the new driver works for anyone else. And while I can do web searches,
this audience is a good pool of folks that may have the answer ????

So, is anyone successfully using the ir-kbd-i2c driver to do HD-PVR
blasting?

Thanks!
--

James Purl - *jamesp@mzrfzr.com <jamesp@mzrfzr.com>*
Re: Anybody get the replacement for the lirc_zilog driver working in newer kernels? [ In reply to ]
I *just* saw a thread from 2019 asking the same thing that I somehow
missed. I could've just pinged that thread, but here we are - apologies for
the new thread (and if I missed any others).

On Thu, Dec 3, 2020 at 11:07 AM James Purl <jamesp@mzrfzr.com> wrote:

> Hello!
>
> tl;dr - Is anyone successfully using the ir-kbd-i2c driver to do HD-PVR IR
> blasting? If yes, what kernel and OS?
>
> Long form:
> I upgraded my Mythbuntu 16.04 LTS systems a few months back (in order to
> get to v31 and other unrelated reasons). I knew that lirc in 18.04+ had
> changed due to new lirc packages (based on the discussions here), so I was
> bracing myself for that. But, I hadn't seen any reports specifically
> regarding the lirc_zilog driver post 2018. In my case, I found I couldn't
> get it working--I transmit only. I currently have Ubuntu 18.04 with the
> highest 4.13* kernel that still had a working lirc_zilog (there was a batch
> of kernels where lirc_zilog stopped working properly as well
> <https://bugzilla.redhat.com/show_bug.cgi?id=1531927>).
>
> Stuff I found
> <https://git.linuxtv.org/media_tree.git/commit/drivers/media/i2c/ir-kbd-i2c.c?id=acaa34bf06e963f0b9481a3c16bfd6867e2369a0>
> indicates lirc_zilog was to be replaced by ir-kbd-i2c, but at the time that
> didn't work (for transmit anyways) for the HD-PVR in the standard 18.04
> kernels for me. I don't know if the default kernel in 20.04 worked with
> ir-kbd-i2c as I was still on v30 at the time I did the OS upgrade and
> couldn't go to 20.04 without also going to v31. I know terms like "not
> worked" / "didn't work" aren't that useful, but I remember in some cases I
> got something like "hardware does not support sending", in other cases it
> appeared successful, but there were no IR signals sent. Mostly I'm seeing
> if the new driver works for anyone else. And while I can do web searches,
> this audience is a good pool of folks that may have the answer ????
>
> So, is anyone successfully using the ir-kbd-i2c driver to do HD-PVR
> blasting?
>
> Thanks!
> --
>
> James Purl - *jamesp@mzrfzr.com <jamesp@mzrfzr.com>*
>
>

--

James Purl - *jamesp@mzrfzr.com <jamesp@mzrfzr.com>*