Re: girs driver issues

>
>
> Which one was incorrectly received? More importantly, did in solve the
> problem with the Samsung signals?
>
> I had to bump up DEFAULT_RECEIVE_ENDINGTIMEOUT in the GirsLite firmware
to 40 in order to not receive a truncated signal from my Samsung remote.
In testing, I found that it was important to ensure the receive window was
big enough to receive a signal without being big enough to receive two
valid signal worth of a remote keypress within the same receive sequence
(ie within one iteration of readline in the girs.c driver).  When I get two
valid receives in the same single receive window, the issue with a key
repeat showing up 10 seconds later occurs.

With this value at 40, everything seems to work acceptably well for routine
use. Hopefully I don't have to tune this value individually for the remotes
in use with the system.  We'll see after I move this down to my home
theater PC.

Thanks,
Tim