Jump to content

Overclock


Recommended Posts

Posted
Oooops, the kernels I've put here yesterday contained a bug, I will deploy a replacement in some minutes.

Edit: they are here.

I used the command of "fastboot boot xxxx.img " to update the kernel. After reboot, the test result is same as before: Linpack: 3.8

Am i needed to re-install the setcpu after updating the kernel?

THX

Posted
Oooops, the kernels I've put here yesterday contained a bug, I will deploy a replacement in some minutes.

Edit: they are here.

I'm curious. What bug? :lol:

Posted (edited)
I'm curious. What bug? :lol:

Try pull down the status bar, or make a phone call with the yesterday ones, and you will see B))

An incorrect version of mdp_ppp.c was compiled into that kernel, I spent my yesterday with the video bug B)

(You see my very poor results in the BitBlt for Froyo topic)

Edited by gusthy
Posted
I used the command of "fastboot boot xxxx.img " to update the kernel. After reboot, the test result is same as before: Linpack: 3.8

Am i needed to re-install the setcpu after updating the kernel?

THX

"fastboot boot boot.img" sometimes boots the original kernel, so I recommend "fastboot flash boot boot.img. Yes, it overwrites your original boot.img, but it is easy to fix just in case.

Posted
Try pull down the status bar, or make a phone call with the yesterday ones, and you will see B))

An incorrect version of mdp_ppp.c was compiled into that kernel, I spent my yesterday with the video bug B)

Ah, wont affect me as I compiled my own kernel :lol:

Posted
Ah, wont affect me as I compiled my own kernel :lol:

Obviously B) but the guys here don't do that. BTW I tried the 0x27 multiplier and Pulse didnt blow up. Do you think it's worth to keep that value? (>0x27 didnt boot)

Guest martinmax
Posted

Guys i flashed the boot image for froyo that gushty posted it , but it is still 528 in setcpu , is there any trick that you do in setcpu ?

Posted
Obviously :lol: but the guys here don't do that. BTW I tried the 0x27 multiplier and Pulse didnt blow up. Do you think it's worth to keep that value? (>0x27 didnt boot)

I think anything more than 710MHz is really pushing things. 0x27 should be 748.8MHz which may work for a short time until the phone becomes too hot?

I spent a bit of time working the frequencies out:

0x20 32 614.4
0x21 33 633.6
0x22 34 652.8
0x23 35 672.0
0x24 36 691.2
0x25 37 710.4
0x26 38 729.6
0x27 39 748.8
0x28 40 768.0[/code]

I'm currently running with 0x24 691.2MHz and it's pretty stable. I'll have a chat with BoBo later about adding different frequencies to the code so SetCPU can work correctly.

ideally I want the kernel to operate at around 600MHz stock but the ability to overclock to a max of 748MHz if you use SetCPU. Will prevent any problems for noobs B)

Why 600? Well the speed increase from 528 to 600 is quite good really and it won't increase heat. Then we can look at the SanFrancisco phone "Oh you have a 600Mhz CPU? So do we. Haha" B)

The futures bright, the futures PULSE

Posted
Guys i flashed the boot image for froyo that gushty posted it , but it is still 528 in setcpu , is there any trick that you do in setcpu ?

That's right. For now the system shows the speed as 528MHz but it's actually higher. Eventually this will be fixed to show the true speed.

Guest martinmax
Posted (edited)
That's right. For now the system shows the speed as 528MHz but it's actually higher. Eventually this will be fixed to show the true speed.

And whats the method that you use to check the real speed ?

Edited by martinmax
Posted
Guys i flashed the boot image for froyo that gushty posted it , but it is still 528 in setcpu , is there any trick that you do in setcpu ?

No, it is fine, it should _look like_ 528 mhz, but it is 710, try Linpack to check it. If it is above 4, it works good.

Posted (edited)
No, it is fine, it should _look like_ 528 mhz, but it is 710, try Linpack to check it. If it is above 4, it works good.

Yeah thats the only way for now. The system declares the speed as 528MHz even though it's higher.

I'm going to spend several hours today fixing this :lol:

(yes.. the man who knows nothing about kernels is going to attempt to fix something.. god help me!)

