[Gta04-owner] Fwd: [beagleboard] 1ghz news?

[Dr. H. Nikolaus Schaller]

Am 24.07.2013 um 15:57 schrieb Dr. H. Nikolaus Schaller:

> may be of interest for you:
> 
> again some progress on 1 GHz kernels (except for USB stability).

And someone has written a blog about this 1 GHz DM3730CBP100 issue:

http://teknoman117.wordpress.com/2013/07/24/beagleboard-xm-1-ghz-operation-safely-and-reliably/

One statement is very important for us as well and it shows how dramatic the situation is with newer kernels (and we did not really notice since all devices were tested with the 2.6.32 hw-validation kernel):

"the last time it was safe was kernel 3.0.28 back in early 2012"

So we should also work on:

http://projects.goldelico.com/p/gta04-kernel/issues/440/

> 
> 
> Anfang der weitergeleiteten E-Mail:
> 
>> Von: Robert Nelson <robertcnelson at gmail.com>
>> Datum: 24. Juli 2013 15:51:56 MESZ
>> An: beagleboard at googlegroups.com
>> Betreff: Re: [beagleboard] 1ghz news?
>> Antwort an: beagleboard at googlegroups.com
>> 
>> On Wed, Jul 24, 2013 at 6:41 AM, Robert Nelson <robertcnelson at gmail.com> wrote:
>>> On Wed, Jul 24, 2013 at 6:09 AM, Nathaniel Lewis
>>> <linux.robotdude at gmail.com> wrote:
>>>> Okay everybody, I've put together a fork of RobertCNelson's
>>>> armv7-multiplatform that adds the necessary driver and modifications to
>>>> allow the Beagleboard xM to run safely at 1 GHz using TI's new adaptive body
>>>> bias driver in the 3.11-rc2 linux kernel.  I'll put together a blog post
>>>> tomorrow, err later, I've been up for 30 hours getting this working.  USB
>>>> works, however the sprz319 erratum has to be ported to 3.11, meaning usb on
>>>> the xM is unstable and most likely will cutout within 15 minutes.  Enjoy!
>>>> https://github.com/Teknoman117/beagleboardxm-kernel
>>> 
>>> Sweet, thanks for working on this Nathaniel!
>>> 
>>> I just pulled the merge, I'm going to test it a few older xM's i have here too..
>>> 
>>> So for device trees in v3.11-rcX (ignoring the expansion boards, i
>>> want to use the 3.8/bone capemgr/dtbos for that) we still need video
>>> working and a easy to enable sprz319 workaround to be feature
>>> identical with the old beagle board file..
>> 
>> Honest, for how long we've come... This just seems really cool. ;)
>> 
>> debian at arm:~$ cpufreq-info
>> cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
>> Report errors and bugs to cpufreq at vger.kernel.org, please.
>> analyzing CPU 0:
>> driver: generic_cpu0
>> CPUs which run at the same hardware frequency: 0
>> CPUs which need to have their frequency coordinated by software: 0
>> maximum transition latency: 300 us.
>> hardware limits: 300 MHz - 1000 MHz
>> available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz
>> available cpufreq governors: conservative, ondemand, userspace,
>> powersave, performance
>> current policy: frequency should be within 300 MHz and 1000 MHz.
>>                 The governor "ondemand" may decide which speed to use
>>                 within this range.
>> current CPU frequency is 300 MHz.
>> cpufreq stats: 300 MHz:43.52%, 600 MHz:2.20%, 800 MHz:0.00%, 1000
>> MHz:54.28%  (3)
>> 
>> Regards,
>> 
>> -- 
>> Robert Nelson
>> http://www.rcn-ee.com/
>> 
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> 
> 
> _______________________________________________
> Gta04-owner mailing list
> Gta04-owner at goldelico.com
> http://lists.goldelico.com/mailman/listinfo/gta04-owner