boot.img = Kernel Image (zImage) + Android Ramdisk Image (ramdisk- uboot.img)
On Jan 28, 6:52 pm, codeworkx <dani.hillenbr...@googlemail.com> wrote: > Hey Guys. > > What's the difference between a bootp zImage (kernel + initrd) and a > android boot.img? > > We're porting Gingerbread to Samsung Galaxy S and added MTD support. > I'm able to flash bootp zImages to boot partition and boot it > correctly. But we're not able to boot boot.img (header + kernel + > initrd + second) from android build system because of the header > (android magic). > Our crappy samsung bootloader doesn't like it. > > Now i'm simply building without the header and we're able to boot it. > The kernel comes up (can see this because we're displaying a splash > image) and crashes over and over again. > > https://github.com/coolya/android_system_core/commit/ad2750e46a865e00... > > Is there any another difference between bootp zImage and a android > boot.img? > What about initrd? Is it compressed or somewhat? -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
