Open CraziFuzzy opened 8 years ago
jwittkoski
commented
8 years ago It's been a while, but I seem to remember using the LIRCTuner to talk to a non-USBUIRT LIRC device. I eventually switched to a different method (using GenericTunerPlugin) but that was more because LIRC tended to be someone unreliable in my situation than the LIRCTuner not working with LIRC itself.
CraziFuzzy
commented
8 years ago Yeah, I'm guess it's possible that with the right configuration files it could be made to work with other LIRC based blasters, especially UIRT2 based ones, but it does represent itself to sage as USB-UIRT Transceiver.
jwittkoski
commented
8 years ago True, but it appears to be talking to the lircd daemon (which can be configured to talk to the USB-UIRT device) and not the USB-UIRT directly.
CraziFuzzy
commented
8 years ago So, I contacted jrhees about this, and it turns out he does have a linux port of the uuirtdrv library that the windows sagetv uses. I'm now thinking the absolute cleanest method going forward might be to expand the current windows sage implementation to include the linux option as well - this should provide the same in-sage integration (learning blaster codes, etc) as the windows solution. I'm guessing his library is only x86, so I just asked him if there's a 64-bit version, or if source is available.
CraziFuzzy
commented
8 years ago @Narflex, did you write the current USB-UIRT implementation? or was that another member of the team?
Narflex
commented
8 years ago think John Rees actually wrote it himself and gave it to us which is why it's in the third_party directory (I know I contacted him before we open sourced it to get permission to include it).
On Wed, Oct 12, 2016 at 5:13 PM, Christopher Piper <notifications@github.com
wrote:
@Narflex https://github.com/Narflex, did you write the current USB-UIRT implementation? or was that another member of the team?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/sagetv/issues/192#issuecomment-253375662, or mute the thread https://github.com/notifications/unsubscribe-auth/ANEIDLWbuskSnbo1JTzq8y2FZrl-4i3Kks5qzXengaJpZM4KTiS1 .
Jeffrey Kardatzke jkardatzke@google.com Google, Inc.
With Sean's recent additions of LIRC to the docker, I am hoping to tackle cleaning up the USB-UIRT implementation in sage. I was actually quite surprised to fine that USB-UIRT support is already explicitly there, but it is in the - what I'd say poorly named - LIRCTuner.h; LIRCTuner.c files. Because there are other LIRC based devices I can see being implemented as well (HD-PVR for one), should this be renamed to USBUIRT.h; USBUIRT.c ? This would allow others to be added as we move forward without the confusion.
To be clear, LIRCTuner is not a generic LIRC interface, it does appear to be specific to the USB-UIRT Transciever, and reports as such to sage as its name.