From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: command bootu to start kernel
Date: Fri, 29 Oct 2010 14:36:18 +0200 [thread overview]
Message-ID: <201010291436.18901.jbe@pengutronix.de> (raw)
In-Reply-To: <AANLkTinXMoAtEAS6hifvFhoxFUETSsqTBX+s01rJ9c3F@mail.gmail.com>
Belisko Marek wrote:
> On Fri, Oct 29, 2010 at 11:26 AM, Marc Kleine-Budde <mkl@pengutronix.de>
wrote:
> > On 10/29/2010 11:21 AM, Belisko Marek wrote:
> >>>>> do you have a "MEM=32" on your command line?
> >>>>
> >>>> Well I add it but same result:
> >>>
> >>> BTW: It must be "mem=", in lowercase, but you did this.
> >>>
> >>> What I was meant to ask was, if you forget to add the "M" to "32".
> >>> Because with mem=32 you tell Linux just to use 32 bytes of memory.
> >>> Maybe your ATAGs are broken, Linux might not see the whole RAM or any
> >>> if it.
> >>
> >> yes it was typo I forgot put M after 32. Kernel now properly boot :).
> >
> > How much RAM you you have? Adjust mem= accordingly.
>
> Have 64M I will adjust.
>
> >> U-boot somehow
> >> add kernel this parameter? Because for u-boot I don't need to set this
> >> parameter.
> >
> > Nope - u-boot and barebox set up this information in the ATAG list.
> > Seems something is broken with your ATAG list.
>
> Could be a problem thats I load barebox directly to ram and run it and
> then RAM size isn't probed
> and correctly set in atags?
No, you need something like that:
[...]
static struct memory_platform_data ram_pdata = {
.name = "ram0",
.flags = DEVFS_RDWR,
};
struct device_d mini_sdram_dev = {
.id = -1,
.name = "mem",
.map_base = CS6_BASE,
.size = 64 * 1024 * 1024,
.platform_data = &ram_pdata,
};
[...]
static int mini2440_devices_init(void)
{
[...]
register_device(&mini2440_sdram_dev);
[...]
armlinux_add_dram(&mini2440_sdram_dev);
[...]
}
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-8766-939 228 |
Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-10-29 12:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 12:42 Belisko Marek
2010-10-27 13:33 ` Juergen Beisert
2010-10-27 13:54 ` Sascha Hauer
2010-10-27 14:03 ` Belisko Marek
2010-10-27 14:38 ` Juergen Beisert
2010-10-29 6:08 ` Belisko Marek
2010-10-29 7:49 ` Belisko Marek
2010-10-29 8:04 ` Marc Reilly
2010-10-29 8:20 ` Belisko Marek
2010-10-29 8:34 ` Baruch Siach
2010-10-29 8:45 ` Belisko Marek
2010-10-29 8:50 ` Marc Kleine-Budde
2010-10-29 9:04 ` Belisko Marek
2010-10-29 9:12 ` Marc Kleine-Budde
2010-10-29 9:21 ` Belisko Marek
2010-10-29 9:26 ` Marc Kleine-Budde
2010-10-29 9:30 ` Uwe Kleine-König
2010-10-29 9:31 ` Belisko Marek
2010-10-29 12:36 ` Juergen Beisert [this message]
2010-11-02 13:53 ` Belisko Marek
2010-10-27 13:46 ` Sascha Hauer
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=201010291436.18901.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