Phoronix is of course not always on the mark, but their results seem to suggest there's a config issue in the Fedora kernel regarding the OMAP4460 core used in the Pandaboard ES - apparently cpufreq support is lacking, and consequently the CPU doesn't run at full speed. The benchmarks seem to confirm this.

On Thu, Jul 5, 2012 at 2:28 PM, Adam Williamson <awilliam(a)redhat.com&gt; wrote: > Phoronix is of course not always on the mark, but their results seem to > suggest there's a config issue in the Fedora kernel regarding the > OMAP4460 core used in the Pandaboard ES - apparently cpufreq support is > lacking, and consequently the CPU doesn't run at full speed. The > benchmarks seem to confirm this. I knew waiting a few weeks before installing F17 ARM on my PandaBoard ES was a wise idea... ;) GA code nowadays means "beta". Beta means "Alpha" and "Alpha" means "broken". ;-P

On Thu, Jul 5, 2012 at 2:59 PM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: > I don't see how Fedora 17 ARM on the pandaboard ES is broken Peter, Since you quote my e-mail, I feel the need to clarify... I wasn't speaking about F17/ARM, just making a broad generalization as to 'release' software being more like 'beta', as often there's several fixes released shortly thereafter, meaning that the 'beta' wasn't as wide as it should have been. It was a comment on the fast-paced nature of software development nowadays, rather than a criticism of F17/ARM. And second, when I used the word "broken" it was in reference to software branded "alpha". Please, re-read my message and you'll surely understand it now.