Timo Juhani Lindfors wrote:
Sebastian Krzyszkowiak <[email protected]> writes:
I think this issue isn't related to cpufreq - I have that on standard
andy-tracking kernel. And for me it happens always - I'm unable to use
GPS at all...
But for me this has never happened before. So even if cpufreq does not
cause it it will at least make it more probable to occur.
It must happen during transaction only because in the PRECHANGE part the
port remains
open. If it is not stable after transaction it can be an error on clock
calculation because
the error is more that x%
Michael
