> "greg.mythtv@..." wrote:
>>> I don't know the hardware well enough, but this seems to be a hardware
>>> bug. You can make a work-around in lirc (hw_hiddev.c) or preferably at
>>> kernel level to ignore repeated commands if the time since the last
>>> event was too long.
>> I will see what I can do to implement a workaround, but I'm not very
>> familiar with the software architecture of lirc, so it may take a while,
>> and it will probably be easier for me to do it in lircd (hw_hiddev.c)
>> rather than at the kernel level.
> It might be easier to do it in lircd but the kernel level is the right
> place to do it because then everybody would benefit from the fix.
> I'm sure that the according kernel developer will be able to help you
> resolving this issue.
You really think the kernel level is the right place?
In order for the kernel to determine whether
to discard input from the device, it would have to decode the
data stream, work out the remote code framing, determine
if the repeat bit is set in one of the "codes" that is received,
and remember if the last code was received recently. To me
all of this intimate knowledge of the remote protocol seems
to lie firmly in the realm of lircd. I could be wrong. Please
set me straight if I am.