Edited by flibblesan
Guest martinmax
Posted
No, it is fine, it should _look like_ 528 mhz, but it is 710, try Linpack to check it. If it is above 4, it works good.

Obviusly it doesnt work , linpack shows ~3

Posted
I think anything more than 710MHz is really pushing things. 0x27 should be 748.8MHz which may work for a short time until the phone becomes too hot?

I spent a bit of time working the frequencies out:

0x20 32 614.4

0x21 33 633.6

0x22 34 652.8

0x23 35 672.0

0x24 36 691.2

0x25 37 710.4

0x26 38 729.6

0x27 39 748.8

0x28 40 768.0

I'm currently running with 0x24 691.2MHz and it's pretty stable. I'll have a chat with BoBo later about adding different frequencies to the code so SetCPU can work correctly.

ideally I want the kernel to operate at around 600MHz stock but the ability to overclock to a max of 748MHz if you use SetCPU. Will prevent any problems for noobs :lol:

Why 600? Well the speed increase from 528 to 600 is quite good really and it won't increase heat. Then we can look at the SanFrancisco phone "Oh you have a 600Mhz CPU? So do we. Haha" B)

The futures bright, the futures PULSE

Yes, but to tell Galaxy Spica guys the same, we need 0x24 B) Btw, this 710 mhz kernel is a test one, of course we will need a mature version.

Our mate Kaffe told us how to do that - someone should implement that. I can write it in the evening, but until that I have to work.

