Closed GoogleCodeExporter closed 9 years ago
It works perfectly, the kernel just doesn't know that he is clocking lower than
he should. The reason for that is that the max rate is set right before the
clock will be set, hence the kernel already wrote 1566 (for example) into the
time-in-state-table. I could rewrite that, but this solution was throwing way
less work at me, which is why I just used it and didn't look back :p
Original comment by showp1984
on 29 Jul 2012 at 9:53
Original issue reported on code.google.com by
kon...@googlemail.com
on 28 Jul 2012 at 3:53