Hi Sean, On Tue, Feb 23, 2021 at 05:50:01PM +0000, Sean Young wrote: > On Tue, Feb 23, 2021 at 05:13:07PM +0100, Matthias Reichl wrote: > > I could only test receiving (don't have a transmitter on that PC) > > and also couldn't test the carrier options (I'm using a demodulating > > TSOP receiver here), but your changes look sane to me. > > I only have got an eeepc box, with the same limitations. Do you happen to > know what hardware there is for this driver? It would be nice to test this > properly. > > This is the only IR driver that can change the RX carrier range, so it's > kinda interesting. In the most recent bug report I got (about a month ago) the user was using an intel NUC (NUC10i3FNH/NUC10i3FNB according to DMI): https://forum.libreelec.tv/thread/23211-intel-nightly-build-problem-with-mce-remote/?postID=148823#post148823 I've also seen NUCs with Nuvoton CIR though and I suspect they'll all probably have a demodulating receiver soldered directly to the board, so probably not easy to tinker with (haven't checked though). I have only an ancient Pentium 4 mainboard (Gigabyte 8IPE775) with an IT8712 here. IR RX/TX and CIR RX/TX are all exposed on a header, but the BIOS is somewhat odd and doesn't contain CIR on/off settings or announce the CIR via ACPI. So I had to manually patch ACPI tables to get that beast working.... ITE8713 pnpid was close enough (couldn't find a datasheet for 8713, only 8712 - that does mention demodulating though). I don't think I have a simple IR diode or transistor here to easily test that, only demodulating TSOPs (and some clones) - hooking that up to the mainboard wouldn't be too hard. so long, Hias
