From: <li...@ba...> - 2010-01-21 07:42:45
|
Hi! Andy Salnikov "a_s...@ya..." wrote: > <lirc@ba...> wrote: >> lircd decodes the signals just fine. >> This seems to be a problem with scheduling latency on you new system > (new >> kernel I guess?). The gap value is very low and lircd probably times out >> waiting for the data. >> >> As a work-around, just increase the gap value to something around 100000 >> or 200000. This should fix it, but you won't be able to use this config >> for transmit anymore. > thanks for suggestion. I tried to increase the gap value and it changed the > situation but did not fix it completely. If I set gap to a big number > like 50000, > 100000, or 200000 I do not see the second event from lircd any more. But > it also kills repeat, if I hold a button pressed I do not see anything > in irw until I release the button and then a single even is produced. You can also specify a gap range like this in 0.8.6: gap 12257 200000 That should work. Christoph |