Hi. So if you set CONFIG_INITRAMFS_SOURCE your device is booting and the boot.img which is generated during android build isn't? Samsung Device? ;-)
For Example: Most Samsung Devices doesn't use Android boot images (android magic + kernel + initramfs). We've worked around this problem using a 2stage ramdisk. https://github.com/CyanogenMod/android_kernel_samsung_c1/blob/android-samsung-2.6.35.7/arch/arm/configs/c1_galaxys2_defconfig#L89 https://github.com/CyanogenMod/android_kernel_samsung_c1/blob/android-samsung-2.6.35.7/usr/galaxys2_initramfs_files/init Finally there are two ramdisks attached to the image. The 1st stage is attached using CONFIG_INITRAMFS_SOURCE which is loading the 2nd stage which will be attached during android build. hope this is helpfull to you. greets codeworkx On 26 Sep., 04:02, steeldusk <[email protected]> wrote: > Hi, > > I've been trying to boot with recovery image built with android. > Kernel seems have no problem booting, but ramdisk.img is not detected > while kernel boots up. (this ramdisk.img is separated from kernel > image) > > I've set, > CONFIG_BLK_DEV_INITRD=y > CONFIG_INITRAMFS_SOURCE="" > CONFIG_RD_GZIP=y > > in kernel configuration and as I understand there is no need to pass > any special bootarg for initramfs. I am not using standard bootloader > so I set atags regarding initrd options. > If I just try booting up with kernel img(kernel+built-in initramfs) > for testing sake, the system boots up ok with initramfs being > detected. > I am really lost with what is wrong. > any help can be great! > > Thanks > > Andy -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
