From: Peter Menzebach <pm-ub@mw-itcon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_SKIP_LOWLEVEL_INIT is broken for at91rm9200dk
Date: Mon, 03 Apr 2006 12:01:54 +0200 [thread overview]
Message-ID: <4430F292.7090508@mw-itcon.de> (raw)
In-Reply-To: <20060403152834.8B8F.LARK@linux.net.cn>
Wang Jian wrote:
> Hi,
>
> When CONFIG_SKIP_LOWLEVEL_INIT is defined, cpu/arm920t/at91rm9200/lowlevel_init.S
> is commented out and lowlevel_init() is undefined.
>
> But cpu/arm920t/start.S will still use lowlevel_init(). See the code
>
> --snip--
> #ifndef CONFIG_SKIP_LOWLEVEL_INIT
> bl cpu_init_crit
> #endif
> --snip--
>
> but cpu_init_crit() is still defined and use lowlevel_init().
>
>
> cpu/arm920t/start.o(.text+0xec):/home/lark/arm-u-boot.git/cpu/arm920t/start.S:264: undefined reference to `lowlevel_init'
> make: *** [u-boot] Error 1
>
>
>
Hi,
Here my patch (I do not find it in the mailing list archives for some
reason...)
Best regards
Peter
CHANGELOG:
Patch by Peter Menzebach, 2005-10-13
ifdef CONFIG_SKIP_LOWLEVEL_INIT around
cpu_init_crit added in cpu/arm920t/start.S
--- u-boot/cpu/arm920t/start.S.orig 2005-10-06 23:47:43.000000000 +0200
+++ u-boot/cpu/arm920t/start.S 2005-10-13 18:56:27.000000000 +0200
@@ -237,6 +237,7 @@
*/
+#ifndef CONFIG_SKIP_LOWLEVEL_INIT
cpu_init_crit:
/*
* flush v4 I/D caches
@@ -264,7 +265,7 @@
bl lowlevel_init
mov lr, ip
mov pc, lr
-
+#endif /* CONFIG_SKIP_LOWLEVEL_INIT */
/*
*************************************************************************
next prev parent reply other threads:[~2006-04-03 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 7:49 [U-Boot-Users] CONFIG_SKIP_LOWLEVEL_INIT is broken for at91rm9200dk Wang Jian
2006-04-03 9:38 ` Marco Cavallini
2006-04-03 10:01 ` Peter Menzebach [this message]
2006-04-03 11:33 ` Wolfgang Denk
2006-04-03 11:59 ` Peter Menzebach
2006-04-03 12:49 ` Wolfgang Denk
2006-04-03 13:35 ` Wang Jian
2006-04-03 13:53 ` Wolfgang Denk
2006-04-04 10:18 ` Mathieu Deschamps
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=4430F292.7090508@mw-itcon.de \
--to=pm-ub@mw-itcon.de \
--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.