Hi,
I was doing the same the last few days for the Samsung Galaxy kernel.
I used "meld" to build a patchset between android-2.6.27 and the
Galaxy sources (most of the differences being additions to the mach-
msm board and arm architecture).
Eventually, you will get to something that compiles. Th
On Thu, Jan 28, 2010 at 12:07 PM, Xan wrote:
> Ok, so to work through this, I need to diff the specific vendor
> differences, apply them to the new 2.6.29 kernel and work out the
> compiler errors? Are there any extra tools or advice that you could
> give? =P
Nope, that sounds about right.
good
Ok, so to work through this, I need to diff the specific vendor
differences, apply them to the new 2.6.29 kernel and work out the
compiler errors? Are there any extra tools or advice that you could
give? =P
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.
On Thu, Jan 28, 2010 at 1:26 AM, Xan wrote:
> Well we can't run eclair or 2.1 on 2.6.27. So I want to update a
> little bit =P I just thought it would be easier than it is now. Is
> there a way to do it instead of patching? Like just copying over
> drivers and telling it to look for them?
Nope, s
Well we can't run eclair or 2.1 on 2.6.27. So I want to update a
little bit =P I just thought it would be easier than it is now. Is
there a way to do it instead of patching? Like just copying over
drivers and telling it to look for them?
The cross compiler? In the toolchain? Yeah i've been using 4
