lowlevel_init.c

lowlevel_init.c

[Xu Yang]

Hello everyone,

i am trying to run linux on realview_eb_mpcore.
I read some articles about how to port linux and uboot to a new board,
according to the article, when I am porting the uboot, i should modify
a file called lowlevel_init.c , which is in the fold
board/realview_eb. this file describes the memory partition of the
board. but in the realview_eb , this file doesn't do this job.
anyone can tell me , where is it done?

without doing this, the file system can be booted or not?

any comments are appreciated.

regards,

yang

Re: lowlevel_init.c

[Xu Yang]

Hi Gavin,

yes, the file lowlevel_init. c is under board/xxx,

but for the board realview-eb this files doesn't contain anything but
a dummy funtion. that is why I am wondering where is the board memory
partitioin done .
thanks,

any new comments?

regards,

yang

2007/8/28, Gavin Shan <gshan@alcatel-lucent.com>:
>
> ----- Original Message -----
> From: "Xu Yang" <risingsunxy@googlemail.com>
> To: <linux-kernel@vger.kernel.org>
> Sent: Tuesday, August 28, 2007 10:49 PM
> Subject: lowlevel_init.c
>
>
> > Hello everyone,
> >
> > i am trying to run linux on realview_eb_mpcore.
> > I read some articles about how to port linux and uboot to a new board,
> > according to the article, when I am porting the uboot, i should modify
> > a file called lowlevel_init.c , which is in the fold
> > board/realview_eb. this file describes the memory partition of the
> > board. but in the realview_eb , this file doesn't do this job.
> > anyone can tell me , where is it done?
> >
> > without doing this, the file system can be booted or not?
> >
> > any comments are appreciated.
> >
> > regards,
> >
> > yang
>
> I don't know what realview_eb_mpcore is actually. I'm supposing you mentioned the uboot.
> The files under board/xxx/ directory is related to board layout. I think what you need to do are:
>
> 1) Make your serial port to work at frist so that you can see any output for debugging.
> 2) Try to print more info to debug your issue.
>
> Gavin

Re: lowlevel_init.c

[Xu Yang]

u-boot/board/realview_eb/lowlevel_init.S
this is the exact path for the file.

2007/8/28, Gavin Shan <gshan@alcatel-lucent.com>:
> I couldn't find out the file.
>
> oak:/home2/gshan/u-boot/board>
> oak>find . -name lowlevel_init.c
> oak:/home2/gshan/u-boot/board>
>
> ----- Original Message -----
> From: "Xu Yang" <risingsunxy@googlemail.com>
> To: "Gavin Shan" <gshan@alcatel-lucent.com>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Tuesday, August 28, 2007 11:04 PM
> Subject: Re: lowlevel_init.c
>
>
> > Hi Gavin,
> >
> > yes, the file lowlevel_init. c is under board/xxx,
> >
> > but for the board realview-eb this files doesn't contain anything but
> > a dummy funtion. that is why I am wondering where is the board memory
> > partitioin done .
> > thanks,
> >
> > any new comments?
> >
> > regards,
> >
> > yang
> >
> > 2007/8/28, Gavin Shan <gshan@alcatel-lucent.com>:
> > >
> > > ----- Original Message -----
> > > From: "Xu Yang" <risingsunxy@googlemail.com>
> > > To: <linux-kernel@vger.kernel.org>
> > > Sent: Tuesday, August 28, 2007 10:49 PM
> > > Subject: lowlevel_init.c
> > >
> > >
> > > > Hello everyone,
> > > >
> > > > i am trying to run linux on realview_eb_mpcore.
> > > > I read some articles about how to port linux and uboot to a new board,
> > > > according to the article, when I am porting the uboot, i should modify
> > > > a file called lowlevel_init.c , which is in the fold
> > > > board/realview_eb. this file describes the memory partition of the
> > > > board. but in the realview_eb , this file doesn't do this job.
> > > > anyone can tell me , where is it done?
> > > >
> > > > without doing this, the file system can be booted or not?
> > > >
> > > > any comments are appreciated.
> > > >
> > > > regards,
> > > >
> > > > yang
> > >
> > > I don't know what realview_eb_mpcore is actually. I'm supposing you mentioned the uboot.
> > > The files under board/xxx/ directory is related to board layout. I think what you need to do are:
> > >
> > > 1) Make your serial port to work at frist so that you can see any output for debugging.
> > > 2) Try to print more info to debug your issue.
> > >
> > > Gavin
> >