Blacklist of locked Down Version´s of RK3188 CPU

[d33]

Blacklist of locked Down Version´s of RK3188 CPU

maybe this is because of CPU overclocking - when CPU is runing on full speed it cuts something somewhere to avoid from overheating ?!

There exists some reasonably complicated code to back off CPU frequency in an overheating scenario but the temperature sensor appears to be unused!


Using my ipad so apols for any stupid ios spelling 'corrections'

[neomode]

Here is a Little Program to check if the CPU is a T Model or not.
Please Test it.
Thx.

Neomode


Removed app not Work as Should, make a new one.

[d33]

Here is a Little Program to check if the CPU is a T Model or not.
Please Test it.
Thx.

Neomode


[ATTACH]5403[/ATTACH]

Oooh Oooh Oooh Prima! Neomode does this read the eFuse directly? If so can you amend this to read the leakage fuse too? That way we can get a real picture of how 'bad' the T chips are.

[digger]

Here is a Little Program to check if the CPU is a T Model or not.
Please Test it.
Thx.

Neomode


[ATTACH]5403[/ATTACH]

Hi neomode,
It is great!
But have just run it under 4.4.2 and it shows ...be real RK3188???
All the test were performed before allow me to to take 99% decision that I have "T".
You are giving me a chance

[neomode]

AW: Blacklist of locked Down Version´s of RK3188 CPU

as i say please test. what it does is a read out of dmesg.
May better i Go to check the efuse.
need more test input.

can you send me your dmesg?
please use this app to do it

https://play.google.com/store/apps/details?id=com.motioncoding.nova.logger

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2

[d33]

Blacklist of locked Down Version´s of RK3188 CPU

as i say please test. what it does is a read out of dmesg.
May better i Go to check the efuse.
need more test input.

can you send me your dmesg?
please use this app to do it

https://play.google.com/store/apps/details?id=com.motioncoding.nova.logger

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2

Aha - so can you do a little change to grab leakage level?


Using my ipad so apols for any stupid ios spelling 'corrections'

[digger]

can you send me your dmesg?
please use this app to do it

https://play.google.com/store/apps/details?id=com.motioncoding.nova.logger

Neomode

I have it alreay been done from my 4.2.2 stock FW but by traditional way.
Are you interested in these lines?
DVFS MSG: core: dfvs_adjust_table_lmtvolt get leakage_level = 2
DVFS MSG: aclk_gpu: dfvs_adjust_table_lmtvolt get leakage_level = 2

[d33]

I have it alreay been done from my 4.2.2 stock FW but by traditional way.
Are you interested in these lines?
DVFS MSG: core: dfvs_adjust_table_lmtvolt get leakage_level = 2
DVFS MSG: aclk_gpu: dfvs_adjust_table_lmtvolt get leakage_level = 2

You posted leakage level of 6000 yesterday???

<4>[ 0.735423] DVFS MSG: core: dvfs_adjust_table_lmtvolt get leakage_level = 6000

[valzja]

Re: Blacklist of locked Down Version´s of RK3188 CPU

You posted leakage level of 6000 yesterday???

That was on 4.4.2, tho....

Sent from my Nexus 5 using Tapatalk

[valzja]

I went back to neo 1.9a yesterday after no luck with overclocking, too....

Sent from my Nexus 5 using Tapatalk

[d33]

That was on 4.4.2, tho....

Sent from my Nexus 5 using Tapatalk

Aha! Very good You are paying attention

The kitkat code reads out the leakage_level and then calculates a leakage_value. Just to confuse us it then prints a message to DMESG saying "leakage_level" but using the leakage_value calculation!!

leakage_level = (efuse_buf[22] >> 4) & 0x0f;
if (leakage_level){
if (leakage_level <= 10)
leakage_val = 3000 * (leakage_level - 1);
else {
leakage_val = 30000 + 5000 * (leakage_level - 1 - 10);
}
if (efuse_version == 0x51){
leakage_val += 1000 * ((efuse_buf[23] & 0x3) + 1);
}
}

So that's clear then

[digger]

You posted leakage level of 6000 yesterday???

Yes, yesterday it was leakage level=6000 but with KitKat4.4.2
Today it is level=2 but with 4.2.2
My deduction: 6000(KitKat)=2(4.2.2).
But I'm not shure.

[d33]

Yes, yesterday it was leakage level=6000 but with KitKat4.4.2
Today it is level=2 but with 4.2.2
My deduction: 6000(KitKat)=2(4.2.2).
But I'm not shure.

Exactly from the code fragment above we can deduce that your fuse bytes for 22 & 23 are:

22 - 00101x11
23 - xxxxxx10

Giving a leakage 'level' of two and a 'value' of 6000

In addition the bolded bit dictates whether it is T processor (1) or a 'normal' one (0) and the underlined bits dictate whether to run the RAM at normal (00) or 'T' speed (not 00)

[edit - I type the logic the wrong way round at first - now fixed]

[norbert6]

AW: Blacklist of locked Down Version´s of RK3188 CPU

Hi neomode,
It is great!
But have just run it under 4.4.2 and it shows ...be real RK3188???
All the test were performed before allow me to to take 99% decision that I have "T".
You are giving me a chance

Same here, but d33 kernel change shows 3188t in the dmesg....

[digger]

Exactly from the code fragment abouve you can deduce that your fuse bytes for 22 & 23 are:

00100xxx
xxxxxx10

Giving a leakage 'level' of two and a 'value' of 6000 - the bolded bit dictates whether it is T processor (0) or a 'normal' one (1)

So as to confirm this we have to pull out content of efuse_buf[22] and efuse_buf[23].
But I have not enough skills, have you?
Edit: Sorry I've just remebered you don't have "T".
Explain me, please, how to do and I try if will be able with my "X"