public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marco Cavallini <arm.linux@koansoftware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_SKIP_LOWLEVEL_INIT is broken for at91rm9200dk
Date: Mon, 03 Apr 2006 11:38:59 +0200	[thread overview]
Message-ID: <4430ED33.8030507@koansoftware.com> (raw)
In-Reply-To: <20060403152834.8B8F.LARK@linux.net.cn>

Wang Jian ha scritto:
> 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 I noticed and solved this problem and all CONFIG_SKIP_LOWLEVEL_INIT 
related one for AT91 last week.
BTW I noticed that there is an existing patch [DNX#2006033142000856] to 
solve it too, but I don't know where is the u-boot patch repository.

Feel free to contact me if you want my own patch.

Best regards
-- 
Marco Cavallini
Koan s.a.s. - Bergamo - ITALIA
Embedded and Real-Time Software Engineering
www.koansoftware.com    |    www.klinux.org

  reply	other threads:[~2006-04-03  9:38 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 [this message]
2006-04-03 10:01 ` Peter Menzebach
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=4430ED33.8030507@koansoftware.com \
    --to=arm.linux@koansoftware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox