From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: about s3c2442
Date: Thu, 10 Jan 2013 10:14:07 +0100 [thread overview]
Message-ID: <201301101014.08015.jbe@pengutronix.de> (raw)
In-Reply-To: <2237706.NjDrlknk66@yiqingliang-pc>
Hi Yi,
Yi Qingliang wrote:
> On Thursday, January 10, 2013 09:36:36 AM Juergen Beisert wrote:
> > Yi Qingliang wrote:
> > > I'm using barebox (based on mini2440) on my s3c2442 board,
> > >
> > > 1. flash barebox into nand: can't start normally, but can see early
> > > output on serial.
> > > 2. load it in sdram: can start normally into shell, and then I use it
> > > to boot kernel (also in sdram, also based on mini2440).
> > > the kernel hang, no output.
> > >
> > > after dig into it, I found something: add "mem=64M" into the kernel
> > > paramer, then the kernel can start.
> > >
> > > BUT:
> > > the barebox doesn't pass that paramert to kernel for mini2440,
> > > why the mini2440 kernel can start normally?
> > >
> > > how does the kernel on 2440 get the sdram size?
> >
> > There is no autodetection possible. Take a look into
> > the "arch/arm/boards/friendlyarm-mini2440/lowlevel_init.S": This is the
> > code which runs immediately after reset. It calls the
> > function "s3c24x0_sdram_init" from the generic part, and uses hard coded
> > values from "arch/arm/boards/friendlyarm-mini2440/config.h" to setup the
> > SDRAM controller according to the attached SDRAM type.
> > When the SDRAM is up and running, it is very easy to read back the SDRAM
> > size from the SDRAM controller's registers (which is done in the
> > function "s3c24xx_get_memory_size").
> >
> > So you need routines which do the same job for your S3C2442 CPU.
>
> and the kernel? how does the kernel know the sdram size for mini2440?
> read the cpu register set by barebox?
No. The bootloader forwards this information to the kernel as an ATAG or via
device tree. But this can only work, if also the bootloader knows the correct
SDRAM size!
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-01-10 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:07 Yi Qingliang
2013-01-10 8:36 ` Juergen Beisert
2013-01-10 9:08 ` Yi Qingliang
2013-01-10 9:14 ` Juergen Beisert [this message]
2013-01-10 17:45 ` Yi Qingliang
2013-01-10 10:00 ` Juergen Beisert
2013-01-10 19:14 ` Yi Qingliang
2013-01-10 11:20 ` Juergen Beisert
2013-01-10 17:54 ` Yi Qingliang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201301101014.08015.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox