Details
Describe the solution you'd like:
Ideally I'd like to move away from using LIRC - patched or unpatched - due to it's uncertain future. As per the discussion in pikvm/pikvm#291 it seems like we can capture raw codes from ir-ctl and implement them as essentially raw TX.
In agile terms this could be viewed as a SPIKE, but may transform over the issue's lifetime.
Anything else you would like to add:
I've repurposed GPIO 19 as TX, and GPIO 16 as RX for the time being.
Some prelim testing indicates that this should be possible, but the config files are not nearly as user-friendly as the LIRC-based configs. I'd be happy to make that sacrifice so that the project can be on more stable ground instead of depending on 3 year old software.
Additional Information:
This may wind up encompassing #4 as well
Details
Describe the solution you'd like:
Ideally I'd like to move away from using LIRC - patched or unpatched - due to it's uncertain future. As per the discussion in pikvm/pikvm#291 it seems like we can capture raw codes from
ir-ctland implement them as essentially raw TX.In agile terms this could be viewed as a SPIKE, but may transform over the issue's lifetime.
Anything else you would like to add:
I've repurposed GPIO 19 as TX, and GPIO 16 as RX for the time being.
Some prelim testing indicates that this should be possible, but the config files are not nearly as user-friendly as the LIRC-based configs. I'd be happy to make that sacrifice so that the project can be on more stable ground instead of depending on 3 year old software.
Additional Information:
This may wind up encompassing #4 as well