On Fri, Feb 11, 2011 at 10:19 AM, Stefan <sgo...@dh-electronics.de> wrote:
> > It's not architecture, but board specific. > > So, I have to delete the goldfish-init and write my board specific > file. > > You don't have to delete it technically, it will just be ignored. > What do I have to write into e.g. init.myOwnBoard.rc if I "only" > want to start Android as I can see it running on the emulator? > > That's quite an open question. The point of this file is to perform any board-specific initialization. It could defining new services, mounting partitions, defining system properties, whatever. Apart from that, consider it an extension of init.rc It really depends on the customization you have done. > Do I have to edit the normal init.rc too for this? > > The idea is that init.rc is platform-specific, while init.<board>.rc is board-specific. I.e. if you modify the platform in significant ways, you would modify init.rc to reflect that. You could then use the same platform to build various product configurations (each corresponding to a different board), and put their own customizations in init.<board1>.rc, init.<board2>.rc, etc... Of course, if all you do is developing a single product/board, you can just modifiy init.rc instead. Would you be so kind and give me an example for a running init.XXX.rc- > File? > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
