From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] clarifications u-boot for arm
Date: Fri, 14 Jul 2006 10:23:36 -0400 [thread overview]
Message-ID: <44B7A8E8.3090004@smiths-aerospace.com> (raw)
In-Reply-To: <d71be96b0607140711p4adc746dt46f2b14e0a1b0a0a@mail.gmail.com>
See bottom posted reply.
Russell Peterson wrote:
> Hello,
>
> The answer to your question "who calls start_armboot?" is answered by
> you ASM code below. Hint... take a close look at the regsiter you are
> loading.
>
> :-)
>
> Regards,
>
> Russell
>
>
> On 7/14/06, *Ram* <vshrirama at gmail.com <mailto:vshrirama@gmail.com>> wrote:
>
> Hi,
> Thanks for your response. I have gone much further and would like
> to know If
>
> ldr pc, _start_armboot
> _start_armboot:
> .word start_armboot
>
>
> Does this really invoke start_armboot?. This is because
> _start_armboot is what is
> stored in pc and not start_armboot and there is also a branch
> point _start_armboot (underscore start_armboot) Please see above.
>
> Actually the above declares a variable start_armboot and does not
> invoke the function
> start_armboot. If this is true, then who calls start_armboot?
[snip - I believe your observations are correct, but am not an expert]
> Thanks and Regards,
> sriram
Sriram:
C compiler naming convention prepends an underscore to the C function
name so the C function start_armboot() can be referenced from assembly
as a branch (call) to the label _start_armboot.
gvb
next prev parent reply other threads:[~2006-07-14 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 7:29 [U-Boot-Users] clarifications u-boot for arm Ram
2006-07-14 8:16 ` Wolfgang Denk
2006-07-14 13:51 ` Ram
2006-07-14 14:11 ` Russell Peterson
2006-07-14 14:23 ` Jerry Van Baren [this message]
2006-07-18 10:54 ` Andreas Schweigstill
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=44B7A8E8.3090004@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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