(It takes around 15 minutes of coding - a long if-else if -else if is needed, plus the copypasting of the frequency table's last line).

Posted (edited)

linpack 4.844 thanks guys with flb 2.1 1.6b and jit

Edited by daco81
Posted
No , without Jit

If you are running Eclair then the Linpack score will be around 2.9 with the overclock kernel.

With Froyo and JIT you'll be getting Linpack score around 4.8 with the overclock kernel.

JIT improves things a lot, but it's very very unstable on Eclair.

Posted
Yeah thats the only way for now. The system declares the speed as 528MHz even though it's higher.

I'm going to spend several hours today fixing this :lol:

(yes.. the man who knows nothing about kernels is going to attempt to fix something.. god help me!)

Flibble, don't spend hours with that, do it fast B)

The mechanism is that in frequency table the first number is only a "label", the clock does nothing with that value. So you add as many lines with the same parameters as you want, only changing the first numbers. This numbers will show up in SetCPU.

Then in the clock div setting procedure there is an if() that contains that obvious 0x24, 25 constants. In the if there is a ">=528000" thing.

You duplicate that if(), and from the highest to the lowest you write the same values in the if's, as you wrote in freq table. and change them to "else if"s.

Finally in the ifs' body you set the appropriate divider values.

Guest martinmax
Posted (edited)
If you are running Eclair then the Linpack score will be around 2.9 with the overclock kernel.

With Froyo and JIT you'll be getting Linpack score around 4.8 with the overclock kernel.

JIT improves things a lot, but it's very very unstable on Eclair.

Can you send me a link about JIT activation on froyo ?

I enabled myself just changing the build.prop from fast to JIT

Edited by martinmax
Posted
Can you send me a link about JIT activation on froyo ?

It was talked about many times here in this forum.

Shortly, you change the line ending ":fast" in build.prop to ":jit" (or simply delete that line) and reboot.

Easiest way in terminal:

su

cd /system

sysrw

vi build.prop

when you are in vi:

/:fast

then it jumps to the proper line

you press d twice, it removes that line

then :wq

reboot

Posted
Flibble, don't spend hours with that, do it fast :lol:

The mechanism is that in frequency table the first number is only a "label", the clock does nothing with that value. So you add as many lines with the same parameters as you want, only changing the first numbers. This numbers will show up in SetCPU.

Then in the clock div setting procedure there is an if() that contains that obvious 0x24, 25 constants. In the if there is a ">=528000" thing.

You duplicate that if(), and from the highest to the lowest you write the same values in the if's, as you wrote in freq table. and change them to "else if"s.

Finally in the ifs' body you set the appropriate divider values.

So the part which, for me, says:

		if(hunt_s->a11clk_khz>=691200) {
a11_div=0;
writel(0x24, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}[/code] I just add duplicates of this for each speed I want to set and make sure the number matches the number in the table and the 0x24 is changed to the right code for the speed? Example:
[code] if(hunt_s->a11clk_khz>=576000) {
a11_div=0;
writel(0x18, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
if(hunt_s->a11clk_khz>=652800) {
a11_div=0;
writel(0x22, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
if(hunt_s->a11clk_khz>=672000) {
a11_div=0;
writel(0x23, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
if(hunt_s->a11clk_khz>=691200) {
a11_div=0;
writel(0x24, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
if(hunt_s->a11clk_khz>=710400) {
a11_div=0;
writel(0x25, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
with the table set to:
/* 7x01/7x25 normal with GSM capable modem */
static struct clkctl_acpu_speed pll0_245_pll1_768_pll2_1056[] = {
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 19200, 0, 0, 30720 },
{ 1, 122880, ACPU_PLL_0, 4, 1, 61440, 1, 3, 61440 },
{ 0, 128000, ACPU_PLL_1, 1, 5, 64000, 1, 3, 61440 },
{ 0, 176000, ACPU_PLL_2, 2, 5, 88000, 1, 3, 61440 },
{ 1, 245760, ACPU_PLL_0, 4, 0, 81920, 2, 4, 61440 },
{ 1, 256000, ACPU_PLL_1, 1, 2, 128000, 1, 5, 128000 },
{ 0, 352000, ACPU_PLL_2, 2, 2, 88000, 3, 5, 128000 },
{ 1, 384000, ACPU_PLL_1, 1, 1, 128000, 2, 6, 128000 },
{ 1, 528000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 128000 },
{ 1, 576000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },
{ 1, 652800, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },
{ 1, 672000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },
{ 1, 691200, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },
{ 1, 710400, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, {0, 0, 0}, {0, 0, 0} }
};[/code]

Guest Fusion0306
Posted
So the part which, for me, says:

		if(hunt_s->a11clk_khz>=691200) {

				a11_div=0;

				writel(0x24, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}
I just add duplicates of this for each speed I want to set and make sure the number matches the number in the table and the 0x24 is changed to the right code for the speed? Example:
		if(hunt_s->a11clk_khz>=576000) {

				a11_div=0;

				writel(0x18, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}

		if(hunt_s->a11clk_khz>=652800) {

				a11_div=0;

				writel(0x22, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}

		if(hunt_s->a11clk_khz>=672000) {

				a11_div=0;

				writel(0x23, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}

		if(hunt_s->a11clk_khz>=691200) {

				a11_div=0;

				writel(0x24, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}

		if(hunt_s->a11clk_khz>=710400) {

				a11_div=0;

				writel(0x25, MSM_CLK_CTL_BASE+0x33C);

				udelay(50);

		}
with the table set to:
/* 7x01/7x25 normal with GSM capable modem */

static struct clkctl_acpu_speed pll0_245_pll1_768_pll2_1056[] = {

	{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 19200, 0, 0, 30720 },

	{ 1, 122880, ACPU_PLL_0, 4, 1,  61440, 1, 3,  61440 },

	{ 0, 128000, ACPU_PLL_1, 1, 5,  64000, 1, 3,  61440 },

	{ 0, 176000, ACPU_PLL_2, 2, 5,  88000, 1, 3,  61440 },

	{ 1, 245760, ACPU_PLL_0, 4, 0,  81920, 2, 4,  61440 },

	{ 1, 256000, ACPU_PLL_1, 1, 2, 128000, 1, 5, 128000 },

	{ 0, 352000, ACPU_PLL_2, 2, 2,  88000, 3, 5, 128000 },

	{ 1, 384000, ACPU_PLL_1, 1, 1, 128000, 2, 6, 128000 },

	{ 1, 528000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 128000 },

	{ 1, 576000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 }, 

	{ 1, 652800, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 }, 

	{ 1, 672000, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 }, 

	{ 1, 691200, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },

	{ 1, 710400, ACPU_PLL_2, 2, 1, 132000, 3, 7, 122880 },  

	{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, {0, 0, 0}, {0, 0, 0} }

};

Go, Flibb! :lol:

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.