rpgAmazon | # 2521 | 2010-04-12, 21:00 | Report

So hard to choose!
Today with ideal kernel, max frec=950... 2 batteries at work (8 am unplugged from car, 2:30 battery change, 7 pm plugged again)
With Lehto 125-950-500, a day without change of battery.
I can assume than user habits are delimiting battery life, anyway, nv kernel beating xlv... how is it possible? If 500 xlv=125 nv, and Lehto 950 ov> ideal 950 ov... ¿?¿?¿?¿
So again reinstaling 125-950-500... I'm getting crazy!!

gabby131 | # 2522 | 2010-04-12, 21:03 | Report

LOL!! just toss coins or roll a dice,

i chose Lehto's because that was the first kernel i got from searching about OC.

let's say first to come is to be served....

titan | # 2523 | 2010-04-12, 21:03 | Report

BTW, there is cpufrequtils in extras-devel.
it contains cpufreq-info to summarize all info.

titan | # 2524 | 2010-04-12, 21:09 | Report

I'm not so sure whether you actually need it for booting.
only some poorly designed parts in Maemo5 use it instead of the more reliable `uname -r` approach.

nokian-series | # 2525 | 2010-04-12, 21:10 | Report

If i remove items it wil desapear? lol
Anyway to workarround this?
Seems strange but i dont like to see duplicated folders

help?

arbitrabbit | # 2526 | 2010-04-12, 21:23 | Report

Here are my stats for the ideal kernel by the way

Current frequency: 500 MHz

Minimum frequency: 500 MHz

Maximum frequency: 810 MHz

FREQUENCY USED
1200 MHz 0
1100 MHz 0
1000 MHz 0
950 MHz 0
900 MHz 0
850 MHz 0
810 MHz 0.000 %
750 MHz 0.000 %
700 MHz 0.000 %
600 MHz 0.000 %
550 MHz 0.000 %
500 MHz 0.010 %

The rest of the time i.e. 99.99%, the CPU is idle (though I have clubbed all the idle states together)

EDIT: Have updated the numbers

---

Last edited by arbitrabbit; 2010-04-12 at 22:50. Reason: Calculations were screwed due to signed integer overflow

Matan | # 2527 | 2010-04-12, 21:24 | Report

Allowing user space to change the vsel column of the mpu table is trivial. It also sounds better to me than having predefined tables in the kernel. The user space program can have those tables. This patch should do the trick:

http://my.arava.co.il/~matan/770/n900/vsel.diff

Disabling specific frequencies might not be as easy. I think that the easiest way is to add a scaling_allowed_frequencies to generic cpufreq code, rather than hacking ARM specific code.

UNderworld | # 2528 | 2010-04-12, 21:31 | Report

managed to get the xlv on... no problems so far..

I got it to 1ghz temp.. I notice cpu goes either 500mhz or 1000mhz, it does not do 850 (default max) anymore...

also, does it only use 500 and 850 frequencies??

what I understand is, 1ghz uses same voltage that 600mhz stock uses.. ?? right??

titan any possibility to throw 500dsp in?? I dont see dsp mentionned in any of your kernels

geneven | # 2529 | 2010-04-12, 21:32 | Report

This has nothing to do with this thread.

The easiest workaround is to wait for the fix.

There is nothing to worry about.

Move items and the problem will go away.

noobmonkey | # 2530 | 2010-04-12, 21:35 | Report

I would very much agree with geneven.....

Please just use the search feature, it is there for a reason........ Tadaaaaaa - thread found!