Hi, On Fri, Feb 11, 2011 at 8:13 PM, hck <michak...@gmail.com> wrote: > 1. Am I porting it right way?
Not at all. Forward porting board support generally means updating said code to be compatible with a newer kernel revision. What you appear to have done is replacing core parts of the kernel (v2.6.35) with old code (v2.6.32) to make it compatible with your board support code. While it may compile after some hacking, it will certainly not work. You've done exactly the opposite of what you should have done. Perform a diff between your v2.6.32 tree and whatever upstream tree was originally used, then extract the board-specific changes and apply them to the v2.6.35 tree (git rebase might be useful here). Then, modify your board code and/or drivers to be compatible with v2.6.35. With some luck it should at least get you a booting kernel. > 2. Do I have to modify my system to boot with other kernel? We don't know your board/phone, thus it's hard to say. In general, the kernel revision shouldn't matter. > 3. When I compile my kernel I'm getting warnings like: "warning: > passing argument 1 of 'spinlock_check' from incompatible pointer > type". Can it cause problems with boot? I'm trying to fix all > warnings. Yes. Especially warning about incompatible pointers, try to realize what it's telling you; The caller is passing a pointer to different type than spinlock_check expects, thus the callee will receive a pointer to something completely different from what it's expecting to see. At best the function will simply fail, probably it will lead to a crash. Joerie -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
