Comment 62 for bug 439163

hi

Thanks Dario for confirming that this works on the hvr1300.

Now we just need to see if this is also a solution for the hvr4000/3000.

Some further investigation as to the reason for this will now be
in progress. Further to the wild guess above about a timing
issue there may also be API difference in effect. The likely
reason that the demod was failing when reset is that the reset
flushed some cached state within the device. With the legacy
API the reset appeared to be not a problem since all data was
probably written at once but it is evident now that perhaps
only partial data is written when retuning with the S2API.

I will look into this. It could also be related to
where the advise_acquire method is invoked perhaps at
the wrong time, who knows.

This is all conjecture, but given here since if anyone who is
partial to investigate this has something to work on.

Cya!