From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap3evm: Pass 'mem' argument to linux kernel
Date: Tue, 27 Sep 2011 15:05:06 +0300 [thread overview]
Message-ID: <4E81BBF2.5090607@compulab.co.il> (raw)
In-Reply-To: <1317122493-26452-1-git-send-email-premi@ti.com>
On 09/27/11 14:21, Sanjeev Premi wrote:
> In absence of this argument, Linux kernel doesn't boot.
>
> Default value has been set to 128M to ensure that
> Linux kernel boots on older EVMs as well.
This change affects all EVMs, unless they explicitly change/remove
the memsize variable or change the *args variables.
Can't the get_ram_size() function be used for detecting the actual
amount of RAM? and then the memory tag or FDT equivalent
(if there is one) used to pass the memory size information?
>
> Signed-off-by: Sanjeev Premi <premi@ti.com>
> Cc: Sandeep Paulraj <s-paulraj@ti.com>
> ---
>
> This patch has been created against u-boot-ti/next.
>
> include/configs/omap3_evm.h | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/include/configs/omap3_evm.h b/include/configs/omap3_evm.h
> index 7af30c2..ea51216 100644
> --- a/include/configs/omap3_evm.h
> +++ b/include/configs/omap3_evm.h
> @@ -200,11 +200,14 @@
> "loadaddr=0x82000000\0" \
> "usbtty=cdc_acm\0" \
> "mmcdev=0\0" \
> + "memsize=128M\0" \
> "console=ttyO0,115200n8\0" \
> "mmcargs=setenv bootargs console=${console} " \
> + "mem=${memsize}\0 " \
> "root=/dev/mmcblk0p2 rw " \
> "rootfstype=ext3 rootwait\0" \
> "nandargs=setenv bootargs console=${console} " \
> + "mem=${memsize}\0 " \
> "root=/dev/mtdblock4 rw " \
> "rootfstype=jffs2\0" \
> "loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr\0" \
--
Regards,
Igor.
next prev parent reply other threads:[~2011-09-27 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 11:21 [U-Boot] [PATCH] omap3evm: Pass 'mem' argument to linux kernel Sanjeev Premi
2011-09-27 12:05 ` Igor Grinberg [this message]
2011-09-27 18:08 ` Premi, Sanjeev
2011-09-28 18:53 ` Wolfgang Denk
2011-09-28 18:47 ` Wolfgang Denk
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=4E81BBF2.5090607@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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