critor wrote:196MHz is the highest safe optimal value. Higher frequencies aren't that interesting because :
- a AHB slightly higher than 66MHz is likely to silently but progressively corrupt your NAND data
- and if you lower the AHB, it will be much lower than 66MHz and thus impact the NAND performances
Also, I've already seen some (rare) CX calculators being unreliable at more than 210MHz.
So hard-coding a value much higher than 196MHz in ControlX is dangerous.
Wow. I was considering tweaking Nover's auto-configuration to see if I could make my calculator go a little faster, but now I think I'll just leave it as it is...
critor wrote:But note that if you have Ndless + Nover set up, you'll calculator will still be overclocked from 196MHz to the highest safe value detected/set in Nover once the OS is launched.
I do have Nover set up already; I was just wondering if there was any way to apply Nover's values before the OS loads. Though, I guess there wouldn't be much of a point.
Thanks for answering my questions.