Mario is correct it only patched the userspace driver and not the kernel.
SnapStream Firefly need the kernel module to be loaded and it will not work on userspace.
I have done some testing with the SnapStream Firefly configs in ATI/NVidia X10 RF kernel and determine that the other remote configs seem to overides the Snapstream Firefly config so I strongly recommends that the SnapStream Firefly configs to be removed from the ATI/NVidia X10 RF alltogether and have it own selection with the same hardware.conf as the ATI/NVidia X10 RF (kernel) but with it own lirc.conf which I have attached to this earlier report.
Also I would like to submit a bug report on the ATI/Nivida X10 RF (userspace) selection when selected it create a string in the hardware.conf MODULES="none" which should actually be just MODULES="", it may not break anything but it will generate a warnings when lirc is started.
It is recommend to remove the text "none" to preventing lirc from generating any warnings when it is starts.
Mario is correct it only patched the userspace driver and not the kernel.
SnapStream Firefly need the kernel module to be loaded and it will not work on userspace.
I have done some testing with the SnapStream Firefly configs in ATI/NVidia X10 RF kernel and determine that the other remote configs seem to overides the Snapstream Firefly config so I strongly recommends that the SnapStream Firefly configs to be removed from the ATI/NVidia X10 RF alltogether and have it own selection with the same hardware.conf as the ATI/NVidia X10 RF (kernel) but with it own lirc.conf which I have attached to this earlier report.
Also I would like to submit a bug report on the ATI/Nivida X10 RF (userspace) selection when selected it create a string in the hardware.conf MODULES="none" which should actually be just MODULES="", it may not break anything but it will generate a warnings when lirc is started.
It is recommend to remove the text "none" to preventing lirc from generating any warnings when it is starts.
Bill