I'm not sure who you're replying to, but I'll try to answer.UnaClocker wrote:I'm having a hard time understanding the overvolting settings. Where did you get the -16,8? Why are you going from a single 1.2v to a .8v and 1.6v? Does it run .8v at idle and 1.6v under load after this change? Wouldn't I simply change the 1.2v to 1.6v? What's the command for that? -16?
Hi Dom,dom wrote:Overclocking.
It is the intention that most users stick with the default clock frequencies. That will give you the longest lifetime of the chip, and the most reliability.
If however you don't mind risking a little stability and chip lifetime, you can tinker with these, and get a little more performance.
Just overclocking (without overvoltaging) is unlikely to have a significant impact on chip lifetime. What you will find, is when you set it too high, you will see random crashes (probably kernel panics).
I would expect that there is a good chance 800MHz will be reliable, and you may be fine with 900MHz. This is assuming room temperature. At extreme temperatures (especially hot) you may have less success. Please note, this is my personal experience from a small number of chip batches - only 700MHz is guaranteed.
Now you can only go higher when you also over voltage. This is when it gets a little riskier. This does have a measurable impact on chip lifespan. Because of this, we will officially recommend you do not do this. Treat this as a voiding warranty situation. We wil blow an OTP (one-time-programmable) bit if you use the over_voltage_* settings, so we will know.
With over_voltage set to 6 (1.35V) I've been running at 1GHz for much of the last couple of months with no noticable problems. Brief tests have been successful at 1.15GHz. I may have voided my warranty however...
over_voltage applies to both the ARM and GPU. Brief tests running the GPU at 500MHz were successful for me. Even if the GPU is not providing any acceleration, you do get a small performance boost for the ARM when core_freq is higher, as the ARM has to cross the core_freq domain to get to SDRAM (or L2). This probably is more noticable when L2 is enabled.
I have not experimented too much with SDRAM overclocking. I would expect 500MHz to be achievable.