Related
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks，but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse？It say we can build stockrom based on LG official open sourse and Google android open sourse，we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail，I think I didn't pick up the guide of LG open sourse 。Do you have some good advices？Thanks again！
Sent from my LG-SU640 using xda premium
I was Wondering How Do I Get Started Porting This Kernel I Know How To Make Roms because I Can From Android forums, Never Did Kernels Or Kernels Ports So How Do I Get Started.... The sources Are Here
Sources :-
Sources at*http://github.com/gokhanmoral/siyahkernel-sgs3
Ramfs at*http://github.com/gokhanmoral/ramfs-sgs3
Toolchain at*http://github.com/gokhanmoral/android_prebuiltSimply clone all to a directory and run build_kernel.sh in the kernel directory
Porting a Kernel primarily modifies the Ram Disk. You will need to get correct drivers from Samsung's source or from CM device tree. In addition, you have to make sure the Governors and Schedulers in Siyah are actually supported on this chipset.
Here's few Guides. Link 1 Link 2 and CM Build Guide
Most important of all, ask the Original Dev for permission!!!
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.
Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?
Hello,
it's possible to compile N for the wave... But I don't really see the use in it...
Wave's ram is too low....using android 7 with it will be so slow
Honestly best ROM made for wave till now is ICS....it is fast and uses less ram
Best Regards
yes
yesterday , galaxy s1 has released cm 14
so lt will be posible
---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------
ghostbiceps said:
Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?
Click to expand...
Click to collapse
yes
yesterday , galaxy s1 has released cm 14
so lt will be possible
Very possible. @fire555 you can apply commits from kernel N of S1 to Wave and port CM14 of S1 to Wave?
You can tell me version of gcc to build kernel for wave? Thanl you
i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank
thinhx2 said:
i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank
Click to expand...
Click to collapse
Using GCC 4.7 should be fine. Maybe newer too.
fire855 said:
Using GCC 4.7 should be fine. Maybe newer too.
Click to expand...
Click to collapse
You can send me link of gcc 4.7?
@fire855
thinhx2 said:
@fire855
Click to expand...
Click to collapse
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.
xc-racer99 said:
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.
Click to expand...
Click to collapse
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs
thinhx2 said:
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs
Click to expand...
Click to collapse
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)
xc-racer99 said:
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)
Click to expand...
Click to collapse
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try
thinhx2 said:
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try
Click to expand...
Click to collapse
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.
xc-racer99 said:
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.
Click to expand...
Click to collapse
I no build rom,because wave can run rom of s1 normal with kernel of wave. I think no need build rom. I only merge new commits of kernel 7.0 s1 to wave. I patched comeplet but i have problem. I will try tonight
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.