From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap4: increase SRAM budget to fix build error
Date: Mon, 08 Aug 2011 16:51:18 +0200 [thread overview]
Message-ID: <4E3FF7E6.9080705@googlemail.com> (raw)
In-Reply-To: <1312783545-14543-1-git-send-email-aneesh@ti.com>
On 08.08.2011 08:05, Aneesh V wrote:
> Signed-off-by: Aneesh V<aneesh@ti.com>
> Cc: Dirk Behme<dirk.behme@googlemail.com>
> Cc: Sandeep Paulraj<s-paulraj@ti.com>
Acked-by: Dirk Behme<dirk.behme@googlemail.com>
> ---
> include/configs/omap4_panda.h | 2 +-
> include/configs/omap4_sdp4430.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/omap4_panda.h b/include/configs/omap4_panda.h
> index e313231..814f15c 100644
> --- a/include/configs/omap4_panda.h
> +++ b/include/configs/omap4_panda.h
> @@ -245,7 +245,7 @@
> /* Defines for SPL */
> #define CONFIG_SPL
> #define CONFIG_SPL_TEXT_BASE 0x40304350
> -#define CONFIG_SPL_MAX_SIZE 0x8000 /* 32 K */
> +#define CONFIG_SPL_MAX_SIZE (38 * 1024)
> #define CONFIG_SPL_STACK LOW_LEVEL_SRAM_STACK
>
> #define CONFIG_SPL_BSS_START_ADDR 0x80000000
> diff --git a/include/configs/omap4_sdp4430.h b/include/configs/omap4_sdp4430.h
> index 5b3110c..1a5d7a6 100644
> --- a/include/configs/omap4_sdp4430.h
> +++ b/include/configs/omap4_sdp4430.h
> @@ -251,7 +251,7 @@
> /* Defines for SPL */
> #define CONFIG_SPL
> #define CONFIG_SPL_TEXT_BASE 0x40304350
> -#define CONFIG_SPL_MAX_SIZE 0x8000 /* 32 K */
> +#define CONFIG_SPL_MAX_SIZE (38 * 1024)
> #define CONFIG_SPL_STACK LOW_LEVEL_SRAM_STACK
>
> #define CONFIG_SPL_BSS_START_ADDR 0x80000000
prev parent reply other threads:[~2011-08-08 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 18:54 [U-Boot] OMAP4: Broken SPL generation Dirk Behme
2011-08-07 9:50 ` Albert ARIBAUD
2011-08-08 5:56 ` Aneesh V
2011-08-08 6:05 ` [U-Boot] [PATCH] omap4: increase SRAM budget to fix build error Aneesh V
2011-08-08 14:51 ` Dirk Behme [this message]
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=4E3FF7E6.9080705@googlemail.com \
--to=dirk.behme@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.