From: Hebbar <gururajakr@sanyo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ARM926: compile cpu_init_crit function only if CONFIG_SKIP_LOWLEVEL_INIT is not defined
Date: Tue, 18 Dec 2007 15:52:33 -0800 (PST) [thread overview]
Message-ID: <14408413.post@talk.nabble.com> (raw)
Hi,
This patches allows cpu_init_crit function to be compilled only if
CONFIG_SKIP_LOWLEVEL_INIT is not defined. At present irrespective of
CONFIG_SKIP_LOWLEVEL_INIT, cpu_init_crit is always compilled. This is for
arm926ejs module.
--- u-boot-1.3.1/cpu/arm926ejs/start.S 2007-12-06 01:21:19.000000000 -0800
+++ uboot/cpu/arm926ejs/start.S 2007-12-19 08:40:37.296875000 -0800
@@ -187,7 +187,7 @@ clbss_l:str r2, [r0] /* clear loop...
_start_armboot:
.word start_armboot
-
+#ifndef CONFIG_SKIP_LOWLEVEL_INIT
/*
*************************************************************************
*
@@ -225,6 +225,9 @@ cpu_init_crit:
bl lowlevel_init /* go setup pll,mux,memory */
mov lr, ip /* restore link */
mov pc, lr /* back to my caller */
+
+#endif /* CONFIG_SKIP_LOWLEVEL_INIT */
+
/*
*************************************************************************
*
Signed-off-by: Hebbar
I welcome comments, complaints, suggestions and advices.
Regards
Gururaja
--
View this message in context: http://www.nabble.com/-PATCH--ARM926%3A-compile-cpu_init_crit-function-only-if-CONFIG_SKIP_LOWLEVEL_INIT-is-not-defined-tp14408413p14408413.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2007-12-18 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 23:52 Hebbar [this message]
2007-12-18 23:59 ` [U-Boot-Users] [PATCH] ARM926: compile cpu_init_crit function only if CONFIG_SKIP_LOWLEVEL_INIT is not defined Hebbar
2007-12-19 6:27 ` Dirk Behme
2008-02-04 22:38 ` Wolfgang Denk
2008-02-05 1:32 ` Hebbar
2008-02-13 23:59 ` Wolfgang Denk
2008-02-14 0:19 ` Hebbar
-- strict thread matches above, loose matches on Subject: below --
2007-12-19 8:48 Gururaja Hebbar K R
2007-12-19 8:58 ` Dirk Behme
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=14408413.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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.