You should start by porting the C library, which would involve: - modifying the tools used to generate the syscalls stubs to emit MIPS assembler fragments, and the SYSCALLS.TXT input file for them - probably grab a few OpenBSD mips-related arch-specific header files for configuration purposes - regenerate the clean kernel headers for the 'arch-mips' sub-tree
Then, modify the dynamic linker to handle all MIPS-specific relocations. Finally, if your CPU is big-endian, probably fix a few endian-related problems in the system or the tools like aapt, etc.. Hope this helps On Mon, Feb 9, 2009 at 1:47 PM, Androidphan <niels.kee...@tass.nl> wrote: > > Is it possible to port Android to a MIPS? What does it take to compile > it for this architecture? I read about libc, that this is not possible > to cross compile, so I need to build Dalvik against glibc? Are there > any other things I need to worry about before trying to cross compile > it for MIPS? What things are ARM specific? > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
