diskinstaller is only used for x86 to create a bootable installer. On Wed, Jan 28, 2009 at 3:21 PM, twebb <taliaferr...@gmail.com> wrote:
> > Other than the brief comments in recovery.c and firmware.c, are there > more detailed documents explaining the android startup process, from > power on to opening screen? I don't necessarily care about the G1 > implementation details but am interested in the android-specific > features. In designing a new android-based device, I'd like to boot, > recover, update, etc. the "android" way, but I'm having a difficult > time understanding what the android way is versus the functionality > that might be proprietary to t-mobile. > > Some questions include: what does the G1 use as a bootloader? Is > diskinstaller used to configure a "blank" G1 (i.e. nothing in flash) > at first power? Comments indicate that the recovery tool uses > commands written to and read from /cache/recovery/..., but code > (recovery.c) seems to show that the bootloader commands are read from > and written to the "misc" partition? How do bootloader and recovery > command mechanisms work? How do they differ? What is the "radio > image" and what is the "hboot image"? How does "firmware" differ from > other images that are updated? Is /cache used as a yaffs2 filesystem > sometimes and as a raw storage area at other times? > > Sorry for all the questions - just trying to get a handle on how > booting and updating really work, and whether these models are the > preferred way to move forward. > > Thanks. > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
