All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] armv7: only call save_boot_params for OMAP
Date: Fri, 16 Sep 2011 21:43:52 +0530	[thread overview]
Message-ID: <4E7375C0.2020403@ti.com> (raw)
In-Reply-To: <1316187178-13700-1-git-send-email-simonschwarzcor@gmail.com>

Hi Simon,

On Friday 16 September 2011 09:02 PM, Simon Schwarz wrote:
> save_boot_params in start.S got called for all armv7 based cpus. Since the
> function relys on the OMAP specific bootloader this broke some boards
> (or to be specific added more errors to already broken ones). This patch
> wraps the call in #ifdef CONFIG_OMAP.

There is a weakly linked default function implemented in armv7/cpu.c.
So, there should not be any build break for u-boot builds.

However armv7/cpu.c is not included in an SPL build, so may cause
trouble for SPL build of non-OMAP boards. The solution for this problem
is the following:

--- a/arch/arm/cpu/armv7/Makefile
+++ b/arch/arm/cpu/armv7/Makefile
@@ -29,9 +29,9 @@ START := start.o

 ifndef CONFIG_SPL_BUILD
 COBJS  += cache_v7.o
-COBJS  += cpu.o
 endif

+COBJS  += cpu.o
 COBJS  += syslib.o

 SRCS   := $(START:.o=.S) $(COBJS:.o=.c)

Let me know if I am missing something.

best regards,
Aneesh


> 
> Signed-off-by: Simon Schwarz <simonschwarzcor@gmail.com>
> ---
>  arch/arm/cpu/armv7/start.S |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/cpu/armv7/start.S b/arch/arm/cpu/armv7/start.S
> index db8e9d2..7cb380c 100644
> --- a/arch/arm/cpu/armv7/start.S
> +++ b/arch/arm/cpu/armv7/start.S
> @@ -134,7 +134,9 @@ IRQ_STACK_START_IN:
>   */
>  
>  reset:
> +#ifdef CONFIG_OMAP
>  	bl	save_boot_params
> +#endif
>  	/*
>  	 * set the cpu to SVC32 mode
>  	 */

  reply	other threads:[~2011-09-16 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 15:32 [U-Boot] [PATCH] armv7: only call save_boot_params for OMAP Simon Schwarz
2011-09-16 16:13 ` Aneesh V [this message]
2011-09-19  8:02   ` Simon Schwarz
2011-09-20  6:22     ` Aneesh V

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=4E7375C0.2020403@ti.com \
    --to=aneesh@ti.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.