Then It could be that the hang is inside the init. you might have to look
at the ramdisk inside the init.
- Preetam
On Thu, Feb 16, 2012 at 12:50 AM, jagan <402ja...@gmail.com> wrote:
> Yes, I have seen as below
>
> Waiting 2sec before mounting root device...
> EXT3-fs: barriers not enabled
> kj
Yes, I have seen as below
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 dev
Are you sure your kernel is reaching till calling init?
it should free memory before calling init, do you see those prints
- Preetam
On Wed, Feb 15, 2012 at 5:42 PM, jagan <402ja...@gmail.com> wrote:
> As per my knowledge..
> init=/system/bin/sh , task performed by init.rc, running init.rc is a
As per my knowledge..
init=/system/bin/sh , task performed by init.rc, running init.rc is a job
of init.
But my case init itself is not running by kernel.
Regards,
Jagan.
On Wed, Feb 15, 2012 at 5:37 PM, Deepak Singal wrote:
> init=/system/bin/sh
>
> On Wed, Feb 15, 2012 at 8:05 PM, jagan <402j
Yes.. at-least by console set-up is ok.
But i got the following error...kernel+android init combo
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 files
init=/system/bin/sh
On Wed, Feb 15, 2012 at 8:05 PM, jagan <402ja...@gmail.com> wrote:
> Even I took the config file from emulator build, it' having android
> changes [android drivers+goldfish changes].
>
> But my concern is,
> If I took the kernel working with any ARM target, tested with normal
It will be able to lunch a shell on it, but nothing that is really
Android like the UI.
This page has a pretty good overview what is needed:
http://elinux.org/Android_Mainlining_Project
On Wed, Feb 15, 2012 at 1:05 PM, jagan <402ja...@gmail.com> wrote:
> Even I took the config file from emulator
Even I took the config file from emulator build, it' having android
changes [android drivers+goldfish changes].
But my concern is,
If I took the kernel working with any ARM target, tested with normal
rootfilesystem[busybox].
the same kernel[w/o any android changes], will it launch the android
root
The root file system can be taken from emulator.
system.img and other images constitute the root file system.
Any kernel will have the feature to launch the init process, for instance
the configuration of a kernel that can launch an init process can also be
taken from emulator.
pull /proc/config
As per as my knowledge, irrespective of android rootfs or
normal-rootfs Linux kernel is capble launch init., until and unless to
explicitly specified the path.
means linux kernel doesn't require any android changes for just to
lanch console.
Regards,
Jagan.
On Wed, Feb 15, 2012 at 12:54 PM, jagan
Hi Guys,
Let have your openings, suggestion & ideas about this topic.
--
Regards,
Jagan, India.
--
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
11 matches
Mail list logo