My intend was to try a Linux kernel which is perfectly working with some ARM target was able to launch the android FS or not. BTW, I tried few of the android spec changes too.
Pls see the below log: Waiting 2sec before mounting root device... EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted <<<< hangs>>>>>> Regards, Jagan.. On Sat, Feb 18, 2012 at 1:19 PM, Cheryala Venu Madhav < [email protected]> wrote: > Hi, > > Did you integrate the ANdroid specific drivers, drivers/staging/ and also > your Android ASHMEM support? > > Is your kernel booting up? and then you are facing the issue with FS > mounting? > > Please share the bootlogs if possible. > > Thanks > Venumadhav > > > On Thu, Feb 16, 2012 at 5:58 PM, freakingtux > <[email protected]>wrote: > >> Hello >> >> >> On Tuesday, February 14, 2012 6:54:59 PM UTC+1, jagan wrote: >> >>> Hi All, >>> >>> I have trying to port android onto my ARM target. >>> Before proceeding with android, I tried for Linux kernel+root file- >>> system. >>> It was pretty working with above combination. [console is up] >>> >>> As my observation filesystem is mounted but kernel is unable to run >>> android init. >>> Was there any changes needed for kernel to run-up the android init, >>> because my kernel doesn't have any android changes. >>> >> >> To run Android you indeed need kernel changes see >> http://elinux.org/Android_Kernel_Features >> >> Greetings >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-porting >> > > > > -- > Thanks > Venumadhav > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
