Did you add ash memory to your kernel? On Mar 13, 3:37 am, Максим Андрущенко <[email protected]> wrote: > Hello! > > I am porting Android on s3c6410 compatible platform. So, using Android > sources, i created platform's profile, and compiled ramdisk.img, system.img, > userdata.img. > > I use 2.6.31-rc4 kernel, in which i included android specific drivers: > > # Android > # > CONFIG_ANDROID=y > CONFIG_ANDROID_BINDER_IPC=y > CONFIG_ANDROID_LOGGER=y > CONFIG_ANDROID_RAM_CONSOLE=y > CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y > CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT=y > CONFIG_ANDROID_RAM_CONSOLE_EARLY_ADDR=0 > CONFIG_ANDROID_RAM_CONSOLE_EARLY_SIZE=0 > CONFIG_ANDROID_TIMED_OUTPUT=y > # CONFIG_ANDROID_TIMED_GPIO is not set > CONFIG_ANDROID_LOW_MEMORY_KILLER=y > > All my platform's driver compiled into kernel statically. > Also i included ramdisk.img into kernel,because it's small sized - 160kb. > I just unzipped ramdisk.img wit command gzip -d ramdisk.img and got > ramdisk.cpio > Here is how i included this ramdisk.cpio to kernel. > > CONFIG_BLK_DEV_INITRD=y > CONFIG_INITRAMFS_SOURCE="/1/ramdisk.cpio" > CONFIG_INITRAMFS_ROOT_UID=0 > CONFIG_INITRAMFS_ROOT_GID=0 > CONFIG_RD_GZIP=y > # CONFIG_RD_BZIP2 is not set > # CONFIG_RD_LZMA is not set > CONFIG_INITRAMFS_COMPRESSION_NONE=y > > Then I compiled kernel and got uImage. > > Using U_BOOT i wrote kernle, system.img and userdata.img into nand flash. > Here is my parameters in u-boot environment to kernel: > mtdparts=s3c6400-nand:384k(u-boot),3m(kernel),65m(system),59m(userdata) > console=ttySAC2,115200 > which means > mtdpart0 - u-boot > mtdpart1 - linux kernel > mtdpart2 - system.img (yaffs2) > mtdpart3 - userdata.img (yaffs2) > > But it's a pity, at the end of kernel booting i got an error: > Freeing init memory: 348K > s3c6410_setup_sdhci2_cfg_card: CTRL 2=00000100, 3=80808080 clk_ctrl=0008 > s3c6410_setup_sdhci2_cfg_card: CTRL 2=00000100, 3=80808080 clk_ctrl=0008 > Kernel panic - not syncing: Attempted to kill init! > > What can it be the problem with? > How init binary from ramdisk.img knows where i placed system.img and > userdata.img? > > Because in the init.rc i found something like this: > mount yaffs m...@system /system > > So isn't it strange?
-- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
