From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: Add support for edb93xx boards
Date: Tue, 8 Dec 2009 22:07:34 +0100 [thread overview]
Message-ID: <20091208210734.GE31886@darwin> (raw)
In-Reply-To: <20091208203319.0179119F3F@gemini.denx.de>
hi wolfgang,
El Tue, Dec 08, 2009 at 09:33:18PM +0100 Wolfgang Denk ha dit:
> In message <20091208151358.GD31886@darwin> you wrote:
> >
> > i am starting to look at this issue and it seems i need some more guidance:
> >
> > before relocating U-Boot to RAM for ARM920T processors a jump to the
> > label *lowlevel_init* is performed, where RAM timings are supposed to
> > be set up. in the patch i sent these operations are performed in
> > assembly and you asked me to rewrite them in C.
> >
> > i'm relativly new to low-level setup, so i apologize if the following
> > question sounds plain stupid to you: is C really available at this
> > point? if my interpretation of the code in cpu/arm920t/start.S is
> > correct, C code starts at start_armboot, after relocation of
> > U-Boot. and after that point i'd think it's to late to change RAM
> > timings as U-Boot is running from RAM.
>
> After relocation we have a full-blown, "normal" C runtime environment.
> Before that, you can use C as well, if you mind the restrictions (like
> data and bss not being available/writable yet, no real stack, etc.).
>
> > could you please give some advice to clear my confusion and maybe
> > provide a pointer to a board/cpu which handles low-level setup in
> > the intended way?
>
> If you check theinit code in cpu/arm920t/start.S you will notice that
> one of the really early things it does is calling coloured_LED_init()
> and red_LED_on(). Note that these functions are implemented in C.
thanks a lot for your explications and for providing an example
best regards
--
Matthias Kaehlcke
Embedded Linux Developer
Barcelona
Insanity: doing the same thing over and over
again and expecting different results
(Albert Einstein)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
next prev parent reply other threads:[~2009-12-08 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 14:54 [U-Boot] [PATCH] ARM: Add support for edb93xx boards Matthias Kaehlcke
2009-12-07 15:51 ` Tom
2009-12-07 19:46 ` Wolfgang Denk
2009-12-07 23:33 ` Matthias Kaehlcke
2009-12-07 23:51 ` Wolfgang Denk
2009-12-08 15:13 ` Matthias Kaehlcke
2009-12-08 15:55 ` kevin.morfitt at fearnside-systems.co.uk
2009-12-08 20:42 ` Wolfgang Denk
2009-12-08 20:33 ` Wolfgang Denk
2009-12-08 21:07 ` Matthias Kaehlcke [this message]
2009-12-18 22:32 ` Matthias Kaehlcke
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=20091208210734.GE31886@darwin \
--to=matthias@kaehlcke.net \
--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.