[Android General] gbl08ma:
The Cink Five is a French MTK 6589 (not T) phone. Specs identical to my ZP910 except for the screen (higher resolution). Also, on Wiko Mobile's website they claim it supports USB OTG, which would be interesting to implement on other MTK phones.

Now downloading the sources (let's hope the connection doesn't fail, and that I don't spend all of the quota for this month... sigh).

EDIT:

I am now compiling this kernel tree, which is the most complete I've ever seen. Funny thing, this one doesn't have the 89T part I mentioned on the OP.

Ideas from http://xdaforums.com/showpost.php?p=43861751&postcount=64 are proving to be useful when compiling this 6589 kernel (mainly the kalOidComplete errors thing).

Of course I'll never be able to get this kernel to boot on my Zopo, as I'd have to guess all of the kernel config including things like GPIOs... but getting a binary will at least be fun.

And in case you never looked into a Mediatek code tree, this thing is a horrible mess (something common to most OEMs and SoC manufacturers, anyway). And this is just the kernel... I don't even imagine how it would be if it also had the preloader, lk, etc. sources...

BTW, I just got a "**** Successfully built kernel ****" message, but then it says "Cannot open file /arch/arm/boot/zImage". Will have to investigate.

EDIT2: I managed to compile a kernel from the Cink Five source tree.

Interesting aspects:

This kernel source is more incomplete when it comes to CPU freq scaling than the one from the Acer Liquid E2 available on Github (and which is missing many of the scripts needed for compilation). For example, it doesn't know of any speeds above 1209 MHz. The source tree on GitHub is effectively more recent.

This kind of saddens me. It means that at some point, Mediatek wrote the code thinking the CPU wouldn't go over 1.2 GHz. Then they may have added the 89T-specific code later, only when they developed a physically different die that effectively allows for higher clocks. And so 6589 and 6589T may have more differences than just a kernel config.

You can see that new DVFS configurations were added to the source code at some point.

From mt_cpufreq.c @ Cink Five source tree (presumably before):

#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz

#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV

From mt_cpufreq.c @ Acer Liquid E2 source tree (presumably after):

#define DVFS_F0_0 (1703000) // KHz
#define DVFS_F0_1 (1599000) // KHz
#define DVFS_F0_2 (1508000) // KHz
#define DVFS_F0_3 (1404000) // KHz
#define DVFS_F0_4 (1300000) // KHz
#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz

#define DVFS_V0 (1250) // mV
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV

This is just a very small part of the differences between the two code trees.

But even if the 6589 can't overclock, the 6589T apparently support a speed of 1.7 GHz (DVFS_F0_0)... unless they added that just for testing purposes.