Gyuri wrote:So long story short: if anyone knows how to make cpufreq working on this thing, please share

I didn't installed lib/modules into the rootfs... After doing it (& copied the kernel source too) cpufreq works.
Code: Select all
root@ix4-300d:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 1000 us.
hardware limits: 667 MHz - 1.33 GHz
available frequency steps: 667 MHz, 1.33 GHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 667 MHz and 1.33 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 667 MHz (asserted by call to hardware).
cpufreq stats: 667 MHz:99.04%, 1.33 GHz:0.96% (261)
analyzing CPU 1:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 1000 us.
hardware limits: 667 MHz - 1.33 GHz
available frequency steps: 667 MHz, 1.33 GHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 667 MHz and 1.33 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 667 MHz (asserted by call to hardware).
cpufreq stats: 667 MHz:99.32%, 1.33 GHz:0.68% (175)
As you can see it's already running on the minimum freq. (page84:
http://www.marvell.com/embedded-process ... 230_OS.PDF)
I tried using the "tuning" function of powertop, but it couldn't save me more power.
About WOL: I still don't want to do the job with WakeOnLan, and I'am afraid I couldn't do it anyway. It seems for me that there is no hardcoded mac address in the nic (is this even possible?), so I won't be able to address the magic packets.
Code: Select all
dmesg
[ 2.705049] mvneta d0070000.ethernet eth0: Using random mac address ae:c0:2c:0d:xx:xx
[ 2.712703] mvneta d0074000.ethernet eth1: Using random mac address 36:65:ec:ef:xx:xx
Code: Select all
ethtool -e eth0
Cannot get EEPROM data: Operation not supported
I must accept, that this board is eating 11W without load & hdds. And that's it
