Robert Nelsons kernel is crippeling my Beaglebone CPU ? ;)))

Hi,

beside other places here:
http://beagleboard.org/bone

is said that the CPU of a Beaglebone is run with 720MHz max.
when powered via 5Volts power plug instead of USB power.

But...

When I do a

    cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

it says that it runs with

    600MHz max.

while my beaglebone is powered via power plug (not USB).

I checked this and put the Beaglebone under 100% load and
it runs with 600MHz.

Where can I get the remaining 120MHz back?

Thank you very much in advance for any help!

Best regards,
mcc

Hi,

beside other places here:
http://beagleboard.org/bone

is said that the CPU of a Beaglebone is run with 720MHz max.
when powered via 5Volts power plug instead of USB power.

But...

When I do a

    cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

it says that it runs with

    600MHz max.

while my beaglebone is powered via power plug (not USB).

I checked this and put the Beaglebone under 100% load and
it runs with 600MHz.

You say "crippeling" i say fixes for bugs users were seeing a few
months back... So i guess we disagree..

Where can I get the remaining 120MHz back?

Disable this patch:
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.2/patch.sh#L185

Regards,

Robert Nelson <robertcnelson@gmail.com> [12-10-03 14:12]:

> Hi,
>
> beside other places here:
> http://beagleboard.org/bone
>
> is said that the CPU of a Beaglebone is run with 720MHz max.
> when powered via 5Volts power plug instead of USB power.
>
> But...
>
> When I do a
>
> cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
>
> it says that it runs with
>
> 600MHz max.
>
> while my beaglebone is powered via power plug (not USB).
>
> I checked this and put the Beaglebone under 100% load and
> it runs with 600MHz.

You say "crippeling" i say fixes for bugs users were seeing a few
months back... So i guess we disagree..

> Where can I get the remaining 120MHz back?

Disable this patch:
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.2/patch.sh#L185

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--

Hi Robert,

thank you for your reply! :slight_smile:

Sorry Robert, if my choice of words may have sound bad, negative or
like a critism. Nothing of that was meant. I am no native english
so sometimes words go wrong.

What kind of bugs were seen? On what I have to keep my eyes on? Is it
"dangerous" in any respect to remove the patch from being applied?

Thank you very much for your help in advance!

Best regards,
mcc

Honestly the bug was occurring back in May, and there's been a lot of
changes since then.. It only manifested itself on bootup, so if you
disable the patch and your board makes it to the login prompt then
it's perfectly fine.. :wink:

Regards,

Robert Nelson <robertcnelson@gmail.com> [12-10-03 15:08]:

It seems Robert did disable the OPP_TURBO patch on his latest git :slight_smile: so now it should boot on 720 by default on 5V external.

3.2.31-psp24 is what I compiled today and noted the change. I’m trying to squash a bug that is puzzling me. I need to make a “ifconfig eth0 down” on /etc/network/if-pre-up in order to CPSW to work with the latest wheezy ARMHF (basically Robert’s Wheezy image plus apt-get upgrade)

It is solved somewhere since changing to Angstrom image does work and I’ve tried ifplugd and connman on Debian Wheezy. Weird :slight_smile: