Hi,
Now I have got the console prompt in my development board. During
Android init flow, console dev file(/dev/ttyS2) is opened and closed before
"on init" trigger happened. While running "console" service the same console
is again opened and "/system/bin/sh" is running on this console.
But in my development board nothing is printed after console dev
file(/dev/ttyS2) has been closed. So I have commented closing console
dev file steps in code(system/core/init/init.c). Now I am getting console
prompt in /dev/ttyS2. *But Clear reason don't know*.
modified code snippet (system/core/init/init.c)
=====================================
if (console[0]) {
snprintf(tmp, sizeof(tmp), "/dev/%s", console);
console_name = strdup(tmp);
}
fd = open(console_name, O_RDWR);
if (fd >= 0)
have_console = 1;
* //close(fd);*
With Regards
J.Balakrishnan
On Thu, Nov 4, 2010 at 8:05 PM, andrew_esh <[email protected]> wrote:
> I don't have "init=/init" in my kernel command line. This is one of
> the places the kernel searches by default, so it should not be needed.
>
> Note that you log says: "<3>init: /init.rc: 45: invalid command
> 'touch'". This implies that the init.rc file has something wrong in
> it, at least on line 45. I'd check the contents of that file first.
>
> Also check that "console=null" is not in your kernel command line.
>
>
> On Nov 3, 6:47 pm, Ashwin Bihari <[email protected]> wrote:
> > Add "init=/init" to your bootargs..
> >
> > Regards
> > -- Ashwin
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Nov 3, 2010 at 6:59 AM, bala krishnan <[email protected]> wrote:
> > > Hi,
> > > I am newbie to android porting work :-). Currently I am porting donut
> > > version of android to pxa300 based development board. I have taken
> Littleton
> > > board android package as a reference. My first moto is to get the
> console
> > > prompt of android kernel (2.6.29) in my development board. But , it is
> > > hanging after init.rc parsing done by init process. I have no idea how
> to
> > > proceed/debug to get the prompt. Here with I have attached boot log.
> >
> > > Please give me some ideas to resolve this problem.
> >
> > > With Regards
> > > J.Balakrishnan
> >
> > > --
> > > unsubscribe:
> > > [email protected]<android-porting%[email protected]>
> > > website:http://groups.google.com/group/android-porting
>
> --
> unsubscribe:
> [email protected]<android-porting%[email protected]>
> website: http://groups.google.com/group/android-porting
>
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
