|
From: Andrei T. <an...@un...> - 2007-05-04 19:45:45
|
If you are using lirc_serial then it's quite possible, even though I can't be sure since I couldn't reproduce your specific problem. On the other hand, my symptoms were similar to yours - after resume, the driver often would remain unresponsive fore a minute or two. Please try the patch and post your results. On Fri, 04 May 2007 14:09:54 -0400, David Frascone <da...@fr...> wrote: > Do you think the "going deaf" part could have been causing the several > minutes of blackout that a few people (me) have been seeing? > > -Dave > > Andrei Tanas wrote: >> The attached patch fixes two issues in lirc_serial >> 1. potential active level autodetection error (if there happens to be an > IR signal present at the moment when the driver is loading). The new code > takes 9 samples with 0.1s intervals and selects active high/low based on > the maximum number of "votes". >> 2. if 2 consecutive "pulse" interrupts occur with more than 15 seconds > interval, the driver would decide that "this MUST be a space" and flip the > "sense" bit (even if it wasn't in autodetection mode!), becoming "deaf". > Under normal conditions this (almost) never happened, with suspend/resume > working the problem became very obvious. The patch just deletes this piece > of code. >> >> Regards, >> Andrei. >> ------------------------------------------------------------------------ >> >> > ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ > > -- > > David Frascone > > Do not fumble with a woman's logic. |