on 29 Jul 10 at 17:41, Maxim Levitsky wrote:
>>> Note that I send timeout report with zero value.
>>> I don't think that this value is importaint.
>> This does not sound good. Of course the value is important to userspace
>> and 2 spaces in a row will break decoding.
> Could you explain exactly how timeout reports work?
It all should be documented in the interface description. Jarod probably
can point you where it can be found.
Timeout reports can only be generated by the hardware because only the
hardware can know the exact amount of time passed since the last pulse
when any kind of buffering is used by the hardware. You see this esp. with
> Lirc interface isn't set to stone, so how about a reasonable compromise.
> After reasonable long period of inactivity (200 ms for example), space
> is sent, and then next report starts with a pulse.
> So gaps between keypresses will be maximum of 200 ms, and as a bonus I
> could rip of the logic that deals with remembering the time?
For sure I will not agree to any constant introduced here. And I also
don't see why. Can you explain why you are trying to change the lirc