I replaced boot.img the Android to MeeGo. But boot partition(/dev/mtdblock2) is too small. This block only can write data about 2.5MB. So It can't put fully rootfs or intelligent initrd. then boot.img(recover.img) is required zImage and initrd. But zImage only booting has already been proven. So It's ok that we prepare zImage and *empty* initrd.
1. Prepare a zImage(CONFIG_BLK_DEV_INITRD is not set). How to make a kernel is writte…
As you know, MeeGo 1.0 has been released. Netbook has the User Experience then you can test that using image on your netbook. But N900 and IVI image has no UX. They seem to be development release in position :(
I have a time now, so I output dmesg on my N900 when it was booted by microSD and temporaly boot of kernel.
I used in the following files.
meego-n900-open-armv7l-184.108.40.20600525.1-sda.raw.bz2 ( bzcat xxx.bz2 | dd of=/dev/sdX(microSD) bs=4k)
meego-n900-open-armv7l-220.127.116.1100525.1-vmlinuz-18.104.22.168-11.2-n900 ( sudo flasher-3.5 -l -b -k xxx)
[ 0.000000] Linux version 22.214.171.124-11.2-n900 ([email protected]) (gcc version 4.4.2 20091027 (MeeGo 4.4.2-7) (GCC) ) #1 PREEMPT Mon May 24 18:36:18 UTC 2010
[ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Nokia RX-51 board
[ 0.000000] Ignoring unrecognised tag 0x414f4d50
[ 0.000000] Memory policy: ECC …