On Thu, 2010-07-29 at 09:23 +0200, Christoph Bartelmus wrote: > Hi Maxim, > > on 29 Jul 10 at 02:40, Maxim Levitsky wrote: > [...] > > In addition to comments, I changed helper function that processes samples > > so it sends last space as soon as timeout is reached. > > This breaks somewhat lirc, because now it gets 2 spaces in row. > > However, if it uses timeout reports (which are now fully supported) > > it will get such report in middle. > > > > 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. > > Christoph Could you explain exactly how timeout reports work? 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? Best regards, Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
