Actually, the best would be the changeset, or patch-set of the changes made by ZTE, so we could build any version of the Android kernel, with some modifications. This would be good for both sides: - ZTE gets a properly debugged, working new kernel, without moving a finger (and even it may add more features) - We, users get a nice working kernel build, what can be freely used, and also, the latest overclock systems, everything. So the patch set would make everyone happy :D fonix232 2011/1/6 Jon Vaughan <jon-sanfran@xxxxxxxxxxxxx> > Hi Ben, > > Thank you for uploading the code. > > I maintain a git source repository at > http://github.com/jvaughan/san-francisco-kernel to help collaboration > between people working on custom software for the Blade. > > For the zte-2.6.29 branch, I committed the code against the > android-msm-2.6.29 branch from Code Aurora Forum. The Code Aurora > code appeared to be close to your released kernel, with the only > changes appearing to be for ZTE device support in your released code, > so this made sense and adds history to our repository. > > Comparing the new 2.6.32 kernel to the Code Aurora 2.6.32 branch, > there are many more changes and they not only zte-specific so it looks > like you didn't use this as your starting point. > > If you're happy to share, it would be helpful to know what kernel you > used as the basis for this release? > > Thanks, > > Jon > >