[Arm-netbook] Dissecting mmcblk0p1 and the boot process

Luke Kenneth Casson Leighton luke.leighton at googlemail.com
Tue Mar 16 11:44:18 GMT 2010

On Tue, Mar 16, 2010 at 11:03 AM, Frans Pop <elendil at planet.nl> wrote:

> I've verified this by doing a flash boot with only:
> - a dummy datang-epc.tar.gz file
> - a custom built kernel as zImage_dt_update (without initrd piggybacked)
> The kernel on mmcblk0p1 at that time was the original ChiTech kernel.
> This resulted in:
> - the zImage_dt_update was booted
> - the normal root FS getting mounted
> - at the next reboot the *original* kernel gets booted again
> So this means we can test custom kernels *without* flashing them!


> The next problem is how exactly to piggyback an initrd on top of the
> kernel. There are various alternatives, but I've not yet found something
> that works. Any help would be much appreciated.

 i thought this was it:


 but you use -T multi option and ... hm.

 i'll take a look later, see if i can uncompress zImage_dt_update.


More information about the Arm-netbook mailing list