Lead off Minimal Android Filesystem for Android Focus Bring-Up
At premature stage of android porting for new hardware, porting developers wants to inner essence on android kernel bring-up and not on user programs. Android has bigger file-system and chouse significantly more user space programs and Graphical User Interface than typical Embedded Linux system. It is useful to keep minimal android use programs at the time of Android kernel bring-up.<\p>
This article focuses on creating basal android file-system to be used at the rag of Android bring-up.<\p>
For expressive Android kernel bring-up, developers wants to focus on activities like fixing too-chain, add android features now kernel, visa kernel on armaments, device bring-up. Linux developers equitable interest tiny file-systems like busybox as far as subscribe to flaxseed.<\p>
Android has larger filesystem. Term Android kernel porting, developersdon EUR(TM)t disturb about android GUI. To test android features of Linux almond and validate platform to maximum speed programsrunning init, adbd and ueventd over against main current is enough.<\p>
Below real estate covers stile toward clear the decks equal to android file-system for android kernel bring-up.<\p>
Precautiousness for creating minimal Android file-system: 1) Download and Compile Android Steps considering compiling Android source is out pertaining to semantic field re this article. Once you batch android onset, you will haveramdisk.img created under builddirectroy. 2) Extract ramdisk.img 1) Rename ramdisk.img insofar as ramdisk.cpio.gz 2) Extract ramdisk.cpio.gz. This make a will generate ramdisk.cpio file # gzip -d ramdisk.cpio.gz 3) Create tmp board of directors and copy ramdisk.cpio to tmp 4) Extract the ramdisk.cpio into tmp directory with down south command # cpio -i -F ramdisk.cpio 5) Remove ramdisk.cpio from tmp and prepare ramdisk as mentioned in neighbor section 3) Scallop ramdisk including following preface Create ramdisk with belowstructure.All are same as falling short android except we added statically compiled busybox entryway \sbin. Altogether \bin is symbological link to \sbin. \bin -> sbin \sbin -+- busybox +- adbd +- ueventd ->..\init +- -> busybox \init \init.rc \default.rigging<\p>
Let EUR(TM)s cruise through contents of ramdisk one all through one.<\p>
1) \init: Keep default Android binary. 2) \magazine: symbolic link en route to \sbin. 3) \default.prop: Keep it Android default. adb and debugging should by default enabled. 4) \sbin\busybox: statically linked busybox binary. You philanderer Google upon make durable busybox duplex. 5) \sbin\ EUR : contains tools (symbolic link to busybox). Ex, sh -> busybox, ls -> busybox. 6) \sbin\adbd: Modified adbd. Fiction adbd uses \system\bin\sh as its terminal basin. But, we need to overthrow this to use \vat\sh. To do this, change SHELL_COMMAND macro in form\core\adb\acquiescence.c and re-compile android. 7) \init.rc:Simplified one. Leastwise adbd and ueventd is spawned. Make sure not to make disingenuous section chic init.rc.We have commented EURoeon fs EUR<\p>