I was looking at the mt_cpufreq.c file in the leaked kernel source for the MTK 6589 SoC (the one running at 1.2 GHz), at https://github.com/varunchitre15/MT...atek/platform/mt6589/kernel/core/mt_cpufreq.c
I noticed there were frequency settings above 1209 MHz defined there. The highest one, DVFS_F0_0 goes above 1.7 GHz.
The code that seems to define the maximum frequency starts on line 1573 of that file. It relies on the returned value of PTP_get_ptp_level to define it. Since PTP_get_ptp_level is just a external header on that file, I needed to search the git repo to find its definition. Turns out it is in this file mt_ptp.c. Pay special attention to line 1018 and below: https://github.com/varunchitre15/MT...ek/platform/mt6589/kernel/core/mt_ptp.c#L1018
There's this interesting bit:
Code:
#if defined(MTK_FORCE_CPU_89T)
return 3; // 1.5GHz
#else
By returning 3, this function tells the frequency scaling driver that the CPU can go up to a 1.5 GHz clock.
I think I read the 6589T also has a higher GPU clock, and it can handle 2 GB of RAM with no problems. I'm not saying that the difference between the 6589 and the 6589T is just a kernel config, in fact, the chip most likely got a new revision. This source code leaked before there was any talk of a turbo revision of the 6589, so I think it's safe to assume that on newer code trees there may be fixes for the 2 GB of RAM and a higher GPU clock.
But I wonder, if the 6589 (not T) is able to go up to 1.5 GHz or even 1.7 GHz. It would be good if someone could compile that kernel with some modifications to make it think it will be running on a 6589T (adding a #define MTK_FORCE_CPU_89T should be enough) and see if it works fine. Since that source code came from a Acer model, maybe it would be easier to start tests on that device (because we can be sure the source is 100% compatible). I think it may run, but it may heat a lot or it may drive the voltage of the CPU up to a point where the phone's PCB is not prepared to deliver, causing damage (maybe the T revision chip fixes this).
have you done any more digging or testing on this?
Just noticed that Jiayu have released a MTK6589T version of the G3S for only $5 extra - could it be just a simple software unlock?
thanks
My guess is that it really is only a kernel setting considering that the Jiayu G3S comes with both chips within 2 weeks. Besides this is a really easy way for mediatek to sell a wide range of SoC's (just varying the voltages/clockspeeds). The main thing I wonder if this also controls the clockspeed of the GPU, since that clock is different as well, considering the MKT6589 and MKT6589T.
http://www.ini3e.com/thread-2610-1-1.html
This chinese article confirms that the only difference is clock speed.
It would be really good if someone who can already compile custom kernels for any MT6589 phone, could make that little modification and check the results - worst case scenario, the chip would get too hot and break forever... but since it seems to have a lot of temperature monitoring in place, I don't think that would happen.
I could do it myself, but I'm not going to download 8 GB of Android source, on my limited home connection, just to apply the MT6589 patches available on GitHub, which probably wouldn't work out-of-the-box since they are for a Acer phone and mine's a Zopo 910.
Bothering people at Zopo to do it is out of question, since they are interested in selling the Zopo C2 which comes with this "turbo" kernel config.
As for the GPU clock, on this kernel source there doesn't seem to be anything controlling that based on the MTK_FORCE_CPU_89T define. But this may be just because this is an old source tree - the one they have been distributing for their clients more recently, for the 6589T, may already have the changes for the GPU clock.
The ideal situation would be to have a kernel which can allow all the possible CPU and GPU frequencies, and these would be controlled and limited on the userspace.
It would be awesome ! Please devs, do something for us
is there anyone working on this
kartikoli said:
is there anyone working on this
Click to expand...
Click to collapse
I looked at it shortly, and noticed a lot of stuff is missing to compile it.
But why not look at it yourself?
Start by git cloning the cm10.1 tree and compile for a device that is supported, to get an idea of how it works.
People who manage to compile the source, please post, because from there we can come close to building CM10.1.
The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10
gbl08ma said:
The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10
Click to expand...
Click to collapse
this group is working on a Cyanogenmod for mtk6589 devices...http://forum.xda-developers.com/showthread.php?p=41345830
http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.
gowtham121 said:
http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.
Click to expand...
Click to collapse
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://forum.xda-developers.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):
Code:
#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):
Code:
#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.
All we now need is someone with a Cink Five to join this forum...Hopefully someone will be willing to test your kernel..
Anyone out there with a Cink Five???
Apparently the Cink Five is targeted at the French market, so probably one will have better luck asking in a French Android forum.
Any French speakers here?
Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !
frans0023 said:
Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !
Click to expand...
Click to collapse
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.
gbl08ma said:
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.
Click to expand...
Click to collapse
No problem for me, send me the file and I will give a try. Just tell me what I have to check, maybe you want the logcat ?
Only boot.img is written when you flash a kernel ?
If it's only that, I could boot on recovery (twrp) and backup the file with "adb pull", then push yours ?
I have to sleep, good night
Envoyé depuis mon CINK FIVE avec Tapatalk
Actually, boot.img is the name of the file on the computer, to be updated with SP Flash tools. I don't know if Wink ever released an update to be flashed this way (but since you have TWRP, probably you have used it).
On the phone (or with recovery), I know a kernel can be flashed with a update.zip.
Right now I don't even know how to create a boot.img file, I only have the zImage. I'm trying to get a way to repack my boot.img so that I can try it on my Zopo...
And then I'll have to solve the problem of the kernel modules (these may be harder to restore since they are in the system partition I think)...
Also:
Is it just me, or the Cink Five is the same as the Fly IQ451? Turns out the zImage I compiled was with the config for the s9201b board, which is the IQ451.
From the pictures of the case, it seems to be the same... but, with Chinese phones, the case means little.
The source tree came configured to use the tinno89_jb config but I changed it because I couldn't compile with it.
Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)
gowtham121 said:
Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)
Click to expand...
Click to collapse
I think you guys still haven't understood very well that my kernel most likely won't even get to the Android boot logo (I bet it will stop in the early kernel boot stages with some kernel panic).
Furthermore I need a boot.img for the Cink Five so I can put my zImage in there. Otherwise it will never be compatible.
Also, I think the build type is set on the Android building process. I can only build a kernel. I don't have a good enough internet connection to download the Android source, and my computer with 8 GB of RAM lacks the necessary 16 GB (!!!) for compiling.
Related
Many people want to run a working froyo on their devices.
This won't be possible in a clean way without compiling a new kernel.
To archive this goal, we need to merge the Huawei specific device drivers (which are for 2.6.29) into a new kernel tree, the 2.6.32.9 one (or even 2.6.35 but 2.6.32.9 comes first since it is stable and thus important to us).
I did some research and preliminary work which I will explain here:
- The base kernel Huawei started with is available here (gitweb) - also check their wiki.
- Huawei started with the Q8650BSDCANLYA324020 tag on the donut_glazed branch (see instructions at the end of the post)
- Huawei has written it's own board driver (note they have used a Q8650 kernel release not a MSM7x25 one, most likely because this board driver is a little older and was not available for the version they wanted)
- After they were finished writing their drivers they released the kernel source (as you can download it from Huawei)
I have checked out the Q8650BSDCANLYA324020 base kernel version and diffed it against the kernel release of Huawei, generated a patch file (and stripped out the DOS linebreaks wtf) which can be applied to the base kernel.
Applying this patch to a more recent kernel (2.6.32.9) is not possible without merging the code into the new kernel tree (and since I'm not a programmer I can't do it - this is were your help is needed).
The other question is in which kernel tree we can port the patch I have extracted. I think we can use Q8650BSDCANLYA504005 on the froyo_almond branch since Huawei used an older version of it. Merging it into the AOSP msm-2.6.32.9 tree may be possible too (but the code aurora msm kernel is an improved AOSP version, so I guess we want that one).
My patch (and some non-pulse-mini fixup patch) alongside with a freshly extracted and fixed .config for the U8120 can be found at http://nico.core.ws/misc/huawei_kernel_u8100_8110_8120/
To port the source you need to checkout the original source (Q8650BSDCANLYA324020), create a new branch in which you apply the Huawei patch, then checkout the froyo kernel (Q8650BSDCANLYA504005) and merge your branch containing the changes from the patch into it.
Another way may be porting the froyo kernel tree back to the eclair one with Huawei patches.
Please post any results/questions/etc. here!
If we should get this working we can also enable the GPU driver (Adreno 200) as requested by many people (and much more (CyanogenMOD anyone? )).
Appendix:
Instructions on how to get the original source:
$ git clone git://codeaurora.org/kernel/msm.git
$ git checkout Q8650BSDCANLYA324020
Instructions on how to apply the patch (assuming "msm" is the kernel tree):
$ cp diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff msm/
$ cd msm/
$ patch -p1 < diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff
If you are compiling for U8100 or U8120 phones, you need to apply another
patch which fixes sensors (otherwise your phone won't be able to read battery
level and stuff):
$ cp needed_fixes_for_non_u8110_devices.diff msm/
$ cd msm/
$ patch -p1 < needed_fixes_for_non_u8110_devices.diff
Note that the above instructions will get you nothing new, only the kernel already running on your device.
This thread is about porting the Huawei patch to a froyo kernel.
Very nice! Thank you for this topic!
I hope this will be successfull
Are the Atheros sources included aswell?
[GER]Roxxor said:
Are the Atheros sources included aswell?
Click to expand...
Click to collapse
To be honest, I don't know. They should be in there though (maybe under a more generic driver name or integrated in the board driver) otherwise Huawei would have violated the GPL.
The problems with the fixes:
wifi
They got almost wifi working in other post
radio
FM radio too with an 3rd party app
dpad
dpad crash in this post too 2 pages back just disable this
screen calibration
calibration fix can meaby be fixed with HTC calibrate??(its an calibration app)
sound
I solve the sound problem with my phone is to replace the libaudio.so from 2.1rom,maybe you can try.\
cedric123 said:
here is an source for the adreno drivers.
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
Click to expand...
Click to collapse
Basically this is the complete kernel source for froyo without Huawei patches (it's the wrong tag too).
When we have ported the drivers we easily can enable that driver.
cedric123 said:
the froyo kernel source: http://www.huaweidevice.com/tcpsdow...&attachmentName=kernel-2.6.32-U8150-Froyo.zip
Click to expand...
Click to collapse
Thats the source for the U8150, not the ones we want. The only thing which may help us at a future point in there is the kernel config.
cedric123 said:
If you compile a kernel right now you'd get a kernel that won't read the batterylevel and the magnetic compass won't work so we need to make a few adjustments.
Click to expand...
Click to collapse
This is in needed_fixes_for_non_u8110_devices.diff
So nothing new here.
So what can we do to help?
Is there a way to chat in XDA?
Any news on this?
cedric123 said:
here is an source for the adreno drivers.
LINK REMOVED
Here are some are adreno 200 drivers from a Custom nexus one ROM:
Areno Drivers package contains the adreno rivers only(i could miss some drivers here so look for the package above contains all drivers from the nexus rom
LINK REMOVED
Click to expand...
Click to collapse
Possible to make an update.zip for this Adreno 200 driver on 2.1 while 2.2 is not working?
editeditediteditediteditedit
Maybe he's working on the project.
Leito92 said:
Maybe he's working on the project.
Click to expand...
Click to collapse
I dont think so he's not saying anything about it for 1 week now...
But even if he doesnt say anything, this topic can be useful.
Someone with git/kernel/c knowledge need to port the patch.
nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
Who can do That?
Kallt_kaffe meaby?
nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
You need some elemental knowledge in C and then simply cut and paste the text in the files.
However, I think that it is more important to be able to compile from source and install the existing Huawei Linux kernel for the U8120. That is, can we compile from source all the code for Android 2.1-update1 and install on the U8120?
It might be good to try to get CyanogenMod on the U8120 for the kernel version that Huawei provides. Then, we can cut down the 1.5MB patch into smaller parts, and even try to get the drivers included in the Linux kernel.
I have not idea how to compile Android 2.1-update1 and get the plain old android source on the phone. I am willing to invest the CPU clocks to compile it, though.
cedric123 said:
Who can do That?
Kallt_kaffe meaby?
Click to expand...
Click to collapse
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
maybe we can get some kernel developers from the desire topic to help us?
I have send Benee, deovferreira, Kali- a PM maybe they could help us
nicoderboss said:
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
Click to expand...
Click to collapse
Can we just replace the normal kernel in the command list for the new kernel so you apply patch in the new kernel(u8150)froyo kernel?
I have had contact with benee a kernel developer for the htc desire. He is willing to help but he needs a device so he can test kernels he build. It is not possible to build kernels without a device because this is a huge project without a good base.
Maybe we can setup a fund raiser to get him a device?
I was looking for a program to overclock MTK6516 processors, from china smartphones with Android, but didn't found anyone witch works.
Somebody knows some program or would like do develope it?
I want this too. I've tried many apps like SetCPU and No-Frills and none of them work.
Most chinese Android devices like the Hero H7000 have pretty decent specs at a pretty damn good price. However, they all use the god damn slow as MTK6xxx CPUs.......
Want something like this too!
Would be nice if one of the developers can write us something
You can't overclock from an app before modding the kernel to allow oc
And to mod the kernel you'ld need the kernel source
kernel unfound since we do not know the brand and manufacturer
Is hard to find it since there is no brand for it and i had been finding it since i bought a Hero H400 android china phone.
Mine CPU is mtk6515 too ~
Anyone tested to root the china phone before?
Thanks.
lingweiyong6 said:
Is hard to find it since there is no brand for it and i had been finding it since i bought a Hero H400 android china phone.
Mine CPU is mtk6515 too ~
Anyone tested to root the china phone before?
Thanks.
Click to expand...
Click to collapse
I've rooted my Gooapple 3G and tweaked it a fair bit and removed the bloatware and managed to get some speed increases that way, but still waiting on Kernel source to be able to do anything more.
The X10 Mini runs the same Qualcomm msm7227 processor as the Gooapple 3G and its widely reported that 787mhz is possible and stable with the X10, so would be nice to have that extra horsepower but until someone comes up with the source it aint gonna happen sadly.
I wonder if its possible to take the hw drivers etc from the Gooapple and merge it with the X10 Mini Source and create a hybrid rom for the Gooapple??
hi thebtman,
You are from Malaysia so this Gooapple 3G.
Need you to give commend on:
1) Camera 5MP?
2) CPU?
3) RAM & ROM?
4) Internet setting for this phone tested?
Any chance in finding an overclocking app for this type of kernel? I've rooted mine, a Star A8 aka Plum Velocity (present on gsmarena) but all the apps told me that is not for my kernel
If you don't have the kernel source, but your phone can be rooted. You can make a Overclock module and load it
Sent from my LG-P500 using XDA App
thachtunganh said:
You can make a Overclock module and load it
Click to expand...
Click to collapse
Easy to say
thachtunganh said:
If you don't have the kernel source, but your phone can be rooted. You can make a Overclock module and load it
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
And how exactly do you do that?
Why is the kernel source required? It's not that hard to decompile the kernel and hexedit some parts, I just fail to recompile it since I don't know the cmdline for those mediatek processors
Working on porting ICS to the Lanyu 910 / X10 Airpad MID-910. I think the kernel sources used for the Pascal2 could possibly work with the 910 after some config changes.
Basically with the 910 we have no stock kernel source available for reference, no stock configuration, no detailed hardware inside the device.. We know it uses the rk2918 rockchip and I know it uses the SWL-2480 / Marvel 8686, simply from observing the identifying markings on the chip. Other than that, all we know is that it uses a 2.6.32 kernel with android 2.3, has an unknown 7" capacitive touch screen, unknown camera, etc. In order for ICS to work with the 910 we'll have to use a 3.0.8+ kernel or backport all of the required components from 3.x to our working 2.6.32 sources -however we don't have the patched sources for the stock firmware, so we are better off to just use 3.0.8 kernel that the source is available for on many rk2918 devices - of course we'd have to make configuration changes to our specific hardware, and possibly patch the sources with modified/new source code for our specific hardware (if we can obtain it).
Pascal 2 has a realtek based wireless chipset.. 910 uses the SWL-2940 / Marvel 8686, the module for this is also included in the kernel sources. The 910 has an unknown touchscreen, so the kernel for the pascal2 may or may not work with the touch screen settings. It is quiet difficult to work on the kernel without in depth knowledge of all the hardware. The 910 has Lanyu printed on the motherboard, and I'm not successful in finding any detailed hardware information for the board on the 910.
Also I am concerned with the memory mappings since the 910 only has 512mb ram and the pascal2 has 1GB+
Really wish these Chinese tablet manufacturers would follow the rules of GPL and release their source code, it would help A LOT with getting ICS to work with the 910.
As far as the rockchip and the ICS rom that vurrut has put together, I am almost 100% sure that the system.img that he used will work with the 910 as long as I get a working 3.0.8 kernel for ICS reconfigured/recompiled and implement some changes in the boot.img for the init services relating to hardware.
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Needed:
Gsensor/Accelerometer MFG/Model
Input Keys Controller - MFG/Model
Battery Sensor Chip - MFG/Model
TouchScreen/Display - MFG/Model
Other mainboard chipsets - MFG/Model (excluding RK2918 Rockchip SoC)
It would be of much help if there was someone here knows the MFG/Model of any of the above hardware, and it would also be a great help if anyone knows what linux kernel drivers are used for any of the components inside the 910.
When I was working with the Kindle Fire kernel I had found a very helpful information page on the internal parts of the device, with very detailed information - it was really helpful. I know that with these generic Chinese tablets finding such info may be much more difficult due to lack of interest and lack of popularity when compared to major brand tablets such as the Kindle Fire - but if anyone out there has ran across similar information it would give us GREAT progress in developing an ICS ROM for the 910. Here is a link to the breakdown of components in the Kindle Fire:
http://www2.electronicproducts.com/Amazon_Kindle_Fire_D01400_Tablet-whatsinside_text-123.aspx
The thread to the ICS ROM for Pacal 2 (rk2918) device is here: http://forum.xda-developers.com/showthread.php?t=1734181
A big thanks to Vurrut for all of his work! Hopefully we can use parts of his ROM to get ICS running on our Lanyu/Airpad!
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Oma7144 said:
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Click to expand...
Click to collapse
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Sent from my A100 using xda premium
linuxsociety said:
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Click to expand...
Click to collapse
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Oma7144 said:
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Click to expand...
Click to collapse
Only partial information can be obtained in this manner as it will only show what device modules are loaded, the information I was wanting was precise model information of the chipsets used in the tablet. And the config for the stock kernel is not included in procfs anyway as the developers must have not said =Y to CONFIG_IKCONFIG
Sent from my A100 using xda premium
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Oma7144 said:
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Click to expand...
Click to collapse
Mr. Oma, I am sorry but I think you may be in the wrong thread, the Lanyu 910 only shares one thing in common with the other common RK2918 based tablets, and that is the RK2918 its self, the rest of the hardware that makes up the full system is different on the 910/Airpad than the more popular tablets that are using the RK2918. For example you probably use a RTL based wifi chip in the config you are using also, where the 910/AP uses the SWL-2480 which uses a Marvel 8686 driver in the linux kernel or you can use the libertas driver in more recent kernels. What exactly is the config you pasted here from? At this point I know the internal hardware enough to get a proper config file for the 910/Airpad, however there are compile issues with certain components and without resolving the compile issues there is no kernel image going to be generated unless I disable the problems at hand in the config, if you want more up-to-date information then head over the the x10 forums and check the original thread for 910/AP kernel development: http://forums.x10.com/index.php?topic=27184.0
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Oma7144 said:
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Click to expand...
Click to collapse
I appreciate your effort in helping me find info, but I have already researched most the possibilities and am already aware of the sites you linked. The problems aren't finding hardware specs, the problem now is getting 3.0.8 sources to compile with the Airpads hardware selected in the configuration, as I posted in the x10 forum, it doesn't appear that any 3.0.8 kernels have been successfully compiled for other devices using the same board-config as the 910, in fact the link you specified with the swl-2480 is the only device that has similar hardware aside from the rk2918 that I have found. The wifi and audio both fail to compile with Ody.se sources. I have decided to put most of my work now into testing/development of Jelly Bean for the Acer Iconia Tab, as it doesn't seem that many others are interested in the 910/Airpad development. Thanks again
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Oma7144 said:
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Click to expand...
Click to collapse
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
linuxsociety said:
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
Click to expand...
Click to collapse
Use gcc 4.5.2 or higher.
- Oma -
Oma7144 said:
Use gcc 4.5.2 or higher.
- Oma -
Click to expand...
Click to collapse
I also tried gcc 4.6.2 and 4.6.3 natively setup with cross compile in Gentoo / Funtoo - I get the same same errors with the wifi and the audio as using the appropriate eabi-arm toolchains.. I tracked down the problems though, it is a dephell with major code changes in common headers. The headers that are included in the sources have changed from 2.6.32.27 and to 3.0.8 and porting everything up to current is quiet more code changes than I am willing to work on. Like I have said though, I am no longer working on this kernel for the generic devices 910/AP, I have more work on my slate now than I need working on the Acer Vangogh / Vendetta kernels for Jelly Bean to incorporate Tiny HAL and newer tegra changes keeping compatability with the only Acer source we have available. But at least I am not limited to products that aren't following the GPL appropriately, and the use of uncommon hardware that makes debugging damn near impossible. I almost have the Vangogh board and Acer specifics ported over to 3.1's grouper from the nexus project and it's much more smoother than working with that chinese developed tab
Ok, than have a good time!
Greetings to Southern Kentucky.
- Oma -
linuxsociety said:
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Click to expand...
Click to collapse
Here you go: eboda-TS, MV8686 WLAN, MMA8452Q Sensor, WM8988 Audio, ANX7150 HDMI, HYM8563 Clock, APX192 Powermgt.
Could you pls compile a kernel?
- Oma -
SGP512 Kernel, first attempt since I just got the device yesterday.
- close to stock
- disabled a few modules which are rather not going to be used
- disabled debug
- integrated wlan driver & configured so that it loads properly
- integrated exFAT
Instructions:
- unzip contents, copy over the modules to /system/lib/modules (remember to set the correct permissions)
- reboot into bootloader & flash the kernel
Code:
fastboot -i 0x0fce flash boot boot.img
fastboot -i 0x0fce reboot
Download binaries: https://drive.google.com/file/d/0B8rpJsF4EG0YMFNHYWZhSHQ5VW8
source
Er... nice that someone starts developing for this device... but:
- what is wrong with the stock WiFi driver? I don't see any problems...
- exFAT is already integrated, no need of special kernel...
Doesn't seem very flash-worthy
I would really appriciate a custom kernel for the Tablet so that we can undervolt the cpu and change frequencies and governors.
But wouldn`t it be the best and easiest way to port (of course with the approval of doomlord) his already existing doomkernel from the Z2 phone?
hasenbein1966 said:
Er... nice that someone starts developing for this device... but:
- what is wrong with the stock WiFi driver? I don't see any problems...
- exFAT is already integrated, no need of special kernel...
Doesn't seem very flash-worthy
Click to expand...
Click to collapse
You won't be able to use the stock modules if you start messing too deep with the kernel & there is no in-kernel (3.4.0) driver for the bcm4339 which the Z2 uses, unless you want to mess with the brcmfmac driver.
Try using the compiled kernel I attached without copying over the associated wifi driver.
Frankus99 said:
I would really appriciate a custom kernel for the Tablet so that we can undervolt the cpu and change frequencies and governors.
But wouldn`t it be the best and easiest way to port (of course with the approval of doomlord) his already existing doomkernel from the Z2 phone?
Click to expand...
Click to collapse
You can already change the freqs & governors with tools like PerformanceControl.
The only part which would need coding is UV control & a sysfs interface for it.
I'll do it sooner or later in my free time, but seeing as I don't have much of the latter, you'll surely see the features being implemented by other devs. Or you can code/port it yourself ;]
This post was never intended to being a starting point for developing a kernel for the community. I got the device 2 days ago & prepared my base for private kernel development & since I didn't see any posts related to a kernel base for the Z2 Tablet I wanted to share it so that interested parties could have a good starting point.
It was NEVER intended for end users.
adwinp said:
You won't be able to use the stock modules if you start messing too deep with the kernel & there is no in-kernel (3.4.0) driver for the bcm4339 which the Z2 uses, unless you want to mess with the brcmfmac driver.
Try using the compiled kernel I attached without copying over the associated wifi driver.
You can already change the freqs & governors with tools like PerformanceControl.
The only part which would need coding is UV control & a sysfs interface for it.
I'll do it sooner or later in my free time, but seeing as I don't have much of the latter, you'll surely see the features being implemented by other devs. Or you can code/port it yourself ;]
This post was never intended to being a starting point for developing a kernel for the community. I got the device 2 days ago & prepared my base for private kernel development & since I didn't see any posts related to a kernel base for the Z2 Tablet I wanted to share it so that interested parties could have a good starting point.
It was NEVER intended for end users.
Click to expand...
Click to collapse
ok, sony released the kernel code on git some time ago, any news with your kernel?
spider623 said:
ok, sony released the kernel code on git some time ago, any news with your kernel?
Click to expand...
Click to collapse
I release this kernel since there were none at that time, at least none integrating the wifi driver & exfat.
Till then, the kernel development for the Z2 tablet took off, so there's no need to keep this post updated.
adwinp said:
I release this kernel since there were none at that time, at least none integrating the wifi driver & exfat.
Till then, the kernel development for the Z2 tablet took off, so there's no need to keep this post updated.
Click to expand...
Click to collapse
really? i haven't seen any other kernels around
spider623 said:
really? i haven't seen any other kernels around
Click to expand...
Click to collapse
Uhmmm.... me neither to be honest.
However, it's extremely nice to see people taking part in kernel development. It's not so easy as one thinks. It's a lot of "trial and error" before something can be released to the public.
(patiently awaiting my Z2 tomorrow)
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D
Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:
Reserved
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#
please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;
2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com