Yes, you should provide a series of patches as advertised. Ideally, each patch should be self-contained, only deal with one specific aspect of the problem, be as small as possible, etc..
I would assume that you could start with the following: 1 - a patch to the build system Makefiles to add support for the new CPU 2 - another patch with prebuilt GCC binaries necessary to cross-compile the Android sources for it (as well as a link to the original sources / config for the toolchain, as required by the GPL). If making these prebuilt binaries is not practical, at least a way to rebuilt them for any of the supported development platforms (linux-x86, darwin-x86 and Windows) from the sources. 3 - another patch with your custom AndroidConfig.h, if needed. 4 - one or more patches to modify the C library to support your architecture 5 - another patch to modify the dynamic linker 6 - etc... On Mon, May 11, 2009 at 12:07 PM, Tony SIM <[email protected]> wrote: > > Hi, > > We have ported Android to a SuperH platform, AP-3300(CPU:SH7723). and > we would like to contribute the change to review server. > > How to add a new architecture to AOSP? > We could not find any topics regarding new CPU add in mailing list > though. should we simply follow regular steps described at following ? > http://source.android.com/submit-patches > > If you have any idea to this type of architecture extension, please > let us know. > > Thanks in advance > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
