Thanks a lot for the reply, Mark. Now I got it understood. I can log in the console on my target board using ramdisk.img files generated using only 'make'. So at least for my target board(ARM926EJ-S), it is compatible with default compiling environment. Thanks. Peter Oh Device Software Engineer | Client Operations | InnoPath Software 400 E. Caribbean Dr. Sunnyvale | CA. USA | +1)4089629357 ________________________________ From: android-porting@googlegroups.com [mailto:android-port...@googlegroups.com] On Behalf Of Mark Wang Sent: Tuesday, February 10, 2009 12:36 AM To: android-porting@googlegroups.com Subject: [android-porting] Re: Can I use generic/ramdisk.img for my target board?
it depends on the File system configuration of your board. ramdisk.img is the root FS with ramdisk format. system.img and data.img will be mounted under /system, /data by default. Of course, images will be built by the cross-compilers attached the Android package. ABI will ensure the system call and Android middlewares. but to enable Android on your target, the android special features like binder, power, etc. must be ported to the target. Good Luck! On Mon, Feb 9, 2009 at 8:07 PM, ebmajor <p...@innopath.com<mailto:p...@innopath.com>> wrote: Hi all, I'm using ARM926EJ-S target board - almost like mainstone board. When I compile android full source using only 'make' command, I can get the 3 images ramdisk.img, system.img, userdata.img under the target/.../generic directory. So can I use these 3 files for my target board? or, should I use some cross comiling option like make CROSS_COMPILE=arm-none-linux-gnueabi- ?? or is there any other ways to compile these 3 image files for real target board? best regards. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
