Guest hecatae Posted February 26, 2011 Report Share Posted February 26, 2011 https://www.codeaurora.org/gitweb/quic/le/ git clone git://codeaurora.org/kernel/msm.git will pull in the kernel from codeaurora we need to look at the 2.6.32 branch and see what changes were made to turn it into git clone https://github.com/ZTE-BLADE/ZTE-BLADE-2.6.32.git and then apply these change to the 2.6.35 branch so 2.6.35 works on the blade. reasons for doing this? a new kernel will give us greater compatibility with new versions of Android, one example: HCDRJacob has already stated that usb tethering and debugging on CM7 needs a new kernel http://code.google.com/p/cyanogenmod/issues/detail?id=2951 http://code.google.com/p/cyanogenmod/issues/detail?id=2975 so who has access to https://github.com/ZTE-BLADE/ so we can fork a master branch from the codeaurora source and start looking for changes? Link to comment Share on other sites More sharing options...
Guest jurrasstoil Posted February 26, 2011 Report Share Posted February 26, 2011 isn't there are 2.6.37 msm kernel out already? Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 26, 2011 Report Share Posted February 26, 2011 (edited) 44 hours ago gingerbread_rel shortlog | log | tree 2 days ago android-msm-2.6.35 shortlog | log | tree 2 days ago froyo_pumpkin shortlog | log | tree 4 days ago android-msm-2.6.35-froyo shortlog | log | tree 8 days ago froyo_almond shortlog | log | tree 4 weeks ago android-msm-2.6.32 shortlog | log | tree 5 weeks ago froyo_squash shortlog | log | tree 5 weeks ago eclair_chocolate shortlog | log | tree 8 weeks ago aosp/android-msm-2.6.35 shortlog | log | tree 2 months ago eclair_caramel shortlog | log | tree 2 months ago froyo-release-2 shortlog | log | tree 3 months ago msm-2.6.35 shortlog | log | tree 3 months ago froyo-release shortlog | log | tree 4 months ago eclair_coffee shortlog | log | tree 4 months ago aosp-kernel-common/android-2.6.35 shortlog | log | tree 4 months ago aosp-kernel-common/android-2.6.36 shortlog | log | tree ... not as far as I can see, the cm kernel is 2.6.37 but codeaurora is not Edited February 26, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest NGG1 Posted February 28, 2011 Report Share Posted February 28, 2011 The 2.6.32 ZTE kernel was forked from the Code Aurora's android-msm-2.6.32 kernel on 15 July 2010 from this tree. I'd prefer if we could port cm-kernel to blade, that contains lots of optimizations, additions. Link to comment Share on other sites More sharing options...
Guest hecatae Posted February 28, 2011 Report Share Posted February 28, 2011 okay, so do we need to compare both codeaurora and the zte kernel, look at the changes and apply these to the cm kernel? what tools would you suggest we use to compare Link to comment Share on other sites More sharing options...
Guest wbaw Posted March 1, 2011 Report Share Posted March 1, 2011 (edited) diff? or one of the graphical versions http://stackoverflow.com/questions/776854/...-trees-in-linux diffuse is installed on my fedora, it seems ok. Edited March 1, 2011 by wbaw Link to comment Share on other sites More sharing options...
Guest hecatae Posted March 4, 2011 Report Share Posted March 4, 2011 (edited) diff? or one of the graphical versions http://stackoverflow.com/questions/776854/...-trees-in-linux diffuse is installed on my fedora, it seems ok. started this yesterday, started modifying cm-kernel msm2.6.37 to suit blade requirements, Meld is very effective Edited March 4, 2011 by hecatae Link to comment Share on other sites More sharing options...
Guest Simon O Posted March 4, 2011 Report Share Posted March 4, 2011 You'll have a much harder job trying to port 2.6.38 to the blade. Just update the ZTE kernel to .35 like the majority of non-HTC devices running CM7 are using since it actually supports qualcomm devices. Should also mention, and this isn't any way to disrespect anybody here, but unless you know exactly what you are doing then using tools like meld to find differences and replace them will just mean you end up bastardizing the cm kernel code with modified ZTE code from the .32 kernel. HCDRJacob is looking at upgrading the current source to .35 which will allow all the gingerbread functions to work correctly. This will mean USB tethering, WiFi tethering etc will work natively. Link to comment Share on other sites More sharing options...
Guest ThrashMan Posted March 4, 2011 Report Share Posted March 4, 2011 HCDRJacob is looking at upgrading the current source to .35 which will allow all the gingerbread functions to work correctly. This will mean USB tethering, WiFi tethering etc will work natively. That's good news. Would it offer any improvement to 2D & 3D performance? Link to comment Share on other sites More sharing options...
Guest Simon O Posted March 5, 2011 Report Share Posted March 5, 2011 That's good news. Would it offer any improvement to 2D & 3D performance? Possibly not but who knows. The most important thing is that Gingerbread is designed for .35 kernels and some features like USB/Wifi tethering need it to work. Link to comment Share on other sites More sharing options...
Guest hecatae Posted March 9, 2011 Report Share Posted March 9, 2011 but we need to check the existing 2.6.32 kernel for bugs and errors before even attempting applying changes to the 2.6.35 kernel Link to comment Share on other sites More sharing options...
Guest GX390 Posted March 9, 2011 Report Share Posted March 9, 2011 Sorry for the noob question but what does a different Kernel actually do? Cheers Link to comment Share on other sites More sharing options...
Guest hecatae Posted March 9, 2011 Report Share Posted March 9, 2011 Sorry for the noob question but what does a different Kernel actually do? Cheers Why upgrade? There are several reasons to upgrade your kernel. Most of the reasons are that you perhaps need a new device driver for your new or old hardware (the previous device driver could have had a bug somewhere) or you need to upgrade due to a bug in the kernel (security one or a non-security one). Usually new kernels run faster than the old ones and are more stable and reliable. http://www.faqs.org/docs/lnag/lnag_kernel_upgrade.html Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now