Once again i will explain:
Imagine the clock speeds at 1000,800 on a specific model.
When you do the commands:
cat /proc/cpuinfo
nvram get clkfreq
openssl speed aes-128-cbc
You will see the results from 1000,800 clock speeds.
If you revert to a accepted clock (lets say 1200,800) or a not accepted one (lets say 2000,1000) will always after rebooting show you on nvram get clkfreq que stock/default value, in this case 1000,800, the difference is:
If a accepted clock you will see "cat /proc/cpuinfo" BOGOMIPS value change, and also the OPENSSL benchmark results.
If not accepted clock, it will keep the original values on "cat /proc/cpuinfo" BOGOMIPS and OPENSSL benchmark results.
nvram get clkfreq will ALWAYS show you the SAME original/stock/default speeds.
That was my conclusion, but i will need to check it further later today, i can be wrong.
Imagine the clock speeds at 1000,800 on a specific model.
When you do the commands:
cat /proc/cpuinfo
nvram get clkfreq
openssl speed aes-128-cbc
You will see the results from 1000,800 clock speeds.
If you revert to a accepted clock (lets say 1200,800) or a not accepted one (lets say 2000,1000) will always after rebooting show you on nvram get clkfreq que stock/default value, in this case 1000,800, the difference is:
If a accepted clock you will see "cat /proc/cpuinfo" BOGOMIPS value change, and also the OPENSSL benchmark results.
If not accepted clock, it will keep the original values on "cat /proc/cpuinfo" BOGOMIPS and OPENSSL benchmark results.
nvram get clkfreq will ALWAYS show you the SAME original/stock/default speeds.
That was my conclusion, but i will need to check it further later today, i can be wrong.