Closed GoogleCodeExporter closed 9 years ago
yes, cpu1 will be reset back to default.
All of that is long and detailed explained in the changelog for 0.5.
That is not the kernels fault, mpdecision & thermald are resetting this.
Previous to 0.5 cpu1 would have been ramped up to max clock (1944Mhz) but I
hacked the kernel for 0.5 to trick mpdecision & thermald into believing that we
are only capable of 1566 Mhz. That's why they now reset cpu1 to the default
clock.
Not a bug, more like a feature.
Original comment by showp1984
on 24 Mar 2012 at 3:15
Original issue reported on code.google.com by
kwci...@gmail.com
on 24 Mar 2012 at 3:11